Commit 335ecd3f authored by PeterNiblett's avatar PeterNiblett
Browse files

Proposed change to clause 4 to fix to issue 15

parent f8b7111e
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -235,7 +235,7 @@ Clause 5 delivers a domain-centric analysis of carefully selected use cases, ill

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.