...
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
TOPIC | DESCRIPTION | WIKI PAGE |
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | E2E_Network_Slicing_R9_Requirements_20200329_v1.0.pptx |
Architecture S/C info | Information on the Architecture sub-committee presentation | |
Prior Project "Base" Wiki | Link to the Honolulu release page for this use case | |
Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case Jira Legacy |
---|
|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
keyREQ-440 | | Key Use Case Leads & Contacts | |
|
Meetings Register & Recordings | Link 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.
...
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
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | |
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-3224 |
---|
|
| Minor impacts related to NSSTs, Slice Profile attributes, etc. | foreseen foreseen foreseen Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CCSDK-2988 |
---|
|
| 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.Enhancements | Interface to CPS, RAN configuration & A1 interface |
DCAE | |
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-2521 |
---|
|
| Minor enhancements in Slice Analysis MS |
Enhancements in DESCompletion of KPI Computation work (PM Mapper or New MS)Mandar Sawant foreseen Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | EXTAPI-450 |
---|
|
| Modernized TMF 628 API support for KPI Monitoring (Stretch goal) | foreseen Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | ONAPMODEL-32 |
---|
|
| Enhancements related to endpoints, Slice Profile ↔ Service Profile mapping, etc.
| No impact, CPS related modeling aspects will be covered by CPS project |
Multi-VIM / Cloud | |
| No impact |
foreseen Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | OPTFRA-872 |
---|
|
| Impacts related to NST selection, endpoints, slice profile decomposition, etc. | Minor updates |
OOM | |
| No impact |
foreseen foreseen foreseen Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDNC-1415 |
---|
|
| 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 | foreseen Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-3381 |
---|
|
| Enhancements in NSMF, RAN/Core/TN NSSMF functionality in SO |
| Minor enhancements, some major enhancements are stretch goals |
VID | |
| No impact |
foreseen foreseen foreseenvictor gao foreseenU-UI | Tao Shen | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | USECASEUI-504 |
---|
|
| Endpoint related enhancements |
See CCSDK | See CCSDK impacts | was later replaced by CPS-168. Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CPS-168 |
---|
|
| Use of CPS instead of Config DB. Originally Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CPS-91 |
---|
|
was created and Models, and interface to store/retrieve use case related data |
List of PTLs:Approved Projects
...