Description of Requirement:

The new network applications, like E2E Slicing and CCVPN, provide different SLA services to customers. In this REQ, a scenario of intent guarantee is proposed to support the SLA requirements of users in run-time, as well as updating users’ intents. In R10, the closed-loop will be developed to support the smart Intent E2E Slicing and CCVPN.

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 R10, a Feature of intent guarantee based on closed-loop is proposed to support the use cases of both CCVPN and E2E Slicing.

Business Impact - It is a challenging problem to guarantee the users’ intents in run-time. The REQ of intent-based network provides a scenario of users’ intent guarantee and interacting.

Business Markets - This REQ provides a novel solution to support the SLA service.

1. A users’ intent instance is proposed to monitor and analysis the network in run-time to satisfy the users’ SLA service.
2. The users’ intents are updated in run-time based on the network situation and the interaction with users.

Funding/Financial Impacts - This function will provide more SLA services to increase the income of operators based on the current networks with few investments.

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. 

Owners (one of these should be the Assignee - use @ notation):

wdongnewin, hyu2010, hekeguang, ahilap

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

DCAE, AAI, UUI

As described in https://wiki.onap.org/display/DW/Jakarta+Impact+View+per+Component :

Project (ONAP Component #1 DCAE) IMPACT: C

• Impact Type: C (Test Only/Code)
• Company Engagement: China Telecom, CMCC, Huawei
• Resources: Dong Wang
• Support Status: S (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: null

Project (ONAP Component #2 AAI) IMPACT: T

• Impact Type: C (Test Only/Code)
• Company Engagement: China Telecom, CMCC, Huawei
• Resources: Dong Wang
• Support Status: S (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: null

Project (ONAP Component #3 UUI) IMPACT: C

• Impact Type: C (Test Only/Code)
• Company Engagement: China Telecom, CMCC, Huawei
• Resources: Dong Wang
• Support Status: S (Supported/Partially supported/Not supported)
• Non-Functional Requirement Support: null

Integration Leads (use @ notation):