Merge branch 'ESTIMED-D2.2-StableDraft-Section-4-Picone' into 'ESTIMED-D2.2-StableDraft'

# Contents

- [Contents](#contents)

- [Intellectual Property Rights](#intellectual-property-rights)

- [Foreword](#foreword)

- [Modal verbs terminology](#modal-verbs-terminology)

  - [3.2 Symbols](#32-symbols)

  - [3.3 Abbreviations](#33-abbreviations)

- [4 Overview](#4-overview)

- [5 Edge & IoT Domains and Use Cases](#5-edge--iot-domains-and-use-cases)

  - [5.1 Introduction](#51-introduction)

  - [5.2 Smart City & Mobility](#52-smart-city--mobility)

    - [5.2.1 Autonomous Vehicle with Continuous Edge Computing](#521-autonomous-vehicle-with-continuous-edge-computing)

    - [5.2.2 Vulnerable Road Users](#522-vulnerable-road-users)

  - [5.3 Industrial & Robotics](#53-industrial--robotics)

    - [5.3.1 Swarm-based Autonomous Ant Delivery Optimization](#531-swarm-based-autonomous-ant-delivery-optimization)

    - [5.3.2 Smart Warehouse Automation](#532-smart-warehouse-automation)

    - [5.3.3 Industrial Digital Twins](#533-industrial-digital-twins)

  - [5.4 Maritime](#54-maritime)

    - [5.4.1 Assistend Manoeuvring for Autonomous Ship](#541-assisted-manoeuvring-for-autonomous-ship)

  - [5.5 Metaverse](#55-metaverse)

    - [5.5.1 Smart Shopping with Edge-AI and Cloud IoT Integration](#551-smart-shopping-with-edge-ai-and-cloud-iot-integration)

  - [5.6 Future Home](#56-future-home)

    - [5.6.1 User Premises Edge and oneM2M Integration](#561-user-premises-edge-and-onem2m-integration)

- [6 MEC-oneM2M Architectural & Use Case Mapping](#6-mec-onem2m-architectural--use-case-mapping)

  - [6.0 Introduction](#60-introduction)

  - [6.1 MEC Frameworks](#61-mec-frameworks)

    - [6.1.1 ETSI MEC Framework](#611-etsi-mec-framework)

    - [6.1.2 MEC Framework XXXX-2](#612-mec-framework-xxxx-2)

    - [6.1.3 MEC Framework XXXX-3](#613-mec-framework-xxxx-3)

  - [6.2 oneM2M Components](#62-onem2m-components)

    - [6.2.1 oneM2M Framework XXXX-1](#621-onem2m-framework-xxxx-1)

    - [6.2.2 oneM2M Framework XXXX-2](#622-onem2m-framework-xxxx-2)

    - [6.2.3 oneM2M Framework XXXX-3](#623-onem2m-framework-xxxx-3)

  - [6.3 Use Cases & Frameworks Mapping](#63-use-cases--frameworks-mapping)

    - [6.3.1 Use Case 1](#631-use-case-1)

    - [6.3.2 Use Case 2](#632-use-case-2)

    - [6.3.1 Use Case XXX](#631-use-case-xxx)

- [7 New Internetworking Proposed Requirements Based on Use Cases](#7-new-internetworking-proposed-requirements-based-on-use-cases)

  - [7.1 XXX](#71-xxx)

- [5 Edge \& IoT Domains and Use Cases](#5-edge--iot-domains-and-use-cases)

  - [5.1	Introduction](#51introduction)

  - [5.2	Smart City \& Mobility](#52smart-city--mobility)

    - [5.2.1	Autonomous Vehicle with Continuous Edge Computing](#521autonomous-vehicle-with-continuous-edge-computing)

    - [5.2.2	Vulnerable Road Users](#522vulnerable-road-users)

  - [5.3	Industrial \& Robotics](#53industrial--robotics)

    - [5.3.1	Swarm-based Autonomous Ant Delivery Optimization](#531swarm-based-autonomous-ant-delivery-optimization)

    - [5.3.2	Smart Warehouse Automation](#532smart-warehouse-automation)

    - [5.3.3	Industrial Digital Twins](#533industrial-digital-twins)

  - [5.4	Maritime](#54maritime)

    - [5.4.1 Assisted Manoeuvring for Autonomous Ship](#541-assisted-manoeuvring-for-autonomous-ship)

  - [5.5	Metaverse](#55metaverse)

    - [5.5.1	Smart Shopping with Edge-AI and Cloud IoT Integration](#551smart-shopping-with-edge-ai-and-cloud-iot-integration)

  - [5.6	Future Home](#56future-home)

    - [5.6.1	User Premises Edge and oneM2M Integration](#561user-premises-edge-and-onem2m-integration)

- [6	MEC-oneM2M Architectural \& Use Case Mapping](#6mec-onem2m-architectural--use-case-mapping)

  - [6.0	Introduction](#60introduction)

  - [6.1	MEC Frameworks](#61mec-frameworks)

    - [6.1.1	ETSI MEC Framework](#611etsi-mec-framework)

    - [6.1.2	MEC Framework XXXX-2](#612mec-framework-xxxx-2)

    - [6.1.3	MEC Framework XXXX-3](#613mec-framework-xxxx-3)

    - [6.2	oneM2M Components](#62onem2m-components)

    - [6.2.1	oneM2M Framework XXXX-1](#621onem2m-framework-xxxx-1)

    - [6.2.2	oneM2M Framework XXXX-2](#622onem2m-framework-xxxx-2)

    - [6.2.3	oneM2M Framework XXXX-3](#623onem2m-framework-xxxx-3)

  - [6.3	Use Cases \& Frameworks Mapping](#63use-cases--frameworks-mapping)

    - [6.3.x](#63x)

      - [6.3.x.1 Use Case Driving Deployment](#63x1-use-case-driving-deployment)

        - [Table 6.3.x.1-1 – Operational Requirements and Platform Support for Autonomous Vehicle with Continuous Edge Computing](#table-63x1-1--operational-requirements-and-platform-support-for-autonomous-vehicle-with-continuous-edge-computing)

    - [6.3.x	Smart Warehouse Automation](#63xsmart-warehouse-automation)

      - [6.3.x.1		Use case Driven Deployment](#63x1use-case-driven-deployment)

        - [Table 6.3.x.1-1 – Operational Requirements and Platform Support for Smart Warehouse Automation](#table-63x1-1--operational-requirements-and-platform-support-for-smart-warehouse-automation)

- [7	New Internetworking Proposed Recommendations Based on Use Cases](#7new-internetworking-proposed-recommendations-based-on-use-cases)

  - [7.1	XXX](#71xxx)

- [Annex A: Title of annex](#annex-a-title-of-annex)

- [Annex B: Title of annex](#annex-b-title-of-annex)

  - [B.1 First clause of the annex](#b1-first-clause-of-the-annex)

- [Annex: Bibliography](#annex-bibliography)

- [Annex : Change history](#annex--change-history)

- [History](#history)

- [Document history](#document-history)

<br />

# 4 Overview

This clause introduces the document, outlining its purpose, scope, and key objectives. It establishes the context of integrating MEC and oneM2M frameworks, highlighting the relevance of Edge and IoT-based technologies in various deployment scenarios. Additionally, it summarizes the key areas explored in the subsequent sections.

The project is focused on three main goals:

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.

- The ability to deploy the MEC + oneM2M service layers using one or more of the four deployment architectures describes in [the whitepaper]

- Ability to make use of federated learning for training a machine learning model and deploying a trained model.

- Ability to apply machine learning model(s) to a swarm of resources.

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 5 will begin with a representation of use cases ...

Clause 6 will describe the architectures that can support the uses cases defined.

Clause 7 will define the requirements to support the architectures and use cases.

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.

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.

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.

# 5 Edge & IoT Domains and Use Cases

![Figure 5.3.2-1: High-level overview of the warehouse automation scenario.](/media/usecase_smart_warehouse.png)

### 5.3.3	Industrial Digital Twins

T

his use case illustrates the integration of the oneM2M IoT platform with the ETSI MEC edge computing framework to support Industrial Digital Twins (IDTs) in smart manufacturing environments. The goal is to enable continuous monitoring, analysis, and optimization of industrial processes by deploying synchronized digital representations of physical assets across both cloud and edge infrastructures. This approach is fundamental to enabling real-time decision-making, predictive maintenance, and autonomous control in dynamic and distributed industrial settings. 

This use case illustrates the integration of the oneM2M IoT platform with the ETSI MEC edge computing framework to support Industrial Digital Twins (IDTs) in smart manufacturing environments. The goal is to enable continuous monitoring, analysis, and optimization of industrial processes by deploying synchronized digital representations of physical assets across both cloud and edge infrastructures. This approach is fundamental to enabling real-time decision-making, predictive maintenance, and autonomous control in dynamic and distributed industrial settings. 

The overall system architecture relies on a cloud-based oneM2M IN-CSE (Infrastructure Node Common Service Entity), which functions as a centralized orchestrator and digital repository, and multiple MN-CSEs (Middle Node Common Service Entities) deployed at the edge on MEC nodes physically co-located with manufacturing equipment or microfactories. These edge-based MN-CSEs are responsible for processing time-sensitive data streams such as sensor readings from production lines, robotic cell statuses, energy usage metrics, and environmental conditions with ultra-low latency. 

# 6	MEC-oneM2M Architectural & Use Case Mapping

## 6.0	Introduction 

This clause provides an analysis of the main reference architectures and characteristics of  MEC and oneM2M , highlighting their core functionalities and how they complement each other in the context of Edge-IoT deployments. For each of the identified use cases, the clause maps the relevant architectural elements and functionalities from both, illustrating how they contribute to the scenario. It also identifies potential new features or enhancements that could further support the use case. Where overlapping functionalities exist across use cases, these are acknowledged and will be further analyzed in the following clause 7, which focuses on deriving structured application requirements and identifying gaps for future standardization efforts.

## 6.1	MEC Frameworks