Technical Charter for O-RAN Software Community

2020

07 01

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
   Ericsson	John-Paul Lane		John Keeney
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Nokia	Juha Oravainen		Thoralf Czichy
   Orange	William Diego		Vincent Danno
   Radisys	Ganesh Shenbagaraman		Sachin Srivastava
   Verizon	Viswa Kumar		Kristen Young

   *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

   1. Samsung released the KPIMON xApp under Apache 2.0 license in the Amber release. However,  the team  has been advised by Samsung legal team that for the KPIMON enhancement in Bronze release should use O-RAN FRAND S/W license.  Since only one license is allowed within a repo and the repo name depends on the license, we request a new repo: scp/ric-app/kpimon. The committers are the same as the existing KPIMON repo.

      KPIMON xAPP:

      • Proposed repository name: scp/ric-app/kpimon.
      • License: O-RAN software license 
      • A brief description: This repo will host the source code for the KPIMON xApp. KPIMON uses E2SM (extended KPM service model) to collect information from the RAN and populate it in two name-spaces (one for cell metrics and other for UE metrics) in the RIC SDL layer.
      • A list of committers:
      1. Jeongyeob Oak, jy.oak@samsung.com, LFID: jyoak
         2. Jun Song, junhyuk.song@samsung.com, LFID: junny
         3. Jinwei.fan, jinwei.fan@samsung.com, LFID: jinwei.fan
6. Copyright updates

7. Marketing of the current release (WG, LF, PR)

   1. Bronze Release PR

   2. Virtual Exhibition.

   3. OSC Logo status.

8. Status of Open Action Items (Old Business)

   1. Action/ William DIEGO update on the coordination with the O-RAN test group
   2. Action/ Jinri Huang notify the EC that the Bronze release has been voted on and approved.
   3. Action/ user-d3360 send Jinri your status slides.

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

   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Bronze Timeline

      2. Review Bronze Release Highlights

   2. user-59b16 Requirements Software Architecture Committee

   3. user-d3360  Integration and Test

   4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

      1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

      2. Matti Hiltunen RIC Applications (RICAPP) 

      3. Thoralf Czichy RIC Platform (RIC)

         1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)

      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. (TBD) O-RAN Radio Unit (ORU)

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

11. Planning for Next Meeting

12. Any Other Business (AOB) 

13. Meeting Summary (resolutions, new action items, etc.)

15. Copyright updates

16. Marketing of the current release (WG, LF, PR)

    1. Bronze Release PR

    2. Virtual Exhibition.

    3. OSC Logo status.

17. Status of Open Action Items (Old Business)

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

    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

       1. Bronze Timeline

       2. Review Bronze Release Highlights

    2. user-59b16 Requirements Software Architecture Committee

    3. user-d3360  Integration and Test

    4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

       1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

       2. Matti Hiltunen RIC Applications (RICAPP) 

       3. Thoralf Czichy RIC Platform (RIC)

          1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)

       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. (TBD) O-RAN Radio Unit (ORU)

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

20. Planning for Next Meeting

21. Any Other Business (AOB) 

22. Meeting Summary (resolutions, new action items, etc.)

2020 06 24

Recording: 2020_06_24_toc .mp4

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

2020 06 17

Recording: 2020_06_17_O-RAN_SC_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

   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

   Kristen Young

   Nokia

   Juha Oravainen

   x

   Thoralf Czichy

   Radisys

   Ganesh Shenbagaraman

   Sachin Srivastavax

   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		Kristen Young
   Nokia	Juha Oravainen	x	Thoralf Czichy
   Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava

   Ericsson

   John-Paul Lane

   x

   John Keeney

   *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 Meeting 

   1. The minutes of the prior meetings were reviewed, and no corrections.
      1. Vote to approve minutes for 10 17 Jun 2020 
      2. On motion made by John-Paulby Jinri Huang
      3. Seconded by Juha Oravainenuser-2057e
      4. VOTE: Vote taken, item passed

4. Review of Today's Agenda

   Jack: We will spend time today to vote and approve the Bronze release for 21 Jun 2020 

5. Rittwik: What is the suggestion for the Viavi simulator on the lab.

