Use Case for ONAP-based SON for 5G networks

Before editing please read instructions here.

 Description of Use Case / Requirement:

This use case aims at realizing ONAP-based SON functionality, starting from the ONAP Casablanca release. In H-release, it will focus on:

(a) Alignment with O-RAN (VES for CM-Notify, O1 yang models)

(b) CPS functionality (stretch goal)

and other small functional enhancements.

M3 scope update:

CPS functionality for this use case will not be available in H-release, though the base yang models-based persistency shall be supported, and the first version of TBMT service will be available. Alignment with VES for CM-Notify and O1 yang models is deferred beyond H-release when CPS functionality for this use case will also be available.

 As a result, this use case has become a test-only use case for Honolulu from a functional perspective.

Details of potential API impacts in H-release

Summary: No API impacts except for the stretch goal of CPS interface. Impacts for even CPS interface may not be present depending on the way the mapper service is implemented in H-release.

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

Link to HLD/LLD (if any):

Note: We don't know all the details of NFRs. From our use case team, we can contribute to NFRs in DCAE and OOF.

Dependency Relationships with Other Projects: None within ONAP, however, dependent on availability of yang models

Project CCSDK/SDN-C IMPACT: C

• Impact Type: C
• Company Engagement: IBM
• Resources: Sandeep Shah
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

M3 update: No impact

Project DCAE IMPACT: C

• Impact Type: C
• Company Engagement: Wipro
• Resources: Niranjana
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

M3 update: Impact only for Global requirements.

Stretch Goals

 Project CPS  IMPACT: C

• Impact Type: C
• Company Engagement: Ericsson, IBM
• Resources: To be confirmed
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

M3 update: No impact in H-release for this use case.

Project Policy IMPACT: C

• Impact Type: C
• Company Engagement: To be confirmed
• Resources: To be confirmed
• Support Status: To be confirmed
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

M3 update: No impact.

Project OOF IMPACT: C

• Impact Type: C
• Company Engagement: Wipro
• Resources: To be confirmed
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

M3 update: No impact.

Integration Leads (use @ notation): Niranjana, krishnaa96