Skip to content
Snippets Groups Projects
Commit 3d47ed02 authored by Ingo Friese's avatar Ingo Friese
Browse files

Update file TS-0041-oneM2M-SensorThings_interworking.md

parent 73732972
No related branches found
No related tags found
1 merge request!9SDS-2024-0141R02-ogc_ipe_communication_schema
Pipeline #1766 passed
Stage: checking
Stage: generation
This commit is part of merge request !9. Comments created here will be created in the context of that merge request.
Hide whitespace changes
Inline Side-by-side
TS-0041-oneM2M-SensorThings_interworking.md
+ 1
− 1
Edit View file @ 3d47ed02
......@@ -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 relies 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)
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment