intro config

TS-0041-oneM2M-SensorThings_interworking.md

@@ -202,9 +202,15 @@ Figure 6.2-2 shows the OGC/STA-to-oneM2M direction. OGC/STA does not provide a p
 
 ## 6.3 Configuration Aspects
 
-In order to enable interworking, preparation is needed in both the oneM2M-CSE and the OGC/STA Server. These configuration steps could be initiated manually beforehand or by the IPE at startup time.
+### 6.3.0 Introduction
 
-![Figure 6.3-1: Both sides of the IPE configuration](media/config.png)
+In order to enable interworking, preparation is needed in both the oneM2M-CSE and the OGC/STA Server. These configuration steps could be initiated manually beforehand or by the IPE at startup time. Both directions of the data flow between OGC/STA Server and the IPE need their own configuration steps. A typical OGC/STA server has two protocol interfaces, HTTP and MQTT. The HTTP interface can be used for most operational tasks like creating and retrieving entities of the OGC data model <a href="#_ref_i.1">[i.1]</a>. The HTTP interface of OGC/STA does not support a publish/subscribe mechanism. To support a publish/subscribe mechanism, OGC/STA has foreseen an additional MQTT Broker, offering parties to subscribe to events they are interested in like e.g. incoming "Observations".
+
+![Figure 6.3.0-1: Both sides of the IPE configuration](media/config.png)
+
+**Figure 6.3.0-1: Both sides of the IPE configuration** 
+
+### 6.3.1 Configuration necessary on the OGC/STA Server side
 
 <mark>The following text is to be used when appropriate:</mark>