update description of existing deployment figures

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

<img src="/media/OptionA.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. For specific Iot data processing, MEC services can be utilized using an IPE hosted on Edge. 

![Figure 6.4.1.1-1: Deployment Option A](/media/OptionA.png)

**Figure 6.4.1.1-1: Deployment Option A**

The figures 6.4.1.1-1 illustrates deployment option A where the oneM2M IN-CSE deployment is on a cloud Node and where the communication between non-oneM2M devices and the IN-CSE is provided by an IPE running as a MEC application.

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

- Compared to Option A, both oneM2M and MEC exist on edge nodes, allowing for data and information exchange to be performed locally, possibly 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.

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

![Figure 6.4.1.2-1: Deployment Option B](/media/OptionB.png)

**Figure 6.4.1.2-1: Deployment Option B**

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 MEC platform discovery and communication additional logics and network configurations (DNS settings) should be performed at MN-CSE.

The figure 6.4.1.2-1  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 MEC platform discovery and communication additional logics and network configurations (DNS settings) should be performed at MN-CSE.

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

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

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

**Figure 6.4.1.3-1: Deployment Option C**

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.

The figure 6.4.1.3-1 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 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.png" width="900" height="500">

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

**Figure 6.4.1.4-1: Deployment Option D**

The following figure X.1 illustrate deployment option D where oneM2M IN-CSE deployed on Cloud, MN-CSE and MEC platform are deployed on the same edge node. In this case, the regitrtaion of MN-CSE (as MEC application) with MEC platform should be done based on MEC011 application registration process.   

The figure 6.4.1.4-1 illustrate deployment option D where oneM2M IN-CSE deployed on Cloud, MN-CSE and MEC platform are deployed on the same edge node. In this case, the regitrtaion of MN-CSE (as MEC application) with MEC platform should be done based on MEC011 application registration process.   

### 6.4.2 Autonomous Vehicle with Continuous Edge Computing

#### 6.4.2.1 Use Case Driving Deployment