Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu

  2. Roll Call & Quorum Check 

    Company

    		Contact NameAttendanceAlternate ContactAttendance

    AT&T

    Jack Murray Co-Chair

    x



    China Mobile

    Jinri Huang Co-Chair

    		x

    Deutsche Telekom 

    David Streibl

    		x

    NTT DOCOMO

    Masafumi Masuda




    O-RANge

    William Diego


    		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 meeting were reviewed, and there were corrections. On motion made by Jinri Huang and seconded by user-2057e   the minutes of the September 4, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
  4. Review of Today's Agenda
  5. Status of Open Action Items (Old Business)
    1. Action/ Jun Hyuk Song start the dialogue on the email list regarding the KPI monitoring xApp concern.  
      1. Jun has spoken to Matti.  Samsung has volunteered to work on the KPI monitor xApp.  Had discussion with Jun about what it means to be an xApp.  Ac xApp and simulator code.  Discussions are moving along.  Concern is that there is fairly little documentation in the LF and the ASA1 spec is not publicly available.  It makes it difficult for EU members to contribute.
    2. Action/ Claudio Coletti raise the issue of the E2 interface and WG3 schedule with the O-RAN Alliance.  
      1. David discussed w/ Claudio.  Presenting how to align spec for E2 will be ready to present to the TSC.
      2. There have been a range of discussions about how do we release the E2 and manage it.  Who owns the E2 spec and how do we document it.  3GPP and O-RAN are specifications.  We have communicated with 3GPP and there is a process of making a request from 3GPP.  Anyone making open source software for 3GPP should look at the wiki under Best Practices.  ASA1 - Jack will work on establishing a process for copyrites for 3GPP and O-RAN.
        1. Will there be a practice description of how to deal with 3GPP copyright information?
          1. Yes
            1. The O-RAN will be for material created under O-RAN Alliance?
              1. Yes, I hope that will be broader so we do't have to do much work. 
                1. Is O-RAN for finalized specs or work in progress?
                  1. It should cover both work in progress and final.  Normally we wouldn't know about wip and progress but since we have inside knowledge before the spec is published.  Jack will work through that.
        2. There was an email from standard development group who are coordinating the process of 3GPP.  Jinri shared with the community.  Call to community to identify the 3GPP issues and bring it back to Jack and Jinri.  
          1. For O-RAN that is correct.  For O-SC it is LF who owns the code and they need to sign off.  LF must be involved.  LF is the first gate.  That is where the information is downloaded from.  Should the PTL get started with the form?
            1. Yes, it's the ETC form.
            2. Do we have an estimate for the timeline?
              1. Hard to say because it is our first time through it.  ETC has not addressed open source.  We're not asking for document or republish whole chapters but we are asking for tables and subsections.  
          2. Yingying - Implementation of the 3GPP stack.  If we don't have agreement from 3GPP then we can upload anything?
            1. We should not be copying in 3GPP specs.  
              1. Is that the table or figures?
            2. Ganesh - for O-CU there is no challenge.  There is no issue.
              1. If you're implementing software that follows the software instructions of how to send the message there is no issue.  Implementing the functionality is not a concern.  If you're reproducing the exact messages then it needs to be covered by copyright.
    3. Action/ John Murray will try to get a representative from each PTL to provide someone to participate in the integration and test team activities.
      1. Service providers should be involved because they will understand what is expected of them.  It will understand what is working and what will work.  We need help in this community.  There is a high and low level activities.  Please reach out to Lusheng and get involved.  I expect all the PTLs to find a representative to participate.
    4. Action/ Tracy Van Brakle   continue discussion about Plugfest.  See where we can do plug and play activities at the MWC North Americas event.
      1. On track for December 2 and a white paper on December 5.  We should figure out something synergistic with China mobile. 
      2. Plugfest in Beijing and POC 
    5. Action/ John Murray talk to user-d3360 about the issues with signing of names on the CLA.
    6. Action/ Andrew Grimberg will check with the engineer of whether or not there is an automated process to auto-add the reviewers.
      1. These are all related to the same item.  For the new repo we are learning as we go.
      2. Action/ Farheen Cefalu combine t
    7. Action/ Andrew Grimberg provide documentation and proposal.  
    8. Action/ Andrew Grimberg vet the TOC process with the TOC members.
    9. Action/ Andrew Grimberg provide clear instructions to TOC mail list on how TOC members can get a gerrit account and the process.
    10. Action/ Farheen Cefalu send a message to the PTLs to provide a one page summary of their progress in the last four weeks to the TOC mailing lists.
      1. Rittwik - we have 5 and 6 more to go.  Rittwik will be setting up a call to be prepared to have a discussion.  Please get your open summary by Friday.  A lot of people have updated it in their wiki status pages.  Action/ user-59b16 create a space where we can do a review and set up a meeting to review the summary docs.
      2. Sachin - I have updated O-DU but it got lost in the email.
    11. Action/ John Murray discuss the B release name.
      1. Action/ user-2057e start a poll for B release.
    12. Action/ John Murray 3GPP copyright discussion
  6. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
    2. Release planning link.
      1. Work with the documentation team to keep documentation up to date.
      2. Jinri - For the Friday O-RAN bring to the attention of the co-chairs.
        1. We are taking the wright ups from each PTLs.  Keeping it simple is fine.  Rittwik is collecting them and make sure they are accessible.  
  7. Report out from PTL: Stand-Up & Report Out on Blockers
    1. Non real time RIC (RAN Intelligent Controller) - John Keeney
    2. RIC Applications - Matti Hiltunen
      1. I submitted a repo request and Jinri has approved.  
      2. On motion made by Matti Hiltunen to create a repo that KPI monitor xApp that calculates KPIs and exposes the xApps in the RIC and seconded by Jinri Huang
        1. VOTE: Vote taken, item passed.
    3. RIC Platform - Thoralf Czichy
    4. O-RAN Centralized Unit user-a934b
      1. On motion made by user-a934b to create a repo for O-CU seconded by Jinri Huang 
        1. VOTE: Vote taken, item passed.
    5. O-RAN Distributed Unit High Sachin Srivastava
    6. O-RAN Distributed Unity Low Zhimin Yuan
    7. O-RAN Radio Unit (TBD)
    8. Operations and Maintenance - Martin Skorupski
    9. Simulations - Alex Stancu
    10. Infrastructure - Xiaohua Zhang
    11. DOC - weichen ni
    12. O-CU user-a934b made a motion to create a repo for 

  8. Test & Integration Planning - Lusheng

    1. Please reach out to Lusheng to see how O-RAN works.  Lusheng will be scheduling meetings around test and integration for the Amber release.
    2. O-RAN software license for Apache 2 we have standard text to make the claim that we have a style of license for apache2.  We do not have O-RAN license yet.  We can ask our internal company review?  
      1. yes, we will then forward it on to Stefan (legal).  He can then talk to individual company.  Include a copy of what we do for Apache 2 for Sefan.
    3. We do have projects who want MIT open source licenses.  How can we include upstream projects.  How should we proceed?  One way is we do not host their code we download build and us when those upstream projects.  Not ideal but it is a clean way to practice.  Another way is if we do need to make modifications to upstream project first.  In practice it is difficult to do it first.  Do the upstream project first and then do our change in your local repo.  Create an external dedicated directory where you maintain the MIT license.  This way there is a clear differentiation between licenses.  
      1. Trishan - check the compatibility and MIT is compatible.
      2. GPL is complicated you have to build it.  We will put it in the best practices.  Interproject relationships like ONAP, ETSY, LF, to build stronger relationships.  Akraino and Acumos are active projects where we can expand.
  9. Requirements Software Architecture Committee - Rittwik
    1. We started the B release epics we want to share with the team.  Requesting all PTLs to improve and provide input.
      1. B release should include use cases that drive what we can test, demo, and deliver.  Specific work in each subsystem.  test team is driven by use cases, requirements, and team.  

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

    1. Start a discussion with alignment with community project ONAP, Akraino, Acumos
    2. Secondary project with code contributions.  If someone is interested in participating we can work on 
  11. Any Other Business (AOB)
    1. Jinri - request for PTL when you hold a teleconference is it OK for PTL can record the meeting.  Issues with China meetings.  
  12. Meeting Summary (resolutions, new action items, etc.)
  • No labels