John Keeney

Martin Skorupski

Next meetings: 

2021-11-24: John Keeney 
2021-12-01: Martin Skorupski 
2021-12-08: John Keeney 
2021-12-15: Martin Skorupski  

O-RAN-SC ToC

• https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC)
• O2 IF from INF project - O2 with SMO (O-RAN-SC project SMO) in e-release
• in Spec from O-RAN → Cloud inventory could be ready for end of the month

• Non-RT-RIC: John Keeney
  • We will be getting started on the rApp (link monitor) in the next few days, and do not foresee any problems.
• SIM: Alex Stancu
  • ongoing
  • 3gpp implementation RESTCONF northbound of ONAP/SDNC - quick demo
• OAM: Martin Skorupski
  • working across several projects and O-RAN (preparation or March Train)
• O-DU:HariomGupta(HCL) / @Vidhu.  
  • network-slicing - close to be released
  • integration with O-DU-high team
• RSAC/SMO: @Rittwik
• INT: James Li
  • looking for the merging of gerrits - see next section

Sébastien Determe 

Christophe Closset 

ONAP Gerrit

• https://gerrit.onap.org/r/c/oom/+/125150 (master) - config for VES collector - wafting for merge by OOM PTL
• https://gerrit.onap.org/r/c/oom/+/125715 (istanbul)

• Slicing Use case:
  • WIPRO lead & team stepping back somewhat  ... (mail from Ahila: https://lists.onap.org/g/onap-tsc/topic/86928483#8256)
  • Will be further discussed at Slicing Use Case team.
  • Use case remains important for O-RAN Slicing discussions.
• SON Use case:
  • N.K. Shankaranarayanan presented SON Use case at Requirements committee ONAP Jakarta
    • Jakarta release - functional requirements proposed list#5GOOFSONUseCase 
    • A1 action needs enforcement - touches on many aspects
    • "rApp'ifying"/"R1-ifying" the use case?
    • Continue to use as a requirements driver - platform, O1, SIM, A1, etc..
• "Sleeping Cell - A1 Enforcement Simulator"
  • Possible to have as Use case for Jakarta ??? Running out of time for Jakarta.
  • Offline call & further discussions needed probably.
  • Pawel Slowikowski Already a PoC - Missing O1 parts - (RANSIM netconf)
    
    • Maybe RANSIM capabilities here? Please Join SON use case call ... or talk offline.

Want to make progress on A1 enhancements in ONAP Jakarta (Slicing / SON)

• Will discuss on ONAP J usecases/requirements sub-committees next/coming weeks.

ONAP RANSim vs OSC Simulators - Try bring together use cases across ONAP / OSC ?

• ONAP RANSim based on Honeycomb, OSC O1 simulators based on Netopeer netconf servers  (All OSC O1 simulators based on same platform)
• Different simulators have different focus - some on use-case logic vs interface/connectors.
• Will hopefully be easier to mix & match deployments / use cases / simulators across OSC and ONAP should be easier as SMO deployments become more modular & composable.
• Note also Sleeping Cell Simulator from Samsung in ONAP Integration (Marcin Krasowski, Pawel Slowikowski, Mateusz Zawadzki)
  

N.K. Shankaranarayanan 

• O1-CM Models over R1

  STL-AO-2021-11-15-WG2-C-ONAP-ORAN-Harmonization-O1-Input.pptx
  

  (Note, you may need to download and view offline if the content appears garbled)

  • For O1-CM enabling functions in R1, then R1 models should be based on O1 models - but probably need something more, extending main O1 model - "Primary Model & Secondary Models"
  • How is secondary model synced with primary model? E.g. In ONAP CPS the TBDMT function does this.
    • Expressiveness of mappings make make it possible/difficult to maintain such mappings ... or would richer logic be needed/possible? FFS.
  • Needs discussion in WG2 (R1 aspects) & WG10 (OAM/SMO aspects) - likely too late for November train at this stage

John Keeney

Martin Skorupski

Status: canceled (Nexus does not support Helm chart distribution)

Question from O-RAN-SC to ONAP: What is possible in ONAP nexus?

Sébastien Determe: adds some info

Idea: store the artifacts - instead of helm - 

Christophe Closset: ONAP on the way to move for helm charts to gitlab....