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.
China Mobile, Wipro, Huawei, AT&T, Amdocs, Verizon, Reliance Jio, Tencent, China Telecom, Tech Mahindra, TIM, LTTS
LIN MENG menglinyjy@chinamobile.com
Swaminathan Seetharaman swaminathan.seetharaman@wipro.com
Shankaranarayanan Puzhavakath Narayanan snarayanan@research.att.com
Borislav Glozman Borislav.Glozman@amdocs.com
| USE CASE | LEAD CONTACTS / DESCRIPTION | WIKI |
| E2E Network Slicing | E2E Network Slicing Use Case in R7 Guilin | |
| Integration Leads | ||
| Requirement ID | Jira for the requirement | |
| Architecture Sub-committee Jira tracker | Architecture sub-committee presentation | |
| Prior projects wiki link | Frankfurt Release | E2E Network Slicing Use Case in R6 Frankfurt |
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.
Requirement | |||
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| 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 | Impacts for (a) KPI Monitoring (b) Closed Loop Control (c) Intelligent Slicing | ||
| DMaaP | No impact foreseen | ||
| External API | Impacts for Service Activation/Deactivation and Termination based on TMF 641 | ||
| Integration | |||
| MODELING | |||
Multi-VIM / Cloud | No impact foreseen | ||
| OOF | 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 | Control Loop enhancements | ||
| PORTAL | No impact foreseen | ||
| SDN-C | Initial configuration of RAN NSSI, reconfiguration during NSSI reuse, RAN NSSI termination, Closed Loop actions. | ||
| SDC | NSST design (RAN, Core, Transport) | ||
| SO | Impacts for (a) CSMF/NSMF improvements (b) NSMF interactions with all 3 NSSMFs - internal and external (c) Core NSSMF (d) RAN NSSMF (e) Transport NSSMF (f) Closed Loop (g) Intelligent Slicing | ||
| VID | No impact foreseen | ||
| VF-C | No impact foreseen | ||
| VNFRQTS | No impact foreseen | ||
| VNF-SDK | No impact foreseen | ||
| CDS | See CCSDK | See CCSDK impacts | |
| UUI | |||
| Runtime Config DB | No impact foreseen, as Config DB shall be used in Guilin release. | ||
List of PTLs:Approved Projects
Note: This section will be shortly updated with links to relevant wiki pages/presentations.
Section | Description |
|---|---|
Use Case Title | E2E Network Slicing |
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 |
This information is taken from this template: Generic Information Element Template
should be copied in the Parent Page (CNF Modeling Workspace) for each Information Element to be defined.
Information Element Template (one table for each Information Element)
Information Element Name | RAN NSST, TN NSST and Slice Profile T (Service template), Endpoint, ConnectionLink and Transport-sla(Data type) |
| Points of Contact | Information Element Main Contact : Chuyi Guo Borislav Glozman Swaminathan Seetharaman Information Modeling and Data Modeling Contact: Chuyi Guo Zhang Min Schema Definition Contact : Chuyi Guo @Henry Yu |
| Related Use Cases | The E2E Network Slicing Use Case: WIKI: E2E Network Slicing Use Case in R7 Guilin and CCVPN Use Case are related to TN Network Slicing: WIKI: CCVPN-TransportSlicing |
Participating ONAP Components | SDC, OOF, SO, AAI, SDN-C, UUI |
| Related JIRA | The related Modeling JIRA is here: |
Description | The modeling design is to enable RAN NSSMF and TN NSSMF internal or external ONAP, and 3 sub-domains combination. |
Related Standards & Industry Activities | Related Standards : 3GPP TS 28.530, TS 28.531, TS 28.541 IETF Related Industry : ORAN |
Attributes | Attributes: Name and describe each attribute of this Information Element. Please include the datatype of the attribute if possible. Is this attribute read-only, read-write? Are there any default values? |
Relationships | Relationships: Describe how this Information Element is related to other Information Elements. Also describe nature of the relationship: association, inheritance, dependency, etc. and multiplicity. |
Originator | Where does this information come from? (What component initially creates it) |
| Consumers | Who uses this information inside & outside of ONAP? How do they use it? Includes description of information consumed (whole class, specific attributes, etc.) |
Producers | Who updates this information inside & outside of ONAP? Under what conditions do they update it? Includes description of information produced (whole class, specific attributes, etc.) |
Steward | Where will this information stored and maintained in ONAP? |
| Impacted APIs & Schemas | Identify impacted ONAP schemas & APIs Are there existing schemas be used or extended? |
Information Modeling Status | What is the status of ONAP Information Modeling activities associated with this Information Element. Please provide links to relevant wiki pages & JIRA. |
Schema Definition Status | What is the status of ONAP Schema Definition activities associated with this Information Element. Please provide links to relevant wiki pages & JIRA. |
ONAP Release Priority | Prioritization for ONAP Releases |
| # | Test Case | Status |
|---|---|---|
| 1 | Successful design of CST, Service Profile and Slice Profile Templates | |
| 2 | Successful design of NST, NSSTs (RAN, Core and Transport) | |
| 3 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF within ONAP). It should result in a new NSI and new NSSIs to be created for all sub-nets. (Option 1) | |
| 4 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF outside ONAP). It should result in a new NSI and new NSSIs to be created for all sub-nets. (Option 2) | |
| 5 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF within ONAP). It should result in existing NSSI to be reused at least for 1 subnet. (Option 1) | |
| 6 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF outside ONAP). It should result in existing NSSI to be reused for RAN sub-net (Option 2) | |
| 7 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF within ONAP). It should result in existing NSI to be reused (Option 1) | |
| 8 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF outside ONAP). It should result in existing NSI to be reused. (Option 2) | |
| 9 | Service activation from CSMF portal – resulting in slice service activation | |
| 10 | Service de-activation from CSMF portal – resulting in slice service deactivation | |
| 11 | Service termination from CSMF portal (remove service profile/slice profile from NSI/NSSI only) | |
| 12 | Service termination (terminate NSI/NSSI also) | |
| 13 | Service instantiation request via ExtAPI (using postman) - resulting in new NSI to be instantiated (similar to test case 3) | |
| 14 | Service instantiation request via ExtAPI (using postman) - resulting in reuse of existing NSI (similar to test case 5) | |
| 15 | Service activation request via ExtAPI (using postman) - resulting in slice service activation | |
| 16 | Service de-activation via ExtAPI (using postman) - resulting in slice service deactivation | |
| 17 | Service termination via ExtAPI (using postman) - (remove service profile/slice profile from NSI/NSSI only) | |
| 18 | KPI Monitoring request to be sent from UUI | |
| 19 | KPI Monitoring response to be displayed on UUI | |
| 20 | Simple closed loop for NSI/NSSI resource optimization (RRM Policy update) (stretch goal) | |
| 21 | Intelligent Slicing - take actions based on ML recommendations to ensure KPI adherence (Admission Control in RAN) (stretch goal) |
| Description | File |
|---|---|
Presentations from LFN Virtual DTF on Jun 24, 2020
| All presentations and recordings are available at: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606742 (or) https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606297 |
| Presentation to ArchCom on 26 May, 2020 | |
| Joint S/C presentation | RAN and Transport Slicing: Joint Meeting Apr 30, 2020 |
| Presentation on Use Case Realization Call on 1 Apr, 2020 | https://wiki.onap.org/download/attachments/81403386/ONAP_E2E_Network_Slicing_Usecase_realization_call_20200401.pptx?version=1&modificationDate=1585804290000&api=v2 |
| Presentation to Requirements Sub-Committee on 2 Mar, 2020 |
MODELING-367