Intent-driven Operating for Cloud-network Convergence Services

Intent-based networking is applied to support the smart interaction between users (customers/operators) and networks. Based on the closed-loop automation of ONAP, the proposal of Intent-driven Closed-loop Autonomous Networks is proposed for the smart operation of networks. In R12, the proposal enhances the functions of Intent-driven Operating for Cloud-network Convergence Services based on CCVPN usecase.

Key Contacts - wdongnewin (China Telecom), hyu2010 (Huawei), Lei Shi (AsiaInfo), Yaohua Sun (BUPT)

Executive Summary - Intent-based networking (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 R12, the proposal enhances the functions of Intent-driven Operating for Cloud-network Convergence Services based on CCVPN usecase.

Business Impact - It is a challenging problem for networks to satisfy users’ intents in real time. The REQ intent-based networking provides intent interaction and guarantee functions for users.

Business Markets - This REQ provides a novel solution of Intent-driven Closed-loop Autonomous Networks with two closed-loops, intent interaction closed-loop and intent guarantee closed-loop. And intent instance is used to manage users’ real-time intents.

Funding/Financial Impacts - Intent-based networking simplifies interaction and network configuration to save OPEX cost. It also provides the services to satisfy users’ real-time intents, so as to increase the income of operators 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 ahilap kevin.tang hekeguang boychuanyu 

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

UUI, SDNC, SO, AAI

As described in  :

Project (ONAP Component #1 UUI) IMPACT: C

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

Project (ONAP Component #2 SDNC) IMPACT: C

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

Project (ONAP Component #3 SO) IMPACT: T

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

Project (ONAP Component #4 AAI) IMPACT: T

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

Integration Leads (use @ notation): 

wdongnewin