Technical Charter for O-RAN Software Community

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

2020 01 22

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
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Orange	William Diego		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

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)
   • MWC (Barcelona)
   • O-RAN Alliance F2F Feb 17-21 (Paris)
   • ONES = LF Networking Conference in April (Los Angeles).  
     • Open Networking & Edge Summit Event
 
7. Status of Open Action Items (Old Business)
   1. Action / TOC voting members: Provide an alternate contact on the TOC list above.
   2. Action/ user-59b16 send Alex Stancu contact for UE simulator support.
   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.  
   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.
   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.
   7. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
   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. Action/ PTLs pull together a summary of each of the projects and what they plan to deliver in Bronze release.
   10. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
   11. 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
   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.
            1. note that from traffic steering epic/use case I did not see any use cases that fit to the near-RT RIC platform
            2. multiple meetings related to health check epic subitems still be created in JIRA related to E2,A1,O1 health check and related to self-monitoring and alarm management.
            3. what is this item about (from Bronze spreadsheet): "RAN NE to support Dynamic Data Collection (DDC) Measurement Intervals"
      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.)

2020 01 15

Recording: 2020-01-15-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	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. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for 08 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. No approvals this week
6. Marketing of the Amber release (WG, LF, PR)
   • MWC (Barcelona)
     • WG1 are correcting a list of demos for MWC compared to last year there were 6 demos.  This year we have collected 16 demos.
     • 2 demos are related to SC. 
       • A1 PoC
       • Edge Cloud Platform (AT&T and Nokia).  Release A is demonstrated in this PoC.
       • Jun Song (Samsung) has a demo to offer for the RIC platform.
         • Submitted to WG3 video for Network slicing.
       • For MWC PoC.  Next Monday there will be a gate to review the PoC.
     • Feb 25 9:30 - 10:45 event Dutch Telecom will have a briefing.  In an auditorium with 200 seats.  Agenda will have the key chair of O-RAN Alliance, Dutch Telecom Executive, China Mobile Co-Chair (Jinri).
   • O-RAN Alliance F2F Feb 17-21 (Paris)
     • Do we have the schedule on the web site so people know when our meetings are.
     • For the TOC will be Tuesday and Thursday evening in Paris.  Those are two sessions.  
   • ONES = LF Networking Conference in April (Los Angeles).  
     • Open Networking & Edge Summit Event
 
     • 2020-02-03 deadline for proposals.  Planning on having a small kiosk or booth for demos.
     • Next weeks meeting is the deadline for raising interest.  Talk to you companies and teams and reach out to Jinri and Jack and let them know what your interests are.  We have to decide how much we want to participate.
     • It will have ONES participation.  Including Akraino and ONAP.  We need EC to be aware of this event to enhance this collaboration.  It is a smaller event to have more interaction.
       • Look for feedback between now and next week.
       • Action/ Farheen add this to next weeks agenda.
       • Action/ Farheen ONES. Correct the entry for LF Networking event to LF. Networking: Open Networking & Edge Summit (formerly Open Networking Summit)
