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 APIs and SDNR code for SON use case based on ONAP model
Case 2: ORAN and ONAP models have signifiant 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
CM VES / DCAE
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
VES message processing:
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. Bring up topic of de-duplication (may not be in this release) Bring up topic of reliable delivery, especially for CM. Follow up with DMaaP team (Milind Sawant?)
CM Notify processing in SDNR
Sandeep
Emails exchanged with Dan (SDNC)
Action items
Follow up with DMaaP team (new PTL? Milind?) re. reliable delivery of CM DMaaP messages.
Discuss DACE VES collector requirements for SON use case