add references of ETSI documents

The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding but are not required for conformance to the present document.

- <a name="_ref_i.1">[i.1]</a>

- <a name="https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf">[i.1]</a> ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture".

- <a name="https://www.etsi.org/images/files/ETSIWhitePapers/ETSI-WP59-Enabling-Multi-access-Edge-Computing-in-iot.pdf">[i.2]</a> Enabling Multi-access Edge Computing in Internet-of- Things: how to deploy ETSI MEC and oneM2M".

# 3 Definition of terms, symbols and abbreviations

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

![6.2-1. Multi-access edge system reference architecture [Todo:Add Reference].](/media/mec_arch_6_1.png)

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

**Figure 6.2-1: ETSI MEC architecture**

Figure 6.2-1 depicts the generic multi-access edge system reference architecture. The MEC framework defined by ETSI 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 components:

- MEC Orchestrator: manages resources and coordinates MEC operations.

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

This section provides a synthesis of the previously identified use cases in section 5 and the architectural features of the MEC and oneM2M frameworks. It maps each use case to the relevant framework components and functionalities, showcasing how MEC and oneM2M support specific operational needs. The mapping highlights the alignment between the frameworks and the identified scenarios, while also pointing out areas where enhancements or additional integration mechanisms may be required to better support cross-domain use cases. 

### 6.4.1 Deployment Options   

The selection of the most appropriate deployment option for each use case is guided by insights from the ETSI white paper [Todo: Add reference], where 4 deployment options are mentioned for interworking of oneM2M and MEC technologies.

The selection of the most appropriate deployment option for each use case is guided by insights from the ETSI white paper[i.2], where 4 deployment options are mentioned for interworking of oneM2M and MEC technologies.

#### 6.4.1.1 Option A: deploy the oneM2M as a cloud, MEC as an edge

- This deployment presents the IoT platform itself on the cloud side.