ETSI MEC Hackathon Sept 2018

Intel® Network Edge Virtualization (NEV) SDKFor Multi-access Edge Computing (MEC)

Features

• Foundational Technology Platform

• Reference Libraries – MEC REST APIs and Optimized MEC data path Routing

• S1, SGi (EPC), WiFi traffic and Local Breakout support

• Sample Application / MEC Child Application Support

• VLAN Tags processing

• Wind River optimized telco cloud for MEC and vRAN Deployment

• Open Stack components

• Standalone deployment support with CentOS

• Intel® System Studio Suite

• Test Suites, Programming Guide, User Guide and App Notes

Release 1:

Hypervisor Wind River Titanium Server Components (on the Host Platform)

MECApps

MECServices

Release 2: Release 3:

CentOS-7

Intel ®Atom™

Processor C2000 Platform

Intel® XEON® Platform

Intel® Architecture: Software Only

MECApps

MECServices

Your Apps go here

ENB and EPC Emulators Telco Cloud NFV infrastructure Optimization and analysis tools

Intel, the Intel logo are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries.*Other names and brands may be claimed as the property of others.

ꭕ √ √

NEV SDK - ETSI MEC NFV ArchitectureDeveloping Open Standards Based Platforms

ETSI GS MEC 017

MEC deployment in LTE mobile networks

Example of MEC deployment option on S1 interface

• Re-routing part of the general packet radio service tunneling protocol-encapsulated (GTP) packets flowing through the S1-U interface to the desired EC applications.

• MEC host infrastructure resides on S1 interface and GTP interface remains at core network

MEC deployment in LTE mobile networks

Example of MEC deployment option on SGi interface

• Usage of distributed SGW and PGW

• GW’s running as VNFs on same NFVi as MEC platform

MEC data plane

eNBUE

SGW

MEC servicesMEC App

S1-U

SGi

MEC platform

Mp2

Mp1 Mp1

S1-C

PGW

MME

SGW/

PGW

WWW

SGi

Distributed CN

Centralized CN site

MEC Host

Standalone and Non-Standalone Scenario

• Current version of NEV SDK supports Rel. 14 LTE deployments - on S1u and SGi

• For 5G SA the NEV SDK will be updated to support the SA changes for both Data plane and Service based Architecture.

EPC

LTE eNB

NGC

gNB

CP and UP UP

CP and UP

EPC

eLTE eNB

NGC

gNB

CP and UP

CP and UP

CP and UP

Data Network

MEC AppsMEC Platforms

MEC AppsMEC Platforms

S1u Deployment

SGi Deployment

MEC AppsMEC Platforms

Data Network

UPF

UP

MEC AppsMEC Platforms

4G S1u Deployment

Non-standalone 5G Standalone 5G

MEC in 5G: Serverless Computing for Massive IoT

MEC APP 2 MEC Service

Traffic rules

control

Policy Service Registry

Data Plane

MEC APP

(service)

MEC App 1 DNS

handling

MEC Platform

MEC Host

1: Local handling at MEC App

MEC APP 2 MEC Service

Traffic rules

control

Policy Service Registry

Data Plane

MEC APP

(service)

MEC App 1 DNS

handling

MEC Platform

MEC Host

3: Reconfiguration to local MEC App 2

MEC APP 2MEC Service

Traffic rules control

Policy Service Registry

Data Plane

MEC APP

(service)

MEC App 1 DNS

handling

MEC Platform

MEC Host 2

4: Traffic steering to alternate MEC Host

MEC APP 2 MEC Service

Traffic rules control

Policy Service Registry

Data Plane

MEC APP(service)

MEC App 1 DNS handling

MEC Platform

MEC Host 1

AF

MEC APP 2

MEC Service

Traffic rules control

Policy Service Registry

Data Plane

MEC APP

(service)

MEC App 1

DNS handling

MEC Platform

MEC Host

Cloud

2: Local Breakout to Cloud

NEV SDK: Data Center Cloud and Cloud Native*

Opens Stack + MEC ManagerMEC Apps Policy and lifecycle

management mm5

App

NEV SDK

Kubernetes + MEC ManagerMEC Apps Policy and lifecycle

management mm5

NT

S M

icro

serv

ice

s P

od

OV

S/V

PP

Po

d

ME

C P

rod

uce

r A

pp

Po

d

Am

azo

