1. Candidate for ONAP Dublin Implementation 5G RAN E2E Slice Design, Deploy and Manage
5G Use Case Team

2. E2E Slice & Service Definition, Deployment, and Management
Requirement Statement:
Each Service Provider (SP) needs to support a rich set of advanced 5G wireless services, such as enhanced Mobile Broad Band (eMBB), massive Internet of Things (mIoT), and Ultra-Reliable, Low-latency Communications (URLLC ), for mission critical communications.
These services have very different requirements on latency, reliability, availability, mobility, and bandwidth.  Deploying multiple separate networks to support these varying requirements is not practical.  End to End network slicing as defined by 3GPP provides specifications for efficient creation of multiple logical networks sharing a common network infrastructure while meeting the specified service levels for each of the services.  ONAP must support the complete lifecycle management of such network slicing.
Automated Configuration:  Automated configuration of a slice during the instantiation, configuration, and activation phases, a newly created set of identifying parameters automatically configured
Automated reconfiguration. Automated reconfiguration happens during run-time e.g. an active slice can be reconfigured automatically because of a change in the service requirements or service conditions.

3. Terminology and Abbreviations
Network Slice: A logical network that provides specific network capabilities and network characteristics.
Network Slice Instance(NSI): A set of Network Function instances and the required resources (e.g. compute, storage and networking resources) which form a deployed Network Slice. NSI contains Core Network part and Access Network part.
NST: Network Slice Template or Profile
NSST: Network Slice Subnet Template or Profiles
NSMF: Network Slice Management Function
NSSI: Network Slice Subnet Instance
NSI: Network Slice Instance
NSSAI: Network Slice Selection Assistance Information
PNF: Physical Network Function
DP: Data Plane

4. Slice Aware 5G Network Architecture
ONAP
Management - Design
ONAP
Management - Runtime
Mobile Slice Services (e.g. eMBB, Massive IoT, Mission-critical IoT)
E2E Slice Instances (NSIs)
RAN Network Slice Segment (NSSIs)
Transport Slice Segments (NSSIs)
Core Slice Segments (NSSIs) 5G
Application
Ecosystem
RAN Abstraction Model
Transport Abstraction Model
Core Abstraction Model RU DU
CU-UP
Edge Cloud
CU-CP-H
CU-CP-L
Front Haul
Mid Haul
Back Haul
Centralized
Cloud
Disaggregated Core
UPF
SMF
UDM
AUSF
AMF
PCF
NSSF
NRF
Internet
External Content
UE/CPE

5. Slicing – Network Architecture
Access Network
Core Network
Communication Services
Service 1
Service 2
Service 3
NSSI - Best Effort
NSSI - Normal
NSSI - Premium
NSSI - HB
NSI A
NSI B
NSI C
© 2017 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.

6. 5G Network Slice Lifecycle Flow – Perquisite & Design Steps
Standardized Abstractions & Modeling (3GPP with some potentially extensions)
Business Objectives / Requirements, Slice subnet & E2E Slice Profiles
Define set of slice subnet and E2E slice templates / profiles to be supported
Sub-slices / services within a broad slice (e.g. interactive video within MBB, etc.)
Key attributes / SLO / Characteristics, Slice aware KPIs / Counters
E2E Slice / Slice Segment network diagram
Identify resources requirements (Radio, transport, core), reservation mode (shared, reserved exclusively, right to preempt, etc.)
How to respond under overload and underload condition (i.e. scale up / scale down)
etc.
Standard Model (e.g. Yang or TOSCA) for Radio Resource Description:
Leverage 3GPP defined TOSCA slice model
Standard Model (e.g. Yang) for Transport Abstraction:
QoS, Bandwidth, resiliency, redundancy, etc.
Core / APN Abstraction Model (e.g. TOSCA):
Resource reservation, entitlements, packet marking, etc.
Standard Model nest / complex services (e.g. TOSCA):
Creating slice using slice segments, nested services, and E2E SLA / SLO specifications
SDC

7. Network Slice Lifecycle Flow – Instantiating Slice Subnet or E2E Slice
VID (or using APIs) SO
A&AI
Select E2E Slice Profile or Slice Subnet Profile / template to Instantiate
Identify resources requirements (Radio, transport, core), reservation mode (shared, reserved exclusively, right to preempt, etc.)
Expected capacity requirements (# devices, peak traffic volume, etc.)
Scope of slice / Slice Subnet (registration areas, etc.)
Slice / slice subnet instance name
Other Parameters to be specified, as expected by the model
etc.
Orchestrator executes Slice Subnet E2E Slice Instantiation or Modification recipe (Could be recursive)
Pass configuration specifications, as per abstraction standards, to RAN controller for radio slice segment creation
Pass QoS, bandwidth, resiliency requirements for transport network to transport controller
Configure NG Core
Start data collection and SLA / SLO monitoring with right DCAE(s) for NEs in scope
Update A&AI with slice / slice segment topology & state
Maintain inventory of instantiated slice subnets, E2E slices, their states and their hierarchical relationship
Runtime Policy Framework
Support closed loop corrective action for Slice / slice subnet SLA violations
DCAE
Controller
Slice Aware KPI / Counter collection
Compute 3GPP defined slice / slice segment KPIs, Analytics application for slice / slice segment SLA / SLO
Publish anomalous event when SLA / SLO violation occurs
RAN / Core NE configuration and Transport slice subnet creation
Disaggregated Core
UPF
SMF
UDM
AUSF
AMF
PCF
NSSF
NRF
Internet RU DU
CU-UP
CU-CP
Front Haul
Mid Haul
Back Haul
External
Content
Edge Cloud
Centralized Cloud

8. Suggested Slicing Scope for Dublin
We want to create two slices:
One for Mobile Broadband (could this be the default slice, and we create only one more slice?)
One for Ultra Low Latency, High Reliability
Our network scope is one registration area with two tracking areas, three DUs, one CU-UP, one CU- CP, and dedicated core for each slice
Do we need a new dedicated vlan between DUs and CU-UP for this new slice with different QoS?

9. 5G Example Network … … … … … … … …
Network In Scope for Slice Demonstration
Cell #1
DU #1
CU-CP
RU #1
Disaggregated Core TA
Edge
Cloud
Cell #2
RU #2
DU #2
CU-UP
AMF
PCF
NSSF
NRF … … … RA
UPF
SMF
UDM
AUSF
RU #n TA
Cell #n
DU #n …
Edge
Cloud …
Centralized
Cloud
Internet
CU-UP
Front Haul
Mid Haul/LAN
BackHaul
External Content
Cell #1
DU #1
RU #1 TA
Edge
Cloud
Cell #2 …
RU #2
DU #2 …
CU-UP … RA
RU #n TA
Cell #n
DU #n

10. Slice demonstration details for Dublin release
Slice model to agree upon
Create ultra low latency high reliability slice template / profile in SDC
Identify fields / parameters specified or populated by VID
SO workflow steps (could be recursive)
Should SO identify all the network elements in scope for a given registration area or the controller or the RAN control plane function (i.e. CU-CP)? ….

11. Thank You!