/
2022 Q1 (Jan, Feb, Mar)

2022 Q1 (Jan, Feb, Mar)

Apr 07, 2022

2022 03 30

Recording: 2022-03-30

Agenda

  1. Call for Scribe (minutes owner): @MASAFUMI MASUDA

  2. Roll Call & Quorum Check 

    *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 @MASAFUMI MASUDA seconded by @Andrea Buldorini [TIM]. The motion is approved.

  4. Review of Today's Agenda

  5. Release Votes and Approval

  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.

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

    1. F2F Meeting

      1. Jinri: EC has decided to make the June F2F Meeting virtual and the October one physical.

      2. Jack: Where is the October one?

      3. Jinri: It has not been decided yet.

      4. 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. TOC Nomination

      1. Action Point: Jinri to get reaffirmation from TSC for the 6 seats including Samsung as of April 6.

    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: I don't see Tracy today. We will talk about it next week.

  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 by March 30.

    2. OSC labs

      1. James Li: We are trying to do some testing on the O-Cloud already set up in the New Jersey lab.

      2. Thoralf: Did you send an email on this topic?

      3. James Li: Yes(https://lists.o-ran-sc.org/g/discuss/message/492).

      4. David Kinsey: We are trying to address network issues.

      5. Jack: Let's keep working. Anything else?

      6. James Li: The Taiwan lab is active in lab setup. IEEE will have the international symposium.

    3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.

      1. Tag this activity for G release.

  9. Standing Agenda Items (Brief Status of Ongoing Activities)

    1. Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Trishan has moved on. Need to work with LF to secure a replacement.

    2. Requirements Software Architecture Committee

      1. Updates

      2. OTF Workshop

        1. OTF Workshop will be held on the April 7.

      3. "G" Release

        1. David Kinsey: We haven't been pushing G Release. We are trying to make sure we get a firm foundation.

        2. Jack: How do we track our support of MVP?

        3. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.

    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. Jack: Do you have updates on how you are doing with code coverage and software testing?

        2. Mahesh: We have the capability of code testing that's been committed.

        3. Jack: I'd like you to add a section that documents what percentage coverage.

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

        1. John Keeney: The code coverage is excellent. I'm trying to figure out what should be shown here.

        2. Jack: If people have an idea how we can improve, I'm happy to discuss it.

      4. @Sunil Kumar RIC Applications (RICAPP)

        1. Jack: There is a number of xApps, so we are focusing on the active ones getting the most attention. If you can update the page, that would be great. 

        2. Sunil: Sure.

      5. @Thoralf Czichy RIC Platform (RIC) 

        1. Jack: You can create a line in the table that conveys code coverage percentage or other useful information.

        2. Thoralf: I can put the link to what we discussed in the project.

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

      7. @Former user (Deleted)  O-RAN Distributed Unit High (ODUHIGH)

        1. Ankit: There is a challenge. I'll discuss in the team.

        2. Jack: Let's make progress.

      8. @Lvfarias (Deactivated) O-RAN Distributed Unit Low (ODULOW)

      9. @Martin Skorupski Operations and Maintenance (OAM)

        1. Martin: I need to add lists and links. The code coverage is about 60%.

      10. @Alex Stancu Simulations (SIM)

        1. Martin: Alex has a little trouble with setting up. He will contact LF.

      11. @Jackie Huang Infrastructure (INF)

        1. Jackie: This is a downstream project. The code coverage relies on the upstream community.

        2. Jack: You need to put some information here.

      12. @Weichen Ni Documentation (DOC)

      13. (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.)

2022 03 23

Recording: 2022-03-23

Agenda

  1. Call for Scribe (minutes owner): @MASAFUMI MASUDA

  2. Roll Call & Quorum Check 

    *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 @MASAFUMI MASUDA seconded by @Thoralf Czichy . The motion is approved.

  4. Review of Today's Agenda

  5. Release Votes and Approval

  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.

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

    1. June F2F Meeting

      1. Jinri: There was no conclusion in the TSC meeting last Friday. Probably there will be a decision this week.

    2. TOC Nomination

      1. Action Point: Jinri to get reaffirmation from TSC for the 6 seats including Samsung as of April 6.

  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 by March 30.

      2. Jack: Is there any progress for the initial Dev cycle?

      3. David Kinsey: We have been trying to get OCU.

      4. Jack: Who is the point person?

      5. David Kinsey: There is no real development team. Ankit from Radisys, Jakie from WInd River and myself are trying to figure out where the parts are.

      6. Ankit: YANG model file needs to be filled by a person from O-Cloud.

      7. Bin: I'm following this activity as a O-Cloud provider.

      8. Jack: David, can you kick off an email? We also need to improve documentations on the lab.

      9. David Kinsey: We are trying to collect a good set of documentation repeatable across the different labs. We have to work with our documentation PTL.

      10. Jack: You can work with James as a key contributor.

    2. OSC labs

      1. Jack: There is some progress on the clock issue at the New Jersey Lab.

      2. Jack: Please encourage your companies to participate the spring plugfest.

    3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.

      1. Tag this activity for G release.

  9. Standing Agenda Items (Brief Status of Ongoing Activities)

    1. Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Trishan has moved on. Need to work with LF to secure a replacement.

    2. Requirements Software Architecture Committee

      1. Updates

      2. OTF Workshop

        1. David Kinsey: My recommendation is to push the OTF Workshop for a week.

        2. Jack: Let's push it for 2 weeks and take the time to get it working, tested and documented.

        3. Jinri: Will it be recorded?

        4. David: Yes. We will do that on the April 7.

        5. Jinri: I recommend you to announce this event.

      3. Security

        1. Jack: Robert, do you have any follow-up questions?

        2. Robert Webb: My questions are answered well.

        3. Jack: This is something that we want to make continuous improvement.

      4. "G" Release

        1. Jack: They start gathering things for the G Release. The F2F meeting is an opportunity to interact with key activities. Our biggest challenge is our limited integration and test team size.

        2. Jack: What's the next piece after the OCU?

        3. David Kinsey: It would be trying to get the SMO and the Near-RT RIC pieces.

    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)

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

      4. @Sunil Kumar RIC Applications (RICAPP)

      5. @Thoralf Czichy RIC Platform (RIC) 

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

      7. @Former user (Deleted)  O-RAN Distributed Unit High (ODUHIGH)

      8. @Lvfarias (Deactivated) 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)

  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.)

