@@ -210,29 +210,29 @@ The IPE shall set a `<subscription>` to the `<container>` that holds the data to
...
@@ -210,29 +210,29 @@ The IPE shall set a `<subscription>` to the `<container>` that holds the data to
The detailed configuration steps are shown in Figure 6.3.2.1-2:
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.
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.
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 message of the `<subscription>` resource creation; otherwise, it responds with an error.
3) The hosting CSE responds with a successful result message of the `<subscription>` resource creation; otherwise, it responds with an error.
#### 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>` 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.
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 receives 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.2-1: Data message flow from IPE to CSE to AE**
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.
If the`<container>`does not exist, and if necessary, a related `<AE>` shall be created on the hosting CSE. The required URLs shall be available to the IPE during operation.
**Figure 6.3.2.2-2: Configuration message flow for IPE-to-CSE direction**
**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:
The detailed configuration steps are shown in Figure 6.3.2.2-2:
1) The IPE requests to create an `<AE>` resource on the Hosting CSE.
1) The IPE requests to create an `<AE>` resource on the hosting CSE.
2) The Hosting CSE evaluates the request, performs the appropriate checks, and creates the `<AE>` resource.
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.
3) The hosting CSE responds with a successful result message upon successful creation of the`<AE>` resource; otherwise, it responds with an error.
4) The IPE requests to create a `<container>` under the `<AE>`.
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.
5) The hosting CSE evaluates the requests, performs the appropriate checks, and creates the `<container>` resource.
6) Hosting CSE responds with the successful result of`<container>` resource creation, otherwise it responds with an error.
6) The hosting CSE responds with a successful result message upon successful creation of the`<container>` resource; otherwise, it responds with an error.
