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 06

12

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

Audio Recording

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

   China Mobile	Jinri Huang Co-Chair

   x

   Deutsche Telekom	David Streibl

   x

   NTT DOCOMO	Toshiro Kawahara

   x

   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 corrections. On motion made by David Streibl and seconded by Jinri the minutes of the June 29, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
4. Review of Today's Agenda
   1. Jinri - Add Face to Face discussion 
   2. Vincent - Recommending to end times as scheduled.
   3. Lusheng - Approval from the TOC to accept Seed Code contribution.
   4. Jack - Proposing a project list for the "A" release discussion
5. Status of Open Action Items (Old Business) 
   1. Action / TOC take a vote on the Near Real Time RIC project proposal sent by Tapio Tallgren. 
      1. Scope would not include the RAN or ONAP except for testing purposes.  Our proposal is to have our project technical leader for the project.
      2. Jinri - we need a synchronization meeting once a month with WG3.  
         1. Vincent - Noting that this is not specific to this proposal.  We will have the same thing to consider for future projects.  We need to have the right tools in place here as we are doing in the Alliance.  We have to start somewhere so we have to be careful not to put too many barriers to what we want to do.  I think it is good to start the work.  Nokia has agreed to align with WG3. 
            1. Jinri - I don't want to hinder progress.  I want to make it crystal clear that we want to have this mechanism in place prior to starting to work.
               1. David S.  I agree with Vince.  It should be an important topic for the Tokyo meeting.
                  1. Jinri - it is on the agenda for the f2f.
                     1. Jack -  We have to have the discussions about whether the WG is tightly aligned with their work or more flexible. A lot of the non functional requirements are not in the domain of the work group in general and we have to work on the Alliance side to find out who will be working on those activities.  Yes, that is a part of this A release cycle.  I think it is important to work through that process.  It's probably more around requirements the PTL and the epic responsibilities.  To make them successful we have to support them.
                        1. David - We also need the synchronization between the requirements committee and the working groups.  I suggested to Claudio of WG3 was to join the calls of the requirements committee.  We need to create the space for the collaboration early on so everyone knows whats happening on all sides.
                        2. Vincent - this is an important discussion and we need to find the right balance between process and encouraging contributions.  If our process is too heavy we will not have contributions.  Keep subcommittees to a minimum.  We need a balance.  Because this is release A we are at the start and should encourage the work.  For now the lightweight ad-hoc process is fine.  It is good to add it to the agenda to the next meeting.  We can look at a long term framework not in release A but the future.  To summarize we should start with something simple.  Let's make sure we are addressing the question but we are keeping it simple. 
                           1. Jack I agree.  keep it simple move quickly and iterate.  It is the responsibility of TOC is oversight.  Votes are not permanent.  We can change in the future according to projects ability to grow.
                  2. Phil - Projects are around repos and the projects go hand in hand.  Is this on the Apache side or the O-RAN Alliance side?
                     1. I suggest we do this using a template for the process to create a project.  This template should bring up which license is being used.
                        1. Tapio this is under the Apache license.
                     2. Jack -  Is it the project or the repo that is defined by the license.
                        1. Phil - You can have two licenses in a repo but does the committer of the project want two licenses?  We want to make it clear up front when creating a project.  It's a question for the TOC.  
                        2. Jack - This is for Apache.  We're going to take it incrementally with projects first.  then PTL, then committers.
                        3. Phil - Tapio provided the list of committers who will have commit rights.
      3. The new NRT-RIC project and committers for the O-RAN SC was reviewed . On motion made by Vincent and seconded by David creating the Near Real time RIC project was approved by the TOC members. 
         1. VOTE: Vote taken, item passed.
      4. PTL role for the first Near Real Time RIC project.  Jack - I am in favor of the TOC voting for the PTL role.
         1. We have a proposal that Thoraf Czichy as the PTL.  Check Thoraf's Linked In profile.
      5. Make Thoralf the PTL for the Near Real Time RIC project. On motion made by Jack and seconded by David making Thoralf the PTL for Near Real Time RIC project was approved by the TOC members. 
         1. VOTE: Vote taken, item passed.

