@@ -525,6 +525,23 @@ In the following table, we will consider all the relevant operational requiremen
### 6.4.4 Swarm-based Autonomous Ant Delivery Optimization
#### 6.4.4.1 Use Case Driving Deployment
The “Swarm-based Autonomous Ant Delivery Optimization” use case enables optimized coordination of autonomous delivery robots using distributed intelligence and real-time data exchange. The oneM2M IN-CSE is deployed in the cloud to manage global swarm state, while MN-CSEs are instantiated at the edge to handle local swarm behavior.
Swarm applications (e.g., route optimization, obstacle detection) are deployed on edge nodes and interact with MN-CSEs for low-latency data processing. Robots continuously report environmental data, pheromone map updates, and coordination feedback to the platform.
As robots move across delivery zones, the system ensures seamless session handover and synchronization of swarm intelligence using MN-CSE coordination. This setup supports dynamic optimization, real-time feedback, and resilient autonomous operations.
##### Table 6.4.4.1-1 – Operational Requirements and Platform Support for Swarm-based Autonomous Ant Delivery Optimization
| Operational Requirement | Support in MEC | Support in oneM2M |
| Up and running IoT platform | Not directly required | Supported: oneM2M IN-CSE can be deployed at cloud
Registration of devices (Swarm Robots) | Not required | Supported: oneM2M enables registration of sensors, actuators, controllers as either IN-AEs 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 (pheromone map updates, route feedback and obstacle reports) | Not required | Supported via oneM2M’s CSF and Mca interfaces
Instantiate of MN-CSE on Edge Node | 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., Swarm optimization) 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 Hybrid Swarm Robots (feedback for Swarm optimization) | 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 Hybrid Swarm Robot 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
