Technical Charter for O-RAN Software Community

2022 06 30

Recording: 

Meeting Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: Jun 30, 2022 08:59 AM

Meeting Recording:

Agenda

1. Call for Scribe (minutes owner): Ganesh Shenbagaraman

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting (16 Jun 2022) approval: proposed by Ganesh Shenbagaraman and seconded by John Paul. The motion is approved
   2. Decision: Minutes for TOC meeting (23 Jun 2022) approval:  proposed by Ganesh Shenbagaraman and seconded by John Paul. The motion is approved
   3. Scribe from next week will be JinGuk/Avinash (Samsung)
2. Review of Today's Agenda.
   1. F release
   2. Presentation from Aarna Networks

3. Release Votes and Approval

   1. F release motion (except KPIMON-GO): James Li proposed motion and seconded by Jinri. The motion is approved

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

      2. 2022-05-12: summary of the open issues
         1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
         2. Updating CLA for SCCL to align to the charter.  This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
         3. Extend OSC SCCL. Open
      3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
      4. 2022-05-26: no news
      5. 2022-06-09: James Li: Request from SDFG co-chair to OSC PTLs to bring up any copyright requests to 3GPP/ETSI. Jack clarified on the past discussions pointing to the issue in referencing from code implementation to these source specification documents. This is still not a resolved issue. Jinri added comments to clarify that the SDFG request is more towards the list of historical requests to 3GPP. Jack and Jinri will check the past requests. PTLs are requested to forward any past request to Jinri. John Keeney pointed to challenges in determining when to make a copyright request. Jack said in view of all these challenges, the legal team is working on a broad approval for use in open source software.
      6. 2022-06-23: Jack: Copyright request is still ongoing, in next few months some progress is expected
5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
      4. 2022-05-19: if people have topics to raise to the F2F, they are invited to share with Jinri and the group by email
      5. 2022-05-26; Jinri: dates are set to June 13th-17^th. David: proposal to hold OSC session on Monday 13^th , time slot#2. One hour should be sufficient for status and workplan presentation  
      6. 2022-06-02: David: As first slot of O-RAN vf2f is on June 13, all PTLs to provide slides to David for F release update and G release plan
      7. 2022-06-09: David: Copied F release update from the F release status page update. But for G release tentative plan most of the projects do not have any update.
         Luis will be updating F release status page
         All PTLs to update tentative G release plan to be presented on 13th June in f2f meeting
      8. 2022-06-16: Jack: Thanks David and other members part of f2f participation (13th June)
         John Keeney: Raised a question about mechanism for getting feedback for f2f presentation
         David: MVP and TIFG are two ways to get feedbacks but as TIFG is more focus on testing hence with MVP there is a better chance to get feedback.
         Jack: Suggested to figure out ways to get feedback from real users of software
         
      9. 2022-06-23: RSAC committee to track MVP items and have a tracker table 
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
      4. 2022-05-19 Information about the Spring Plug Fest shared by Tracy 
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
      3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before thediscussion at the meeting. 
      4. 2022-05-26 Jinri: item still open for contibutions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
      5. 2022-06-02: John Keeney: Raised a question regarding status of the survey
         Jinri: EC could not take it up due to other urgent business, but some people are in process of initial analysis.
6. Old business and Status of Open Actions
   1. "F" Release:
      1. 2022-05-18: Timeplan review 
         1. Release is planned by end of June. Large scale software changes should be completed  by the end of this week, in order to have time to test and release
         2. Integration and testing page for F release in https://wiki.o-ran-sc.org/display/IAT/F+Release+Integration+and+Testing
      2. 2022-05-19: Jack: by end of june we will also have to prepare the usual Press Release. It is expected that PTLs would have to update their project content and status in the release table (within 1 week). This will be used as baseline for the press release
      3. 2022-05-26: at the next meeting we will go through the status of the individual projects so as to start the code scan in the following days
      4. 2022-06-02: Jack: Tracking F release status page update
         Near-Real-time RIC: To be updated
         Near-Real-time RAN Intelligent Controller Platform: To be updated
         Non-Real time RIC: Updated
         OAM: To be updated
         OCU: To be updated
         ODU-HIGH: To be updated
         ODU-Low: To be updated
         SIM: To be updated
         INF: To be updated
         INT: James and Sridhar: To continue exploring tools and solution for cross platform test framework for integration and testing
         DOC: All project individually documents for each release but to have a consolidated documentation is an open topic
         SMO: To be updated
         All PTLs should update F release status in the release table to start code and license scan in following days
      5. 2022-06-09: Sridhar: To coordinate software scan activity for all projects to have a report next week
         Jack: Branching for F release on 20th June 2022 followed by package and documentation release on 30th June 2022
      6. 2022-06-16: Sridhar: Scanning is ongoing and report expected to be released next week
         Jack: PTLs to quickly respond to any issues reported in scanning as it may delay “F” release plan
      7. 2022-06-23: Sridhar: License scan completed for all except com projects (com/golog, com/log, com/pylog) and expected to complete this week. There is no issue to be reported
         Mahesh: For SMO there are 4 repo two are ready for branch and remaining are being discussed with Sridhar regarding permission issue
         Luis: L1 binary for F release is expected at the end of the week. To update F release page as well the for O-DU-LOW part by next week
         Jack: Branching for all projects to be done by 30th June before TOC
         Thoralf: Docker image links are to be placed in F Release Integration and Testing
         Xiaohua: Jinri asked PTLs to share all F release highlight points for upcoming press release
      8. 2022-06-30: Sridhar: License scanning is completed and approved with LF
         Branching status for all projects:
         Near-Real-time RIC: KPI MON-GO not branched. Jack: to be pushed in maintenance F release
         Near-Real-time RAN Intelligent Controller Platform: Done
         Non-Real time RIC: Done
         OAM: Done
         OCU: NA
         ODU-HIGH: Done
         ODU-Low: Done
         SIM: Done
         INF: Done
         INT: NA
         DOC: NA
         SMO: Done
         
         Mahesh: Document page not getting updated for the SMO project
         James: To check for this issue
         Jinri: Reminder to all PTLs to share F release highlights for press release
   2. OSC Lab
      1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
      2. 2022-06-02: PTP clock sync issue update
         Ankit: Checked scripts for synchronization of the clock but ptp sync still failing to get in sync with grandmaster and internal clock only used by ODU.
         David: We have checked Hardware and configuration. Server 190 is being connected to the home gateway and configured as expected. Clock sync between grandmaster and fronthaul gateway has been verified. Issue needs to be debugged further
      3. 2022-06-09: Luis: to discuss with Rich and to have a remote debug session for clock sync issue.
      4. 2022-06-016: Issue still remains, Jack to have a check what next step could be to resolve this issue
   3. 5G Super Blueprint status - to be considered for G release.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
         5. 2022-05-12:  workshop likely to be on Wednesday May 18th.  James Liwill check and confirm
         6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
         7. 2022-06-16:David: AI ML repo integration discussed in the RSAC and recommendation is to go ahead with AI ML as an independent project
            Jack: Assessment of capabilities, target plan to be discussed for AI ML project
            Avinash: A detailed plan to be presented
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
         4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack:  priority should be given to those exploiting and validating OSC software capability
         5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
         6. 2022-06-02 Action point : Jack to update G release timeline calendar for review and voting
            Jack: G release planning status
            David: We are running behind for G release planning, it could not be done in the last RSAC due to limited participants
         7. 2022-06-09: Jack: Raised a question regarding O-DU-LOW new functionality under G release?
            Luis: Incremental improvements and optimization expected in G release but as of now no new feature expected on ORAN Fronthaul interface
            Jack: All PTLs to update and provide tentative G release plan to Jinri for the presentation on 13th June in f2f meeting
         8. 2022-06-16: Jack: G release page to be linked in Release section and subsequent sections to be added
            David: To schedule each project planning (in RSAC) in first three weeks of G release
            Jack: Activity to plan in G release: Deployment of all modules with health check
            Rittwik: Raised a query to have a specific use case for Taiwan lab
            Jack: Both labs repeating same use case independently helps in removing local dependency and better documentation for end user to use and replicate the system
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. James Li Integration and Testing (INT)
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. Demo on SMO VES collector setup provided by Mahesh Jethanandani . Recording available here 

      3. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. SUNIL SINGH RIC Applications (RICAPP)

      5. Thoralf Czichy RIC Platform (RIC) 

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      8. Luis Farias O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

      11. Jackie Huang Infrastructure (INF)

      12. weichen ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
   2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
   3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
   4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

