Page Comparison

...

Time

Item

Who

Notes

CPS/Yang model

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 and , 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 signifiant 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

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

Link to VES message details:

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.
Bring
- - Follow up re. topic of de-duplication (may not be in this release)
Bring
- - Follow up re. 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)

Architecture and flow re-affirmed during discussion:

Step 3a: CM notification received by VES collector. Assumed that all VES messages are relevant to some ONAP use case
Step 4a: VES Collector forwards CM msg to special DMaaP "VES_CM" topic
Step 4b: SDNR parses CM VES msg and updates CPS DB. Note that current SDNR code has separate DmaaP topics for updates to CM for SON and Slicing. Work required to support common CM topic.
Step 4c: SDNR sends SON_CM_Notification to MS on special DMaaP "SON_SDNR_MS" topic
Step 3d: FM/PM VES msg received by collector
Step 4d: VES collector publishes FM/PM msg on special DMaaP "VES_PM" or "VES_FM" topic
Step 4e: MS processes 4c and 4d message and queries CPS DB

Image Added

Action items

Follow up with DMaaP team (new PTL? Milind?) re. reliable delivery of CM DMaaP messages.
Discuss DACE DCAE VES collector requirements for SON use case -
Do both in the same call - either SON or DCAE.