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

29

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu 

2. Roll Call & and Quorum Check

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair

   x

   China Mobile	Jinri Huang Co-Chair

   x

   Deutsche Telekom	David Streibl

   x

   NTT DOCOMO	Toshiro Kawahara
   Orange	Vincent Danno

   x

   Verizon	Viswa Kumar

   x

   
   

3. Review and Agree to Minutes of Previous Meetings
   1. The minutes of the prior meeting were reviewed, and there were no comments, questions or corrections. On motion made by David and seconded by Viswa, the minutes of the May 06, 2019 meeting were the approved by the TSC members. 

4. • VOTE: Vote taken, item passed.

5. The minutes of the 5/8/19 meeting were reviewed, and there were no comments, questions or corrections. On motion made by David and seconded by Vince, the minutes of the May 06, 2019 meeting were the approved by the TSC members. 

VOTE: Vote taken, item passed.
7. Review of Today's Agenda
8. Status of Open Action Items (Old Business)
   1. Action Lusheng post the Rittwik's requirements document master mailing list.
   2. Action Farheen share Rittwik's document on the wiki. (Done)
   3. 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.
      1. Is the O-RAN SC community open to people outside of the O-RAN Alliance?
         1. Yes, this is open source LF project.  All activities here will occur as an open source project and any one can contribute under Apache2 and we're putting a process in place for you to participate.
   4. Action Farheen remove Registration and Visa letter
   5. Action Phil send Jack the acumos non-discriminatory document.
   6. Action Farheen remove Registration and Visa letter from Tokyo face to face.
   7. Action David Streibl send a note to the community about the color naming convention.
   8. Action Lusheng share repo changes and committers spreadsheet with Farheen to attach to these minutes.
   9. Action Lusheng provide gerret repo descriptions to LF technical team.
   10. Action David Tallgren send the proposal to the mail list.  Proposal is to make the RIC as an O-RAN project.  Start a new project called RAN Intelligent Controller or RIC under the Apache2 license.
   11. Action Jack will talk to TOC about extending the TOC call to 90 minutes as opposed to 60 minutes.Action Naming of Releases
9. 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
5. Requirements and Software Architecture 

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

    1. Proposed changes to the gerrit repositories.  Updates to committers.  We will need to get the community approval to execute the changes.
    2. Add RIC as a new project.

    Items 

11. Planning for Next Meeting
12. Open Discussion
13. Any Other Business (AOB)
14. Meeting Summary (resolutions, new action items, etc.)

2019 05

22

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

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum

1. Check

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

   
   

2. Review and Agree to Minutes of Previous

1. Meetings
   1. The minutes of the prior meeting were reviewed, and there was a correction to attendance.  Vince was removed and David Streibl was added. On motion made by David Streibl and seconded by Viswa, the minutes of the May 15, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
   2. The minutes of the 5/8/19 meeting were reviewed, and there were no comments, questions or corrections. On motion made by David and seconded by Vince, the minutes of the May 08, 2019 meeting were the approved by the TOC members.
      1. VOTE: Vote taken, item passed.
2. Review of Today's Agenda
3. 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.
    • 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

1. 1. Action Lusheng post the Rittwik's requirements document master mailing list.
   2. Action Farheen share Rittwik's document on the wiki. (Done)
   3. 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.
   4. Is the O-RAN SC community open to people outside of the O-RAN Alliance?
      1. Yes, this is open source LF project.  All activities here will occur as an open source project and any one can contribute under Apache2 and we're putting a process in place for you to participate.
   5. Action Farheen remove Registration and Visa letter from Tokyo face to face.
   6. Action Phil send Jack the acumos non-discriminatory document.
   7. Action David Naming of Releases 
      1. Colors are promising except for Magenta which is a name of a company. 
      2. Action David send a note to the community about the color naming convention.
2. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
   2. Action Farheen Send out a reminder for the TOC to take a vote on finalizing the release calendar. 
   3. Report out from PTL: Stand-Up & Report Out on Blockers
   4. Test & Integration Planning
      1. Jinri - we have to keep the test and integration separated.
      2. In this space we will be focusing on operation of the software while they will look at the RAN operations using the software as a key component of what is being delivered to them.
      3. Can a non-TOC during the conference call?  How does the open source community align with O-RAN Alliance?  How do the working groups align with each other?  There is no channel of communication between the groups.
      4. Jinri - There is an annoucement about the O-RAN face to face.  The TOC will talk on Tuesday and Thursday.  For us we haven't drawn the agenda for face to face. We need to figure out how to have the face to face meetings between the WGs.  WG 6, 8, will not be overlapping.  We only have 4 days and 4 meeting rooms.  Every time there will be 4 working groups in parallel.  We may collide with the schedule of WG2 or WG3.  If we think it is important to join working groups I will talk to Amir about joining the working groups in the evening. 
   5. Report Out of Sub-Committees
      1. Requirements and Software Architecture
3. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. Lusheng - Proposed changes to the gerrit repositories.  Updates to committers.  We will need to get the community approval to execute the changes.  From Andrew Grimberg (LF) to Everyone: (08:55 AM) 
FYI LF Release Engineering will take results of votes over the mailing list as valid too
   2. Lusheng - reviewed new and updated repositories and committers.
      1. Are many of the projects are related to near real time RIC project? Yes  This is seed code.  This gives people to see the activities going on in the seed code space.
      2. Action Lusheng share repo changes and committers spreadsheet with Farheen to attach to these minutes.
      3. Jinri - I want to understand moving the seed code to project and it's process.  We need to decide what kind of seed code is good enough for the project.
         1. O-RAN SC form a project for the RIC that will report up to the TOC and anyone who wants to be involved.
      4. The new committers and repositories.  On motion made by Jack and seconded by Jinri, new committers and repositories was approved by the TOC members. 
         1. VOTE: Vote taken, item passed.
      5. There are no descriptions for the repos because I have not been given any.  Action Lusheng provide descriptions to LF.  

1. 1. Add RIC as a new project David Tallgren  Action David Tallgren send the proposal to the mail list.  Proposal is to make the RIC as an O-RAN project.  Start a new project called RAN Intelligent Controller or RIC under the Apache2 license.
      1. Jinri - How do you share the alignment between the project and WG3?  
         1. The TOC has to figure out.  Individual companies are not funding the O-RAN Alliance is funding the open source community to be formed.  There is software that is not high profile software such as OA&M operations.  So there is a series of activities that need to go on that may not appear to the O-RAN Alliance.  In a release software developers can go so far.  The challenge is to pull together goals that the O-RAN Alliance is asking for as the end goal.  There is a process that will take an incremental path towards those goals.  And if someone wants a function x and no one is willing to write the software x so the community takes a vote.  If the people who want x should gather the resources and step forward and execute on x. 
         2. The goal is the get the interested parties to develop the features.  Developers and contributors drive the week to week software contributions.  It is a relationship between specifications and developers.  Our goal is to achieve an O-RAN aligned implementation thru developers participation.  We take what O-RAN specifications are in place.  We accept all input from O-RAN and open participants.  We hand it back to the O-RAN Alliance test and they decide if what was developed is aligned with O-RAN Alliance.  We will continue to evolve the standards.  
            1. Concern that the release will not meet the WG3 plan.  E2 spec. 
               1. Open source does not wait for specifications.  It's highly iterative.  How it works is not defined until the developer starts to make it work.  In the open source space we don't wait.  We build it and propose ideas.  The WG3 will approve or not approve as a compliant implementation.  Documentation is important in the open source approach.  By the end of November you'll have software that may be acceptable or not.  Then you move on to B release.  That's the open source software driven approach.  
   2. Rittwik gave a high level description of the release A requirements
      1. We will have two meetings.  Both in the evening NYC time to accommodate Europe and Asia.
2. Planning for Next Meeting
   1. Should we extend the TOC to 90 minutes? 
      1. Action Jack will talk to TOC about extending the TOC call to 90 minutes as opposed to 60 minutes.
3. Open Discussion
   1. The scope of the project.  Does it include the CU, DU, RU Edgeware?  Yes, the names keep changing.  It includes the Non Real Time RIC like ONAP.  It includes the Near Real Time RIC OCU, ODU, what we can do with the ORU.  Open to other ideas that people have to what software tools, or components to round out making the whole O-RAN Alliance specification available to the broader community.  People take the source code. 
