Page History

John Keeney 

Please follow the calendar

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

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

• 2024-06-25 John Keeney (Martin not sure)07-09 Martin Skorupski
• 2024-07-02 16 John Keeney
• 2024-07-09 23 Martin Skorupski 
• 2024-07-16 30 John Keeney

• O-RAN-SC ToC
  • https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC) 
    • Release J approved
      
      
• OSFG
  • whitepaper 
    • addressing feedback from O-RAN TSC
  • more CVEs :(
    • https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=O-RAN
      
      

• Non-RT-RIC: John Keeney
  • J-Release planningdone!
    • https://wiki.o-ran-sc.org/display/RICNR/Release+J
    • using rApp Manager function for other tasks
      • rApp using rApp Manager
      • r1 is the interface to use 
    • service manager function → alpha version → main contribution for J.
      • CAPIF registry and discovery of services and API-Gateway
      • includes access control for the services
      • concept from O-RAN Alliance (SME) 
      • integration with rApp Manager
    • A1-Policy function in ONAP with new northbound interface
    • carry over from I-Release - A1-mediator compatibly with A1-Policy
    • updates based on WG2 Specs (R1 specification, SMO decomposition )
    • work on DME - R1 API updates - for study?
    ONAP policy functions will be updated, new nbi according to O-RAN rApp discussion
  • K-Release planning
    • use case driven implementation
    • demonstrator  in Montreal (O-RAN f2f Oct 17?)
    • A1 controller from ONAP
    • focus more on integration → to help Bimo
    • by Subhash (AIMLFW)
      • add AI to the NonRtRic/NearRtRic integration
      • needs to be architect-ed
      • init on a wiki 

• SIM: Alex Stancu
  • schema-mount implementation ongoing as presented in ONE Summit in AprilJ-Release done!
  •  K-Release
    • Sim architecture updates → pushed to next release
  • J-Release preparation
    • no new use cases
    • → enhancing sim infrastructure
      • e.g. go from C to Python using the Python APIs from netopeer and sysrepo
    • keep up-to-date with O-RAN Specs
  • O2 interface requested by ToC - no requirements
  • • new py implementation of O1 and OFHM for sims
    • use sims for integration
    • by Subhash
      • data from viavi 
      • maybe another data source/data set → Bimo may know
      • check
    Datasets for AI/ML and other cases
    • Please see
      • : https://wiki.o-ran-sc.org/display/SIM/Simulated+datasets
        
        

• OAM: Martin Skorupski
  • J-Release tagged
  • 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?
      
      • open

• O-DU: @Vidhu
  • • No update this week
      
      

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

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

  • flight integration of pipeline management
  • model retraining study 
  • highlight for J → upgrade of the platform
  • K-ReleaseDemo under preparation
    • spec alignment with O-RAN next train
    • 
      
      

• SMO: Seshu Kumar Mudiganti 
  • • Minutes & Meeting: Meeting notes 
    • J Release planning
      • integration point OAI, Nephio, O-RAN-SC
        
    • by John: Topo seed code under review
    • • 
        

• INT: James Li(CMTI)
  • ODU-Low and Taiwan lab - trouble shooting
  • f2f - provide feature mapping to specs
  • demo request for f2f - maybe with Bimo - AI/ML will be involved (?)
  • Conversation with POWDER - What O-RAN-SC is using POWDER for - collaboration with OAI → ToC
  Preparation of ONE Summit ... ( - especially for RIC-APP ) 
  
  • no report

• RSAC:
  • Minutes: RSAC Meetings