2021 12 15

Agenda

Call for Scribe (minutes owner): Former user (Deleted)

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		Jackie Huang	x

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

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for TOC meeting approval: proposed by David seconded by James The motion is approved
Review of Today's Agenda
Release Votes and Approval
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.
  1. Update on 11/17/21 : Trishan de Lanerolle we can put an exception clause for introduce a new license (BSD), this will be done in coordination with WG6.
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. No update on 12/01/21.
  4. No update on 12/08/21.
  5. No update on 12/15/21.
Copyright update
1. 12/01/21:
  1. Jinri: What is the status of defining the process for moving eg. YANG files under SCCL license. There was also question if OSC charter needs update to reflect SCCL.
  2. Jack: I am working on writing the process description but it needs further work on streamlining of the process and automation. Only O-RAN SCP charter controlled by O-RAN will need update and there is ongoing discussion with legal team.
2. 12/08/21:
  1. Jack: Progress on CLA was made. Ongoing work on the processes.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
1. 12/01/21:
  1. Jirni: There will be no physical O-RAN F2F meeting in Feb 21. If it happens as virtual meeting is not decided yet.
  2. Jirni: Most of the new specs targeting November train are under review of O-RAN TSC.
  3. Jirni: There is to be confirmed plan to have 2 PRs. First one will be about plug-fest. Second one that will include OSC release E and other 2021 achievements is now planned for Jan 22.
  4. Jack: Last TOC meeting of 2021 will happen on 15th Dec and then we will resume on 5th Jan.
2. 12/08/21:
  1. PR for release E:
    1. Action point: Jinri asks PTLs to provide quote and highlight of 2-3 new features or improvements in their project.
    2. Tracy: This year's joined O-RAN/TIP Plugfest used release E software. PR message should be aligned. Link to release D PR message.
    3. Please contact Jinri if your company is interested in providing quote. There is process to balance the quotes and include quotes from one company in every other PR instead of consecutively.
3. 12/15/21
  1. Rittwik and David Kinsey will sync with Jinri about release overview
  2. Our PR is likely to be published together in O-RAN Alliance 2021 summary and possibly other pieces.
Old business and Status of Open Action
1. "E" Release timeline.
  1. 12/08/21:
    1. James: No blockers for release. Working with PTL to follow on their progress and what can be worked for integration. Also working on release wiki page.
    2. Trishan: License scan was executed and PTLs received email with the results. There were only few medium level issues.
    3. James will follow up with PTL to resolve all the issues.
    4. Jack: Basic required steps for release:
      1. Resolve the license scan issues and update documentation.
      2. Branch e-release before TOC call on Dec 15th
      3. TOC release vote will happen on Dec 15th.
      4. Approx. week after vote release is publishes after process of packaging.
  2. 12/15/21:
    1. James: No outstanding issues from scan, monitoring the release processes from projects.
    2. Agreement that James will not create single tarball file for the release E as it was not created for D release. There will be reference to container image list same as it was provided for D release.
    3. Jinri makes a motion to approve of release of O-RAN SC Release E. Seconded by David. The motion is approved.
