Update 4 files

- /media/config_cse23.png
- /media/config_cse_flow23.png
- /media/config_cse_flow13.png
- /TS-0041-oneM2M-SensorThings_interworking.md

TS-0041-oneM2M-SensorThings_interworking.md

@@ -202,9 +202,9 @@ In figure 6.3.2.1-1 a oneM2M `<AE>` triggert by a sensor sends data to the CSE b
 
 The IPE shall set a `<subscription>` to the `<container>` that holds data that should be forwarded to OGC/STA server.
 
-![Figure 6.3.2.1-2: Configuration message flow for CSE-to-IPE direction](media/config_cse_flow1.png)
+![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** 
+**Figure 6.3.2.1-2: Configuration message flow for AE-to-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.
@@ -216,13 +216,13 @@ The detailed configuration messages are shown in Figure 6.3.2.1-2:
 In figure 6.3.2.2-1) a oneM2M AE creates a <subscription> to the <container> that is being used by the IPE. Subsequently the AE gets a <notification> along with data contained in a <contentInstance> every time the IPE creates a <contentInstance> in that <container>. ....
 
 
-![Figure 6.3.2.1-1: Data message flow from AE to CSE to IPE](media/config_cse2.png)
+![Figure 6.3.2.1-1: Data message flow from AE to CSE to IPE](media/config_cse23.png)
 
 **Figure 6.3.2.1-1: Data message flow from AE to CSE to IPE** 
 
 
 
-![Figure 6.3.2.1-2: Configuration message flow for CSE-to-IPE direction](media/config_cse_flow2.png)
+![Figure 6.3.2.1-2: Configuration message flow for CSE-to-IPE direction](media/config_cse_flow23.png)
 
 **Figure 6.3.2.1-2: Configuration message flow for CSE-to-IPE direction**