Use Case Overview & Description

Note: 'Support for Intent Framework and Intent Modeling' 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  contains following functional blocks (to be discussed in Honolulu release):

• Intent UI ( Covred in ONAP UUI by https://lf-onap.atlassian.net/browse/REQ-453)

• Intent Management：

  • Providing NBI for consumers, including intent schema and instance management in a general way

• Intent Translation：

  • Translate high-level of abstraction to a more concrete form in order to be validated and processed.

  • The system takes a higher-level business goal (what) as input from end users and converts it to the necessary network configuration or orchestration request (how).

• Intent Decision and Execution：

  • Decide which, if any, candidate solution shall be executed in response to a request by another managed entity for a set of governance actions.

  • Execute one of translated intent solution by sending request to other component, such as SO, CDS, Policy, or external low-level intent system (intent framework).

• Intent Database：

  • Store intent schema, intent instance and intent knowledge

Open

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

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 - 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 operations.

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

List of PTLs:Approved Projects

*Each Requirement should be tracked by its own User Story in JIRA 

USE CASE DIAGRAM

Open

Use Case Functional Definitions

Supporting materials

TEST Report

Test Case：

Network Provision Test Flow

Open

Test Process：

TBD

Test Cases and Status