Technical Charter for O-RAN Software Community

TOC Voting Members

Company	Name	Alternate
AT&T	Jack Murray Co-Chair	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	Weichen Ni
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	Sachin Srivastava
Verizon	Viswanath Kumar Skand Priya	Kristen Young
Available (10)	Available (10)
Available (11)	Available (11)
Available (12)	Available (12)

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

TOC Meeting Info

Technical Oversight Committee meetings are open to the public and held on Wednesdays at 8 AM Eastern Time USA. World Time Zone Map

Zoom 2 Info:

Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/6540568082
Or Telephone: Dial (for higher quality, dial a number based on your current location)
- 855 880 1246 (Toll Free), 877 369 0926 (Toll Free)
- Meeting ID: 654 056 8082
- International numbers available: https://zoom.us/u/acyy3hylQi

City	Time	Zoom/Audio Bridge
UTC-time	Wednesday 12:00	https://zoom.us/j/6540568082
New York (EDT / UTC-4)	Wednesday 08:00	+1 669 900 6833 +1 646 558 8656 855 880 1246 (Toll Free) 877 369 0926 (Toll Free) Meeting ID: 654 056 8082
Paris (CEST / UTC+2)	Mar-11/Mar-18/Mar-25: Wednesday 13:00 Apr-1-2020 onwards: Wednesday 14:00	+33 7 5678 4048 +33 1 8288 0188 805 082 588 (Toll Free) Meeting ID: 654 056 8082
Beijing (CST / UTC+8)	Wednesday 20:00	+86 10 87833177 +86 10 53876330 400 616 8835 (Toll Free) 400 669 9381 (Toll Free) Meeting ID: 654 056 8082
Tokyo (JST / UTC+9)	Wednesday 21:00	+81 524 564 439 +81 3 4578 1488 0 800 100 5040 (Toll Free) Meeting ID: 654 056 8082
Helsinki (EEST / UTC+3)	Mar-11/Mar-18/Mar-25: Wednesday 14:00 Apr-1-2020 onwards: Wednesday 15:00	+358 341092129 Meeting ID: 654 056 8082

2020 09 23

Recording:

Agenda

Call for Scribe (minutes owner): David Streibl

Roll Call & Quorum Check

