@@ -766,19 +766,19 @@ Depending on system design and device capability, handover control can follow on
In practice, the chosen strategy should balance device capability, network intelligence, and the requirements of the application domain. For resource-constrained IoT devices, offloading decision-making to the MEC/oneM2M layer may reduce device complexity and power usage, while device-controlled handovers may provide faster reaction times and greater autonomy in heterogeneous deployments.
Some of the requirements that be considered for an effective handover mechanism include:
Some of the requirements that be considered for an effective handover mechanism include (__required__):
-**Device Identity:** The device must maintain a consistent identity across different MEC/oneM2M instances to ensure that its context and state can be accurately transferred during a handover.
-**Device Identity(_required__):** The device must maintain a consistent identity across different MEC/oneM2M instances to ensure that its context and state can be accurately transferred during a handover.
-**Session Continuity:** The handover process must ensure that ongoing sessions are not interrupted, and that any in-progress data transfers are completed successfully.
-**Data Consistency:** The handover mechanism must guarantee that the device's data remains consistent and up-to-date across all MEC/oneM2M instances involved in the process.
-**Data Consistency(_required__):** The handover mechanism must guarantee that the device's data remains consistent and up-to-date across all MEC/oneM2M instances involved in the process.
-**Data Latency:** The handover process must minimize data latency to ensure that real-time applications can continue to function without interruption. This may include methods to pre-fetch data, maintain persistent connections, or identifying fast versus slow changing data.
-**Network Conditions:** The handover mechanism must take into account the current network conditions, such as bandwidth availability and signal strength, to determine the best MEC/oneM2M instance for the device to connect to.
-**Gateway-local Registrations:** Device can (re)register with any gateway to ensure that its context and state are preserved during a handover.
-**Gateway-local Registrations(_required__):** Device can (re)register with any gateway to ensure that its context and state are preserved during a handover.
-**Fast Re-authentication:** The handover process must support fast re-authentication mechanisms to minimize downtime and ensure a smooth transition between MEC/oneM2M instances, e.g. token-based handover that consists of short-lived tokens that are refreshed via the IN-CSE.
@@ -824,6 +824,8 @@ Some of the requirements that be considered for an effective handover mechanism
-**Feature Flags:** Device announces supported HO features; gateways negotiate the HO method.
These proposed requirements for an effective handover will be analyzed in oneM2M TR-0080.
## 7.3 Swarm Computing
**Swarm Computing** refers to the coordination of multiple MEC/oneM2M instances to perform distributed computing tasks, leveraging the capabilities of edge devices and networks. In this paradigm, individual MEC/oneM2M nodes act like members of a swarm, each contributing processing power, storage, connectivity, or sensing capabilities to achieve collective goal. The system operates in a decentralized and adaptive manner, where tasks can be dynamically partitioned, distributed, and recombined across nodes depending on resource availability, network conditions, and application requirements. This enables resilient, scalable, and low-latency processing, as task are executed closer to the data sources and devices while ensuring cooperative load balancing, fault tolerance, and energy efficiency.
