Merge branch 'ESTIMED-D2.2-Clause-6-revisions-4.0.3' into 'ESTIMED-D2.2-StableDraft-4.0.3'

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.2	MEC Frameworks

This section provides an overview of the MEC framework, detailing its components, services, and how it supports Edge-based applications.

ETSI ISG MEC (European Telecommunications Standards Institute Industry Specification Group for Multi-access Edge Computing) is the home of technical standards for edge computing. The work of the MEC initiative aims to unite the telco and IT-cloud worlds, providing IT and cloud-computing capabilities within the RAN (Radio Access Network). The MEC ISG specifies the elements that are required to enable applications to be hosted in a multi-vendor multi-access edge computing environment.

ETSI MEC framework offers application developers and content providers, cloud-computing capabilities at the edge of the network, in an environment characterized by ultra-low latency and high bandwidth together with real-time access to network information that can be leveraged by applications

ETSI MEC framework offers application developers and content providers, cloud-computing capabilities at the edge of the network, in an environment characterized by ultra-low latency and high bandwidth together with real-time access to radio network information that can be leveraged by applications.

![Figure 6.2-1. Multi-access edge system reference architecture.](media/mec_arch_6_1.png)

**Figure 6.2-1: Multi-access edge system reference architecture**

Figure 6.2-1 depicts the generic multi-access edge system reference architecture. The MEC framework defined by ETSI GS MEC 003 [i.1] includes a standardized architecture with the following key components:

Figure 6.2-1 depicts the generic multi-access edge system reference architecture. The MEC framework defined by ETSI GS MEC 003 [i.1] includes a standardized architecture with the following key functional elements:

- MEC Orchestrator: manages resources and coordinates MEC operations.

- MEC Host: includes the MEC platform, MEC applications, and the underlying virtualization infrastructure.

    - MEP (MEC Platform): provides collection of essential functionalities required to run MEC applications on a particular Virtualisation infrastructure and enable them to provide and consume MEC services. The MEC platform can also provide services.

    - MEC Platform (MEP): provides collection of essential functionalities required to run MEC applications on a particular Virtualisation infrastructure and enable them to provide and consume MEC services. The MEC platform can also provide services.

    - MEC Applications: instantiated and run on the Virtualisation infrastructure based on configuration or based on requests validated by the MEC management.

    - API GW for Clients: controls access to MEC applications by client applications

- MEP Manager: handles the lifecycle management of the MEC platform.

- Virtualisation infrastructure manager (VIM): Mainly allocating, managing and releasing Virtualised (compute, storage and networking) resources of the Virtualisation infrastructure

The architecture also defines several reference points for communication:

MEC also offers another reference architecture variant for MEC in NFV, MEC federation and Support for Security Monitoring and Management. The architecture also defines the following multiple reference points across the various provided reference architecture variants:

- Mp: connects MEC applications with the MEC platform.

- Mm: used for management operations.

- Mx: links to external systems.

- Mff: enables federation with other MEC or non-MEC systems. 

To support applications running at the edge, ETSI has developed a set of standardized service APIs. These APIs allow applications to access useful network and context information through the Mp1 interface. Applications can also register new services or subscribe to existing ones through this interface.

Some examples of MEC service APIs include:

- Location API (MEC-013)

- Radio Network Information API (MEC-012)

- Traffic Management API (MEC-015)

- Device Application Interface (MEC-016)

- Application Mobility Service API (MEC-021)

- WLAN Information API (MEC-028)

- Fixed Access Information API (MEC-029)

- V2X Information API (MEC-030)

- IoT API (MEC-033)

- Federation Enablement API (MEC-040)

- QoS Measurement API (MEC-045)

- Sensor Sharing API (MEC-046)

To support applications running at the edge, ETSI has developed a set of standardized service APIs. This local services environment is a flexible and extendable framework, as new services can be introduced by following the API guidelines in ETSI GS MEC 009, when creating new service APIs. These APIs allow applications to access useful network and context information through the Mp1 interface. MEC applications (API producer) can also register new services to MEP and consume/subscribe to existing ones through this interface. Transition from MEC Phase 1 to MEC Phase 4 (period 2024-2026) provided MEC service APIs include:

- Application lifecycle, rules and requirements management (ETSI GS MEC-010-2)

- Edge Platform Application Enablement (ETSI GS MEC-011)

- Location API (ETSI GS MEC-013)

- Radio Network Information API (ETSI GS MEC-012)

- Traffic Management API (ETSI GS MEC-015)

- Device Application Interface (ETSI GS MEC-016)

- Application Mobility Service API (ETSI GS MEC-021)

- WLAN Information API (ETSI GS MEC-028)

- Fixed Access Information API (ETSI GS MEC-029)

- V2X Information API (ETSI GS MEC-030)

- IoT API (ETSI GS MEC-033)

- Federation Enablement API (ETSI GS MEC-040)

- QoS Measurement API (ETSI GS MEC-045)

- Sensor Sharing API (ETSI GS MEC-046)

All APIs are described using the OpenAPI Specification (OAS), ensuring consistency and ease of integration across platforms.