|
| 1 | +syntax = "proto2"; |
| 2 | + |
| 3 | +option optimize_for = SPEED; |
| 4 | + |
| 5 | +import "osi_version.proto"; |
| 6 | +import "osi_common.proto"; |
| 7 | +import "osi_environment.proto"; |
| 8 | +import "osi_object.proto"; |
| 9 | +import "osi_trafficsign.proto"; |
| 10 | +import "osi_trafficlight.proto"; |
| 11 | +import "osi_hostvehicledata.proto"; |
| 12 | + |
| 13 | +package osi3; |
| 14 | + |
| 15 | +// |
| 16 | +// \brief The streaming update interface enables simulation entities to send |
| 17 | +// partial updates to other modules that favor performance (especially latency) |
| 18 | +// over data completeness/consistency (e.g. visualization applications). |
| 19 | +// |
| 20 | +// Static and/or non-relevant objects can be omitted as required for the |
| 21 | +// specific use case. Adding an object's unique id to the repeated field \c |
| 22 | +// obsolete_id indicates that it will no longer be updated from then on. |
| 23 | +// |
| 24 | +// \note The receiver of partial streaming update messages can only rely on the |
| 25 | +// most up-to-date information at the corresponding timestamp. E.g. omitting |
| 26 | +// objects does not indicate static behaviour but it may be sufficient for the |
| 27 | +// use case to update certain objects at a later point in time. |
| 28 | +// |
| 29 | +message StreamingUpdate |
| 30 | +{ |
| 31 | + // The interface version used by the sender. |
| 32 | + // |
| 33 | + optional InterfaceVersion version = 1; |
| 34 | + |
| 35 | + // The data timestamp where the information of contained objects is calculated. |
| 36 | + // |
| 37 | + // Zero time is arbitrary but must be identical for all messages. |
| 38 | + // Zero time does not need to coincide with the UNIX epoch. |
| 39 | + // Recommended is the starting time point of the simulation. |
| 40 | + // |
| 41 | + optional Timestamp timestamp = 2; |
| 42 | + |
| 43 | + // The list of stationary objects (excluding traffic signs and traffic |
| 44 | + // lights). |
| 45 | + // |
| 46 | + repeated StationaryObject stationary_object_update = 3; |
| 47 | + |
| 48 | + // The list of moving objects. |
| 49 | + // |
| 50 | + repeated MovingObject moving_object_update = 4; |
| 51 | + |
| 52 | + // The list of traffic signs. |
| 53 | + // |
| 54 | + repeated TrafficSign traffic_sign_update = 5; |
| 55 | + |
| 56 | + // The list of traffic lights. |
| 57 | + // |
| 58 | + repeated TrafficLight traffic_light_update = 6; |
| 59 | + |
| 60 | + // Conditions of the environment. |
| 61 | + // |
| 62 | + optional EnvironmentalConditions environmental_conditions_update = 7; |
| 63 | + |
| 64 | + // Host vehicle data. |
| 65 | + // |
| 66 | + // Host vehicle data is data that the host vehicle knows about itself, |
| 67 | + // e.g. from location sensors, internal sensors and ECU bus data, etc., |
| 68 | + // that is made available to sensors as input. |
| 69 | + // |
| 70 | + // The ID inside this message allows an association to moving object data. |
| 71 | + // |
| 72 | + repeated HostVehicleData host_vehicle_data_update = 8; |
| 73 | + |
| 74 | + // Entities that will no longer be updated, because they are considered |
| 75 | + // obsolete by the sender. |
| 76 | + // |
| 77 | + // \note IDs are globally unique. |
| 78 | + // |
| 79 | + repeated Identifier obsolete_id = 9; |
| 80 | +} |
0 commit comments