...
Use Case Overview & Description
(description of U/C)
Note: 'Support for Vertical Industry' might be viewed as Honolulu POC (TSC 2020-11-05 ).
Vertical Industry is one of the greatest potential 5G markets. Unlike traditional 2C scenarios, where the consumers of OSS are CSP internal operation staff or BSS system, in 5G era operators need to provide O&M capabilities for potentially multiple vertical industries consumers. This requirement propose to help operators to manage multiple vertical industry networks using ONAP.
It will contain the following scenarios:
a) One centralized operator ONAP only manages multiple vertical industry networks established by operators, and
b) One centralized operator ONAP manages both vertical industry networks and traditional mobile networks (e.g. slicing).
Requirement Summay
- Tenant management and isolation for Vertical Industry
- Enhance A&AI Schema for vertical industry tenant, including basic tenant profile
- Isolate resources (pnf/vnf/service instance etc.) from different vertical industry tenants, and shares potential resources between operator network and vertical industry network
- Implement permission control for different vertical industry tenants by leveraging Multi-tenancy in ONAP.
- Provide centralized user interface in UUI for different vertical industry tenants, allowing them to access their own data, including resources and necessary configurations.
- Enhance service instantiation procedure with specified tenant and necessary vertical industry area (aka. specified locations)
- Adding necessary building blocks or workflows for service instantiation in ONAP SO.
- Support for vertical industry scenario A in R8
- Operator instantiates different services for two different vertical tenants, further creates initial NRM configurations for them.
- Tenants are expected to access their own resources from centralized UUI.
Use Case Key Information
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub- committeecommittee。 |
| ||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation | |||||||||
| Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | |||||||||
| Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: Lei Huang Zhang Min Cheng Huang yaoguang wang USE KEY CONTACTS: | |||||||||
| Meetings Register & Recordings | Link to Use Case Team meetings. |
...
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").
Vertical Industry is one of the greatest potential 5G markets. Unlike traditional 2C scenarios, where the consumers of OSS are CSP internal operation staff or BSS system, in 5G era operators need to provide O&M capabilities for potentially multiple vertical industries consumers. This requirement propose to help operators to manage multiple vertical industry networks using ONAP. In R8, it will contain the following scenarios: a) One centralized operator ONAP only manages multiple vertical industry networks established by operators, and b) One centralized operator ONAP manages both vertical industry networks and traditional mobile networks (e.g. slicing).
Business Impact - Vertical industry networks contain various combinations of resources, such as VNFs, PNFs, and service instances. Providing one unified OM platform is the most efficient way to satisfy various vertical industry’s requirements. ONAP can be a great automation management platform for 5G vertical industry.
Business Markets - All operators and service providers that want to use ONAP to support the management of vertical industry networks
Funding/Financial Impacts - Reduce the operation expense while providing Network O&M service for different vertical industriesFunding/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)
...