6. Release Votes and Approval

   1. Last week we discussed delaying Bronze for one week.  We had the press release.  We voted and approved the delay by one week.
   2. Lusheng; With the extension we have completed all the flows for the use cases.  We have started preparing for the release.  A wiki page has been created for tracking the remaining tasks.
      1. Repo must address all finding with the LF legal scan.  There were 3 findings.  2 offending references have been removed.  1 for O-DU project has a resolution but it will take some time.  The resolution will be on Thursday or Friday. After scan seed code 2 GNR scans have to be addressed.  Lusheng will address after O-DU scan has passed.
      2. Binary artifacts will be perpetual.
      3. All the repos must update their release
      4. Bronze branch will be released for all the code.
      5. We are between 80 and 90% completion level for all the remaining tasks.
         1. See Releasing Bronze Tasks to see how we keep track of where everything is.
         2. John Keeney: Which comes first the code or the release?
         3. Lusheng: We have completed one round of passing Bronze release testing.  Previously for the non real time RIC there it was yellow.  The last round of testing passed.  We will do another round of testing after the tasks are complete.
         4. Remaining tasks for Integration and testing teams. 
         5. We are also creating a Getting Started wiki page to stand up their own near real time RIC and non real time RIC.  We will also provide a video of the flows.
         6. We will have a Bronze Release Page
         7. Deferred to Bronze Maintenance Release
            1. US O-DU Low and O-DU High Use Case
            2. Full Traffic Steering Use Case
            3. RICApp xApp raising alarms Use Case
            4. O-DU-LOW CICD
            5. O-CU CICD
         8. Rittwik: This is pending the emulator decision because the input to the KPIMon is dependent on the emulator or else it is not a full traffic steering use case.
         9. Jinri: Where can I get these slides?
            1. Action/ user-d3360 send Jinri your status slides.
            2. Jack: I wanted to elaborate on the getting started.  I asked a team of people to take a look at the process of starting the procedure.  We found from other projects that it is easier to have a getting started page for new people who are not familiar with the project.
            3. How do we see updates before release and after release?
            4. The deadline for the release is Sunday 21 Jun 2020 
            5. Lusheng: The tarball is the source code for getting the branch at that moment.  The images are self service releasing.  What does it really mean when people release.  We will provide recipe files in the Getting Started.  After a repo has been released and more changes are needed we will maintain the head of the Bronze branch as much as we could.
         10. Given the current status user-d3360made a motion for a go or no go for the Bronze release. 
             1. On motion made by user-d3360 to officially release the Bronze code on 21 Jun 2020 
             2. seconded by Jinri Huang
             3. VOTE: Vote taken, item passed
7. Copyright updates
   1. Jack: O-RAN copyrite usage for O-RAN specifications.  
      1. Jinri: I was late to the last EC.  I will follow up with Zybnek.
      2. Jack: We have not gotten official closure for the vote.  Next week we will get the exact clarification.  On a related topic ETSE approved the O-RAN Alliance use of copyright.  In process and making progress for the O-RAN SC to have copyrights.

8. Marketing of the current release (WG, LF, PR)

   1. Bronze Release PR

      1. We are working through establishing some guidelines for that PR release.  Some of the feedback is we're trying to keep the statements refined.  I was asked to go back and ask the companies to trim to make a crisp statement with a blog are for extended information.  We are working through that with the EC and PR teams.

   2. Virtual Exhibition.

      1. Jinri: I don't have the progress.  I have not seen any email exchange between Zybnek, Paul and me.  Zybnek is working on online.  I will update the progress next time.
      2. Jack: It will come out along with the board meeting.  The opportunity to the community is to show off progress we are making in the O-SC.  It is a good place to show the O-SC software.
      3. John Paul: I heard 19 Jun 2020 is the last day for the deadline communication.
      4. Jinri: Gate 1 is to review.  Gate 2 is PR which has already past.
      5. John Paul: The submission of the actual demo deadline is this Friday 19 Jun 2020 .
      6. Juha: I see the deadline is 19 Jun 2020 
      7. Zhimin: Intel has not given feedback for the PR.  Is it already tracked?
      8. Jinri: It is already tracked.  I forwarded it to Zybnek.
   3. OSC Logo status.

