SDS-2025-0017R02-ogc_ipe_configuration_aspects_supl

Coversheet	Value
Meeting ID	TP#68
Work-item	WI-0100
Reason	wordings & revision

TS-0041-oneM2M-SensorThings_interworking.md

@@ -244,6 +244,53 @@ Once the destination-"Datastream" is created, the IPE can send an "Observation"
 
 **Figure 6.3.1.2-1: Message flow from IPE to OGC/STA Server to OGC/STA Client** 
 
+### 6.3.2 Configuration of the oneM2M CSE
+
+#### 6.3.2.0 Overview
+
+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, triggered 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 the data to be forwarded to OGC/STA server.
+
+![Figure 6.3.2.1-2: Configuration message flow for CSE to IPE direction](media/config_cse_flow13.png)
+
+**Figure 6.3.2.1-2: Configuration message flow for CSE to IPE direction** 
+
+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 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
+
+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](media/config_cse23.png)
+
+**Figure 6.3.2.2-1: Data message flow from IPE to CSE to AE** 
+
+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.
+
+![Figure 6.3.2.2-2: Configuration message flow for IPE to CSE direction](media/config_cse_flow23.png)
+
+**Figure 6.3.2.2-2: Configuration message flow for IPE to CSE direction** 
+
+The detailed configuration steps are shown in Figure 6.3.2.2-2:
+1)	The IPE requests to register an `<AE>` resource on the hosting CSE.
+2)	The hosting CSE evaluates the request, performs the appropriate checks, and registers the `<AE>` resource.
+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>`.
+5)	The hosting CSE evaluates the requests, performs the appropriate checks, and creates the `<container>` resource. 
+6)	The hosting CSE responds with a successful result message upon successful creation of the `<container>` resource; otherwise, it responds with an error.
 
 # Proforma copyright release text block
 <mark>This text box shall immediately follow after the heading of an element (i.e. clause or annex) containing a proforma or template which is intended to be copied by the user. Such an element shall always start on a new page.</mark>