2022 03 16

Recording: 2022-03-16

Agenda

  1. Call for Scribe (minutes owner): @MASAFUMI MASUDA

  2. Roll Call & Quorum Check 

    *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 @MASAFUMI MASUDA  seconded by @John Paul Lane . The motion is approved.

  4. Review of Today's Agenda

    1. TOC Renewal

      1. Jack: Every year in March we renew the participants in the TOC 6 open positions.

    2. Security Requirement

      1. Robert: I want to understand security requirements and aspects around the software community.

  5. Release Votes and Approval

  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.

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

    1. O-RAN ALLIANCE Funding

      1. Action Point: There is some O-RAN Alliance funding available for a one-time investment in improving our activity. If anyone has suggestions on how to improve / accelerate the work that we are doing, please bring your suggestions and ideas forward and we will discuss at the next TOC meeting.

    2. F2F Meeting

      1. Jinri: June F2F meeting has not been decided. TSC will discuss this Friday.

    3. TOC Nomination

      1. Jack: We recently filled our 12th position and approved with Samsung, correct?

      2. Jinri: Yes, is has been approved and reflected in the Board report.

      3. Jack: We need re-approval from TSC for the 6 seats as of April 6.

      4. Jinri: I can do that.

      5. Action Point: Jinri to get re-approval from TSC for the 6 seats including Samsung as of April 6.

  8. Old business and Status of Open Actions

    1. Charter Update

    2. Document Modification and Creation

    3. "F" Release:

      1. Action Point: PTLs to add a line showing code coverage stats for F release.

    4. OSC labs

      1. Jinri: O-RAN ALLIANCE recently began the call for participation for the spring plugfest.

    5. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.

      1. Tag this activity for G release.

  9. Standing Agenda Items (Brief Status of Ongoing Activities)

    1. Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Trishan has moved on. Need to work with LF to secure a replacement.

    2. Requirements Software Architecture Committee

      1. Updates

        1. Rittwik: Yesterday we talked about the PTP thing and the Taiwan OSC Lab. With regard to the OCU deployment, Yang model file is being sent to all the labs.

        2. Jack: We don't have an open-source OCU. In the interim, we will use a test fixture that we get a binary from Radisys.

      2. OTF Workshop

        1. James: OTF workshop was pushed back for 2 weeks. We want to have all the projects understand how it works.

      3. Security

        1. Jack: All the active projects have completed the security badging. We have talked about security requirements in the RSAC committee.

        2. Rittwik: There are risk and threat analysis. If they come up with a concreate recommendation out of that in July train, then maybe we can implement some of that.

        3. Jinri: Do we have a regular communication channel with SFG?

        4. Rittwik: We join some of the SFG meetings.

        5. Jack: It's everyone's responsibility to bring these topics forward.

        6. Robert: There might be some opportunities to drive some security requirements in the RSAC.

      4. "G" Release

        1. Jack: The next F2F is the opportunity to highlight things for "G" Release.

    3. Report out from PTL: Stand-Up & Report Out on Blockers

      1. @James Li Integration and Testing (INT)

        1. James: We talked about the POWDER testbed. It's a good resource.

        2. Tracy: The question is that is it reasonable or possible to commingle what they are doing now with acting as OSC Lab.

        3. Jack: We focused those labs on the bigger plugfests and other activities. It's the community to decide to leverage that.

      2. @Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      4. @Sunil Kumar RIC Applications (RICAPP)

      5. @Thoralf Czichy RIC Platform (RIC) 

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

      7. @Former user (Deleted)  O-RAN Distributed Unit High (ODUHIGH)

      8. @Lvfarias (Deactivated) 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)

  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.)

