enabling 5g networks & multi-access edge cloud · host i/o heavy vnfs/microservices dynamic,...

1

ENABLING 5G NETWORKS &MULTI-ACCESS EDGE CLOUD

OĞUZ SUNAYCHIEF ARCHITECTOPEN NETWORKING FOUNDATION

5G & NETWORK TRANSFORMATION CONFERENCE– OCTOBER 17, 2018

2

OUTLINE

WHY DO TELCOS NEED AN EDGE CLOUD?

M-CORDAS THE MOBILE EDGE

M-CORDNEXT STEPSM-CORD & ORAN

EVOLVING ONF’S OPEN SOURCE CORE

ONF’SOPEN EDGE CLOUDBOTTOM UP PERSPECTIVE

KEY TAKEAWAYS

ONF’SOPEN EDGE CLOUDTOP-DOWN PERSPECTIVE

3

WHY DO TELCOS NEED AN EDGE CLOUD?

4

CELLULAR EVOLUTIONENABLEMENT AND SCALING OF VOICE AND MBB IN THE FIRST 40 YEARS

1G 2G 3G 4G

AMPS, NMT, TACS

Analog Voice

GSM/GPRS, D-AMPS, cdmaOne

Digital Voice+

Basic Data<0.5 Mbps

CDMA2000 /EV-DO

WCDMA/HSPA+TD-SCDMA

Mobile Broadband63+ Mbps

LTE, LTE-AFaster

Mobile Broadband300+ Mbps

1980s 1990s 2000s 2010s 2020s

5G

NR & NG-COREExtreme

Mobile Broadband, Massive MTC, URLLC

1+ Gbps

5

WHY DO TELCOS NEED THE EDGE CLOUD?WHAT USE CASES NEED THE EDGE?

LAW OF PHYSICS

LAW OF ECONOMICS

LAW OF THE LAND

6

M-CORD AS THE MOBILE EDGE

7

M-CORD AS THE MOBILE EDGEM-CORD PILLARS

CentralCloud

Utilizing COTS servers and white box switches

Hosting vRAN, core network VNFs and value-added cloud services using cloud principles

Programmable leaf-spine fabric that can also host I/O heavy VNFs/microservices

Dynamic, automated, policy-driven programmatic control of the RAN

Open Source platform for dynamic instantiation and control of subscriber-based services and service chains

Native, open source 3GPP Core Network VNFs, and in the future, open source vRAN components

8

M-CORD AS THE MOBILE EDGEENABLING DISAGGREGATED, DISTRIBUTED RAN, CORE AND END-USER SERVICES

RUUE/CPE DU CU-U

RIC Near-RT

Edge Services

UDM

AUSF

SMF AMF

PCF

UPF

Telco Services

CU-C

GLOBAL ORCHESTRATOR

ANTENNA SITES

CELL SITES

M-CORDCENTRAL

CLOUD

EXTERNALSERVICES

UPFUPF

NG CORE CP

RTT ~<1ms ~1ms ~10-100ms ~>500ms

~10-30ms

~30-100ms

RTT Requirements from AT&T

DISAGGREGATED RANDISAGGREGATED CORE

DISTIBUTED CORE

PROGRAMMABLE RAN

DISTIBUTED SERVICES

DISTRIBUTED RAN

9

M-CORD TODAY: DEMO AT MWCA 2018

Kubernetes

XOS

Core CP #1

Core CP #2

Core UP #2

TelcoApps

RAN Control

Fabric Control

Networking Apps

Ne

two

rk a

nd

In

fras

tru

ctu

re

Sta

te

ONAP

CentralCloud

XOS

Core Control

ONOS

Core UP #1.p4

ONAP

Analytics

Docker

Istio

OTTApps

Envoy Prometheus

Grafana

AnalyticsONOS

Fabric.p4 Fabric.p4

Fabric.p4Fabric.p4

10

M-CORD TODAY: DEMO AT MWCA 2018

M-CORD 6.0Architecture built on open

source CORD 6.0

P4 FabricUtilizing a p4-programmable

fabric

Cloud NativeAll containerized, utilizing Kubernetes,

Prometheus, Grafana, and Helm

Closed Loop AnalyticsDemonstrating closed loop

analytics and automation

ONAP IntegrationDemonstrating integration with ONAP

for both design-time and run-time

