@@ -214,13 +214,13 @@ The detailed configuration steps are shown in Figure 6.3.2.1-2:
#### 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. The IPE creates a `<contentInstance>` in the dedicated `<container>`. Subsequently, the AE receives 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 destination-`<container>` in the CSE that is used by the IPE to store data from the OGC/STA server. The IPE creates a `<contentInstance>` in the dedicated `<container>`. 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**
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.
If the destination `<container>` does not exist, it shall be created. If the creation of a `<container>` requires a related `<AE>`, the `<AE>` shall be registered on the hosting CSE. The required URLs shall be available to the IPE during operation.
