Technical Charter for O-RAN Software Community

Heads Up! Different International Timings for Daylight Savings (Fall back one hour)

VOTE for the B Release!

2019 10 30

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
   China Mobile	Jinri Huang Co-Chair
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Masafumi Masuda
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar

   *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 Meetings
4. Review of Today's Agenda
5. Marketing of the Amber release (WG, LF, PR)
6. Status of Open Action Items (Old Business)
   • Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video. 
   • Tracy Van Brakle will send out an email to TOC mail list.  We are not going to keep score or pass fail.
   • Jinri Huang will upload presentations and minutes under Events page on the wiki of the face to face meeting. 
   • user-59b16  reach out to Jinri Huang for slides.
   • Action/ Farheen Cefalu remind Jack about how we want to arrange the events page with O-RAN Alliance slides.
   • Action/ Trishan de Lanerolle provide a report to John Murray of the analytics around contributions of the Amber release.
   • Call to Action/ PTLs give a status report for release preparation.  Action/ user-d3360 post the request through mail list.
   • Summarize Face to Face meeting.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
   2. user-d3360 Test & Integration Planning (INT)
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Action/ Jack will move the order of the agenda by moving Test to the top during the release process. 
      2. Matti Hiltunen RIC Applications (RICAPP) 
      3. Thoralf Czichy RIC Platform (RIC)
      4. user-a934b O-RAN Centralized Unit (OCU)
      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      7. Martin Skorupski Operations and Maintenance (OAM)
      8. Alex Stancu Simulations (SIM)

      9. Xiaohua Zhang Infrastructure (INF)

      10. weichen ni Documentation (DOC)
      11. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      12. (TBD) O-RAN Radio Unit (ORU)
   4. user-59b16 Requirements Software Architecture Committee
   5. Project Metrics
8. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
   2. Thoralf Czichy  Near-RealTime RIC platform repos that are required.
9. Planning for Next Meeting
   1. Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
   2. Jack will be adding more items to next weeks agenda.
10. Open Discussion
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes
       • The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
         • Vote to approve minutes for 16 Oct 2019 
         • On motion made by user-2057e
         • Seconded by MASAFUMI MASUDA
         • VOTE: Vote taken, item passed
       • Proposal to make changes to the RIC Platform repos above or Thoralf's request through lists.o-ran-sc.org
         • On motion made by Thoralf Czichy
         • Seconded by MASAFUMI MASUDA
         • VOTE: Vote taken, item passed
    2. Actions 
       • Farheen Cefalu Add to the marketing of the Amber release to TOC agenda.
       • Call to action for TOC members to lead the Amber release marketing and PR strategy for the Amber release.
       • Trishan de Lanerolle  support Tracy Van Brakle with PR.
       • user-59b16  will reach out to Jinri Huang for F2F slides to put in the Events wiki.
       • Action/ Farheen Cefalu remind Jack about how we want to arrange the events page with O-RAN Alliance slides.
       • Action/ Trishan de Lanerolle provide a report to John Murray of the analytics around contributions to the Amber release. How many committers?
       • Action/ Farheen Cefalu  add an agenda item for project metrics.
       • Call to all PTLs to give a status report for release preparation.  Action/ user-d3360 post the request through mail list.
       • user-59b16 post the churn use case presentation on RSAC.
       • Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
       • Action/ Farheen Cefalu move the order of the agenda by moving Test to the top during the release process. 

2019 10 23

