Zoom Meeting Recording (Zoom meetings are not uploading to this wiki.  A ticket was opened with Helpdesk linuxfoundation.org #75652)

Audio Only Recording

Agenda

  1. Call for Scribe (minutes owner) 
  2. Roll Call & Quorum Check 
  3. Review and Agree to Minutes of Previous Meetings
  4. Review of Today's Agenda
  5. Status of Open Action Items (Old Business)
  6. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
    2. Report out from PTL: Stand-Up & Report Out on Blockers

    3. Test & Integration Planning

    4. Report Out of Sub-Committees

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

  8. Planning for Next Meeting
  9. Open Discussion
  10. Any Other Business (AOB)
  11. Meeting Summary (resolutions, new action items, etc.)

Minutes

  • Call for Scribe (minutes owner) Farheen Cefalu
  • Roll Call & Quorum Check  

Company

Contact NameAttendanceAlternate ContactAttendance

AT&T

Jack Murray Co-Chair

x

China Mobile

Jinri Huang Co-Chair




Deutsche Telekom 

David Streibl

x

NTT DOCOMO

Toshiro Kawahara




Orange

Vincent Danno




Verizon

Viswa Kumar




  • Review and Agree to Minutes of Previous Meeting
    • No Quorum therefor no vote taken.
  • Review of Today's Agenda
  • Status of Open Action Items (Old Business)
    • Phil Report out status of domain name migration.
    • All services jenkins, jira, wiki, gerret, and the last of the github pages will be complete by the end of today.
    • Lusheng Report status of a PTL for the new Requirements and Architecture sub-committee
      • gerret transition migration was completed yesterday.
      • Do we have any new code contributions?
      • Lusheng - I had a meeting with Lenova and China Mobile on Monday.  Lenova has AAL Abstraction Adaptation Layer.  described as living in the hyper visor layer of virtualization to improve.
      • China Mobile wants to make contributions for integrated of eNB.  It is a software module target environment is bare metal and not VM.  They wish to contribute to ORAN.  I have the meeting recorded and update to the wiki site today.  I will have a follow up meeting with them.  I briefly discussed with them but I have a follow up meeting.
      • I created a mailing list for TOC.
        • We need to spread the word and start attending these meetings to get things done.  There are ongoing discussions around the TOC.  We have to bring others to grow the community.  I encourage everybody to go out and talk to their partners. 
    • TOC review Requirements document for A release. See Release Calendar
      • Kickoff of software subcommittee to have working meetings.  To that end we have to figure out the approach for the mailing list.  We should start getting the committees together to gather requirements and use cases to put together this release.  This document is open to changes.  These are Jack's and Rittwik's thoughts on how to get going.  We don't have long just the remainder of the month. 
      • We will get into M0 of this release on June 3.  It is a point of discussion.
      • Rittwik -  This is a pre-spec.  Shared the RIC architecture picture. 
      • Release A M0 starts June 3.  We have to get a first draft and get going based on on that.  M0 is taking and finalizing the proposed requirements into what we think we can execute.  Preparing for development.  The meeting in Tokyo in June is late into this process.  By that meeting most of this planning work will have been set up.  One of the things to figure out is how to line up O-RAN specifications meetings. 
      • By June 22 we need to have a good enough draft for the face to face. 
      • By then most of the epics and user stories will have been entered and you will be into sprint grooming.  Some pieces of software come from other places such as logging.  Not all software has to be developed in our project but can leverage as much open source work that is out there.
      • Representation of a full end to end O-RAN Stack.
      • There is a non Real time RIC with an A1 interface. Consider Non-RT RIC (e.g. ONAP)
      • Near-RT RIC framework
      • Application/ms frameworkd to host multiple xApps
        • A amessage bus
        • A1 mediator
        • E2 Termination agent
        • R-NIB DBaaS 
        • UE manager
        • Dashboard
        • Need a provider for O-CU
        • O-DU
        • Open Front Haul
        • O-RU (will host the RIC)
      • RIC Platform
        • Near-RT RIC  Service use cases are left blank for now.  We need to discuss and decide what would be a good high level use case.  We will look at WG2 use cases traffic steering, load balancing will be a good first level.  Pick some basic use cases and align them with O-RAN.  We want a use case that will drive the work but not step on the end application.
        • Project objectives
          • ONAP - Uncertain. 
          • Viewing architecture Non-RT RIC shall be able to update policies in several near-RT RIC.
          • For simplicity we are going to keep it one to one.
          • then we need a communication bus.
          • A release cardinality of one to one for now.
          • Action Lusheng post the document that Ritwik is sharing to he master mailing list.
          • Create a mail list for sub-committees and for sub-projects.
          • What is the plan for the upstream community?
          • We will do all of our work in Dublin.  If you go SDNR route you will be putting your rest interface thru SDNR.
          • Netcomf is not easy to implement.  It will be mostly REST interfaces in the O-RAN SC will have a non real time repo.
          • Where are we with getting the team in place?
            • We're having a meeting tomorrow but we are not making fast enough progress in getting people in place.
            • We need to get more people participating here.
      • Add the event that Jinri posted to groups.io
        • Action Farheen talk to Lusheng or Rittwik to get access
      • David will gather naming convention for releases.
  • Standing Agenda Items (Brief Status of Ongoing Activities)
    • Release Manager/Release Planning: Weekly TOC Scheduling
    • Report out from PTL: Stand-Up & Report Out on Blockers
    • Test & Integration Planning
    • Report Out of Sub-Committees
  • New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 
    • Add O-RAN Alliance meeting in June to the wiki.
    • We have to get more developers.  Action Phil send Jack the acumos non-discriminatory document.
  • Planning for Next Meeting
    • Get more developers to join this call.  We have 30 but need to get going.
    • Action Team increase contributors by encouraging people to participate!
  • Open Discussion
  • Any Other Business (AOB)
  • Meeting Summary (resolutions, new action items, etc.)
    • No votes taken due to lack of quorum
    • Action Lusheng post the document that Ritwik shared to the master mailing list.
    • Action Farheen share Rittwik's document on the wiki.
    • Action Farheen talk to Lusheng about gaining access to O-RAN alliance wiki in order to update the events page with the face to face meeting in Tokyo.
    • Action Phil send Jack the acumos non-discriminatory document.
  • No labels