1. 1. Action / Jinri Huang send a reflector to highlight O-RAN members to attend the Shanghai O-RAN Alliance meeting following the Tokyo meeting.
   2. Action/ user-2057e send out a poll for a color that begins with "a" for the A release.
      1. Holding because the wiki had a conflict.  Action/David put out a poll to select a fish and which fish name for release A.  Try not to pick a complicated name.
   3. Action / user-d3360 will make a request over the email chain about the June 5th deadline.  There is an interest from Intel, Radisys, Inspur, China Mobile to contribute seed code and they will need the O-RAN licenses in standard plain text.
      1. Charter for the O-RAN specification project has been finalized and approved by the O-RAN legal team and this has been run by Scott.  There is a charter a license and a contributors agreement that needs to be signed and associated with that project.  Stefan has prepared the documents in PDF form and will be distributed for the EC tomorrow at Thursday.  We have to make sure it gets distributed to EC members.  Jinri - Yes he has notified the EC members.  The O-RAN license will be available after the Thursday's meeting.
      2. Lusheng - From a software seed code perspective can we also claim a license claim text?  It is legal language and need help with O-RAN.
      3. Seed code request was unable to do through email.  I will make the request later on this call for other repos that are ready for creation.
      4. Action / Lusheng - I will provide a more detailed spreadsheet.  I received the information last night.
      5. Jinri - Back to the software license.  There was a discussion around applicable law.  applicable law will be in the U.S.   We will request to change the applicable law to Germany.
         1. Jack - I may be biased.  It is best to do this through email.  On legal matters I don't want to mis-speak.  Please send request through email.
         2. Out of the seed code projects that are here it doesn't say what licenses we are under.  
            1. Radisys will use O-RAN, Intel has both, China Mobile has O-RAN.
   4. Action  user-d3360 will follow up with Phil's backup regarding the CLA because China Mobile is ready to contribute code.
      1. Jack - Phil do you have a CLA platform for the contributor agreement. 
         1. Phil - Yes, we have a tool for the O-RAN Alliance side will be implemented there.  TOC do you want to have a CLA on the Apache 2? It is optional.  
            1. Jack - Should we use the CLA for the open source software community project as well.  This way you will have a record of who signed up for which open source community or O-RAN specification.  I don't know how many have dual licenses?  Phil - we are in new territory.  Jack - I think it is better to sign one or the other instead of both.  We'll put the thought process in place and we will know signed for one and not the other.  Phil - Agreed.
            2. Any questions or concerns?  The CLA content does exist.  Action/Jack send out the CLA to the list.  Stefan published it ahead of the EC meeting to approve.  
   5. Action / user-59b16from AT&T is coordinating the Requirements and Software sub-committee meetings.
      1. Working document under the Contributions link.
         1. Intel, Samsung attended.  The meeting was recorded and will be loaded into the wiki meetings page.  Post your comments on the Contributions page.
         2. Jinri - Did any co-chairs from the O-RAN Alliance attend the meeting?
            1. No.  It was not a European friendly time slot.  Internally WG1, 2, and 6 were socialized and we got some feedback.
   6. Action / user-59b16invite all the WG chairs to the Requirements and Software Architecture meetings.  One of the principles of TOC is to align the WGs.
      1. Jinri - I sent an email to the working group chairs.  I am not sure how many working group members were invited.  Action / Jinri send out the invitation to remind the co-chairs about Rittwik's meeting.
   7. Action/ Jun Hyuk Song Send out the corrections you made to the A release requirements document to the reflector (toc@lists.o-ran-sc.org).
      1. He was on the call last night and gave a lot of feedback.
   8. Action / Farheen Cefalu update next weeks meeting to two hours.
2. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. M0 will not be a traditional milestone because we didn't have enough prep time.  M0 will be compressed.  This requirements document should be pretty mature by the time we reach M0.  Look at Rittwik's document.  A lot of epics are in there.  We will be compressed in M1 but will work through those requirements.  The Software Committees job is to go through the epics and put them in jira.
   2. Lusheng - Setting up a Jira for the project is able to set up pretty quickly.  Maybe a couple days.
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

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

   1. Jinri - Add Face to Face discussion 
   2. Vincent - Recommending to end times as scheduled.
   3. Lusheng - Approval from the TOC to accept Seed Code contribution.
   4. Jack - Proposing a project list for the "A" release discussion
4. Planning for Next Meeting
5. Open Discussion
6. Any Other Business (AOB)
7. Meeting Summary (resolutions, new action items, etc.)

2019 05 29

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

Audio only

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

