Vertical Industry Use Case
Use Case Overview & Description
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-committee。 | REQ-468 - Getting issue details... STATUS |
| Architecture S/C info | Information on the Architecture sub-committee presentation | 2020-11-24: Honolulu-R8 PoC Requirements Architecture Reviews |
| 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 | REQ-468 - Getting issue details... STATUS |
| Key Use Case Leads & Contacts | USE CASE LEAD: Lei Huang (Unlicensed) Zhang Min Cheng Huang wangyaoguang USE KEY CONTACTS: | |
| Meetings Register & Recordings | Link to Use Case Team meetings. | 2021-01-14: Use Case Realization Meeting Register MoM |
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 - 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 industries.
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 | |||
| AAF | |||
| APPC | |||
| CLAMP | |||
| CC-SDK | |||
| DCAE | |||
| DMaaP | |||
| External API | |||
| HOLMES | |||
| MODELING | |||
Multi-VIM / Cloud | |||
| OOF | |||
| OOM | |||
| POLICY | |||
| PORTAL | |||
| SDN-C | |||
| SDC | |||
| SO | |||
| VID | |||
| VF-C | |||
| VNFRQTS | |||
| VNF-SDK | |||
| CDS |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
USE CASE DIAGRAM
Use cases define how different users interact with a system under design. Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).
Use Case Functional Definitions
Use Case Title | Title of the Use Case |
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 |
TESTING
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
End to End flow to be Tested
**This should be a summary level Sequence diagram done in Gliffy**
Test Cases and Status
| 1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
| 2 | create additional requirements as needed for each discreet step | COMPLETE |
| 3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
Report
In Support For Vertical Industry PoC, we design and develop Operator Management page and Tenant Management page in ONAP Use Case UI：
- Operator Management page: Only operator maintenance officers can access. In this page, operator maintenance officers can create a Tenant account for the corresponding vertical Industry, assign the instantiated network service to the corresponding vertical industry tenant and monitor the info about the existing vertical industry tenant accounts, instantiated network services, and active xNFs;
- Tenant Management page: Only vertical industry maintenance officers can access. In this page, the vertical industry maintenance officer can monitor info about the network service instances and xNFs which have been assigned to this vertical industry tenant.
Operator Management Page