Technical Charter for O-RAN Software Community

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 07 24

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu (AT&T)

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	Masafumi Masuda	x
   Orange	Vincent Danno	x
   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 no corrections. On motion made by Jinri and seconded by David the minutes of the July 17, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
4. Review of Today's Agenda
   1. Vincent 
5. Status of Open Action Items (Old Business)
   1. Action/ user-2057e - provide an update of Release "A" name. 
   2. Action/ Farheen Cefalu - link Poll to vote and explain how the team can take Polls.
   3. Action / John Murray CLA status.
      1. ORAN has approved the license charter and CLA for ORAN Specification code project.  Jinri and Jack are working on setting up a website to link to it.  Working with ORAN Alliance to create an introduction, charter, and license will be available as read only.  On this side we can make sure that our repositories are leveraging the licenses properly.
         1. Tristan - We have the platform they need to set up the signed CLAs.  
      2. It opens up the ability to do work with the license.  The contributors can start contributing.
         1. Tristan - we won't hold up the development process.  
      3. Assuming Stefan is on vacation.
         1. Jinri - Hank briefed the voting status on the board.  We had 15 board members.  We got 8 from them.  EC approved all the documents.  They are delayed by a few days because they are still collecting votes.  I believe Stefan will send the document they want to you.
   4. Action/ John Murray will provide a contact from WG8 to David Kinsey 
   5. Action/ Vincent Danno discuss the email about who wants to participate at ONS Europe and how best to represent the ORAN software community space there.
      1. Vincent - Not participation but more about planning the demos.  There has been some reaction to my email.  There will be one Orange Phillppe will have a demo.
      2. Are we going to have demos?  The deadline for presentations has passed but is there a deadline for the demo.
         1. Vincent - Not sure if LF agreed to pass the deadline for the demos.  
            1. Jinri - W4 demos will be there.  ORAN Alliance demos will be there.  
               1. Vincent - We are not planning a demo it will be a key note.
               2. Action/ Jinri Huang Check with the co-chairs regarding a demo.  I will need more information about the demo.
                  1. The deadline is July 31, 2019.  There is still time to submit a demo.
   6. Action/ Jinri Huang come up with a naming convention to differentiate the Near real time RIC with the Non real time RIC that prevents the duplication of the short name (KEY) NRTRIC in LF Jira and Confluence.  Jira/Confluence do not support mixed case keys.  Keys are all upper case.
      1. Thank you Lusheng for supporting the naming convention.  
         1. In the meeting minutes we should use the name defined by the Alliance in their White paper.  
         2. Reference Jiniri's reflector.

            1. Here is my proposal.

               1, for most occasions such as in the meeting minute, in the Release A epic document where there is no constraint on the naming, the name defined in O-RAN Alliance White Paper shall be used, which are:
               non-realtime RIC, abbreviated as, Non-RT RIC, or NRT RIC;
               near-realtime RIC, abbreviated as, near-RT RIC, or nRT RIC; // note, it it is about the platform, then the word “platform” should be explicitly spelled out.

               2, For project name and the corresponding project key, as shown here at https://wiki.o-ran-sc.org/display/ORAN/Projects, proposal is:

               "Non-realtime RIC (or Non-RT RIC, or NRT RIC) as the project name, with project key as “NRTRIC"
               "Near-reamtime RIC platform (or near-RT RIC platform, or nRT RIC platform) as the project name, with project key as “RICPLF"

               3, For repo name which requires lower case, digits, slash and dash, suggest to use “non-rt-ric” and “nrt-ric-plf” for Non-RT RIC and near-RT RIC platform, respectively.

               1. Lusheng - Can we keep the existing defined names for the repos?  We agreed to the naming convention in the past.  This is an amendment to the June 12th naming.
                  1. Jinri - I am OK with that.
                  2. Action/ user-d3360 talk to the Near real time RIC regarding the naming of the existing.
               2. John - suggested to use No-real time RIC.  We need a to set up the accounts for gerret.  I suggest No-rtRIC for Non real time RIC.  NRTRIC is causing confusion.  NONRTRIC for Non real time RIC.  
               3.  John Keeney I propose for the Project KEY NONRTRIC.  I am most concerned about the short names for Jira and gerret.  For that let us call NRTRIC and NONRTRIC.
                  1. Lusheng - Jira is more strict.
                  2. John Keeney made a motion, Jinri seconded the vote
                     1. VOTE: Vote taken, item passed.
   7. Discussion on alignment between Non-realtine RIC and OAM projects. 

      Non-realtime RIC focus on feature functionality of A1-interface (consumer and provider), and closed-loop use cases.
      OAM focus on align of O1 interfaces on ME and verification of related interface specifications.
      Both projects will align activities on a case-by-case based for O1 interfaces (NetConf client ODL, and http-Server – ves-receiver from DCAE).
      Current ONAP baseline should be Dublin for Release A

