fix issue #3: add figures for each deployment options

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. 

### 6.4.1 Deployment Options   

The selection of the most appropriate deployment option for each use case is guided by insights from the ETSI white paper [Todo: Add reference], where 4 deployment options are mentioned for interworking of oneM2M and MEC technologies. The  figure xx depict the following 4 deployment options:  

The selection of the most appropriate deployment option for each use case is guided by insights from the ETSI white paper [Todo: Add reference], where 4 deployment options are mentioned for interworking of oneM2M and MEC technologies.

Option A: deploy the oneM2M as a cloud, MEC as an edge

#### 6.4.1.1 Option A: deploy the oneM2M as a cloud, MEC as an edge

- This deployment presents the IoT platform itself on the cloud side.

- This is one of the most common deployment scenarios that use cloud based IoT platforms and edge computing.

- 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.

Option B: oneM2M and MEC as an edge with the different physical node

<img src="/media/OptionA.1.png" width="900" height="500">

<img src="/media/OptionA.2.png" width="900" height="500">

The following figures X illustrate deployment option A where oneM2M IN-CSE deployment is on the cloud Node and where the communication between  Iot applications (MN-AE) and multiple oneM2M devices is supported and managed by oneM2M platform. The choice to utilize MN-CSE at fog node is upto the scenario.

#### 6.4.1.2 Option B: oneM2M and MEC as an edge with the different physical node

- This option presents oneM2M and MEC deployed as edge nodes but located on different physical edge nodes.

- Compared to Option A, both oneM2M and MEC exist on the same edge node, allowing for all data and information exchange to be performed locally, resulting in faster processing.

- Although oneM2M IoT service providers and ETSI MEC entities are different, this scenario can still be used in the early edge computing market.

Option C: oneM2M and MEC in the same physical edge node

<img src="/media/OptionB.png" width="900" height="500">

The following figure X illustrate deployment option B where oneM2M IN-CSE deployed on Cloud, MN-CSE is deployed at separate edge node than MEC platform. The MN-CSE acting as an Edge application for registration with MEC platform deployed on differnt edge node, for platforms discovery and communication additional logics and network configurations (DNS settings) should be performed.

#### 6.4.1.3 Option C: oneM2M and MEC in the same physical edge node

- In this scenario, oneM2M and MEC platforms are installed and operated on the same physical edge node, which can significantly improve service by eliminating unnecessary data and information exchange.

- A Service Level Agreement between the platform providers is required, and both platforms support dynamic deployment to various edge nodes.

Option D: oneM2M and MEC are tightly coupled in the same edge node

<img src="/media/OptionC.png" width="900" height="500">

The following figure X illustrate deployment option C where oneM2M IN-CSE deployed on Cloud, MN-CSE and MEC platform are deployed on the same edge node.

#### 6.4.1.4 Option D: oneM2M and MEC are tightly coupled in the same edge node

- This scenario involves oneM2M and MEC platforms being physically coupled through APIs, allowing for mutual interworking.

- The oneM2M platform is recognized as an MEC application, utilizing all functions provided by MEC to provide a 100% edge computing environment.

- The MEC platform can directly provide data source, processing, and multi-access networking by hosting oneM2M as an application.

- A standard document providing interoperability and interworking between the two platforms, oneM2M and ETSI MEC, is required.

<img src="/media/OptionD.1.png" width="900" height="500">

<img src="/media/OptionD.2.png" width="900" height="500">

The following figure X.1 illustrate deployment option D where oneM2M IN-CSE deployed on Cloud and MN-CSE can be added as a MEC service inside the MEC platform, for this case the service has to be MEC complient and can be accessible using mp1 interface via MEC platform. In other case, the regitrtaion of MN-CSE (as MEC application) with MEC platform should be done based on MEC011 application registration process.   

### 6.4.x Autonomous Vehicle with Continuous Edge Computing

Mapping of oneM2M and MEC Framework to the Use Case