diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md index f706ce84654056bb03bfc370477df0b541c0cab6..4ca8f064d13a46908e1a4263ad1aa8464a34fadb 100644 --- a/TS-0041-oneM2M-SensorThings_interworking.md +++ b/TS-0041-oneM2M-SensorThings_interworking.md @@ -221,9 +221,9 @@ This reference is needed by the IPE to relate an "Observation" to a "Datastream" The creation of entities like "Datastream" and "Thing" requires a number of mandatory properties that shall be known at configuration time, e.g. 'name' and 'description'. These property fields MAY automatically derived e.g. from the "Label" or "ResourceName" attributes of the regarded oneM2M `<AE>` or `<container>` during IPE configuration. The OGC/STA procedures for creating OGC entities are described in SensorThing API documentation <a href="#_ref_i.1">[i.1]</a>. -When "Thing" and "Datastream" entities are created the IPE is able to send "Observations" to the OGC/STA server as HTTP POST messages. The interested OGC/STA Client can now subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server and thus getting every "Observation" forwarded from the IPE (see Figure 6.3.1.2-1) +When "Thing" and "Datastream" entities are created the IPE is able to send "Observations" to the OGC/STA server as HTTP POST messages. The interested OGC/STA Client can now subscribe to the destination "Datastream" at the MQTT Broker of the OGC/STA server and thus getting every "Observation" forwarded from the IPE (see Figure 6.3.1.2-1) Alternativly the OGC/STA client MAY use a HTTP-GET requst to get the data when needed. - + **Figure 6.3.1.2-1: Message flow from OGC STA Client to OGC/STA Server to IPE** diff --git a/media/config_ogc2.png b/media/config_ogc2.png new file mode 100644 index 0000000000000000000000000000000000000000..495b7136a792070cdad84b54c6399fa45da34f20 Binary files /dev/null and b/media/config_ogc2.png differ