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

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2019 10 02

Zoom Meeting: 2019-10-02-toc.mp4

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	x
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Masafumi Masuda	x
   O-RANge	William Diego	x	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 Meeting
   1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for 25 Sep 2019 
      2. On motion made by William Diego
      3. Seconded by Masafumi Masuda
         VOTE: Vote taken, item passed
4. Review of Today's Agenda
   1. Items added to section 10 New Agenda new Business below.
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.
      2. Farheen Cefalu add to the wiki events page. 
         1. Jinri received a call for participation.  Farheen Cefalu follow up with Tracy and Jinri.
      3. Jinri Huang to talk to CMCC how to promote at Beijing plugfest.
         1. Jinri will report back 09 Oct 2019 .
            1. Two parallel sessions in Beijeng and USA.  Jinri wants to promote TOC in both events.
   2. Action/ user-2057e start a poll for B release.
   3. Action/ user-59b16 publish the meeting details on the RSAC page regarding WG3 and E2.
      1. Last week Rittwik organized the meeting to align the O-RAN working groups.  Jinri attended.  There was another alignment meeting with software working group and O-RAN Alliance.
   4. 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. Conclusion is we are not using SPDX.
   5. Action/ user-d3360 talk to Jack about which use cases are being covered by the test and integration team, for release B.
   6. Action / Tracy Van Brakle TOC will look to Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. RSAC meeting Rittwik mentioned most development work in RSAC is ongoing.  Our target is to have our release at the end of November.  Initial idea to reconsider the timeline.  Rittwik and Jack are not here.  Call for opinions.
         1. Matti - Code freeze is Monday this week.  We are not supposed to add anything.  Proposal by Rittwik to extend the release by three weeks (1 full sprint).  Code freeze was September 30 extend it for three weeks.  Team needs more development time.
            1. Who should we request an extension from?
               1. Release Manager
               2. Voting approval by TOC and TSC.
               3. Action/ user-59b16 place a formal approval request for code freeze extension.
            2. LF projects release has a special meaning.
               1. Code hosted by LF gerrit, nexus, etc.
               2. To release code must be published to other global repos.  Gerrit goes to github.  Docker images go to Dockerhub.  To publish means to publish to these global repositories.  Meaning we should have some standards.
                  1. Do we have any standards for release?  
                     1. LF has different criteria for different releases.
                     2. Licenses have to have standards.
                     3. As far as software quality is the TOC/TSC decision.
      2. Jun Song - wants to raise an issue.  RSAC meeting I raised two issues for KPI XApp.  We don't know how to verify and test the xApp once we complete the coding.  
         1. Matti - from integration point of view what are the requirements his KPI xApp has to meet?  It will talk to simulator via E2 termination.  Other xApps are tested with a simple simulator without E2.  Action/ Matti Hiltunen document the simulator test on the RSAC space in the wiki.  We don't have anything else for the Amber release besides the simulator to test xApps.
         2. Lusheng - I would like to see one xApp for a complete integration.  I would like to see it following the overall flow and architecture.  We can enhance a component for the Amber release.  It can be deployed so the APIs provided by the near real time platform would be a big achievement.
            1. As long as you can deploy the xApp would be a minimum viable product.
               1. Martin agrees.  We need to have the basic building blocks complete.
      3. Jinri - We need Rittwik to vote on extending the timeline.
   2. Release planning link.
   3. Copyright
      1. Which projects have the copyright issue?
         1. CU, DU, RIC Applications.
      2. There was a form from O-RAN Alliance regarding the copyright issue.  
         1. We should let Jack address.  He wants to test one or two components.  Jinri will review with Jack.
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. Outstanding Resource Requests for Linux Foundation

         1. https://lists.o-ran-sc.org/g/toc/topic/new_repo_requests_ricp/34367904?p=,,,100,0,0,0::recentpostdate%2Fsticky,,,100,2,0,34367904 

            1. hi,

               I hereby request two new repos managed by the RICP (near-RT RIC platform) project.

               ric-plt/asn1-documents

                     - Summary: ASN.1 definitions and related documents

                     - Description: ASN.1 definitions and related documents that are needed by other components in compilation. E.g., this includes E2 ASN.1 definitions.

                     - License: Creative Commons Attribution 4.0 International License (unless document comes from somewhere else)

                     - Initial committers: Thoralf Czichy (thoralf.czichy@...), Alistair Urie (alistair.urie@...), Paul Stephens (paul.stephens@...), Antti Puhakka ( antti.puhakka@... )

               ric-plt/streaming-protobufs

                     - Summary: protobuf definitions used when streaming messages to other xApps

                     - Description: contains protobuf definitions that xApps can use, for example, to derive statistics from streams of messages obtained from the RAN.  

                     - License: Creative Commons Attribution 4.0 International License

                     - Initial committers: Timo Tietavainen (timo.tietavainen@... ), Jussi Maki Aijala (jussi.maki-aijala@...), Rolf Badorek (rolf.badorek@...)

               All committers are already committers in other repos of the RIC platform. Additionally we have Alistair and Paul working in WG3 of

               the O-RAN alliance and myself as RIC PTL.

               Thoralf

      2. Vote to approve two new repos managed by the RICP (near-RT RIC platform) project 

         1. ric-plt/asn1-documents will be in word or pdf which are not reviewable by git gerrit.  License will be the common.

            1. Committers: Thoralf Czichy, Allistair Urie, Paul Stephens, Antti Puhakka.

         2. Protobuf definitions ric-plt/streaming-protobufs.  They are an interface.  No code link or creative logic.  3 Nokia Committers. See Thoralf Czichy  message on lists.o-ran-sc.org TOC.
            1. Committers: Thoralf Czichy, Jussi Maki Aijala, Rolf Badorek.
   1. 1. 1. On motion made by William Diego
         2. Seconded by Masafumi Masuda
            VOTE: Vote taken, item passed
   2. O-RAN Centralized Unit user-a934b
   3. O-RAN Distributed Unit High Sachin Srivastava
   4. O-RAN Distributed Unity Low Zhimin Yuan
   5. O-RAN Radio Unit (TBD)
   6. Operations and Maintenance - Martin Skorupski
   7. Simulations - Alex Stancu
   8. Infrastructure - Xiaohua Zhang
   9. DOC - weichen ni
   10. O-CU user-a934b 

