ETSI MEC: An Introduction(almost) everything you want to know about ETSI MECETSI MEC Leadership Team

For: Public consumption
Last update: December 2023

ETSI MEC: Enabling Edge through Standardization
Foundation for Edge Computing – Fully standardized solution to enable applications in distributed cloud created by ETSI MEC + 3GPP
Application Life Cycle Management

Watch the MEC video

RESTful based APIs for Runtime Application Services

https://www.youtube.com/
watch?v=crnPWql-0oo

ETSI: The Standards People

producing globally applicable standards for
ICT-enabled systems

ETSI ISG MEC
ISG: Industry Specification Group

MEC: Multi-access Edge Computing
Cloud Computing at the Edge of the
network.

open to all of industry, regardless of
ETSI membership and focused on allindustry needs

NFV
MEC

• Continuously growing MEC membership: 127 (in April 2023); e.g. in June 2021 it was 114• Diverse ecosystem: Operators - Technology Providers - IT players - Application developers - Startups
2 -…

©RenewedETSI 2023– AllISG
rightswebpage:
MECreserved
Leadership Team, LS officers for Vertical Industries and MEC Support Team: https://portal.etsi.org/TB-SiteMap/MEC/MEC-Leaders-and-Support-Team

ETSI
MEC
– Foundation
Edge Computing
Focusedon application
enablementfor& APIsClientapp

Remote level

MEC app

Cloud Back end
for service

Service
RESTfulAPIs
exposure

Mp1

MEC
platform

MEC
service

Mp3

Service registry

Basic principles:•

Open standard à allowing multiple implementations and ensuring interoperability•

MEC exploiting ETSI NFV framework and definitions à enabling MEC in NFV deployments•

Alignment with 3GPP based on fruitful collaboration of common member companies à enabling MEC in 5G•

Access-agnostic nature (as per MEC acronym - Multi-access Edge Computing) à enabling other accesses•

Addressing the needs of a wide ecosystem à enable multiple verticals (e.g. automotive), federations© ETSI 2023 – All rights reserved

Accessnetwork

MEC Host

Service

MEC offers to application developers and content
providers cloud-computing capabilities and an IT service
environment at the edge of the network

Edge level

Traffic rules
control

DNS
handling

Web

Remoteservers

Infrastructure

UE level

MEC platform

MEC Host

Data plane

MEC is focused on existential questionsof applications “on the edge”

3

MEC supports
many
5G usecases and market segments
Focusedon application
enablement& APIsMore info at this ETSI White Paper on MEC© ETSI 2023 – All rights reserved

https://www.etsi.org/images/files/ETSIWhitePapers/etsi_wp11_mec_a_key_technology_towards_5g.pdf

4MEC and vertical industries
MEC is a key enabler for many
vertical market segments.
Several (specialized) use cases driven
by different verticals:
•
•
•
•
•
•
•
•

Edge Exposure Day (Sept 18th, 2022, Kfar Saba, Israel) supported by ETSI© ETSI
2023diverse– All rights
reserved
Attendancefrompeople,e.g. local companies, MEC delegates, repr from 5GAA and AECC, …

automotive,
industrial automation,
VR/AR,
Videostreaming,
Gaming,e-health,
Smart Cities,
Etc …

MEC Panels Series5

MEC Panels Series: meeting vertical industries
A series of live panels with relevant experts from the various vertical market segments.
https://mecwiki.etsi.org/index.php?title=MEC_Panel_SeriesFirst event on Drones vertical:• 26 June 2023, co-located with MEC#34• 70+ people registered• 6 keynotes and 1 demo
• Final panel discussion
Other possible verticals (TBD)• CDN, XR, metaverse• Industrial automation© ETSI 2023 – All rights reserved

6MEC reference architecture
APIs
•
•
•
•
•
•
•
•
•

Application Support
Service Management
Radio Network Information
Location
UE Identity
Bandwidth Management
Fixed Access Information
WLAN Information
V2X Information Service•

Application Package
lifecycle and operation
granting
Device applicationinterface•© ETSI 2023 – All rights reserved

7

MEC Standard work: from Phase 1 to Phase 3§ Key overall specification§ Evolution of Phase 1 and closing open items§ Application Mobility (MEC 021 – published)§ Technical Requirements (MEC 002)
§ Framework and Ref. Arch. (MEC 003)
§ MEC PoC Process (MEC-IEG 005)
§ API Framework (MEC 009)

§ IaaS Management APIs
§ Platform mgmt. (MEC 010-1)§ Application mgmt. (MEC 010-2)§ Device-triggered LCM operations (MEC 016)

§ PaaS Service Exposure§ Required Platform Svcs / App. Enablement(MEC 011)§ Service APIs (MEC 012, 013, 014, 015)

§ Key Studies for Future Work§ Study on MEC in NFV (MEC 017)
§ Study on Mobility Support (MEC 018)

2015

ETSI MEC phase 1 (Completed)§ Lawful Intercept (MEC 026 – published)§ Addressing key Industry Segments§ V2X (MEC 022 – published; MEC 030 – published)§ Industrial Automation, VR/AR§ Key use-cases and new requirement§ Network Slicing (MEC 024 – published)§ Container Support (MEC 027 – published)§ Normative work for integration with NFV§ Incorporate in v2 of existing specs as needed§ From “Mobile” to “Multi-Access”§ Full Phase 3 work ongoing (with some pre-Phase 4).
§ MEC as heterogeneous clouds§ Expanding traditional cloud and NFV LCM approaches§ Inter-MEC systems and MEC-Cloud systems
coordination: “MEC Federation”(MEC 035 – published / MEC040 -- published)§ Mobile/intermittently connected and resource
constrained devices (MEC 036), MEC IoT API (MEC 033)

§ MEC Security (GR MEC 041)
§ MEC deployments (MEC in Park enterprises: MEC 038)
§ MEC Application Slices (MEC 044)
§ Continuing emphasis on enabling developers§ Wi-Fi (MEC 028 – published)§ Application Package Format and Descriptor Specification (MEC 037)

§ Fixed Access (MEC 029 – published)§ API Serialization§ MEC integration in 5G networks (MEC 031)
• Developer community engagement§ MEC Sandbox development§ Testing and compliance§ Continue to define services that meet industry
demand (e.g. Abstracted Radio Network Info for• Hackathons, MEC Delpoyment Trials
Industries, GR MEC 043)
• Testing and Compliance (MEC-DEC 025 – published;§ Maintain and enhance existing APIs (e.g. MEC 013)
multipart specification MEC-DEC 032-x)• API publication through ETSI Forge (more overleaf)

2018

ETSI MEC phase 2 (Completed)2021 ETSI MEC phase 3 (almost completed)Legenda

