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#

• 2023-01-25 John Keeney
• 2023-02-01 Martin Skorupski 
• 2023-02-08 John Keeney
• 2023-02-15 Martin Skorupski 

• O-RAN-SC ToC

• • https://wiki.o-ran-sc.org/display/TOC#ORANSCTechnicalOversightCommittee(TOC)
    • ONAP TSC/O-RAN-SC ToC collaboration
    • updates on LFN Induvial dashboard (https://openprofile.dev) required for proper statistics at insights (https://insights.lfx.linuxfoundation.org/projects/oran/dashboard;subTab=technical)

• Non-RT-RIC: John Keeney
  • H-Release planning
    • data management exposure
      • data type filtering
    • service management exposure
      • auth
      • rApp management
    • rsac inputs
    • interfacing with ai/ml project artifacts
    • rApp package and its definition in O-RAN Alliance
  • checkout Jira

• SIM: Alex Stancu
  • H-Release planning
  • Trigger SIM for sending VES messages via ODLUX.

• OAM: Martin Skorupski
  • updates according O-RAN OAM-Interface Spec
  • Working on updating stndDefined VES messages with latest artifacts from 3GPP REL-18
    • using Node-Red to visualize the flows
• O-DU:HariomGupta(HCL) / @Vidhu
  
  • No update this week

• AI/ML: @Sandeep J
  • No update this week

• RSAC/SMO:David Kinsey 
  • SMO turned into RSAC call - please see RSAC meeting minutes
    • how to package SMO functions into an pure O-RAN-SC blueprint
    • AI for James
• INT: James Li(CMTI)
  • No update this week

ONAP TSC discussed in 2022-12 that we shall synch with you and John in terms of your recent activities around ONAP/O-RAN-SC/SMO.

Do you think we could have a short chat at the next Wednesday’s meeting (6 PM CET) you run?

Problem statement and objectives

• formalize interaction between ONAP and O-RAN-SC
• prio activities in ONAP
• O-RAN Alliance interactions
• avoid fragmentation 
  • needs awareness of tasks and use cases
  • and finally alignment of tasks, use cases and time lines

1 - Releases and requirements: 

• cadence between ONAP and OSC
• they have a peer relationship
• both upstream and downstream.

(see also previous minutes)

2. Relationships: LFN/LF, OSC/O-RAN, OSC/ONAP/O-RAN

- OSC does not have special relationship with O-RAN Alliance

- ONAP and OSC have same relationship with O-RAN Alliance (license issues to use specs from O-RAN Alliance)

• LFN projects - O-RAN-SC is not part
  • O-RAN Alliance and O-RAN-SC relationship - no specific 
    • issue of licence

• input from dev to specs

3.  List specific examples of areas of interaction and issues involved:

• release cadence
• non-rt-ric
• rapps
• oam
• orchestration and cloud
• simulator (cu,du,ru)
• use cases alignment 
• integration
• license issues

potential actions

• bring together ONAP REQ and O-RAN-SC RSAC - just a "hello"
• bring together ONAP TSC and O-RAN-SC ToC
• explanation of the diff between O-RAN Alliance and O-RAN-SC
  • This page talks about *TWO* project streams managed by the TOC. https://www.o-ran.org/software

2023-01-18 update: N.K. Shankaranarayanan 

• TSC was looking to the meeting minutes
• AI was defined for a handshake as proposed above
• on the TSC agenda also tomorrow
• please see TSC minutes (2023 TSC MEETING MINUTES )....

2032-01-25 update:

Planning for ONAP London

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