@@ -185,18 +185,31 @@ The IPE shall map the 'result' attribute of an OGC/STA 'Observation' to the 'con
**Figure 6.1-1: OGC / STA-to-oneM2M data model mapping**
<mark>The following text is to be used when appropriate:</mark>
### 6.3.2 Configuration of the oneM2M CSE
#### 6.3.3.0 Overview
#### 6.3.2.0 Overview
The IPE needs to perform configuration steps at 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 set 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**
The IPE needs also to perform configuration steps at the hosting CSE.
The IPE shall set a `<subscription>` to the `<container>` that holds data that should be forwarded to OGC/STA server.
#### Communication direction oneM2M CSE towards IPE

The...
**Figure 6.3.2.1-2: Configuration message flow for 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.
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.