MEC Phase 3 Work Items
MEC Phase 3 (2021-2023)
MEC Phase 4 (2024-2026)
MEC 001 - Terminology
MEC 002 v311 - Use Cases and Requirements
MEC 002 v321 - Use Cases and Requirements
MEC 003 - Framework and Reference Architecture
MEC009 - General principles, patterns and common aspects of MEC Service APIs
MEC 010-2 v311 - MEC Mgmt; Part 2: App lifecycle, rules and req mgmt
MEC 010-2 v321 - MEC Mgmt; Part 2: App lifecycle, rules and req mgmt
MEC 011 - Edge Platform Application Enablement
MEC 013 - Location API
MEC 014 - UE Identity API
MEC 015 - Traffic mgmt API
MEC 016 - Device App Interface API
MEC 021 - Phases 3 - Application Mobility Service API
MEC 030 v311
MEC 030 v321
MEC 036 - Constrained Device (impacting MEC Phase 4)
MEC 037 v311
MEC 037 v321 - App Pkg Format Description
MEC 040 v311
MEC 040 - Federation enablement APIs
MEC 041 - Study on MEC Security
MEC 043 - Abstracted Radio Network Information for Industries (impacting MEC Phase 4)
MEC 044 - Study on MEC Application Slices
MEC 045 - QoS Measurement API
MEC 046 - Sensor-sharing API
MEC 047 - Distributed Edge Network - (MEC Phase 4)
MEC 048 - Enablement API for Customer Self-Service
MEC-DEC23 – Open API (STF 644)
MEC DEC32-1 - API Conf Test Spec; Part 1: Test Req and Impl Conf Statement (ICS)API Conformance Test Specification; Part 2 and Part 3 (TTF027)
MEC DEC32-2 - API Conf Test Spec; Part 2: Test Purposes (TP)MEC DEC32-3 - API Conf Test Spec; Part 3: Abstract Test Suite (ATS)MEC-DEC-34 Sandbox - STF 625
MEC-DEC49 Edge Native Connector - STF 678 - (MEC Phase 4)© ETSI 2018

early draft

final draft

TB approval

publication/completion

2023

2022
4Q

stable draft

1Q

2Q

2024
3Q

4Q

1Q

2Q

2025
3Q

4Q

1Q

2Q

10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4
1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6 6
1 1 2 3 4 4 5 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
0 0 0 0 0 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6 6
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6
0 0 0 1 1 1 1 1 1 1 1 2 2 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6 6 6
1 1 2 2 2 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 5 6 6 6 6 6 6 6 6 6
0 0 0 0 0 0 0 0 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6 6
1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6 6
2 3 4 5 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6 6
0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6
0 0 0 0 0 0 0 0 0 0 0 1 1 1 2 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6
1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 3 4 5 6 6 6 6 6 6 6 6 6 6 62 2 2 2 4 5 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
0 0 0 0 0 0 0 0 0 0 0 0 0 1 2 3 3 4 5 6 6 6 6 6 6 6 6 6 6 6
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6
1 1 2 2 4 5 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6
2 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
0 0 0 0 0 0 0 0 0 0 1 1 1 1 2 3 3 4 5 6 6 6 6 6 6 6 6 6 6 6
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6
0 0 0 1 1 1 1 1 1 1 1 1 1 1 2 3 3 4 5 6 6 6 6 6 6 6 6 6 6 6
0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 3 3 4 5 6 6 6 6 6 6 6 6 6 6 6
0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 2 2 3 4 4 5 6
0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 6

0
5
0
0
B

Milestone A
1 1 1 15 5 5 50 0 0 00 0 0 0C Mil. D

1
5
0
0

Mil. B
1 1 1
5 5 5
1 1 1
1 1 1

Mil. C
1 1 1
5 5 5
1 1 1
1 1 1

Mil. D
1 1 1
5 5 5
1 1 1
1 1 1

1
5
2
2

1
5
2
2

Mil. A

1
5
2
2

1
5
3
3

1
5
4
4

Mil. B

2
5
5
5

2
5
6
6

3
5
6
6

4
5
6
6

Mil. C

6
5
6
6

6
5
6
6

5

6
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

6
5
6
6
Mil. D

Mil. E

9