10. Planning for Next Meeting
    1. Aarna networks presentation planned for next week

11. Any Other Business (AOB)

12. Meeting Summary (resolutions, new action items, etc.)

2022 06 23

Recording: 

Meeting Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: Jun 23, 2022 08:59 AM

Meeting Recording:
https://zoom.us/rec/share/jShc9akz9A0rLqU_NRp6BpfjAuIIJ0jCpUqEM9lXPCJP1JxsLcTtNLOWP3cOEKx3.5D2yj6aWWUz7uzu7

Agenda

1. Call for Scribe (minutes owner): Ganesh Shenbagaraman

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting (16 Jun 2022) approval: To be approved in next meeting as recording was not available.
2. Review of Today's Agenda.
   1. Today`s focus will be on preparing for F release, license scan, branching and documentation
   2. Sridhar/Matt: Gerrit and Jenkins Update Time slot booking announcement and request for any conflict?
      No issue raised in the TOC call

3. Release Votes and Approval

   1. F Release

   2. Approval of new Near-RT RIC and xApp repo requests : ric-plt/xapp-frame-rust ric-app/hw-rust (link=https://lists.o-ran-sc.org/g/toc/message/715)
      Thoralf Czichy proposed motion to create new repos and seconded by Xiaoha/Jinri . The motion has been approved

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

      2. 2022-05-12: summary of the open issues
         1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
         2. Updating CLA for SCCL to align to the charter.  This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
         3. Extend OSC SCCL. Open
      3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
      4. 2022-05-26: no news
      5. 2022-06-09: James Li: Request from SDFG co-chair to OSC PTLs to bring up any copyright requests to 3GPP/ETSI. Jack clarified on the past discussions pointing to the issue in referencing from code implementation to these source specification documents. This is still not a resolved issue. Jinri added comments to clarify that the SDFG request is more towards the list of historical requests to 3GPP. Jack and Jinri will check the past requests. PTLs are requested to forward any past request to Jinri. John Keeney pointed to challenges in determining when to make a copyright request. Jack said in view of all these challenges, the legal team is working on a broad approval for use in open source software.
      6. 2022-06-23: Jack: Copyright request is still ongoing, in next few months some progress is expected
5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
      4. 2022-05-19: if people have topics to raise to the F2F, they are invited to share with Jinri and the group by email
      5. 2022-05-26; Jinri: dates are set to June 13th-17^th. David: proposal to hold OSC session on Monday 13^th , time slot#2. One hour should be sufficient for status and workplan presentation  
      6. 2022-06-02: David: As first slot of O-RAN vf2f is on June 13, all PTLs to provide slides to David for F release update and G release plan
      7. 2022-06-09: David: Copied F release update from the F release status page update. But for G release tentative plan most of the projects do not have any update.
         Luis will be updating F release status page
         All PTLs to update tentative G release plan to be presented on 13th June in f2f meeting
      8. 2022-06-16: Jack: Thanks David and other members part of f2f participation (13th June)
         John Keeney: Raised a question about mechanism for getting feedback for f2f presentation
         David: MVP and TIFG are two ways to get feedbacks but as TIFG is more focus on testing hence with MVP there is a better chance to get feedback.
         Jack: Suggested to figure out ways to get feedback from real users of software
         
      9. 2022-06-23: RSAC committee to track MVP items and have a tracker table 
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
      4. 2022-05-19 Information about the Spring Plug Fest shared by Tracy 
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
      3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before thediscussion at the meeting. 
      4. 2022-05-26 Jinri: item still open for contibutions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
      5. 2022-06-02: John Keeney: Raised a question regarding status of the survey
         Jinri: EC could not take it up due to other urgent business, but some people are in process of initial analysis.
6. Old business and Status of Open Actions
   1. "F" Release:
      1. 2022-05-18: Timeplan review 
         1. Release is planned by end of June. Large scale software changes should be completed  by the end of this week, in order to have time to test and release
         2. Integration and testing page for F release in https://wiki.o-ran-sc.org/display/IAT/F+Release+Integration+and+Testing
      2. 2022-05-19: Jack: by end of june we will also have to prepare the usual Press Release. It is expected that PTLs would have to update their project content and status in the release table (within 1 week). This will be used as baseline for the press release
      3. 2022-05-26: at the next meeting we will go through the status of the individual projects so as to start the code scan in the following days
      4. 2022-06-02: Jack: Tracking F release status page update
         Near-Real-time RIC: To be updated
         Near-Real-time RAN Intelligent Controller Platform: To be updated
         Non-Real time RIC: Updated
         OAM: To be updated
         OCU: To be updated
         ODU-HIGH: To be updated
         ODU-Low: To be updated
         SIM: To be updated
         INF: To be updated
         INT: James and Sridhar: To continue exploring tools and solution for cross platform test framework for integration and testing
         DOC: All project individually documents for each release but to have a consolidated documentation is an open topic
         SMO: To be updated
         All PTLs should update F release status in the release table to start code and license scan in following days
      5. 2022-06-09: Sridhar: To coordinate software scan activity for all projects to have a report next week
         Jack: Branching for F release on 20th June 2022 followed by package and documentation release on 30th June 2022
      6. 2022-06-16: Sridhar: Scanning is ongoing and report expected to be released next week
         Jack: PTLs to quickly respond to any issues reported in scanning as it may delay “F” release plan
      7. 2022-06-23: Sridhar: License scan completed for all except com projects (com/golog, com/log, com/pylog) and expected to complete this week. There is no issue to be reported
         Mahesh: For SMO there are 4 repo two are ready for branch and remaining are being discussed with Sridhar regarding permission issue
         Luis: L1 binary for F release is expected at the end of the week. To update F release page as well the for O-DU-LOW part by next week
         Jack: Branching for all projects to be done by 30th June before TOC
         Thoralf: Docker image links are to be placed in F Release Integration and Testing
         Xiaohua: Jinri asked PTLs to share all F release highlight points for upcoming press release
   2. OSC Lab
      1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
      2. 2022-06-02: PTP clock sync issue update
         Ankit: Checked scripts for synchronization of the clock but ptp sync still failing to get in sync with grandmaster and internal clock only used by ODU.
         David: We have checked Hardware and configuration. Server 190 is being connected to the home gateway and configured as expected. Clock sync between grandmaster and fronthaul gateway has been verified. Issue needs to be debugged further
      3. 2022-06-09: Luis: to discuss with Rich and to have a remote debug session for clock sync issue.
      4. 2022-06-16: Issue still remains, Jack to have a check what next step could be to resolve this issue
   3. 5G Super Blueprint status - to be considered for G release.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
         5. 2022-05-12:  workshop likely to be on Wednesday May 18th.  James Liwill check and confirm
         6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
         7. 2022-06-16:David: AI ML repo integration discussed in the RSAC and recommendation is to go ahead with AI ML as an independent project
            Jack: Assessment of capabilities, target plan to be discussed for AI ML project
            Avinash: A detailed plan to be presented
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
         4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack:  priority should be given to those exploiting and validating OSC software capability
         5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
         6. 2022-06-02 Action point : Jack to update G release timeline calendar for review and voting
            Jack: G release planning status
            David: We are running behind for G release planning, it could not be done in the last RSAC due to limited participants
         7. 2022-06-09: Jack: Raised a question regarding O-DU-LOW new functionality under G release?
            Luis: Incremental improvements and optimization expected in G release but as of now no new feature expected on ORAN Fronthaul interface
            Jack: All PTLs to update and provide tentative G release plan to Jinri for the presentation on 13th June in f2f meeting
         8. 2022-06-16: Jack: G release page to be linked in Release section and subsequent sections to be added
            David: To schedule each project planning (in RSAC) in first three weeks of G release
            Jack: Activity to plan in G release: Deployment of all modules with health check
            Rittwik: Raised a query to have a specific use case for Taiwan lab
            Jack: Both labs repeating same use case independently helps in removing local dependency and better documentation for end user to use and replicate the system
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. James Li Integration and Testing (INT)
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. Demo on SMO VES collector setup provided by Mahesh Jethanandani . Recording available here 

      3. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. SUNIL SINGH RIC Applications (RICAPP)

      5. Thoralf Czichy RIC Platform (RIC) 

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      8. Luis Farias O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

      11. Jackie Huang Infrastructure (INF)

      12. weichen ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
   2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
   3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
   4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

10. Planning for Next Meeting
    1. Aarna networks presentation planned for next week

11. Any Other Business (AOB)

    1. Keysight (John Faulkner, Paolo Marini) give a presentation on Keysight test systems capability. Material will be distributed over the TOC reflector.
    2. Ganesh Shenbagaraman (Radisys ) to nominate new PTL name for the O-RAN Distributed Unit High (ODUHIGH) project
    3. David: How to plan integration of new AI ML project with other projects such as OAM, SMO & non-RTRIC. To create a subproject or a separate repo as new project?
       Avinash: Propose to have a discussion on different options to integrate in upcoming RSAC or TOC meeting.
       All relevant project PTLs need to discuss and finalize integration approach (upcoming RSAC meeting could be used for this discussion)
    4. Jinri: Concern from MVP-C co-chair Suzy about lack of representation from OSC in MVP package progress with Rittwik not playing that role anymore. Rittwik and Jack clarified that this can be tracked within O-RAN and SMO PTL. This discussion will be continued.
    5. Discussion on 16-Jun-22: Brandon Wick (Aarna networks) talked about Aarna's contribution to SMO project in OSC and brought up the topic of press release from O-RAN OSC. Jack explained the process followed for PR after each release.
    6. Jack: All active ORAN sites to be updated, and unused sites (oran github) to be archived if required

12. Meeting Summary (resolutions, new action items, etc.)

2022 06 16

Recording: 

Meeting Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: Jun 16, 2022 08:58 AM

Meeting Recording:
https://zoom.us/rec/share/o6fStEfS-k68eNbDXs9yHmCJPK2-DjZwMp_gTajnBuUFo0_ujPHw_ZdjgnAvoxWJ.e5vn1flJ-caQyQ0e

Agenda

1. Call for Scribe (minutes owner): Ganesh Shenbagaraman

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting (02 Jun 2022) approval: proposed by  Ganesh Shenbagaraman and seconded by John Paul. The motion is approved.
   2. Minutes of TOC meeting (09 Jun 2022) approval: proposed by  Ganesh Shenbagaraman and seconded by John Paul. The motion is approved.
2. Review of Today's Agenda.
   1. Today`s focus will be on preparing for F release, license scan, branching and documentation

