Skip to content
Snippets Groups Projects

SDS-2025-0016R02-ogc_ipe_configuration_aspects

Merged SDS-2025-0016R02-ogc_ipe_configuration_aspects
SDS-2025-0016-ogc_ipe_configuration_aspects into R5
Merged Ingo Friese requested to merge SDS-2025-0016-ogc_ipe_configuration_aspects into R5
Viewing commit f0a8a825
Prev Next
Show latest version
1 file
+ 5
− 5
Compare changes
  • Side-by-side
  • Inline
TS-0041-oneM2M-SensorThings_interworking.md
+ 5
− 5
@@ -204,13 +204,13 @@ Both directions of the data flow between the OGC/STA server and the IPE require
#### 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 an HTTP-POST message. The 'result' attribute of an "Observation" contains the sensor data.
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 an HTTP-POST message.
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 shall 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 subscribing, 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](media/config_ogc.png)
![Figure 6.3.1.1-1: Message flow from OGC/STA Client to OGC/STA Server to IPE](media/config_ogc.png)
**Figure 6.3.1.1-1: Message flow from OGC STA Client to OGC/STA Server to IPE**
**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
@@ -221,9 +221,9 @@ The creation of entities like "Datastream" and "Thing" requires several mandator
Once the "Thing" and "Datastream" entities are created, the IPE can send "Observations" to the OGC/STA server as HTTP POST messages. The interested OGC/STA client can then subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server and receive every "Observation" forwarded from the IPE (see Figure 6.3.1.2-1). Alternatively, the OGC/STA client may use an HTTP-GET request to pull the data as needed.
![Figure 6.3.1.2-1: Message flow from OGC STA Client to OGC/STA Server to IPE](media/config_ogc2.png)
![Figure 6.3.1.2-1: Message flow from IPE to OGC/STA Server to OGC/STA Client](media/config_ogc2.png)
**Figure 6.3.1.2-1: Message flow from OGC STA Client to OGC/STA Server to IPE**
**Figure 6.3.1.2-1: Message flow from IPE to OGC/STA Server to OGC/STA Client**
# Proforma copyright release text block