Open Source EPCHosting open source, containerized

disaggregated EPC + services

E2E Network SlicingExhibiting ONOS-based programmable

end-to-end network slicing

Service MeshDemonstrating OTT services

connection management with Istio

Comprehensive, Highly Integrated DemoHighlighting the Power of Open Source

11

M-CORD: NEXT STEPS

12

M-CORD & ORAN

13

ORAN ARCHITECTURE AND COMPONENTSSIMPLIFIED VIEW

13

RadioUnit

DistributedUnit

CentralizedUnit-UP

CentralizedUnit-CP

ORAN NearRT Controller

CoreNetwork

Orchestrator

ORAN Specified APIs3GPP Specified

Base Station

14

OPEN SOURCE ORAN AT ONFWHAT ONF CAN DO?

14

Open Source ORAN Near RT RIC

Open Source Disaggregated Centralized Unit Stack (Containerizedand potentially P4-based)

Open Source Distributed Unit Stack andWhitebox Implementation of Distributed Unit

RadioUnit

DistributedUnit

CentralizedUnit-UP

CentralizedUnit-CP


CoreNetwork

Orchestrator


15

OPEN SOURCE ORAN AT ONFWHY SHOULD ONF DO IT?

15

An ONOS-basedxRAN Controller

already exists

ONF can leverage themomentum from its open source EPC to engage the community

ONF is already in talks with one of its partners to open source a significant component of this

Open Source Disaggregated Centralized Unit Stack (Containerizedand potentially P4-based)

Open Source Distributed Unit Stack andWhitebox Implementation of Distributed Unit

RadioUnit

DistributedUnit

CentralizedUnit-UP

CentralizedUnit-CP


CoreNetwork

Orchestrator


Open Source ORAN Near RT RIC

16

M-CORD’S OPEN SOURCE CORE

17

CORE NETWORK DISAGGREGATION

CP

UP

EPC/NG-CORE VNFs running on COTS Servers and SDN Switches

MME HSS SGWC

PCRF

PGWU

SGWU

PGWC

Different network slices may have different subsets of the EPC/NG-CORE VNFs instantiated at the edge.

18

CORE NETWORK EVOLUTIONEPC FOR LTE WITH UNIFIED S/PGW

LTE RAN

SPGW-U

HSS

Telco Internal/ExternalPacket Data Network

MME

PCRF

SPGW-C

19

CORE NETWORK EVOLUTIONONF IMPLEMENTATION: PROGRAMMABLE CORE

LTE RAN

SPGW-U

HSS


MME

PCRF

Core Controller

SPGW-C

Subscriber-BasedBilling/Charging

PoliciesSlicing Controller

Subscriber-BasedSlice Selection

Policies

ONF Specified APIs3GPP Specified

Disaggregated, containerized EPC components available today

ONOS-basedSlicing Controlavailabletoday

ONOS-based Core Control available today

20

CORE NETWORK EVOLUTIONLTE EPC TO 5G NG-CORE

MME AMF AUSF

SPGW-C SMF

PCRF PCF

HSS UDM

SPGW-U UPF

NSSF

21

CORE NETWORK EVOLUTIONNEXT STEPS: EVOLUTION TO 5G NG CORE

5G RAN

UPF

UDM


PCF

Core Controller

SMF

Subscriber-BasedBilling/Charging

Policies

AUSF

Slicing Controller

NSSF

AMFONF Specified APIs3GPP Specified

22

ONF & OPEN EDGE CLOUD

BOTTOM-UP PERSPECTIVE

23

ONF’S OPEN EDGE CLOUD VISION

23

EDGECLOUD

EDGECLOUD

PUBLIC / CENTRALCLOUD

Multi-Access Support

Support For Service Graphs Spanning Multi-Clouds (Edge + Public, Edge 1 + Edge 2 + Public, etc.)

24

OPEN EDGE CLOUDINITIAL PLANNED POC

24

25


TOP-DOWN PERSPECTIVE

26

CLOUD SERVICE MODELS FOR THE TELCO EDGE

COMPUTEINFRASTRUCTURE

NETWORKINGFABRIC

ACCESSNODES

Edge Cloud Services Controller (XOS)

VMs Containers

OpenStack KubernetesSDN Controller (ONOS)

VOLTHA

SDN Controller (ONOS)

VO

LT

xRA

N

Pro

gRA

N

vR

ou

ter

PaaS APIs

Telco’s Own Services 3rd Party Services MVNO Services

RANOLT

Mu

ltic

ast

Fab

ric

Co

ntr

ol

DH

CP

VT

N

Co

ntr

ol

27

PAAS FOR THE OPEN EDGE CLOUD

• Using NB PaaS APIs, Edge Cloud Services Controller provides isolation from the

underlying infrastructure as well as from virtualization, lifecycle management,

networking and connectivity platforms.

• Using PaaS APIs, the controller allows its own developers, 3rd parties and MVNOs

to create, onboard, instantiate and manage container/VM/P4-based service &

service graphs, collect analytics data, utilize provided ML libraries, and connect to

public clouds, etc.

28

CONNECTIVITY-AS-A-SERVICE

XOS

ONOS KUBERNETES

PaaS APIs

3rd PARTY APP

CORE UP CORE CP

29

TELEMETRY-AS-A-SERVICE

XOS

COMPUTE & STORAGE INFRASTRUCTURE

SDN FABRIC ACCESS NETWORK

TELEMETRY

PaaS APIs

3rd PARTY APP

30

SERVICE MESH-AS-A-SERVICE

XOS

ONOS

KUBERNETES

PaaS APIs

3rd PARTY APP

3rd PARTY APP CONTAINERS

ISTIO

31

LEARNING-AS-A-SERVICE

XOS

ONOS KUBERNETES

PaaS APIs

3rd PARTY APP

ML ENGINE INFER ENGINE

ML LIBRARY

32


EXAMPLE USE CASES

33

OPEN EDGE CLOUD USE CASE

TelcoCloud

EDGE CLOUD

EDGE CLOUD

TURK TELEKOMCENTRAL CLOUD

PUBLICCLOUD

TURK TELEKOM CORE CP

VEOML

TURK TELEKOM CORE UP VEO

INFER

VEOIOT HUB

TURK TELEKOM CORE UP VEO

INFER

VEOIOT HUB

AUTONOMOUS DRIVING

OWNED BY EDGE CLOUDPROVIDER OWNED BY CONNECTIVITY

PROVIDER

OWNED BY PUBLIC CLOUD PROVIDER

OWNED BY OTT SERVICEPROVIDER

34

OPEN EDGE CLOUD USE CASE

TelcoCloud

EDGE CLOUD

EDGE CLOUD

TURK TELEKOMCENTRAL CLOUD

PUBLICCLOUD

AT&T CORE CP

MACHINELEARNING

PUBLIC SAFETY

TelcoCloud

OWNED BY EDGE CLOUDPROVIDER

OWNED BY CONNECTIVITYPROVIDER

OWNED BY PUBLIC CLOUD PROVIDER

OWNED BY THECITY

TURK TELEKOM CORE CP

MACHINELEARNING

INFERENCE

VIDEOPROCESSING

TURK TELEKOM CORE UP

AUTOALERT

TURK TELEKOMIMS

INFERENCE

VIDEO PROCESSING

TURK TELEKOM CORE UP

AUTOALERT

TURK TELEKOMIMS

35

KEY TAKEAWAYS

36

KEY TAKEAWAYS

CORD enables telcos monetize their assets at the network edge in new ways that are in line with today’s cloud offerings.

An edge cloud platform should provide multi-tenancy in two dimensions: telco end-user subscribers and edge cloud PaaS customers.

An edge cloud is necessary to start offering delay-sensitive services to end users &

enterprises.

The edge cloud architecture needs to be inherently different than today’s cloud. It is

a distributed computing paradigm where connectivity meets the cloud.

ONF’s CORD leverages commodity hardware, disaggregation, virtualization

and programmability to provide telcos with a compelling solution.

Turk Telekom and Argela are key partners in ONF. We look forward to continued significant contributions to the platform developments from Argela and their lead in lab/field trials at Turk Telekom for M-CORD and Open Edge Cloud.

ONF’s open edge cloud aims to enable telco-offered PaaS to 3rd party application developers: Connectivity-as-a-Service, Service Mesh-as-a-Service, Telemetry-as-a-Service are example offerings.

37

THANK YOU

enabling 5g networks & multi-access edge cloud · host i/o heavy vnfs/microservices dynamic,...

Documents