2. Review of Today's Agenda
3. Status of Open Action Items (Old Business)
   1. Action / user-2057e put out a poll to select a fish and which fish name for release A.  Try not to pick a complicated name.
   2. Action / user-d3360  - I will provide a more detailed spreadsheet to Farheen.  I received more information last night.
   3. Action / Jack send out the CLA to the list.  Stefan published it ahead of the EC meeting to approve.  
   4. Action / Jinri Huang Jinri send out the invitation to remind the co-chairs about Rittwik's meeting
   5. Action / Farheen Cefalu Farheen  update the time on the F2F.  Morning 8:30AM - noon Tokyo Japanese time.  This will make is easier for the U.S. to join.  
   6. Action / Farheen Cefalu Farheen For the F2F use the zoom meeting bridge for people to join remotely and post on the wiki.
   7. Action / user-59b16 will prepare something for the face to face meeting with TOC WG3
   8. Action / user-d3360 work with Phil offline regarding setting up subcommittees under an umbrella project and do the approval through email.
   9. Action/ Jack Bring a proposal to approve a list of projects.
4. 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. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

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

2019 06 05

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
   China Mobile	Jinri Huang Co-Chair	x
   Deutsche Telekom	David Streibl	x
   NTT DOCOMO	Toshiro Kawahara	x
   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 corrections. On motion made by David Streibl and seconded by Jinri the minutes of the June 29, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
4. Review of Today's Agenda
   1. Jinri - Add Face to Face discussion 
   2. Vincent - Recommending to end times as scheduled.
   3. Lusheng - Approval from the TOC to accept Seed Code contribution.
   4. Jack - Proposing a project list for the "A" release discussion
5. Status of Open Action Items (Old Business) 
   1. Action / TOC take a vote on the Near Real Time RIC project proposal sent by Tapio Tallgren. 
      1. Scope would not include the RAN or ONAP except for testing purposes.  Our proposal is to have our project technical leader for the project.
      2. Jinri - we need a synchronization meeting once a month with WG3.  
         1. Vincent - Noting that this is not specific to this proposal.  We will have the same thing to consider for future projects.  We need to have the right tools in place here as we are doing in the Alliance.  We have to start somewhere so we have to be careful not to put too many barriers to what we want to do.  I think it is good to start the work.  Nokia has agreed to align with WG3. 
            1. Jinri - I don't want to hinder progress.  I want to make it crystal clear that we want to have this mechanism in place prior to starting to work.
               1. David S.  I agree with Vince.  It should be an important topic for the Tokyo meeting.
                  1. Jinri - it is on the agenda for the f2f.
                     1. Jack -  We have to have the discussions about whether the WG is tightly aligned with their work or more flexible. A lot of the non functional requirements are not in the domain of the work group in general and we have to work on the Alliance side to find out who will be working on those activities.  Yes, that is a part of this A release cycle.  I think it is important to work through that process.  It's probably more around requirements the PTL and the epic responsibilities.  To make them successful we have to support them.
                        1. David - We also need the synchronization between the requirements committee and the working groups.  I suggested to Claudio of WG3 was to join the calls of the requirements committee.  We need to create the space for the collaboration early on so everyone knows whats happening on all sides.
                        2. Vincent - this is an important discussion and we need to find the right balance between process and encouraging contributions.  If our process is too heavy we will not have contributions.  Keep subcommittees to a minimum.  We need a balance.  Because this is release A we are at the start and should encourage the work.  For now the lightweight ad-hoc process is fine.  It is good to add it to the agenda to the next meeting.  We can look at a long term framework not in release A but the future.  To summarize we should start with something simple.  Let's make sure we are addressing the question but we are keeping it simple. 
                           1. Jack I agree.  keep it simple move quickly and iterate.  It is the responsibility of TOC is oversight.  Votes are not permanent.  We can change in the future according to projects ability to grow.
                  2. Phil - Projects are around repos and the projects go hand in hand.  Is this on the Apache side or the O-RAN Alliance side?
                     1. I suggest we do this using a template for the process to create a project.  This template should bring up which license is being used.
                        1. Tapio this is under the Apache license.
                     2. Jack -  Is it the project or the repo that is defined by the license.
                        1. Phil - You can have two licenses in a repo but does the committer of the project want two licenses?  We want to make it clear up front when creating a project.  It's a question for the TOC.  
                        2. Jack - This is for Apache.  We're going to take it incrementally with projects first.  then PTL, then committers.
                        3. Phil - Tapio provided the list of committers who will have commit rights.
      3. The new NRT-RIC project and committers for the O-RAN SC was reviewed . On motion made by Vincent and seconded by David creating the Near Real time RIC project was approved by the TOC members. 
         1. VOTE: Vote taken, item passed.
      4. PTL role for the first Near Real Time RIC project.  Jack - I am in favor of the TOC voting for the PTL role.
         1. We have a proposal that Thoraf Czichy as the PTL.  Check Thoraf's Linked In profile.
      5. Make Thoralf the PTL for the Near Real Time RIC project. On motion made by Jack and seconded by David making Thoralf the PTL for Near Real Time RIC project was approved by the TOC members. 
         1. VOTE: Vote taken, item passed.

