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

pic description

parent a0ce6488
Branches
No related tags found
1 merge request!9SDS-2024-0141R02-ogc_ipe_communication_schema
......@@ -190,11 +190,15 @@ The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'con
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.
![Figure 6.2-1 Communication oneM2M-to-OGC/STA direction](media/com_flow_1.png)
![Figure 6.2-1: Communication oneM2M-to-OGC/STA direction](media/com_flow_1.png)
**Figure 6.2-1: Communication oneM2M-to-OGC/STA direction**
Figure 6.2-2 shows the OGC/STA-to-oneM2M direction. OGC/STA does not provide a publish/subscribe mechanism on HTTP protocol level, but OGC allows an optional MQTT extension for STA services <a href="#_ref_i.1">[i.1]</a>. The IPE subscribes to the MQTT-Broker of the OGC/STA server. The OGC/STA server publishes its new "Observation" via the MQTT broker. The IPE creates a &lt;contentInstance&gt; using a HTTP request and copies the 'result' attribute of the "Observation" to the 'content' attribute of the &lt;contentInstance&gt;. The &lt;container&gt; may be created beforehand at the hosting CSE where the IPE &lt;contentInstance&gt; resources are stored. All interested applications may subscribe to this &lt;container&gt; resource.
![Figure 6.2-2 Communication OGC/STA-to-oneM2M direction](media/com_flow_2.png)
![Figure 6.2-2: Communication OGC/STA-to-oneM2M direction](media/com_flow_2.png)
**Figure 6.2-2: Communication OGC/STA-to-oneM2M direction**
## 6.3 Message Flow
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment