From 3d6aa37149c49f7fe129c4ccb85b8647af97965e Mon Sep 17 00:00:00 2001 From: garciay Date: Mon, 1 Sep 2025 16:43:46 +0200 Subject: [PATCH 01/12] Refine the skeleton of the document --- GR_MEC-DEC_051.md | 214 +++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 192 insertions(+), 22 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index b929713..228c2b7 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -2,16 +2,16 @@
-**ETSI GR LLL-LLL DDD Vm.t.e (yyyy-mm)** +**ETSI GR MEC-DECODE 051 V0.0.1 (2025-11)** ![~~CAPTION~~](media/GroupReport-logo.png) -**Group REPORT**
+**MEC-DECODE**
-Title;
+Multi-access Edge Computing (MEC);
-Part #: Part element of title;
+ ESTIMED Integration Solutions
Sub-part #: Sub-part element of title
@@ -38,19 +38,18 @@ _Should you need a step-by-step guide for drafting an ETSI deliverable, please c **Disclaimer** -The present document has been produced and approved by the () ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. +The present document has been produced and approved by the Multi-access Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. -ETSI GR LLL-LLL DDD Vm.t.e (yyyy-mm) - - Reference
+DGR/MEC-DEC051EstimedIS
+ <Workitem>
Keywords
-<keywords>
+M2M, MEC, oneM2M
ETSI
@@ -161,24 +160,40 @@ In the present document "**should** ", "**should not** ", "**may** ", "**need no # 1 Scope -The present document ... +This document provides the list of the missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DECODE 050 [i.1](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf). +Editor's notes: Based on the use cases and requirements identified in ETSI GR ​MEC-DEC 050 that can utilize IoT and Edge computing technologies, this GR will propose various solutions that can support these enhancements for enabling MEC-oneM2M deployments # 2 References ## 2.1 Normative references Normative references are not applicable in the present document. - ## 2.2 Informative references -References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. +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. -> NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. +- [\[i.1\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GR MEC-DECODE 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. +- [\[i.2\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/002/04.01.01_60/gs_MEC002v040101p.pdf) ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Use Cases and Requirements" +- [\[i.3\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture". +- [\[i.4\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) ETSI GS MEC 011: "Multi-access Edge Computing (MEC); +Edge Platform Application Enablement". +- [\[i.5\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". +- [\[i.6\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". +- [\[i.7\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". +- [\[i.8\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Federation enablement APIs". -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. +... + +- [\[i.10\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". + +... + +- [\[i.h\]](https://labs.etsi.org/rep/estimed/wp6/hackathons/hackathon-1#hackathon-1) ETSI STF 685 (ESTIMED): First Hackathon +... +- [\[i.x\]]() ETSI TS 103 900 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Cooperative Awareness Service; Release 2". +- [\[i.x\]]() ETSI TS 103 831 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service; Release 2". -- [i.1] # 3 Definition of terms, symbols and abbreviations @@ -187,22 +202,177 @@ The following referenced documents may be useful in implementing an ETSI deliver For the purposes of the present document, the [following] terms [given in ... and the following] apply: - - ## 3.2 Symbols For the purposes of the present document, the [following] symbols [given in ... and the following] apply: - ## 3.3 Abbreviations For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply: +# 4. Review of scenario and requirements + +## 4.1. Introduction +The document ETSI GR MEC-DECODE 050 [i.1] introduces 4 different deployment options and a set of use cases. +The clause below are a summary of the presented in the document GR MEC-DECODE 050 [i.1] + + +### 4.1.1 The deployment options +The table below shows the requirements involved by each of the 4 deployment options for each platform. + +#### Table 4.1.1-1 – Deployments options and platform requirements + +| Deployment options | Requirements for MEC | Requirements for oneM2M | +| ------------------ | -------------------- | ----------------------------- | +| Option A | No | No | +| Option B | No | No | +| Option C | No | No | +| Option D | No | [deployment-option-oneM2M-01] [deployment-option-oneM2M-02] [deployment-option-oneM2M-03] | + + +[deployment-option-oneM2M-01] The oneM2M platform may support IoT platform registration as described in ETSI GS MEC 033 clause 5.3. + +[deployment-option-oneM2M-02] The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.2 and 5.2.3. + +[deployment-option-oneM2M-03] The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.13 and 5.2.3. + + +### 4.1.2 The use cases + +#### Table 4.1.2-1 – Deployments options and platform requirements + +| Use cases | Requirements for MEC | Requirements for oneM2M | +| ------------------------------------------------ | -------------------------- | ----------------------------- | +| Autonomous Vehicles and Edge Continuum | [deployment-option-MEC-01] [deployment-option-MEC-02] | [deployment-option-oneM2M-01] | +| Vulnerable Road User Detection | [deployment-option-MEC-01] [deployment-option-MEC-02] | [deployment-option-oneM2M-01] | +| Swarm-based Autonomous Ant Delivery Optimization | [deployment-option-MEC-03] [deployment-option-MEC-04] | [deployment-option-oneM2M-02] [deployment-option-oneM2M-02] | +| Smart Warehouse Automation | [deployment-option-MEC-01] [deployment-option-MEC-02] | | +| Industrial Digital Twins | | | +| Assisted Manoeuvring for Connected Ships | | | +| Smart Virtual Shopping Service | | | +| Advanced Smart Home Services | | | + +TODO Finalyse the table above + +[deployment-option-MEC-01] The MEC platform Mobility Service API [i.7] may be revised to fit use case requirement. + +[deployment-option-MEC-02] The MEC platform Federation [i.8] may be revised to fit use case requirement. + +[deployment-option-MEC-03] The MEC platform may support a MEC service that support swarm computing features. + +[deployment-option-MEC-04] The MEC platform may support a MEC service that support Federated learning features. + +[deployment-option-oneM2M-01] The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. + +[deployment-option-oneM2M-02] The oneM2M platform may support MEC Swarm computing Service API. + +[deployment-option-oneM2M-03] The oneM2M platform may support MEC Federated learning Service API. + + +# 5. ETSI MEC requirements + +## 5.1. Introduction +The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [i.3]. The ETSI GR MEC-DECODE 050 [i.1] highlights the need of new MEC services and the need to revise some existing MEC services. + +## 5.2. Missing requirements + +### 5.2.1. Features Federated Learning service + +[FL-Service-01] The MEC platform exposes APIs to allow authorized MEC applications to register, discover, and consume the Federated Learning service. + +[FL-Service-02] The Federated Learning service supports the coordination between multiple federated clients (MEC applications) and a federated server (central aggregator), leveraging model descriptors and status information via standardized interfaces. + +[FL-Service-04] The Federated Learning service provides secure handling of model parameters and updates during federated training and aggregation, supporting integrity and confidentiality mechanisms as required. + +[FL-Service-05] The Federated Learning service allows the announcement and dynamic discovery of available federated learning resources and participating nodes in the MEC ecosystem. + +[FL-Service-06] The Federated Learning service supports dynamic control by the MEC operator over which applications can participate in federated learning rounds, according to policy and resource availability. +[FL-Service-07] The Federated Learning service exposes status, resource consumption metrics (CPU, RAM, disk), and activity updates related to federated training to authorized consumers. + +[FL-Service-08] The Federated Learning service provides means for applications to register rewards or incentives associated with participation in federated learning, supporting mechanisms for reporting and auditing training contributions. + +[FL-Service-09] The Federated Learning service handles volatility and mobility of participating entities (e.g., UEs entering/leaving an Area of Interest), assisting with migration and context transfer as necessary. + +TODO To be refined + + +### 5.2.2. Swarm computing + +TODO + + +### 5.2.3. MEC Interworking with oneM2M +Even if for the purpose of the first ETSI STF 685 Hackathon [i.h], a first version of the MEC Interworking with oneM2M was introduced, the Interworking with oneM2M is considered as a new MEC feature. +The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms. +The MEC Interworking with oneM2M follows these three steps [i.10]: +1. Interworking on the connection layer +2. Interworking on the resource framework layer +3. Interworking on the information model layer + +### 5.2.3.1 MEC Interworking on the connection layer + +TODO + + +### 5.2.3.2 MEC Interworking on the resource framework layer + +TODO + + +### 5.2.3.3 MEC Interworking on the information model layer + +TODO + + +## 5.3. Requirements to be enhanced or to be re-worked +The clauses below described the existing requirements in the ETSI MEC architecture that require some enhancements or to be re-worked. + + +### 5.3.1. Platform registration +To work together, both the oneM2M platform and the MEC platform need to know each others. +The ETSI GS MEC 033 [i.5] introduces a registration mechanism for an IoT platform to register to the MEC platform. + + +### 5.3.2. Mobility services + +TODO + + +### 5.3.3. IoT Devices + +TODO + + +### 5.3.4. Sensor sharing + +TODO + + +## Conclusions & Actions +This clause provides a list of the NWI to propose to ETSI ISG MEC in order to initiate the standardisation work the features covered by this document. + +TODO + + +# 6. oneM2M requirements + +## 6.1. Introduction + +TODO + + +## 6.x Conclusions & Actions +This clause provides a list of the NWI to propose to omeM2M in order to initiate the enhancement of the oneM2M platform with these new features. + +TODO + + +# 7. Conclusions +A few sentences to conclude the document -# 4 User defined clause(s) from here onwards +TODO -## 4.1 User defined subdivisions of clause(s) from here onwards
@@ -232,7 +402,7 @@ For the purposes of the present document, the [following] abbreviations [given i | Date | Version | Information about changes | |------------|---------|---------------------------| -|<Month year>| <#> | <Changes made are listed in this cell> | +|V1.0.0 | <#> | Publication | | | | | | | | | | | | | @@ -247,7 +417,7 @@ For the purposes of the present document, the [following] abbreviations [given i +:==============+:==============+:================+ | Version | Date | Milestone | +---------------+---------------+-----------------+ -| | <#> | | +|V0.0.1 | November 2025 |Early draft | +---------------+---------------+-----------------+ | | | | +---------------+---------------+-----------------+ -- GitLab From ee6ae11af918ed0462f35aa198d6618db3657269 Mon Sep 17 00:00:00 2001 From: garciay Date: Thu, 4 Sep 2025 15:11:51 +0200 Subject: [PATCH 02/12] Add links with tasks T3.x as editor's note; Refined some clauses --- GR_MEC-DEC_051.md | 68 +++++++++++++++++++++++++++++++++++------------ 1 file changed, 51 insertions(+), 17 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index 228c2b7..f9503a5 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -185,6 +185,7 @@ Edge Platform Application Enablement". ... - [\[i.10\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". +- [\[i.11\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf) ETSI TS 118 123 V4.8.1 (2024-02): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". ... @@ -253,7 +254,7 @@ The table below shows the requirements involved by each of the 4 deployment opti | Smart Virtual Shopping Service | | | | Advanced Smart Home Services | | | -TODO Finalyse the table above +**TODO** Finalyse the table above [deployment-option-MEC-01] The MEC platform Mobility Service API [i.7] may be revised to fit use case requirement. @@ -294,35 +295,48 @@ The current state of the art on the ETSI MEC architecture are described in ETSI [FL-Service-09] The Federated Learning service handles volatility and mobility of participating entities (e.g., UEs entering/leaving an Area of Interest), assisting with migration and context transfer as necessary. -TODO To be refined +**TODO** To be refined + +Editor's note: This clause is linked to the task T3.4 ### 5.2.2. Swarm computing -TODO +**TODO** + +Editor's note: This clause is linked to the task T3.4 ### 5.2.3. MEC Interworking with oneM2M + Even if for the purpose of the first ETSI STF 685 Hackathon [i.h], a first version of the MEC Interworking with oneM2M was introduced, the Interworking with oneM2M is considered as a new MEC feature. -The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms. +The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [i.10]. The MEC Interworking with oneM2M follows these three steps [i.10]: 1. Interworking on the connection layer 2. Interworking on the resource framework layer 3. Interworking on the information model layer +The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [i.3] describes the procedure to achieve this registration. + +Editor's note: This clause is linked to the task T3.1 + ### 5.2.3.1 MEC Interworking on the connection layer -TODO +Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [i.10], the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is upported. + +**TODO** To be continued ### 5.2.3.2 MEC Interworking on the resource framework layer -TODO +**TODO** To be continued ### 5.2.3.3 MEC Interworking on the information model layer -TODO +For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models such as the ones defined in ETSI TS 118 123 [i.11]. + +**TODO** To be continued ## 5.3. Requirements to be enhanced or to be re-worked @@ -333,45 +347,65 @@ The clauses below described the existing requirements in the ETSI MEC architectu To work together, both the oneM2M platform and the MEC platform need to know each others. The ETSI GS MEC 033 [i.5] introduces a registration mechanism for an IoT platform to register to the MEC platform. +Editor's note: This clause is linked to the task T3.2 + -### 5.3.2. Mobility services +### 5.3.2. Application Mobility Service API -TODO +Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the requirements required in ETSI GR MEC-DECODE 050 [i.1] implies to review and enhance it. +**TODO** To be continued -### 5.3.3. IoT Devices +Editor's note: This clause is linked to the task T3.3 -TODO +### 5.3.3. IoT Devices API -### 5.3.4. Sensor sharing +Currently, ETSI GS MEC 033 [i.5] provides features about IoT Devices API, which includes IoT platform registration amd IoT devices management. The use cases and the requirements required in ETSI GR MEC-DECODE 050 [i.1] implies to review and enhance it. -TODO +**TODO** To be continued + + +### 5.3.4. Sensors sharing API + +Currently, ETSI GS MEC 046 [i.6] provides features about Sensors Sharing APIs. The use cases and the requirements required in ETSI GR MEC-DECODE 050 [i.1] implies to review and enhance it. + +**TODO** To be continued + +Editor's note: This clause is linked to the task T3.1 ## Conclusions & Actions This clause provides a list of the NWI to propose to ETSI ISG MEC in order to initiate the standardisation work the features covered by this document. -TODO +| Requirements | NWI proposal (summary) | Approved by STF | +| ------------ | ---------------------- | --------------- | +| | | | + +**TODO** + +Editor's note: This clause is linked to the tasks T3.1 and T3.5 # 6. oneM2M requirements ## 6.1. Introduction -TODO +**TODO** ## 6.x Conclusions & Actions This clause provides a list of the NWI to propose to omeM2M in order to initiate the enhancement of the oneM2M platform with these new features. -TODO +**TODO** + +Editor's note: This clause is linked to the task T3.5 # 7. Conclusions A few sentences to conclude the document -TODO +**TODO**
-- GitLab From 16aee0e27a1ff7987747bab19d5032fec6dd4725 Mon Sep 17 00:00:00 2001 From: garciay Date: Wed, 10 Sep 2025 07:07:47 +0200 Subject: [PATCH 03/12] Adding proposal for FLService & SWService --- GR_MEC-DEC_051.md | 183 +++++++++++++++++++++++++++++++--------------- 1 file changed, 126 insertions(+), 57 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index f9503a5..7d2bf4c 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -112,7 +112,7 @@ No part may be reproduced or utilized in any form or by any means, electronic or -© ETSI yyyy. +© ETSI 2025. All rights reserved.
@@ -160,9 +160,7 @@ In the present document "**should** ", "**should not** ", "**may** ", "**need no # 1 Scope -This document provides the list of the missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DECODE 050 [i.1](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf). - -Editor's notes: Based on the use cases and requirements identified in ETSI GR ​MEC-DEC 050 that can utilize IoT and Edge computing technologies, this GR will propose various solutions that can support these enhancements for enabling MEC-oneM2M deployments +This document provides the list of the missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DECODE 050 [i.1]. # 2 References @@ -180,12 +178,14 @@ Edge Platform Application Enablement". - [\[i.5\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". - [\[i.6\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". - [\[i.7\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". -- [\[i.8\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Federation enablement APIs". +- [\[i.8\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 059: "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". +- [\[i.9\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 061: "Multi-access Edge Computing (MEC); Federation enablement APIs". + ... -- [\[i.10\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". -- [\[i.11\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf) ETSI TS 118 123 V4.8.1 (2024-02): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". +- [\[i.11\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". +- [\[i.12\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf) ETSI TS 118 123 V4.8.1 (2024-02): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". ... @@ -215,8 +215,7 @@ For the purposes of the present document, the [following] abbreviations [given i # 4. Review of scenario and requirements ## 4.1. Introduction -The document ETSI GR MEC-DECODE 050 [i.1] introduces 4 different deployment options and a set of use cases. -The clause below are a summary of the presented in the document GR MEC-DECODE 050 [i.1] +The document ETSI GR MEC-DECODE 050 [i.1] introduces 4 different deployment options and a set of use cases. The clauses below are a summary of the presented in the document GR MEC-DECODE 050 [i.1]. ### 4.1.1 The deployment options @@ -229,14 +228,14 @@ The table below shows the requirements involved by each of the 4 deployment opti | Option A | No | No | | Option B | No | No | | Option C | No | No | -| Option D | No | [deployment-option-oneM2M-01] [deployment-option-oneM2M-02] [deployment-option-oneM2M-03] | +| Option D | No | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-03]** | -[deployment-option-oneM2M-01] The oneM2M platform may support IoT platform registration as described in ETSI GS MEC 033 clause 5.3. +**[deployment-option-oneM2M-01]** The oneM2M platform may support IoT platform registration as described in ETSI GS MEC 033 clause 5.3. -[deployment-option-oneM2M-02] The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.2 and 5.2.3. +**[deployment-option-oneM2M-02]** The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.2 and 5.2.3. -[deployment-option-oneM2M-03] The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.13 and 5.2.3. +**[deployment-option-oneM2M-03]** The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.13 and 5.2.3. ### 4.1.2 The use cases @@ -245,10 +244,10 @@ The table below shows the requirements involved by each of the 4 deployment opti | Use cases | Requirements for MEC | Requirements for oneM2M | | ------------------------------------------------ | -------------------------- | ----------------------------- | -| Autonomous Vehicles and Edge Continuum | [deployment-option-MEC-01] [deployment-option-MEC-02] | [deployment-option-oneM2M-01] | -| Vulnerable Road User Detection | [deployment-option-MEC-01] [deployment-option-MEC-02] | [deployment-option-oneM2M-01] | -| Swarm-based Autonomous Ant Delivery Optimization | [deployment-option-MEC-03] [deployment-option-MEC-04] | [deployment-option-oneM2M-02] [deployment-option-oneM2M-02] | -| Smart Warehouse Automation | [deployment-option-MEC-01] [deployment-option-MEC-02] | | +| Autonomous Vehicles and Edge Continuum | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | **[deployment-option-oneM2M-01]** | +| Vulnerable Road User Detection | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | **[deployment-option-oneM2M-01]** | +| Swarm-based Autonomous Ant Delivery Optimization | **[deployment-option-MEC-03]** **[deployment-option-MEC-04]** | **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-02]** | +| Smart Warehouse Automation | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | | | Industrial Digital Twins | | | | Assisted Manoeuvring for Connected Ships | | | | Smart Virtual Shopping Service | | | @@ -256,19 +255,19 @@ The table below shows the requirements involved by each of the 4 deployment opti **TODO** Finalyse the table above -[deployment-option-MEC-01] The MEC platform Mobility Service API [i.7] may be revised to fit use case requirement. +**[deployment-option-MEC-01]** The MEC platform Mobility Service API [i.7] may be revised to fit use case requirement. -[deployment-option-MEC-02] The MEC platform Federation [i.8] may be revised to fit use case requirement. +**[deployment-option-MEC-02]** The MEC platform Federation [i.9] may be revised to fit use case requirement. -[deployment-option-MEC-03] The MEC platform may support a MEC service that support swarm computing features. +**[deployment-option-MEC-03]** The MEC platform may support a MEC service that support swarm computing features. -[deployment-option-MEC-04] The MEC platform may support a MEC service that support Federated learning features. +**[deployment-option-MEC-04]** The MEC platform may support a MEC service that support Federated learning features. -[deployment-option-oneM2M-01] The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. +**[deployment-option-oneM2M-01]** The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. -[deployment-option-oneM2M-02] The oneM2M platform may support MEC Swarm computing Service API. +**[deployment-option-oneM2M-02]** The oneM2M platform may support MEC Swarm computing Service API. -[deployment-option-oneM2M-03] The oneM2M platform may support MEC Federated learning Service API. +**[deployment-option-oneM2M-03]** The oneM2M platform may support MEC Federated learning Service API. # 5. ETSI MEC requirements @@ -280,29 +279,58 @@ The current state of the art on the ETSI MEC architecture are described in ETSI ### 5.2.1. Features Federated Learning service -[FL-Service-01] The MEC platform exposes APIs to allow authorized MEC applications to register, discover, and consume the Federated Learning service. +**[FL-01]** The MEC system may support the feature called FLService. + +**[FL-02]** When the MEC system supports the feature FLService, the MEC system supports the capability to expose APIs to allow authorized MEC applications to register, discover, and consume the Federated Learning service. -[FL-Service-02] The Federated Learning service supports the coordination between multiple federated clients (MEC applications) and a federated server (central aggregator), leveraging model descriptors and status information via standardized interfaces. +**[FL-03]** The FLService supports the coordination between multiple federated clients (MEC applications) and a federated server, leveraging model descriptors and status information via standardized interfaces. -[FL-Service-04] The Federated Learning service provides secure handling of model parameters and updates during federated training and aggregation, supporting integrity and confidentiality mechanisms as required. +**[FL-04]** The FLService provides secure handling of model parameters and updates during federated training and aggregation, supporting integrity and confidentiality mechanisms as required. -[FL-Service-05] The Federated Learning service allows the announcement and dynamic discovery of available federated learning resources and participating nodes in the MEC ecosystem. +**[FL-05]** The FLService allows the announcement and dynamic discovery of available federated learning resources and participating nodes in the MEC ecosystem. -[FL-Service-06] The Federated Learning service supports dynamic control by the MEC operator over which applications can participate in federated learning rounds, according to policy and resource availability. -[FL-Service-07] The Federated Learning service exposes status, resource consumption metrics (CPU, RAM, disk), and activity updates related to federated training to authorized consumers. +**[FL-06]** The FLService supports dynamic control by the MEC operator over which applications can participate in federated learning rounds, according to policy and resource availability. -[FL-Service-08] The Federated Learning service provides means for applications to register rewards or incentives associated with participation in federated learning, supporting mechanisms for reporting and auditing training contributions. +**[FL-07]** The FLService exposes status, resource consumption metrics (CPU, RAM, disk), and activity updates related to federated training to authorized consumers. -[FL-Service-09] The Federated Learning service handles volatility and mobility of participating entities (e.g., UEs entering/leaving an Area of Interest), assisting with migration and context transfer as necessary. +**[FL-08]** The FLService provides means for applications to register rewards or incentives associated with participation in federated learning, supporting mechanisms for reporting and auditing training contributions. + +**[FL-09]** The FLService handles volatility and mobility of participating entities (e.g., UEs entering/leaving an Area of Interest), assisting with migration and context transfer as necessary. **TODO** To be refined +Editor's note: The ETSI MEC Sandbox will use Flower framework for the federated learning + Editor's note: This clause is linked to the task T3.4 ### 5.2.2. Swarm computing -**TODO** +MEC Swarm Computing Service Features + +**[SC-01]** The MEC system may support the feature called SCService. + +**[SC-02]** When the MEC system supports the feature SCService, the MEC system offers APIs enabling authorized MEC applications to discover, join, and coordinate Swarm Computing clusters. + +**[SC-02]** The MEC system ensures authentication and authorization for swarm participants and controllers, enabling secure distributed operation. + +**[SC-03]** The SCService supports dynamic formation, adaptation, and dissolution of collaborative clusters based on node availability, proximity, and policy. + +**[SC-04]** The SCService and efficient peer-to-peer communication between nodes, with support for data sharing, task coordination, and status propagation. + +**[SC-05]** The SCService exposes status, resource availability, and operational metrics of swarm participants in real time to authorized applications and operators. + +**[SC-06]** The SCService supports distributed decision-making and adaptive workload adjustment within the swarm, based on context, node health, and performance objectives. + +**[SC-07]** The SCService allows seamless ingress and egress of nodes, maintaining service continuity and dynamic adjustment of swarm topology. + +**[SC-08]** The SCService provides mechanisms for fault tolerance and recovery, enabling compensation for failure or loss of participating nodes. + +**[SC-09]** The SCService supports operator policies determining participation, prioritization, and resource allocation for swarm tasks. + +**[SC-10]** The SCService facilitates secure code and data distribution across swarm nodes, supporting confidentiality, integrity, and compliance requirements for collaborative tasks. + +**TODO** To be continued Editor's note: This clause is linked to the task T3.4 @@ -310,33 +338,48 @@ The current state of the art on the ETSI MEC architecture are described in ETSI ### 5.2.3. MEC Interworking with oneM2M Even if for the purpose of the first ETSI STF 685 Hackathon [i.h], a first version of the MEC Interworking with oneM2M was introduced, the Interworking with oneM2M is considered as a new MEC feature. -The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [i.10]. -The MEC Interworking with oneM2M follows these three steps [i.10]: +The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [i.11]. +The MEC Interworking with oneM2M follows these three steps [i.11]: 1. Interworking on the connection layer 2. Interworking on the resource framework layer 3. Interworking on the information model layer +### 5.2.3.1 MEC Interworking architecture + +The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture, the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.5] and ETSI GS MEC 046 [i.6]. + The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [i.3] describes the procedure to achieve this registration. Editor's note: This clause is linked to the task T3.1 -### 5.2.3.1 MEC Interworking on the connection layer +### 5.2.3.2 MEC Interworking on the connection layer -Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [i.10], the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is upported. +Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [i.11], the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is supported. +By the end of the STF 685 project, the MEC Interworking with oneM2M will provide support of CoAP over Secured Websocket. + +**[interworking-MEC-01]** The MEC Interworking supports MQTT over secured Websocket. + +**[interworking-MEC-02]** The MEC Interworking supports CoAP over secured Websocket. **TODO** To be continued -### 5.2.3.2 MEC Interworking on the resource framework layer +### 5.2.3.3 MEC Interworking on the resource framework layer -**TODO** To be continued +Currently, only JSON serialization mechanism is natively supported, by the end of the STF 685 project, the MEC Interworking with oneM2M will provide compliancy to oneM2M-defined the resource framework layer such as the ones defined in ETSI TS 118 123 [i.12]. +**[serialization-MEC-01]** The MEC Interworking supports XML serialization. -### 5.2.3.3 MEC Interworking on the information model layer +**[serialization-MEC-02]** The MEC Interworking supports CBOR serialization. -For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models such as the ones defined in ETSI TS 118 123 [i.11]. +**TODO** To be refined -**TODO** To be continued + +### 5.2.3.4 MEC Interworking on the information model layer + +For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models such as the ones defined in ETSI TS 118 123 [i.12]. + +**TODO** To be refined ## 5.3. Requirements to be enhanced or to be re-worked @@ -380,7 +423,15 @@ This clause provides a list of the NWI to propose to ETSI ISG MEC in order to in | Requirements | NWI proposal (summary) | Approved by STF | | ------------ | ---------------------- | --------------- | -| | | | +|**[deployment-option-MEC-01]**| | | +|**[deployment-option-MEC-02]**| | | +|**[deployment-option-MEC-03]**| | | +|**[deployment-option-MEC-04]**| | | +|**[interworking-MEC-01]**| | | +|**[interworking-MEC-01]**| | | +|**[serialization-MEC-01]**| | | +|**[serialization-MEC-01]**| | | + **TODO** @@ -394,7 +445,28 @@ This clause provides a list of the NWI to propose to ETSI ISG MEC in order to in **TODO** -## 6.x Conclusions & Actions +## 6.2 oneM2M new requirements + +**TODO** + + +### 6.2.1 Registration mechanism + +**TODO** + + +### 6.2.2 Support of MQTT & CoAP over secured Websocket + +**TODO** + + +## 6.3. Requirements to be enhanced or to be re-worked +The clauses below described the existing requirements in the oneM2m architecture that require some enhancements or to be re-worked. + +**TODO** + + +## 6.4 Conclusions & Actions This clause provides a list of the NWI to propose to omeM2M in order to initiate the enhancement of the oneM2M platform with these new features. **TODO** @@ -434,26 +506,23 @@ A few sentences to conclude the document # Annex : Change history -| Date | Version | Information about changes | -|------------|---------|---------------------------| -|V1.0.0 | <#> | Publication | -| | | | -| | | | -| | | | +| Date | Version | Information about changes | +| --------------- | ------- | ----------------------------------------- | +| <Month year> | <#> | <Changes made are listed in this cell> | +| | | | +| | | | +| | | |
# History -+-------------------------------------------------+ -|Document History | -+:==============+:==============+:================+ | Version | Date | Milestone | -+---------------+---------------+-----------------+ +|---------------|---------------|-----------------| |V0.0.1 | November 2025 |Early draft | -+---------------+---------------+-----------------+ +|---------------|---------------|-----------------| | | | | -+---------------+---------------+-----------------+ +|---------------|---------------|-----------------| | | | | -+---------------+---------------+-----------------+ +|---------------|---------------|-----------------| -- GitLab From 12828cc4802901d2633d6c9359ac20c37b67c784 Mon Sep 17 00:00:00 2001 From: garciay Date: Tue, 7 Oct 2025 15:04:55 +0200 Subject: [PATCH 04/12] Fix issue https://labs.etsi.org/rep/estimed/wp3/gr-mec-dec-051/-/issues/1 --- GR_MEC-DEC_051.md | 35 ++++++++++++++++++----------------- 1 file changed, 18 insertions(+), 17 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index 7d2bf4c..a17bbe1 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -2,7 +2,7 @@
-**ETSI GR MEC-DECODE 051 V0.0.1 (2025-11)** +**ETSI GR MEC-DEC 051 V0.0.1 (2025-11)** ![~~CAPTION~~](media/GroupReport-logo.png) @@ -160,7 +160,7 @@ In the present document "**should** ", "**should not** ", "**may** ", "**need no # 1 Scope -This document provides the list of the missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DECODE 050 [i.1]. +This document provides the list of the missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DEC 050 [i.1]. # 2 References @@ -170,16 +170,17 @@ Normative references are not applicable in the present document. ## 2.2 Informative references 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. -- [\[i.1\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GR MEC-DECODE 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. +- [\[i.1\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GR MEC-DEC 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. - [\[i.2\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/002/04.01.01_60/gs_MEC002v040101p.pdf) ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Use Cases and Requirements" - [\[i.3\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture". - [\[i.4\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) ETSI GS MEC 011: "Multi-access Edge Computing (MEC); Edge Platform Application Enablement". -- [\[i.5\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". -- [\[i.6\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". -- [\[i.7\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". -- [\[i.8\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 059: "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". -- [\[i.9\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 061: "Multi-access Edge Computing (MEC); Federation enablement APIs". +- [\[i.5\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". +- [\[i.6\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". +- [\[i.7\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 040: "Multi-access Edge Computing (MEC); Federation enablement APIs". +- [\[i.8\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". +- [\[9\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GR MEC 059: "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". +- [\[i.10\]](https://docbox.etsi.org/ISG/MEC/70-Draft/0061v411AIML.in.MEC/MEC-0061v411AIML.in.MECv402.docx) ETSI GR MEC 061: "Multi-access Edge Computing (MEC); Artificial Intelligence / Machine Learning in MEC". ... @@ -215,7 +216,7 @@ For the purposes of the present document, the [following] abbreviations [given i # 4. Review of scenario and requirements ## 4.1. Introduction -The document ETSI GR MEC-DECODE 050 [i.1] introduces 4 different deployment options and a set of use cases. The clauses below are a summary of the presented in the document GR MEC-DECODE 050 [i.1]. +The document ETSI GR MEC-DEC 050 [i.1] introduces 4 different deployment options and a set of use cases. The clauses below are a summary of the presented in the document GR MEC-DEC 050 [i.1]. ### 4.1.1 The deployment options @@ -255,9 +256,9 @@ The table below shows the requirements involved by each of the 4 deployment opti **TODO** Finalyse the table above -**[deployment-option-MEC-01]** The MEC platform Mobility Service API [i.7] may be revised to fit use case requirement. +**[deployment-option-MEC-01]** The MEC platform Mobility Service API [i.5] may be revised to fit use case requirement. -**[deployment-option-MEC-02]** The MEC platform Federation [i.9] may be revised to fit use case requirement. +**[deployment-option-MEC-02]** The MEC platform Federation [i.7] may be revised to fit use case requirement. **[deployment-option-MEC-03]** The MEC platform may support a MEC service that support swarm computing features. @@ -273,7 +274,7 @@ The table below shows the requirements involved by each of the 4 deployment opti # 5. ETSI MEC requirements ## 5.1. Introduction -The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [i.3]. The ETSI GR MEC-DECODE 050 [i.1] highlights the need of new MEC services and the need to revise some existing MEC services. +The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [i.3]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new MEC services and the need to revise some existing MEC services. ## 5.2. Missing requirements @@ -346,7 +347,7 @@ The MEC Interworking with oneM2M follows these three steps [i.11]: ### 5.2.3.1 MEC Interworking architecture -The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture, the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.5] and ETSI GS MEC 046 [i.6]. +The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture, the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.6] and ETSI GS MEC 046 [i.8]. The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [i.3] describes the procedure to achieve this registration. @@ -388,14 +389,14 @@ The clauses below described the existing requirements in the ETSI MEC architectu ### 5.3.1. Platform registration To work together, both the oneM2M platform and the MEC platform need to know each others. -The ETSI GS MEC 033 [i.5] introduces a registration mechanism for an IoT platform to register to the MEC platform. +The ETSI GS MEC 033 [i.6] introduces a registration mechanism for an IoT platform to register to the MEC platform. Editor's note: This clause is linked to the task T3.2 ### 5.3.2. Application Mobility Service API -Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the requirements required in ETSI GR MEC-DECODE 050 [i.1] implies to review and enhance it. +Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. **TODO** To be continued @@ -404,14 +405,14 @@ Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The ### 5.3.3. IoT Devices API -Currently, ETSI GS MEC 033 [i.5] provides features about IoT Devices API, which includes IoT platform registration amd IoT devices management. The use cases and the requirements required in ETSI GR MEC-DECODE 050 [i.1] implies to review and enhance it. +Currently, ETSI GS MEC 033 [i.6] provides features about IoT Devices API, which includes IoT platform registration amd IoT devices management. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. **TODO** To be continued ### 5.3.4. Sensors sharing API -Currently, ETSI GS MEC 046 [i.6] provides features about Sensors Sharing APIs. The use cases and the requirements required in ETSI GR MEC-DECODE 050 [i.1] implies to review and enhance it. +Currently, ETSI GS MEC 046 [i.8] provides features about Sensors Sharing APIs. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. **TODO** To be continued -- GitLab From 34ee2c55b9069b1284319c994403b19c1cc49f11 Mon Sep 17 00:00:00 2001 From: garciay Date: Wed, 8 Oct 2025 11:30:10 +0200 Subject: [PATCH 05/12] Addressing issue https://labs.etsi.org/rep/estimed/wp3/gr-mec-dec-051/-/issues/2 --- GR_MEC-DEC_051.md | 38 +++++++++++++++++++++----------------- 1 file changed, 21 insertions(+), 17 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index a17bbe1..d35639a 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -216,13 +216,15 @@ For the purposes of the present document, the [following] abbreviations [given i # 4. Review of scenario and requirements ## 4.1. Introduction -The document ETSI GR MEC-DEC 050 [i.1] introduces 4 different deployment options and a set of use cases. The clauses below are a summary of the presented in the document GR MEC-DEC 050 [i.1]. +The document ETSI GR MEC-DEC 050 [i.1] introduces 4 different deployment options with the evolution towards the joint MEC-oneM2M standardized architecture (GR MEC-DEC 050 [i.1]) to support these. + + +## 4.2 The deployment options -### 4.1.1 The deployment options The table below shows the requirements involved by each of the 4 deployment options for each platform. -#### Table 4.1.1-1 – Deployments options and platform requirements +### Table 4.2-1 – Deployments options and platform requirements | Deployment options | Requirements for MEC | Requirements for oneM2M | | ------------------ | -------------------- | ----------------------------- | @@ -239,30 +241,32 @@ The table below shows the requirements involved by each of the 4 deployment opti **[deployment-option-oneM2M-03]** The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.13 and 5.2.3. -### 4.1.2 The use cases +## 4.3 The use cases -#### Table 4.1.2-1 – Deployments options and platform requirements +### Table 4.3-1 – Deployments options and platform requirements | Use cases | Requirements for MEC | Requirements for oneM2M | | ------------------------------------------------ | -------------------------- | ----------------------------- | -| Autonomous Vehicles and Edge Continuum | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | **[deployment-option-oneM2M-01]** | -| Vulnerable Road User Detection | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | **[deployment-option-oneM2M-01]** | -| Swarm-based Autonomous Ant Delivery Optimization | **[deployment-option-MEC-03]** **[deployment-option-MEC-04]** | **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-02]** | -| Smart Warehouse Automation | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | | -| Industrial Digital Twins | | | -| Assisted Manoeuvring for Connected Ships | | | -| Smart Virtual Shopping Service | | | -| Advanced Smart Home Services | | | +| Autonomous Vehicles and Edge Continuum | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** **[deployment-option-MEC-03]** | **[deployment-option-oneM2M-01]** | +| Vulnerable Road User Detection | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** **[deployment-option-MEC-03]** | **[deployment-option-oneM2M-01]** | +| Swarm-based Autonomous Ant Delivery Optimization | **[deployment-option-MEC-01]** **[deployment-option-MEC-04]** **[deployment-option-MEC-05]** | **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-02]** | +| Smart Warehouse Automation | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** **[deployment-option-MEC-03]** **[deployment-option-MEC-04]** | | +| Industrial Digital Twins | **[deployment-option-MEC-01]** | | +| Assisted Manoeuvring for Connected Ships | **[deployment-option-MEC-01]** | | +| Smart Virtual Shopping Service | **[deployment-option-MEC-01]** | | +| Advanced Smart Home Services | **[deployment-option-MEC-01]** | | **TODO** Finalyse the table above -**[deployment-option-MEC-01]** The MEC platform Mobility Service API [i.5] may be revised to fit use case requirement. +**[deployment-option-MEC-01]** The MEC interworking with oneM2M platform. + +**[deployment-option-MEC-02]** The MEC platform Mobility Service API [i.5] may be revised to fit use case requirement. -**[deployment-option-MEC-02]** The MEC platform Federation [i.7] may be revised to fit use case requirement. +**[deployment-option-MEC-03]** The MEC platform Federation [i.7] may be revised to fit use case requirement. -**[deployment-option-MEC-03]** The MEC platform may support a MEC service that support swarm computing features. +**[deployment-option-MEC-04]** The MEC platform may support a MEC service that support swarm computing features. -**[deployment-option-MEC-04]** The MEC platform may support a MEC service that support Federated learning features. +**[deployment-option-MEC-05]** The MEC platform may support a MEC service that support Federated learning features. **[deployment-option-oneM2M-01]** The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. -- GitLab From 0d1b3d0f1180e6186ba113cf8ba2f1d783f11a08 Mon Sep 17 00:00:00 2001 From: garciay Date: Wed, 8 Oct 2025 11:30:10 +0200 Subject: [PATCH 06/12] Addressing issue https://labs.etsi.org/rep/estimed/wp3/gr-mec-dec-051/-/issues/2 --- GR_MEC-DEC_051.md | 374 +++++++++++++++++++++++++++++++++------------- 1 file changed, 268 insertions(+), 106 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index a17bbe1..0a6ac8d 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -160,7 +160,9 @@ In the present document "**should** ", "**should not** ", "**may** ", "**need no # 1 Scope -This document provides the list of the missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DEC 050 [i.1]. +This document provides a set of missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DEC 050 [i.1]. + +This document provides also some requirement for the ETSI MEC Sandbox [i.13] to support the implementation and the deployment of the different use cases in each of the deployment options [i.1]. # 2 References @@ -170,31 +172,27 @@ Normative references are not applicable in the present document. ## 2.2 Informative references 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. -- [\[i.1\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GR MEC-DEC 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. +- [\[i.1\]](https://labs.etsi.org/rep/estimed/wp2/gr-mec-dec-050.git) ETSI GR MEC-DEC 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. - [\[i.2\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/002/04.01.01_60/gs_MEC002v040101p.pdf) ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Use Cases and Requirements" - [\[i.3\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture". -- [\[i.4\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) ETSI GS MEC 011: "Multi-access Edge Computing (MEC); -Edge Platform Application Enablement". +- [\[i.4\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) ETSI GS MEC 011: "Multi-access Edge Computing (MEC); Edge Platform Application Enablement". - [\[i.5\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". - [\[i.6\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". - [\[i.7\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 040: "Multi-access Edge Computing (MEC); Federation enablement APIs". - [\[i.8\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". - [\[9\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GR MEC 059: "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". - [\[i.10\]](https://docbox.etsi.org/ISG/MEC/70-Draft/0061v411AIML.in.MEC/MEC-0061v411AIML.in.MECv402.docx) ETSI GR MEC 061: "Multi-access Edge Computing (MEC); Artificial Intelligence / Machine Learning in MEC". - - -... - - [\[i.11\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". - [\[i.12\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf) ETSI TS 118 123 V4.8.1 (2024-02): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". +- [\[i.12\]](https://labs.etsi.org/rep/estimed/wp3/tr-0077.git) oneM2M TR-0077 Specification: "". +- [\[i.13\]](https://labs.etsi.org/rep/mec/mec-sandbox-scenarios.git) The ETSI MEC Sandbox Scenarios. +- [\[i.14\]]() oneM2M TS-0001: "Functional Architecture". -... -- [\[i.h\]](https://labs.etsi.org/rep/estimed/wp6/hackathons/hackathon-1#hackathon-1) ETSI STF 685 (ESTIMED): First Hackathon -... -- [\[i.x\]]() ETSI TS 103 900 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Cooperative Awareness Service; Release 2". -- [\[i.x\]]() ETSI TS 103 831 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service; Release 2". +- [\[i.x\]](https://www.etsi.org/deliver/etsi_ts/103900_103999/103900/02.02.01_60/ts_103900v020201p.pdf) ETSI TS 103 900 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Cooperative Awareness Service; Release 2". +- [\[i.x\]](https://www.etsi.org/deliver/etsi_ts/103800_103899/103831/02.02.01_60/ts_103831v020201p.pdf) ETSI TS 103 831 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service; Release 2". +- [\[i.z\]](https://datatracker.ietf.org/doc/html/rfc6455) RFC6455: "The WebSocket Protocol". # 3 Definition of terms, symbols and abbreviations @@ -212,25 +210,82 @@ For the purposes of the present document, the [following] symbols [given in ... For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply: +`3D Three-dimensional` +`3GPP 3rd Generation Partnership Project` +`5G Fifth Generation mobile networks` +`ADN Application Dedicated Node` +`ADN-AE Application Dedicated Node - Application Entity` +`AE Application Entity` +`AGV Autonomous Guided Vehicles` +`AIS Automatic Identification System` +`AI Artificial Intelligence` +`API Application Programming Interface` +`API GW API Gateway` +`AR Augmented Reality` +`ASN Application Service Node` +`ASN-CSE Application Service Node - Common Services Entity` +`AV Autonomous Vehicle` +`CPE Customer Premises Equipment` +`CPU Central Processing Unit` +`CSF Common Service Function` +`CSE Common Services Entity` +`CNC Computer Numerical Control` +`CoAP Constrained Application Protocol` +`DT Digital Twin` +`FL Federated Learning` +`GPU Graphics Processing Unit` +`HTTP Hypertext Transfer Protocol` +`HV Host Vehicle` +`IDT Industrial Digital Twin` +`IN Infrastructure Node` +`IN-AE Infrastructure Node - Application Entity` +`IN-CSE Infrastructure Node - Common Services Entity` +`IoT Internet of Things` +`IPE Interworking Proxy application Entity` +`LIDAR Light Detection and Ranging` +`MEP MEC Platform` +`MN-AE Middle Node AE` +`MN-CSE Middle Node - Common Services Entity` +`NaaS Network as a Service` +`NFV Network Function Virtualisation` +`NoDN Non-oneM2M Node` +`NSE Network Services Entity` +`OAS OpenAPI Specification` +`OCF Open Connectivity Foundation` +`ROC Remote Operation Center` +`SAREF Smart Appliances REFerence` +`VIM Virtualisation Infrastructure Manager` +`VRU Vulnerable Road User` + +**TODO** To be refined + + +# 4 Analysis on the joint MEC-oneM2M deployments -# 4. Review of scenario and requirements +## 4.1 Deployment options -## 4.1. Introduction -The document ETSI GR MEC-DEC 050 [i.1] introduces 4 different deployment options and a set of use cases. The clauses below are a summary of the presented in the document GR MEC-DEC 050 [i.1]. +The document ETSI GR MEC-DEC 050 [i.1], clause 6.4.1 introduces 4 different deployment options : +- Option A: The oneM2M CSE platforms are deployed on the cloud; +- Option B: The oneM2M CSE platforms are at the network edge but the oneM2M platforms and the MEC System are deployed on a separate node; +- Option C: The oneM2M CSE platforms and the MEC System are deployed on the same node; +- Option D: The oneM2M CSE platforms are deployed as part of the MEC System. +## 4.2 Platform Requirements based on the deployment options -### 4.1.1 The deployment options The table below shows the requirements involved by each of the 4 deployment options for each platform. -#### Table 4.1.1-1 – Deployments options and platform requirements +### Table 4.2-1 – Deployments options and platform requirements | Deployment options | Requirements for MEC | Requirements for oneM2M | | ------------------ | -------------------- | ----------------------------- | -| Option A | No | No | -| Option B | No | No | -| Option C | No | No | -| Option D | No | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-03]** | +| Option A | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | +| Option B | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | +| Option C | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | +| Option D | **[mec-enhancement-033]** **[mec-enhancement-046]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-03]** | + +**[mec-enhancement-033]** ETSI GS MEC 033 need to be enhance to fillful oneM2M resources mapping +**[mec-enhancement-046]** ETSI GS MEC 046 need to be enhance to fillful oneM2M resources mapping **[deployment-option-oneM2M-01]** The oneM2M platform may support IoT platform registration as described in ETSI GS MEC 033 clause 5.3. @@ -238,47 +293,105 @@ The table below shows the requirements involved by each of the 4 deployment opti **[deployment-option-oneM2M-03]** The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.13 and 5.2.3. +**Note:** Requirements and enhancements are detailled in clause 6. + +**TODO** To be refined + -### 4.1.2 The use cases +# 5 Edge & IoT Domains and Use Cases -#### Table 4.1.2-1 – Deployments options and platform requirements +## 5.1 Introduction + +The document ETSI GR MEC-DEC 050 [i.1], clause 5 introduces several a basic set of use cases focused on on how the integration of the ETSI MEC and oneM2M frameworks enables next-generation Edge-IoT solutions. +The domain covered are: + +### Table 5.1-1: Domains covered + ++-----------------------+--------------------------------------------+-----------------------------------------+ +| Domain | Use Cases | Focus | ++:======================+:===========================================+:========================================+ +| Smart City & Mobility |- Autonomous Vehicles and Edge Continuum | Real-time data processing, V2X | +| |- Vulnerable Road User Detection | communication, urban mobility | +| | | optimization, traffic safety | ++-----------------------+--------------------------------------------+-----------------------------------------+ +| Industrial & Robotics |- Swarm-based Autonomous Ant Delivery | Intelligent coordination, low-latency | +| | Optimization | control, industrial automation, | +| |- Smart Warehouse Automation | edge-based robotics | +| |- Industrial Digital Twins | | ++-----------------------+--------------------------------------------+-----------------------------------------+ +| Maritime |- Assisted Manoeuvring for Connected Ships | Remote vessel monitoring, | +| | | mission-critical edge processing, | +| | | seamless edge-cloud communication | ++-----------------------+--------------------------------------------+-----------------------------------------+ +| Metaverse |- Smart Virtual Shopping Service | IoT-enhanced virtual environments, | +| | | edge-hosted AI analytics, immersive | +| | | low-latency digital experiences | ++-----------------------+--------------------------------------------+-----------------------------------------+ +| Future Home |- Advanced Smart Home Services | Real-time media, education, health, and | +| | | automation services within personalized,| +| | | responsive smart environments | ++-----------------------+--------------------------------------------+-----------------------------------------+ + + +## 5.2 The Edge & IoT use cases + +The evolution towards the joint MEC-oneM2M standardized architecture to support both the deployment options and the Edge & IoT use cases was proposed in clause 7 of the document ETSI GR MEC-DEC 050 [i.1]. + +### Table 5.2-1 – Deployments options and platform requirements | Use cases | Requirements for MEC | Requirements for oneM2M | | ------------------------------------------------ | -------------------------- | ----------------------------- | -| Autonomous Vehicles and Edge Continuum | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | **[deployment-option-oneM2M-01]** | -| Vulnerable Road User Detection | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | **[deployment-option-oneM2M-01]** | -| Swarm-based Autonomous Ant Delivery Optimization | **[deployment-option-MEC-03]** **[deployment-option-MEC-04]** | **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-02]** | -| Smart Warehouse Automation | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | | -| Industrial Digital Twins | | | -| Assisted Manoeuvring for Connected Ships | | | -| Smart Virtual Shopping Service | | | -| Advanced Smart Home Services | | | +| Autonomous Vehicles and Edge Continuum | **[IPE-XXX-0X]** **[mec-enhancement-021]** **[mec-enhancement-040]** **[Location-0X]** **[V2X-0X]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-04]** | +| Vulnerable Road User Detection | **[IPE-XXX-0X]** **[mec-enhancement-021]** **[mec-enhancement-040]** **[Location-0X]** **[V2X-0X]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-04]** | +| Swarm-based Autonomous Ant Delivery Optimization | **[IPE-XXX-0X]** **[SC-0X]** **[FL-0X]** **[CustomerPremiseEdge-0X]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-05]** **[deployment-option-oneM2M-06]** | +| Smart Warehouse Automation | **[IPE-XXX-0X]** **[mec-enhancement-021]** **[mec-enhancement-040]** **[SC-0X]** **[CustomerPremiseEdge-0X]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-05]** **[deployment-option-oneM2M-06]** | +| Industrial Digital Twins | **[IPE-XXX-0X]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-05]** **[deployment-option-oneM2M-06]** | +| Assisted Manoeuvring for Connected Ships | **[IPE-XXX-0X]** **[mec-enhancement-021]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-05]** **[deployment-option-oneM2M-06]** | +| Smart Virtual Shopping Service | **[IPE-XXX-0X]** **[mec-enhancement-021]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-05]** **[deployment-option-oneM2M-06]** | +| Advanced Smart Home Services | **[IPE-XXX-0X]** **[mec-enhancement-021]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-05]** **[deployment-option-oneM2M-06]** | **TODO** Finalyse the table above -**[deployment-option-MEC-01]** The MEC platform Mobility Service API [i.5] may be revised to fit use case requirement. +**[IPE-XXX-0X]** The MEC interworking with oneM2M platform. + +**[mec-enhancement-021]** The MEC platform Mobility Service API [i.5] may be revised to fit use case requirement. + +**[mec-enhancement-040]** The MEC platform Federation [i.7] may be revised to fit use case requirement. + +**[FL-0X]** The MEC platform may support a MEC service that support Federated learning features. + +**[SC-0X]** The MEC platform may support a MEC service that support swarm computing features. + +**[deployment-option-oneM2M-04]** The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. -**[deployment-option-MEC-02]** The MEC platform Federation [i.7] may be revised to fit use case requirement. +**[deployment-option-oneM2M-05]** The oneM2M platform may support MEC Federated learning Service API. -**[deployment-option-MEC-03]** The MEC platform may support a MEC service that support swarm computing features. +**[deployment-option-oneM2M-06]** The oneM2M platform may support MEC Swarm computing Service API. -**[deployment-option-MEC-04]** The MEC platform may support a MEC service that support Federated learning features. +**Note:** The proposed requirements and the proposed enhancements are detailled in clause 6 for the MEC platform and clause 7 for the oneM2M platform. -**[deployment-option-oneM2M-01]** The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. +The following requirements are lready described in the ETSI GS MEC 002: -**[deployment-option-oneM2M-02]** The oneM2M platform may support MEC Swarm computing Service API. +**[Location-0X]** Feature LocationService [i.2 clause 6.3.4 Feature LocationService] -**[deployment-option-oneM2M-03]** The oneM2M platform may support MEC Federated learning Service API. +**[V2X-0X]** Feature V2XService [i.2 clause 6.3.8 Feature V2XService] +**[CustomerPremiseEdge-0X]** Feature CustomerPremiseEdge [i.2 clause 6.3.11 Feature CustomerPremiseEdge] -# 5. ETSI MEC requirements +**TODO** To be refined + + +# 6 ETSI MEC platform requirements + +## 6.1 Introduction -## 5.1. Introduction The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [i.3]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new MEC services and the need to revise some existing MEC services. -## 5.2. Missing requirements +## 6.2 Missing requirements + +### 6.2.1 Federated Learning requirement (**[FL-0X]**) -### 5.2.1. Features Federated Learning service +Federated Learning is a distributed machine learning approach in which model training is performed locally on multiple nodes and only model’s parameters or weights, not row data, are exchanged with aggregators. Instead of sending sensitive data to a central location, each node trains a local model using its own data and then shares only the model updates with a central location, which aggregates these updates to improve the global model. This enhances privacy, reduces bandwidth usage, and allows model adaptation close to data sources. **[FL-01]** The MEC system may support the feature called FLService. @@ -300,12 +413,14 @@ The current state of the art on the ETSI MEC architecture are described in ETSI **TODO** To be refined -Editor's note: The ETSI MEC Sandbox will use Flower framework for the federated learning +Editor's note: The ETSI MEC Sandbox [i.13] can use Flower framework for the federated learning Editor's note: This clause is linked to the task T3.4 -### 5.2.2. Swarm computing +### 6.2.2 Swarm computing requirement (**[SC-0X]**) + +Swarm Computing refers to the coordination of multiple MEC/oneM2M instances to perform distributed computing tasks, leveraging the capabilities of edge devices and networks. In this paradigm, individual MEC/oneM2M nodes act like members of a swarm, each contributing processing power, storage, connectivity, or sensing capabilities to achieve collective goal. The system operates in a decentralized and adaptive manner, where tasks can be dynamically partitioned, distributed, and recombined across nodes depending on resource availability, network conditions, and application requirements. MEC Swarm Computing Service Features @@ -331,154 +446,201 @@ MEC Swarm Computing Service Features **[SC-10]** The SCService facilitates secure code and data distribution across swarm nodes, supporting confidentiality, integrity, and compliance requirements for collaborative tasks. -**TODO** To be continued +**TODO** To be refined Editor's note: This clause is linked to the task T3.4 +## 6.3 Requirements to be enhanced + +The clauses below described the existing requirements in the ETSI MEC architecture that require some enhancements or to be re-worked. + +### 6.3.1 ETSI GS MEC 033 enhancement (**[mec-enhancement-033]**) + +To work together, both the oneM2M platform and the MEC platform need to know each others. +The ETSI GS MEC 033 [i.6] introduces a registration mechanism for an IoT platform to register to the MEC platform. + +**TODO** + +Editor's note: This clause is linked to the tasks T3.1 & T3.2 + -### 5.2.3. MEC Interworking with oneM2M +### 6.3.2 ETSI GS MEC 046 enhancement (**[mec-enhancement-046]**) + +**TODO** + +Editor's note: This clause is linked to the tasks T3.1 & T3.2 + + +### 6.3.3 ETSI GS MEC 021 enhancement (**[mec-enhancement-021]**) + +Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. + +**TODO** To be continued + +Editor's note: This clause is linked to the tasks T3.2 & T3.3 + + +## 6.4 ETSI MEC Sandbox requirements + +### 6.4.1 MEC Interworking with oneM2M requirement (**[IPE-XXX-0X]**) -Even if for the purpose of the first ETSI STF 685 Hackathon [i.h], a first version of the MEC Interworking with oneM2M was introduced, the Interworking with oneM2M is considered as a new MEC feature. The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [i.11]. The MEC Interworking with oneM2M follows these three steps [i.11]: 1. Interworking on the connection layer 2. Interworking on the resource framework layer 3. Interworking on the information model layer -### 5.2.3.1 MEC Interworking architecture +### 6.4.1.1 MEC Interworking architecture -The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture, the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.6] and ETSI GS MEC 046 [i.8]. +The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture [i.2], the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.6] and ETSI GS MEC 046 [i.8]. The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [i.3] describes the procedure to achieve this registration. Editor's note: This clause is linked to the task T3.1 -### 5.2.3.2 MEC Interworking on the connection layer + +### 6.4.1.2 MEC Interworking on the connection layer Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [i.11], the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is supported. By the end of the STF 685 project, the MEC Interworking with oneM2M will provide support of CoAP over Secured Websocket. -**[interworking-MEC-01]** The MEC Interworking supports MQTT over secured Websocket. +**[IPE-COMM-01]** The MEC Interworking supports HTTP/HTTPS. -**[interworking-MEC-02]** The MEC Interworking supports CoAP over secured Websocket. +**[IPE-COMM-02]** The MEC Interworking supports MQTT over secured Websocket. -**TODO** To be continued +**[IPE-COMM-03]** The MEC Interworking supports CoAP over secured Websocket. + +**TODO** To be refined -### 5.2.3.3 MEC Interworking on the resource framework layer +### 6.4.1.3 MEC Interworking on the resource framework layer Currently, only JSON serialization mechanism is natively supported, by the end of the STF 685 project, the MEC Interworking with oneM2M will provide compliancy to oneM2M-defined the resource framework layer such as the ones defined in ETSI TS 118 123 [i.12]. -**[serialization-MEC-01]** The MEC Interworking supports XML serialization. +**[IPE-SER-01]** The MEC Interworking supports XML serialization. + +**[IPE-SER-02]** The MEC Interworking supports JSON serialization. -**[serialization-MEC-02]** The MEC Interworking supports CBOR serialization. +**[IPE-SER-03]** The MEC Interworking supports CBOR serialization. **TODO** To be refined -### 5.2.3.4 MEC Interworking on the information model layer +### 6.4.1.4 MEC Interworking on the information model layer -For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models such as the ones defined in ETSI TS 118 123 [i.12]. +Mainly, MEC Interworking on the information model layer provides the harmonization of the informatioon model for both oneM2M with and MEC platform. +For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models as defined in ETSI TS 118 123 [i.12]. **TODO** To be refined -## 5.3. Requirements to be enhanced or to be re-worked -The clauses below described the existing requirements in the ETSI MEC architecture that require some enhancements or to be re-worked. +# 7. oneM2M requirements +## 7.1. Introduction -### 5.3.1. Platform registration -To work together, both the oneM2M platform and the MEC platform need to know each others. -The ETSI GS MEC 033 [i.6] introduces a registration mechanism for an IoT platform to register to the MEC platform. +The current state of the art on the oneM2M architecture are described in oneM2M TS-0001 Functional Architecture [i.14]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new oneM2M requirements and the need to revise some existing ones. -Editor's note: This clause is linked to the task T3.2 +**TODO** To be refined -### 5.3.2. Application Mobility Service API +## 7.2 oneM2M new requirements -Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. +### 7.2.1 Registration mechanism (**[deployment-option-oneM2M-01]**) -**TODO** To be continued +The oneM2M platform (MN-CSE) may support ETSI GS MEC 033 [i.6] to register to MEC platform. +During the setup phase of the oneM2M platform, it registers to the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [i.6] clauses 5.3.4 IoT platform registration and 7.5.3.4 POST. +During the shutdown phase of the oneM2M platform, it deregisters from the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [i.6] clauses 5.3.6 IoT platform deregistration and 7.6.3.5 DELETE. +The data structure used for these operations is described in ETSI GS MEC 033 [i.6] clause 6.2.3 Type: IotPlatformInfo. -Editor's note: This clause is linked to the task T3.3 +**TODO** To be refined + +Editor's note: This clause is linked to the tasks T3.1 -### 5.3.3. IoT Devices API +### 7.2.2 Registration mechanism (**[deployment-option-oneM2M-03], [deployment-option-oneM2M-03]**) -Currently, ETSI GS MEC 033 [i.6] provides features about IoT Devices API, which includes IoT platform registration amd IoT devices management. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. +In order to act as a MEC application (MN-CSE, MN-AE) or a MEC service (MN-CSE), the oneM2M platform may support ETSI GS MEC 011 [i.4] application management and service management. **TODO** To be continued +Editor's note: This clause is linked to the tasks T3.1, T3.2, T3.3 and T3.4 -### 5.3.4. Sensors sharing API -Currently, ETSI GS MEC 046 [i.8] provides features about Sensors Sharing APIs. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. +### 7.2.3 ETSI C-ITS Support (**[deployment-option-oneM2M-04]**) -**TODO** To be continued +The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. -Editor's note: This clause is linked to the task T3.1 +**TODO** -## Conclusions & Actions -This clause provides a list of the NWI to propose to ETSI ISG MEC in order to initiate the standardisation work the features covered by this document. +### 7.2.4 MEC Federated Learning Service API Support (**[deployment-option-oneM2M-05]**) -| Requirements | NWI proposal (summary) | Approved by STF | -| ------------ | ---------------------- | --------------- | -|**[deployment-option-MEC-01]**| | | -|**[deployment-option-MEC-02]**| | | -|**[deployment-option-MEC-03]**| | | -|**[deployment-option-MEC-04]**| | | -|**[interworking-MEC-01]**| | | -|**[interworking-MEC-01]**| | | -|**[serialization-MEC-01]**| | | -|**[serialization-MEC-01]**| | | +The oneM2M platform may support MEC Federated learning Service API. + +**TODO** + + +### 7.2.5 MEC Swarm computing Service API Support (**[deployment-option-oneM2M-06]**) +The oneM2M platform may support MEC Swarm computing Service API. **TODO** -Editor's note: This clause is linked to the tasks T3.1 and T3.5 +### 7.2.6 Support of MQTT & CoAP over secured Websocket + +Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP cannot be used. The workaround is to use MQTT & CoAP over secured Websocket [i.z] + +**TODO** To be refined -# 6. oneM2M requirements -## 6.1. Introduction +## 7.3. Requirements to be enhanced or to be re-worked **TODO** -## 6.2 oneM2M new requirements +# 8 Conclusions & Actions -**TODO** +## 8.1.1 ISG MEC New Work Items +This clause provides a list of the NWI to propose to ETSI ISG MEC in order to initiate the standardisation work the features covered by this document. -### 6.2.1 Registration mechanism +| Requirements | NWI proposal (summary) | Approved by STF | +| ------------ | ---------------------- | --------------- | +|**[mec-enhancement-021]**| | | +|**[mec-enhancement-040]**| | | +|**[FL-0X]**| | | +|**[SC-0X]**| | | -**TODO** +**TODO** To be refined -### 6.2.2 Support of MQTT & CoAP over secured Websocket +Editor's note: This clause is linked to the tasks T3.1 and T3.5 -**TODO** +## 8.1.2 ETSI MEC Sandbox issues -## 6.3. Requirements to be enhanced or to be re-worked -The clauses below described the existing requirements in the oneM2m architecture that require some enhancements or to be re-worked. +This clause provides a list of the issues to open in the ETSI MEC Sandbox [i.13] GITLAB to cover the requirements. -**TODO** +| Requirements | GITLAB Issue (summary) | Approved by ESTIMED | +| -------------- | ---------------------- | ------------------- | +|**[IP-COMM-01]**| | | +|**[IP-COMM-03]**| | | +|**[IP-COMM-03]**| | | +|**[IP-SER-01]** | | | +|**[IP-SER-01]** | | | +|**[IP-SER-01]** | | | -## 6.4 Conclusions & Actions -This clause provides a list of the NWI to propose to omeM2M in order to initiate the enhancement of the oneM2M platform with these new features. +**TODO** To be refined -**TODO** -Editor's note: This clause is linked to the task T3.5 +Editor's note: This clause is linked to the tasks T3.1 and T3.5 -# 7. Conclusions -A few sentences to conclude the document +## 8.2. oneM2M -**TODO** +Refer to oneM2M TR-0077 Specification [i.12].
-- GitLab From 3d921ed79360af34245cdb66aa95d843488a28b6 Mon Sep 17 00:00:00 2001 From: garciay Date: Tue, 21 Oct 2025 17:09:01 +0200 Subject: [PATCH 07/12] Replace Standard common part before Content; Remove useless file --- GR_MEC-DEC_051.md | 129 +-------- GR_MEC-DEC_051.md.org | 648 ------------------------------------------ 2 files changed, 12 insertions(+), 765 deletions(-) delete mode 100644 GR_MEC-DEC_051.md.org diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index 0a6ac8d..b705e57 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -1,122 +1,17 @@ -
- -**ETSI GR MEC-DEC 051 V0.0.1 (2025-11)** - -![~~CAPTION~~](media/GroupReport-logo.png) - - -**MEC-DECODE**
- -Multi-access Edge Computing (MEC);
- - ESTIMED Integration Solutions
- -Sub-part #: Sub-part element of title
- -Release # - -
- -
-
-
-
- -_Should you need a step-by-step guide for drafting an ETSI deliverable, please consult the "_ [_Principles for Drafting ETSI Deliverables_ ](_Principles for Drafting ETSI Deliverables_ )_" document. Otherwise you may contact us at_ [_edithelp@etsi.org_ ](mailto:edithelp@etsi.org). - - -
-
-
-
- - - -
- -**Disclaimer** - -The present document has been produced and approved by the Multi-access Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. -It does not necessarily represent the views of the entire ETSI membership. - -Reference
- -DGR/MEC-DEC051EstimedIS
- -<Workitem>
- -Keywords
- -M2M, MEC, oneM2M
- -ETSI
- -650 Route des Lucioles
- -F-06921 Sophia Antipolis Cedex - FRANCE
- -Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
- - -Siret N° 348 623 562 00017 - APE 7112B
- -Association à but non lucratif enregistrée à la
- -Sous-préfecture de Grasse (06) N° w061004871
- -
- -
- -
- -**_Important notice_** - -The present document can be downloaded from the [ETSI Search & Browse Standards](ETSI Search & Browse Standards) application. - -The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI deliverable is the one made publicly available in PDF format on [ETSI deliver](ETSI deliver) repository. - -Users should be aware that the present document may be revised or have its status changed, this information is available in the [Milestones listing](Milestones listing). - -If you find errors in the present document, please send your comments to
the relevant service listed under [Committee Support Staff](Committee Support Staff). - -If you find a security vulnerability in the present document, please report it through our - -[Coordinated Vulnerability Disclosure (CVD)](Coordinated Vulnerability Disclosure (CVD)) program. - -
- -**_Notice of disclaimer & limitation of liability_** - -The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of experience to understand and interpret its content in accordance with generally accepted engineering or - -other professional standard and applicable regulations. - -No recommendation as to products and services or vendors is made or should be implied. - -No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness for any particular purpose or against infringement of intellectual property rights. - -In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages. - - - -Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use of or inability to use the software. - -
- -**_Copyright Notification_** - -No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. - - - -© ETSI 2025. - -All rights reserved.
- -
+--- +Title: Multi-access Edge Computing (MEC); ESTIMED Use Cases & Recommendations +Spec Number: MEC-DEC 051 +Version: v0.0.1 +Date: 2025-11 +Release: 1 +Work Item: DGR/MEC-DEC051EstimedRec +keywords: M2M, MEC, oneM2M +Copyright Year: 2025 +Long ISG Name: Multi-access Edge Computing +Short ISG Name: MEC +--- # Contents diff --git a/GR_MEC-DEC_051.md.org b/GR_MEC-DEC_051.md.org deleted file mode 100644 index 3b1ef59..0000000 --- a/GR_MEC-DEC_051.md.org +++ /dev/null @@ -1,648 +0,0 @@ - - -
- -**ETSI GR MEC-DEC 051 V0.0.1 (2025-11)** - -![~~CAPTION~~](media/GroupReport-logo.png) - - -**MEC-DECODE**
- -Multi-access Edge Computing (MEC);
- - ESTIMED Integration Solutions
- -Sub-part #: Sub-part element of title
- -Release # - -
- -
-
-
-
- -_Should you need a step-by-step guide for drafting an ETSI deliverable, please consult the "_ [_Principles for Drafting ETSI Deliverables_ ](_Principles for Drafting ETSI Deliverables_ )_" document. Otherwise you may contact us at_ [_edithelp@etsi.org_ ](mailto:edithelp@etsi.org). - - -
-
-
-
- - - -
- -**Disclaimer** - -The present document has been produced and approved by the Multi-access Edge Computing (MEC) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. -It does not necessarily represent the views of the entire ETSI membership. - -Reference
- -DGR/MEC-DEC051EstimedIS
- -<Workitem>
- -Keywords
- -M2M, MEC, oneM2M
- -ETSI
- -650 Route des Lucioles
- -F-06921 Sophia Antipolis Cedex - FRANCE
- -Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
- - -Siret N° 348 623 562 00017 - APE 7112B
- -Association à but non lucratif enregistrée à la
- -Sous-préfecture de Grasse (06) N° w061004871
- -
- -
- -
- -**_Important notice_** - -The present document can be downloaded from the [ETSI Search & Browse Standards](ETSI Search & Browse Standards) application. - -The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI deliverable is the one made publicly available in PDF format on [ETSI deliver](ETSI deliver) repository. - -Users should be aware that the present document may be revised or have its status changed, this information is available in the [Milestones listing](Milestones listing). - -If you find errors in the present document, please send your comments to
the relevant service listed under [Committee Support Staff](Committee Support Staff). - -If you find a security vulnerability in the present document, please report it through our - -[Coordinated Vulnerability Disclosure (CVD)](Coordinated Vulnerability Disclosure (CVD)) program. - -
- -**_Notice of disclaimer & limitation of liability_** - -The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of experience to understand and interpret its content in accordance with generally accepted engineering or - -other professional standard and applicable regulations. - -No recommendation as to products and services or vendors is made or should be implied. - -No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness for any particular purpose or against infringement of intellectual property rights. - -In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages. - - - -Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use of or inability to use the software. - -
- -**_Copyright Notification_** - -No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. - - - -© ETSI 2025. - -All rights reserved.
- -
- -# Contents - - -
- - -# Intellectual Property Rights - -Essential patents - -IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations pertaining to these essential IPRs, if any, are publicly available for **ETSI members and non-members** , and can be found in ETSI SR 000 314: _"Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards"_ , which is available from the ETSI Secretariat. Latest updates are available on the [ETSI IPR online database](https://ipr.etsi.org/). - -Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. - - -Trademarks - -The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. - -**DECT™**, **PLUGTESTS™**, **UMTS™** and the ETSI logo are trademarks of ETSI registered for the benefit of its Members. **3GPP™**, **LTE™** and **5G™** logo are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. **oneM2M™** logo is a trademark of ETSI registered for the benefit of its Members and of the oneM2M Partners. **GSM®** and the GSM logo are trademarks registered and owned by the GSM Association. - -# Foreword -This Group Report (GR) has been produced by ETSI Industry Specification Group <long ISGname> (<short ISGname>). - - -# Modal verbs terminology -In the present document "**should** ", "**should not** ", "**may** ", "**need not** ", "**will** ", "**will not** ", "**can** " and "**cannot** " are to be interpreted as described in clause 3.2 of the [ETSI Drafting Rules](https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-Rules) (Verbal forms for the expression of provisions). - -"**must** " and "**must not** " are **NOT** allowed in ETSI deliverables except when used in direct citation. - - -# Executive summary - - - -# Introduction - - -
- - -# 1 Scope -This document provides a set of missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DEC 050 [i.1]. - -This document provides also some requirement for the ETSI MEC Sandbox [i.13] to support the implementation and the deployment of the different use cases in each of the deployment options [i.1]. - -# 2 References - -## 2.1 Normative references -Normative references are not applicable in the present document. - -## 2.2 Informative references -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. - -- [\[i.1\]](https://labs.etsi.org/rep/estimed/wp2/gr-mec-dec-050.git) ETSI GR MEC-DEC 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. -- [\[i.2\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/002/04.01.01_60/gs_MEC002v040101p.pdf) ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Use Cases and Requirements" -- [\[i.3\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture". -- [\[i.4\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) ETSI GS MEC 011: "Multi-access Edge Computing (MEC); Edge Platform Application Enablement". -- [\[i.5\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". -- [\[i.6\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". -- [\[i.7\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 040: "Multi-access Edge Computing (MEC); Federation enablement APIs". -- [\[i.8\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". -- [\[9\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GR MEC 059: "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". -- [\[i.10\]](https://docbox.etsi.org/ISG/MEC/70-Draft/0061v411AIML.in.MEC/MEC-0061v411AIML.in.MECv402.docx) ETSI GR MEC 061: "Multi-access Edge Computing (MEC); Artificial Intelligence / Machine Learning in MEC". -- [\[i.11\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". -- [\[i.12\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf) ETSI TS 118 123 V4.8.1 (2024-02): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". -- [\[i.12\]](https://labs.etsi.org/rep/estimed/wp3/tr-0077.git) oneM2M TR-0077 Specification: "". -- [\[i.13\]](https://labs.etsi.org/rep/mec/mec-sandbox-scenarios.git) The ETSI MEC Sandbox Scenarios. -- [\[i.14\]]() oneM2M TS-0001: "Functional Architecture". - - -- [\[i.x\]](https://www.etsi.org/deliver/etsi_ts/103900_103999/103900/02.02.01_60/ts_103900v020201p.pdf) ETSI TS 103 900 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Cooperative Awareness Service; Release 2". -- [\[i.x\]](https://www.etsi.org/deliver/etsi_ts/103800_103899/103831/02.02.01_60/ts_103831v020201p.pdf) ETSI TS 103 831 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service; Release 2". - -- [\[i.z\]](https://datatracker.ietf.org/doc/html/rfc6455) RFC6455: "The WebSocket Protocol". - - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the [following] terms [given in ... and the following] apply: - - -## 3.2 Symbols -For the purposes of the present document, the [following] symbols [given in ... and the following] apply: - - -## 3.3 Abbreviations - -For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply: - -`3D Three-dimensional` -`3GPP 3rd Generation Partnership Project` -`5G Fifth Generation mobile networks` -`ADN Application Dedicated Node` -`ADN-AE Application Dedicated Node - Application Entity` -`AE Application Entity` -`AGV Autonomous Guided Vehicles` -`AIS Automatic Identification System` -`AI Artificial Intelligence` -`API Application Programming Interface` -`API GW API Gateway` -`AR Augmented Reality` -`ASN Application Service Node` -`ASN-CSE Application Service Node - Common Services Entity` -`AV Autonomous Vehicle` -`CPE Customer Premises Equipment` -`CPU Central Processing Unit` -`CSF Common Service Function` -`CSE Common Services Entity` -`CNC Computer Numerical Control` -`CoAP Constrained Application Protocol` -`DT Digital Twin` -`FL Federated Learning` -`GPU Graphics Processing Unit` -`HTTP Hypertext Transfer Protocol` -`HV Host Vehicle` -`IDT Industrial Digital Twin` -`IN Infrastructure Node` -`IN-AE Infrastructure Node - Application Entity` -`IN-CSE Infrastructure Node - Common Services Entity` -`IoT Internet of Things` -`IPE Interworking Proxy application Entity` -`LIDAR Light Detection and Ranging` -`MEP MEC Platform` -`MN-AE Middle Node AE` -`MN-CSE Middle Node - Common Services Entity` -`NaaS Network as a Service` -`NFV Network Function Virtualisation` -`NoDN Non-oneM2M Node` -`NSE Network Services Entity` -`OAS OpenAPI Specification` -`OCF Open Connectivity Foundation` -`ROC Remote Operation Center` -`SAREF Smart Appliances REFerence` -`VIM Virtualisation Infrastructure Manager` -`VRU Vulnerable Road User` - -**TODO** To be refined - - -# 4 Analysis on the joint MEC-oneM2M deployments - -## 4.1 Deployment options - -The document ETSI GR MEC-DEC 050 [i.1], clause 6.4.1 introduces 4 different deployment options : -- Option A: The oneM2M CSE platforms are deployed on the cloud; -- Option B: The oneM2M CSE platforms are at the network edge but the oneM2M platforms and the MEC System are deployed on a separate node; -- Option C: The oneM2M CSE platforms and the MEC System are deployed on the same node; -- Option D: The oneM2M CSE platforms are deployed as part of the MEC System. - -## 4.2 Platform Requirements based on the deployment options - -The table below shows the requirements involved by each of the 4 deployment options for each platform. - -### Table 4.2-1 – Deployments options and platform requirements - -| Deployment options | Requirements for MEC | Requirements for oneM2M | -| ------------------ | -------------------- | ----------------------------- | -| Option A | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | -| Option B | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | -| Option C | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | -| Option D | **[mec-enhancement-033]** **[mec-enhancement-046]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-03]** | - -**[mec-enhancement-033]** ETSI GS MEC 033 need to be enhance to fillful oneM2M resources mapping - -**[mec-enhancement-046]** ETSI GS MEC 046 need to be enhance to fillful oneM2M resources mapping - -**[deployment-option-oneM2M-01]** The oneM2M platform may support IoT platform registration as described in ETSI GS MEC 033 clause 5.3. - -**[deployment-option-oneM2M-02]** The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.2 and 5.2.3. - -**[deployment-option-oneM2M-03]** The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.13 and 5.2.3. - - -### 4.1.2 The use cases - -#### Table 4.1.2-1 – Deployments options and platform requirements - -| Use cases | Requirements for MEC | Requirements for oneM2M | -| ------------------------------------------------ | -------------------------- | ----------------------------- | -| Autonomous Vehicles and Edge Continuum | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | **[deployment-option-oneM2M-01]** | -| Vulnerable Road User Detection | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | **[deployment-option-oneM2M-01]** | -| Swarm-based Autonomous Ant Delivery Optimization | **[deployment-option-MEC-03]** **[deployment-option-MEC-04]** | **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-02]** | -| Smart Warehouse Automation | **[deployment-option-MEC-01]** **[deployment-option-MEC-02]** | | -| Industrial Digital Twins | | | -| Assisted Manoeuvring for Connected Ships | | | -| Smart Virtual Shopping Service | | | -| Advanced Smart Home Services | | | - -**TODO** Finalyse the table above - -**[deployment-option-MEC-01]** The MEC platform Mobility Service API [i.5] may be revised to fit use case requirement. - -**[deployment-option-MEC-02]** The MEC platform Federation [i.7] may be revised to fit use case requirement. - -**[deployment-option-MEC-03]** The MEC platform may support a MEC service that support swarm computing features. - -**[deployment-option-MEC-04]** The MEC platform may support a MEC service that support Federated learning features. - -**[deployment-option-oneM2M-04]** The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. - -**[deployment-option-oneM2M-05]** The oneM2M platform may support MEC Federated learning Service API. - -**[deployment-option-oneM2M-06]** The oneM2M platform may support MEC Swarm computing Service API. - -**Note:** The proposed requirements and the proposed enhancements are detailled in clause 6 for the MEC platform and clause 7 for the oneM2M platform. - -The following requirements are lready described in the ETSI GS MEC 002: - -**[Location-0X]** Feature LocationService [i.2 clause 6.3.4 Feature LocationService] - -**[V2X-0X]** Feature V2XService [i.2 clause 6.3.8 Feature V2XService] - -**[CustomerPremiseEdge-0X]** Feature CustomerPremiseEdge [i.2 clause 6.3.11 Feature CustomerPremiseEdge] - -**TODO** To be refined - - -# 6 ETSI MEC platform requirements - -## 6.1 Introduction - -The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [i.3]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new MEC services and the need to revise some existing MEC services. - -## 6.2 Missing requirements - -### 6.2.1 Federated Learning requirement (**[FL-0X]**) - -Federated Learning is a distributed machine learning approach in which model training is performed locally on multiple nodes and only model’s parameters or weights, not row data, are exchanged with aggregators. Instead of sending sensitive data to a central location, each node trains a local model using its own data and then shares only the model updates with a central location, which aggregates these updates to improve the global model. This enhances privacy, reduces bandwidth usage, and allows model adaptation close to data sources. - -**[FL-01]** The MEC system may support the feature called FLService. - -**[FL-02]** When the MEC system supports the feature FLService, the MEC system supports the capability to expose APIs to allow authorized MEC applications to register, discover, and consume the Federated Learning service. - -**[FL-03]** The FLService supports the coordination between multiple federated clients (MEC applications) and a federated server, leveraging model descriptors and status information via standardized interfaces. - -**[FL-04]** The FLService provides secure handling of model parameters and updates during federated training and aggregation, supporting integrity and confidentiality mechanisms as required. - -**[FL-05]** The FLService allows the announcement and dynamic discovery of available federated learning resources and participating nodes in the MEC ecosystem. - -**[FL-06]** The FLService supports dynamic control by the MEC operator over which applications can participate in federated learning rounds, according to policy and resource availability. - -**[FL-07]** The FLService exposes status, resource consumption metrics (CPU, RAM, disk), and activity updates related to federated training to authorized consumers. - -**[FL-08]** The FLService provides means for applications to register rewards or incentives associated with participation in federated learning, supporting mechanisms for reporting and auditing training contributions. - -**[FL-09]** The FLService handles volatility and mobility of participating entities (e.g., UEs entering/leaving an Area of Interest), assisting with migration and context transfer as necessary. - -**TODO** To be refined - -Editor's note: The ETSI MEC Sandbox [i.13] can use Flower framework for the federated learning - -Editor's note: This clause is linked to the task T3.4 - - -### 6.2.2 Swarm computing requirement (**[SC-0X]**) - -Swarm Computing refers to the coordination of multiple MEC/oneM2M instances to perform distributed computing tasks, leveraging the capabilities of edge devices and networks. In this paradigm, individual MEC/oneM2M nodes act like members of a swarm, each contributing processing power, storage, connectivity, or sensing capabilities to achieve collective goal. The system operates in a decentralized and adaptive manner, where tasks can be dynamically partitioned, distributed, and recombined across nodes depending on resource availability, network conditions, and application requirements. - -MEC Swarm Computing Service Features - -**[SC-01]** The MEC system may support the feature called SCService. - -**[SC-02]** When the MEC system supports the feature SCService, the MEC system offers APIs enabling authorized MEC applications to discover, join, and coordinate Swarm Computing clusters. - -**[SC-02]** The MEC system ensures authentication and authorization for swarm participants and controllers, enabling secure distributed operation. - -**[SC-03]** The SCService supports dynamic formation, adaptation, and dissolution of collaborative clusters based on node availability, proximity, and policy. - -**[SC-04]** The SCService and efficient peer-to-peer communication between nodes, with support for data sharing, task coordination, and status propagation. - -**[SC-05]** The SCService exposes status, resource availability, and operational metrics of swarm participants in real time to authorized applications and operators. - -**[SC-06]** The SCService supports distributed decision-making and adaptive workload adjustment within the swarm, based on context, node health, and performance objectives. - -**[SC-07]** The SCService allows seamless ingress and egress of nodes, maintaining service continuity and dynamic adjustment of swarm topology. - -**[SC-08]** The SCService provides mechanisms for fault tolerance and recovery, enabling compensation for failure or loss of participating nodes. - -**[SC-09]** The SCService supports operator policies determining participation, prioritization, and resource allocation for swarm tasks. - -**[SC-10]** The SCService facilitates secure code and data distribution across swarm nodes, supporting confidentiality, integrity, and compliance requirements for collaborative tasks. - -**TODO** To be refined - -Editor's note: This clause is linked to the task T3.4 - -## 6.3 Requirements to be enhanced - -The clauses below described the existing requirements in the ETSI MEC architecture that require some enhancements or to be re-worked. - -### 6.3.1 ETSI GS MEC 033 enhancement (**[mec-enhancement-033]**) - -To work together, both the oneM2M platform and the MEC platform need to know each others. -The ETSI GS MEC 033 [i.6] introduces a registration mechanism for an IoT platform to register to the MEC platform. - -**TODO** - -Editor's note: This clause is linked to the tasks T3.1 & T3.2 - - -### 6.3.2 ETSI GS MEC 046 enhancement (**[mec-enhancement-046]**) - -**TODO** - -Editor's note: This clause is linked to the tasks T3.1 & T3.2 - - -### 6.3.3 ETSI GS MEC 021 enhancement (**[mec-enhancement-021]**) - -Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. - -**TODO** To be continued - -Editor's note: This clause is linked to the tasks T3.2 & T3.3 - - -## 6.4 ETSI MEC Sandbox requirements - -### 6.4.1 MEC Interworking with oneM2M requirement (**[IPE-XXX-0X]**) - -The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [i.11]. -The MEC Interworking with oneM2M follows these three steps [i.11]: -1. Interworking on the connection layer -2. Interworking on the resource framework layer -3. Interworking on the information model layer - -### 6.4.1.1 MEC Interworking architecture - -The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture [i.2], the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.6] and ETSI GS MEC 046 [i.8]. - -The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [i.3] describes the procedure to achieve this registration. - -Editor's note: This clause is linked to the task T3.1 - - -### 6.4.1.2 MEC Interworking on the connection layer - -Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [i.11], the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is supported. -By the end of the STF 685 project, the MEC Interworking with oneM2M will provide support of CoAP over Secured Websocket. - -**[IPE-COMM-01]** The MEC Interworking supports HTTP/HTTPS. - -**[IPE-COMM-02]** The MEC Interworking supports MQTT over secured Websocket. - -**[IPE-COMM-03]** The MEC Interworking supports CoAP over secured Websocket. - -**TODO** To be refined - - -### 6.4.1.3 MEC Interworking on the resource framework layer - -Currently, only JSON serialization mechanism is natively supported, by the end of the STF 685 project, the MEC Interworking with oneM2M will provide compliancy to oneM2M-defined the resource framework layer such as the ones defined in ETSI TS 118 123 [i.12]. - -**[IPE-SER-01]** The MEC Interworking supports XML serialization. - -**[IPE-SER-02]** The MEC Interworking supports JSON serialization. - -**[IPE-SER-03]** The MEC Interworking supports CBOR serialization. - -**TODO** To be refined - - -### 6.4.1.4 MEC Interworking on the information model layer - -Mainly, MEC Interworking on the information model layer provides the harmonization of the informatioon model for both oneM2M with and MEC platform. -For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models as defined in ETSI TS 118 123 [i.12]. - -**TODO** To be refined - - -# 7. oneM2M requirements - -## 7.1. Introduction - -The current state of the art on the oneM2M architecture are described in oneM2M TS-0001 Functional Architecture [i.14]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new oneM2M requirements and the need to revise some existing ones. - -**TODO** To be refined - - -## 7.2 oneM2M new requirements - -### 7.2.1 Registration mechanism (**[deployment-option-oneM2M-01]**) - -The oneM2M platform (MN-CSE) may support ETSI GS MEC 033 [i.6] to register to MEC platform. -During the setup phase of the oneM2M platform, it registers to the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [i.6] clauses 5.3.4 IoT platform registration and 7.5.3.4 POST. -During the shutdown phase of the oneM2M platform, it deregisters from the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [i.6] clauses 5.3.6 IoT platform deregistration and 7.6.3.5 DELETE. -The data structure used for these operations is described in ETSI GS MEC 033 [i.6] clause 6.2.3 Type: IotPlatformInfo. - -**TODO** To be refined - -Editor's note: This clause is linked to the tasks T3.1 - - -### 7.2.2 Registration mechanism (**[deployment-option-oneM2M-03], [deployment-option-oneM2M-03]**) - -In order to act as a MEC application (MN-CSE, MN-AE) or a MEC service (MN-CSE), the oneM2M platform may support ETSI GS MEC 011 [i.4] application management and service management. - -**TODO** To be continued - -Editor's note: This clause is linked to the tasks T3.1, T3.2, T3.3 and T3.4 - - -### 7.2.3 ETSI C-ITS Support (**[deployment-option-oneM2M-04]**) - -The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. - -**TODO** - - -### 7.2.4 MEC Federated Learning Service API Support (**[deployment-option-oneM2M-05]**) - -The oneM2M platform may support MEC Federated learning Service API. - -**TODO** - - -### 7.2.5 MEC Swarm computing Service API Support (**[deployment-option-oneM2M-06]**) - -The oneM2M platform may support MEC Swarm computing Service API. - -**TODO** - - -### 7.2.6 Support of MQTT & CoAP over secured Websocket - -Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP cannot be used. The workaround is to use MQTT & CoAP over secured Websocket [i.z] - -**TODO** To be refined - - -## 7.3. Requirements to be enhanced or to be re-worked - -**TODO** - - -# 8 Conclusions & Actions - -## 8.1.1 ISG MEC New Work Items - -This clause provides a list of the NWI to propose to ETSI ISG MEC in order to initiate the standardisation work the features covered by this document. - -| Requirements | NWI proposal (summary) | Approved by STF | -| ------------ | ---------------------- | --------------- | -|**[mec-enhancement-021]**| | | -|**[mec-enhancement-040]**| | | -|**[FL-0X]**| | | -|**[SC-0X]**| | | - -**TODO** To be refined - - -Editor's note: This clause is linked to the tasks T3.1 and T3.5 - - -## 8.1.2 ETSI MEC Sandbox issues - -This clause provides a list of the issues to open in the ETSI MEC Sandbox [i.13] GITLAB to cover the requirements. - -| Requirements | GITLAB Issue (summary) | Approved by ESTIMED | -| -------------- | ---------------------- | ------------------- | -|**[IP-COMM-01]**| | | -|**[IP-COMM-03]**| | | -|**[IP-COMM-03]**| | | -|**[IP-SER-01]** | | | -|**[IP-SER-01]** | | | -|**[IP-SER-01]** | | | - - -**TODO** To be refined - - -Editor's note: This clause is linked to the tasks T3.1 and T3.5 - - -## 8.2. oneM2M - -Refer to oneM2M TR-0077 Specification [i.12]. - - -
- - -# Annex A:
Title of annex - - -
- - -# Annex B:
Title of annex -## B.1 First clause of the annex -## B.1.1 First subdivided clause of the annex - - -
- - -# Annex: Bibliography - - -
- - -# Annex : Change history - - -| Date | Version | Information about changes | -| --------------- | ------- | ----------------------------------------- | -| <Month year> | <#> | <Changes made are listed in this cell> | -| | | | -| | | | -| | | | - -
- - -# History - -| Version | Date | Milestone | -|---------------|---------------|-----------------| -|V0.0.1 | November 2025 |Early draft | -|---------------|---------------|-----------------| -| | | | -|---------------|---------------|-----------------| -| | | | -|---------------|---------------|-----------------| -- GitLab From 3792867a775f6421f5f2c3751d97d2dde25f487b Mon Sep 17 00:00:00 2001 From: Miguel Angel Reina Ortega Date: Wed, 22 Oct 2025 12:35:10 +0000 Subject: [PATCH 08/12] Some small enhancements --- GR_MEC-DEC_051.md | 62 ++++++++++++++++++++++++----------------------- 1 file changed, 32 insertions(+), 30 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index b705e57..1b56967 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -15,10 +15,8 @@ Short ISG Name: MEC # Contents -
- # Intellectual Property Rights Essential patents @@ -27,21 +25,25 @@ IPRs essential or potentially essential to normative deliverables may have been Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. - Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. -**DECT™**, **PLUGTESTS™**, **UMTS™** and the ETSI logo are trademarks of ETSI registered for the benefit of its Members. **3GPP™**, **LTE™** and **5G™** logo are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. **oneM2M™** logo is a trademark of ETSI registered for the benefit of its Members and of the oneM2M Partners. **GSM®** and the GSM logo are trademarks registered and owned by the GSM Association. +**DECT™**, **PLUGTESTS™**, **UMTS™** and the ETSI logo are trademarks of ETSI registered for the benefit of its Members. **3GPP™**, **LTE™** and **5G™** logo are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. **oneM2M™** logo is a trademark of ETSI registered for the benefit of its Members and of the oneM2M Partners. **GSM**® and the GSM logo are trademarks registered and owned by the GSM Association. # Foreword -This Group Report (GR) has been produced by ETSI Industry Specification Group <long ISGname> (<short ISGname>). +This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Multi-access Edge Computing (MEC). + + + + # Modal verbs terminology -In the present document "**should** ", "**should not** ", "**may** ", "**need not** ", "**will** ", "**will not** ", "**can** " and "**cannot** " are to be interpreted as described in clause 3.2 of the [ETSI Drafting Rules](https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-Rules) (Verbal forms for the expression of provisions). -"**must** " and "**must not** " are **NOT** allowed in ETSI deliverables except when used in direct citation. +In the present document \"**should**\", \"**should not**\", \"**may**\", \"**need not**\", \"**will**\", \"**will not**\", \"**can**\" and \"**cannot**\" are to be interpreted as described in clause 3.2 of the [ETSI Drafting Rules](https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-Rules) (Verbal forms for the expression of provisions). + +\"**must**\" and \"**must not**\" are **NOT** allowed in ETSI deliverables except when used in direct citation. # Executive summary @@ -55,9 +57,9 @@ In the present document "**should** ", "**should not** ", "**may** ", "**need no # 1 Scope -This document provides a set of missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DEC 050 [i.1]. +This document provides a set of missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). -This document provides also some requirement for the ETSI MEC Sandbox [i.13] to support the implementation and the deployment of the different use cases in each of the deployment options [i.1]. +This document provides also some requirement for the ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) to support the implementation and the deployment of the different use cases in each of the deployment options [\[i.1\]](#_ref_i.3). # 2 References @@ -67,27 +69,27 @@ Normative references are not applicable in the present document. ## 2.2 Informative references 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. -- [\[i.1\]](https://labs.etsi.org/rep/estimed/wp2/gr-mec-dec-050.git) ETSI GR MEC-DEC 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. -- [\[i.2\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/002/04.01.01_60/gs_MEC002v040101p.pdf) ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Use Cases and Requirements" -- [\[i.3\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture". -- [\[i.4\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) ETSI GS MEC 011: "Multi-access Edge Computing (MEC); Edge Platform Application Enablement". -- [\[i.5\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". -- [\[i.6\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". -- [\[i.7\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 040: "Multi-access Edge Computing (MEC); Federation enablement APIs". -- [\[i.8\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". -- [\[9\]](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GR MEC 059: "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". -- [\[i.10\]](https://docbox.etsi.org/ISG/MEC/70-Draft/0061v411AIML.in.MEC/MEC-0061v411AIML.in.MECv402.docx) ETSI GR MEC 061: "Multi-access Edge Computing (MEC); Artificial Intelligence / Machine Learning in MEC". -- [\[i.11\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". -- [\[i.12\]](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf) ETSI TS 118 123 V4.8.1 (2024-02): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". -- [\[i.12\]](https://labs.etsi.org/rep/estimed/wp3/tr-0077.git) oneM2M TR-0077 Specification: "". -- [\[i.13\]](https://labs.etsi.org/rep/mec/mec-sandbox-scenarios.git) The ETSI MEC Sandbox Scenarios. -- [\[i.14\]]() oneM2M TS-0001: "Functional Architecture". +- [i.1](https://labs.etsi.org/rep/estimed/wp2/gr-mec-dec-050.git) ETSI GR MEC-DEC 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. +- [i.2](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/002/04.01.01_60/gs_MEC002v040101p.pdf) ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Use Cases and Requirements" +- [i.3](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture". +- [i.4](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) ETSI GS MEC 011: "Multi-access Edge Computing (MEC); Edge Platform Application Enablement". +- [i.5](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". +- [i.6](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". +- [i.7](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 040: "Multi-access Edge Computing (MEC); Federation enablement APIs". +- [i.8](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". +- [i.9](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GR MEC 059: "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". +- [i.10](https://docbox.etsi.org/ISG/MEC/70-Draft/0061v411AIML.in.MEC/MEC-0061v411AIML.in.MECv402.docx) ETSI GR MEC 061: "Multi-access Edge Computing (MEC); Artificial Intelligence / Machine Learning in MEC". +- [i.11](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". +- [i.12](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf) ETSI TS 118 123 V4.8.1 (2024-02): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". +- [i.13](https://labs.etsi.org/rep/estimed/wp3/tr-0077.git) oneM2M TR-0077 Specification: "". +- [i.14](https://labs.etsi.org/rep/mec/mec-sandbox-scenarios.git) The ETSI MEC Sandbox Scenarios. +- [i.15]() oneM2M TS-0001: "Functional Architecture". -- [\[i.x\]](https://www.etsi.org/deliver/etsi_ts/103900_103999/103900/02.02.01_60/ts_103900v020201p.pdf) ETSI TS 103 900 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Cooperative Awareness Service; Release 2". -- [\[i.x\]](https://www.etsi.org/deliver/etsi_ts/103800_103899/103831/02.02.01_60/ts_103831v020201p.pdf) ETSI TS 103 831 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service; Release 2". +- [i.x](https://www.etsi.org/deliver/etsi_ts/103900_103999/103900/02.02.01_60/ts_103900v020201p.pdf) ETSI TS 103 900 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Cooperative Awareness Service; Release 2". +- [i.y](https://www.etsi.org/deliver/etsi_ts/103800_103899/103831/02.02.01_60/ts_103831v020201p.pdf) ETSI TS 103 831 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service; Release 2". -- [\[i.z\]](https://datatracker.ietf.org/doc/html/rfc6455) RFC6455: "The WebSocket Protocol". +- [i.z](https://datatracker.ietf.org/doc/html/rfc6455) RFC6455: "The WebSocket Protocol". # 3 Definition of terms, symbols and abbreviations @@ -159,7 +161,7 @@ For the purposes of the present document, the [following] abbreviations [given i ## 4.1 Deployment options -The document ETSI GR MEC-DEC 050 [i.1], clause 6.4.1 introduces 4 different deployment options : +The document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1), clause 6.4.1 introduces 4 different deployment options : - Option A: The oneM2M CSE platforms are deployed on the cloud; - Option B: The oneM2M CSE platforms are at the network edge but the oneM2M platforms and the MEC System are deployed on a separate node; - Option C: The oneM2M CSE platforms and the MEC System are deployed on the same node; @@ -197,7 +199,7 @@ The table below shows the requirements involved by each of the 4 deployment opti ## 5.1 Introduction -The document ETSI GR MEC-DEC 050 [i.1], clause 5 introduces several a basic set of use cases focused on on how the integration of the ETSI MEC and oneM2M frameworks enables next-generation Edge-IoT solutions. +The document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1), clause 5 introduces several a basic set of use cases focused on on how the integration of the ETSI MEC and oneM2M frameworks enables next-generation Edge-IoT solutions. The domain covered are: ### Table 5.1-1: Domains covered @@ -230,7 +232,7 @@ The domain covered are: ## 5.2 The Edge & IoT use cases -The evolution towards the joint MEC-oneM2M standardized architecture to support both the deployment options and the Edge & IoT use cases was proposed in clause 7 of the document ETSI GR MEC-DEC 050 [i.1]. +The evolution towards the joint MEC-oneM2M standardized architecture to support both the deployment options and the Edge & IoT use cases was proposed in clause 7 of the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). ### Table 5.2-1 – Deployments options and platform requirements -- GitLab From df46b8b9a29209d79fbc3e9aab55401499f30a18 Mon Sep 17 00:00:00 2001 From: garciay Date: Thu, 23 Oct 2025 15:32:29 +0200 Subject: [PATCH 09/12] Report feedback from STF 685 WP3#4 meeting --- GR_MEC-DEC_051.md | 118 +++++++++++++++++++++++----------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index 1b56967..faf9f09 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -1,7 +1,7 @@ --- -Title: Multi-access Edge Computing (MEC); ESTIMED Use Cases & Recommendations +Title: Multi-access Edge Computing (MEC); oneM2M and MEC interworking and deployments Spec Number: MEC-DEC 051 Version: v0.0.1 Date: 2025-11 @@ -377,60 +377,6 @@ Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The Editor's note: This clause is linked to the tasks T3.2 & T3.3 -## 6.4 ETSI MEC Sandbox requirements - -### 6.4.1 MEC Interworking with oneM2M requirement (**[IPE-XXX-0X]**) - -The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [i.11]. -The MEC Interworking with oneM2M follows these three steps [i.11]: -1. Interworking on the connection layer -2. Interworking on the resource framework layer -3. Interworking on the information model layer - -### 6.4.1.1 MEC Interworking architecture - -The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture [i.2], the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.6] and ETSI GS MEC 046 [i.8]. - -The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [i.3] describes the procedure to achieve this registration. - -Editor's note: This clause is linked to the task T3.1 - - -### 6.4.1.2 MEC Interworking on the connection layer - -Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [i.11], the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is supported. -By the end of the STF 685 project, the MEC Interworking with oneM2M will provide support of CoAP over Secured Websocket. - -**[IPE-COMM-01]** The MEC Interworking supports HTTP/HTTPS. - -**[IPE-COMM-02]** The MEC Interworking supports MQTT over secured Websocket. - -**[IPE-COMM-03]** The MEC Interworking supports CoAP over secured Websocket. - -**TODO** To be refined - - -### 6.4.1.3 MEC Interworking on the resource framework layer - -Currently, only JSON serialization mechanism is natively supported, by the end of the STF 685 project, the MEC Interworking with oneM2M will provide compliancy to oneM2M-defined the resource framework layer such as the ones defined in ETSI TS 118 123 [i.12]. - -**[IPE-SER-01]** The MEC Interworking supports XML serialization. - -**[IPE-SER-02]** The MEC Interworking supports JSON serialization. - -**[IPE-SER-03]** The MEC Interworking supports CBOR serialization. - -**TODO** To be refined - - -### 6.4.1.4 MEC Interworking on the information model layer - -Mainly, MEC Interworking on the information model layer provides the harmonization of the informatioon model for both oneM2M with and MEC platform. -For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models as defined in ETSI TS 118 123 [i.12]. - -**TODO** To be refined - - # 7. oneM2M requirements ## 7.1. Introduction @@ -496,9 +442,63 @@ Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP **TODO** -# 8 Conclusions & Actions +# 8 ETSI MEC Sandbox requirements + +## 8.1 MEC Interworking with oneM2M requirement (**[IPE-XXX-0X]**) + +The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [i.11]. +The MEC Interworking with oneM2M follows these three steps [i.11]: +1. Interworking on the connection layer +2. Interworking on the resource framework layer +3. Interworking on the information model layer + +### 8.1.1 MEC Interworking architecture + +The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture [i.2], the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.6] and ETSI GS MEC 046 [i.8]. + +The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [i.3] describes the procedure to achieve this registration. + +Editor's note: This clause is linked to the task T3.1 + + +### 8.1.2 MEC Interworking on the connection layer + +Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [i.11], the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is supported. +By the end of the STF 685 project, the MEC Interworking with oneM2M will provide support of CoAP over Secured Websocket. + +**[IPE-COMM-01]** The MEC Interworking supports HTTP/HTTPS. + +**[IPE-COMM-02]** The MEC Interworking supports MQTT over secured Websocket. + +**[IPE-COMM-03]** The MEC Interworking supports CoAP over secured Websocket. + +**TODO** To be refined + + +### 8.1.3 MEC Interworking on the resource framework layer + +Currently, only JSON serialization mechanism is natively supported, by the end of the STF 685 project, the MEC Interworking with oneM2M will provide compliancy to oneM2M-defined the resource framework layer such as the ones defined in ETSI TS 118 123 [i.12]. + +**[IPE-SER-01]** The MEC Interworking supports XML serialization. + +**[IPE-SER-02]** The MEC Interworking supports JSON serialization. + +**[IPE-SER-03]** The MEC Interworking supports CBOR serialization. + +**TODO** To be refined + + +### 8.1.4 MEC Interworking on the information model layer + +Mainly, MEC Interworking on the information model layer provides the harmonization of the informatioon model for both oneM2M with and MEC platform. +For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models as defined in ETSI TS 118 123 [i.12]. + +**TODO** To be refined + + +# 9 Conclusions & Actions -## 8.1.1 ISG MEC New Work Items +## 9.1.1 ISG MEC New Work Items This clause provides a list of the NWI to propose to ETSI ISG MEC in order to initiate the standardisation work the features covered by this document. @@ -515,7 +515,7 @@ This clause provides a list of the NWI to propose to ETSI ISG MEC in order to in Editor's note: This clause is linked to the tasks T3.1 and T3.5 -## 8.1.2 ETSI MEC Sandbox issues +## 9.1.2 ETSI MEC Sandbox issues This clause provides a list of the issues to open in the ETSI MEC Sandbox [i.13] GITLAB to cover the requirements. @@ -535,7 +535,7 @@ This clause provides a list of the issues to open in the ETSI MEC Sandbox [i.13] Editor's note: This clause is linked to the tasks T3.1 and T3.5 -## 8.2. oneM2M +## 9.2. oneM2M Refer to oneM2M TR-0077 Specification [i.12]. -- GitLab From 46a66f96ecb2ce8d489bef2b0898467b4bb4f85e Mon Sep 17 00:00:00 2001 From: garciay Date: Fri, 24 Oct 2025 13:39:30 +0200 Subject: [PATCH 10/12] Remove requirement wording; Review Scope clause --- GR_MEC-DEC_051.md | 52 +++++++++++++++++++++++------------------------ 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index faf9f09..00be4e0 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -57,9 +57,9 @@ In the present document \"**should**\", \"**should not**\", \"**may**\", \"**nee # 1 Scope -This document provides a set of missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms. This list is based on the use cases and requirements identified in the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). +This document identifies a set of missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms, and based on that provides recommendations. This list is based on the use cases and recommendations identified in the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). -This document provides also some requirement for the ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) to support the implementation and the deployment of the different use cases in each of the deployment options [\[i.1\]](#_ref_i.3). +This document also provides some recommendations for the ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) to support the implementation and the deployment of the different use cases in each of the deployment options [\[i.1\]](#_ref_i.3). # 2 References @@ -167,13 +167,13 @@ The document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1), clause 6.4.1 introduces 4 - Option C: The oneM2M CSE platforms and the MEC System are deployed on the same node; - Option D: The oneM2M CSE platforms are deployed as part of the MEC System. -## 4.2 Platform Requirements based on the deployment options +## 4.2 Platform recommendations based on the deployment options -The table below shows the requirements involved by each of the 4 deployment options for each platform. +The table below shows the recommendations involved by each of the 4 deployment options for each platform. -### Table 4.2-1 – Deployments options and platform requirements +### Table 4.2-1 – Deployments options and platform recommendations -| Deployment options | Requirements for MEC | Requirements for oneM2M | +| Deployment options | recommendations for MEC | recommendations for oneM2M | | ------------------ | -------------------- | ----------------------------- | | Option A | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | | Option B | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | @@ -190,7 +190,7 @@ The table below shows the requirements involved by each of the 4 deployment opti **[deployment-option-oneM2M-03]** The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.13 and 5.2.3. -**Note:** Requirements and enhancements are detailled in clause 6. +**Note:** Recommendations and enhancements are detailled in clause 6. **TODO** To be refined @@ -234,9 +234,9 @@ The domain covered are: The evolution towards the joint MEC-oneM2M standardized architecture to support both the deployment options and the Edge & IoT use cases was proposed in clause 7 of the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). -### Table 5.2-1 – Deployments options and platform requirements +### Table 5.2-1 – Deployments options and platform recommendations -| Use cases | Requirements for MEC | Requirements for oneM2M | +| Use cases | Recommendations for MEC | Recommendations for oneM2M | | ------------------------------------------------ | -------------------------- | ----------------------------- | | Autonomous Vehicles and Edge Continuum | **[IPE-XXX-0X]** **[mec-enhancement-021]** **[mec-enhancement-040]** **[Location-0X]** **[V2X-0X]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-04]** | | Vulnerable Road User Detection | **[IPE-XXX-0X]** **[mec-enhancement-021]** **[mec-enhancement-040]** **[Location-0X]** **[V2X-0X]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-04]** | @@ -265,9 +265,9 @@ The evolution towards the joint MEC-oneM2M standardized architecture to support **[deployment-option-oneM2M-06]** The oneM2M platform may support MEC Swarm computing Service API. -**Note:** The proposed requirements and the proposed enhancements are detailled in clause 6 for the MEC platform and clause 7 for the oneM2M platform. +**Note:** The proposed recommendations and the proposed enhancements are detailled in clause 6 for the MEC platform and clause 7 for the oneM2M platform. -The following requirements are lready described in the ETSI GS MEC 002: +The following recommendations are lready described in the ETSI GS MEC 002: **[Location-0X]** Feature LocationService [i.2 clause 6.3.4 Feature LocationService] @@ -278,13 +278,13 @@ The following requirements are lready described in the ETSI GS MEC 002: **TODO** To be refined -# 6 ETSI MEC platform requirements +# 6 ETSI MEC platform recommendations ## 6.1 Introduction The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [i.3]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new MEC services and the need to revise some existing MEC services. -## 6.2 Missing requirements +## 6.2 Missing recommendations ### 6.2.1 Federated Learning requirement (**[FL-0X]**) @@ -317,7 +317,7 @@ Federated Learning is a distributed machine learning approach in which model tra ### 6.2.2 Swarm computing requirement (**[SC-0X]**) -Swarm Computing refers to the coordination of multiple MEC/oneM2M instances to perform distributed computing tasks, leveraging the capabilities of edge devices and networks. In this paradigm, individual MEC/oneM2M nodes act like members of a swarm, each contributing processing power, storage, connectivity, or sensing capabilities to achieve collective goal. The system operates in a decentralized and adaptive manner, where tasks can be dynamically partitioned, distributed, and recombined across nodes depending on resource availability, network conditions, and application requirements. +Swarm Computing refers to the coordination of multiple MEC/oneM2M instances to perform distributed computing tasks, leveraging the capabilities of edge devices and networks. In this paradigm, individual MEC/oneM2M nodes act like members of a swarm, each contributing processing power, storage, connectivity, or sensing capabilities to achieve collective goal. The system operates in a decentralized and adaptive manner, where tasks can be dynamically partitioned, distributed, and recombined across nodes depending on resource availability, network conditions, and application recommendations. MEC Swarm Computing Service Features @@ -341,15 +341,15 @@ MEC Swarm Computing Service Features **[SC-09]** The SCService supports operator policies determining participation, prioritization, and resource allocation for swarm tasks. -**[SC-10]** The SCService facilitates secure code and data distribution across swarm nodes, supporting confidentiality, integrity, and compliance requirements for collaborative tasks. +**[SC-10]** The SCService facilitates secure code and data distribution across swarm nodes, supporting confidentiality, integrity, and compliance recommendations for collaborative tasks. **TODO** To be refined Editor's note: This clause is linked to the task T3.4 -## 6.3 Requirements to be enhanced +## 6.3 Recommendations to be enhanced -The clauses below described the existing requirements in the ETSI MEC architecture that require some enhancements or to be re-worked. +The clauses below described the existing recommendations in the ETSI MEC architecture that require some enhancements or to be re-worked. ### 6.3.1 ETSI GS MEC 033 enhancement (**[mec-enhancement-033]**) @@ -370,23 +370,23 @@ The ETSI GS MEC 033 [i.6] introduces a registration mechanism for an IoT platfor ### 6.3.3 ETSI GS MEC 021 enhancement (**[mec-enhancement-021]**) -Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the requirements required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. +Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the recommendations required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. **TODO** To be continued Editor's note: This clause is linked to the tasks T3.2 & T3.3 -# 7. oneM2M requirements +# 7. oneM2M recommendations ## 7.1. Introduction -The current state of the art on the oneM2M architecture are described in oneM2M TS-0001 Functional Architecture [i.14]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new oneM2M requirements and the need to revise some existing ones. +The current state of the art on the oneM2M architecture are described in oneM2M TS-0001 Functional Architecture [i.14]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new oneM2M recommendations and the need to revise some existing ones. **TODO** To be refined -## 7.2 oneM2M new requirements +## 7.2 oneM2M new recommendations ### 7.2.1 Registration mechanism (**[deployment-option-oneM2M-01]**) @@ -437,12 +437,12 @@ Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP **TODO** To be refined -## 7.3. Requirements to be enhanced or to be re-worked +## 7.3. Recommendations to be enhanced or to be re-worked **TODO** -# 8 ETSI MEC Sandbox requirements +# 8 ETSI MEC Sandbox recommendations ## 8.1 MEC Interworking with oneM2M requirement (**[IPE-XXX-0X]**) @@ -502,7 +502,7 @@ For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M This clause provides a list of the NWI to propose to ETSI ISG MEC in order to initiate the standardisation work the features covered by this document. -| Requirements | NWI proposal (summary) | Approved by STF | +| Recommendations | NWI proposal (summary) | Approved by STF | | ------------ | ---------------------- | --------------- | |**[mec-enhancement-021]**| | | |**[mec-enhancement-040]**| | | @@ -517,9 +517,9 @@ This clause provides a list of the NWI to propose to ETSI ISG MEC in order to in ## 9.1.2 ETSI MEC Sandbox issues -This clause provides a list of the issues to open in the ETSI MEC Sandbox [i.13] GITLAB to cover the requirements. +This clause provides a list of the issues to open in the ETSI MEC Sandbox [i.13] GITLAB to cover the recommendations. -| Requirements | GITLAB Issue (summary) | Approved by ESTIMED | +| Recommendations | GITLAB Issue (summary) | Approved by ESTIMED | | -------------- | ---------------------- | ------------------- | |**[IP-COMM-01]**| | | |**[IP-COMM-03]**| | | -- GitLab From 6ab11be6b3da05ebe61975c28eaea5b51ea9803c Mon Sep 17 00:00:00 2001 From: Miguel Angel Reina Ortega Date: Wed, 10 Dec 2025 03:49:33 +0100 Subject: [PATCH 11/12] Some editorials --- GR_MEC-DEC_051.md | 129 ++++++++++++++++++++-------------------------- 1 file changed, 57 insertions(+), 72 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index 00be4e0..136562a 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -1,5 +1,3 @@ - - --- Title: Multi-access Edge Computing (MEC); oneM2M and MEC interworking and deployments Spec Number: MEC-DEC 051 @@ -13,10 +11,6 @@ Long ISG Name: Multi-access Edge Computing Short ISG Name: MEC --- -# Contents - -
- # Intellectual Property Rights Essential patents @@ -46,20 +40,12 @@ In the present document \"**should**\", \"**should not**\", \"**may**\", \"**nee \"**must**\" and \"**must not**\" are **NOT** allowed in ETSI deliverables except when used in direct citation. -# Executive summary - - - -# Introduction - - -
- # 1 Scope + This document identifies a set of missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms, and based on that provides recommendations. This list is based on the use cases and recommendations identified in the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). -This document also provides some recommendations for the ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) to support the implementation and the deployment of the different use cases in each of the deployment options [\[i.1\]](#_ref_i.3). +This document also provides some recommendations for the ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) to support the implementation and the deployment of the different use cases in each of the deployment options [\[i.3\]](#_ref_i.3). # 2 References @@ -69,27 +55,24 @@ Normative references are not applicable in the present document. ## 2.2 Informative references 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. -- [i.1](https://labs.etsi.org/rep/estimed/wp2/gr-mec-dec-050.git) ETSI GR MEC-DEC 050 V1.0.0: "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. -- [i.2](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/002/04.01.01_60/gs_MEC002v040101p.pdf) ETSI GS MEC 002: "Multi-access Edge Computing (MEC); Use Cases and Requirements" -- [i.3](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf) ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture". -- [i.4](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf) ETSI GS MEC 011: "Multi-access Edge Computing (MEC); Edge Platform Application Enablement". -- [i.5](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf) ETSI GS MEC 021: "Multi-access Edge Computing (MEC); Application Mobility Service API". -- [i.6](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf) ETSI GS MEC 033: "Multi-access Edge Computing (MEC); IoT API". -- [i.7](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GS MEC 040: "Multi-access Edge Computing (MEC); Federation enablement APIs". -- [i.8](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf) ETSI GS MEC 046: "Multi-access Edge Computing (MEC); Sensor-sharing API". -- [i.9](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf) ETSI GR MEC 059: "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". -- [i.10](https://docbox.etsi.org/ISG/MEC/70-Draft/0061v411AIML.in.MEC/MEC-0061v411AIML.in.MECv402.docx) ETSI GR MEC 061: "Multi-access Edge Computing (MEC); Artificial Intelligence / Machine Learning in MEC". -- [i.11](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf) ETSI TS 118 133 V4.0.1: "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". -- [i.12](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf) ETSI TS 118 123 V4.8.1 (2024-02): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". -- [i.13](https://labs.etsi.org/rep/estimed/wp3/tr-0077.git) oneM2M TR-0077 Specification: "". -- [i.14](https://labs.etsi.org/rep/mec/mec-sandbox-scenarios.git) The ETSI MEC Sandbox Scenarios. -- [i.15]() oneM2M TS-0001: "Functional Architecture". - - -- [i.x](https://www.etsi.org/deliver/etsi_ts/103900_103999/103900/02.02.01_60/ts_103900v020201p.pdf) ETSI TS 103 900 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Cooperative Awareness Service; Release 2". -- [i.y](https://www.etsi.org/deliver/etsi_ts/103800_103899/103831/02.02.01_60/ts_103831v020201p.pdf) ETSI TS 103 831 V2.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service; Release 2". - -- [i.z](https://datatracker.ietf.org/doc/html/rfc6455) RFC6455: "The WebSocket Protocol". +[i.1] [ETSI GR MEC-DEC 050 V1.0.0](https://labs.etsi.org/rep/estimed/wp2/gr-mec-dec-050.git): "Multi-access Edge Computing (MEC); ESTIMED Use Cases & Proposed Recommendations. +[i.2] [ETSI GS MEC 002](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/002/04.01.01_60/gs_MEC002v040101p.pdf): "Multi-access Edge Computing (MEC); Use Cases and Requirements" +[i.3] [ETSI GS MEC 003](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/04.01.01_60/gs_mec003v040101p.pdf): "Multi-access Edge Computing (MEC); Framework and Reference Architecture". +[i.4] [ETSI GS MEC 011](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/04.01.01_60/gs_MEC011v040101p.pdf): "Multi-access Edge Computing (MEC); Edge Platform Application Enablement". +[i.5] [ETSI GS MEC 021](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/03.01.01_60/gs_MEC021v030101p.pdf): "Multi-access Edge Computing (MEC); Application Mobility Service API". +[i.6] [ETSI GS MEC 033](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/033/03.01.01_60/gs_MEC033v030101p.pdf): "Multi-access Edge Computing (MEC); IoT API". +[i.7] [ETSI GS MEC 040](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf): "Multi-access Edge Computing (MEC); Federation enablement APIs". +[i.8] [ETSI GS MEC 046](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/046/03.02.01_60/gs_MEC046v030201p.pdf): "Multi-access Edge Computing (MEC); Sensor-sharing API". +[i.9] [ETSI GR MEC 059](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.03.01_60/gs_MEC040v030301p.pdf): "Multi-access Edge Computing (MEC); Exploit Edge Computings Resources". +[i.10] [ETSI GR MEC 061](https://docbox.etsi.org/ISG/MEC/70-Draft/0061v411AIML.in.MEC/MEC-0061v411AIML.in.MECv402.docx): "Multi-access Edge Computing (MEC); Artificial Intelligence / Machine Learning in MEC". +[i.11] [ETSI TS 118 133 V4.0.1](https://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf): "Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)". +[i.12] [ETSI TS 118 123 V4.8.1 (2024-02)](https://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf): "oneM2M; SDT based Information Model and Mapping for Vertical Industries (oneM2M TS-0023 version 4.8.1 Release 4)". +[i.13] [oneM2M TR-0077 Specification](https://labs.etsi.org/rep/estimed/wp3/tr-0077.git): "". +[i.14] [The ETSI MEC Sandbox Scenarios](https://labs.etsi.org/rep/mec/mec-sandbox-scenarios.git). +[i.15] [oneM2M TS-0001](): "Functional Architecture". +[i.16] [ETSI TS 103 900 V2.2.1](https://www.etsi.org/deliver/etsi_ts/103900_103999/103900/02.02.01_60/ts_103900v020201p.pdf): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Cooperative Awareness Service; Release 2". +[i.17] [ETSI TS 103 831 V2.2.1](https://www.etsi.org/deliver/etsi_ts/103800_103899/103831/02.02.01_60/ts_103831v020201p.pdf): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service; Release 2". +[i.18] [RFC6455](https://datatracker.ietf.org/doc/html/rfc6455): "The WebSocket Protocol". # 3 Definition of terms, symbols and abbreviations @@ -171,7 +154,7 @@ The document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1), clause 6.4.1 introduces 4 The table below shows the recommendations involved by each of the 4 deployment options for each platform. -### Table 4.2-1 – Deployments options and platform recommendations +**Table 4.2-1: Deployments options and platform recommendations** | Deployment options | recommendations for MEC | recommendations for oneM2M | | ------------------ | -------------------- | ----------------------------- | @@ -190,7 +173,7 @@ The table below shows the recommendations involved by each of the 4 deployment o **[deployment-option-oneM2M-03]** The oneM2M platform may support MEC application registration as described in ETSI GS MEC 011 clause 5.2.13 and 5.2.3. -**Note:** Recommendations and enhancements are detailled in clause 6. +> NOTE: Recommendations and enhancements are detailled in clause 6. **TODO** To be refined @@ -202,7 +185,7 @@ The table below shows the recommendations involved by each of the 4 deployment o The document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1), clause 5 introduces several a basic set of use cases focused on on how the integration of the ETSI MEC and oneM2M frameworks enables next-generation Edge-IoT solutions. The domain covered are: -### Table 5.1-1: Domains covered +**Table 5.1-1: Domains covered** +-----------------------+--------------------------------------------+-----------------------------------------+ | Domain | Use Cases | Focus | @@ -234,7 +217,7 @@ The domain covered are: The evolution towards the joint MEC-oneM2M standardized architecture to support both the deployment options and the Edge & IoT use cases was proposed in clause 7 of the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). -### Table 5.2-1 – Deployments options and platform recommendations +**Table 5.2-1: Deployments options and platform recommendations** | Use cases | Recommendations for MEC | Recommendations for oneM2M | | ------------------------------------------------ | -------------------------- | ----------------------------- | @@ -251,29 +234,29 @@ The evolution towards the joint MEC-oneM2M standardized architecture to support **[IPE-XXX-0X]** The MEC interworking with oneM2M platform. -**[mec-enhancement-021]** The MEC platform Mobility Service API [i.5] may be revised to fit use case requirement. +**[mec-enhancement-021]** The MEC platform Mobility Service API [\[i.5\]](#_ref_i.5)may be revised to fit use case requirement. -**[mec-enhancement-040]** The MEC platform Federation [i.7] may be revised to fit use case requirement. +**[mec-enhancement-040]** The MEC platform Federation [\[i.7\]](#_ref_i.7)may be revised to fit use case requirement. **[FL-0X]** The MEC platform may support a MEC service that support Federated learning features. **[SC-0X]** The MEC platform may support a MEC service that support swarm computing features. -**[deployment-option-oneM2M-04]** The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. +**[deployment-option-oneM2M-04]** The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [\[i.16\]](#_ref_i.16) or DEN messages [\[i.17\]](#_ref_i.17). **[deployment-option-oneM2M-05]** The oneM2M platform may support MEC Federated learning Service API. **[deployment-option-oneM2M-06]** The oneM2M platform may support MEC Swarm computing Service API. -**Note:** The proposed recommendations and the proposed enhancements are detailled in clause 6 for the MEC platform and clause 7 for the oneM2M platform. +> NOTE: The proposed recommendations and the proposed enhancements are detailled in clause 6 for the MEC platform and clause 7 for the oneM2M platform. The following recommendations are lready described in the ETSI GS MEC 002: -**[Location-0X]** Feature LocationService [i.2 clause 6.3.4 Feature LocationService] +**[Location-0X]** Feature LocationService [\[i.2\]](#_ref_i.2) clause 6.3.4 Feature LocationService -**[V2X-0X]** Feature V2XService [i.2 clause 6.3.8 Feature V2XService] +**[V2X-0X]** Feature V2XService [\[i.2\]](#_ref_i.2) clause 6.3.8 Feature V2XService -**[CustomerPremiseEdge-0X]** Feature CustomerPremiseEdge [i.2 clause 6.3.11 Feature CustomerPremiseEdge] +**[CustomerPremiseEdge-0X]** Feature CustomerPremiseEdge [\[i.2\]](#_ref_i.2) clause 6.3.11 Feature CustomerPremiseEdge **TODO** To be refined @@ -282,7 +265,7 @@ The following recommendations are lready described in the ETSI GS MEC 002: ## 6.1 Introduction -The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [i.3]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new MEC services and the need to revise some existing MEC services. +The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [\[i.3\]](#_ref_i.3). The ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1)highlights the need of new MEC services and the need to revise some existing MEC services. ## 6.2 Missing recommendations @@ -310,7 +293,7 @@ Federated Learning is a distributed machine learning approach in which model tra **TODO** To be refined -Editor's note: The ETSI MEC Sandbox [i.13] can use Flower framework for the federated learning +Editor's note: The ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) can use Flower framework for the federated learning Editor's note: This clause is linked to the task T3.4 @@ -354,7 +337,7 @@ The clauses below described the existing recommendations in the ETSI MEC archite ### 6.3.1 ETSI GS MEC 033 enhancement (**[mec-enhancement-033]**) To work together, both the oneM2M platform and the MEC platform need to know each others. -The ETSI GS MEC 033 [i.6] introduces a registration mechanism for an IoT platform to register to the MEC platform. +The ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)introduces a registration mechanism for an IoT platform to register to the MEC platform. **TODO** @@ -370,7 +353,7 @@ The ETSI GS MEC 033 [i.6] introduces a registration mechanism for an IoT platfor ### 6.3.3 ETSI GS MEC 021 enhancement (**[mec-enhancement-021]**) -Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The use cases and the recommendations required in ETSI GR MEC-DEC 050 [i.1] implies to review and enhance it. +Currently, ETSI GS MEC 021 [\[i.7\]](#_ref_i.7)provides features about Mobility services. The use cases and the recommendations required in ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1)implies to review and enhance it. **TODO** To be continued @@ -381,7 +364,7 @@ Currently, ETSI GS MEC 021 [i.7] provides features about Mobility services. The ## 7.1. Introduction -The current state of the art on the oneM2M architecture are described in oneM2M TS-0001 Functional Architecture [i.14]. The ETSI GR MEC-DEC 050 [i.1] highlights the need of new oneM2M recommendations and the need to revise some existing ones. +The current state of the art on the oneM2M architecture are described in oneM2M TS-0001 Functional Architecture [\[i.14\]](#_ref_i.14). The ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1)highlights the need of new oneM2M recommendations and the need to revise some existing ones. **TODO** To be refined @@ -390,10 +373,10 @@ The current state of the art on the oneM2M architecture are described in oneM2M ### 7.2.1 Registration mechanism (**[deployment-option-oneM2M-01]**) -The oneM2M platform (MN-CSE) may support ETSI GS MEC 033 [i.6] to register to MEC platform. -During the setup phase of the oneM2M platform, it registers to the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [i.6] clauses 5.3.4 IoT platform registration and 7.5.3.4 POST. -During the shutdown phase of the oneM2M platform, it deregisters from the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [i.6] clauses 5.3.6 IoT platform deregistration and 7.6.3.5 DELETE. -The data structure used for these operations is described in ETSI GS MEC 033 [i.6] clause 6.2.3 Type: IotPlatformInfo. +The oneM2M platform (MN-CSE) may support ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)to register to MEC platform. +During the setup phase of the oneM2M platform, it registers to the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)clauses 5.3.4 IoT platform registration and 7.5.3.4 POST. +During the shutdown phase of the oneM2M platform, it deregisters from the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)clauses 5.3.6 IoT platform deregistration and 7.6.3.5 DELETE. +The data structure used for these operations is described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)clause 6.2.3 Type: IotPlatformInfo. **TODO** To be refined @@ -402,7 +385,7 @@ The data structure used for these operations is described in ETSI GS MEC 033 [i. ### 7.2.2 Registration mechanism (**[deployment-option-oneM2M-03], [deployment-option-oneM2M-03]**) -In order to act as a MEC application (MN-CSE, MN-AE) or a MEC service (MN-CSE), the oneM2M platform may support ETSI GS MEC 011 [i.4] application management and service management. +In order to act as a MEC application (MN-CSE, MN-AE) or a MEC service (MN-CSE), the oneM2M platform may support ETSI GS MEC 011 [\[i.4\]](#_ref_i.4)application management and service management. **TODO** To be continued @@ -411,7 +394,7 @@ In order to act as a MEC application (MN-CSE, MN-AE) or a MEC service (MN-CSE), ### 7.2.3 ETSI C-ITS Support (**[deployment-option-oneM2M-04]**) -The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [i.x] or DEN messages [i.y]. +The oneM2M platform may support ETSI GS MEC 030 V2X Information API to have access to the ETSI ITS messages such as CA messages [\[i.16\]](#_ref_i.16) or DEN messages [\[i.17\]](#_ref_i.17). **TODO** @@ -432,7 +415,7 @@ The oneM2M platform may support MEC Swarm computing Service API. ### 7.2.6 Support of MQTT & CoAP over secured Websocket -Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP cannot be used. The workaround is to use MQTT & CoAP over secured Websocket [i.z] +Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP cannot be used. The workaround is to use MQTT & CoAP over secured Websocket [\[i.18\]](#_ref_i.18) **TODO** To be refined @@ -446,24 +429,24 @@ Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP ## 8.1 MEC Interworking with oneM2M requirement (**[IPE-XXX-0X]**) -The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [i.11]. -The MEC Interworking with oneM2M follows these three steps [i.11]: +The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [\[i.11\]](#_ref_i.11). +The MEC Interworking with oneM2M follows these three steps [\[i.11\]](#_ref_i.11): 1. Interworking on the connection layer 2. Interworking on the resource framework layer 3. Interworking on the information model layer ### 8.1.1 MEC Interworking architecture -The MEC Interworking with oneM2M architecture is derived from [i.11] clause 6.2.1. From the ETSI MEC architecture [i.2], the MEC Interworking with oneM2M is part of the MEC Platform [i.3] clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [i.6] and ETSI GS MEC 046 [i.8]. +The MEC Interworking with oneM2M architecture is derived from [\[i.11\]](#_ref_i.11) clause 6.2.1. From the ETSI MEC architecture [i.2], the MEC Interworking with oneM2M is part of the MEC Platform [\[i.3\]](#_ref_i.3)clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)and ETSI GS MEC 046 [\[i.8\]](#_ref_i.8). -The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [i.3] describes the procedure to achieve this registration. +The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [\[i.3\]](#_ref_i.3)describes the procedure to achieve this registration. Editor's note: This clause is linked to the task T3.1 ### 8.1.2 MEC Interworking on the connection layer -Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [i.11], the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is supported. +Based on Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) [\[i.11\]](#_ref_i.11), the MEC Interworking with oneM2M supports bindings defined by oneM2M, except for MQTT, where only MQTT over Secured Websocket is supported. By the end of the STF 685 project, the MEC Interworking with oneM2M will provide support of CoAP over Secured Websocket. **[IPE-COMM-01]** The MEC Interworking supports HTTP/HTTPS. @@ -477,7 +460,7 @@ By the end of the STF 685 project, the MEC Interworking with oneM2M will provide ### 8.1.3 MEC Interworking on the resource framework layer -Currently, only JSON serialization mechanism is natively supported, by the end of the STF 685 project, the MEC Interworking with oneM2M will provide compliancy to oneM2M-defined the resource framework layer such as the ones defined in ETSI TS 118 123 [i.12]. +Currently, only JSON serialization mechanism is natively supported, by the end of the STF 685 project, the MEC Interworking with oneM2M will provide compliancy to oneM2M-defined the resource framework layer such as the ones defined in ETSI TS 118 123 [\[i.12\]](#_ref_i.12). **[IPE-SER-01]** The MEC Interworking supports XML serialization. @@ -491,7 +474,7 @@ Currently, only JSON serialization mechanism is natively supported, by the end o ### 8.1.4 MEC Interworking on the information model layer Mainly, MEC Interworking on the information model layer provides the harmonization of the informatioon model for both oneM2M with and MEC platform. -For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models as defined in ETSI TS 118 123 [i.12]. +For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models as defined in ETSI TS 118 123 [\[i.12\]](#_ref_i.12). **TODO** To be refined @@ -502,6 +485,8 @@ For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M This clause provides a list of the NWI to propose to ETSI ISG MEC in order to initiate the standardisation work the features covered by this document. +**Table 9.1.1-1: New Work Items for ETSI ISG MEC** + | Recommendations | NWI proposal (summary) | Approved by STF | | ------------ | ---------------------- | --------------- | |**[mec-enhancement-021]**| | | @@ -517,7 +502,9 @@ This clause provides a list of the NWI to propose to ETSI ISG MEC in order to in ## 9.1.2 ETSI MEC Sandbox issues -This clause provides a list of the issues to open in the ETSI MEC Sandbox [i.13] GITLAB to cover the recommendations. +This clause provides a list of the issues to open in the ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) GITLAB to cover the recommendations. + +**Table 9.1.2-1: Open issues for ETSI MEC Sandbox** | Recommendations | GITLAB Issue (summary) | Approved by ESTIMED | | -------------- | ---------------------- | ------------------- | @@ -537,7 +524,7 @@ This clause provides a list of the issues to open in the ETSI MEC Sandbox [i.13] ## 9.2. oneM2M -Refer to oneM2M TR-0077 Specification [i.12]. +Refer to oneM2M TR-0077 Specification [\[i.12\]](#_ref_i.12).
@@ -581,8 +568,6 @@ Refer to oneM2M TR-0077 Specification [i.12]. | Version | Date | Milestone | |---------------|---------------|-----------------| |V0.0.1 | November 2025 |Early draft | -|---------------|---------------|-----------------| | | | | -|---------------|---------------|-----------------| | | | | -|---------------|---------------|-----------------| +| | | | -- GitLab From ec9083a2c5b0b974e944adf8c2cfc6069cb548ec Mon Sep 17 00:00:00 2001 From: Miguel Angel Reina Ortega Date: Wed, 10 Dec 2025 03:52:40 +0100 Subject: [PATCH 12/12] Editorial changes after MEC-DECODE #33 session --- GR_MEC-DEC_051.md | 108 +++++++++++++++++++++++++++++++++------------- 1 file changed, 79 insertions(+), 29 deletions(-) diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md index 136562a..1e0be8a 100644 --- a/GR_MEC-DEC_051.md +++ b/GR_MEC-DEC_051.md @@ -2,7 +2,7 @@ Title: Multi-access Edge Computing (MEC); oneM2M and MEC interworking and deployments Spec Number: MEC-DEC 051 Version: v0.0.1 -Date: 2025-11 +Date: 2025-12 Release: 1 Work Item: DGR/MEC-DEC051EstimedRec keywords: M2M, MEC, oneM2M @@ -43,9 +43,9 @@ In the present document \"**should**\", \"**should not**\", \"**may**\", \"**nee # 1 Scope -This document identifies a set of missing or to be enhanced requirements for both ETSI MEC and oneM2M platforms, and based on that provides recommendations. This list is based on the use cases and recommendations identified in the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). +This document identifies a set of missing or to be enhanced features for both ETSI MEC and oneM2M platforms, and based on that provides recommendations. This list is based on the use cases and recommendations identified in the document ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1). -This document also provides some recommendations for the ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) to support the implementation and the deployment of the different use cases in each of the deployment options [\[i.3\]](#_ref_i.3). +This document also provides some recommendations for the ETSI MEC Edge Native Connector [\[i.13\]](#_ref_i.13) to support the implementation and the deployment of the different use cases in each of the deployment options [\[i.1\]](#_ref_i.3). # 2 References @@ -163,9 +163,9 @@ The table below shows the recommendations involved by each of the 4 deployment o | Option C | **[mec-enhancement-033]** **[mec-enhancement-046]** | No | | Option D | **[mec-enhancement-033]** **[mec-enhancement-046]** | **[deployment-option-oneM2M-01]** **[deployment-option-oneM2M-02]** **[deployment-option-oneM2M-03]** | -**[mec-enhancement-033]** ETSI GS MEC 033 need to be enhance to fillful oneM2M resources mapping +**[mec-enhancement-033]** ETSI GS MEC 033 need to be enhanced to fillful oneM2M resources mapping -**[mec-enhancement-046]** ETSI GS MEC 046 need to be enhance to fillful oneM2M resources mapping +**[mec-enhancement-046]** ETSI GS MEC 046 need to be enhanced to fillful oneM2M resources mapping **[deployment-option-oneM2M-01]** The oneM2M platform may support IoT platform registration as described in ETSI GS MEC 033 clause 5.3. @@ -234,9 +234,9 @@ The evolution towards the joint MEC-oneM2M standardized architecture to support **[IPE-XXX-0X]** The MEC interworking with oneM2M platform. -**[mec-enhancement-021]** The MEC platform Mobility Service API [\[i.5\]](#_ref_i.5)may be revised to fit use case requirement. +**[mec-enhancement-021]** The MEC platform Mobility Service API [\[i.5\]](#_ref_i.5) may be revised to fit use case needs. -**[mec-enhancement-040]** The MEC platform Federation [\[i.7\]](#_ref_i.7)may be revised to fit use case requirement. +**[mec-enhancement-040]** The MEC platform Federation [\[i.7\]](#_ref_i.7) may be revised to fit use case needs. **[FL-0X]** The MEC platform may support a MEC service that support Federated learning features. @@ -265,11 +265,11 @@ The following recommendations are lready described in the ETSI GS MEC 002: ## 6.1 Introduction -The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [\[i.3\]](#_ref_i.3). The ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1)highlights the need of new MEC services and the need to revise some existing MEC services. +The current state of the art on the ETSI MEC architecture are described in ETSI GS MEC 003 [\[i.3\]](#_ref_i.3). The ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1) highlights the need of new MEC services and the need to revise some existing MEC services. ## 6.2 Missing recommendations -### 6.2.1 Federated Learning requirement (**[FL-0X]**) +### 6.2.1 Federated Learning recommendations (**[FL-0X]**) Federated Learning is a distributed machine learning approach in which model training is performed locally on multiple nodes and only model’s parameters or weights, not row data, are exchanged with aggregators. Instead of sending sensitive data to a central location, each node trains a local model using its own data and then shares only the model updates with a central location, which aggregates these updates to improve the global model. This enhances privacy, reduces bandwidth usage, and allows model adaptation close to data sources. @@ -279,7 +279,7 @@ Federated Learning is a distributed machine learning approach in which model tra **[FL-03]** The FLService supports the coordination between multiple federated clients (MEC applications) and a federated server, leveraging model descriptors and status information via standardized interfaces. -**[FL-04]** The FLService provides secure handling of model parameters and updates during federated training and aggregation, supporting integrity and confidentiality mechanisms as required. +**[FL-04]** The FLService provides secure handling of model parameters and updates during federated training and aggregation, supporting integrity and confidentiality mechanisms as recommended. **[FL-05]** The FLService allows the announcement and dynamic discovery of available federated learning resources and participating nodes in the MEC ecosystem. @@ -293,12 +293,12 @@ Federated Learning is a distributed machine learning approach in which model tra **TODO** To be refined -Editor's note: The ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) can use Flower framework for the federated learning +Editor's note: The ETSI MEC Edge Native Connector [\[i.13\]](#_ref_i.13) can use Flower framework for the federated learning Editor's note: This clause is linked to the task T3.4 -### 6.2.2 Swarm computing requirement (**[SC-0X]**) +### 6.2.2 Swarm computing recommendations (**[SC-0X]**) Swarm Computing refers to the coordination of multiple MEC/oneM2M instances to perform distributed computing tasks, leveraging the capabilities of edge devices and networks. In this paradigm, individual MEC/oneM2M nodes act like members of a swarm, each contributing processing power, storage, connectivity, or sensing capabilities to achieve collective goal. The system operates in a decentralized and adaptive manner, where tasks can be dynamically partitioned, distributed, and recombined across nodes depending on resource availability, network conditions, and application recommendations. @@ -332,12 +332,12 @@ MEC Swarm Computing Service Features ## 6.3 Recommendations to be enhanced -The clauses below described the existing recommendations in the ETSI MEC architecture that require some enhancements or to be re-worked. +The clauses below described the existing recommendations in the ETSI MEC architecture that need some enhancements or to be re-worked. ### 6.3.1 ETSI GS MEC 033 enhancement (**[mec-enhancement-033]**) To work together, both the oneM2M platform and the MEC platform need to know each others. -The ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)introduces a registration mechanism for an IoT platform to register to the MEC platform. +The ETSI GS MEC 033 [\[i.6\]](#_ref_i.6) introduces a registration mechanism for an IoT platform to register to the MEC platform. **TODO** @@ -353,7 +353,7 @@ The ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)introduces a registration mechanism for ### 6.3.3 ETSI GS MEC 021 enhancement (**[mec-enhancement-021]**) -Currently, ETSI GS MEC 021 [\[i.7\]](#_ref_i.7)provides features about Mobility services. The use cases and the recommendations required in ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1)implies to review and enhance it. +Currently, ETSI GS MEC 021 [\[i.7\]](#_ref_i.7) provides features about Mobility services. The use cases and the recommendations introduced in ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1) implies to review and enhance it. **TODO** To be continued @@ -364,7 +364,7 @@ Currently, ETSI GS MEC 021 [\[i.7\]](#_ref_i.7)provides features about Mobility ## 7.1. Introduction -The current state of the art on the oneM2M architecture are described in oneM2M TS-0001 Functional Architecture [\[i.14\]](#_ref_i.14). The ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1)highlights the need of new oneM2M recommendations and the need to revise some existing ones. +The current state of the art on the oneM2M architecture are described in oneM2M TS-0001 Functional Architecture [\[i.14\]](#_ref_i.14). The ETSI GR MEC-DEC 050 [\[i.1\]](#_ref_i.1) highlights the need of new oneM2M recommendations and the need to revise some existing ones. **TODO** To be refined @@ -373,10 +373,10 @@ The current state of the art on the oneM2M architecture are described in oneM2M ### 7.2.1 Registration mechanism (**[deployment-option-oneM2M-01]**) -The oneM2M platform (MN-CSE) may support ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)to register to MEC platform. -During the setup phase of the oneM2M platform, it registers to the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)clauses 5.3.4 IoT platform registration and 7.5.3.4 POST. -During the shutdown phase of the oneM2M platform, it deregisters from the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)clauses 5.3.6 IoT platform deregistration and 7.6.3.5 DELETE. -The data structure used for these operations is described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)clause 6.2.3 Type: IotPlatformInfo. +The oneM2M platform (MN-CSE) may support ETSI GS MEC 033 [\[i.6\]](#_ref_i.6) to register to MEC platform. +During the setup phase of the oneM2M platform, it registers to the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6) clauses 5.3.4 IoT platform registration and 7.5.3.4 POST. +During the shutdown phase of the oneM2M platform, it deregisters from the ETSI MEC Platform using the procedure described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6) clauses 5.3.6 IoT platform deregistration and 7.6.3.5 DELETE. +The data structure used for these operations is described in ETSI GS MEC 033 [\[i.6\]](#_ref_i.6) clause 6.2.3 Type: IotPlatformInfo. **TODO** To be refined @@ -385,7 +385,7 @@ The data structure used for these operations is described in ETSI GS MEC 033 [\[ ### 7.2.2 Registration mechanism (**[deployment-option-oneM2M-03], [deployment-option-oneM2M-03]**) -In order to act as a MEC application (MN-CSE, MN-AE) or a MEC service (MN-CSE), the oneM2M platform may support ETSI GS MEC 011 [\[i.4\]](#_ref_i.4)application management and service management. +In order to act as a MEC application (MN-CSE, MN-AE) or a MEC service (MN-CSE), the oneM2M platform may support ETSI GS MEC 011 [\[i.4\]](#_ref_i.4) application management and service management. **TODO** To be continued @@ -415,7 +415,7 @@ The oneM2M platform may support MEC Swarm computing Service API. ### 7.2.6 Support of MQTT & CoAP over secured Websocket -Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP cannot be used. The workaround is to use MQTT & CoAP over secured Websocket [\[i.18\]](#_ref_i.18) +Due to the limitation introduced by the ETSI MEC Edge Native Connector, raw MQTT and raw CoAP cannot be used. The workaround is to use MQTT & CoAP over secured Websocket [\[i.18\]](#_ref_i.18) **TODO** To be refined @@ -425,9 +425,9 @@ Due to the limitation introduced by the ETSI MEC Sandbox, raw MQTT and raw CoAP **TODO** -# 8 ETSI MEC Sandbox recommendations +# 8 ETSI MEC Edge Native Connector recommendations -## 8.1 MEC Interworking with oneM2M requirement (**[IPE-XXX-0X]**) +## 8.1 MEC Interworking with oneM2M recommendation (**[IPE-XXX-0X]**) The purpose of the MEC Interworking with oneM2M is to enable the exchange of information between the two platforms as defined in [\[i.11\]](#_ref_i.11). The MEC Interworking with oneM2M follows these three steps [\[i.11\]](#_ref_i.11): @@ -437,9 +437,9 @@ The MEC Interworking with oneM2M follows these three steps [\[i.11\]](#_ref_i.11 ### 8.1.1 MEC Interworking architecture -The MEC Interworking with oneM2M architecture is derived from [\[i.11\]](#_ref_i.11) clause 6.2.1. From the ETSI MEC architecture [i.2], the MEC Interworking with oneM2M is part of the MEC Platform [\[i.3\]](#_ref_i.3)clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [\[i.6\]](#_ref_i.6)and ETSI GS MEC 046 [\[i.8\]](#_ref_i.8). +The MEC Interworking with oneM2M architecture is derived from [\[i.11\]](#_ref_i.11) clause 6.2.1. From the ETSI MEC architecture [\[i.2\]](#_ref_i.2), the MEC Interworking with oneM2M is part of the MEC Platform [\[i.3\]](#_ref_i.3) clause 6.3.2 Architecture diagram and it is shared by both services ETSI GS MEC 033 [\[i.6\]](#_ref_i.6) and ETSI GS MEC 046 [\[i.8\]](#_ref_i.8). -The MEC Interworking with oneM2M requires a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [\[i.3\]](#_ref_i.3)describes the procedure to achieve this registration. +The MEC Interworking with oneM2M supposes a pre-requisite: the oneM2M platform have to be registered to the MEC platform. Currently, ETSI GS MEC 033 [\[i.3\]](#_ref_i.3) describes the procedure to achieve this registration. Editor's note: This clause is linked to the task T3.1 @@ -473,11 +473,61 @@ Currently, only JSON serialization mechanism is natively supported, by the end o ### 8.1.4 MEC Interworking on the information model layer + + + + + + + +#### 8.1.4.1 Introduction + Mainly, MEC Interworking on the information model layer provides the harmonization of the informatioon model for both oneM2M with and MEC platform. -For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models as defined in ETSI TS 118 123 [\[i.12\]](#_ref_i.12). +The IPE is an AE in the oneM2M sense and is an IoT‑facing service in the MEC sense.​ +For non-oneM2M devices using ETSI MEC services, the MEC Interworking with oneM2M provides compliancy to oneM2M-defined information models as defined in ETSI TS 118 123 [\[i.12\]](#_ref_i.12): +- Resource Mapping +- Protocol Translation +- Service Discovery + **TODO** To be refined +#### 8.1.4.1 Architecture + +A oneM2M–MEC IPE can be realized as a MEC IoT Service (MEC IoTS) exposing oneM2M Mca resources toward MEC Apps over Mp1, while acting as an Interworking Proxy Entity (IPE AE) toward an IN‑CSE/MN‑CSE, fully aligning with ETSI MEC 003 **[]** and oneM2M TS‑0033 **[]**. This IPE terminates Mca on the oneM2M side, Mp1 on the MEC side, and can be deployed as a MEC service, reusing and extending MEC 033 IoT API **[]** and MEC 046 sensor‑sharing **[]** concepts. + +A standards‑aligned architecture includes the following key functional entities and reference points. +- oneM2M side: + - IN‑CSE and/or MN‑CSE, exposing Mca to AEs, including the MEC IPE AE **[]**;​ + - MEC IPE AE: an Interworking Proxy Entity registered at the Registrar CSE, exposing non‑oneM2M MEC resources as oneM2M resource instances (e.g., containers, flexContainers for MEC services, subscriptions for MEC events) **[]**.​ +- MEC side: + - MEC Host with MEC Platform (MEP) and MEC Platform Manager, conforming to ETSI MEC 003 **[]**.​ + - MEC IoT Service (MEC IoTS‑oneM2M), either: + - as a MEC App registered in the Service Registry and exposing an Mp1 REST API to MEC Apps; or + - as a platform‑internal service exposed via Mp1, following MEC 033’s IoT API model **[]**.​ + - MEC Apps consuming: + - oneM2M‑originated data (e.g., device telemetry, commands) through the MEC IoTS‑oneM2M; and + - MEC services such as Location, V2X, sensor sharing (MEC 046 **[]**) which are in turn exposed back into oneM2M via the IPE.​ + +Interconnections (high level).​ +- Mca: between MEC IPE AE and Registrar CSE (IN‑CSE/MN‑CSE) for CRUDN on oneM2M resources and subscription/notification. +- Mp1: between MEC IoTS‑oneM2M and MEC Apps; and between MEC IoTS‑oneM2M and other MEC services (Location, Radio Network Info, Sensor‑sharing). +- Mm, Mx: standard MEC 003 management and external reference points (e.g., to 5GC enablers per TS 118 133) are unchanged; the IPE is transparent to those.​ + +Logical mapping. +The MEC IoTS‑oneM2M and the IPE AE can be implemented as one component: +- northbound interface: Mp1 REST API that resembles/sub‑sets MEC 033 IoT API for device discovery/provisioning and MEC 046 data exposure (sensor data, metadata, subscription);​ +- southbound interface: oneM2M Mca client speaking HTTP/CoAP/MQTT bindings and CRUDN on resource tree (AE, container, contentInstance, subscription, flexContainer templates for MEC sensor semantics).​ + + +#### 8.1.4.2 Use cases + + + +#### 8.1.4.3 + + + # 9 Conclusions & Actions @@ -500,9 +550,9 @@ This clause provides a list of the NWI to propose to ETSI ISG MEC in order to in Editor's note: This clause is linked to the tasks T3.1 and T3.5 -## 9.1.2 ETSI MEC Sandbox issues +## 9.1.2 ETSI MEC Edge Native Connector issues -This clause provides a list of the issues to open in the ETSI MEC Sandbox [\[i.13\]](#_ref_i.13) GITLAB to cover the recommendations. +This clause provides a list of the issues to open in the ETSI MEC Edge Native Connector [\[i.13\]](#_ref_i.13) GITLAB to cover the recommendations. **Table 9.1.2-1: Open issues for ETSI MEC Sandbox** -- GitLab