1. 1. Action / Jinri Huang send a reflector to highlight O-RAN members to attend the Shanghai O-RAN Alliance meeting following the Tokyo meeting.
   2. Action/ user-2057e send out a poll for a color that begins with "a" for the A release.
      1. Holding because the wiki had a conflict.  Action/David put out a poll to select a fish and which fish name for release A.  Try not to pick a complicated name.
   3. Action / user-d3360 will make a request over the email chain about the June 5th deadline.  There is an interest from Intel, Radisys, Inspur, China Mobile to contribute seed code and they will need the O-RAN licenses in standard plain text.
      1. Charter for the O-RAN specification project has been finalized and approved by the O-RAN legal team and this has been run by Scott.  There is a charter a license and a contributors agreement that needs to be signed and associated with that project.  Stefan has prepared the documents in PDF form and will be distributed for the EC tomorrow at Thursday.  We have to make sure it gets distributed to EC members.  Jinri - Yes he has notified the EC members.  The O-RAN license will be available after the Thursday's meeting.
      2. Lusheng - From a software seed code perspective can we also claim a license claim text?  It is legal language and need help with O-RAN.
      3. Seed code request was unable to do through email.  I will make the request later on this call for other repos that are ready for creation.
      4. Action / Lusheng - I will provide a more detailed spreadsheet.  I received the information last night.
      5. Jinri - Back to the software license.  There was a discussion around applicable law.  applicable law will be in the U.S.   We will request to change the applicable law to Germany.
         1. Jack - I may be biased.  It is best to do this through email.  On legal matters I don't want to mis-speak.  Please send request through email.
         2. Out of the seed code projects that are here it doesn't say what licenses we are under.  
            1. Radisys will use O-RAN, Intel has both, China Mobile has O-RAN.
   4. Action  user-d3360 will follow up with Phil's backup regarding the CLA because China Mobile is ready to contribute code.
      1. Jack - Phil do you have a CLA platform for the contributor agreement. 
         1. Phil - Yes, we have a tool for the O-RAN Alliance side will be implemented there.  TOC do you want to have a CLA on the Apache 2? It is optional.  
            1. Jack - Should we use the CLA for the open source software community project as well.  This way you will have a record of who signed up for which open source community or O-RAN specification.  I don't know how many have dual licenses?  Phil - we are in new territory.  Jack - I think it is better to sign one or the other instead of both.  We'll put the thought process in place and we will know signed for one and not the other.  Phil - Agreed.
            2. Any questions or concerns?  The CLA content does exist.  Action/Jack send out the CLA to the list.  Stefan published it ahead of the EC meeting to approve.  
   5. Action / user-59b16from AT&T is coordinating the Requirements and Software sub-committee meetings.
      1. Working document under the Contributions link.
         1. Intel, Samsung attended.  The meeting was recorded and will be loaded into the wiki meetings page.  Post your comments on the Contributions page.
         2. Jinri - Did any co-chairs from the O-RAN Alliance attend the meeting?
            1. No.  It was not a European friendly time slot.  Internally WG1, 2, and 6 were socialized and we got some feedback.
   6. Action / user-59b16invite all the WG chairs to the Requirements and Software Architecture meetings.  One of the principles of TOC is to align the WGs.
      1. Jinri - I sent an email to the working group chairs.  I am not sure how many working group members were invited.  Action / Jinri send out the invitation to remind the co-chairs about Rittwik's meeting.
   7. Action/ Jun Hyuk Song Send out the corrections you made to the A release requirements document to the reflector (toc@lists.o-ran-sc.org).
      1. He was on the call last night and gave a lot of feedback.
   8. Action / Farheen Cefalu update next weeks meeting to two hours.
2. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. M0 will not be a traditional milestone because we didn't have enough prep time.  M0 will be compressed.  This requirements document should be pretty mature by the time we reach M0.  Look at Rittwik's document.  A lot of epics are in there.  We will be compressed in M1 but will work through those requirements.  The Software Committees job is to go through the epics and put them in jira.
   2. Lusheng - Setting up a Jira for the project is able to set up pretty quickly.  Maybe a couple days.
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

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

   1. Jinri - Add Face to Face discussion Jinri, Toshiro, Vincent will send Chris Endular? from Orange, Vincent will send someone from Verizon O-RAN side.  KJ will be there from AT&T.  
      1. Reviewed Jinri's powerpoint. 
      2. Action/Farheen  update the time on the F2F.  Morning 8:30AM - noon Tokyo Japanese time.  This will make is easier for the U.S. to join.  
      3. This is our first face to face meeting to increase the visibility of the software community.  The channel is not good.  I would like to take this opportunity to improve the channel.
      4. Finalize the Software document.  This will be a key focus in our face to face meeting.  
         1. Software document is the architecture and requirements documents.
         2. Peter Moonki Hong - Is this only for O-RAN members?  No this is open to everyone.  For the face to face 99% are O-RAN members. Is registration required?  No registration needed.  We should put up the remote access on the wiki.  It's open to attend remotely.  We need clarification on times.  Action / Farheen For the F2F use the zoom meeting bridge for people to join remotely and post on the wiki.
         3. Agenda item 7.  The purpose is to give an introduction to the whole audience.
         4. I would like to invite TOC-WG3 to joint session.  We will need Rittwik or someone else prepare an introduction.
            1. Will someone from Nokia be there?  Yes.  Action/Rittwik will prepare something for the face to face meeting with TOC WG3
            2. WG8 is about to publish their software architecture and their API interface requirements specification.  
            3. Is Rittwik OK with 2 hours.
   2. Vincent - Recommending to end times as scheduled.
   3. Lusheng - Approval from the TOC to accept Seed Code contribution.
      1. Lusheng sharing seed code contribution list.  
         1. Inspur related to infrastructure platform.
         2. Redisys we provided the committer names and contact.  The original name Radisys 5G is not good for open source.  Will talk to them later today.
         3. Will finalize Measurement campaign and machine learning apps.  
         4. UE Manager 
         5. Configure Radio Network Information Base. We have the RIC platform as a newly formed project.  I will talk to Thoralf later.  Action/Lusheng send to Farheen to include in the minutes.
         6. Viswa - Approval is for seed code only?  yes.  This is a seed code acceptance not new projects, correct?
         7. Are these these the new committers.  Phil - It would be strange to have a project that has multiple committers. Have an umbrella project with sub projects.  Each sub-project with different committers.  Lusheng - yes, we can do that.  Phil - The folks on the IT side only see repos.  You want command and control.  The committers are overseeing the code contributions within a repo.  Whether we map each repo to a subproject has not been addressed.  
            1. Jack - We're gathering seed code and our next step is to map that to projects.  We don't know how to map it until everyone can see it.
               1. Phil The code that's in the RIC platform do you need to have an understanding of how all the pieces fit?  If no then have sub-projects.  If yes, then sub-projects across all projects.  
               2. Radisys, Nokia, and AT&T are contributed.  But right now to get their code in we need to evaluate to make into a project.  Right now it is specified by the companies who are contributing.  
               3. Phil - What level of access do you need with this code.  What are you planning on doing with this code during the evaluation phase?  
                  1. General audience is mostly looking at it.  
               4. Phil - how much effort do we expect to go through?
               5. Lusheng - Inspur, Radisys have deadlines.  Action /Lusheng work with Phil offline and do the approval through email.
   4. Jack - Proposing a project list for the "A" release discussion
      1. We approved the near real time RIC but there are a list of projects that have to be addressed.  OCU, DCU.  I'd like to create the project so we can create the Jira entries for them so we can start working the release.  Without being able to put the projects in the project tab we are unable to begin.  It's important that we create the projects as the intent of what we intend to fill out.  Action/ Jack Bring a proposal to approve a list of projects.  It is attached to the requirements document.  I'll share that on a spreadsheet and we'll talk aobut.
         1. Focus on the rest of the projects
         2. Requirements document 
         3. Epics
