Page Comparison

• ORAN model available to ORAN members but not yet to be shared for ONAP use. See:
   https://wiki.o-ran-sc.org/display/OAM/Use+case+demonstration
  
  Plan:
• Analyze difference between ONAP model (3GPP-based model developed for Slicing use case) and ORAN model.
• Case 1: ORAN and ONAP models are aligned, or have small differences which are relatively easy to reconcile.
  • Ensure ONAP model covers SON use case.
  • Develop CPSDB APIs, SDNR code, CL msg format/payload for SON use case based on ONAP model.
    • SDNR code: changes to SDNR to use new yang model for config execution
    • CL msg format/payload: MS and SDNR msgs could change
    • CPS DB API change: CPS/SDNR work needed, has impact on SON-MS and OOF
• Case 2: ORAN and ONAP models have significant differences which are not easy to reconcile
  • Need to re-assess
  • Work for APIs, CPS, and SDNR would require re-work if we proceed with ONAP model

We expect the following impacts in H-release in SON-Handler MS:

• Potential minor impacts related to CM-Notify contents being interpreted and posted (on DMaaP) by SDN-R (SON-Handler already handles a DMaaP message from SDN-R for notifications received over netconf interface from RAN)
• Minor enhancements in the analysis logic before triggering OOF for PCI optimization, and/or Control Loop actions
• Impacts related to interface with CPS (instead of with Config DB) – this will be a stretch goal, depending on CPS readiness and associated impacts getting handled

Link to VES message details:

https://docs.onap.org/projects/onap-vnfrqts-requirements/en/latest/Chapter8/ves_7_2/ves_event_listener_7_2.html 

VES message processing approach:

• VES message has domains which can be used to distinguish CM, FM, PM.
• CM/FM/PM messages will be published on dedicated DMaaP topics for CM/FM/PM topics.
  • Follow up re. topic of de-duplication (may not be in this release)
  • Follow up re. topic of reliable delivery, especially for CM. Follow up with DMaaP team (Milind Sawant?)