2023-07-04 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) - Agenda

John Keeney

Please follow the calendar

• https://lists.o-ran-sc.org/g/main/calendar

• https://lists.onap.org/g/onap-meetings/calendar#

• 2023-07-11 Martin Skorupski 
• 2023-07-18 John Keeney 
• 2023-07-25 Martin Skorupski 

• O-RAN-SC ToC

• • https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC)
    • this week July6th: release approval for H-Release expected

• Non-RT-RIC: John Keeney 

• • Release process for ONAP and O-RAN-SC 
  • Please see:  https://wiki.o-ran-sc.org/display/REL/H+Release#HRelease-Non-Real-timeRIC(NONRTRIC)

• SIM: Alex Stancu
  • well - PM file generation working - thanks for the feedback by Non-RT-RIC team - further progress ongoing
  • Please see: https://wiki.o-ran-sc.org/display/REL/H+Release#HRelease-Simulators(SIM)

• OAM: Martin Skorupski
  • documentation
    
    • doc issue solution: https://gerrit.o-ran-sc.org/r/c/nonrtric/+/11110/1/docs/requirements-docs.txt
      
      • Thanks John!
• O-DU: @Vidhu
  • no report

• AI/ML: @Sandeep J

  • Minutes & Meeting: Meeting notes 

  • No update

• SMO: Seshu Kumar Mudiganti 
  • Minutes & Meeting: Meeting notes 
• INT: James Li(CMTI)
  • h-release - see https://wiki.o-ran-sc.org/display/TOC/TOC+Documents
  • no report

What is the motivation of CAPIF in NONRTRIC?

• Varada Varad In NONRTRIC, what is the relation to CAPIF?
  
  • John Keeney As part of SME we need a service registry & APIs for service registration & discover. 3GPP already define some functions and APIs for this: CAPIF (ref: Release H - CAPIF) 
  • ... So we would like to reuse if possible, pending on-going specification in O-RAN Alliance WG2
    • Some discussion already in O-RAN WG2 about reusing CAPIF, so O-RAN spec alignment with SA6 CAPIF will continue there.
  • Please take a look at our CAPIF implementation: Hopefully aligned but not promising compliance with 3GPP spec
    • Release H - CAPIF
    • https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/sme
    • https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-sme
    • https://github.com/o-ran-sc/nonrtric-plt-sme/tree/master/capifcore 
    • nexus3.o-ran-sc.org:10002/o-ran-sc/nonrtric-plt-capifcore:1.1.0
  • Varada Varad (Previously?) Worked in 3GPP SA6 team so would welcome feedback on CAPIF to SA6 delegates
    • John Keeney Have already given some feedback internally to Ericsson SA6 delegates, but main alignment should happen between O-RAN WG2 & 3GPP SA6.
      • Rapporteur for O-RAN WG2 R1-SME specification: Vidyadhar Nallabothula (Ericsson) vidhyadhar Nallabothula

N.K. Shankaranarayanan 

• ONAP SON uses case ... & others
  • Coming together well now. ... counting down to M3
  •  See links below:
    
    • https://wiki.onap.org/display/DW/O1+CM+Update+Notification+VES+Message
    • https://wiki.onap.org/display/DW/CPS-1434%3A+VES+Message+to+update+CPS+DB
    • https://jira.onap.org/browse/CPS-1434
    • https://jira.onap.org/browse/INT-2177
• Update
  • CPS - how the code can be used?
    • modification of yang (subset for needed use case) to be applied and
    • other configurations (dataset as json)
    • yangs can be also injected based on SDNC (NF yangs - in this case unmodified yangs)
    • manual steps vs automation
    • CPS demo:  2023-04-04 Meeting notes - Developer Wiki - Confluence (onap.org)
      
      • https://wiki.onap.org/download/attachments/162106197/20230404_son_call_cps_api_demo.mp4?version=1&modificationDate=1680624282435&api=v2 
      • https://wiki.onap.org/display/DW/2023-04-04+Meeting+notes

Issue when deployment with OOM:

• oom - strimzi > 
  • one option to reinstall strimzi 

Preparation for the next release

• enhancements of RAN SIM

To be on the agenda for June 13!

on the Agenda at O-RAN f2f on WED.

N.K. Shankaranarayanan Seshu Kumar Mudiganti John Keeney Martin Skorupski 

• N.K. Shankaranarayanan  Presentation of slides discussed in past weeks at RSAC call today. See above.
  
  • Draft Slides: (for presentation at RSAC)
    
    • 
  • Update: (14/06/2023)
    • Following presentation at RSAC

      •  using the term "scenario" instead of "use case"

      • red and blue colors for the names of projects/components in the figure

      • separate slide to capture SMO interaction scenario for ES use case

      • RSAC Recording/ minutes will appear here soon
      • Draft Slides:
        
  • Older ... 
    
    • https://wiki.o-ran-sc.org/download/attachments/3604609/ONAP_OSC_Areas_20230321.pdf?api=v2 
    • Based on discussion of topics on : https://wiki.onap.org/pages/viewpage.action?pageId=162105284 
    • Recording: (second half of) https://zoom.us/rec/share/D3ZkRsAQ1lu9QY1zomJmAnmXzAUL3FTWJSFqCPDIUKVmZ96HbEu7DQLy34yidjDe.GMyDeZXm34UwgOSR
  • Excellent session to make people aware / motivated about overlaps, with concrete opportunity for better alignment & engagement.
• Seshu Kumar Mudiganti We also need to concentrate on Non functional aspects, such as scalability, security, energy usage. John Keeney Those are costly. Trade off against resources available for functional aspects. Do we need to find out if there is a preference for functional vs non-functional?
• Lots of hard work to do. We will try to identify concrete follow ups.
• Lets continue on the areas we already have good alignment, & strengthen focus on newer potential areas, as described int he slides.

N.K. Shankaranarayanan 

Still! "not ok" - how to use NETCONF YANGs from 3GPP and O-RAN

Problem Statement might be not fully understood. 

Next step: Call with Magnus Buhrgard 

After the call and some emails: Magnus it preparing a call with 3GPP SA5 representatives and then another ONAP LS to 3GPP

The topic is on the ONAP TSC agenda tomorrow: TSC 2022-09-08

• Update from Magnus Buhrgard at ONAP TSC call tomorrow
• Slides available

> Magnus wont give up