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

Update file TS-0041-oneM2M-SensorThings_interworking.md

parent dc458987
No related branches found
No related tags found
1 merge request!9SDS-2024-0141R02-ogc_ipe_communication_schema
Pipeline #1497 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 @ d85382dc
......@@ -185,7 +185,7 @@ The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'con
**Figure 6.1-1: OGC / STA-to-oneM2M data model mapping**
## 6.2 Communication Schema
## 6.2 Communication Flow
In order to transfer data from a oneM2M sensor to OGC/STA the IPE creates a <subscription> to the <container> resource with the desired data and when a new <contentInstance> is added it gets a <notification> message containing the <contentInstance> resource.
Figure 6.2-1 shows the oneM2M-to-OGC/STA direction. Based upon the creation of the <contentInstance> in the hosting CSE, the IPE gets a <notification> message including the <contentInstance>. The IPE constructs an "Observation" creation request and copies the 'content' attribute of the <contentInstance> to the 'result' attribute of the "Observation" shown in Figure 6.1-1 and sends it to the OGC/STA server.
......
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