(Copy this Page in the → ... → select COPY)
Use Case Overview & Description
(description of U/C)Contact:Dong Wang (wangd5@chinatelecom.cn), China Telecom
Co-contributors
China Telecom:Xin Zhang Huang ZongHe
HUAWEI:wangyaoguang
Requirement Overview & Description
A lightweight and high-cohesion Nature Language Processing (NLP) function is proposed to add in the UUI project, in order to translate the network operation engineers’ text/voice intents to the suitable slicing parameters quickly and decrease the manual configurations.
Smart Operator Intent Translation in UUI based on IBN - R8 5G Slicing Support:
- Executive Summary - Intent-based network (IBN) is a self-driving network that uses decoupling network control logic and closed-loop orchestration techniques to automate application intents. An IBN is an intelligent network, which can automatically convert, verify, deploy, configure, and optimize itself to achieve target network state according to the intent of the operators, and can automatically solve abnormal events to ensure the network reliability. In R8, the smart operator intent translation function is proposed to support the 5G slicing selection of current E2E usecase in UUI.
- Business Impact - In 5G networks, dozens of slice templates will be created to support different SLA requirements. It is difficult for the operators to select the target slice and create the slice instance manually. The IBN based smart operator intent translation function is applied to select the target slice automatically and accurately.
- Business Markets - Currently, the smart operator intent translation function is developed to support the 5G slice selection. In the further releases, it will be improved to support multiple network configurations in ONAP.
- Funding/Financial Impacts - This function will have OPEX savings by selecting more accurately slices to save the network resources, and decreasing the labor cost using automation technology.
- Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Use Case Key Information
TOPIC | DESCRIPTION | WIKI PAGE | ||||||||
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committeeHonolulu release - functional requirements proposed list#SmartOperatorIntentTranslationinUUIbasedonIBN-R85GSlicingSupport | |||||||||
Architecture S/C info | Information on the Architecture sub-committee presentationONAPARC-641 | Honolulu-R8 Functional 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 caseREQ-453 |
| ||||||||
Key Use Case Leads & Contacts | USE CASE Requirement LEAD: | |||||||||
Meetings Register & Recordings | Link to Use Case Team meetings. |
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 - Intent-based network (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)IBN) is a self-driving network that uses decoupling network control logic and closed-loop orchestration techniques to automate application intents. An IBN is an intelligent network, which can automatically convert, verify, deploy, configure, and optimize itself to achieve target network state according to the intent of the operators, and can automatically solve abnormal events to ensure the network reliability. In R8, the smart operator intent translation function is proposed to support the 5G slicing selection of current E2E usecase in UUI.
Business Impact - In 5G networks, dozens of slice templates will be created to support different SLA requirements. It is difficult for the operators to select the target slice and create the slice instance manually. The IBN based smart operator intent translation function is applied to select the target slice automatically and accurately.
Business Markets - Currently, the smart operator intent translation function is developed to support the 5G slice selection. In the further releases, it will be improved to support multiple network configurations in ONAP.
Funding/Financial Impacts - This function will have OPEX savings by selecting more accurately slices to save the network resources, and decreasing the labor cost using automation technology.
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 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 CaseSmart Operator Intent Translation in UUI based on IBN - R8 5G Slicing Support | ||
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 CaseUUI | ||
Description | A lightweight and high-cohesion Nature Language Processing (NLP) function is proposed to add in the UUI project, in order to translate the network operation engineers’ text/voice intents to the suitable slicing parameters quickly and decrease the manual configurations. | ||
Points of Contact | |||
Preconditions | |||
Triggers / Begins when | |||
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 | |||
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.
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
...
**This should be a summary level Sequence diagram done in Gliffy** 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 |
...