From d85382dc1fc07be0acf87ac4565eb9d58ed38d0b Mon Sep 17 00:00:00 2001 From: Ingo Friese <ingo.friese@telekom.de> Date: Thu, 14 Nov 2024 20:42:57 +0000 Subject: [PATCH] Update file TS-0041-oneM2M-SensorThings_interworking.md --- TS-0041-oneM2M-SensorThings_interworking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md index f5b1851..9a45f64 100644 --- a/TS-0041-oneM2M-SensorThings_interworking.md +++ b/TS-0041-oneM2M-SensorThings_interworking.md @@ -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. -- GitLab