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

introduction

parent f5370a49
No related branches found
No related tags found
2 merge requests!7Sds 2024 0117 ogc to one m2 m data model mapping,!6SDS-2024-0064R02-architecture_model
This commit is part of merge request !7. Comments created here will be created in the context of that merge request.
......@@ -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>
......
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