Technical Charter for O-RAN Software Community

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

2020 01 15

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
   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.  
   • LF Networking Conference in April (Los Angeles).
     • Feb 3rd 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)
https://events.linuxfoundation.org/open-networking-edge-summit-north-america/

7. Status of Open Action Items (Old Business)
   • Action / TOC voting members: Provide an alternate contact on the TOC list above.
     • Aciton/ 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.
                 • Action / David Kinsey talk to 
           • 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 send 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.  
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

2020 01 08

Recording: toc-weekly-20191218.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
   NTT DOCOMO	Masafumi Masuda	x
   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 18 Dec 2019 
      2. On motion made by weichen ni
      3. Seconded by MASAFUMI MASUDA
      4. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Release Votes and Approval:
6. Marketing of the Amber release (WG, LF, PR)
   1. There is work going on for demos.  Jinri is collecting material.  This is an O-RAN activity.
   2. LF Networking Conference in April.  If people are planning on attending please reach out to Jack or Jinri.  This will be in LA.  Feb 3rd deadline for proposal.  Planning on having a small kiosk or booth for demos.
      1. Tracy - The work we did for the plugfest is on the LFN program this month.  That is not a big event. This is for developers.
         1. Action/ Tracy Van Brakle will send info on LF Networking to Jack and add the event to our wiki.
7. Status of Open Action Items (Old Business)
   • Action / TOC voting members: Provide an alternate contact on the TOC list above.
     • Jinri to send out email.
   • Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
     • There is a press release on O-RAN wiki for this event that went out.  They are waiting for the press release.  The executive committee will let us know in the next two days.  The press release was impressive.
       • We learned a lot captured in Jira tickets.
   • Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
     • Rittwik will meet this week and report out next week.
   • 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.
     • One based on O-RAN services and OAM functions that will form tracks that each release will be improving OAM.  The end to end use case relies heavily on O-CU and O-DU functionality that we can progress in this release.
     • We need to synch up with the PTLs of O-CU and O-DU and the architecture committee to support these use cases.
     • Rittwik - update yesterdays RSAC meeting Ganesh from Radisys this Friday.  He is encouraging O-CU and O-DU come together and identify feasible use cases.
     • This is a high priority and PTLs must work together.  Be modestly aggressive to target this release.  Looking forward to an update next week on these discussions.
     • Rittwik - Setting expectations: when KPIs come to RIC (measurement page) then you do the analytics and then turn it into a traffic steering action as a simple hand off from one cell to another not a real UE.  We need a realy UE simulator component needs to be contributed to understand the hand off.  
     • Action/ Farheen Cefalu  add to agenda.  Call to Community to address the UE simulator as well as the fact that the test community in O-RAN will have a need for this.  We have our Simulator team that can identify a UE simulator.
   • Action/ PTLs enter epics from Contributions into jira.
     • Jack will start pulling reports from Jira to see the scope of this release.
   • 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 on what they plan to deliver in Bronze release.
     • ETE use case is focused on the lower stack but we don't want to ignore the higher level functions.  What use case can drive the work in the non-Realtime RIC.
       • Tracy - O-RAN testing group has a POC plugfest keyed up for the Bronze release.  Plugfest will be end of June 2020.  It's a dynamic 5G multi-operator with first responders.  
       • Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
8. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release
         1. Clean up documentation 
         2. Close Jira issues
         3. After every release we will have a window where a developer can work on the maintenance items.  We're trying to improve what we have done for the Amber release.
         4. Make changes to the Amber branch.  If you need help to trigger the jobs for the Amber maintenance release contact user-d3360
      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. No epics yet.  I am having a problem with the healthcheck use case.  There is a meeting with John Ng to meet tomorrow.  
      3. user-a934b O-RAN Centralized Unit (OCU)
         1. We have some new committers in the B release.  
            1. Is there a roadmap of the O-CU functionality of how you will add functionality?
            2. Action/ user-a934b provide a list of functionality that you plan 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. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
         1. We are updating the scope for the Bronze release.
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
         1. We will be working closely with the ODUHIGH project.
         2. Our plan is to release the binary.  We are reviewing the license.  We need to have a license agreement first. 
         3. Jack will work with the legal team to address the license.
      6. Martin Skorupski Operations and Maintenance (OAM)
         1. We are working on the healthcheck use case.  We are forming our epics.
      7. Alex Stancu Simulations (SIM)
         1. Planning to work with OTF team for the Bronze release. 
      8. Xiaohua Zhang Infrastructure (INF)
         1. Working on epics.  Planning to deliver epics next week for Bronze release.  We need to work with O-DU to provide infrastructure.  Please include Xiaohua Zhang for infrastructure.
      9. weichen ni Documentation (DOC)
         1. Think about best practices area.  Read that and give guidance to the team of what your expectations are around the documentation.  To make things usable outside of developers to make it work.  Both the software detailed documentation and how to use the overall system. 
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
          1. Working on epics.  We plan to tidy up our repo.  There is functionality that should be in other projects such as simulations, and dashboard (OAM).  We will set up sub repos in those repos.
          2. The need for coordination of the SC and O-RAN projects.  IBM is duplicating work.  We plan to look through our roadmap to see where to push those changes.  Whether to O-RAN or O-RAN SC.
             1. Part of the challenge of being new and starting new.  People are confused on coordination.  This raises another discussion about what an SMO is and should we have a project and space to pull together the SMO owrk.  Original agreement was ONAP would be upstream and RAN specific should be here with O-RAN Alliance.  As a community how do we sort out this overlap and now that this community has been established how do we structure the needs.
                1. This is a good conversation to start at the plugfes in Prague.  If we have a slide that explains the division of labor that would be very useful.  I know Vimal worked on something like that.  Jack will talk to Vimal to sort it out
                2. All parties are well aware with Vimal's slides but we want more.
                3. One suggestion ONAP may need to be happening this conversation rather than here.  Trishan de Lanerolle can help get the right people.  
                   1. We have the right people.  We need to coordinate it better.
      11. (TBD) O-RAN Radio Unit (ORU)
   4. user-59b16 Requirements Software Architecture Committee
      1. O-CU and O-DU teams look at the steering and healthcheck and simulator use cases.
9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. By Jinri: possible contribution to MWC Barcelona
      1. Can we see what demos are planned?
         1. Paul - This is out on the wiki.
   2. O-ARN Alliance Face to face meeting: 
      1. Jinri: on Monday TSC call, we discussed meeting arrangement but no conclusion yet.  F2F to be held Feb 17-21, Paris. 
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 18 Dec 2019 
          2. On motion made by weichen ni
          3. Seconded by MASAFUMI MASUDA
          4. VOTE: Vote taken, item passed
    2. Actions
       1. Action/ Tracy Van Brakle will send info to Jack and add the event to our wiki.
       2. Action / TOC voting members: Provide an alternate contact on the TOC list
       3. Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
       4. Action/ Farheen Cefalu  add to agenda.  Call to Community to address the UE simulator as well as the fact that the test community in O-RAN will have a need for this.  We have our Simulator team that can identify a UE simulator.
       5. Action/ PTLs enter epics from Contributions into jira
       6. 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.
       7. Action/ PTLs pull together a summary of each of the projects on what they plan to deliver in Bronze release.
       8. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.

Return to Todays Agenda ^

Archived Meetings