Technical Charter for O-RAN Software Community

TOC Mail Lists

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)
  • 855 880 1246 (Toll Free), 877 369 0926 (Toll Free)
  • Meeting ID: 654 056 8082
  • International numbers available: https://zoom.us/u/acyy3hylQi

2019 05 15

Anchor

return

return

return2019 05 22

Zoom Meeting Recording

Agenda Agenda

1. Call for Scribe (minutes owner) 

2. Roll Call & Quorum Check  Check

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair
   China Mobile	Jinri Huang Co-Chair
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Toshiro Kawahara
   Orange	Vincent Danno
   Verizon	Viswa Kumar

   
   

3. Review and Agree to Minutes of Previous MeetingMeetings
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
   1. Action
   Phil Report out status of domain name migration.
   2. Lusheng post the document that Ritwik shared to the master mailing list.
   3. Action Farheen share Rittwik's document on the wiki.
   4. Action Farheen talk to Lusheng about gaining access to oran alliance wiki in order to update the events page with the face to face meeting in Tokyo.
   5. Action Phil send Jack the acumos non-discriminatory document.
   6. Action Lusheng Report status of a PTL for the new Requirements and Architecture sub-committee
   7. Action TOC review Requirements document for A release.
   8. Action Farheen add the event that Jinri posted to groups.io
   9. Action David will gather naming convention for releases. 
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

2019 05

15

Zoom Meeting 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  

• Review and Agree to Minutes of Previous Meeting

  • The minutes of the prior meeting were reviewed, and there were no comments, questions or corrections. On motion made by Jinri and seconded by David, the minutes of the May 1, 2019 meeting were the approved by the TOC members. 

    VOTE: Vote taken, item passedNo Quorum therefor no vote taken.
• Review of Today's Agenda
• Reviewed by TOC - Only TOC are allowed to vote and second items.  Others can make proposals.
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 ORAN 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 ORAN.  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 ORAN 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
• Domain name change - rough timeline of 2 weeks. 
  • The operations team will reach out to Lusheng. 
  • When we launched we were oran-osc.  We have been guided to change the dns to o-ran-sc.org.
  • No disruption to anyone using the old domain name.
  • Mailing lists are on the Groups.io will move to the new domain name.
  • Action Phil will contact Jordan from LF Ops.
• Decide on requirements for first A release.
  • We can started a new sub-committee.  I have posted a document of what functionality we want to target for this first release.
  • WG3 started putting out some use cases.
  • We have to decide what we are targeting to buld epics and use cases around that requirement.
  • This committees job is to work on requirements for the software release.  We need to form that committee and start having meetings around that activity.
  • Action Lusheng post a message in the email list to organize that meeting.  We will elect the PTL for that activity.  We have until the end of the month to get into the release A process and plan.  The key here is deciding what we will do in this first release.  AT&T has pushed seed code for the near real time RIC and xApps (orchestration and A1) and are looking for contributions as well as building blocks and logging.  Then there is the dicussion about how much further down the stack we will work for this release for CU, DU, RU, areas.  Do we consider a simulator?  All that starts around the subcommittee and documents around A release.
    • Jinri - Lusheng I suggest you reach out to WG co-chairs in the ORAN Alliance.  Their early involvement is very important.
  • We will start with one committee for now to get started.  There is a large amount of work to be done.
  • Lusheng sent out an email to the mailing list to start the conversation.
    • These are the items we think we should get started with.  If we want to set up an end to end system running by the end of this year.
    • Action Team  Looking for contributors for near real time RIC.  
      • Plantform stable and open plugable architecture.
      • xApps are targeting specific functions for the NRTRIC.  
        • Expecting vendors to contribute their xApps to the project.
      • There is also real time RIC and looking for contributions to ONAP.  This the function that oversees the operation of the RIC.  We are looking to adopt.
      • The next item is portal or dashboard.  You need a UI to operate the deployments and operations.
      • CU/DU we are looking for contributions to run.  Intel and Radisys intends to contribute.  
      • Simulator project this is the initial release and we won't have the luxury of all the pieces.  Future this project can facilitate testing the system and simulations.  
      • Let's discuss the larger use case for release A.
    • Jack - Projects are important for the epics, user stories, repos, and how the overall project is organized.  Each of these areas will have a sub-team.  Each project has a PTL.  There are code committers along with contributors.  Everyone can be a contributor.  Using Apache and ORAN licenses.  Looking for input from this meeting and the requirements meetings and the mail lists.  They will appear in the tab above projects.
      • Jinri- the accelerator project is missing from this list.
        • Yes, this is software only.  Action Lusheng follow up with the team for the Accelerator project and network guys.
        • China mobil is not listed here either.  
        • Some of these are not all projects.  Some will be cloud layer and each piece have it's own sub-project.  We don't want to have 50 projects but want some pieces of work done under a more general project grouping.  Here we want to see major components.  We don't have to have as many activities but it stretches the group to cover more topics.  
• Need a volunteer to work with O-RAN WG.  The O-RAN Alliance TSC handles filling in the position O-RAN WG. 
  • We need to close on filling the TSC slots.  It is an ORAN TSC function.  We are going to operate with whatever TSC members assigned so we are moving forward with those 6.  Since we only have six those six will be doing votes.  As more are approved by ORAN TSC they will become active in this community.  LF projects set up the structure for projects this way.
    • Jinri - There is a change from EC.  Jinri will update Jack later.  
• Jinri will push on completion of the charter.
  • email from Hank that he will distribute the charter as a draft.  It's not approved until the ORAN Alliance vote approves it.  We will be sharing the updated license and the final charter for the ORAN specification after this meeting.  
  • Has the EC set a deadline or dates on the documents?
    • Jinri - dates for document?  No
    • This TOC has requested a deadline target.  We wanted the updated drafts by last Friday.  They are out but not distributed the legal approved.  We will try to get comments by May 17.   
      • Is there a timeline from the EC perspective?
        • No, it's up to us.  In our last meeting we committed to May 17.  Just received their draft today.  Targeting May 23, 24.
        • We need it done by the end of May for the project kickoff.
  • This version is much easier to be accepted by key players.  It takes the feedback from the first round and incorporates it.
Jinri post ORAN event in Japan in June to committee mail list.Action Farheen add
• • the event that Jinri posted to groups.io
  • TOC come up with a list of features or epics before the M0 start date.
    • We are structuring the requirements subcommittee.
    • The document Jack is working on will go over the high level requirements.
  TOC come up with a naming convention for our releases.
  Action
  • • • Action Farheen talk to Lusheng or Rittwik to get access
  • • David will gather naming convention for releases.
    
  • • Be aware of trademarks.
    • • • Selecting names of rivers.
          • In OPEN NFV.  We were selecting rivers on different continents and it was difficult
          • Colors? https://color-ize.com/color-list.php
    constellations?
  • Standing Agenda Items (Brief Status of Ongoing Activities)
    • Release Manager/Release Planning: Weekly TOC Scheduling
  • We are looking for a volunteer for a release manager.
  • • Report out from PTL: Stand-Up & Report Out on Blockers
  PTLs report out blockers and issues.
  • • Test & Integration Planning
  • Key to tracking the health of the release.
  • • Report Out of Sub-Committees
  • Progress of the activities and any issues that they have.
  We have to start to attract software developers and contributors to the projects.
  • New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 
    • Add ORAN 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
    • Working on requirements document
    • • Get more developers to join this call.  We have 30 but need to get going.
      • Action Team increase contributors by encouraging people to participate!
    Getting volunteer to contribute code for a successful release.
    • 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 oran 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.

    Return to todays agenda