Introduce backchannel message TrafficCommandUpdate

Signed-off-by: Habedank Clemens <qxs2704@europe.bmw.corp>

Author: Habedank Clemens

osi_trafficcommandupdate.proto

@@ -0,0 +1,67 @@
+syntax = "proto2";
+
+option optimize_for = SPEED;
+
+import "osi_version.proto";
+import "osi_common.proto";
+
+package osi3;
+
+//
+// \brief This message enables the traffic participant model to send updates 
+// to the scenario engine about the execution of its received \c TrafficCommand input. While traffic 
+// actions are usually executed successfully by the traffic participant 
+// there may be actions which the traffic participant is not able to execute
+// either for capability or situation-specific reasons. This message gives
+// the traffic participant the basic possiblity to send feedback if an action 
+// cannot happen as requested by the \c TrafficCommand. Currently, it is out of
+// scope to standardize the exact reason for non-executability or failed execution 
+// because the reason can have multiple explantions. The point in time 
+// for this message to be sent is only restricted to be after the \c TrafficCommand  
+// with the corresponding traffic action(s) has been sent. The 
+// responsibility for deciding about successful or unsuccessful scenario execution
+// lies fully on the side of the scenario engine.  
+//
+// \note This interface is currently just a placeholder and could be
+// changed in experimental ways to support semantics of upcoming OpenSCENARIO 
+// versions. 
+//
+message TrafficCommandUpdate
+{
+    // 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. It is recommended to use zero timestamp as 
+    // the starting time point of the simulation.
+    //
+    optional Timestamp timestamp = 2;
+
+    // The ID of this traffic participant which must coincide with a prior sent ID, cf.
+    // \c TrafficCommand::traffic_participant_id.
+    //
+    optional Identifier traffic_participant_id = 3;
+
+    // Dismissed traffic action id(s) from the perspective of a traffic participant, if any.
+    //
+    // \note Dismissed traffic action id(s) identify actions which cannot be executed or 
+    // completed by the traffic participant. If more than one action id is supplied it means that
+    // multiple actions are regarded as dismissed. This field must have the same value(s) as 
+    // \c TrafficAction::ActionHeader::action_id of the prior sent \c TrafficCommand and must correspond
+    // to the same traffic participant.
+    //
+    // \Attention If an action is not dismissed, abortet by the scenario engine with a 
+    // \c TrafficAction::AbortActionsAction or ended by the scenario engine with a
+    // \c TrafficAction::EndActionsAction it is assumed that the traffic participant is 
+    // in the process of executing this action.
+    //
+    repeated Identifier dismissed_action_id = 4;
+
+    // Information about the reason of failure.
+    // 
+    // \note This is just a custom, informal string without a standardized meaning. 
+    //
+    optional string failure_reason = 5; 
+}