@@ -627,7 +627,21 @@ Low-latency control for real time data processing | Supported: MEC Apps handle t
### 6.4.9 Future Homes
#### 6.4.9.1 Use case Driven Deployment
The “Future Homes” use case delivers immersive and personalized smart home services through ETSI MEC and oneM2M integration. A centralized CSE (IN-CSE or MN-CSE) runs on a Cloud or MEC node to manage devices across homes, while local CSEs (MN-CSE/ASN-CSE) are deployed on non-MEC nodes such as home gateways or CPEs.
Latency-critical tasks like video analytics and sensor fusion are offloaded to Customer Premises Edge devices hosting MEC apps or CSEs, with MEC platforms leveraging the MEP interface for discovery and task delegation.
In the following table, we will consider all the relevant operational requirement for this use case.
##### Table 6.4.9.1-1 – Operational Requirements and Platform Support for Future Homes
| Operational Requirement | Support in MEC | Support in oneM2M |
| IoT platform deployment | Not directly | Supported: oneM2M IN-CSE can be deployed at cloud or as MN-CSE elsewhere
Registration of devices at the home premises (lights, thermostats, cameras, wearables) |Not required | Supported: oneM2M enables registration of sensors, actuators, controllers as either IN-AEs or MN-AE or ADN-AE via standardized resource structures and CSFs
Registration of applications | Not required | Supported: oneM2M enables registration of Applications as AEs via standardized resource structures and CSFs
Real-time data ingestion from AEs (location data, Health alerts or anomalies, room temperature, energy consumption, object movements) | Not required | Supported via oneM2M’s CSF and Mca interfaces
Instantiate of MN-CSE/ASN-CSE on Edge Node (Customer Premises Edge) | 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. Not Supported in MEC: If MEC supports CPEs, then MEC systems can discover them, and MEP enables MEC applications to offload real time data processing tasks to this non-MEC systems | Supported: oneM2M platform needs to include a CSF to integrate with the MEC platform
Instantiate of AE (e.g., Energy Optimization, Real-time Safety Alerts, Contextual Scene Adaptation, Manage home appliances) on Edge Node | AE can be instantiated as MEC Application on MEC Host or as Edge application on CPEs | Supported: oneM2M platform needs to include a CSF to instantiate an AE as MEC application
Offloading low latency tasks of IoT Platform for real time data processing | Not required. But MEC IoT API (MEC033) enables minimal registration and discovery of IoT platforms | Supported: Tasks can be offloaded to MN-CSE instances using Mcc interface mechanisms.
Service continuity during devices movements. | Supported via MEC013 Location API (tracks UE movement), MEC021 (Application Mobility service) and MEC040 (supports MEC Federation and cross-MEP orchestration) | Supported: oneM2M handles session handover and task migration to a new edge (MN-CSE/ASN-CSE) instance coordinated by IN-CSE/MN-CSE
# 7 New Internetworking Proposed Recommendations Based on Use Cases
