Technical Charter for O-RAN Software Community

2020 03 18

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		Lusheng Ji
   China Mobile	Jinri Huang Co-Chair		Weichen Ni
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar		Skand Priya

   *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. Release Votes and Approval
6. Marketing of the Amber release (WG, LF, PR)
   1. O-RAN Alliance  Feb 17-21 (Paris) F2F canceled and now virtual meeting schedule published
   2. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
7. Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
   1. Action Ken Trudgeon from Viavi will report back on O-1 capabilities for an end to end full stack capability for the OAM team John Keeney.
   2. Action/ ENGWEI KOO will set up a meeting with  Tracy Van Brakle , Martin Skorupski John Keeney , and Alex Stanc to discuss O-1 interface options with Viavi
   3. Action/ Jinri Huang will share slides to set up projects using the O-RAN SC regarding the Open Data Set project from O-RAN TSC.
   4. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
   5. Action/ user-59b16 update TSC with the short/long term UE emulator support.  
   6. Action/ David (DT) we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
   7. Action/William DIEGO  will talk to the focus group regarding test coordinator for the O-RAN SC.
      
   8. Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
   9. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release. 
   10. Action/ Jinri Huang will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
   11. Action/ user-a934b work with Lusheng to create the test cases for O-CU.
       
   12. Action/ user-a934b update the Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues. 
   13. Action/ Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.
   14. Action/ Sachin Srivastava update ODU-High Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues. 
   15. Action/ PTLs assign someone to lead the integration and test.
   16. Action/ Farheen Cefalu request to escalate the calendar issue with LF or add it to agenda for TOC call.
8. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
   2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
      3. user-a934b O-RAN Centralized Unit (OCU) 
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
   3. user-59b16 Requirements Software Architecture Committee
   4. user-d3360  Integration and Test
9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
10. Planning for Next Meeting
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)

2020 03 11 

Recording: 2020-03-11-toc.mp4
Audio: 2020-03-11-toc_audio_only.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	Lusheng Ji
   China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar		Skand Priya

   *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. No Quorum, no votes were taken in this meeting.
