@@ -194,11 +194,11 @@ The IPE needs to perform configuration steps at the hosting CSE.
...
@@ -194,11 +194,11 @@ The IPE needs to perform configuration steps at the hosting CSE.
#### 6.3.2.1 Communication direction oneM2M CSE towards IPE
#### 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 set 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 sets a `<subscription>` to the `<container>` and gets a `<notification>` message along with a `<contentInstance>`, when new data arrives.
**Figure 6.3.2.1-1: Data message flow from AE to CSE to IPE**
**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 data that should be forwarded to OGC/STA server.
...
@@ -213,19 +213,25 @@ The detailed configuration messages are shown in Figure 6.3.2.1-2:
...
@@ -213,19 +213,25 @@ The detailed configuration messages are shown in Figure 6.3.2.1-2:
#### 6.3.2.2 Communication direction IPE towards oneM2M CSE
#### 6.3.2.2 Communication direction IPE towards oneM2M CSE
In figure 6.3.2.2-1) a oneM2M AE creates a <subscription> to the <container> that is being used by the IPE. Subsequently the AE gets a <notification> along with data contained in a <contentInstance> every time the IPE creates a <contentInstance> in that <container>. ....
In figure 6.3.2.2-1 a oneM2M AE creates a `<subscription>` to the `<container>` in the CSE that is used by the IPE to store data from the OGC/STA server. Subsequently the AE gets a `<notification>` along with data contained in a `<contentInstance>` every time when the IPE creates new data.
**Figure 6.3.2.2-1: Data message flow from IPE to CSE to AE**
**Figure 6.3.2.1-1: Data message flow from AE to CSE to IPE**
If not existing a `<container>` and if necessary, also a related `<AE>` shall be created at the hosting CSE. The required URL(s) shall be available to the IPE during operation.
**Figure 6.3.2.2-2: Configuration message flow for IPE-to-CSE direction**
The detailed configuration messages are shown in Figure 6.3.3.2-2:
1) The IPE requests to create an `<AE>` resource on the Hosting CSE.
**Figure 6.3.2.1-2: Configuration message flow for CSE-to-IPE direction**
2) The Hosting CSE evaluates the request, performs the appropriate checks, and creates the `<AE>` resource.
3) Hosting CSE responds with the successful result of `<AE>` resource creation, otherwise it responds with an error.
4) The IPE requests to create a `<container>` under the `<AE>`.
5) The Hosting CSE evaluates the requests, performs the appropriate checks, and creates the `<container>` resources.
6) Hosting CSE responds with the successful result of `<container>` resource creation, otherwise it responds with an error.
