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 09 25

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
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Masafumi Masuda	x
   O-RANge	William Diego	x	Vincent Danno
   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
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
   1. Actions: Plugfest 
      1. Tracy Van Brakle to provide writeup next week as base for blog, etc.
         1. Write up is coming your way today.  Formal call for participation from the Test and Integration.  Tracy will include the call for participation.  Moving forward with OSC POC North America and Beijing Plugfests happening in parallel.  There will be a formal readout of this entire effort December 16 and 17.
         2. Jack - We'll add information on the Events page and the base.
      2. John Murray add to the wiki events page.  ToC member 
      3. Jinri Huang to talk to CMCC how to promote at Beijing plugfest
   2. Action/ user-2057e start a poll for B release.
   3. Action/ Thoralf Czichyto send details of which spec, section, version, to John Murray regarding RIC Platform copyrights.
      1. Jack - I saw the 3GPP copyrights.  I have a list and got feedback from Scott Nicolas from LF.  We need to work on permission to replicate.  What's necessary is a license to be copied.  
         1. If we are an upstream project and have to hand off to a down stream project then each down stream project can work with the same (example MIT) license.
         2. 3GPP does not have that option.  We will pursue permission for coverage.  We have to talk to the open source community to get consensus.  3GPP is not familiar with the ETSY process.
   4. Action/ user-59b16 To organize meeting regarding TSC requested AT&T and Nokia to report on misalignments between Near Realtime RIC OSC implementation and WG3
      1. Meeting tomorrow for alignment.  Call out to PTLs.
      2. Updated WG3 regarding E2 directionality.
         1. RIC establishing the E2 nodes connecting to RIC but not bi-directional.  We put a bi-directional code.
         2. We are creating one slide per project.  If PTLs are available tomorrow at 9AM EST they will be able to voice.
         3. Action/ user-59b16 publish the meeting details on the RSAC page regarding WG3 and E2.
         4. Important for the team to use Jira properly.  Jira
   5. Action/ user-d3360to work with LF to get the current listing. Completed:  20190920-oran-audit
   6. user-d3360 SPDX identifier for Apache 2.
      1. John Murray email Trishan de Lanerolle to confirm there is no issue from LF, if no objection I am okay with it.  Bring this back next week.
      2. Action/ user-d3360contact Trishan de Lanerolle
         1. New files 
         2. ORAN software license will not be able to use SPDX.
            1. Jack consistency is the issue.  Rather than have varying policies we should stay with the current non-SPDX path that we're on.  Are there strong feeling to be moving to xPDX in the apache license based repos.
               1. Lusheng - As a developer I support the non-SPDX 
               2. Jack - we will not adopt the SPDX.
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. We are at the beginning of the final dev sprint for our Amber release.
         1. IST - Is the integration team involved in the pairwise testing?
            1. So far for non-Real time.  Lusheng spoke to PTLs.  We have a rough picture of what is coming.  We don't have a detailed plan of what is coming but we don't see any problems with the Integration test plan.  
            2. We need help from other projects for the testing project.  We have a sub team that is building a tool called open testing framework.  We plan to use this for some of the E2E testing flows.  We will need help from other projects.  We need help from ORAN to define the test flows and test cases.
            3. Action/ user-d3360 talk to Jack about which use cases are being covered for the test.
               1. We will need to record a demo of the functional project and share it across the community. 
               2. Jack will look to Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
               3. Lusheng the plan for the demo project is self contained mostly using ONAP.  In the near real time there is a simulator that interacts with the OAM component.  We can contain this flow in the ETE demo.  We can have some north side of A1 release components.
               4. Jack concerned about statements at Plugfest about Amber release deliverables.  We have to figure out what portion of the Plugfest is aligned.  
               5. Jack - I have to put on next weeks agenda to agreeing on the B release start date.  Current ends in November.  Start date is December 2.  I put a gap in for the end of December and Chinese New year due to holidays.  There is a new concept of a maintenance window.  Developers can work consistently through the timeline.  Maintenance windows allows developers to catch up on their Jira issues (defects).
               6. This will be a big discussion item at the F2F. 
   2. Release planning link.
   3. Copyright
      1. Jack will submit the 3GPP.
7. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non real time RIC (RAN Intelligent Controller) - John Keeney
   2. RIC Applications - Matti Hiltunen
   3. RIC Platform - Thoralf Czichy
   4. O-RAN Centralized Unit user-a934b
   5. O-RAN Distributed Unit High Sachin Srivastava
   6. O-RAN Distributed Unity Low Zhimin Yuan
   7. O-RAN Radio Unit (TBD)
   8. Operations and Maintenance - Martin Skorupski
      1. Asking for a new repo. I have sent out the emails for the vote.  This will use a license from the O-RAN Alliance.  We may also use 3GPP but we are only using concepts.  WG1 tried to come up with a common information model.  On motion made by Martin Skorupski  for creating an OAM sub-repo called modeling using the O-RAN license.  Seconded by Viswa.
         1. VOTE: 4-0.  approved.
      2. We do not want to mis-represent the work that we are doing at the Plugfest.
         1. Martin - needs the data models from the O-RAN Alliance.  
   9. Simulations - Alex Stancu
   10. Infrastructure - Xiaohua Zhang
   11. DOC - weichen ni
   12. O-CU user-a934b 