6. Standing Agenda Items (Brief Status of Ongoing Activities)

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Release planning link
2. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non Real Time RIC

3. Test & Integration Planning - Lusheng

4. Report Out of Sub-Committees
   1. Requirements Software Architecture Committee - Rittwik

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

   1. Intel and Radisys agreed to have Zhimin Yuan be the PTL and Sachin Srivastava as Co-PTL of the O-DU project. Zhimin and Sachin will coordinate on the O-DU project management going forward.
   2. CMCC would like to nominate Weichen Ni for PTL of INF project
   3. CMCC would like to nominate Yingying Wang for PTL of O-CU project
   4. Remaining open PTL positions   Documentation, Simulator, O-RU
   5. Vincent - Talk about the new reflector.
   6. Creation of repo questions
8. Any Other Business (AOB)
9. Meeting Summary (resolutions, new action items, etc.)

2019 07 17

zoom meeting: 2019-07-17-toc.mp4

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu (AT&T)

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	Masafumi Masuda	x
   Orange	Vincent Danno	x
   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 no corrections. On motion made by David and seconded by Vincent the minutes of the July 10, 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/ user-2057e - update the access for the poll so Jinri can vote on the release name. 
      1. Polls are not visible if you are not logged in.  An LF account is needed.
      2. Colors are winning.  
   2. Action/ user-2057e - provide an update of Release "A" name. 
   3. Action / John Murray CLA status.
      1. Jack - Exchanged email with Tristan.  There is work to get the LF work set up.  I am talking to the PM on the ORAN Alliance side.  The ORAN charter and license will be hosted on ORAN Alliance site referenced from this site.  I have not yet received final approval for the license from the board.  I will reach out to the leadership.
   4. Action / John Keeney send out a proposal to the TOC email list for the non real time RIC proposal from Ericsson.   John Keeney is based out of Ireland.
   5. Action / TOC - Vote for non realtime RIC PTL change and consider High Street for the OAM Project PTL
      1. Proposal submitted from Martin Skorupski from High Street.  A Berlin software company. 
      2. Proposal change for Ericsson to lead non real-tine RIC Project PTL
      3. We received two PTL proposal.
         1. John Keeney for Non real time RIC.
            1. John - In terms of NrtRIC and OAM scoping will be a challenge.  Both rely on A1 interfaces.
         2. Martin Skorupski for OA&M
            1. Martin - there is some overlap we need to minimize the overlap by working together.  
               1. When will you define the scope between the two?
                  1. John and Martin will have their first discussion this week to define the scope.  It has not been discussed yet.
                  2. Action/ John Keeney Martin Skorupski define the scope of the projects.
      4. Proposal to place Martin Skorupski  as PTL for OA&M. On motion made by Jack and seconded by David.  Martin Skorupski was approved by the TOC members for the OA&M project. 
         1. VOTE: Vote taken, item passed.
      5. Proposal to place John Keeney as Non real time RIC PTL.  On motion made by Jack and seconded by David.  John Keeney was approved by the TOC members as the PTL for the Non real time RIC project. 
         1. VOTE: Vote taken, item passed.
   6. Action/ John Murray will provide a contact from WG8 to David Kinsey 
   7. Action/ Vincent Danno start an email discussion about who wants to participate at ONS Europe and how best to represent the ORAN software community space there.
      1. Vincent - I was late to start the discussion.  It has been started.
         1. Is there a deadline?
            1. There is a deadline for submission to the LF for talks or demos.  The deadline has passed.  We have to coordinate amongst ourselves to support the conference.
   8. Action/ Jinri Huang come up with a naming convention to differentiate the Near real time RIC with the Non real time RIC that prevents the duplication of the short name (KEY) NRTRIC in LF Jira and Confluence.  Jira/Confluence do not support mixed case keys.  Keys are all upper case.
   9. Action/ David Kinsey start populating the Projects page on the wiki to describe projects.
      1. Rittwik - How do we proceed without a PTL on the project? We have epics that need to be worked.
         1. we may need to recruit temporary PTLs.  Not ideal but we need PTLs in order to proceed.
6. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Release planning link
      1. Jack has updated the page.  Aligned the calendar with the working groups.  The current timeline we are in week 17 getting ready to start dev sprint 1.  The projects that are in place can participate in the dev1 sprint.  A lot of what's going to happen in this release is seed code.  We still have to discuss if we want to change the schedule.  Stick to the schedule and deliver.  I've added another row at the bottom of the calendar to map the connection points of the overall schedule.  We want to make sure we meet with the working groups.  The schedule reflects the reviews with the working groups.  After two development sprints we can come back to the working groups and give them a demo of the second sprint.  Once we complete all the dev. sprints and have something working we will review with ORAN at the end of the cycle.  
         1. Rittwik - It will be good to align with the face to face meetings.  Can we do the demonstrations (demos).  
            1. The face to face meetings are not currently aligned.  
         2. These are the alignments that best fit with the software process.  I have come up with a first draft of "B" release and the dates.  This is a proposal.  There is a break in the calendar from December 21 -January 6.  Most of the groups are unavailable during this time.  Let me know if there are other dates that the team needs to manage.
         3. Action/ TOC Review, refine the calendars
            1. Chinese new year?  
               1. Yes, that is the feedback I am looking for.  We will follow what the community wants to do.  We can't do too many but want to make it fair.
2. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non Real Time RIC

3. Test & Integration Planning - Lusheng

4. Report Out of Sub-Committees
   1. Requirements Software Architecture Committee - Rittwik

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

   1. Jinri Huang is concerned that there has not bee enough discussion around the PTL selection.
      1. Both Martin and David agreed to work out the scope of their projects amongst themselves.   
8. Any Other Business (AOB)
9. Meeting Summary (resolutions, new action items, etc.)
   1. Votes
      1. The minutes of the prior meeting were reviewed, and there were no corrections. On motion made by David and seconded by Vincent the minutes of the July 10, 2019 meeting were the approved by the TOC members. 
         1. VOTE: Vote taken, item passed.
      2. Proposal to place Martin Skorupski of HighStreet as PTL for OA&M. On motion made by John Murray  and seconded by user-2057e .  Martin Skorupski was approved by the TOC members for the OA&M project. 
         1. VOTE: Vote taken, item passed.
      3. Proposal to place John Keeney as Non real time RIC PTL.  On motion made by John Murray and seconded by user-2057e .  John Keeney was approved by the TOC members as the PTL for the Non real time RIC project. 
         1. VOTE: Vote taken, item passed.
   2. Actions
      1. Action/ user-2057e - provide an update of Release "A" name. 
      2. Action / John Murray CLA status.
      3. Action/ John Murray will provide a contact from WG8 to David Kinsey 
      4. Action/ Vincent Danno status of the email discussion about who wants to participate at ONS Europe and how best to represent the ORAN software community space there.
      5. Action/ Jinri Huang come up with a naming convention to differentiate the Near real time RIC with the Non real time RIC that prevents the duplication of the short name (KEY) NRTRIC in LF Jira and Confluence.  Jira/Confluence do not support mixed case keys.  Keys are all upper case.

Back to Todays Agenda

2019 07 31

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu (AT&T)

2. Roll Call & Quorum 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	Masafumi Masuda
   Orange	Vincent Danno
   Verizon	Viswa Kumar

   *Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quoram and can vote on activities.  

3. Review and Agree to Minutes of Previous Meeting
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
   1. Action/ user-2057e - provide an update of Release "A" name. 
   2. Action / John Murray CLA status.
   3. Action/ John Murray will provide a contact from WG8 to David Kinsey 
   4. Action/ Vincent Danno discuss the email about who wants to participate at ONS Europe and how best to represent the ORAN software community space there.
   5. Action/ Jinri Huang come up with a naming convention to differentiate the Near real time RIC with the Non real time RIC that prevents the duplication of the short name (KEY) NRTRIC in LF Jira and Confluence.  Jira/Confluence do not support mixed case keys.  Keys are all upper case.
   6. Discussion on alignment between Non-realtine RIC and OAM projects. 

      Non-realtime RIC focus on feature functionality of A1-interface (consumer and provider), and closed-loop use cases.
      OAM focus on align of O1 interfaces on ME and verification of related interface specifications.
      Both projects will align activities on a case-by-case based for O1 interfaces (NetConf client ODL, and http-Server – ves-receiver from DCAE).
      Current ONAP baseline should be Dublin for Release A

6. Standing Agenda Items (Brief Status of Ongoing Activities)

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Release planning link
2. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non Real Time RIC

3. Test & Integration Planning - Lusheng

4. Report Out of Sub-Committees
   1. Requirements Software Architecture Committee - Rittwik

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

   1. Intel and Radisys agreed to have Zhimin Yuan be the PTL and Sachin Srivastava as Co-PTL of the O-DU project. Zhimin and Sachin will coordinate on the O-DU project management going forward.
   2. CMCC would like to nominate Weichen Ni for PTL of INF project
   3. CMCC would like to nominate Yingying Wang for PTL of O-CU project
   4. Remaining open PTL positions   Documentation, Simulator, O-RU
   5. Candidates for the TOC open seats have to be filled.  This is not a part of this TOC function the ORAN Alliance has to find the candidates.
      1. Vincent - we need to plan a call.
8. Any Other Business (AOB)
9. Meeting Summary (resolutions, new action items, etc.)