diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md
index 48162963b8ab9d360f62ec4b1804fa2a81b1ede8..f706ce84654056bb03bfc370477df0b541c0cab6 100644
--- a/TS-0041-oneM2M-SensorThings_interworking.md
+++ b/TS-0041-oneM2M-SensorThings_interworking.md
@@ -190,10 +190,42 @@ The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'con
### 6.3.0 Introduction
-In order to enable interworking, preparation is needed in both the oneM2M-CSE and the OGC/STA server. Both directions of the data flow between OGC/STA server and the IPE need their own configuration steps.
+In order to enable interworking, preparation is needed in both oneM2M-CSE and OGC/STA server (Figure 6.3.0-1).
+
-<mark>The following text is to be used when appropriate:</mark>
+**Figure 6.3.0-1: Both sides of the IPE configuration**
+
+### 6.3.1 Configuration necessary on the OGC/STA Server side
+
+#### 6.3.1.0 Configuration necessary on the OGC/STA Server
+
+Both directions of the data flow between OGC/STA server and the IPE need their own configuration steps.
+
+#### 6.3.1.1 Communication direction OGC/STA Server towards IPE
+
+In Figure 6.3.1.1-1 an OGC/STA client is connected to an OGC/STA server and its data is forwarded to the IPE. The OGC/STA client publishes data to the OGC/STA server via a HTTP-Post message. The 'result' attribute of an "Observation" contains the sensor data.
+An "Observation" according to STA Sensing Entities Data Model <a href="#_ref_i.1">[i.1]</a> belongs to a "Datastream" (see Figure 5-2).
+
+The IPE needs to subscribe to the relevant "Datastream" at the MQTT-Broker of the OGC/STA Server using its specific URL or topic like e.g. {"sta-example-server-address.com/v1.0/Datastreams(8715)"}. After doing that the IPE receives every "Observation" that is pushed to that "Datastream".
+
+
+
+**Figure 6.3.1.1-1: Message flow from OGC STA Client to OGC/STA Server to IPE**
+
+#### 6.3.1.2 Communication direction IPE towards OGC/STA Server
+
+The IPE requires a destination-"Datastream" in order to send an "Observation". In case there is no associated "Datastream" on the OGC/STA server it MUST be created. This MAY be done beforehand or at start-up time of the IPE and is up to the implementation.
+When a "Datastream" is created at the OGC/STA server reference ID (e.g. {"@iot.id:3635353"}) is given back.
+This reference is needed by the IPE to relate an "Observation" to a "Datastream" and MUST be available during IPE operation. Appart from the "Datastream" additional entitites of the OGC data model like e.g. "Location" or "Sensor" MAY be created.
+
+The creation of entities like "Datastream" and "Thing" requires a number of mandatory properties that shall be known at configuration time, e.g. 'name' and 'description'. These property fields MAY automatically derived e.g. from the "Label" or "ResourceName" attributes of the regarded oneM2M `<AE>` or `<container>` during IPE configuration. The OGC/STA procedures for creating OGC entities are described in SensorThing API documentation <a href="#_ref_i.1">[i.1]</a>.
+
+When "Thing" and "Datastream" entities are created the IPE is able to send "Observations" to the OGC/STA server as HTTP POST messages. The interested OGC/STA Client can now subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server and thus getting every "Observation" forwarded from the IPE (see Figure 6.3.1.2-1)
+
+
+
+**Figure 6.3.1.2-1: Message flow from OGC STA Client to OGC/STA Server to IPE**
# Proforma copyright release text block
diff --git a/media/config.png b/media/config.png
new file mode 100644
index 0000000000000000000000000000000000000000..b74bfd68183b936fe76b5fa4fe5d994b424dc793
Binary files /dev/null and b/media/config.png differ
diff --git a/media/config_ogc.png b/media/config_ogc.png
new file mode 100644
index 0000000000000000000000000000000000000000..8c12246ccc79e918bb313447cc8eba244ce52b97
Binary files /dev/null and b/media/config_ogc.png differ