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

6.3.2.1

parent 9076bbea
No related branches found
No related tags found
1 merge request!11SDS-2025-0017R02-ogc_ipe_configuration_aspects_supl
......@@ -190,26 +190,27 @@ The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'con
#### 6.3.2.0 Overview
The IPE needs to perform configuration steps at the hosting CSE.
The IPE needs to perform configuration steps on the hosting CSE.
#### 6.3.2.1 Communication direction oneM2M CSE towards IPE
In figure 6.3.2.1-1 a oneM2M AE triggert by a sensor sends data to the CSE by creating a `<contentInstance>` in a `<container>` at the CSE. The IPE sets a `<subscription>` to the `<container>` and gets a `<notification>` message along with a `<contentInstance>`, when new data arrives.
In Figure 6.3.2.1-1 a oneM2M AE, triggert by a sensor, sends data to the CSE by creating a `<contentInstance>` in a `<container>` at the CSE.
The IPE subscribes to the `<container>`by creating a `<subscription>` and receives a `<notification>` message along with the `<contentInstance>` when new data arrives.
![Figure 6.3.2.1-1: Message flow from AE to CSE to IPE](media/config_cse1.png)
**Figure 6.3.2.1-1: Message flow from AE to CSE to IPE**
The IPE shall set a `<subscription>` to the `<container>` that holds data that should be forwarded to OGC/STA server.
The IPE shall set a `<subscription>` to the `<container>` that holds the data to be forwarded to OGC/STA server.
![Figure 6.3.2.1-2: Configuration message flow for AE-to-CSE-to-IPE direction](media/config_cse_flow13.png)
**Figure 6.3.2.1-2: Configuration message flow for AE-to-CSE-to-IPE direction**
The detailed configuration messages are shown in Figure 6.3.2.1-2:
1) The IPE creates a `<subscription>` to the `<container>` that is appointed to hold data to be forwarded to the OGC/STA side.
The detailed configuration steps are shown in Figure 6.3.2.1-2:
1) The IPE creates a `<subscription>` to the `<container>` that is appointed to hold the data to be forwarded to the OGC/STA side.
2) The hosting CSE evaluates the request, performs the appropriate checks, and creates the `<subscription>` resource.
3) The hosting CSE responds with the successful result of the `<subscription>` resource creation, otherwise it responds with an error.
3) The hosting CSE responds with the successful result message of the `<subscription>` resource creation; otherwise, it responds with an error.
#### 6.3.2.2 Communication direction IPE towards oneM2M CSE
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment