This page describes the Intent Based Network.
Table of Contents
Use Case Name
| Intent-based Network (IBN) |
...
ORGANIZATION MGMT, SALES STRATEGIES - 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.
Scope for G release
Category | Requirement | Content | |
Architectural Requirements | AR1 | Support 5G slice creation by intent based network | Use intent based network to create 5G slice. |
AR2 | Support Intent instance LCM operations | provide functions for intent instance create, terminate, and KPI monitoring operations. | |
Functional Requirements | FR1 | User intent idendify | Use NLP module to parse user inputs, identify user intent and extract the key information. |
FR2 | Intent Translation | Translate high-level of abstraction to a more concrete form in order to be validated and processed. | |
FR3 | Intent Verification | Verify if the intent decision was executed as expected.（At present, there is no simulation verification, simple implementation, non-target solution） | |
FR4 | Intent Decision | Decide which, if any, policies shall be executed in response to a request by another managed entity for a set of governance actions. | |
FR5 | Intent Guarantee | Two-level closed loop and two-level monitoring | |
Development Status
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF | |||
| APPC | |||
| CLAMP | |||
| CC-SDK | |||
| DCAE | |||
| DMaaP | |||
| External API | |||
| MODELING | |||
Multi-VIM / Cloud | |||
| OOF | |||
| POLICY | |||
| PORTAL | |||
| SDN-C | |||
| SDC | |||
| SO | |||
| VID | |||
| VNFRQTS | |||
| VNF-SDK | |||
| CDS |
...
Use Case Title | Intent-based Network |
Actors (and System Components) | The list of Actors and System Components that participate in the Use Case |
Description | Short overview of the Use Case The Intent-based Network (IBN) is applied to the configuration and optimization of network functions based on the Intents. The current version of IBN is applied to the opening and closed-loop operation of network slices in the 5G use case. |
Points of Contact | Authors and maintainers of the Use Case. Use Case Lead, Key Use Case members and code contributors. Use Case Lead: Huang ZongHe huangzongh@chinatelecom.cn |
Preconditions | A list of conditions that are assumed to be true before the Use Case is invoked Includes description of Information Consumed |
Triggers / Begins when | Describes the trigger for beginning the Use Case |
Steps / Flows (success) | Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced |
Post-conditions | The expected results of the execution of the Use Case Includes description of Information Produced |
Alternate / Exception Paths | Description of any exceptions or special process that could occur during Use Case |
Related Use Cases | List of the Use Cases referenced by this Use Case |
Assumptions | Describes any assumptions that are made for this use case |
Tools / References / Artifacts | List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case |
Other Impacts
Impacted componets
Component name | Impacted detail |
AAI | Need to add new object definition in AAI schema, including intent instance, intent solution and intent solution parameter. |
UUI | A new page is needed in UUI, which user can input network requirement by human-nature language, then the new page sends the user input to IBN componet and displays the response information to user. This procedure may be repeated multiple times until the conversation is completed and a new intent is formed in IBN component. |
Testing
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
...