WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
@@ -509,6 +509,20 @@ In the following table, we will consider all the relevant operational requiremen
### 6.4.3 Vulnerable Road Users
### 6.4.3 Vulnerable Road Users
#### 6.4.3.1 Use Case Driving Deployment
#### 6.4.3.1 Use Case Driving Deployment
he “Vulnerable Road Users” (VRU) use case shares deployment characteristics with the “Autonomous Vehicle with Continuous Edge Computing” scenario, where achieving ultra-low latency, localized processing, and context awareness is critical. This is necessary to effectively process data from nearby roadside units, sensors mounted on traffic signals, and other urban infrastructure to enable real-time analytics and immediate response. To support this, specific processing tasks can be offloaded to oneM2M Edge Instances (MN-CSEs) operating close to the data sources. As vehicles and VRUs dynamically move across different geographic zones, coordination across multiple MEC nodes becomes essential. Therefore, a centralized IN-CSE deployed in the cloud is ideal for maintaining global context, orchestrating and synchronizing edge instances, and ensuring uninterrupted service continuity. Meanwhile, MN-CSEs should be deployed close to the edge to provide low-latency decision support
In the following table, we will consider all the relevant operational requirement for this use case.
##### Table 6.4.3.1-1 – Operational Requirements and Platform Support for Vulnerable Road Users
| 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
### 6.4.4 Swarm-based Autonomous Ant Delivery Optimization
### 6.4.4 Swarm-based Autonomous Ant Delivery Optimization