4. Review of Today's Agenda
5. Release Votes and Approval:  Formal votes are not required for adding and committers by TOC.  Committer votes can be done by the committers within that project.  The PTL should send a notification of the committer to the main mailing list.  
   1. Dear ToC members,

      The development of the KPIMON xApp is moving to a different team. Therefore, I would like the additional committers for the ric-app/kpimon repo:

      zhongwei liu(zw620.liu@samsung.com)
      ming hao(ming80.hao@samsung.com)
      xin guo(xin97.guo@samsung.com)
      guanghe xin(guanghe.xin@samsung.com) 

      Thank you,

      Matti

   2. [ cross-posting to "toc" (formal approval) and "main" (ricp project discussion) ]

      hi

      For TOC approval. Below a request to replace one committer with another one for the existing near-RT RIC platform component vespamgr.

      Name: https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/vespamgr

      Project: near-RT RIC

      IN:  Abukar Mohamed (LFID: Nune)

      OUT: Heikki Ahola (not working on RIC components anymore)

      Nune has been working on various RIC components already, like the xApp manager. Both - Nune and Heikki - are from Nokia.

      The vespa manager The VESPA manager uses the VES Agent (https://github.com/nokia/ONAP-VESPA) to adapt near-RT RIC internal

      statistics collection using Prometheus (xApps and platform containers) to ONAP's VES (VNF event streaming).

      Best regards,
      Thoralf Czichy
      PTL, O-RAN-SC near-RT RIC

   3. Dear ToC members,

      I would like to request approval for a new committer in the sim/e2-interface repository:
      · name: Bharath Balasubramanian
      · email: bharathb@research.att.com
      · company: AT&T
      · Linux Foundation id: bharathb
      · timezone: America/New York (GMT -5)

      This is needed for moving the E2 simulator from the INT project to the SIM project.

      Many thanks in advance!

      Kind Regards
      Alex
      O-RAN-SC SIM project PTL

      Alexandru Stancu, PhD
      Senior Software and Telecommunications Engineer

   4. Dear ToC members,

      I would like to request approval for a new committer in the scp/oam/modeling repository:

      • name: 'Alex Stancu'
      • email: 'alexandru.stancu@highstreet-technologies.com'
      • id: 'alex.stancu'
      • company: 'highstreet technologies GmbH'
      • timezone: 'Europe/Bucharest'

      This is needed after Kevin Scaggs retired.
      Many thanks in advance!
      Kind Regards
      Martin
      O-RAN-SC OAM project PTL
      Martin Skorupski

6. Marketing of the Amber release (WG, LF, PR)
   1. O-RAN Alliance  Feb 17-21 (Paris) F2F canceled and now virtual meeting schedule published
   2. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
      1. ONES has been cancelled.
      2. Tracy - Our proposal for the panel discussion was accepted.  ONES is pushed out to August/September.  That will be when we do the POC and Plugfest for OSC Bronze.  We should have members attend if the COVID-19 is not an issue.
      3. Martin - Should we update the Plugfest from June to September.
         1. Tracy - Waiting for an official yes before we change the dates.
7. Status of Open Action Items (Old Business)
   1. Action/ user-59b16  discuss Viavi 
      1. ENGWEI KOO  (Viavi) Ken Trudgeon (Viavi)shared a slide Viavi DU RAN/RAN Emulation around traffic use cases. 
      2. 1. Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
         2. Slide 4. Re Jack's question. Can we emulate the O-CU?
            1. Currently we don't have an O-CU emulator but have had discussions with your team.  We have R&D.  We'd provide a peer to provide emulations.  It's on our road map and we do have capabilities that are being leveraged.  We are working with your team to generate traffic into the simulator without O-CU present.
            2. John Keeney - Are there OAM interfaces?
               1. Action Ken Trudgeon provide rudimentary counters and traces that can be provided.
                  1. Ken - we maintain a large data.  It's a matter of delivering KPIs to you.
                  2. ENGWEI KOO we are emulating the O-RAN network functions.  For O-RU Emulator we delivered to WG4.  Our understanding is not as deep as yourself. O1 is not finalized for the DU and CU.  Is it possible to have a call to discuss O1 standardization and review what Viavi can provide as an emulator step.
                  3. Action/ Tracy Van Brakle set up a meeting with Martin, John, and Alex with ENGWEI KOO based in Singapore.
                  4. Jack - Final decisions have not been made.  This is a continual discussion.  Everybody brings their contributions.  There are financial considerations.  We will continue our discussions.
                     1. Tracy - There is an expectation that the O-RAN integration systems for donations.
                        1. Jack - O-RAN wants an Interoperability role.
                           1. Tracy - AT&T and other members have donated a significant amount.
   2. Action/ Jinri Huang will share slides to set up projects using the O-RAN SC regarding the Open Data Set project from O-RAN TSC.
   3. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
   4. Action/ user-59b16 update TSC with the short/long term UE emulator support.  
   5. Action/ David (DT) we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
   6. Action/William DIEGO  will talk to the focus group regarding test coordinator for the O-RAN SC.
      
   7. Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
   8. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release. 
   9. Action/ Jinri Huang will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
   10. Action/ user-a934b work with Lusheng to create the test cases for O-CU.
       
   11. Action/ user-a934b update the Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues. 
   12. Action/ Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.
8. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
   2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
         1. Note that demo is scheduled for Thursday, Mar-12, 9am Eastern Time
      3. user-a934b O-RAN Centralized Unit (OCU) 
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
         1. What progress was made in the first dev cycle?  Are there outstanding items?  How are you progressing?
            1. 7 epics.  Targeting 1 epic in sprint 1.  We have Jira user stories.  Some more tasks have to be designed.  We have taken up E2 side based on draft specification.
            2. Action/ Sachin Srivastava update Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues. 
               1. Are there major issues?
                  1. Looking for clarity on integration testing.  Will be meeting with Viavi.  
                     1. Jack - Good point raised on integration.  Looking for one individual per company for integration and test.  
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
         1. Zhimin - Looking for O-DU integration.  Viavi didn't demonstrate O-CU on different products. 
            1. Ken - On O-CU emulation is in our road map but it's not currently available.  We don't anything for emulating an O-CU yet.  We are open to further discussions around re-purposing.
            2. Rittwik - DU High and DU Low.  We need a call with Lusheng.  It is contingent on Viavi getting on board.
               1. Jack - It is a major functional goal to create a DU test apparatus.  These two pieces are needed for Bronze.
               2. Rittwik - What do you (Jack) need to make a proposal or decision.
                  1. Jack - Does anyone in the community have a broader perspective that will pull together the integration and testing?  We won't have end points without having a simulator.  Does anyone object to finding a simulator partner.  Is there anyone who has other ideas, concerns, questions about using a simulation platform partner to advance our needs?
                     1. For upcoming PoCs and Plugfests it is critical for O-RAN.
                        1. Jack - We want to focus on O-RAN SC community to recognize the need and value for the emulator.
                           1. John Keeney - O1.  Agrees we need something in this lower level space.
                           2. Alex Stancu - We will want it for the Simulator project.  Thinking long term.
                        2. The challenge we have is the individual components don't exist at all.  Trying to use the broader simulator where more of the system is working will have different needs.  How much do I build?  it would be quite an investment to build an O-CU.  
                        3. Rittwik - The simulator will help show the value of traffic steering can be achieved through simulator.
                        4. Lusheng - It is important for filling gaps in testing and use cases.  Viavi team what is the extensiblity?  Can we work with plugins with simulators?
                           1. Ken - Typically we deliver these into large scale manufacturer.  It is what we are doing here.  Providing and API.  We don't have an issue with publishing well defined APIs of the simulator that you can use.  Being able to allow you to connect to that we would be open to those conversations.
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
         1. We need a resource that will help enhance the E2 simulator.
         2. Open source projects aren't about one company building a component.  We need to promote people of common interests collaborating on common interests.  It is not free form but people who benefit from the E2 should get involved.  People from the working groups need to get involved so everyone can benefit from it.  Call to community to help Alex Stancu
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
   3. user-59b16 Requirements Software Architecture Committee
9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. John Keeney  calendars are not synchronized or coordinated across teams.  Action/ Farheen Cefalu request to escalate the calendar issue with LF or add it to agenda for TOC call.
10. Planning for Next Meeting
11. Any Other Business (AOB) 
    1. Thoralf suggests to discuss if we should proceed with committer changes based on OSC charter: https://o-ran-sc.org/ORAN_SC_Charter.pdf. Quote from page 2: "A Contributor may become a Committer by a majority approval of the existing Committers. A Committer may be removed by a majority approval of the other existing Committers.". Chris comments, "the established procedure for handling committer changes in other LF projects is like this: 1) a committer sends email to a public email list to nominate the new person, with a statement that ideally lists commits to the repo to demonstrate a history of contributions, 2) the CURRENT COMMITTERS vote on the nomination by replying to the same public email list,3) if a majority of committers approve the change, the new person is approved, 4) to implement the change hopefully it's enough to edit the INFO.yaml file and merge the change; if not, write a ticket at LF and point to the votes in the email list." With all that said, the project is relatively young and we're just now having a wave of committer changes. Should we move over to such a per-repo process, also to relieve the TOC voting members? Note thet current TOC-process for committer changes is described here: How to request committer changes
12. Meeting Summary (resolutions, new action items, etc.)

2020 03 04

Recording: 2020-03-04_toc.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	Lusheng Ji
   China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
   Deutsche Telekom	David Streibl	x	Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar		Skand Priya

   *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. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for 26 Feb 2020 
      3. On motion made by Jinri Huang
      4. Seconded by user-2057e
      5. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Release Votes and Approval

   1. Repo request for RICAPP - 4th reminder - Matti Hiltunen

      1. Dear O-RAN SC TOC members,

         I would like to request the following new repos to accommodate the new xApps required for the O-RAN SC Bronze release use cases (traffic steering and health check). 

         Jinri and Jack have already approved this - waiting for one more.

         TS xAPP:

         • Proposed repository name: ric-app/ts
         • License: Apache 2 
         • A brief description: This repo will host the source code for the TS (Traffic Steering) xApp. Written in C++. 
         • A list of committers:
           1. Ron Shacham, rshacham@...
           2. Shraboni Jana, sj492a@...
           3. Scott Daniels, daniels@...

         QP xApp:

         • Proposed repository name: ric-app/qp
         • License: Apache 2 
         • A brief description: This repo will host the source code for the QP (QuE Predictor) xApp that uses a machine learning model to predict the QoE of a UE if it is handed over to a new cell. Written in Python.
         • A list of committers:
           1. Manoop Talasila, talasila@...
           2. Guy Jacobson, guy@...
           3. Gueyoung Jung, gjung@....com
         • QP Driver xApp:
         • Proposed repository name: ric-app/qp-driver
         • License: Apache 2 
         • A brief description: This repo will host the source code for the QP Driver xApp that pulls the features used in the QP ML model out of the SDL layer for the UEs whose QoE we want to improve. Written in go.
         • A list of committers:
           1. Tommy Carpenter, tommy@...
           2. Scott Daniels, daniels@...
           3. Jack Lucas, jflucas@...

         HW xApp:

         • Proposed repository name: ric-app/hw
         • License: Apache 2 
         • A brief description: This repo will host the source code for the HW (HellowWorld) demo xApp that demonstrates how to utilize the different RIC capabilities from a C++-based xApp (HelloWorld A1 policy, HelloWorld E2 SM, RMR, SDL, O-1 config). This demo xApp will also implement the A1 health check.
         • A list of committers:
      2. Ron Shacham, rshacham@...
      3. Shraboni Jana, sj492a@...
      4. Scott Daniels, daniels@... 
      5. VOTE: On motion made by Matti Hiltunen
         1. Seconded by user-2057e
         2. VOTE: Vote taken, item passed

   2. Repo Request - portal/nonrtric-controlpanel - 2nd reminder John Keeney

      1. Hi TOC members,

         Please prioritise the request below. Thanks Jack for your previous reply.

         Thanks,

         John

         Sent: Wednesday 26 February 2020 13:25
         Subject: Repo Request - portal/nonrtric-controlpanel

         Hi TOC members

         We agreed at last week’s TOC meeting to permit creation of a GUI for the NONRTRIC function. Thank you.

         But we also decided that it  would be ok to change the name, however LF will very likely require the name to be included in the official approval.

         So I am re-submitting the request with a new name “portal/nonrtric-controlpanel”

         I would like to request the following new repo:

         1. Proposed repository name: “portal/nonrtric-controlpanel”
         2. License: Apache 2 
         3. A brief description: This repo will be used for the NONRTRIC GUI – for visualising and manipulating NONRTRIC concepts such as A1 Policies/PolicyTypes supported in RAN, R-APPs, etc.
         4. A list of initial committers:
            a)  John Keeney, John.Keeney@... , lfid: JohnKeeney
            b) Patrik Buhr, patrik.buhr@... , lfid: PatrikBuhr

         Note: NONRTRIC GUI  functionality already exists in nonrtric repo. This new repo will be the new home for this.

         Thank you in advance

         John Keeney

      2. VOTE: On motion made by John Keeney
         1. Seconded by user-2057e
         2. VOTE: Vote taken, item passed

   3. New committers in SIM project - E2 and A1 repos request from Alex Stancu

      1. Dear ToC members,

         I would like to request approval for some committer changes under the SIM project:

         1. sim/e2-interface repository
         • Add new committer, because we want to move the E2 Simulator from INT project to SIM project. Harry is the main E2 Simulator developer, so we need to add him as a committer to the SIM project.
         1. First new committer
         • name: Harry Tran
         • email: tuyen@...
         • company: AT&T
         • Linux Foundation id: harrytran
         • timezone: America/New York (GMT -5)
         2. sim/a1-interface repository
         • Add new committers, because we want to move the A1 stub simulator from NONRTRIC project to SIM project.
         1. First new committer
         • name: 'John Keeney’
         • email: 'John.Keeney@...’
         • id: ‘johnkeeney'
         • company: 'Ericsson Software Technology’
         • timezone: 'Europe/Dublin’
         2. Second new committer
         • name: 'Maxime Bonneau’
         • email: ' maxime.bonneau@...’
         • company: 'Ericsson Software Technology’
         • id: ‘maximesson'
         • timezone: 'Sweden/Stockholm’

         Many thanks in advance!

         Kind Regards,
         Alex
         O-RAN-SC SIM project PTL

         --
         Alexandru Stancu, PhD
         Senior Software and Telecommunications Engineer
         
         Skype: stancu.liviualex
         E-Mail: alexandru.stancu@...
         Web: https://www.highstreet-technologies.com
         
         highstreet technologies GmbH
         Hähnelstraße 6
         12159 Berlin

      2. VOTE: On motion made by Alex Stancu
         1. Seconded by Jinri Huang
         2. VOTE: Vote taken, item passed
