Technical Charter for O-RAN Software Community

2020 06

10

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		Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar		Kristen Young
   Nokia	Juha Oravainen		Thoralf Czichy
   Radisys	Ganesh Shenbagaraman		Sachin Srivastava
   Ericsson	John-Paul Lane		John Keeney

   *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

6. Copyright updates

7. Marketing of the current release (WG, LF, PR)

   1. Bronze Release PR

   2. Virtual Exhibition.

   3. OSC Logo status.

8. Status of Open Action Items (Old Business)

   1. Action/ William DIEGO update on the coordination with the O-RAN test group
   2. Action/ TOC members vote to approve Martin's email for a new repo request.Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
   3. Action/ Vishnu send Rittwik the slides for the ITU / AiML Challenge
   4. Action/ Rittwik: Share the spreadsheet with Jinri and Yingying.  Regarding the topic of O-CU 5G statusPost ITU / AiML Challenge slides on the wiki and pull together a team.  Include Thoralf.
   5. Action /  Trishan de Lanerolle provide the Insight slides to Farheen CefaluAction/ PTLs provide one or two bullet highlights worth including in Jack send the highlights out on the reflector before the press release.  It does not have to be long.  One or two sentences one or two bullet points.  03 Jun 2020 Should include statements from any company's.

9. Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Release Manager Trishan de Lanerolle /

   Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Bronze Timeline

      2. Review Bronze Release Highlights

   2. user-59b16 Requirements Software Architecture Committee

   3. user-d3360  Integration and Test

   4. 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. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

      2. Matti Hiltunen RIC Applications (RICAPP) 

      3. Thoralf Czichy RIC Platform (RIC)

         1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)

      4. user-a934b O-RAN Centralized Unit (OCU) 

      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

      7. Martin Skorupski Operations and Maintenance (OAM)

      8. Alex Stancu Simulations (SIM)

      9. Xiaohua Zhang Infrastructure (INF)

      10. weichen ni Documentation (DOC)

      11. (TBD) O-RAN Radio Unit (ORU)

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

06 03

Zoom Recording: 2020-05-27_toc_audio_only.m4a06_03-toc.mp4

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   xx

   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			Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar		Kristen Young
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava
   Ericsson	John-Paul Lane	x	John Keeney

   *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 corrected by Farheen who replaced Jean-Paul name where Juha had seconded last 20 May 2020 meeting minutes approval voteno corrections.
      1. Vote to approve minutes for 20 27 May 2020 
      2. On motion made by Juha Oravainenby John-Paul Lane
      3. Seconded by Ganesh Shenbagaramanweichen ni
      4. VOTE: Vote taken, item passed

4. Review of Today's Agenda

   1. Preparation for Bronze ReleaseJack: I added this item for the preparation for the Bronze ReleaseJuha - Last week discussed Virtual meeting.  
      1. Trishan: We have the Insights team on today.
      2. Chat: From Trishan de Lanerolle (LF) to Everyone: (08:30 AM)
         
