5G SON use case enhancements for Kohn release

Before editing please read instructions here.

 Description of Use Case / Requirement:

This use case aims at realizing ONAP-based SON functionality. In Kohn release, it will focus on:

• Implementation of SON use case flow over A1 interface in addition to existing flow over O1 interface. PCI actions will remain as O1-based config actions. ANR actions will be implemented as A1-based messages to an enhanced RAN-Sim which provides an abstraction of RAN Apps which can create changes in configuration.
• (RAN-Sim) Introduction of abstracted A1 termination and RAN App functionality
• (CCSDK/SDN-R) Implementation of A1-based action in SDNR for ANR message
• (DCAE) Modifications of SON-Handler MS: (a) modification of ANR message to send A1 policy message instead of O1 netconf edit, (b) modification of PCI control loop messages to align with new CL format. Keeping SONH-MS CL msg payload for PCI msg same as Jakarta with SDN-R mapping it to if needed to align with O-RAN yang model, (c) work with updated PM/FM VES message formats
  * (Policy) Modification of control loop name/policy for A1-based actions
  
  * -(TBD/Stretch goal) CM Update, CPS update—

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: C
• Company Engagement: CapGemini, Ericsson, Wipro
• Resources: xyz (People)
• Support Status: S

Project CCSDK/SDN-C IMPACT: C 

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

Project Policy IMPACT: C

• Impact Type: C
• Company Engagement: AT&T, Ericsson
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project DCAE IMPACT: C

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

Project OOF IMPACT: None expected

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

Project CPS IMPACT: None expected

• 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): 

Niranjana (TBD)
 

API Impacts in I-release:

Summary: Current focus on A1 support in SDN-R. Full support for A1 in control loop has dependencies on support for changes in Policy and SON-Handler MS. 
RAN-Sim will use modified VES formats if we can get support for changes in SON-Handler MS in DCAE.