Technical Charter for O-RAN Software Community

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

2020 01 29

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. We will move a vote to the TSC to approve the slate of members from 01 Apr 2020  - 01 Apr 2021 
      3. Nokia, Radisys, and Ericsson will be TOC members for next year.
         1. No one from Nokia
         2. No one from Radisys
         3. No one from Ericsson 
         4. 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. We appreciate the stop gap.
   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 for test.
   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)
9. 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
10. 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 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
    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
11. Planning for Next Meeting
12. Any Other Business (AOB) 
13. Meeting Summary (resolutions, new action items, etc.)
    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

2020 01 22

Recording: 2020-01-22_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 15 Jan 2020 
      2. On motion made by user-2057e
      3. Seconded by MASAFUMI MASUDA
      4. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Release Votes and Approval
   1. No approvals this week
6. Marketing of the Amber release (WG, LF, PR)
   1. Upon Maintenance release  we will do a small notification of Bronze features.
      1. Jinri - PM is preparing PR before MWC.  We can enter a few sentences there.
         1. Jack - Agrees
         2. Action/ Jinri Huang add a few lines to MWC.
            1. I need assistance.
            2. Paul Smith - we are going to be making additions to the PR.  We need changes as soon as possible.
            3. Jack - the maintenance release doesn't have any features.
               1. Lusheng from integration there is a bug fix.
                  1. Jack - Bugs are not something we want to report.
                  2. Is there anything in doing the plugfest?
                     1. Martin - Not for the Amber release 
                     2. Jack - we are not going add a few lines.
   2. MWC (Barcelona)
      1. Gate 2 MWC demos.  16 demos.  There are 3 demos that can feature the bronze release elements.  I requested sponsors to include the software community demo whenever appropriate.
         1. Jun Hyuk Song  wants to see the which demos have the Bronze elements. 
            1. Jinri - 2 or 3 demos out of 16 are demonstrating SC.  It will be on the o-ran alliance wiki.  Paul may be putting this demo on their wiki.  If it urgent for you then please reach out to Paul.
            2. David Kinsey - A1 is mis-leading
               1. We refer to it as O1-A1 functionality. David and Tracy will talk offline.
   3. O-RAN Alliance F2F Feb 17-21 (Paris)
      1. Action/ Farheen - Get the information from Jack and put it on the events page of the wiki.
      2. Jinri requested PTLs to report their progress during the F2F meeting.  
         1. There is status of what's been established and the plan of what is in Bronze.  
            1. Focus on the plans for Bronze.  We will arrange 1/2 hour for each project.  
               1. Jack encouraging everyone to be engaged in communicating the message of Bronze.
               2. That every element in the stack and be built and deployed by the LF toolbase and the second ETE use case can be exercised the way it is supposed to function.  Rittwik has defined what use case will be exercised in the Bronze.
               3. John Keeney  and Tracy Van Brakle  and Martin Skorupski we want to articulate what we are targeting to release in Bronze.  We need to reduce that to a written objective now that we are closing our use cases. 
                  1. Rittwik as a part of closing this use case we need a clear two paragraph message that articulates what the community can expect out of the use case.  This is an executive summary more than technical details.  2 paragraph executive summary.  Whatever we've agreed to has to be documented.  We have concerns that we won't progress far enough on the use cases but we should agree on what we are going to do in Bronze.  Less about negotiation and more about what we have agreed to what the target is.
               4. John Keeney , Martin Skorupski , Xiaohua Zhang , David Kinsey (covering for Rittwik), KJ - Kaustubh Joshi
   4. ONES = LF Networking Conference in April (Los Angeles).  
      • Open Networking & Edge Summit Event
 
        • CFP is closing Feb 3, Monday.  This is the primary networking event for the Edge group Akraino, 
        • Can we recycle the demos in MWC.
          • Is anyone planning to have a booth there?
            • Trishan - Is there interest in doing a stand alone O-RAN booth?
              • Jinri - We can use our partners booth such as O1-A1 demo by AT&T and Ericsson.  Will Hank be there?
              • We have to decide if we want him to propose a talk.  If yes, then Jack will ask Hank.  It seems at this time 
