@@ -204,7 +204,7 @@ Figure 6.2-2 shows the OGC/STA-to-oneM2M direction. OGC/STA does not provide a p
### 6.3.0 Introduction
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 <ahref="#_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".
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 STA Sensing Entities Data Model <ahref="#_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".
...
...
@@ -212,6 +212,18 @@ In order to enable interworking, preparation is needed in both the oneM2M-CSE an
### 6.3.1 Configuration necessary on the OGC/STA Server side
In Figure 6.3.1-1) a STA Client is connected to an OGC/SensorThings API Server and its data is forwarded to the IPE. The SensorThings Client publishes data to the SensorThings API-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 <ahref="#_ref_i.1">[i.1]</a> belongs to a "DataStream" (see Figure 5-2). This "DataStream" has an unique Id like e.g. {"@iot.id": "8715"} and topic name like e.g. {"sta-example-server-address.com/v1.0/Datastreams(8715)"}.
*Configuration step:* The IPE needs to subscribe to the relevant "DataStream" at the MQTT-Broker of the OGC/STA Server using its specific URL. After doing that the IPE receives every "Observation" that is pushed to that "DataStream".
**Figure 6.3.1-1: Message flow from OGC STA Client to OGC/STA Server to IPE**
* Weieter mit Abschnitt TR-0065 6.3.2.2
<mark>The following text is to be used when appropriate:</mark>
