From 4ae1d73b21f022158058ca3a154b763939bde9a7 Mon Sep 17 00:00:00 2001 From: Ingo Friese <ingo.friese@telekom.de> Date: Thu, 23 May 2024 14:03:52 +0000 Subject: [PATCH] introduction --- TS-0041-oneM2M-SensorThings_interworking.md | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md index 30540e8..61e83b5 100644 --- a/TS-0041-oneM2M-SensorThings_interworking.md +++ b/TS-0041-oneM2M-SensorThings_interworking.md @@ -174,8 +174,19 @@ The Sensing Entities data model and the purpose of data within the data model di - Data embedded in the Sensing Entities Data Model, like "historic locations" should be seen as data for documentation purposes. -## 5.1 User defined subdivisions of clause(s) from here onwards -<Text> +# 6 Architecture Model of OGC/STA to oneM2M interworking + +## 6.0 Introduction + +Figure 6.0-1 shows an architecture approach for an Interworking Proxy Entity (IPE) between oneM2M and the OGC SensorThings API. The IPE is located between a oneM2M CSE and an OGC/SensorThings API (STA)-Server. + +The basic interworking enables applications that are connected to an oneM2M-based system to get data from sensors that are connected to an OGC/STA server. Furthermore, an application that is connected to an OGC/STA server will be able to get data from sensors that are connected to an oneM2M-based system. + + +<figure> + <img src="media/figure6_0__1.png" alt="arch_overview"> + <figcaption>Figure 6.0-1: IPE architecture overview with data flow</figcaption> +</figure> <mark>The following text is to be used when appropriate:</mark> -- GitLab