1. ETSI Multi-access Edge Computing (MEC)
A new environment for innovation and value creation
Sami Kekki, Huawei Technologies Finland
8th FOKUS FUSECO Forum, Berlin, 9. – 10. November, 2017

2. Multi-access Edge Computing (MEC) An Environment for Innovation and Value Creation
… as in Real Estate, it’s about just 3 things: Location, Location, Location
Cloud computing and an IT service environment at the network edge.
Edge is opened for 3rd party applications.
Proximity
Ultra-low latency
High bandwidth
Real-time access to network and context information
Location awareness

3. What Can We Provide at the Edge?
Unparalleled Quality of Experience
Contextualized services
Efficient utilization of the Radio and the Network resources
Enablers for innovative applications and services towards mobile subscribers, enterprises and vertical segments
Real time
Interactive
Analytical
Security and privacy
Distributed

4. ETSI Multi-access Edge Computing
Pioneering open standards for Edge Computing
Since 2014
First and still only international SDO focused on this space
Leadership across ecosystem
Broad participation 4

5. MEC Business Benefits
A new value chain and an energized ecosystem, based on Innovation and business value
Wider collaboration can help to drive favorable market conditions for sustainable business for all players in the value chain.
The opportunity is there; get into the value chain and take your piece
Business transformation
New market segments (enterprises, verticals and subscribers);
short innovation cycle;
revenue generation and differentiation
We are engineers, not marketeers. You can spot new opportunities
A myriad of new use cases
Video acceleration, augmented reality, connected vehicles, IoT analytics, enterprise services, network performance and utilization optimization, retail, eHealth, etc.
Come and pitch new ideas to us

6. ETSI ISG MEC: What Do We Specify? (1)
We don’t make any
of this work
We make it all work on your Generic Edge infrastructure
And we help you expose the cool new things apps can do in your networks

7. ETSI ISG MEC: What Do We Specify? (2)
Key service-related APIs for information exposure
IoT
Augmented Reality
Connected Vehicles
Private Wireless Network
Real-time Video
Virtual Reality …
API
API
Management and
Orchestration
API
API
API
Platform Functionality
Application Enablement by platform functions
API
ETSI MEC
API
Service
Service
Service
API
Virtualization Infrastructure
E.g. facilitate the running of applications at the right location at the right time, application life cycle management, rules, requirements

8. MEC Reference Architecture Let’s Make this More Specific
The MEC reference architecture was specified in GS MEC003, based on use case -driven Requirements in GS MEC002
Platform Mgmt.
(MEC010-1)
-Radio Network Information (MEC012)
-Location (MEC013)
-UE Identity (MEC014)
-BW Management Service (MEC015)
UE Application Interface (MEC016)
App. LCM
(MEC010-2)
App. Enablement
(MEC011)

9. Opening the Network Edge towards the Developer Community
ME app 4
Service
APInnn
ME app n
Service
MEC0nn
MEC009 API Principles
MEC023 Open API Representations …
ME app 1
ME app 2
ME app 3
APIs: REST-HTTP style + Data model + JSON[&XML] formats + Message Bus Hooks Richardson maturity model level 2..3
MEC012 Radio Network Information API
MEC013 Location API
MEC014 UE Identity API
MEC015 Bandwidth Manager API
MEC016 UE App Interface API
MEC011 App Enablement
ETSI-defined Mobile Edge Services
Mobile edge platform / Mp1
MEC0nn
= ETSI MEC API specification
API0nn
= Third party ME service API specification
Specs:
API definitions: forge.etsi.org
© ETSI All rights reserved

10. OpenAPI Specification: API description files (aka Swagger Specification)
Open source framework for defining & creating RESTful APIs
OpenAPI Specification compliant API description file
Inherently includes MEC data structure definitions
Machine readable facilitating content validation
Allows autocreation of stubs for both service client & server
Motivation with ISG: specification accessibility and validation
Accessibility → Wider adoption by the developers
Adoption → Critical review and feedback
Where we are now
ETSI Repository is live:
MEC011, 12, 13, 14, 15 and 16 are all there
Future Plans
Complete set of APIs available via ETSI Repository, ISG organized to handle feedback in a timely manner
The ISG is currently exploring other approaches towards a more extensive engagement with the developer community.

11. Let’s reflect on the work status…
We’ve come a long way in just 2 years!
Published
Technical Requirements (MEC 002)
Framework and Reference Architecture (MEC 003)
MEC Proof of Concept (PoC) Process (MEC-IEG 005)
Service Scenarios (MEC-IEG 004)
Metrics (MEC-IEG 006)
API Framework (MEC 009)
Management APIs (MEC 010-1)
Management APIs (MEC 010-2)
Application Enablement (MEC 011)
Service APIs (MEC 012, 013, 014, 015)
UE Application Interface (MEC 016)
Study on Mobility Support (MEC 018)
Coming Soon
Study on MEC in NFV (MEC 017)
Phase 2
Evolution of Phase 1 and closing open items
Lawful Intercept
Charging
Application Mobility
Normative work for integration with NFV
From “Mobile” to “Multi-Access”
Wi-Fi
Fixed Access
From VMs to Containers
From a host to a distributed edge
MEC Testing Framework (MEC 025)
Developer community engagement
Supporting partner organizations as they move towards deployment
End 2014
ETSI MEC phase 1
ETSI MEC phase 2 …
© ETSI All rights reserved

12. MEC in NFV environment – Cross ISG effort
Today MEC is for any virtualization environment
MEC in NFV work produces the necessary adjustments to
run MEC apps and MEC platform in NFVI
where they appear as VNFs towards MANO
MEC in NFV is to maximise the benefits from the investments into virtualization
Key issues:
Re-use of NFV MANO
Split between Orchestrators
Delegation of App VNF LCM to VNFM
Dissolution of MEC host
Study item is about to get complete
Coordination & collaboration with ISG NFV: both ISGs are committed to normative work
DRAFT

13. Epilogue
In just over 2 years of activity ETSI MEC ISG gained significant momentum and is accelerating the industry
Key building block in the evolution of mobile-broadband networks, complementing NFV and 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.
Inter-operable and implementable API specifications the key technical asset today.
The work on Phase 2 will extend the applicability of the MEC technology and render the MEC environment even more attractive to third-party application developers.

14. Thank you! THANK YOU Contact Details
Presenter/ISG vice-chair: Sami Kekki,
ISG Chair: Alex Reznik,
ETSI Support Officer: Chantal Bonardi,
Thank you!