Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Note:The Note:The earlier "NETWORK SLICING PoC" and "Vertical Industry Oriented On-demand 5G Service" Has have been merged into one use case.             This use case "E2E Network Slicing Use Case" is the new joint use case for Frankfurt and the future releases.

            Use case descriptions, proposed functions for R6, impacted modules, workflows, etc.  will be filled under this catalog soon.

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

Use Case Owner 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

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 IMPACTS

Requirement

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-158

...

PROJECTPTLUser Story / EpicRequirement
A&AI
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-2600


No code impact foreseen for Frankfurt release. Update A&AI schema with Network Slicing model

(stretch goal for Frankfurt)

AAF


No impact foreseen for Frankfurt release
APPC

Need to check whether this is needed.


No impact foreseen for Frankfurt
CLAMP
No impact foreseen for Frankfurt release
CC-SDK
No impact foreseen for Frankfurt release
DCAE


Not included in Frankfurt scope. May be realized as a PoC. 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-1878

KPI monitoring - new KPI Compute MS and DB. Stretch goal for Frankfurt.

 has been moved to Guilin release

DMaaP
No impact foreseen for Frankfurt release
External API

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyEXTAPI-349

Interface to external CSMF, and CSMF interface to NB systems. Not blocking for Frankfurt (stretch goal)Provide a demo Network Slicing A&AI model
Service order API enhancements alone in scope for Frankfurt.
Integration

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-1467


MODELING
Epic #1 - Network Slicing Demo

Enhance ONAP model with Network Slicing related constructs, including time based activation and KPI monitoring

Provide a demo Network Slicing SDC model


Intention is to re-use existing constructs for Frankfurt release.

Multi-VIM /

Cloud


No impact foreseen for Frankfurt release
OOF
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-277


  • OOF shall
fetch details of active slices, slice sub-nets and services from A&AI.Given the similarities between Slicing and Service instantiation workflows, this could potentially be integrated/interact with HAS, but, if needed, can be seen as standalone for Frankfurt release
  • select appropriate NST(s)
  • OOF shall select appropriate NSI(s) as well as provide recommendations for creating new NSI.
POLICY

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-2056

No code impact foreseen for Frankfurt release

  • Config policy for slice allocation, slice sharing, slice sub-net allocation and slice sub-net sharing
Config policy for resource allocation for a slice sub-net
  • Config policy for optimization constraints
– e.g., network resource optimization, resiliency, etc.
PORTAL
No impact foreseen for Frankfurt release
SDN-C



Not in scope for Frankfurt release, may be realized as a PoC. 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-915

  • DGs for receiving DMaaP message from SO with RAN NSSI details, map them to netconf messages and send to RAN.
  • Interaction with PNF PnP to be discussed
  • Runtime DB interaction

(Stretch goal for Frankfurt)

has been moved to Guilin release.

SDC

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2555

Enhance SDC with properties mapping from composite  to nested service
No code impacts for Frankfurt release
SO
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-
2281
2368


  • CSMF impacts, workflows for service instantiation, involving service decomposition, NST selection, NSI allocation trigger, service instantiation
  • NSMF impacts, workflows for NSI selection, NSI instantiation, NSSI selection, trigger for NSSI instantiation, NSI activation
NSSMF impacts under discussion with ArchComStretch goal
  • Interface to external NSSMF
  • Store slice catalog items, update active slice inventory

(NSSMF impacts still under discussion with ArchCom, not in scope for Frankfurt release)

VID


No impact foreseen for Frankfurt release
VF-CYan Yang
<To be created>

Not in scope for Frankfurt release,
part of
potential NSSMF functionality
,
under discussion
with ArchCom
VNFRQTS
No impact foreseen for Frankfurt release
VNF-SDK
No impact foreseen for Frankfurt release
CDS
No impact foreseen for Frankfurt release
UUITao Shen

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyUSECASEUI-333

CSMF portal and NSMF portal
Runtime DB
<To be created>

Not in scope for Frankfurt release, as this is not yet an official ONAP component. It is intended to contain RAN slice subnet inventory (config and runtime details)
. Stretch goal for Frankfurt, this is not yet an official ONAP component
beyond Frankfurt.

List of PTLs:Approved Projects


Test cases

Further details will be updated in Functional Test Cases.

Service activation with KPI monitoringFetching KPI data from DCAE DB from Portal
No.DescriptionStatus
1

Successful design of

NSSTs

CST ,Service Profile Template

NOT YET TESTED

2Successful design of NSTsof NST, NSST

NOT YET TESTED

3

Service instantiation via CSMF portal resulting in

automatic

NSI selection

(new NSSIs

without any override by operator via NSMF portal - new NSI to be instantiated

)

NOT YET TESTED

4

Service instantiation via CSMF portal resulting in NSI selection

with manual inputs (existing NSSIs

without any override by operator via NSMF portal - existing NSI to be selected

)

NOT YET TESTED
5On-demand service activation from CSMF portal - service activation, NSI binding

Service instantiation via CSMF portal resulting in NSI selection with operator overriding automatically selected option from NSMF portal - new NSI to be instantiated

NOT YET TESTED

6

Service instantiation via CSMF portal resulting in NSI selection with operator overriding automatically selected option - existing NSI to be selected

NOT YET TESTED
7

Service

On-demand service

activation from CSMF portal

- service

– 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 (remove service profile/slice profile from NSI/NSSI)

7Service instantiation with KPI monitoring

NOT YET TESTED8
10Service instantiation request via ExtAPI (using postman) - resulting in new NSI to be instantiatedNOT YET TESTED9
11Service instantiation request via ExtAPI (using postman) - resulting in reuse of existing NSINOT YET TESTED

Supporting Files

DescriptionFile
Presentation to ArchCom on 22 Oct, 2019
Presentation to ArchCom on 05 Nov, 2019
(Brief) Presentation to ArchCom on 19 Nov, 2019
Presentation at Prague DDF on 14 Jan, 2020
Presentation to ArchCom on 25 Feb, 2020
Presentation to Requirements Sub-Committee on 2 Mar, 2020