n C

lou

d

Ad

ap

ter

Po

D

Azu

re C

lou

d

Ad

ap

ter

Po

D

ME

C C

on

sum

er

Ap

p P

od

NES Microservices Pod

Mm5 API

Mp1 API

ME

C C

on

sum

er

Ap

p P

od

MEC Service

VM

eMBB/Mobile devices

Base station

LTE

mMTC

IPv4

NBIOT/5G NR

Base station

AR compute local cloud

EPC

InternetOr from CUPS

IOT G/W and modules

Multi Access Edge Cloud interface to public cloud*

MEC GG adapter

MecApp

eMBB/Mobile devices

Base station

LTE

mMTC

IPv4

NBIOT/5G NR

Base station

AR compute local cloud

EPC

InternetOr from CUPS

IOT Hub Azure Resources

IOT G/W and modules

Multi Access Edge Cloud interface to public cloud*

MecApp

Amazon Green Grass Support on NEV SDK*

LTE/BTSDevices

MEC Platform

VM

NEV SDK Dataplane + API

MEC AR APP

VM

AWS Cloud

EPC

1

2

3

0

0

0

Data plane: Changes End-to-End Setup Flow

Internet

Tutorial – Hackathon NW Setup

Internet GW

Intel NEV SDK

AP GW

Saguna-1

10

.10

.10

.x

MGTSwitch

AP

10.10.10.4

10.10.10.5

10.10.10.1

10.10.10.3

Saguna-210.10.10.2

10.101.0.110.101.2.100 10.101.0.100

10.101.1.100

10.101.2.1

10.101.5.1

10.101.5.100

10.101.1.1

enp65s0f0

enp134s0f0 eno2

eno2enp65s0f0

enp65s0f0

enp65s0f0

enp65s0f0

enp134s0f0

enp136s0f0

enp136s0f2

enp136s0f3

enp24s0f0

93.57.17.110

Network Edge Services (NES)

REST API Services RegistryPlatform services

Network Traffic Services (NTS)

13

Data Traffic Configurations

Virtualization Management

Accelerated vSwtich/

OVS

VM

NES API

MEC Apps

VM

NES API

MEC Apps

Multi-Access Edge Computing (MEC) SDK

Windriver OVP(TIS)/CentOS 7.2 – RT Kernel

Data Plane Development Kit (DPDK)

Hardware abstraction – Logical ports

ETSI MEC Mp1

Intel® Xeon™ Platform

IP Traffic

S1 Traffic S1 Traffic

vENB vEPC Internet

IP TrafficIP Traffic

S1 Traffic

vENB InternetDistributedvSGW/vPGW

vEPCvMME, vHSS

IP Traffic IP Traffic

InternetWiFi Gateway Local Breakout

IP Traffic/ S1 Traffic

Control Node

Windriver Openstack

Mobile Edge platform Manager

ETSI MECMm5

L2(vlan)

IP

UDP

GTP-U

L2(vlan)

IP

Access Point

Mobile Edge Platform

HTTP Server

MEC AppMEC App Service

Agent App

External API

NES API

NES Thread

(User space Device Driver) NIS

MEC Manager

RedisDatabase

HTTP Server Process

NES Process

Redis Process

NTS

Service Registry

Legend

Dependence

Module

Scope of the Mobile Edge Platform

Scope of the NEV SDK High Level Design

Platform Producer

Linux Tap

MEC API MEC API MEC API

DNS Msq.

MEC APIMEC API

Modules run a root

NEV SDK components interaction

14

Local HostHiRedis Lib: Socket

DPDK Ring

HTTPS REST

HTTPSREST

HTTPSREST

HTTPSREST

Local hostHiRedis Lib: Socket

VirtIO Ring

FCGISocket

Web Socket

Web Socket

Web Socket

C API callUnix Socket

HTTPSREST

Data traffic

RESTful (MEC-like) API List

15

Procedure Name URL HTTP Verb Qualification

MM5 Application Configuration /appliance/v1/configuration POST Mandatory

MM5 Application Termination /appliance/v1/termination POST Mandatory

MM5 Manager Connection Establishment /appliance/v1/notifications/memanager GET Mandatory

MP1 Live Indicator /appliance/v1/live_apps POST Mandatory

MP1 Termination Indicator /appliance/v1/live_apps DELETE Mandatory

