ETSI Multi-access Edge Computing (MEC)

A key enabler for IoT and mission-critical, vertical solutions

Nurit Sprecher
IoT World 2017
1
 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

 Proximity
 Ultra-low latency
 High bandwidth
 Real-time access to network
and context information
 Location awareness

2
 What Can We Provide at the Edge?

Unparalleled Quality of Experience

Contextualized services
Efficient utilization of the Radio and the Network resources
Innovative applications and services towards mobile
subscribers, enterprises and vertical segments

Security and
Real time Interactive Analytical Distributed
privacy

3
 MEC
Business Benefits

A new value chain and an Wider collaboration can help to drive favorable market
energized ecosystem, based on conditions for sustainable business for all players in the value
Innovation and business value chain.

New market segments (enterprises, verticals and subscribers);

Business transformation short innovation cycle;
revenue generation and differentiation

Video acceleration, augmented reality, connected vehicles,

A myriad of new use cases IoT analytics, enterprise services, network performance and
utilization optimization, retail, eHealth, etc.

4
 MEC Deployment Options

5
 MEC Benefits for Internet of Things (IoT)

MEC enables us to:

Pre-filter content, Take actions locally, Gain access to a real-

reducing the network satisfying demanding time network and
load and injected traffic requirements for low- context information as
into the cloud latency well as service analytics

Offer additional privacy Increase the reliability Run an M2M Gateway

and security of continuous function (e.g. as defined
operations by ETSI / OneM2M) as a
MEC application

6
 EXAMPLE OF USE CASES

7
 Augmented Reality

High bandwidth low latency content delivery

The MEC application analyses the output from a device’s camera and the precise
location; objects viewed on the the device camera are overlaid with local augmented
reality content.
Enables unique experience of a visitor to a museum or other (indoors or outdoors)
points of interest
Ensures low latency and high rate of data processing

8
 Edge video orchestration

Exciting live views for stadium visitors

Feeds live video streams from professional, stadium cameras mounted close to the
playing field (e.g. behind the goals) and provides additional player context to mobile
devices in real time.
With MEC, a media is produced, injected and played out locally.
Live feeds viewed on the LTE device are in sync with what the stadium visitor sees in
real time.

9
 Connected Vehicles

V2X Communication

Existing cloud services are extended into the highly distributed mobile edge
environment, leveraging the existing LTE connectivity.
The MEC application operates as a roadside unit for vehicle-to-infrastructure (V2I).
Road hazards can be recognized and warnings can be sent to nearby cars with
extremely low latency.
Enables a nearby car to receive data in a matter of milliseconds, and the driver to react
instantly.
10
 Video Analytics

Intelligent Video Analytics

Distributed live video streams analytics at the mobile edge

Events are triggered automatically (e.g. movement, missing objects, crowd, etc.);
enables fast detection and action triggering
Optimizes backhaul and transport capacity
Applicable to public safety, smart cities

11
 Local IoT Networks

Local IoT Networks

Amazon Greengrass extends the AWS (Amazon Web Services) cloud capabilities to the edge,
closer to the IoT devices.
Allows IoT devices to collect and analyze data closer to the source of information and
respond to local events quickly
Ensures low-latency and secured communication between IoT devices on local networks,
with additional privacy and significant cost savings
Applicable to Industrial IoT Link to: AWS Greengrass commercial
12
launch press event video
ETSI MEC
ETSI Multi-access Edge Computing

Pioneering open standards for

Edge Computing Leadership across ecosystem
• Since 2014
• First and still only international
SDO focused on this space

Broad participation
 ETSI MEC ISG: 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
on your networks

15
 ETSI MEC ISG: What Do We Specify? (2)

Key service-related APIs for

Private Wireless

Real-time Video

Virtual Reality
Augmented

Connected information exposure

Vehicles
…
Network
Reality
IoT

API API
API API API
ETSI MEC API
S S S Management
V
Platform
V V and
C C C Functionality
Orchestration
API
Virtualization Infrastructure

E.g. facilitate the running of

