@@ -582,12 +582,13 @@ This option captures the MEC and oneM2M standard as they exist at the start of t
- devices may use non-MEC services, e.g. UPC-UA devices, using a 3rd party IPE hosted as an MEC APP.
- devices may use oneM2M services through a Mca proxy. This Mca proxy can be hosted as an MEC APP. These oneM2M devices can also take advantage of exposed MEC services.
(this needs editing) Although some of the benefits of edge computing can be achieved through network and processing, the advantages of 100% edge computing are not fully utilized because the cloud remains the final endpoint where data is stored and managed.
Although some of the benefits of edge computing can be achieved through network and processing, the advantages of 100% edge computing are not fully utilized because the cloud remains the final endpoint where data is stored and managed.
- A standard document providing interoperability and interworking between the two platforms, oneM2M and ETSI MEC, is required.
#### 6.4.1.2 Option B: oneM2M and MEC as an edge with the different physical node
This option enhances the performance of the edge deployment by introducing additional services through the integration of a oneM2M MN-CSE. An oneM2M IPE is added that interworks MEC services and devices. This can be realized using an exemplar setup consisting of one platform with an MEC framework and a second platform hosting the MN-CSE.
- An oneM2M IN-CSE is deployed in the cloud and an IN-AE represents the application that is connected to the IN-CSE.
@@ -597,8 +598,7 @@ This option enhances the performance of the edge deployment by introducing addit
- Additional services can be exposed by oneM2M AEs as such interworking with other devices, swarm computing and federated learning.
- These additional oneM2M AEs can be deployed on either the oneM2M platform or the MEC platform.
This deployment uses oneM2M IoT service providers and ETSI MEC entities that may be different, this scenario can still be used in the early edge computing market by using the same custom MEC IPE that was defined in option A. Additionally, new capabilities from oneM2M can be delpoyed to support compute intensive services.
- A standard document providing interoperability and interworking between the two platforms, oneM2M and ETSI MEC, is required.
@@ -610,8 +610,7 @@ This option focuses on integrating the services of oneM2M and ETSI MEC. This ach
- The edge consists of the MEC platform that connects devices using MEC apis and the oneM2M MN-CSE to support a variety to devices.
- The MEC IPE is replaced with new APIs that take advantage of new standards work from ETSI MEC and oneM2M.
In this scenario, oneM2M and MEC platforms are installed and operated on the same physical edge node. This can significantly improve services by eliminating unnecessary data movement and information exchange. It also supports customizing the system to take advantage of high compute platform capabilities that may be needed for federated learning or swarm computing.
- A standard document providing interoperability and interworking between the two platforms, oneM2M and ETSI MEC, is required.
@@ -623,7 +622,7 @@ This option attempts to simplify the services by offered by ETSI MEC and oneM2M
- The edge consists of the MEC platform that connects devices using MEC apis and the oneM2M MN-CSE to support a variety to devices.
- MEC exposes APIs that integrate the oneM2M services.
In this scenario oneM2M integrates to MEC and offers services that support directly supporting providing data source, processing, and multi-access networking.
- A standard document providing interoperability and interworking between the two platforms, oneM2M and ETSI MEC, is required.