4. Call for Scribe (minutes owner) Farheen Cefalu

Roll Call and 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

Toshiro Kawahara

xOrange

Vincent Danno

x

Verizon

Viswa Kumar

x
5. Review and Agree to Minutes of Previous Meetings
   1. The minutes of the prior meeting were reviewed, and there were no corrections. On motion made by David Streibl and seconded by Vincent the minutes of the May 22, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
6. Review of Today's Agenda
   • Action / Jinri send a reflector to highlight O-RAN members to attend the Shanghai f2f meeting.
   • What other projects we need to open to kick off our A release.  
   • Add descriptions of repos.
Status of Open Action Items (Old Business)
7. Action Farheen remove Registration and Visa letter from Tokyo face to face.
8. Action David Streibl send a note to the community about the color naming convention.
   1. If anyone has other naming conventions other than colors update the wiki page.
   2. How do we decide the name like a poll on the wiki?
   3. Posting a poll is acceptable and anyone and everyone can vote on the poll.
   4. If we don't have any other options we'll use color.  Action/ user-2057e put a poll for a color for the A release.

Action Lusheng share repo changes and committers spreadsheet with Farheen to attach to these minutes.  Repo and committer changes request on today's ToC call.eml.  June 5th is the deadline for seed code contributions. 

Action / user-d3360  will make a request over the email chain about June 5th deadline.  Maybe half a dozen to one dozen repos are interested.  Intel, Radisys, Inspur, China Mobile has seed code ready to contribute and they will need the O-RAN licenses in standard plain text.  Phil said he wants to get the Contributors License (CLA).  Phil is out of office this week returning June 4th.  Action  user-d3360 will follow up with Phil's backup.  Action / user-d3360  contact user-59b16 about making a change to the matrix below.

New Repos and Committers

Repo

Description

Committer Name

Email

it/dev

Various development support tools and artifacts

Lusheng Ji

lji@research.att.com

Daved Korman

dk3239@att.com

Chris Lott

cl778h@att.com

Zhe Huang

zhehuang@research.att.com

ric-plt/xapp-frame

artifacts for the (near realtime) RIC xapp framework, including common libararies, etc

Abukar Mohamed

abukar.mohamed@nokia.com

Juha Hyttinen

juha.hyttinen@nokia.com

Antti Puhakka

antti.puhakka@nokia.com

com/golog

Golang implementation of the common logging library

Katri Turunen

katri.turunen@nokia.com

Roni Riska

roni.riska@nokia.com

Heikk Ahola

heikki.ahola@nokia.com

ric-plt/utils

Utilities and common configurations for the (near realtime) RIC Platform

Matti Hiltunen

hiltunen@research.att.com

Tommy Carpenter

tommy@research.att.com

Lusheng Ji

lji@research.att.com

ric-plt/submgr

(near-realtime) RIC Platform Subscription Manager

Peter Szilagyi

peter.3.szilagyi@nokia.com

Kalman Nagy

kalman.nagy@nokia.com

Bálint Üveges

balint.uveges@nokia.com

Viktor Bekesi

viktor.bekesi@nokia.com

Update existing Repo's committers

Repo

Action

Name

Email

ric-plt/a1

Add

Tommy Carpenter

tommy@research.att.com

Scott Daniels

daniels@research.att.com

Chris Lott

 cl778h@att.com

ric-plt/lib/rmr

Add

Tommy Carpenter

tommy@research.att.com

Gueyoung Jung

gjung@research.att.com

ric-app/admin

Delete

Varun Gupta

vgupta@research.att.com

Add

Raja Sivaraj

rs405h@att.com

ric-plt/dbaas

Add

Arvo Heinonen

arvo.heinonen@nokia.com