3. Release Votes and Approval

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

      2. 2022-05-12: summary of the open issues
         1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
         2. Updating CLA for SCCL to align to the charter.  This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
         3. Extend OSC SCCL. Open
      3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
      4. 2022-05-26: no news
      5. 2022-06-09: James Li: Request from SDFG co-chair to OSC PTLs to bring up any copyright requests to 3GPP/ETSI. Jack clarified on the past discussions pointing to the issue in referencing from code implementation to these source specification documents. This is still not a resolved issue. Jinri added comments to clarify that the SDFG request is more towards the list of historical requests to 3GPP. Jack and Jinri will check the past requests. PTLs are requested to forward any past request to Jinri. John Keeney pointed to challenges in determining when to make a copyright request. Jack said in view of all these challenges, the legal team is working on a broad approval for use in open source software.
5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
      4. 2022-05-19: if people have topics to raise to the F2F, they are invited to share with Jinri and the group by email
      5. 2022-05-26; Jinri: dates are set to June 13th-17^th. David: proposal to hold OSC session on Monday 13^th , time slot#2. One hour should be sufficient for status and workplan presentation  
      6. 2022-06-02: David: As first slot of O-RAN vf2f is on June 13, all PTLs to provide slides to David for F release update and G release plan
      7. 2022-06-09: David: Copied F release update from the F release status page update. But for G release tentative plan most of the projects do not have any update.
         Luis will be updating F release status page
         All PTLs to update tentative G release plan to be presented on 13th June in f2f meeting
      8. 2022-06-16: Jack: Thanks David and other members part of f2f participation (13th June)
         John Keeney: Raised a question about mechanism for getting feedback for f2f presentation
         David: MVP and TIFG are two ways to get feedbacks but as TIFG is more focus on testing hence with MVP there is a better chance to get feedback.
         Jack: Suggested to figure out ways to get feedback from real users of software
         
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
      4. 2022-05-19 Information about the Spring Plug Fest shared by Tracy 
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
      3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before thediscussion at the meeting. 
      4. 2022-05-26 Jinri: item still open for contibutions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
      5. 2022-06-02: John Keeney: Raised a question regarding status of the survey
         Jinri: EC could not take it up due to other urgent business, but some people are in process of initial analysis.
6. Old business and Status of Open Actions
   1. "F" Release:
      1. 2022-05-18: Timeplan review 
         1. Release is planned by end of June. Large scale software changes should be completed  by the end of this week, in order to have time to test and release
         2. Integration and testing page for F release in https://wiki.o-ran-sc.org/display/IAT/F+Release+Integration+and+Testing
      2. 2022-05-19: Jack: by end of june we will also have to prepare the usual Press Release. It is expected that PTLs would have to update their project content and status in the release table (within 1 week). This will be used as baseline for the press release
      3. 2022-05-26: at the next meeting we will go through the status of the individual projects so as to start the code scan in the following days
      4. 2022-06-02: Jack: Tracking F release status page update
         Near-Real-time RIC: To be updated
         Near-Real-time RAN Intelligent Controller Platform: To be updated
         Non-Real time RIC: Updated
         OAM: To be updated
         OCU: To be updated
         ODU-HIGH: To be updated
         ODU-Low: To be updated
         SIM: To be updated
         INF: To be updated
         INT: James and Sridhar: To continue exploring tools and solution for cross platform test framework for integration and testing
         DOC: All project individually documents for each release but to have a consolidated documentation is an open topic
         SMO: To be updated
         All PTLs should update F release status in the release table to start code and license scan in following days
      5. 2022-06-09: Sridhar: To coordinate software scan activity for all projects to have a report next week
         Jack: Branching for F release on 20th June 2022 followed by package and documentation release on 30th June 2022
      6. 2022-06-16: Sridhar: Scanning is ongoing and report expected to be released next week
         Jack: PTLs to quickly respond to any issues reported in scanning as it may delay “F” release plan
   2. OSC Lab
      1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
      2. 2022-06-02: PTP clock sync issue update
         Ankit: Checked scripts for synchronization of the clock but ptp sync still failing to get in sync with grandmaster and internal clock only used by ODU.
         David: We have checked Hardware and configuration. Server 190 is being connected to the home gateway and configured as expected. Clock sync between grandmaster and fronthaul gateway has been verified. Issue needs to be debugged further
      3. 2022-06-09: Luis: to discuss with Rich and to have a remote debug session for clock sync issue.
      4. 2022-06-016: Issue still remains, Jack to have a check what next step could be to resolve this issue
   3. 5G Super Blueprint status - to be considered for G release.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
         5. 2022-05-12:  workshop likely to be on Wednesday May 18th.  James Liwill check and confirm
         6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
         7. 2022-06-16:David: AI ML repo integration discussed in the RSAC and recommendation is to go ahead with AI ML as an independent project
            Jack: Assessment of capabilities, target plan to be discussed for AI ML project
            Avinash: A detailed plan to be presented
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
         4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack:  priority should be given to those exploiting and validating OSC software capability
         5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
         6. 2022-06-02 Action point : Jack to update G release timeline calendar for review and voting
            Jack: G release planning status
            David: We are running behind for G release planning, it could not be done in the last RSAC due to limited participants
         7. 2022-06-09: Jack: Raised a question regarding O-DU-LOW new functionality under G release?
            Luis: Incremental improvements and optimization expected in G release but as of now no new feature expected on ORAN Fronthaul interface
            Jack: All PTLs to update and provide tentative G release plan to Jinri for the presentation on 13th June in f2f meeting
         8. 2022-06-16: Jack: G release page to be linked in Release section and subsequent sections to be added
            David: To schedule each project planning (in RSAC) in first three weeks of G release
            Jack: Activity to plan in G release: Deployment of all modules with health check
            Rittwik: Raised a querry to have a specific use case for Taiwan lab
            JacK: Both labs repeating same use case independently helps in removing local dependency and better documentation for end user to use and replicate the system
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. James Li Integration and Testing (INT)
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. Demo on SMO VES collector setup provided by Mahesh Jethanandani . Recording available here 

      3. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. SUNIL SINGH RIC Applications (RICAPP)

      5. Thoralf Czichy RIC Platform (RIC) 

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      8. Luis Farias O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

      11. Jackie Huang Infrastructure (INF)

      12. weichen ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
   2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
   3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
   4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

