Versions Compared

Version Old Version 4 New Version Current
Changes made by

N.K. Shankaranarayanan

N.K. Shankaranarayanan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees

Discussion items

ItemNotes
AcknowledgmentWe acknowledge the invaluable contributions and leadership from Swami to the SON use case (and other projects in ONAP). We wish him the very best as he pursues other career opportunities.
We welcome and appreciate Krishna stepping in to help lead the use case.
JIRA items

M1 approved.
Main Jira:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-720

Interface to CPS

Plan for Istanbul (based on 5/21 morning CPS call)
Proceed with hard-coded (manually retrieved) yang model used by RAN-Sim which will be provided to CPS Core using some operation supported by CPS

TBDMT works with CPS Core directly (minor change to existing TBDMT) to retrieve schema/model

In parallel, track progress of NCMP progress (long-term target is for NCMP to own models and data for xNF). Significant work needed in CPS team, SDNC etc to support model retrieval from netconf device. However, impact on TBDMT is expected to be minor for the transition to work with NCMP instead of CPS Core.

Yang model

Sandeep has updated API page: CPS APIs and provided the two documents attached below (yang model and yang tree).

Changes include:

  • addition of a region object which has a list of CUs (list of cells optional) and a list of cell-relations (TCI optional)
  • latitude and longitude for nrCellDU


View file
namecps-ran-schema-model@2021-05-19.yang
height250
View file
namecps-ran-schema-model@2021-05-19-tree.txt
height250

Topology modelEarly stages of defining network topology model to be used by ONAP. Strawman model has physical and logical nodes, with physical and logical connections and endpoints.
For 5G SON, we need efficient way to capture the neighbor relationship between cells.
See Proposed Topology IM Sketch
ONAP/ORANShankar will track ONAP/ORAN discussion, especially with focus on use cases, status of code. Topics include:
  1. Ownership/source of code
  2. Management of variants and duplication
  3. Yang models, and model discovery
  4. Topology models of RAN
  5. R-apps, e.g son-handler-ms and oof.

Action items

  •