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 I-release, it will focus on:

• Updates in FM reporting and fault handling to be in line with VES 7.2, 3GPP and smoother future alignment with O1
• Align with 3GPP NRM/O-RAN yang models for SON use case

• Use CPS for storing/retrieving RAN config data for this use case 
  Primary and secondary yang models (one of the items in CCSDK-3296) has been done. Remaining items are deferred to Jakarta release

• Configuration Management (CM) notifications over VES based on VES 7.2 (stretch goal)

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

nkshankar , krishnaa96

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:

 Project DCAE IMPACT: C

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

Project CCSDK/SDN-C IMPACT: C  (Removed from scope and deferred to Jakarta release)

• Impact Type: C
• Company Engagement: IBM
• Resources: xyz (People)
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project OOF IMPACT: C

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

Project CPS IMPACT: C

• Impact Type: C
• Company Engagement: (TBDMT - Wipro) (CPS Core - to be checked)
• Resources: xyz (People)
• Support Status: As of now, partially supported
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy
• Note for M1 (green in impact matrix). "Exact details of CPS scope & associated impacts for Istanbul are still being worked out. Based on the progress and discussions in next 1-2 weeks, we will update the scope if needed before M2."

Integration Leads (use @ notation): 

Niranjana
 

API Impacts in I-release:

Summary: No API impacts except new interface to CPS (replacing existing interface to Config DB) for RAN configuration data.