Skip to content
Snippets Groups Projects

SDS-2024-0141R02-ogc_ipe_communication_schema

Merged SDS-2024-0141R02-ogc_ipe_communication_schema
SDS-2024-0141-ogc_ipe_communication_schema into R5
Merged Ingo Friese requested to merge SDS-2024-0141-ogc_ipe_communication_schema into R5
Compare
and
Show latest version
1 file
+ 2
− 2
Compare changes
  • Side-by-side
  • Inline
TS-0041-oneM2M-SensorThings_interworking.md
+ 2
− 2
@@ -167,7 +167,7 @@ The Sensing Entities data model and the purpose of data within the data model di
Figure 6.0-1 shows an architecture approach for an Interworking Proxy Entity (IPE) between oneM2M and the OGC SensorThings API. The IPE is located between a oneM2M CSE and an OGC/SensorThings API (STA)-Server.
The basic interworking enables applications that are connected to an oneM2M-based system to get data from sensors that are connected to an OGC/STA server. Furthermore, an application that is connected to an OGC/STA server will be able to get data from sensors that are connected to an oneM2M-based system.
The basic interworking enables applications that are connected to an oneM2M-based system to get data from sensors that are connected to an OGC/STA server. Furthermore, an application that is connected to an OGC/STA server will be able to get data from sensors that are connected to an oneM2M-based system. The communication flow of the IPE SHALL rely on HTTP and MQTT. The MQTT protocol enables publish-subscribe functionality for the OGC side, as specified in the MQTT extension of the SensorThings API <a href="#_ref_i.1">[i.1]</a>.
![Figure 6.0-1: IPE architecture overview](media/STA_oneM2M_architekturbild_01.svg)
@@ -220,7 +220,7 @@ An "Observation" according to STA Sensing Entities Data Model <a href="#_ref_i.1
![Figure 6.3.1-1: Message flow from OGC STA Client to OGC/STA Server to IPE](media/config_ogc.png)
**Figure 6.3.1-1: Message flow from OGC STA Client to OGC/STA Server to IPE**
g
<mark>The following text is to be used when appropriate:</mark>