2. OSC lab in Taiwan (Prof Ray's lab):
  1. 11/24/21 : Former user (Deleted) initial configurations (TDD specs) is ongoing.
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 functionalities that 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.
  3. 12/15/21: Planning discusion
    1. There are multiple smaller contributions planned for F release.
    2. NTT Docomo proposes to leverage Tacker OpenStack as upstream project for O2 implementation in SMO project but there is also WindRiver contribution on O2 so alignment will be needed in F release planning.
    3. Testing of Slicing E2E should be one of the goals of OSC Lab in release F to validate work done in E.
5. Access to the lab, raised by Mahesh Jethanandani
  1. Mahesh: SMO and ODU high have different access levels to the lab and VMs.
  2. Jack Murray : Please send me the e-mail with details and I will help with the access to the lab. Access to the VMs is more dependent on each project but we can work on that.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
2. Requirements Software Architecture Committee
3. OSC lab
  1. Update on 11/24/21 Former user (Deleted) :
    1. Lab is now running, all equipements are there, cables have been delivered last week. Next week, if we can get all PTP running, then the work can continue.
    2. For the Slicing UCs we need some of this preliminary work, but december seems to be short.
    3. O2 pre-spec implementation is available (James Li), tests could be scheduled on december - E release. Bin Yang wanted a server that he can stand up in the OC lab to do this O2 validation. Jackie Huang An email was send with hardware requirements.
    4. James Liis documented on the wiki that's going on with the New Jersey lab, the Taiwan lab and also I think CMCC want to send that set up a lab in the West Coast.
  2. Update on 12/01/21:
    1. E2E slicing use-case cannot be executed fully but we are progressing. Should be functional in F release.
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)
    1. One repo is branched. Second one waits for permition modification from LF. Code is ready for release otherwise.
  3. John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
    1. Repos are branched. Release images are ready. Small improvements of docs is ongoing.
  4. Sunil Singh RIC Applications (RICAPP)
    1. Branching should be done by end of the week. The release page will note which apps have been updated in E release a which are obsolete.
  5. Thoralf Czichy RIC Platform (RIC)
    1. Ready to branch after aproval. Everything should be ready for release.
  6. (TBD) O-RAN Centralized Unit (OCU)
  7. Former user (Deleted) O-RAN Distributed Unit High (ODUHIGH)
  8. 1. Code and docs are reade. Yet to update docker image page, will do after this meeting.
    2. Action Point: Former user (Deleted) to check that ODULOW binary is compatible with E release.
      1. ODULOW binary will be ready with maintenance release. It should be fine as we plan to do the integration in that timeframe.
  9. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  10. Martin Skorupski Operations and Maintenance (OAM)
    1. Everything is ready.
  11. Alex Stancu Simulations (SIM)
    1. Everything is ready. Docker images are available and code is branched.
  12. Jackie Huang Infrastructure (INF)
    1. Code is ready but we found issue in in generated ISO image. Fixed version will be available EoW.
  13. Weichen Ni Documentation (DOC)
  14. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
1. TOC vote on O-RAN SC software release E. → see point 9.a for details
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2021 12 08

Recording: toc recording

Agenda

Call for Scribe (minutes owner): Former user (Deleted)

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		Scarpina Salvatore
Wind River	Bin Yang		Jackie Huang	x

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

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for TOC meeting approval: proposed by David Streibl seconded by John-Paul Lane. The motion is approved
Review of Today's Agenda
Release Votes and Approval
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.
  1. Update on 11/17/21 : Trishan de Lanerolle we can put an exception clause for introduce a new license (BSD), this will be done in coordination with WG6.
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. No update on 12/01/21.
  4. No update on 12/08/21.
Copyright update
1. 11/24/21:
  1. Jack: Meeting last week for agreed on the CLA structure (not closed yet).
2. 12/01/21:
  1. Jinri: What is the status of defining the process for moving eg. YANG files under SCCL license. There was also question if OSC charter needs update to reflect SCCL.
  2. Jack: I am working on writing the process description but it needs further work on streamlining of the process and automation. Only O-RAN SCP charter controlled by O-RAN will need update and there is ongoing discussion with legal team.
3. 12/08/21:
  1. Jack: Progress on CLA was made. Ongoing work on the processes.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
1. 11/24/21:
  1. Thoralf Czichynext O-RAN meeting will be virtual and probably July 2022 meeting will be face to face.
  2. Jack, Jinri and others should meet to prioritise topics for next release, time slots will be proposed for those discussions.
2. 12/01/21:
  1. Jirni: There will be no physical O-RAN F2F meeting in Feb 21. If it happens as virtual meeting is not decided yet.
  2. Jirni: Most of the new specs targeting November train are under review of O-RAN TSC.
  3. Jirni: There is to be confirmed plan to have 2 PRs. First one will be about plug-fest. Second one that will include OSC release E and other 2021 achievements is now planned for Jan 22.
  4. Jack: Last TOC meeting of 2021 will happen on 15th Dec and then we will resume on 5th Jan.
3. 12/08/21:
  1. PR pro release E:
    1. Action point: Jinri asks PTLs to provide quote and highlight of 2-3 new features or improvements in their project.
    2. Tracy: This year's joined O-RAN/TIP Plugfest used release E software. PR message should be aligned. Link to release D PR message.
    3. Please contact Jinri if your company is interested in providing quote. There is process to balance the quotes and include quotes from one company in every other release PR instead of consecutively.
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. 11/17/21 - Jack: At this window of time the code should be principally freezing with the exception of bug fixes and functionality.
  3. 12/01/21:
    1. First security scan will be executed tomorrow 2nd Dec. Branching need to ocure after sec. scan is passed by repository but before vote that is planned for 15th Dec. Additional security scan can be executed if needed.
    2. Vote on E release will happen on 15th Dec. We need to be ready by then with branches.
  4. 12/08/21:
    1. James: No blockers for release. Working with PTL to follow on their progress and what can be worked for integration. Also working on release wiki page.
    2. Trishan: License scan was executed and PTLs received email with the results. There were only few medium level issues.
    3. James will follow up with PTL to resolve all the issues.
    4. Jack: Basic required steps for release:
      1. Resolve the license scan issues and update documentation.
      2. Branch e-release before TOC call on Dec 15th
      3. TOC release vote will happen on Dec 15th.
      4. Approx. week after vote release is publishes after process of packaging.