10. Planning for Next Meeting

11. Any Other Business (AOB)

    1. Keysight (John Faulkner, Paolo Marini) give a presentation on Keysight test systems capability. Material will be distributed over the TOC reflector.
    2. Ganesh Shenbagaraman (Radisys ) to nominate new PTL name for the O-RAN Distributed Unit High (ODUHIGH) project
    3. David: How to plan integration of new AI ML project with other projects such as OAM, SMO & non-RTRIC. To create a subproject or a separate repo as new project?
       Avinash: Propose to have a discussion on different options to integrate in upcoming RSAC or TOC meeting.
       All relevant project PTLs need to discuss and finalize integration approach (upcoming RSAC meeting could be used for this discussion)
    4. Jinri: Concern from MVP-C co-chair Suzy about lack of representation from OSC in MVP package progress with Rittwik not playing that role anymore. Rittwik and Jack clarified that this can be tracked within O-RAN and SMO PTL. This discussion will be continued.
    5. Discussion on 16-Jun-22: Brandon Wick (Aarna networks) talked about Aarna's contribution to SMO project in OSC and brought up the topic of press release from O-RAN OSC. Jack explained the process followed for PR after each release.
    6. Jack: All active ORAN sites to be updated, and unused sites (oran github) to be archived if required

12. Meeting Summary (resolutions, new action items, etc.)

2022 06 09

Recording: 

Meeting Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: Jun 9, 2022 08:51 AM

Meeting Recording:
https://zoom.us/rec/share/AN47ffN2eACgbSIlAMA6Rck0hvtWTWdBQ4cqR07Es1W58lR6BXH_30gZ4LFXG4Fz.y8z6MaMUyzrxLvBR

Agenda

