Technical Charter for O-RAN Software Community

2020 05 06

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

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

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

3. Review and Agree to Minutes of Previous Meeting 

4. Review of Today's Agenda

   1. Add O-RAN Distributed Unit Low (ODULOW) May 31st Bronze delivery request to the top of the agenda because we ran out of time last week.

5. Release Votes and Approval

6. Marketing of the current release (WG, LF, PR)

   1. Virtual Exhibition.

7. Status of Open Action Items (Old Business)

   1. Action/ William DIEGO update on the coordination with the O-RAN test group
   2. Action/ user-d3360  add the longer term test strategy to the agenda. 

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

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

      1. Project Bronze Release

   2. user-59b16 Requirements Software Architecture Committee

   3. user-d3360  Integration and Test

      1. Gerrit review process improvement
      2. Integration and testing status report
         

   4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

      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)

         1. status update

      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)

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

   1. OAI purposed Meeting
   2. OSC Logo

10. Planning for Next Meeting

11. Any Other Business (AOB) 

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

2020 04 29

Recording: 2020-04-29_toc.mp4

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

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

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

3. Review and Agree to Minutes of Previous Meeting 

   1. Clarify comments about questions about 9.iii.a needed clarity so Farheen updated minutes.
   2. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   3. 1. Vote to approve minutes for 22 Apr 2020 
      2. On motion made by user-2057e
      3. Seconded by weichen ni
      4. VOTE: Vote taken, item passed

4. Review of Today's Agenda

5. Release Votes and Approval

   1. Jack: we will need to vote on how to support the Viavi simulator as a part of our test environment.  At some point we will have to bring to vote a decision to request for funding to support a part of the bronze activity.  We are looking at it as a rental fee on the open source side.  People from Viavi are on the technical side. 
   2. If people are interested in this topic reach out to user-d3360 or user-59b16.  One of our challenges working in the RAN at some point we have to have devices and radios to simulator.  We have a small effort on simulating protocols but RAN simulator is more active.  The short term activity is how do we deal with this in Bronze without a full operating stack.  
   3. We need more paticipation in the test department.  There is a lot of activity going on there.
   4. ORAN Alliance and O-RAN SC are two different leadership. 
      1. Open source focus group in O-RAN Alliance.
      2. TOC is focus group in O-RAN SC.
      3. OSFG is asked to take a vote.  There are recommendations of the OSFG group in the O-RAN Alliance and there are votes for the TOC for the O-RAN SC.
      4. John-Paul Is there any information about the specification project?
         1. Jack: The O-RAN SC has a charter under the LF.  We follow LF guidelines.  O-RAN Alliance funds the LF for the O-RAN SC to operate under 2 licenses.
            1. Apache open source initiative.
            2. O-RAN Alliance license.  I am not a lawyer it is managed by the software alliance entity.  We use the Apache license, Documentation is slightly different.  The O-RAN license is managed by the O-RAN Alliance.  I do not call this an open source license.  In this forum I refer to it as a FRAND license.  We're an open source community we have the Apache license and the FRAND license from the O-RAN Alliance.  
            3. Jack: Look at the charter.  The charter for the OSC is an LLC founded in the USA under a series of LLC under the Linux Foundation.  We also have the O-CU and O-DU High.
            4. Jack: It is intended to mimic 3GPP and the O-RAN FRAND policy.  I am not a lawyer.

6. Marketing of the current release (WG, LF, PR)

   1. Virtual Exhibition.

