ONAP & The Edge Cloud (Part-1 – ONAP View Point)

Chris Donley, & Prakash Ramchandran, Dell Introducing Open Network Automation Platform (ONAP) Blending ECOMP, OPEN-O, and Best Practices

+

Design

Analytics Orchestration

Policy Control ONAP Value Proposition

End-to-End Automation • Complete lifecycle automation – design, inventory, control, operate, and metrics • Orchestrate and automate across geographic and domain boundaries, technologies and layers • Modular, model-driven approach • Re-usable, nested service definitions simplify service development

Industry Harmonization • Collaborative marketplace of ideas for global operators and solution providers • Enable migration from proprietary, purpose-built orchestration tools • Reduce market fragmentation with common, open development platform/APIs • Support wide range of use cases and operating environments

Efficient Deployment A common platform for rapidly • Incorporates production-proven code • Developed for both brownfield/ greenfield deployments to protect existing designing, implementing & investments • Modular platform components reduce integration cost and time managing differentiated • Optimize operations through closed-loop network intelligence and analytics services. ONAP Beijing Architecture (High-Level View with Projects)

4 instantiation

2 VF Resource 5 VNFD 3 Service Workflow

6 8 9 7 NSD (Utilities) DG DG

1 Integration

VNF Requirements VNF

Modeling VNF Validation Program Validation VNF

VNF

Model Driven

4 ONAP Casablanca Release Planning

Highlights (under discussion): • Modularity to fit into multiple operator networks • API Improvements • Enhanced support for Kubernetes • Preparing for VNF Compliance Testing • Multi-CPU architecture • Enhanced platform maturity • Enhanced security • External controllers

Huawei Confidential Edge Use Cases

• Virtual Provider Edge (25Gbps Symmetric or Asymmetric UL/DL) • Connected Vehicle Application for Safety • 4K Video using Fixed Wireless Access • New Application for Connected Edge Devices (copyright Cplane.ai)

Huawei Confidential Virtual Provider Edge Router

• Virtual Provider Edge Router (vPE) is a VNF serving as an edge router • Network Service Descriptor (NSD) will include the vPE VNFD. • VNF typically located between two networks such as the provider core network and the provider access network • The packets to the core network will be filtered, classified, and metered with Quality of Service (QoS) parameters. • The packets to the access network will be shaped according to the subscription policy. • Refer for details on ONAP wiki (Throughput 25Gbps Symmetric) • https://wiki.onap.org/display/DW/Virtual +Provider+Edge

Huawei Confidential Connected Vehicle Applications : V2I Safety & V2V Safety V2X Connected Vehicle Applications CVA) Low latency, Location Based, Moderate throughput

• V2I Safety • V2V Safety • Red Light Violation Warning • Emergency Electronic Brake Lights • Curve Speed Warning (EEBL) • Stop Sign Gap Assist • Forward Collision Warning (FCW) • Spot Weather Impact Warning • Intersection Movement Assist (IMA) • Reduced Speed/Work Zone • Left Turn Assist (LTA) Warning • Blind Spot/Lane Change Warning • Pedestrian in Signalized (BSW/LCW) • Crosswalk Warning (Transit) • Do Not Pass Warning (DNPW) • Vehicle Turning Right in Front of http://www.its.dot.gov/pilots Bus Warning (Transit) The OBU, RSU, AU Pilot and topology (Wyoming Pilot)

• Implementation Elements • 75 Roadside Units (RSUs) broadcasting and receiving messages via DSRC /Citizen Band • 400 equipped vehicles with on-board units (OBUs) • V2V, V2I, I2V applications alerting drivers to various road conditions • CV data collection for improved traffic management and traveler information

Huawei Confidential Satellite Service Provider, CSP and Transportation Info. Mgmt. (TIM)

Huawei Confidential UHD 4K Fixed TV or Mobile Edge Delivery (EBB use case)

https://www.techradar.com/news/television/ultra-hd-everything-you-need-to-know-about-4k-tv-1258884 Huawei Confidential Edge Considerations

Huawei Confidential Hierarchical ONAP Central/Edge Architecture

Casablanca Release Work Items 1. Extend models to include edge cloud IaaS/PaaS attributes • Distributed, Highly-secure, Config/Cloud-diverse, Capacity- constrained and Peformance/Isolation-aware 2. Hierarchical Central/Edge Architecture/functional interactions

Source: “Edge Scoping,” https://wiki.onap.org/pages/editpage.action?pageId=28381325 s 01.11.2017

ONAP in Edge Cloud leveraging Openstack PART-2: A Word On “Open Edge Cloud”

PRAKASH RAMCHANDRAN

CHRIS DONLEY

16 Hierarchical ONAP Central/Edge Architecture

Casablanca Release Work Items 1. Extend models to include edge cloud IaaS/PaaS attributes • Distributed, Highly- secure, Config/Cloud- diverse, Capacity- constrained and Peformance/Isolation- aware 2. Hierarchical Central/Edge Architecture/functional interactions

Source: “Edge Scoping,” https://wiki.onap.org/pages/editpage.action?pageId=28381325 Functional Architecture Variations with MANO split with NFVO+VNFM and VIM

18 Multi-VIM ONAP with support for Service at Edge and Core

Multi

Openstack VMware

19 What requirements changes for in Core & Open Edge from ONAP R2 to R3

• Open Edge • 5G Core

• Open Edge tries embrace MEC • Core Starts Embrace E2E 5G

• MEC is viewed as variation of NFV • Core is trying to adopt to App. Function(s), trying to co- ordinate with Access & Mobility Management Service (AMS) & • Edge Resources are getting Containerized Session Management Service (SMS).

• Applications and Systems are disaggregating as Microservices • Event Exposure Management and Policy Management trying to support Edge services. • Mid-haul emerging to manage traffic offloads

• User Plane Function needs to be able to work with local & • Support for Throughput 20 Gbps/DL-10 Gbps UL , Low latency remote Data Networks of 1-5 ms order a must.

20 Open Edge Infrastructure: Used case Connected Vehicle Application (CAV)

• NFVO for Connected Vehicle Applications

• OBU – On Board Unit (Any Open Edge OBU) Orchestration & Network Management • RSU – Road Side Unit (Any Open Edge RSU) RSUC I2I RSUC • RSUC – Road Side Unit Controller (Openstack based Open Edge RSUC with Transport Management SystemTMS ) – To be I2I I2I defined

BS RSU RSU RSU BS RSU • Open Edge Cloud (Open Edge Cluster) RSU V2I RSU V2I V2I V2I • AU – Application Unit (VM or a Container for TMS) OBU OBU

• Connectivity V2I, V2V, I2V, I2I OBU OBU OBU V2V OBU V2V

21 Connected Vehicle Applications

22 Sample Specification for Open Edge Cloud

Typical OBU specs (Small) 1U or 2U server Typical RSU specs (Medium) (2U-20U) • OBU unit infrastructure:

• RSU infrastructure: • CPU : dual core CPU capable of multi threading @ 512 MB

• CPU: multi core 64 bit CPU capable of multi threading @ 2 GHz [LS2045 – LS2085 having 8 Cortex A-57 CPUs NXP processors] • Memory: 2-4 GB RAM

• Memory: 8 GB RAM • Storage: 16 GB SDRAM

• Storage: 128 GB SDRAM • Sensors interconnect – Direct coupling / CAN

• N/W: • Networking:

• Downlink – DSRC or WIFI (multilink infrastructure with RFID, BT, WIFI, • Downlink: WIFI for connection to mobiles DSRC)

• Uplink: WIFI, DSRC, multilink connection (BT, RFID, DSRC, WIFI) • Uplink – WiMax / WIFI to a access point connection to internet using 802.11p WAVE

23 Sample Connected Application Cont.

Typical AU function & features Openstack Module Mapping

• Application Unit:

• Deploy applications for local operations, VANET signalling for VANET messages to other vehicles (V2V) • AU can be implemented as multiple AFs for Safety, Traffic Analytics, Security/firewall & load balancer, packet classifiers to • Most of these applications are connected to onboard sensors. classify flows & transfer traffic from road side to the centralized Unit(CU) through core (offload service))

• Applications for safety interact with RSU for inputs like (road blocks, lane restrictions, accident, etc). These applications • RSU needs multiple service instances, hence requires VN, VM, should be dynamically deployed. VS (Nova/Neutron/Cinder/Ceph/Swift)

24 OpenStack Components

• Keystone for ID management / service catalog management (will be at controller)

• Glance (global)

• Distributed nova at the RSU

• Distributed neutron at RSU

• Distributed cinder / ceph / swift at RSU

25 Options Galore – To explore per use case

NFVO ONAP OPENBATON OSM SDN-C OPEN EDGE CONTROLLER ONAP AKRAINO ZUN based ODL / ONOS/ Tungsten RSUC OPENSTACK AF Titanium Server /EdgeX / NEV Huawei or or Ericsson SD-WAN conrollers API or Neutron /Kuryer based

RSU CISCO or Juniper DNOSS Cumulus or NXP or Dell OBU Host or guest OS over Sierra Wireless InfoBlox Qualcom/ Hypervisor AU VM Container Bare metal UE/Tablet Apple Android Nokia Huawei

26 Edge Considerations

27 THANKS. ONAP Edge WG – Chris Donley Openstack Edge WG – Prakash Ramchandran Questions?

openstack @OpenStack openstack OpenStackFoundation

28