9. Status of Open Action Items (Old Business)

   1. Action/ William DIEGO update on the coordination with the O-RAN test group
      1. https://oranalliance.atlassian.net/wiki/spaces/TTIFG/pages/480542932/1.0+Draft.
      2. William: I will continue to attend the ETE meetings.
   2. Action/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
      1. We had some OSC meetings on this topic.  One was a F2F of all the WGs.  Well over 100 participants attended.  We had a second one on a more detailed discussion on the emulator activities.  We made a presentation and discussed the values.
   3. Action/ Vishnu send Rittwik the slides for the ITU / AiML Challenge
      1. Jack: We did not do too much 
   4. Action/ Rittwik: Post ITU / AiML Challenge slides on the wiki and pull together a team.  Include Thoralf.
      1. Rittwik: I would like to know where we are with Viavi simulator?
      2. Jack: It is at the EC level.  They have been very busy the last few weeks.  It is on the agenda but we have not come to a resolution or a vote at this time.
      3. Jinri: Several EC members had dropped the meeting and not enough time to discuss.  Tomorrows EC call this has been put at the top priority.  The EC members have reviewed the documentation late so they postponed it to tomorrows call.
      4. Jack: More complicated because of the Virtual F2F.  
   5. Action/ Rittwik: I will set up a meeting for ITU AI/ML and pull together a team.
   6. Action/ Trishan: clear all the legal items for the code and figure out what is needed for the O-CU repo creation so the team can continue.
   7. Action/ user-d3360 provide Trishan with the O-CU repo trouble ticket.
      1. The repo was created and since then O-CU has uploaded the code and merged.
      2. Jack: The key is to get that repo added to the analytics page.
      3. Trishan: It should be available after 6 hours of adding the 
   8. Action/ Jinri Huang generate an email to inform Zybnek and EC regarding that we will be delaying the release 
      1. Jack: Action/ Jinri Huang notify the EC that the Bronze release has been voted on and approved.
      2. Jack: We'll start planning for Cherry and Bronze Maintenance release.  We want to look at the end to end use cases that will align the community and O-RAN Alliance forward.  I need to ask for people to look at the requirements and test teams.  Those teams have done two releases and are small.  Typically on projects we rotate people.  We will need new people to step up for the Cherry release or else we won't be able to do all the testing.  It is imortant for all the oprators, vendors, and participants in the community and look to contribute and find a place where everybody an pitch in.  Requirements, Inetgration and Test and requirements will be pulling this all together.  These up front and back end teams need participation with the community ore las we will have do more testing.  I asked the other TOC members to take time to see if there is any where they can contribute.
      3. Jack: We are at the end of our meeting and thanked the team.  DU High and Low made significant progress to make the end to end flow.  We have new code coming in from two areas like TR69 and O-CU code that will bring functionality.  We are looking to Cherry to add more O1 and A1 support so it looks lie a system and not just stand alone parts.  I look forward to new projects such as the SMO work.  There is still a lot to do and participate.  I wanted to thank everybody for all the progress and look forward to watch Cherry

