...
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | E2E_Network_Slicing_vF2F_rqmts_v_1.0.pptx | ||||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation |
E2E_Network_Slicing_ArchCom_Review_v1.0.pptx Wiki page: E2E Network Slicing use case: Honolulu Architecture Review | ||||||||||
| Prior Project "Base" Wiki | Link to the Guilin release page for this use case | |||||||||||
| Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||||
| Key Use Case Leads & Contacts | USE CASE LEADS: LIN MENG , Swaminathan Seetharaman USE CASE KEY CONTACTS: LIN MENG , Swaminathan Seetharaman, Henry Yu, Milind Jalwadi (Unlicensed) Borislav Glozman | |||||||||||
| 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.
...
| PROJECT | PTL | User Story / Epic | Requirement | ||||||||||||||||||||
| A&AI |
| Minor impacts related to NSSTs, Slice Profile attributes, etc. | |||||||||||||||||||||
| AAF | No impact foreseen | ||||||||||||||||||||||
| APPC | No impact foreseen | ||||||||||||||||||||||
| CLAMP | No impact foreseen | ||||||||||||||||||||||
| CC-SDK |
| 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 |
|
| |||||||||||||||||||||
| DMaaP | No impact foreseen | ||||||||||||||||||||||
| External API |
| Modernized TMF 628 API support for KPI Monitoring (Stretch goal) | |||||||||||||||||||||
| HOLMES | No impact foreseen | ||||||||||||||||||||||
| MODELING |
| Enhancements related to endpoints, Slice Profile ↔ Service Profile mapping, etc. | |||||||||||||||||||||
Multi-VIM / Cloud | No impact foreseen | ||||||||||||||||||||||
| OOF |
| Impacts related to NST selection, endpoints, slice profile decomposition, etc. | |||||||||||||||||||||
| OOM | No impact foreseen | ||||||||||||||||||||||
| POLICY | No impact foreseen | ||||||||||||||||||||||
| PORTAL | No impact foreseen | ||||||||||||||||||||||
| SDN-C |
| 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 |
| 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 | ||||||||||||||||||||||
| CDS | See CCSDK | See CCSDK impacts | |||||||||||||||||||||
| U-UI | Tao Shen |
| Endpoint related enhancements | ||||||||||||||||||||
| CPS |
| Use of CPS instead of Config DB. Originally
|
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
...
Supporting Files
| Date | Description | File |
|---|---|---|
| Feb 02, 2021 | Presentation given at LFN DDF Recording (including Guilin demo for Option 2) | |
| Dec 08, 2020 | Presentation given to ArchCom | |
| Dec 08, 2020 | Presentation given to ETSI ZSM | |
| Nov 12, 2020 | Presentation given at Use case realization call | |
| Oct 14, 2020 | Presentation 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, 2021 | Presentation given at LFN Honolulu Webinar |