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

@@ -203,9 +203,9 @@ The IPE subscribes to the `<container>`by creating a `<subscription>` and receiv
 
 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 AE-to-CSE-to-IPE direction](media/config_cse_flow13.png)
+![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 AE-to-CSE-to-IPE direction** 
+**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.
@@ -222,9 +222,9 @@ In Figure 6.3.2.2-1, a oneM2M AE creates a `<subscription>` to the `<container>`
 
 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](media/config_cse_flow23.png)
+![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** 
+**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 create an `<AE>` resource on the hosting CSE.