7. Status of Open Action Items (Old Business)

   1. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
   2. Action/ William DIEGO update on the coordination with the O-RAN test group
      1. William we are working with Viavi to establish a date.  Planning to integrate into the Cherry release timeline.
      2. Jack: I try to give people more time.  I encourage people to work ahead of the next release.  People should be thinking about participating the requirements for Cherry.  This way when we start talking full time about Cherry we are ready.
      3. We will need both long and short term 
   3. Action/ William DIEGO send John Murray the dates from the TIFG slide deck so he can add it to the Cherry Release timeline.
   4. Action / TOC Martin: We want to have data modeling on the wiki in a broader way.
      1. Martin will add a new page and link to the Program Developer Guide.
   5. Action/ Zhimin Yuan Sachin Srivastava come up with a timeline of your activities with user-d3360 because you are not going to make the timeline for the Bronze release.  Try to come up with a plan that will be able to be delivered in the Bronze Maint release for the FAPI and the O-DU Low and High.
      1. Zhimin: we did a lot of time on this.  
      2. Sachin: sharing slide deck.  Adding points.  We are discussing integrating plan.  We talk to Viavi about O-RU and O-CU.
         1. Trying to break into pieces.  Each piece has less dependecies.  We can do the P5 message integration using our own O-RU and O-CU stack.  But the dependency is properly installed and configured.  For O-DU high and O-DU low we got some agreement.
         2. Test Cases Profile For Example is very important for RAN Integration.  We need guidance of which section we should start.
         3. We have had discussions with Lusheng and Rittwik to move forward with the Cherry and Dawn release.  We have had a few gaps with O-DU High and O-DU Low.  We are targeting the P5 messages exchanged between High and Low.  We will be using the third dependency we will be using the L1 and L2 loss because there is no FAPI detector.  From a target perspective we will be targeting the P5 messages using the stub from O-CU.  Going forward we will need to define the use case call flows test plan where we can use O-RU and O-CU.
         4. Jack: Aknowledges and appreciates everyones effort.  Getting the P5 messages are a positive step forward.  P5 is something that will work in the Bronze release or the Cherry Release?
         5. Sachin:
            1. When we will hve the O-DU server to start testing.  I will need help with Lusheng.
            2. Configure the O-DU low and O-DU high. 
            3. Once we have agreement on these two points we will be able to provide a time estimate.  We will be using the Intel software in the lab to save time.
            4. Jack: We have had the Intel software reviewed by the O-RAN legal team.  You can use it.  It will be discussed at the TSC meeting and no one raises concerns we can move forward with using it.  Since it has passed legal review it should be OK.  We are setting up the lab with the servers.  I am making sure that the servers will be available.  I am in charge of that.  Delays are due to everyone working from home.
            5. Action/ user-d3360  add the longer term test strategy to the agenda.  Get it from Lusheng.
            6. Jack: The binary software should never be loaded into the LF repos.  It is built and deployed into the machines.  We have legal clearance to use it but I still have to get the TSC to approve.  We can start a second O-DU software to use a different approach.  Our goal is not to limit ourselves to one option. 
            7. Rittwik: Intel can only give permission by the end of May.  Does this mean we can start working in the lab and have phase 1 tested.
            8. Jack: We have been given legal clearance that we can use it.  As a risk item you can use it but it can't become a part of the official release policy.  
            9. Sachin: O-DU High we had a discussion.  It can be used to do the initial integration.  
            10. Lusheng: It can be a part of Bronze.  It can be integrated with the near Real Time RIC.
            11. Jack: How are we tracking the completeness in a release.  Are we planning to deliver 20% - 50%.  At some time we want to state that success when we do the interoperability testing.
   6. O-RAN Alliance Copyright update
      1. We are working the issue in detail.  Lawyers and board work approvals are ongoing.  It is a logistical issue.  There are no concerns about doing it but how to do it properly.  Part of the challenge is asking for approvals by paragraphs for specifications so we are trying to find out the implementation details.

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

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

      1. Project Bronze Release

      2. Does the time extension apply to all repos?
      3. No only the ones that request exentension.
      4. Lusheng: We have 4 tracks. for healthcheck we have to find out what can be delivered and what needs to be tested.  We need to have discussion with Martin, John, and Thoralf.

   2. user-59b16 Requirements Software Architecture Committee

   3. user-d3360  Integration and Test

      1. Gerrit review process improvement
      2. Integration and testing status report
         

   4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

      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)

         1. Code is planned to be available on May 31.  Can we have O-DU Low for the Bronze release package?
         2. Jack: That puts us at the end of any cycle.  Can we work to put it into the Bronze maintenance release to give us enough time to test.
         3. Zhimin: The testing will be handled before May 31.  
         4. Jack: We will need to discuss further and we are near the end of the meeting.  We don't release code unless it has gone through the open source testing.  
         5. Action / Farheen Cefalu add this topic to the top of the agenda next week.

      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)

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

   1. OAI purposed Meeting
      1. Jack OSC wants a discussion with OSC.  
      2. OAI meeting is taking place?  
         1. Initial meeting between OSC and OAI TOC.  To see if they want to participate as an upstream project and a separate project.
         2. John-Paul: When will the invitation be sent?
         3. Action/ Jack: I will post that.  They have suggested some dates.
   2. OSC Logo

10. Planning for Next Meeting

11. Any Other Business (AOB) 

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