@@ -590,6 +590,22 @@ Synchronization of Digital Twin state between edge and cloud | Not required | o
### 6.4.7 Assisted Manoeuvring for Autonomous Ships
#### 6.4.7.1 Use case Driven Deployment
The “Assisted Manoeuvring for Autonomous Ships” use case supports autonomous ship operations through coordinated deployment of oneM2M and MEC components. A cloud-hosted IN-CSE collects and processes global vessel data (e.g., location, speed, sensor feeds), while edge-hosted MN-CSEs (ROC) are deployed near ports to assist with real-time decision-making.
When a ship enters port waters, MEC hosts localized MEC/Edge applications (e.g., assisted maneuvering, collision avoidance) that interact with MN-CSEs for low-latency analytics. As the vessel moves, tasks are seamlessly offloaded across MN-CSEs, with the IN-CSE ensuring synchronization and service continuity.
This deployment enables responsive control, enhanced safety, and uninterrupted autonomous operation of unmanned ships near coastal and harbor zones. In the following table, we will consider all the relevant operational requirement for this use case.
##### Table 6.4.7.1-1 – Operational Requirements and Platform Support for Assisted Manoeuvring for Autonomous Ships
| Operational Requirement | Support in MEC | Support in oneM2M |
| IoT platform deployment | Not directly required | Supported: oneM2M IN-CSE can be deployed at cloud
Registration of devices on the Ships | Not required | Supported: oneM2M enables registration of sensors, actuators, controllers as either IN-AEs or MN-AE or ADN-AE via standardized resource structures and CSFs
Registration of applications | Not required | Supported: oneM2M enables registration of Applications as AEs via standardized resource structures and CSFs
Real-time data ingestion from AEs (vessel localization, its speed, course and other environment variables) | Not required | Supported via oneM2M’s CSF and Mca interfaces
Instantiate of MN-CSE on Edge Node plays role ROC with AI capabilities | MEC provides the infrastructure to host oneM2M as a service producing MEC application using Mp1 interface. Can provide support to integrate a new MEC IoT service (MEC 0xx to be defined later) inside the MEC Platform which should be more coupled with oneM2M standards. Whereas MEC IoT API (MEC033) enables minimal registration and discovery of IoT platforms. | Supported: oneM2M platform needs to include a CSF to integrate with the MEC platform
Instantiate of AE (e.g., generate warnings in real-time and optimize its transmission to the vessel) on Edge Node | AE can be instantiated as MEC Application on MEC Host | Supported: oneM2M platform needs to include a CSF to instantiate an AE as MEC application
Low-latency control for unmanned Vessels (i.e. assisted maneuvering, collision avoidance and situational awareness) | Supported: MEC Apps handle time-sensitive operations with minimal delay | Supported: MN-CSE enables fast coordination through subscriptions, notifications, and data routing
Offloading low latency tasks of IoT Platform for real time data processing | Not required. But MEC IoT API (MEC033) enables minimal registration and discovery of IoT platforms. | Supported: Tasks can be offloaded to MN-CSE instances using Mcc interface mechanisms.
Service continuity during vessels 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.8 Smart Metaverse Shopping with Edge-AI and Cloud-IoT Integration