1. Call for Scribe (minutes owner): Ganesh Shenbagaraman

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: Minutes for TOC meeting approval: To be approved in next meeting as recording could not be accessed.
2. Review of Today's Agenda
   1. Today`s focus will be on preparing for F release, license scan, branching and documentation
   2. James Li: Aarna Network expressed interest to present details of their open-source SMO to ORAN community
      Jack: Session (20-25 mins slot) to be scheduled tentatively on 30th June post F release.
      James: To inform Aarna networks about the meeting

3. Release Votes and Approval

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

      2. 2022-05-12: summary of the open issues
         1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
         2. Updating CLA for SCCL to align to the charter.  This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
         3. Extend OSC SCCL. Open
      3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
      4. 2022-05-26: no news
      5. 2022-06-09: James Li: Request from SDFG co-chair to OSC PTLs to bring up any copyright requests to 3GPP/ETSI. Jack clarified on the past discussions pointing to the issue in referencing from code implementation to these source specification documents. This is still not a resolved issue. Jinri added comments to clarify that te SDFG request is more towards the list of historical requests to 3GPP. Jack and Jinri will check the past requests. PTLs are requested to forward any past request to Jinri. JOhn Keeney pointed to challenges in determining when to make a copyright request. Jack said in view of all these challenges, the legal team is working on a broad approval for use in open source software.
5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
      4. 2022-05-19: if people have topics to raise to the F2F, they are invited to share with Jinri and the group by email
      5. 2022-05-26; Jinri: dates are set to June 13th-17^th. David: proposal to hold OSC session on Monday 13^th , time slot#2. One hour should be sufficient for status and workplan presentation
      6. 2022-06-02: David: As first slot of O-RAN vf2f is on June 13, all PTLs to provide slides to David for F release update and G release plan
      7. 2022-06-09: David: Copied F release update from the F release status page update. But for G release tentative plan most of the projects do not have any update.
         Luis will be updating F release status page
         All PTLs to update tentative G release plan to be presented on 13th June in f2f meeting  
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
      4. 2022-05-19 Information about the Spring Plug Fest shared by Tracy 
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
      3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before thediscussion at the meeting. 
      4. 2022-05-26 Jinri: item still open for contibutions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
      5. 2022-06-02: John Keeney: Raised a question regarding status of the survey
         Jinri: EC could not take it up due to other urgent business, but some people are in process of initial analysis.
6. Old business and Status of Open Actions
   1. "F" Release:
      1. 2022-05-18: Timeplan review 
         1. Release is planned by end of June. Large scale software changes should be completed  by the end of this week, in order to have time to test and release
         2. Integration and testing page for F release in https://wiki.o-ran-sc.org/display/IAT/F+Release+Integration+and+Testing
      2. 2022-05-19: Jack: by end of june we will also have to prepare the usual Press Release. It is expected that PTLs would have to update their project content and status in the release table (within 1 week). This will be used as baseline for the press release
      3. 2022-05-26: at the next meeting we will go through the status of the individual projects so as to start the code scan in the following days
      4. 2022-06-02: Jack: Tracking F release status page update 
         Near-Real-time RIC: To be updated
         Near-Real-time RAN Intelligent Controller Platform: To be updated
         Non-Real time RIC: Updated
         OAM: To be updated
         OCU: To be updated
         ODU-HIGH: To be updated
         ODU-Low: To be updated
         SIM: To be updated
         INF: To be updated
         INT: James and Sridhar: To continue exploring tools and solution for cross platform test framework for integration and testing
         DOC: All project individually documents for each release but to have a consolidated documentation is an open topic
         SMO: To be updated
         All PTLs should update F release status in the release table to start code and license scan in following days
      5. 2022-06-09: Sridhar: To coordinate software scan activity for all projects to have a report next week
         Jack: Branching for F release on 20th June 2022 followed by package and documentation release on 30th June 2022
         
   2. OSC Lab
      1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
      2. 2022-06-02: PTP clock sync issue update
         Ankit: Checked scripts for synchronization of the clock but ptp sync still failing to get in sync with grandmaster and internal clock only used by ODU.
         David: We have checked Hardware and configuration. Server 190 is being connected to the home gateway and configured as expected. Clock sync between grandmaster and fronthaul gateway has been verified. Issue needs to be debugged further
      3. 2022-06-09: Luis: to discuss with Rich and to have a remote debug session for clock sync issue.
   3. 5G Super Blueprint status - to be considered for G release.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
         5. 2022-05-12:  workshop likely to be on Wednesday May 18th.  James Liwill check and confirm
         6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
         4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack:  priority should be given to those exploiting and validating OSC software capability
         5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
         6. 2022-06-02 Action point : Jack to update G release timeline calendar for review and voting
            Jack: G release planning status
            David: We are running behind for G release planning, it could not be done in the last RSAC due to limited participants
         7. 2022-06-09: Jack: Raised a question regarding O-DU-LOW new functionality under G release?
            Luis: Incremental improvements and optimization expected in G release but as of now no new feature expected on ORAN Fronthaul interface
            Jack: All PTLs to update and provide tentative G release plan to Jinri for the presentation on 13th June in f2f meeting
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. James Li Integration and Testing (INT)
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. Demo on SMO VES collector setup provided by Mahesh Jethanandani . Recording available here 

      3. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. SUNIL SINGH RIC Applications (RICAPP)

      5. Thoralf Czichy RIC Platform (RIC) 

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      8. Luis Farias O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

      11. Jackie Huang Infrastructure (INF)

      12. weichen ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
   2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
   3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
   4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

10. Planning for Next Meeting

11. Any Other Business (AOB)

    1. Keysight (John Faulkner, Paolo Marini) give a presentation on Keysight test systems capability. Material will be distributed over the TOC reflector.
    2. Ganesh Shenbagaraman (Radisys ) to nominate new PTL name for the O-RAN Distributed Unit High (ODUHIGH) project
    3. David: How to plan integration of new AI ML project with other projects such as OAM, SMO & non-RTRIC. To create a subproject or a separate repo as new project?
       Avinash: Propose to have a discussion on different options to integrate in upcoming RSAC or TOC meeting.
       All relevant project PTLs need to discuss and finalize integration approach (upcoming RSAC meeting could be used for this discussion)
    4. Jinri: Concern from MVP-C co-chair Suzy about lack of representation from OSC in MVP package progress with Rittwik not playing that role anymore. Rittwik and Jack clarified that this can be tracked within O-RAN and SMO PTL. This discussion will be continued.

12. Meeting Summary (resolutions, new action items, etc.)

2022 06 02

Recording: 

Meeting Recording:

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: Jun 2, 2022 08:58 AM

Meeting Recording:
https://zoom.us/rec/share/1clxNoIE9fo91gkK9re9iGBIsAivJqGG8qsiht1CxeUP3Z8hySpTt9Vo6j7o9Wrn.PpB6GS_eVFc8t3I7

Agenda

1. Call for Scribe (minutes owner): Ganesh Shenbagaraman

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: proposed by Ganesh Shenbagaraman and seconded by Jinri Huang. The motion is approved.
2. Review of Today's Agenda
   1. Ultan Kelly: Prof Ray from Taiwan lab wants to arrange a visit to the OSC lab to recreate setup at Taiwan lab.
      Jack: Further discussion to be done offline and Jack will be contact point for the visit and logistic
      Ultan Kelly to provide contact details to Prof Ray
   2. Today’s focus will be on review of release planning

3. Release Votes and Approval

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

      2. 2022-05-12: summary of the open issues
         1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
         2. Updating CLA for SCCL to align to the charter.  This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
         3. Extend OSC SCCL. Open
      3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
      4. 2022-05-26: no news
5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
      4. 2022-05-19: if people have topics to raise to the F2F, they are invited to share with Jinri and the group by email
      5. 2022-05-26; Jinri: dates are set to June 13th-17^th. David: proposal to hold OSC session on Monday 13^th , time slot#2. One hour should be sufficient for status and workplan presentation  
      6. 2022-06-02: David: As first slot of O-RAN vf2f is on June 13, all PTLs to provide slides to David for F release update and G release plan
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
      4. 2022-05-19 Information about the Spring Plug Fest shared by Tracy 
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
      3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before thediscussion at the meeting. 
      4. 2022-05-26 Jinri: item still open for contibutions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
      5. 2022-06-02: John Keeney: Raised a question regarding status of the survey
         Jinri: EC could not take it up due to other urgent business, but some people are in process of initial analysis.
         
6. Old business and Status of Open Actions
   1. "F" Release:
      1. 2022-05-18: Timeplan review 
         1. Release is planned by end of June. Large scale software changes should be completed  by the end of this week, in order to have time to test and release
         2. Integration and testing page for F release in https://wiki.o-ran-sc.org/display/IAT/F+Release+Integration+and+Testing
      2. 2022-05-19: Jack: by end of june we will also have to prepare the usual Press Release. It is expected that PTLs would have to update their project content and status in the release table (within 1 week). This will be used as baseline for the press release
      3. 2022-05-26: at the next meeting we will go through the status of the individual projects so as to start the code scan in the following days
      4. 2022-06-02: Jack: Tracking F release status page update 
         Near-Real-time RIC: To be updated
         Near-Real-time RAN Intelligent Controller Platform: To be updated
         Non-Real time RIC: Updated
         OAM: To be updated
         OCU: To be updated
         ODU-HIGH: To be updated
         ODU-Low: To be updated
         SIM: To be updated
         INF: To be updated
         INT: James and Sridhar: To continue exploring tools and solution for cross platform test framework for integration and testing
         DOC: All project individually documents for each release but to have a consolidated documentation is an open topic
         SMO: To be updated
         All PTLs should update F release status in the release table to start code and license scan in following days
   2. OSC Lab
      1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
      2. 2022-06-02: PTP clock sync issue update
         Ankit: Checked scripts for synchronization of the clock but ptp sync still failing to get in sync with grandmaster and internal clock only used by ODU.
         David: We have checked Hardware and configuration. Server 190 is being connected to the home gateway and configured as expected. Clock sync between grandmaster and fronthaul gateway has been verified. Issue needs to be debugged further
         
   3. 5G Super Blueprint status - to be considered for G release.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
         5. 2022-05-12:  workshop likely to be on Wednesday May 18th.  James Liwill check and confirm
         6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
         4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack:  priority should be given to those exploiting and validating OSC software capability
         5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
         6. 2022-06-02 Action point : Jack to update G release timeline calendar for review and voting
            Jack: G release planning status
            David: We are running behind for G release planning, it could not be done in the last RSAC due to limited participants
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. James Li Integration and Testing (INT)
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. Demo on SMO VES collector setup provided by Mahesh Jethanandani . Recording available here 

      3. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. SUNIL SINGH RIC Applications (RICAPP)

      5. Thoralf Czichy RIC Platform (RIC) 

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      8. Luis Farias O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

      11. Jackie Huang Infrastructure (INF)

      12. weichen ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
   2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
   3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
   4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

10. Planning for Next Meeting

11. Any Other Business (AOB)

    1. Keysight (John Faulkner, Paolo Marini) give a presentation on Keysight test systems capability. Material will be distributed over the TOC reflector.
    2. Ganesh Shenbagaraman (Radisys ) to nominate new PTL name for the O-RAN Distributed Unit High (ODUHIGH) project

12. Meeting Summary (resolutions, new action items, etc.)

2022 05 26

Recording: 

Topic: Zoom3 O-RAN SC
Start Time: May  26, 2022 at 9am EDT

Meeting Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: May 26, 2022 08:58 AM

Meeting Recording:
https://zoom.us/rec/share/zHOileWAAdLLusX2heGU011ssoVuh13vfTZwpyhwQ93fu3lLLwTZiVL8p_osKAZk.pom--njiIWJKdDkX

Agenda

1. Call for Scribe (minutes owner): Andrea Buldorini (TIM)

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: proposed by Andrea and seconded by Jinri. The motion is approved.

   2. Scribe from next week will be Ganesh/Ankit (Radisys)

2. Review of Today's Agenda

3. Release Votes and Approval

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

      2. 2022-05-12: summary of the open issues
         1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
         2. Updating CLA for SCCL to align to the charter.  This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
         3. Extend OSC SCCL. Open
      3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
      4. 2022-05-26: no news
5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
      4. 2022-05-19: if people have topics to raise to the F2F, they are invited to share with Jinri and the group by email
      5. 2022-05-26; Jinri: dates are set to June 13th-17^th. David: proposal to hold OSC session on Monday 13^th , time slot#2. One hour should be sufficient for status and workplan presentation  
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
      4. 2022-05-19 Information about the Spring Plug Fest shared by Tracy 
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
      3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before thediscussion at the meeting. 
      4. 2022-05-26 Jinri: item still open for contibutions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
6. Old business and Status of Open Actions
   1. "F" Release:
      1. 2022-05-18: Timeplan review 
         1. Release is planned by end of June. Large scale software changes should be completed  by the end of this week, in order to have time to test and release
         2. Integration and testing page for F release in https://wiki.o-ran-sc.org/display/IAT/F+Release+Integration+and+Testing
      2. 2022-05-19: Jack: by end of june we will also have to prepare the usual Press Release. It is expected that PTLs would have to update their project content and status in the release table (within 1 week). This will be used as baseline for the press release
      3. 2022-05-26: at the next meeting we will go through the status of the individual projects so as to start the code scan in the following days
   2. OSC Lab
      1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
   3. 5G Super Blueprint status - to be considered for G release.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
         5. 2022-05-12:  workshop likely to be on Wednesday May 18th.  James Liwill check and confirm
         6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
         4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack:  priority should be given to those exploiting and validating OSC software capability
         5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. James Li Integration and Testing (INT)
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. Demo on SMO VES collector setup provided by Mahesh Jethanandani . Recording available here 

      3. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. SUNIL SINGH RIC Applications (RICAPP)

      5. Thoralf Czichy RIC Platform (RIC) 

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      8. Luis Farias O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

      11. Jackie Huang Infrastructure (INF)

      12. weichen ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
   2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
   3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
   4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

10. Planning for Next Meeting

11. Any Other Business (AOB)

    1. Keysight (John Faulkner, Paolo Marini) give a presentation on Keysight test systems capability. Material will be distributed over the TOC reflector.

12. Meeting Summary (resolutions, new action items, etc.)

2022 05 19

Recording: 

Topic: Zoom3 O-RAN SC
Start Time: May  19, 2022 at 9am EDT

Meeting Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: May 19, 2022 09:00 AM

Meeting Recording:
https://zoom.us/rec/share/X3iDN0a5vjss4WquxXhW70ezY5WCWVymAbRHahNN6dJTYBK5hgqZbGbaTtNQ-EBx.mvTas78WYQlUl-t_

Agenda

1. Call for Scribe (minutes owner): Andrea Buldorini (TIM)

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: proposed by Andrea and seconded by Jinri. The motion is approved.
2. Review of Today's Agenda

3. Release Votes and Approval

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

      2. 2022-05-12: summary of the open issues
         1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
         2. Updating CLA for SCCL to align to the charter.  This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
         3. Extend OSC SCCL. Open
      3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
      4. 2022-05-19: if people have topics to raise to the F2F, they are invited to share with Jinri and the group by email
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
      4. 2022-05-19 Information about the Spring Plug Fest shared by Tracy 
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
      3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before thediscussion at the meeting. 
6. Old business and Status of Open Actions
   1. "F" Release:
      1. 2022-05-18: Timeplan review 
         1. Release is planned by end of June. Large scale software changes should be completed  by the end of this week, in order to have time to test and release
         2. Integration and testing page for F release in https://wiki.o-ran-sc.org/display/IAT/F+Release+Integration+and+Testing
      2. 2022-05-19: Jack: by end of june we will also have to prepare the usual Press Release. It is expected that PTLs would have to update their project content and status in the release table (within 1 week). This will be used as baseline for the press release
   2. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
      1. Tag this activity for G release.
      2. 2022-04-06: no news
         
      3. 2022-05-12: no news
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
         5. 2022-05-12:  workshop likely to be on Wednesday May 18th.  James Liwill check and confirm
         6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
         4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack:  priority should be given to those exploiting and validating OSC software capability
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. James Li Integration and Testing (INT)
         1. 2022-05-19: Test automation status (see summary)

            1. James Li Team is lowering resources. One option is to support with funded resources. Ideally each project should have at least one test exploiting test automation process.

            2. Jack: this would probably be fully addressed in G release; Integration and Testing project will be crucial in Rel-G to demonstrate that OSC software platform is solid and enabling future development of more sophisticated use cases.  
      2. Mahesh Jethanandani Service Management and Orchestration (SMO) :: 2022-04-13: copyright blockers issue. 

      3. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. SUNIL SINGH RIC Applications (RICAPP)

      5. Thoralf Czichy RIC Platform (RIC) 

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      8. Luis Farias O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

      11. Jackie Huang Infrastructure (INF)

      12. weichen ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
   2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
   3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

10. Planning for Next Meeting

11. Any Other Business (AOB)

    1. Zoom login issue (Thoralf).
       1. Had to cancel RIC/RIC xApp project meeting due to problems with access to the verification code (extra verification step). We (as also other subprojects use https://zoom.us/j/9644759813 ).
       2. Verification code is sometimes requested. A distribution list was created and used as zoom account. If anybody else needs to use the bridge, ask Sridhar Raoto be added
    2. Repos Committers rights (see minutes of 2022-05-05). Mahesh had completed the process to be authorized as committer. If other PTLs would like to become committers, it is necessary to update the INFO file accordingly 

12. Meeting Summary (resolutions, new action items, etc.)

2022 05 12

Recording: 

Topic: Zoom3 O-RAN SC
Start Time: May  12, 2022 at 9am EDT

Meeting Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: May 12, 2022 08:54 AM

Meeting Recording:
https://zoom.us/rec/share/ivAtRpYxgnq8iR0ZVbOoUlj-JVgpHphuR6yW6siVm9M1OtKITZNEwCiAWNzW6xm1.VZ1UrD4vWyJDyBFi

Agenda

1. Call for Scribe (minutes owner): Andrea Buldorini (TIM)

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: proposed by Andrea and seconded by Thoralf. The motion is approved.
2. Review of Today's Agenda
   1. Thoralf would like the Zoom login issue to be addressed.
      1. Had to cancel yesterday's RIC/RIC xApp project meeting due to problems with access to the verification code (extra verification step). We (as also other subprojects use https://zoom.us/j/9644759813 ). Postponed to the next call
   2. Today focus will be on "F" Release status

3. Release Votes and Approval

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

      2. 2022-05-12: summary of the open issues
         1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
         2. Updating CLA for SCCL to align to the charter.  This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
         3. Extend OSC SCCL. Open
5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
6. Old business and Status of Open Actions
   1. "F" Release:
      1. 2022-05-18: Timeplan review 
         1. Release is planned by end of June. Large scale software changes should be completed  by the end of this week, in order to have time to test and release
         2. Integration and testing page for F release in https://wiki.o-ran-sc.org/display/IAT/F+Release+Integration+and+Testing
   2. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
      1. Tag this activity for G release.
      2. 2022-04-06: no news
         
      3. 2022-05-12: no news
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
         5. 2022-05-18:  workshop likely to be on Wednesday May 18th.  James Liwill check and confirm
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
         4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack:  priority should be given to those exploiting and validating OSC software capability
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. 2022-04-06: no news
      2. James Li Integration and Testing (INT)
      3. Mahesh Jethanandani Service Management and Orchestration (SMO) :: 2022-04-13: copyright blockers issue. 

      4. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      5. SUNIL SINGH RIC Applications (RICAPP)

      6. Thoralf Czichy RIC Platform (RIC) 

      7. (TBD) O-RAN Centralized Unit (OCU) 

      8. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      9. Luis Farias O-RAN Distributed Unit Low (ODULOW) 

      10. Martin Skorupski Operations and Maintenance (OAM)

      11. Alex Stancu Simulations (SIM)

      12. Jackie Huang Infrastructure (INF)

      13. weichen ni Documentation (DOC)

      14. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
   2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

10. Planning for Next Meeting

11. Any Other Business (AOB)

12. Meeting Summary (resolutions, new action items, etc.)

2022 05 05

Recording: 

Topic: Zoom3 O-RAN SC
Start Time: May  05, 2022 at 9am EDT

Meeting Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: May 5, 2022 09:00 AM

Meeting Recording:
https://zoom.us/rec/share/ieWP8jI_MCo5tr2q3mqXrI5jCuZ2_4gHUWAzLz6xh7FcRGaUwVbylZ4LUohILOmd.V2G_WllLKtNNCKb3

Agenda

1. Call for Scribe (minutes owner): Andrea Buldorini (TIM)

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: proposed by Arun and seconded by Andrea. The motion is approved.
2. Review of Today's Agenda

3. Release Votes and Approval

   1. Request by Mahesh to get committer’s rights as PTL to speed up procedures (on behalf of LF IT staff). (see https://lists.o-ran-sc.org/g/toc/message/685). It is proposed to request access rights for other OSC PTLs. Jack propose to coordinate among PTLs to adopt a common approach across all the projects if possible. Shridar Rao will also verify with LF IT group what would be the best approach. Mahesh and Shridar will get info from PTLs to make one request to LF.
      1. Motion to enable PTLs as committers by Mahesh; Jinri seconds. The motion is approved.
   2. Request by CommScope to reactivate the archived OAM/TR069-Adapter repo; LFN requires approval by TOC  
      1. Motion to reactivate TR069 by Martin; Jinri second; The motion is approved

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
      3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
   2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events. 
   3. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
   4. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
         5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
   5. Challenges for the OSC community (as report to EC)
      1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
      2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
6. Old business and Status of Open Actions
   1. "F" Release:
      1. Action Point: PTLs to add a line showing code coverage stats for F release.
      2. 2022-04-06: we checked the page F Release - not all subprojects have a heading or reference to this.
      3. 2022-04-13: page F Release still does not reflect the progress and required stats.
         1. Action Point : PTLs  from non-RT RIC (ok), O-DU (not ok), Simulators (ok), Infrastructure (ok), SMO (not ok):  to check and update the stats on the F Release respective pages
      4. 2022-04-20: Jackie (Windriver) asked how to create "F" release in JIRA for his project. Answer: Try this link and if it does not work, contact Sridhar Rao (srao@linuxfoundation.org).
   2. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
      1. Tag this activity for G release.
      2. 2022-04-06: no news
         
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.  
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. 2022-04-06: no news
      2. James Li Integration and Testing (INT)
      3. Mahesh Jethanandani Service Management and Orchestration (SMO) :: 2022-04-13: copyright blockers issue. 

      4. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      5. SUNIL SINGH RIC Applications (RICAPP)

      6. Thoralf Czichy RIC Platform (RIC) 

      7. (TBD) O-RAN Centralized Unit (OCU) 

      8. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      9. Luis Farias O-RAN Distributed Unit Low (ODULOW) :2022-04-13: planning to make a F Release contribution (from FlexRan. Currently some integration blocker at the NJ plugfest. Jack, suggested to work with Ankit (Radisys), watch F Release page updates reg this.

      10. Martin Skorupski Operations and Maintenance (OAM)

      11. Alex Stancu Simulations (SIM)

      12. Jackie Huang Infrastructure (INF)

      13. weichen ni Documentation (DOC)

      14. (TBD) O-RAN Radio Unit (ORU)
8. Collaboration with OAI
   1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative

9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

   1. Presentation by Ultan (Viavi) and Avinash Bath (Samsung) on their view and interest in OSC.
      1. 2022-04-27 : Kexuan Sun (Viavi) presented the RIC Test solution.
      2. 2022-05-05: Avinash Bath (Samsung) presented “OSC contribution goals”
         1. Jack: suggest to coordinate with other project on the data movement strategy, also taking into account existing LF initiatives on data management and AI
10. Planning for Next Meeting

11. Any Other Business (AOB)

12. Meeting Summary (resolutions, new action items, etc.)

2022 04 27

Recording: 

Topic: Zoom3 O-RAN SC
Start Time: Apr 27, 2022 08:00 AM

Meeting Recording: (exceptionally as mp4): 2022-04-27-toc-part1.mp4 and 2022-04-27-toc-part2.mp4

Agenda

1. Call for Scribe (minutes owner): Arun Kumar

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: proposed by Arun and seconded by Bin . The motion is approved.
2. Review of Today's Agenda
   1. we go through the items below. Note that we have special (non-regular) items in 5a and 10a

3. Release Votes and Approval

   1. Presentation by Northeastern University (Michele P & Andrea L) on a contribution ns-3 based simulator
      1. 2022-04-27: Polese, Michele from NE Univ : presented the tool capabilities overall. The 'ns3-oran-interface or ns-O-RAN ', is the intended repo for OSC contribution. The motion to create a new repo 'ns3-O-RAN-e2' and under licence type GPL2 in the Sim project is approved.

1. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

2. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
   2. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
   3. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
   4. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
3. Old business and Status of Open Actions
   1. "F" Release:
      1. Action Point: PTLs to add a line showing code coverage stats for F release.
      2. 2022-04-06: we checked the page F Release - not all subprojects have a heading or reference to this.
      3. 2022-04-13: page F Release still does not reflect the progress and required stats.
         1. Action Point : PTLs  from non-RT RIC (ok), O-DU (not ok), Simulators (ok), Infrastructure (ok), SMO (not ok):  to check and update the stats on the F Release respective pages
      4. 2022-04-20: Jackie (Windriver) asked how to create "F" release in JIRA for his project. Answer: Try this link and if it does not work, contact Sridhar Rao (srao@linuxfoundation.org).
   2. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
      1. Tag this activity for G release.
      2. 2022-04-06: no news
         
4. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop will be held on the April 7 in RSAC call. 2022-04-13: now planned for Apr-21 9am EDT. 2022-04-20: likely new date: May-4 8am EDT
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. 2022-04-06: no news
      2. James Li Integration and Testing (INT)
      3. Mahesh Jethanandani Service Management and Orchestration (SMO) :: 2022-04-13: copyright blockers issue. 

      4. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      5. SUNIL SINGH RIC Applications (RICAPP)

      6. Thoralf Czichy RIC Platform (RIC) 

      7. (TBD) O-RAN Centralized Unit (OCU) 

      8. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      9. Luis Farias O-RAN Distributed Unit Low (ODULOW) :2022-04-13: planning to make a F Release contribution (from FlexRan. Currently some integration blocker at the NJ plugfest. Jack, suggested to work with Ankit (Radisys), watch F Release page updates reg this.

      10. Martin Skorupski Operations and Maintenance (OAM)

      11. Alex Stancu Simulations (SIM)

      12. Jackie Huang Infrastructure (INF)

      13. weichen ni Documentation (DOC)

      14. (TBD) O-RAN Radio Unit (ORU)

5. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

   1. Presentation by Ultan (Viavi) and JinGuk (Samsung) on their view and interest in OSC.
      1. 2022-04-27 : Kexuan Sun (Viavi) presented the RIC Test solution. 
6. Planning for Next Meeting

7. Any Other Business (AOB)

   1. reminder: Starting next week (=May-5) we meet on Thursdays, May-5, at 9am EST. 2022-04-27:  Andrea Buldorini will be the scribe for May.
      

8. Meeting Summary (resolutions, new action items, etc.)

2022 04 20

Recording: 

Topic: Zoom3 O-RAN SC's Personal Meeting Room

Start Time: Apr 20, 2022 08:03 AM

Meeting Recording:
https://zoom.us/rec/share/nWK6Fe5QFGqXVU8BX-_q9VJ5FP9J3xJTxWpx_wk-z78HTqYwMYRjltf93gVTBThh.3xoTamh5pxweZVkm

Agenda

1. Call for Scribe (minutes owner): Thoralf Czichy

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x	David Kinsey
   China Mobile	Jinri Huang Co-Chair	x	James Li
   Deutsche Telekom	Jakub Nový (starting 2022-04-20)	x	Ondřej Hudousek
   Ericsson	John-Paul Lane		John Keeney	x
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Arunkumar Halebid		Thoralf Czichy	x
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman	x	Manasi Padhy
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang
   Viavi Solutions	Ultan Kelly	x	Kexuan Sun
   Samsung	JinGuk Jeong	x	Avinash Bhat

   *Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

3. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: proposed by Thoralf and seconded by Bin Yang. The motion is approved.
4. Review of Today's Agenda
   1. we go through the items below.

5. Release Votes and Approval

   1. -

6. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
         

7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
   2. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
         
   3. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
         4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
   4. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
8. Old business and Status of Open Actions
   1. "F" Release:
      1. Action Point: PTLs to add a line showing code coverage stats for F release.
      2. 2022-04-06: we checked the page F Release - not all subprojects have a heading or reference to this.
      3. 2022-04-13: page F Release still does not reflect the progress and required stats.
         1. Action Point : PTLs  from non-RT RIC (ok), O-DU (not ok), Simulators (ok), Infrastructure (ok), SMO (not ok):  to check and update the stats on the F Release respective pages
      4. 2022-04-20: Jackie (Windriver) asked how to create "F" release in JIRA for his project. Answer: Try this link and if it does not work, contact Sridhar Rao (srao@linuxfoundation.org).
   2. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
      1. Tag this activity for G release.
      2. 2022-04-06: no news
         
9. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Sridhar Rao  /Release Planning: Weekly TOC Scheduling
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop will be held on the April 7 in RSAC call. 2022-04-13: now planned for Apr-21 9am EDT. 2022-04-20: likely new date: May-4 8am EDT
         
         1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. 2022-04-06: no news
      2. James Li Integration and Testing (INT)
      3. Mahesh Jethanandani Service Management and Orchestration (SMO) :: 2022-04-13: copyright blockers issue. 

      4. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      5. SUNIL SINGH RIC Applications (RICAPP)

      6. Thoralf Czichy RIC Platform (RIC) 

      7. (TBD) O-RAN Centralized Unit (OCU) 

      8. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      9. Luis Farias O-RAN Distributed Unit Low (ODULOW) :2022-04-13: planning to make a F Release contribution (from FlexRan. Currently some integration blocker at the NJ plugfest. Jack, suggested to work with Ankit (Radisys), watch F Release page updates reg this.

      10. Martin Skorupski Operations and Maintenance (OAM)

      11. Alex Stancu Simulations (SIM)

      12. Jackie Huang Infrastructure (INF)

      13. weichen ni Documentation (DOC)

      14. (TBD) O-RAN Radio Unit (ORU)

10. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

11. Planning for Next Meeting
    1. Presentation by Ultan (Viavi) and JinGuk (Samsung) on their view and interest in OSC.
    2. Presentation by Northeastern University on a ns-3 based simulator → to discuss under item 5

12. Any Other Business (AOB)

    1. 2022-04-20: new meeting time proposal by Jinri: https://lists.o-ran-sc.org/g/toc/message/676. Jinri has made a motion starting May-5 to use Thursdays, 9am EST. Apr-27 still the Wednesday timeslot. Ganesh seconded. The motion was approved.
       

13. Meeting Summary (resolutions, new action items, etc.)

2022 04 13

Recording: 

Topic: Zoom3 O-RAN SC
Start Time: Apr 13, 2022 08:00 AM

Meeting Recording:
https://zoom.us/rec/share/fGQnbh3PqavtDj_mSM-cT0FThRIhTCyrWmN5wBTCt9VslRUNoZedJqYoBPzuRPfo.IWBgu_G-0-pt3y9N

Agenda

1. Call for Scribe (minutes owner): Arunkumar Halebid

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x	David Kinsey
   China Mobile	Jinri Huang Co-Chair	x	James Li
   Deutsche Telekom	David Streibl→ Jakub Nový (starting 2022-04-20)	x	Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Nokia	Arunkumar Halebid	x	Thoralf Czichy
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang
   Viavi Solutions	Ultan Kelly	x	Kexuan Sun
   Samsung	Jeong JinGuk		Avinash Bhat	x

   *Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

3. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting approval: proposed by Arun and seconded by David The motion is approved.
4. Review of Today's Agenda
   1. we go through the items below.

5. Release Votes and Approval

   1. Thoralf (near-RT RIC) proposed a new repo ric-plt/stslgo . Details: https://lists.o-ran-sc.org/g/toc/message/674. Seconded by Jinri. The motion is approved.

6. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06: no news; 2022-04-13 : no major progress/updates.
         

7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting

      1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
      2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-13 : Open;
   2. Plugfest
      1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
      2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
      3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information).
   3. O-RAN spending
      1. 2022-04-06
         1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
         2. David responded with potential need for simulation tool
         3. Jinri reminded participants of the meeting to check for any additional spending needs.
8. Old business and Status of Open Actions
   1. "F" Release:
      1. Action Point: PTLs to add a line showing code coverage stats for F release.
      2. 2022-04-06: we checked the page F Release - not all subprojects have a heading or reference to this.
      3. 2022-04-13: page F Release still does not reflect the progress and required stats.
         1. Action Point : PTLs  from  non-RT RIC, O-DU, Simulators, Infrastructure, SMO :  to check and update the stats on the F Release respective pages
   2. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
      1. Tag this activity for G release.
      2. 2022-04-06: no news
         
9. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release ManagerSridhar Rao  /Release Planning: Weekly TOC Scheduling
      1. Trishan has moved on. Need to work with LF to secure a replacement. 
      2. Action Point: Jack to send another message to Arpit requesting when replacement for Trishan is available.>DONE(2022-04-13). Sridhar Rao (srao@linuxfoundation.org) will replace Trishan
   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
      
      1. OTF Workshop
         1. OTF Workshop will be held on the April 7 in RSAC call. 2022-04-13: now planned for Apr-21 9am EDT. 2022-04-20: likely new date: May-4 8am EDT
            
         2. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
         3. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
         4. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
         5. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
      2. "G" Release
         1. Jack: How do we track our support of MVP?
         2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
         3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. 2022-04-06: no news
      2. James Li Integration and Testing (INT)
      3. Mahesh Jethanandani Service Management and Orchestration (SMO) :: 2022-04-13: copyright blockers issue. 

      4. John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      5. SUNIL SINGH RIC Applications (RICAPP)

      6. Thoralf Czichy RIC Platform (RIC) 

      7. (TBD) O-RAN Centralized Unit (OCU) 

      8. user-30c9d  O-RAN Distributed Unit High (ODUHIGH)

      9. Luis Farias O-RAN Distributed Unit Low (ODULOW) :2022-04-13: planning to make a F Release contribution (from FlexRan. Currently some integration blocker at the NJ plugfest. Jack, suggested to work with Ankit (Radisys), watch F Release page updates reg this.

      10. Martin Skorupski Operations and Maintenance (OAM)

      11. Alex Stancu Simulations (SIM)

      12. Jackie Huang Infrastructure (INF)

      13. weichen ni Documentation (DOC)

      14. (TBD) O-RAN Radio Unit (ORU)

10. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

11. Planning for Next Meeting

12. Any Other Business (AOB)

13. Meeting Summary (resolutions, new action items, etc.)

Archived Meetings