Technical Charter for O-RAN Software Community

2021 11 17

Recording:

Agenda

1. Call for Scribe (minutes owner): William DIEGO 

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair		David Kinsey
   China Mobile	Jinri Huang Co-Chair		James Li
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   Ericsson	John-Paul Lane		John Keeney
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy
   TIM	Andrea Buldorini		Scarpina Salvatore
   Wind River	Bin Yang		Jackie Huang

   *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, seconded by   . The motion is approved
      
4. Review of Today's Agenda
   1. Any new items to add?
   2. Thoralf-2021-11-12: Note that on the near-RT RIC side we are now planing to set up Jenkins jobs for automatic creation of ARM64 container images and libraries into Nexus and packagecloud (similar as done for x86). I understand LF supports also other projects (outside of OSC) in such work. We now moved the discussion under IT-23251 (LF support). This is supported by Kiel and Victor. Unfortunately I (Thoralf) can't participate in the 2021-11-17 meeting, but any further information needed, please send a e-mail or we discuss this in the 2021-11-24 TOC meeting.

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 11/10/21: No update.
6. Copyright update
   1. 11/03/21:
      1. Jack SSCL update : A meeting with legal team will held today. Some questions as who will be the PTL, what project will put it under this repo and also questions related to the project charter that has to be updated and then voted.
      2. Jinri : a meeting will be organised in the context of OSFG to have further discussion about SCCL for O-RAN Alliance side (Nov. 11 at 9-10PM Beijing time = 8-19AM EST = 2-3PM CET). Jinri invite the community to subscribe at the OSFG mailing list. → https://lists.o-ran-sc.org/g/toc/message/609
   2. 11/10/21: 
      1. CLA for SCCL meeting later today, more information on next session.
      2. July train publication for O-RAN specs, 24th november?
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. 11/10/21:

      1. Thoralf Czichy new E2 API 2.0 spec (July train) should be supported for next release, does something planned to support new version on on other sub-project (e.g. O-DU side)? user-30c9d we (O-DU)can plan to support E2 API 2.0 pour F release.

      2. xApps are not impacted by the E2 API 2.0 version.

      3. Thoralf Czichy platform is indepedent of service models so no impacted by new version of PMs.

8. Old business and Status of Open Action 

   1. "E" Release timeline.
      1. 11/03/21: PR of E release is expected for the first days of the next year. 
   2. OSC lab in Taiwan (Prof Ray's lab):
      1. 10/27/21: Rittwik: Prof Ray's student will update wiki to document the networks/what they have done today.(11/10/21 James Liis in contact and supporting them.)
      2. 11/10/21: user-59b16 Prof Ray's student is asking for some help (user-30c9d ) to deal with MAC scheduler (extract scheduler functionalities from ODU). We can start some discussons about it in F release (scheduler assitance as a service model)
   3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
      1. 11/10/21: Tracy Van Brakle 5G super blueprint is already taking advantage of the OSC initiated developments in ONAP (but not just ONAP). Jack: There are new functionalitiesthat are needed that we need to make sure that gets into the roadmap.
   4. "F" Release time:
      1. 10/27/21: Rittwik: will focus on O-Cloud usecase in F release, as well as the continuation of network slicing use case. Will reach out to PTLs to check if any more use cases. And might divide use cases between Taiwan lab and New Jersey lab.
      2. 11/03/21: Jack: please reach Rittwik and David to get early information into the planning process of F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

      1. 10/27/21: no update, just wait for final CLA approval to setup repos

   2. Requirements Software Architecture Committee user-59b16

      1. 10/27/21: Rittwik: Suggest Jack reach out to Rich

      2. 11/10/21: user-59b16
         1. RSAC for F release is still going on, assuming network slicing will not get fully completed for E release some backlog items like having the test done via the OTF might move to F release.
         2. We are also talking about use case for CRD and application  packaging (WG10), it's an open forum to support/propose use cases.
         3. Jack: the real question is what do we want to emphasize for next 2 releases (F and G)? guidance from whole community is expected on that.
         4. James Li: INF project mentioned that E release are 3 deployments scenarios to be tested and plan to work with other projects to run on top of the platform that could be part of future integration tests effort.
   3. OSC lab
      1. Update on 11/10/21:
         1. user-59b16 PTP grand mater is going to be installed (whichs is key for network slicing use case), Jack will monitor next week activities on the lab.
         2. Jack: added a coupe of new people to the team from AT&T who will join these activities as well.
         3. James Li: keysight is willing to help on the west coast OSC lab, we are discussing on a detailed plan, more updates in the comming weeks.

1. 1. 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 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. Zhimin Yuan 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)

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

3. Planning for Next Meeting

4. Any Other Business (AOB)

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

2021 11 10

Recording: Zoom recording

Agenda

1. Call for Scribe (minutes owner): William DIEGO 

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		James Li	x
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy	x
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy	x
   TIM	Andrea Buldorini		Scarpina Salvatore	x
   Wind River	Bin Yang		Jackie Huang

   *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 William DIEGO, seconded by John Paul Lane  . The motion is approved
      
4. Review of Today's Agenda
   1. No new items to add.

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 11/03/21: Still waiting for information from WG6. No update.
         6. Update on 11/10/21: No update.
6. Copyright update
   1. 11/03/21:
      1. Jack SSCL update : A meeting with legal team will held today. Some questions as who will be the PTL, what project will put it under this repo and also questions related to the project charter that has to be updated and then voted.
      2. Jinri : a meeting will be organised in the context of OSFG to have further discussion about SCCL for O-RAN Alliance side (Nov. 11 at 9-10PM Beijing time = 8-19AM EST = 2-3PM CET). Jinri invite the community to subscribe at the OSFG mailing list. → https://lists.o-ran-sc.org/g/toc/message/609
   2. 11/10/21: 
      1. CLA for SCCL meeting later today, more information on next session.
      2. July train publication for O-RAN specs, 24th november?
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. 11/03/21: no update

   2. 11/10/21:
      1. Thoralf Czichy new E2 API 2.0 spec (July train) should be supported for next release, does something planned to support new version on on other sub-project (e.g. O-DU side)? user-30c9d we (O-DU)can plan to support E2 API 2.0 pour F release
      2. xApps are not impacted by the E2 API 2.0 version.
      3. Thoralf Czichy platform is indepedent of service models so no impacted by new version of PMs.

8. Old business and Status of Open Action 

   1. "E" Release timeline.
      1. 10/27/21:
         1. James started to reach out to PTLs to get status, and working on unit tests of network slicing use case.
         2. Will use New Jesey Lab for E Release
         3. Jack suggests to create some documentation so other people could leverage the effort, and pull in community's participation.
      2. 11/03/21: PR of E release is expected for the first days of the next year. 
   2. OSC lab in Taiwan (Prof Ray's lab):
      1. 10/27/21: Rittwik: Prof Ray's student will update wiki to document the networks/what they have done today.(11/10/21 James Liis in contact and supporting them.)
      2. 11/10/21: user-59b16 Prof Ray's student is asking for some help (user-30c9d ) to deal with MAC scheduler (extract scheduler functionalities from ODU). We can start some discussons about it in F release (scheduler assitance as a service model)
   3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
      1. 11/10/21: Tracy Van Brakle 5G super blueprint is already taking advantage of the OSC initiated developments in ONAP (but not just ONAP). Jack: There are new functionalitiesthat are needed that we need to make sure that gets into the roadmap.
   4. "F" Release time:
      1. 10/27/21: Rittwik: will focus on O-Cloud usecase in F release, as well as the continuation of network slicing use case. Will reach out to PTLs to check if any more use cases. And might divide use cases between Taiwan lab and New Jersey lab.
      2. 11/03/21: Jack: please reach Rittwik and David to get early information into the planning process of F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

      1. 10/27/21: no update, just wait for final CLA approval to setup repos

   2. Requirements Software Architecture Committee user-59b16

      1. 10/27/21: Rittwik: Suggest Jack reach out to Rich

      2. 11/10/21: user-59b16
         1. RSAC for F release is still going on, assuming network slicing will not get fully completed for E release some backlog items like having the test done via the OTF might move to F release.
         2. We are also talking about use case for CRD and application  packaging (WG10), it's an open forum to support/propose use cases.
         3. Jack: the real question is what do we want to emphasize for next 2 releases (F and G)? guidance from whole community is expected on that.
         4. James Li: INF project mentioned that E release are 3 deployments scenarios to be tested and plan to work with other projects to run on top of the platform that could be part of future integration tests effort.
   3. OSC lab
      1. Update on 11/10/21:
         1. user-59b16 PTP grand mater is going to be installed (whichs is key for network slicing use case), Jack will monitor next week activities on the lab.
         2. Jack: added a coupe of new people to the team from AT&T who will join these activities as well.
         3. James Li: keysight is willing to help on the west coast OSC lab, we are discussing on a detailed plan, more updates in the comming weeks.

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

      1. James Li Integration and Testing (INT)
         1. 11/10/21: Ones the labs will setup next week, we will start with manual testing and in future we can automatise test via OTF. We are still working on the SMO installation part, we are able to deploy ONAP and Non-RT RIC functions (work on going).
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. 11/10/21:
            1. one of the pieces that is important for SMO is the O2 interfaces. The version that is in the lab has support for O1 interfaces (basic configuration)
            2. Acces to the lab to have access to the VM, talk with  David Kinsey who can help to facilitate the communication to do the set up.

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

      4. SUNIL SINGH RIC Applications (RICAPP) 

      5. Thoralf Czichy RIC Platform (RIC)

         1. 11/10/21: We do last check on contribution and up to dec. 7 still accepting contributions.

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

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

         1. 11/10/21: The feature are on track, and the dev willbe complited by the next sprint but in this release not sure if we can validate the L2 features in the OSC lab then we micht need to validate the e2e features in the next release.

      8. Zhimin Yuan 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)

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

3. Planning for Next Meeting

4. Any Other Business (AOB)

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

2021 11 03

Recording: zoom recording

Agenda

1. Call for Scribe (minutes owner): William DIEGO 

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		Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman	x	Manasi Padhy
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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 Bin Yang , seconded by Jinri Huang . The motion is approved
      
