You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

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.

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 CASELEAD CONTACTS / DESCRIPTIONWIKI
E2E Network Slicing
Integration Leads
Requirement IDJira for the requirement


REQ-342 - Getting issue details... STATUS

Architecture Sub-committee Jira trackerArchitecture sub-committee presentation


ONAPARC-583 - Getting issue details... STATUS

Prior projects wiki link





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


PROJECTPTLUser Story / EpicRequirement
A&AI

AAF


No impact foreseen
APPC



CLAMP
No impact foreseen
CC-SDK

DCAE



DMaaP
No impact foreseen
External API



Integration



MODELING

Multi-VIM / Cloud


No impact foreseen
OOF



POLICY



PORTAL
No impact foreseen
SDN-C



SDC



SO



VID


No impact foreseen
VF-C

VNFRQTS

VNF-SDK

CDS

UUI



Runtime Config DB

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 CaseStatus
1

Request a service to be instantiated 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

NOT YET TESTED

2create additional requirements as needed for each discreet step

COMPLETE

3Test cases should cover entire Use Case

PARTIALLY COMPLETE

 Test Cases should include enough detail for testing team to implement the test

 FAILED

Supporting Files

  • No labels