10. 1. Samsung released the KPIMON xApp under Apache 2.0 license in the Amber release. However,  the team  has been advised by Samsung legal team that for the KPIMON enhancement in Bronze release should use O-RAN FRAND S/W license.  Since only one license is allowed within a repo and the repo name depends on the license, we request a new repo: scp/ric-app/kpimon. The committers are the same as the existing KPIMON repo.

       KPIMON xAPP:

       • Proposed repository name: scp/ric-app/kpimon.
       • License: O-RAN software license 
       • A brief description: This repo will host the source code for the KPIMON xApp. KPIMON uses E2SM (extended KPM service model) to collect information from the RAN and populate it in two name-spaces (one for cell metrics and other for UE metrics) in the RIC SDL layer.
       • A list of committers:
       1. Jeongyeob Oak, jy.oak@samsung.com, LFID: jyoak
          2. Jun Song, junhyuk.song@samsung.com, LFID: junny
          3. Jinwei.fan, jinwei.fan@samsung.com, LFID: jinwei.fan
       2. Jack This is a little different because of the dual license.  Is there someone from Samsung project?
       3. Matti: I submitted this request as a RICApp PTL.
       4. Jack: Will the old repo be reitired?  Will contributions be split because of dual licenses?  Do you know how we are going to treat the new license?
       5. Matti: I was wondering that my self.  There are contributions in Amber.  
       6. Jack: Once content is released under Apache the content stays.  Until we get clarification from Samsung, the way I would categorize is we are leaving the existing repo there and archiving it.  Active contributions will go to the new repo and stays in its form.
       7. Peter Moonki Hong: Can I have clarification?
       8. Jack: There has been a request for a new repo and the question I had was what will happen to the old repo.  Typically we would archive and close the old repo and have new repo contributions.
       9. Peter Moonki HOng: When it comes to KPI monitoring xApp we want to leave the repo as it is and archiving the repository.  We will stop contributing to the old repo and start contributing the new repo for KPI monitoring of xApps.
          1. On motion made by Peter Moonki Hong from Samsung to approve creating the new KPI monitor repo and archiving the existing one
          2. David: Was the archived repo Apache only contributed by other than Apache?
          3. Peter: Motivation is to change their direcition to the FRAND license.  
          4. DAvid: All the code is 100% contribution from Samsung.
          5. Matti:  It's copyright AT&T and Samsung. 
          6. David (DT): This is a lawyer question.  If it all code by one company then they can release under new license but if there is code from another company then needs clarification from lawyers.
          7. Jack: This is a new occurrence.  The AT&T code would still be under the Apache license and anyone can continue to use it going forward.  It is released under Apache.  To create the new repo it becomes a mixed repo that has pulled code from the Apache license and made into O-RAN license.  I'll have to get clarification on what that means.  Action/ John Murray get clarification regarding transfer of AT&T Apache code into the new dual license repo.  General rule in the past is the most restrictive license dictates the combined code follows the most restrictive license.
          8. Lusheng: Will AT&T continue contributing to the SCP repo?
          9. Matti: No we had the admission control xApp but the person who wrote the code has left AT&T.  I don't see any reason for the Amber release repo to carry on.
          10. Jack: It will be archived and the code is available for people to use.
          11. Lusheng: LF does support making a repo read only (archive) to use for the KPIMON.
          12. John Keeney: I presume it's possible for people who have branched the code can continue using?
          13. Jack: That's why it is archived.  It follows the Apache usage rules.  The new repo will use the new license with the new contributions with what they pull forward from Apache under O-RAN restrictions.
              1. On motion made by Peter Moonki Hong from Samsung to approve creating the new KPI monitor repo and archiving the existing one.
              2. Seconded by Jinri Huang
              3. VOTE: Vote taken, item passed
    2. Summary Bronze Release
       1. Lusheng: We have completed the remaining tasks for the release.  The detailed status is reported on the Bronze Release (Jun 2020)
          1. New Getting Started guide
       2. Jinri: Expresses his sincere gratitude for the hard work.
11. Copyright updates
    1. Jack: Did we get an official approval of the copyright yet?  
    2. Jinri: I believe the voting results have come out.  The EC has not announced.
    3. Jack: We will get clarification on the EC call today and let everyone on this team know about the copyright permission from the O-RAN Alliance material.

12. Marketing of the current release (WG, LF, PR)

    1. Bronze Release PR

       1. Jinri: Preparation for the virtual exhibition is done.  I have the website link to the virtual exhibition.  There are 13 new demos uploaded to the O-RAN virtual exhibition website.  Among the 13 there is one from our open source community provided by Ericsson and their partners.
       2. Jack: Do you have to be an O-RAN member for the virtual space?
       3. Jinri: No it is a part of the O-RAN website.
       4. Jack: The Bronze PR activity is ongoing.

    2. Virtual Exhibition https://www.virtualexhibition.o-ran.org/

    3. OSC Logo status.

