@@ -435,23 +435,39 @@ Description of the target MEC Framework ….
Description of the target MEC Framework ….
### 6.2 oneM2M Components
### 6.3 oneM2M Components
This section provides an overview of the MEC framework, detailing its components, services, and how it supports Edge-based applications.
### 6.2.1 oneM2M Framework XXXX-1
### 6.3.1 Introduction to onM2M
Description of the target oneM2M Framework ….
oneM2M is a global standards initiative that develops specifications for a horizontal platform (or Service Layer) used for the exchange and sharing of data among Internet of Things applications. Individual IoT solutions using oneM2M can share data and resources through common service layer functions such as resource discovery and semantic interoperability. As a result, application developers, solution providers and data suppliers can share data between applications that span multiple verticals and reduce their dependence on single-vendor solutions.
oneM2M provides a layer of abstraction - similar to an operating system - that shields developers from the details of network communication protocols, interfaces to IoT device and device management. It provides a framework for interworking with different technologies, for example 3GPP and Modbus.
It is also designed as a distributed software layer, making it particularly suitable for use in Edge computing deployments, mitigating the burdens on data centers and core networks and improving communication latency by acquiring, processing, and storing data at the edge of network.
### 6.2.2 oneM2M Framework XXXX-2
### 6.3.2 oneM2M Architecture
Description of the target oneM2M Framework ….
The oneM2M service layer is a general-purpose standard that applies to all industry verticals. It brings together all components in the IoT solution stack and specifies a distributed software/middleware layer, sitting between applications and underlying communication networking HW/SW.
oneM2M service layer can be integrated into devices, gateways, and servers. This figure shows a simplified oneM2M simplified architecture:
This architecture is composed of the following entities:
-*Reference Point*: One or more interfaces - Mca, Mcn, Mcc and Mcc’ (between 2 service providers)
-*Common Services Entity (CSE)*: Provides the set of "service functions" that are common to the IoT domains
-*Application Entity (AE)*: Provides application logic for the end-to-end IoT solutions
-*Network Services Entity*: Provides services to the CSEs beyond the data transport
-*Node*: Logical equivalent of a physical (or possibly virtualized) server or device
Description of the target oneM2M Framework ….
In particular, oneM2M defines several different kinds of nodes, which are named based on the specific instantiation option considered:
-*Application Service Node* (ASN) at the Edge device / Gateway (GW)
-*Middle Node (MN)* An Edge Node / Gateway (GW)
-*Infrastructure Node (IN)* A Cloud provider / company server
-*Infrastructure Node (IN)* A ervers belonging to other companies or cloud providers
## 6.3 Use Cases & Frameworks Mapping
In addition, the oneM2M architecture supports another type of node, the so-called “Non-oneM2M Node” (NoDN), not shown in the figure above. This is a node that does not contain native oneM2M Entities (neither AEs nor CSEs). Typically, such nodes would host some non-oneM2M IoT implementations or legacy technology which can be connected to the oneM2M system via interworking proxies or agents.
## 6.4 Use Cases & Frameworks Mapping
This section provides a synthesis of the previously identified use cases and the architectural features of the MEC and oneM2M frameworks. It maps each use case to the relevant framework components and functionalities, showcasing how MEC and oneM2M support specific operational needs. The mapping highlights the alignment between the frameworks and the identified scenarios, while also pointing out areas where enhancements or additional integration mechanisms may be required to better support cross-domain use cases. Additionally, the selection of the most appropriate deployment option for each use case is guided by insights from the ETSI white paper: [Todo: Add reference]
