Contribution SDS-2025-0017R04-ogc_ipe_configuration_aspects_supl merged into R5

Original contribution: SDS-2025-0017-ogc_ipe_configuration_aspects_supl

See merge request !11

TS-0041-oneM2M-SensorThings_interworking.md

@@ -244,6 +244,73 @@ 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 General Configuration Aspects
+
+The IPE needs to perform configuration steps on the hosting CSE.
+
+The IPE shall register itself as an Application Entity (AE) that is represented as an *`<AE>`* resource in a oneM2M resource tree.
+
+The CSE uses notifications to communicate new events to the IPE (AE). Therefore, the *`<AE>`* resource shall have the *requestReachability* (rr) attribute set to 'true'.
+
+The *`<AE>`* resource shall have a *pointOfAccess* (poa) attribute giving the protocol and address that the IPE is going to use to receive notifications from the CSE.
+
+The message flow for the creation of an *`<AE>`* resource is shown in Figure 6.3.2.0-1:
+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 response upon successful creation of the *`<AE>`* resource; otherwise, it responds with an error.
+
+![Figure 6.3.2.0-1: Message flow of an *`<AE>`* resource creation in oneM2M](media/create_ae_flow.png)
+
+**Figure 6.3.2.0-1: Message flow of an *`<AE>`* resource creation in oneM2M** 
+
+#### 6.3.2.1 Communication direction oneM2M CSE towards IPE
+
+It needs two *`<container>`* resources in the CSE for the operation of the IPE, one for outgoing data and one for incoming data.
+The *`<container>`* resource that is appointed to hold the data to be forwarded to the OGC/STA side (outgoing data) has to be created, if not already existing.
+
+The message flow for the creation of a *`<container>`* resource is shown in Figure 6.3.2.1-1:
+1)	The IPE sends a request to create a *`<container>`* resource.
+2)	The hosting CSE evaluates the request, performs the appropriate checks, and creates the *`<container>`* resource. 
+3)	The hosting CSE responds with a successful result response upon successful creation of the *`<container>`* resource; otherwise, it responds with an error.
+
+![Figure 6.3.2.1-1: Message flow of an *`<container>`* resource creation in oneM2M](media/create_container_flow.png)
+
+**Figure 6.3.2.1-1: Message flow of an *`<container>`* resource creation in oneM2M** 
+
+A *`<subscription>`* resource shall be created under this *`<container>`* resource.
+
+The *`<subscription>`* resource shall have the *notificationURI* attribute set to the *resourceID* of the *`<AE>`* resource. 
+
+The message flow for the creation of an *`<subscription>`* resource is shown in Figure 6.3.2.1-2:
+1)	The IPE sends a creation request for a *`<subscription>`* resource to the *`<container>`* resource that is appointed to hold the data to be forwarded to the OGC/STA side.
+2)	The hosting CSE evaluates the request and performs the appropriate checks and creates the *`<subscription>`* resource.
+3)	The hosting CSE responds with a successful result response of the *`<subscription>`* resource creation; otherwise, it responds with an error.
+
+![Figure 6.3.2.1-2: Message flow of an *`<subscription>`* resource creation in oneM2M](media/create_subscription_flow1.png)
+
+**Figure 6.3.2.1-2: Message flow of an *`<subscription>`* resource creation in oneM2M** 
+
+The CSE is now prepared to send data from oneM2M to OGC / STA via the IPE. As shown in Figure 6.3.2.1-3, a oneM2M Application Entity (AE), triggered by a sensor, sends data to the CSE by creating a *`<contentInstance>`* resource under the *`<container>`* resource that was appointed for outgoing data.
+Since the IPE has subscribed to this *`<container>`* resource it receives a notification message along with all attributes of the *`<contentInstance>`* resource when new data arrives. The IPE maps the data from oneM2M to OGC / STA as described in 6.1 .
+
+![Figure 6.3.2.1-3: Message flow from AE to CSE to IPE](media/config_cse1.png)
+
+**Figure 6.3.2.1-3: Message flow from AE to CSE to IPE** 
+
+#### 6.3.2.2 Communication direction IPE towards oneM2M CSE
+
+The *`<container>`* resource that is appointed to hold the data from the OGC/STA side (incoming data) has to be created, if not already existing.
+The message flow for the creation of a *`<container>`* resource is shown in Figure 6.3.2.1-1.
+
+The CSE is now prepared to receive data from OGC / STA via the IPE. The IPE sends data as *`<contentInstance>`* resources to the dedicated *`<container>`* resource. If other oneM2M Application Entities are interested in this data, they may subscribe to the dedicated *`<container>`* resource. Alternatively, they can retrieve *`<contentInstance>`* resources from it in polling mode.
+
+ In Figure 6.3.2.2-1, the IPE (AE) sends data as *`<contentInstance>`* resources to the dedicated *`<container>`* resource. Subsequently, the AE receives a notification along with data contained in a *`<contentInstance>`* resource 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** 
 
 # 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>