Skip to end of metadata
Go to start of metadata

TOC Voting Members 

Company

NameAlternate

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
OrangeWilliam DiegoVincent Danno

Verizon

Viswanath Kumar Skand Priya

Kristen Young

Nokia

Juha Oravainen

Thoralf Czichy

Radisys

Ganesh Shenbagaraman

Sachin Srivastava

Ericsson

John-Paul Lane


Available (10)Available (10)
Available (11)Available (11)
Available (12)Available (12)

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.


TOC Meeting Info

Technical Oversight Committee meetings are open to the public and held on Wednesdays at 8 AM Eastern Time USA.  World Time Zone Map

Zoom 2 Info:

  • Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/6540568082
  • Or Telephone: Dial (for higher quality, dial a number based on your current location)
CityTimeZoom/Audio Bridge
UTC-timeWednesday 12:00

https://zoom.us/j/6540568082

New York (EDT / UTC-4)Wednesday 08:00+1 669 900 6833
+1 646 558 8656
855 880 1246 (Toll Free)
877 369 0926 (Toll Free)
Meeting ID: 654 056 8082
Paris (CEST / UTC+2)

Mar-11/Mar-18/Mar-25: Wednesday 13:00

Apr-1-2020 onwards: Wednesday 14:00

+33 7 5678 4048
+33 1 8288 0188
805 082 588 (Toll Free)
Meeting ID: 654 056 8082
Beijing (CST / UTC+8)Wednesday 20:00+86 10 87833177
+86 10 53876330
400 616 8835 (Toll Free)
400 669 9381 (Toll Free)
Meeting ID: 654 056 8082
Tokyo (JST / UTC+9) Wednesday 21:00+81 524 564 439
+81 3 4578 1488
0 800 100 5040 (Toll Free)
Meeting ID:
654 056 8082
Helsinki  (EEST / UTC+3)

Mar-11/Mar-18/Mar-25: Wednesday 14:00

Apr-1-2020 onwards: Wednesday 15:00

+358 341092129

Meeting ID: 654 056 8082


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. ActionWilliam Diego Maza update on the coordination with the O-RAN test group
    2. Action/ 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: Post ITU / AiML Challenge slides on the wiki and pull together a team.  Include Thoralf.
    5. Action / Jack send the highlights out on the reflector before the press release.
  9. 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. Rittwik Jana Requirements Software Architecture Committee

    3. Lusheng Ji  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. Yingying Wang 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

Recording: 2020_06_03-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


    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 no corrections.
      1. Vote to approve minutes for  
      2. On motion made by John-Paul Lane
      3. Seconded by weichen ni
      4. VOTE: Vote taken, item passed
  4. Review of Today's Agenda

    1. Juha - Last week discussed Virtual meeting.  
      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.
  5. 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.
  6. 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.
  7. 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.
  8. Status of Open Action Items (Old Business)

    1. ActionWilliam Diego Maza 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. ActionTrishan 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.   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.  
  9. 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. Rittwik Jana Requirements Software Architecture Committee

    3. Lusheng Ji  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.
    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. Yingying Wang 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.)

    1. Votes:
      1. The minutes of the prior meetings were reviewed, and no corrections.
      2. Vote to approve minutes for  
      3. On motion made by John-Paul Lane
      4. Seconded by weichen ni
      5. VOTE: Vote taken, item passed
    2. Actions:
      1. ActionWilliam Diego Maza update on the coordination with the O-RAN test group
      2. Action/ 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: Post ITU / AiML Challenge slides on the wiki and pull together a team.  Include Thoralf.
      5. Action / Jack send the highlights out on the reflector before the press release.
  • No labels

11 Comments

  1. The "Zoom Meeting Recording" link under the "2019 05 01" Meeting minutes points to an O-RAN-SC charter PDF instead of the expected .MP4 file

    1. Ranny Haiby  I have updated the link to the correct link.  Thanks for catching!

  2. The "Zoom Meeting Recording" link under the "2019 0515" Meeting minutes points to 2019 0508 meeting recording.MP4 file.


  3. Jun Hyuk Song , I was unable to upload the May 15 recorded zoom meeting.  I opened a trouble ticket.  I'll keep you posted.

  4. I suggest creating one sub page per week to record meeting minutes to prevent scroll overflow of this page.

    1. Viswanath Kumar Skand Priya Yes, All archived minutes are on the side navigation.  This page is reserved for future meetings.

  5. July 3rd 7.2 recording is the same as June 26th.  Actually, Jinri explained meeting results with David & Inspur, and Xiaohua Zhang from Wind River confirmed the cooperation with Inspur on StarlingX. Jack concerned about the relationship between upstream and OSC, suggested Inspur to do work different from upstream in OSC. So it is better to revise it.

  6. gao xian , thank you for bringing the issue to my attention.  I have updated the video file.  The meeting has been archived.  2019 07 03.  Good luck!

  7. Farheen Cefalu

    A few comments on Aug. 7 meeting minute.


    1, throughout the whole minute, it should be "O-RAN" instead of "ORAN";

    2, In New business → POC and Spec investigation from EC discussion: it should be "MWC" instead of "NWC". There are 3 such occurrence. 

    3, In 5.d.3 regarding Ganesh and Alex's AP: it should be ODU instead of ODL;


  8. Farheen Cefalu


    One more comment regarding the Aug. 7 minute.


    On the last AP, the POC could be video, ppt, or live/static demo

  9. Farheen Cefalu


    The numbering of 0828's agenda looks not correct...