https://lfanalytics.io/projects/o-ran

   2. Insights Team
      1. Shubhra Kar  (CTO Insight) sharing a deck.
      2. LF planning to launch Networking Project this year.  Reviewing short term and long term roadmap.  Have been working with PMs for the Networking Project.
      3. Birdseye view of what they are trying.  LF foundations automation platform.  Security scanning, single sign on service.  Wrap zoom around security layer.  Analytics will go deeper today.  We have easy CLA tools.  
      4. We have been writing automation around asset management, voting, and PM service.  We announced crowd funding service and more.  The goal it to build a centralized platform to provide services in the platform lifecycle.
      5. There is an IP automation part. 
      6. Today we are going to talk about Insights.  It is still early.  It is our V1 version.  What are we trying to solve.  1. members, 2. Projects, 3. contributors.  We want to look at employees impact.  We want to see activities going up or down.  For the projects you want to grow the community you want to measure health.  Also, optimization is built in.  While youre collecting data is the data secure?  Email addresses are they stored in GDPR and privacy policies.  Look at contributors commits and backlog working in sprints.  However, can the contributor think about security?  Are there security metrics available.  In the version1 we haven't integrated our license yet.
      7. This is home grown.  LF needed to rely on third party tools.  This has been built for LF community and all the projects under LF umbrella.  Large team supports this from operations perspective.  It is GDPR compliant.  Features are the multi dimensional views.  From a support perspective we are putting a support structure and offer weekly office hours from our engineers. 
      8. We are gathering our metrics around commits and issue tracking.  We aggregate on a daily basis.  We have automated the instrumentation.  So if a project adds another data source tomorrow we can add it without a lot of overhead.  We are building custom dashboards on kibana.  Two challenges are identiy management. No consistency in contributors ids.  How do we unify an identity of a user and refer back to one person.  For member companies you want that credit to be applied to the company.  How do you affiliate the contributors to these companies?  There is no source of truth.  We have a solution of how we manage through an administrative console.  As we build it out we are scaling into a self-serve platform.  We have put access rules into place.  These are the data sources.  We have projects moving into gitlab.  Issue tracking systems.  Bugzilla in jira.  If you are using jenkins in your builds we have instrumentation that is pulling that data.  As well as Slack, Jira, Confluence, Github Issues,...
      9. John-Paul does there need to be a design time update from the team or our own reports?
      10. We do create templatized dashboards.  If you want to visualize data in a custom view you can download anonymized data and voting dashboard, we have that instrumentation.  We have sprints we work on the design and put it on staging get user acceptance and move it to production.  
      11. Jonh-Paul so as a company we could run a query across a number of projects.
      12. Shubrah: You can we are coming up with an out of box dashboard that will be released in fall.
      13. Shubrah showing a demonstration.  Watch the recording.
      14. When will it be available to use?
      15. V1 is available right now.  If you look at the site.  There is a roadmap and newer views we are building for code pipelines.  There is a role out plan PMs in the Networking team.  We are doing waves and sign off.  Wave 1 was presented.  Wave 2 we want to give to O-RAN. There are others.
      16. Jack: can we have these slides.
      17. Action/ Trishan de Lanerolle provide the Insight slides to Farheen Cefalu
      18. David McBride: We split the schedule into greenfield project that don't have a developer O-RAN tool.  Last week we talked to CNTT this week FIDO, O-RAN...
      19. These are the projects that have developer tools.
      20. Shubhra: PMs are validating their data.  This is UAT.
      21. Jack: Is there a best procedure for closing these unknowns?  How we do that?  Is there guidance?  
      22. Shubhra: Trishan is one Admin who can work on affiliation.  We have a filter list.  
      23. Trishan: We can add a couple of members in the community add them and then merge it back in.

   3. Bronze Release PR

   4. Virtual Exhibition.

   5. OSC Logo status.

5. Release Votes and Approval

   1. Jack: Any items open for votes and approvals?  What is going to happen here is we are going to have a Go No Go vote on the Bronze release.  Today is not the right day yet.  The B release is supposed to happen on June 14th.  Next week we should have a go / no go vote on the software release and press release.  We have work to finish if we plan to release on time.  That would mean the press release will come out Monday June15 or Tuesday June16.
   2. Jinri: For the press release the O-RAN Alliance is not quite sure if we will have a separate PR for Bronze release or mid year press release for O-RAN Alliance.  I plan to bring this up in todays EC call.
   3. Jack: That is fine where the mechanics are when we release the info but the preparation of the documentation and released will stick to the time line.  We are finishing up end to end testing this week and we'll have to decide if we are ready for a release on the 14th.  That will give us time to pull together documentation and additional work for the Bronze release.  One of the things we have to finish up gathering for B.  We have to have our testing complete and the package to pull together.  We'll discuss here how EC wants to release the information but for us we want to make sure we have the information ready for the press release.  
   4. Jinri: Before hand preparation for information.  In the press release we want to see the high lights.  It is OK to ask the PTLs to provide 2 or 3 bullet points that they would like for us to highlight in the press release.
   5. Action/ PTLs provide one or two bullet highlights worth including in the press release.  It does not have to be long.  One or two sentences one or two bullet points.  03 Jun 2020 Should include statements from any company's.
   6. Jack: I will be out next week.  Lusheng will be my proxy.  Jinri could you run the meeting?
   7. Jinri: Yes, I think so.
6. Copyright updates

7. Marketing of the current release (WG, LF, PR)

   1. Virtual Exhibition.

      1. Jinri: There was an OSC related demo submitted to working group 1 O-RAN Alliance.
      2. Jiri: There is the virtual exhibition will last 2 weeks.  The OSC have two time slots on Monday June 8th.  Cherry release kick off discussion.  Row #13 OSC line.  The first item is the Cherry release kickoff 2 timeslots on Monday. Next topic Viavi on Tuesday.  This is based on what I collected before.  There is third one that is proposed by WG8 but they request us to join this discussion.  The question to you and Rittwik just to confirm that we do need these two slots that we have required.  We can attend.
         1. How long is the slot?
         2. One block is one hour.  2 hours for Cherry release.  Starting time will be 8AM EST.
         3. Rittwik: Does this clash?  You have WG1, 2, 3.
         4. Jinri: They will join this topic.  WG1, WG2 is the entitiy who requested across this discussion followed by the topic.
         5. Action/ Farheen Cefalu add the spreadsheet to the Events page.
         6. Jinri: The latest one is the one I sent to you, Rittwik and Lusheng.
   2. OSC Logo status.

8. Status of Open Action Items (Old Business)

   1. Action/ William DIEGO update on the coordination with the O-RAN test group
   2. Action/ TOC members approve Martin's email for a repo request.
   3. Action/ Rittwik: Share the spreadsheet with Jinri and Yingying.  Regarding the topic of O-CU 5G status.
9. 1. 1. Jack: Jinri has been involved in setting it up.  It was mostly Jinri.
         1. Action/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.

         2. https://oranalliance.atlassian.net/wiki/spaces/OAH/pages/644448276/Virtual+F2F+Meetings+June+8-19+2020
            https://wiki.o-ran-sc.org/pages/resumedraft.action?draftId=1179657&draftShareId=102136bc-a84f-4418-bf53-c4fbd986063a&

      2. ITU / AiML Challenge
         1. Vishnu:  This is an invitation to collaborate.
         2. ITU has launched a 5G challenge.  We request O-RAN SC to consider collaboration or a problem statement for the challenge.
         3. We are trying To create platforms using open source.
         4. We provide feedback and collaborate with ITU specifications.
         5. Who?  Open to everybody 5GU.  And also include you as a nominee.
         6. LFAI and NGNM.
         7. I discussed two plans with Rittwik two plans.  
         8. Tool set 
      3. Jack: Dates to get back to you by?
         1. Vishnu: June second week around 10th or 15th.  You can provide a date for your collaboration window.  If you need to come in the next window will be midSeptember.  I can stretch it to 3rd week of June.  
         2. Jack: I would like to get a few people to get involved.
            1. Matti and Rittwik.
         3. Is it only for xApps?
            1. Vishnu: It is open contact Vishnu.
         4. Jack: is there anyone else who would like to get involved?
            1. John-Paul we would like to know more.
            2. Thoralf: slides? 
            3. Action/ Vishnu send Rittwik the slides.
            4. Action/ Rittwik: Post it on the wiki and pull together a team.  Include Thoralf.

10. Release Votes and Approval

    1. Jack: Saw Zbynek's draft with information for the release.  Several people asked for supporting statements.  Please contact Jack or Zybnek for release highlights.  The company's that have statements send Jack requests and he will pass along to Zbynek.
    2. John Keeney: Will it be possible to see the press release before it goes out?
       1. Action/ Jack: Will share the document through the reflector.  Jack and Jinri provided the input.
       2. John: When is the deadline for the highlights? 
          1. Jack: We try to be ready by 6/14.  The press release will come out any time after that.  They will make the final decision on the exact.  Have to them by the end of this week.
          2. We will focus next week on the final vote to approve the release.
