*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
reminder: Starting (May-5 2022) we meet on Thursdays, at 9am EST. Time Zone Map
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-08-03: SUNIL SINGH request for approval vote for a new xApp repo RICAPP project contributed & maintained by Alexandre Huff from UTFPR Univ. New xApp implements the E2SM-CCC service model. Motion proposed by David Kinsey , seconded by James Li , motion passed unanimously.
2023-08-03: Tack Maintenance Release: RICAPP SUNIL SINGH , ODULOW Ankit Barve , NONRTRIC John Keeney all on track, will close out next week.
2023-08-10: Approval of the Maintenance Release.
2023-09-07: None of the PTLs brought any items.
AP Review
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Publishing O-RAN code-like segments under SCCL CLA Jinri Huang
2023-05-18: waiting for a feedback from O-RAN Office
2023-09-14: Jakub NovyDavid Kinsey mentioned it was more of an introductory meeting (setting our position) . Next meeting is scheduled on post the ToC Meeting
Naming and directory structure has been agreed upon and next step will be to get it approve.
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-09-07: Irfan Ghauri shared the updates on the event details. This is an "in person only" event, refer to Link for detailed Agenda. Action:Jinri Huang to send invite on O-RAN SC and relevant folks in O-RAN Alliance based on the format to be shared by Irfan Ghauri
2023-09-14: Irfan Ghauri provided an update on Committee Meeting.
Plan is to follow a workshop mode, 3 sessions (RAN, OAM and Lab Status) and demo.
Made call for speakers and panels.
Provide OAI ~Nephio and proposed a joint discussion on the topic.
David Kinsey Proposed to showcase some O-RAN SC F2F demos at the event.
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint Tracy Van Brakle
demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)
AsiaPac - Taiwan and other locations
EU
North America
sources of funding to assure sustain-ability
O-RAN nGRG - application due August __, 2023
Public Sector - NSF? NTIA?
Whitepaper (2023-09-14: It was clarified to be a whitepaper)
O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October __ to __
2023-08-03: Next F2F registration is now opened. Rittwik Jana mentioned ONF reached out for the energy saving topics. Martin Skorupski put it on the agenda of OSFG meeting to talk about energy savings and the collaboration with ONF.
2023-09-07: David Kinsey made a call for sessions and requested members to update them directly in the event page. Refer Link for updates. AIML, SMO de-compositions within O-Cloud & Energy Saving sessions were discussed and added to the list. Proposal is to have 6 slots. David Kinsey proposed to cancel the ToC Call during the event week.
2023-09-14: David Kinsey mentioned that we should have at least 5 sessions for the planned items (Refer Link). The schedule is yet to be finalized. Details to be updated so that event can be planned better.
Others
Standing/old business
OSC Lab
2023-08-17: Our Bedminster Lab is in the process of move David Kinsey
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
2023-08-03: Rittwik Jana Focus on energy savings; Figure out a plan of execution to get the metrics; ML modeling; SMO discussion.
2023-09-07: David Kinsey made a call to PTL to update the I Release plan. PTLs to complete this before the F2F Meeting. Rittwik Jana provided updates on the data set.
2023-09-14: Rittwik Jana updated that there are 2 datasets Alex is working on one dataset and Viavi is working on the other.
Project reports (by features)
2023-08-03: Project reports in groups will be strike out, and it will be done by features, which will need to be restructured.
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-08-03: SUNIL SINGH request for approval vote for a new xApp repo RICAPP project contributed & maintained by Alexandre Huff from UTFPR Univ. New xApp implements the E2SM-CCC service model. Motion proposed by David Kinsey , seconded by James Li , motion passed unanimously.
2023-08-03: Tack Maintenance Release: RICAPP SUNIL SINGH , ODULOW Ankit Barve , NONRTRIC John Keeney all on track, will close out next week.
2023-08-10: Approval of the Maintenance Release.
2023-09-07: None of the PTLs brought up any items.
AP Review
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-09-07: Irfan Ghauri shared the updates on the event details. This is an "in person only" event, refer to Link for detailed Agenda. Action:Jinri Huang to send invite on O-RAN SC and relavant folks in O-RAN Alliance based on the format to be shared by Irfan Ghauri
OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint Tracy Van Brakle
demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)
AsiaPac - Taiwan and other locations
EU
North America
sources of funding to assure sustain-ability
O-RAN nGRG - application due August __, 2023
Public Sector - NSF? NTIA?
roadmap (White Paper? Info Report)
O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October __ to __
2023-08-03: Next F2F registration is now opened. Rittwik Jana mentioned ONF reached out for the energy saving topics. Martin Skorupski put it on the agenda of OSFG meeting to talk about energy savings and the collaboration with ONF.
2023-09-07: David Kinsey made a call for sessions and requested members to update them directly in the event page. Refer Link for updates. AIML, SMO de-compositions within O-Cloud & Energy Saving sessions were discussed and added to the list. Proposal is to have 6 slots. David Kinsey proposed to cancel the ToC Call during the event week.
Others
Standing/old business
OSC Lab
2023-08-17: Our Bedminster Lab is in the process of move David Kinsey
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
2023-08-03: Rittwik Jana Focus on energy savings; Figure out a plan of execution to get the metrics; ML moddeling; SMO discussion.
2023-09-07: David Kinsey made a call to PTL to update the I Release plan. PTLs to complete this before the F2F Meeting. Rittwik Jana provided updates on the data set.
Project reports (by features)
2023-08-03: Project reports in groups will be strike out, and it will be done by features, which will need to be restructured.
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-08-03: SUNIL SINGH request for approval vote for a new xApp repo RICAPP project contributed & maintained by Alexandre Huff from UTFPR Univ. New xApp implements the E2SM-CCC service model. Motion proposed by David Kinsey , seconded by James Li , motion passed unanimously.
2023-08-03: Tack Maintenance Release: RICAPP SUNIL SINGH , ODULOW Ankit Barve , NONRTRIC John Keeney all on track, will close out next week.
2023-08-10: Approval of the Maintenance Release.
AP Review
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)
AsiaPac - Taiwan and other locations
EU
North America
sources of funding to assure sustain-ability
O-RAN nGRG - application due August __, 2023
Public Sector - NSF? NTIA?
roadmap (White Paper? Info Report)
O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October __ to __
2023-08-03: Next F2F registration is now opened. Rittwik Jana mentioned ONF reached out for the energy saving topics. Martin Skorupski put it on the agenda of OSFG meeting to talk about energy savings and the collaboration with ONF.
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
2023-08-03: Rittwik Jana Focus on energy savings; Figure out a plan of execution to get the metrics; ML moddeling; SMO discussion.
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-08-03: SUNIL SINGH request for approval vote for a new xApp repo RICAPP project contributed & maintained by Alexandre Huff from UTFPR Univ. New xApp implements the E2SM-CCC service model. Motion proposed by David Kinsey , seconded by James Li , motion passed unanimously.
2023-08-03: Tack Maintenance Release: RICAPP SUNIL SINGH , ODULOW Ankit Barve , NONRTRIC John Keeney all on track, will close out next week.
2023-08-10: Approval of the Maintenance Release.
AP Review
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)
AsiaPac - Taiwan and other locations
EU
North America
sources of funding to assure sustain-ability
O-RAN nGRG - application due August __, 2023
Public Sector - NSF? NTIA?
roadmap (White Paper? Info Report)
O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October __ to __
2023-08-03: Next F2F registration is now opened. Rittwik Jana mentioned ONF reached out for the energy saving topics. Martin Skorupski put it on the agenda of OSFG meeting to talk about energy savings and the collaboration with ONF.
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
2023-08-03: Rittwik Jana Focus on energy savings; Figure out a plan of execution to get the metrics; ML moddeling; SMO discussion.
Project reports (by features)
2023-08-03: Project reports in groups will be strike out, and it will be done by features, which will need to be restructured.
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-08-03: SUNIL SINGH request for approval vote for a new xApp repo RICAPP project contributed & maintained by Alexandre Huff from UTFPR Univ. New xApp implements the E2SM-CCC service model. Motion proposed by David Kinsey , seconded by James Li , motion passed unanimously.
2023-08-03: Tack Maintenance Release: RICAPP SUNIL SINGH , ODULOW Ankit Barve , NONRTRIC John Keeney all on track, will close out next week.
2023-08-10: Approval of the Maintenance Release.
AP Review
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)
AsiaPac - Taiwan and other locations
EU
North America
sources of funding to assure sustain-ability
O-RAN nGRG - application due August __, 2023
Public Sector - NSF? NTIA?
roadmap (White Paper? Info Report)
O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October __ to __
2023-08-03: Next F2F registration is now opened. Rittwik Jana mentioned ONF reached out for the energy saving topics. Martin Skorupski put it on the agenda of OSFG meeting to talk about energy savings and the collaboration with ONF.
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
2023-08-03: Rittwik Jana Focus on energy savings; Figure out a plan of execution to get the metrics; ML moddeling; SMO discussion.
Project reports (by features)
2023-08-03: Project reports in groups will be strike out, and it will be done by features, which will need to be restructured.
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-08-03: SUNIL SINGH request for approval vote for a new xApp repo RICAPP project contributed & maintained by Alexandre Huff from UTFPR Univ. New xApp implements the E2SM-CCC service model. Motion proposed by David Kinsey , seconded by James Li , motion passed unanimously.
2023-08-03: Tack Maintenance Release: RICAPP SUNIL SINGH , ODULOW Ankit Barve , NONRTRIC John Keeney all on track, will close out next week.
2023-08-10: Approval of the Maintenance Release.
AP Review
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)
AsiaPac - Taiwan and other locations
EU
North America
sources of funding to assure sustain-ability
O-RAN nGRG - application due August __, 2023
Public Sector - NSF? NTIA?
roadmap (White Paper? Info Report)
O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October __ to __
2023-08-03: Next F2F registration is now opened. Rittwik Jana mentioned ONF reached out for the energy saving topics. Martin Skorupski put it on the agenda of OSFG meeting to talk about energy savings and the collaboration with ONF.
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
2023-08-03: Rittwik Jana Focus on energy savings; Figure out a plan of execution to get the metrics; ML moddeling; SMO discussion.
Project reports (one group per week, rotating)
2023-08-03: Project reports in groups will be strike out, and it will be done by features, which will need to be restructured.
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-08-03: SUNIL SINGH request for approval vote for a new xApp repo RICAPP project contributed & maintained by Alexandre Huff from UTFPR Univ. New xApp implements the E2SM-CCC service model. Motion proposed by David Kinsey , seconded by James Li , motion passed unanimously.
2023-08-03: Tack Maintenance Release: RICAPP SUNIL SINGH , ODULOW Ankit Barve , NONRTRIC John Keeney all on track, will close out next week.
AP Review
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)
AsiaPac - Taiwan and other locations
EU
North America
sources of funding to assure sustain-ability
O-RAN nGRG - application due August __, 2023
Public Sector - NSF? NTIA?
roadmap (White Paper? Info Report)
O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October __ to __
2023-08-03: Next F2F registration is now opened. Rittwik Jana mentioned ONF reached out for the energy saving topics. Martin Skorupski put it on the agenda of OSFG meeting to talk about energy savings and the collaboration with ONF.
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
2023-08-03: Rittwik Jana Focus on energy savings; Figure out a plan of execution to get the metrics; ML moddeling; SMO discussion.
Project reports (one group per week, rotating)
2023-08-03: Project reports in groups will be strike out, and it will be done by features, which will need to be restructured.
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
Work three things in parallel: demonstrations within university labs (multiple regions); roadmap; sources of funding to assure sustain-ability
:For the release. we need to get the release approved. Everybody filled in their contributions on release page except for RIC Apps - that is still pending (has not been done). Are we not including RIC Apps in this release?
Ankit Barve What about documentation? James Li Not listed ... David Kinsey It is complete - heard from Tunisia ... and should (will) be included within list of release items.
Avinash Bhat Let's go for a vote ... the plan is to do the release without it the RIC Apps being pushed. David Kinsey As part of the H release … All those in favor say, aye, this is David Kinsey saying, Aye.
Motion approved unanimously with a note that caps will be considered for the maintenance to this release
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)
AsiaPac - Taiwan and other locations
EU
North America
sources of funding to assure sustain-ability
O-RAN nGRG - application due August __, 2023
Public Sector - NSF? NTIA?
roadmap (White Paper? Info Report)
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October __ to __
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang 2023-06-08David Kinsey : recommended text based demo along with 2-3 min long video
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
Work three things in parallel: demonstrations within university labs (multiple regions); roadmap; sources of funding to assure sustain-ability
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang 2023-06-08David Kinsey : recommended text based demo along with 2-3 min long video
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
2023-07-06: David KinseyFor the release. we need to get the release approved. Everybody filled in their contributions on release page except for RIC Apps - that is still pending (has not been done). Are we not including RIC Apps in this release?
Ankit Barve What about documentation? James Li Not listed ... David Kinsey It is complete - heard from Tunisia ... and should (will) be included within list of release items.
Avinash Bhat Let's go for a vote ... the plan is to do the release without it the RIC Apps being pushed. David Kinsey As part of the H release … All those in favor say, aye, this is David Kinsey saying, Aye.
Motion approved unanimously with a note that caps will be considered for the maintenance to this release.
2023-07-06: Release H approved (with one condition); Release I planning to begin
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
Work three things in parallel: demonstrations within university labs (multiple regions); roadmap; sources of funding to assure sustain-ability
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang 2023-06-08David Kinsey : recommended text based demo along with 2-3 min long video
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
2023-07-06: David KinseyFor the release. we need to get the release approved. Everybody filled in their contributions on release page except for RIC Apps - that is still pending (has not been done). Are we not including RIC Apps in this release?
Ankit Barve What about documentation? James Li Not listed ... David Kinsey It is complete - heard from Tunisia ... and should (will) be included within list of release items.
Avinash Bhat Let's go for a vote ... the plan is to do the release without it the RIC Apps being pushed. David Kinsey As part of the H release … All those in favor say, aye, this is David Kinsey saying, Aye.
Motion approved unanimously with a note that caps will be considered for the maintenance to this release.
2023-07-06: Release H approved (with one condition); Release I planning to begin
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-05-18: decided to first clarify the terms of the OAI-OSC collaboration (AP: OSFG Jinri HuangTracy Van Brakle) before getting into the details of the demo scenario (initially proposed for Osaka F2F) and of labs interconnection. Lab aspects from OSC point of view could be discussed next week with "INF lab II" report
2023-05-25: Tracy Van Brakle OAI proposed 3 demos. Details on the proposals will be shared by email to discuss which ones are more related to OSC development.
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang 2023-06-08David Kinsey : recommended text based demo along with 2-3 min long video
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
2023-07-06: David KinseyFor the release. we need to get the release approved. Everybody filled in their contributions on release page except for RIC Apps - that is still pending (has not been done). Are we not including RIC Apps in this release?
Ankit Barve What about documentation? James Li Not listed ... David Kinsey It is complete - heard from Tunisia ... and should (will) be included within list of release items.
Avinash Bhat Let's go for a vote ... the plan is to do the release without it the RIC Apps being pushed. David Kinsey As part of the H release … All those in favor say, aye, this is David Kinsey saying, Aye.
Motion approved unanimously with a note that RIC Apps will be considered for the maintenance to this release.
2023-07-06: Release H approved (with one condition); Release I planning to begin
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-05-18: decided to first clarify the terms of the OAI-OSC collaboration (AP: OSFG Jinri HuangTracy Van Brakle) before getting into the details of the demo scenario (initially proposed for Osaka F2F) and of labs interconnection. Lab aspects from OSC point of view could be discussed next week with "INF lab II" report
2023-05-25: Tracy Van Brakle OAI proposed 3 demos. Details on the proposals will be shared by email to discuss which ones are more related to OSC development.
2023-06-29: Jinri Huang Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang 2023-06-08David Kinsey : recommended text based demo along with 2-3 min long video
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
2023-06-01: Presentation by MVPC co-chair 'SU GU' on "MVP-C Releases and Features Introduction to OSC"
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page. David Kinsey to send reminder to above project PTLs to update the H release page and also to create I release page with project template. H release to be postponed on next TOC July 6th Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any. Jinri Huang to check regarding PR statement.
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-05-18: decided to first clarify the terms of the OAI-OSC collaboration (AP: OSFG Jinri HuangTracy Van Brakle) before getting into the details of the demo scenario (initially proposed for Osaka F2F) and of labs interconnection. Lab aspects from OSC point of view could be discussed next week with "INF lab II" report
2023-05-25: Tracy Van Brakle OAI proposed 3 demos. Details on the proposals will be shared by email to discuss which ones are more related to OSC development.
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang 2023-06-08David Kinsey : recommended text based demo along with 2-3 min long video
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
2023-06-01: Presentation by MVPC co-chair 'SU GU' on "MVP-C Releases and Features Introduction to OSC"
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-05-18: decided to first clarify the terms of the OAI-OSC collaboration (AP: OSFG Jinri HuangTracy Van Brakle) before getting into the details of the demo scenario (initially proposed for Osaka F2F) and of labs interconnection. Lab aspects from OSC point of view could be discussed next week with "INF lab II" report
2023-05-25: Tracy Van Brakle OAI proposed 3 demos. Details on the proposals will be shared by email to discuss which ones are more related to OSC development.
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang 2023-06-08David Kinsey : recommended text based demo along with 2-3 min long video
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
2023-06-01: Presentation by MVPC co-chair 'SU GU' on "MVP-C Releases and Features Introduction to OSC"
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
2023-06-08 Sridhar Rao License scanning completed and report has been sent to all PTLs James Li Patch has been submitted for the AI raised under integration project
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-05-18: decided to first clarify the terms of the OAI-OSC collaboration (AP: OSFG Jinri HuangTracy Van Brakle) before getting into the details of the demo scenario (initially proposed for Osaka F2F) and of labs interconnection. Lab aspects from OSC point of view could be discussed next week with "INF lab II" report
2023-05-25: Tracy Van Brakle OAI proposed 3 demos. Details on the proposals will be shared by email to discuss which ones are more related to OSC development.
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
2023-06-01: Presentation by MVPC co-chair 'SU GU' on "MVP-C Releases and Features Introduction to OSC"
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-05-18: decided to first clarify the terms of the OAI-OSC collaboration (AP: OSFG Jinri HuangTracy Van Brakle) before getting into the details of the demo scenario (initially proposed for Osaka F2F) and of labs interconnection. Lab aspects from OSC point of view could be discussed next week with "INF lab II" report
2023-05-25: Tracy Van Brakle OAI proposed 3 demos. Details on the proposals will be shared by email to discuss which ones are more related to OSC development.
2023-05-25: discussions are still at an early phase. An update will be provided in the next meetings.
O-RAN next phase
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-25: Agenda for OSC presentations is still in progress. No request were made so far from PTLs. It is further clarified that the scope is to O-RAN Alliance an overview on how O-RAN features have been considered in OSC development. This does not necessarily involve all the OSC project so PTLs should make some proposal. At the last F2F in Prague, some O-RAN members (e.g. WG6 cochair) expressed their interest in receiving guidance from OSC.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang
2023-05-25: Jinri Huang already received some proposals. It is clarified that the demos can either be a single project or multi-project initiative. A summary of the proposals will be provided next week (under AI 5)
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
2023-05-26 Issues on moderation/permission for comments on the wiki (see message from John Keeney )
Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial. Matt will keep on working on this and update the group.
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
2023-05-18: decided to first clarify the terms of the OAI-OSC collaboration (AP: OSFG Jinri HuangTracy Van Brakle) before getting into the details of the demo scenario (initially proposed for Osaka F2F and of labs interconnection. Lab aspects from OSC point of view could be discussed next week with "INF lab II" report
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
2023-05-18: Jinri Huang proposed date is May 30th. to be confirmed
2023-05-18: Clarified that the scope of the OSC presentations to F2F is to show what OSC is doing and how it related to O-RAN WGs work. These will be OSC open meeting (OSC zoom meeting). Jackie Huang and Seshu Kumar Mudiganti mentioned that INF project discussed about ONAP/OSC cross-coordination on O-Cloud activities (from Sylva presentation last week). David Kinsey suggested to give an overview from INF to O-RAN WG6 in Osaka.
2023-05-18: AP All PTLs: project interested in showing a video demo during Osaka F2F (as in Madrid F2F) to contact Jinri Huang
Others
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
AP (from 2023-05-04) For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
Original primary goals based on contributions from Nokia, Samsung, HCL, Capgemini, Parallel Wireless, Alexandre Huff (UTFPR) and Abhijit G:
We will deprecate the RMR-based E2 subscription interface and H-release xApps need to use the REST based interface already supported by the the C++, go, and python xApp frameworks (RIC-375). The subscription manager should handle subscriptions for failing xApps (RIC-929) and provide a callback on subscription delete success/failure (RIC-928). We plan to implement the RIC subscription delete required procedure (RIC-851)
Update to newer golang version of all components (RIC-881)
We will develop a CRD, i.e., a K8S operator on top of the DMS REST API to simplify xApp deployment (RIC-715). Also the DMS Rest interface gets the missing delete API (RIC-954).RIC-717 allows to deploy multiple cooperating xApps together.
On E2 side we will implement the E2 Reset procedure from RAN to RIC (RIC-949)and the RIC Subscription Delete procedure (RIC-851). We also implement robustness improvements (RIC-932 for reconnect cases) and troubleshooting improvements (RIC-813, RIC-814).
There's work planned to deploy the kserve-based model provisioning from the AI/ML project into the RIC platform (RIC-955)
The xapp frameworks for Golang (RIC-930), C++ andRust (RIC-951) will get some enhancements that are already implemented in the other languages, incl. support for xApp registration in the xapp-framework-cpp (RIC-705).
E2T (RIC-813) and E2Mgr (RIC-814) support dynamic changing of log levels for better troubleshooting
RIC-953 A1 testing improvements and bug fixes
Added to plan during H:
Support for policy status notifications in A1 (RIC-973 (incl. RIC-975)
Achieved H release highlights= high-level release notes (TODO-date) below (note that the release image list is here: TODO-link)
E2 reset (from E2 node to RIC), E2 subscription delete required, A1 policy status notfications
Preparation of feature for I release, e.g., include xApps in subscription delete required decision
For the H release of the near-RT RIC we do only limited integration testing: only the use cases: deploy RIC, deploy xApp, make E2 connection, get list of A1 policies has been tested.
Filled in end-of-release checklist: TODO-link
Status 2023-05-11: From the 22 epics planned (link) we implemented 4(link). 6 items have been moved out of the H release, e.g, because of implementation delays (link). Incomplete items: 12 (link). Additionally we fixed 8 bugs and small implementation tasks (link)
AP (from 2023-02-23)Jinri Huang : push O-RAN legal to get feedback and get statement from O-RAN legal on how to enforce the SCCP CLA
2023-04-06: AP update: mail sent to O-RAN office requesting the SCCL CLA enforcement, waiting for the feedback
2023-04-13: response back from O-RAN Office. Details to be discussed later.
2023-05-04: no update
AP (from 2023-03-16)Jakub Novy: Check on progress that Jindrich is making. We continue working on a way to publish O-RAN code-like segments.
Jakub had a session with Jindrich on what is needed. Next step is with Jindrich. Jakub also had a discussion with WG3's Claudio.
Jakub commented that we once this becomes clear, we should talk with other WG. WG3 needs are pretty clear.
2023-04-20: no update but Jakub Novy will keep on monitoring.
2023-03-23, 2023-03-30: no update, O-RAN office is looking for suitable solution. Jakub waiting for Jindrich.
2023-04-13: no update. Still waiting for Office to feed back.
2023-04-20: Jinri Huang explained to the O-RAN office. Had conversations with Sridhar, and seems like the SCCL CLA was not that complicated. Recommend to close the AP and re-open it in case there's any issue in the future.
2023-04-27: Jakub Novy still following up on the solution. It's worth mentioning that OSFG should be informed about this activity because this seems to benefit to their agenda.
2023-05-04: AP is closed. Item is moved under OSFG agenda item.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
(2023-04-13) AP: Julien Boudani to reach Sylva and invite them to OSC to give an introduction;
2023-04-27: Julien Boudani will invite Sylva to TOC to give a 30-minute presentation on 5/11 via email. Confirmed by email
2023-05-04: AP is closed.
Others
AP (from 2023-04-27):David Kinsey next O-RAN F2F is 6/29-6/23 in Osaka, Japan. We need to have more conversations with the WGs by having some joint sessions with them. Now the topics are beginning to merge onto different team pages and we can plan ahead with WGs to make sure we have a slot with them. It's about 7 weeks before the F2F and let's have a talk on this at the next RSAC.
2023-05-04: AP is closed. Planning of F2F meeting agenda will be taken by RSAC
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Presentation of project Sylva will be given to TOC on May 11th, for the first 30 minutes of the call.
Standing/old business
OSC Lab
David KinseyCurrent focus is on the deployment of the tools O-RAN is purchasing (simulators and RIC tester) in Bedminster Lab. Cupertino will connect to Bedminster to federate and support end-to-end use cases. See also information in the RSAC status report
Collaboration with OAI
AP (from 2023-03-09) David KinseyOSC and OAI lab connection. The overall goal is to have some result of such a cooperation that can be presented at next O-RAN f-2-f.
2023-04-20: David Kinsey no update. Talked to Rich on this and there shouldn't be any problem setting up the connection.
2023-04-27: David Kinsey heard that Tracy Van Brakle and others are thinking of using OTIC lab to use our released software to interconnect with OAI. Need to hear from OSFG on the final decision before moving forward.
2023-05-04: AP is closed
5G Super Blueprint status - to be considered for H release.
AP (from 2023-04-27):Sridhar Rao docker account has been created for OSC; Matthew Watkinsfiled a request for open source credits on behalf of the project but not sure when will hear back the results.
2023-05-04: AP is closed
Project reports (one group per week, rotating)
2023-05-04: Group 1: RSAC, Integration I (cross-project testing related), infrastructure
For bilateral coordination with O-RAN Alliance on Feature Plan, it is agreed to hold the overall presentation from O-RAN MVP-C co-chair in TOC (AP Jinri Huang open), while further Iterations with individual feature rapporteurs will be arranged in RSAC
Integration I (cross-project testing related) James Li
Group 4: Integration II (lab related), O-DU-HIGH, O-DU-LOW
Any Other Business (AoB)
Due to national holidays on May 18th, for the next round, OAM will be presented on May 11th together with group 2 topics and SIM will be presented on May 25th together with group 4 topics. Updated schedule:
2023-05-11: RIC, RICAPP, AIMLFW, OAM (30 min overall, due to Sylva presentation in the first half an hour)
2023-05-18: NONRTRIC, SMO
2023-05-25: Integration II (lab related), O-DU-HIGH, O-DU-LOW, SIM
*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: Motion proposed by Andrea Buldorini , seconded by Avinash Bhat , motion approved unanimously.
Review of Today's Agenda
suggested and agreed by the team to go through AP list first, then continue the discussion on the proposal from last week. if time allows, then review the stand items.
AP (from 2023-02-23)Jinri Huang : push O-RAN legal to get feedback and get statement from O-RAN legal on how to enforce the SCCP CLA.
Sridhar Rao I have checked with LF legal. SCCP is already created. LF will be hosting the repo, but it's not a legal entity for SCCP and SCCL (similar to SCP and SCL). It's O-RAN legal.
2023-03-23: David mentioned, for example, scans to be done by O-RAN.
Jinri to check what this was about and if it is already resolved. David suggested that under this AP we also need knowledge on process for the checks that
Jinri Huang To discuss SCCL implementation, a meeting with O-RAN office and some experts is arranged for next week (=last week of February).
2023-03-30: no update
2023-04-06: AP update: mail sent to O-RAN office requesting the SCCL CLA enforcement, waiting for the feedback;
23-04-13: response back from O-RAN Office. Details to be discussed later.
AP (from 2023-03-16)Jakub Novy: Check on progress that Jindrich is making. We continue working on a way to publish O-RAN code-like segments.
Jakub had a session with Jindrich on what is needed. Next step is with Jindrich. Jakub also had a discussion with WG3's Claudio.
Jakub commented that we once this becomes clear, we should talk with other WG. WG3 needs are pretty clear.
2023-04-20: no update but Jakub Novy will keep on monitoring.
2023-03-23, 2023-03-30: no update, O-RAN office is looking for suitable solution. Jakub waiting for Jindrich.
2023-04-13: no update. Still waiting for Office to feed back.
2023-04-20: Jinri Huang explained to the O-RAN office. Had conversations with Sridhar, and seems like the SCCL CLA was not that complicated. Recommend to close the AP and re-open it in case there's any issue in the future.
2023-04-27: Jakub Novy still following up on the solution. It's worth mentioning that OSFG should be informed about this activity because this seems to benefit to their agenda.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG discussions
2023-03-09,2023-03-16, 2023-03-30: no news.
O-RAN next phase
2023-02-09: James Li presented OSC revamp. A deep-dive session is scheduled during the F2F.
2023-02-23: James Li Next step is how we are going to execute. First thing is the impact OSC wants to make and the second is CI/CD/CT.
2023-03-02: Jinri: better mapping between OSC work and O-RAN working groups needed. Wish for OSC taking input from O-RAN working groups.
2023-03-09: AP (from 2023-03-09)David Kinsey to discuss with Jinri on what can be done to get this (=better cooperation) forward - goal should be refined and then we can come up with a plan. James commented that an e-mail to TOC (not "discuss") mailing list could help to refine this.
2023-03-30
James: TSC co-chairs requested updated on "O-RAN next phase". Jinri preparing something for next week TSC
OSFG/OSC and OAI workshop planned for second half of this year (~September). This is the same as David's AP above under "iv" above
David: we should track what parts of specifications are implemented, e.g., on A1, E2 level
David: in f-2-f better to have one-on-one sessions between OSC/OSFG and each WG to focus on topics of interest by WGs.
2023-03-23: Jinri remembers that Alex C. wanted to involve Orange in cooperation between OSC and other organizations (ONAP, OAI, nephio). Julien to check on Orange side
AP (from 2023-03-23)Jinri HuangJulien Boudani : arrange a call on the external cooperation topic (ONAP, OAI, nephio, ...)
2023-04-20: Julien Boudani sent an email to the Sylva co-chair and invite them to give a presentation at TOC. They are in the KubeCon this week.
2023-04-27: Julien Boudani will invite Sylva to TOC to give a 30-minute presentation on 5/11 via email.
2023-03-30: not yet discussed. Julien mentioned some doubts on how nephio will fit it. David gave an example of nephio deployment philosophy.
2023-04-13:call made b/w Jinri and Julien. It is pointed out that Sylva may have many interesting area with OSC. Suggested to invite them to come ot OSC to deliver an introduction.
Seshu: also working in Sylvia, realizing the potential relationship b/w OSC and sylvia. would like to help;
Jinri: request the delegate to send the material beforehand for review, for better discussion;
(2023-04-13) AP: Julien Boudani to reach Sylva and invite them to OSC to give an introduction;
Seshu mentioned there will be an independent demo to showcase how the pieces (nephio, ONAP, OSC etc) could work together; It is suggested to do this in RSAC next week; The purpose is to showcase the ability of collaboration across dif. open source projects/communities. After the RSAC, the demo will be introduced in TOC next week.
It is request to broadcast the recording in the email reflector;
RSAC: next wed. 8AM, Rittwik to send the invite to Seshu;
2023-04-20:
David Kinsey : Seshu Kumar Mudiganti gave a presentation yesterday at the RSAC/SMO meeting. We did a lot of discussion on Nephio and other projects that's in the ecosystem around OSC. It ran out of time before we actually did the demo.It might occur at the next Wednesday's SMO/RSAC meeting.
Others
(2023-04-06) TSC this week cancelled; OSC report will be in 6 weeks;
2023-04-27: David Kinsey next O-RAN F2F is 6/29-6/23 in Osaka, Japan. We need to have more conversations with the WGs by having some joint sessions with them. Now the topics are beginning to merge onto different team pages and we can plan ahead with WGs to make sure we have a slot with them. It's about 7 weeks before the F2F and let's have a talk on this at the next RSAC.
Old business and Status of Open Actions
OSC Lab
Collaboration with OAI
2023-03-09: AP (from 2023-03-09) David KinseyOSC and OAI lab connection. The overall goal is to have some result of such a cooperation that can be presented at next O-RAN f-2-f.
James also interested in this. David seems to want the connection to be able to deploy from OSC SMO to OAI cloud. Also still discussion on OAI licensing and lab usage.
2023-04-20: David Kinsey no update. Talked to Rich on this and there shouldn't be any problem setting up the connection.
2023-04-27: David Kinsey heard that Tracy and others are thinking of using OTIC lab to use our released software to interconnect with OAI. Need to hear from OSFG on the final decision before moving forward.
5G Super Blueprint status - to be considered for H release.
2023-03-02: David KinseyTalked with OAI. First step is to connect labs so as to be able to connect elements in different locations. Idea is that this becomes a continuous test environment (CT).
2023-03-30: on hold
Standing Agenda Items (Brief Status of Ongoing Activities)
2023-03-30: to optimizie some of the daily-ran build jobs they will be moved to "on need basis" (cost optimization). See e-mail from Jessica.
2023-04-27: Sridhar Rao docker account has been created for OSC; Matthew Watkins filed a request for open source credits on behalf of the project but not sure when will hear back the results.
Requirements Software Architecture Committee (RSAC, link incl. meeting details)
2023-03-16:
Tacker (as DMS endpoint) and integration with O-Cloud. SMO project continues to develop it, but deployed in central cloud. See also O2DMS in ETSI NFV profile
Some flows for O2 interface now defined. Now need a contributor for implementing the SMO part of this. To be checked with Tacker team. Already checking with NTUST team if they have someone.
Rittwik: next RSAC call will be about AI/ML workflow and integration
2023-03-23: two presentations were given in RSAC call. One on SMO Decomposition and how that applies to OSC and one on interaction between OSC and ONAP (latter requires more discussion in RSAC). See RSAC meeting minutes link.
2023-03-30:
RSAC discussed lab environments. Still plan to keep OAI CU in Taiwan lab only.
ODU high contributions from Taiwan team.
2023-04-27: user-59b16 O-DU integration ongoing at the Taiwan lab. They're trying to get the basic O-DU integration complete by the end of this month. Also the O-Cloud deployment and connection to the O-CU endpoint.
Report out from PTL: Stand-Up & Report Out on Blockers
2023-02-23: James Li We have started some conversation around O2 integration.
2023-03-16: Worked on O2 integration. Working with Sridhar on Xtesting to bring existing Robot test cases.
2023-03-23: Working on CI/CD/CT integration with some Amdocs platform in some public cloud. RIC platform deployment and testing is used as test case for this proof of concept using AWS. David suggested this to be brought to RSAC (2 weeks from now). Also preferred OSC lab over public clouds like AWS. David also preferred O-Cloud and O2, though. James referred to Bing (infra team) as there seem to be some work with Powder lab on infrastructure team side as well.
2023-03-30: WR applying x testing to cases in it/test for testing of IMS interface.
2023-03-09: Happy to see new contributors: Cap gemini, Parallel wireless and Abhijit (rust CI),
2023-03-16: Supporting deployment of the RIC platform using O2 is currently pending a discussion between James and the SMO project and on Bin Yang to check a helm-only deployment of the near-RT RIC.
2023-03-30: Bin Yang: working on helm charts now. patch set coming soon. David and Bin Yang discussed on different ways of distributing the logic of combining parts into an overarching CNF/VNF.
(TBD) O-RAN Centralized Unit (OCU):
Ankit Barve O-RAN Distributed Unit High (ODUHIGH):
2023-03-16: gnb up in Taiwan lab and available for testing with G release.
2023-03-23: waiting for test tool availability in Taiwan lab
2023-04-27: focusing on inter-CU activity, and the TM 500 and L1 synchronization need to be checked first before we can resume.
2023-02-23: Jackie Huang We are considering to support ARM architecture. We can think about AMD as well. We have a discussion on the O2 compliance testing.
2023-03-09:started porting the INF upstream project to ARM, incl. a demo at MWC on ARM. David asked: is this planned to be in OSC repos. Jackie: yes
2023-04-27: resource shortage due to some role and responsibility change. Keep on working in the upstream StarlingX project but at the PoC level now. Also consider to support the cross compiling but it's more difficult for us. We have a long term plan with ARM and may implement the product level support of ARM architecture in the 2nd half of this year, and for OSC this may be integrated in the next release. Also contributed the O2 compliance test automation to the INT project. Asked whether there are any ARM servers in OSC. David Kinsey can talk about that on the RSAC agenda.
2023-04-27: David Kinsey got approval to purchase RU simulator and RIC test tools. The current plan is to deploy them into the Bedminster lab, cross connect some of the RIC test tools with the Cupertino lab, and possibly with the Taiwan lab too. Now it needs a memorandum of understanding between AT&T and O-RAN alliance for hosting their tools. Working on a draft document to go though AT&T legal and then have O-RAN alliance to agree.
2023-03-09: working on integration with non-RT RIC and Near-RT RIC. On track. David asked if work with near-RT RIC will be fed back to WG3? Any opinion? Avinash: sees this currently as an implementation issue. John (for non-RT RIC) still too early.
2023-04-27: Joseph Thaliath working on the integration with DME on the Non RT RIC side. Had an initial demo for that.
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
(2023-04-06) Jinri Huang, a proposal on OSC release planning and TOC meeting arrangement
Suggested Step 4: need internal discussion to identify which aspects of the features should be targeted. Otherwise, a feature may be too large in magnitude to be completed end 2 end;
Suggested Step 5: a readout could be arranged with communication back to working groups to tell them the features that OSC is working on;
feedback mechanism is suggested so that user communities voice could be heard and taken into account in the next phase design; it is agreed yet the detailed mechanism needs to be figured out in the future;
Some discussion points regarding Proposal 2
A comment with suggestion on the feature matrix was made. A feature matrix could be used to indicate the relationship/priority of different pieces of a feature, to indicate the progress (as dashboard). could be in wiki, git or other place.
concern was make that MVP-C features may be too vague to give actionable activities; MVP-C co-chairs need wo work with OSC to decompose the feature to actionable activities; this could be integrated into Step 3 (see the proposal) or Step 4 (see the comment above). Need to work with feature rapporteur.
TIM pointed out that for each feature, there are correspondingly a set of documents/specifications detailing the feature. These could be detailed input for OSC work.
Jinri Huang to integrate the comments and update the proposal (AP: 2023-04-06)
2023-04-20: Jinri Huang sent a proposal a few hours ago.
2023-04-27: Jinri Huang sent a updated new TOC meeting arrangement proposal. David Kinsey Next week will start with the new outline. RSAC, INT and INF will provide their reports.
(2023-04-13) TOC meeting arrangement discussion:
Jinri Huang : bring new business forward and have only 3-4 projects to present at each meeting with more details and also allow enough time for discussion. My second thought now is that we may even reduce to 2-3 projects to present at each TOC meeting so it may rotate in every 6 weeks.
Avinash Bhat this is a good solution and I support it. I remember there's a comment from David Kinsey to have a fourth group to do it a monthly base.
Jinri Huang : in the original proposal there were 3 groups. No matter how many groups we end up forming, the important thing is that we agree on this framework.
Seshu Kumar Mudiganti : Take a worst case of 10 minutes per project, 4 projects per group take up to 40 minutes; so perhaps we can have 3 projects per group to limit the project related discussion to 30 minutes and also allow time to cover other topics.
Jinri Huang : let me re-group it later on, perhaps with 4 groups
user-59b16: just think out loud here – instead of PTL level grouping, can there be one where it's more overall linkage across all projects? Some projects, like O-DU-low may not have much to speak about due to its low activity. Rather I'd like to have TOC present to all projects like a umbrella thing that go over high level picture so we all worked in the same level direction. The conversation should happen both ways, including the project groups, and TOC taking one slot to provide feedback for all to align better.
Jinri Huang I agree. Perhaps RSAC should be the one to present high level picture, but definitely TOC should be involved. In addition, we may need to figure out a way for PTLs to present their report not purely on a software development perspective, but also to cover the architecture, design, underlying intention, etc. We may not do it all correctly from the beginning but should give it a try.
AP: Jinri Huang to contact MVP-C co-chairs Suzy and Koo to schedule a time to give a high-level introduction on feature packages in TOC.
2023-04-20: Jinri Huang haven't contacted the MVP-C co-chairs yet, wanted to have the Sylva meeting scheduled first.
(2023-04-20)TOC meeting arrangement discussion:
Jinri Huang : sent an updated version in email a few hours ago. Per the proposal 1 of the release planning on slide 2, it's still rough but enough for us to take action. Proposed 4 groups. and projects in each group will present in one TOC meeting on progress and discussions.
David Kinsey there're outliers, like the documentation project only reports near the release time.
Alex Stancu it makes sense to have the SIM project together with NONRTRIC and OAM
David Kinsey : suggest to have the infrastructure team to move to group 1 from group 4. In addition, no PTLs are associated with the Keysight/Viavi simulators, and the Radisys commercial CU that we are using in the labs.
user-59b16 : integration team might provide that overview? Essentially it's pulling together external dependencies, things that are down streaming from etc. Also do you want LF or release management to say a few words?
David Kinsey INF, INT and RSAC are close together in one group
Jinri Huang : These 3 may take too much time in 1 TOC meeting. Also O-DU-low may not use much time
David Kinsey : There're 2 aspects on the integration: 1) the XTesting framework and automated testing across all projects; 2) integration around O-DU-high. Also we have 3 labs to report on their progress so it might be good to split up integration into 2 parts, with the 2nd parts on lab reports.
David Kinsey : we need a motion to approve this new format, on the groupings, and what to do if there's a 5th week in a month. Jinri Huang made a motion, and David Kinsey second it. Votes approved.
AP: Jinri Huang will finalize the grouping, and what to do on the 5th week.
Jackie Huang shared on how the O-RAN WG6 O2IMS interface v03.00 spec is aligned in the INF project in the G release.
Yogendra Pal do you have a way to let others find out details if something is partially compliant?
David Kinsey propose to have mandatory and optional fields to assist on the details.
Planning for Next Meeting
Any Other Business (AOB)
AP (from 2023-03-16) David Kinsey: SMO PTL position is open for a new PTL. Mahesh will have to move on by end of March. Candidates should send a short e-mail with their proposal including their qualifications.
AP: 2023-04-06: Sridhar to set up a voting for the SMO PTL election
2023-04-13: election finished and Seshu Kumar Mudiganti became the SMO PTL., AP closed.
2023-04-13:
MATT: currently going through the process of applying for open source credits. therefore, asking about whether the projects have any docker account; 2023-04-13 AP: suggest PTL to respond via email later;
2023-04-20: Sridhar Rao Joseph will replace Hoojoo Lee as PTL for the AI/ML project. David Kinsey let's confirm it on the next TOC meeting.
2023-04-27: Joseph is confirmed as the new AI/ML PTL (Motion made by David Kinsey second by Ganesh Shenbagaraman and without any objection) . Also Jackie Huang will replace Bin Yang as the voting TOC member, and Jon Zhang will serve as the alternate.
Meeting Summary (resolutions, new action items, etc.)
*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: Motion proposed by Jinri Huang , seconded by Julien Boudani , motion approved unanimously.
Review of Today's Agenda
suggested and agreed by the team to go through AP list first, then continue the discussion on the proposal from last week. if time allows, then review the stand items.
AP (from 2023-02-23)Jinri Huang : push O-RAN legal to get feedback and get statement from O-RAN legal on how to enforce the SCCP CLA.
Sridhar Rao I have checked with LF legal. SCCP is already created. LF will be hosting the repo, but it's not a legal entity for SCCP and SCCL (similar to SCP and SCL). It's O-RAN legal.
2023-03-23: David mentioned, for example, scans to be done by O-RAN.
Jinri to check what this was about and if it is already resolved. David suggested that under this AP we also need knowledge on process for the checks that
Jinri Huang To discuss SCCL implementation, a meeting with O-RAN office and some experts is arranged for next week (=last week of February).
2023-03-30: no update
2023-04-06: AP update: mail sent to O-RAN office requesting the SCCL CLA enforcement, waiting for the feedback;
23-04-13: response back from O-RAN Office. Details to be discussed later.
AP (from 2023-03-16)Jakub Novy: Check on progress that Jindrich is making. We continue working on a way to publish O-RAN code-like segments.
Jakub had a session with Jindrich on what is needed. Next step is with Jindrich. Jakub also had a discussion with WG3's Claudio.
Jakub commented that we once this becomes clear, we should talk with other WG. WG3 needs are pretty clear.
2023-04-20: no update but Jakub Novy will keep on monitoring.
2023-03-23, 2023-03-30: no update, O-RAN office is looking for suitable solution. Jakub waiting for Jindrich.
2023-04-13: no update. Still waiting for Office to feed back.
2023-04-20: Jinri Huang explained to the O-RAN office. Had conversations with Sridhar, and seems like the SCCL CLA was not that complicated. Recommend to close the AP and re-open it in case there's any issue in the future.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG discussions
2023-03-09,2023-03-16, 2023-03-30: no news.
O-RAN next phase
2023-02-09: James Li presented OSC revamp. A deep-dive session is scheduled during the F2F.
2023-02-23: James Li Next step is how we are going to execute. First thing is the impact OSC wants to make and the second is CI/CD/CT.
2023-03-02: Jinri: better mapping between OSC work and O-RAN working groups needed. Wish for OSC taking input from O-RAN working groups.
2023-03-09: AP (from 2023-03-09)David Kinsey to discuss with Jinri on what can be done to get this (=better cooperation) forward - goal should be refined and then we can come up with a plan. James commented that an e-mail to TOC (not "discuss") mailing list could help to refine this.
2023-03-30
James: TSC co-chairs requested updated on "O-RAN next phase". Jinri preparing something for next week TSC
OSFG/OSC and OAI workshop planned for second half of this year (~September). This is the same as David's AP above under "iv" above
2023-04-20: Tracy Van Brakle is working on a update to TSC this week. Hopefully we'll get some update next week on the Super Wireless RAN blueprint next week.
2023-03-16:
David: we should track what parts of specifications are implemented, e.g., on A1, E2 level
David: in f-2-f better to have one-on-one sessions between OSC/OSFG and each WG to focus on topics of interest by WGs.
2023-03-23: Jinri remembers that Alex C. wanted to involve Orange in cooperation between OSC and other organizations (ONAP, OAI, nephio). Julien to check on Orange side
AP (from 2023-03-23)Jinri HuangJulien Boudani : arrange a call on the external cooperation topic (ONAP, OAI, nephio, ...)
2023-04-20: Julien Boudani sent an email to the Sylva co-chair and invite them to give a presentation at TOC. They are in the KubeCon this week.
2023-03-30: not yet discussed. Julien mentioned some doubts on how nephio will fit it. David gave an example of nephio deployment philosophy.
2023-04-13:call made b/w Jinri and Julien. It is pointed out that Sylva may have many interesting area with OSC. Suggested to invite them to come ot OSC to deliver an introduction.
Seshu: also working in Sylvia, realizing the potential relationship b/w OSC and sylvia. would like to help;
Jinri: request the delegate to send the material beforehand for review, for better discussion;
(2023-04-13) AP: Julien Boudani to reach Sylva and invite them to OSC to give an introduction;
Seshu mentioned there will be an independent demo to showcase how the pieces (nephio, ONAP, OSC etc) could work together; It is suggested to do this in RSAC next week; The purpose is to showcase the ability of collaboration across dif. open source projects/communities. After the RSAC, the demo will be introduced in TOC next week.
It is request to broadcast the recording in the email reflector;
RSAC: next wed. 8AM, Rittwik to send the invite to Seshu;
2023-04-20:
David Kinsey : Seshu Kumar Mudiganti gave a presentation yesterday at the RSAC/SMO meeting. We did a lot of discussion on Nephio and other projects that's in the ecosystem around OSC. It ran out of time before we actually did the demo.It might occur at the next Wednesday's SMO/RSAC meeting.
Others
(2023-04-06) TSC this week cancelled; OSC report will be in 6 weeks;
Old business and Status of Open Actions
OSC Lab
Collaboration with OAI
2023-03-09: AP (from 2023-03-09) David KinseyOSC and OAI lab connection. The overall goal is to have some result of such a cooperation that can be presented at next O-RAN f-2-f.
James also interested in this. David seems to want the connection to be able to deploy from OSC SMO to OAI cloud. Also still discussion on OAI licensing and lab usage.
2023-04-20: David Kinsey no update. Talked to Rich on this and there shouldn't be any problem setting up the connection.
5G Super Blueprint status - to be considered for H release.
2023-03-02: David KinseyTalked with OAI. First step is to connect labs so as to be able to connect elements in different locations. Idea is that this becomes a continuous test environment (CT).
2023-03-30: on hold
Standing Agenda Items (Brief Status of Ongoing Activities)
2023-03-30: to optimizie some of the daily-ran build jobs they will be moved to "on need basis" (cost optimization). See e-mail from Jessica.
Requirements Software Architecture Committee (RSAC, link incl. meeting details)
2023-03-16:
Tacker (as DMS endpoint) and integration with O-Cloud. SMO project continues to develop it, but deployed in central cloud. See also O2DMS in ETSI NFV profile
Some flows for O2 interface now defined. Now need a contributor for implementing the SMO part of this. To be checked with Tacker team. Already checking with NTUST team if they have someone.
Rittwik: next RSAC call will be about AI/ML workflow and integration
2023-03-23: two presentations were given in RSAC call. One on SMO Decomposition and how that applies to OSC and one on interaction between OSC and ONAP (latter requires more discussion in RSAC). See RSAC meeting minutes link.
2023-03-30:
RSAC discussed lab environments. Still plan to keep OAI CU in Taiwan lab only.
ODU high contributions from Taiwan team.
Report out from PTL: Stand-Up & Report Out on Blockers
2023-02-23: James Li We have started some conversation around O2 integration.
2023-03-16: Worked on O2 integration. Working with Sridhar on Xtesting to bring existing Robot test cases.
2023-03-23: Working on CI/CD/CT integration with some Amdocs platform in some public cloud. RIC platform deployment and testing is used as test case for this proof of concept using AWS. David suggested this to be brought to RSAC (2 weeks from now). Also preferred OSC lab over public clouds like AWS. David also preferred O-Cloud and O2, though. James referred to Bing (infra team) as there seem to be some work with Powder lab on infrastructure team side as well.
2023-03-30: WR applying x testing to cases in it/test for testing of IMS interface.
2023-03-09: Happy to see new contributors: Cap gemini, Parallel wireless and Abhijit (rust CI),
2023-03-16: Supporting deployment of the RIC platform using O2 is currently pending a discussion between James and the SMO project and on Bin Yang to check a helm-only deployment of the near-RT RIC.
2023-03-30: Bin Yang: working on helm charts now. patch set coming soon. David and Bin Yang discussed on different ways of distributing the logic of combining parts into an overarching CNF/VNF.
(TBD) O-RAN Centralized Unit (OCU):
Ankit Barve O-RAN Distributed Unit High (ODUHIGH):
2023-03-16: gnb up in Taiwan lab and available for testing with G release.
2023-03-23: waiting for test tool availability in Taiwan lab
2023-02-23: Jackie Huang We are considering to support ARM architecture. We can think about AMD as well. We have a discussion on the O2 compliance testing.
2023-03-09:started porting the INF upstream project to ARM, incl. a demo at MWC on ARM. David asked: is this planned to be in OSC repos. Jackie: yes
2023-03-09: working on integration with non-RT RIC and Near-RT RIC. On track. David asked if work with near-RT RIC will be fed back to WG3? Any opinion? Avinash: sees this currently as an implementation issue. John (for non-RT RIC) still too early.
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
(2023-04-06) Jinri Huang, a proposal on OSC release planning and TOC meeting arrangement
Suggested Step 4: need internal discussion to identify which aspects of the features should be targeted. Otherwise, a feature may be too large in magnitude to be completed end 2 end;
Suggested Step 5: a readout could be arranged with communication back to working groups to tell them the features that OSC is working on;
feedback mechanism is suggested so that user communities voice could be heard and taken into account in the next phase design; it is agreed yet the detailed mechanism needs to be figured out in the future;
Some discussion points regarding Proposal 2
A comment with suggestion on the feature matrix was made. A feature matrix could be used to indicate the relationship/priority of different pieces of a feature, to indicate the progress (as dashboard). could be in wiki, git or other place.
concern was make that MVP-C features may be too vague to give actionable activities; MVP-C co-chairs need wo work with OSC to decompose the feature to actionable activities; this could be integrated into Step 3 (see the proposal) or Step 4 (see the comment above). Need to work with feature rapporteur.
TIM pointed out that for each feature, there are correspondingly a set of documents/specifications detailing the feature. These could be detailed input for OSC work.
Jinri Huang to integrate the comments and update the proposal (AP: 2023-04-06)
2023-04-20: Jinri Huang sent a proposal a few hours ago.
(2023-04-13) TOC meeting arrangement discussion:
Jinri Huang : bring new business forward and have only 3-4 projects to present at each meeting with more details and also allow enough time for discussion. My second thought now is that we may even reduce to 2-3 projects to present at each TOC meeting so it may rotate in every 6 weeks.
Avinash Bhat this is a good solution and I support it. I remember there's a comment from David Kinsey to have a fourth group to do it a monthly base.
Jinri Huang : in the original proposal there were 3 groups. No matter how many groups we end up forming, the important thing is that we agree on this framework.
Seshu Kumar Mudiganti : Take a worst case of 10 minutes per project, 4 projects per group take up to 40 minutes; so perhaps we can have 3 projects per group to limit the project related discussion to 30 minutes and also allow time to cover other topics.
Jinri Huang : let me re-group it later on, perhaps with 4 groups
user-59b16: just think out loud here – instead of PTL level grouping, can there be one where it's more overall linkage across all projects? Some projects, like O-DU-low may not have much to speak about due to its low activity. Rather I'd like to have TOC present to all projects like a umbrella thing that go over high level picture so we all worked in the same level direction. The conversation should happen both ways, including the project groups, and TOC taking one slot to provide feedback for all to align better.
Jinri Huang I agree. Perhaps RSAC should be the one to present high level picture, but definitely TOC should be involved. In addition, we may need to figure out a way for PTLs to present their report not purely on a software development perspective, but also to cover the architecture, design, underlying intention, etc. We may not do it all correctly from the beginning but should give it a try.
AP: Jinri Huang to contact MVP-C co-chairs Suzy and Koo to schedule a time to give a high-level introduction on feature packages in TOC.
2023-04-20: Jinri Huang haven't contacted the MVP-C co-chairs yet, wanted to have the Sylva meeting scheduled first.
(2023-04-20)TOC meeting arrangement discussion:
Jinri Huang : sent an updated version in email a few hours ago. Per the proposal 1 of the release planning on slide 2, it's still rough but enough for us to take action. Proposed 4 groups. and projects in each group will present in one TOC meeting on progress and discussions.
David Kinsey there're outliers, like the documentation project only reports near the release time.
Alex Stancu it makes sense to have the SIM project together with NONRTRIC and OAM
David Kinsey : suggest to have the infrastructure team to move to group 1 from group 4. In addition, no PTLs are associated with the Keysight/Viavi simulators, and the Radisys commercial CU that we are using in the labs.
user-59b16 : integration team might provide that overview? Essentially it's pulling together external dependencies, things that are down streaming from etc. Also do you want LF or release management to say a few words?
David Kinsey INF, INT and RSAC are close together in one group
Jinri Huang : These 3 may take too much time in 1 TOC meeting. Also O-DU-low may not use much time
David Kinsey : There're 2 aspects on the integration: 1) the XTesting framework and automated testing across all projects; 2) integration around O-DU-high. Also we have 3 labs to report on their progress so it might be good to split up integration into 2 parts, with the 2nd parts on lab reports.
David Kinsey : we need a motion to approve this new format, on the groupings, and what to do if there's a 5th week in a month. Jinri Huang made a motion, and David Kinsey second it. Votes approved.
AP: Jinri Huang will finalize the grouping, and what to do on the 5th week.
Jackie Huang shared on how the O-RAN WG6 O2IMS interface v03.00 spec is aligned in the INF project in the G release.
Yogendra Pal do you have a way to let others find out details if something is partially compliant?
David Kinsey propose to have mandatory and optional fields to assist on the details.
Planning for Next Meeting
Any Other Business (AOB)
AP (from 2023-03-16) David Kinsey: SMO PTL position is open for a new PTL. Mahesh will have to move on by end of March. Candidates should send a short e-mail with their proposal including their qualifications.
AP: 2023-04-06: Sridhar to set up a voting for the SMO PTL election
2023-04-13: election finished and Seshu Kumar Mudiganti became the SMO PTL., AP closed.
2023-04-13:
MATT: currently going through the process of applying for open source credits. therefore, asking about whether the projects have any docker account; 2023-04-13 AP: suggest PTL to respond via email 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: Motion proposed by Jinri Huang , seconded by Julien Boudani , motion approved unanimously.
Review of Today's Agenda
suggested and agreed by the team to go through AP list first, then continue the discussion on the proposal from last week. if time allows, then review the stand items.
AP (from 2023-02-23)Jinri Huang : push O-RAN legal to get feedback and get statement from O-RAN legal on how to enforce the SCCP CLA.
Sridhar Rao I have checked with LF legal. SCCP is already created. LF will be hosting the repo, but it's not a legal entity for SCCP and SCCL (similar to SCP and SCL). It's O-RAN legal.
2023-03-23: David mentioned, for example, scans to be done by O-RAN.
Jinri to check what this was about and if it is already resolved. David suggested that under this AP we also need knowledge on process for the checks that
Jinri Huang To discuss SCCL implementation, a meeting with O-RAN office and some experts is arranged for next week (=last week of February).
2023-03-30: no update
2023-04-06: AP update: mail sent to O-RAN office requesting the SCCL CLA enforcement, waiting for the feedback;
23-04-13: response back from O-RAN Office. Details to be discussed later.
AP (from 2023-03-16)Jakub Novy: Check on progress that Jindrich is making. We continue working on a way to publish O-RAN code-like segments.
Jakub had a session with Jindrich on what is needed. Next step is with Jindrich. Jakub also had a discussion with WG3's Claudio.
Jakub commented that we once this becomes clear, we should talk with other WG. WG3 needs are pretty clear.
2023-03-23, 2023-03-30: no update, O-RAN office is looking for suitable solution. Jakub waiting for Jindrich.
2023-04-13: no update. Still waiting for Office to feed back.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG discussions
2023-03-09,2023-03-16, 2023-03-30: no news.
O-RAN next phase
2023-02-09: James Li presented OSC revamp. A deep-dive session is scheduled during the F2F.
2023-02-23: James Li Next step is how we are going to execute. First thing is the impact OSC wants to make and the second is CI/CD/CT.
2023-03-02: Jinri: better mapping between OSC work and O-RAN working groups needed. Wish for OSC taking input from O-RAN working groups.
2023-03-09: AP (from 2023-03-09)David Kinsey to discuss with Jinri on what can be done to get this (=better cooperation) forward - goal should be refined and then we can come up with a plan. James commented that an e-mail to TOC (not "discuss") mailing list could help to refine this.
2023-03-30
James: TSC co-chairs requested updated on "O-RAN next phase". Jinri preparing something for next week TSC
OSFG/OSC and OAI workshop planned for second half of this year (~September). This is the same as David's AP above under "iv" above
2023-03-16:
David: we should track what parts of specifications are implemented, e.g., on A1, E2 level
David: in f-2-f better to have one-on-one sessions between OSC/OSFG and each WG to focus on topics of interest by WGs.
2023-03-23: Jinri remembers that Alex C. wanted to involve Orange in cooperation between OSC and other organizations (ONAP, OAI, nephio). Julien to check on Orange side
AP (from 2023-03-23)Jinri HuangJulien Boudani : arrange a call on the external cooperation topic (ONAP, OAI, nephio, ...)
2023-03-30: not yet discussed. Julien mentioned some doubts on how nephio will fit it. David gave an example of nephio deployment philosophy.
2023-04-13:call made b/w Jinri and Julien. It is pointed out that Sylva may have many interesting area with OSC. Suggested to invite them to come ot OSC to deliver an introduction.
Seshu: also working in Sylvia, realizing the potential relationship b/w OSC and sylvia. would like to help;
Jinri: request the delegate to send the material beforehand for review, for better discussion;
(2023-04-13) AP: Julien Boudani to reach Sylva and invite them to OSC to give an introduction;
Seshu mentioned there will be an independent demo to showcase how the pieces (nephio, ONAP, OSC etc) could work together; It is suggested to do this in RSAC next week; The purpose is to showcase the ability of collaboration across dif. open source projects/communities. After the RSAC, the demo will be introduced in TOC next week.
It is request to broadcast the recording in the email reflector;
RSAC: next wed. 8AM, Rittwik to send the invite to Seshu;
Others
(2023-04-06) TSC this week cancelled; OSC report will be in 6 weeks;
Old business and Status of Open Actions
OSC Lab
Collaboration with OAI
2023-03-09: AP (from 2023-03-09) David KinseyOSC and OAI lab connection. The overall goal is to have some result of such a cooperation that can be presented at next O-RAN f-2-f.
James also interested in this. David seems to want the connection to be able to deploy from OSC SMO to OAI cloud. Also still discussion on OAI licensing and lab usage.
5G Super Blueprint status - to be considered for H release.
2023-03-02: David KinseyTalked with OAI. First step is to connect labs so as to be able to connect elements in different locations. Idea is that this becomes a continuous test environment (CT).
2023-03-30: on hold
Standing Agenda Items (Brief Status of Ongoing Activities)
2023-03-30: to optimizie some of the daily-ran build jobs they will be moved to "on need basis" (cost optimization). See e-mail from Jessica.
Requirements Software Architecture Committee (RSAC, link incl. meeting details)
2023-03-16:
Tacker (as DMS endpoint) and integration with O-Cloud. SMO project continues to develop it, but deployed in central cloud. See also O2DMS in ETSI NFV profile
Some flows for O2 interface now defined. Now need a contributor for implementing the SMO part of this. To be checked with Tacker team. Already checking with NTUST team if they have someone.
Rittwik: next RSAC call will be about AI/ML workflow and integration
2023-03-23: two presentations were given in RSAC call. One on SMO Decomposition and how that applies to OSC and one on interaction between OSC and ONAP (latter requires more discussion in RSAC). See RSAC meeting minutes link.
2023-03-30:
RSAC discussed lab environments. Still plan to keep OAI CU in Taiwan lab only.
ODU high contributions from Taiwan team.
Report out from PTL: Stand-Up & Report Out on Blockers
2023-02-23: James Li We have started some conversation around O2 integration.
2023-03-16: Worked on O2 integration. Working with Sridhar on Xtesting to bring existing Robot test cases.
2023-03-23: Working on CI/CD/CT integration with some Amdocs platform in some public cloud. RIC platform deployment and testing is used as test case for this proof of concept using AWS. David suggested this to be brought to RSAC (2 weeks from now). Also preferred OSC lab over public clouds like AWS. David also preferred O-Cloud and O2, though. James referred to Bing (infra team) as there seem to be some work with Powder lab on infrastructure team side as well.
2023-03-30: WR applying x testing to cases in it/test for testing of IMS interface.
2023-03-09: Happy to see new contributors: Cap gemini, Parallel wireless and Abhijit (rust CI),
2023-03-16: Supporting deployment of the RIC platform using O2 is currently pending a discussion between James and the SMO project and on Bin Yang to check a helm-only deployment of the near-RT RIC.
2023-03-30: Bin Yang: working on helm charts now. patch set coming soon. David and Bin Yang discussed on different ways of distributing the logic of combining parts into an overarching CNF/VNF.
(TBD) O-RAN Centralized Unit (OCU):
Ankit Barve O-RAN Distributed Unit High (ODUHIGH):
2023-03-16: gnb up in Taiwan lab and available for testing with G release.
2023-03-23: waiting for test tool availability in Taiwan lab
2023-02-23: Jackie Huang We are considering to support ARM architecture. We can think about AMD as well. We have a discussion on the O2 compliance testing.
2023-03-09:started porting the INF upstream project to ARM, incl. a demo at MWC on ARM. David asked: is this planned to be in OSC repos. Jackie: yes
2023-03-09: working on integration with non-RT RIC and Near-RT RIC. On track. David asked if work with near-RT RIC will be fed back to WG3? Any opinion? Avinash: sees this currently as an implementation issue. John (for non-RT RIC) still too early.
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
(2023-04-06) Jinri Huang, a proposal on OSC release planning and TOC meeting arrangement
Suggested Step 4: need internal discussion to identify which aspects of the features should be targeted. Otherwise, a feature may be too large in magnitude to be completed end 2 end;
Suggested Step 5: a readout could be arranged with communication back to working groups to tell them the features that OSC is working on;
feedback mechanism is suggested so that user communities voice could be heard and taken into account in the next phase design; it is agreed yet the detailed mechanism needs to be figured out in the future;
Some discussion points regarding Proposal 2
A comment with suggestion on the feature matrix was made. A feature matrix could be used to indicate the relationship/priority of different pieces of a feature, to indicate the progress (as dashboard). could be in wiki, git or other place.
concern was make that MVP-C features may be too vague to give actionable activities; MVP-C co-chairs need wo work with OSC to decompose the feature to actionable activities; this could be integrated into Step 3 (see the proposal) or Step 4 (see the comment above). Need to work with feature rapporteur.
TIM pointed out that for each feature, there are correspondingly a set of documents/specifications detailing the feature. These could be detailed input for OSC work.
Jinri Huang to integrate the comments and update the proposal (AP: 2023-04-06)
(2023-04-13) TOC meeting arrangement discussion:
Jinri Huang : bring new business forward and have only 3-4 projects to present at each meeting with more details and also allow enough time for discussion. My second thought now is that we may even reduce to 2-3 projects to present at each TOC meeting so it may rotate in every 6 weeks.
Avinash Bhat this is a good solution and I support it. I remember there's a comment from David Kinsey to have a fourth group to do it a monthly base.
Jinri Huang : in the original proposal there were 3 groups. No matter how many groups we end up forming, the important thing is that we agree on this framework.
Seshu Kumar Mudiganti : Take a worst case of 10 minutes per project, 4 projects per group take up to 40 minutes; so perhaps we can have 3 projects per group to limit the project related discussion to 30 minutes and also allow time to cover other topics.
Jinri Huang : let me re-group it later on, perhaps with 4 groups
user-59b16: just think out loud here – instead of PTL level grouping, can there be one where it's more overall linkage across all projects? Some projects, like O-DU-low may not have much to speak about due to its low activity. Rather I'd like to have TOC present to all projects like a umbrella thing that go over high level picture so we all worked in the same level direction. The conversation should happen both ways, including the project groups, and TOC taking one slot to provide feedback for all to align better.
Jinri Huang I agree. Perhaps RSAC should be the one to present high level picture, but definitely TOC should be involved. In addition, we may need to figure out a way for PTLs to present their report not purely on a software development perspective, but also to cover the architecture, design, underlying intention, etc. We may not do it all correctly from the beginning but should give it a try.
AP: Jinri Huang to contact MVP-C co-chairs Suzy and Koo to schedule a time to give a high-level introduction on feature packages in TOC.
Planning for Next Meeting
Any Other Business (AOB)
AP (from 2023-03-16) David Kinsey: SMO PTL position is open for a new PTL. Mahesh will have to move on by end of March. Candidates should send a short e-mail with their proposal including their qualifications.
AP: 2023-04-06: Sridhar to set up a voting for the SMO PTL election
2023-04-13: election finished and Seshu Kumar Mudiganti became the SMO PTL., AP closed.
2023-04-13:
MATT: currently going through the process of applying for open source credits. therefore, asking about whether the projects have any docker account; 2023-04-13 AP: suggest PTL to respond via email later;
Meeting Summary (resolutions, new action items, etc.)
AP (from 2023-02-23)Jinri Huang : push O-RAN legal to get feedback and get statement from O-RAN legal on how to enforce the SCCP CLA.
Sridhar Rao I have checked with LF legal. SCCP is already created. LF will be hosting the repo, but it's not a legal entity for SCCP and SCCL (similar to SCP and SCL). It's O-RAN legal.
2023-03-23: David mentioned, for example, scans to be done by O-RAN.
Jinri to check what this was about and if it is already resolved. David suggested that under this AP we also need knowledge on process for the checks that
Jinri Huang To discuss SCCL implementation, a meeting with O-RAN office and some experts is arranged for next week (=last week of February).
2023-03-30: no update
2023-04-06: AP update: mail sent to O-RAN office requesting the SCCL CLA enforcement, waiting for the feedback;
AP (from 2023-03-16)Jakub Novy: Check on progress that Jindrich is making. We continue working on a way to publish O-RAN code-like segments.
Jakub had a session with Jindrich on what is needed. Next step is with Jindrich. Jakub also had a discussion with WG3's Claudio.
Jakub commented that we once this becomes clear, we should talk with other WG. WG3 needs are pretty clear.
2023-03-23, 2023-03-30: no update, O-RAN office is looking for suitable solution. Jakub waiting for Jindrich.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
OSFG discussions
2023-03-09,2023-03-16, 2023-03-30: no news.
O-RAN next phase
2023-02-09: James Li presented OSC revamp. A deep-dive session is scheduled during the F2F.
2023-02-23: James Li Next step is how we are going to execute. First thing is the impact OSC wants to make and the second is CI/CD/CT.
2023-03-02: Jinri: better mapping between OSC work and O-RAN working groups needed. Wish for OSC taking input from O-RAN working groups.
2023-03-09: AP (from 2023-03-09)David Kinsey to discuss with Jinri on what can be done to get this (=better cooperation) forward - goal should be refined and then we can come up with a plan. James commented that an e-mail to TOC (not "discuss") mailing list could help to refine this.
2023-03-30
James: TSC co-chairs requested updated on "O-RAN next phase". Jinri preparing something for next week TSC
OSFG/OSC and OAI workshop planned for second half of this year (~September). This is the same as David's AP above under "iv" above
2023-03-16:
David: we should track what parts of specifications are implemented, e.g., on A1, E2 level
David: in f-2-f better to have one-on-one sessions between OSC/OSFG and each WG to focus on topics of interest by WGs.
2023-03-23: Jinri remembers that Alex C. wanted to involve Orange in cooperation between OSC and other organizations (ONAP, OAI, nephio). Julien to check on Orange side
AP (from 2023-03-23)Jinri HuangJulien Boudani : arrange a call on the external cooperation topic (ONAP, OAI, nephio, ...)
2023-03-30: not yet discussed. Julien mentioned some doubts on how nephio will fit it. David gave an example of nephio deployment philosophy.
(2023-04-06) TSC this week cancelled; OSC report will be in 6 weeks;
Old business and Status of Open Actions
OSC Lab
Collaboration with OAI
2023-03-09: AP (from 2023-03-09) David KinseyOSC and OAI lab connection. The overall goal is to have some result of such a cooperation that can be presented at next O-RAN f-2-f.
James also interested in this. David seems to want the connection to be able to deploy from OSC SMO to OAI cloud. Also still discussion on OAI licensing and lab usage.
5G Super Blueprint status - to be considered for H release.
2023-03-02: David KinseyTalked with OAI. First step is to connect labs so as to be able to connect elements in different locations. Idea is that this becomes a continuous test environment (CT).
2023-03-30: on hold
Standing Agenda Items (Brief Status of Ongoing Activities)
2023-03-30: to optimizie some of the daily-ran build jobs they will be moved to "on need basis" (cost optimization). See e-mail from Jessica.
Requirements Software Architecture Committee (RSAC, link incl. meeting details)
2023-03-16:
Tacker (as DMS endpoint) and integration with O-Cloud. SMO project continues to develop it, but deployed in central cloud. See also O2DMS in ETSI NFV profile
Some flows for O2 interface now defined. Now need a contributor for implementing the SMO part of this. To be checked with Tacker team. Already checking with NTUST team if they have someone.
Rittwik: next RSAC call will be about AI/ML workflow and integration
2023-03-23: two presentations were given in RSAC call. One on SMO Decomposition and how that applies to OSC and one on interaction between OSC and ONAP (latter requires more discussion in RSAC). See RSAC meeting minutes link.
2023-03-30:
RSAC discussed lab environments. Still plan to keep OAI CU in Taiwan lab only.
ODU high contributions from Taiwan team.
Report out from PTL: Stand-Up & Report Out on Blockers
2023-02-23: James Li We have started some conversation around O2 integration.
2023-03-16: Worked on O2 integration. Working with Sridhar on Xtesting to bring existing Robot test cases.
2023-03-23: Working on CI/CD/CT integration with some Amdocs platform in some public cloud. RIC platform deployment and testing is used as test case for this proof of concept using AWS. David suggested this to be brought to RSAC (2 weeks from now). Also preferred OSC lab over public clouds like AWS. David also preferred O-Cloud and O2, though. James referred to Bing (infra team) as there seem to be some work with Powder lab on infrastructure team side as well.
2023-03-30: WR applying x testing to cases in it/test for testing of IMS interface.
2023-03-09: Happy to see new contributors: Cap gemini, Parallel wireless and Abhijit (rust CI),
2023-03-16: Supporting deployment of the RIC platform using O2 is currently pending a discussion between James and the SMO project and on Bin Yang to check a helm-only deployment of the near-RT RIC.
2023-03-30: Bin Yang: working on helm charts now. patch set coming soon. David and Bin Yang discussed on different ways of distributing the logic of combining parts into an overarching CNF/VNF.
(TBD) O-RAN Centralized Unit (OCU):
Ankit Barve O-RAN Distributed Unit High (ODUHIGH):
2023-03-16: gnb up in Taiwan lab and available for testing with G release.
2023-03-23: waiting for test tool availability in Taiwan lab
2023-02-23: Jackie Huang We are considering to support ARM architecture. We can think about AMD as well. We have a discussion on the O2 compliance testing.
2023-03-09:started porting the INF upstream project to ARM, incl. a demo at MWC on ARM. David asked: is this planned to be in OSC repos. Jackie: yes
2023-03-09: working on integration with non-RT RIC and Near-RT RIC. On track. David asked if work with near-RT RIC will be fed back to WG3? Any opinion? Avinash: sees this currently as an implementation issue. John (for non-RT RIC) still too early.
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
(2023-04-06) Jinri Huang, a proposal on OSC release planning and TOC meeting arrangement
Suggested Step 4: need internal discussion to identify which aspects of the features should be targeted. Otherwise, a feature may be too large in magnitude to be completed end 2 end;
Suggested Step 5: a readout could be arranged with communication back to working groups to tell them the features that OSC is working on;
feedback mechanism is suggested so that user communities voice could be heard and taken into account in the next phase design; it is agreed yet the detailed mechanism needs to be figured out in the future;
Some discussion points regarding Proposal 2
A comment with suggestion on the feature matrix was made. A feature matrix could be used to indicate the relationship/priority of different pieces of a feature, to indicate the progress (as dashboard). could be in wiki, git or other place.
concern was make that MVP-C features may be too vague to give actionable activities; MVP-C co-chairs need wo work with OSC to decompose the feature to actionable activities; this could be integrated into Step 3 (see the proposal) or Step 4 (see the comment above). Need to work with feature rapporteur.
TIM pointed out that for each feature, there are correspondingly a set of documents/specifications detailing the feature. These could be detailed input for OSC work.
Jinri Huang to integrate the comments and update the proposal (AP: 2023-04-06)
Planning for Next Meeting
Any Other Business (AOB)
AP (from 2023-03-16) David Kinsey: SMO PTL position is open for a new PTL. Mahesh will have to move on by end of March. Candidates should send a short e-mail with their proposal including their qualifications.