Participants: China Mobile, Wipro, Huawei, AT&T, Amdocs, Verizon, Reliance Jio, Tencent, China Telecom, Tech Mahindra

Use Case Owners and Contacts

LIN MENG menglinyjy@chinamobile.com

Swaminathan Seetharaman swaminathan.seetharaman@wipro.com

Chuanyu Chen chenchuanyu@huawei.com

Shankaranarayanan Puzhavakath Narayanan snarayanan@research.att.com

Borislav Glozman Borislav.Glozman@amdocs.com

Sub-pages

Table of Contents

USE CASE KEY INFORMATION

USE CASE	LEAD CONTACTS / DESCRIPTION	WIKI
E2E Network Slicing	LIN MENG Swaminathan Seetharaman	E2E Network Slicing Use Case in R7 Guilin
Integration Leads	Zhang Min dhebeha mj
Requirement ID	Jira for the requirement	REQ-342 - Getting issue details... STATUS
Architecture Sub-committee Jira tracker	Architecture sub-committee presentation	ONAPARC-583 - Getting issue details... STATUS
Prior projects wiki link	Frankfurt Release	E2E Network Slicing Use Case in R6 Frankfurt

BUSINESS DRIVER

This section describes Business Drivers needs.

Executive Summary: 5G Network Slicing is one of the key features of 5G. The essence of Network Slicing is in sharing network resources (PNFs, VNFs, CNFs) while satisfying widely varying and sometimes seemingly contradictory requirements to different customers in an optimal manner. Same network is expected to provide different Quality of Experience to different consumers, use case categories and industry verticals including factory automation, connected home, autonomous vehicles, smart cities, remote healthcare, in-stadium experience and rural broadband. An End-to-End Network Slice consists of RAN, Transport and Core network slice sub-nets. This Use Case intends to demonstrate the modeling, orchestration and assurance of a simple network slice (e.g. eMBB). While 3GPP standards are evolving and 5G RAN and core are being realized, this Use Case will start with realizing an E2E Network Slice with a simple example of a 5G RAN, Core and Transport Network Slice sub-nets. It will also align with relevant standard bodies (e.g., 3GPP, ETSI, TM Forum) as well as other open initiatives such as O-RAN where relevant, w.r.to both interfaces as well as the functional aspects.

Business Impact: Network Slicing is a feature that almost every service provider will leverage. It allows a service provider to improve their network efficiency by maximizing the network throughput more tailored to each user's use of the network. It is seen as an imperative for efficient and optimal use of their network. This will be particularly relevant as 5G is expected to have upwards of 10,000x the traffic load over 4G and 20GB peak data rates.

Business Markets: Network Slicing, for this use case, is specifically aimed at a 5G access, core and transport. In the future, this might be extended to other domains or applications such as fixed-wireless convergence, Wi-Fi access, all aspects of transport including fronthaul, or unified network management orchestration. Network Slicing functionality is what almost every wireless service provider will inevitably find valuable. The concepts and modeling work being done for Network Slicing will find applications in other areas as well. (Industries) Some applications and industries such as smart cities, remote maintenance, video streaming vs life-saving first-responder type applications will demand different requirements from Network slicing. (Markets/Regions) There are no regional specific aspects to Network Slicing.

Funding/Financial Impacts: Network slicing engenders the optimal use of resources for a Network. Thus, this represents OPEX savings for a service provider.

Organization Mgmt, Sales Strategies: There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

DEVELOPMENT IMPACTS

Requirement
PROJECT	PTL	User Story / Epic	Requirement
A&AI	William Reehil
AAF	Jonathan Gathman		No impact foreseen
APPC	Takamune Cho
CLAMP	Gervais-Martial Ngueko		No impact foreseen
CC-SDK	Dan Timoney
DCAE	Vijay Kumar	DCAEGEN2-2338 - Getting issue details... STATUS	Impacts for (a) KPI Monitoring (b) Closed Loop Control (c) Intelligent Slicing
DMaaP	Mandar Sawant		No impact foreseen
External API	Adrian OSullivan	EXTAPI-449 - Getting issue details... STATUS	Impacts for Service Activation/Deactivation and Termination based on TMF 641
Integration	Morgan Richomme
MODELING	Hui Deng
Multi-VIM / Cloud	Bin Yang		No impact foreseen
OOF	krishna moorthy
POLICY	Pamela Dragosh
PORTAL	Manoop Talasila		No impact foreseen
SDN-C	Dan Timoney
SDC	Ofir Sonsino
SO	Seshu Kumar Mudiganti
VID	ittay		No impact foreseen
VF-C	Yan Yang		No impact foreseen
VNFRQTS	Steven wright		No impact foreseen
VNF-SDK	victor gao		No impact foreseen
CDS	Yuriy Malakov
UUI	Tao Shen
Runtime Config DB	Benjamin Cheung Joanne Liu Rudel

