Before editing please read instructions here.

 Description of Use Case / Requirement:

This use case aims at realizing ONAP-based SON/Automation functionality for radio networks aligned with O-RAN. In the New Delhi release, it will focus on:

• Initialization and update of CPS DB for RAN CM. See Config Management (CM) Sequence Flow - Developer Wiki - Confluence (onap.org)
  • Automated initialization of primary yang model in CPS DB after SDN-R to NF connection is established (steps 20-25 in flow)
  • Persist the CM change in CPS DB (processed by NCMP) (steps 37-39)
  • Enhancement in DMI plugin codebase as needed (receive new DMaaP message, register cmHandle)
• Enhancements for RAN-Sim

• • Create RAN Service using RAN SIM helm charts
  • Create CDS based workflows for Honeycomb Day-1 Config updates.
  • Update yang model as needed to align with O-RAN
• Enhancement for SDN-R
  • Send notification on DMaaP (new message) when NF connection has been established (step 20)
  • Ensure that SDN-R DB is updated when CM VES notification has been received (step 35-36)
• SON-Handler enhancements - TBD

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

nkshankar

Link to HLD/LLD (if any):

Note: We don't know all the details of NFRs. 

Dependency Relationships with Other Projects:

 RAN-Sim IMPACT: C (Simulation Repo, Not ONAP Project)

• Impact Type: Code change
• Company Engagement: CapGemini
• Resources: xyz (People)
• Support Status: S

Project DCAE IMPACT: TBD

• Impact Type: New Kafka msg, May also have changes to SON-Handler microservice
• Company Engagement: Capgemini
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project CPS IMPACT: *Code change{*}

• Impact Type: Adaptation of NCMP/DMI. No change to API
• Company Engagement: Capgemini, Ericsson 
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project CCSDK/SDN-C IMPACT: Code change

• Impact Type: Publish Kafka msg when NF is mounted. No API change
• Company Engagement: CapGemini, AT&T
• Resources: xyz (People)
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project Policy IMPACT: TBD

• Impact Type: Part of test
• Company Engagement: Capgemini, Ericsson
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project OOF IMPACT: None

• Impact Type: Part of Test
• Company Engagement: TBD
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Integration Leads (use @ notation): 

 vvarvate 
 

API Impacts in N-release:

Summary: We do not expect changes in APIs. The tasks involve completing carry-over work and creating configuration features for existing modules.