2. OSC lab in Taiwan (Prof Ray's lab):
  1. 11/24/21 : Former user (Deleted) initial configurations (TDD specs) is ongoing.
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.
5. Access to the lab, raised by Mahesh Jethanandani
  1. Mahesh: SMO and ODU high have different access levels to the lab and VMs.
  2. Jack Murray : Please send me the e-mail with details and I will help with the access to the lab. Access to the VMs is more dependent on each project but we can work on that.
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
  1. Update on 11/24/21:
    1. Former user (Deleted) use case for F release - (1) APP package CRD descriptor (link with WG10), implement a pre-spec of this. (2) Slice use case will also continue for F release. The complition of O2 will be for F release.
3. OSC lab
  1. Update on 11/24/21 Former user (Deleted) :
    1. Lab is now running, all equipements are there, cables have been delivered last week. Next week, if we can get all PTP running, then the work can continue.
    2. For the Slicing UCs we need some of this preliminary work, but december seems to be short.
    3. O2 pre-spec implementation is available (James Li), tests could be scheduled on december - E release. Bin Yang wanted a server that he can stand up in the OC lab to do this O2 validation. Jackie Huang An email was send with hardware requirements.
    4. James Liis documented on the wiki that's going on with the New Jersey lab, the Taiwan lab and also I think CMCC want to send that set up a lab in the West Coast.
  2. Update on 12/01/21:
    1. E2E slicing use-case cannot be executed fully but we are progressing. Should be functional in F release.
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)
    1. Feature commits are complete. Working on documentation. We should be ready.
  3. John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
    1. Finishing documentation. Branching will happen in couple of days. Will check license scan results.
  4. Sunil Singh RIC Applications (RICAPP)
    1. Matti: All code is committed. Documentation should be ready by next Wednesday.
  5. Thoralf Czichy RIC Platform (RIC)
    1. All the container images were created, tested the basic things. We plena demo on Dec 21st that also partially documents the release.
  6. (TBD) O-RAN Centralized Unit (OCU)
  7. Former user (Deleted) O-RAN Distributed Unit High (ODUHIGH)
    1. Started documentation. Waiting for feedback on O1 integration and then we can branch.
    2. Action Point: Former user (Deleted) to check that ODULOW binary is compatible with E release.
  8. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  9. Martin Skorupski Operations and Maintenance (OAM)
    1. Need t check scan results and then we will be ready for branching.
  10. Alex Stancu Simulations (SIM)
    1. We are ready. Just finishing SIM usage wiki page and documentation.
  11. Jackie Huang Infrastructure (INF)
    1. Checked license scan report and confirmed with Trishan and Jeff that no further actions are required. All the code is merged including in StarlingX. Started updating released notes and dev. guide.
  12. Weichen Ni Documentation (DOC)
  13. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2021 12 01

Recording: zoom recording

Agenda

Call for Scribe (minutes owner): Former user (Deleted)

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		Manasi Padhy
TIM	Andrea Buldorini	x	Scarpina Salvatore
Wind River	Bin Yang		Jackie Huang	x

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

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for November 24th TOC meeting approval: proposed by David Streibl seconded by Jinri Huang. The motion is approved
Review of Today's Agenda
Release Votes and Approval
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.
  1. Update on 11/17/21 : Trishan de Lanerolle we can put an exception clause for introduce a new license (BSD), this will be done in coordination with WG6.
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. No update on 12/01/21.
Copyright update
1. 11/24/21:
  1. Jack: Meeting last week for agreed on the CLA structure (not closed yet).
2. 12/01/21:
  1. Jinri: What is the status of defining the process for moving eg. YANG files under SCCL license. There was also question if OSC charter needs update to reflect SCCL.
  2. Jack: I am working on writing the process description but it needs further work on streamlining of the process and automation. Only O-RAN SCP charter controlled by O-RAN will need update and there is ongoing discussion with legal team.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
