## oneM2M/MEC federation - need short description of what is supported now (what API is this)
## oneM2M/MEC federation/orchestration - need short description of what is supported now (what API is this)
For federation, we need to first find MEC/oneM2M instances that are registered and/or discoverable.
We will need to create a federation group, which is a collection of MEC/oneM2M instances that can communicate with each other.
given a federation group, we need to determine which MEC/oneM2M instances will be used for Federated learning, swarm computing, handover. This will depend on the capabilities of the MEC/oneM2M instances, such as their processing power, storage capacity, and network connectivity.
We will need processes for each of handover, federated learning, and swarm computing.
We will need to define handover for devices that are moving between MEC/oneM2M instances. What is the criteria for handover? How do we determine when a device should be handed over to another MEC/oneM2M instance? What process is used to handover a device?
We will need to define how to move registrations between MEC/oneM2M instances.
We will need to define how to move subscriptions between MEC/oneM2M instances.
We will need to define how to move data between MEC/oneM2M instances.
We will need to define how to move data between MEC/oneM2M instances. This includes what data should be moved, how it should be moved, and when it should be moved.
We will need to define how to sync data between MN-CSE and IN-CSE. digital twins can be used to represent the state of the vehicle in the MEC/oneM2M system.
# Clause for Clause 6.4.2
We can use a digital twin of the vehicle to represent the vehicle in the MEC/oneM2M system. The digital twin can be used to store the state of the vehicle, including its location, speed, and other relevant information. The digital twin can also be used to store the history of the vehicle, including its previous locations and speeds. We can determine what data should be maintained in the cloud and what data should be maintained in the MEC/oneM2M system.
# Notes for Clause 6.4.2
We can use a digital twin of the vehicle to represent the physicalvehicle in the MEC/oneM2M system. The digital twin can be used to store the state of the vehicle, including its location, speed, and other relevant information. The digital twin can also be used to store the history of the vehicle, including its previous locations and speeds. We can determine what data should be maintained in the cloud and what data should be maintained in the MEC/oneM2M system.
How do we determine which data has low latency requirements and should be maintained in the MEC/oneM2M system, and which data can be stored in the cloud?
We can use the following criteria to determine which data should be maintained in the MEC/oneM2M system and which data can be stored in the cloud:
