ENABLING 5G NETWORKS & MULTI-ACCESS EDGE CLOUD

Transcription

1 ENABLING 5G NETWORKS & MULTI-ACCESS EDGE CLOUD OĞUZ SUNAY CHIEF ARCHITECT OPEN NETWORKING FOUNDATION 5G & NETWORK 1 TRANSFORMATION CONFERENCE OCTOBER 17, 2018

2 OUTLINE WHY DO TELCOS NEED AN EDGE CLOUD? M-CORD NEXT STEPS M-CORD & ORAN EVOLVING ONF S OPEN SOURCE CORE ONF S OPEN EDGE CLOUD TOP-DOWN PERSPECTIVE M-CORD AS THE MOBILE EDGE ONF S OPEN EDGE CLOUD BOTTOM UP PERSPECTIVE KEY TAKEAWAYS 2

3 3 WHY DO TELCOS NEED AN EDGE CLOUD?

4 CELLULAR EVOLUTION ENABLEMENT AND SCALING OF VOICE AND MBB IN THE FIRST 40 YEARS 1980s 1990s 2000s 2010s 2020s 1G 2G 3G 4G 5G 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 Broadband 63+ Mbps LTE, LTE-A Faster Mobile Broadband 300+ Mbps NR & NG-CORE Extreme Mobile Broadband, Massive MTC, URLLC 1+ Gbps 4

5 WHY DO TELCOS NEED THE EDGE CLOUD? WHAT USE CASES NEED THE EDGE? LAW OF PHYSICS LAW OF ECONOMICS LAW OF THE LAND 5

6 6 M-CORD AS THE MOBILE EDGE

7 M-CORD AS THE MOBILE EDGE M-CORD PILLARS 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 Utilizing COTS servers and white box switches Hosting vran, core network VNFs and valueadded cloud services using cloud principles Dynamic, automated, policy-driven programmatic control of the RAN Programmable leaf-spine fabric that can also host I/O heavy VNFs/microservices Central Cloud 7

8 M-CORD AS THE MOBILE EDGE ENABLING DISAGGREGATED, DISTRIBUTED RAN, CORE AND END-USER SERVICES DISAGGREGATED RAN GLOBAL ORCHESTRATOR DISAGGREGATED CORE ~30-100ms ~10-30ms RIC Near-RT CU-C PROGRAMMABLE RAN Edge Services UDM AUSF SMF PCF AMF NG CORE CP UE/CPE RU DU CU-U UPF UPF UPF DISTIBUTED SERVICES ANTENNA SITES DISTRIBUTED RAN CELL SITES DISTIBUTED CORE Telco Services M-CORD CENTRAL CLOUD RTT ~<1ms ~1ms ~10-100ms ~>500ms EXTERNAL SERVICES 8 RTT Requirements from AT&T

9 Network and Infrastructure State M-CORD TODAY: DEMO AT MWCA 2018 XOS ONAP RAN Control Fabric Control Core Control Networking Apps Istio Analytics Grafana ONOS ONOS Core CP #1 Core CP #2 Core UP #2 Telco Apps Analytics Envoy OTT Apps Prometheus XOS Kubernetes Docker Core UP #1.p4 Fabric.p4 Fabric.p4 Central Cloud ONAP Fabric.p4 Fabric.p4 9

10 M-CORD TODAY: DEMO AT MWCA 2018 M-CORD 6.0 Architecture built on open source CORD 6.0 P4 Fabric Utilizing a p4-programmable fabric Cloud Native All containerized, utilizing Kubernetes, Prometheus, Grafana, and Helm Service Mesh Demonstrating OTT services connection management with Istio Comprehensive, Highly Integrated Demo Highlighting the Power of Open Source Open Source EPC Hosting open source, containerized disaggregated EPC + services Closed Loop Analytics Demonstrating closed loop analytics and automation ONAP Integration Demonstrating integration with ONAP for both design-time and run-time E2E Network Slicing Exhibiting ONOS-based programmable end-to-end network slicing 10

11 11 M-CORD: NEXT STEPS

12 12 M-CORD & ORAN

13 ORAN ARCHITECTURE AND COMPONENTS SIMPLIFIED VIEW Orchestrator Base Station ORAN Specified APIs 3GPP Specified Radio Unit ORAN Near RT Controller Distributed Unit Centralized Unit-CP Centralized Unit-UP Core Network 13 13

14 OPEN SOURCE ORAN AT ONF WHAT ONF CAN DO? Open Source ORAN Near RT RIC Orchestrator Open Source Disaggregated Centralized Unit Stack (Containerized and potentially P4-based) ORAN Specified APIs 3GPP Specified Radio Unit ORAN Near RT Controller Distributed Unit Open Source Distributed Unit Stack and Whitebox Implementation of Distributed Unit Centralized Unit-CP Centralized Unit-UP Core Network 14 14

15 15 15 ORAN Specified APIs 3GPP Specified OPEN SOURCE ORAN AT ONF An ONOS-based xran Controller already exists Radio Unit WHY SHOULD ONF DO IT? Open Source ORAN Near RT RIC ORAN Near RT Controller Distributed Unit Orchestrator Open Source Distributed Unit Stack and Whitebox Implementation of Distributed Unit ONF is already in talks with one of its partners to open source a significant component of this Open Source Disaggregated Centralized Unit Stack (Containerized and potentially P4-based) Centralized Unit-CP Centralized Unit-UP ONF can leverage the momentum from its open source EPC to engage the community Core Network

16 16 M-CORD S OPEN SOURCE CORE

17 CORE NETWORK DISAGGREGATION EPC/NG-CORE VNFs running on COTS Servers and SDN Switches MME HSS SGW C PCRF PGW C CP PGW U UP SGW U Different network slices may have different subsets of the EPC/NG-CORE VNFs instantiated at the edge. 17

18 CORE NETWORK EVOLUTION EPC FOR LTE WITH UNIFIED S/PGW HSS PCRF SPGW-C SPGW-U Telco Internal/External Packet Data Network LTE RAN MME 18

19 Subscriber-Based Slice Selection Policies Slicing Controller CORE NETWORK EVOLUTION ONF IMPLEMENTATION: PROGRAMMABLE CORE HSS PCRF Disaggregated, containerized EPC components available today ONOS-based Core Control available today Core Controller Subscriber-Based Billing/Charging Policies ONOS-based Slicing Control available today LTE RAN SPGW-C MME SPGW-U Telco Internal/External Packet Data Network ONF Specified APIs 3GPP Specified 19

20 CORE NETWORK EVOLUTION LTE EPC TO 5G NG-CORE MME AMF AUSF SPGW-C PCRF HSS SPGW-U SMF PCF UDM UPF NSSF 20

21 CORE NETWORK EVOLUTION NEXT STEPS: EVOLUTION TO 5G NG CORE UDM NSSF Slicing Controller PCF Core Controller Subscriber-Based Billing/Charging Policies AUSF SMF UPF Telco Internal/External Packet Data Network 5G RAN 21 AMF ONF Specified APIs 3GPP Specified

22 ONF & OPEN EDGE CLOUD BOTTOM-UP PERSPECTIVE 22

23 ONF S OPEN EDGE CLOUD VISION EDGE CLOUD PUBLIC / CENTRAL CLOUD Multi-Access Support EDGE CLOUD Support For Service Graphs Spanning Multi-Clouds (Edge + Public, Edge 1 + Edge 2 + Public, etc.) 23 23

24 OPEN EDGE CLOUD INITIAL PLANNED POC 24 24

25 ONF & OPEN EDGE CLOUD TOP-DOWN PERSPECTIVE 25

26 VOLT xran ProgRAN VTN Control Fabric Control DHCP Multicast vrouter CLOUD SERVICE MODELS FOR THE TELCO EDGE Telco s Own Services 3 rd Party Services MVNO Services Edge Cloud Services Controller (XOS) PaaS APIs SDN Controller (ONOS) SDN Controller (ONOS) OpenStack Kubernetes VOLTHA VMs Containers OLT ACCESS NODES RAN NETWORKING FABRIC COMPUTE INFRASTRUCTURE 26

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, 3 rd 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. 27

28 CONNECTIVITY-AS-A-SERVICE XOS 3 rd PARTY APP PaaS APIs ONOS KUBERNETES CORE UP CORE CP 28

29 TELEMETRY-AS-A-SERVICE XOS 3 rd PARTY APP PaaS APIs TELEMETRY COMPUTE & STORAGE INFRASTRUCTURE SDN FABRIC ACCESS NETWORK 29

30 SERVICE MESH-AS-A-SERVICE XOS 3 rd PARTY APP PaaS APIs ONOS ISTIO KUBERNETES 3 rd PARTY APP CONTAINERS 30

31 LEARNING-AS-A-SERVICE XOS 3 rd PARTY APP PaaS APIs ONOS KUBERNETES ML ENGINE INFER ENGINE ML LIBRARY 31

32 ONF & OPEN EDGE CLOUD EXAMPLE USE CASES 32

33 OPEN EDGE CLOUD USE CASE AUTONOMOUS DRIVING OWNED BY OTT SERVICE PROVIDER OWNED BY EDGE CLOUD PROVIDER VEO IOT HUB Telco Cloud OWNED BY CONNECTIVITY PROVIDER TURK TELEKOM CORE UP VEO INFER TURK TELEKOM CORE CP TURK TELEKOM CORE UP VEO IOT HUB EDGE CLOUD VEO INFER EDGE CLOUD OWNED BY PUBLIC CLOUD PROVIDER TURK TELEKOM CENTRAL CLOUD VEO ML 33 PUBLIC CLOUD

34 OPEN EDGE CLOUD USE CASE PUBLIC SAFETY OWNED BY THE CITY VIDEO PROCESSING OWNED BY EDGE CLOUD PROVIDER AUTO ALERT Telco Cloud OWNED BY CONNECTIVITY PROVIDER TURK TELEKOM CORE UP INFERENCE TURK TELEKOM IMS AT&T CORE CP TURK TELEKOM TURK TELEKOM CORE UP TURK TELEKOM VIDEO PROCESSING EDGE IMS CLOUD INFERENCE EDGE CLOUD AUTO ALERT OWNED BY PUBLIC CLOUD PROVIDER TURK TELEKOM CENTRAL CLOUD MACHINE LEARNING 34 PUBLIC CLOUD

35 35 KEY TAKEAWAYS

36 KEY TAKEAWAYS An edge cloud is necessary to start offering delay-sensitive services to end users & enterprises. 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. 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. ONF s open edge cloud aims to enable telco-offered PaaS to 3 rd party application developers: Connectivity-as-a-Service, Service Mesh-as-a-Service, Telemetry-asa-Service are example offerings. 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. 36

37 37 THANK YOU