11. Copyright updates
    1. Jack: The updated statement is still in the process of being voted upon at the board level.  I don't see the details.  I am not in the email pool.  I get some information back but it's in process.  The board votes take a little more time to gather the input from everyone and they try to get everyones vote.  I will get an update as soon as I return.

12. Marketing of the current release (WG, LF, PR)

    1. Bronze Release PR

    2. Virtual Exhibition.

       1. There is a June update to the virtual exhibition coming out.  Jinri has been talking about the demos and submitting them to Paul Smith from AT&T.  Any questions?
    3. OSC Logo status.

13. Status of Open Action Items (Old Business)

    1. Action/ William DIEGO update on the coordination with the O-RAN test group
       1. John-Paul.  It will be decision based.
       2. Jack: Yes, O-RAN will look at it and give the thumbs up that we've looked at it and saying it's met their principles.
       3. John-Paul: There is nothing from stopping anyone from using testing simulators but they have to be approved by OTIG.
       4. Tracy: I think what you are saying is consistent with the OTIG guidelines.  I am familiar with the one in North America to demonstrate ONAP elements.  
    2. Action/ TOC members vote to approve Martin's email for a new repo request.
    3. Action/ Rittwik: Share the spreadsheet with Jinri and Yingying.  Regarding the topic of O-CU 5G status.
       1. Rittwik: asked Yingying to share Cherry release to pass along.
          1. Jack: This is important that we promote and support in the Cherry release.  I am looking for progress in the Cherry release.
          2. Rittwik: ODU OCU ORU are discussing their minimum support that they agree to inside Radisys, Viavi, Yingying are providing input to show they are in consensus. 
          3. Jack: That starts to make them more useful.  
    4. Action/ Trishan de Lanerolle provide the Insight slides to Farheen Cefalu
       1. Jack: We got the report last week from Trishan.  People saw issues with Unknown attributes.  Farheen got most of that addressed.  We have improved the unknowns and got them addressed.
       2. In the attribution process one of the challenges we've observed is as an AT&T representative to make a decision, people were contributing from different att.com domain we were seeing code coming from different parts of the company.  We were getting a lot of dither inside the AT&T.  Even though I can see it and know that contributions are coming from Nokia.  As a company think about unifying your subdomains into one company domain to make it easier to see the entire company.
       3. John Keeney: Cross cutting projects such as documentation and tests.  Content is driven by other projects.  Such as Non real time RIC can we tag some of those changes to certain topics.
          1. Jack: Yes, we are open to that discussion.  We can review for example they only had information by each sub project which made it difficult to see progress by sub sections.  We can carve out time to talk about it and work with Trishan and team to work with.  
             1. John: To make sure everyone gets credited for work they are doing.  
             2. Jack: Documentation has it's own set of reports.  There is ability to look at that and it is separate.
    5. Action/ PTLs provide one or two bullet highlights worth including in the press release.  It does not have to be long.  One or two sentences one or two bullet points.  03 Jun 2020 Should include statements from any company's.
       1. Jack: I will send it out in the reflector.
       2. Matti: What is the process for collecting highlight emails?
          1. Copy Jack in an email.
       3. Rittwik: Put the highlight you think you have received put it on the front Bronze highlights.  Put it on the Bronze Release page.  