List of PTLs:Approved Projects

Use Case Functional Definitions

Note: This section will be shortly updated with links to relevant wiki pages/presentations.

Section	Description
Use Case Title	E2E Network Slicing
Actors (and System Components)	The list of Actors and System Components that participate in the Use Case
Description	Short overview of the Use Case
Points of Contact	Authors and maintainers of the Use Case. Use Case Lead, Key Use Case members and code contributors.
Preconditions	A list of conditions that are assumed to be true before the Use Case is invoked Includes description of Information Consumed
Triggers / Begins when	Describes the trigger for beginning the Use Case
Steps / Flows (success)	Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced
Post-conditions	The expected results of the execution of the Use Case Includes description of Information Produced
Alternate / Exception Paths	Description of any exceptions or special process that could occur during Use Case
Related Use Cases	List of the Use Cases referenced by this Use Case
Assumptions	Describes any assumptions that are made for this use case
Tools / References / Artifacts	List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case

Test Cases and Status

#	Test Case	Status
1	Successful design of CST, Service Profile and Slice Profile Templates	NOT YET TESTED
2	Successful design of NST, NSSTs (RAN, Core and Transport)	NOT YET TESTED
3	Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF within ONAP). It should result in a new NSI and new NSSIs to be created for all sub-nets.	NOT YET TESTED
4	Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF outside ONAP). It should result in a new NSI and new NSSIs to be created for all sub-nets.	NOT YET TESTED
5	Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF within ONAP). It should result in existing NSSI to be reused at least for 1 subnet.	NOT YET TESTED
6	Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF outside ONAP). It should result in existing NSSI to be reused for RAN sub-net and transport subnet (e.g., FH).	NOT YET TESTED
7	Service activation from CSMF portal – resulting in slice service activation	NOT YET TESTED
8	Service de-activation from CSMF portal – resulting in slice service deactivation	NOT YET TESTED
9	Service termination from CSMF portal (remove service profile/slice profile from NSI/NSSI only)	NOT YET TESTED
10	Service termination (terminate NSI/NSSI also)	NOT YET TESTED
11	Service instantiation request via ExtAPI (using postman) - resulting in new NSI to be instantiated (similar to test case 3)	NOT YET TESTED
12	Service instantiation request via ExtAPI (using postman) - resulting in reuse of existing NSI (similar to test case 5)	NOT YET TESTED
13	Service activation request via ExtAPI (using postman) - resulting in slice service activation	NOT YET TESTED
14	Service de-activation via ExtAPI (using postman) - resulting in slice service deactivation	NOT YET TESTED
15	Service termination via ExtAPI (using postman) - (remove service profile/slice profile from NSI/NSSI only)	NOT YET TESTED
16	KPI Monitoring request to be sent from UUI	NOT YET TESTED
17	KPI Monitoring response to be displayed on UUI	NOT YET TESTED
18	Simple closed loop for NSI/NSSI resource optimization (RRM Policy update) (stretch goal)	NOT YET TESTED
19	Intelligent Slicing - take actions based on ML recommendations to ensure KPI adherence (Admission Control in RAN) (stretch goal)	NOT YET TESTED

Supporting Files

Description	File
Presentation on Use Case Realization Call on 1 Apr, 2020	https://wiki.onap.org/download/attachments/81403386/ONAP_E2E_Network_Slicing_Usecase_realization_call_20200401.pptx?version=1&modificationDate=1585804290000&api=v2
Presentation to Requirements Sub-Committee on 2 Mar, 2020	ONAP_E2E_Network_Slicing_Req_Subcommittee_Mar2_v1.0.pptx
Presentation from F2F
Joint S/C presentation	RAN and Transport Slicing: Joint Meeting Apr 30, 2020
Presentation to ArchCom on 26 May, 2020	ONAP_E2E_Network_Slicing_Arch_Com_26_May_2020_v_2.0.pptx

E2E Network Slicing Use Case in R7 Guilin

This page and its sub-pages captures all requirement and implementation details for the E2E Network Slicing use case for Guilin release.

The E2E Network Slicing use case started in Frankfurt. Details of the Frankfurt implementation can be found at E2E Network Slicing Use Case in R6 Frankfurt.