2023-04-12 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-04-19 John Keeney
• 2023-04-26 Martin Skorupski 
• 2023-05-03 John Keeney
• 2023-05-10 Martin Skorupski 

• O-RAN-SC ToC

• • https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC)
    • alignment with MVP-C 

• Non-RT-RIC: John Keeney

• • Continuing as per last week : No specific update this week
    
    • Alot of work in JDK 17 & Springboot 3 updates
    • Consolidating PM data exposure in new repo for RAN PM functions
      • https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric%2Fplt%2Franpm.git;a=summary
    • (R1) Service Exposure & Management
      • CAPIF Aligned Service Registry
      • Secured/Sandbox execution environment
      • Controlled access & exposure of service to/from rApps

    • (R1) Data Management & Exposure

      • File-based PM data → InfluxDB
      • Previous focus on PM data - but will extend to other use cases too
      • Aim to work with AIML project for Training (and Inference ?) data access

    • rApp Management

      • Built on ONAP “Automation Composition” model & platform to implement rApp use cases
        • Inference Services in rApps
          • Added a 'KServe Participant'
        • rApp-specific extensions needed
      • Packaging, Onboarding & Orchestration of rApps
        • rApp-specific packaging & Onboarding
          • Aim to align with / inform ongoing work in O-RAN (& OSC) about Common App packaging & Onboarding.
        • (rApps with & without µService)
      • Overlap with Service Exposure work to examine role of an rApp Manager to support controlled exposure & LCM of µService and non-µService parts of an rApp

    • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)

      • A1 Spec evolution
      • A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
      • A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
    • Sample use cases (rApps)
      • Requirements Drivers for rApp/R1 development
      • High degree of cross-project integration activity

    • Testing, Maintenance & Housekeeping

      • Function Test & Integration Test environment,
      • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
      • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.

• SIM: Alex Stancu
  • Working on O-DU simulator with 3GPP Yang Models. Currently script-based to build custom images - avoids 3GPP licensing issues. 
    • script is ready 
    • new Sim-O-DU available
  • PM File generation
    • update for the stndDefined fileReady → 3GPP REL-18
    • John Keeney Alex Stancu No update

• OAM: Martin Skorupski
  • stndDefined examples for FM, CM ....
  • Scripts for injecting 3GPP Yaml (VES) from external repos.
  • under investigation: WG4 OFHM v11 → VES → stndDefined → RFC8040 (RESTCONF notification) → O-RAN OFHM yang
  • OFHM supervision mechanism. 
• O-DU: @Vidhu
  • no report

• AI/ML: @Sandeep J

  • Minutes & Meeting: Meeting notes

• RSAC/SMO: David Kinsey
  • no  SMO meeting today
    
    
• INT: James Li(CMTI)
  • no update

• 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

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.
  
  • Slides: 
    
    • 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