Technical Charter for O-RAN Software Community

2020 03 25

Audio Recording: 020-03-25-toc-audio_only.m4a

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	Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar		Skand Priya

   *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. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for 18 Mar 2020 
      3. On motion made by Jinri Huang
      4. Seconded by user-2057e
      5. VOTE: Vote taken, item passed
4. Review of Today's Agenda
   1. Jack - Next week will be our first meeting of April. We will cross over completion of our first year as our open source community.  Thank you to everyone who supported the projects and contributed.  We will be transitioning to add 3 additional members to the TOC.  We will move to a 9 members of the TOC.  They will be introduced next week.
5. Release Votes and Approval
6. Marketing of the current release (WG, LF, PR)
   1. Jinri - Nothing to report for marketing.
      1. Jack - We have to talk about  how to broaden our communication to the broader community.  We have to educate and communicate progress and activities.  We will have to get back to this at some point.
   2. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
7. Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
   1. Action/ ENGWEI KOO will set up a meeting with  Tracy Van Brakle , Martin Skorupski John Keeney , and Alex Stanc to discuss O-1 interface options with Viavi.
      1. Rittwik - 7a and 7e relate to work with Viavi.  
      2. Jack - 7a was to discuss O-1 functionality and how there work will impact.
      3. Engwei - John, Martin, and High Street met on how O-1 testing is required here.  We concluded that there will be further dicussions for use cases. requirements for simulators.  What measurements and pm counters over to RIC for dynamic traffic steering.  We discussed E-1.  From Viavi we will make sure we are tracking the team.  John mentioned the need is for the Cherry release and anything for the Bronze.  Thanked the team for bringing Viavi up to speed.
      4. Action / ENGWEI KOO  - will add a deck.  Looking at the swim lane tables to track how Viavi will 
   2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
   3. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
   4. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
   5. Action/ user-59b16 update TSC with the short/long term UE emulator support.  
      1. Rittwik - sharing slide of what is needed for the short term.
      2. Action/ user-59b16 upload the slide to the RSAC page.
   6. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release.
      1. Jack - Reviewed Releases page.  Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
      2. Rittwik - WG input requirements from 14 - 20th of June.  Not sure that WG3 requirements will be done by then.
         1. Then we won't use them.  We can't be constantly changing so developers don't know what to build.  If we don't have then we will rework the use cases.  We can shift things a little.  The timelines are aggressive enough without changes.
         2. Rittwik - Please bring this chart up on this point to the TSC.  
         3. Jack - If it's not in the Cherry Release then it will get into the plan for D but won't happen until a year later.
         4. David - What do you mean by working group input freeze?
            1. Jack - We've been asked to coordinate with the O-RAN WGs.  We have Bronze release touchpoints.  The goal was to look for WG input.  When we complete our planning we will do a review with them.  We have a touch base twice.  Dev Sprint 4 ends 4-26.  We will give a demo of the functionality we plan to release.  In this case it's Bronze.  For Cherry I added the comment that we'd be freezing what specifications we'll be working with. 
            2. Thoralf - There is a difference between specifications.  
            3. Jinri - The freeze is not the freeze of specs.  We recognize at this time the latest spec we have from WG.
            4. In week 21 we will use version spec 2.1 that O-RAN Alliance is expecting to release in week 23.
            5. Jack - we agree on which specs we are working.  I'll be happy to use a different word than "freeze".
            6. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
            7. Jack - We need to figure out how to align.  I expect they will be in the same release window.
               1. Rittwik - We will face challenges with the current situation.
               2. Jack - Each release has it's own set of decisions.  We can stretch out a little bit.  If we stretch out in ETE testing then we have stretch.  The community can review if we provide it to the TOC.
   7. Action/ user-2057e update Vote Release Name page with the D release name options.
      1. David - There are very few colors with the word D in it.  It will be a fairly short list to avoid the "dark"  and "deep" colors.
   8. Action/ Jinri Huang will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
   9. Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
   10. Action/ Thoralf Czichy share the OSC Alignment Aspects slides with Jack.  We have means to align with WG3.  Rittwik - We need a timeline chart for C and D.  We need to know our timelines of what is at stake.  We need this for all WGs.
   11. Action/ Tracy Van Brakle  Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.
       1. Jack - will continue the discussion to see how we can improve.  We're a young community.  Some of our needs are different than other communities.  As a community if people find better ideas, or ways to do things bring them to the PTL or the TOC.  There may be things we can learn and get better at.
   12. Action/ John Keeney open a trouble ticket with LF for the Confluence calendar issue.
       1. Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
8. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
   2. 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. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
         1. note I updated the committer change process as per discussion last week: How to request committer changes.
         2. Action/ Jack Review Thoralf's How to request committer changes
      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)
   3. user-59b16 Requirements Software Architecture Committee
      1. We will be starting Cherry.
      2. We need the Viavi simulator.
      3. Jack - Pulling together the overall stack it is important to show pieces evolving and their process.
      4. Lusheng - we have one and a half sprints left.  We would like to have the simulator.
      5. Jack - David - Was there any update with the testing committee?
      6. Action / William DIEGO - Status of test 
   4. user-d3360  Integration and Test
      1. In terms of code quality.  LF is using SONAR Cloud to report unit test coverage.  The integration team is providing  the sample repo set up to set up your code to SONAR analysis.  Captured in the wiki page.
      2. Action/ user-d3360 add the wiki link in the Integration and Test.
      3. Demo activities are important and required to keep the overall project and stakeholders in synch and manage expectations.
9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 
   1. Jinri Huang  - I saw an O-CU approval.  
   2. weichen ni  - suggest each PTL to use an API document.  Generate a weblink to create.  
10. Planning for Next Meeting
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)

2020 03 18

Recorded Video: 2020-03-18-toc.mp4

Audio: 2020-03-18-toc-audio_only.m4a

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	Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar		Skand Priya

   *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. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for 04 Mar 2020 
      3. On motion made by Jinri Huang
      4. Seconded by user-2057e
      5. VOTE: Vote taken, item passed
   2. The minutes of the prior meetings were reviewed, and there was a comment on updating 7, questions or corrections.
      1. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for 11 Mar 2020 
      3. On motion made by Jinri Huang
      4. Seconded by user-2057e
      5. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Release Votes and Approval
   1. Jinri - OC-U needs a new repo.
6. Marketing of the Amber release (WG, LF, PR)
   1. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
7. Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
   1. Action Ken Trudgeon from Viavi will report back on O-1 capabilities for an end to end full stack capability for the OAM team John Keeney.
   2. Action/ ENGWEI KOO will set up a meeting with  Tracy Van Brakle , Martin Skorupski John Keeney , and Alex Stanc to discuss O-1 interface options with Viavi
   3. Action/ Jinri Huang will share slides to set up projects using the O-RAN SC regarding the Open Data Set project from O-RAN TSC.
      1. Shared slides with the team and the slides are being updated.  We have a policy update and it is under the clearance process.  Jinri will update the community once it's finalized.
   4. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
      1. Demos were moved to virtual.  O-RAN Alliance is working on this.  Jinri will work with Farheen to add the link.
      2. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests.  OTIC will be voting on the moving the Plugfest to September.
   5. Action/ user-59b16 update TSC with the short/long term UE emulator support.  
      1. We have to make decisions about what simulator and emulator support we need and can attain.
      2. Rittwik - We've built a technical plan to build out the O-RAN Lab in T-lab.  Viavi has proposed emulator and simulator.  You will also get a business proposal from Viavi today.  You will have all the plans.  The technical plan is in the RSAC space.  
      3. Action / Tracy Van Brakle clarify OTIC North America
   6. Action/ David (DT) we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      1. Spoke to colleague but didn't reach a conclusion.
   7. Action/William DIEGO  will talk to the focus group regarding test coordinator for the O-RAN SC.
      
      1. William spoke to companies needs to have ETE framework.  Viavi is providing contributions to this focus group.
         1. Jack is looking for OSC interacting with the focus group and how we are doing that.
      2. William - it is important to wait until we have the ETE framework is established.  Once it's documented I can present that and position us with this group.
   8. Action/ Lusheng follow up with Zhimin offline to set up target architecture for O-DU Low.
      1. Lusheng - we understand what O-DU Low means for setting up an environment for unit testing and building.  We have a path forward.  It was presented last night to the RSAC and will be on the Integration Test plan.  Side note for technical proposal of the integration lab is subject to EC approval.
         1. Jack - It will continue to evolve.  I have been contacted by other peoples interest in O-DU as well.
   9. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release. 
      1. We are getting close to D release naming poll.  We can move forward with the D release naming poll.
   10. Action/ Jinri Huang will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
       1. Getting the WGs to understand what are their cut-off dates for their specifications.  Want to put the specifications for Cherry from WG2 and WG3 in our timeline.
       2. Rittwik - We need to align what use cases can be done.  Specs won't be out in time.  We need to tell them these. are our times but the WG2 and WG3 can't meet the dates.  Either wait for specs come out in Q3 because Cherry dev will be ending.  Or pre-spec but then you have to wait to D release to test it.  Any use case will require an E2 service model.  If the E2 service model is the key.  Timing alignment and communicating priorities so they can work it to meet our timeline.  Can we bring this issue to EC for discussion?  It is informally discussed. 
       3. Jack - There's a use case that is part of WG1.  Have they accepted this as one of their use cases?
          1. Yes. Traffic steering use case.
       4. Jinri - During virtual F2F with WG3 they have adjusted their timeline to meet our Bronze release.  For Cherry release they have not provided a design date.  They agreed to the timing adjustment method.
          1. Rittwik - At the F2F they will be publishing 3 versions of E2 v.1 will com out in August v. 3 will come out in December.  Thoralf provided guidance when it should start and finish.  
             1. Jinri - Meeting Cherry release is in synch.  
             2. Action/ Thoralf Czichy share the OSC Alignment Aspects slides with Jack.  We have means to align with WG3.  
             3. Rittwik - We need a timeline chart for C and D.  We need to know our timelines of what is at stake.  We need this for all WGs.
   11. Action/ user-a934b work with Lusheng to create the test cases for O-CU.
       
       1. Lusheng - Yingying brought a contact for integration and test.  We will work together.
   12. Action/ user-a934b update the Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues. 
   13. Action/ Tracy Van Brakle  Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.
       1. Tracy will take the action item.
   14. Action/ Sachin Srivastava update ODU-High Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues. 
   15. Action/ PTLs assign someone to lead the integration and test.
       1. If you go to Integration and Test there the table is in the Bronze release 
   16. Action/ Farheen Cefalu request to escalate the calendar issue with LF or add it to agenda for TOC call.
       1. Home time zone for the calendar.  
       2. Difficult to coordinate the calendars with Outlook.  There are errors with the format of the calendars.  Does OSC have a home time zone?  What is it and what time zone should be used.
       3. Thoralf - For Confluence raise a ticket with help at LF. For local time zones use UTC.  
       4. Lusheng - We have two calendar applications one is a part of Confluence and the other is from Groups.io.  The mailing list is triggered by Groups.io.  Groups.io takes care of the time change but the Confluence does not seem to work.
       5. Jack will work with Trishan de Lanerolle to address the items above.
       6. Action/ John Keeney open a trouble ticket with LF for the Confluence calendar issue.
8. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
   2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
         1. note I updated the committer change process as per discussion last week: How to request committer changes
      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)
   3. user-59b16 Requirements Software Architecture Committee
   4. user-d3360  Integration and Test
9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
10. Planning for Next Meeting
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)

Return to Todays Agenda ^

Archived Meetings