Technical Charter for O-RAN Software Community

Heads Up! Different International Timings for Daylight Savings (Fall back one hour)

2020 02 05

Recording: 2020-02-05-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		Lusheng Ji	x
   China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar

   *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 there were no comments, questions or corrections.
      1. Vote to approve minutes for 29 Jan 2020 
      2. On motion made by Masafumi Masuda
      3. Seconded by William DIEGO
      4. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Release Votes and Approval
   • Maintenance window closed last Saturday.  Lusheng asked PTLs to update their information.  
   • Action/ user-d3360 Ask PTLs to update the Status column on Amber Maintenance (Feb, 2020) page.
   • Is there a doc meeting required for the maintenance release?
     • The docs project will automatically update the documentation.
   • Except for the Amber Maintenance (Feb, 2020) update the maintenance release is complete?
     • Bug fixes.
     • Unfinished features had an opportunity
   • Motion made by user-d3360 to approve the Amber maintenance release on 05 Feb 2020 
     • Seconded by MASAFUMI MASUDA
     • VOTE: Vote taken, item passed
6. Marketing of the Amber release (WG, LF, PR)
   1. MWC (Barcelona)
      1. Jinri - More about O-RAN Alliance demo.
         1. for this year O-RAN Alliance will have 23 demos which will be scattered from different sponsors.  This is a large number considering O-RAN Alliance opened it's membership 1.5 years ago.  It already had 150 members.  There are 26 operator members.
         2. O-RAN does not have it's own dedicated booth.
   2. O-RAN Alliance F2F Feb 17-21 (Paris)
      1. Jinri - will have to leave in 10 minutes for an adhoc TSC meeting regarding the current tense situation caused by the Corona virus in China. The F2F may be changed to an online virtual meeting or have the attendees meet remotely.
      2. For the TOC meeting Agenda 
         1. Take an opportunity to introduce our Bronze release.
         2. Require the PTLs to bring their project status report for the discussion.  PTLs can introduce additional functionality in order to support the Bronze release.  What is the current status, challenges, and architecture.
         3. Bring your alignment with the working groups in particular WG3.
         4. Jinri will bring brief TSC reports from TOC.
         5. When and where will we know about the decision about the F2F.

         6. Do we simply point to the Jira tickets or should we have a slide deck?

            1. Slide decks are preferred because they will distributed to other O-RAN Alliance WGs.  This is a good opportunity to share your accomplishments with the WG.  Looking for design, timeframe, challenges, and most importantly WG alignment.

            2. Two weeks to go for F2F so we need to prepare.

         7. Action/ PTLs get your F2F slide decks ready.  That is in 3 days.

   3. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
      1. Ericsson submitted a proposal for a panel discussion that will discuss the results in Amber plugfest.  Confident that the proposal will be accepted.  We are trying to get visibility for OSC-Amber and get everybody excited about OSC Bronze.
      2. Action/ Jinri Huang  Tracy Van Brakle  suggested speak with Paul about the demos at ONES.
7. Status of Open Action Items (Old Business)

   1. Action/ Farheen - Get the information from Jack and put it on the events page of the wiki.

   2. Action / TOC voting members: Provide an alternate contact on the TOC list above.

   3. Action/ Thoralf Czichy update the TOC with the new Nokia TOC members.

   4. Action/ user-59b16 talk to Jack to send out an email to the new TOC members; Nokia, Ericsson, and Radisys.

   5. Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.

   6. Action/ user-59b16 update TSC with the short/long term UE simulator support.  

      1. He has been talking to members regarding feasibility but not sure if he has gotten commitment for it.
      2. ENGWEI KOO user-59b16 asked Engwei to join.  We created a slide to better understand the UE simulator.
      3. Shared a high-level slides.
         1. We are looking for the O-DU, O-CU generating messages to the real time RIC.
         2. Engwei - Are you looking for OCU simulator that's connected to 
         3. We need emulator UE KPIs that represent the RF signal strengths of neighbors so we can predict based on signal strength whether the UE quality of experience from a neighbor or serving cells.  We need those measurements and KPIs.  Cell utilization metrics are also needed.  
         4. Engwei set up a call with user-59b16

   7. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.

   8. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.

   9. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.Take a look at the template and fill out what you can.  If you don't have information then let Martin know.

      1. PTLs provide general or any kind of alarms 

   10. Action / On the Bronze release page update their table.  A few have but I would like everyone to begin filling out their tables.  Convey to people outside what we're going to do in this release.

   11. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.

       1. Readout June 25 and as we get closer we'll have a project plan.  We are focusing on two first responder scenarios.  Tracy posted the slides on the wiki.
       2. Action/ Tracy Van Brakle send the URL for the POC.  

   12. Action/ PTLs update Architecture pages.

       1. user-d3360  send out a reminder to PTLs.
8. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release - is closed
      2. Project Bronze Release
         1. Working with LF on the CI/CD pipeline.  Contact user-d3360 if you have trouble with the CI/CD pipeline.  Jenkins server has been acting up.
   2. user-d3360 Test & Integration Planning (INT)
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
         1. list of draft epics: use this JIRA filter as per Jira usage conventions. Seven subteams now analyze this draft.
         2. Traffic steering derived JIRA epics: filter (2 of 4 are currently in Bronze) // Health-check derived JIRA epics: filter . Already sure that not all will fit in Bronze.
            
      3. user-a934b O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
   4. user-59b16 Requirements Software Architecture Committee
9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. Intel contributions - Jack is working with legal issues with binary contributions. C++ compiler to build G++ for Amber.  The G++ performance is not as high as Intel.
   2. Contact user-59b16 or David Kinsey if you want to contribute to the 
   3. Formalizing structure for release management.
   4. We need a release manager.
10. Planning for Next Meeting
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)

2020 01 29

Recording: 2020-01-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	x	Weichen Ni
   Deutsche Telekom	David Streibl	x
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar

   *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 there were no comments, questions or corrections.
      1. Vote to approve minutes for 29 Jan 2020 
      2. On motion made by Jinri Huang
      3. Seconded by user-2057e
      4. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Release Votes and Approval
   1. Into near-RT RIC section: Already handled by e-mail: Approval obtained from TOC for new repo o1 in near-RT-RIC: https://lists.o-ran-sc.org/g/toc/topic/new_repo_ricp_near_rt_ric/70071381?p=,,,100,0,0,0::recentpostdate%2Fsticky,,,100,2,0,70071381
      1. We are in the last week of the maintenance release approval.
6. Marketing of the Amber release (WG, LF, PR)
   1. MWC (Barcelona)
   2. O-RAN Alliance F2F Feb 17-21 (Paris)
   3. ONES = LF Networking Conference in April (Los Angeles).  
      • Open Networking & Edge Summit Event
 
      • There doesn't seem to be interest in activities at ONES.
        • Tracy - There will be a discussion today whether or not we should have the POC Plugfest at ONES.
          • That would be a paper which will be acceptable option that we can discuss.
          • Rittwik - Thoralf, Matti, and I are going to put an abstract together.
            • Jack - If people want to submit talks then include everyone in your community.
7. Status of Open Action Items (Old Business)
   1. Action/ Jinri Huang add a few lines to MWC.
   2. Action/ Farheen - Get the information from Jack and put it on the events page of the wiki.
   3. Action / TOC voting members: Provide an alternate contact on the TOC list above.
      1. We have approval for new seats for new TOC members. 
      2. The TSC will vote to approve the new TOC members of the O-RAN SC who will serve as voting members from 01 Apr 2020  - 01 Apr 2021 
      3. Nokia, Radisys, and Ericsson will be TOC members for next year.
         1. No one from Radisys is on the call.
         2. No one from Ericsson is on the call.
         3. Action/ Thoralf Czichy update Nokia.
      4. Action/ user-59b16 send out an email to all three new companies above.
   4. Action/ user-59b16 send Alex Stancu contact for UE simulator support.  
      1. we need better coordination with the test focus group in O-RAN.  I'd like to ask if one of the other TOC members will take on the role of coordination with the test group so we can come up with a common plan in the test group.
      2. Rittwik - Martin and Alex have a TM500 for the POC. This is where the UE simulator talks to the BU.  Martin - The labs are in Europe and can not be used for a long run.
         1. Jack - We appreciate the stop gap but need to work on coming up with a long term solution.
   5. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
   6. Action/ user-d3360 set up a call with John Murray, Trishan de Lanerolle, Jinri Huang regarding license differences from the LF license scans for logging.
      1. The issue was from O-DU low Intel using binary as upstream and use ICC compiler.  We discussed this and you started the discussion on the legal side.
         1. Jack can speak to the licensing but editing the compiler.
         2. Action / Lusheng update and make it clear.
         3. Intel has a provision that allows them to use their license code.  But because it's the O-DU project it is not OSI approved.  We are working with them to allow O-RAN project to use their Intel code.  They plan to use it as a test or demo apparatus.  If a company decides to build their own O-DU they would deal with Intel to address their licenses to use that code.  This will allow us to use the Layer 1 binary that will make it easier to work.  The Intel binary is officially part of the O-SC project.  It is used for test purposes only.
   7. Action/ user-d3360 send Trishan de Lanerolle and email with the question regarding the license discrepancy.
   8. Action/ Martin Skorupski will provide the PTLs a template spreadsheet for alarms.  VES collector will display the alarm list.
   9. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.Take a look at the template and fill out what you can.  If you don't have information then let Martin know.
   10. Action / On the Bronze release page update their table.  A few have but I would like everyone to begin filling out their tables.  Convey to people outside what we're going to do in this release.
   11. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
   12. Action/ PTLs update Architecture pages.  
8. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release
         1. Lusheng - is not aware of any feature updates beyond bug fixes.
         2. Action/ Rittwik - Talk to Jack about Radisys involvement.  
            1. They understand the flows.  We discussed except there is no O-CU to provide the metrics.  I asked Radisys they're thinking about using their closed O-CU API on a black box. 
            2. Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.
      2. Project Bronze Release
         1. Thoralf Czichy proposes that near-RT RIC platform functionality (content) freeze is Feb-7. This is as there's a near-RT RIC platform contributor planning f-2-f workshop planned Feb-3 to Feb-5. Bronze Timeline doesn't have an exact date (drawing suggest in week of Feb-3 to Feb-8). Preliminary content is here: filter10401.
            
         2. Matti asked for an extension for the RIC app.
            1. Both RIC and RIC apps will finalize their commitment in Jira next week.
   2. user-d3360 Test & Integration Planning (INT)
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
         1. list of draft epics: use this JIRA filter as per Jira usage conventions. Seven subteams now analyze this draft.
         2. Traffic steering derived JIRA epics: filter (2 of 4 are currently in Bronze) // Health-check derived JIRA epics: filter . Already sure that not all will fit in Bronze.
            
      3. user-a934b O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
   4. user-59b16 Requirements Software Architecture Committee
9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. Ask LF for more support for CI.  Code changes and submits don't mandate a connection to the Jira id.  If the submissions have a link we can view.
      1. What if we don't turn on the linkage?
         • From contribution perspective not much impact.  This is our current practice we do not add this line.  By adding this line this will force people to use Jira to track the issues.  This adds one more reference for people to investigate.  This is good software practice.  
         • Chris L. Can we start with a phased approach?  
           • yes, does LF support this?
             • you can turn on warning on the gerrit commit content.
               • Lusheng - If the TOC is OK we will do this on a warning basis first.  After M4 we will enforce.  
               • Jira usage will begin with a warning phase and then will be enforced after M4.
                 1. Vote to approve to turn on the warning feature on the gerrit commit content for 29 Jan 2020 
                 2. On motion made by Jinri Huang
                 3. Seconded by user-2057e
                 4. VOTE: Vote taken, item passed
   2. Add a Jira plugin called Test management used for entering test cases into jira.  Request to ask LF to add this test management plugin to be added for 10 users or less.
      1. How many users will be using this?
         1. 3 - 4 tops.  If the Jira platform supports a group of users.
            1. Up to 10 users the cost is $100.  We can revisit if there are more.
         2. Request to ask LF to add this test management plugin to be added for 10 users or less.
            1. Vote to approve addition of test use case plugin 29 Jan 2020 
            2. On motion made by Jinri Huang
            3. Seconded by user-2057e
            4. VOTE: Vote taken, item passed
10. Planning for Next Meeting
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes:
       1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
          1. Vote to approve minutes for 29 Jan 2020 
          2. On motion made by Jinri Huang
          3. Seconded by user-2057e
          4. VOTE: Vote taken, item passed
       2. ira usage will begin with a warning phase and then will enforce.
          1. Vote to approve to turn on the warning feature on the gerrit commit content for 29 Jan 2020 
          2. On motion made by Jinri Huang
          3. Seconded by user-2057e
          4. VOTE: Vote taken, item passed
       3. Request to ask LF to add this test management plugin to be added for 10 users or less.
          1. Vote to approve addition of test use case plugin 29 Jan 2020 
          2. On motion made by Jinri Huang
          3. Seconded by user-2057e
          4. VOTE: Vote taken, item passed
    2. Actions
       1. Action/ Farheen - Get the information from Jack and put it on the events page of the wiki.
       2. Action / TOC voting members: Provide an alternate contact on the TOC list above.
       3. Action/ Thoralf Czichy update the TOC with the new Nokia TOC members.
       4. Action/ user-59b16 talk to Jack to send out an email to the new TOC members; Nokia, Ericsson, and Radisys.
       5. Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.
       6. Action/ user-59b16 update TSC with the short/long term UE simulator support.  
       7. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
       8. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
       9. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.Take a look at the template and fill out what you can.  If you don't have information then let Martin know.
       10. Action / On the Bronze release page update their table.  A few have but I would like everyone to begin filling out their tables.  Convey to people outside what we're going to do in this release.
       11. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
       12. Action/ PTLs update Architecture pages.

Return to Todays Agenda ^

Archived Meetings