Smart Operator Intent Translation in UUI based on IBN - R8 5G Slicing Support

Description

A lightweight and high-cohesion Nature Language Processing (NLP) function is proposed to add in the UUI project, in order to translate the network operation engineers’ text/voice intents to the suitable slicing parameters quickly and decrease the manual configurations.

 

Description of Use Case / Requirement:

Smart Operator Intent Translation in UUI based on IBN - R8 5G Slicing Support:

  • 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 R8, the smart operator intent translation function is proposed to support the 5G slicing selection of current E2E usecase in UUI.

  • Business Impact - In 5G networks, dozens of slice templates will be created to support different SLA requirements. It is difficult for the operators to select the target slice and create the slice instance manually. The IBN based smart operator intent translation function is applied to select the target slice automatically and accurately.

  • Business Markets - Currently, the smart operator intent translation function is developed to support the 5G slice selection. In the further releases, it will be improved to support multiple network configurations in ONAP.

  • Funding/Financial Impacts - This function will have OPEX savings by selecting more accurately slices to save the network resources, and decreasing the labor cost using automation technology.

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

  • REQ-329 remaining unresolved issues -1) The management of intent, stored in our own database, has not yet reached an agreement with AAI;2) Intentional decision-making, without using the capabilities provided by Policy, call the drools interface by itself 3) The guarantee of intention is just a simple piling process

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

China Telecom: @Xin Zhang

China Mobile:

Huawei:

Link to HLD/LLD (if any):

 

Documents to be reviewed:

 

Dependency Relationships with Other Projects:

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

  • Reference architecture

         - UUI

Project Impact (Test Only (TO), Code (C)):

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

 UUI(C)

Integration Leads (use @ notation):

 

Company Engagement:

China Telecom, China Mobile, Huawei

Attachments

2
100% Done
Loading...

Activity

Show:

Former user March 11, 2021 at 10:56 AM

==================================
Congratulations M3 Honolulu Milestone Passed
==================================

Former user January 28, 2021 at 12:19 PM

==================================
Congratulations M2 Honolulu Milestone Passed
==================================

Former user January 21, 2021 at 3:38 PM

==================================
Congratulations M1 Honolulu Milestone Passed
==================================

Former user December 1, 2020 at 7:20 PM

"Req or Use Case" = "Requirement" has been deprecated. Please update this issue.

See this email for details: https://lists.onap.org/g/onap-requirements-sub/message/1844

Former user November 26, 2020 at 5:10 PM

Thank you for the update.
The new Honolulu release plan will be discussed during the next PTL call on Nov 30th.
I have updated the following wiki in alignment with new release cadence terminology: https://wiki.onap.org/display/DW/Honolulu+Impact+View+per+Component.
Please contact the impacted PTL to help them on Global requirements and best practices. Thank you.

Done

Details

Assignee

Reporter

Requirement Type

Specification

Arch Review

GO

Scope Status

Original Scope

T-Shirt Size

M

M1 Approval

GO

RC0 Scorecard

Green

M2 Approval

GO

M3 Approval

GO

M3 Scorecard

Green

Fix versions

Priority

Epic Name

Created October 19, 2020 at 5:35 AM
Updated May 6, 2021 at 11:52 PM
Resolved April 19, 2021 at 9:49 AM