diff --git a/GR_MEC-DEC_051.md b/GR_MEC-DEC_051.md
index b92971325317c4709229dd87ffb4a3f33217e6f6..1e0be8a62313a15ec46d2bdd20c212204bd6bd1e 100644
--- a/GR_MEC-DEC_051.md
+++ b/GR_MEC-DEC_051.md
@@ -1,208 +1,581 @@
+---
+Title: Multi-access Edge Computing (MEC); oneM2M and MEC interworking and deployments
+Spec Number: MEC-DEC 051
+Version: v0.0.1
+Date: 2025-12
+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
+---
+# Intellectual Property Rights
-
+Essential patents
-**ETSI GR LLL-LLL DDD Vm.t.e (yyyy-mm)**
+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.
-
-**Group REPORT**
+Trademarks
-Title;
+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.
-Part #: Part element of title;
+**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.
-Sub-part #: Sub-part element of title
+# Foreword
-Release #
+This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Multi-access Edge Computing (MEC).
-
+
-
-
-
-
+
-_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).
+# 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.
-
+# 1 Scope
-**Disclaimer**
+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).
-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.
-It does not necessarily represent the views of the entire ETSI membership.
-ETSI GR LLL-LLL DDD Vm.t.e (yyyy-mm)
+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
-
-Reference
+## 2.1 Normative references
+Normative references are not applicable in the present document.
-<Workitem>
+## 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.
-Keywords
+[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".
-<keywords>
-ETSI
+# 3 Definition of terms, symbols and abbreviations
-650 Route des Lucioles
+## 3.1 Terms
-F-06921 Sophia Antipolis Cedex - FRANCE
+For the purposes of the present document, the [following] terms [given in ... and the following] apply:
-Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+## 3.2 Symbols
+For the purposes of the present document, the [following] symbols [given in ... and the following] apply:
-Siret N° 348 623 562 00017 - APE 7112B
-Association à but non lucratif enregistrée à la
+## 3.3 Abbreviations
-Sous-préfecture de Grasse (06) N° w061004871
+For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:
-
+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**
-**_Important notice_**
+| 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 |
+| 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]** |
-The present document can be downloaded from the [ETSI Search & Browse Standards](ETSI Search & Browse Standards) application.
+**[mec-enhancement-033]** ETSI GS MEC 033 need to be enhanced to fillful oneM2M resources mapping
-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.
+**[mec-enhancement-046]** ETSI GS MEC 046 need to be enhanced to fillful oneM2M resources mapping
-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).
+**[deployment-option-oneM2M-01]** The oneM2M platform may support IoT platform registration as described in ETSI GS MEC 033 clause 5.3.
-If you find errors in the present document, please send your comments to
the relevant service listed under [Committee Support Staff](Committee Support Staff).
+**[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.
-If you find a security vulnerability in the present document, please report it through our
+**[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.
-[Coordinated Vulnerability Disclosure (CVD)](Coordinated Vulnerability Disclosure (CVD)) program.
+> NOTE: Recommendations and enhancements are detailled in clause 6.
-
+**TODO** To be refined
-**_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
+# 5 Edge & IoT Domains and Use Cases
-other professional standard and applicable regulations.
+## 5.1 Introduction
-No recommendation as to products and services or vendors is made or should be implied.
+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:
-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.
+**Table 5.1-1: Domains covered**
-In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
++-----------------------+--------------------------------------------+-----------------------------------------+
+| 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
-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.
+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**
-**_Copyright Notification_**
+| 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]** |
+| 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]** |
-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.
+**TODO** Finalyse the table above
+**[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 needs.
-© ETSI yyyy.
+**[mec-enhancement-040]** The MEC platform Federation [\[i.7\]](#_ref_i.7) may be revised to fit use case needs.
-All rights reserved.
+**[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.
-# Contents
+**[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.
-# Intellectual Property Rights
+The following recommendations are lready described in the ETSI GS MEC 002:
-Essential patents
+**[Location-0X]** Feature LocationService [\[i.2\]](#_ref_i.2) clause 6.3.4 Feature LocationService
-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/).
+**[V2X-0X]** Feature V2XService [\[i.2\]](#_ref_i.2) clause 6.3.8 Feature V2XService
-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.
+**[CustomerPremiseEdge-0X]** Feature CustomerPremiseEdge [\[i.2\]](#_ref_i.2) clause 6.3.11 Feature CustomerPremiseEdge
+**TODO** To be refined
-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.
+# 6 ETSI MEC platform recommendations
-**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.
+## 6.1 Introduction
-# Foreword
-This Group Report (GR) has been produced by ETSI Industry Specification Group <long ISGname> (<short ISGname>).
+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
-# 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).
+### 6.2.1 Federated Learning recommendations (**[FL-0X]**)
-"**must** " and "**must not** " are **NOT** allowed in ETSI deliverables except when used in direct citation.
+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.
-# Executive summary
+**[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 recommended.
-# Introduction
+**[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.
-# 1 Scope
-The present document ...
+**[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
-# 2 References
+Editor's note: The ETSI MEC Edge Native Connector [\[i.13\]](#_ref_i.13) can use Flower framework for the federated learning
-## 2.1 Normative references
-Normative references are not applicable in the present document.
+Editor's note: This clause is linked to the task T3.4
-## 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.
+### 6.2.2 Swarm computing recommendations (**[SC-0X]**)
-> NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
+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.
-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.
+MEC Swarm Computing Service Features
+**[SC-01]** The MEC system may support the feature called SCService.
-- [i.1]
+**[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.
-# 3 Definition of terms, symbols and abbreviations
+**[SC-02]** The MEC system ensures authentication and authorization for swarm participants and controllers, enabling secure distributed operation.
-## 3.1 Terms
+**[SC-03]** The SCService supports dynamic formation, adaptation, and dissolution of collaborative clusters based on node availability, proximity, and policy.
-For the purposes of the present document, the [following] terms [given in ... and the following] apply:
+**[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.
-## 3.2 Symbols
-For the purposes of the present document, the [following] symbols [given in ... and the following] apply:
+**[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 recommendations for collaborative tasks.
-## 3.3 Abbreviations
+**TODO** To be refined
-For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:
+Editor's note: This clause is linked to the task T3.4
+
+## 6.3 Recommendations to be enhanced
+
+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.
+
+**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\]](#_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
+
+Editor's note: This clause is linked to the tasks T3.2 & T3.3
+
+
+# 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\]](#_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
+
+
+## 7.2 oneM2M new recommendations
+
+### 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.
+
+**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\]](#_ref_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]**)
-# 4 User defined clause(s) from here onwards
+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**
+
+
+### 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 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
+
+
+## 7.3. Recommendations to be enhanced or to be re-worked
+
+**TODO**
+
+
+# 8 ETSI MEC Edge Native Connector recommendations
+
+## 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):
+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\]](#_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 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
+
+
+### 8.1.2 MEC Interworking on the connection layer
+
+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.
+
+**[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\]](#_ref_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
+
+
+
+
+
+
+
+
+#### 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.
+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
+
+## 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.
+
+**Table 9.1.1-1: New Work Items for ETSI ISG MEC**
+
+| Recommendations | 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
+
+
+## 9.1.2 ETSI MEC Edge Native Connector issues
+
+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**
+
+| Recommendations | 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
+
+
+## 9.2. oneM2M
+
+Refer to oneM2M TR-0077 Specification [\[i.12\]](#_ref_i.12).
-## 4.1 User defined subdivisions of clause(s) from here onwards
@@ -230,26 +603,21 @@ For the purposes of the present document, the [following] abbreviations [given i
# Annex : Change history
-| Date | Version | Information about changes |
-|------------|---------|---------------------------|
-|<Month year>| <#> | <Changes made are listed in this cell> |
-| | | |
-| | | |
-| | | |
+| 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 |
+| | | |
| | | |
-+---------------+---------------+-----------------+
| | | |
-+---------------+---------------+-----------------+