General intent model and general intent interface requirements in R11

For complex intent, such as the intent of cloud leased line, it is necessary to decompose the complex intent into sub intents of different dimensions, and implement the user's original intent through the execution of sub intents. So we need to deal with machin-machine intent, and for different intents or sub intents in the system, it is necessary to provide general intent model and general intent interface to ensure that all intents(especially machine-machine intents) operate according to the same expression and process. 

Key Contacts - Lingli Deng(CMCC), Keguang He (CMCC), Chuanyu Chen (Huawei), Dong Wang (China Telecom), Henry Yu(Huawei)

Executive Summary - This requirement provides general intent model and general intent interface in ONAP to make all intents(especially machine-machine intents) in the system operate in the same way. At the same time, for complex intents, the technology of intent decomposition and orchestration is provided, and the above ideas and schemes are fully implemented in ONAP through a use case based on cloud leased line. Business Impact - Complex intents can be decomposed into simple intents, and the modeling and interaction of intents can be ensured to be handled in a unified way.

Business Markets - This REQ provides a novel solution to intent modeling and interaction: 1. It provides model federation mechanism to make the intent modeling execute according to the unified specification, and can reuse the existing domain related models which enables extension to different application scenarios.

2. It provides the unified intent interface, which makes the intent interaction in the running state more interoperable and manageable.

Funding/Financial Impacts - By formulating general intent modeling methods and interactive interfaces, standardize the intent operation process, improve user friendliness, improve the customer experience and increase the business value.

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):

denglingli(CMCC),   hekeguang  (CMCC),  boychuanyu (Huawei),  wdongnewin (China Telecom),  hyu2010 (Huawei)

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

UUI, MODELING , DCAE, POLICY, SO

As described in  :

Project (ONAP Component #1 UUI) IMPACT: C

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

Project (ONAP Component #2 MODELING ) IMPACT: C

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

Project (ONAP Component #3 DCAE) IMPACT: T

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

Project (ONAP Component #4 Policy) IMPACT: T

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

Project (ONAP Component #5 So) IMPACT: T

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

Integration Leads (use @ notation):