adding notes for clause 7. brain storming the features needed for stf685 for...

# Notes for Clause 7

## oneM2M/MEC federation - 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.

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 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.

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:

1. **Latency Requirements**: Data that requires real-time processing or has low latency requirements should be maintained in the MEC/oneM2M system. This includes data related to vehicle control, safety, and immediate user interactions.

2. **Data Volume**: High-volume data that is generated frequently, such as sensor data, should be processed in the MEC/oneM2M system to reduce the load on the cloud and minimize latency.

3. **Data Sensitivity**: Sensitive data that requires immediate action or has privacy implications should be processed in the MEC/oneM2M system to ensure compliance with privacy regulations and to provide timely responses.

4. **Data Persistence**: Data that does not require immediate processing and can be stored for longer periods can be stored in the cloud. This includes historical data, analytics, and data that can be processed in batches.

5. **Network Conditions**: In scenarios with unreliable or limited network connectivity, data that needs to be accessed quickly and reliably should be maintained in the MEC/oneM2M system, while data that can tolerate delays can be stored in the cloud. 

 No newline at end of file