Technical Charter for O-RAN Software Community

2020 07 08

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

5. Release Votes and Approval

6. Copyright updates

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

   1. Bronze Release PR

   2. Virtual Exhibition

   3. OSC Logo status

   4. LF Insights

8. Status of Open Action Items (Old Business)

   1. Action/ John Murray will check the progress of making the Virtual Exhibition being made public.
   2. Action/ Farheen Cefalu add a link to the LF analytics Insight on this page.

9. 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)

         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)

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

11. Planning for Next Meeting

12. Any Other Business (AOB) 

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

2020 07 01

Recording: 2020_07_01_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		Ondřej Hudousek
   Ericsson	John-Paul Lane	x	John Keeney
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Orange	William Diego	x	Vincent Danno
   Radisys	Ganesh Shenbagaraman		Sachin Srivastava	x
   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.

3. Review and Agree to Minutes of Previous Meeting 

   1. The minutes of the prior meetings were reviewed, and no corrections.
      1. Vote to approve minutes for 24 Jun 2020 
      2. On motion made by Juha Oravainen
      3. Seconded by John Paul
      4. VOTE: Vote taken, item passed

4. 1. Review of Today's Agenda

   2. Release Votes and Approval

   3. Copyright updates
      1. Jack will get the new software specifications posted on the site.  The board had a meeting and approved.  The leadership was supportive and excited about the progress.  Virtual exhibition has some nice demos.
         1. John-Paul are there plans to make the Virtual Exhibition publicly accessible.
         2. Action/ John Murray will check the progress of making the Virtual Exhibition being made public. 
      2. Action/ Farheen Cefalu add a link to the LF analytics Insight on this page.

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

      1. Bronze Release PR

      2. Virtual Exhibition.

      3. OSC Logo status.

   5. Status of Open Action Items (Old Business)

      1. Action / user-d3360 add the topic of license attributions to the agenda.  We want to start the pairwise testing.
      2. Action/ John Murray get clarification regarding transfer of AT&T Apache code into the new dual license repo
         1. Apache can be copy forward but we do not remove the Apache license.  We will move that to an inactive status and the Samsung contributions will be in the new license repo.

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

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

         1. Releases Cherry Release Planning

            1. We should be in the epic and what are the main end to end use cases.  

      2. user-59b16 Requirements Software Architecture Committee

         1. Sharing spreadsheet.
            1. OCU Epics.  These are the things we will do with O-CU.  WG8 epics for Cherry.  No Bronze pairwise testing with O-CU.  Still pairwise testing with O-CU High.
            2. OTF Epics. Planning resources for OTF. 
               1. Eliza some epics are lower priority for Cherry.  Also the deployment of xApps and rApps.  That is not here.  Eliza Celenti is coming up with a plan.  
               2. Rittwik will catch up David about call flow.
               3. David Kinsey  yes, we have to establish a timeline and xApp deployment.  We came up with a simple approach of a flow.  We want O-SC to have a Cherry requirement.  This will validate O2.  The app should be able to join with the RIC.
               4. user-59b16  will that touch non RTU RIC?
                  1. David Kinsey not really.  You will have a piece of the SMO and xApp.  The non RT RIC is aware ahead of time and doesn't use A1 to discover.  We should have a discussion but may not be able to form epics.
               5. Non RT RIC is a requirement study.  
                  1. You have to have some software.  Parts are at risk and others are not.  SDK will not be at risk.  The thing in the SMO that would manage the LCM would be at risk.  We are proposing it can be applied to MANO or ONAP but it would have to be downstream to provide real value.
                  2. ACiton/ David Kinsey set up a meeting with Martin Skorupski to continue discussion.
            3. INF Epics
               1. StarlingX is the commercial apps.  Which part is commercialized?  I think StarlingX is what is being commercialized.  What we have with OSC is a derivative of that.
            4. NRT RIC has a lot of epics.  The epics come down to many things.  Some of it may happen in Cherry and some may not.  There is a priority list of High, medium, low.
               1. The PTL and the people need to manage their epics.  The key is to have the E2E use cases working.
               2. The ETE flows have not chained.  There were four health check flows. 
               3. We need to have a checklist of where we are with the end to end flows.  They are complex.  It is important that you give organization for each use case of where we are in the progress of that use check.
            5. We had a discussion on O-DU High on flows but because of resources and time we have to have a prioritized, stretched, and agressive plan to demonstrate significant progress to the overall flow.
            6. ODU-Low epics
            7. Simulator E2 simulator enhancements.  
            8. Traffic Steering xApp Bronze - Viavi decided to contribute access to some of their tools.  Add it to the agenda.  Be sure everyone understands what's available from the simulator. 
            9. What are the major advances that are significant to the E2E use cases.
               1. Get the pipeline working.  For Cherry it is ambitious to get the KPI-MON thru the xApp.  
               2. Mentality how do you get the data just in time and target a UE.  That's the E2E healthcheck validation.  See RSAC Cherry Release presentation.
               3. E2 service model may not be fully complete before sprint development starts.  This is pre-spec. so it will be a challenge.
            10. Healthcheck - The healthcheck flows will not change.  Components will have to adhere.  near RT RIC has not completed their flows.  It is up to the PTLs to take a look.  We need a score card or else we wont know where people are at.
            11. LCM - David is coming up with call flows.
            12. Jack - Does anyone want to add items to our E2E use case.  How do we show A1 functionality?  How do we demonstrate more of the A1 controller as part of the E2E use cases?
                1. John-Paul Is there something required for OR-Apps?
                2. Jack How do we pull cases together like rApps and getting the SDK in place and get rApps.  We have the pieces but to pull it all together we need to create 2 projects.  1 for SMO and who wants to contribute a model.  I want to open up a discussion to create an SMO project and elect a PTL to make an overall system gradually.  I do want people to think about it and who would want to participate in organizing it.  We need to start and manage contributions to it to get to the point of getting rApps in place.
                3. John-Paul If we had an ORApp.
                4. There is a Hello World that can be either rApp or OApp.
                5. We can list some of the code for the R1 interface.
                6. These need to go into more depth in the RSAC.  We can summarize here but the details.
                7. I am getting interest in O-DU Low project.  The question is how best to manage that.  I thought the most effective way is to treat them in parallel.  We can see how much code can be used across them.  There is interest and people will be joining in the next few weeks to discuss.
                8. Rittwik - I will update the spreadsheet.  When the planning is done it is up to the PTLs to run with it.
                9. Jack - The challenge in Cherry is to develop technology adding the O-1 interface and become more of a functional subsystem.  We will get O-CU code that will start to fill out those blocks.  Just because people are active in xApps we don't want to lose the focus of developing all the parts of the stack.  Each component should advance a certain amount in that release in coming up with an O-RAN system.
                10. PTLs think about advancing their modules and making it interoerable with the E2E flows.  We must make it a useful system where people can grab parts of the code and move the whole O-RAN community forward.  Try to make as much re-usable for the community as they leverage those products.  We've gotten through 2 releases and declared the paths we're on.  We have to listen to the larger community and grow participation of people using and contributing the code.  This will only happen if people and companys participate.  
                11. Think of how we can improve Cherry.  Look for ideas of how to improve how we work.  We need to grow and round out.  This is a group of small teams.  O-RAN Alliance is over 200 members we have to get more people to participate.  It is a project for wider participation including service providers not just generating specs but dealing with ramifications of using those specs.

      3. user-d3360  Integration and Test

         1. user-d3360  discuss general practice.
         2. user-d3360  Getting Started

      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)

            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)

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

      1. Discuss SMO 

   8. is Planning for Next Meeting

   9. Any Other Business (AOB) 

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

   1. Votes
      1. The minutes of the prior meetings were reviewed, and no corrections.
         1. Vote to approve minutes for 24 Jun 2020 
         2. On motion made by Juha Oravainen
         3. Seconded by John Paul
         4. VOTE: Vote taken, item passed
   2. Actions
      1. Action/ John Murray will check the progress of making the Virtual Exhibition being made public.
      2. Action/ Farheen Cefalu add a link to the LF analytics Insight on this page.

Archived Meetings