add headings for each usecases

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

#### 6.4.x.1 Use Case Driving Deployment

### 6.4.2 Autonomous Vehicle with Continuous Edge Computing

#### 6.4.2.1 Use Case Driving Deployment

For the “Autonomous Vehicle with Continuous Edge Computing” use case, achieving ultra-low latency, context awareness, and localized processing is essential to handle data from nearby sources and enable real-time analytics. To meet these requirements, certain tasks can be offloaded to oneM2M Edge Instances (MN-CSEs).

As autonomous vehicles move across MEC zones, orchestration and synchronization across multiple oneM2M platforms is required. For this, a centralized IN-CSE deployed in the cloud is suitable to maintain global context, coordinate edge instances, and ensure seamless service continuity. 

| Instantiate of MN-CSE on Edge Node                               | MEC provides the infrastructure to host oneM2M as a service producing MEC application (using Mp1 interface or as a new MEC service inside the MEC Platform. MEC IoT API (MEC033) enables registration and discovery of IoT platforms. | Supported: oneM2M platform needs to include a Common Services Function (CSF) to integrate with the MEC platform                                |

| Instantiation of AE on Edge Node                                 | AE can be instantiated as MEC Application on MEC Host                                                                                                                                                  | Supported: oneM2M platform needs to include a Common Services Function (CSF) to instantiate an AE as MEC application

###  6.4.x	Smart Warehouse Automation

Mapping of oneM2M and MEC Framework to the Use Case.

### 6.4.3 Vulnerable Road Users

#### 6.4.3.1 Use Case Driving Deployment

#### 6.4.x.1		Use case Driven Deployment

### 6.4.4 Swarm-based Autonomous Ant Delivery Optimization

#### 6.4.4.1 Use Case Driving Deployment

###  6.4.5	Smart Warehouse Automation

#### 6.4.5.1		Use case Driven Deployment

The architecture integrates a centralized oneM2M IN-CSE, responsible for managing infrastructure-level data (sensors, tags, operational policies), and multiple MN-CSEs deployed at the MEC edge, enabling real-time, latency-sensitive decision-making close to the action. For time-critical events such as rerouting AGVs, responding to hazards, or optimizing resource allocation, processing tasks are offloaded to MEC-hosted MN-CSEs. These instances provide ultra-low-latency data processing

In the following table, we will consider all the relevant operational requirement for this use case.

| Service continuity during AGV zone transitions          | Supported via MEC013 Location API (tracks UE movement) and MEC040 (supports MEC Federation and cross-MEP orchestration)                                                                                | Supported: oneM2M handles session handover and task migration to a new edge (MN-CSE) instance coordinated by IN-CSE                            |

###  6.4.6	Industrial Digital Twins

#### 6.4.6.1		Use case Driven Deployment

###  6.4.7	Assisted Manoeuvring for Autonomous Ships

#### 6.4.7.1		Use case Driven Deployment

###  6.4.8	Smart Shopping with Edge-AI and Cloud-IoT Integration

#### 6.4.8.1		Use case Driven Deployment

###  6.4.9	Future Homes

#### 6.4.9.1		Use case Driven Deployment

# 7	New Internetworking Proposed Recommendations Based on Use Cases

This clause identifies the  recommendations of applications based on the identified use cases and the associated application scenarios described and identified in previous clauses. It builds upon the architectural mappings presented in Clause 6 to extract and consolidate core functional and technical recommendations that are common across multiple use cases. In addition, it identifies unique new  recommendations that arise from individual use cases. These findings provide valuable input for both ETSI MEC and oneM2M, supporting the evolution of their respective frameworks as well as their interworking and integration. The goal of this section is to ensure that emerging needs are captured systematically and considered in future development and standardization efforts.