7. Status of Open Action Items (Old Business)
   1. Action / TOC voting members: Provide an alternate contact on the TOC list above.
      1. Jack will share an update next week for the ECs recommendation on the path forward.
   2. Action/ user-59b16 send Alex Stancu contact for UE simulator support.
      1. Rittwik - Asked Alex to reach out.  Martin Skorupski we are in contact VeeAvi (sp?).  For UE's we will need hardware which is difficult to acquire.
      2. We need to find out what is the UE agenda.  The O-DU project should see how they are testing the O-DU.  We have to see if the actual UE simulators can be used to test O-CUs.  
         1. Jack - You will need a UE and a radio emulator.
            1. Yes, I need a server that emulates a UE.  You don't need RF equipment for this.
            2. This is an important topic and key issue.  Which raises, 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.  It will take a commitment from TOC to spend time on the subject.  Jinri is doing the PR work.  If one of the other TOC can take on the role of coordinating with the test group.  It is an important activity that will require coordination between the development and test teams.  If we are going to coordinate on a UE simulator then the test group should also come up with someone. 
            3. Action / Farheen add to next weeks agenda
   3. 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.  It is a critical piece and will need a roadmap view.  
      1. Jack - Look at negotiating with the working groups about our needs.  I let the EC know that it is harder to maintain momentum in the second release due to exhaustion from the first release.  We need to keep advancing.  The first 3 or 4 releases are critical to the success.
      2. Jinri - we can remind the working groups at the F2F meeting.
      3. Rittwik - Reached out to WG8 RCU about supporting hand over for OSC.  Their answer is negative.  O-Cu feature won't be ready until Cherry release.  
         1. Be cautious that for Cherry release it has to be executable.  It is too late to plan at the Cherry release.
   4. 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. Sorting out Intel's contribution for license.  Lusheng will look into that.  Intel API interfaces and loader are a part of the SC.  They allow someone to take their software.  Not compatible with SC licenses.  Jack will be meeting with Stephan (Intel) that O-RAN can use their software for testing but is not an approved open source software.  It is a testing apparatus that we can load.  We still have a gap on what constitutes a layer 1 open source contribution.
   5. Action/ user-d3360 send Trishan de Lanerolle and email with the question regarding the license discrepancy.
   6. Action/ Martin Skorupski will provide the PTLs a template spreadsheet for alarms.  VES collector will display the alarm list.
      1. Martin Skorupski : posted: Bronze use case: Health-Check, https://lists.o-ran-sc.org/g/main/topic/bronze_usecase_heathcheck/69880291?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,69880291
      2. Any question talk to Martin
   7. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
      1. If there are one or two alarms already known then inform Martin Skorupski
      2. Martin will be flexible about the alarm formats, etc.
   8. Action/ PTLs participate in the Bronze planning meetings held twice a week by the RSAC committee.  PTLs who are planning to contribute to Bronze must attend.
   9. Rittwik - OAI fell off the list.  We had a meeting with OAI.  
      1. Christian (Orange) - Drafted the open interface license with Nokia to understand the differences between OAI and 
      2. Christian - OAI across systems to provide something related to E2 service model.  Not directly open interface focused but Eurocom (sp?) funded Mosaic 5G within this is a flexran project.  Flexran is related to near real time RIC in O-RAN world.
      3. Mohamed (Orange) - As a part of my work on 5G RAN i investigated FLex-RAN.  Flexor and controller is an implementation of near real time RIC.  If you want to manage the schedule then control or manage the CU or DU.  For southbound there is a embedded agent within the source code for enode gnode B.  To perform near real time operations on open interface.  Available under Apache 2.0 license. 
      4. It is a brief description of what we can do with Flex-RAN.  If you need it we could organize a presentation for the F2F
      5. Action / Farheen put this back on the agenda.  In terms of licensing we can set up parallel meeting times.
      6. http://mosaic-5g.io/flexran/
   10. Action/ PTLs pull together a summary of each of the projects and what they plan to deliver in Bronze 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)
9. 1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release
      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. 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
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.)
    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 15 Jan 2020 
          2. On motion made by user-2057e
          3. Seconded by MASAFUMI MASUDA
          4. VOTE: Vote taken, item passed
    2. Actions
       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.
       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.
       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.
       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.
       10. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
       11. Action/ PTLs update Architecture pages.  

Return to Todays Agenda ^

Archived Meetings