13. Status of Open Action Items (Old Business)

    1. Action/ William DIEGO update on the coordination with the O-RAN test group
       1. Jack: There is an open item from for the EC to work with the test group on a discussion around the emulator/simulator needs.  We need to coordinate that.  I got an email but am not sure where we are in the process of meeting.  We need to meet to work out a longer approach.
    2. Action/ Jinri Huang notify the EC that the Bronze release has been voted on and approved.
    3. Action/ user-d3360 send Jinri your status slides.

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

    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

       1. Bronze Timeline

          1. Maintenance release is avialable.
          2. Lusheng: We have a request from LF legal to have a formal process to address the use of external source code licenses?  Should we use specific attributions or use a blanket statement.  Action / user-d3360 add the topic of license attributions to the agenda.  We want to start the pairwise testing.
          3. Jack: Use the opportunity to do pairwise testing.
       2. Review Bronze Release Highlights

    2. user-59b16 Requirements Software Architecture Committee

       1. Our hope is to get the lab prepped by 6-30.  We want to get the KPIMON inserted.  We've asked Viavi to monitor a trace file that can be delivered by the end of the month we can make the use case more sophisticated.  That will lead to the Cherry release to run with a real time simulator.  We are counting on Viavi.
       2. The ML enabled traffic steering xApp I want to get a simulator of RAN topology.
       3. rApps and xApps will detail the onflows.  How do you deploy the rApp and put it in run time.  We also have to think about what kind of training and the training pipeline.
       4. How is O-CU going to talk to O-DU.  Introduction of SMO in regards to LCM and pre-release R-1 interface for Cherry will drive R-1 interface for Dawn.  
       5. R-1 interface is for introducing R-Apps.  It is still being discussed in O-RAN Alliance.  Some of it is pre-release and not set in stone.  We can drive requirements down and start the ball roling.  The DU Low and HIgh P7 is going to be integrated.  R-U, D-U, C-U is a challenge.  We've come up with a tentative plan of what the combined configuration.  We will attempt to attach one UE and have a functional RAN element working.  We have to get all the parameters and time.  With HARK disabled can we attach a UE?  It is important to get a functional end to end stack working.
       6. Lusheng: Do you mean simulated or physical UE?
       7. Rittwik: O-R is a simulated but with the real RAN we want a physical UE.
       8. Is there anything resembling and R-U stub for DU-Low?
       9. Rittwik: Yes, there is an R-U stub that is there already.  That is basic functionality.
       10. Tracy: I think you are aware that AT&T will use SMO in stages?  Is it ONAP based SMO?
           1. Rittwik: It will be ONAP based.
           2. I wanted to confirm the basic.
           3. Jack: The SMO is a big box that we've thrown some pieces in. It means different things to different people.  The O-RAN Alliance WG1 leaves it to implementation.  The challenge for us is to decide do we create a formal SMO project or not?  There could be more than one if there's enough support in the community or do we avoid that?  The issue we have to figure out is to make a working thing we need to pull together all the pieces.  If we wrap it with a SMO label.  How do we bring it forward enough so that companies understand how to use the pieces to wrap it together and see how somebody comes out with commercial implementation.  The work is useful if it ends up with multiple providers across the globe.
           4. Tracy: The SMO are components or subset of building blocks.  It has a few components some are being added and dependent on contributor support.
           5. Jack: The SMO needs to be provided by the software community to do the work.  
           6. Tracy: AT&T is not the only operator who wants to start implementing the Phase 1 SMO and have some reassurance that phase 2 SMO can be built on phase 1 SMO.
           7. Jack: Industry trends company's lose interest.  The SMO has to support a range of functionality but also make it easy for this community to build, test, demonstrate and move the community forward.  We will cue this up for the next discussion.
           8. Jack: How are we going to approach pulling the SMO pieces together.  Continue to get the O-DU moving forward.  Looking at how the O-DU and O-CU work together.  What about the O-RU?  Those are more targeted discussions.  As we mature a lot of discussions become complex.
           9. Jinri: TSC requested we work Acumos team for near Real Time RIC development.  
           10. Jack: I will get someone from the project give a presentation here.

    Standing Agenda Items (Brief Status of Ongoing Activities)

    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

       1. Bronze Timeline

       2. Review Bronze Release Highlights
    2. user-59b16 Requirements Software Architecture Committee

    3. user-d3360  Integration and Test

    4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

       1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

       2. Matti Hiltunen RIC Applications (RICAPP) 

       3. Thoralf Czichy RIC Platform (RIC)

          1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)

       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. (TBD) O-RAN Radio Unit (ORU)

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

16. Planning for Next Meeting

17. Any Other Business (AOB) 

18. Meeting Summary (resolutions, new action items, etc.)

    1. Votes:
       1. On motion made by Peter Moonki Hong from Samsung to approve creating the new KPI monitor repo and archiving the existing one.
          1. Seconded by Jinri Huang
       2. The minutes of the prior meetings were reviewed, and no corrections.
          1. Vote to approve minutes for 10 Jun 2020 
          2. On motion made by John-Paul
          3. Seconded by Juha Oravainen
          4. VOTE: Vote taken, item passed
          Given the current status user-d3360made a motion for a go or no go for the Bronze release. On motion made by user-d3360 to officially release the Bronze code on 
       3. 21 Vote to approve minutes for 17 Jun 2020 
          seconded
          1. On motion made by Jinri Huang
          2. Seconded by user-2057e
          3. VOTE: Vote taken, item passed
    2. Actions:
    3. Action/ William DIEGO update on the coordination with the O-RAN test group
    4. Action/ Jinri Huang notify the EC that the Bronze release has been voted on and approved.
    Action/ user-d3360 send Jinri your status slides.

Archived Meetings