applications at the correct location
Application at the right time, application life
Enablement cycle management, rules, etc.

16
 MEC Reference Architecture
Let’s Make this More Specific

Based on use-case driven Requirements Spec (MEC002)

Platform Mgmt
(MEC010-1)

Radio Network
Information Service
(MEC012)

App. LCM
Location Service
(MEC010-2)
(MEC013)

UE Identity Service
(MEC014)

BW Mgmt Service
(MEC015)

App. Enablement
(MEC011)

17
We defined an architecture (MEC003) API Rules for MEC APIs (MEC009)
 Opening the Network Edge towards the
Developer Community

Developer community

APInnn MEC0nn
…

MEC023 Open API Representations

Service Service

MEC009 API Principles

ME app 1 ME app 2 ME app 3 ME app 4 ME app n

APIs: REST-HTTP style + Data model + JSON[&XML] formats + Message Bus Hooks
Richardson maturity model level 2..3
MEC012 MEC015
MEC013 MEC014 UE MEC011
Radio Network Bandwidth
Location API Identity API App Enablement
Information API Manager API

ETSI-defined Mobile Edge Services Mobile edge platform / Mp1

MEC0nn = ETSI MEC API specification API0nn = Third party ME service API specification

18 © ETSI 2016. All rights reserved

 Let’s reflect on the work status…
We’ve come a long way in just 2 years!
Published
 Technical Requirements,
including use cases (GS MEC
002)
 Framework and Reference
Architecture (GS MEC 003)
 MEC Proof of Concept (PoC)
Process (GS MEC-IEG 005)
 Service Scenario (GS MEC-IEG
004)
 Metrics (GS MEC-IEG 006)
End 2014
ETSI MEC phase 1
Coming Soon
 API Framework (GS MEC 009)
 Management APIs (GS MEC 010-
1, GS MEC 010-2, GS MEC 011)
 Service APIs (GS MEC 012, 013,
014, 015)
 UE Application Interface (GS MEC
016)
 Study on NFV Alignment (GS MEC
017)
 Study on Mobility Support(GS
MEC 018)
End 2016
But there is so much more to do!
Phase 2
 Evolution of Phase 1
 Filling gaps related to Lawful Intercept
 Studying possible new charging models
 Mobility
 Normative work for integration
with NFV
 From “Mobile” to “Multi-access”
 Wi-Fi
 Fixed Access
• From VMs to Containers
• Developer community
engagement
• Supporting partner organizations
as they move towards deployment
ETSI MEC phase 2
 OpenAPI Specification: API description files
(Swagger Specification)

OpenAPI 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 https://www.openapis.org/

• Accessibility → Wider adoption by the developers
• Adoption → Critical review and feedback

Where we are now

• ETSI Repository targeted for June 2017
• Available for: Radio Network Information (MEC012), Location (MEC013) and UE Application Interface
(MEC016)
• In-progress: Application Enablement (MEC011), UE Identity (MEC014) and Bandwidth Management
(MEC015)
Future Plans
• Complete set of APIs available via ETSI Repository
The ISG is currently exploring other approaches towards a more extensive engagement
with the developer community.

20
 Epilogue

MEC has created a great momentum in the industry, adding a new dimension and paving
the way towards new opportunities.
MEC is a great opportunity for existing and innovative applications to take advantage of
compute platform closer to the user which is rich with information not available elsewhere
in the network.
MEC is identified as a key enabler for IoT and mission-critical, vertical solutions
MEC is widely recognized in the telecommunications industry as one of the key
architectural concepts and technologies for 5G. Many of the use cases can be enabled with
Mobile Edge Computing prior to 5G
MEC enables a myriad of new use cases across multiple sectors as well as innovative
business opportunities.
•The work on release 2 will broaden the applicability of the MEC technology and will
render the MEC environment even more attractive to third-party application
developers.

21
 THANK YOU

Contact Details
Contact Details:

Nurit Sprecher
nurit.sprecher@nokia.com

ETSI MEC Support:

chantal.bonardi@etsi.org

Thank you!

22