O-RAN SC Technical Oversight Committee (TOC)
Table of Contents
- 1 Technical Charter for O-RAN Software Community
- 2 TOC Voting Members
- 3 TOC Meeting Info
- 4 TOC Documents repository
- 5 2025 06 12
- 6 2025 06 05
- 7 2025 05 29
- 8 2025 05 22
- 9 2025 05 15
- 10 2025 05 08
- 11 2025 04 24
- 12 2025 04 17
- 13 2025 04 10
- 14 2025 04 03
- 15 2025 03 27
- 16 2025 03 20
- 17 2025 03 13
- 18 2025 03 06
- 19 2025 02 27
- 20 2025 02 20
- 21 2025 02 13
- 22 2025 02 06
- 23 Archived Meetings
TOC Voting Members
Company | Name | Alternate |
---|---|---|
David Kinsey Co-Chair | ||
Jinri Huang Co-Chair | James Li | |
Jakub Nový | ||
Sandeep Sarma | John Keeney | |
Yasufumi Morioka | Minami Ishii | |
Arunkumar Halebid | Abdulwahid | |
Julien Boudani | Oumayma Charrad | |
Ganesh Shenbagaraman | Ankit Barve | |
Andrea Buldorini | ||
Jackie Huang | Jon Zhang | |
Ultan Kelly | Baruch Friedman | |
Avinash Bhat | Peter Moonki Hong |
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.
TOC Meeting Info
Technical Oversight Committee meetings are open to the public [ changed as of 5/5/2022] and no longer on Wednesdays at 8 AM Eastern Time USA. World Time Zone Map
We meet on Thursdays, at 9am EST. Time Zone Map
Zoom 2 Info:
Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/7562808472
Or Telephone: Dial (for higher quality, dial a number based on your current location)
855 880 1246 (Toll Free), 877 369 0926 (Toll Free)
Meeting ID: 7562808472
International numbers available: https://zoom.us/u/avfEhZhiB
City | Time | Zoom/Audio Bridge |
---|---|---|
9 AM Eastern Time USA. World Time Zone Map | ||
New York (EST / UTC-5) | 9 AM Eastern Time USA. World Time Zone Map | +1 669 900 6833, +1 646 558 8656, 855 880 1246 (Toll Free), 877 369 0926 (Toll Free), Meeting ID: 756 280 8472 |
Paris (CET / UTC+1) | 9 AM Eastern Time USA. World Time Zone Map | +33 7 5678 4048, +33 1 8288 0188, 805 082 588 (Toll Free), Meeting ID: 756 280 8472 |
Beijing (CST / UTC+8) | 9 AM Eastern Time USA. World Time Zone Map | +86 10 87833177, +86 10 53876330, 400 616 8835 (Toll Free), 400 669 9381 (Toll Free), Meeting ID: 756 280 8472 |
Tokyo (JST / UTC+9) | 9 AM Eastern Time USA. World Time Zone Map | +81 524 564 439, +81 3 4578 1488, 0 800 100 5040 (Toll Free), Meeting ID: 756 280 8472 |
Helsinki (EET / UTC+2) | 9 AM Eastern Time USA. World Time Zone Map | +358 341092129, Meeting ID: 756 280 8472 |
TOC Documents repository
2025 06 12
Recording
Meeting Recording:
Agenda
Scribe: David Kinsey (AT&T)
Previous scribe:
2025 => June: AT&T; May: Nokia; April: NTT Docomo; March: DTAG; February: China Mobile; January: Viavi2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia
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 |
|
|
| |
Jinri Huang Co-Chair |
| James Li |
| |
Jakub Nový |
|
|
| |
Sandeep Sarma |
| John Keeney |
| |
Yasufumi Morioka |
| Minami Ishii |
| |
Arunkumar Halebid |
| Abdul Wahid |
| |
Julien Boudani |
| Oumayma Charrad |
| |
Ganesh Shenbagaraman |
| Ankit Barve |
| |
Andrea Buldorini |
| Sergio Benco |
| |
Jackie Huang |
| Jon Zhang |
| |
Ultan Kelly |
| Baruch Friedman |
| |
Avinash Bhat |
| 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 May 29, 2025 Jun 5, 2025
Next Meeting Jun 19, 2025
Release Update
New repo requests
05-08: AIMLFW repository approved by TOC
New business
O-RAN Business - OSFG Update & F2F Meeting
Tooling budget update
SCCL enforcement
Old Business
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: Lack of Quorum Meeting minutes not reviewed
Release
06-05: Release Vote 06-26 TOC Meeting
06-05: RSAC will work with PTLs to complete release highlights
05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.
05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.
Other
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
05-29: Some strategies to work on CVE’s -
companies using OSC code in their product would solve these CVE issues, to comply by providing the same fixes in OSC too.
Scanning and reporting of CVE’s is welcome, however the fixing of CVE’s is not guaranteed.
Scanning code based on the production code rather than the prototype code.
For maintainablity, common/production base image could be regularly updated by LF.
Document all the CVE’s raised with a Jira possibly. PTL’s to check and analyse the reports for thier respective projects.
05-22: To think on on strategy as a blog/write up on how the CVE’s are handled. Still waitig on this. @Sridhar Rao may have some insights.
05-15: Need some actions on this. Waiting for David .
Rutgers Access Policies
05-15: Couple of new servers assigned, totally 10 servers available. Work is needed to get those up and running.
k8s version deprecation
05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG updates:
Workshop:
06-05: 2nd Workshop outline from OSFG, looking for 2-day venue and date in September.
05-29: Workshop updates like potential open source projects that are interested, issues with addressing CVE’s in open src,LF projects working with ORAN can attend ORAN events post approvals.
05-22: Workshop is on 05-23.
O-RAN SCCL enforcement:
06-05: OSARP reviewed by OCOP. Some comments taken, edits in progress.
06-05: Document might be ready to be approved by July Train but WGs won’t be able to adopt it in time. Therefore, looking for post July Train completion and adoption.
06-05: Might be able to take a copy early if merged into the main branch by the WG. License has to be applied by O-RAN before a copy can be taken.
05-22: Demo is not presented to ORAN. Document is almost ready for approval, probably for June release. License(example template) is available in o-ran.org/scc
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
ORAN Tooling
06-05: O-RAN CFO needs to understand the business value of open source
05-22: AT&T wil not be able to take the funds from ORAN to buy tools. Till then need strategy touse with the existing stubs and simulators for testing.
OSC/OSFG Update for TSC
06-05: Deck reviewed and updated
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.
05-15: Professor Ray to attend F2F in June, one panel reserved for ORAN .
05-08: Panels reservation required. Need to check further.
Old Business
RSAC co-chair
04-17: no update; still looking for.
Project Updates
RSAC - @Martin Skorupski
INT - @bimo fransiscus asisi
05-22: Post reconfiguration TM500 is able to connect to ODU low. Professor Vipin working on the xFAPI issue by removing the code dependency on the module. Legal issues to be addressed as some code used is licensed.
05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
05-15: No updates.
Internship update
Meeting Summary and Closure
Next Meeting Jun 19, 2025 starts by 18:15
2025 06 05
Recording
Meeting Recording:
Agenda
Scribe: David Kinsey (AT&T)
Previous scribe:
2025 => June: AT&T; May: Nokia; April: NTT Docomo; March: DTAG; February: China Mobile; January: Viavi
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 |
|
| |
Jinri Huang Co-Chair | X | James Li |
| |
Jakub Nový | X |
|
| |
Sandeep Sarma |
| John Keeney | X | |
Yasufumi Morioka |
| Minami Ishii |
| |
Arunkumar Halebid |
| Abdul Wahid |
| |
Julien Boudani | X | Oumayma Charrad |
| |
Ganesh Shenbagaraman |
| Ankit Barve |
| |
Andrea Buldorini | X | Sergio Benco |
| |
Jackie Huang |
| Jon Zhang |
| |
Ultan Kelly |
| Baruch Friedman |
| |
Avinash Bhat |
| Subhash | X |
*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 May 29, 2025
Next Meeting Jun 12, 2025
Release Update
New repo requests
05-08: AIMLFW repository approved by TOC
New business
O-RAN Business - OSFG Update & F2F Meeting
Tooling budget update
SCCL enforcement
Old Business
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: Lack of Quorum Meeting minutes not reviewed
Release
06-05: Release Vote 06-26 TOC Meeting
06-05: RSAC will work with PTLs to complete release highlights
05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.
05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.
Other
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
05-29: Some strategies to work on CVE’s -
companies using OSC code in their product would solve these CVE issues, to comply by providing the same fixes in OSC too.
Scanning and reporting of CVE’s is welcome, however the fixing of CVE’s is not guaranteed.
Scanning code based on the production code rather than the prototype code.
For maintainablity, common/production base image could be regularly updated by LF.
Document all the CVE’s raised with a Jira possibly. PTL’s to check and analyse the reports for thier respective projects.
05-22: To think on on strategy as a blog/write up on how the CVE’s are handled. Still waitig on this. @Sridhar Rao may have some insights.
05-15: Need some actions on this. Waiting for David .
Rutgers Access Policies
05-15: Couple of new servers assigned, totally 10 servers available. Work is needed to get those up and running.
k8s version deprecation
05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG updates:
Workshop:
06-05: 2nd Workshop outline from OSFG, looking for 2-day venue and date in September.
05-29: Workshop updates like potential open source projects that are interested, issues with addressing CVE’s in open src,LF projects working with ORAN can attend ORAN events post approvals.
05-22: Workshop is on 05-23.
O-RAN SCCL enforcement:
06-05: OSARP reviewed by OCOP. Some comments taken, edits in progress.
06-05: Document might be ready to be approved by July Train but WGs won’t be able to adopt it in time. Therefore, looking for post July Train completion and adoption.
06-05: Might be able to take a copy early if merged into the main branch by the WG. License has to be applied by O-RAN before a copy can be taken.
05-22: Demo is not presented to ORAN. Document is almost ready for approval, probably for June release. License(example template) is available in o-ran.org/scc
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
ORAN Tooling
06-05: O-RAN CFO needs to understand the business value of open source
05-22: AT&T wil not be able to take the funds from ORAN to buy tools. Till then need strategy touse with the existing stubs and simulators for testing.
OSC/OSFG Update for TSC
06-05: Deck reviewed and updated
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.
05-15: Professor Ray to attend F2F in June, one panel reserved for ORAN .
05-08: Panels reservation required. Need to check further.
Old Business
RSAC co-chair
04-17: no update; still looking for.
Project Updates
RSAC - @Martin Skorupski
INT - @bimo fransiscus asisi
05-22: Post reconfiguration TM500 is able to connect to ODU low. Professor Vipin working on the xFAPI issue by removing the code dependency on the module. Legal issues to be addressed as some code used is licensed.
05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
05-15: No updates.
Internship update
Meeting Summary and Closure
Next Meeting Jun 12, 2025
2025 05 29
Recording
Meeting Recording: link
Agenda
Scribe: @abdulwahid.w (Nokia)
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia
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 |
|
| |
Jinri Huang Co-Chair |
| James Li |
| |
Jakub Nový | x |
|
| |
Sandeep Sarma |
| John Keeney | x | |
Yasufumi Morioka | x | Minami Ishii |
| |
Arunkumar Halebid |
| Abdul Wahid | x | |
Julien Boudani |
| Oumayma Charrad |
| |
Ganesh Shenbagaraman |
| Ankit Barve | x | |
Andrea Buldorini | x | Sergio Benco |
| |
Jackie Huang | x | Jon Zhang |
| |
Ultan Kelly | x | Baruch Friedman |
| |
Avinash Bhat |
| 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 May 22, 2025
Next Meeting Jun 5, 2025
Release Update
New repo requests
05-08: AIMLFW repository approved by TOC
New business
O-RAN Business - OSFG Update & F2F Meeting
Tooling budget update
SCCL enforcement
Old Business
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @Ankit Barve Motion to Approve; Seconded by @David Kinsey [AT&T] . No Objections. May 29, 2025 Minutes approved.
Release
05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.
05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.
04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf
04-03: @Sally Cooper : PR has been approved. PR will post Apr 3, 2025
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.
Release Votes (checklist) and Approval
New repo request
04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections. Motion was carried.
04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.
Other
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
05-29: Some strategies to work on CVE’s -
companies using OSC code in their product would solve these CVE issues, to comply by providing the same fixes in OSC too.
Scanning and reporting of CVE’s is welcome, however the fixing of CVE’s is not guaranteed.
Scanning code based on the production code rather than the prototype code.
For maintainablity, common/production base image could be regularly updated by LF.
Document all the CVE’s raised with a Jira possibly. PTL’s to check and analyse the reports for thier respective projects.
05-22: To think on on strategy as a blog/write up on how the CVE’s are handled. Still waitig on this. @Sridhar Rao may have some insights.
05-15: Need some actions on this. Waiting for David .
04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.
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.
05-15: Couple of new servers assigned, totally 10 servers available. Work is needed to get those up and running.
k8s version deprecation
05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
04-24: @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.
04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.
04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.
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 http://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:
05-29: Workshop updates like potential open source projects that are interested, issues with addressing CVE’s in open src,LF projects working with ORAN can attend ORAN events post approvals.
05-22: Workshop is on 05-23.
04-24: registration was requested if attend to OAI workshop either in person of remotely.
04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.
04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.
04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista;
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
04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.
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
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:
05-22: Demo is not presented to ORAN. Document is almost ready for approval, probably for June release. License(example template) is available in o-ran.org/scc
04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed.
04-17: @Jakub Novy [DTAG] in progress, trying to get closed.
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.
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.
3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination
04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system.
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
ORAN Tooling
05-22: AT&T wil not be able to take the funds from ORAN to buy tools. Till then need strategy touse with the existing stubs and simulators for testing.
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.
05-08: Panels reservation required. Need to check further.
05-15: Professor Ray to attend F2F in June, one panel reserved for ORAN .
Old Business
RSAC co-chair
04-17: no update; still looking for.
04-10: no update. still looking for a new RSAC co-chair.
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
INT - @bimo fransiscus asisi
05-22: Post reconfiguration TM500 is able to connect to ODU low. Professor Vipin working on the xFAPI issue by removing the code dependency on the module. Legal issues to be addressed as some code used is licensed.
05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.
04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.
04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.
04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)
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.
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.
SMO blueprint
04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
05-15: No updates.
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
Internship update
Meeting Summary and Closure
03-27: @David Kinsey [AT&T] out on May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting Jun 5, 2025 starts by 18:15
2025 05 22
Recording
Meeting Recording: link
Agenda
Scribe: @abdulwahid.w (Nokia)
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia
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 |
|
| |
Jinri Huang Co-Chair | x | James Li |
| |
Jakub Nový | x |
|
| |
Sandeep Sarma |
| John Keeney |
| |
Yasufumi Morioka | x | Minami Ishii |
| |
Arunkumar Halebid |
| Abdul Wahid | x | |
Julien Boudani | x | Oumayma Charrad | x | |
Ganesh Shenbagaraman |
| Ankit Barve | x | |
Andrea Buldorini |
| Sergio Benco |
| |
Jackie Huang | x | Jon Zhang |
| |
Ultan Kelly | x | 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 May 15, 2025
Next Meeting May 29, 2025
Release Update
New repo requests
08.05: AIMLFW repository approved by TOC
New business
O-RAN Business - OSFG Update & F2F Meeting
Tooling budget update
SCCL enforcement
Old Business
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @David Kinsey [AT&T] Motion to Approve; Seconded by @Ultan.Kelly . No Objections. May 22, 2025 Minutes approved.
Release
05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.
05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.
04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf
04-03: @Sally Cooper : PR has been approved. PR will post Apr 3, 2025
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.
Release Votes (checklist) and Approval
New repo request
04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections. Motion was carried.
04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.
Other
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
05-22: To think on on strategy as a blog/write up on how the CVE’s are handled. Still waitig on this. @Sridhar Rao may have some insights.
05-15: Need some actions on this. Waiting for David .
04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.
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.
05-15: Couple of new servers assigned, totally 10 servers available. Work is needed to get those up and running.
k8s version deprecation
05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
04-24: @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.
04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.
04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.
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 http://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:
05-22: Workshop is on 05-23.
04-24: registration was requested if attend to OAI workshop either in person of remotely.
04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.
04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.
04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista;
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
04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.
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
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:
05-22: Demo is not presented to ORAN. Document is almost ready for approval, probably for June release. License(example template) is available in o-ran.org/scc
04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed.
04-17: @Jakub Novy [DTAG] in progress, trying to get closed.
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.
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.
3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination
04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system.
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
ORAN Tooling
05-22: AT&T wil not be able to take the funds from ORAN to buy tools. Till then need strategy touse with the existing stubs and simulators for testing.
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.
05-08: Panels reservation required. Need to check further.
05-15: Professor Ray to attend F2F in June, one panel reserved for ORAN .
Old Business
RSAC co-chair
04-17: no update; still looking for.
04-10: no update. still looking for a new RSAC co-chair.
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
INT - @bimo fransiscus asisi
05-22: Post reconfiguration TM500 is able to connect to ODU low. Professor Vipin working on the xFAPI issue by removing the code dependency on the module. Legal issues to be addressed as some code used is licensed.
05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.
04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.
04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.
04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)
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.
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.
SMO blueprint
04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
05-15: No updates.
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
Internship update
Meeting Summary and Closure
03-27: @David Kinsey [AT&T] out on May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting May 29, 2025
2025 05 15
Recording
Meeting Recording: link
Agenda
Scribe: @abdulwahid.w (Nokia)
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia
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 | ||||
Jinri Huang Co-Chair | James Li | |||
Jakub Nový | x | |||
Sandeep Sarma | x | John Keeney | ||
Yasufumi Morioka | x | Minami Ishii | ||
Arunkumar Halebid | Abdul Wahid | x | ||
Julien Boudani | Oumayma Charrad | x | ||
Ganesh Shenbagaraman | Ankit Barve | x | ||
Andrea Buldorini | Sergio Benco | x | ||
Jackie Huang | x | Jon Zhang | ||
Ultan Kelly | x | 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 May 8, 2025
Next Meeting May 22, 2025
Release Update
New repo requests
08.05: AIMLFW repository approved by TOC
New business
O-RAN Business - OSFG Update & F2F Meeting
Tooling budget update
SCCL enforcement
Old Business
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @Avinash Bhat Motion to Approve; Seconded by @Jakub Novy [DTAG]. No Objections. May 8, 2025 Minutes approved.
Release
05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.
05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.
04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf
04-03: @Sally Cooper : PR has been approved. PR will post Apr 3, 2025
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.
Release Votes (checklist) and Approval
New repo request
04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections. Motion was carried.
04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.
Other
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
05-15: Need some actions on this. Waiting for David .
04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.
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.
05-15: Couple of new servers assigned, totally 10 servers available. Work is needed toget those up and running.
k8s version deprecation
05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
04-24: @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.
04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.
04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.
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:
04-24: registration was requested if attend to OAI workshop either in person of remotely.
04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.
04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.
04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista;
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
04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.
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
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:
04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed.
04-17: @Jakub Novy [DTAG] in progress, trying to get closed.
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.
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.
3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination
04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system.
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
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.
05-08: Panels reservation required. Need to check further.
05-15: James to attend F2F in June, one panel reserved for ORAN .
Old Business
RSAC co-chair
04-17: no update; still looking for.
04-10: no update. still looking for a new RSAC co-chair.
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
INT - @bimo fransiscus asisi
05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.
04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.
04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.
04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)
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.
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.
SMO blueprint
04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
05-15: No updates.
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
Internship update
8. Meeting Summary and Closure
03-27: @David Kinsey [AT&T] out on May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting May 22, 2025 : @Martin Skorupski is tentative. Will send a mail on the next meeting based on Jinri and David's availability.
2025 05 08
Recording
Meeting Recording:
Agenda
Scribe: @abdulwahid.w (Nokia)
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia
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 | ||||
Jinri Huang Co-Chair | X | James Li | ||
Jakub Nový | X | |||
Sandeep Sarma | John Keeney | X | ||
Yasufumi Morioka | X | Minami Ishii | ||
Arunkumar Halebid | Abdul Wahid | X | ||
Julien Boudani | Oumayma Charrad | |||
Ganesh Shenbagaraman | Ankit Barve | X | ||
Andrea Buldorini | ||||
Jackie Huang | X | Jon Zhang | ||
Ultan Kelly | X | 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 Apr 17, 2025
Next Meeting May 8, 2025
Release Update
New repo requests
08.05: AIMLFW repository approved by TOC
New business
O-RAN Business - OSFG Update & F2F Meeting
Tooling budget update
SCCL enforcement
Old Business
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @Ankit Barve Motion to Approve; Seconded by @Sandeep Sarma (Ericsson); No Objections. Apr 24, 2025 Minutes approved.
Release
04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf
04-03: @Sally Cooper : PR has been approved. PR will post Apr 3, 2025
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.
Release Votes (checklist) and Approval
New repo request
04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections. Motion was carried.
04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.
Other
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.
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.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
04-24: @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.
04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.
04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.
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:
04-24: registration was requested if attend to OAI workshop either in person of remotely.
04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.
04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.
04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista;
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
04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.
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
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:
04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed.
04-17: @Jakub Novy [DTAG] in progress, trying to get closed.
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.
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.
3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination
04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system.
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
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.
05-08: Panels reservation required. Need to check further.
Old Business
ASN.1 compiler
05-08: This is completed
04-24: we will check the progress next week.
04-17: @Sridhar Rao still working for delete the ASN.1 compiler.
04-10: the archive ASN.1 compiler will be deleted by @Sridhar Rao Apr 10, 2025 .
04-03: @Sridhar Rao @Martin Skorupski @David Kinsey [AT&T] Motion to approve; Seconded by @Sridhar Rao; No Objections, the motion for "deleting the archive for the ASN1 compiler that is in error" is approved; @Sridhar Rao will delete the archive with error.
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.
RSAC co-chair
04-17: no update; still looking for.
04-10: no update. still looking for a new RSAC co-chair.
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
INT - @bimo fransiscus asisi
04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.
04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.
04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)
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.
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.
SMO blueprint
04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
Internship update
8. Meeting Summary and Closure
03-27: @David Kinsey [AT&T] out on May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting May 8, 2025
2025 04 24
Recording
Meeting Recording:
Agenda
Scribe: @Yasufumi Morioka (NTT Docomo)
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia
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 | |||
Jinri Huang Co-Chair | James Li | X | ||
Jakub Nový | ||||
Sandeep Sarma | X | John Keeney | X | |
Yasufumi Morioka | X | Minami Ishii | ||
Arunkumar Halebid | Abdul Wahid | X | ||
Julien Boudani | Oumayma Charrad | X | ||
Ganesh Shenbagaraman | Ankit Barve | X | ||
Andrea Buldorini | ||||
Jackie Huang | X | Jon Zhang | ||
Ultan Kelly | X | 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 Apr 17, 2025
Next Meeting May 1, 2025
Release Update
New repo requests
New business
O-RAN Business - OSFG Update & F2F Meeting
Tooling budget update
SCCL enforcement
Old Business
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @Ankit Barve Motion to Approve; Seconded by @Sandeep Sarma (Ericsson); No Objections. Apr 17, 2025 Minutes approved.
Release
04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf
04-03: @Sally Cooper : PR has been approved. PR will post Apr 3, 2025
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.
Release Votes (checklist) and Approval
New repo request
04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections. Motion was carried.
04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.
Other
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.
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.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
04-24: @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.
04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.
04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.
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:
04-24: registration was requested if attend to OAI workshop either in person of remotely.
04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.
04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.
04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista;
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
04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.
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
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:
04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed.
04-17: @Jakub Novy [DTAG] in progress, trying to get closed.
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.
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.
3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination
04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system.
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
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
04-24: we will check the progress next week.
04-17: @Sridhar Rao still working for delete the ASN.1 compiler.
04-10: the archive ASN.1 compiler will be deleted by @Sridhar Rao Apr 10, 2025 .
04-03: @Sridhar Rao @Martin Skorupski @David Kinsey [AT&T] Motion to approve; Seconded by @Sridhar Rao; No Objections, the motion for "deleting the archive for the ASN1 compiler that is in error" is approved; @Sridhar Rao will delete the archive with error.
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.
RSAC co-chair
04-17: no update; still looking for.
04-10: no update. still looking for a new RSAC co-chair.
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
INT - @bimo fransiscus asisi
04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.
04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.
04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)
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.
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.
SMO blueprint
04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
Internship update
8. Meeting Summary and Closure
03-27: @David Kinsey [AT&T] out on May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting May 1, 2025 @David Kinsey [AT&T]to host; it might be a holiday in Europe. Nokia will be scribe in May.
2025 04 17
Recording
Meeting Recording: Link
Agenda
Scribe: @Yasufumi Morioka (NTT Docomo)
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May:
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 | |||
Jinri Huang Co-Chair | James Li | X | ||
Jakub Nový | ||||
Sandeep Sarma | X | John Keeney | ||
Yasufumi Morioka | X | Minami Ishii | ||
Arunkumar Halebid | Abdul Wahid | X | ||
Julien Boudani | X | Oumayma Charrad | ||
Ganesh Shenbagaraman | Ankit Barve | X | ||
Andrea Buldorini | X | |||
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 Apr 10, 2025
Next Meeting Apr 24, 2025
Release Update
New business
CVE handling update
O-RAN Business - OSFG Update & F2F Meeting
O-RAN Open-Source Workshop
O-RAN SCCL enforcement status
Old Business
ASN.1 compiler
Project updates
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @Avinash Bhat Motion to Approve; Seconded by Julien Boudani; No Objections. Apr 10, 2025 Minutes approved.
Release
04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf
04-03: @Sally Cooper : PR has been approved. PR will post Apr 3, 2025
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.
Release Votes (checklist) and Approval
Other
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
CVE Handling: Common Vulnerabilities and Exposures (CVE)
04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.
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.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.
04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.
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:
04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.
04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.
04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista;
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:
04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.
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
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:
04-17: @Jakub Novy [DTAG] in progress, trying to get closed.
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.
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.
3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination
04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system.
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
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
04-17: @Sridhar Rao still working for delete the ASN.1 compiler.
04-10: the archive ASN.1 compiler will be deleted by @Sridhar Rao Apr 10, 2025 .
04-03: @Sridhar Rao @Martin Skorupski @David Kinsey [AT&T] Motion to approve; Seconded by @Sridhar Rao; No Objections, the motion for "deleting the archive for the ASN1 compiler that is in error" is approved; @Sridhar Rao will delete the archive with error.
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.
RSAC co-chair
04-17: no update; still looking for.
04-10: no update. still looking for a new RSAC co-chair.
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
INT - @bimo fransiscus asisi
04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.
04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.
04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)
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.
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.
SMO blueprint
04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
Internship update
8. Meeting Summary and Closure
03-27: @David Kinsey [AT&T] out on Apr 24, 2025 and May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting Apr 24, 2025 @David Kinsey [AT&T]to host. NTT Docomo will be scribe in April.
2025 04 10
Recording
Meeting Recording: Link
Agenda
Scribe: @Yasufumi Morioka (NTT Docomo)
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 | |||
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 | X | |||
Jackie Huang | X | 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 Apr 3, 2025
Next Meeting Apr 17, 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: : @Ankit Barve Motion to Approve; Seconded by @Sandeep Sarma (Ericsson); No Objections. Apr 3, 2025 Minutes approved.
Release
04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf
04-03: @Sally Cooper : PR has been approved. PR will post Apr 3, 2025
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.
Release Votes (checklist) and Approval
Other
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.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.
04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.
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:
04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.
04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista;
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:
04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.
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
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.
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.
3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination
04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system.
IEEE GLOBECOM 2025 O-RAN workshop
04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.
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
04-10: the archive ASN.1 compiler will be deleted by @Sridhar Rao Apr 10, 2025 .
04-03: @Sridhar Rao @Martin Skorupski @David Kinsey [AT&T] Motion to approve; Seconded by @Sridhar Rao; No Objections, the motion for "deleting the archive for the ASN1 compiler that is in error" is approved; @Sridhar Rao will delete the archive with error.
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.
04-10: no update. still looking for a new RSAC co-chair.
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
INT - @bimo fransiscus asisi
04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.
04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)
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.
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.
SMO blueprint
04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
Internship update
8. Meeting Summary and Closure
04-10: @David Kinsey [AT&T] canceled his business trip on Apr 24, 2025, so that we will have a meeting on Apr 24, 2025.
04-03: @David Kinsey [AT&T] asks Jinri, @James Li and @Martin Skorupski to check their availability during David out Apr 24, 2025
03-27: @David Kinsey [AT&T] out on Apr 24, 2025 and May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting Apr 17, 2025 @David Kinsey [AT&T]to host. NTT Docomo will be scribe in April.
2025 04 03
Recording
Meeting Recording: Link
Agenda
Scribe: @Yasufumi Morioka (NTT Docomo)
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 | |||
Jinri Huang Co-Chair | X | James Li | ||
Jakub Nový | X | |||
Sandeep Sarma | X | John Keeney | ||
Yasufumi Morioka | X | Minami Ishii | ||
Arunkumar Halebid | X | Abdul Wahid | ||
Julien Boudani | Oumayma Charrad | X | ||
Ganesh Shenbagaraman | Ankit Barve | X | ||
Andrea Buldorini | X | |||
Jackie Huang | X | Jon Zhang | ||
Ultan Kelly | X | 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 27, 2025
Next Meeting Apr 10, 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: : @Ankit Barve Motion to Approve; Seconded by @Jakub Novy [DTAG]; No Objections. Mar 27, 2025 Minutes approved.
Release
04-03: @Sally Cooper : PR has been approved. PR will post Apr 3, 2025
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.
Release Votes (checklist) and Approval
Other
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.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.
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:
04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista;
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:
04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.
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
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.
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.
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
04-03: @Sridhar Rao @Martin Skorupski @David Kinsey [AT&T] Motion to approve; Seconded by @Sridhar Rao; No Objections, the motion for "deleting the archive for the ASN1 compiler that is in error" is approved; @Sridhar Rao will delete the archive with error.
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.
04-03: no update. still looking for a new RSAC co-chair.
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
INT - @bimo fransiscus asisi
04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)
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.
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.
SMO blueprint
04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.
INF - @Jackie Huang
RIC - @abdulwahid.w
RICAPP - @Sunil Singh
SIM - @Alex Stancu
OAM - @Martin Skorupski
SMO - @Seshu Kumar Mudiganti
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
Internship update
8. Meeting Summary and Closure
04-03: @David Kinsey [AT&T] asks Jinri, @James Li and @Martin Skorupski to check their availability during David out Apr 24, 2025
03-27: @David Kinsey [AT&T] out on Apr 24, 2025 and May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting Apr 10, 2025 @David Kinsey [AT&T]to host. NTT Docomo will be scribe in April.
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 (EURECOM/OpenAirInterface) 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
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
01-23 @Sally Cooper provided 10 minute update on Marketing Plan.
Call to like LinkedIn Posts
Goal to issue several blogs this year
Goal to increase the number of followers on LinkedIn
Suggestion to do Webinar on SCCL with real examples. @Sally Cooper to follow up in April when November Train is available to the public.
Internship update
8. Meeting Summary and Closure
03-27: @David Kinsey [AT&T] out on Apr 24, 2025 and May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting Apr 3, 2025 @David Kinsey [AT&T]to host. NTT Docomo will be scribe in April.
2025 03 20
Recording
Meeting Recording: link
Agenda
Scribe: @Jakub Novy [DTAG]
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ý | X | |||
Sandeep Sarma | X | John Keeney | ||
Yasufumi Morioka | X | Minami Ishii | ||
Arunkumar Halebid | Abdul Wahid | |||
Julien Boudani | X | Oumayma Charrad | ||
Ganesh Shenbagaraman | Ankit Barve | X | ||
Andrea Buldorini | X | |||
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 13, 2025
Next Meeting Mar 27, 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: Julien: Motion to Approve; Seconded by @Jakub Novy [DTAG]; No Objections. Mar 13, 2025 Minutes approved.
Release
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-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-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-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 (EURECOM/OpenAirInterface) 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
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
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
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu
03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
01-23 @Sally Cooper provided 10 minute update on Marketing Plan.
Call to like LinkedIn Posts
Goal to issue several blogs this year
Goal to increase the number of followers on LinkedIn
Suggestion to do Webinar on SCCL with real examples. @Sally Cooper to follow up in April when November Train is available to the public.
Internship update
8. Meeting Summary and Closure
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting Mar 27, 2025 @David Kinsey [AT&T]to host. DTAG will be scribe in March. For April, it will be NTT Docomo.
2025 03 13
Recording
Meeting Recording: Link
Agenda
Scribe: @Jakub Novy [DTAG]
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG
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ý | X | |||
Sandeep Sarma | X | John Keeney | ||
Yasufumi Morioka | Minami Ishii | |||
Arunkumar Halebid | Abdul Wahid | |||
Julien Boudani | X | Oumayma Charrad | ||
Ganesh Shenbagaraman | Ankit Barve | X | ||
Andrea Buldorini | ||||
Jackie Huang | X | 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 6, 2025
Next Meeting Mar 20, 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: @Jakub Novy [DTAG]: Motion to Approve; Seconded by @Ankit Barve; No Objections. Mar 6, 2025 Minutes approved.
Release
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-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-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-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-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-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 (EURECOM/OpenAirInterface) 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
Old Business
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
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
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.
03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
01-23 @Sally Cooper provided 10 minute update on Marketing Plan.
Call to like LinkedIn Posts
Goal to issue several blogs this year
Goal to increase the number of followers on LinkedIn
Suggestion to do Webinar on SCCL with real examples. @Sally Cooper to follow up in April when November Train is available to the public.
Internship update
8. Meeting Summary and Closure
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting Mar 20, 2025 @David Kinsey [AT&T]to host. DTAG will be scribe in March.
2025 03 06
Recording
Meeting Recording: Link
Agenda
Scribe: @Jakub Novy [DTAG]
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG
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 | Tracy Van Brakle | X | ||
Jinri Huang Co-Chair | X | James Li | ||
Jakub Nový | X | |||
Sandeep Sarma | X | John Keeney | ||
Yasufumi Morioka | X | Minami Ishii | ||
Arunkumar Halebid | Abdul Wahid | X | ||
Julien Boudani | X | Oumayma Charrad | ||
Ganesh Shenbagaraman | Ankit Barve | X | ||
Andrea Buldorini | X | |||
Jackie Huang | X | 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 Feb 27, 2025
Next Meeting Mar 13, 2025
Release Update
O-RAN Business - OSFG Update & F2F Meeting
O-RAN Open-Source Workshop
Release J & K PR Statement
F2F Schedule
Old Business
Project Updates
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: Julien Boudani: Motion to Approve; Seconded by @Avinash Bhat; No Objections. Feb 27, 2025 Minutes Approved.
Release
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
03-06: CVE Handling: Common Vulnerabilities and Exposures (CVE)
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).
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.
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-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:
Open Source workshop:
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.
O-RAN SCCL enforcement:
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-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 (EURECOM/OpenAirInterface) 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
Old Business
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
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
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.
01-23 @Sally Cooper provided 10 minute update on Marketing Plan.
Call to like LinkedIn Posts
Goal to issue several blogs this year
Goal to increase the number of followers on LinkedIn
Suggestion to do Webinar on SCCL with real examples. @Sally Cooper to follow up in April when November Train is available to the public.
Internship update
8. Meeting Summary and Closure
03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks.
Next Meeting Mar 13, 2025 @David Kinsey [AT&T]to host. DTAG will be scribe in March.
2025 02 27
Recording
Meeting Recording: Recording Link
Agenda
Scribe: @James Li
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG
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ý | x | |||
John-Paul Lane | x | John Keeney | ||
Yasufumi Morioka | Minami Ishii | |||
Arunkumar Halebid | Abdul Wahid | |||
Julien Boudani | ||||
Ganesh Shenbagaraman | Ankit Barve | x | ||
Andrea Buldorini | ||||
Jackie Huang | x | Jon Zhang | ||
Ultan Kelly | x | 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 (Jan 16th)
Next Meeting Mar 6, 2025
Release Update
O-RAN Business - OSFG Update & F2F Meeting
O-RAN Open-Source Workshop
Release J & K PR Statement
F2F Schedule
Old Business
Project Updates
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @Jakub Novy [DTAG]Motion to Approve ; Seconded by @Jackie Huang : No Objections. 2/20 Minutes Approved.
Release
02-27: Katie now understands the situation and will have it closed by the end of week.
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 Zbynik 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
19-12: @Matt Watkins Gerrit software upgrade had to be rolled back and the maintenance overran by ~an hour. Will be run again during the vacation period.
19-12: K-Release timeline disucssed and release Approved. One remark : RIC APP project may be ready for the maintenance release.
12-12: @Matt Watkins Upgrade Gerrit and restart Jenkins Tuesday 10AM to 11AM (message will be send to the slack channel).
12-12: @Sridhar Rao & @David Kinsey [AT&T] K-release => some highlights need to be populated. Tagging will be done on the 19th of december (PTLs to get the OK that
hey are ready for tagging). Final realease ready before the end of the year. But voting will be on the 9th of January.
12-05: @Sridhar Rao initiated a request for security scanning, will complete it and send the report. The release probably won't happen until January 9.
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
02-27: @John-Paul Lane (Ericsson) will leave the TOC position. @Sandeep Sarma (Ericsson) will replace him.
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.
12-19:MoU between LFN and O-RAN Alliance :work in progress with remarks from OSFG expected in preparation of the press release. We have some wordings concern about OSC present in the MoU. We need to confirm it before publishing it. OSC was already using ONAP Code and recently we are also working with Nephio. We are not happy with the statement that may be understood like "OSC should part of LFN". The MoU should be high level and not going specifically focusing on topics like Security (which is already known point for OSC). @James Li will send an email to OSFG.
12-05: Memorandum of understanding between O-RAN and LFN is under preparation with OSFG
12-05: Letter of intent between AT&T and O-RAN regarding the funding of the lab. AT&T will send out the purchase orders for the tools.
12-12: Part of the budget planned for this year (VIAVI) and a second wave is next year (Keysight). O-RAN is funding, AT&T is purshacing. Adjustment of the End User License Agreement to authorize the tools .
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG updates: @Tracy Van Brakle OSFG is in preparation for the F2F, as well as getting more tactical and practical with some of the open source reference designs over the past few month
Open Source workshop:
02-27: @David Kinsey [AT&T] uploaded his deck. There were a couple sessions during the F2F to discuss about the workshop and it seems to be a separate event from F2F meeting as originally thought. Discussion with TIFG regarding testing suggests they may help on O1 tests.
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.
O-RAN SCCL enforcement:
02-27: @Jakub Novy [DTAG]: Had several sessions with WGs about the Software release process that includes SCCL -- it was generally accepted with a few practical comments. Target the June 2025 train to publish.
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
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.
Face-to-Face Meeting
02-27: demo videos uploaded to Youtube.
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 (EURECOM/OpenAirInterface) 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
Old Business
Tooling Changes
RSAC 02-13: 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
Update on Nephio
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
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
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
01-23 @Sally Cooper provided 10 minute update on Marketing Plan.
Call to like LinkedIn Posts
Goal to issue several blogs this year
Goal to increase the number of followers on LinkedIn
Suggestion to do Webinar on SCCL with real examples. @Sally Cooper to follow up in April when November Train is available to the public.
Internship updates
8. Meeting Summary and Closure
Discussed lunar new-year holidays and will affect attendance of next meetings so discussion to postpone next weeks meeting.
Next Meeting Mar 6, 2025 Jinri Huang to host. DTAG will be scribe in March.
2025 02 20
Recording
Meeting Recording: Recording Link
Agenda
Scribe: @James Li
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG
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ý | x | |||
John-Paul Lane | x | John Keeney | ||
Yasufumi Morioka | x | Minami Ishii | ||
Arunkumar Halebid | Abdul Wahid | x | ||
Julien Boudani | x | |||
Ganesh Shenbagaraman | Ankit Barve | x | ||
Andrea Buldorini | ||||
Jackie Huang | x | 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 (Jan 16th)
Next Meeting Feb 27, 2025
Release Update
O-RAN Business - OSFG Update & F2F Meeting
O-RAN Open-Source Workshop
Release J & K PR Statement
F2F Schedule
Old Business
Project Updates
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: @Julian Garrett Motion to Approve ; Seconded by @John-Paul Lane (Ericsson) : No Objections. 2/13 Minutes Approved. @David Kinsey [AT&T]Motion to Approve ; Seconded by @Jakub Novy [DTAG] : No Objections. 2/6 Minutes Approved.
Release
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 Zbynik 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
19-12: @Matt Watkins Gerrit software upgrade had to be rolled back and the maintenance overran by ~an hour. Will be run again during the vacation period.
19-12: K-Release timeline disucssed and release Approved. One remark : RIC APP project may be ready for the maintenance release.
12-12: @Matt Watkins Upgrade Gerrit and restart Jenkins Tuesday 10AM to 11AM (message will be send to the slack channel).
12-12: @Sridhar Rao & @David Kinsey [AT&T] K-release => some highlights need to be populated. Tagging will be done on the 19th of december (PTLs to get the OK that
hey are ready for tagging). Final realease ready before the end of the year. But voting will be on the 9th of January.
12-05: @Sridhar Rao initiated a request for security scanning, will complete it and send the report. The release probably won't happen until January 9.
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
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.
12-19: MoU between LFN and O-RAN Alliance : work in progress with remarks from OSFG expected in preparation of the press release. We have some wordings concern about OSC present in the MoU. We need to confirm it before publishing it. OSC was already using ONAP Code and recently we are also working with Nephio. We are not happy with the statement that may be understood like "OSC should part of LFN". The MoU should be high level and not going specifically focusing on topics like Security (which is already known point for OSC). @James Li will send an email to OSFG.
12-05: Memorandum of understanding between O-RAN and LFN is under preparation with OSFG
12-05: Letter of intent between AT&T and O-RAN regarding the funding of the lab. AT&T will send out the purchase orders for the tools.
12-12: Part of the budget planned for this year (VIAVI) and a second wave is next year (Keysight). O-RAN is funding, AT&T is purshacing. Adjustment of the End User License Agreement to authorize the tools .
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG updates: @Tracy Van Brakle OSFG is in preparation for the F2F, as well as getting more tactical and practical with some of the open source reference designs over the past few month
Open Source workshop:
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.
O-RAN SCCL enforcement:
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
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.
Face-to-Face Meeting
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 (EURECOM/OpenAirInterface) 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
Old Business
Tooling Changes
RSAC 02-13: 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
Update on Nephio
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
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
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
01-23 @Sally Cooper provided 10 minute update on Marketing Plan.
Call to like LinkedIn Posts
Goal to issue several blogs this year
Goal to increase the number of followers on LinkedIn
Suggestion to do Webinar on SCCL with real examples. @Sally Cooper to follow up in April when November Train is available to the public.
Internship updates
8. Meeting Summary and Closure
Discussed lunar new-year holidays and will affect attendance of next meetings so discussion to postpone next weeks meeting.
Next Meeting Feb 27, 2025 @David Kinsey [AT&T]to host. Scribe for February is China Mobile and DTAG will be in March.
2025 02 13
Recording
Meeting Recording: Recording Link
Agenda
Scribe: @James Li
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG
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 | x | James Li | ||
Jakub Nový | ||||
John-Paul Lane | x | John Keeney | ||
Yasufumi Morioka | x | Minami Ishii | ||
Arunkumar Halebid | Abdul Wahid | |||
Julien Boudani | ||||
Ganesh Shenbagaraman | Ankit Barve | x | ||
Andrea Buldorini | x | |||
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 (Jan 16th)
Next Meeting Feb 20, 2025
Release Update
O-RAN Business - OSFG Update & F2F Meeting
O-RAN Open-Source Workshop
Release J & K PR Statement
F2F Schedule
Old Business
Project Updates
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Decision: Motion to Approve ; Seconded by : No Objections. Minutes Approved.
Release
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 Zbynik 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
19-12: @Matt Watkins Gerrit software upgrade had to be rolled back and the maintenance overran by ~an hour. Will be run again during the vacation period.
19-12: K-Release timeline disucssed and release Approved. One remark : RIC APP project may be ready for the maintenance release.
12-12: @Matt Watkins Upgrade Gerrit and restart Jenkins Tuesday 10AM to 11AM (message will be send to the slack channel).
12-12: @Sridhar Rao & @David Kinsey [AT&T] K-release => some highlights need to be populated. Tagging will be done on the 19th of december (PTLs to get the OK that
hey are ready for tagging). Final realease ready before the end of the year. But voting will be on the 9th of January.
12-05: @Sridhar Rao initiated a request for security scanning, will complete it and send the report. The release probably won't happen until January 9.
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
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.
12-19: MoU between LFN and O-RAN Alliance : work in progress with remarks from OSFG expected in preparation of the press release. We have some wordings concern about OSC present in the MoU. We need to confirm it before publishing it. OSC was already using ONAP Code and recently we are also working with Nephio. We are not happy with the statement that may be understood like "OSC should part of LFN". The MoU should be high level and not going specifically focusing on topics like Security (which is already known point for OSC). @James Li will send an email to OSFG.
12-05: Memorandum of understanding between O-RAN and LFN is under preparation with OSFG
12-05: Letter of intent between AT&T and O-RAN regarding the funding of the lab. AT&T will send out the purchase orders for the tools.
12-12: Part of the budget planned for this year (VIAVI) and a second wave is next year (Keysight). O-RAN is funding, AT&T is purshacing. Adjustment of the End User License Agreement to authorize the tools .
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG updates: @Tracy Van Brakle OSFG is in preparation for the F2F, as well as getting more tactical and practical with some of the open source reference designs over the past few month
Open Source workshop:
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.
O-RAN SCCL enforcement:
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
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.
Face-to-Face Meeting
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
Old Business
Tooling Changes
RSAC 02-13: 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
Update on Nephio
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
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
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
01-23 @Sally Cooper provided 10 minute update on Marketing Plan.
Call to like LinkedIn Posts
Goal to issue several blogs this year
Goal to increase the number of followers on LinkedIn
Suggestion to do Webinar on SCCL with real examples. @Sally Cooper to follow up in April when November Train is available to the public.
Internship updates
8. Meeting Summary and Closure
Discussed lunar new-year holidays and will affect attendance of next meetings so discussion to postpone next weeks meeting.
Next Meeting Feb 20, 2025 @David Kinsey [AT&T]to host. Scribe for February is China Mobile and DTAG will be in March.
2025 02 06
Recording
Meeting Recording: Recording Link
Agenda
Scribe: @James Li
Previous scribe:
2025 => January: Viavi; February: China Mobile; March: DTAG
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 | Tracy Van Brakle | x | ||
Jinri Huang Co-Chair | James Li | x | ||
Jakub Nový | x | |||
John-Paul Lane | x | John Keeney | ||
Yasufumi Morioka | Minami Ishii | |||
Arunkumar Halebid | Abdul Wahid | |||
Julien Boudani | x | |||
Ganesh Shenbagaraman | Ankit Barve | x | ||
Andrea Buldorini | x | |||
Jackie Huang | Jon Zhang | |||
Ultan Kelly | x | Baruch Friedman | ||
Avinash Bhat | Peter Moonki Hong | x |
*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 (Jan 16th)
Next Meeting Feb 13, 2025
Release Update
New Items:
O-RAN Business - OSFG Update & F2F Meeting
Old Business
Project Updates
AoB Future New Agenda Items and Announcements
Review and Agree to Minutes of Previous Meeting
Comments: @Ultan.Kelly was Scribe.
Decision: Motion to Approve @Tracy Van Brakle; Seconded by John-Paul Lane: No Objections. Minutes Approved.
Release
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
19-12: @Matt Watkins Gerrit software upgrade had to be rolled back and the maintenance overran by ~an hour. Will be run again during the vacation period.
19-12: K-Release timeline disucssed and release Approved. One remark : RIC APP project may be ready for the maintenance release.
12-12: @Matt Watkins Upgrade Gerrit and restart Jenkins Tuesday 10AM to 11AM (message will be send to the slack channel).
12-12: @Sridhar Rao & @David Kinsey [AT&T] K-release => some highlights need to be populated. Tagging will be done on the 19th of december (PTLs to get the OK that
hey are ready for tagging). Final realease ready before the end of the year. But voting will be on the 9th of January.
12-05: @Sridhar Rao initiated a request for security scanning, will complete it and send the report. The release probably won't happen until January 9.
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
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.
12-19: MoU between LFN and O-RAN Alliance : work in progress with remarks from OSFG expected in preparation of the press release. We have some wordings concern about OSC present in the MoU. We need to confirm it before publishing it. OSC was already using ONAP Code and recently we are also working with Nephio. We are not happy with the statement that may be understood like "OSC should part of LFN". The MoU should be high level and not going specifically focusing on topics like Security (which is already known point for OSC). @James Li will send an email to OSFG.
12-05: Memorandum of understanding between O-RAN and LFN is under preparation with OSFG
12-05: Letter of intent between AT&T and O-RAN regarding the funding of the lab. AT&T will send out the purchase orders for the tools.
12-12: Part of the budget planned for this year (VIAVI) and a second wave is next year (Keysight). O-RAN is funding, AT&T is purshacing. Adjustment of the End User License Agreement to authorize the tools .
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG updates: @Tracy Van Brakle OSFG is in preparation for the F2F, as well as getting more tactical and practical with some of the open source reference designs over the past few month
O-RAN SCCL enforcement:
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
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.
Face-to-Face Meeting
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
Old Business
Tooling Changes
Project Updates
Update on Nephio
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
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
Non-RT RIC - @John Keeney (Ericsson EST)
AIML - @subhash
ODUHIGH - @Ankit Barve
ODULOW - @Peng Lu (Deactivated)
DOC - @Weichen Ni
Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
01-23 @Sally Cooper provided 10 minute update on Marketing Plan.
Call to like LinkedIn Posts
Goal to issue several blogs this year
Goal to increase the number of followers on LinkedIn
Suggestion to do Webinar on SCCL with real examples. @Sally Cooper to follow up in April when November Train is available to the public.
Internship updates
8. Meeting Summary and Closure
Discussed lunar new-year holidays and will affect attendance of next meetings so discussion to postpone next weeks meeting.
Next Meeting Feb 13, 2025 @David Kinsey [AT&T]to host. Scribe for February is China Mobile and DTAG will be in March.