@@ -437,8 +437,6 @@ Description of the target MEC Framework ….
### 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.3.1 Introduction to oneM2M
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.
@@ -453,16 +451,16 @@ oneM2M service layer can be integrated into devices, gateways, and servers. Figu
**Figure 6.3.2-1: oneM2M architecture**
This architecture is composed of the following entities:
-*Common Services Entity (CSE)*: Provides the set of "service functions" that are common to multiple IoT domains
-*Application Entity (AE)*: Represents application logic for the end-to-end IoT solutions. This includes device firmware, gateway logic or backend applications
-*Interworking Proxy application Entity (IPE)*: A specialized AE that is used to interface between oneM2M and an external system
-*Network Services Entity*: Provides networking services to CSEs that are more than just data transport
-*Node*: Logical equivalent of a physical (or possibly virtualized) server or device
-*Common Services Entity (CSE)*: Provides the set of "service functions" that are common to multiple IoT domains.
-*Application Entity (AE)*: Represents application logic for the end-to-end IoT solutions. This includes device firmware, gateway logic or backend applications.
-*Interworking Proxy application Entity (IPE)*: A specialized AE that is used to interface between oneM2M and an external system.
-*Network Services Entity*: Provides networking services to CSEs that are more than just data transport.
-*Node*: Logical equivalent of a physical (or possibly virtualized) server or device.
oneM2M defines several different kinds of node, which are named based on their use by oneM2M.
-*Infrastructure Node (IN)*: A Cloud provider / company server. It hosts a CSE that is referred to as an IN-CSE and may host AEs. There is exactly one IN in the Infrastructure Domain of each oneM2M Service Provider
-*Application Service Node (ASN)*: A Node that contains at least one AE co-located with a CSE (an ASN-CSE)
-*Infrastructure Node (IN)*: A Cloud provider / company server. It hosts a CSE that is referred to as an IN-CSE and may host AEs. There is exactly one IN in the Infrastructure Domain of each oneM2M Service Provider.
-*Application Service Node (ASN)*: A Node that contains at least one AE co-located with a CSE (an ASN-CSE).
-*Middle Node (MN)*: A Node that contains one CSE (an MN-CSE) and zero or more AEs. It is typically found in an Edge Server or Gateway box.
-*Application Dedicated Node (ADN)*:A Node that contains at least one AE but does not contain a CSE.
@@ -470,9 +468,9 @@ oneM2M defines several different kinds of node, which are named based on their u
In addition, the oneM2M architecture defines one other type of node, the so-called “Non-oneM2M Node” (NoDN), not shown in Figure 6.3.2-1. 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.
The principal *Reference Points* defined by oneM2M are:
-*Mca*: The interface used by an AE to use the common services provided by the CSE
-*Mca*: The interface used by an AE to use the common services provided by the CSE.
-*Mcc*: Communication flows across the Mcc reference point enable a CSE to use the services supported by another CSE.
-*Mcc'*: Communication flows between CSEs that belong to different oneM2M service providers
-*Mcc'*: Communication flows between CSEs that belong to different oneM2M service providers.
-*Mcn*: Communication flows between a Common Services Entity (CSE) and the Network Services Entity (NSE) allowing the CSE to use the network services (other than transport and connectivity) provided by the NSE.
### 6.3.3 oneM2M Architecture Common Service Layer Functions
