From 227f5b4e20bf57f67d5317622e21a4120deb99bb Mon Sep 17 00:00:00 2001 From: Andreas Neubacher <andreas.neubacher@magenta.at> Date: Fri, 13 Sep 2024 13:23:40 +0000 Subject: [PATCH] Editorial changes: Corrected incorrect code for Figures --- TS-0041-oneM2M-SensorThings_interworking.md | 33 +++++++++------------ 1 file changed, 14 insertions(+), 19 deletions(-) diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md index 446a22a..a4b2db7 100644 --- a/TS-0041-oneM2M-SensorThings_interworking.md +++ b/TS-0041-oneM2M-SensorThings_interworking.md @@ -1,4 +1,4 @@ - + |oneM2M<br/>Technical Specification |oneM2M<br />Technical Specification | |-|-| @@ -139,20 +139,18 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in # 5 Introduction to OGC SensorThings API -The SensorThings API (STA) is a standard of the Open Geospatial Consortium (OGC). It provides a framework for communication and exchanging data between sensors and applications. The standard is devided in two parts. SensorThings API Part 1 is dedicated to sensing and was published in 2016 and updated in 2021 <a href="#_ref_1">[1]</a>. +The SensorThings API (STA) is a standard of the Open Geospatial Consortium (OGC). It provides a framework for communication and exchanging data between sensors and applications. The standard is devided in two parts. SensorThings API Part 1 is dedicated to sensing and was published in 2016 and updated in 2021. A STA-based architecture works in client/server mode. A sensor device pushes data to the SensorThings Server via HTTP. A SensorThings Server may also support MQTT protocol to support publish and subscribe capabilities. An interested application can subscribe to the MQTT-Broker, in order to get notified about new sensor events. -<figure> - <img src="media/STA_flow.png" alt="STA_message_flow"> - <figcaption>Figure 5-1 STA message flow</figcaption> -</figure> + -The data in the SensorThings server are organized as according to **Sensing Entities** (see Figure 5-2: Sensing Entities data model <a href="#_ref_1">[1]</a>). +**Figure 5-1 STA message flow** -<figure> - <img src="media/data_model.jpg" alt="data_model"> - <figcaption>Figure 5-2 STA Sensing Entities Data Model <a href="#_ref_1">[1]</a></figcaption> -</figure> +The data in the SensorThings server are organized as according to **Sensing Entities** (see Figure 5-2: Sensing Entities data model. + + + +**Figure 5-2 STA Sensing Entities Data Model** In the Sensing Entities Data Model events or sensor data are called "observations". Before a sensor is able to push an observation to the server it needs at least a 'Thing' and a 'Datastream' entity. This has to be created beforehand. One 'Thing' might have different 'Sensors', one 'Location' or many 'HistoricalLocations'. @@ -171,10 +169,9 @@ Figure 6.0-1 shows an architecture approach for an Interworking Proxy Entity (IP 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. -<figure> - <img src="media/STA_oneM2M_architekturbild_01.svg" alt="arch_overview"> - <figcaption>Figure 6.0-1: IPE architecture overview</figcaption> -</figure> + + +**Figure 6.0-1: IPE architecture overview** ## 6.1 OGC/STA-to-oneM2M Data Model Mapping @@ -184,11 +181,9 @@ According to oneM2M TS-0033 <a href="#_ref_2">[2]</a> a representation of a non- The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'content' attribute of a oneM2M <contentInstance>, and vice versa as shown in Figure 6.1-1. -<figure> - <img src="media/data_mapping.svg" alt="data_mapping"> - <figcaption>Figure 6.1-1: OGC / STA-to-oneM2M data model mapping</figcaption> -</figure> + +**Figure 6.1-1: OGC / STA-to-oneM2M data model mapping** <mark>The following text is to be used when appropriate:</mark> -- GitLab