2025 Q1 (Jan, Feb, Mar)
2025 03 27
Recording
Meeting Recording: link
Agenda
Scribe: @Jakub Novy [DTAG] via recording
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo
2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange
2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson
2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T
Roll Call & Quorum Check
Company | Contact Name | Attendance | Alternate Contact | Attendance |
|---|---|---|---|---|
David Kinsey Co-Chair | X | Tracy Van Brakle |
| |
Jinri Huang Co-Chair |
| James Li | X | |
Jakub Nový |
|
|
| |
Sandeep Sarma | X | John Keeney |
| |
Yasufumi Morioka | X | Minami Ishii |
| |
Arunkumar Halebid |
| Abdul Wahid |
| |
Julien Boudani |
| Oumayma Charrad | X | |
Ganesh Shenbagaraman |
| Ankit Barve | X | |
Andrea Buldorini |
|
|
| |
Jackie Huang |
| Jon Zhang |
| |
Ultan Kelly |
| Baruch Friedman |
| |
Avinash Bhat | X | Peter Moonki Hong |
|
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.
Review of Today's Agenda
Roll Call
Review previous meeting minutes Mar 20, 2025
Next Meeting Apr 3, 2025
Release Update
O-RAN Business - OSFG Update & F2F Meeting
O-RAN Open-Source Workshop
Release J & K PR Statement
Old Business
Project Updates
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @James Li: Motion to Approve; Seconded by @Sandeep Sarma (Ericsson); No Objections. Mar 20, 2025 Minutes approved.
Release
03-27: @Sally Cooper: waiting for the last approval from Intel, but it should come in. Logo solved.
03-20: not all input from PTLs received. Discussion about objective continues. Most of the project participating in RSAC knows what to do, but it needs to be documented.
03-13: Schedule under L-Release Timeline - Releases - Confluence/Wiki. We are finishing sprint 1. PLT asked to update the objectives.
03-06: No news. Next release planned for June, following 3 releases per year.
02-20: @David Kinsey [AT&T] will check with Katie to get approval on the AT&T quote in PR. @Sally Cooper: there's also one for China Mobile.
02-13: @David Kinsey [AT&T]O-RAN alliance is okay with the J/K press release being published on the the Linux Channel as well as the Oran Channel, but they do want it to be a joint release. @Sally Cooperwill work with Zbynek on this.
02-06: @Sally Cooper: Got some feedback from Orange on the press release; are waiting for approval. And we'd like to get this published before the 10th so we can include it in the upcoming Linux Foundation Newsletter.
01-30: Press Release for K Release recommended to be released before Feb 10th. Some comments are still outstanding.
01-23: Press Release for K Release same status as 01-16. Sally has pinged AT&T for feedback.
01-16: Press Release for K Release is a work in progress and out for approval with quotes. Waiting for individual companies to get their internal PR approval. Suggestion to create a follow-up Blog to elaborate further on the technical details. @Sally Cooper to publish.
Release Votes (checklist) and Approval
01-09: @Sridhar Rao Most of the Checklist is complete. A Couple of outliers which should be complete today.
Branching for ODUHIGH
A couple of Projects for Release Notes: PTL are already engaged
Sally Cooper working on PR statement for TSC to approve, if not then will use previous blog method for release communications.
@Sridhar Rao Will provide either PR for TSC to approve for TSC status report on 01-10 or we will use the blog method
Other
02-06 : Maintenance Release
Subhash: AI/ML completed all requirements for the maintenance release, will drop a label for the release
@Alex Stancu: will create a maintenance branch for the SIM project too.
Peter Moonki Hong from Samsung raised a motion to approve the maintenance, and @Ankit Barve seconded. Motion approved.
01-30 : Maintenance Release
@Abdul Wahid noted that the conflict manager will be in the release.
01-23 : Maintenance Release
AI/ML framework updates on track but to be finalized.
Python Simulator updates noted as complete.
RIC Platform Updates need to be confirmed.
01-16: Maintenance Release
AI/ML framework updates to be confirmed
Python Simulator updates noted as complete
RIC Platform Updates need to be confirmed.
01-09: Maintenance Release due early February
AIMLFW: Unit Test Coverage increase/minor bug fixes
SIM: New Python Simulator, some hicups in the Repo requires some correction.
RICPLT: Conflict Manager Phase 1 missed K release but will likely be in the Maintenance release
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
03-27: @Martin Skorupski page Common Vulnerabilities and Exposures (CVE) updated with status column. @Sridhar Rao will also improve the LNF scans as we go from Jenkins to Gitlab actions. The scan will work only on build. Infrastructure is there (https://github.com/lfit/releng-reusable-workflows ) and open to anyone who wants to try it.
03-20: @Martin Skorupski there is a table at RSAC wiki with status. In discussion with PTLs. Will add columns for release when CVE was discovered and resolved.
03-12: @Martin Skorupski: feedback period running. @David Kinsey [AT&T]: maybe it is too general, some CVEs were already closed. Someone should look at the new CVEs. If something is corrected, it should be mentioned in our release notes. The CVD process of O-RAN covers the update of CVE status in the database. We need just to report the updates to O-RAN.
03-12: @Jakub Novy [DTAG]: do we have a statement in OSC's code that we provide it "as is"? @David Kinsey [AT&T] / @Martin Skorupski: it is in both licenses we are using.
03-06: From WG11 towards OSC. There is a new CVE discovered (CVE-2024-34035, CVE-2024-34036). WG11 asks position of OSC regarding CVEs. @Martin Skorupski: we are contribution driven, so we cannot guarantee that it will be fixed. Draft of the statement is here: https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/333381634/Common+Vulnerabilities+and+Exposures+CVE. @Martin Skorupski to share via mail and TOC to approve next week(s).
Rutgers Access Policies
03-06: @Martin Skorupski: Request for AccessPolicies by Rutgers (new O-RAN-SC Lab): draft answer to 4 questions here: OWL- Open Wireless Lab#O-RAN-SC-Access-and-Use-Policy
@Tracy Van Brakle: Keysight and Viavi wants to have a special ID to track the usage of their tools. @Martin Skorupski:How should be the access approved? By OSC TOC.
03-13: access list here: OWL- Open Wireless Lab - Requirements and Software Architecture Committee - Confluence/Wiki, not yet fully implemented.
02-13: presentation on “Analysis of Opensource Near-RT-RIC” by Rimedo Labs. The presentation PPT at the meeting is not yet available, but a copy of the latest draft report can be found here
01-23: MoU between LFN and O-RAN Alliance: Closed Out
01-16: MoU between LFN and O-RAN Alliance: Back on track after a 2 month delay. Closed out wording between the STFG, OSFG and OSC. To be approved by legal and the EC. Final step is to send back to the LFN and create Press Release.
01-09: MoU between LFN and O-RAN Alliance: work still in progress on next weeks OSFG agenda. James will provide David with latest draft to try and expedite changes.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
03-27: @David Kinsey [AT&T] no update about tooling, will provide next week.
03-27: @Sridhar Rao logo now fixed.
03-20: @Sridhar Rao there is an O-RAN logo at docs.o-ran-sc.org. @David Kinsey [AT&T] It is there since beginning. If O-RAN does not approve it, we can change it. @James Li to reach out to PTL for DOC project, Wichen Ni
03-06: @Tracy Van Brakle OSC development efforts in Rutgers will be supported by new tools (O-RU, RICtest). Finalizing the procurement with O-RAN office now.
OSFG updates:
Workshop:
03-27: workshop will be in Kista, Irfan and John will be present, not David. Local contact known to align details. David will share the agenda with Sridhar. John will manage the booking of a room.
03-20: @Sridhar Rao will reach to other LNF projects if they are interested if the date is decided. @David Kinsey [AT&T] if its in Kista, then the date is set. It is not sure if its full day/half day. @Sridhar Rao will make a poll to see who from OSC can join on 23rd of May. @James Li will add a topic on Monday's OSFG call to prepare a paragraph about it which Sridhar can share with other projects.
03-20: @David Kinsey [AT&T]can send a mail to reflector about the possible topics. Will push at OSFG. No other update.
03-13: currently three options, see below.
OAI workshop:
03-13: @David Kinsey [AT&T] May 21-22 (Wed-Thu) in Kista, Sweeden. If we would be present, we need to start preparing the line-up. So far we do not have the confirmation from various communities if they can attend - deadline is in two weeks, it will be difficult to manage. https://openairinterface.org/summer-2025-workshop-the-openairinterface-path-to-ai-driven-6g/
03-13: @John Keeney (Ericsson EST) might be able to secure an Ericsson location in Kista.
Open Source workshop:
03-13: Other option is to join the LNF at end of June in Denver. We would still need to work on it soon. https://events.linuxfoundation.org/open-source-summit-north-america/
03-06: @Tracy Van Brakle we should discuss demos with OAI and Nephio - better to wait for David and Irfan to be back
02-20: @David Kinsey [AT&T] there will be a presentation cannot share it right now. It needs to be presented at the opening session at the F2F to the TSC. Will be able to share it then at next week TOC call. At the ETSI SNS4SNS Telefonica presented this archetypical golden loop that there are flows to open source, and from open source, and that goes both from the specification bodies and the testing bodies. In OSC we are missing those. We send our feedback back to the specification bodies. But they don't give us any direct feedback. And so there's a recommendation for the working groups to become more involved in the open source activities that are active in their area, and OSFG would help or provide that gateway for that communication, and some agreements or alignments would have to occur between OSFG and those working groups unless working groups are willing to reach out and and talk directly with the open source communities. So there needs to be an engagement on the specification side to the open source communities. The other side of the thing is testing. Our OTICs do plugfests, and other activities; but from an open source community we would gravitate to do things like hackathons, in various flavors as how to use the software, how to to leverage the software, how to develop the software etc.. The activity to organize and put on a hackathon are similar activities for a plugfest. So OTICs might facilitate and support hackathons, and provide a feedback loop. Additionally, other open source communities can submit their software to an OTIC for badging or testing for compliance if they are following O-RAN specifications. The 3rd leg is about over a dozen different players on the field, that all are somehow related, or in the conversations around O-RAN. Today they're all disorganized and not building to a common blueprint. So the recommendation is to have this workshop to have those communities come together and work out how to best align these projects so that the work done is more focused. However, like OSC who has its mandate from from O-RAN to demonstrate their architecture and execute on their specifications. Any other open source communities that would be part of this common blueprint has to sign up this mandate. These are what the workshop is going to be geared towards trying to achieve. At the F2F there will be a couple sessions on the planning of such a workshop. The workshop can co-locate with the F2F just like the 6G workshop in the past.
02-13: @David Kinsey [AT&T]OSFG is working on an open source workshop. See if we can get a bunch of the open source projects related to O-RAN, or might be related to O-RAN, or could be related to O-RAN and and try to get them together and discuss how they can play together. Goals of the workshop are to get the projects to align and commit to a blueprint. There'll be a couple of sessions for planning at the F2F for that.
Workshop at O-RAN F2F
03-13: Possible, It will be difficult to collocate due to large overlap with other O-RAN meetings. OSC co-chairs are also active in the WGs as well as many of the TOC members.
O-RAN SCCL enforcement:
03-20: @Jakub Novy [DTAG]: still waiting for O-RAN legeal, OCOP clarifications.
03-13: @Jakub Novy [DTAG]: in progress, pending confirmation from O-RAN legal.
03-06: @Jakub Novy [DTAG]: in progress, received feedback during F2F, demo repo prepared, OSARP document is under development.
01-23: @Jakub Novy [DTAG] mentioned test/demo was in progress. Artifact release process is to be reviewed by all.
01-16: OSFG Part complete but had discussion about the post-process and how to publish on public site from ORAN. Test build to be scheduled by @@Martin Skorupski Publication release process was already reviewed by Jakob and Martin. @huangjinri@chinamobile.com to add an agenda item to explain the process for the TSC Opening Session at the Face to Face meeting. @David Kinsey [AT&T], @Jakub Novy [DTAG], @Martin Skorupski to come up with wording for the description based on SCCP repo. and existing draft.
01-09: O-RAN Process being submitted to OCOP. Need to understand how publication to OSC occurs.
Collaboration with OAI (lab interconnection) and Nephio
03-20: @Martin Skorupski OAI and Nephio artifacts are already in one lab in France, so it works.
03-06: no update
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.
03-06: no update
Face-to-Face Meeting
03-06: Jinri: good event. We discussed the collaboration with standardization part, workshop, there were on-site and on-line demos. Next F2F planned for June.
02-20:
F2F sessions link 2025-02 O-RAN F2F Paris updated to include more details, such as the OSFG discussions with various WGs, and demo details, etc. With @Sally Cooper's help one can upload the demo video to Youtube at this video link. Only the OSC sessions are available to public on Zoom (demo sessions on the RSAC Zoom Bridge, and TOC on the TOC Zoom bridge), and OSFG meetings are for O-RAN members on their WebEx. AP: @James Li to reach out to @Irfan Ghauri (OAI) to find out detailed agenda for each of the four OSFG sessions for @David Kinsey [AT&T] to coordinate with his other sessions and ensure his availability for those related to the open-source workshop.
Lobby demo to demonstrates the full use of both OSC and OAI for an actual O-RAN implementation from the radio and the management (SMO) all together. Got some pushback from EC and now it's going through the process of mail approval from EC board members.
@bimo fransiscus asisi: 1) needs transition of ownership of the it/dep repo (@James Li will work with him on this); 2) status of ASN.1 compiler – hasn't heard back from Nokia. Not sure whether it needs to escalate to TOC to change to a different one (currently use the one that OAI uses); 3) break down of the end-to-end integration use case of energy saving, perhaps will discuss at RSAC; 4) update the calendar of the TOC meeting as it shows the wrong time (supposed to be 10 pm instead of 9 pm Taipei time). @Martin Skorupski has similar issue with RSAC meeting schedule on calendar when it was moved by 1 hour. @Sridhar Rao will help.
02-13:
@Martin Skorupski3 sessions scheduled for OSC, one on Wednesday 2/26, and two on Thursday 2/27. The TOC meeting on Thursday is scheduled as usual, but the bridge will be open 15 minutes earlier but starts at 9am EST.
The lobby demo at the F2F is a joint OSC/OAI demo, with OAM, Non RT RIC and Simulators from OSC, and CU/DU from OAI.
02-06: @Martin Skorupski created F2F preparations here: 2025-02 O-RAN F2F Paris that covers the sessions with WGs (agenda not finalized yet, at least one with WG1 on decoupled SMO; SCCL discussion with WG2 and WG6, @Martin Skorupskiwill reach out to WG11 as well; could be an interesting topic about machine readable testing results with TIFG), as well as a page for OSC demos (should have enough for 90 minutes demo session).
01-30: The lobby demo was finalized (3x30 minutes demos); Asking for 2 sessions of OSC but some items missing. @Martin Skorupski to reach out to the working groups to get 30mins on their sessions/calendar.
01-23: Face-to-Face Meeting planning in progress
Demo will be remote hence requested Internet Access
Requires one demo session. Discussion about various Working Groups for input. Need to get this topic on their calendars and @David Kinsey [AT&T] can help @Martin Skorupskiachieve this.
01-16: Face-to-Face Meeting planning in progress
Noted that Sridhar can attend.
Lobby Demo write-up with short description of demo
To be approved by EC for meeting next Wednesday. Draft developed on the call and @huangjinri@chinamobile.com to finalize with Martin & Sridhar to provide feedback. David referenced the O-RAN Handbook section 2.4.2.2 for guidelines. Demo name to be confirmed along the lines of 'OAI/OSC Feature Integration' with DU/CU/SMO with configurations on DU, O1 Get Request to CU and OFH M-Plane as a stepping stone for the Super Wireless Blueprint.
Other
@Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.
Old Business
ASN.1 compiler
03-27: @Martin Skorupski: wiki page created based on discussion last week: ASN.1 Compiler. There is a pointer at gerrit to very old and unused compiler. Some people were using the Nokia one which is not too active either. Suggestion is to use another ASN.1 compiler, which is up-to-date. The code needs to be changed to reflect the change. This wiki can be a guidance for the future.
03-20: ASN.1 compiler issues - can we switch to the OAI one? There is also almost empty repo which needs to be updated/deleted. @bimo fransiscus asisi we need some official step to inform projects to use a different compiler. @Martin Skorupski will prepare a material for next meeting and vote.
03-20: still looking for a new RSAC co-chair.
02-13: RSAC: We'll begin that solicitation today for another RSAC co-chair, as Ritwick confirmed this week he doesn't have the capacity to continue. Anybody who wants to self nominate or knows somebody that would be interested can propose
Project Updates
RSAC - @Rittwik Jana or @Martin Skorupski
01-09 There might be an OSC/OAI integration demo in the F2F lobby
01-09 There are a couple of demos that weren't ready for Oct F2F which will be presented in March F2F. Might only need 1 session.
01-09 Would like @Sridhar Rao to be invited to March F2F OSFG/OSC sessions. He will need a visa so we need to start this soon.
INT - @bimo fransiscus asisi
03-27: @bimo fransiscus asisi: There is a Discussion End-to-End Integration page to have end-to-end call in INT project. Call for anyone who wants to participate. There is one energy use case from TIFG. It was discussed at the RSAP. Feedback welcomed.
02-06: @bimo fransiscus asisi has a quick reminder for everyone that slack will be the main platform for communication, especially with PTLs. Please let him know if you have issue regarding using slack as project updates.
01-23: Intel's internal test case fails. @Ray-Guang Cheng looking for TM500 configuration. NTUST blocked and further progress will be delayed due to the lunar new year holiday.
01-16: There is a bottleneck bt. FlexRan and TM500. @fransiscus bimo to work with Intel at the next the RSAC about the configuration. Plan is to get working TM500 and gNB configuration used with the OAI gNB and repeat it after checking parameters that are likely to change (Frequency and compression bits).
01-09: @Ray-Guang Cheng: Problem with integrated O-DU not communicating with TM-500. @David Kinsey [AT&T]:Need project help to debug. RSAC to help do incremental builds to identify when disconnect occurs: 1) ODULOW → TM500 2) xFAPI->ODULOW→TM500 5) ODUHIGH->xFAPI->ODULOW→TM500. Need to isolate since all three components indicate they don't have a defect but integrated build doesn't work.
ASN.1 Fix
01-16: Still open - Status remains the same due to absence.
01-09: @bimo fransiscus asisi: Need ASN1 fix. @abdulwahid.w: Nokia has a resource but haven't reached out since new year. Wahid will get a status.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti