ONAP 5G USE CASE ENHANCEMENTS ONAP and 5G USE CASE Enhancements 5G Slicing R3 CASABLANCA 5G Use Case Team May 3, 2018 version 0

5G Slicing & Management Original Plan Define a scenario for slice design, creation and management Focus on a simple slice model and scenario for the 5G RAN environment Identify the flows (design & runtime) Identify enhancements/requirements for the impacted ONAP components Demonstrate use case scenario Need Alternatives To Plan Issue: Domain Models For Slicing – From 3GPP? X/ORAN? ONAP? Or other SDO - The Slicing models are not mature & have not been standardized - The Release 15 3GPP work (in 5G Core) is not available till June ’18 Are there other alternatives to consider from a Casablanca scoping perspective? - e.g. use an existing LTE (or other non 5G) model to do the work - e.g. keep the focus on a generic model to drive ONAP requirements and defer implementation of scenario / demo to post-Casablanca; this still leaves open Casablanca slicing demonstrations (on existing networks using existing ONAP capabilities) – the proposed alternative in this presentation - e.g. Other ??

B: Casablanca – Slice Management Model ONAP Management - Design ONAP Management - Runtime Mobile Slice Services (e.g. eMBB, Massive IoT, Mission-critical IoT) Network Slice Instances (NSIs) RAN Subnet Instances (NSSI) Transport Subnet Instances (NSSIs) Core Subnet Instances (NSSIs) 5G Application Ecosystem RAN Abstraction Model Transport Abstraction Model Core Abstraction Model Radio Antennas Core Network Functions CU-CP CU-UP Internet RU DU Centralized Cloud External Content Front Haul Front Haul II Back Haul Edge Cloud UE/CPE RU – Remote Radio Unit DU – Distributed Unit (5G Base Unit) CU-UP – Centralized Unit, User Plane CU-CP – Centralized Unit, Control Plane

B: Slice Management Model – ONAP Requirements Description Many providers are interested in using ONAP for slice management and extending the cloud notion of sharing network/compute/storage to sharing network functions and network slice subnet instances . 3GPP standards are still evolving and early versions are not expected to be available before June 2018. However, we would like to demonstrate these concepts in ONAP initially using a simple slice definition, creation, and management for 5G Radio Network. Radio Access Network slice subnet instances supported and demonstrated in Casablanca will be limited to simple examples such as eMBB (enhance Mobile Broad Band). Key enhancements needed are: Enhance SDC to model & define network slice subnets for Radio network Enhance SO Instantiate and lifecycle manage network slice subnet instances Enhance A&AI to inventory and store state of slice segments Enhance Multi-Cloud and A&AI to support Guarantee (hard isolation), Burstable (soft isolation) and Best Effort (no isolation) QoS classes for Edge Clouds Integrated design (e.g. configuration and service designs) Support Complex Service Modeling (e.g. service composition, nested allotted resources) Rationale Typical carrier deployments will be complex enough to need support for nested / complex services, correlation across multiple elements - hence, these are critical functional requirements for a carrier-grade ONAP Impacted ONAP components SDC, SO, CC-SDK (SDN-C, APP-C), AAI, Multi-Cloud, DCAE Participating Companies AT&T Amdocs China Mobile Ciena Cisco Ericsson Huawei Intel Nokia

Example: A Mobility Slice – Key Enhancements Needed PNF Network E2E Service Slice: PNF Network VNF Allotted Resource VNF PNF Network Allotted Resource requirement: A Core Slice X: PNF Network VNF Allotted Resource capability: A VNF SDC Enhancements: – Multiple Allotted Resources Per Service – Nested Allotted Resources – Complex Hierarchy -- Models Allotted Resource PNF Network Allotted Resource requirement: B Transport Slice Y: PNF Network VNF Allotted Resource capability: B VNF Orchestration Enhancements: – Layered Orchestration Allotted Resource PNF Network Allotted Resource requirement: C RAN Slice Z: PNF Network VNF Allotted Resource capability: C Controller Enhancements: – Responsible Controller Instance for Slice VNF Allotted Resource AAI Enhancements: – Slice Model/Hierarchy

SLICING ENHANCEMENTS OVERVIEW Slicing enhancements – Design/SDC Enhancements For Modeling – Multiple Allotted Resources Per Service – Nested Allotted Resources Per Service – Service Hierarchy (Many Levels #?) Slicing enhancements – Orchestration/SO Enhancements To Support Slice Hierarchy Slicing enhancements – Controller/SDN-R Enhancements To Support Slice Hierarchy Slicing enhancements – Inventory/AAI Enhancements To Support Slice Hierarchy Slicing enhancements – Multi-Cloud/QoS Enhancements SLICING ENHANCEMENTS FOR CASABLANCA Domain Models For Slicing – From 3GPP? X/ORAN? ONAP? Or other SDO - The Slicing models are not mature & have not been standardized - However, the identified ONAP enhancements will be needed when Operators implement slices (whether using vendor-specific or standardized models) - With the identified enhancements implemented in the Casablanca timeframe, we hope to have vendor/operator implementations post-Casablanca - This still allows for Casablanca slicing demonstrations (on existing networks using existing ONAP capabilities)

Backup

Generic Slicing View … PNF E2E Service Slice: topology_template: node_templates: PNF Network VNF Allotted Resource Network VF Module VNF PNF Allotted Resource requirement: A Sub Slice A: topology_template: node_templates: PNF Network VNF Allotted Resource capability: A Network VNF Allotted Resource PNF Allotted Resource requirement: B Sub Slice B: topology_template: node_templates: PNF Network VNF Allotted Resource capability: B Network VNF Allotted Resource …

From ONAP Architecture Deck “Generic” model-driven Service flow Each Resource Type has its own “Generic” model-driven flow. There currently exist such flows for “VNF” and “Network” Resource Types. Service Orchestration Resource Orchestration Cloud Resource Orchestration PNF Service X: topology_template: node_templates: PNF Network VNF Allotted Resource Network VF Module Note recursion VNF Service Orchestration Resource Orchestration Allotted Resource requirement: A PNF An Allotted Resource can be homed to an existing “underlying” network function or Service Instance, or homing could determine that a new network function Service Instance is needed. This would result in a 2nd level of Service Orchestration. Service Y: topology_template: node_templates: PNF Network VNF Allotted Resource capability: A Network Service Y is being treated as a “Resource” from the perspective of Service X. VNF Allotted Resource