*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
Matthew Watkins reported the status of migration from Jenkins Jobs to Github Actions (gha). Open items can be found here. JJ and gha will continue in parallel for a while.
John Keeney requested guidance of where to find a central reference about the gha and link to the repos. Clarified that gha are described at repo level. Documentation available here. Creating a wiki page and FAQ for reference can be considered.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Clarified that user stories 1-4 are planned to be completed by June 2024 and may be demonstrated at the next F2F
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
Upcoming F2F meeting
White Paper
04-18: Jinri HuangA white paper is being drafted, with several contributors working on it. Current focus is on CI/CD/CT. Status will be reported at the next call. AP:Irfan Ghauri
04-25:Irfan Ghauri the current version of the WP need a redrafting to synthetize the material provided. Target date is now mid of May. bimo fransiscus asisi arequest was sent to LF to verify the CI/CD part.
Other
03-07: The draft of OSC and POWDER joint news quotes for review. The contents should be gone through the O-RAN agenda before TSC.James Liwill dubble-check intention of the news, andTracy Van Braklewill check it with PR point of view.
03-14: Reagarding POWDER,James Limentioned about the situation of going through process. The process has been started and feedback is being collected,
03-21: Reagarding POWDER,James Limentioned that theprocess is still on reviewing of OSC.
03-28: Reagarding POWDER, it was still under reviewing. After the review, the document would be publised on the website.
04-11:James Lireported that the point was discussed in the last OSFG meeting and will report next week.
04-18:James Litext for news quotes was finalized and sent to O-RAN EC for approval. Once received back it will be sent to POWDER for publication on their site
04-25:James Li still waiting for the final feedback from EC.
03-21: Bimo NTUST presented situation of OSC ODU integration with TM500 RUSIM. The status is pending since O-DU had a issue on statice compression mode while RUSIM does not support uncompressed or dynamic compression mode. There was a discussion about the need to integrate the latest software.
03-28: Meetings was being held to move the integration testing forward.
04-04: No progress on integration issues between the OSC O-DU and RUSIM.
04-11: Bimo: work to the solve the testing of compressed mode options is still ongoing. FW gateway needed to be reconfigured and tests will be performed in the next days. Security testing is ongoing. O-CU license is expiring and a request to the vendor was put forward.
04-25: Bimo introduces professor Vipin Rathi who is working on integrating O-DU/LOW with the new release of the Intel FlexRAN API. peng Lu OCU-ODU integration already done so update with the new FlexRAN code release still possible within J release. fransiscus bimo for O-CU we are waiting for license extention by Radysis. Also integration ongoing with OAI commercial gNB and 5G Genius Core for e2e testing.
John Keeney presented a proposal for contribution on open source "Topology and Inventory SMO Service" according to O-RAN WG10 specifications, with clear separation between the API and the information models. Initial seed code available for analysis before submitting to SMO project and call for contributors. Code can be temporarily hosted in an existing SMO repo before moving to an official dedicated repo. To be managed with Seshu Kumar Mudiganti
David Kinsey lack of resources for SMO build in Bedminster. Request to support from Taiwan how to get some resources e.g. from POWDER (3 servers is the estimated amount for the task). James Li and Seshu Kumar Mudiganti will propose a way forward.
04:18: O-RAN TSC cochair requested information about the activity at project level (companies, releases). This is expected by next week meeting (Apr 25th). Projects to prioritize: NON RTIRC, NEAR RTRIC, RICAPPS, AIMLFW. Jinri HuangJinri will resend the request to PLT
04:25: postponed to the next call due to lack of time
7. Any Other Business (AoB)
OSC half-day workshop (co-located with ONE SUMMIT)
03-07: Irfan Ghauri presents tentative plan of the workshop. Potential title of workshop, programs, speakes have been discussed. David Kinsey will send out email to discuss futher.
03-14: Potential programs and speakers have been discussed. The title and subtitle of workshop was approved as "Accelerating the Open and Smart RAN, (subtitle) Open source enablers for the O-RAN Reference Design" : Motion proposed David was approved without objection.
03-21: Irfan Ghaurimentioned the state of preparation for the workshop. Some speakers will be confirmed by next week. Speakers were required to upload bios and pictures.
03-28: The state of preparation for the workshop was discussed. The mailing list of speakers for easy communication was prepaired. Sridhar Rao would send e-mail summarizing the information necessary for workshop participants later.
04-04:Sridhar Rao provides an update workshop agenda and logistics
04-11:Sridhar Rao : ChiLin cannot attend in person. Jin Li (Keysight) can replace in the role of moderator however “introduction to O-RAN” will be covered by David Kinsey (from remote). Change of the order in the agenda will be addressed by Sridhar.
04-18:Sridhar Rao We have booth and it would be good to show some demos / recordings from previous workshops to be played along the week. AP: Check with Irfan Ghauri . Sagar Arora : a demo about deployment of O-RAN components with Nephio will be given in the week
CVE
03-07: How to handle CVEs in O-RAN SC have been discussed. David Kinsey concerns to record vulnerabilities in a public database and mentioned about security requirements. Revisit in the next call.
03-14: David Kinsey mentioned about discussions of the security requirement
04-11: John Keeney suggests to proactively address the need to define a process. Proposes to request guidance as this should have been considered by LF already. Product readiness can be a condition to address vulnerability, but the categorization is per feature, not per project. Sridhar Rao proposes to give a presentation of various options considered in LF to perform the static security analysis. David Kinsey proposes to keep track of the status of the security scanning at project level (using project wiki pages).
04-18:Sridhar Rao presents some LF practices and tools for security analysis. David Kinsey This seems appropriate for project certification and badging; but for CVE we need to check "per-function" against the security requirements defined by O-RAN. Also the level of maturity of the feature is relevant to understand if security aspects were addressed in the version developed.
Intelligence perspective on gap analysis between 3GPP and O-RAN
03-28:Jinri Huangmentioned this topic and would summarize the detail of question for AIML project later.
LF Support for project activities
04-11:Sridhar Rao announced that LF would be able to provide support by means of new internships, e.g. for security testing or other activities. AP PTLs: contact Sridhar in case support is needed in project activities.
Clarified that user stories 1-4 are planned to be completed by June 2024 and may be demonstrated at the next F2F
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
Upcoming F2F meeting
White Paper
04-18: Jinri HuangA white paper is being drafted, with several contributors working on it. Current focus is on CI/CD/CT. Status will be reported at the next call. AP:Irfan Ghauri
Other
03-07: The draft of OSC and POWDER joint news quotes for review. The contents should be gone through the O-RAN agenda before TSC. James Li will dubble-check intention of the news, and Tracy Van Brakle will check it with PR point of view.
03-14: Reagarding POWDER, James Li mentioned about the situation of going through process. The process has been started and feedback is being collected,
03-21: Reagarding POWDER, James Li mentioned that the process is still on reviewing of OSC.
03-28: Reagarding POWDER, it was still under reviewing. After the review, the document would be publised on the website.
04-11: James Li reported that the point was discussed in the last OSFG meeting and will report next week.
04-18: James Li text for news quotes was finalized and sent to O-RAN EC for approval. Once received back it will be sent to POWDER for publication on their site
Standing/old business
OSC Lab
03-14: OSC Taiwan Lab Update
O DU High "J" release status has been presented by Ankit Barve. Discussions were held on about nFAP and the status of debugging issues.
03-21: Bimo NTUST presented situation of OSC ODU integration with TM500 RUSIM. The status is pending since O-DU had a issue on statice compression mode while RUSIM does not support uncompressed or dynamic compression mode. There was a discussion about the need to integrate the latest software.
03-28: Meetings was being held to move the integration testing forward.
04-04: No progress on integration issues between the OSC O-DU and RUSIM.
04-11: Bimo: work to the solve the testing of compressed mode options is still ongoing. FW gateway needed to be reconfigured and tests will be performed in the next days. Security testing is ongoing. O-CU license is expiring and a request to the vendor was put forward.
03-28: The project was the phase of starting development. Sagar Arora would present the detail in the next meeting, including how to make project tracking transparent.
04:18: O-RAN TSC cochair requested information about the activity at project level (companies, releases). This is expected by next week meeting (Apr 25th). Projects to prioritize: NON RTIRC, NEAR RTRIC, RICAPPS, AIMLFW. Jinri HuangJinri will resend the request to PLT
7. Any Other Business (AoB)
OSC half-day workshop (co-located with ONE SUMMIT)
03-07: Irfan Ghauri presents tentative plan of the workshop. Potential title of workshop, programs, speakes have been discussed. David Kinsey will send out email to discuss futher.
03-14: Potential programs and speakers have been discussed. The title and subtitle of workshop was approved as "Accelerating the Open and Smart RAN, (subtitle) Open source enablers for the O-RAN Reference Design" : Motion proposed David was approved without objection.
03-21: Irfan Ghaurimentioned the state of preparation for the workshop. Some speakers will be confirmed by next week. Speakers were required to upload bios and pictures.
03-28: The state of preparation for the workshop was discussed. The mailing list of speakers for easy communication was prepaired. Sridhar Rao would send e-mail summarizing the information necessary for workshop participants later.
04-04:Sridhar Rao provides an update workshop agenda and logistics
04-11:Sridhar Rao : ChiLin cannot attend in person. Jin Li (Keysight) can replace in the role of moderator however “introduction to O-RAN” will be covered by David Kinsey (from remote). Change of the order in the agenda will be addressed by Sridhar.
04-18:Sridhar Rao We have booth and it would be good to show some demos / recordings from previous workshops to be played along the week. AP: Check with Irfan Ghauri . Sagar Arora : a demo about deployment of O-RAN components with Nephio will be given in the week
CVE
03-07: How to handle CVEs in O-RAN SC have been discussed. David Kinsey concerns to record vulnerabilities in a public database and mentioned about security requirements. Revisit in the next call.
03-14: David Kinsey mentioned about discussions of the security requirement
04-11: John Keeney suggests to proactively address the need to define a process. Proposes to request guidance as this should have been considered by LF already. Product readiness can be a condition to address vulnerability, but the categorization is per feature, not per project. Sridhar Rao proposes to give a presentation of various options considered in LF to perform the static security analysis. David Kinsey proposes to keep track of the status of the security scanning at project level (using project wiki pages).
04-18:Sridhar Rao presents some LF practices and tools for security analysis. David Kinsey This seems appropriate for project certification and badging; but for CVE we need to check "per-function" against the security requirements defined by O-RAN. Also the level of maturity of the feature is relevant to understand if security aspects were addressed in the version developed.
Intelligence perspective on gap analysis between 3GPP and O-RAN
03-28:Jinri Huangmentioned this topic and would summarize the detail of question for AIML project later.
LF Support for project activities
04-11:Sridhar Rao announced that LF would be able to provide support by means of new internships, e.g. for security testing or other activities. AP PTLs: contact Sridhar in case support is needed in project activities.
Clarified that user stories 1-4 are planned to be completed by June 2024 and may be demonstrated at the next F2F
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
Upcoming F2F meeting
Other
03-07: The draft of OSC and POWDER joint news quotes for review. The contents should be gone through the O-RAN agenda before TSC. James Li will dubble-check intention of the news, and Tracy Van Brakle will check it with PR point of view.
03-14: Reagarding POWDER, James Li mentioned about the situation of going through process. The process has been started and feedback is being collected,
03-21: Reagarding POWDER, James Li mentioned that the process is still on reviewing of OSC.
03-28: Reagarding POWDER, it was still under reviewing. After the review, the document would be publised on the website.
04-11: James Li reported that the point was discussed in the last OSFG meeting and will report next week.
Standing/old business
OSC Lab
03-14: OSC Taiwan Lab Update
O DU High "J" release status has been presented by Ankit Barve. Discussions were held on about nFAP and the status of debugging issues.
03-21: Bimo NTUST presented situation of OSC ODU integration with TM500 RUSIM. The status is pending since O-DU had a issue on statice compression mode while RUSIM does not support uncompressed or dynamic compression mode. There was a discussion about the need to integrate the latest software.
03-28: Meetings was being held to move the integration testing forward.
04-04: No progress on integration issues between the OSC O-DU and RUSIM.
04-11: Bimo: work to the solve the testing of compressed mode options is still ongoing. FW gateway needed to be reconfigured and tests will be performed in the next days. Security testing is ongoing. O-CU license is expiring and a request to the vendor was put forward.
03-28: The project was the phase of starting development. Sagar Arora would present the detail in the next meeting, including how to make project tracking transparent.
04-11: AIMLFW PTLJoseph Thaliath announced that he is taking a new role in the company and proposes subhash kumar singh to take over as PTL. Subhash already started to contribute to the project and will continue in the new role of PTL. Motion to approve Subhash as new PTL of AIMLFW project made by David Kinsey , seconded by Avinash Bhat . The motion is approved.
7. Any Other Business (AoB)
OSC half-day workshop (co-located with ONE SUMMIT)
03-07: Irfan Ghauri presents tentative plan of the workshop. Potential title of workshop, programs, speakes have been discussed. David Kinsey will send out email to discuss futher.
03-14: Potential programs and speakers have been discussed. The title and subtitle of workshop was approved as "Accelerating the Open and Smart RAN, (subtitle) Open source enablers for the O-RAN Reference Design" : Motion proposed David was approved without objection.
03-21: Irfan Ghaurimentioned the state of preparation for the workshop. Some speakers will be confirmed by next week. Speakers were required to upload bios and pictures.
03-28: The state of preparation for the workshop was discussed. The mailing list of speakers for easy communication was prepaired. Sridhar Rao would send e-mail summarizing the information necessary for workshop participants later.
04-04:Sridhar Rao provides an update workshop agenda and logistics
04-11:Sridhar Rao : ChiLin cannot attend in person. Jin Li (Keysite) can replace in the role of moderator however “introduction to O-RAN” will be covered by David Kinsey (from remote). Change of the order in the agenda will be addressed by Sridhar.
CVE
03-07: How to handle CVEs in O-RAN SC have been discussed. David Kinsey concerns to record vulnerabilities in a public database and mentioned about security requirements. Revisit in the next call.
03-14: David Kinsey mentioned about discussions of the security requirement
04-11: John Keeney suggests to proactively address the need to define a process. Proposes to request guidance as this should have been considered by LF already. Product readiness can be a condition to address vulnerability, but the categorization is per feature, not per project. Sridhar Rao proposes to give a presentation of various options considered in LF to perform the static security analysis. David Kinsey proposes to keep track of the status of the security scanning at project level (using project wiki pages).
Intelligence perspective on gap analysis between 3GPP and O-RAN
03-28:Jinri Huangmentioned this topic and would summarize the detail of question for AIML project later.
LF Support for project activities
04-11:Sridhar Rao announced that LF would be able to provide support by means of new internships, e.g. for security testing or other activities. AP PTLs: contact Sridhar in case support is needed in project activities.
8. Meeting Summary and Closure
Next Meeting 2024/04/18.
2024 04 04
Recording
Meeting Recording:
Agenda
Call for scribe (minutes owner): Andrea Buldorini (TIM)
Clarified that user stories 1-4 are planned to be completed by June 2024 and may be demonstrated at the next F2F
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
Upcoming F2F meeting
Other
03-07: The draft of OSC and POWDER joint news quotes for review. The contents should be gone through the O-RAN agenda before TSC. James Li will dubble-check intention of the news, and Tracy Van Brakle will check it with PR point of view.
03-14: Reagarding POWDER, James Li mentioned about the situation of going through process. The process has been started and feedback is being collected,
03-21: Reagarding POWDER, James Li mentioned that the process is still on reviewing of OSC.
03-28: Reagarding POWDER, it was still under reviewing. After the review, the document would be publised on the website.
Standing/old business
OSC Lab
03-14: OSC Taiwan Lab Update
O DU High "J" release status has been presented by Ankit Barve. Discussions were held on about nFAP and the status of debugging issues.
03-21: Bimo NTUST presented situation of OSC ODU integration with TM500 RUSIM. The status is pending since O-DU had a issue on statice compression mode while RUSIM does not support uncompressed or dynamic compression mode. There was a discussion about the need to integrate the latest software.
03-28: Meetings was being held to move the integration testing forward.
04-04: No progress on integration issues between the OSC O-DU and RUSIM.
03-28: The project was the phase of starting development. Sagar Arora would present the detail in the next meeting, including how to make project tracking transparent.
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
Near RT RIC PTL
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: No other candidate besides Abdulwahid. Motion proposed by Jinri Huang and seconded by Julien Boudani , motion was approved without objection.
7. Any Other Business (AoB)
OSC half-day workshop (co-located with ONE SUMMIT)
03-07: Irfan Ghauri presents tentative plan of the workshop. Potential title of workshop, programs, speakes have been discussed. David Kinsey will send out email to discuss futher.
03-14: Potential programs and speakers have been discussed. The title and subtitle of workshop was approved as "Accelerating the Open and Smart RAN, (subtitle) Open source enablers for the O-RAN Reference Design" : Motion proposed David was approved without objection.
03-21: Irfan Ghaurimentioned the state of preparation for the workshop. Some speakers will be confirmed by next week. Speakers were required to upload bios and pictures.
03-28: The state of preparation for the workshop was discussed. The mailing list of speakers for easy communication was prepaired. Sridhar Rao would send e-mail summarizing the information necessary for workshop participants later.
04-04:Sridhar Rao provides an update workshop agenda and logistics
CVE
03-07: How to handle CVEs in O-RAN SC have been discussed. David Kinsey concerns to record volunerabilities in a pulic database and mentioned about security requirements. Revisit in the next call.
03-14: David Kinsey mentioned about discussions of the security requirement
Intelligence perspective on gap analysis between 3GPP and O-RAN
03-28:Jinri Huangmentioned this topic and would summarize the detail of question for AIML project later.
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.
Review and Agree to Minutes of Previous Meeting
Decision:Minutes approval for last TOC meeting 2024-03-21 : Motion proposed Jinri by and seconded Julien by motion was approved on the premise that the some correction mentioned in the meeting would be made.
Review of Today's Agenda
ONE summit
POWDER
Project report
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
01-04: No New Items this week
01-11: Update from Nephio on integration activity: Sagar Arora
03-28: How to make the SMO project tracking transparent: Sagar Arora
03-21: Sridhar Rao peresented the potential changes of the release regarding the gha-migration topic, which had revied super comitters (LINK). These changes are aproved: Motion proposed David was approved without objection.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
02-01: WG10 working on process definition for ORAN. 3 activates planned for F2F - developing the process together with OSFG (outline, what are the steps, responsibilities; not necessarily the document itself), informing WGs about the changes, presenting to TSC.
Collaboration with OAI (lab interconnection) and Nephio
02-01: Sagar Arora: in the SMO call this week, presentation about NF orchestration using SMO shown. AP Seshu Kumar Mudiganti to upload the ppt to the TOC documents.
02-15: SMO integration in Nephio: approved this week, there are already volunteers willing to working on that. It will be implemented in OSC and then ported to Nephio. J release a Nephio rel 3 are at the similar time, which is good.
02-15: xApp deployment through Nephio usecase presented by Neman Gupta from Samsung. Seshu Kumar Mudiganti to upload the doc to the TOC documents. Messaging from WG6 should be considered.
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
Upcoming F2F meeting
02-15: OSFG agenda presented, for more info refer to O-RAN wiki.
03-07: The draft of OSC and POWDER joint news quotes for review. The contents should be gone through the O-RAN agenda before TSC. James Li will dubble-check intention of the news, and Tracy Van Brakle will check it with PR point of view.
03-14: Reagarding POWDER, James Li mentioned about the situation of going through process. The process has been started and feedback is being collected,
03-21: Reagarding POWDER, James Li mentioned that the process is still on reviewing of OSC.
03-28: Reagarding POWDER, it was still under reviewing. After the review, the document would be publised on the website.
,Standing/old business
OSC Lab
02-01: East cost lab still down, Bedminster may stay down and we may move to Rutgers in New Jersey. David Kinsey working on that, alignment calls planned.
03-14: OSC Taiwan Lab Update
O DU High "J" release status has been presented by Ankit Barve. Discussions were held on about nFAP and the status of debugging issues.
03-21: Bimo NTUST presented situation of OSC ODU integration with TM500 RUSIM. The status is pending since O-DU had a issue on statice compression mode while RUSIM does not support uncompressed or dynamic compression mode. There was a discussion about the need to integrate the latest software.
03-28: Meetings was being held to move the integration testing forward.
03-28: The project was the phase of starting development. Sagar Arora would present the detail in the next meeting, including how to make project tracking transparent.
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
Near RT RIC PTL
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: No other candidate besides Abdulwahid. Motion proposed by Jinri Huang and seconded by Julien Boudani , motion was approved without objection.
(Old link is still shown Group Email Notification)
01-11: Modify Calendar Permissions TOC/RSAC bridges; Hostcode distribution
02-01: info.yaml updated with Near-RIC committer changes over last week. No action needed.
02-15: Thank you, Thoralf Czichy , for all your contributions as PTL!
02-15: Deutsche Telekom TOC alternate representative removed.
One Summit
02-15: One Summit: Half-day workshop "OpenGovCon: 6G Innovation Day" focusing on future RAN planned on Apr 29, 30 and May 1st at San Jose, Sridhar Rao will share more info and promote O-RAN OSC at booth there. Support from other TOC members requested.
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: We need to ensure speakers. David Kinsey will reach to Irfan Ghauri to discuss if he can support this.
02-29: Sridhar Rao - the latest date to have the speakers list is 20.3. to have time for marketing.
02-29: we need to be sure that we can collect speakers and topics for 1/2 day agenda.
OSC half-day workshop (co-located with ONE SUMMIT)
03-07: Irfan Ghauri presents tentative plan of the workshop. Potential title of workshop, programs, speakes have been discussed. David Kinsey will send out email to discuss futher.
03-14: Potential programs and speakers have been discussed. The title and subtitle of workshop was approved as "Accelerating the Open and Smart RAN, (subtitle) Open source enablers for the O-RAN Reference Design" : Motion proposed David was approved without objection.
03-21: Irfan Ghaurimentioned the state of preparation for the workshop. Some speakers will be confirmed by next week. Speakers were required to upload bios and pictures.
03-28: The state of preparation for the workshop was discussed. The mailing list of speakers for easy communication was prepaired. Sridhar Rao would send e-mail summarizing the information necessary for workshop participants later.
Super committer permission
02-29: announcement from release engineering about need to implement the super committer permissions.
02-29: needed because of the shift from Jenkins to Gitlab Actions. Permission needed for testing in production.
02-29: John Keeney supports the idea. No strong pushback from any other PTLs.
02-29: Jessica Gonzalez will prepare a proposal for next TSC, we need 2 people release engineering team + 2 from the community. John Keeney and Martin Skorupski volunteer.
03-07: Jessica and Matthew from LF, and John and Martin from OSC have been approved as super commiters (Link) : Motion proposed David by and seconded Julien by motion was approved without objection.
CVE
03-07: How to handle CVEs in O-RAN SC have been discussed. David Kinsey concerns to record volunerabilities in a pulic database and mentioned about security requirements. Revisit in the next call.
03-14: David Kinsey mentioned about discussions of the security requirement
Contacts
03-14: NOKIA alternate contact changed:Thoralf Czichy →Abdulwahid
Intellegence perspective on gap analysis between 3GPP and O-RAN
03-28:Jinri Huangmentioned this topic and would summarize the detail of question for AIML project later.
03-21: Sridhar Rao peresented the potential changes of the release regarding the gha-migration topic, which had revied super comitters (LINK). These changes are aproved: Motion proposed David was approved without objection.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
02-01: WG10 working on process definition for ORAN. 3 activates planned for F2F - developing the process together with OSFG (outline, what are the steps, responsibilities; not necessarily the document itself), informing WGs about the changes, presenting to TSC.
Collaboration with OAI (lab interconnection) and Nephio
02-01: Sagar Arora: in the SMO call this week, presentation about NF orchestration using SMO shown. AP Seshu Kumar Mudiganti to upload the ppt to the TOC documents.
02-15: SMO integration in Nephio: approved this week, there are already volunteers willing to working on that. It will be implemented in OSC and then ported to Nephio. J release a Nephio rel 3 are at the similar time, which is good.
02-15: xApp deployment through Nephio usecase presented by Neman Gupta from Samsung. Seshu Kumar Mudiganti to upload the doc to the TOC documents. Messaging from WG6 should be considered.
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
Upcoming F2F meeting
02-15: OSFG agenda presented, for more info refer to O-RAN wiki.
03-07: The draft of OSC and POWDER joint news quotes for review. The contents should be gone through the O-RAN agenda before TSC. James Li will dubble-check intention of the news, and Tracy Van Brakle will check it with PR point of view.
03-14: Reagarding POWDER, James Li mentioned about the situation of going through process. The process has been started and feedback is being collected,
03-21: Reagarding POWDER, James Li mentioned that the process is still on reviewing of OSC.
,Standing/old business
OSC Lab
02-01: East cost lab still down, Bedminster may stay down and we may move to Rutgers in New Jersey. David Kinsey working on that, alignment calls planned.
03-14: OSC Taiwan Lab Update
O DU High "J" release status has been presented by Ankit Barve. Discussions were held on about nFAP and the status of debugging issues.
03-21: Bimo NTUST presented situation of OSC ODU integration with TM500 RUSIM. The status is pending since O-DU had a issue on statice compression mode while RUSIM does not support uncompressed or dynamic compression mode. There was a discussion about the need to integrate the latest software.
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
Near RT RIC PTL
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: No other candidate besides Abdulwahid. Motion proposed by Jinri Huang and seconded by Julien Boudani , motion was approved without objection.
(Old link is still shown Group Email Notification)
01-11: Modify Calendar Permissions TOC/RSAC bridges; Hostcode distribution
02-01: info.yaml updated with Near-RIC committer changes over last week. No action needed.
02-15: Thank you, Thoralf Czichy , for all your contributions as PTL!
02-15: Deutsche Telekom TOC alternate representative removed.
One Summit
02-15: One Summit: Half-day workshop "OpenGovCon: 6G Innovation Day" focusing on future RAN planned on Apr 29, 30 and May 1st at San Jose, Sridhar Rao will share more info and promote O-RAN OSC at booth there. Support from other TOC members requested.
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: We need to ensure speakers. David Kinsey will reach to Irfan Ghauri to discuss if he can support this.
02-29: Sridhar Rao - the latest date to have the speakers list is 20.3. to have time for marketing.
02-29: we need to be sure that we can collect speakers and topics for 1/2 day agenda.
OSC half-day workshop (co-located with ONE SUMMIT)
03-07: Irfan Ghauri presents tentative plan of the workshop. Potential title of workshop, programs, speakes have been discussed. David Kinsey will send out email to discuss futher.
03-14: Potential programs and speakers have been discussed. The title and subtitle of workshop was approved as "Accelerating the Open and Smart RAN, (subtitle) Open source enablers for the O-RAN Reference Design" : Motion proposed David was approved without objection.
03-21: Irfan Ghaurimentioned the state of preparation for the workshop. Some speakers will be confirmed by next week. Speakers were required to upload bios and pictures.
Super committer permission
02-29: announcement from release engineering about need to implement the super committer permissions.
02-29: needed because of the shift from Jenkins to Gitlab Actions. Permission needed for testing in production.
02-29: John Keeney supports the idea. No strong pushback from any other PTLs.
02-29: Jessica Gonzalez will prepare a proposal for next TSC, we need 2 people release engineering team + 2 from the community. John Keeney and Martin Skorupski volunteer.
03-07: Jessica and Matthew from LF, and John and Martin from OSC have been approved as super commiters (Link) : Motion proposed David by and seconded Julien by motion was approved without objection.
CVE
03-07: How to handle CVEs in O-RAN SC have been discussed. David Kinsey concerns to record volunerabilities in a pulic database and mentioned about security requirements. Revisit in the next call.
03-14: David Kinsey mentioned about discussions of the security requirement
Contacts
03-14: NOKIA alternate contact changed:Thoralf Czichy →Abdulwahid
02-01: WG10 working on process definition for ORAN. 3 activates planned for F2F - developing the process together with OSFG (outline, what are the steps, responsibilities; not necessarily the document itself), informing WGs about the changes, presenting to TSC.
Collaboration with OAI (lab interconnection) and Nephio
02-01: Sagar Arora: in the SMO call this week, presentation about NF orchestration using SMO shown. AP Seshu Kumar Mudiganti to upload the ppt to the TOC documents.
02-15: SMO integration in Nephio: approved this week, there are already volunteers willing to working on that. It will be implemented in OSC and then ported to Nephio. J release a Nephio rel 3 are at the similar time, which is good.
02-15: xApp deployment through Nephio usecase presented by Neman Gupta from Samsung. Seshu Kumar Mudiganti to upload the doc to the TOC documents. Messaging from WG6 should be considered.
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
Upcoming F2F meeting
02-15: OSFG agenda presented, for more info refer to O-RAN wiki.
03-07: The draft of OSC and POWDER joint news quotes for review. The contents should be gone through the O-RAN agenda before TSC. James Li will dubble-check intention of the news, and Tracy Van Brakle will check it with PR point of view.
03-14: Reagarding POWDER, James Li mentioned about the situation of going through process. The process has been started and feedback is being collected,
,Standing/old business
OSC Lab
02-01: East cost lab still down, Bedminster may stay down and we may move to Rutgers in New Jersey. David Kinsey working on that, alignment calls planned.
03-14: OSC Taiwan Lab Update
O DU High "J" release status has been presented by Ankit Barve. Discussions were held on about nFAP and the status of debugging issues.
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
Near RT RIC PTL
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: No other candidate besides Abdulwahid. Motion proposed by Jinri Huang and seconded by Julien Boudani , motion was approved without objection.
(Old link is still shown Group Email Notification)
01-11: Modify Calendar Permissions TOC/RSAC bridges; Hostcode distribution
02-01: info.yaml updated with Near-RIC committer changes over last week. No action needed.
02-15: Thank you, Thoralf Czichy , for all your contributions as PTL!
02-15: Deutsche Telekom TOC alternate representative removed.
One Summit
02-15: One Summit: Half-day workshop "OpenGovCon: 6G Innovation Day" focusing on future RAN planned on Apr 29, 30 and May 1st at San Jose, Sridhar Rao will share more info and promote O-RAN OSC at booth there. Support from other TOC members requested.
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: We need to ensure speakers. David Kinsey will reach to Irfan Ghauri to discuss if he can support this.
02-29: Sridhar Rao - the latest date to have the speakers list is 20.3. to have time for marketing.
02-29: we need to be sure that we can collect speakers and topics for 1/2 day agenda.
OSC half-day workshop (co-located with ONE SUMMIT)
03-07: Irfan Ghauri presents tentative plan of the workshop. Potential title of workshop, programs, speakes have been discussed. David Kinsey will send out email to discuss futher.
03-14: Potential programs and speakers have been discussed. The title and subtitle of workshop was approved as "Accelerating the Open and Smart RAN, (subtitle) Open source enablers for the O-RAN Reference Design" : Motion proposed David was approved without objection.
Super committer permission
02-29: announcement from release engineering about need to implement the super committer permissions.
02-29: needed because of the shift from Jenkins to Gitlab Actions. Permission needed for testing in production.
02-29: John Keeney supports the idea. No strong pushback from any other PTLs.
02-29: Jessica Gonzalez will prepare a proposal for next TSC, we need 2 people release engineering team + 2 from the community. John Keeney and Martin Skorupski volunteer.
03-07: Jessica and Matthew from LF, and John and Martin from OSC have been approved as super commiters (Link) : Motion proposed David by and seconded Julien by motion was approved without objection.
CVE
03-07: How to handle CVEs in O-RAN SC have been discussed. David Kinsey concerns to record volunerabilities in a pulic database and mentioned about security requirements. Revisit in the next call.
03-14: David Kinsey mentioned about discussions of the security requirement
Contacts
03-14: NOKIA alternate contact changed:Thoralf Czichy →Abdulwahid
8. Meeting Summary and Closure
03-14: NOKIA alternate contact changed:Thoralf Czichy → Abdulwahid
03-14: The title of OSC half-day workshop (co-located with ONE SUMMIT) was approved.
03-07: The table "Features Implemented Mapping to O-RAN Spec by Project" has implemented in the Release Page. The table will be updated and reviewed. This AP is closed.
02-01: Maintenance Release set for next week TOC
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
02-01: WG10 working on process definition for ORAN. 3 activates planned for F2F - developing the process together with OSFG (outline, what are the steps, responsibilities; not necessarily the document itself), informing WGs about the changes, presenting to TSC.
Collaboration with OAI (lab interconnection) and Nephio
02-01: Sagar Arora: in the SMO call this week, presentation about NF orchestration using SMO shown. AP Seshu Kumar Mudiganti to upload the ppt to the TOC documents.
02-15: SMO integration in Nephio: approved this week, there are already volunteers willing to working on that. It will be implemented in OSC and then ported to Nephio. J release a Nephio rel 3 are at the similar time, which is good.
02-15: xApp deployment through Nephio usecase presented by Neman Gupta from Samsung. Seshu Kumar Mudiganti to upload the doc to the TOC documents. Messaging from WG6 should be considered.
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
Upcoming F2F meeting
02-15: OSFG agenda presented, for more info refer to O-RAN wiki.
03-07: The draft of OSC and POWDER joint news quotes for review. The contents should be gone through the O-RAN agenda before TSC. James Li will dubble-check intention of the news, and Tracy Van Brakle will check it with PR point of view.
Standing/old business
OSC Lab
02-01: East cost lab still down, Bedminster may stay down and we may move to Rutgers in New Jersey. David Kinsey working on that, alignment calls planned.
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
Near RT RIC PTL
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: No other candidate besides Abdulwahid. Motion proposed by Jinri Huang and seconded by Julien Boudani , motion was approved without objection.
(Old link is still shown Group Email Notification)
01-11: Modify Calendar Permissions TOC/RSAC bridges; Hostcode distribution
02-01: info.yaml updated with Near-RIC committer changes over last week. No action needed.
02-15: Thank you, Thoralf Czichy , for all your contributions as PTL!
02-15: Deutsche Telekom TOC alternate representative removed.
One Summit
02-15: One Summit: Half-day workshop "OpenGovCon: 6G Innovation Day" focusing on future RAN planned on Apr 29, 30 and May 1st at San Jose, Sridhar Rao will share more info and promote O-RAN OSC at booth there. Support from other TOC members requested.
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: We need to ensure speakers. David Kinsey will reach to Irfan Ghauri to discuss if he can support this.
02-29: Sridhar Rao - the latest date to have the speakers list is 20.3. to have time for marketing.
02-29: we need to be sure that we can collect speakers and topics for 1/2 day agenda.
Super committer permission
02-29: announcement from release engineering about need to implement the super committer permissions.
02-29: needed because of the shift from Jenkins to Gitlab Actions. Permission needed for testing in production.
02-29: John Keeney supports the idea. No strong pushback from any other PTLs.
02-29: Jessica Gonzalez will prepare a proposal for next TSC, we need 2 people release engineering team + 2 from the community. John Keeney and Martin Skorupski volunteer.
03-07: Jessica and Matthew from LF, and John and Martin from OSC have been approved as super commiters (Link) : Motion proposed David by and seconded Julien by motion was approved without objection.
OSC half-day workshop (co-located with ONE SUMMIT)
03-07: Irfan Ghauri presents tentative plan of the workshop. Potential title of workshop, programs, speakes have been discussed. David Kinsey will send out email to discuss futher.
CVE
03-07: How to handle CVEs in O-RAN SC have been discussed. David Kinsey concerns to record volunerabilities in a pulic database and mentioned about security requirements. Revisit in the next call.
01-04:Sridhar Raohave updated the release checklist. The doc projects is now tagged.The websites are updated too, also the the O-RAN Wiki page, and the O-RAN org page.
02-01: Maintenance Release set for next week TOC
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
11-02: Jakub: currently handled in WG10 tooling team; 2 main topics: SCCL itself, should be included in the code artifact, 2nd is the repository to make the file public; in progress, some braining storming, nothing for OSC to use directly; WG10 to generate the requirements; take to other WG, OFFICE, or OCOP, working on the design part of the thing; more difficult than expected;
11-09:Jakub Novymentioned that SCCL was discussed at this week's OSFG meeting, Suggest to follow up at next week TOC. More decisions needed at O-RAN level.
11-16:Jakub NovyThere is a meeting with O-RAN legal next week to review any potential issues.
11-30: David Kinsey A meeting took place with tooling within WG10. ACOP also needs to be consulted over the process. Jakub Novy to provide update on meeting with O-RAN legal.
12-07:Jakub NovyNot much to report. Got some feedback from O-RAN legal on brainstorming phase of WG10; Also checking with ETSI, Doug is helping.David Kinseycurrently pushing SCCL with WG3, WG10 and WG4.John Keeneyis of interest of publishing R1 related files with SCCL from WG2.David KinseyR1 related file may end up be an Open API.
A target of SCCL implementation may be possible by end of April
A summary is suitable to be presented to the TOC
02-01: WG10 working on process definition for ORAN. 3 activates planned for F2F - developing the process together with OSFG (outline, what are the steps, responsibilities; not necessarily the document itself), informing WGs about the changes, presenting to TSC.
Collaboration with OAI (lab interconnection) and Nephio
01-11: Nephio O-RAN Integration Status:Sagar Arora (Presentation can be found here TOC Documents)
02-01: Sagar Arora: in the SMO call this week, presentation about NF orchestration using SMO shown. AP Seshu Kumar Mudiganti to upload the ppt to the TOC documents.
02-15: SMO integration in Nephio: approved this week, there are already volunteers willing to working on that. It will be implemented in OSC and then ported to Nephio. J release a Nephio rel 3 are at the similar time, which is good.
02-15: xApp deployment through Nephio usecase presented by Neman Gupta from Samsung. Seshu Kumar Mudiganti to upload the doc to the TOC documents. Messaging from WG6 should be considered.
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
O DU High and O DU Low reworking together again and the next step is to connect O DU low back up to the TM500
Licensing issues (TM500) to be resolved by VIAVI
01-25: Progress : to get a Sandbox in Windriver
To move from Bedminster to there : our fronthaul gateway and our Grand Master Clock
02-01: East cost lab still down, Bedminster may stay down and we may move to Rutgers in New Jersey. David Kinsey working on that, alignment calls planned.
12-07:Sridhar RaoFrom the I release checklist page, only 5 projectsNONRTRIC, RICPLT, ODUHIGH*, INF, AIMLFW completed the committed features. Need all PTLs to work and complete by next Thursday for release vote.For the "Release documentation for Blog/Article on Release" item will have a dedicated marketing person to update the wiki and generate a PR for I release.Ankit Barvehow about "Features Implemented Mapping to O-RAN Spec by Project" table for I release?David KinseyIt might be kept at the project level for each PTL to fill in the details of the O-RAN specs impacting features.Ankit BarvePropose to add as a last section to the project.
01-11: RSAC "J" Release Planning Status
01-18: features for J release
Looking at how to connect the infrastructure that we have for the O Cloud to the Fronthall gateway. So, we could deploy O-DU into the cloud and have it able to connect to the TM500 through the Fronthall gateway.
Looking at trying to getan O-DU high / O-DU low instance that is continuously up. Therefore, we would move to continuous integration and test model. So, that new releases of the software would be tested by updating the existing version.
01-25: RSAC issue with the web page
Specify the properprocedure to safeguard the "Viavi" data set (possible solutions : Server in a lab or in a repository)!
Action Item : Ultan Kelly to check with peers and come back with recommendations to the RSAC
02-01: PLTs to fill the project goals/features for J Release which could be presented during F2F.
02-08: Rittwik Jana highlights for J release (except O-DU low) are finalized
Project reports (by features) (Note: From Aug. 3, it is decided that Project reports in groups will be strike out, and it will be done by features)
01-25: the list of project reports needs to be updated (with the start of our sprint in February)
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
Near RT RIC PTL
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: No other candidate besides Abdulwahid. Motion proposed by Jinri Huang and seconded by Julien Boudani , motion was approved without objection.
(Old link is still shown Group Email Notification)
01-11: Modify Calendar Permissions TOC/RSAC bridges; Hostcode distribution
02-01: info.yaml updated with Near-RIC committer changes over last week. No action needed.
02-15: Thank you, Thoralf Czichy , for all your contributions as PTL!
02-15: Deutsche Telekom TOC alternate representative removed.
One Summit
02-15: One Summit: Half-day workshop "OpenGovCon: 6G Innovation Day" focusing on future RAN planned on Apr 29, 30 and May 1st at San Jose, Sridhar Rao will share more info and promote O-RAN OSC at booth there. Support from other TOC members requested.
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-29: We need to ensure speakers. David Kinsey will reach to Irfan Ghauri to discuss if he can support this.
02-29: Sridhar Rao - the latest date to have the speakers list is 20.3. to have time for marketing.
02-29: we need to be sure that we can collect speakers and topics for 1/2 day agenda.
Super committer permission
02-29: announcement from release engineering about need to implement the super committer permissions.
02-29: needed because of the shift from Jenkins to Gitlab Actions. Permission needed for testing in production.
02-29: John Keeney supports the idea. No strong pushback from any other PTLs.
02-29: Jessica Gonzalez will prepare a proposal for next TSC, we need 2 people release engineering team + 2 from the community. John Keeney and Martin Skorupski volunteer.
8. Meeting Summary and Closure
01-11: Nephio O-RAN Integration Status
01-11: Candidates for ODULOW PTL
Nomination of Peng LU as a PTL (Motion proposed by David and seconded by Jinri. Motion was approved without objection)
01-11: OSC Taiwan Lab status (OSC O-DU Integration, CI/CD Testing and Integration, Energy Saving),
01-18: Athenes F2F meeting Agenda
01-18: Features for release J
01-25: Topics for theF2F meeting (OSFG session)
01-25: OSC Taiwan Lab update
Next Meeting 2024/03/07.
2024 02 22 - Meeting skipped
Due to the concurrent O-RAN F2F meeting, the meeting was cancelled. Quorum was not checked and thus not reached.
01-04:Sridhar Raohave updated the release checklist. The doc projects is now tagged.The websites are updated too, also the the O-RAN Wiki page, and the O-RAN org page.
02-01: Maintenance Release set for next week TOC
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
11-02: Jakub: currently handled in WG10 tooling team; 2 main topics: SCCL itself, should be included in the code artifact, 2nd is the repository to make the file public; in progress, some braining storming, nothing for OSC to use directly; WG10 to generate the requirements; take to other WG, OFFICE, or OCOP, working on the design part of the thing; more difficult than expected;
11-09:Jakub Novymentioned that SCCL was discussed at this week's OSFG meeting, Suggest to follow up at next week TOC. More decisions needed at O-RAN level.
11-16:Jakub NovyThere is a meeting with O-RAN legal next week to review any potential issues.
11-30: David Kinsey A meeting took place with tooling within WG10. ACOP also needs to be consulted over the process. Jakub Novy to provide update on meeting with O-RAN legal.
12-07:Jakub NovyNot much to report. Got some feedback from O-RAN legal on brainstorming phase of WG10; Also checking with ETSI, Doug is helping.David Kinseycurrently pushing SCCL with WG3, WG10 and WG4.John Keeneyis of interest of publishing R1 related files with SCCL from WG2.David KinseyR1 related file may end up be an Open API.
A target of SCCL implementation may be possible by end of April
A summary is suitable to be presented to the TOC
02-01: WG10 working on process definition for ORAN. 3 activates planned for F2F - developing the process together with OSFG (outline, what are the steps, responsibilities; not necessarily the document itself), informing WGs about the changes, presenting to TSC.
Collaboration with OAI (lab interconnection) and Nephio
01-11: Nephio O-RAN Integration Status:Sagar Arora (Presentation can be found here TOC Documents)
02-01: Sagar Arora: in the SMO call this week, presentation about NF orchestration using SMO shown. AP Seshu Kumar Mudiganti to upload the ppt to the TOC documents.
02-15: SMO integration in Nephio: approved this week, there are already volunteers willing to working on that. It will be implemented in OSC and then ported to Nephio. J release a Nephio rel 3 are at the similar time, which is good.
02-15: xApp deployment through Nephio usecase presented by Neman Gupta from Samsung. Seshu Kumar Mudiganti to upload the doc to the TOC documents. Messaging from WG6 should be considered.
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
O DU High and O DU Low reworking together again and the next step is to connect O DU low back up to the TM500
Licensing issues (TM500) to be resolved by VIAVI
01-25: Progress : to get a Sandbox in Windriver
To move from Bedminster to there : our fronthaul gateway and our Grand Master Clock
02-01: East cost lab still down, Bedminster may stay down and we may move to Rutgers in New Jersey. David Kinsey working on that, alignment calls planned.
12-07:Sridhar RaoFrom the I release checklist page, only 5 projectsNONRTRIC, RICPLT, ODUHIGH*, INF, AIMLFW completed the committed features. Need all PTLs to work and complete by next Thursday for release vote.For the "Release documentation for Blog/Article on Release" item will have a dedicated marketing person to update the wiki and generate a PR for I release.Ankit Barvehow about "Features Implemented Mapping to O-RAN Spec by Project" table for I release?David KinseyIt might be kept at the project level for each PTL to fill in the details of the O-RAN specs impacting features.Ankit BarvePropose to add as a last section to the project.
01-11: RSAC "J" Release Planning Status
01-18: features for J release
Looking at how to connect the infrastructure that we have for the O Cloud to the Fronthall gateway. So, we could deploy O-DU into the cloud and have it able to connect to the TM500 through the Fronthall gateway.
Looking at trying to getan O-DU high / O-DU low instance that is continuously up. Therefore, we would move to continuous integration and test model. So, that new releases of the software would be tested by updating the existing version.
01-25: RSAC issue with the web page
Specify the properprocedure to safeguard the "Viavi" data set (possible solutions : Server in a lab or in a repository)!
Action Item : Ultan Kelly to check with peers and come back with recommendations to the RSAC
02-01: PLTs to fill the project goals/features for J Release which could be presented during F2F.
02-08: Rittwik Jana highlights for J release (except O-DU low) are finalized
Project reports (by features) (Note: From Aug. 3, it is decided that Project reports in groups will be strike out, and it will be done by features)
01-25: the list of project reports needs to be updated (with the start of our sprint in February)
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
(Old link is still shown Group Email Notification)
01-11: Modify Calendar Permissions TOC/RSAC bridges; Hostcode distribution
02-01: info.yaml updated with Near-RIC committer changes over last week. No action needed.
02-15: Abdulwahid (Wahid) introduced himself as a candidate for new RT-RIC PTL role. David Kinsey asked Wahid to stand in the role of PTL during the official process. Vote day will be 29.2.
02-15: One Summit: Half-day workshop "OpenGovCon: 6G Innovation Day" focusing on future RAN planned on Apr 29, 30 and May 1st at San Jose, Sridhar Rao will share more info and promote O-RAN OSC at booth there. Support from other TOC members requested.
02-15: Thank you, Thoralf Czichy , for all your contributions as PTL!
02-15: Deutsche Telekom TOC alternate representative removed.
8. Meeting Summary and Closure
01-11: Nephio O-RAN Integration Status
01-11: Candidates for ODULOW PTL
Nomination of Peng LU as a PTL (Motion proposed by David and seconded by Jinri. Motion was approved without objection)
01-11: OSC Taiwan Lab status (OSC O-DU Integration, CI/CD Testing and Integration, Energy Saving),
01-04:Sridhar Raohave updated the release checklist. The doc projects is now tagged.The websites are updated too, also the the O-RAN Wiki page, and the O-RAN org page.
02-01: Maintenance Release set for next week TOC
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
11-02: Jakub: currently handled in WG10 tooling team; 2 main topics: SCCL itself, should be included in the code artifact, 2nd is the repository to make the file public; in progress, some braining storming, nothing for OSC to use directly; WG10 to generate the requirements; take to other WG, OFFICE, or OCOP, working on the design part of the thing; more difficult than expected;
11-09:Jakub Novymentioned that SCCL was discussed at this week's OSFG meeting, Suggest to follow up at next week TOC. More decisions needed at O-RAN level.
11-16:Jakub NovyThere is a meeting with O-RAN legal next week to review any potential issues.
11-30: David Kinsey A meeting took place with tooling within WG10. ACOP also needs to be consulted over the process. Jakub Novy to provide update on meeting with O-RAN legal.
12-07:Jakub NovyNot much to report. Got some feedback from O-RAN legal on brainstorming phase of WG10; Also checking with ETSI, Doug is helping.David Kinseycurrently pushing SCCL with WG3, WG10 and WG4.John Keeneyis of interest of publishing R1 related files with SCCL from WG2.David KinseyR1 related file may end up be an Open API.
A target of SCCL implementation may be possible by end of April
A summary is suitable to be presented to the TOC
02-01: WG10 working on process definition for ORAN. 3 activates planned for F2F - developing the process together with OSFG (outline, what are the steps, responsibilities; not necessarily the document itself), informing WGs about the changes, presenting to TSC.
O DU High and O DU Low reworking together again and the next step is to connect O DU low back up to the TM500
Licensing issues (TM500) to be resolved by VIAVI
01-25: Progress : to get a Sandbox in Windriver
To move from Bedminster to there : our fronthaul gateway and our Grand Master Clock
02-01: East cost lab still down, Bedminster may stay down and we may move to Rutgers in New Jersey. David Kinsey working on that, alignment calls planned.
12-07:Sridhar RaoFrom the I release checklist page, only 5 projectsNONRTRIC, RICPLT, ODUHIGH*, INF, AIMLFW completed the committed features. Need all PTLs to work and complete by next Thursday for release vote.For the "Release documentation for Blog/Article on Release" item will have a dedicated marketing person to update the wiki and generate a PR for I release.Ankit Barvehow about "Features Implemented Mapping to O-RAN Spec by Project" table for I release?David KinseyIt might be kept at the project level for each PTL to fill in the details of the O-RAN specs impacting features.Ankit BarvePropose to add as a last section to the project.
01-11: RSAC "J" Release Planning Status
01-18: features for J release
Looking at how to connect the infrastructure that we have for the O Cloud to the Fronthall gateway. So, we could deploy O-DU into the cloud and have it able to connect to the TM500 through the Fronthall gateway.
Looking at trying to getan O-DU high / O-DU low instance that is continuously up. Therefore, we would move to continuous integration and test model. So, that new releases of the software would be tested by updating the existing version.
01-25: RSAC issue with the web page
Specify the properprocedure to safeguard the "Viavi" data set (possible solutions : Server in a lab or in a repository)!
Action Item : Ultan Kelly to check with peers and come back with recommendations to the RSAC
02-01: PLTs to fill the project goals/features for J Release which could be presented during F2F.
02-08: Rittwik Jana highlights for J release (except O-DU low) are finalized
Project reports (by features) (Note: From Aug. 3, it is decided that Project reports in groups will be strike out, and it will be done by features)
01-25: the list of project reports needs to be updated (with the start of our sprint in February)
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
01-04:Sridhar Raohave updated the release checklist. The doc projects is now tagged.The websites are updated too, also the the O-RAN Wiki page, and the O-RAN org page.
02-01: Maintenance Release set for next week TOC
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
11-02: Jakub: currently handled in WG10 tooling team; 2 main topics: SCCL itself, should be included in the code artifact, 2nd is the repository to make the file public; in progress, some braining storming, nothing for OSC to use directly; WG10 to generate the requirements; take to other WG, OFFICE, or OCOP, working on the design part of the thing; more difficult than expected;
11-09:Jakub Novymentioned that SCCL was discussed at this week's OSFG meeting, Suggest to follow up at next week TOC. More decisions needed at O-RAN level.
11-16:Jakub NovyThere is a meeting with O-RAN legal next week to review any potential issues.
11-30: David Kinsey A meeting took place with tooling within WG10. ACOP also needs to be consulted over the process. Jakub Novy to provide update on meeting with O-RAN legal.
12-07:Jakub NovyNot much to report. Got some feedback from O-RAN legal on brainstorming phase of WG10; Also checking with ETSI, Doug is helping.David Kinseycurrently pushing SCCL with WG3, WG10 and WG4.John Keeneyis of interest of publishing R1 related files with SCCL from WG2.David KinseyR1 related file may end up be an Open API.
A target of SCCL implementation may be possible by end of April
A summary is suitable to be presented to the TOC
02-01: WG10 working on process definition for ORAN. 3 activates planned for F2F - developing the process together with OSFG (outline, what are the steps, responsibilities; not necessarily the document itself), informing WGs about the changes, presenting to TSC.
Collaboration with OAI (lab interconnection) and Nephio
01-11: Nephio O-RAN Integration Status:Sagar Arora (Presentation can be found here TOC Documents)
02-01: Sagar Arora: in the SMO call this week, presentation about NF orchestration using SMO shown. AP Seshu Kumar Mudigantito upload the ppt to the TOC documents.
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
O DU High and O DU Low reworking together again and the next step is to connect O DU low back up to the TM500
Licensing issues (TM500) to be resolved by VIAVI
01-25: Progress : to get a Sandbox in Windriver
To move from Bedminster to there : our fronthaul gateway and our Grand Master Clock
02-01: East cost lab still down, Bedminster may stay down and we may move to Rutgers in New Jersey. David Kinsey working on that, alignment calls planned.
12-07:Sridhar RaoFrom the I release checklist page, only 5 projectsNONRTRIC, RICPLT, ODUHIGH*, INF, AIMLFW completed the committed features. Need all PTLs to work and complete by next Thursday for release vote.For the "Release documentation for Blog/Article on Release" item will have a dedicated marketing person to update the wiki and generate a PR for I release.Ankit Barvehow about "Features Implemented Mapping to O-RAN Spec by Project" table for I release?David KinseyIt might be kept at the project level for each PTL to fill in the details of the O-RAN specs impacting features.Ankit BarvePropose to add as a last section to the project.
01-11: RSAC "J" Release Planning Status
01-18: features for J release
Looking at how to connect the infrastructure that we have for the O Cloud to the Fronthall gateway. So, we could deploy O-DU into the cloud and have it able to connect to the TM500 through the Fronthall gateway.
Looking at trying to getan O-DU high / O-DU low instance that is continuously up. Therefore, we would move to continuous integration and test model. So, that new releases of the software would be tested by updating the existing version.
01-25: RSAC issue with the web page
Specify the properprocedure to safeguard the "Viavi" data set (possible solutions : Server in a lab or in a repository)!
Action Item : Ultan Kelly to check with peers and come back with recommendations to the RSAC
02-01: PTLs to fill the project goals/features for J Release which could be presented during F2F.
Project reports (by features) (Note: From Aug. 3, it is decided that Project reports in groups will be strike out, and it will be done by features)
01-25: the list of project reports needs to be updated (with the start of our sprint in February)
02-01: Energy savings dataset from Viavi - it is acceptable to encrypt it and let Viavi control the password. Process to request the dataset/password to be sorted. Help from Alex Stancu needed.
01-04: Sridhar Raohave updated the release checklist. The doc projects is now tagged. The websites are updated too, also the the O-RAN Wiki page, and the O-RAN org page.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
11-02: Jakub: currently handled in WG10 tooling team; 2 main topics: SCCL itself, should be included in the code artifact, 2nd is the repository to make the file public; in progress, some braining storming, nothing for OSC to use directly; WG10 to generate the requirements; take to other WG, OFFICE, or OCOP, working on the design part of the thing; more difficult than expected;
11-09:Jakub Novymentioned that SCCL was discussed at this week's OSFG meeting, Suggest to follow up at next week TOC. More decisions needed at O-RAN level.
11-16:Jakub NovyThere is a meeting with O-RAN legal next week to review any potential issues.
11-30: David Kinsey A meeting took place with tooling within WG10. ACOP also needs to be consulted over the process. Jakub Novy to provide update on meeting with O-RAN legal.
12-07: Jakub Novy Not much to report. Got some feedback from O-RAN legal on brainstorming phase of WG10; Also checking with ETSI, Doug is helping. David Kinsey currently pushing SCCL with WG3, WG10 and WG4.John Keeney is of interest of publishing R1 related files with SCCL from WG2. David Kinsey R1 related file may end up be an Open API.
Collaboration with OAI (lab interconnection) and Nephio
12-07: Irfan GhauriThe document that I prepared basically was co-signed by Ganesh and I'd like permission from Ganesh to be able to present. David Kinsey we'll put it on for next week.
12-07: David Kinsey has a draft for the joint workshop PR but needs get approval from AT&T. Still a pending question about O-DU-low, needs a decision with the roadmap to whether to keep the O-DU-low project. Need to send those questions to Lewis from Intel.
12-14: We walked through the OAI O-CU + OSC O-DU-High + OAI O-DU-Low presentation by Ganesh Shenbagaraman and Irfan Ghauri to be found in the Toc Documents folder
01-11: Nephio O-RAN Integration Status: Sagar Arora (Presentation can be found here TOC Documents)
01-11: Next Steps
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
12-07: Tracy Van Brakle The roadmap of the blueprint is in the form of a white paper and it's a drafty draft on OSFG contribution page. David Kinsey where's O-Cloud in this phase 1 (early iteration)? Nephio is just an enabler. We need O-Cloud to interconnect our labs. Tracy Van Brakle For the road map, introduce O-Cloud as a starting point, 4th quarter 2023; and then Cloudify O-Cloud, 2nd quarter 2024 (deployment by the SMO using O2 interface). David Kinsey when should we be targeting a demonstration with an OAI network function, using an OSC SMO to deploy it with Nephio enablers? 3 roadmaps (OSC, OAI, Nephio) have to be aligned. Saw demo at the workshop that use SMO + Near RT RIC + xApp on A1 to make policy change for DU bandwidth. So something is there but needs to be more generalized. Bala from Red Hat indicates that Nephio is creating their user stories and priorities for the R3 release (starting early 2024 towards the middle of 2024), and O2 IMS is one of them. Tracy Van Brakle Doug and I will see where srsRAN might fit in, and when if they do. srsRAN expressed their interest to participate.
12-07: Sridhar Rao From the I release checklist page, only 5 projects NONRTRIC, RICPLT, ODUHIGH*, INF, AIMLFW completed the committed features. Need all PTLs to work and complete by next Thursday for release vote.For the "Release documentation for Blog/Article on Release" item will have a dedicated marketing person to update the wiki and generate a PR for I release. Ankit Barve how about "Features Implemented Mapping to O-RAN Spec by Project" table for I release? David Kinsey It might be kept at the project level for each PTL to fill in the details of the O-RAN specs impacting features. Ankit Barve Propose to add as a last section to the project.
01-11: RSAC "J" Release Planning Status
01-18: features for J release
Looking at how to connect the infrastructure that we have for the O Cloud to the Fronthall gateway. So, we could deploy O-DU into the cloud and have it able to connect to the TM500 through the Fronthall gateway.
Looking at trying to get an O-DU high / O-DU low instance that is continuously up. Therefore, we would move to continuous integration and test model. So, that new releases of the software would be tested by updating the existing version.
01-25: RSAC issue with the web page
Specify the proper procedure to safeguard the "Viavi" data set (possible solutions : Server in a lab or in a repository)!
Action Item : Ultan Kelly to check with peers and come back with recommendations to the RSAC
Project reports (by features) (Note: From Aug. 3, it is decided that Project reports in groups will be strike out, and it will be done by features)
01-04: Sridhar Raohave updated the release checklist. The doc projects is now tagged. The websites are updated too, also the the O-RAN Wiki page, and the O-RAN org page.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
11-02: Jakub: currently handled in WG10 tooling team; 2 main topics: SCCL itself, should be included in the code artifact, 2nd is the repository to make the file public; in progress, some braining storming, nothing for OSC to use directly; WG10 to generate the requirements; take to other WG, OFFICE, or OCOP, working on the design part of the thing; more difficult than expected;
11-09:Jakub Novymentioned that SCCL was discussed at this week's OSFG meeting, Suggest to follow up at next week TOC. More decisions needed at O-RAN level.
11-16:Jakub NovyThere is a meeting with O-RAN legal next week to review any potential issues.
11-30: David Kinsey A meeting took place with tooling within WG10. ACOP also needs to be consulted over the process. Jakub Novy to provide update on meeting with O-RAN legal.
12-07: Jakub Novy Not much to report. Got some feedback from O-RAN legal on brainstorming phase of WG10; Also checking with ETSI, Doug is helping. David Kinsey currently pushing SCCL with WG3, WG10 and WG4.John Keeney is of interest of publishing R1 related files with SCCL from WG2. David Kinsey R1 related file may end up be an Open API.
A target of SCCL implementation may be possible by end of April
A summary is suitable to be presented to the TOC
Collaboration with OAI (lab interconnection) and Nephio
12-07: Irfan GhauriThe document that I prepared basically was co-signed by Ganesh and I'd like permission from Ganesh to be able to present. David Kinsey we'll put it on for next week.
12-07: David Kinsey has a draft for the joint workshop PR but needs get approval from AT&T. Still a pending question about O-DU-low, needs a decision with the roadmap to whether to keep the O-DU-low project. Need to send those questions to Lewis from Intel.
12-14: We walked through the OAI O-CU + OSC O-DU-High + OAI O-DU-Low presentation by Ganesh Shenbagaraman and Irfan Ghauri to be found in the Toc Documents folder
01-11: Nephio O-RAN Integration Status: Sagar Arora (Presentation can be found here TOC Documents)
01-11: Next Steps
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
12-07: Tracy Van Brakle The roadmap of the blueprint is in the form of a white paper and it's a drafty draft on OSFG contribution page. David Kinsey where's O-Cloud in this phase 1 (early iteration)? Nephio is just an enabler. We need O-Cloud to interconnect our labs. Tracy Van Brakle For the road map, introduce O-Cloud as a starting point, 4th quarter 2023; and then Cloudify O-Cloud, 2nd quarter 2024 (deployment by the SMO using O2 interface). David Kinsey when should we be targeting a demonstration with an OAI network function, using an OSC SMO to deploy it with Nephio enablers? 3 roadmaps (OSC, OAI, Nephio) have to be aligned. Saw demo at the workshop that use SMO + Near RT RIC + xApp on A1 to make policy change for DU bandwidth. So something is there but needs to be more generalized. Bala from Red Hat indicates that Nephio is creating their user stories and priorities for the R3 release (starting early 2024 towards the middle of 2024), and O2 IMS is one of them. Tracy Van Brakle Doug and I will see where srsRAN might fit in, and when if they do. srsRAN expressed their interest to participate.
12-07: Sridhar Rao From the I release checklist page, only 5 projects NONRTRIC, RICPLT, ODUHIGH*, INF, AIMLFW completed the committed features. Need all PTLs to work and complete by next Thursday for release vote.For the "Release documentation for Blog/Article on Release" item will have a dedicated marketing person to update the wiki and generate a PR for I release. Ankit Barve how about "Features Implemented Mapping to O-RAN Spec by Project" table for I release? David Kinsey It might be kept at the project level for each PTL to fill in the details of the O-RAN specs impacting features. Ankit Barve Propose to add as a last section to the project.
01-11: RSAC "J" Release Planning Status
01-18: features for J release
Looking at how to connect the infrastructure that we have for the O Cloud to the Fronthall gateway. So, we could deploy O-DU into the cloud and have it able to connect to the TM500 through the Fronthall gateway.
Looking at trying to get an O-DU high / O-DU low instance that is continuously up. Therefore, we would move to continuous integration and test model. So, that new releases of the software would be tested by updating the existing version.
Project reports (by features) (Note: From Aug. 3, it is decided that Project reports in groups will be strike out, and it will be done by features)
01-04: Sridhar Raohave updated the release checklist. The doc projects is now tagged. The websites are updated too, also the the O-RAN Wiki page, and the O-RAN org page.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
11-02: Jakub: currently handled in WG10 tooling team; 2 main topics: SCCL itself, should be included in the code artifact, 2nd is the repository to make the file public; in progress, some braining storming, nothing for OSC to use directly; WG10 to generate the requirements; take to other WG, OFFICE, or OCOP, working on the design part of the thing; more difficult than expected;
11-09:Jakub Novymentioned that SCCL was discussed at this week's OSFG meeting, Suggest to follow up at next week TOC. More decisions needed at O-RAN level.
11-16:Jakub NovyThere is a meeting with O-RAN legal next week to review any potential issues.
11-30: David Kinsey A meeting took place with tooling within WG10. ACOP also needs to be consulted over the process. Jakub Novy to provide update on meeting with O-RAN legal.
12-07: Jakub Novy Not much to report. Got some feedback from O-RAN legal on brainstorming phase of WG10; Also checking with ETSI, Doug is helping. David Kinsey currently pushing SCCL with WG3, WG10 and WG4.John Keeney is of interest of publishing R1 related files with SCCL from WG2. David Kinsey R1 related file may end up be an Open API.
A target of SCCL implementation may be possible by end of April
A summary is suitable to be presented to the TOC
Collaboration with OAI (lab interconnection) and Nephio
12-07: Irfan GhauriThe document that I prepared basically was co-signed by Ganesh and I'd like permission from Ganesh to be able to present. David Kinsey we'll put it on for next week.
12-07: David Kinsey has a draft for the joint workshop PR but needs get approval from AT&T. Still a pending question about O-DU-low, needs a decision with the roadmap to whether to keep the O-DU-low project. Need to send those questions to Lewis from Intel.
12-14: We walked through the OAI O-CU + OSC O-DU-High + OAI O-DU-Low presentation by Ganesh Shenbagaraman and Irfan Ghauri to be found in the Toc Documents folder
01-11: Nephio O-RAN Integration Status: Sagar Arora (Presentation can be found here TOC Documents)
01-11: Next Steps
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
12-07: Tracy Van Brakle The roadmap of the blueprint is in the form of a white paper and it's a drafty draft on OSFG contribution page. David Kinsey where's O-Cloud in this phase 1 (early iteration)? Nephio is just an enabler. We need O-Cloud to interconnect our labs. Tracy Van Brakle For the road map, introduce O-Cloud as a starting point, 4th quarter 2023; and then Cloudify O-Cloud, 2nd quarter 2024 (deployment by the SMO using O2 interface). David Kinsey when should we be targeting a demonstration with an OAI network function, using an OSC SMO to deploy it with Nephio enablers? 3 roadmaps (OSC, OAI, Nephio) have to be aligned. Saw demo at the workshop that use SMO + Near RT RIC + xApp on A1 to make policy change for DU bandwidth. So something is there but needs to be more generalized. Bala from Red Hat indicates that Nephio is creating their user stories and priorities for the R3 release (starting early 2024 towards the middle of 2024), and O2 IMS is one of them. Tracy Van Brakle Doug and I will see where srsRAN might fit in, and when if they do. srsRAN expressed their interest to participate.
Other
Standing/old business
OSC Lab
01-11: OSC Taiwan Lab Update
01-11: Lab Tool Update
Funding did not occur. It's risky and we may not get those tools.
12-07: Sridhar Rao From the I release checklist page, only 5 projects NONRTRIC, RICPLT, ODUHIGH*, INF, AIMLFW completed the committed features. Need all PTLs to work and complete by next Thursday for release vote.For the "Release documentation for Blog/Article on Release" item will have a dedicated marketing person to update the wiki and generate a PR for I release. Ankit Barve how about "Features Implemented Mapping to O-RAN Spec by Project" table for I release? David Kinsey It might be kept at the project level for each PTL to fill in the details of the O-RAN specs impacting features. Ankit Barve Propose to add as a last section to the project.
01-11: RSAC "J" Release Planning Status
Project reports (by features) (Note: From Aug. 3, it is decided that Project reports in groups will be strike out, and it will be done by features)
12-14: Motion from Thoralf to approve the release with the condition that the three outstanding projects, which the PTL were not represented (RICAPP, SMO, DOC) would close their project activities by 12/21. Seconded by John-Paul. Motion was Approved
12-21: Release Review, Conditions were met so 12-14 vote is confirmed.
01-04: Sridhar Raohave updated the release checklist. The doc projects is now tagged. The websites are updated too, also the the O-RAN Wiki page, and the O-RAN Org page.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
11-02: Jakub: currently handled in WG10 tooling team; 2 main topics: SCCL itself, should be included in the code artifact, 2nd is the repository to make the file public; in progress, some braining storming, nothing for OSC to use directly; WG10 to generate the requirements; take to other WG, OFFICE, or OCOP, working on the design part of the thing; more difficult than expected;
11-09:Jakub Novymentioned that SCCL was discussed at this week's OSFG meeting, Suggest to follow up at next week TOC. More decisions needed at O-RAN level.
11-16:Jakub NovyThere is a meeting with O-RAN legal next week to review any potential issues.
11-30: David Kinsey A meeting took place with tooling within WG10. ACOP also needs to be consulted over the process. Jakub Novy to provide update on meeting with O-RAN legal.
12-07: Jakub Novy Not much to report. Got some feedback from O-RAN legal on brainstorming phase of WG10; Also checking with ETSI, Doug is helping. David Kinsey currently pushing SCCL with WG3, WG10 and WG4.John Keeney is of interest of publishing R1 related files with SCCL from WG2. David Kinsey R1 related file may end up be an Open API.
11-02: the joint workshop, full and good agenda. Plus, OAI has good relationship with SRSRAN;
11-09:Irfan Ghaurireminder that workshop happens at Innovation Campus in Burlington not Boston Downtown. Approx 150 registered participants. Full agenda.
11-09APIrfan Ghaurito resend agenda to mailing list.
11-02:AP: Jinri Huangto reach O-RAN office to discuss the joint PR draft -
11-02: O-RAN and OAI will consider and work on a joint PR.
11-09: See AP review above.
Jinri HuangFrom Zbynek & Jindrich: O-RAN changing PR process so no new PRs this year.
Jinri HuangO-RAN can promote the PR if issued through OAI channel & Add links to it
Irfan GhauriOAI can help here. Draft proposed. Ongoing & will revert with an update.
11-09APIrfan GhauriFor OAI/OSC workshop: will revert with an update on PR content & channel
11-16:Irfan GhauriThe workshop was generally very well attended. NTIA and NSF attended to give government perspective on O-RAN. Good to get the opportunity to address government agencies directly. Demos were very well received. Presented the next phases of collaboration between OSC and OAI e.g. Nephio and OSC collaboration for SMO and relationship to OAI. Meeting next week with Radisys to discuss potential integration of OAI CU with OSC. Next steps are to try to operationalise the OSC collaboration roadmap with, for example, Nephio. Recordings of workshop, poster sessions and demo sessions to be made available online shortly. Need to have a plan / roadmap for OSC features through 2024 similar to the OAI roadmap.
11-16:Tracy Van BrakleThere is an opportunity for teams to present demo proposals at the upcoming North America O-RAN plugfest readout on Nov 29th. Tracy will post further information to the public mailing list.
11-30:Tracy Van BrakleReadout meeting took place for North American O-RAN plugfest. Some outstanding demonstrations were presented. Demonstrators and participants from industry an university faculty students. Mini-PR to be discussed to mark this event. Funding is starting to come from O-RAN Alliance and government agencies (in US and beyond). Martin Skorupski it was good to see things moving in alignment between the O-RAN Alliance and open source.
11-30: David Kinsey will prepare PR regarding the Boston meeting of OSC and OAI. Irfan Ghauri has shared the summary of meeting with OAI steering meeting. Interesting to learn that Nephio has input into the SMO (FOCOM).
11-30: Irfan Ghauri Next steps are to present a joint roadmap. Should be presented to and reviewed by the OSC TOC. David Kinsey there is a challenge for OSC to do better with creating a multi-release feature roadmap.
11-30: Irfan Ghauri follow-up discussions are already taking place for the traffic network functions. For example, Radisys are working on the O-DU integration with OAI. The workshop really helped to kickstart this collaboration between OSC and OAI. David Kinsey Do we continue to use the OSC O-DU (Low) or do we start to look towards OAI for this function? Ankit Barve has taken an action point at RSAC to investigate a mix n match approach with OSC and OAI for O-DU. Should have a clearer picture on this over the coming weeks.
12-07: Irfan GhauriThe document that I prepared basically was co-signed by Ganesh and I'd like permission from Ganesh to be able to present. David Kinsey we'll put it on for next week.
12-07: David Kinsey has a draft for the joint workshop PR but needs get approval from AT&T. Still a pending question about O-DU-low, needs a decision with the roadmap to whether to keep the O-DU-low project. Need to send those questions to Lewis from Intel.
12-14: We walked through the OAI O-CU + OSC O-DU-High + OAI O-DU-Low presentation by Ganesh Shenbagaraman and Irfan Ghauri to be found in the Toc Documents folder
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprintTracy Van Brakle.
11-09:Tracy Van Brakle: Draft of First version - aiming for Release 0 at end of year.
11-30:Tracy Van BrakleMeeting planned for December 14th to review the roadmap with O-RAN Alliance TSC co-chairs. OSFG meeting Monday 4th will review (5am PT).
11-30:Tracy Van BrakleNeed blueprint status, technical issues and roadmap as input to the TSC co-chair meeting.
11-30:Jinri HuangPlans to approach Jindrich Brett in O-RAN Alliance to confirm process for voting on a vendor co-chair for OSFG
12-07: Tracy Van Brakle The roadmap of the blueprint is in the form of a white paper and it's a drafty draft on OSFG contribution page. David Kinsey where's O-Cloud in this phase 1 (early iteration)? Nephio is just an enabler. We need O-Cloud to interconnect our labs. Tracy Van Brakle For the road map, introduce O-Cloud as a starting point, 4th quarter 2023; and then Cloudify O-Cloud, 2nd quarter 2024 (deployment by the SMO using O2 interface). David Kinsey when should we be targeting a demonstration with an OAI network function, using an OSC SMO to deploy it with Nephio enablers? 3 roadmaps (OSC, OAI, Nephio) have to be aligned. Saw demo at the workshop that use SMO + Near RT RIC + xApp on A1 to make policy change for DU bandwidth. So something is there but needs to be more generalized. Bala from Red Hat indicates that Nephio is creating their user stories and priorities for the R3 release (starting early 2024 towards the middle of 2024), and O2 IMS is one of them. Tracy Van Brakle Doug and I will see where srsRAN might fit in, and when if they do. srsRAN expressed their interest to participate.
Other
11-09: Mix up with times for this week's OSFG meeting. Calendar has now been updated to 7AM EST (Jinri Huang).
11-30:David KinseyBedminster lab remains down. Considering consolidation into a different AT&T lab, in a different location (still NJ), which is more aligned with OSC work. Access processes should be similar to current access process.APonDavid KinseyandTracy Van Brakleto review and revert.
11-30:David Kinseyproposals for lab contract to be reviewed within AT&T. Work is ongoing and progress is being made. Next two weeks are critical in order to get funding from O-RAN Alliance and finalise lab plans.
11-02: Mapping b/w OSC project work and WG spec. work discussed. There is a table for this mapping for H release. See here:H Release(The table at the end of the page). Good example from INF project with a detailed excel file to record the detailed mapping. Jinri encourage the PTL to make such efforts, or at least fill in the table. Some echos on this suggestion. Some comments are that the work is beyond trial and time-consuming. sometime difficult since some spec. may not have stage-3 defined. Another suggestion is to use the conformance spec. Jinri responded that the value of the work is significant. Yet admitted community is contribution-driven. Yet still strongly encourage the team to do this.
11-02:AP:Jinrito work with Jackie to refine the table template.
11-09: See AP review above.
Jinri Huang: This table is for mapping template between project & specs. No update this week. Will continue
11-09:AP:Sridhar Raowill report back next week on progress/status of release process & checklist
11-16: Sridhar has reviewed the status of release I documentation. Many documents still outstanding.AP: All PTLs to update release I checklist and ensure a plan to finalise release docs.
11-30:Sridhar Raois not seeing updates on wiki release pages. Based on current lack of progress, it may be difficult to meet release deadlines for December. PTLs and teams need more urgency in updating release I pages / wiki, highlights, release checklist and other release-relevant documentation. Once all documentation is ready, the only thing required is a TOC release vote.
11-30:David KinseyRelease I date is provisionally targeting 25th - 29th December. This may be challenging for some. Need to agree a date for the release vote to take place.Thoralf Czichysuggests the 14th December (keeping 21st December as a backup) for the Release I vote.David Kinseymade motion to release on 14th December,Thoralf Czichyseconded. Motion approved.
12-07: Sridhar Rao From the I release checklist page, only 5 projects NONRTRIC, RICPLT, ODUHIGH*, INF, AIMLFW completed the committed features. Need all PTLs to work and complete by next Thursday for release vote.For the "Release documentation for Blog/Article on Release" item will have a dedicated marketing person to update the wiki and generate a PR for I release. Ankit Barve how about "Features Implemented Mapping to O-RAN Spec by Project" table for I release? David Kinsey It might be kept at the project level for each PTL to fill in the details of the O-RAN specs impacting features. Ankit Barve Propose to add as a last section to the project.
Project reports (by features) (Note: From Aug. 3, it is decided that Project reports in groups will be strike out, and it will be done by features)
AP: Project/Feature Update from Thoralf Czichy on Nov 16 (report not ready) → Nov 23: link
11-30: Thoralf Czichy significant number of items which were planned for Release I will be delayed to Release J. However, they are being worked on so confidence is high that they will be delivered in Release J timeframe. Some bug fixes in Release I, others moved to Release J. Work continues to enable Release I. Detailed RIC Platform project report is available here.
AP: Project/Feature Update from Alex Stancu on Nov 16
11-16: Team data set in Nexus - publicly available to read. AI/ML team looking into model training. Energy savings data set being reviewed by NTUST. Release I will deliver the enablers and E2E demo will be available in release J.