Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date

Attendees

Discussion items

TimeItemWhoNotes

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 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

CM Notify processing in SDNRSandeepEmails exchanged with Dan (SDNC) 

Action items

  •  
  • No labels