1. 11/24/21:
  1. Thoralf Czichynext O-RAN meeting will be virtual and probably July 2022 meeting will be face to face.
  2. Jack, Jinri and others should meet to prioritise topics for next release, time slots will be proposed for those discussions.
2. 12/01/21:
  1. Jirni: There will be no physical O-RAN F2F meeting in Feb 21. If it happens as virtual meeting is not decided yet.
  2. Jirni: Most of the new specs targeting November train are under review of O-RAN TSC.
  3. Jirni: There is to be confirmed plan to have 2 PRs. First one will be about plug-fest. Second one that will include OSC release E and other 2021 achievements is now planned for Jan 22.
  4. Jack: Last TOC meeting will happen on 15th Dec and then we will resume on 5th Jan.
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. 11/17/21 - Jack: At this window of time the code should be principally freezing with the exception of bug fixes and functionality.
  3. 12/01/21:
    1. First security scan will be executed tomorrow 2nd Dec. Branching need to ocure after sec. scan is passed by repository but before vote that is planned for 15th Dec. Additional security scan can be executed if needed.
    2. Vote on E release will happen on 15th Dec. We need to be ready by then with branches.
2. OSC lab in Taiwan (Prof Ray's lab):
  1. 11/24/21 : Former user (Deleted) initial configurations (TDD specs) is ongoing.
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.
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
  1. Update on 11/24/21:
    1. Former user (Deleted) use case for F release - (1) APP package CRD descriptor (link with WG10), implement a pre-spec of this. (2) Slice use case will also continue for F release. The complition of O2 will be for F release.
3. OSC lab
  1. Update on 11/24/21 Former user (Deleted) :
    1. Lab is now running, all equipements are there, cables have been delivered last week. Next week, if we can get all PTP running, then the work can continue.
    2. For the Slicing UCs we need some of this preliminary work, but december seems to be short.
    3. O2 pre-spec implementation is available (James Li), tests could be scheduled on december - E release. Bin Yang wanted a server that he can stand up in the OC lab to do this O2 validation. Jackie Huang An email was send with hardware requirements.
    4. James Liis documented on the wiki that's going on with the New Jersey lab, the Taiwan lab and also I think CMCC want to send that set up a lab in the West Coast.
  2. Update on 12/01/21:
    1. E2E slicing use-case cannot be executed fully but we are progressing. Should be functional in F release.

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)
    1. SMO project is in process for committing, bug-fixing. Close to ready to branch. Will investigate if CII Badge is possible in E release.
  3. John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
    1. We are ready to branch after scan. Currently working on O-DU slicing use-case. There will be multiple version of the use-case as there are 2 types of VES and 2 controllers and 3 approaches to rApp implementation. Other project are not consuming our APIs so we can continue right until branch.
  4. Sunil Singh RIC Applications (RICAPP)
    1. We are reviewing and verifiyng the xApps.
  5. Thoralf Czichy RIC Platform (RIC)
    1. Couple of items to commit are aiming for December 7th. After that there will be only bug-fixes committed. We still need to fill in wiki with generated containers over next few days.
  6. (TBD) O-RAN Centralized Unit (OCU)
  7. Former user (Deleted) O-RAN Distributed Unit High (ODUHIGH)
  8. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  9. Martin Skorupski Operations and Maintenance (OAM)
    1. We are ready for the scan. Had couple of demos using different APIs from 3GPP and OSC hello world API. We identified issue in OpenDaylight netconf client but there is possible workaround.
  10. Alex Stancu Simulations (SIM)
    1. We are ready for the brancing and the scan.
  11. Jackie Huang Infrastructure (INF)
    1. We are in bug-fixing stage, there are still several issues we need to fix. It should be OK to scan and then late branch.
    2. Jack Murray: There is a lot of new INF code so there is possibility to also use maintenance release that usually happens month after main release.
  12. Weichen Ni Documentation (DOC)
  13. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
1. Meeting Schedule for next year
2. New Release PR
Planning for Next Meeting
Any Other Business (AOB)
1. Access to the lab, raised by Mahesh Jethanandani
  1. Mahesh: SMO and ODU high have different access levels to the lab and VMs.
  2. Jack: Please send me the e-mail with details and I will help with the access to the lab. Access to the VMs is more dependent on each project but we can work on that.
Meeting Summary (resolutions, new action items, etc.)

2021 11 24

Recording: zoom recording

Agenda

