| Up and running IoT platform | Not applicable | Supported: oneM2M platform can be deployed at cloud or any edge node |
| Registration of vehicles, IoT devices, and applications | Not applicable | Supported: oneM2M features provide CSFs to register both devices and AEs (Application Entities) |
| Data collection from IoT Devices (Vehicle sensors, Road sensors, LIDAR) | Not applicable | Supported via oneM2M’s Common Service Layer using Mca interfaces for data exchange |
| 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
| Up and running IoT platform | Not Required | Supported: oneM2M platform can be deployed at cloud or any edge node |
| Registration of vehicles, IoT devices, and applications | Not Required | Supported: oneM2M features provide Commom Service Functions (CSFs) to register both devices and AEs (Application Entities) |
| Data collection from IoT Devices (Vehicle sensors, Road sensors, LIDAR) | Not Required | Supported via oneM2M’s Common Service Layer using Mca interfaces for data exchange |
| 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 |
| Instantiation of AE 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
### 6.4.3 Vulnerable Road Users
@@ -517,11 +517,11 @@ In the following table, we will consider all the relevant operational requiremen
| Operational Requirement | Support in MEC | Support in oneM2M |
| Up and running IoT platform | Not applicable | Supported: oneM2M platform can be deployed at cloud or any edge node |
| Registration of vehicles, IoT devices, and applications | Not applicable | Supported: oneM2M features provide CSFs to register both devices and AEs (Application Entities) |
| Data collection from IoT Devices (Vehicle sensors, Road sensors, LIDAR) | Not applicable | Supported via oneM2M’s Common Service Layer using Mca interfaces for data exchange |
| 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
| Up and running IoT platform | Not Required | Supported: oneM2M platform can be deployed at cloud or any edge node |
| Registration of vehicles, IoT devices, and applications | Not Required | Supported: oneM2M features provide CSFs to register both devices and AEs (Application Entities) |
| Data collection from IoT Devices (Vehicle sensors, Road sensors, LIDAR) | Not Required | Supported via oneM2M’s Common Service Layer using Mca interfaces for data exchange |
| 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 |
| Instantiation of AE 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
### 6.4.4 Swarm-based Autonomous Ant Delivery Optimization
#### 6.4.4.1 Use Case Driving Deployment
@@ -549,17 +549,17 @@ Service continuity during Hybrid Swarm Robot zone transitions | Supported via ME
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.
##### Table 6.4.x.1-1 – Operational Requirements and Platform Support for Smart Warehouse Automation
##### Table 6.4.5.1-1 – Operational Requirements and Platform Support for Smart Warehouse Automation
| Operational Requirement | Support in MEC | Support in oneM2M |
| Warehouse IoT platform deployment | Not directly required | Supported: oneM2M IN-CSE can be deployed at cloud or control center |
| Registration of sensors, AGVs, and applications | Not required | Supported: oneM2M features provide CSFs to register both devices and AEs (Application Entities) |
| Collection of environmental and telemetry data | Not required | Supported via oneM2M’s Common Service Layer 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 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 |
| Instantiate of AE (e.g., AGV controller, sensor manager) 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 |
| 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 CSF to integrate with the MEC platform |
| Instantiate of AE (e.g., AGV controller, sensor manager) 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 AGVs and asset tracking | 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 applicable | Supported: Tasks can be offloaded to MN-CSE instances using Mcc interface mechanisms. |
| Offloading low latency tasks of IoT Platform for real time data processing | Not Required | Supported: Tasks can be offloaded to MN-CSE instances using Mcc interface mechanisms. |
| 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 |
@@ -569,7 +569,7 @@ The “Industrial Digital Twin” use case requires tight integration between on
MEC hosts edge applications (e.g., quality inspection, anomaly detection) that interact with MN-CSEs. As mobile assets like AGVs move, the MEC, MN-CSE and IN-CSE coordinate handovers and synchronize twin states across MN-CSEs, ensuring seamless operation and minimal downtime.
In the following table, we will consider all the relevant operational requirement for this use case.
##### Table 6.4.x.1-1 – Operational Requirements and Platform Support for Industrial Digital Twins
##### Table 6.4.6.1-1 – Operational Requirements and Platform Support for Industrial Digital Twins
| Operational Requirement | Support in MEC | Support in oneM2M |
| IoT platform deployment | Not directly required | Supported: oneM2M IN-CSE can be deployed at cloud or control center
@@ -621,12 +621,13 @@ In the following table, we will consider all the relevant operational requiremen
Registration of IoT devices deployed in the physical store | Not required | Supported: oneM2M enables registration of industrial sensors, actuators, controllers as either IN-AEs or ADN-AE via standardized resource structures and CSFs
Registration of IoT applications | Not required | Supported: oneM2M enables registration of industrial Applications as AEs via standardized resource structures and CSFs
Real-time data ingestion from Stores (shelf inventory levels, product locations, environmental conditions) | Not required | Supported via oneM2M’s CSF and Mca interfaces
Instantiate of MN-CSE on Edge Node (If required) | 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 MN-CSE on Edge Node with AI capabilities (If required) | 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., sensor manager, analytics & controller) on Edge Node | AE can be instantiated as MEC Application on MEC Host. It can use AI models for analysing real time data and providing feedback. Virtual Store App instantiate as an MEC application/Edge Application on MEC Host. | Supported: oneM2M platform needs to include a CSF to instantiate an AE as MEC application
Low-latency control for real time data processing | Supported: MEC Apps handle time-sensitive operations with minimal delay | Supported: MN-CSE enables fast coordination through subscriptions, notifications, and data routing
### 6.4.9 Future Homes
#### 6.4.9.1 Use case Driven Deployment
##### Table 6.4.9.1-1 – Operational Requirements and Platform Support for Future Homes
# 7 New Internetworking Proposed Recommendations Based on Use Cases
