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

• Development of PM/FM/CM VES message formats which are aligned with O-RAN O1 (https://lf-onap.atlassian.net/browse/DCAEGEN2-2986#icft=DCAEGEN2-2986) 

• Update of RANSim to use new PM/FM VES message formats (No separate Jira for RANSim)

  The following items in blue are removed from scope. We are blocked since we need enhancement of RANSim.

• Modifications of SON-Handler MS to work with updated PM/FM message formats (https://lf-onap.atlassian.net/browse/DCAEGEN2-2986#icft=DCAEGEN2-2986)

• Update of RANSim to use new CM VES message formats (No separate Jira for RANSim)

• (Stretch goal) Modifications of CCSDK VES Parser, TBDMT, CPS to work with updates CM message format. ( CCSDK-3532 ) 

• (Stretch goal) Implementation of flow over A1 interface: (a) Introduction of abstracted xApp and A1 termination in RAN-Sim, (b) Introduction of new message with guidance to abstracted xApp in RAN-Sim, (c) Implementation of A1 interface support in SDNR
  (Discussions will continue to plan for this work in next release)

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

@Former user , @Former user

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:
We do not have any changes required from DCAE and CPS

 Project DCAE IMPACT: C

• Impact Type: C

• Company Engagement: TBD (STL, Wipro?)

• Resources: xyz (People)

• Support Status: S

• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project CCSDK/SDN-C IMPACT: C 

• Impact Type: C

• Company Engagement: TBD (Wipro?)

• Resources: xyz (People)

• Support Status: S

• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project OOF IMPACT: C (No impact expected)

• Impact Type: C

• Company Engagement: Wipro

• Resources: xyz (People)

• Support Status: S

• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project CPS IMPACT: C (No impact expected)

• 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

Integration Leads (use @ notation): 

@Former user (TBD)
 

API Impacts in I-release:

Summary: No API impacts except new interface to CPS (replacing existing interface to Config DB) for RAN configuration data. 
We do expect to have modified VES formats which will be aligned with DCAE VES Collector.