/
2021 Q3 (Jul, Aug, Sep)

2021 Q3 (Jul, Aug, Sep)

Nov 20, 2021

2021 09 29

Recording: Zoom recording

Agenda

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

  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 09/22/2021 TOC meeting approval: proposed by Andrea, seconded by Juha. The motion is approved 

  4. Review of Today's Agenda

  5. Release Votes and Approval

    1. AAL project

      1. Action point: Trishan to check if your have to sign a new agreement for the repo if TOC decides on BSD license use. Refer to minutes of previous meeting(s) for details.

      2. Action point: Jack to present the write up about the AAL project  to have a vote.

        1. This was put on the table on 2021-07-07 meeting

        2. Jack: There is discussion ongoing in WG6 and we're still waiting for some aspects that discussion to be resolved. Some clarifications were made but until we get more information we leave this table for now

        3. Update on 08/04/21: This is on hold. WG6 is not having meetings due to vacations. Stage 3 specs are now being targeted for November train. 

        4. Update on 08/18/21: Jack said there is no update and this item continues to be tabled.

        5. Update on 09/01/21: No update in the vacation period. Still waiting for guidance. 

        6. Update on 09/15/21: No update. To be continued.

        7. Update on 09/22/21: No update.

    2. New Repos, Updates and Cleanup 

      1.  Matti proposes the creation of the following new repos for RICAPP:

      2. ric-app/ric-sdk-cpp (@Matti Hiltunen )

        1. 09/22/21: Matti proposes the creation of a new repo for RICAPP

          1. Thoralf proposed some changes by email to clarify the description.  It was commented that RIC SDK in O-RAN is still under discussion and it is not clear

          2. Matti will propose a review based on suggestions received.

        2. (update on 09/29/21) A revised proposal was submitted  (see https://lists.o-ran-sc.org/g/toc/message/573)

          1. Motion made by Matti, seconded by Juha. Motion is approved.

      3. ric-plt/ricctl (@Thoralf Czichy )

        1. new repo proposed for RICPTL project (see https://lists.o-ran-sc.org/g/toc/message/571)

          1. Principle is to reuse CLI implementation from ONAP by reference (no forking). Work is targeting E release with initial set of commands. To be extended in later releases.

        2. Motion made by Juha, seconded by Andrea. Motion is Approved

      4. inf/pti/o2 (@Jackie Huang )

        1. a new repo was proposed for INF project (see https://lists.o-ran-sc.org/g/toc/message/572)

        2. Motion made by Jackie, seconded by Jinri. Motion is Approved

  6. Copyright update

    1. Update from Jack (08/25/21): The SCCL license is posted on the O-RAN website. A separate CLA is required for contribution under SCCL license.

    2. Thoralf asked who is putting the first copy of code from specifications in the repository. Jack confirmed any OSC participant can initiate.

    3. CLA draft is ready and is due for approval from O-RAN. Trishan informed it takes 2 weeks for implementation of new CLA.

    4. Update from Jack (09/01/21): still waiting for feedback from O-RAN Alliance about the material to be used first.

    5. 09/15/21: Jinri provided to O-RAN EC a list of examples for candidate material to be shared under SCCL license. 

    6. 09/29/21: Jack and Jinri will synchup on SCCL licence process with O-RAN legal a dedicated meeting  

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

    1. July train has passed IPR review. November train deadline will be slightly shifted to November 24th (WGs approval)

    2. vF2F in October is cancelled. Next (v)F2F will be in February 2022.

    3. Budget review before the next O-RAN board (@Trishan de Lanerolle ). If additional resources are needed, to be raised and discussed before submission to EC

  8. Old business and Status of Open Action 

    1. "E" Release timeline.

    2. OSC lab in Taiwan (Prof Ray's lab):

      1. Update on 08/25/21: Prof Ray talking to Intel and Viavi. Division of work is not complete till lab is up. 

      2. Potentially integration work can happen in Taiwan lab when sprints complete. By end of the release, they can package it all.

      3. Jack suggested a gradual progression in Taiwan lab with a few modules or blocks being integrated first.

      4. Update on 09/01/21. Rittwik: Prof Ray got in touch with some PTLs. PTLs interested in collaboration may get back to to coordinate with Prof. Ray

      5. Update on 09/08/21. Rittwik: work is still ongoing on lab setup.

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

    4. "F" Release timeline

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

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

    2. @Former user (Deleted) Requirements Software Architecture Committee

      1.  OSC lab setup still ongoing. PTP grandmaster deployment and configuration under assessment

      2. Radysis (Manasi) had sent HW/SW requirements for the O-CU. AP. David to check with Rich if this went through.

      3. 09/22/21: Open issue on PM data transfer mechanism from O-DU high. ( @Former user (Deleted)/ @David Kinsey [AT&T] )

        • update on 09/29/21: still open

2021 09 22

Recording: Zoom recording

Agenda

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

  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 09/15/2021 TOC meeting approval: proposed by Andrea, seconded by David S. Motion approved.

  4. Review of Today's Agenda

  5. Release Votes and Approval

    1. AAL project

      1. Action point: Trishan to check if your have to sign a new agreement for the repo if TOC decides on BSD license use. Refer to minutes of previous meeting(s) for details.

      2. Action point: Jack to present the write up about the AAL project  to have a vote.

        1. This was put on the table on 2021-07-07 meeting

        2. Jack: There is discussion ongoing in WG6 and we're still waiting for some aspects that discussion to be resolved. Some clarifications were made but until we get more information we leave this table for now

        3. Update on 08/04/21: This is on hold. WG6 is not having meetings due to vacations. Stage 3 specs are now being targeted for November train. 

        4. Update on 08/18/21: Jack said there is no update and this item continues to be tabled.

        5. Update on 09/01/21: No update in the vacation period. Still waiting for guidance. 

        6. Update on 09/15/21: No update. To be continued.

        7. Update on 09/22/21: No update.

    2. Repos Updates and Cleanup 

      1. Trishan: The following repos were submitted for TOC consideration to be archived (https://lists.o-ran-sc.org/g/toc/message/549): 

        1. Submitted by Alex Stancu : 

          • sim

          • sim/e1-interface

          • sim/f1-interface

          • sim/fh-interface

        2. Submitted by Mahesh Jethanadani: 

          • smo

          • smo/a1

          • smo/app

          • smo/o2

        3. Submitted by Jackie Huang

          • aal/lib

          • aal/logic

          • aal/mgmt

          • aal/virt

        4. "Empty repos" not being updated since the last 12 months (Note: empty repos can be reactivated upon request if the activity resumes)

          • com/sctp (already agreed at the previous meeting)

          • gnb-int/build

          • gnb-int/common

          • gnb-int/src

          • it/int

          • log (already agreed at the previous meeting)

          • o-cu/e2

          • o-cu/sim

          • o-du

          • o-du/sim

          • o-ru/sim

          • ric-nrt/a1ric-nrt/oam

          • ric-plt/sdl/config (already agreed at the previous meeting)

          • tracelibgo (already agreed at the previous meeting) 

        5. Motion to archive the above repos made by Jack, seconded by Ganesh. The motion is approved

        6. Matti proposes the creation of the following new repos for RICAPP:

          1. ric-app/rc (https://lists.o-ran-sc.org/g/toc/message/545)

            1. it is commented that O-RAN would probably publish the E2SM-RC specification by October, but the project can start working earlier

            2. Motion to approve the creation of ric-app/rc repo made by Jack, seconded by Andrea. The motion is approved.

          2. ric-app/ric-sdk-cpp

            1. Thoralf proposed some changes by email to clarify the description.  It was commented that RIC SDK in O-RAN is still under discussion and it is not clear 

            2. Matti will propose a review based on suggestions received.

        7. Change of PTL in RICAP (https://lists.o-ran-sc.org/g/toc/message/548)

          1. Matti will step down from PTL role, while keeping on supporting the new PTL and the group for some time. @Sunil Kumar (HCL) has been voted by the group as the new candidate.

          2. Motion to approve Sunil Sing as new PTL for RICAPP made by Jack, seconded by Juha. The motion is approved.

  6. Copyright update

    1. Update from Jack (08/25/21): The SCCL license is posted on the O-RAN website. A separate CLA is required for contribution under SCCL license.

    2. Thoralf asked who is putting the first copy of code from specifications in the repository. Jack confirmed any OSC participant can initiate.

    3. CLA draft is ready and is due for approval from O-RAN. Trishan informed it takes 2 weeks for implementation of new CLA.

    4. Update from Jack (09/01/21): still waiting for feedback from O-RAN Alliance about the material to be used first.

    5. 09/15/21: Jinri provided to O-RAN EC a list of examples for candidate material to be shared under SCCL license. 

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

    1. Status of PR for "D" Release to be checked

  8. Old business and Status of Open Action 

    1. "E" Release timeline.

      1. Status of implementation and call for contributions

      2. OSC lab

        • Update on 09/22/21 David K.: O-FH Gateway almost ready to be shipped. Still working on a permament solution for the clock.

    2. OSC lab in Taiwan (Prof Ray's lab):

      1. Update on 08/25/21: Prof Ray talking to Intel and Viavi. Division of work is not complete till lab is up. 

      2. Potentially integration work can happen in Taiwan lab when sprints complete. By end of the release, they can package it all.

      3. Jack suggested a gradual progression in Taiwan lab with a few modules or blocks being integrated first.

      4. Update on 09/01/21. Rittwik: Prof Ray got in touch with some PTLs. PTLs interested in collaboration may get back to to coordinate with Prof. Ray

      5. Update on 09/08/21. Rittwik: work is still ongoing on lab setup. 

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

    2. "F" Release timeline

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

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

    2. @Former user (Deleted) Requirements Software Architecture Committee

      1.  (Status on 09/22/21 provided by David K.) We havent addressed Slicing use case timeline in RSAC yet. We mainly worked on the O1 CR to meet the O-RAN submission deadline by Oct 11th.  

      2. Open issue on PM data transfer mechanism from O-DU high. ( @Former user (Deleted)/ @David Kinsey [AT&T] )

2021 09 15

Recording: Zoom recording

Agenda

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

  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 09/08/2021 TOC meeting approval: proposed by Andrea, seconded by John Paul. Motion approved.

  4. Review of Today's Agenda

  5. Release Votes and Approval

    1. AAL project

      1. Action point: Trishan to check if your have to sign a new agreement for the repo if TOC decides on BSD license use. Refer to minutes of previous meeting(s) for details.

      2. Action point: Jack to present the write up about the AAL project  to have a vote.

        1. This was put on the table on 2021-07-07 meeting

        2. Jack: There is discussion ongoing in WG6 and we're still waiting for some aspects that discussion to be resolved. Some clarifications were made but until we get more information we leave this table for now

        3. Update on 08/04/21: This is on hold. WG6 is not having meetings due to vacations. Stage 3 specs are now being targeted for November train. 

        4. Update on 08/18/21: Jack said there is no update and this item continues to be tabled.

        5. Update on 09/01/21: No update in the vacation period. Still waiting for guidance. 

        6. Update on 09/15/21: No update. To be continued.

    2. Repos to be archived

      1. Repos belonging to the following categories:

        1. managed/owned repos PTLs request to archive

        2. unmanged/unused repos

        3. repos with missing info.yaml files

      2. 09/08/21 - Action point: @Trishan de Lanerolle will collect proposals from PTLs to vote on at the next meeting. 

      3. 09/15/21

        • the following repos are proposed to be archived as no longer active:

          1. ODU_Dev_Bronze_Rel

          2. E2AP

          3. com/asn1c

          4. log

          5. ric-plt/sdl/config

          6. tracelibgo

          7. com/sctp

          8. ric-plt/resource-status-manager

          9. ric-plt/resource-status-processor

          10. ric-app/admin

          11. ric-app/kpimon

          12. ric-app/ml

          13. ric-app/qp-driver

        • Motion proposed by Jack, seconded by Juha. Motion approved.

        • The following additional repose are proposed for archiving (Martin):

          • portal

        • Motion proposed by Jack, seconded by Andrea. Motion approved.

  6. Copyright update

    1. Update from Jack (08/25/21): The SCCL license is posted on the O-RAN website. A separate CLA is required for contribution under SCCL license.

    2. Thoralf asked who is putting the first copy of code from specifications in the repository. Jack confirmed any OSC participant can initiate.

    3. CLA draft is ready and is due for approval from O-RAN. Trishan informed it takes 2 weeks for implementation of new CLA.

    4. Update from Jack (09/01/21): still waiting for feedback from O-RAN Alliance about the material to be used first.

    5. 09/15/21: Jinri provided to O-RAN EC a list of examples for candidate material to be shared under SCCL license. 

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

    1. Status of PR for "D" Release to be checked

  8. Old business and Status of Open Action 

    1. "E" Release timeline.

      1. Rittwik: Tracking of Slicing use case need to have access to the jira tickets from the SMO / Non RT RIC and O-DU high projects in order to ensure the closed loop is achievable.

        • Open issue on PM data transfer mechanism from O-DU high. To be continued in SMO project (David). 

      2. Mahesh flagged the disaggregated VES implementation. David Kinsey is investigating this.

        1. Update on 09/01/21:

          1. Rittwik: to check ONAP viewpoint about potential enhancement to VES coming from OSC Rel-E requirements

          2. Martin: there is a debate in ONAP about PM streaming and potential enhancements wrt. 3GPP standardized solution, but this should not be of impact for OSC

          3. Martin and John have reported the status of disaggregated VES to ONAP-OSC alignment team. The discussion is at an early stage but ONAP PTLs are now informed and alignment will go on.

        2. Update  on 09/08/21 (David):

          1. to discuss with ONAP at the forthcoming meeting; main task for SMO project could be to ensure that DMaaP also work for other projects while Inlfux and Logstash collect data from O1

        3. Update  on 09/15/21 (David): Aligned with ONAP was achieved and the principle for an updated VES flow (to ensure support for multiple clients with minimal impact) was agreed. Wrt O1 interface, it was also agreed to submit a CR to O-RAN (and possibly harmonize with 3GPP). Closed

      3. Action point: @Ganesh Shenbagaraman Provide an update, if O1 is going to be available anytime soon in Radisys O-CU test fixture?

        1. Radisys team working on the update for  O-CU O1. No date is confirmed yet.

        2. update on 09/08/21: CNF implementation still to be confirmed. Info expected in a couple of weeks.

      4. Action point: @huangjinri@chinamobile.com to raise with EC on the projects dwindling with low contributions.

        1. Update on 09/15/21 (Jack): the current status was reported to EC. It is expected that more recent projects and activities will get into a more mature state. Also new feature under specification in O-RAN Alliance (e.g. R1 interface) will provide more input for further activities in OSC. If members have inputs or issues to raise towards O-RAN alliance, they can bring to Architecture team. Closed

      5. Status of implementation and call for contributions

        1. Jack, Rittwik: need to document the current status and areas where contributions are needed to fill the gaps. First target could be on O-RAN protocols and interfaces

        2. Thoralf: agree. We should also invite for contributions on integration activities.

        3. Action point @Trishan de Lanerolleto create a wiki section to document and keep track of the progress.

        4. update on 09/15/21. Trishan provided a new page with title "Participate". Closed

      6. Action point: @Former user (Deleted) to add status page. PTLs will update the progress on use cases approval and new features.

        1. Rittwik provided the Release E status page. This is being updated by PTLs. Target is to have an initial version from all the PTLs for the next meeting on 09/22/21. Closed

      7. OSC lab is still lacking of some Open Front-haul equipment. Action Point @David Kinsey [AT&T] to check the status and report back.

    2. OSC lab in Taiwan (Prof Ray's lab):

      1. Update on 08/25/21: Prof Ray talking to Intel and Viavi. Division of work is not complete till lab is up. 

      2. Potentially integration work can happen in Taiwan lab when sprints complete. By end of the release, they can package it all.

      3. Jack suggested a gradual progression in Taiwan lab with a few modules or blocks being integrated first.

      4. Update on 09/01/21. Rittwik: Prof Ray got in touch with some PTLs. PTLs interested in collaboration may get back to to coordinate with Prof. Ray

      5. Update on 09/08/21. Rittwik: work is still ongoing on lab setup. 

    3. Jack (08/25/21): Challenges in test and integration activities. Looking for volunteers to fill this gap.

      1. Update on 09/01/21 (Jack) new contributors may be interested (e.g. also Prof Ray) .  Need for a leadership to take the role of coordination.

      2. Update on 09/15/21: this is still missing. Reopen when volunteers show up.    

    4. Action point: @Trishan de Lanerolle to follow up on participation in ONES summit. 

      1. O-RAN SC presence in ONES summit. Trishan brought up the option of OSC booths and demos.

      2. Trishan highlighted the opportunity to interact with other networking projects.

      3. Nokia has an OSC-related presentation at ONES2021. Thoralf noted travel restrictions make it difficult to have in-person contributions from Nokia.

      4. Decision to participate to be made before end of August.

      5. Trishan to follow up on interest on logistics.

      6. 09/01/21 - Trishan: the event will be fully virtual. We have material (demos and proposals) to be presented.

      7. 09/15/21 - Trishan: We have demo provided by Tracy and the preparation was done. No open issues. Closed

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

    6. "F" Release timeline

      1. no items

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

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

    2. @Former user (Deleted) Requirements Software Architecture Committee

    3. Integration and Test (PTL needed)

      1. 09/01/21 - Rittwik:

        1. VES agent SMO, OAM PLTs are engaged. Network Slicing: three-way testing is foreseen. Need to document the call flow validation.

        2.  Multiparty coordination may be supervised by RICAPP project

        3. Action Point: @Former user (Deleted)to document the above in the status page. Done in 09/15/21. Closed

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

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