8. Test & Integration Planning - Lusheng

9. Requirements Software Architecture Committee - Rittwik
   1. We are encouraging people to think about release B but have not gotten much feedback.
   2. We need to know the backlog items.
      1. Martin is focusing on having the interface running in release A.  For B release Martin is thinking of Machine Learning.
         1. Rittwik we are looking into it for release B.
            1. As a community we need end to end use cases which is what drives the larger demos to the broader community about what we can do and how it works.  These demos occur at events.  Call out to everyone to work with Rittwik on what are the key use cases that we can pick to focus our test and build efforts around by the end of the B release?  If you don't have this kind of ETE use case then you need some parent ETE use cases to drive the work.  That focuses our efforts.  We need to have up to 5 key end to end use cases.  We focus on showcasing these demos at events.  Please work with Rittwik to get those ideas in place.

10. New Agenda Items (New Business)

    1. O-RAN F2F discussion user-59b16
       1. B release agenda items.  We want to give a detailed architecture view of the non-Realtime RIC.  We have one meeting that is 3 hours long.
          1. That week we will have our regular meeting.  That will be a supplimental meeting.
          2. Rittwik - we need to nail down 3 end to end use cases.  Not pair-wise use cases.  We need full stack use cases.  It will be good to study the O-RAN Alliance use cases or parts of them and demo them.  We want end user end to end use cases to report who benefits from the work we're doing.  
             1. Use cases
             2. Release Planning
             3. Working Alignment
             4. Detailed Architecture
11. Any Other Business (AOB)
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes:
       1. Asking for a new repo. I have sent out the emails for the vote.  This will use a license from the O-RAN Alliance.  We may also use 3GPP but we are only using concepts.  WG1 tried to come up with a common information model.  On motion made by Martin Skorupski  for creating an OAM sub-repo called modeling using the O-RAN license.  Seconded by Viswa.
          1. VOTE: 4-0.  approved. 
    2. Action/ John Murray ask for alternate voting members of TOC.

2019 09 18

Audio recording: oransc-toc-20190918-audio_only.m4a

Agenda

1. Call for Scribe (minutes owner) Lusheng Ji

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
   O-RANge	William Diego	x	Vincent Danno
   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. Moved by user-2057e , seconded by Jinri Huang
      
      1. VOTE: 5-0.  approved.
4. Review of Today's Agenda
   1. New agenda items requested (DOC project committer approval request, INF project committer approval request, discussing license header) added to PTL reporting section.
5. Status of Open Action Items (Old Business)
   1. Action/ John Murray will try to get a representative from each PTL to provide someone to participate in the integration and test team activities.
      1. Service providers should be involved because they will understand what is expected of them.  It will understand what is working and what will work.  We need help in this community.  There is a high and low level activities.  Please reach out to Lusheng and get involved.  I expect all the PTLs to find a representative to participate.
         1. user-d3360: Nokia participation, further discussion with Highstreet and Rutgers.  Asking each project with software deliverables to send rep participating in integration and testing activities.
         2. Gil Hellmann: (windriver) will participate from INF.
   2. Action/ Tracy Van Brakle   continue discussion about Plugfest.  See where we can do plug and play activities at the MWC North Americas event.
      1. On track for December 2 and a white paper on December 5.  We should figure out something synergistic with China mobile. 
      2. Plugfest in Beijing and POC 
         1. Plugfest in Beijing, with real equipment
         2. PoC with OWL (Rutgers Winlab): Amber release
         3. How to promote.
            1. Jinri Huang encourage taking this opportunity.
            2. Tracy Van Brakle to provide writeup next week as base for blog, etc.   
            3. John Murray add to the wiki events page.  ToC member 
            4. Jinri Huang to talk to CMCC how to promote at Beijing slugfest
   3. Action/ Andrew Grimberg will check with the engineer of whether or not there is an automated process to auto-add the reviewers.
      1. Action/ Andrew Grimberg provide documentation and proposal.  
      2. Action/ Andrew Grimberg vet the TOC process with the TOC members.
      3. Action/ Andrew Grimberg provide clear instructions to TOC mail list on how TOC members can get a gerrit account and the process.
      4. user-d3360 no update from LF.  We should not be blocked by INFO.yaml.  If any blocker for new repo, we will raise to LF. 
   4. Action/ John Murray discuss the B release name.
      1. Action/ user-2057e start a poll for B release.
         1. user-2057e will work on this
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. user-59b16 got all the reports.  Will invite O-RAN WG cochairs to RSAC meeting, group by group so people going into F2F knowing the progress. Reports available from the RSAC link in the original Farheen email.
   2. Release planning link.
      1. John Murray We are at week 36.  Risk for near Realtime RIC Platform and xApp.  Start talking about B release schedule.  Plan to be approved: B release Dec 2nd.to June.  At the beginning there is a window for Amber maintenance release, --opportunity to close Release A tech debts.  
   3. Copyright
7. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non real time RIC (RAN Intelligent Controller) - John Keeney
   2. RIC Applications - Matti Hiltunen
   3. RIC Platform - Thoralf Czichy
      1. John Murray any update on the contribution blocked
         1. Thoralf Czichy escalated high up in Nokia.  we have verbal okay.  there are couple of conditions, none problematic.  One thing we must have clear scope.  Publishing E2 spec and ASN.1, legal discussion still on going.
         2. John Murray Filled copyright permission form for OAM project, currently under LF review, will submit to 3GPP as the first example.  Since the code hosted on LF repo, we work through LF.  We will see how this first one goes then others to follow.  O-RAN Alliance is also working with 3GPP.  This also include ASN.1 specifications.  
            1. Action/ Thoralf Czichyto send details of which spec, section, version, to John Murray
            2. John Murray Move this item to Standing Agenda Items from now on.
         3. Jinri Huang TSC requested AT&T and Nokia to report on misalignments between Near Realtime RIC OSC implementation and WG3.  user-59b16 we will need Paul Stevens from WG3 and Matti and other from OSC to start.  John Murray Start to work on this before the F2F.  Also how to manage the time line e.g. when Near Realtime RIC started there was no E2 yet.  Jinri Huangencourage other PTLs to think how to work with WGs, suggesting good documentation for communication.
            1. Action/ user-59b16 To organize meeting 
   4. O-RAN Centralized Unit user-a934b
   5. O-RAN Distributed Unit High Sachin Srivastava
   6. O-RAN Distributed Unity Low Zhimin Yuan
   7. O-RAN Radio Unit (TBD)
   8. Operations and Maintenance - Martin Skorupski
   9. Simulations - Alex Stancu
   10. Infrastructure - Xiaohua Zhang
       1. Committer approval request for Jackie Huang (Jackie.huang@windriver.com) from Wind River for pti/rtp repo and Jianqiang Lu (lujq1@lenovo.com)from Lenovo for AAL repos.
          1. Motion seconded by Jinri Huang,  5 - 0, vote passes.
          2. Discussion John Murray PTL should maintain a contact list for committers in each project.
             1. Action/ user-d3360to work with LF to get the current listing. Completed:  20190920-oran-audit
   11. DOC - weichen ni
       1. Committer approval request for Farheen from AT&T, Eric from LF.  
          1. Discussion: John Murray future plan for community approval process.  currently we ask this activity to come to ToC.
          2. Motion seconded by Jinri Huang, 4 - 0, vote passes.
   12. O-CU user-a934b 

8. Test & Integration Planning - Lusheng

   1. user-d3360 Need standard text for O-RAN Software License.  
      1. John Murray Forwarded to O-RAN Alliance, no response yet.  Jinri Huang Next week EC call I will remind them.
   2. user-d3360 SPDX identifier for Apache 2.
      1. John Murray email Trishan de Lanerolle to confirm there is no issue from LF, if no objection I am okay with it.  Bring this back next week.
      2. Action/ user-d3360contact Trishan de Lanerolle
9. Requirements Software Architecture Committee - Rittwik
   1. user-59b16 B release requirements to share on this meeting next week.
   2. John Murray clear demonstrable use cases as high priority.

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

11. Any Other Business (AOB)
    1. Thoralf Czichy just got email we got green light.  we can move back to open source now.
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes: 
       1. Review and Agree to Minutes of 2019-09-18
          1. Moved by user-2057e , seconded by Jinri Huang
             
             1. VOTE: 5-0.  approved. 
       2. Committer approval request for Jackie Huang (Jackie.huang@windriver.com) from Wind River for pti/rtp repo and Jianqiang Lu (lujq1@lenovo.com)from Lenovo for AAL repos.
          1. Motion seconded by Jinri Huang,  5 - 0, vote passes.
       3. Committer approval request for Farheen from AT&T, Eric from LF.  
          1. Discussion: John Murray future plan for community approval process.  currently we ask this activity to come to ToC.
          2. Motion seconded by Jinri Huang, 4 - 0, vote passes.
    2. Actions
       1. Plugfest 
       2. Tracy Van Brakle to provide writeup next week as base for blog, etc.   
       3. John Murray add to the wiki events page.  ToC member 
       4. Jinri Huang to talk to CMCC how to promote at Beijing slugfest
    3. Action/ user-2057e start a poll for B release.
    4. Action/ Thoralf Czichyto send details of which spec, section, version, to John Murray regarding RIC Platform copyrights.
    5. Action/ user-59b16 To organize meeting
    6. Action/ user-d3360to work with LF to get the current listing. Completed:  20190920-oran-audit
    7. user-d3360 SPDX identifier for Apache 2.
       1. John Murray email Trishan de Lanerolle to confirm there is no issue from LF, if no objection I am okay with it.  Bring this back next week.
       2. Action/ user-d3360contact Trishan de Lanerolle

BACK TO TODAYS AGENDA ^