8. Test & Integration Planning - Lusheng

9. Requirements Software Architecture Committee - Rittwik

10. New Agenda Items (New Business)

    1. Approval from Thoralf Czichy for Near Real time RIC
    2. Face to face meeting discussion regarding agenda Jinri Huang
       1. Who will be at F2F? Jinri Huang , MASAFUMI MASUDA, William DIEGO user-a934b.  Rittwik will be there.  Thoralf and Matti will work with Rittwik for the RIC presentation.
       2. October 14 - 16 we are in the afternoon session from 4:30 - 7:00PM.  There are four purposes for the meeting.
          1. consolidate our alignment with WG.
          2. Discuss release B planning
          3. Copyright issue discussion
          4. Discuss the respective projects but since low attendance of PTLs we may reconsider.
          5. To make the communication for WG better there is a slide.  Check with other working groups and prepare similar slides.  Let us call them Alignment Analysis.  I can see a list of items divided into three groups with three marks.  
             1. "Aligned" mark: items developed based on released spec. or what have been agreed in the WG.
             2. "pre-spec" mark: items being specified, or to be specified in the future in WG.
             3. "TBD" mark; 
                1. Do the items go beyond the interface protocols A1, O1?
                   1. Definitely interface and maybe messages.  This is generic.
                      1. Should the PTLs or WGs come with the list of items?
          6. Last remarks: Go to WG3 wiki and check out their alignment document as an example.
          7. Reviewed draft agenda
             1. Day 1: Alignment - Needs TOC support to convince TSC about WGs alignment.
             2. Day 2: Allocate 2 hours for Release B.
             3. Day 3: Copyright issues.
    3. There is a motion in working group 1 to rename the non real time RIC.  Mentioned to Jack.  We have until the Costa Rica F2F meeting to decide if the OSC has a meeting on this.  Action/ Farheen add to next weeks call.
    4. Action/ Farheen add discuss the relationship with the upstream projects to next weeks agenda.  John Keeney is looking for guidance for upstream and downstream projects such as Acumos and Akraino.
11. Any Other Business (AOB)
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes:
       1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
          1. Vote to approve minutes for 25 Sep 2019 
             1. On motion made by William Diego
             2. Seconded by Masafumi Masuda
                1. VOTE: Vote taken, item passed
       2. Vote to approve two new repos managed by the RICP (near-RT RIC platform) project
          1. ric-plt/asn1-documents will be in word or pdf which are not reviewable by git gerrit.  License will be the common.
             1. Committers: Thoralf Czichy, Allistair Urie, Paul Stephens, Antti Puhakka.
          2. Protobuf definitions ric-plt/streaming-protobufs.  They are an interface.  No code link or creative logic.  3 Nokia Committers. See Thoralf Czichy  message on lists.o-ran-sc.org TOC.
             1. Committers: Thoralf Czichy, Jussi Maki Aijala, Rolf Badorek.
                1. On motion made by William Diego
                2. Seconded by Masafumi Masuda
                   VOTE: Vote taken, item passed
    2. Actions
       1. Plugfest Actions
          1. Tracy Van Brakle to provide writeup next week as base for blog, etc.
          2. Farheen Cefalu add to the wiki events page. 
          3. Jinri received a call for participation.  Farheen Cefalu follow up with Tracy and Jinri.
          4. Jinri Huang to talk to CMCC how to promote at Beijing plugfest.  Jinri will report back 09 Oct 2019 .
             1. Two parallel sessions in Beijeng and USA.  Jinri wants to promote TOC in both events.
          5. Action/ user-2057e start a poll for B release.
          6. Action/ user-59b16 publish the meeting details on the RSAC page regarding WG3 and E2.
          7. Action/ John Keeney discuss renaming of near real time RIC.
          8. Action/ John Keeney discuss the relationship with the upstream projects such as Acumos and Akraino.
          9. Action/ Jinri Huang discuss PTLs slide preparation for the F2F meeting.

Return to Todays Agenda ^

Archived Meetings