@@ -254,15 +254,17 @@ For the purposes of the present document, the [following] abbreviations [given i
# 4 Overview
This clause introduces the document by outlining its purpose, scope, and key objectives. It sets the foundation for the integration of ETSI MEC and oneM2M frameworks, emphasizing their relevance in enabling advanced Edge and IoT-based deployments across diverse application domains. The document is organized into three main clauses, each addressing a specific aspect of the analysis.
This clause introduces the document by clearly defining its purpose, scope, and key objectives. It lays the groundwork for the integration of the ETSI MEC and oneM2M frameworks, highlighting their critical role in enabling advanced Edge and IoT deployments across a wide range of application domains.
Clause 5 presents a domain-oriented analysis of selected use cases, demonstrating how MEC and oneM2M can be effectively applied in practical Edge-IoT scenarios. Use cases are grouped according to relevant domains—such as Mobility, Industrial, and Maritime—to reflect the specific operational context. Within each domain, use cases are described in detail, including the context, involved stakeholders, technical and operational requirements, as well as associated challenges. The role of MEC and oneM2M technologies in addressing these challenges is also examined. These use cases were identified through a structured exploration process involving key stakeholders, who contributed via a dedicated form designed to capture all essential elements of each use case. This approach ensured consistency and completeness by documenting the use case description, actors, requirements, preconditions and postconditions, triggers, and expected interaction flows.
The ESTIMED project takes a use case-driven approach to steer the integration of ETSI MEC and oneM2M. This strategy effectively demonstrates the tangible benefits of merging edge computing capabilities with standardized IoT architectures. By anchoring the analysis in real-world scenarios, the approach not only guides integration efforts but also informs future standardization initiatives to better meet operational demands. The project emphasizes identifying new functional requirements and potential extensions to existing specifications, thereby contributing to the continuous refinement and evolution of both MEC and oneM2M frameworks in response to emerging IoT and edge computing challenges. Following this methodology, the document is organized into three main clauses, each addressing a core aspect of the analysis.
Clause 6 builds on the identified use cases by analyzing the main reference architectures of the MEC and oneM2M frameworks. It highlights their respective core functionalities and explores how they complement each other in supporting Edge-IoT scenarios. The clause also maps architectural elements and capabilities from both frameworks to each use case, identifying existing overlaps and new features that may enhance support for specific scenarios. These mappings serve as the basis for a broader architectural reflection, setting the stage for further technical analysis.
Clause 5 delivers a domain-centric analysis of carefully selected use cases, illustrating the practical application of MEC and oneM2M in Edge-IoT environments. Use cases are categorized by relevant domains—such as Mobility, Industrial, and Maritime—to reflect their specific operational contexts. Within each domain, use cases are thoroughly examined, covering the scenario context, involved stakeholders, technical and operational requirements, and key challenges. The clause also explores how MEC and oneM2M technologies contribute to overcoming these challenges. The use cases were identified through a structured engagement with stakeholders, facilitated by a dedicated form designed to capture all critical details consistently, including descriptions, actors, requirements, preconditions and postconditions, triggers, and interaction flows.
Clause 7 consolidates the insights gained from the architectural mapping by extracting and formalizing new functional and technical recommendations. These recommendations are derived from both common patterns observed across multiple use cases and unique needs emerging from individual scenarios. The resulting output informs the ongoing development of both ETSI MEC and oneM2M, particularly in terms of their interworking and integration. This clause aims to ensure that evolving deployment needs are addressed through well-aligned framework enhancements and targeted standardization efforts.
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.
Overall, the document provides a structured foundation for understanding how MEC and oneM2M can jointly enable scalable, interoperable, and future-oriented Edge-IoT solutions.
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.
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.