Call for Scribe (minutes owner): William DIEGO

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.

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for TOC meeting approval: proposed by William DIEGO seconded by Former user (Deleted) . The motion is approved
2. Former user (Deleted)scribe for december
Review of Today's Agenda
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.
    1. Update on 11/17/21 : Trishan de Lanerolle we can put an exception clause for introduce a new license (BSD), this will be done in coordination with WG6.
  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/24/21.
Copyright update
1. 11/17/21:
  1. Jack: There is an other meeting this afternoon with the legal team working on the CLA and update of charter to allow the SCCL license to be manage as part of those projects.
2. 11/24/21:
  1. Jack: Meeting last week for agreed on the CLA structure (not closed yet).
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
1. 11/17/21: huangjinri@chinamobile.com
  1. O-RAN alliance specification work is ongoing to reach november train.
  2. Format of next O-RAN F2F meeting is not decided yet.
2. 11/24/21:
  1. Thoralf Czichynext O-RAN meeting will be virtual and probably July 2022 meeting will be face to face.
  2. Jack, Jinri and others should meet to prioritise topics for next release, time slots will be proposed for those discussions.
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. 11/17/21 - Jack: At this window of time the code should be principally freezing with the exception of bug fixes and functionality.
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: Former user (Deleted) Prof Ray's student is asking for some help (Former user (Deleted) ) 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. 11/24/21 : Former user (Deleted) initial configurations (TDD specs) is ongoing.
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.
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 Former user (Deleted)
  1. Update on 11/17/21:
    1. Former user (Deleted) Regarding Test & Integraytion, someone who is not affiliated with any company what would like to help and provide some integration testing to James
    2. Jack: how is LF handle individual contributors, there is a policy? Trishan de Lanerolle It's an open project so contributions from individua are fine and have same process of any other contributors (review, approval), just lets us (LF) know.
    3. Former user (Deleted) In this case this personwanted access to the New Jersey lab for that it's needed company name, profesional email, phone that he didn't have. Trishan de Lanerolle for project is different, and for lab is different. Jack: let's take it offline and talk about it (David Kinsey [AT&T])
    4. Former user (Deleted)regarding F release we need a kind of a theme to attach ourselves, for E rel. was network slicing. For F rel. could be production ready and hardeing of our code. Jack: F rel. will attempt to be the first full release and not all the componets have the same maturity. Rittwik: Maybe we will just add on to slicing and make it more mature.
    5. James Li David Kinsey [AT&T] O2 interface integration with SMO integration test. Jackie Huang A small part of O2 interface as an MVP wil be ready for the end of this month. (Will be part of the RSAC agenda for next Tuesday).
  2. Update on 11/24/21:
    1. Former user (Deleted) use case for F release - (1) APP package CRD descriptor (link with WG10), implement a pre-spec of this. (2) Slice use case will also continue for F release. The complition of O2 will be for F release.
3. OSC lab
  1. Update on 11/17/21:
    1. Former user (Deleted)PTP get setup, lab is ready to test maybe a few things of E release and maintenace
    2. Jack: Fronthaul gateway cable is missing (supply problem)
    3. James Li : Jackie Huang is requesting OSC lab access VPN and VM. David Kinsey [AT&T] : contact me providing name, mail, phone and company. Jack: need to updated wiki with this new info and new contact.
  2. Update on 11/24/21 Former user (Deleted) :
    1. Lab is now running, all equipements are there, cables have been delivered last week. Next week, if we can get all PTP running, then the work can continue.
    2. For the Slicing UCs we need some of this preliminary work, but december seems to be short.
    3. O2 pre-spec implementation is available (James Li), tests could be scheduled on december - E release. Bin Yang wanted a server that he can stand up in the OC lab to do this O2 validation. Jackie Huang An email was send with hardware requirements.
    4. James Liis documented on the wiki that's going on with the New Jersey lab, the Taiwan lab and also I think CMCC want to send that set up a lab in the West Coast.

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 (Ericsson EST) 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. Former user (Deleted) O-RAN Distributed Unit High (ODUHIGH)
  8. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  9. Martin Skorupski Operations and Maintenance (OAM)
  10. Alex Stancu Simulations (SIM)
  11. Jackie Huang Infrastructure (INF)
  12. Weichen Ni Documentation (DOC)
  13. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2021 11 17

Recording: Zoom recording

Agenda

Call for Scribe (minutes owner): William DIEGO

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		Jackie Huang

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

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
Review of Today's Agenda
1. Budget summary for 2022 Trishan de Lanerolle
  1. Summary of 2021 accomplishments: Rel. D and Rel. E, SCCL license, F Rel. planning
  2. Planning for 2022: Technical priorities, alignment with other SDO/OSS, LF support
  3. 2022 budgest allocation: Dev. support 50.08% , Prog Mgmt + operations 21.6% , G&A 6.3%, Marketing support 8.9%, events 6.6%, legal 5.8%
