Mobile Edge Clouds · The new trend is hence towards mobile edge clouds and fog computing Applications can reside in different points in the infrastructure, depending on needs (e.g

Mobile Edge CloudsApplication Fields, Architecture and Opportunities

Dr. Patrick Marsch, Nokia Bell Labs, November 15th 2016

On the edge of a new era

2 © Nokia 2016

Outline

Motivation & Introduction

Example Applications

Architecture & Challenges

Ecosystem & Opportunities

Code::dive, November 15th 2016

3 © Nokia 2016

Internet

Transport network /aggregation

Core network

Radio access network

A classical cellular communications system


Base stations, handling all processing related to radio access

Backhaul

Authentication,billing etc.

ApplicationFixed mapping of communications

functionalities to physical entities

Strongly simplified

up to few km

10s to 100s of km

100s to 1000s of km

User devices

Highly specialized processing entities (often

hardware-based)

4 © Nokia 2016

The recent trend towards cloudification

Different function splits between cloud and edge possible

Much faster development

times

Cheaper dueto usage ofoff-the-shelf equipment

Betterresource

usage

Better scalability

Easier / faster reconfiguration

Easier network evolution

up to few km

10s to 100s of km

100s to 1000s of km

Backhaul

Core network, handling e.g. authentication, billing etc,

Sense > Analyze > Decide > Act

CoreTransportRadio

Virtualized resources

IT virtualization

Compute Storage Networking

Application

Virtualized network functions

User devices


5 © Nokia 2016

The problem: Latency and inefficient traffic routing

up to few km

10s to 100s of km

100s to 1000s of km

Backhaul

Core network, handling e.g. authentication, billing etc,

Application

User devices

Latency - Communication even among devices in proximity may be prone to large E2E latencies

Inefficient traffic routing –data is moved through network, even though it can be kept local

Security / Privacy - potentially sensitive data may be subjectto security attacks


6 © Nokia 2016

Why latency matters: Human senses and cyber-physical systems

Visual sensation to muscular reaction (web browsing)

~0.5s

Vestibulo-ocular reflex, reaction

from head to eye motion (AR/VR)

~7ms

Human haptic sense (remote control)

~1ms

1s 100ms 10ms 1ms

few ms

Physical interaction of

machines(here: ball handling)

<50,000km <5,000km <500km <50km

Max. distance of application

from user (considering

speed of light)

Human audio sense (synchr.

of video/audio)

~100ms


7 © Nokia 2016

Mobile edge cloud

(at base station)

The new trend is hence towards mobile edge clouds and fog computing

Applications can reside in different points in the infrastructure,

depending on needs (e.g. latency requirements)

Mobile edge clouds may be set up, and network functions moved

dynamically based on instantaneous requirements

If applications are distributed over many network near-edge entities and/or devices themselves, this is

coined fog computing

up to few km

10s to 100s of km

100s to 1000s of km

User devices

Central cloud

Application

Application

Mobile edge cloud

(at aggregation point)Application


Example MEC Applications

9 © Nokia 2016

Full automation

(SAE level 5*)

No automation

(SAE level 0*)

Example 1: Vehicular safety and efficiency

degree of driving assistance and automation

com

mu

nic

ati

on

s re

qu

irem

en

ts

Driver assistance

(SAE level 1*)

Partial automation

(SAE level 2*)

Conditional automation

(SAE level 3*)

High automation

(SAE level 4*)

Platooning

Traffic steering / lane changing

See-through driving

Vulnerable road user protection

* SAE levels according to https://cyberlaw.stanford.edu/files/publication/files/15CPB_AutonomousDriving.pdf

Augmented reality support

Electronic brake lights

https://cyberlaw.stanford.edu/files/publication/files/15CPB_AutonomousDriving.pdf

10 © Nokia 2016

Example 1: Vehicular safety and efficiency

• Most vehicular safety and efficiency use cases will be based largely on direct vehicular-to-vehicular comms. (V2V)

• But there are good reasons to compliment this with infrastructure communications based on MEC, e.g.

Provision of additional context

Processing of data from many vehicles,

analytics

Enable comms. beyond V2V range

Authentication support

Latency (e.g. <50ms) and routing efficiency


11 © Nokia 2016

Example 2: Local user-tailored real-time video distribution

• In local mass events, people typically demand highly correlated data

• The trend goes towards user-tailored media

• People expect real-time experience• Both can be provided most efficiently

via a Mobile Edge Cloud

At F1 Shanghai, 2016, Nokia demonstrated MEC involving about 100 LTE cells. Spectators accessed >1.2 TB of video data with delays << 1s


12 © Nokia 2016

Example 3: Mission-critical control (e.g. tele-diagnostics / tele-surgery)

Operating surgeon

Real-time video

processing

Surgical robot / patient

Wireless control with haptic force feedback(requiring few ms E2E latency)

Visual feedback to the surgeon for which patient motion is compensated

Images: DaVinci surgical robot, www.davincisurgery.com

• Tele-diagnostics / tele-surgery will bring affordable medical treatment to many more persons, especially in rural areas

• It requires ultra-low-latency communication and real-time video processing in proximity to operating surgeon and patient


13 © Nokia 2016

Example 4: Augmented Reality

Trade-off between latency and throughput

Local processing (e.g. gyroscope-based rendering)

Edge cloud processing (e.g. provision of context-aware content)

The lower the latency, the less throughput is needed due to more accurate content provision

Source: NTT Docomo 5G video

SportsEducation

Tourism

Shopping

Gaming

Knowledge support


14 © Nokia 2016

Data andcomputeheavy

Interactive

In summary, which application types can benefit most from MEC?

Real time

Lowest application latency end-to-end, for a real time user experience or critical communications

Maximum transaction rate between device and cloud for an interactive user experience

Private

Local communications for robust performance, privacy, and security

IoT

Real time insights from data exploited at the point of capture, minimum cloud ingress bandwidth

Local compute and storage for most demanding workloads to go mobile


Public

MEC Architecture and Challenges

16 © Nokia 2016

How Mobile Edge Computing works

Cellular network

Base station

Base station

Mobile EdgeComputing

Virtualization Infrastructure

Virtual Network Functions (VNF)

PlatformVNF

Application VNFs

Core Network

General architecture

Internet

Cellular network

Platform

Application (terminate)

Application (pass-thru)

Application termination vs. pass-thru

Device Internet

Possibly enterprise IT


17 © Nokia 2016

Venue (e.g. stadium, exhibition center)

Specific architecture involved in user-tailored video distribution

Local

video production

Local base station

Edge Video Orchestration

Core networkMobile Edge

Computing server


18 © Nokia 2016

MEC server platform and API as envisioned by ETSI (simplified)

ETSI Industry Specification Group for Mobile Edge Computing

• Co-founded by Nokia in October 2014

• Close to 70 members

A MEC platform API is foreseen that• Is application-agnostic• Provides interoperability• Enables portability

MEC Application Platform

MEC Application Platform Services

Traffic Offload Function

Radio Network Info Services

Comms. Services

Service Registry

VM

MEC App

VM

MEC App

VM

MEC App

VM

MEC App

MEC Hosting Infrastructure

Standardized function or interface

19 © Nokia 2016

MEC deployment options

Hotspots Cities Network-wide

•E.g. smart City initiatives, services for city residents etc.

•Deployed at metro aggregation sites and baseband hotels

•E.g. ubiquitous services that require a consistent experience / performance

•Deployment in radio clouds

• E.g. special services in stadiums, exhibitions, malls, enterprise campuses

•MEC deployed in small cell or macro base stations


20 © Nokia 2016

Challenges related to MEC

Mobility

In many cases, MEC apps need to move with the user

Performance, Resilience

The cellular system should not be affected by MEC presence

Portability

Some MEC applications need to work seamlessly across operator / vendor domains (e.g. automotive)

Security

3GPP and IT security needs have to be addressed simultaneously

Legal Aspects

MEC may be in conflict with net neutrality; lawful interception needs to be possible despite MEC



22 © Nokia 2016

What makes MEC application development special

Access to local context information (radio

context, user identity, user proximity etc.)

Very high transaction rate between device

and application possible

Possibility to utilize abundancy of local data

(e.g. sensor measurements, video

etc.)

Additional packaging and security

requirements, has to run on virtual machine

Has to be able to run in different locations in the network (e.g.

base station vs. aggregation cloud)


23 © Nokia 2016

MEC ecosystem and opportunities for different market players

Mobile network operators• Move from “bit-pipes” to

application hosts• Offer innovative new services• Tap into new business

opportunities beyond their traditional domain

Network vendors• Open up cellular

communications architecture• Differentiate and add value

through partnering with other players and enabling new services

Application service providers• Plethora of opportunities for offering

localized services (e.g. city tourism app)

Application developers• Develop MEC applications benefiting

from context information, higher transaction rates

• Provide virtualized network functions, provide orchestration frameworks

Entreprises• Consume network as a service• Digitize workflows, manage

facilities more efficiently


24 © Nokia 2016

The Nokia AppFactory and its benefits

Incubation with partners

and customers

On-boardingprocess

Legal framework

AppFactory

LifecycleSupport

Partner Engagement

ApplicationPackaging

andPublishing

CertificationTest Bench /

DevelopmentSupport

DeveloperCertification

Portal /App

Catalogue

Benefit for

application developers

application service

providers

Benefit for

mobile network operators

enterprises

25 © Nokia 2016

AppFactory in the value chain

Users

Users

Generate value and business

DeployCertify &

Publish

Application developer

AppFactoryApplication Steering

Start

Business Idea

Application service provider

App Catalogue

Development

…

Operator Network

Operator Network


26 © Nokia 2016

Summary

Motivation & Introduction

Example Applications

Architecture & Challenges



27 © Nokia 2016

Summary

Mobile edge cloud

(at base station)

The trend goes towards mobile edge clouds, mainly due to latency, data routing and privacy

reasons of novel applications and IoT

MEC will enable a plethora of opportunities for application service provides, application developers, operators and enterprises

ETSI is standardizing a MEC application platform to enable interoperability and

portability of MEC applications up to few km

10s to 100s of km

100s to 1000s of kmCentral cloud

Mobile edge cloud

(at aggregation point)

The Nokia AppFactory brings ecosystem partners together to drive innovation and

obtain fast time-to-revenue


Thank you for your attention!Dr. Patrick Marsch, Nokia Bell Labs, November 15th 2016

On the edge of a new era

Documents

Mobile Edge Clouds · The new trend is hence towards mobile edge clouds and fog computing Applications can reside in different points in the infrastructure, depending on needs (e.g