2022 03 09

Recording: 2022-03-09

Agenda

  1. Call for Scribe (minutes owner): @MASAFUMI MASUDA

  2. Roll Call & Quorum Check 

    *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 @MASAFUMI MASUDA seconded by @John Paul Lane. The motion is approved.

  4. Review of Today's Agenda

    1. Daylight saving time handling

      1. All agreed to shift the meeting time one hour earlier starting the Mar-16 meeting being aligned with the US daylight saving time.

  5. Release Votes and Approval

    1. AAL project

      1. Request is to create a new repo under the O-DU Low project. Contribution is from Intel. Different license (BSD) needed for this repo.

        1. Need to approve the creation of the repo in O-DU Low project.

        2. Need to approve use of BSD license for contributions to the new repo.

        3. Need to approve a committer for the repo - proposal is Niall Power (Intel). 

      2. A written proposal was requested to describe the proposal and also questions have been sent to Intel. It would be good to get clarification on these issues before taking a vote.

      3. Response to request for further information is still outstanding. This issue will remain tabled.

      4. Niall presented the WG6 AAL repo details and his answers to Thoralf's questions.

        1. Jack: Is that part of ODU LOW project?

        2. Niall: That makes sense.

        3. John-Paul: Do we need to make an exception for the BSD license?

        4. Jack: TOC can approve a different open source license.

        5. Decision: Request to create a new repo using the BSD-3 license under the ODU LOW project is proposed by @Niall Power seconded by @Former user (Deleted). Ten of 11 voting members (more than two-thirds defined in the charter) are for the proposal. The motion is approved.

    2. SMO project

      1. Mahesh: I sent a request to change the name of a repo under the SMO (https://lists.o-ran-sc.org/g/toc/message/666).

      2. Jack: When we created the Near-RT RIC, we separated out a project for xApps. What should we do for rApps?

      3. Thoralf: One of the key criteria was the license issues.

      4. John-Paul: We would consider keeping the rApp in the same project as the Non-RT RIC and if we saw a need to split them later, then we could create a separate project.

      5. Jack: We don't need an answer for the topic today. We need to have periodical discussions on those items. I'll return to Mahesh's request.

      6. Decision: Request to change the name of smo/app to smo/pkg is proposed by @Mahesh Jethanandani seconded by @John Paul Lane. 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.

        1. John-Paul: It is unlikely to see SCCL license being published before the March train cut off.

        2. Jack: I'll raise the question to see if we can get an answer from Jinri in next week's call.

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

    1. Action Point: There is some O-RAN Alliance funding available for a one-time investment in improving our activity. If anyone has suggestions on how to improve / accelerate the work that we are doing, please bring your suggestions and ideas forward and we will discuss at the next TOC meeting.

    2. TOC nomination

      1. Avinash: I want to check the status of the TOC nomination. I will send a reminder email.

      2. Jack: To follow the process, I'm going to look for a confirmation that the company wants to continue in the existing role for another year. We have no new requests.

      3. Jack: Would Ericsson like to continue to participate for the next year?