@@ -140,7 +140,7 @@ The present document may include trademarks and/or tradenames which are asserted
# Foreword
This Group Report (GR) has been produced by ETSI Industry Specification Group <long ISGname> (<short ISGname>).
<mark>akr: Who will provide the foreword?</mark>
<!-- <mark>akr: Who will provide the foreword?</mark> -->
# Modal verbs terminology
@@ -151,7 +151,7 @@ In the present document "**should** ", "**should not** ", "**may** ", "**need no
# Executive summary
<mark>akr: Who will provide the executive summary?</mark>
<!-- <mark>akr: Who will provide the executive summary?</mark> -->
# Introduction
@@ -177,14 +177,13 @@ References are either specific (identified by date of publication and/or edition
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.
<mark>akr: I changed the html anchors to real (markdown) links.</mark>
-[\[i.1\]](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.2\]](https://www.etsi.org/images/files/ETSIWhitePapers/ETSI-WP59-Enabling-Multi-access-Edge-Computing-in-iot.pdf) Enabling Multi-access Edge Computing in Internet-of- Things: how to deploy ETSI MEC and oneM2M".
# 3 Definition of terms, symbols and abbreviations
<mark>akr: Do we have terms, symbols and abbreviations to define? If not, change the contents of the clauses to "Not applicable.</mark>
Not applicable.
## 3.1 Terms
@@ -225,7 +224,6 @@ The goal of this clause is to present selected domains where edge computing and
The table below summarizes the domains and the associated use cases covered in this clause:
<mark>akr: table header style is taken care of by CSS and converters. I removed it here and in other tables.</mark>
| Smart City & Mobility | - Autonomous Vehicles and Edge Continuum<br>- Vulnerable Road User Detection | Real-time data processing, V2X communication, urban mobility optimization, traffic safety |
@@ -253,8 +251,6 @@ As the AV moves across different zones, it will seamlessly transition from one M
By integrating oneM2M’s standardized data management with MEC's edge computing capabilities, this use case shows real-time, low-latency processing, while also enabling the migration of applications across MEC zones without compromising service quality. As the AV moves, the system adjusts dynamically, ensuring continuous service delivery through the seamless orchestration between the cloud, MEC, and edge devices. This use case not only supports static services but also mobility services, ensuring that the AV receives timely updates and services as it traverses multiple zones.
<mark>akr:Please use relative paths in references. Absolute paths will not work with local editing.</mark>
**Figure 5.2.2-1: Autonomous Vehicle Edge Computing service continuity.**
@@ -658,8 +654,6 @@ The “Industrial Digital Twin” use case requires tight integration between on
MEC hosts edge applications (e.g., quality inspection, anomaly detection) that interact with MN-CSEs. As mobile assets like AGVs move, the MEC, MN-CSE and IN-CSE coordinate handovers and synchronize twin states across MN-CSEs, ensuring seamless operation and minimal downtime.
In the following table, we will consider all the relevant operational requirement for this use case.
<mark>akr: The following table was broken and not syntactically correct. Please check the table and the content that it is okay now.</mark>
##### Table 6.4.6.1-1 – Operational Requirements and Platform Support for Industrial Digital Twins
| Operational Requirement | Support in MEC | Support in oneM2M |
@@ -685,8 +679,6 @@ The “Assisted Manoeuvring for Autonomous Ships” use case supports autonomous
When a ship enters port waters, MEC hosts localized MEC/Edge applications (e.g., assisted maneuvering, collision avoidance) that interact with MN-CSEs for low-latency analytics. As the vessel moves, tasks are seamlessly offloaded across MN-CSEs, with the IN-CSE ensuring synchronization and service continuity.
This deployment enables responsive control, enhanced safety, and uninterrupted autonomous operation of unmanned ships near coastal and harbor zones. In the following table, we will consider all the relevant operational requirement for this use case.
<mark>akr: The following table was broken and not syntactically correct. Please check the table and the content that it is okay now.</mark>
##### Table 6.4.7.1-1 – Operational Requirements and Platform Support for Assisted Manoeuvring for Autonomous Ships
| Operational Requirement | Support in MEC | Support in oneM2M |
@@ -709,8 +701,6 @@ The MEC App subscribes to live data from the IN-CSE and processes it to deliver
Optionally, an MN-CSE may be instantiated on the MEC platform to further reduce latency and improve service continuity. This hybrid deployment ensures real-time, synchronized experiences across the digital and physical retail layers.
In the following table, we will consider all the relevant operational requirement for this use case.
<mark>akr: The following table was broken and not syntactically correct. Please check the table and the content that it is okay now.</mark>
##### Table 6.4.8.1-1 – Operational Requirements and Platform Support for Smart Metaverse Shopping
| Operational Requirement | Support in MEC | Support in oneM2M |
@@ -728,8 +718,6 @@ The “Future Homes” use case delivers immersive and personalized smart home s
Latency-critical tasks like video analytics and sensor fusion are offloaded to Customer Premises Edge devices hosting MEC apps or CSEs, with MEC platforms leveraging the MEP interface for discovery and task delegation.
In the following table, we will consider all the relevant operational requirement for this use case.
<mark>akr: The following table was broken and not syntactically correct. Please check the table and the content that it is okay now.</mark>
##### Table 6.4.9.1-1 – Operational Requirements and Platform Support for Future Homes
| Operational Requirement | Support in MEC | Support in oneM2M |