14. Standing Agenda Items (Brief Status of Ongoing Activities)

    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

       1. Bronze Timeline

          1. We are at the end of the timeline. 
       2. Review Bronze Release Highlights

    2. user-59b16 Requirements Software Architecture Committee

    3. user-d3360  Integration and Test

       1. RSAC defined flows for Bronze.  Traffic steering has been completed and successful. 
          1. Traffic Steering use case is successful.
          2. For A1 flow under health check segment flows have been successfully tested.
             1. Hello World is not working yet so we are using traffic steering.
          3. ODU High are successfully able to establish heathcheck communication.
             1. O1 alarm flow over healthcheck we have model re-alignment are different.  We will set up a meeting with the PTLs of both OAM and Near Real time RIC.  We will see if we can close this gap and how long it will take.  Thoralf has a conflict and Martin is not available today.
             2. Jack: Do we understand the gap why it happened.  How do we address this moving forward? Is this improve communication? Change specs?  Or get clarification on the topic?
                1. Lusheng: There is a short term to see how large the gap is and can we close in this release?
                2. For longer term pairwise testing on different projects has been minimal.  In Cherry improve in the design and architectural phase if somebody can own the ETE flow.  Not just a high level agreement at the definition phase.  We are finding it at the end of the release.
                3. We should start pairwise and intercomponent earlier than the last integration and testing phase.  We couldn't do much of testing.  It would be better if the developer or owners of the inter communication or components throughout.  
          4. In terms of sheduling we have until the end of next week.  The go/no go will happen next Wednesday.  Next week we will have the virtual face to face as well.  The projects need to branch the code, documentation, and release notes.  We will try our best to target this deadline but we may need some time to cover the final release items.  
          5. Jack: TOC please provide input regarding slipping the timeline by one week.  This will delay the press release.  The TOC members should talk to the participants and getting these items addressed.  This is crunch time and look forward and prepare for a slip in the schedule by one or two weeks.
          6. Rittwik: I think you've completed 90% of testing.  The 10% can be pushed to maintenance meeting.
          7. Jack: We'll discuss the details in next weeks meeting.

    Standing Agenda Items (Brief Status of Ongoing Activities)

    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

       1. Bronze Timeline

       2. Review Bronze Release Highlights

    2. user-59b16 Requirements Software Architecture Committee

    3. user-d3360  Integration and Test

    4. 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. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

       2. Matti Hiltunen RIC Applications (RICAPP) 

       3. Thoralf Czichy RIC Platform (RIC)

          1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)

       4. user-a934b O-RAN Centralized Unit (OCU) 

       5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

       6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

       7. Martin Skorupski Operations and Maintenance (OAM)

       8. Alex Stancu Simulations (SIM)

       9. Xiaohua Zhang Infrastructure (INF)

       10. weichen ni Documentation (DOC)

       11. (TBD) O-RAN Radio Unit (ORU)

15. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 

16. Planning for Next Meeting

17. Any Other Business (AOB)

    Keep working towards completing our tests.

     

    Get back to Lusheng to assist with integration work.  I appreciate everyones efforts and see if 

18. Meeting Summary (resolutions, new action items, etc.)

    1. Votes:
       1. The minutes of the prior meetings were reviewed, and corrected by Farheen who replaced Jean-Paul name where Juha had seconded last 20 May 2020 meeting minutes approval voteno corrections.
       2. Vote to approve minutes for 20 27 May 2020 
       3. On motion made by Juha Oravainenby John-Paul Lane
       4. Seconded by Ganesh Shenbagaraman
       5. VOTE: Vote taken, item passed
       weichen ni
       6. VOTE: Vote taken, item passed
    2. Actions:Actions
       1. Action/ Trishan de Lanerolle provide the Insight slides to Farheen Cefalu
       Action/ PTLs provide one or two bullet highlights worth including in the press release.  It does not have to be long.  One or two sentences one or two bullet points.  03 Jun 2020 Should include statements from any company's.
       2. Action/ William DIEGO update on the coordination with the O-RAN test group
       3. Action/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
       4. Action/ Vishnu send Rittwik the slides for the ITU / AiML ChallengeAction/ TOC members approve Martin's email for a repo request.
       5. Action/ Rittwik: Share the spreadsheet with Jinri and Yingying.  Regarding the topic of O-CU 5G status.Post ITU / AiML Challenge slides on the wiki and pull together a team.  Include Thoralf.
       6. Action / Jack send the highlights out on the reflector before the press release.

Archived Meetings