2024-08-06 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#

• 2024-08-13 Martin Skorupski (John OoO)
• 2024-08-20 Martin Skorupski
• 2024-08-27 John Keeney
• 2024-09-03 Martin Skorupski

• O-RAN-SC ToC
  • https://lf-o-ran-sc.atlassian.net/wiki/spaces/TOC/overview#ORANSCTechnicalOversightCommittee(TOC) 
    
    • Confluence up and running 
      • named links are ok - but linked to numbered pages are problematic
      • user names are also problematic
        • please create accounts in Atlassian using the Linux Foundation account email address
      • PlantUML not working (yet)
• OSFG
  • summer break - next meeting Aug12
  • on agenda for next meeting: Demos for O-RAN f2f Oct28+

• Non-RT-RIC: John Keeney

• • K-Release planning
    • use case driven implementation
    • demonstrator  in Montreal (O-RAN f2f Oct 17?)
    • A1 controller from ONAP
      • NBI is now spec in O-RAN → backward compatibility is affected
      • team is thinking about how to address it. 
      • bug fix will be available soon - for ONAP Montreal and New Delhi
    • focus more on integration → to help Bimo
    • bootstrapping service manager in smo-install
    • doc for R1 based policy management
  • by Subhash (AIMLFW)
    • add AI to the NonRtRic/NearRtRic integration
    • needs to be architect-ed
    • init on a wiki 
      • SMO deployment vs RAN deployment

• SIM: Alex Stancu
  •  K-Release
    • new py implementation of O1 and OFHM for sims
    • use sims for integration
    • demo for O-RAN f2f: https://lf-o-ran-sc.atlassian.net/wiki/spaces/SIM/pages/13435008/Hierarchical+OAM+functions+Use+Case

• OAM: Martin Skorupski
  • K-Release
    • What do you want?
      • WG11 Security updates
      • WG10 OAM updates
        • Topology? RAN, Transport, Cloud, ....
          • 3GPP → ?
          • ietf-network-topology → yang
          • O-RAN? → yang!!?!
          • onf:tapi→ yang
          • TMForum → OpenApiSpec
        • How to link/relationship between model/nodes?
          • externalizing the relationships!!! 
    • What should be demoed in October O-RAN f2f?
      
      • hybrid vs hierarchical all at the same time via on O-DU....
      • stndDefined newAlarms and clearedAlarms should be consumed by SDN-R from kafka - input from O-DU team

• AI/ML: @Subash Singh
  
  • Minutes & Meeting: Meeting notes

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

  • highlight for J → upgrade of the platform
  • K-Release
    • spec alignment with O-RAN next train
    • integration of AI/ML framework with with SME (main topic)
    • feature preparation
    • model retraining aligned with NonRtRic - design preparations

• SMO: Seshu Kumar Mudiganti 
  • • by John Keeney: topo and inventory efforts 
      • should be model driven but tests are impacted
      • aligned with 3GPP and enhanced → pre-spec
      • rough cloud-topo model (pre-spec)
      • concept of grouping topos - already in API
      • concept of tagging topo entries (decorators) - supporting queries  
      • references:
        • doc: https://docs.o-ran-sc.org/projects/o-ran-sc-smo-teiv/en/latest/data-models-guide.html
        • code: https://gerrit.o-ran-sc.org/r/gitweb?p=smo/teiv.git;a=tree;f=teiv/src/main/resources/models
    • Minutes & Meeting: Meeting notes 
    • J Release planning
      • integration point OAI, Nephio, O-RAN-SC
        

• O-DU: @Vidhu
  • No update this week
    
    
• INT:  (bimo fransiscus asisi )
  • Please see INT meetings (https://wiki.o-ran-sc.org/display/IAT/Current+Meetings)

• RSAC:
  • Minutes: RSAC Meetings 
  • Agenda for tomorrow

@ Deena Mukundan:

• CAPIF implementation - spec is moving on related to R1
• integration with keyCloak -
  • Security should be configured though CAPIF
  • KeyCloak should be outside of CAPIF system
    • results in standalone KeyCloak instance
• Doc → please see technical discussion page in H and/or I release.