(Lusheng update:  LF helpdesk tickets: #75906 and #75705)

9. Action Lusheng provide gerret repo descriptions to LF technical team.
   1. In Progress for new seed code contributors.
10. Action Farheen Send out a reminder to the TOC to take a vote on finalizing the release calendar.  
11. The A Release schedule was reviewed, and there were no corrections. On motion made by Jack and seconded by Vincent the "A" release schedule was approved by the TOC members. 
    1. VOTE: Vote taken, item passed.
12. 1. Jinri - Who is organizing the discussion for the epics?  
       1. The epics will be driven by the Requirements and Architecture subcommittee.
          1. Action / user-59b16from AT&T is coordinating the Requirements and Software sub-committee meetings.
       2. Are there software architecture meetings?  
          1. Next week we will formerly kickoff  one in the evening time in NYC and one is in the morning NYC time.
          2. Jinri - We need to inform Working Groups.  David agrees.  We need to work out how we are going to work with the Alliance.  For example with RIC WG 3, and 2 have to know what is going on in the requirements.
             1. Jinri and Jack are socializing how to leverage WG1 as an interface.  It's going to be hard to build interfaces with every WG.  Could we leverage WG1 as an interface to the broader WG community.
             2. Jinri - Action/Rittwik or Jinri invite all the WG chairs to the Requirements and Software Architecture meetings.  One of the principles of TOC is to align the WGs.  
             3. Viswa - I don't understand. I thought this was already aligned.
                1. Jinri - It is hosted by LF and TOC has to report to the O-RAN community.
                2. Gian Michele Dell'Aera (TIM) please have them sign up asap.
                3. Jack - Many of the software decisions will bubble up to a very terse line.  Key is E1, and E2 specifications.  There will be another package that will provide guidelines.  We will eventually consolidate on the key types like E2 or radio resource management.  There is a lot of other work that won't be pressing such as OA&M  functions.  The things that you need to make the software solution but don't get feature attention.
                4. Viswa - I have added a series of questions.  I find it hard to find via wiki.  
                   1. Have you seen the requirements document yet? 
                      1. No
                      2. We have it posted on the wiki https://wiki.o-ran-sc.org/display/RSAC
                      3. Rittwik will be leading setting up the calls and notifying users.  Lusheng is gathering code contributed by different people and uploaded to gerret.  Seed code has not been approved to be a part of the project.  This code is available to move into the official project for our A release.  In the weeks ahead we will have discussions over whether or not to move the seed code.
                      4. In O-RAN WG8.  How is that different than what we are trying to do here?
                         1. We've had discussions.  WG8 will not generate code.  The emphasis there is more on CU, RU, DU layers than the non RT RIC.  Code will come from O-RAN SC.
                         2. Requiremets & Software Architecture will cover post CU and post DU.
                         3. Jinri - concerned about day after tomorrow we have a TSC call.  Typically in O-RAN Alliance there are three big events.  They usually want to release during these events.  Is it possible to get this completed by NWC North America in September time frame?  
                            1. You can look at the schedule and there is no way to put this in September time frame.  Looking at the schedule this gives us a short development schedule.  We can try to align with Barcelona.  This schedule tends to be the pattern that works.  The original goal was to try to have an impact this year.
                         4. Jun Song (Samsung) We found mistakes on the requirements document.  You can post the document back on the reflector.  Action/Jun Send out the corrections to the reflector.
13. Action David Tallgren send the proposal to the mail list.  There is a proposal to make the RIC a project in gerret.  RAN Intelligent Controller (RIC) under the Apache2 license.
    1. David proposed making RIC a project.  The TOC has the right to create sub-projects in the TOC.  The proposal is to make RIC into an official project.  We have the people from Nokia as proposers for the projects. Sharing official proposal deck.  Scope is this Near RT RIC as a part of release A as the timeline that was accepted.  Nokia will start development work as soon as it's approved.  Hosted in the Akraino REC platform.  We would like to have a gerret repo, jira, wiki space, host a weekly zoom meeting, #RIC, and slack channel.  Nokia has a bunch of committers.  We are proposing  Thoralf Czichy (Nokia) be PTL of the RIC project.   
       1. Could you touch on xApp framework?
          1. The plan is there is at least one demo xapp as part of the RIC project but the actual x-apps are not a part of this effort.
          2. Peter Moonki Hong (Samsung) asked Is this separate development? 
             1. No the main development will transition the seed code to the project and the code would be classified as the project code where the community can move to near RTRIC.  AT&T has been very involved with Nokia.  AT&T has a number of developers also working into the seed repository.  This is a proposal from Nokia and AT&T is very active in this along with the WGs for the requirements and specifications.  The difference with the x-apps will be creating a separate project for the xapp development which will depend on near RTRIC platform and framework.  x-apps will be less about framework and more about RAN.  It will be under a separate Apache license.  
          3. Post questions to the reflector and we will work on getting a wiki page set up.
       2. Action/TOC take a vote on the RIC project.
14. Action Jack will talk to TOC about extending the TOC call to 90 minutes as opposed to 60 minutes.
    1. We will shoot for 2 hours next week.  We will spend more time talking about requirements and the proposal for projects.  We will have a repo structure as a part of the architecture.  We are struggling with getting the O-RAN license approved. My opinion is take DU, there is a lot of implementation of code that people want to do under the O-RAN licensing.  I recommend we create an Apache and O-RAN repo to that project.  This way the framework may not involve the O-RAN licensence.  That way it can be an upstream feed to the O-RAN license and be a complete build.  People should give feedback.  This will allow anyone who wants to know what has been contributed under Apache or O-RAN license.  Action / Farheen update next weeks meeting to two hours.
15. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Releases
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

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

    1. Jinri - The week following the Tokyo meeting there will be an O-RAN Symposium June 25 whole day in Shanghai.  It is open to everyone and I encourage everyone to add to the event.  Next week will run this meeting for two hours.  We will start talking about Epics.  So start to think about the epics in the "A" Release.  We will take a poll on naming the releases and we will move forward.
17. Planning for Next Meeting
18. Open Discussion
19. Any Other Business (AOB)
20. Meeting Summary (resolutions, new action items, etc.)
    1. The A Release schedule was reviewed, and there were no corrections. On motion made by Jack and seconded by Vincent the "A" release schedule was approved by the TOC members. 
       1. VOTE: Vote taken, item passed.
    2. The minutes of the prior meeting were reviewed, and there were no corrections. On motion made by David Streibl and seconded by Vincent the minutes of the May 22, 2019 meeting were the approved by the TOC members. 
       1. VOTE: Vote taken, item passed.
    3. Action/TOC take a vote on the RIC project.
    4. Action / Jinri send a reflector to highlight O-RAN members to attend the Shanghai f2f meeting.
    5. Action/ user-2057e send out a poll for a color that begins with "a" for the A release.
    6. Action / user-d3360 will make a request over the email chain about June 5th deadline.  Maybe half a dozen to one dozen repos are interested.  Intel, Radisys, Inspur, China Mobile has seed code ready to contribute and they will need the O-RAN licenses in standard plain text.
    7. Action  user-d3360 will follow up with Phil's backup regarding the CLA because China Mobile is ready to contribute code.
    8. Action / user-59b16from AT&T is coordinating the Requirements and Software sub-committee meetings.
    9. Action / user-59b16invite all the WG chairs to the Requirements and Software Architecture meetings.  One of the principles of TOC is to align the WGs.
    10. Action/ Jun Hyuk Song Send out the corrections on the requirements document to the reflector toc@lists.o-ran-sc.org.
    11. Action/David put out a poll to select a fish and which fish name for release A.  Try not to pick a complicated name.
    12. Action/Lusheng - I will provide a more detailed spreadsheet to Farheen.  I received more information last night.
    13. Action/Jack send out the CLA to the list.  Stefan published it ahead of the EC meeting to approve.  
    14. Action/Jinri send out the invitation to remind the co-chairs about Rittwik's meeting
    15. Action/Farheen  update the time on the F2F.  Morning 8:30AM - noon Tokyo Japanese time.  This will make is easier for the U.S. to join.  
    16. Action/Farheen For the F2F use the zoom meeting bridge for people to join remotely and post on the wiki.
    17. Action/Rittwik will prepare something for the face to face meeting with TOC WG3
    18. Action /Lusheng work with Phil offline regarding setting up subcommittees under an umbrella project and do the approval through email.
    19. Action/Jack Bring a proposal to approve a list of projects.
    20. The minutes of the prior meeting were reviewed, and there were no corrections. On motion made by David Streibl and seconded by Jinri the minutes of the June 29, 2019 meeting were the approved by the TOC members. 
        1. VOTE: Vote taken, item passed.
    21. The new NRT-RIC project and committers for the O-RAN SC was reviewed . On motion made by Vincent and seconded by David creating the Near Real time RIC project was approved by the TOC members. 
        1. VOTE: Vote taken, item passed.
    22. Make Thoralf the PTL for the Near Real Time RIC project. On motion made by Jack and seconded by David making Thoralf the PTL for Near Real Time RIC project was approved by the TOC members. 
        1. VOTE: Vote taken, item passed
    Action / Farheen Cefalu update next weeks meeting to two hours
    23. 1. .

Return to todays agenda