MP1 Connection Establishment /appliance/v1/notifications/{RefID} GET mandatory

MP1 Service Activation /appliance/v1/service POST mandatory

MP1 Service Deactivation /appliance/v1/service/{serviceId} DELETE optional

MP1 Service Discovery /appliance/v1/service GET mandatory

MP1 Service Subscription /appliance/v1/subscriptions/{serviceId} GET mandatory

MP1 Subscriptions Update /appliance/v1/subscriptions PUT mandatory

MP1 Service Unsubscription /appliance/v1/subscriptions/{serviceId} DELETE optional

MP1 Subscriptions Reset /appliance/v1/subscriptions DELETE optional

MP1 Service Data Update /appliance/v1/notifications POST mandatory

MP1 Traffic Rule Creation /appliance/v1/traffic POST mandatory

MP1 Traffic Rule Update /appliance/v1/traffic/{Traffic_Rule_ID} PUT mandatory

MP1 Traffic Rule Removal /appliance/v1/traffic/{Traffic_Rule_ID} DELETE mandatory

4 Types of ME Producer ApplicationsME SERVICES

1. TYPE 1. Host-borne. Platform generates service data, stores service data on the ME Platform, and provides them as Platform-Specific Services.

2. TYPE 2. VM-borne. ME App Service generates and stores service data but publishes it through the ME Platform; the ME Platform validates the format of published service data.

3. TYPE 3. VM-borne. ME App Service generates and stores service data; ME App establishes service subscription with ME App Service directly.

4. TYPE 4. VM-borne. ME App Service generates service data but stores data on the ME Platform, and provides them also as Platform-Specific Services like ME SERVICE TYPE 1.

What’re your requirements

Discussion

1) RNIS / Radio information for Industry 4.0 / Robotics Application

2) Path to commercialization

Resources

Links and Resources

• Intel NEV SDK

• https://networkbuilders.intel.com/network-technologies/nev

• Wireless Crypto Libs in DPDK

• http://www.dpdk.org/browse/dpdk-stable/tree/drivers/crypto

• Intel Parallel Studio

• https://software.intel.com/en-us/intel-parallel-studio-xe

Glossary• NFV – Network Function Virtualization

• VNF – Virtual Network Function

• SDN - Software Defined Network

• 3GPP – 3G Partnership Project

• RAN – Radio Access Network

• vRAN – Virtualized Radio Access Network

• FlexRAN – Flexible Radio Access Network

• SDK – Software Development Kit

• EPC – Evolved Packet Core

• MEC – Multi-Access Edge Compute

• NEV – Network Edge Virtualization

• eNodeB / eNB – Enhanced NodeB (BaseStation)

• UE – User Equipment (Device)

• COTS – Commercial Off The Shelf

• CPRI – Common Public Radio Interface

• RRH – Remote Radio Head

• FPGA – Field Programmable Gate Array (Accelerator)

• PHY – Physical Layer (L1)

• MAC – Medium Access Control (L2)

• RLC – Radio Link Control (L2)

• RRC – Radio Resource Control (L3)

• PDCP – Packet Data Control Protocol (L3)

• TNL – Transport Network Layer

• RF – Radio Front End

• SON – Self Organizing Network

• OAM - Operation Administration And Maintenance

• QAT – Quick Assist Technology

• DPDK – Data Plane Development Kit

• DL – DownLink (eNodeB to UE)

• UL – UpLink (UE to eNodeB)

• OAMP – Operations, Administration, Maintenance and Provisioning

• NIC – Network Interface Card

• VM – Virtual Machine

• KVM – Kernel Virtual Machine

• 5G TF – 5G Technical Forum

• 5G NR – 5G New Radio

• IA – Intel® Architecture

• NDA – Non Disclosure Agreement

• ETSI - The European Telecommunications Standards Institute

Disclaimer

Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at [intel.com].

Cost reduction scenarios described are intended as examples of how a given Intel- based product, in the specified circumstances and configurations, may affect future costs and provide cost savings. Circumstances will vary. Intel does not guarantee any costs or cost reduction.

Intel, the Intel logo, are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries.

*Other names and brands may be claimed as the property of others.

© Intel Corporation

5G Business Driver : Data is the new Oil

23

Source: Cisco GCI, 2015-2020

Bandwidth and Latency Requirements (5G Use cases)

© GSMA Intelligence (2014)

24