MEC toward 6G• CAVEAT: nobody knows yet what 6G will be! So, we cannot claim (still) what MEC in 6G
will be, of course.
• On the other hand, MEC evolution and vision can be shaped (in a pragmatic way).
• The newly approved ToR#5 of MEC (available here) is related to the period 2023-2024.
• Thus, it will include also the beginning of MEC Phase 4 (2024-2026).
• So, at least, we could draw (from the ToR#5) some differences between MEC Phase 3(2021-2023) and Phase 4 (2024-2026).
2015

2018

2021

2024

ETSI MEC phase 1(Completed)ETSI MEC phase 2(Completed)ETSI MEC phase 3(ongoing)

ETSI MEC phase 4(2024-2026)

MEC toward 6G : planning MEC Phase 4• CAVEAT: nobody knows yet what 6G will be! So, we cannot claim (still) what MEC in 6G
will be, of course.
• On the other hand, MEC evolution and vision can be shaped (in a pragmatic way).
• The newly approved ToR#5 of MEC (available here) is related to the period 2023-2024.
• Thus, it will include also the beginning of MEC Phase 4 (2024-2026).
• So, at least, we could draw (from the ToR#5) some differences between Phase 3 (202122023) and Phase 4 (2024-2026).
In a nutshell, a transition from MEC Phase 3 to MEC Phase 4 can lead to:
•
•
•
•
•

more consolidated work on MEC Federation, including exposure of resources managed by multiple operators, e.g.
addressing multi-domain and multi-tenancy slicing and MEC support for application slicing;
MEC architectural/service updates needed to support cloud native communication systems and edge native design forapp developers (also with container support)
introduction of proper normative work to improve security and privacy in MEC systems
Further promotion of MEC as an attractive development environment for the industry by creating “developer-friendly
environments” (e.g. portals, SDK) that enable convergence of key industry ecosystem, e.g. app developers and operators
Further outreach efforts, e.g. Hackathons/trials in collab with open source communities, industry groups (e.g. 5GAA, etc..)OurStandards© ETSI 2023 – All rights reserved

ETSI MEC
– Foundation
for Edge
Focusedon application
enablement& APIsComputing
Basic principles:• Open standard à allowing multiple implementations and ensuring interoperability• MEC exploiting ETSI NFV framework and definitions à enabling MEC in NFV deployments• Alignment with 3GPP based on fruitful collaboration of common member companies à enabling MEC in 5G• Access-agnostic nature (as per MEC acronym - Multi-access Edge Computing) à enabling other accesses• Addressing the needs of a wide ecosystem à enable multiple verticals (e.g. automotive), federations
In 2021 5GAA joined
the MEC membership© ETSI 2023 – All rights reserved

13

ETSI MEC
– Foundation
for Edge
Focusedon application
enablement& APIsComputing
Application Enablement
and Framework

API Principles

Specific service-related
APIsManagement andOrchestration related APIs

Service definition framework
and baseline platform services
authorized applications.

Principles and guidance fordeveloping and documenting
APIs

Standardized service-exposure
APIs for key services thatManagement of MEC hosts either
as stand-alone entities or part ofa larger NFV-managed•

Registration, discovery andnotification;• Developer-friendly approach
to foster development

Methodology forauthentication andauthorization of apps
providing/consuming
services;• Ensures that a consistent
set of APIs are used bydevelopers.

••

Communication support forservices (query/response
and notifications).

• Defines approach forauthentication andauthorization of apps
providing/consuming services•

Expose network andcontext information•

Allow definition of localized,
contextual services•

Support key use cases (e.g.
enterprise, vehicular)•

Allow fine-grained edge
traffic management

framework•

Facilitate running of 3rd party
application•

Enable deployment at thecorrect location at the righttime, based on technical andbusiness parameters•

Integrate into telco operations
systems, e.g. OSS• Based on TMF and OMA bestpracticesEnables a myriad of new use cases across multiple sectors as well as innovative business opportunities© ETSI 2023 – All rights reserved

14

Enabling Global Application Portability

ü Simple to use, well documented APIs,
published with OpenAPI Framework
ü Create innovative applications quickly

ISG MEC Spec: MEC009
API Principles & Guidelines

and easily, reducing time-to-revenue
ü New APIs (compliant with the MEC

RESTful based HTTP APIs presented via OpenAPI compliant descriptions(https://forge.etsi.org/), in YAML & JSON including the full data model

API principles) can be added
ü Increase the Total Addressable Market(TAM)

MEC API
Framework

MEC012
Radio Network
Info API

MEC013
Location API

MEC014
UE Identity
API

MEC015
Bandwidth
Mgmt API

MEC028WLAN InfoAPI

MEC Services exposed via individual APIs

© ETSI 2023 – All rights reserved

MEC029Fixed Access
Info API

MEC0xyYour Service
API

MEC011
Application
Enablement API

MEC Platform

15

Application portability via the ETSI MEC APIs ecosystem
That’s all you need as a MEC App
developer
Discover network, users,
capabilities and local services
Manage traffic, DNS, mobility,
V2X, etc.
Register your own service anddiscover third party services
available locally
Plus: APIs for interoperability
among MEC systems and infra© ETSI 2023 – All rights reserved

16

MEC and Management: The Killer Use Case for Automation
MEC deployments present challenging environment

Unique requirements and processes•(large scale: geography) x (small scale: cloud footprint)•

Minimize need for human presence•

Unmanned/lights out location•

Maximize service time intervals•

Outside traditional service areas•

Minimize skills required from those on site

While supporting “critical infrastructure”

In other words•

Telco, public safety, etc.

•

Get as close as possible to the web-scale maintenance model•“9’s” of availability requirements•

In a very non-web-scale environment•

The following ETSI White Papers address the MEC deployment aspects:
WP#23: Cloud RAN and MEC: A Perfect Pairing
WP#24: MEC Deployments in 4G and Evolution Towards 5G
WP#28: MEC in 5G networks
WP#30: MEC in an Enterprise Setting: A Solution Outline
WP#56: Unlocking Digital Transformation with Autonomous Networks:ETSI2023
perspectives
and major
achievements© ETSI– All rights
reservedqqqqq

Suggested reading:•ETSI White Paper Unlocking Digital
Transformation with Autonomous
Networks: ETSI perspectives and17
major achievements (March 2023).

A key part of ETSI Network Automation Standards
Inter-MEC &MEC-Cloud(MEC 035 Study)
Device-triggered
LCM Enablement(MEC 16)

Management ofMEP
as a VNF(MEC 10-1)

LCM Mgmt of 3rdparty Apps
(MEC 10-2)

ZSM: overall approach© ETSI 2023 – All rights reserved

NFV, OSM: managing telco clouds

MEC: managing edge telco clouds
18

MEC White Papers: A view of a whole pictureStandards are necessarily tools, not solutions

https://portal.etsi.org/TBSiteMap/MEC/MEC-White-Papers

Enable interoperability
Support a broad range of use cases and system architecture
Address only a specific part of the whole picture

MEC White Papers: how we help industry see the whole picture- Mobile Edge Computing: A key technology towards 5G (September 2015)- Developing Software for Multi-Access Edge Computing (First edition - September 2017)- Cloud RAN and MEC: A Perfect Pairing (February 2018)- MEC Deployments in 4G and Evolution Towards 5G (February 2018)- MEC in 5G networks (June 2018)- MEC in an Enterprise Setting: A Solution Outline (September 2018)- Developing Software for Multi-Access Edge Computing (2nd edition - February 2019)- Network Transformation;(Orchestration, Network and Service Management Framework) (October 2019)- Harmonizing standards for edge computing - A synergized architecture leveraging ETSI ISG MEC and 3GPP specifications (July 2020)- Enhanced DNS Support towards Distributed MEC Environment (September 2020)- MEC security: Status of standards support and future evolutions (First edition - May 2021)- MEC federation:deployment considerations (June 2022)- MEC security; Status of standards support and future evolutions (2nd edition - September 2022)- Unlocking Digital Transformation with Autonomous Networks: ETSI perspectives and major achievements (March 2023)
NEW!
- MEC Support for Edge Native Design: an application developer perspective (June 2023)- Enabling Multi-access Edge Computing in Internet-of- Things: how to deploy ETSI MEC and oneM2M (June 2023)© ETSI 2023 – All rights reserved…and many more to come!

19

ETSI White paper on MEC Federation: deployment considerations• This White Paper focuses on the deployment options related to MEC federation, especiallyfrom an architectural point of view, and with a key focus on ETSI MEC implementations, butalso with the aim to provide an open approach considering other standards andtechnologies.
• For this purpose, the White Paper firstly analyzes the recent publications of GSMA OPG andrecent updates in ETSI MEC and 3GPP specifications, then introduces the synergizedMulti-access Edge Computing

architecture supported by both standards organizations, which indicates the backgroundinformation for the deployment of MEC federation.

Key considerations in the paper:• Introduces the business stories that enable readers to understand how MEC federation is beneficial for MEC system providers• Based on these business stories, corresponding deployment options are introduced.
• Provide insights for edge stakeholders, and all readers in general, to better understand how to choose the appropriate
deployment options© ETSI 2023 – All rights reserved

https://www.etsi.org/images/files/ETSIWhitePapers/
ETSI_WP_49_MEC-Federation-Deployment-considerations.pdf

20MEC security: status of standards support and future evolutions• MEC scenarios are characterized by a complex multi-vendor, multi-supplier, multi-set of
equipment including both HW and SW devices. Given this overall level of system
heterogeneity, areas of security, trust, and privacy are key topics for the edge

environments.
• In that perspective, MEC stakeholders should pay attention to the vulnerability and integrityof any third-party elements, and a truly end-to-end approach to MEC security needs toMulti-access Edge Computing

consider not only the current standards in ETSI ISG MEC, but also the other available
standards that can be applicable to the MEC environment.

• ETSI white paper, authored by many experts (in the domain of edge computing, security and involved in various
standard bodies), provides an overview of ETSI MEC standards and current support for security, which is also
complemented by a description of other relevant standards in the domain (e.g. ETSI TC CYBER, ETSI ISG NFV,3GPP SA3) and cybersecurity regulation potentially applicable to edge computing.

• https://www.etsi.org/newsroom/press-releases/2123-2022-09-etsi-publishes-a-new-white-paper-on-multiaccess-edge-computing-security© ETSI 2023 – All rights reserved

Second edition
published Sept 2022

21

MEC Support for Edge Native Design: an application developer perspective• This White Paper provides an overview and vision about the Edge Native approach, as a natural
evolution of Cloud Native. Edge Native was first introduced in 2020 by the Linux Foundation'sOpen Glossary of Edge Computing• It explains in detail the concept of “Edge Native”, describes what Edge Native means for edge
developers to build their applications and introduces how ETSI ISG MEC and other organizations
support this Edge Native design paradigm. In particular, the White Paper guides developers in theprinciples and specific requirements of edge computing and how they can combine them with themodern architectural approach introduced by Cloud Native. It also gives insight into the generaltechnical community interested in ETSI MEC solutions or Edge Native application design concepts.
• The authors of the White Paper conclude that the ETSI MEC standard (synergized with 3GPP specifications)can offer a footprint for interoperability, API basic design principles to ensure universal adoption, and possibly
also some guidelines for API abstraction, complementing the work of open-source projects. Therefore, to fully
exploit edge capabilities and for the adoption of edge native design principles from application development
communities, joint efforts from open source and standards will be needed.
• https://www.etsi.org/images/files/ETSIWhitePapers/ETSI-WP55-MEC_support_towards_Edge_native.pdf© ETSI 2021 – All rights reserved

Suggested reading:ETSI White Paper on“MEC support towards
Edge Native Design”

22

Focus on

MEC
Federation© ETSI 2023 – All rights reserved

MEC Phase 3: expanding the scope to MEC Federation

Starting from
Industry requirements …
Ref: GSMA White paper: “Telco Edge Cloud: Edge Service Description and Commercial Principles”, Oct 2020

… ETSI MEC published a very first work on MEC federation
ETSI GR MEC 035 v3.1.1: “Multi-access Edge Computing(MEC); Study on Inter-MEC systems and MEC-Cloudsystems coordination ”, June 2021,
https://www.etsi.org/deliver/etsi_gr/MEC/001_099/03
5/03.01.01_60/gr_mec035v030101p.pdf© ETSI 2023 – All rights reserved

MEC Federation:“federated model of MEC systems enabling
shared usage of MEC services and applications”
24

MEC Phase 3: expanding the scope to MEC Federation
Intra MEC

Inter MEC

MEC - Cloud

Inter MEC host (Intra MEC system)
management already supported by
ETSI MEC

Main scope for MEC 035 study

Ongoing normative work
(e.g. GS MEC 040, MEC 003),
in alignment with
GSMA OPG requirements© ETSI 2023 – All rights reserved
Ref: ETSI GR MEC 035 v3.1.1, June 2021, https://www.etsi.org/deliver/etsi_gr/MEC/001_099/035/03.01.01_60/gr_mec035v030101p.pdf

25

MEC Study on Inter-MEC systems and MEC-Cloud systems
coordination (MEC 035)
Many Use cases#1: MEC federation scenario of V2X services

1. Interop. between MNOs
2. Interop. between MEC
vendors/suppliers
3. Interop between OEMs
(applications)Inspired by 5GAA use cases
including multi-MNO, multiOEM, multi-MEC
Requirements for MEC:
• MEC system discovery• MEC platform discovery• MEC platform level
information exchange© ETSI 2023 – All rights reserved
Ref: ETSI GR MEC 035 v3.1.1, June 2021, https://www.etsi.org/deliver/etsi_gr/MEC/001_099/035/03.01.01_60/gr_mec035v030101p.pdf

26

Study (MEC 035) on
inter-MEC system and Cloud-MEC system coordination
Multi-operator agreements enabling MEC Federation for V2X services§ Type-1 use case - national roaming likescenario: customers of operator A could
access the edge infrastructure of operator B
to ensure the best possible service.
§ Type-2 use case: An app developer has acommercial relationship with operator A.
Federation agreements could allow the app
developer to deploy its App in operator B’s
MEC system.
§ Type-3 use case - federation broker: afederation broker has a set of agreementswith several MNOs.

© ETSI 2023 – All rights reserved
Ref: ETSI GR MEC 035 v3.1.1, June 2021, https://www.etsi.org/deliver/etsi_gr/MEC/001_099/035/03.01.01_60/gr_mec035v030101p.pdf

27

MEC Study on Inter-MEC systems and MEC-Cloud systems
coordination (MEC 035)
Many Use cases#6: MEC federation scenario for immersive AR game

© ETSI 2023 – All rights reserved
Ref: ETSI GR MEC 035 v3.1.1, June 2021, https://www.etsi.org/deliver/etsi_gr/MEC/001_099/035/03.01.01_60/gr_mec035v030101p.pdf

28

GSMA OPG (Operator Platform Group) mapping with ETSI MECETSI MEC is aligning alsowith 3GPP to create aconsistent standard andavoid duplication of work

Note: GSMA is listed as a MEC Participant, can submit contributions to ISG MEC for Discussion or Decision, and not onlyfor Information. Dually, ETSI MEC nominated 2 observers, to represent the ISG in GSMA OPG.
Ref: GSMA Permanent Reference Document, "Operator Platform Telco Edge Requirements", v1.0, Jun. 2021.
©https://www.gsma.com/futurenetworks/wp-content/uploads/2021/06/OPG-Telco-Edge-Requirements-2021.pdf.
ETSI 2023 – All rights reserved
Link:

29

MEC 003 – introducing Architecture variant for MEC federation
Phase 3 deliverable published in March 2022
MEC federator (MEF): enables a MEC federation
between MEC systems•

A MEF interfaces to at least one MEO•

Each MEF enables information exchange with atleast one other MEF•

A MEF may serve as a single point of contact for
multiple MEFs in the MEC federation

MEF may support the following functionality:
•
•
•
•
•

•

© ETSI 2023 – All rights reserved

registration of MEC system information by a MEO;
MEC system discovery;broker capability acting as a one to many intermediary
between MEFs;
information (e.g. MEC system information) exchange;
application lifecycle management (e.g. onboarding/instantiation/termination) across different
MEC systems;
application monitoring across different MEC systems.

Reference: https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/03.01.01_60/gs_MEC003v030101p.pdf

30

MEC 040 – introducing MEC Federation Enablement APIs
Phase 3 deliverable v311 ongoing (stable draft @Oct 2022)

Federation Enablement APIs offer services such as
discovery, information exchange and application life cycle
management to enable the inter-work of one MEC systemwith another MEC system:•

Registration/Update/Deregistration of MEC system(s) to
the federation•

MEC system discovery•

MEC application instance discovery•

MEC service discovery•

Application package mgmt and App instance LCM•

Providing/updating MEC system-wide MEC App instanceinformation updates to MEF

Example (MEC System Discovery) :••ETSI Webinar“MEC Federation Enablement APIs:
overview and instructions for use”àrights
Watchreserved
it here© ETSI 2023 – All

Information flow used for enabling MEO to be aware of another
MEC system
The MEC system discovery is the primitive and essential
procedure for enabling the other functionalities relating to the
Feature MEC Federation

Reference: https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.01.01_60/gs_MEC040v030101p.pdf

31

Alignment between GSMA OPG, ETSI MEC and 3GPP SA6
A possible relationship could consist in the following high-level steps:
1. GSMA asks SDOs to cover standards for the OP architecture (and OSCs to complement with open source)
2. Worksplit (ETSI, 3GPP, OSCs,.. ) and consequent std work, publication of standards etc..
3. Finally, GSMA will certify OP compliance

1.

2.

3.
OSC#2
OSC#1

…
GSMA PRD document(requirements)

Work from SDOs and OSCs
(under the GSMA guidance)
OSC = Open-Source Community

GSMA compliance & OPcertification

MEC Federation: the ETSI MEC view
• Tentative standards mapping presented at the joint GSMA OPG workshop, on 21/01/2021 (*)• A common view on SDO mapping and worksplit is the first step for the collaboration• Alignment with 3GPP is also needed to create consistent standards and avoid duplication of work(*) Recording of the workshop is here; 3GPP slides are here; ETSI MEC slides can be found also here

Note: finalizationof this mapping
is currently WIP© ETSI 2023

ETSI MEC APIs,
external APIsand API exposure

Extending MEC with new MEC Service APIs
MEC Services: value-added capabilities to enable MEC applications––“Built-in” MEC standardized services provided via the MEC Platform.
MEC applications can offer new MEC Services APIs, extending the MEC system

MEC
service© ETSI 2023

www.etsi.org/deliver/etsi_gs/MEC/001_099/009/03.01.01_60/gs_MEC009v030101p.pdf

Service registry

Service

MEC
app

NOTE: ETSI GS MEC 009 is defining Generalprinciples, patterns and common aspectsof MEC Service APIs

Mp1

Mp1

MEC
app

NOTE: also the MEC Sandbox includes
capabilities to advertise, discover, andconsume New MEC Services

MEC
app

Traffic
rules
control

DNS
handling

MEC platform

try-mec.etsi.org
35

2 – MEC App exposing a New MEC Service
MEC App Instance

MEC Platform(service producing)

New Service Registration:– MEC application initializes and confirms
it is ready to the MEC Platform (MEP)– MEC app prepares its new service API– MEC app registers the new service with
the MEP, providing Service Information– MEP registers the service and allocatesa service instance– The New MEC Service is now available
for other MEC Apps in the MEC system

MEC app start-up and initialization(appInstanceId)
MEC app is running

POST /mec_app_support/v1/applications/appInstanceId/confirm_ready(“READY”)
Response = 204 – Success No Content
Service initialization and ready(myNewService)

Service registration
POST /mec_service_mgmt/v1/applications/appInstanceId/services(ServiceInfo)
Register the service

Response = 201 – Service Info (serInstanceId)

The new service is available; ready for discovery and use by other MEC apps in the MEC system© ETSI 202336

3 – MEC App discovering a new MEC Service
New MEC Service Discovery:– Case 1: Subscription / Notification••

Service consuming MEC App creates aService Availability Subscription
When the new service registers andbecomes available, the MEP issues aService Availability Notification, indicating
the New Service is available– Case 2: Service Availability Query••

Service consuming MEC App issues aservice availability query to the MEP
MEP responds with the new service’s
information, including it’s URI endpoint.

MEC App Instance(service producing)

MEC App Instance

MEC Platform(service consuming)

Case 1: Subscription / Notification
Create service availability subscription (myNewService)
New service becomes available and registers with the MEP(myNewService)
New service availability notification
POST /mec_app_callback/newservicecallback(myNewService, serInstanceId, ACTIVE, ADDED)

Case 2: Service Availability Query
New service availability query
GET /mec_service_mgmt/v1/services?ser_name=myNewService
Response = 200 – Service Info (myNewService – endpoint URI)

Serving consuming MEC App interacts with the new service via its API and URI endpoint– MEC app utilises the New MEC
Service via it’s API and endpoint© ETSI 2023

37

MEC Sandbox – try new MEC Service APIs
try-mec.etsi.org

The ETSI MEC Sandbox is an interactive
environment that enables developers tolearn & experiment with “live” ETSI MECService APIs from anywhere in the world

Available MEC Services:
–
–
–
–
–
–
–
–

MEC Platform Application Enablement & Service Management APIs
(MEC 011)
Radio Network Information (MEC 012)
Location Service (MEC 013)
New Bandwidth Management and Traffic Steering (MEC 015)
New Device Application Interface (MEC 016)
Application Mobility Service (MEC 021)
WLAN Access Information (MEC 028)
V2X Information Service (MEC 030)

© ETSI 2023

38

API Exposure and cross-consumption in a MEC Federation•

Option for Edge Native applications to consume MEC

Edge Application (API invoker)

services in a MEC federation (via CAPIF framework and the

MEC
Application

EAS

CAMARA architecture)

API provider
domain functions

CAPIF Core
Function

CAMARA Exposure GW

UE

NOTE: this option also facilitates thesynergies with ETSI MEC and GSMA OPG
architecture, as API exposure can be
exploited also in the MEC federation foredge native application development.

Edge
App

CAMARAarchitecture

Clientapp

CAMARA Transformation
Function

EES

5GC

…

PCF

AMF

MEC
Platform

Edge Platform

NEF

Edge Data
Network

SMF
N6

RAN

N3

UPF

N9

(*) ETSI White Paper “MEC Support for Edge Native Design”,© ETSI 2023
https://www.etsi.org/images/files/ETSIWhitePapers/ETSI-WP55-MEC_support_towards_Edge_native.pdf

UPF39

© ETSI 2018ETSI MEC &CAMARA:
topics forcollaboration

Technical highlights• CAMARA is focused on NBI “Service APIs”, as abstractions from “Internal APIs”•

Since CAMARA’s focus is “application developers” interface APIs, the assumption is for them to have limited orzero knowledge of the network and edge infrastructure.

• According to the figure below, ETSI MEC is standardizing some “Internal APIs”
REMARKS:
•
•

•

M EC

© ETSI 2023

e.g. MEC 012, MEC 013, …

M EC

ETSI MEC standardized APIs are “relevant for
NBI”, i.e. can be abstracted in CAMARA, for theactual NBI exposure to app devs
Also new APIs (i.e. not in need to be standardizedin ETSI MEC) can be added, recognized by the
MEC Platform, and exposed to authorized
Applications
CAPIF is a well recognized (and standard)reference for universal API exposure

M EC

e.g. MEC 003, MEC 040, …

MEC 043 report on Abstracted API for Industries

41

ETSI MEC & CAMARA: collaboration establishment

MoU
betwe in place
en ET
SI andLF

Topics of the collaboration:•

Technical work northbound interface and support for ubiquitous API exposure•

ensuring complementary work on standards / API definitions (CAMARA NBI, SBI by ETSI MEC
and cloud federation) and open-source implementations / tests•

guidelines for API exposure and interwork (e.g., joint white papers)•

Join forces to engage application development communities (e.g., to better attract
application developers, increase the awareness on edge application and help creating API
market demand•

Other areas of collaboration (to be further elaborated) may include the work item
MEC 043 on Abstracted API for Industries

The MEC Chair is collecting names of volunteering delegates that canpractically facilitate the joint work and collaboration with CAMARA.
ETSI
2023MoU: https://docbox.etsi.org/Partners/Agreements/Linux_Foundation_MoU_2022.pdf
Link to©theETSI/LF

42

WG DECODE:© ETSI 2023 – All rights reserved

Enabling MEC
Deployment
and Ecosystem
Development

ETSI ISG MEC DECODE Working Group:
MEC Deployment and Ecosystem engagement activities•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki
https://try-mec.etsi.org/•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

Collaborations: CAMARA, Akraino•

MEC Sandbox•

Hackathons•

Plugtests•

MEC Tech Series© ETSI 2023 – All rights reserved

https://apiportal.akraino.org/apimap.html

https://www.opencompute.org/summit/
global-summit/hackathon
17-19 Oct 2023

NFV&MEC IOP Plugtests

https://mecwiki.etsi.org/index.
php?title=MEC_Ecosystem
44

MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

Collaborations: CAMARA, Akraino•

MEC Sandbox•

Hackathons•

Plugtests•

MEC Tech Series© ETSI 2023 – All rights reserved

Navigating with the
Swagger UI

Discover the APIs on forge.etsi.org/rep/mec
45

OpenAPI representations: ETSI Forge

News: STF (Special Task Force)
for OpenAPI description automation
Status: Project completed Dec 2023,
providing an automated workflow for
OpenAPI description creation directlyfrom the ETSI MEC specifications© ETSI 2023 – All rights reserved

Navigatingwith the
ReDoc UI
46

MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

MEC Sandbox•

Collaborations: Akraino•

Hackathons•

Plugtests•

MEC Tech Series© ETSI 2023 – All rights reserved

FUT

Test
Environment

OpenAPIs

MEC APIs

News: Guidelines on Interoperability testing published Nov 2022
Follow-on API Conformance ETSI TTF launched 2023

MEC API

Test
SystemGeneral testing framework for
MEC Technologies (MEC 0025)

Robot

MEC-DEC032

API Conformance testing developed
for server implementations• Standardized test suite (MECDEC 032) Test implementations
in Robot Framework and TTCN-3• Openly available and released
under BSD-3 license
47

MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

MEC Sandbox•

Collaborations: Akraino•

Hackathons•

Plugtests•

MEC Tech Series© ETSI 2023 – All rights reserved

PoCs
https://mecwiki.etsi.org/index.php?title=Ongoing_PoCs
New MDTs

MEC Deployment Trials
https://mecwiki.etsi.org/inde
x.php?title=Ongoing_MDTs
MEC Ecosystem
https://mecwiki.etsi.org/inde
x.php?title=MEC_Ecosystem

New implementations

We encourage newsubmissions to ETSI MEC !

For further details,
please see:
http://mecwiki.etsi.org or
contact CTI_Support@etsi.org

48

MEC PoCs: Show off YOUR cool Edge
Recent PoCs (13 are complete)

PoC #13

PoC #14

MEC infotainment for smart
roads and city hot spots

Network resource allocation
for Gaming using MEC
BandWidth Management
service and TeraFlowSDN

TIM, Intel, Vivida, ISMB, City of Turin

New PoC

The next PoC

CTTC, xFlow Research, Telefónica

We encourage new POC
submissions to ETSI MEC !

IMAGINE YOUR BEST HERE
PoC #15

PoC #16

New PoC

New PoC

Distributed MEC based AR
remote maintenance forlogistics transportation

MEC based Smartproduction and scheduling

China Telecom, China Telecom Intelligent
NETWORK Technology Co., LTD, Huawei

China Telecom, China Telecom Intelligent
NETWORK Technology Co., LTD, Huawei© ETSI 2023 – All rights reserved

Thought Leaders in Edge
ComputingFor further details,
please see:
http://mecwiki.etsi.org or
contact CTI_Support@etsi.org

49

MEC Deployment Trial: MEC in action in Live Networks
Next step from MEC PoC to keep engaging the ecosystem in MEC standards based deployments
From Proof of Concept to proof of viability in a Live Network environment
Follows the proven MEC PoC framework with a new set of acceptance criteria

1. Trial deployed in Live Network
2. Demonstrated to the industry, e.g., in an industry event or in ISG MEC
3. Feedback to MEC standardization; improvement proposals, lessons learnt, next steps
For further details,
please see: http://mecwiki.etsi.org or contact
CTI_Support@etsi.org

Currently the following MDTs are active:

MEC Deployment Trial

MEC Deployment Trial

MEC Deployment Trial

MEC Deployment Trial

MDT #3

MDT #4

MDT #5

MDT #6

Edge-Cloud VR cloud
game scheme basedon 5G network

ARVR navigation
based on 5G MEC

Smart Factory over
MEC

Federated Edge Hubon MEC

China Unicom, Huawei,
Tencent, Intel

China Telecom, Huawei,
21CN© ETSI 2023 – All rights reserved

SK telecom,
MyungWha Corporation

SK telecom, Singtel
Hewlett Packard Enterprise

We encourage new
MDT submissions to
ETSI MEC !
50

MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

MEC Sandbox•

Collaborations: Akraino•

Hackathons•

Plugtests•

MEC Tech Series

New features andAPIs implemented© ETSI 2023 – All rights reserved

https://try-mec.etsi.org/
A simulator of a real 4G/5G network as seen via the MEC APIs
4G/5G/Wi-Fi access points
Steady and moving UE (~devices)
API Console, integrated Swagger UI, & more
Real MEC Apps can interact with the Sandbox and can register services

51

ETSI MEC Sandbox - Introduction
MEC Sandbox initial launch in January 2021

• Rational for the MEC Sandbox:– Developers indicated the ETSI Forge Open API representations–

are an excellent resource to learn MEC API syntax
However, developers also need to understand the behavior of
MEC services, which can only be achieved by interaction• Interactive MEC emulation environment enablingedge app developers to learn & experiment with“live” ETSI MEC Service APIs from anywhere in
the world:– App developers can remotely call MEC service end-points fromtheir edge application of environment– Alternatively, developers may interact with MEC services via a
web-portal “Try-it” Swagger interface© ETSI 2023 – All rights reserved

52

ETSI MEC Sandbox – Features and MEC Services
The MEC Sandbox emulates an edge system set in
Monaco, including user selectable 4G, 5G, and WiFi
network topology configurations (scenarios)

MEC Services:
–
–
–
–
–

MEC 011: Application and Service Enablement
MEC 012: Radio Network Information Service
MEC 013: Location Service
MEC 021: Application Mobility Service
MEC 028: WLAN Access Information Service

Edge Network Scenarios:
–
–
–
–
–

© ETSI 2023 – All rights reserved

4G Macro – Single MEC Platform
4G/5G Macro – Single MEC Platform
4G/5G/WiFi – Single MEC Platform
4G/5G/WiFi – Dual MEC Platform
4G/5G/WiFi – Dual MEC + Short Terminal
Mobility Paths
53

Putting it all together…with ETSI GS MEC 013 – Location API
Specification Document

gs_mec013v020101p.pdf© ETSI 2023 – All rights reserved

ETSI Forge – Open API(human and machine readable)

forge.etsi.org - LocationAPI.yaml

MEC Sandbox(live interaction - try-mec.etsi.org)

54

Check out the MEC Sandbox!!
Added in 2022:

try-mec.etsi.org– V2X API (MEC 030), with further
enhancements in 2023 (message distribution)– Bandwidth Management and Traffic Steering
Service (MEC 015)
– Device Application API (MEC 016)

Available MEC Services:
–
–
–
–
–

Application and Service Enablement APIs (MEC 011)
Location (MEC 013)
Radio Network Information (MEC 012)
WLAN Access Information (MEC 028)
Application Mobility Service (MEC 021)

© ETSI 2023 – All rights reserved

55

Additional Resources to learn more…
Sandbox in use –“Getting Started with the MEC Sandbox” –MEC Hackathon 2023

ETSI Webinar Recording (Feb 2021) –etsi.org/events/getting-started-with-the-mec-sandbox

MEC Tech Series playlist on ETSI’s YouTube channel:
mecwiki.etsi.org/MEC_Tech_Series

Edge Computing World - MEC Hackathon
2023 - Developer Challenge

MEC Sandbox Slack Workspace -Join the discussion board - Link
Detailed Technical Information –Insights for Edge Software Developers

v Episode #4 – MEC Sandbox
v Episode #9 - VIS API in MEC Sandbox
ETSI 2022#11– Allv©Episode- rights
MEC Sandbox Service Enablement
reserved– MEC Sandbox Wiki (User guide):

https://mecwiki.etsi.org/index.php?title=MEC_Sandbox_Help– MEC Sandbox’s underlying Edge Emulation Engine:
https://github.com/InterDigitalInc/AdvantEDGE

56

MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

Collaborations: CAMARA, Akraino•

MEC Sandbox•

Hackathons•

Plugtests

REMARKS:•••ETSI MEC standardized APIs are “relevant for NBI”, i.e., can be abstracted in
CAMARA, for the actual NBI exposure to app devs.
Also new APIs (i.e., not in need to be standardized in ETSI MEC) can be added,
recognized by the MEC Platform, and exposed to authorized Applications
CAPIF is a well recognized (and standard) reference for universal API exposure

MEC 043 report on
Abstracted API for
Industries
M EC•

MEC Tech Series© ETSI 2023 – All rights reserved

M EC

e.g. MEC 012, MEC 013, …

M EC

e.g. MEC 003, MEC 040, …

57

MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

Collaborations: CAMARA, Akraino•

MEC Sandbox•

Hackathons•

Plugtests•

MEC Tech Series© ETSI 2023 – All rights reserved

https://apiportal.akraino.org/apimap.html

58MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge

Past MEC Hackathons:Ø18-19 September 2018: 3 parallel events (link)•
Berlin (co-located with Edge Computing Congress)•
Beijing (China)•
Turin (Italy)Ø

17-18 September 2019: 2 parallel events (link)•
London, UK (co-located with Edge Computing Congress)•
Shenzen (China)•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)

Ø

18 November 2019, in collab. with LF Edge Akraino (link)•
San Diego (USA) (with KubeCon + CloudNativeCon North America)•

Collaborations: CAMARA, AkrainoØ

25-26 November 2020•
2020 Droidcon MEC Hackathon (co-located with Droidcon Italy) (link)•

MEC Sandbox

Ø•Hackathons

12-14 October 2021 & 10-12 October 2022, in collab. with LF Edge Akraino•
2021 Edge Computing World (link)•
2022 Edge Computing World (Santa Clara, USA) (link)•

Plugtests•

MEC Tech Series© ETSI 2023 – All rights reserved

MEC Hackathon 2023 (link)

https://www.opencompute.org/summit/global-summit/hackathon

59

Edge AI Hackathon 2023
- The Developer Challenge

Edge-Native AI/HW/SW Co-design

Teams are challenged to design &prototype an Edge-Native solution,
focusing on the use of AI andconsidering overall application
performance optimization.
Utilizing a wide set of developer
resources offered from across our
supporting organizations.
https://www.opencompute.org/summit/global-summit/hackathon© ETSI 2023. All rights reserved.

60

MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

Collaborations: CAMARA, Akraino•

MEC Sandbox•

Hackathons•

Plugtests•

MEC Tech Series© ETSI 2023 – All rights reserved

3 – 7 June 2019
4th NFV Plugtests
2019
15 – `9 June 2020
NFV&MEC
Plugtests 2020
1 – 28 Feb 2021
NFV&MEC API
Plugtests 2021
1 - 15 Oct 2021
NFV&MEC IOP
Plugtests 2021

61

MEC: DECODE Working Group•

OpenAPI representations: ETSI Forge•

Testing and Conformance•

MEC Ecosystem wiki•

PoCs (proof-of-concepts)•

MDTs (MEC Deployment Trials)•

MEC Sandbox•

Collaborations: Akraino•

Hackathons•

Plugtests•

MEC Tech Series© ETSI 2023 – All rights reserved

62Get involved with MEC!
v Learn and implement MEC APIs on ETSI Forge (forge.etsi.org)
v Experiment with MEC APIs in the MEC Sandbox (try-mec.etsi.org)
v Share your projects on the MEC Ecosystem wiki (mecwiki.etsi.org)
v Consider joining a MEC Hackathon as a participant or organizer (link)v Share your insights by volunteering to produce a MEC Tech Series episodeon a topic of your choice (link)v Join the discussion on social media (#MEC, #ETSI, #theStandardsPeople)
v Register for the NFV&MEC Plugtest program / events (link)v Join ISG MEC for design, standardization, and ecosystem development
activities (link)© ETSI 2022 – All rights
reserved

63

The larger
Telco World:
ETSI MEC and 5G© ETSI 2023 – All rights reserved

MEC Phase 2 – Study Item MEC in 5G (MEC 031)
The ETSI white paper MEC in 5G networks sets the scene for this study item
ISG MEC investigates the opportunities offered to MEC by the 5G system and its edge computing enablers
The scope includes the following
NSSF

NRF

UDM

PCF

NEF

MEC System

API framework,

MEC Orchestrator

3. Organization of MEC as an AF,
4. Pertinent interactions of MEC with (R)AN

AUSF

AMF

SMF

PCF

UPF

N6N

6

Virtualization
Virtualization
Infrastructure
Infrastructure
Data Network(LA/DN)

ServiceServiceService

MEC
MEC Platform
Platform
ManagerManager(R)ANAPP
MEC Platform

UE

N9

65

Distributed Host
Host Level
Level
Distributed

N4© ETSI 2023 – All rights reserved

System Level
System Level

1. C-plane interactions with 5GC,
2. Functional split between MEC and 5GC wrt.

3GPP enablers for MEC – Selection & re-location of UPF
NSSF

AUSF

UDM

NEF

AMF

SMF

PCF

Selection & re-location of UPF
MEC
AF

AF influence on traffic routing
Mobility event notifications
from SMF
Concurrent access to local andcentral DN

UE

RAN

UPF

DN

UPF

DN

© ETSI 2023 – All rights reserved

MEC as an AF (Application Function) can request the 5GC to• Select a local UPF near the target (R)AN node
• use the local UPF for PDU sessions of the target UE(s)• control the traffic forwarding from the local UPF so that the UL traffic matchingwith the traffic filters received from MEC (AF) is diverted towards MEC hosts
while other traffic is sent to the Central Cloud
66

3GPP enablers for MEC – Selection & re-location of UPF
Selection & re-location of UPF
NSSF

AUSF

UDM

NEF

AF influence on traffic routing
AMF

SMF

PCF

MEC
AF

Mobility event notifications
from SMF
Concurrent access to local andcentral DN

UE

RAN

UPF

DN

UE

RAN

UPF

UPF

DN

In case of UE mobility, the 5GC can• re-select a new local UPF more suitable tohandle application traffic identified by MEC (AF)• notify the AF about the new serving UPF

DN© ETSI 2023 – All rights reserved

67

3GPP enablers for MEC – AF influence on traffic routing
NSSF

AUSF

UDM

NEF

AMF

SMF

PCF

Selection & re-location of UPF
MEC
AF

AF influence on traffic routing
Mobility event notifications
from SMF
Concurrent access to local andcentral DN

UE

RAN

UPF

UPF

DN

DN

MEC as an AF can provide the following to 5GC• traffic filters identifying MEC applications deployed locallyon MEC hosts in Edge Cloud• the target UEs (one UE identified by its IP/MAC address, agroup of UE, any UE)• information about forwarding the identified traffic further
e.g. references to tunnels towards MEC hosts© ETSI 2023 – All rights reserved

68

3GPP enablers for MEC – Mobility event notifications
Selection & re-location of UPF
NSSF

AUSF

UDM

NEF

AF influence on traffic routing
AMF

SMF

PCF

MEC
AF

Mobility event notifications
from SMF
Concurrent access to local andcentral DN

UE

RAN

UPF

DN

UE

RAN

UPF

DN

© ETSI 2023 – All rights reserved

UPF

DN

5GC allows MEC as an AF• subscribe to UE mobility events that may affect traffic
forwarding to MEC applications• Receive notifications of UE mobility events affecting MEC
application instances
69

3GPP enablers for MEC - Concurrent access to local and central DN
Same UP session allows the UE to obtain content both from local server and central server
Service continuity enabled by IP address anchoring at the centralized UPF.
No impact on UE in case of Uplink Classifier (ULCL) option is used.
NSSF

AUSF

AMF

UE

RAN

UPF

UDM

SMF

UPF

DN

Edge Cloud for Ultra-low latency,
high reliability services© ETSI 2023 – All rights reserved

AF influence on traffic routing
Mobility event notifications
from SMF

NEF

PCF

Selection & re-location of UPF

MEC
AF

Concurrent access to local andcentral DN

DNCentral Clouda.k.a. Conventional “internet”

70

MEC harmonized architecture with SA6 EDGEAPP•

Joint white paper (*) from both ETSI and
3GPP officials•

3GPP TS 23.558 “Architecture for enabling
Edge Applications; (Release 17)” v1.1.0,
Oct. 2021 (informative Annex C)•

Alignment between 3GPP and ETSI MEC iscurrently in scope of eEDGEAPP in 3GPP
SA6 (ref. S6-211858 and TR 23.958).

Edge ComputingStandards

Notes:

Open Source•

In 5G, alignment of the 2 standards is the key.

•

General consensus to align ETSI and 3GPP in order to avoid duplication of work.

•

Anyway, alignment doesn’t mean equivalence

ETSI
MEC

MEC
in 5G

3GPP

(Note: ETSI MEC is Multi-access Edge Computing, thus including also Wi-Fi, fixed access, etc..)© ETSI 2023(*) Ref. ETSI White paper: “Harmonizing standards for edge computing - A synergized architecture leveraging ETSI ISG MEC and 3GPP specifications”, July 2021, link here71

MEC and NFV
a commonapproach to
management© ETSI 2023 – All rights reserved

MEC and NFV: MANO for the Telco Edge
MEP as a VNF:
must be running for any
other VNF/app to run

MEPM: EMS for MEP

MEPM is (part of) App’s
EMS
App can be a VNF: even if
it doesn’t know it© ETSI 2023 – All rights reserved

MEPM can be App’s
VNFM

73

MEC management: MEC-specific Operations
Mm1 required APIs:•

Application Package Management•

Application Lifecycle Management

Mm3 required APIs:•

Application Package Management•

Application Lifecycle Management•

Application Lifecycle Change Notification

These NFV semi-agnostic© ETSI 2023 – All rights reserved•

Information models designed to be feasible without NFV•Data models are NFV-consistent and compatible
74

MEC management: MEC-NFV Interaction
3 “Hybrid” Reference points identified as shown•

Mv3: at this point no specific changes to Ve-Vnfm-vnf are
expected (i.e. it can be used as is)•

Mv2: Necessary changes are being addressed by NFV IFA aspart of FEAT12 work (MECinNFV)•

Mv1: work identified, coordination plan is on-going

Additionally, MEC descriptor (AppD) must be linked to NFV
descriptor (VNFD). This has been addressed as part of Rel 3
work using Non-MANO artifact capability as defined in Annex B
of ETSI GS NFV-SOL 004 v. 2.5.1 and higher.

© ETSI 2023 – All rights reserved75Thank you for your attention©ETSI 2023 – All rights reserved

Follow us on:76Epilogue
ETSI ISG MEC is the leading voice in standardization & industry alignment around MEC
Key building block in the evolution of mobile-broadband networks, complementing NFV & SDN
Key enabler for IoT and mission-critical, vertical solutions
Widely recognized as one of the key architectural concepts and technologies for 5G
Can be used to enable many 5G use cases without a full 5G roll-out (i.e. with 4G networks)
Enable a myriad of new use cases across multiple sectors as well as innovative business opportunities