search

OpenSimulationInterface / open-simulation-interface

A generic interface for the environmental perception of automated driving functions in virtual scenarios.
Other
270 stars 126 forks source link

communications #324

Open horiachirculescu opened 5 years ago

horiachirculescu commented 5 years ago

Hello,

I am just wondering if it usefull to actually simulate the communications with other moving/stationary vehicles/stationary various info stations/etc.... Maybe using osi3::DetectedMovingObject::ConnectedMovingObject osi3::DetectedStationaryObject::ConnectedStationaryObject

The last one could be used also for parking lots...

mbencik commented 5 years ago

What does mean communication? Defining relations between who can communicate with who, or something else? What would be a connected object?

horiachirculescu commented 5 years ago

Hello,

A connected object could be another car (stationary or not) saying that "a queue is formed ahead, slow down", a parking meter from a parking lot saying "3 small parking spaces and 1 large truck parking space availlable at the moment", or an intelligent street light saying that "there are 12 seconds until green light", or a petrol station saying that "EV fast charger not availlable at the moment". Communications can be perfomed using LoRA, basically an IoT mesh of low-powered sensors/PLCs.

pmai commented 5 years ago

I think there is room to model such information sensors (i.e. the part of the vehicle that does the actual communication with other vehicles/stationary objects) and actors (i.e. the part of the vehicle that sends information to other vehicles/stationary objects); I think seperate messages might have to be defined, since the overlap between non-information sensors and information sensors seems restricted to few common features. However looking into how this data can also be mapped to additional fields in the common sensor data output message could also be made to work.

A draft PR for something like this would definitely be interesting.