4. Review of Today's Agenda
   1. No new items to add.

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 11/03/21: Still waiting for information from WG6. No update.
6. Copyright update
   1. 10/27/21:
      1. Jack updates the process is pending on O-RAN alliance's creating of related directories and the approval of CLA for SCCL before OSC can setup the repo.
      2. Doug Knisely mentioned there were some comments/questions related to drfat CLA to Stefan but got no response. need keep pushing for response
      3. Tracy: wait for confirmation of 3gpp representative about the demo type of agreement can be get from 3GPP. John Keeney mentions there is an ongoing discussion for a formal aggrement. Jack suggests to ask Brian and copy him for support.
   2. 11/03/21:
      1. Jack SSCL update : A meeting with legal team will held today. Some questions as who will be the PTL, what project will put it under this repo and also questions related to the project charter that has to be updated and then voted.
      2. Jinri : a meeting will be organised in the context of OSFG to have further discussion about SCCL for O-RAN Alliance side (Nov. 11 at 9-10PM Beijing time = 8-19AM EST = 2-3PM CET). Jinri invite the community to subscribe at the OSFG mailing list. → https://lists.o-ran-sc.org/g/toc/message/609
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. 11/03/21: no update

8. Old business and Status of Open Action 

   1. "E" Release timeline.
      1. 10/27/21:
         1. James started to reach out to PTLs to get status, and working on unit tests of network slicing use case.
         2. Will use New Jesey Lab for E Release
         3. Jack suggests to create some documentation so other people could leverage the effort, and pull in community's participation.
      2. 11/03/21: PR of E release is expected for the first days of the next year.
   2. OSC lab in Taiwan (Prof Ray's lab):
      1. 10/27/21: Rittwik: Prof Ray's student will update wiki to document the networks/what they have done today.
   3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
   4. "F" Release time:
      1. 10/27/21: Rittwik: will focus on O-Cloud usecase in F release, as well as the continuation of network slicing use case. Will reach out to PTLs to check if any more use cases. And might divide use cases between Taiwan lab and New Jersey lab.
      2. 11/03/21: Jack: please reach Rittwik and David to get early information into the planning process of F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

      1. 10/27/21: no update, just wait for final CLA approval to setup repos

   2. Requirements Software Architecture Committee user-59b16

      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. ( user-30c9d/ David Kinsey )
         • update on 09/29/21: still open
      4. 10/27/21: Rittwik: Suggest Jack reach out to Rich
   3. OSC lab
      1. Update on 11/03/21 David Kinsey:
         1. Still working on that, we have (Martin Skorupski should confirm) the configuration to the ODU and the format of the PM report to be used to reach the SMO in order to manage the slice, the target is to close that before the end of the current release.
         2. For the integration part for the F release we are trying to get projets to build their test in OTF, so at the end of the release, integration should just be running the release test and verifying their execution and then certifying the release.
         3. We are still working on the lab, the Nokia IXR has been received but not been fully installed and integrated yet (still missing one cable). Then, We still working on the clock whether we can use Nokia clock , we are also trying to get the offered by Viavi that would also be deployed them into the into the blockhouse (building at the base of the antenna) where it can get a GPS antenna permanent one and it doesn't have to go into drift mode at all and it's one that we would have more or less access or control over. eed increase coordination because some equipements are shared as for TM500 (it includes OSC  lab in Taiwan).

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

      1. James Li Integration and Testing (INT)
         1. 11/03/21:
            1. Participation on SMO meeting, and being involved on installation and related tests, it is work in progress (linked to OSC lab work).
            2. Jack: Action point - Add into the E release description a check list or outline of what we're able to do.
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. 11/03/21: Trying to drive network slice automation use case scenario: progress in terms of VES event format and support in the SMO and on ODU. On the config side,we have identified some YANG models that need to be supported.

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

         1. 11/03/21: John Paul Lane: progress continues with the items for the E release looking at the Service exposure and looking at theour life cycle managemnt there's no blockers at this point.

      4. SUNIL SINGH RIC Applications (RICAPP) 

         1. 11/03/21: Matti Hiltunen:
            1. RICAPP is still working on adding the new xAPP to RAN control with Mavenir being the contributor, and then integrating more of the xApps into a complete use case with the Viavi E2 to simulator.
            2. Originally we create the repo for ONF since this is the python SDK and Facebook is working on that (they promise to contribute), but they are still trying to figure out the CLA, as soos as CLA will signed Facebook is ready to contribute. We have also requested a new repo for c++ SDK for VMware. Both of this repos are under Apache 2.0 license.

      5. Thoralf Czichy RIC Platform (RIC)

         1. 11/03/21: We're still working on the E release features most prominently on the E2 API support. Samsung is working on those 2 new repos ric-plt/ricdms. We are in the process of changing container base image from ubuntu 18.04 to 20

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

         1. 11/03/21: Jack: We use a test fixture from Radisys which will support some of open interfaces. Ganesh Shenbagaraman: we are ready to support this soon and exact date will be confimr and communicate next friday.

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

         1. 11/03/21:Ganesh Shenbagaraman: we are on track for all the release contains. SMO integration, data models and counters, we confirm our readiness of that integration (tbc)

      8. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

         1.  11/03/21:
            1. Alex Stancu We have YANG model available for the network  slicing use case there are on review on Gerrit, an also for the SIM project we will able to use those into the simulator.
            2. Tracy Van Brakle: we will be using these models within the upcoming O-RAN PoC Plugfest.

      10. Alex Stancu Simulations (SIM)

          1. E2 simulator: lacking of resources. To check with companies which contributed so far and potential new contributors

      11. Jackie Huang Infrastructure (INF)

          1. For O2 interface implementation, request to create a new repo (see above), and is working on the draft of HLD.
          2. 11/03/21: Now we have 2 new repos, work is in progress, most of the code implementation is expected to be done by the end of november.

      12. weichen ni Documentation (DOC)

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

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

3. Planning for Next Meeting

4. Any Other Business (AOB)

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

2021 10 27

Recording: zoom recording

Agenda

1. Call for Scribe (minutes owner): Bin Yang

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		James Li	x
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   Ericsson	John-Paul Lane		John Keeney	x
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy	x
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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 10/20/2021 TOC meeting approval: proposed by Bin, seconded by David. The motion is approved
      
4. Review of Today's Agenda
   1. Will the inclusion of SCCL under O-RAN Specification Code Project (SCP) present any issues with 3GPP adoption of SCCL at a future point in time? Clarification on this point is requested following an OSC meeting on Friday 22nd October. Added to agenda by John-Paul Lane.
      1. 10/27/21: Jack thinks there is no answer to this question yet until more discussion with 3GPP. 
   2. Comments on the draft proposal of new CLA for SCCL - added to agenda by John-Paul Lane:
      1. The draft proposal of new CLA for SCCL references the O-RAN SCP Technical Charter. The SCP Technical Charter refers only to the existing O-RAN software license, it does not mention SCCL. Is an update required to the SCP Technical Charter to include SCCL? Any amendments to the Technical Charter requires “a two thirds vote of the O-RAN Alliance”. Not sure if this would require a vote of O-RAN EC or O-RAN board? 
      2. 10/27/21: Jack understands the issue and will raise it up to get clarification on it.
      3. The CLA specifies “This version of the O-RAN SCCL allows an entity or person to submit contributions to the O-RAN SCP, to authorize contributions submitted by an entity’s designated employees to the O-RAN SCP, and to grant copyright and patent licenses thereto.” The intention of SCCL is to grant copyright only, not patent. Does this statement in the CLA need to be clarified / qualified?  

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.
         8. Update on 10/06/21: No update.
         9. Update one 10/13/21: No update.
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. 10/06/21: Jinri shares updates: He had meeting with Hank and some other players to discuss SCCL, detail in slices (https://lists.o-ran-sc.org/g/discuss/message/368), will continue the discussion offline
   8. 10/20/21: Jack:
      1. talked over meetings yesterday which clarified how to proceed and answered a bunch of questions. The first step is to get source file setup in O-RAN alliance , put license headers to each of those files, then they will be available for OSC downloading to OSC repo under SCCL licenses (managed as oscp license as part of o-ran-sc specification code project). people could modify them based on code management procedures.
      2. The information has been posted on o-ran alliance website and reviewed yesterday, now waiting for source materials and final approval of CLA which has been sent out and get feedback by legal team.
      3. logistics issues are open: 1, who will be PTL/Committers of this repo to manage the changes of these files, we have to setup a structure for that repo to manage the file changes; Initial thought is one repo structur for SCCL code, and INT project's PTL/Committers who will manage the changes of that repo.
      4. Jack will ask Stefan to send out the CLA today.
   9. 10/27/21:
      1. Jack updates the process is pending on O-RAN alliance's creating of related directories and the approval of CLA for SCCL before OSC can setup the repo.
      2. Doug Knisely mentioned there were some comments/questions related to drfat CLA to Stefan but got no response. need keep pushing for response
      3. Tracy: wait for confirmation of 3gpp representative about the demo type of agreement can be get from 3GPP. John Keeney mentions there is an ongoing discussion for a formal aggrement. Jack suggests to ask Brian and copy him for support.
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

   4. 10/06/21: current focus is to prepare for the board meeting before the end of this month
   5. 10/20/21:
      1. Jinri updates on preparation of board meeting at the end of this month: consolidate highlight w.r.t. OSC E release collecting from PTLs, will send it out tomorrow morning to get review from the team.
      2. Jack suggests to add update about PTL changes on OSC projects.
   6. 10/27/21:
      1. Jinri sent out slides for team reviewing: https://lists.o-ran-sc.org/g/toc/message/605
      2. Tracy, Jack: no update, just wait for final details of information for the board meeting

8. Old business and Status of Open Action 

   1. "E" Release timeline.
      1. 10/20/21: David: no update yet
      2. 10/27/21:
         1. James started to reach out to PTLs to get status, and working on unit tests of network slicing use case.
         2. Will use New Jesey Lab for E Release
         3. Jack suggests to create some documentation so other people could leverage the effort, and pull in community's participation.
   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.
      6. 10/20/21: David: no update yet
      7. 10/27/21: Rittwik: Prof Ray's student will update wiki to document the networks/what they have done today.
   3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
   4. "F" Release timeline
      1. 10/20/21:
         1. David: F release planning begins out in Jan. Equipment is not arrived yet,tried to reach out to ramsey but no response.
         2. Jack: will reach out to Ramsey in a meeting today to cover it there.
      2. 10/27/21:
         1. Rittwik: will focus on O-Cloud usecase in F release, as well as the continuation of network slicing use case. Will reach out to PTLs to check if any more use cases. And might divide use cases between Taiwan lab and New Jersey lab.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

      1. 10/27/21: no update, just wait for final CLA approval to setup repos

   2. user-59b16 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. ( user-30c9d/ David Kinsey )
         • update on 09/29/21: still open
      4. 10/27/21: Rittwik: Suggest Jack reach out to Rich
   3. OSC lab
      1. Update on 10/13/21. David Kinsey : Core emulator and UE emulator will be called back by vendors to support other activities (O-RAN Plugfest), which impacts MVP since not able to establish core/radio connection. The integration activity for release D and E will be blocked. The clearance to purchase the front haul gateway is ready, the purchasing of the equipment is ongoing.

1. 1. 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 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. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

          1. NETCONF call home procedure was implemented

          2. waiting for YANG model for slicing to be provided in order to start the implementation

          3. E2 simulator: lacking of resources. To check with companies which contributed so far and potential new contributors

      11. Jackie Huang Infrastructure (INF)

          1. Upgrade most of the components from Starlingx to align with the latest release 5.0, and to support both kubernetes and openstack as the infrastructure platform
          2. Now most of those components are in a standalone layer meta-starlingx and is has been moved to StarlingX community, which is used as the upstream layer for INF project, so for now, most of the development activity is actually happen in StarlingX community
          3. we have completed and verified for AIO-SX with kubernetes deployment, and AIO-DX deployment is in testing and bug fixing
          4. For O2 interface implementation, request to create a new repo (see above), and is working on the draft of HLD.

      12. weichen ni Documentation (DOC)

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

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

3. Planning for Next Meeting
   1. Next meeting will be chaired by Jack. Scribe in November will be William
   2. Jack: PTLs please update your status on wiki and will go through the stand-up & report out process on next week's meeting.

4. Any Other Business (AOB)

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

2021 10 20

Recording: zoom recording

Agenda

1. Call for Scribe (minutes owner): Bin Yang

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	x	Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy	x
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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 10/13/2021 TOC meeting approval: proposed by Bin, seconded by David. 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.
         8. Update on 10/06/21: No update.
         9. Update one 10/13/21: No update.
   2. INT PTL
      1. Sept. 30 2021: James from China Mobile Technology (USA) self nominated as INT PTL role View/Reply Online (#576)
         1. Update on 10/06/21: Jinri will check with Jack on how to move on
            
      2. Oct. 12 2021: Simone Crosta from HCL expressed interest in the INT PTL Role https://lists.o-ran-sc.org/g/toc/message/588
      3. Update on 10/13/21: Go through PTL election process, candidates are James and Simone, who should send email to elaborate their contribution if eletected as INT PTL by Friday, Trishan will setup a vote for TOC members to vote before next weekly meeting.
      4. Update on Oct./20/21:
         1. statements of contributions from candidates has been sent out to mail list: James(https://lists.o-ran-sc.org/g/toc/message/596), Simone Crosta (https://lists.o-ran-sc.org/g/toc/message/599)
         2. opavote link to "Vote to appoint PTL for Integration Project" sent out.
         3. James from China Mobile Technology (USA) has been elected as INT PTL
   3. Modeling change
      1. Use of two 3GPP YANG models for the closed-loop network slicing automation use case in O-RAN SC. View/Reply Online (#364)
         1. Can use it in built image, but not in source code repo, neither in documentation
         2. Jinri will arange a meeting with Hank and Stefane to clarify this kind of questions
         3. Update on 10/13/21:
            1. Jinri updates progress: 1) share sccl collataral via email, 2) reach out to Hand and Stefane, no response yet, 3) share initial understanding of where we are: can be built into image but not into code repo, neither in docs. need guidance from LFN. Try to contact Marine who manage these YANG models but no response.
            2. Jack walks through SCCL docs
         4. Update on 10/20/21:
            1. Jack: 3GPP has not adopted SCCL so 3GPP models are not covered by SCCL. all model has to be pulled as part of building process and can be redistributed along with built binaries.
      2. Extension to the API freeze deadline for the E-release based on the outcome of the above item
         1. Mahesh requests 3 weeks extension for API freeze to publish API and get consensus with John
   4. for approval (raised by Thoralf): ric-plt/ricdms repo: https://lists.o-ran-sc.org/g/toc/message/603 → 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. 10/06/21: Jinri shares updates: He had meeting with Hank and some other players to discuss SCCL, detail in slices (https://lists.o-ran-sc.org/g/discuss/message/368), will continue the discussion offline
   8. 10/20/21: Jack:
      1. talked over meetings yesterday which clarified how to proceed and answered a bunch of questions. The first step is to get source file setup in O-RAN alliance , put license headers to each of those files, then they will be available for OSC downloading to OSC repo under SCCL licenses (managed as oscp license as part of o-ran-sc specification code project). people could modify them based on code management procedures.
      2. The information has been posted on o-ran alliance website and reviewed yesterday, now waiting for source materials and final approval of CLA which has been sent out and get feedback by legal team.
      3. logistics issues are open: 1, who will be PTL/Committers of this repo to manage the changes of these files, we have to setup a structure for that repo to manage the file changes; Initial thought is one repo structur for SCCL code, and INT project's PTL/Committers who will manage the changes of that repo.
      4. Jack will ask Stefan to send out the CLA today.
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

   4. 10/06/21: current focus is to prepare for the board meeting before the end of this month
   5. 10/20/21:
      1. Jinri updates on preparation of board meeting at the end of this month: consolidate highlight w.r.t. OSC E release collecting from PTLs, will send it out tomorrow morning to get review from the team.
      2. Jack suggests to add update about PTL changes on OSC projects.

8. Old business and Status of Open Action 

   1. "E" Release timeline.
      1. 10/20/21: David: no update yet
   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.
      6. 10/20/21: David: no update yet
   3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
   4. "F" Release timeline
      1. 10/20/21:
         1. David: F release planning begins out in Jan. Equipment is not arrived yet,tried to reach out to ramsey but no response.
         2. Jack: will reach out to Ramsey in a meeting today to cover it there.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 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. ( user-30c9d/ David Kinsey )
         • update on 09/29/21: still open
   3. OSC lab
      1. Update on 10/13/21. David Kinsey : Core emulator and UE emulator will be called back by vendors to support other activities (O-RAN Plugfest), which impacts MVP since not able to establish core/radio connection. The integration activity for release D and E will be blocked. The clearance to purchase the front haul gateway is ready, the purchasing of the equipment is ongoing.

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

      1.  (TBD) Integration and Testing (INT)

         1. James Li indicates interest in contributing/leading INT project.  Jack proposes to send the information to the TOC reflector and start a discussion among the interested companies. 

      2. Mahesh Jethanandani Service Management and Orchestration (SMO)

      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. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

          1. NETCONF call home procedure was implemented

          2. waiting for YANG model for slicing to be provided in order to start the implementation

          3. E2 simulator: lacking of resources. To check with companies which contributed so far and potential new contributors

      11. Jackie Huang Infrastructure (INF)

          1. Upgrade most of the components from Starlingx to align with the latest release 5.0, and to support both kubernetes and openstack as the infrastructure platform
          2. Now most of those components are in a standalone layer meta-starlingx and is has been moved to StarlingX community, which is used as the upstream layer for INF project, so for now, most of the development activity is actually happen in StarlingX community
          3. we have completed and verified for AIO-SX with kubernetes deployment, and AIO-DX deployment is in testing and bug fixing
          4. For O2 interface implementation, request to create a new repo (see above), and is working on the draft of HLD.

      12. weichen ni Documentation (DOC)

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

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

3. Planning for Next Meeting
   1. Next meeting will be chaired by Jack. Scribe in October will be Bin Yang (Windriver)

4. Any Other Business (AOB)

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

2021 10 13

Recording:  zoom recording

Agenda

1. Call for Scribe (minutes owner): Bin Yang

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	x	Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy	x
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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 10/06/2021 TOC meeting approval: proposed by Bin, seconded by John-Paul. 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.
         8. Update on 10/06/21: No update.
         9. Update one 10/13/21: No update.
   2. INT PTL
      1. Sept. 30 2021: James from China Mobile Technology (USA) self nominated as INT PTL role View/Reply Online (#576)
         1. Update on 10/06/21: Jinri will check with Jack on how to move on
            
      2. Oct. 12 2021: Simone Crosta from HCL expressed interest in the INT PTL Role https://lists.o-ran-sc.org/g/toc/message/588
      3. Update on 10/13/21: Go through PTL election process, candidates are James and Simone, who should send email to elaborate their contribution if eletected as INT PTL by Friday, Trishan will setup a vote for TOC members to vote before next weekly meeting.
   3. Modeling change
      1. Use of two 3GPP YANG models for the closed-loop network slicing automation use case in O-RAN SC. View/Reply Online (#364)
         1. Can use it in built image, but not in source code repo, neither in documentation
         2. Jinri will arange a meeting with Hank and Stefane to clarify this kind of questions
         3. Update on 10/13/21:
            1. Jinri updates progress: 1) share sccl collataral via email, 2) reach out to Hand and Stefane, no response yet, 3) share initial understanding of where we are: can be built into image but not into code repo, neither in docs. need guidance from LFN. Try to contact Marine who manage these YANG models but no response.
            2. Jack walks through SCCL docs
      2. Extension to the API freeze deadline for the E-release based on the outcome of the above item
         1. Mahesh requests 3 weeks extension for API freeze to publish API and get consensus with John
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. 10/06/21: Jinri shares updates: He had meeting with Hank and some other players to discuss SCCL, detail in slices (https://lists.o-ran-sc.org/g/discuss/message/368), will continue the discussion offline
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

   4. 10/06/21: current focus is to prepare for the board meeting before the end of this month

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. user-59b16 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. ( user-30c9d/ David Kinsey )
         • update on 09/29/21: still open
   3. OSC lab
      1. Update on 10/13/21. David Kinsey : Core emulator and UE emulator will be called back by vendors to support other activities (O-RAN Plugfest), which impacts MVP since not able to establish core/radio connection. The integration activity for release D and E will be blocked. The clearance to purchase the front haul gateway is ready, the purchasing of the equipment is ongoing.

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

      1.  (TBD) Integration and Testing (INT)

         1. James Li indicates interest in contributing/leading INT project.  Jack proposes to send the information to the TOC reflector and start a discussion among the interested companies. 

      2. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      4. Matti Hiltunen 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. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

          1. NETCONF call home procedure was implemented

          2. waiting for YANG model for slicing to be provided in order to start the implementation

          3. E2 simulator: lacking of resources. To check with companies which contributed so far and potential new contributors

      11. Jackie Huang Infrastructure (INF)

          1. Upgrade most of the components from Starlingx to align with the latest release 5.0, and to support both kubernetes and openstack as the infrastructure platform
          2. Now most of those components are in a standalone layer meta-starlingx and is has been moved to StarlingX community, which is used as the upstream layer for INF project, so for now, most of the development activity is actually happen in StarlingX community
          3. we have completed and verified for AIO-SX with kubernetes deployment, and AIO-DX deployment is in testing and bug fixing
          4. For O2 interface implementation, request to create a new repo (see above), and is working on the draft of HLD.

      12. weichen ni Documentation (DOC)

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

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

3. Planning for Next Meeting
   1. Next meeting will be chaired by Jack. Scribe in October will be Bin Yang (Windriver)

4. Any Other Business (AOB)

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

2021 10 06

Recording:  zoom recording

Agenda

1. Call for Scribe (minutes owner): Bin Yang

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair		David Kinsey
   China Mobile	Jinri Huang Co-Chair	x	James Li
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy	x
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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/29/2021 TOC meeting approval: proposed by Andrea, seconded by David. 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.
         8. Update on 10/06/21: No update.
   2. INT PTL
      1. James from China Mobile Technology (USA) self nominated as INT PTL role View/Reply Online (#576)
         1. Update on 10/06/21: Jinri will check with Jack on how to move on
            
   3. Modeling change
      1. Use of two 3GPP YANG models for the closed-loop network slicing automation use case in O-RAN SC. View/Reply Online (#364)
         1. Can use it in built image, but not in source code repo, neither in documentation
         2. Jinri will arange a meeting with Hank and Stefane to clarify this kind of questions
      2. Extension to the API freeze deadline for the E-release based on the outcome of the above item
         1. Mahesh requests 3 weeks extension for API freeze to publish API and get consensus with John
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. 10/06/21: Jinri shares updates: He had meeting with Hank and some other players to discuss SCCL, detail in slices (https://lists.o-ran-sc.org/g/discuss/message/368), will continue the discussion offline
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

   4. 10/06/21: current focus is to prepare for the board meeting before the end of this month

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. user-59b16 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. ( user-30c9d/ David Kinsey )
         • update on 09/29/21: still open

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

      1.  (TBD) Integration and Testing (INT)

         1. James Li indicates interest in contributing/leading INT project.  Jack proposes to send the information to the TOC reflector and start a discussion among the interested companies. 

      2. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      4. Matti Hiltunen 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. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

          1. NETCONF call home procedure was implemented

          2. waiting for YANG model for slicing to be provided in order to start the implementation

          3. E2 simulator: lacking of resources. To check with companies which contributed so far and potential new contributors

      11. Jackie Huang Infrastructure (INF)

          1. Upgrade most of the components from Starlingx to align with the latest release 5.0, and to support both kubernetes and openstack as the infrastructure platform
          2. Now most of those components are in a standalone layer meta-starlingx and is has been moved to StarlingX community, which is used as the upstream layer for INF project, so for now, most of the development activity is actually happen in StarlingX community
          3. we have completed and verified for AIO-SX with kubernetes deployment, and AIO-DX deployment is in testing and bug fixing
          4. For O2 interface implementation, request to create a new repo (see above), and is working on the draft of HLD.

      12. weichen ni Documentation (DOC)

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

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

3. Planning for Next Meeting
   1. Next meeting will be chaired by Jack. Scribe in October will be Bin Yang (Windriver)

4. Any Other Business (AOB)

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

2021 09 29

Recording: Zoom recording

Agenda

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

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		Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy	x
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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. user-59b16 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. ( user-30c9d/ David Kinsey )
         • update on 09/29/21: still open

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

      1.  (TBD) Integration and Testing (INT)

         1. James Li indicates interest in contributing/leading INT project.  Jack proposes to send the information to the TOC reflector and start a discussion among the interested companies. 

      2. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      4. Matti Hiltunen 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. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW) 

      9. Martin Skorupski Operations and Maintenance (OAM)

      10. Alex Stancu Simulations (SIM)

          1. NETCONF call home procedure was implemented

          2. waiting for YANG model for slicing to be provided in order to start the implementation

          3. E2 simulator: lacking of resources. To check with companies which contributed so far and potential new contributors

      11. Jackie Huang Infrastructure (INF)

          1. Upgrade most of the components from Starlingx to align with the latest release 5.0, and to support both kubernetes and openstack as the infrastructure platform
          2. Now most of those components are in a standalone layer meta-starlingx and is has been moved to StarlingX community, which is used as the upstream layer for INF project, so for now, most of the development activity is actually happen in StarlingX community
          3. we have completed and verified for AIO-SX with kubernetes deployment, and AIO-DX deployment is in testing and bug fixing
          4. For O2 interface implementation, request to create a new repo (see above), and is working on the draft of HLD.

      12. weichen ni Documentation (DOC)

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

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

3. Planning for Next Meeting
   1. Next meeting will be chaired by Jinri Huang. Scribe in October will be Bin Yang (Windriver)

4. Any Other Business (AOB)

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

2021 09 22

Recording: Zoom recording

Agenda

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

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		James Li
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy	x
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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 SINGH (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. user-59b16 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. ( user-30c9d/ David Kinsey )

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

      1.  (TBD) Integration and Testing (INT)
      2. Mahesh Jethanandani Service Management and Orchestration (SMO)
         1. VES flow is the major use case impacting SMO project we are working on. No issues to raise

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

         1. Focus for Rel-E is on rApps and R1.
         2. Looking ad the relation with control loop definition and management in ONAP, to ensure consistenty with rApp approach. Possibly harmonized contributions to ONAP anche OSC
         3. Since specification of R1 services is not yet mature, we will focus and expand the generic service exposeure (already started in Rel-D) 

      4. Matti Hiltunen RIC Applications (RICAPP) 

         1. Wiki page on release status has been updated
         2. New RC xApp will be started. Mavenir agreed to implement it
         3. Extending Anomaly detection and traffic steering use cases. RC xApps fits into that as well, but need to also include load prediction xApp already developed in previous release. Accuracy will be improved by including geolocation (info from VIAVI simulator into Influx DB)
         4. Demo xApp "hello world" will be extended to show the functionalities.

      5. Thoralf Czichy RIC Platform (RIC)

         1. implementation is ongoing as planned.
         2. IT support request in https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22326
         3. Plan to implement a A1 mediator and  enhance E2 subscriptiom mechanism.

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

         1. No open implementation so far, just a test fixture
         2. Manasi: this will be enhanced with O1 functionality by end of October. How to deploy O-CU in OSC lab is TBD. Check with David Kinsey

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

         1. Support for multiple bearers (60% completion) per UE and multiple UEs for scheduling (20% completion). 
         2. Closed loop slicing (40%): implementation according to 3GPP Rel-15
         3. Clarified that relation with O-CU for pairing is limited to the support of slice configuration over O1 NETCONF 

      8. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW) 

         1. Mansi: working on testing and integration with O-DU high. The problems is end-to-end due to missing FHGW and p2p grandmaster

      9. Martin Skorupski Operations and Maintenance (OAM)

         1. Implementing selected OAM functionat the EDGE
         2. Support to ODUHIGH to implement VES and NETCONF for O1 interface
         3. Pre-spec implementation of PM streaming with VES (while working on the O1 CR to O-RAN)
         4. Update to the next Open Daylight version

      10. Alex Stancu Simulations (SIM)

      11. Jackie Huang Infrastructure (INF)

      12. weichen ni Documentation (DOC)

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

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

3. Planning for Next Meeting

4. Any Other Business (AOB)

   1. On behalf of TOC and OSC community, Jack thanks Matti for the great job as PTL of RICAPP project.

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

2021 09 15

Recording: Zoom recording

Agenda

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

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		James Li	x
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman		Manasi Padhy	x
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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: Jinri Huang 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: user-59b16 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 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. user-59b16 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: user-59b16to 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 Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. Matti Hiltunen 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. Zhimin Yuan 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.)

2021 09 08

Recording: Zoom Recording

Agenda

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

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		James Li	x
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen		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

   *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/01/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. 
   2. Disabling anonymous comments on OSC Wiki
      1. John Keeney proposed to disallow the feature allowing anonymous comments, in order to prevent spam on the OSC wiki pages. Motion by John Keeney, seconded by David Streibl. Motion approved.
      2. Action point: Trishan de Lanerolle to ensure anonymous comments are disabled by wiki admin. Done. Action point closed (09/08/21)
   3. 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 
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.
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

8. Old business and Status of Open Action 

   1. "E" Release timeline.
      1. Update on 08/25/21 on E release plan.
         1. Rittwik to follow up on INF project. Alex updated SIM project info. v4 of release plan to be updated on RSAC wiki.
      2. Update on 09/01/21 (Rittwik)
         1. INF project; new items were added to include some new O2-DMS approved in the O-RAN WG6 July train
         2. SIM project also added new features
         3. Network Slicing and Disaggregated VES use cases were agreed
      3. 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 
      4. 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.
      5. Action point: Jinri Huang to raise with EC on the projects dwindling with low contributions.
      6. 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.
      7. Action point: user-59b16 to add status page. PTLs will update the progress on use cases approval and new features.
   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.   
   4. Jack and Rittwik (08/25/21): Nokia equipment (fronthaul gateway) getting shipped to OSC lab. Follow up with Viavi needed for PTP grandmaster.  
   5. 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.
   6. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 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: user-59b16to document the above in the status page

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

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

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

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Jackie Huang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

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

2021 09 01

Recording: Zoom recording

Agenda

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

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		James Li	x
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   Ericsson	John-Paul Lane		John Keeney	x
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy
   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

   *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 08/25/2021 TOC meeting approval: proposed by Ganesh, seconded by Masafumi. 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. 
   2. Disabling anonymous comments on OSC Wiki
      1. John Keeney proposed to disallow the feature allowing anonymous comments, in order to prevent spam on the OSC wiki pages. Motion by John Keeney, seconded by David Streibl. Motion approved.
      2. Action point: Trishan de Lanerolle to ensure anonymous comments are disabled by wiki admin.
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.
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
   1. Action point: Jinri to organize release statement and PR for "D" Release
      1. Jinri's update (08/11/21): EC approved content but text is still being refined. Quotes from companies mentioned in previous releases are not accepted. The other criterion is level of contribution. PR expected next week.

8. Old business and Status of Open Action Items

   1. Action point: PTLs help is needed to provide a list of files, which will use SCCL license. This is closed.
   2. D Release
      1. Action point: Mahesh Jethanandani to add SMO to D-release image list page: D Release Docker Image List - Integration and Testing - Confluence (o-ran-sc.org). Mahesh to follow up. 
      2. Action point:  Jinri Huang  to follow up with Intel on O-DU-Low representation.
   3. D Release Maintenance (Update on 09/01/21)
      1. Jack: D Release Maintenance was approved and projects are expected to make the respective branches available
      2. Manasi: O-DU High is aligning with OAM and Non-RT RIC PTLs on the process.
   4. "E" Release timeline.
      1. Update on 08/25/21 on E release plan.
         1. Rittwik to follow up on INF project. Alex updated SIM project info. v4 of release plan to be updated on RSAC wiki.
      2. Update on 09/01/21 (Rittwik)
         1. INF project; new items were added to include some new O2-DMS approved in the O-RAN WG6 July train
         2. SIM project also added new features
         3. Network Slicing and Disaggregated VES use cases were agreed
      3. 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.
      4. 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.
      5. Action point: Jinri Huang to raise with EC on the projects dwindling with low contributions. 
         1. Rittwik flagged lack of progress in certain projects (Infra, O-DU-Low, O-CU) and asked Jinri to highlight to EC. Standing up on O-Cloud is still not happening. Jinri to discuss with Rittwik offline.
         2. Jinri to follow up with Prof Ray (Taiwan Uty) on their participation in lab setup and integration. Rittwik to share the email ID of Prof Ray.
      6. Action point: user-59b16 to add status page. PTLs will update the progress on use cases approval and new features.
   5. 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
   6. 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.   
   7. Jack and Rittwik (08/25/21): Nokia equipment (fronthaul gateway) getting shipped to OSC lab. Follow up with Viavi needed for PTP grandmaster.
   8. Repo clean-up:
      1. Action Point: Trishan de Lanerolle to close all not active repos.
         1. All PTLs to follow up on repos not active and communicate to Trishan. 
      2. Matti raised the point of legacy repos to be archived. Jack: this need formal approval by TOC at the next meeting 
   9. Update on scorecard: Consolidating the scorecards of sub projects will lead to new analytics. No action needed from anyone.
      1. 09/01/21 - Trishan: new charts will come up in the next month in the analytics platform.  
   10. 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.
   11. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 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: user-59b16to document the above in the status page

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

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

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

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Jackie Huang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

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

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

    1. Vote on Archiving of legacy repos to take place at the next TOC meeting
11. Planning for Next Meeting

12. Any Other Business (AOB)

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

2021 08 25

Recording: Zoom recording

Agenda

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

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		James Li	x
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   Ericsson	John-Paul Lane		John Keeney	x
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy	x
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman	x	Manasi Padhy
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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 08/18/2021 TOC meeting approval: proposed by Ganesh, seconded by Andrea. 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.
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.
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
   1. Action point: Jinri to organize release statement and PR for "D" Release
      1. Jinri's update (08/11/21): EC approved content but text is still being refined. Quotes from companies mentioned in previous releases are not accepted. The other criterion is level of contribution. PR expected next week.

8. Old business and Status of Open Action Items

   1. Action point: PTLs help is needed to provide a list of files, which will use SCCL license. This is closed.
   2. D Release
      1. Action point: Mahesh Jethanandani to add SMO to D-release image list page: D Release Docker Image List - Integration and Testing - Confluence (o-ran-sc.org). Mahesh to follow up. 
      2. Action point:  Jinri Huang  to follow up with Intel on O-DU-Low representation.
   3. D Release Maintenance (Update on 08/18/21)
      1. Ganesh and Manasi updated on the status of testing with O-DU-Low. Testing currently blocked by PTP clock 
      2. Manasi: O-DU-High and O-DU-Low pair-wise testing is completed.
      3. John Keeney (Non-RT RIC) , Martin confirmed code freeze.
      4. Maintenance release approval. Motion proposed by Jack and seconded by David. Motion approved with the mention that O-DU-High and O-DU-high were only pair tested.
   4. "E" Release timeline.
      1. Update on 08/25/21 on E release plan.
         1. Rtitwik to follow up on INF project. Alex updated SIM project info. v4 of release plan to be updated on RSAN wiki.
      2. Mahesh flagged the disaggregated VEs implementation. David Kinsey is investigating this.
      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.
      4. Action point: Jinri Huang to raise with EC on the projects dwindling with low contributions. 
         1. Rittwik flagged lack of progress in certain projects (Infra, O-DU-Low, O-CU) and asked Jinri to highlight to EC. Standing up on O-Cloud is still not happening. Jinri to discuss with Rittwik offline.
         2. Jinri to follow up with Prof Ray (Taiwan Uty) on their participation in lab setup and integration. Rittwik to share the email ID of Prof Ray.
      5. Rittwik to add status page 
   5. 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.
   6. Jack (08/25/21): Challenges in test and integration activities. Looking for volunteers to fill this gap.
   7. Jack and Rittwik (08/25/21): Nokia equipment (fronthaul gateway) getting shipped to OSC lab. Follow up with Viavi needed for PTP grandmaster.
   8. Repo clean-up:
      1. Action Point: Trishan de Lanerolle to close all not active repos.
         1. All PTLs to follow up on repos not active and communicate to Trishan. 
   9. Update on scorecard: Consolidating the scorecards of sub projects will lead to new analytics. No action needed from anyone.
   10. 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.
   11. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 Requirements Software Architecture Committee

   3. Integration and Test (PTL needed)

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

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

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

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Jackie Huang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

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

2021 08 18

Recording: Zoom recording

Agenda

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

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	x	Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy	x
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman	x	Manasi Padhy
   TIM	Andrea Buldorini	x	Scarpina Salvatore
   Wind River	Bin Yang	x	Jackie Huang

   *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 08/11/2021 TOC meeting approval: proposed by Ganesh, seconded by Jinri. Motion approved.
   2. Minutes for 08/04/21 TOC meeting approval: proposed by Ganesh, seconded by Jinri. 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. 
6. Copyright update
   1. Update from Jack (08/18/21): ASN definitions and models from O-RAN spec to be brought in OSC repos under SCCL. EC to approve the list.
   2. List of requests to be compiled. Thoralf emailed TOC group for near RT RIC ASN requests.
   3. Jinri: EC requested a list of examples first to facilitate the process. Request to other PTLs to provide examples.
   4. Martin: Submitted in email a list of the YANG models we are interested in. Will add models from 2 more specifications.
   5. Tracy, Martin: We also have a list of YANG models under discussion and not approved yet.
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
   1. Action point: Jinri to organize release statement and PR for "D" Release
      1. Jinri's update (08/11/21): EC approved content but text is still being refined. Quotes from companies mentioned in previous releases are not accepted. The other criterion is level of contribution. PR expected next week.

8. Old business and Status of Open Action Items

   1. Action point: PTLs help is needed to provide a list of files, which will use SCCL license
      1. Jinri brought this up with O-RAN TSC. EC ready to review example files to facilitate the definition. The example files could be specification sections/tables/charts that we plan to use in OSC. 
      2. Thoralf highlighted example from O-RAN WG3 E2AP spec (Section 9.3). He will initiate a new discussion in the mailing list.
      3. John Keeney requested more clarity on SCCL license and its use for existing files in repos. Should it be used if code uses specs or if we generate code from specs? Need more guidance from TOC or legal team.
      4. Trishan asked if code files will be stored separately under this license.
      5. Jinri will work with Stefan to provide some example files and guidance.
   2. D Release
      1. Action point: Mahesh Jethanandani to add SMO to D-release image list page: D Release Docker Image List - Integration and Testing - Confluence (o-ran-sc.org). Mahesh to follow up. 
      2. Action point:  Jinri Huang  to follow up with Intel on O-DU-Low representation.
      3. O-DU-High PTL (Manasi) to update release download information. Completed during the meeting.
   3. D Release Maintenance
      1. Update from Manasi (08/18/21): Further e2e testing is blocked due to lack of local GM clock.  Rittwik said Viaivi is working on providing this to OSC lab.
      2. Decision of pending code changes and release readiness to be closed in TOC meeting on 8/25.
      3. Non-RT RIC: John Paul Lane to confirm if there are any open issues.
      4. OAM: Martin: OAM code is good to go.
      5. O-DU High: Manasi updated code is ready.
      6. O-DU Low: Manasi updated that some testing is pending based on the latest fixes.
      7. SIM: Alex said no fixes needed.
      8. Maintenance release cannot be approved due to lack of updates from other PTLs.
   4. "E" Release timeline.
      1. Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
         1. Action point: user-59b16 to make an overview presentation together with PTLs in E-release timeframe
      2. 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.
      3. Action point: user-59b16will reach out every PTL and go through necessary E release content items. Action closed.
         1. Rittwik presented E release contents in detail. Disaggregated VES and network slicing.
         2.  Disaggregated VES agent with decoupling of transport and Pub/sub mechanism. FM/PM coordination work in WG10 (Nov release train).
         3. Mahesh raised a point on dependency on Nov train spec release for OSC E release.
         4. Networks slicing feature proposed by Radisys. Closed lop slice assurance. 
         5. SMO, Non-RT RIC, OAM and O-DU-High project teams have reviewed call flows.
         6. Jinri: Is this targeted for an video quality kind of application? Rittwik said this is defined generically for any such use.
         7. Jack: Are notifications to SMO standardized? Mahesh said E release implementation will be pre-spec. Discussion ongoing in WG5.
         8. Rittwik: PM counters and r1 APIs will be pre-spec as well.
         9. Manasi: we can use basic counters already available in July train.
         10. Discussed other minor work items of E release from each component.
         11. RICAPP: Discussed LP, AD, QP, Bouncer xApps. Exploring intetest from xApps from Mavenir, Viavi and CMCC.
         12. O-DU-High: Network slicing, L2 specific features, scaling for multi-UE and multi-bearer. E2 enhancments as stretch goal.
         13. OAM: NW slicing, ODL Silicon upgrade, deployment and automation aspects in a CNF/K8s environment.
         14. Rittwik again highlighted the projects in trouble as they are lagging: INF, O-DU-Low and O-CU
         15. Bin Yang: INF PTL will come up with a plan. Action Point: Bin Yang /WindRiver will provide plan for INF.
         16. SMO and other project o add to slides shared by Rittwik.
         17. Jinri: New PTL from O-DU-Low wil be Luis (Intel). 
         18. Jack: Intel PTL should go to RSAC to represent O-DU-Low.
         19. Rtittwik: Projects are ready to start the sprints in E release. Action Point: Rittwik to set up a page for release item list update by PTLs.
         20. Mahesh: SMO team will discuss to waht extent the disaggregation requirements can be met.
      4. Action point: Jinri Huang to raise with EC on the projects dwindling with low contributions. 
         1. Rittwik flagged lack of progress in certain projects (Infra, O-DU-Low, O-CU) and asked Jinri to highlight to EC. Standing up on O-Cloud is still not happening. Jinri to discuss with Rittwik offline.
         2. Jinri to follow up with Prof Ray (Taiwan Uty) on their partcipation in lab setup and integration. Rittwik to share the email ID of Prof Ray.
      5. Rittwik to add status page 
   5. OSC lab in Taiwan (Prof Ray's lab):
      1. Rittwik discussed with Prof Ray (Taiwan).  The lab is ready and the Prof Ray's team is volunteering for more work. Prof Ray to attend next TOC meeting.
   6. Repo clean-up:
      1. Action Point: Trishan de Lanerolle to slose all not active repos.
         1. All PTLs to follow up on repos not active and communicate to Trishan. 
   7. Update on scorecard: Consolidating the scorecards of sub projects will lead to new analytics. No action needed from anyone.
   8. Action point: Trishan de Lanerolle to follow up on partcipation 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.
   9. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 Requirements Software Architecture Committee

   3. Integration and Test (PTL needed)

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

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

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

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Jackie Huang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

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

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

    1. Discussion on copyright and E release prioritized
11. Planning for Next Meeting

12. Any Other Business (AOB)

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

2021 08 11

Recording: Zoom recording

Agenda

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

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair		David Kinsey	x
   China Mobile	Jinri Huang Co-Chair	x	James Li
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy	x
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman	x	Manasi Padhy
   TIM	Andrea Buldorini		Scarpina Salvatore
   Wind River	Bin Yang		Jackie Huang

   *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: For the 08/04/2021 TOC meeting minutes to be approved next week as minutes were published just before the meeting
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. 
6. Copyright update
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
   1. Action point: Jinri to organize release statement and PR for "D" Release
      1. Jinri's update (08/11/21): EC approved content but text is still being refined. Quotes from companies mentioned in previous releases are not accepted. The other criterion is level of contribution. PR expected next week.

8. Old business and Status of Open Action Items

   1. Action point: PTLs help is needed to provide a list of files, which will use SCCL license
      1. Jinri brought this up with O-RAN TSC. EC ready to review example files to facilitate the definition. The example files could be specification sections/tables/charts that we plan to use in OSC. 
      2. Thoralf highlighted example from O-RAN WG3 E2AP spec (Section 9.3). He will initiate a new discussion in the mailing list.
      3. John Keeney requested more clarity on SCCL license and its use for existing files in repos. Should it be used if code uses specs or if we generate code from specs? Need more guidance from TOC or legal team.
      4. Trishan asked if code files will be stored separately under this license.
      5. Jinri will work with Stefan to provide some example files and guidance.
   2. D Release
      1. Action point: Mahesh Jethanandani to add SMO to D-release image list page: D Release Docker Image List - Integration and Testing - Confluence (o-ran-sc.org). Mahesh to follow up. 
      2. Action point:  Jinri Huang  to follow up with Intel on O-DU-Low representation.
      3. O-DU-High PTL (Manasi) to update release download information. Completed during the meeting.
   3. D Release Maintenance
      1. Non-RT RIC: John Paul Lane to confirm if there are any open issues.
      2. OAM: Martin: OAM code is good to go.
      3. O-DU High: Manasi updated code is ready.
      4. O-DU Low: Manasi updated that some testing is pending based on the latest fixes.
      5. SIM: Alex said no fixes needed.
      6. Maintenance release cannot be approved due to lack of updates from other PTLs.
   4. "E" Release timeline.
      1. Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
         1. Action point: user-59b16 to make an overview presentation together with PTLs in E-release timeframe
      2. 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.
      3. Action point: user-59b16will reach out every PTL and go through necessary E release content items
         1. Rittwik: Details of major use cases captured in RSAC wiki. Disaggregated VES and network slicing.
         2. Updates in other components are captured by project PTLs.
         3. Rtitwik to present detailed update in the next week on major use cases and key features project wise.
         4. Manasi to upload ppt on WIki page. Near RT RIC information already available. Matti to email update to Rittwik.
         5. Martin analyzing the impacts due to network slicing.
      4. Action point: Jinri Huang to raise with EC on the projects dwindling with low contributions. 
         1. Rittwik flagged lack of progress in certain projects (Infra, O-DU-Low, O-CU) and asked Jinri to highlight to EC. Standing up on O-Cloud is still not happening. Jinri to discuss with Rittwik offline.
         2. Jinri to follow up with Prof Ray (Taiwan Uty) on their partcipation in lab setup and integration. Rittwik to share the email ID of Prof Ray.
      5. Rittwik to add status page 
   5. Repo clean-up:
      1. Action Point: Trishan de Lanerolle to slose all not active repos.
         1. All PTLs to follow up on repos not active and communicate to Trishan. 
   6. Update on scorecard: Consolidating the scorecards of sub projects will lead to new analytics. No action needed from anyone.
   7. Action point: Trishan de Lanerolle to follow up on partcipation 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 ONES201. 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.
   8. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 Requirements Software Architecture Committee

   3. Integration and Test (PTL needed)

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

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

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

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Jackie Huang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

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

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

    1. Streamlining the analytics using Scorecard (Trishan)
11. Planning for Next Meeting

12. Any Other Business (AOB)

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

2021 08 04

Recording: Zoom recording link

Agenda

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

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair		David Kinsey	x
   China Mobile	Jinri Huang Co-Chair	x	James Li
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman	x	Manasi Padhy
   TIM	Andrea Buldorini		Scarpina Salvatore	x
   Wind River	Bin Yang	x	Jackie Huang

   *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: For the 07/28/2021 TOC meeting minutes, motion by Juha Oravainen, seconded by Ganesh Shenbagaraman. Motion passed
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. 
6. Copyright update
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
   1. Action point: Jinri to organize release statement and PR for "D" Release
      1. Jinri's update (08/04/21): EC decided to not use quotes from previous release. Quotes from 2 companies could not be accommodated. Further update on- PR status from Jinri over email.

8. Old business and Status of Open Action Items

   1. Action point: PTLs help is needed to provide a list of files, which will use SCCL license
      1. John Keeney requested more clarity on SCCL license and its use for existing files in repos. Should it be used if code uses specs or if we generate code from specs? Need more guidance from TOC or legal team.
      2. Trishan asked if code files will be stored separately under this license.
      3. Jinri will work with Stefan to provide some example files and guidance.
   2. D Release
      1. Action point: Mahesh Jethanandani to add SMO to D-release image list page: D Release Docker Image List - Integration and Testing - Confluence (o-ran-sc.org). Mahesh to follow up. 
      2. Trishan updated that Felix is working on D release page. Issues in the web page (links, incorrect info, tarball downlaod) pointed out by others.
   3. D Release Maintenance
      1. Non-RT RIC: A couple of fixes are being incorporated.
      2. O-DU High: O-DU low integration ongoing. 1 optimization fix included.
   4. "E" Release timeline.
      1. Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
         1. Action point: user-59b16 to make an overview presentation together with PTLs in E-release timeframe
      2. 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 O1.
      3. Action point: user-59b16will reach out every PTL and go through necessary E release content items
         1. Rittwik: I discussed with Thoralf and will discuss with other PTLs as well
      4. Rittwik to add status page 
   5. Repo clean-up:
      1. Jack: Every repo should be attached to a project with a PTL. House-keeping and due diligence are the responsibility of the PTL.
         1. Trishan de Lanerolle: I'll follow up with the Release engineering
   6. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 Requirements Software Architecture Committee

   3. Integration and Test (PTL needed)

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

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

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

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Jackie Huang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

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

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

    1. Streamlining the analytics using Scorecard (Trishan)
11. Planning for Next Meeting

12. Any Other Business (AOB)

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

2021 07 28

Recording: Link to Zoom recording

Agenda

1. Call for Scribe (minutes owner): Juha Oravainen

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		James Li	X
   Deutsche Telekom	David Streibl	X	Ondřej Hudousek
   Ericsson	John-Paul Lane	X	John Keeney
   NTT DOCOMO	Masafumi Masuda	X	Anil Umesh
   Nokia	Juha Oravainen	X	Thoralf Czichy
   Orange	William Diego	X	Vincent Danno
   Radisys	Ganesh Shenbagaraman	X	Sachin Srivastava
   TIM	Andrea Buldorini	X	Scarpina Salvatore
   Wind River	Bin Yang	X	Jackie Huang

   *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: For the 07/21/2021 TOC meeting minutes, motion by Juha Oravainen , seconded by Ganesh Shenbagaraman Motion passed
4. Review of Today's Agenda

5. Release Votes and Approval

   1. New PTL for O-DU High project
      1. Decision Nominate Manasi Padhy to the PTL role of O-DU High project. Motion by Ganesh Shenbagaraman, seconded by user-2057e. Motion passed
   2. AAL project
      1. Action point: Trishan to check if your have to sign a new agreement for the repo.
         1. A clean path forward here would be to have a separate CCLA / ICLA for just the BSD repo(s). The repo(s) for this project would then use BSD-3-Clause as the project's outbound license, as preferred by the WG6
         2. That CCLA/ICLA would be substantively based on the Apache Software Foundation's CCLA and ICLA (which are widely used across open source projects), with some administrative changes to better align with how the EasyCLA process works for managing CLAs. The existing O-RAN SC repos would continue to use the existing CLAs, the new one would only be for the BSD repo(s)
         3. The decision on whether to take this approach could be voted on and approved by the O-RAN SC's TOC, as part of their responsibilities under the Technical Charter. Note that under section 7(c), it would need to be a 2/3 vote of the entire TOC to grant the project license exception to use BSD-3-Clause here instead of Apache-2.0. Also we would have some administrative and configuration work on the back end to set up and enforce the 3rd CLA
      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
6. Copyright update
   1. Jack: I got the approved license and frequently asked questions
   2. Jack: Needed info will be updated to O-RAN Software Community — O-RAN ALLIANCE page
   3. Jack: Everything should be in place for the E Release 
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
   1. Action point: Jinri to organize release statement and PR for "D" Release
   2. Rittwik: There is O-RAN Plugfest coming. Is there any wiki pages for this?
   3. Jack: I'll take a look

8. Old business and Status of Open Action Items

   1. Action point: PTLs help is needed to provide a list of files, which will use SCCL license
   2. D Release
      1. Action point: Mahesh Jethanandani to add SMO to D-release image list page: D Release Docker Image List - Integration and Testing - Confluence (o-ran-sc.org)
   3. D Release Maintenance
      1. Jack: The maintenance release is planned to be ready in about two weeks
      2. Jack: ODULOW is working on a maintenance release item
      3. John: Non RT RIC is pushing couple of small bug fixes
      4. Mahesh: SMO is making small changes for measurement events
      5. Manasi: ODUHIGH is optimizing code a little bit and we are working with ODULOW for the e2e integration to happen 
      6. Jack: PTLs need to update D-Release pages about the information on the release
   4. "E" Release timeline.
      1. Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
         1. Action point: user-59b16 to make an overview presentation together with PTLs in E-release timeframe
      2. Action point: Ganesh Shenbagaraman Provide an update, if O1 is going to be available anytime soon in Radisys O-CU test fixture?
      3. Action point: user-59b16will reach out every PTL and go through necessary E release content items
         1. Rittwik: I discussed with Thoralf and will discuss with other PTLs as well
      4. Rittwik to add status page 
   5. Repo clean-up:
      1. Jack: Every repo should be attached to a project with a PTL. House-keeping and due diligence are the responsibility of the PTL.
         1. Trishan de Lanerolle: I'll follow up with the Release engineering
   6. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 Requirements Software Architecture Committee

      1. Rittwik: We have two concrete proposals right now. One is disaggregated VES agent where the proposal is to decouple the transport. The goal is to support multiple end consumers and we  are discussing this in RSAC
      2. Jack: What pieces would be affected by this?
      3. Rittwik: SMO and OAM projects for sure and perhaps Simulator project
      4. Martin: The question is if ODU and other projects are affected?
      5. Rittwik: We can check
      6. Jack: It is important to make sure you talk to all the PTLs and clearly document which projects are affected and in which magnitude
      7. Ritttwik: Sure. The other proposal is Network Slicing where ODU is talking with NONRTRIC and assure a particular slice. So, the monitoring will happen and then based on that monitoring the slice level performance metric will get adjusted
      8. Jack: is the underlying capability that you need to do this present or is it going to generate some underlying capabilities that have to be extended?
      9. Rittwik: The underlying capability has to be extended.
      10. Ganesh: This will be a multi release commitment
      11. Rittwik  I also had a call with Thoralf before he left on vacation about O1 support from the near RT RIC. Thoralf had some ideas, which I haven't put to the slides yet
      12. Jack: I think you need to put ODULOW support and capability on the agenda for the discussion. Currently we don't get much representation from Intel- Maybe Philippe is somebody we can  talk to
      13. Rittwik: There is a lot of specifications that is coming in O2. I was wondering, if Infra project could implement some of these O2-D and O2-M protocols that are being specified
      14. Rittwik: I need to reach out also other PTLs
      15. Jack: From overall O1 capability you need to talk with Ganesh about the ODU Low test fixture
      16. Jack: Discuss also with Mahesh what is the roadmap of SMO project

   3. Integration and Test (PTL needed)

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

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

      6. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Jackie Huang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

      12. (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. William DIEGO will be having vacation in August, Ganesh Shenbagaraman will take care of the scribe role then
    2. Jack will be out on vacation first two weeks of August. Jinri will cover these weeks

12. Any Other Business (AOB)

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

2021 07 21

Recording: Link to Zoom recording

Agenda

1. Call for Scribe (minutes owner): Juha Oravainen

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		James Li	X
   Deutsche Telekom	David Streibl	X	Ondřej Hudousek
   Ericsson	John-Paul Lane		John Keeney	X
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Nokia	Juha Oravainen	X	Thoralf Czichy
   Orange	William Diego	X	Vincent Danno
   Radisys	Ganesh Shenbagaraman	X	Sachin Srivastava
   TIM	Andrea Buldorini	X	Scarpina Salvatore
   Wind River	Bin Yang	X	Jackie Huang

   *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: For the 07/14/2021 TOC meeting minutes, motion by Juha Oravainen , seconded by user-2057e. Motion passed
4. Review of Today's Agenda
   1. William DIEGO will be having vacation in August, Ganesh Shenbagaraman will take care of the scribe role then

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.
         1. A clean path forward here would be to have a separate CCLA / ICLA for just the BSD repo(s). The repo(s) for this project would then use BSD-3-Clause as the project's outbound license, as preferred by the WG6
         2. That CCLA/ICLA would be substantively based on the Apache Software Foundation's CCLA and ICLA (which are widely used across open source projects), with some administrative changes to better align with how the EasyCLA process works for managing CLAs. The existing O-RAN SC repos would continue to use the existing CLAs, the new one would only be for the BSD repo(s)
         3. The decision on whether to take this approach could be voted on and approved by the O-RAN SC's TOC, as part of their responsibilities under the Technical Charter. Note that under section 7(c), it would need to be a 2/3 vote of the entire TOC to grant the project license exception to use BSD-3-Clause here instead of Apache-2.0. Also we would have some administrative and configuration work on the back end to set up and enforce the 3rd CLA
      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
6. Copyright update
   1. Jack is working with Zbynek and Stefan to get SCCL topic to be updated to O-RAN Alliance web pages so that we can have the license published as an option. We also have to get a CLA in place for people contributing underneath that license
   2. Jack: 3GPP work will most probably continue in September
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
   1. Action point: Jinri to organize release statement and PR for "D" Release
      1. Discussion is still ongoing in EC

8. Old business and Status of Open Action Items

   1. Action point: PTLs help is needed to provide a list of files, which will use SCCL license
      1. Jack: Do we want to have a branch that deals with all the models and another branch dealing with the code and another one with documentation? Do we want to organize this by project? There are different kind of options how we want to organize. If PTLs can think about this, then we'll bring it up again next week
   2. New PTL for the Infrastructure project is needed. Action point: Xiaohua Zhangwill propose a new PTL via e-mail
      1. Mail from July 14: toc@lists.o-ran-sc.org | Need step down from the PTL of INF, and propose Jackie Huang to be PTL of INF
         1. Bin: I support Xiaohua's proposal to nominate Jackie Huang as a new PTL
         2. Jack: Does anyone else have any comments or want to nominate someone for this PTL role?
         3. Decision: Nominate Jackie Huang to the PTL role of Infrastructure project. Motion by Bin Yang, seconded by Juha Oravainen Motion passed
   3. D Release
      1. Action point: Mahesh Jethanandani to add SMO to D-release image list page: D Release Docker Image List - Integration and Testing - Confluence (o-ran-sc.org)
         1. Mahesh: I'll work with Trishan to make sure that link is available
   4. "E" Release timeline.
      1. Action point: Jack to create "E" Release timeline and publish.
         1. This is now published in the Releases page: Releases - Releases - Confluence (o-ran-sc.org) 
      2. Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
         1. Action point: user-59b16 to make an overview presentation together with PTLs in E-release timeframe
      3. Action point: Ganesh Shenbagaraman Provide an update, if O1 is going to be available anytime soon in Radisys O-CU test fixture?
         1. Manasi: We need to have some internal discussion and give update next week
         2. Mahesh: Do we have O-CU as a project in E-release?
         3. Jack: Radisys has made available a test fixture O-CU, which will be available for testing in the lab. We do not have a code project
      4. Action point: user-59b16will reach out every PTL and go through necessary E release content items
         1. Rittwik: I discussed with Thoralf and will discuss with other PTLs as well
   5. Repo clean-up:
      1. Jack: Every repo should be attached to a project with a PTL. House-keeping and due diligence are the responsibility of the PTL.
         1. Trishan: I'll follow up with the Release engineering. I think they were running an audit to see the list of the empty reports
   6. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
   7. PTL company change.
      1. Jack: I got a message from Mahesh, PTL of SMO. He has moved from VMware to Juniper. We have to decide to do going forward. Hopefully he can attend next meeting and have a dialogue
      2. Jack: How you Mahesh see this work is going forward?
      3. Mahesh: People who have been working on the project are still committed to continue the work in the E-release
      4. Jack: The key question here is what are the E-release requirements and can you come up with a plan to deliver against those
      5. Jack: If you Mahesh are committed and interested in continuing in the role and there are no other questions then we'll continue and look towards the success of the project
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 Requirements Software Architecture Committee

   3. Integration and Test (PTL needed)

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

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

      6. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Jackie Huang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

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

2021 07 14

Recording: Link to Zoom recording

Agenda

1. Call for Scribe (minutes owner): Juha Oravainen

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	X	Ondřej Hudousek
   Ericsson	John-Paul Lane	X	John Keeney
   NTT DOCOMO	Masafumi Masuda	X	Anil Umesh
   Nokia	Juha Oravainen	X	Thoralf Czichy
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman	X	Sachin Srivastava
   TIM	Andrea Buldorini	X
   Wind River	Xiaohua Zhang	X	Jackie Huang

   *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: For the 07/07/2021 TOC meeting minutes, motion by Juha Oravainen , seconded by John Paul Lane . Motion passed
4. Review of Today's Agenda
   1. Jack will be out on vacation first two weeks of August. Jinri will cover these weeks
   2. Bin Yangwill be Wind River's new TOC representative starting next week
   3. New PTL for the Infrastructure project is needed. Action point: Xiaohua Zhangwill propose a new PTL via e-mail
   4. John: Does anybody have any comments to this mail "OSC: LF Nexus repo for helm charts. (o-ran-sc.org)" This would make it much easier to reuse OSC components
      1. Trishan: Can you make a support ticket?
      2. Jack: We might need to organize a little bit around it to make it easier for the release engineering to manage them if each project has their own way of where the helm charts sit and how they're organized.
      3. Martin: That's a good approach. 
      4. Jack:  So, this should just be an update to the best practices
      5. Trishan: That would be a question if it's a recommendation or requirement. If it becomes a requirement, then probably a vote would be helpful. Otherwise if it's a recommendation, then update the best practices should be sufficient
      6. Jack: Let's go and see how it works out

5. Release Votes and Approval

   1. D Release
      1. Action point: Jinri to organize release statement and PR for "D" Release
         1. PR is currently suspended, it will be discussed in the EC meeting
      2. SMO is missing from D release docker release image list: D Release Docker Image List - Integration and Testing - Confluence (o-ran-sc.org) 
         1. Action point: Mahesh Jethanandani to add SMO to D-release image list page 
   2. AAL project
      1. Action point: Trishan to check if your have to sign a new agreement for the repo.
         1. A clean path forward here would be to have a separate CCLA / ICLA for just the BSD repo(s). The repo(s) for this project would then use BSD-3-Clause as the project's outbound license, as preferred by the WG6
         2. That CCLA/ICLA would be substantively based on the Apache Software Foundation's CCLA and ICLA (which are widely used across open source projects), with some administrative changes to better align with how the EasyCLA process works for managing CLAs. The existing O-RAN SC repos would continue to use the existing CLAs, the new one would only be for the BSD repo(s)
         3. The decision on whether to take this approach could be voted on and approved by the O-RAN SC's TOC, as part of their responsibilities under the Technical Charter. Note that under section 7(c), it would need to be a 2/3 vote of the entire TOC to grant the project license exception to use BSD-3-Clause here instead of Apache-2.0. Also we would have some administrative and configuration work on the back end to set up and enforce the 3rd CLA
      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. Action point: Ganesh to provide an update from ODU point of view.
6. Copyright update
   1. Jack: We need to work to put together procedures and methods to support SCCL license
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
   1. Jinri: SCCL license was approved by the board two weeks ago. As a follow-up, EC is asking a list of files, which will use SCCL license
      1. Action point: PTLs help is needed to provide a list of files, which will use SCCL license
   2. Jinri: WG6 will release only Stage 1 and Stage 2 in July train but Stage 3 is not in the content because of some legal concerns
      1. Jack: We're waiting for clarification from WG6, if we should make new AAL repo or not

8. Old business and Status of Open Action Items

   1. "E" Release timeline.
      1. Action point: Jack to create "E" Release timeline and publish.
      2. Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
         1. Action point: user-59b16 to make an overview presentation together with PTLs in E-release timeframe
      3. Action point: Ganesh Shenbagaraman Provide an update, if O1 is going to be available anytime soon in Radisys O-CU test fixture?
         1. Ganesh: Investigation was started and we should be able to give an update on this by next week
      4. Action point: user-59b16will reach out every PTL and go through necessary E release content items
         1. Rittwik: I discussed with Thoralf and will discuss with other PTLs as well
   2. Repo clean-up:
      1. Jack: Every repo should be attached to a project with a PTL. House-keeping and due diligence are the responsibility of the PTL.
         1. Trishan: We ran the report and took an action on archiving the empty ones.
         2. Jack: And then making sure that all the other ones are attached to some project, which has a PTL so that we can get track the responsibility
         3. Trishan: Yes, and also as a reminder, projects should always have updated info.yaml file with the list of approved committers
   3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.
   4. PTL company change.
      1. Jack: I got a message from Mahesh, PTL of SMO. He has moved from VMware to Juniper. We have to decide to do going forward. Hopefully he can attend next meeting and have a dialogue.
      2. Jack: PTL role belongs to the person, not to the company but the person still have to be able to contribute
      3. Jack: We need to have a discussion here, do we need to open it back up for nomination for the PTL role and reconsider options at this point or not
      4. John-Paul: Should we have a process around PTL elections generally?
      5. Jack: The election window is the March timeframe for normal elections. That's the general principle but we have not been doing that because the projects have been so narrowly participated. Meaning that most projects are a single company project and there's not been enough committers to hold an election. To get things started the TOC was voting on the PTLs till there was enough participation in any project to hold an election
      6. John-Paul: Should we at least have a nomination and a review once a year until we can get that diversity across the different projects?
      7. Jack: Yes, and I think we talked about it briefly in the March window, but I don't think anyone raised the concern of a change
      8. Jack: I want to have the discussion is the SMO going to be the first project, where we have a diverse set of contributors enough to hold an election and try to understand how we should move forward
      9. Rittwik: should we have secondary PTLs in projects?
      10. Jack: Committers can take care of this in general
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 Requirements Software Architecture Committee

   3. Integration and Test (PTL needed)

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

      5. @gusu  O-RAN Centralized Unit (OCU) 

      6. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

         1. Intel will be doing ODULOW release as part of the maintenance. There were some items identified by ODUHIGH that they need to address 

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Xiaohua Zhang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

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

2021 07 07

Recording: Link to Zoom recording

Agenda

1. Call for Scribe (minutes owner): Juha Oravainen

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		Ondřej Hudousek
   Ericsson	John-Paul Lane	X	John Keeney
   NTT DOCOMO	Masafumi Masuda	X	Anil Umesh
   Nokia	Juha Oravainen	X	Thoralf Czichy
   Orange	William Diego	X	Vincent Danno
   Radisys	Ganesh Shenbagaraman	X	Sachin Srivastava
   TIM	Andrea Buldorini	X
   Wind River	Xiaohua Zhang	X	Jackie Huang

   *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: For the 06/30/2021 TOC meeting minutes, motion by MASAFUMI MASUDA , seconded by Jinri Huang . Motion passed 
4. Review of Today's Agenda

5. Release Votes and Approval

   1. D Release
      1. Action point; PTLs to branch that can branch and to update the release page.
         1. All the projects are ready to branch except O-DU Low. This release there are no changes in O-DU low but they have since found some items to be worked, which will be covered in the maintenance release
         2. Decision: Close the D release, publish it and make it available. Motion by Jinri Huang , seconded by JP Lane  Motion passed
      2. Action point: Jinri to organize release statement and PR for "D" Release.
   2. AAL project
      1. Action point: Trishan to check if your have to sign a new agreement for the repo.
         1. A clean path forward here would be to have a separate CCLA / ICLA for just the BSD repo(s). The repo(s) for this project would then use BSD-3-Clause as the project's outbound license, as preferred by the WG6
         2. That CCLA/ICLA would be substantively based on the Apache Software Foundation's CCLA and ICLA (which are widely used across open source projects), with some administrative changes to better align with how the EasyCLA process works for managing CLAs. The existing O-RAN SC repos would continue to use the existing CLAs, the new one would only be for the BSD repo(s)
         3. The decision on whether to take this approach could be voted on and approved by the O-RAN SC's TOC, as part of their responsibilities under the Technical Charter. Note that under section 7(c), it would need to be a 2/3 vote of the entire TOC to grant the project license exception to use BSD-3-Clause here instead of Apache-2.0. Also we would have some administrative and configuration work on the back end to set up and enforce the 3rd CLA
      2. Action point: Jack to present the write up about the AAL project  to have a vote.
         1. Message from WG6 co-chairs:
            1. As discussed on the AAL FEC way forward call today, we would like to initiate a new repo in OSC. This overall proposal will be discussed and approved by WG6 later this week and then we also need to review it with the TSC, but as our intention is to use the repo for the July specification train, we would request OSC to initiate the creation of the repo so that work can occur in parallel with the discussions.

            2. Why

               1. WG6 is considering splitting its AAL FEC specification into two portions to be published together in the July 2021 train – a) a formal specification document published through the normal O-RAN FRAND process that covers stage 1 and stage 2 specifications, and b) a stage 3 API document that covers data structures and programming language level details specific to open source implementations such as DPDK that would be published in ORAN OSC repo under a BSD license and referenced from the formal AAL FEC specification.
         2. Jack: Niall Power from Intel is willing to be the PTL Committer
         3. Jack: There's a request to enable creating this new project and repo. TOC needs to approve that it would be a BSD-3 license and it would need to name Niall Power as the PTL and an initial Committer
         4. Juha: If we make this BSD exception, is it valid only for this project?
         5. Jack: Only for this project
         6. Juha: DPDK is using also GPL license
         7. Jack: Yes, for the low level code but this is not part what is asked for, only BSD is asked
         8. John-Paul: Is this a short term fix until some more permanent way of working can be put in place between O-RAN Alliance and DPDK or is this intended to be the the way of handling the stage three for fact going forward
         9. Jack: This is the way of handling it going forward. O-RAN SC is the place where open source software should be contributed and O-RAN Alliance focus is the specifications
         10. John-Paul: Do we see that's a clear separation?
         11. Jack: I'm not been deeply involved in WG6 but they came to to me to ask about the how to handle the BSD license. But if you're going to contribute it under BSD license what's the difference between putting it in OSC and O-RAN Alliance
         12. John-Paul: There's an outstanding action point at the moment for WG6 to get more clarity from O-RAN legal how the SCCL license and the BSD license might play together and they're waiting on that feedback before they take their vote starting this Friday
         13. Jack: All I'm trying to do is enable because they want to move quickly. If they chose not to do it, will just fold up the repos and not use them
         14. John-Paul: But if we wait to next week and take a vote on this. Does that prevent in any way the repo being set up quickly and still meeting the timeframe. Should we wait and have TOC vote next week?
         15. Jack: If we move forward and approve this, it doesn't enable anything from WG6 until they decide to use it. This just enables to move forward and give them a positive statement that this path is possible and removes one level of uncertainty
         16. Jack: So, we have a motion in front of us to to do this. Do we have a second.?
         17. Jack: If nobody is willing to second, then it won't go to a vote at this time. So, that puts that on the table
      3. Action point: Ganesh to provide an update from ODU point of view.
6. Copyright update
7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

8. Old business and Status of Open Action Items

   1. "E" Release timeline.
      1. Action point: Jack to create "E" Release timeline and publish.
      2. Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
      3. 2021-07-07 discussion below:
      4. Jack: how is the planning for the E-release?
      5. Rittwik: We will continue with VES disaggregated VES agent, DU and RU radio mode testing was not completed and we are going to start on the network slicing design document use case. These are kind of the three high level items. We will also make sure that SMO MVP requirements are coming into the OSC
      6. Jack: there are two items that I'd like to add.
         1. One is with the approval of SCCL license. We should work towards getting key parts of the specification into repos that we can work from and modify as needed
         2. The other one is the ongoing question about can we validate O1 interaction with each component
            1. Action point: Ganesh ShenbagaramanProvide an update, if O1 is going to be available anytime soon in Radisys O-CU test fixture?
      7. Rittwik: We discussed in RSAC meeting and we're trying to propose for the MVP SMO and essentially I think it can be broken down into O1, O2 and LCM, and so there is work that needs to be done across all of these three categories. O1 specifically is broken down into finer granularity.
      8. Jack: it is also important to make sure all the components have a minimum capability
      9. Action point: user-59b16will reach out every PTL and go through necessary items
      10. We need to get copyright items also addressed
      11. Jack: how you Mahesh Jethanandanisee the different parties that are interested in SMO are coming together?

      12. Mahesh: We did a little bit of testing with O-DU, but I think we need to extend that to all the other components to cover those. Not only from  CM perspective but also from FM and PM perspective

   2. Repo clean-up:
      1. Jack: Every repo should be attached to a project with a PTL. House-keeping and due diligence are the responsibility of the PTL.
   3. 5G Super Blueprint status - tabled for D and E, will be reevaluated for F release.
   4. PTL company change.
      1. Jack: I got a message from Mahesh, PTL of SMO. He has moved from VMware to Juniper. We have to decide to do going forward. Hopefully he can attend next meeting and have a dialogue.
9. Standing Agenda Items (Brief Status of Ongoing Activities)

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

   2. user-59b16 Requirements Software Architecture Committee

   3. Integration and Test (PTL needed)

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

      1. Mahesh Jethanandani Service Management and Orchestration (SMO)

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

      3. Matti Hiltunen RIC Applications (RICAPP) 

      4. Thoralf Czichy RIC Platform (RIC)

      5. @gusu  O-RAN Centralized Unit (OCU) 

      6. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      7. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)   

      8. Martin Skorupski Operations and Maintenance (OAM)

      9. Alex Stancu Simulations (SIM)

      10. Xiaohua Zhang Infrastructure (INF)

      11. weichen ni Documentation (DOC)

      12. (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