Skip to content
Snippets Groups Projects

SDS-2025-0017R04-ogc_ipe_configuration_aspects_supl

Merged SDS-2025-0017R04-ogc_ipe_configuration_aspects_supl
SDS-2025-0017-ogc_ipe_configuration_aspects_supl into R5
Merged Ingo Friese requested to merge SDS-2025-0017-ogc_ipe_configuration_aspects_supl into R5
Compare
and
8 files
+ 48
− 1
Compare changes
  • Side-by-side
  • Inline
Files
8
TS-0041-oneM2M-SensorThings_interworking.md
+ 67
− 0
@@ -180,7+180,7 @@
- sensor (IoT-data); and
- administrative data (like historic locations or historic products IDs).
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. The data type of the 'result' field of an "Observation" is according to SensorThings API <a href="#_ref_i.1">[i.1]</a> 'any' and depends on the 'observationType' defined in the associated "Datastream". The 'content' attribute of an oneM2M instance may be stringified data <a href="#_ref_3">[3]</a> understandable with the help of the 'contentInfo' attribute. The 'contentInfo' attribute on the oneM2M side may be added by the IPE. The original timestamps, present in the "Observation" as 'phenomenonTime' and in the `<contentInstance>` as "creationTime," shall be discarded. These timestamps are to be reset by the OGC /STA server and the CSE. They may be transmitted for informational purposes as part of the 'result' or the 'content' fields.
![Figure 6.1-1: OGC / STA-to-oneM2M data model mapping](media/data_mapping.svg)
@@ -188,7+188,7 @@
## 6.2 Communication Flow
Figure 6.2-1 shows the oneM2M-to-OGC/STA direction. In order to transfer data from a oneM2M sensor to the OGC/STA server the IPE creates a `<subscription>` to the `<container>` resource in the CSE containing the desired data. Triggered by a sensor event a new `<contentInstance>` is added to the `<container>` by the `<AE>`. The IPE gets a `<notification>` containing the `<contentInstance>` resource.
The IPE constructs an "Observation" creation request and copies the 'content' attribute of the `<contentInstance>` to the 'result' attribute of the "Observation" and sends it to a "Datastream" to be created as detailed in Section 6.3.1 at the OGC/STA server. The OGC/STA applcation gets the sensor data either by polling the OGC/STA server or subscribing to the corresponding "Datastream" at the MQTT broker of 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**
Figure 6.2-2 shows the OGC/STA-to-oneM2M direction. The IPE subscribes to the desired "Datastream" of the MQTT-Broker at the OGC/STA server. The OGC/STA server publishes a new "Observation" via the MQTT broker triggered by a OGC/STA sensor. The IPE creates a `<contentInstance>` in a container, to be created as detailed in Section 6.3.2 in the CSE and copies the 'result' attribute of the "Observation" to the 'content' attribute of the `<contentInstance>`. The oneM2M applcation gets the sensor data either by polling the CSE or subscribing to the desired `<container>` at the CSE.
![Figure 6.2-2: Communication OGC/STA-to-oneM2M direction](media/com_flow_2.png)
@@ -208,7+208,7 @@
### 6.3.0 Introduction
To enable interworking, preparation is required for both the oneM2M-CSE and the OGC/STA server (see Figure 6.3.0-1). As described in Section 6.0, the IPE maps data from an OGC/STA "Observation" to a oneM2M `<contentInstance>` and vice versa. This specification defines a 1-to-1 relationship in each direction between the "Datastream" associated with the "Observation" and the `<container>` associated with the `<contentInstance>`. An IPE may implement multiple 1-to-1 relationships.
![Figure 6.3.0-1: Both sides of the IPE configuration](media/config.png)
@@ -236,7+236,7 @@
The IPE requires a destination-"Datastream" to send an "Observation" containing data from the oneM2M side. If no associated "Datastream" exists on the OGC/STA server, it shall be created. This can be done beforehand or at the IPE's start-up, depending on the implementation.
When a "Datastream" is created on the OGC/STA server, a reference ID (e.g. {"@iot.id:3635353"}) is returned. This reference is required by the IPE to associate an "Observation" with a "Datastream" and shall be available during IPE operation. In addition to the "Datastream" other entities of the STA Sensing Entities Data Model <a href="#_ref_i.1">[i.1]</a>, such as "Location" or "Sensor," may be created.
The creation of entities like "Datastream" and "Thing" requires several mandatory properties that shall be known at configuration time (e.g., 'name' and 'description'). These property fields may be automatically derived, for example, from the "Label" or "ResourceName" attributes of the corresponding oneM2M `<container>` resource or if existing, from the corresponding `<AE>` resource during IPE configuration. The OGC/STA procedures for creating OGC entities are described in SensorThing API documentation <a href="#_ref_i.1">[i.1]</a>.
Once the destination-"Datastream" is created, the IPE can send an "Observation" to the OGC/STA server as HTTP POST message. An interested OGC/STA client can subscribe to the destination-"Datastream" at the MQTT Broker of the OGC/STA server to receive each "Observation" forwarded by the IPE (see Figure 6.3.1.2-1). Alternatively, the OGC/STA client may use an HTTP-GET request to retrieve the data as needed.
@@ -244,7+244,7 @@
**Figure 6.3.1.2-1: Message flow from IPE to OGC/STA Server to OGC/STA Client**
### 6.3.2 Configuration of the oneM2M CSE
#### 6.3.2.0 General Configuration Aspects
The IPE needs to perform configuration steps on the hosting CSE.
The IPE shall register itself as an Application Entity (AE) that is represented as an *`<AE>`* resource in a oneM2M resource tree.
The CSE uses notifications to communicate new events to the IPE (AE). Therefore, the *`<AE>`* resource shall have the *requestReachability* (rr) attribute set to 'true'.
The *`<AE>`* resource shall have a *pointOfAccess* (poa) attribute giving the protocol and address that the IPE is going to use to receive notifications from the CSE.
The message flow for the creation of an *`<AE>`* resource is shown in Figure 6.3.2.0-1:
1) The IPE requests to register an *`<AE>`* resource on the hosting CSE.
2) The hosting CSE evaluates the request, performs the appropriate checks, and registers the *`<AE>`* resource.
3) The hosting CSE responds with a successful result response upon successful creation of the *`<AE>`* resource; otherwise, it responds with an error.
![Figure 6.3.2.0-1: Message flow of an *`<AE>`* resource creation in oneM2M](media/create_ae_flow.png)
**Figure 6.3.2.0-1: Message flow of an *`<AE>`* resource creation in oneM2M**
#### 6.3.2.1 Communication direction oneM2M CSE towards IPE
It needs two *`<container>`* resources in the CSE for the operation of the IPE, one for outgoing data and one for incoming data.
The *`<container>`* resource that is appointed to hold the data to be forwarded to the OGC/STA side (outgoing data) has to be created, if not already existing.
The message flow for the creation of a *`<container>`* resource is shown in Figure 6.3.2.1-1:
1) The IPE sends a request to create a *`<container>`* resource.
2) The hosting CSE evaluates the request, performs the appropriate checks, and creates the *`<container>`* resource.
3) The hosting CSE responds with a successful result response upon successful creation of the *`<container>`* resource; otherwise, it responds with an error.
![Figure 6.3.2.1-1: Message flow of an *`<container>`* resource creation in oneM2M](media/create_container_flow.png)
**Figure 6.3.2.1-1: Message flow of an *`<container>`* resource creation in oneM2M**
A *`<subscription>`* resource shall be created under this *`<container>`* resource.
The *`<subscription>`* resource shall have the *notificationURI* attribute set to the *resourceID* of the *`<AE>`* resource.
The message flow for the creation of an *`<subscription>`* resource is shown in Figure 6.3.2.1-2:
1) The IPE sends a creation request for a *`<subscription>`* resource to the *`<container>`* resource that is appointed to hold the data to be forwarded to the OGC/STA side.
2) The hosting CSE evaluates the request and performs the appropriate checks and creates the *`<subscription>`* resource.
3) The hosting CSE responds with a successful result response of the *`<subscription>`* resource creation; otherwise, it responds with an error.
![Figure 6.3.2.1-2: Message flow of an *`<subscription>`* resource creation in oneM2M](media/create_subscription_flow1.png)
**Figure 6.3.2.1-2: Message flow of an *`<subscription>`* resource creation in oneM2M**
The CSE is now prepared to send data from oneM2M to OGC / STA via the IPE. As shown in Figure 6.3.2.1-3, a oneM2M Application Entity (AE), triggered by a sensor, sends data to the CSE by creating a *`<contentInstance>`* resource under the *`<container>`* resource that was appointed for outgoing data.
Since the IPE has subscribed to this *`<container>`* resource it receives a notification message along with all attributes of the *`<contentInstance>`* resource when new data arrives. The IPE maps the data from oneM2M to OGC / STA as described in 6.1 .
![Figure 6.3.2.1-3: Message flow from AE to CSE to IPE](media/config_cse1.png)
**Figure 6.3.2.1-3: Message flow from AE to CSE to IPE**
#### 6.3.2.2 Communication direction IPE towards oneM2M CSE
The *`<container>`* resource that is appointed to hold the data from the OGC/STA side (incoming data) has to be created, if not already existing.
The message flow for the creation of a *`<container>`* resource is shown in Figure 6.3.2.1-1.
The CSE is now prepared to receive data from OGC / STA via the IPE. The IPE sends data as *`<contentInstance>`* resources to the dedicated *`<container>`* resource. If other oneM2M Application Entities are interested in this data, they may subscribe to the dedicated *`<container>`* resource. Alternatively, they can retrieve *`<contentInstance>`* resources from it in polling mode.
In Figure 6.3.2.2-1, the IPE (AE) sends data as *`<contentInstance>`* resources to the dedicated *`<container>`* resource. Subsequently, the AE receives a notification along with data contained in a *`<contentInstance>`* resource every time when the IPE creates new data.
![Figure 6.3.2.2-1: Data message flow from IPE to CSE to AE](media/config_cse23.png)
**Figure 6.3.2.2-1: Data message flow from IPE to CSE to AE**
# Proforma copyright release text block
<mark>This text box shall immediately follow after the heading of an element (i.e. clause or annex) containing a proforma or template which is intended to be copied by the user. Such an element shall always start on a new page.</mark>