Skip to end of metadata
Go to start of metadata


Use Case Overview & Description

This use case intends to demonstrate the modeling, orchestration, assurance and optimization of end-to-end network slices, including RAN, Transport and Core slice sub-nets. This use case shall support different deployment scenarios of the Slice Management & Orchestration functions through a modular architecture and standards-based interfaces.

Use Case Key Information

TOPICDESCRIPTIONWIKI PAGE
Requirements ProposalThis is a link to the requirements proposal made on the Requirements Sub-committeeE2E_Network_Slicing_vF2F_rqmts_v_1.0.pptx
Architecture S/C infoInformation on the Architecture sub-committee presentation
Prior Project "Base" WikiLink to the Guilin release page for this use case
Requirements Jira (REQ-###) TicketLink to the REQ Jira ticket for this use case

REQ-440 - Getting issue details... STATUS

Key Use Case Leads & Contacts
Meetings Register & RecordingsLink to Use Case Team meetings

BUSINESS DRIVER

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 Status

PROJECTPTLUser Story / EpicRequirement
A&AI

AAI-3224 - Getting issue details... STATUS

Minor impacts related to NSSTs, Slice Profile attributes, etc.

AAF
No impact foreseen
APPC

No impact foreseen

CLAMP
No impact foreseen
CC-SDK

CCSDK-2988 - Getting issue details... STATUS

CDS impacts related to initial configuration of Core NSSI NFs, reconfiguration during Core NSSI reuse as well as due to Closed Loop actions. Potential impacts for RAN Slicing.
DCAE

DCAEGEN2-2521 - Getting issue details... STATUS

  • Enhancements in Slice Analysis MS
  • Enhancements in DES
  • Completion of KPI Computation work (PM Mapper or New MS)
DMaaP
No impact foreseen
External API

EXTAPI-450 - Getting issue details... STATUS

Modernized TMF 628 API support for KPI Monitoring (Stretch goal)
HOLMES
No impact foreseen
MODELING

ONAPMODEL-32 - Getting issue details... STATUS

Enhancements related to endpoints, Slice Profile ↔ Service Profile mapping, etc.

Multi-VIM /

Cloud


No impact foreseen
OOF

OPTFRA-872 - Getting issue details... STATUS

Impacts related to NST selection, endpoints, slice profile decomposition, etc.
OOM
No impact foreseen
POLICY
No impact foreseen
PORTAL
No impact foreseen
SDN-C

SDNC-1415 - Getting issue details... STATUS

Initial configuration of RAN NSSI, reconfiguration during NSSI reuse, RAN NSSI termination, Closed Loop actions. In addition determination of RAN resources, A1 interface support for Network Slicing
SDC
No impact foreseen
SO

SO-3381 - Getting issue details... STATUS

Enhancements in NSMF, RAN/Core/TN NSSMF functionality in SO
VID
No impact foreseen
VF-C
No impact foreseen
VNFRQTS
No impact foreseen
VNF-SDK
No impact foreseen
CDSSee CCSDKSee CCSDK impacts
U-UITao Shen

USECASEUI-504 - Getting issue details... STATUS

Endpoint related enhancements
CPS

CPS-168 - Getting issue details... STATUS

Use of CPS instead of Config DB. Originally  CPS-91 - Getting issue details... STATUS  was created and was later replaced by CPS-168.

List of PTLs:Approved Projects

*Each Requirement should be tracked by its own User Story in JIRA 

USE CASE DIAGRAM

Use cases define how different users interact with a system under design.  Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).

Use Case Diagram Example.png

Use Case Functional Definitions

Use Case Title

Title of the Use Case

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

TESTING

Current Status

  1. Testing Blockers

  2. High visibility bugs
  3. Other issues for testing that should be seen at a summary level
  4. Where possible, always include JIRA links


End to End flow to be Tested

**This should be a summary level Sequence diagram done in Gliffy** 


Use Case Flow


Test Cases and Status


1There should be a test case for each item in the sequence diagram

NOT YET TESTED

2create additional requirements as needed for each discreet step

COMPLETE

3Test cases should cover entire Use Case

PARTIALLY COMPLETE


Supporting Files

DateDescriptionFile
Feb 02, 2021

Presentation given at LFN DDF

Recording (including Guilin demo for Option 2)

Dec 08, 2020Presentation given to ArchCom
Dec 08, 2020Presentation given to ETSI ZSM
Nov 12, 2020Presentation given at Use case realization call
Oct 14, 2020Presentation given to Requirements Sub-Committee during the LFN vF2F for Honolulu requirements
Oct 13, 2020

Presentation given at LFN vF2F on Honolulu requirements & Roadmap (in detail).

Recording: See here.

May 11, 2021Presentation given at LFN Honolulu Webinar
  • No labels