...
Use Case Overview & Description
(description of U/C)
Note: 'Support for Vertical Industry' might be viewed as Honolulu POC (TSC 2020-11-05 ).
In R7, Intent technology was proposed as a proof-of-concept (REQ-329). It can be viewed as one of most promising solutions towards autonomous network.
This requirement propose to enhance ONAP with an general-purpose intent framework, which may contains intent translation, intent execution and intent decision and execution etc. We would like to provide more POCs around it, and propose to be one of ONAP component or sub-component in the future. In R8, the requirement will provide the internal reference architecture and interacting with other ONAP components, and also introduce intent modeling for specific use cases, such as intelligent radio capacity optimization and intelligent slicing management.
Introduction to Intent Framework
Intent framework is a system that helps to implement and operate networks that can improve network availability and agility. It takes a high-level business goal (intent) as input, converts it to the necessary network configurations and applies the network changes via network automation and/or network orchestration. Continuously monitoring the status of the network under control, the system validates in real time that the intent is being met, and can take corrective actions when desired intent is not met.
It may contain following functional blocks (to be discussed in Honolulu release):
- Intent UI ( Covred in ONAP UUI by
)Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-453 - Intent Management
- Intent Translation
- Intent Decision and Execution
- Intent Database
Requirement Summary
1. Intent Framework architecture definition
- Functional blocks and interfaces between them
- Initial Implementation as a separate component with multiple micro services.
2. External interface to other existing ONAP Components
- UUI, SO, CDS, AAI/CPS, etc
3. Discussion of general Intent modeling, and giving some concrete intent data model for specific use cases
4. Demo of Intent Framework
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 "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 Huang ZongHe 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").
In R7, Intent technology was proposed as a proof-of-concept (REQ-329). It can be viewed as one of most promising solutions towards autonomous network. This requirement propose to enhance ONAP with an general-purpose intent framework, which may contains intent translation, intent execution and intent decision and execution etc. We would like to provide more POCs around it, and propose to be one of ONAP component or sub-component in the future. In R8, the requirement will provide the internal reference architecture and interacting with other ONAP components, and also introduce intent modeling for specific use cases, such as intelligent radio capacity optimization and intelligent slicing management.
Business Impact - It is a valuable business function that can furthermore reduce the operation expense in terms of automation management.
Business Markets - All operators and service providers that want to use ONAP for network management.
Funding/Financial Impacts - Reduction in operations expense from using procedural while complex operations to using intent-driven declarative operationsFunding/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)
...