Skip to content
Snippets Groups Projects
Commit bc1bf2b7 authored by Ingo Friese's avatar Ingo Friese
Browse files

typos

parent 81276863
No related branches found
No related tags found
1 merge request!11SDS-2025-0017R02-ogc_ipe_configuration_aspects_supl
Pipeline #1828 canceled with stages
This commit is part of merge request !11. Comments created here will be created in the context of that merge request.
......@@ -214,7 +214,7 @@ The detailed configuration steps are shown in Figure 6.3.2.1-2:
#### 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.
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)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment