E2E Network Slicing Use Case in R7 Guilin
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.
Participating Organizations
China Mobile, Wipro, Huawei, AT&T, Amdocs, Verizon, Reliance Jio, Tencent, China Telecom, Tech Mahindra, TIM, LTTS
Use Case Owners and Contacts
@LIN MENG menglinyjy@chinamobile.com
@Swaminathan Seetharaman swaminathan.seetharaman@wipro.com
@Shankaranarayanan Puzhavakath Narayanan snarayanan@research.att.com
@Borislav Glozman Borislav.Glozman@amdocs.com
Table of Contents
USE CASE KEY INFORMATION
USE CASE | LEAD CONTACTS / DESCRIPTION | WIKI |
E2E Network Slicing | @LIN MENG @Swaminathan Seetharaman | |
Integration Leads | @Zhang Min @dhebeha mj |
|
Requirement ID | Jira for the requirement
| REQ-342: E2E Network Slicing requirements for Guilin releaseDone |
Architecture Sub-committee Jira tracker | Architecture sub-committee presentation
| ONAPARC-583: Guilin-R7 ArchCom Review (AR-0011-R7-052020) E2E Network Slicing ArchitectureClosed |
Prior projects wiki link | Frankfurt Release |
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.
FUNCTIONAL DEVELOPMENT IMPACTS
Requirement |
| ||
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | @William Reehil |
| |
AAF | @Jonathan Gathman |
| No impact foreseen |
APPC | @Takamune Cho |
| No impact foreseen |
CLAMP | @Gervais-Martial Ngueko |
| No impact foreseen |
CC-SDK | @Dan Timoney | 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 | @Vijay Kumar | Impacts for (a) KPI Monitoring (b) Closed Loop Control (c) Intelligent Slicing | |
DMaaP | @Mandar Sawant |
| No impact foreseen |
External API | @Adrian OSullivan | Impacts for Service Activation/Deactivation and Termination based on TMF 641 | |
Integration | @Morgan Richomme |
|
|
MODELING | @Hui Deng |
| |
Multi-VIM / Cloud | @Bin Yang |
| No impact foreseen |
OOF | @krishna moorthy | Impacts for (a) Improvements in Frankfurt functionality - e.g., callback for NST/NSI selection (b) Slice profile generation (c) RAN/Core/Transport Slice NSSI selection | |
POLICY | @Pamela Dragosh | Control Loop enhancements | |
PORTAL | @Manoop Talasila |
| No impact foreseen |
SDN-C | @Dan Timoney |