4. Any Other Business (AOB)
5. Meeting Summary (resolutions, new action items, etc.
   1. The minutes of the prior meeting were reviewed, and there was a correction to attendance.  Vince was removed and David Streibl was added. On motion made by David Streibl and seconded by Viswa, the minutes of the May 15, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
   2. The minutes of the 5/8/19 meeting were reviewed, and there were no comments, questions or corrections. On motion made by David and seconded by Vince, the minutes of the May 08, 2019 meeting were the approved by the TOC members.
      1. VOTE: Vote taken, item passed.
   3. The new committers and repositories.  On motion made by Jack and seconded by Jinri, new committers and repositories was approved by the TOC members. 
   1. VOTE: Vote taken, item passed.

1. • Action Farheen remove Registration and Visa letter from Tokyo face to face.
   • Action David Streibl send a note to the community about the color naming convention.
   • Action Lusheng share repo changes and committers spreadsheet with Farheen to attach to these minutes.
   • Action Lusheng provide gerret repo descriptions to LF technical team.
   • Action David Tallgren send the proposal to the mail list.  Proposal is to make the RIC as an O-RAN project.  Start a new project called RAN Intelligent Controller or RIC under the Apache2 license.
   • Action Jack will talk to TOC about extending the TOC call to 90 minutes as opposed to 60 minutes.

Chat Summary

From Jun Song (Samsung) to Everyone: (08:48 AM)

RH


From Andrew Grimberg (LF) to Everyone: (08:55 AM)

FYI LF Release Engineering will take results of votes over the mailing list as valid too


From Peter Moonki Hong to Everyone: (09:04 AM)

seems time is up, but I would like to leave some questions to O-RAN TOC for clarifying several stuff from open source perspectives. O-RAN SC is an open source project hosted by LF and will be releases under Apache2.o license. In the meantime, there is O-RAN Specification Code Project and it will rease the code under a different source code license, if I am undersrading correctly. What is the relationship between O-RAN SC and SCP and what is a role of TOC for dealing with them?


From Viswa ( Verizon ) to Everyone: (09:05 AM)

dropping for another call. thank you


From Peter Moonki Hong to Everyone: (09:06 AM)

And who can be a "Contributor" in ORAN SCP? any open source developers? or developers of O-RAN Alliance members?
Thank you in advance.

From TSC Zoom to Everyone: (09:07 AM)

probably we could answer peter 's question offline


From Andrew Grimberg (LF) to Everyone: (09:08 AM)

Anyone that has an LFID is potentially a contributor. IIRC we aren't requiring CLAs and just DCO so there's no barrier of needing someone to sign either a Corporate CLA or an Individual CLA before they can contribute. Just login and start contributing
DCO == Signed-off-by line in the commit message footer
CLA == Contributor Licsense Agreement


From Peter Moonki Hong to Everyone: (09:09 AM)

SCP is also under Apache2.0 license?
From Lusheng Ji to Everyone: (09:12 AM)

@Peter SCP is not under Apache 2. It is under a different license O-RAN Software License

From Peter Moonki Hong to Everyone: (09:13 AM)

Yahh that is my understanding as well. Then SCP is under SC?
or under O-RAN Alliance?

From Jun Song (Samsung) to Everyone: (09:16 AM)

RH

From Lusheng Ji to Everyone: (09:16 AM)

SCP and SC are sister projects under Linux Foundation. They have the same relationship W.R.T. O-RAN Alliance. They (will) share a lot of resources in LF but under different software licenses.


From Peter Moonki Hong to Everyone: (09:17 AM)

Okay, now I get it. Thank you for your kind information.


From Lusheng Ji to Everyone: (09:17 AM)

You are welcome.

From Peter Moonki Hong to Everyone: (09:20 AM)

need to drop off. thank you for all kind information.

From Farheen Cefalu (AT&T) to Everyone: (09:36 AM)

https://wiki.o-ran-sc.org/display/RSAC?preview=/1179968/3604507/O-RAN%20SC%20Ver%20A%20SW%20Requirements%2020190520a.docx
main@lists.o-ran-sc.org
Please send the requirements proposals to main@lists.o-ran-sc.org


From Jun Song (Samsung) to Everyone: (09:39 AM)

RH


From David (DT) to Everyone: (09:44 AM)

Sorry, have to go to other meeting

.

Return to todays agenda