Commit d672aae5 authored by Marco Picone's avatar Marco Picone
Browse files

Figure captions fixed

parent f672a606

GR_MEC-DEC_050.md

+2 −1
Original line number Diff line number Diff line
@@ -531,7 +531,7 @@ This option focuses on integrating the services of oneM2M and ETSI MEC. This ach 
- The MEC IPE is replaced with new APIs that take advantage of new standards work from ETSI MEC and oneM2M. 



![6.4.1.3-1. Deployment Option C.](/media/OptionC.png)

**6.4.1.3-1. Deployment Option C.

**6.4.1.3-1. Deployment Option C.**



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.
@@ -544,6 +544,7 @@ This option attempts to simplify the services by offered by ETSI MEC and oneM2M 
- MEC exposes APIs that integrate the oneM2M services. 



![6.4.1.4-1. Deployment Option D.](/media/OptionD.png)



**6.4.1.4-1. Deployment Option D.**



In this scenario oneM2M integrates to MEC and offers services that support directly supporting providing data source, processing, and multi-access networking.