.
7. Status of Open Action Items (Old Business)
   • Action / TOC voting members: Provide an alternate contact on the TOC list above.
     • Action/ Farheen get Masafumi's backup from Jack.
   • Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
     • First meeting with Christian and his counterparts was held last week.
     • E2 traffic steering model needs to be approved by WG3. O-CU and O-DU handoffs won't happen until the Cherry release.  Another is healthcheck.
       • Is this advancing the software and moving the community forward?
       • Concern that we may have to add another use case to develop another aspect of the software.  How much do we advance in each release.  One thing that blocks should not prevent us from moving forward.
         • Hampered by the O-CU O-DU profile timeline alignment with OSC is tricky.  They have their timeline already that doesn't align.
           • Can we enrich the use case around some other functionality that is advancing.
         • O-CU and O-DU have to step up and what value they can add.
           • Can we develop a better set of detailed and expanded data so we can have a complete set?
           • How complete of data collection can we do in this release.
         • Steering use case.  Cu and DU should implement the E2 interface.  There were attributes and KPIs identified for modules.  That document needs to be reviewed so that it is clear to CU and DU.
           • We need to see how we can get the data into CU and DU but we don't have SMO support for that.
             • Challenge is getting the data out of those devices at performance levels.  First step is to acquire it and manage it.  The next step is to deliver it to the upstream layers.
               • We don't have any in 01 or ONAP or SMO to do real time PM.  We need to get leverage against ONAP and O-1 team to define those interfaces in support of non-RT RIC.  Or we do that work ahead of specs which leads to problems. 
                 • Get that proposal.
           • Rittwik - O-DU and O-CU teams have to get together for the traffic steering use case.  
           • Sachin - Call flow is not listed for a simple traffic steering use case.  As a first step we should look at a simulator based approach.  Simply simulate the use case and then the CU and DU can adopt that simulators results.
           • The use case lists KPIs but doesn't list which one is for CU and what is DU.  The document we have today is an extensive list of KPIs to use and how training will take place.  We don't know how to get it to the SMO.  We don't need to use ONAP for now.
             • Jack asking the team to figure out how best to advance these features in the B release.  Expecting O-CU and O-DU to support the other healcheck use case.  Expecting a minimum software element with O1 communication.  The team can decide how extensive it is.  Second use case know that we've deployed every element in the stack and validate that it is running.  This is a necessary first step to deploy all the pieces.
   • Action/ Jinri Huang provide an answer to user-59b16 regarding support for O-CU, O-DU.  Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
     • We had a meeting with CM, Radisys, Intel
     • Rittwik has not heard back about simulator.
       • Call to community:  What are we doing about a UE simulator.
         • Action/ user-59b16 send Alex Stancu contact for simulator support.
       • Rittwik - we can have one or two cell phones.  But not sure that is possible in bronze release. You have to have many UEs in multiple cells.  It's OK to do unit tests but to test in full force we have to do it with a simulator.
         • Martin Skorupski  will use cell phones instead of a simulator for Bronze release.
   • 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.  
   • Action/ O-CU and O-DU PTLs and RSAC to get together regarding the end to end steering use case jeopardy. 
   • Action/ Community to address the UE simulator jeopardy on this TOC call.
   • Action/ PTLs enter epics from Contributions into jira.
     • Thoralf - see section 8c below.  This will happen next week to discuss.  Having trouble with the traffic steering use case.  Don't see how the traffic steering use case fits with near RT RIC.  Healthcheck of the different interfaces will be entered this week into jira.  We will have a list on the meeting after next week.e
     • Matti - Use case details are evolving.  
     • Sachin - Expecting Jira stories to be in Jira by next week.
     • Zhimin - Yes we put the O-DU tasks in Jira.  
       • Lusheng - discussed at the end of last release.  Issue is to compilation in LF.  The licensing is different.  We will need some legal council on this matter.
       • Jack - Have a meeting.  Action/ user-d3360 set up a call with John Murray, Trishan de Lanerolle, Jinri Huang.  We want to make sure we can do the logging.  Take it to another meeting.  Action/ user-d3360 send Trishan de Lanerolle and email with the question.
     • Martin - Common data models from WG4 and how to make it available for the software community.  We want to continue what John Keeney did called an SMO that can be deployed.  What the SMO should look like.
       • Focus on what the distribution of an SMO will use for our work in Bronze and then we will update it for Cherry.  Lusheng and team for integration and the O-RAN test community.  When you listed the alarms, is that the same as all the error messages?  Software will generate error messages but we don't gather that info. 
         • If they report according to the ONAP standards then VES collector will display the alarm list.
           • Each piece of software needs to gather their alarms and be documented.
             • Yes.  that is in my proposal.
             • Every PTL come up with a list of alarm names, and document it.  That can be translated to VES message formats.
             • Jack asking people to use spreadsheet.
         • Action/ Martin Skorupski will provide the PTLs a template spreadsheet for alarms.
         • Speaking to Chris Lott about portal and dashboard discussion.
     • Alex - Simulator project will have epics.  
       • Jack - We need to know what Simulator is focusing on.
     • Xiaohua - Epics are in jira.  Trying to finish by the end of next week.  Community members can read up.
     • Wei Chen - no epics
     • John K. - Traffic steering functionality at the SMO level is happening.  Getting closer to entering but needs more time.
   • 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.
   • Action/ PTLs pull together a summary of each of the projects and what they plan to deliver in Bronze release.
   • Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
   • Action/ PTLs update Architecture pages with the Bronze release features they plan to deliver.  
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
   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.
            1. note that from traffic steering epic/use case I did not see any use cases that fit to the near-RT RIC platform
            2. multiple meetings related to health check epic subitems still be created in JIRA related to E2,A1,O1 health check and related to self-monitoring and alarm management.
            3. what is this item about (from Bronze spreadsheet): "RAN NE to support Dynamic Data Collection (DDC) Measurement Intervals"
      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 08 Jan 2020 
          2. On motion made by Jinri Huang
          3. Seconded by user-2057e
          4. VOTE: Vote taken, item passed
    2. Actions
       1. Action / TOC voting members: Provide an alternate contact on the TOC list above.
       2. Action/ user-59b16 send Alex Stancu contact for UE simulator support.
       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.  
       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.
       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.
       7. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
       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. Action/ PTLs pull together a summary of each of the projects and what they plan to deliver in Bronze release.
       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