Company	Contact Name	Alternate Contact
AT&T	Jack Murray Co-Chair	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	Weichen Ni
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	Sachin Srivastava
Verizon	Viswa Kumar	Kristen Young

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
Review of Today's Agenda
Release Votes and Approval.
Copyright update.
1. AP: William to contact Orange OAI representative and schedule a meeting between OSC and OAI.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Status of Open Action Items (Old Business).
1. AP: Ganesh ONF SD-RAN investigation summary
2. O-CU development and O-CU for Cherry traffic steering use-cases
3. Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. @Felix Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. Mahesh Jethanandani Service Management and Orchestration (SMO)
  12. (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.

2020 09 16

Recording: 2020-09-16_toc.mp4

Agenda

Call for Scribe (minutes owner): David Streibl

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
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
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. Decision: Moved by David, seconded by Jinri, no objection, 20200909 minutes approved.
Review of Today's Agenda
Release Votes and Approval.
Copyright update.
1. ~~AP Jinri: Will check with EC about the O-RAN contrib. withdrawls concerning copyright.~~ DONE
  Jinri checked with EC, they promised to expedite.
2. Jinri review copyright questions sent by John Keeney but the answer needs copyright expertise so Jinri asked in mailing list for volunteer from OSC that would help with this and also generally with copyright as longstanding issue for OSC. Gu Su would like to help with this topic and act as interface between OSC and other parties concerning copyright.
  1. John Keeney: For clarification, questions I asked are related to OSC and O-RAN. ETSI and 3GPP discussions are separate.
  2. Jinri: I believe Gu Su will reach out to you offline.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
1. ONF SD-RAN relation to OSC:
  1. Jinri: Based on info from EC, ONF is preparing blog post to clarify some misunderstanding created by the original articles.
  2. Jinri: EC requested for OSC to create blog post about possible of collaboration with different OSS communities. I will reach out to Jack, Rittwik and others about the text.
    1. Rittwik: Do you mean down-streaming other communities for use in OSC or up-streaming?
    2. Jinri: It should be general statement stating our willingness to cooperate with other communities to avoid fragmentation of the ecosystem.
    3. RIttwik: One Item here is the collaboration with OAI. Is there progress? I saw article stating they are providing full 5G SW stack.
    4. Jack: There is licencing complication. We can't use the lower layer code from OAI with the current licence as upstream project. Discussion about it was delayed over the summer but I am willing to discuss plan forward. Some of the higher level code is Apache 2.0 and could be used as upstream.
    5. Rittwik: One of our challenges is the O-CU. Even their O-CU could be helpful but they do not have E2 interface. We could extend the O-CU by E2 and contribute it to OSC but that needs resolved licencing first.
    6. William: I propose to schedule a meeting between OSC and OAI to reopen the discussion. AP: William will contact Orange OAI representative and schedule a meeting between OSC and OAI.
2. Trishan: O-RAN received positive press on FCC 5G Open RAN forum. I think it was represented in one of the panels.
  1. Jinri: I don't think it was O-RAN Alliance represented there but individual companies.
  2. Trishan: Does O-RAN plan an promotion on that front?
  3. Jack: O-RAN Alliance is very supportive of the Open RAN aspect but it is non-political entity and does not delve into political forums. This is up to individual companies if they want to do so. As the organization O-RAN tries to stay out of politics.
  4. Tracy: There were principal investigator from Uni. of Utah and Rutgers Uni. as participants from OTIC US East and West describing the demos and use-cases but to specifically referencing O-RAN. I don't think anybody spoke in the voice of the O-RAN Alliance.
  5. Jack: Basically the Universities were presenting the work they are doing.
3. Jinri: The was email call for demo on O-RAN Alliance plugfest virtual exhibition for canceled MWC America and MWC 2021. Interested O-RAN members should contanct Paul Smith.
PTL to provide information regarding O-RAN-related open source communities.
Status of Open Action Items (Old Business).
1. O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation/requirements b/w O-CU and the other projects
2. O-CU PTL to prioritize the items shown on the presentation slide (https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2) to make sure some key features such as handoff could be supported for traffic steering use case.
3. The team to arrange an offline meeting to further discuss the challenges.
  1. Rittwik: We are tracking 3 items in RSAC.
    1. Setting up the O-DU subsystem - going well, supported from Intel and Radisys, requires connection to Viavi emulator and O-CU
    2. We are not sure what is current status of OSC O-CU. As a interim replacement I proposed to use stripped down Radisys commercial SW as test fixture. We need it to attache UE and test O-DU-low and O-DU-high and hand-off between cells. There are 2 usecases: DU testing and traffic steering testing, both need O-CU.
    3. SMO item that Mahesh presented earlier.
  2. Jack: Yingying will not be cover O-CU PTL anymore. Is that correct?
  3. Jinri: Yes, we need to have a call for new PTL. I talked with ICT, they are doing internal evaluation but are not optimistic. Progress on current CU will be difficult.
    1. ~~AP Jinri: Will talk with ICT~~ DONE
  4. Jack: So need to replan O-CU development as current implementation is partially done. It is difficult to continue on such low-level code if original developers move on. We need to raise it as open issue. We have to use alternative solution.
  5. Rittwik: Viavi has internal R&D O-CU that could be potentially used.
  6. Ultan (Viavi): We are bringing it from internal lab, it is NSA currently.
  7. Rittwik: Could this be used in Cherry timeline
  8. Ultan: We will check, depend on our availability.
  9. Sphoori (Radisys): O-DU-high currently supports SA only.
4. Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. CherryTimeline
    1. Jack: We are in week 34, dev sprint 3. Is there any item that PTLs need to address?
2. user-59b16 Requirements Software Architecture Committee
  1. Rittwik:Work is progressing and PTLs are checking integration status of the projects. We have the flows that are usually checked by Felix towards the end of integration testing. So it will be Felix's responsibility to see how much of those flows is validated.
  2. Jack: Is the lab stable and accessible to work in?
  3. Rittwik: There are small access issues but we progressed to point where it is used for work.
  4. Rittwik: We are also looking into items that will flow from Cherry to Dawn and also working on preliminary draft for Dawn.
3. user-d3360 Integration and Test
  1. Felix will replace Lusheng as PTL until end of Cherry release and following that there will be vote on new PTL for I&T
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. Mahesh Jethanandani SMO (SMO)
  12. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
1. Mahesh presented SMO Cherry development plan.
2. 1. Mahesh: It is plan on what could we do in Sprint 2 and 3, essentially demonstration of pre-O2 LCM features
  2. For details see: https://wiki.o-ran-sc.org/x/Voo_AQ
  3. Jack: Felix and Trishan can help you with admin tasks. Also it is important to get something working so as new project you could target end of of Sprint 4 with you demo and get couple more weeks for development.
  4. Jack: I expect that SMO will eventually leverage work in OAM project and NONRTRIC. It is umbrella project I would like all the OSC companies to participate in. There is interest from E///, IBM and others but broad cooperation on SMO will be needed.
3. I&T project changes
  1. Felix replaces Lusheng as PTL until end of Cherry release
    1. ~~AP Felix: To send self-nomination e-mail for I&T PTL.~~ DONE
  2. Jack and Jinri plan to ask if TIFG could provide PTL for I&T
  3. Jack: We need to create I&T team with representatives from other projects and multiple companies as the activity grows. This is basically open call to get involved in I&T.
    1. John-Paul: Should we put this as item on F2F agenda?
    2. Jinri: Paul Smith is drafting the F2F agenda, 2 slots will be available for OSC
    3. Jack: Rittwik and David as part of RSAC, let's make sore this is part of the agenda for meeting with TIFG. I will raise it with EC.
    4. David Kinsey: It will be probably cross-organizational type meeting, I will reach out to Paul
    5. Jack: We could go to TIFG meeting also.
    6. David: There is currently listing of cross-organizational items before individual WGs get their time slots. Let's see if we have enough to talk about to have it as separate item from RSAC and road-map.
4. AP Ganesh self-nominated to investigate SD-RAN
  1. Jack: Ganesh will talk about the SD-RAN next week.
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.

2020 09 09

Recording: 2020-09-09_toc.mp4

Agenda

Call for Scribe (minutes owner): David Streibl

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
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
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
Review of Today's Agenda
1. Decision: Moved by David, seconded by Ganesh, no objection, 20200902 minutes approved.
Release Votes and Approval.
Copyright update.
1. Usage of 3gpp models in O-CU develop
  1. Jinri talked with co-chair of STFG and also raised the issue on last TSC call
  2. SDFG delayed by holiday season, request also forwarded to O-RAN legal team
2. 60 day review windows time
  1. Jinri: EC is preparing motion for board to delegate the right to give copyright permission to OSC to EC even during 60 day review window
  2. John-Paul: How should OSC handle code based on unpublished O-RAN spec if there is withdrawal of contribution in O-RAN
  3. Jinri: There is no detailed guideline from EC. Should be very uncommon.
  4. Jack: There should not be multiple decision levels. We should keep the decision on one level, in this case on EC.
  5. AP Jinri: Will check with EC about the Withdrawls
3. Mahesh: What does copyright allow us if we want to make fixes/changes to improve 3GPP models or submitting the changes back to 3GPP?
  1. Jinri: We are not allowed to modify the models.
  2. Martin: There is preparation of process in WG1 where O-RAN Alliance members that are also 3GPP members would contribute the change requests to 3GPP.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
1. Jinri provided status report to TSC last week -
  1. SMO Project PTL decision
  2. ONF SD-RAN
    1. EC is aware of the PR issue
    2. John-Paul: Is there any plan/activity to collaborate between O-RAN and ONF on RIC?
    3. Jinri: Not aware on any activity.
    4. Rittwik: There is official PR from ONF and separate news article with comments from ONF staff member not representing ONF official view. Collaboration is happening on working level. ONF sees SD-RAN as one of the RIC implementations, this one specifically using ONF ONOS controller.
    5. Juha: In which project does ONF contribute/plan to contribute?
    6. Rittwik: ONF has discussion paper contribution for ORAN WG3.
    7. John-Paul: It would be good to know details about the SD-RAN project, potential fragmentation and overlap.
    8. AP Ganesh self-nominated to investigate SD-RAN
Status of Open Action Items (Old Business).
1. O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation/requirements b/w O-CU and the other projects
2. O-CU PTL to prioritize the items shown on the presentation slide (https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2) to make sure some key features such as handoff could be supported for traffic steering use case.
3. The team to arrange an offline meeting to further discuss the challenges.
  1. Rittwik: We will need more meeting to align.
  2. Jinri: I will reach out to O-CU PTL and Gu Su.
  3. Rittwik:
    1. Bottleneck is O-CU emulator, it does not exist today
      1. Viavi can provide O-RU emulator and EPC
      2. Viavi requesting if Radisys or ICT could provide O-CU emulator
      3. Ganesh: Started internal discussion if Radisys O-CU could be used, will have tech details on RSAC meeting later this week
      4. Rittwik: Close-source binary O-CU for testing would help, ICT plans to provide OSS one.
      5. AP Jinri: Will talk with ICT
4. ~~Jinri will bring the copyright issue to TSC/EC (to push the process), Jinri will follow up with O-RAN manager Zbyněk concerning 60 days copyright topic~~ DONE
5. ~~Ganesh will elaborate the copyright issue regarding O-CU and O-DU, Sachin will check on O-CU and O-DU part with Ganesh~~ DONE
6. ~~PTL to fill in the goal and the scope in the Cherry deliverable summary page (see Cherry Release (Dec 2020)) first. To have update once a month.~~ DONE
7. ~~Mahesh will make quick report on SMO plan~~
  1. There will be starting discussion about SMO on Tuesday RSAC meeting
8. PTL to provide information regarding O-RAN-related open source communities for Jinri
  1. Jack: Lets keep this item long-term.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
  3. AP: Jinri will reach out to Trishan
2. user-59b16 Requirements Software Architecture Committee
  1. Rittwik and David are tracking tickets in Jira to provide scorecard based on RSAC objectives and what has been implemented in Cherry
3. user-d3360 Integration and Test
  1. Felix: How should be proceed with select PTL replacement?
  2. Jinri: We could vote on PTL this now or on next TOC.
  3. Jack: Let Felix self-nominate via mailing list with little background. Team is very small, so it should be easy.
  4. Jack: We need to expand Integration and Test as we add other components and there will need to be interface between other project and IaT. More participation in Integration and Test team is needed.
  5. AP Felix: To send self-nomination e-mail.
  6. Jinri: This is area where TOC members and future potential TOC members could contribute.
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
1. ONF SD-RAN details proposed by Juha - addressed in 7.
2. Integration plan and timeline by Rittwik - addressed in 8. c.
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.

2020 09 02

Recording: 2020-09-02_toc.mp4

Agenda

Call for Scribe (minutes owner): David Streibl

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair		Lusheng Ji	x
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
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		Sachin Srivastava	x
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. Decision: Moved by David, seconded by John-Paul, no objection, 20200826 minutes approved.
Review of Today's Agenda
1. No new items added,
  1. Planned plugfest status raised by John-Paul Lane will be addressed in 7.
  2. STFG and TSC/EC update raised by John Keeney will be addressed in 6.
Release Votes and Approval.
1. None needed.
2. New committers for integration project approved by mail
Copyright update.
1. No update on 60 days issue from EC. AP: Jinri will follow up with O-RAN manager Zbyněk.
2. Copyright issue description (Old bussiness 8.e.)
  1. Martin sent mail to TOC mailing list with details
  2. AP: Sachin will check on O-CU and O-DU part with Ganesh
  3. AP: Jinri will bring the copyright request to TSC call September 4th
3. No update from STFG as of last week
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- Tracy: Plug-fest preparation is moving forward. There will be virtual/ semi virtual demo in EU, USA, Asia, India
  More details for O-RAN members on https://oranalliance.atlassian.net/wiki/spaces/TTIFG/pages/503971932/PF2+General.
  If there is interested member of O-RAN willing to present, please contact TIFG
  Followed up by US based event after Cherry release last week of November
Status of Open Action Items (Old Business).
1. O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation/requirements b/w O-CU and the other projects
2. O-CU PTL to prioritize the items shown on the presentation slide (https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2) to make sure some key features such as handoff could be supported for traffic steering use case.
3. The team to arrange an offline meeting to further discuss the challenges. Gu Su from China Mobile can help.
  1. Rittwik: Created plan for O-RU, O-DU, O-CU integration with Intel, Radisys and Viavi, details in RSAC meeting notes
  2. AP: Rittwikwill reach out via email, will include Gu Su
4. Jinri will bring the copyright issue to TSC/EC (to push the process)
  1. Addressed in 6.
5. Ganesh will also elaborate the copyright issue regarding O-CU and O-DU. ~~Martin will send the written copyright issue description to Jinri and Jack so that Jinri could follow up.~~ DONE.
6. PTL to fill in the goal and the scope in the Cherry deliverable summary page (see Cherry Release (Dec 2020)) first. To have update once a month.
  1. Partially complete. Few missing projects
  2. Review will be done every first call of the month
7. SMO Project PTL Nominations
  1. Trishan: Mahesh Jethanandani from VMWare was selected as SMO PTL via condorcet method by TOC.
  2. AP: Mahesh will make quick report on SMO plan, targeting next week TOC
8. PTL to provide information regarding O-RAN-related open source communities
  1. Still in process, needs to be done by 3rd, so it can be presented on Friday TSC call. If it is not completed by then, Jinri will postpone presentation to next TSC call.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
  3. Still in progress, Jinri and Trishan will discus offline.
2. user-59b16 Requirements Software Architecture Committee
  1. Rittwik : Plan for integration of O-CU / O-DU-high / O-DU-low created - targeting traffic steering use-case
  2. Zhimin: Professor Ray-Guang Cheng plans contribution in future, targeting mainly Documentation project
  3. Jinri : There is question if we can use individual CLA in combination with OSC licence
  4. Ray-Guang Cheng : Will check status of the CLA with his students
3. user-d3360 Integration and Test
  1. Trishan: Integration and Test project can make recompilation for new PTL for TOC.
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
    1. John:
      1. Focus on up-streaming A1 controller to ONAP - almost finished, next step is work on it's utilization in OSC as part of O-RAN and OSC use-cases
      2. Starting work on A1 enrichment information coordination
      3. Preparations for Cherry, ongoing alignment with RSAC use-cases - health-check and traffic steering still needs a lot of activity
    2. Jinri: Where do we get the enrichment information?
    3. John: New concept in O-RAN, will need enrichment info registry and coordination function.
    4. Jinri: What is code split between OSC and ONAP?
    5. John: Not clear yet, needs alignment - A1, O1, O2 need development from SMO side
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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.

2020 08 26

Recording: TOC-weeekly-20200826.mp4

Agenda

Call for Scribe (minutes owner): Jinri Huang, China Mobile

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair		Lusheng Ji	X
China Mobile	Jinri Huang Co-Chair	X	Weichen Ni
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
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. There is no comment raised on the 0819 meeting minute.
  1. Decision: Moved by David Streibl and seconded by Juha Oravainen, without objection and abstention, the 20200819 meeting minute is approved.
Review of Today's Agenda
1. No new items added;
Release Votes and Approval.
1. None.
Copyright update.
1. JInri explained the background again (see previous meeting minute). Recent progress: There is araft proposal in which EC is requesting Board to authorize EC to grant the usage of the copyright in the draft specification to OSC, during the 60-day period of review window. The proposal will be sent to Board for approval. Time is not decided yet. However, there is a potential risk here. If some company withdraws the IPR during the review period which results in the modification on the specification, it may impact OSC work. The possibility is very minor.
2. Question is asked on why the IPR claim is not made in the CR time but after the spec. is finished? Answer is that it is specified in the Consititution. Changing the IPR policy will take too much time and all the member companies have to review.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
1. a lot of discussion happend regarding the ONF articles concern raised by John-Paul. Here is the link.
  1. https://www.sdxcentral.com/articles/news/onf-picks-up-where-o-ran-alliance-falls-short/2020/08/
  2. https://www.prnewswire.com/news-releases/onf-announces-new-5g-sd-ran-project-301117481.html
2. Basically, the feeling from the team is surprise and confusion, including: wording is negative to the work OSC is doing; what is the relationship with O-RAN Alliance? Has anyone been contacted in O-RAN? Does OSC need to respond?
3. Jinri will bring this to EC and TSC next week.
4. As for MVP, discussion ongoing. Jinri will follow this.
Status of Open Action Items (Old Business).
1. O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation/requirements b/w O-CU and the other projects
  1. see below. discussion combined with item 8b.
2. O-CU PTL to prioritize the items shown on the presentation slide (https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2) to make sure some key features such as handoff could be supported for traffic steering use case.
3. The team to arrange an offline meeting to further discuss the challenges. Gu Su from China Mobile can help.
  1. Ganesh: Call has been held to discuss the O-CU dependency with other projects. Key point raised: copyright issue for the 3GPP-defined yang model. Not have permission to use 3GPP yang model in OSC. Any development of the node, esp. CU and DU has to be on hold. The definition is from 3GPP; work can not move forward coz of this.
  2. Rittwik: possible to write the code with STUB. With STUB, people could download the code. We do not inject to the repo. Just like ASN.1 issue. We do not get permission from 3GPP. However it did not stopping us from contribution. When permission coming through, we can open it up. Suggest to continue the work on health check. Not to defer to dawn.
  3. Ganesh: Refer to model, generate the code, not to store the yang files in the repo?
  4. Martin: Exactly how we do so far. We implement the code, save it in privie repo (a bit strange in open source community). Not have this code in any nexus, jenkin, whatever internal tool chain for OAM and SIM project. Can do domenstation to be functional. However, avoid generated code from YANG files at the time of being since somebody may think code generation is viewed as modification.
  5. Ganesh: Any common code generation tool across projects?
  6. Martin: No. Netconf servers or clients have their own code gernation for their purpose. Generate code from YANG for API. Avoid put it in nexus, or else where public.
  7. Ganesh agree.
  8. Rittwik: 2^nd comment: Currently getting permission from 3GPP is stalled. Who is the LS/coordinator from O-RAN to 3GPP. Can OSC have direct line of comuincationw tiht 3GPP. Is that possible? Suggest Jinri to surface this up to the EC/TSC.
  9. Jinri: Has the copyright issue been setnt o SDFG before? Old or new issue? Martin answered that it is an old issue. (half an year ago)
  10. Jinri: Later on, we need clear record (of the copyright request/issue in the meeting minute. 2^nd, some email from SDFG indictes that ETSI officers are on vacation. Will be back recently and speed up the process. 3^rd, Jinri will surface this up to EC/TSC; 4^th, we need to push SDFG.
  11. AP: Jinri will bring the copyright issue to TSC/EC (to push the process)
  12. Rittwik: could we have direct line of communication with 3GPP? Jinr: difficult.
    For follow-up,
  13. AP: Martin will send the written copyright issue description to Jinri and Jack so that Jinri could follow up. Ganesh will also elaborate the copyright issue regarding O-CU and O-DU.
  14. Ganesh: WG5 also asking t how to handle the YANG model for ODU. Will check with them in the background.
4. Lusheng to create a wiki page with a template for PTL to fill in the Cherry deliverable summary
  1. Thoralf helped to create the page already. Here is the link: Cherry Release (Dec 2020)
  2. AP: PTL to fill in the goal and the scope first. Will have update once a month.
5. SMO Project PTL Nominations
  1. voting email has been sent out to TOC. No specific deadline for this. 3 votes already right now.
  2. Q: if Jack could not make it, can the alternate vote it by email? A: yes.
  3. Trishan will add the invitation to Lusheng.
  4. Jinri: expect to get this done by next TOC.
6. Trishan to send Jinri the voting process.
  1. done. AP closed.
7. PTL to provide informaion regarding O-RAN-related open source communities
  1. Jinri emphasized the importance of this request, not because of the AP from TSC/EC, but also beneficial to the whole community. Deadline is set by next TOC meeting. Format is flexbile: slides or simple text in the mail.
8. Mailing list issue (stop "main" for discussion, use "discussion" list)
  1. Recommendation from LF. It is the best practice not to use "main" list for discussion. Suggest to use a dedicated "discussion" list while using "main" for major announcement in the community. The LF staff could help with the transition and no action is requried from the members.
  2. No opposion to this. No fee is invovled. LF could get this done within one day.
  3. Decision: the OSC will use a dedicated "discussion" list for topic discussion.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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.
1. Decision: Moved by David Streibl and seconded by Juha Oravainen, without objection and abstention, the 20200819 meeting minute is approved.
2. AP: Jinri will bring the copyright issue to TSC/EC (to push the process)
3. AP: Martin will send the written copyright issue description to Jinri and Jack so that Jinri could follow up. Ganesh will also elaborate the copyright issue regarding O-CU and O-DU.
4. AP: PTL to fill in the goal and the scope first. Will have update once a month.
5. Decision: the OSC will use a dedicated "discussion" list for topic discussion.

2020 08 19

Recording: TOC-weekly-20200819-audio-only.mp4

Agenda

Call for Scribe (minutes owner): Jinri Huang, CMCC

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair		Lusheng Ji	X
China Mobile	Jinri Huang Co-Chair	X	Weichen Ni
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
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
- There is no comment raised on the 0812 meeting minute.
  1. Decision: Moved by David Streibl and seconded by Ganesh Shenbagaraman, without objection and abstention, the 20200812 meeting minute is approved.
Review of Today's Agenda
- One new items added:
  1. Mailing list issue (stop "main" for discussion, use "discussion" list)
Release Votes and Approval.
Copyright update.
- No update on this. EC is too busy to process the request. Jinri and Jack will continue to follow; Meantime, the written request by John has already been forwarded to EC and the legal team, waiting for response;
- John: about A1 spec. the code is already ready, whether waiting for 60 days before releaseing the code needs feedback from O-RAN; JInri understood the issue and will continu to follow;
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- Jinri mentioned that he noticed there was a TIFG-RSAC call on Monday discussing the MVP and asked for any update.
- Rittwik responded that Koo is writing the minutes. This topic is also discussed in RSAC and he has uploaded the material. The goal is to come up with MVP requirement for TIFG.
- Jinri asked about the concusion? What MVP should be?
- Rittwik responded different people have diffrent Ideas. From OSC perspecitive, it is clear. We focus on 3 use cases. Want to validate them. For example for traffic steering, the minimum requriements include UE attachment, get E2 data, do the hand over. That is min. requiremens.
- OSC should provide min. requirement that TIFG can review. And TIFG should come up with test spec.
- Jinri invited Rittwik to to attend the call with WG1-UCTG, WG1 co-chairs and TIFG co-chairs to discuss MVP.
- JInri asked a question on whether high level requirements are not enough for MVP.
- Rittwik: Not high level. We had call flow there.
- Question from Jinri: do you expect description of the features on certain interfaces?
- Rittwik: call flows dictate what are the components and interface. If a call flow does not show, then not necessary. E.g. in O-CU discussion, the E1 interface is not required, then it is not required for traffic steering use case (as a minimum requirement).
Status of Open Action Items (Old Business).
1. O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation/requirements b/w O-CU and the other projects
  1. see below. discussion combined with item 8b.
2. O-CU PTL to prioritize the items shown on the presentation slide (https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2) to make sure some key features such as handoff could be supported for traffic steering use case.
  1. Ganesh indicated that there was already some discussion on this topic in RSAC. MVP was discussed. A concern is raised in that now we are running out of time for cherry. What content to agree for traffic steering use case in terms of E2 messages, lelvel of CU-DU functionalities etc.. For this Ganesh followed up DU team. They seemed to be ready with message with some already implemented in Bronze release and the others in this release. Question is about CU: By when to finish the work? Need decision from TOC on how to proceed considering that we do not have enough time to push all the content. How to prioritize?
  2. Rittwik: There is no enough visibility of CU in the wiki (need weekly meting update. Need weekly meeting with others). It is difficulty to track the features. No idea on aligning or misaligned with planning. Suggest to prioritize some features to ensure traffic steering to be realized.
  3. JInri indicated that there was a re-org inside CMCC and the O-CU PTL has moved to other position. the O-CU work is not the major obligation. We are discussing with a partner company.
  4. Q: how many features for O-CU in Cherry release?
  5. A: UE Attach; Hand over action, traffic steering app to provide the control action.
  6. Q: Did O-CU project promise to support the features?
  7. A: NO. O-CU is working on other aspects.
    1. AP: The team to arrange an offline meeting to further discuss the challenges. Gu Su from China Mobile can help.
3. PTLs to keep Cherry deliverable summary tables up to date
  1. Reminder from Jinri again ont his matter.
  2. Matti: What is the summary table means? For Bronze release , we hve a wike page. Not one for cherry. Where to update? Or is it excel spreadsheet?
  3. Lusheng: a wiki page with template, will it help? Farheen do that last time. Lusheng will help this time.
    AP: Lusheng to create a wiki page with a template for PTL to fill in the Cherry deliverable summary
4. SMO Project PTL Nominations
  1. Jack to talk with Trisan offline to make sure the voting process is right.
    1. Jack is out recently. Trishan to send Jinri the voting process.
    2. AP: Trishan to send Jinri the voting process.
  2. Presentation from the two nominees
    1. Presentation by Liam Fallon.
      1. Q: in addition to ONAP, what other open source communities are you heavily involved and contributed?
      2. A: Mainly ONAP. Yet also moved around LINUX, internally (inside Ericsson) wrote linux kernel (not contributing);
      3. Q: Your role in ONAP?
      4. A: Design the architcure policy framework; involved in control loop committee, lead the development part in Ericsson; is one of the biggest contributors for Ericsson in ONAP;
      5. Q: What is your view on the relationship b/w SMO and ONAP; i.e. what components should be developed in ONAP and OSC respectively?
      6. A: Not doing SW in OSC which has been developed in ONAP; The OSC coding would be more about use cse side of thing as user advise. Bringing back to ONAP would be powerful;
    2. Presentation by Mahesh Jethanandani
      1. Q: If becoming the PTL, how many resources to bring in?
      2. A: Have contact with OSN, OPENDALYLIGH etc. Could generate enough interest in the group. They would be interest.
    3. For the next step, Trisan will contact JInri and start the voting process. There is a tool for the voting;
5. Repo request from RIC project:
  1. it is clarified that it is for RIC-APP project and the request has already been done;
6. PTL to provide informaion regarding O-RAN-related open source communities
  1. Reminder again from Jinri on this topic. There will be a TSC call in two weeks. need to report the progress there.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
1. O-CU OSC plans
2. Mailing list issue (stop "main" for discussion, use "discussion" list)
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.
1. Decision: Moved by David Streibl and seconded by Ganesh Shenbagaraman, without objection and abstention, the 20200812 meeting minute is approved.
2. AP: The team to arrange an offline meeting to further discuss the challenges. Gu Su from China Mobile can help.
3. AP: Lusheng to create a wiki page with a template for PTL to fill in the Cherry deliverable summary
4. AP: Trishan to send Jinri the voting process.

2020 08 12

Recording: TOC-weekly-20200812.mp4

Agenda

Call for Scribe (minutes owner): Jinri Huang from China Mobile

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	X	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	X	Weichen Ni
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
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. There is no comment raised on the 0805 meeting minute.
  1. Decision: Moved by Jinri and seconded by David, without objection and abstention, the 20200805 meeting minute is approved.
2. Jack also mentioned that the history TOC meetings are also archived. The link is at the bottom of the page.
Review of Today's Agenda
1. No new agenda items raised. Some topics, such as some remaining question regarding the Bronze Maintenance Release, the nomination status etc. will be discussed in old business section (e.g. release note etc.)
Release Votes and Approval.
1. Jack mentioned that there were a couple of APs last week regarding the Maintainence Rel.
2. Lusheng responded: one request is from Jinri which is about a summary of changes. That was done. See https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=14221635. Regarding the licensing, 2 ways. One is to manually went through all the updated files to make sure the licensing is ok. Another check is done by Steve from LF. No problem found. Also clarified that O-CU is not in the scope.
3. Jack: did that address people’s questions to cover the maintenance Release? Any more question? No response.
4. Motion moved by Lusheng to accept and release the Bronze maintenance release;
  Jinri seconded;
  There was a comment from John-Paul, indicating that he was not on the call last week. Will vote in the dark. Jack indicated that last week John Keeney was the deputy and he did not raised an critical issues. Indeed, he also indicated some updated on NRT RIC in the maintenance release. John is fine with the response.
  ALL the TOC members voted yes. There is no objection/abstaintion.
  Decision: The maintenance release is approved.
Copyright update.

Jack: raised the issue in EC meeting, there was a good discussion. EC members are working together to improve the situation. Right now, the copyright is not available to us until after 60 days;
Jinri commented that during the EC call, there was a draft proposal which is to provide “draft approval” for the usage of copyright within 60 day window. However, that was just an idea. Still need further confirmation from EC in the future.

Marketing of the current release (WG, LF, PR)
1. Jinri indicated that this item is not just about marketing. It should be related to many other O-RAN issues. Suggest to change the name to O-RAN-related business (EC/TSC/WG/, marketing etc.);
2. Jinri indicated recently O-RAN has initated the work on TSC-level minimum viable product (MVP) which is important to OSC’s future planning. Will come back with more information when there is more consolidated result.
3. Jack also indicated that more representation should be in the RSAC from different companies. All the major companies involved should be part of the RSAC committee. PTL have already been there. Operators should also be there too. So people could understand better. Sometime, two lines of items means 2-year coding. Understanding where the SW is from our standpoint to where we can achieve, the goal is important to their process. RSAC should be involved in the discussion. At least some people. It is daunting to steer through the list of spec. and capabilities for any particular release. Always a lot of opportunity there. Yet what to focus with the limited resource? How to do that? Getting more people involved. RSAC is important.
4. Lusheng will be leaving on from the assignment from a couple of weeks later, expecting people to step in and help; will be some big gap (lusheng has been doing a lot); need more participation in that space; ATT will participate yet need someone to take leadership there;
Status of Open Action Items (Old Business).
1. O-CU project to provide O-CU introduction on Cherry planning
  1. O-CU update. See the presentation. https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2
  2. Questions are raised on e.g. whether the handover procedure could be supported, how/when the O-CU could be integrated with O-DU-HIGH. Some discussion on this. No conclusion. A suggestion from Jack is to request O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation. Another suggestion from Rittwik is to prioritize the items shown on the slide to make sure some key features such as handoff could be supported for traffic steering use case. It is indicated that if we wait for the 3GPP O-CU features to be finished and then add on the E2 support, it will be two release late.
  3. AP: O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation/requirements b/w O-CU and the other projects
  4. AP: O-CU PTL to prioritize the items shown on the presentation slide (https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2) to make sure some key features such as handoff could be supported for traffic steering use case.
2. PTLs to keep Cherry deliverable summary tables up to date
  1. A reminder to make sure work is ongoing. Will go throught the table in the upcoming week;
3. SMO Project PTL Nominations
  1. Currently there are two nomination from Ericsson and VMWare. The nomination will be open until next week TOC call. After that, the voting will be kicked off.
  2. AP: Jack will talk with Trisan offline to make sure the voting process is right.
  3. Next TOC call, the candidates will be invited to give a short introduction talk.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
    1. Matin not here. Alex made the presentation which is on https://wiki.o-ran-sc.org/display/OAM/2020-08-12+OAM+report
    2. There was a question out there relevant to OTF team and Alex is suggested to reach David Kinsey for help.
    3. Question from David: If go with DECA microseverice, how much of the DCAE needed up and running in the environment for the OSC to be functional? No conclusion/answer to it. Will be discussed in RSAC. In particular, it is also related to the job division b/w SMO, OAM, ONAP.
      David: RSAC this week not holding meeting, rittwik not available. Suggest to hold this question off and line it up after we have the SMO vote to make sure have right people on; Later there will be two RSAC meetings per week. We are already a little behind for the cherry;
    4. Jack: Regarding how to work with other projects, EC is pushing us to enhance the cooperation; would like to make sure RSAC involved in any requirements we asked for. There is a Jira request on our side document that request and how we can use it. Be careful about how much we build requirement for ONAP. Not all the communities are committed to ONAP. Have to make sure the committeement we made. That is why we need more participation in RSAC going forward. Need better job of coordination;
    5. Tracy: for some of the requirements that are understood, are you meaning creating corresponding jira ticket in the OSC or coross-referencing? Jack: yes. Not want to duplicate things. There is need to record the process so O-RAN can find out what we are relying on them.
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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)
1. A repo request for approval in the email. TOC should vote offline.
2. Jinri reminded the request to PTL on the reflector regarding the provision of O-RAN-related open source communities informaiton.
Meeting Summary (resolutions, new action items, etc.
1. Decision: Moved by Jinri and seconded by David, without objection and abstention, the 20200805 meeting minute is approved.
2. Decision: The maintenance release is approved.
3. AP: O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation/requirements b/w O-CU and the other projects
4. AP: O-CU PTL to prioritize the items shown on the presentation slide (https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2) to make sure some key features such as handoff could be supported for traffic steering use case.
5. AP: Jack will talk with Trisan offline to make sure the voting process is right.

2020 08 05

Recording: TOC-weekly-20200805.mp4

Agenda

Call for Scribe (minutes owner): Lusheng Ji (AT&T)

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	Y	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	Y	Weichen Ni
Deutsche Telekom	David Streibl	Y	Ondřej Hudousek
Ericsson	John-Paul Lane		John Keeney	Y
NTT DOCOMO	Masafumi Masuda	Y	Anil Umesh
Nokia	Juha Oravainen	Y	Thoralf Czichy
Orange	William Diego	Y	Vincent Danno
Radisys	Ganesh Shenbagaraman	Y	Sachin Srivastava
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. Moved by Jack, seconded by John (Keeney), no objection, minutes approved.
Review of Today's Agenda
1. No new agenda item requested.
Release Votes and Approval
1. Maintenance release status: NonRTRIC updated to 2.0.1; INT added demo scripts; unmet objectives moved to Cherry;
2. Q: William: status of O-CU. Jack: source code only for now; testing/build will be in Cherry.
3. Q: Jinri: summary of changes. Lusheng: Not yet; will provide.
4. Q: Juha: license scan? Lusheng: Not yet; will do.
5. Jack: table vote till next week, pending the action items raised by Q's.
Copyright updates
1. Board info received from Zbynek. Not reached full conclusions yet. Have some resolutions, for example EC can grant Copy Right approvals regarding ASN/1 messages, APIs, for OSC to develop. But still some minor issues remaining to be clarified before this is fully concluded and communicated to OSC.
2. John Keeney: for code developed before CR grant, how to handle copy right owner request (e.g. reassignment), or treat the 60 day cool off period as dev dead zone?
  1. Jack: our permission for dev from O-RAN Alliance is at the end of 60 day cool-off for the copyrighted materials. Clarification will need to bring to the legal team response beyond this point. Need emails from John and Thoralf for framing the specific questions to legal.
Marketing of the current release (WG, LF, PR)
1. Jinri: not marketing, but some "O-RAN Alliance related issues".
  1. Mirror sites for Asia and Europe: O-RAN board requested OSC to investigate.
  2. EC asks us to provide a list of O-RAN related components being dev in ONAP and by whom; Jinri will send email to reflector for details of the request;
  3. TSC asks us to provide list of O-RAN-related open source projects (e.g. ONAP, Acumos etc.).
2. John Keeney volunteering for providing info from Non RT RIC perspective; Trishan and William offering help for investigating ONAP side.
3. Tracy: interested in other open source projects than ONAP? Jinri: Yes
Status of Open Action Items (Old Business)
1. No open action items from before. Going forward will add these 2 items: reflectors and inter-relationship with other open source projects.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
  1. Skipped due to Rittwik not able to make it to today's meeting.
3. user-d3360 Integration and Test
  1. Dev sprint demos will start from Dev Sprint 2 (for achievements from Dev Sprint 1)
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
    1. Maintenance release enhancements: bug fixes, cert management;
    2. For Cherry:Latest of A1 (pending instructions on what to do with the 60-day cool off); SMO scope alignment; Upstream A1 to ONAP
      1. Jinri: EC meeting is next week for getting clarification on the 60-day cool-off. Need specifics on what questions to clarify.
  2. Matti Hiltunen RIC Applications (RICAPP)
    1. Skipped due to Matti not able to make it to today's meeting.
  3. Thoralf Czichy RIC Platform (RIC)
    1. Near RT RIC has a demo next week.
    2. E2AP spec update from Alliance. Configuration transfer; fail-over and scalability, we will see if we can fit in Cherry (discussion with Rittwik).
      1. Jack: make sure what's planned captured in NearRT RIC Platform project Cherry summary table.
    3. Welcoming Samsung and HCL participating in NearRT RIC Platform.
    4. Bronze release back log issues in E2 term/E2 mgr, sub mgr: work in progress. 1 under review (hopefully demo next week). RIC-444, RIC-628 in Dev Sprint 2.
  4. user-a934b O-RAN Centralized Unit (OCU)
    1. Jack: many interests in O-CU. Can Yingying provide a 10~15 min talk on O-CU plan for Cherry next week or the week after? Jinri: okay.
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
    1. Sphoorthi:
      1. ODUHIGH tried to integration effort with ODULOW during maintenance release, aligned with Intel's FAPI file.
        Code in master branch now, do we need to move to bronze branch? Lusheng: not have to because this does not impact the (reduced) maintenance release objectives.
      2. FAPI file from Intel not fully aligned with spec. O-DU HIGH implementation aligned with Intel file.
        Jack: A gap that needs to be raised in documentation, make sure Intel follow through, put in a JIRA ticket to track.
      3. Cherry features: UE attachment. O1 interface (minimum health-check)
    2. Ganesh: Welcoming HCL to O-DU HIGH participation.
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (TBD) O-RAN Radio Unit (ORU)
5. Jack: reminding PTLs on keeping Cherry deliverable summary tables up to date. Will continue on remaining projects. Call on SMO project PTL and contributors, will discuss more next week.
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.

2020 07 29

Recording: GMT20200729-120223_Zoom2-O-RA_1920x1020.mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
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		Sachin Srivastava
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. Vote to approve minutes for 22 Jul 2020
2. On motion made by Jinri Huang
3. Seconded by Juha Oravainen
4. VOTE: Vote taken, item passed
Review of Today's Agenda
1. We will continue about the SMO and the voting.
2. Review the maintenance release and schedule.
3. Discuss Minute taking and scribe. We have to rotate among the TOC members.
4. Discussion on Cherry
Release Votes and Approval
1. SMO Vote: Jack: Last week a few people dropped early. We got 4 in favor 1 abstaining 1 against. We need to get to 5 votes across TOC even though we had majority present I want to make sure the TOC takes time to work through it and get approval. We have a standing motion on creating an SMO project brought by Rittwik on the RSAC committee. Are there further clarifications.
  1. AT&T, Ericsson, NTT DOCOMO, and Nokia voted in favor. Jinri abstained.
  2. Jinri: I would like to change my vote to Yes.
  3. William from Orange votes in favor.
    1. Vote to add the SMO project to O-RAN SC.
    2. On motion made by user-59b16
    3. Seconded by John-Paul Lane
    4. VOTE: Vote taken, item passed
  4. Jack: We need to add the SMO to wiki and create a repo in gerrit. Action/ user-59b16 add the SMO project to the wiki and gerrit.
  5. Jack: We will need a PTL. Looking for people to take on a role as a PTL for the new SMO project. We should be following Best Practices. As an interested party anyone can contribute to the project. Requires an LF ID. We prefer you use your company's email. If you want to take a more active role you can offer to be a committer. There are a small number of committers per project, minimum 2, maximum 5. The PTL can also be a committer.
  6. You also have to sign the CLA agreement for licensing. There are two different licenses
    1. Apache license
    2. O-RAN license
    3. For SMO we expect contributions under the Apache license. We are not under the 3GPP interfaces. One of the questions asked by EC. For RIC Near RT controller we have separate applications. We are going to try to capture these applications as SMO applications and continue to see if that works or we need to separate. R-Apps under the SMO projects. We will create a structure that clearly identifies the people.
  7. Action/ user-59b16 start the Principles we will kick the wiki off with these principles. The RSAC has proposed minimum viable product. Looking at O-RAN Alliance working groups specifications. If we don't find specs there then we try to work with them towards the specification so we are not creating throw away code.
2. Lusheng: Email voting request was sent to the ML on July 9th. The vote if for 3 procedures and best practices.
  1. All gerrit code submissions to include at least 1 Jira issue. This is for tracking purposes. This creates a Link between gerrit submissions and Jira issues.
    1. We currently have 3 votes. Who wants to vote in favor?
    2. Jinri: I thought I already cast my vote via email. I vote yes.
    3. Jack: I vote yes.
    4. That brings us to 5 votes.
    5. VOTE: Vote taken, item passed
    6. Lusheng get clarification from LF how to list multiple issue IDs to gerrit.
    7. Will this be a gerrit pre-check?
    8. Yes, the system will return with a warning message.
  2. License scans are not done until one or two weeks prior to a release. We require more time. LF does not scan SCP repos. That leaves those repos open. LF does have a tool called nexus iq. People have been using that to do license scans. Because of the language the security vulnerability may not be helpful for Java but for Go C++ is not as helpful. Requesting all the repos to add this nexus iq job. Action item for repo owners is to define a job. There are samples available for you to follow.Any questions?
    1. On motion made by Lusheng to include a license scan to all repos.
    2. Seconded by Jinri Huang
    3. Vote taken item passed
  3. Adopting semantic versioning for the artifacts (libraries and docker images and use it for the artifacts). The action item is for the developers and contributors in the future please use major, minor, and patch versioning. We can write some best practices in the future but this is the format. Another action item is what will be the best way to verify a version.
    1. On motion made by Lusheng to include a semantic versioning process to all repos.
    2. Seconded by Jinri Huang .
    3. Vote taken item passed
Copyright updates
1. No updates on copyrights
2. Jinri: Zbynek sent an official copyright notification to us.
3. Jack: We have an action item that we have to make a proposal to the EC with Stefan but that is still in process.
4. John-Paul: Is this the 60 day impacts?
5. Jack: No we were talking about the copyright permission from O-RAN Alliance on any copyrighted material. The 60 day gets approved by us and we're refining the language for that feature. That is an alliance issue when the material can be managed copyright material.
6. John-Paul: Is that resolved?
7. Jack: Has the 60 day copyright IPR issues resolved?
8. Action/ Jinri Huang will check with Zbynek of whether this will imapact.
Marketing of the current release (WG, LF, PR)
Status of Open Action Items (Old Business)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
    1. August 1st is the close out date. I will look to Lusheng to give us a report but I think the progress is less than hoped for in a few areas.
    2. Lusheng: Status: we have a couple deliverables planned.
      1. O-DU Low running in the OSC integration lab and completing the O-DU high. This is lagging behind. We've been having system related issues. We had 2 dell servers. For some reason the NIC and FPGA cards do not work right on these two servers. Later we got the wolf pass servers. We're having problems installing OS on this server. It will not make it to this weekend.
    3. KPI-MON xApp flow the near real time xApp team have been trying to build the docker image with other xApps to complete this flow. There were some problems with the routing.
      1. Matti: The subscription manager is rejecting the request. I reached out to the team but have not gotten the response. The internal communication is working but given the time I am not sure we will deliver.
    4. Additional minor improvements in documentation and the integration repo to upload demo scripts for people to run the demo.
    5. Rittwik: O-DU High is ready to integrate with O-DU Low.
    6. Lusheng: The O-DU High can follow the future enhancement to move feature code in Bronze release, update their release notes.
    7. John Keeney We don't see the verification jobs when we release. I assume there will be full integration tests. I want to know if we can help.
    8. Lusheng; The issue is the base image that your docker file requires has expired on the staging docker registry. We need to generate that first.
    9. Henrik Anderson: Will the staging jobs be ready?
    10. Lusheng: The LF has two registrys STAGING and RELEASE. If it's in the staging registry it will live there for 30 days. Jenkins has a job that will regenerate the newest version of the base image. That image gets refreshed. It will exist in the staging repo. The build reference is to the previous version of the base image. We need to figure out to regenerate.
    11. Henrik: When we push things to the Bronze branch they don't exist in the staging repo.
    12. Lusheng: Let's work offline.
    13. Jack: We are looking for people who will be interested in Integration and Test. Lusheng will be reducing his time. We need more participation in the integration and test area beyond their project. We need coordination work to have a few more people involved.
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
  1. Rittwik: EC has reqested a requirements document for the RAN simulator. That allows us to socialized with the EC and TOC for bidding for a RAN simulator.
  2. Jack: Any PTL who wants to leverage the simulator beyond planning and generating data should communicate to your their requests and requirements. Anyone who has needs in that space reach out to user-59b16 for the Cherry release. Since there is a cost associated we want to make sure we're getting everyone's input.
  3. Are all the use cases finalized for Cherry?
  4. Rittwik: Yes, they are in the wiki and lifecycle management for the SMO and the traffic steering and health-check use cases.
  5. Matti: I have new teams that want to contribute to xApps. I will reach out to you.
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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.)
1. Actions
  1. Action/ user-59b16 add the SMO project to the wiki and gerrit.
2. Votes
  1. Review and Agree to Minutes of Previous Meeting
    1. Vote to approve minutes for 22 Jul 2020
    2. On motion made by Jinri Huang
    3. Seconded by Juha Oravainen
    4. VOTE: Vote taken, item passed
  2. Vote to add the SMO project to O-RAN SC.
    1. On motion made by user-59b16
    2. Seconded by John-Paul Lane
    3. VOTE: Vote taken, item passed
  3. On motion made by Lusheng to include a license scan to all repos.
    1. Seconded by Jinri Huang
    2. Vote taken item passed
  4. On motion made by Lusheng to include a semantic versioning process to all repos.
    1. Seconded by Jinri Huang .
    2. Vote taken item passed

Show all results

Space shortcuts

Page tree

Technical Charter for O-RAN Software Community

TOC Voting Members

TOC Meeting Info

2020 09 23

2020 09 16

2020 09 09

2020 09 02

2020 08 26

2020 08 19

2020 08 12

2020 08 05

2020 07 29

Archived Meetings

Space shortcuts

Page tree

O-RAN SC Technical Oversight Committee (TOC)

Technical Charter for O-RAN Software Community

TOC Voting Members

TOC Meeting Info

2020 09 23

2020 09 16

2020 09 09

2020 09 02

2020 08 26

2020 08 19

2020 08 12

2020 08 05

2020 07 29

Archived Meetings