Merge branch 'ESTIMED-D2.2-Peter-Niblett-issues' into 'ESTIMED-D2.2-StableDraft-4.0.3'

Building on this foundation, Clause 6 analyzes the principal architectures of MEC and oneM2M frameworks, emphasizing their core functionalities and complementarity in supporting Edge-IoT deployments. For each use case, the clause maps relevant architectural components and capabilities from both frameworks, highlighting overlaps as well as identifying new features that could enhance support for specific scenarios. This mapping lays the groundwork for a comprehensive architectural reflection and technical assessment.

Clause 7 synthesizes the findings from the architectural mappings into actionable functional and technical recommendations. These are derived from both commonalities shared across multiple use cases and unique requirements specific to individual scenarios. The recommendations aim to guide the ongoing development and integration of ETSI MEC and oneM2M, ensuring that their interworking effectively addresses evolving deployment needs through aligned framework enhancements and targeted standardization efforts.

Clause 7 includes recommendations that enable a framework for the federation and orchestration of MEC and oneM2M instances. It also discusses how these capabilities can be used in Swarm Computing and Federated Learning applications.

Overall, this document establishes a structured and cohesive foundation to understand and advance how MEC and oneM2M can jointly enable scalable, interoperable, and forward-looking Edge-IoT solutions.

## 7.1 Introduction

The main focus of integration between **ETSI MEC** and **oneM2M** is to enable efficient data processing, low-latency communication, and enhanced service delivery in edge computing environments. The major capability of this integration includes **federation of the ETSI MEC platforms** and **interaction with oneM2M instances**, allowing for distributed computing and data management across multiple edge nodes. Both ETSI MEC and oneM2M provide some basic APIs and protocols in order to facilitate such a federation. However, orchestration mechanisms are still required to ensure seamless operation across multiple MEC/oneM2M instances. This clause describes a preliminary set of functional and technical recommendations for enabling a framework for the federation and orchestration of MEC/oneM2M instances. These recommended processes, which not only complement many use cases in clause 4 but also unlock additional value by introducing capabilities that extend and enhance their intended scope, including:

The main focus of integration between **ETSI MEC** and **oneM2M** is to enable efficient data processing, low-latency communication, and enhanced service delivery in edge computing environments. The major capability of this integration includes **federation of the ETSI MEC platforms** and **interaction with oneM2M instances**, allowing for distributed computing and data management across multiple edge nodes. Both ETSI MEC and oneM2M provide some basic APIs and protocols in order to facilitate such a federation. However, orchestration mechanisms are still required to ensure seamless operation across multiple MEC/oneM2M instances. This clause describes a preliminary set of functional and technical recommendations for enabling a framework for the federation and orchestration of MEC/oneM2M instances. These recommended processes, which not only complement many use cases in clause 5 but also unlock additional value by introducing capabilities that extend and enhance their intended scope, including:

- **Handover**: refers to the process of transferring control of a device or service from MEC/oneM2M instance to another, ensuring seamless connectivity and service continuity.