Update architecture_overview.adoc by osi-streaming

Signed-off-by: Thomas Nader <thomas.nader@bmw.de>
Signed-off-by: Pierre R. Mai <pmai@pmsf.de>

Author: ThomasNaderBMW

doc/architecture/architecture_overview.adoc

@@ -32,6 +32,10 @@ The following figure shows a more advanced use case for traffic participants.
 .Traffic participant with sensor models, AD function, and dynamic model
 image::{images_open_simulation_interface}/osi-traffic-participant-advanced.png[1100]
 
+[#fig-interface-streaming]
+.Interface for Streaming
+image::{images_open_simulation_interface}/osi-streaming-principle.png[1100]
+
 The `HostVehicleData` interface describes the measured internal states of a traffic participant.
 OSI currently provides only limited support for data structures that describe measured internal states of traffic participants.
 One example would be the `MotionRequest` interface that can be used to communicate the results of the behavior planning to the dynamic model.
@@ -48,4 +52,4 @@ However, this does not mean that it is optional to fill the field.
 For the purpose of providing a complete interface, all existing fields should be set, unless not setting a field carries a specific meaning, as indicated in the accompanying comment.
 
 NOTE: All field numbers equal to or greater than 10000 are available for user-specific extensions via custom fields.
-No future evolution of OSI will therefore use field numbers equal to or greater than 10000.
+No future evolution of OSI will therefore use field numbers equal to or greater than 10000.