2. Thoralf Czichy 2021-11-12: Note that on the near-RT RIC side we are now planning 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.
  1. Trishan de Lanerolle: on the LF side we have ARM based servers at the DC build it, so we are going to bring a couple of those (already done for ONAP and other couple projects). Work in progress which could be completed for the next release.
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.
    1. Update on 11/17/21 : Trishan de Lanerolle we can put an exception clause for introduce a new license (BSD), this will be done in coordination with WG6.
  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/17/21.
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?
3. 11/17/21:
  1. Jack: There is an other meeting this afternoon with the legal team working on the CLA and update of charter to allow the SCCL license to be manage as part of those projects.
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)? Former user (Deleted) 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.
2. 11/17/21: huangjinri@chinamobile.com
  1. O-RAN alliance specification work is ongoing to reach november train.
  2. Format of next O-RAN F2F meeting is not decided yet.
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. 11/17/21 - Jack: At this window of time the code should be principally freezing with the exception of bug fixes and functionality.
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: Former user (Deleted) Prof Ray's student is asking for some help (Former user (Deleted) ) 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.
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 Former user (Deleted)
  1. 10/27/21: Rittwik: Suggest Jack reach out to Rich
  2. 11/10/21: Former user (Deleted)
    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. Update on 11/17/21:
    1. Former user (Deleted) Regarding Test & Integraytion, someone who is not affiliated with any company what would like to help and provide some integration testing to James
    2. Jack: how is LF handle individual contributors, there is a policy? Trishan de Lanerolle It's an open project so contributions from individua are fine and have same process of any other contributors (review, approval), just lets us (LF) know.
    3. Former user (Deleted) In this case this personwanted access to the New Jersey lab for that it's needed company name, profesional email, phone that he didn't have. Trishan de Lanerolle for project is different, and for lab is different. Jack: let's take it offline and talk about it (David Kinsey [AT&T])
    4. Former user (Deleted)regarding F release we need a kind of a theme to attach ourselves, for E rel. was network slicing. For F rel. could be production ready and hardeing of our code. Jack: F rel. will attempt to be the first full release and not all the componets have the same maturity. Rittwik: Maybe we will just add on to slicing and make it more mature.
    5. James Li David Kinsey [AT&T] O2 interface integration with SMO integration test. Jackie Huang A small part of O2 interface as an MVP wil be ready for the end of this month. (Will be part of the RSAC agenda for next Tuesday).
3. OSC lab
  1. Update on 11/10/21:
    1. Former user (Deleted) 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.
  2. Update on 11/17/21:
    1. James Li acces to lab contact David Kinsey [AT&T] providing all the details of contacts (names, mail, etc)
  3. Update on 11/17/21:
    1. Former user (Deleted)PTP get setup, lab is ready to test maybe a few things of E release and maintenace
    2. Jack: Fronthaul gateway cable is missing (supply problem)
    3. James Li : Jackie Huang is requesting OSC lab access VPN and VM. David Kinsey [AT&T] : contact me providing name, mail, phone and company. Jack: need to updated wiki with this new info and new contact.

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)
    1. Jack: Security badging (CII badging) remains open for SMO and ODULOW (Former user (Deleted) will send a message to Zhimin Yuan (Deactivated) )
  3. John Keeney (Ericsson EST) 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. Former user (Deleted) O-RAN Distributed Unit High (ODUHIGH)
  8. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  9. Martin Skorupski Operations and Maintenance (OAM)
  10. Alex Stancu Simulations (SIM)
  11. Jackie Huang Infrastructure (INF)
  12. Weichen Ni Documentation (DOC)
  13. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2021 11 10

Recording: Zoom recording

Agenda

Call for Scribe (minutes owner): William DIEGO

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.

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
Review of Today's Agenda
1. No new items to add.
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.
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?
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)? Former user (Deleted) 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.
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: Former user (Deleted) Prof Ray's student is asking for some help (Former user (Deleted) ) 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.
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 Former user (Deleted)
  1. 10/27/21: Rittwik: Suggest Jack reach out to Rich
  2. 11/10/21: Former user (Deleted)
    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.

2021 Q4 (Oct, Nov, Dec)

2021 12 15

2021 12 08

2021 12 01

2021 11 24

2021 11 17

2021 11 10