6. Marketing of the Amber release (WG, LF, PR)
   1. O-RAN Alliance  Feb 17-21 (Paris) F2F canceled and now virtual meeting schedule published
   2. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
   3. Jinri is plannng the virtual O-RAN demo at the end of this month.
7. Status of Open Action Items (Old Business)
   1. Action/ user-59b16 Start an email chain with Viavi regarding how much will it cost and value are we getting?
      1. Viavi is putting together a proposal.  
      2. Jack - I'd like to see it hosted in the cloud so different teams can use it.  It will easier and open access.  Were they OK with that plan? 
         1. Yes, but there may be a cost associated with it.  Viavi will reach out to Jack and discuss offline.
   2. Action/ Jinri Huang will share slides to set up projects using the O-RAN SC regarding the Open Data Set project from O-RAN TSC.
   3. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
   4. Action/ user-59b16 update TSC with the short/long term UE emulator support.  
   5. Action/ David (DT) we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
   6. Action/William DIEGO  will talk to the focus group regarding test coordinator for the O-RAN SC.
      1. William - Participated last Monday and will provide more information in the coming meetings.
      2. Jack - David and William touch base with Rittwik regarding the Viavi emulator.
   7. Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
   8. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release.  Jinri will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
   9. Action/ user-a934b work with Lusheng to create the test cases for O-CU.
   10. Action/ Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.  
8. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
   2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
         1. There are about 17 epics where one is listed as done.  
            1. Jinri - there is an issue for the RICApp project.  Jinri will communicate with Matti offline.  Thoralf will respond to Jinri's request regarding the issue.  Matti Hiltunen document the copyrite issues as a part of your ongoing summary of the project.  There is a recording of the RSAC presentation.  
      2. Thoralf Czichy RIC Platform (RIC) 
      3. user-a934b O-RAN Centralized Unit (OCU)
         1. Action/ user-a934b update the Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues.  
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
         1. Have a discussion with Jack regarding the 
      6. Martin Skorupski Operations and Maintenance (OAM)
         1. Will update the pie for non real time RIC.
         2. For OAM we are focusing on Bronze release.  
         3. For NetConf is challenging and we spoke at the F2F client.
         4. Development and deployment for SMO Bronze.  We need better documentation.  In addition we are having public URLs and public service available.
         5. Jinri - Defining SMO functions.  
            1. Martin I am not defining them I am looking at deploying them.
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
          1. 148 issues and tasks. Large number of subtasks have been closed for test coverage and sonar scores.  Jira workflows are different across different projects such as O-RAN.  Our epics span releases. Upcoming sprint we are focusing on use case and design and architecture around rApp.  We will be defining what the rApp is.
             1. Jack - Across the board we need a metric on how many issues tasks are targeted in Bronze.  Suggestions?
             2. John - Trust the feedback from the PTLs that user stories and tasks are being delivered on time.
             3. Tracy is late with setting up the meeting with David Mc Bride.  
      11. (TBD) O-RAN Radio Unit (ORU)
   3. user-59b16 Requirements Software Architecture Committee
9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
10. Planning for Next Meeting
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)
    1. Actions
       1. Action/ Jinri Huang will share slides to set up projects using the O-RAN SC regarding the Open Data Set project from O-RAN TSC.
       2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
       3. Action/ user-59b16 update TSC with the short/long term UE emulator support.  
       4. Action/ David (DT) we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
       5. Action/William DIEGO  will talk to the focus group regarding test coordinator for the O-RAN SC.
       6. Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
       7. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release.  Jinri will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
       8. Action/ user-a934b work with Lusheng to create the test cases for O-CU.
       9. Action/ Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.  
       10. Action/ user-a934b update the Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues.

Return to Todays Agenda ^

Archived Meetings