Use Case Realization Call: January 29, 2020

Owned by Benjamin Cheung
Last updated: Feb 12, 2020
11 min read

Date

Jan 29, 2020

Attendees

  • @Benjamin Cheung

  • @Andy Mayer

  • @Joanne Liu Rudel

  • @Egemen K. Cetinkaya [Verizon]

  • Melanie Sater

  • @Michela Bevilacqua

  • @Fernando Oliveira

  • Albino Pinho

  • @Zu Qiang

  • Raghavan Subramanian

  • @Swaminathan Seetharaman

  • @Bob Papa

  • S. Ricci

  • -

DISCUSSION ITEMS LOG

 

Ctgry

Item

Who

Notes

Meeting Notes Discussion

Discussion Notes from Jan 29, 2020 

All Team members

  1. MODELING - Maybe first focus on models classes that A&AI might need. How do those elements get populated & modified. RTCfg will also need details & the architectural approach how they would approach extensibility; representing in swagger API or flexible schema approach.

  2. A&AI - The A&AI will be stopping at level of PNF (CU/DU), the cells underneath associated w/ a DU you can't find in A&AI. That would be stored in RTCfg DB the index would match with the PNF.

  3. NETWORK SLICING - (Swami) building up, intro some classes. in R7 should we introduce all the classes? Q? (Michela) Where were the classes introduced? For R6 modeling the slice as a service using the only the existing constructors & current platform info-model.

  4. ORAN MODELING - The ORAN alignment, w/ their yang info-models. ORAN-ONAP alignment. Contact ORAN SMEs.

  5. RunTime Config DB - Q? (Joanne) The config DB would be focused on SON U/C importing ORAN yang model to be used in the SON/PCI & associated attributes in R6. (Swami) No. The yang models are not officially available from ORAN. In OOF/SON will still use the old yang models. There is work in converting yang to the schema. ORAN yang model itseill be in R7. Alignment taking ORAN alignment; earlier CMNotify notification over Netconf I/F because ORAN decided it will be a VES event, that VES have a draft specification basedon that will generate a VES notification.

  6. RunTime config DB Schema & Extensibility - Q (Andy)? How does RunTime Config DB deal w/ Extensiblity - the YANG model. Schema in R6 is hard-coded; iin the long term the info from vendor provided PNF package could guide the RTCffDB schema (R7). Q (Joanne)? Relation between 5G info model . Attach the 5G Specific aspects for 5G elements (xNFs). Runtime pc the yang model info that would be represented in A&AI. other info only be in RTCfgDB. MODEL the DOMAIN. Config stuff as a "blob" need to parse. A view of what the info model is. Anything dynamic, changeable, or discovering (would not be in A&AI).

  7. OOF/SON PCI