Adaption of description and making HostVehicleData repeated

Adaption of description and making HostVehicleData repeated

Author: ThomasNaderBMW

osi_streaming.proto

@@ -4,65 +4,54 @@ import "osi_version.proto";
 import "osi_common.proto";
 import "osi_object.proto";
 import "osi_trafficlight.proto";
-//import "osi_hostvehicledata.proto";
+import "osi_hostvehicledata.proto";
 
 package osi3;
 
 //
-// ToDo: Rework Description
-// \brief The traffic update message is provided by traffic participant
-// models to provide updates to their position, state and future
-// trajectory back to the simulation environment. The message is
-// designed to update data of exactly one traffic participant,
-// optionally with an attached trailer. 
+// \brief This message is about partial updates from simulation entities.
 //
-// \note For reasons of convenience and consistency, the updated
-// information is provided as a MovingObject.  Certain fields of this
-// sub-message are not required to be set and will be ignored by the
-// simulation environment, because they are static information.
-// Instead of creating a seperate message type for only the non-static
-// information, re-use existing message.
+// First time message is being sent:
 //
-// RULE: Needs to include all stuff that changed.
+// ToDo
+//
+// Afterwards:
+// As streaming update this message contains objects of which at least one
+// property has changed. Unchanged properties are nevertheless sent.
+//
+// 
 //
 message Streaming
 {
     // The interface version used by the sender (traffic participant model).
     //
     optional InterfaceVersion version = 1;
 
-    // The data timestamp of the simulation environment. Zero time is arbitrary
-    // but must be identical for all messages. Zero time does not need to
-    // coincide with the UNIX epoch. Recommended is the starting time point of
-    // the simulation.
-    //
-    // \note For moving object update data the timestamp coincides both with
-    // the notional simulation time the data applies to and the time it was sent.
-    // There is no inherent latency for moving object update data, as opposed
-    // to sensor data.
+    // The data timestamp where the information of contained objects is calculated. 
+    // 
+    // Zero time is arbitrary but must be identical for all messages. 
+    // Zero time does not need to coincide with the UNIX epoch. 
+    // Recommended is the starting time point of the simulation.
     //
     optional Timestamp timestamp = 2;
 
-    // To discuss: Are they needed?
     // The list of stationary objects (excluding traffic signs and traffic
     // lights).
     //
     repeated StationaryObject stationary_object_update = 4;
 
-    // Updated traffic participant data
-    //
     // \note It is not expected that static fields are populated. If they
     // are, they may be ignored by the receiver of this message, for example, dimensions,
     // or vehicle category.  All dynamic fields should be populated where known,
     // for example, velocity, light states, or future trajectory.
     //
+    // ToDo: how to handle trailers?
     // \note The field is repeated because it is possible to have a trailer attached to
     // a vehicle, see MovingObject::VehicleClassification::has_trailer and
     // MovingObject::VehicleClassification::trailer_id. 
     //
     repeated MovingObject moving_object_update = 5;
 
-    // To discuss: Are they needed?
     // The list of traffic signs.
     //
     repeated TrafficSign traffic_sign = 6;
@@ -73,15 +62,15 @@ message Streaming
 
     // Conditions of the environment.
     //
-    optional EnvironmentalConditions environmental_conditions = 12;
+    optional EnvironmentalConditions environmental_conditions_update = 12;
 
     // Host vehicle data.
     //
     // Host vehicle data is data that the host vehicle knows about itself,
     // e.g. from location sensors, internal sensors and ECU bus data, etc.,
     // that is made available to sensors as input.
     //
-    optional HostVehicleData host_vehicle_data = 29;
+    repeated HostVehicleData host_vehicle_data_update = 29;
 
     // Entities that will no longer be updated, because they are considered
     // obsolete by the sender.