Zoom meeting: 2019-10-23_toc._audio.m4a

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	x
   NTT DOCOMO	Masafumi Masuda	x
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar

   *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 Meetings
   • The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   • Vote to approve minutes for 16 Oct 2019 
   • On motion made by user-2057e
   • Seconded by MASAFUMI MASUDA
   • VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
   1. Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      1. Tracy reviewed with several working groups last week.  I am uploading the current slides and a welcome package.  Demo video will record the live demo and read out in zoom and post that in the O-RAN Alliance wiki and the O-RAN-SC wiki.  Unless there are other suggestions for the video?
         1. Good idea we need to figure out how we'll organize our information about our releases from that demo and marketing stand point.
         2. Action Farheen Cefalu Add to the marketing of the Amber release to TOC agenda.  We need to work on a package with WG and LF on what PR we are going to put out.
         3. Call to action for TOC members to lead the Amber release marketing and PR strategy for the Amber release.
         4. Tracy - Talk to Jack offline for the expectations on the vendors.  They are asking questions about PR.  
         5. Action/ Tracy Van Brakle will send out an email to TOC mail list.  We are not going to keep score or pass fail.
         6. Trishan de Lanerolle  support Tracy Van Brakle with PR.
   2. Jinri Huang will upload presentations and minutes under Events page on the wiki of the face to face meeting. 
      1. user-59b16  reach out to Jinri Huang for slides.
         1. Make sure there is nothing in the documents that O-RAN is not ready to release publicly.
         2. Executive Committee slides can go up?
            1. Let's get a list of what we can put up.  There is a difference between the TOC meetings and the O-RAN Alliance meetings.  We can point to the O-RAN Alliance wiki or else we need permission to share their slides on O-RAN-SC.
            2. Action/ Farheen Cefalu remind Jack about how we want to arrange the events page with O-RAN Alliance slides.
   3. user-d3360 send Jinri Huang the count of committers in gerret.
      1. Amber metrics need to be gathered.  How many committers?
         1. Action/ Trishan de Lanerolle provide a report to John Murray of the analytics around contributions of the Amber release.
      2. LF has a new analytics platform based on code contributions in a project.  
         1. When will the reports be available?
         2. Action/ Farheen Cefalu  add an agenda item for project metrics.
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. We have 2 weeks and then we will have our updated code freeze.
      2. We will freeze code November 2 and then a few weeks of defect fixing, then freeze and branch the code.  We will document the code during the code freeze and then have our release.  Once we branch the code we will return to a maintenance cycle in January.  The maintenance release will run through Feb 1.  This is projected for B.  We have not finalized the B plan.  Dec. 2 we will start Epic identification.  RSAC will come with their use cases and details.  We take off from December 21st to January 6th.  If changes need to be made make them now.  They need to be finalized in the next few weeks.
   2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Action/ Jack will move the order of the agenda by moving Test to the top during the release process. 
      2. Matti Hiltunen RIC Applications (RICAPP) 
      3. Thoralf Czichy RIC Platform (RIC)

         1. Below a list of changes to repos (new ones, as well as deletions) under the RICP (near-RT RIC Platform) that we would like the TOC to approve. Parts marked with RICP/RICAPP are proposed by Matti and I (PTLs for RICAPP and RICP) and parts marked with RICP only  me as PTL.

            (WE1) Project RICP
              ric-plt/resource-status-manager
                  - Summary: Implements the management of Resource Status messages over E2
                  - Description: The Resource Status Manager is responsible to control the generation of
                      Resource Status messages sent by the RAN to the RIC by issuing Resource Status Requests.
                      The RSM provides an API that allows to start and stop the generation of these messages as
                      well as to issue specific request commands. The RSM provides also default values which are used
                      whenever a new RAN (eNB) is added to the RIC.
                  - License: Apache 2
                  - Initial committers: (all AT&T) Shuky Har-Noy  ( shuky.har-noy@intl.att.com),  Hila Anina ( hanina@intl.att.com), Yaki Ratz ( yaki.ratz@intl.att.com )

            (WE2) Project RICP/RICAPP
              We (RICP and RICAPP PTL) would like to remove the following repositories:
                 ric-app/demo    (empty)
                 ric-app/reporter (not maintained anymore for 6 months (and actually confusing community if someone uses this as reference) and e.g. the measurement campaign xApp can replace it)
                 com/asn1         (an ASN.1 compiler for which we found that it causes to much issues that we had to troubleshoot. We already switched to using com/asn1c (which is derived from https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_vlm_asn1c&d=DwIFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Tnwenk7t78Qk7cMlMZ90EGmbng6eVuV4yQNhqbtpKkk&m=xoq2zMpPhab9uHOEBVXWXAFXjPsyFpAgdbNtyADOnwY&s=Rkl10dXpdSlyLJTKlTd3zwy98meppgWMQ_0PNWZ8QjQ&e=)

            (WE3) Project RICP
               new repo: ric-plt/ric-test
                  - Summary: RIC platform-specific testing that are not specific to a single RIC component
                  - Description: This repo includes test cases that span the full RIC platform, i.e., that cannot run against a single RIC component. This may also include
                      simulators related to the E2 base protocol, or related abstract test xApps (that do not actually implement 3GPP specifications). Note that the test
                      cases must still be limited to RIC platform only. If you want to write/check test cases that integrate also other O-RAN SC components, check
                      the it/test repository.
                  - License: Apache 2
                  - Initial committers: (first one AT&T, the other two from Nokia): Xuan Tuyen Tran (Harry) (tuyen@research.att.com ), Amit Uttam  ( amit.uttam@nokia.com )  and Shashikumar HN ( shashikumar.hn@nokia.com )

            (WE4) Project RICP
               new repo: ric-plt/ric-dep
                  - Summary: Code and configuration files that are needed for deploying a near-RT RIC platform instance
                  - Description: This includes, for example, helm charts for RIC platform components. In this we can make assumptions about the underlying k8s already existing or
                                 we can also spin up blueprints for such a deployment. Note that this component is intentionally limiting itself to the RIC platform and does
                                 not include other O-RAN SC components. For such you might want to look at the it/dep repo managed by another O-RAN SC project.
                  - License: Apache 2
                  - Initial committers: (first one AT&T, the other two from Nokia): Lusheng Ji (lji@research.att.com) , Prabhu K ( prabhu.k@nokia.com )  Ranjit  Angajala   ( ranjit.angajala@nokia.com )

              Note that this needed for legal reasons to clearly define the scope of the near-RT RIC project. It is aligned with a "scope" wiki text that we wrote for the same reason.
              Also note that we continue with the it/dep repo as a general integration repo where any O-RAN SC components can be integrated together. In scope of their work on
              integrating all O-RAN SC components, engineers working on the it/dep repo might re-use some of the functionality that was original committed to ric-plt/ric-dep .

            (WE5) Project RICP/RICAPP
              We would like to remove the empty ric-app/uemgr and instead create a new repo under ric-plt/. This is in order to clearly link
              the demo xApp to the RIC platform project. At the same time also note that the license of this is changed to a documentation
              license. So that its legal scope reflects its actual role in the RIC platform. Naturally there will continue to be actual xApps under the
              RICAPP project. Placing it under the RICP project (and not RICAPP) allows Nokia to contribute to it. The name is intentionally kept
              generic. As part of this change we also move this page https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.o-2Dran-2Dsc.org_display_RICA_UE-2BManager-2BxApp&d=DwIFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Tnwenk7t78Qk7cMlMZ90EGmbng6eVuV4yQNhqbtpKkk&m=xoq2zMpPhab9uHOEBVXWXAFXjPsyFpAgdbNtyADOnwY&s=gaI_Yvwbqi4X3KKgd2KlO1cau-oPGsKTpA0lo3SzHeo&e= to the RICP project (a reference
              in RICA continues to refer to it.
              deleted repo: ric-app/uemgr
              new repo: ric-plt/demo1
                  - Summary: A simple demo xApp running on the RIC platform.
                  - Description: Contains a simple demo xApp running on the RIC platform.
                  - License: Creative Commons Attribution 4.0 International License
                  - Initial committers: (all Nokia) Timo Tietavainen ( timo.tietavainen@nokia.com ), Jussi Maki Aijala (jussi.maki-aijala@nokia.com), Juha Hyttinen (juha.hyttinen@nokia.com) , Anssi Mannila  ( anssi.mannila@nokia.com)

            (WE6) ) Project RICP
              We delete the following repo: ric-plt/ue-nib . The scope of the RIC platform does not include this functionality. If, then
              such functionality should be developed outside of the RIC platform, e.g., under the RICAPP project. Some of the earlier functionality (read and write
              of the demo data that is actually needed in the "demo1" demo xapp (under documentation license) is moved into the demo1 repo as it is
              closely related and does not make too much sense as standalone documentation repo. Note that this implies that the functionality is now under
              document license in ric-plt/demo1

            1. Empty repos are allowed to be deleted.  Repos with content are open source and remain for historical reasons.
               1. Needs to be marked as depricated.  When we complete the Amber release there should not be code dependencies.  Therefore we can remove the repos because this is the first A release.  
            2. The RIC platform as an entity must be open source contained platform.  When you cross over to system integration is work in a different project that will rely on the RIC project but other people on different licenses won't be able to participate.  
               1. E2 was removed due to legal issues.
               2. RIC PLT E2 had files ASN1 files that were not supposed to be there.  That compiler was used in early development but won't be used again.
            3. Concern about putting this in documentation license downstream and someone contributes back to a test repo then it becomes a part of the test by the integration team.
               1. That is acceptable.  
         2. Proposal to make changes to the RIC Platform repos above
         3. On motion made by Thoralf Czichy
         4. Seconded by MASAFUMI MASUDA
         5. VOTE: Vote taken, item passed
      4. user-a934b O-RAN Centralized Unit (OCU)
      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      7. Martin Skorupski Operations and Maintenance (OAM)
      8. Alex Stancu Simulations (SIM)

      9. Xiaohua Zhang Infrastructure (INF)

         1. During f2f repos were summarized.  3 repos were supposed to be contributed by inspur.  I double checked and they are not using those repos anymore.  They will not be making future contributions.
            1. These are seed code repos that were not a part of the Amber release.  We need to go ahead and clean up and remove those seed repos.  No vote needed.  This is normal clean up.  
            2. Action/ Xiaohua Zhang raise a ticket with LF to remove the seed code projects.
      10. weichen ni Documentation (DOC)
      11. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      12. (TBD) O-RAN Radio Unit (ORU)

   3. user-d3360 Test & Integration Planning (INT)

      1. Call to all PTLs to give a status report for release preparation.  Action/ user-d3360 post the request through mail list.
      2. Next TOC will occur after daylight savings time.  Not all communities will recognize that shift and that will move this meeting minus 1 hour.
   4. user-59b16 Requirements Software Architecture Committee
      1. Discussed traffic churn use case with different values.  We should prepare for that.  We are going to look at our spreadsheet of epics consolidate and move on to call flows.  It's in a word document with some call flows.  I am hoping that Thoralf Czichy and Matti Hiltunen will discover algos that will work with xApps.  Talked to Samsung about CU DU binary code for an example.  Jin Sun said their management will look into it.  Radisys agreed to provide a CU DU binary.
         1. As part of the release planning when we get into the B release we identify the epics.  Yes there is an approval.  This is the version of our requirements and use cases as part of the B release.  That package should be brought to the TOC for a vote to freeze the target environments.  
            1. When does that happen?
               1. December 7th once the epics are identified we should freeze it so the projects can commit to B release.  This gives the development team to groom their user stories.
         2. How many end to end use cases?
            1. One
         3. Jack would like to see a simpler e2e  base line "hello world" use case that demonstrates that the platform is working.  It is a simple metrics use case that can exercise the components and return metrics on the different components running in place.  We need a use case that we maintain for the basic level of operation before talking about complex.  We want a base line use case that exercises the system and gathers metrics.  A heartbeat check.  This way everyone is at a base point before advancing their use case.  There should be a self diagnostic test so the platform is base lined.
         4. user-59b16 post the presentation.
7. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
   2. Thoralf Czichy  Near-RealTime RIC platform repos that are required.
8. Planning for Next Meeting
   1. Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
   2. Jack will be adding more items to next weeks agenda.
9. Open Discussion
10. Any Other Business (AOB) 
11. Meeting Summary (resolutions, new action items, etc.)
    1. Votes
       • The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
         • Vote to approve minutes for 16 Oct 2019 
         • On motion made by user-2057e
         • Seconded by MASAFUMI MASUDA
         • VOTE: Vote taken, item passed
       • Proposal to make changes to the RIC Platform repos above or Thoralf's request through lists.o-ran-sc.org
         • On motion made by Thoralf Czichy
         • Seconded by MASAFUMI MASUDA
         • VOTE: Vote taken, item passed
    2. Actions 
       • Farheen Cefalu Add to the marketing of the Amber release to TOC agenda.
       • Call to action for TOC members to lead the Amber release marketing and PR strategy for the Amber release.
       • Trishan de Lanerolle  support Tracy Van Brakle with PR.
       • user-59b16  will reach out to Jinri Huang for F2F slides to put in the Events wiki.
       • Action/ Farheen Cefalu remind Jack about how we want to arrange the events page with O-RAN Alliance slides.
       • Action/ Trishan de Lanerolle provide a report to John Murray of the analytics around contributions to the Amber release. How many committers?
       • Action/ Farheen Cefalu  add an agenda item for project metrics.
       • Call to all PTLs to give a status report for release preparation.  Action/ user-d3360 post the request through mail list.
       • user-59b16 post the churn use case presentation on RSAC.
       • Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
       • Action/ Farheen Cefalu move the order of the agenda by moving Test to the top during the release process. 

Return to Todays Agenda ^

Archived Meetings