R10 E2E Network Slicing use case
Use Case Overview & Description
Network Slicing provides dedicate specialized call plane resources called Network Slicing within the network.
Release 10 of E2E Network Slicing introduces the evolution of incremental improvements of Network Slicing.
Use Case Key Information
TOPIC | DESCRIPTION | WIKI PAGE |
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | |
Architecture S/C info | Information on the Architecture sub-committee presentation | |
Prior Project "Base" Wiki | Link to the Istanbul 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 LEAD: @Kevin Tang , @Ahila P USE KEY CONTACTS: @Kevin Tang , @Ahila P , @Henry Yu , @Dong Wang , @Borislav Glozman @LIN MENG | |
Meetings Register & Recordings | Link to Use Case Team meetings. | J-release: E2E Network Slicing use case weekly meetings (Dec - May 2022) I-release: E2E Network Slicing use case weekly meetings (May - Oct 2021) |
BUSINESS DRIVER
This section describes Business Drivers needs. These business drivers are presented on the Requirements Sub-committee and should also be put into the release requirements sub-committee page.
Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")
Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").
Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").
Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case).
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): 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. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
Development Status
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | @William Reehil | No impact | |
AAF | @Jonathan Gathman | No impact | |
APPC | @Takamune Cho | No impact | |
CC-SDK | @Dan Timoney | CPS integration in RAN Slicing | |
CPS | @Toine Siebelink | Using CPS-NCMP from TBDMT to store/read RAN configurations | |
DCAE | @Vijay Kumar | Capacity based NSI/NSSI Selection | |
DMaaP | @Mandar Sawant (Old) → @Fiachra Corcoran (New) | No impact | |
External API | @Adrian OSullivan | No impact | |
HOLMES | @Guangrong Fu | No impact | |
MODELING | @Hui Deng | No impact | |
Multi-VIM / Cloud | @Bin Yang | No impact | |
OOF | @krishna moorthy | Capacity based NSI/NSSI Selection | |
OOM | @Sylvain Desbureaux | No impact | |
POLICY/CLAMP | @Liam Fallon | No impact | |
PORTAL | @Sunder Tattavarada | No impact | |
SDN-C | @Dan Timoney | No impact | |
SDC | @ChrisC | No impact | |
SO | @Seshu Kumar Mudiganti | Dynamic endpoints discovery, OOF involvement in TN slicing, TN model enhancements, Support for activation, deactivation scenarios in external NSSMFs | |
VID |