Technical Charter for O-RAN Software Community

06 03

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

4. Review of Today's Agenda

5. Preparation for Bronze

   Release

6. Insight Team

Release Votes and Approval

7. Copyright updates

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

   1. Bronze Release PR

   2. Virtual Exhibition.

   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
   2. Action/ TOC members vote to approve Martin's email for a new repo request.
   3. Action/ Rittwik: Share the spreadsheet with Jinri and Yingying.  Regarding the topic of O-CU 5G status.

   Standing Agenda Items (Brief Status of Ongoing Activities)

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

      1. Bronze Timeline

      2. Review Bronze Release Highlights
      provide the Insight slides to Farheen Cefalu
   2. Action/ PTLs provide one or two bullet highlights worth including in the press release.  It does not have to be long.  One or two sentences one or two bullet points.  03 Jun 2020 Should include statements from any company's.

10. 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 (

    5. user-59b16 Requirements Software Architecture Committee

    6. user-d3360  Integration and Test

    7. 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)

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

12. Planning for Next Meeting

13. Any Other Business (AOB) 

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

Anchor
previous_meeting previous_meeting

2020 05

27

Zoom Recording: 2020-05-2027_toc_audio_only.mp4m4a

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	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 there were no comments, questions or correctionscorrected by Farheen who replaced Jean-Paul name where Juha had seconded last 20 May 2020 meeting minutes approval vote.
      1. Vote to approve minutes for 13 20 May 2020 
      2. On motion made by Jinri HuangJuha Oravainen
      3. Seconded by John-Paul Laneby Ganesh Shenbagaraman
      4. VOTE: Vote taken, item passed

4. Review of Today's Agenda

   1. John-Paul We would like to nominate John Keeney as the alternative contact for Ericsson.
   2. Martin has a request open for a repo and would like to discuss the Cherry release.

5. Release Votes and Approval

   1. Martin Skorupski adding a repo for TR-69.  
   2. Martin: We developed an adaptor.  We have 3 approvals we need 5.
   3. Action/ TOC members approve Martin's email for a repo request.
   4. Jack: Is TR-69 RU or DU?
      1. Tracy: The notion here is that since TR-069 Broadband's CPE planned management protocol 3GPP standard we are referring to an TR-069 adaptor to integrate into the O-RAN architecture. Most indoor / outdoor are speaking this TR-069 small cell solutions.  Not just Com-scope.  This complies with all 5G TR-069 communications.  This is the universal adaptor for this so all will interface.  It is operator selectable.  Some will select TR-069 others will use the O-RAN interface. 
      2. Jack: Is Com-scope getting proper credit.
      3. Martin: They are contributing the code and I will make sure they are aligned with all Linux Foundation licenses and will make sure they get the credit.
      4. Jack: Is TR-069 approved as an option under release?
      5. Tracy: This is coming under the O-RAN specification.  It will be included with multiple data models.  The TR-61 will be in the modeling specification.
      6. Martin: It was adapted by 3GPP and WG1.  They want to align their modeling topics with 3GPP.  It fits into O-RAN.  
      7. Jack: This is good it touches the aspect of touching networks and getting them going.
      8. Ganesh: Is this related to the data models?  This supports multi data models.  Which data models?
      9. Martin: TR-96 and TR-181. 
      10. Tracy:  If interested the first and global plugfest slides are on the O-RAN wiki.  I'll send the link in the chat.  Their demo is in the O-RAN virtual information.
          1. CHAT: From Tracy van Brakle (AT&T - WG1) to Everyone: (08:17 AM)
             
https://oranalliance.atlassian.net/wiki/spaces/TTIFG/pages/519208969/PF1+North+America+and+Europe+Presentations?atlOrigin=eyJpIjoiNTY3NzUyNzNjNzM2NDZhMWI5N2ZiYTE1OGVkNmE4YmUiLCJwIjoiYyJ9
 link to CommScope slide from 1st O-RAN PoC/Plugfest in December 2019

             From William Diego (Orange) to Everyone: (08:26 AM)
             
E2E test framework draft: https://oranalliance.atlassian.net/wiki/spaces/TTIFG/pages/480542932/Draft

             From ENG WEI KOO (VIAVI) to Everyone: (08:29 AM)
             
thanks William you are fast! appreciate it
      11. Jack: This covers the small cell items but the CU and DU will be under the O1 specifications.
      12. Marin: Yes
      13. Jack: TSC had a vote on approving Intel binary usage as part of the DU Low.  The vote closed last Friday.  It got only positive votes.  I sent a note to Zbynek who is the project lead? of the O-RAN Alliance looking for a statement that it has passed.  I have not gotten that statement from him yet.  I don't know how many votes needed to pass.  There are 15 passed votes.  I am waiting for confirmation from Zbynek.
      14. Jinri: I can confirm.
      15. Jack: We will consider that an approved vote for people who want to implement Flex-ran implementation around integration and test as an initial working DU at the end of maintenance assuming that we don't have further delays.
6. Copyright updates
   1. Jack: As i described last week there was a vote with the board on an initial copyright request.  Jinri did it get reviewed or is it still in process?
   2. Jinri: It is not officially approved yet.
   3. Jack: An updated one was brought forward that addresses all of the open source software needs.  They are updating and going through the process email vote. The process has started Stephan has introduced it for the vote.  The board votes by mail and it takes a few weeks to vote through that process.  Any questions:

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

   1. Virtual Exhibition.

      1. Jack: The bronze release will be coming out mid next month.  We've heard from companies that want to add a statement as a part of the release.  We're working on writing comments in the release on capabilities please send Jack and Jinri a note.  We are starting to pull together the body of the content for the release.   Once we get something together we'll be adding the comments.
      2. Jinri: Just a reminder tomorrow will be the deadline for the A1 review of O-RAN Alliance for June but so far I have not gotten feedback from anyone.
      3. John-Paul: Ericsson will submit later today to Paul Smith within the deadline.
   2. 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
      1. William: I sent an email two days ago in order to complete info on our test integration end to end test specifications.  We are working on that.  We expect to have the final version in two or three weeks.  
      2. Eng Wei Koo: We have to get together with Lusheng to get thru the contribution to ask for help.  I sent it out a draft.  I can send to this team.  We came together for this discussion and will get it together for next week.
   2. Action/ William DIEGO and user-59b16 lead the effort to organize a long term discussion with Viavi about the coordinated view of the test group and their activities.
   3. Action/ Jinri Huang status of the O-CU 5G contributions to repos.
      1. Jinri: For the O-CU part will be from ICT.  They are in the process of signing a CLA and are getting their F1 code ready.  They will create a repo and update the code once CLA is signed.
      2. Rittwik: Will there be testing for Bronze release?
      3. Jinri: No.  
      4. Rittwik: Will there be ODU High?  OCU should look at a spreadsheet.  Action/ Rittwik: Share the spreadsheet with Jinri and Yingying.
      5. Jinri: As far as I know ICT attended last weeks meeting.
      6. Rittwik: Yes, they were listening in.  He should see the spreadsheet.
      7. Jinri: If you have his email you can send the spreadsheet directly to him and cc me.
      8. Jack: Are they a member of O-RAN or are they just going to contribute to OSC?
      9. Yinying; they are a member or O-RAN Alliance and WG8.
      10. Jack: At some point it would be good to set up a meeting with RSAC committee about laying out the timeline and feature roadmap.  I know it is a larger component with different section so people have a better understanding of how it will progress.  It is very important for the overall project.  Thank everyone for their efforts for bringing that forward.
   4. Action/ TOC continue last weeks review of projects.
9. 1. Preparation for Bronze Release
      1. Jack: I added this item for the preparation for the Bronze Release.  
      2. Trishan: We have the Insights team on today.
      3. Chat: From Trishan de Lanerolle (LF) to Everyone: (08:30 AM)
         
https://lfanalytics.io/projects/o-ran

   2. Insights Team
      1. Shubhra Kar  (CTO Insight) sharing a deck.
      2. LF planning to launch Networking Project this year.  Reviewing short term and long term roadmap.  Have been working with PMs for the Networking Project.
      3. Birdseye view of what they are trying.  LF foundations automation platform.  Security scanning, single sign on service.  Wrap zoom around security layer.  Analytics will go deeper today.  We have easy CLA tools.  
      4. We have been writing automation around asset management, voting, and PM service.  We announced crowd funding service and more.  The goal it to build a centralized platform to provide services in the platform lifecycle.
      5. There is an IP automation part. 
      6. Today we are going to talk about Insights.  It is still early.  It is our V1 version.  What are we trying to solve.  1. members, 2. Projects, 3. contributors.  We want to look at employees impact.  We want to see activities going up or down.  For the projects you want to grow the community you want to measure health.  Also, optimization is built in.  While youre collecting data is the data secure?  Email addresses are they stored in GDPR and privacy policies.  Look at contributors commits and backlog working in sprints.  However, can the contributor think about security?  Are there security metrics available.  In the version1 we haven't integrated our license yet.
      7. This is home grown.  LF needed to rely on third party tools.  This has been built for LF community and all the projects under LF umbrella.  Large team supports this from operations perspective.  It is GDPR compliant.  Features are the multi dimensional views.  From a support perspective we are putting a support structure and offer weekly office hours from our engineers. 
      8. We are gathering our metrics around commits and issue tracking.  We aggregate on a daily basis.  We have automated the instrumentation.  So if a project adds another data source tomorrow we can add it without a lot of overhead.  We are building custom dashboards on kibana.  Two challenges are identiy management. No consistency in contributors ids.  How do we unify an identity of a user and refer back to one person.  For member companies you want that credit to be applied to the company.  How do you affiliate the contributors to these companies?  There is no source of truth.  We have a solution of how we manage through an administrative console.  As we build it out we are scaling into a self-serve platform.  We have put access rules into place.  These are the data sources.  We have projects moving into gitlab.  Issue tracking systems.  Bugzilla in jira.  If you are using jenkins in your builds we have instrumentation that is pulling that data.  As well as Slack, Jira, Confluence, Github Issues,...
      9. John-Paul does there need to be a design time update from the team or our own reports?
      10. We do create templatized dashboards.  If you want to visualize data in a custom view you can download anonymized data and voting dashboard, we have that instrumentation.  We have sprints we work on the design and put it on staging get user acceptance and move it to production.  
      11. Jonh-Paul so as a company we could run a query across a number of projects.
      12. Shubrah: You can we are coming up with an out of box dashboard that will be released in fall.
      13. Shubrah showing a demonstration.  Watch the recording.
      14. When will it be available to use?
      15. V1 is available right now.  If you look at the site.  There is a roadmap and newer views we are building for code pipelines.  There is a role out plan PMs in the Networking team.  We are doing waves and sign off.  Wave 1 was presented.  Wave 2 we want to give to O-RAN. There are others.
      16. Jack: can we have these slides.
      17. Action/ Trishan de Lanerolle provide the Insight slides to Farheen Cefalu
      18. David McBride: We split the schedule into greenfield project that don't have a developer O-RAN tool.  Last week we talked to CNTT this week FIDO, O-RAN...
      19. These are the projects that have developer tools.
      20. Shubhra: PMs are validating their data.  This is UAT.
      21. Jack: Is there a best procedure for closing these unknowns?  How we do that?  Is there guidance?  
      22. Shubhra: Trishan is one Admin who can work on affiliation.  We have a filter list.  
      23. Trishan: We can add a couple of members in the community add them and then merge it back in.

   3. Bronze Release PR

   4. Virtual Exhibition.

   5. OSC Logo status.

10. Release Votes and Approval

    1. Jack: Any items open for votes and approvals?  What is going to happen here is we are going to have a Go No Go vote on the Bronze release.  Today is not the right day yet.  The B release is supposed to happen on June 14th.  Next week we should have a go / no go vote on the software release and press release.  We have work to finish if we plan to release on time.  That would mean the press release will come out Monday June15 or Tuesday June16.
    2. Jinri: For the press release the O-RAN Alliance is not quite sure if we will have a separate PR for Bronze release or mid year press release for O-RAN Alliance.  I plan to bring this up in todays EC call.
    3. Jack: That is fine where the mechanics are when we release the info but the preparation of the documentation and released will stick to the time line.  We are finishing up end to end testing this week and we'll have to decide if we are ready for a release on the 14th.  That will give us time to pull together documentation and additional work for the Bronze release.  One of the things we have to finish up gathering for B.  We have to have our testing complete and the package to pull together.  We'll discuss here how EC wants to release the information but for us we want to make sure we have the information ready for the press release.  
    4. Jinri: Before hand preparation for information.  In the press release we want to see the high lights.  It is OK to ask the PTLs to provide 2 or 3 bullet points that they would like for us to highlight in the press release.
    5. Action/ PTLs provide one or two bullet highlights worth including in the press release.  It does not have to be long.  One or two sentences one or two bullet points.  03 Jun 2020 Should include statements from any company's.
    6. Jack: I will be out next week.  Lusheng will be my proxy.  Jinri could you run the meeting?
    7. Jinri: Yes, I think so.
11. Copyright updates

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

    1. Virtual Exhibition.

       1. Jinri: There was an OSC related demo submitted to working group 1 O-RAN Alliance.
       2. Jiri: There is the virtual exhibition will last 2 weeks.  The OSC have two time slots on Monday June 8th.  Cherry release kick off discussion.  Row #13 OSC line.  The first item is the Cherry release kickoff 2 timeslots on Monday. Next topic Viavi on Tuesday.  This is based on what I collected before.  There is third one that is proposed by WG8 but they request us to join this discussion.  The question to you and Rittwik just to confirm that we do need these two slots that we have required.  We can attend.
          1. How long is the slot?
          2. One block is one hour.  2 hours for Cherry release.  Starting time will be 8AM EST.
          3. Rittwik: Does this clash?  You have WG1, 2, 3.
          4. Jinri: They will join this topic.  WG1, WG2 is the entitiy who requested across this discussion followed by the topic.
          5. Action/ Farheen Cefalu add the spreadsheet to the Events page.
          6. Jinri: The latest one is the one I sent to you, Rittwik and Lusheng.
    2. 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
    2. Action/ TOC members approve Martin's email for a repo request.
    3. Action/ Rittwik: Share the spreadsheet with Jinri and Yingying.  Regarding the topic of O-CU 5G status.

14. 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)

    Standing Agenda Items (Brief Status of Ongoing Activities)

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

       1. Bronze Timeline

          1. Jack: We're into ETE testing and documentation.  We should be planning an O-RAN demo of the capabilities of the Bronze release.  Things are sliding a bit.  We should be looking at inviting the WGs and members of O-RAN to see the release features.
          2. Lusheng: I have two items.
             1. One is report status of testing.  We're making good progress.  Most complex flow health-check made good progress.  Waiting for the Hello World xApp.  O-TU is able to talk to non real time RIC.  We're waiting for the Hello World xApp to be ready for testing.
             2. Matti: The gap was we didn't have the image being generated and the developer of the xApp was going to talk to someone to set it up.  It should be there or else let me know.
             3. Lusheng: I couldn't find any documentation for this xApp.  Do you have policy that will work with Hello World?  We can add/delete policy into A1 only applicable if we have the policy.
             4. John Keeney: We saw the body of the policy but not the schemas.
             5. Jack: We have some work to do here.
       2. Lusheng: There are 2 health-check flows that requires OAM artifacts.  We were able to deploy Frankfurt but had some difficulty with the other.
       3. Lusheng: for the traffic steering use cases we have the docker images on the nexus repos we should be able to start testing very soon.
       4. Lusheng: The O-DU lab testing we're getting a lot of help from Intel.  The cards that Intel contributed are having issues and we are debugging.
       5. Lusheng: We made a plan for the CI Flow and O-DU.  there are some CI flows are not being used because the Intel compiler will not allow.  Also testing requires particular LF software that is not good for that.  We will use CI flow using LF.  We will do the other tests in the lab.  we are planning to finish this by the maintenance release.  In addition to us other LF are using this process.
       6. Jack: Did you mention there was test framework code that would be available to the test group?
       7. Lushgen: Yes, there is OTF open testing framework ATT contribution repo IP/OTF because open source available for TGIG and OTIG.  If they have special requirements to build demos or goals we will work with them.
       8. Review Bronze Release Highlights

    2. user-59b16 Requirements Software Architecture Committee

       1. I received input from infra, testing teams for Cherry release.  Also had a good discussion with John Keeney.  There have been discussions with O-RU O-DU and some activities going on there.
       2. Jinri: Regarding software rental from Viavi.  I sent the request to TSC co chair.  It was not brought to EC but I will keep pushing.  How is the progress?
       3. Rittwik: Technical work is continuing. Viavi wants to get the work done.

    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)

          1. Bug fixing and testing before Bronze release.  WE are seeing scale and roundtrip times through the nonrealtime ric and controller.  As we scale up to 10x and 100x.  https support and ipv6 support has been keeping us busy with integration and test.  Cherry we've been chatting with Cherry release.  We will continue to discuss in RSAC in the coming release.  One way of improving there is no SMO project which is ONAP we are finding that we will we working with Cherry. 
          2. Jack: It doesn't mean that there wont be a project. At some point we will have to address but we dont' have enough working pieces to work on the higher level. 
          3. John: We have better alignment.

       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)

          1. Jack: How are things going?
          2. Zhimin: We are quite busy to prepare release package.  We are doing the final security and quality review and then we can go upstream.  For Cherry release our committee requirement and integration with other project feature perspective.  The O-DU low was support the typical config.  We have doubt about going to the Massive MIMO or not?  We have a doubt here and would like to know what is the community requirement for O-DU low.  
          3. Jack: That should be worked through the RSAC committee.
          4. Rittwik: We have a pretty good idea of O-DU Low and High.

       7. Martin Skorupski Operations and Maintenance (OAM)

          1. I was looking to the Cherry release.  In bronze we depend on the models in order to have nice implementations ready.  We didn't get something from O-RAN in time we are pointing to models that are readily available.  We have to move on because this complicates the components.  All the software I had in mind for the O-RAN sC is in Open Daylight and ONAP.  It looks like my team has to move into the modeling teams of O-RAN Alliance so we can have some models available for SC.  Basically for Cherry release ONF is now coming up with a near RTRIC project they are asking for models.  I don't have many models to offer in the Cherry release.  I don't know what to contribute in terms of software.
          2. Jack: Modeling is a critical issue.  Let's put this on the table for further discussion.  Jinri let's highlight on the O-RAN Alliance side that this is a blocker for this space.  We have to come up with a strategy.  Let's chat on the side and see what we can come back with from that community.  Rittwik this effects your items as well.  Let's make it clear what our blockers are in this space.
          3. Martin: I am aware so I started working with 
          4. Tracy: I have some slides that describe the status open issues.  When you discuss this with the O-RAN Alliance folks these slides show progress and pitfalls.  One of our problems not a lack of models but too many models.  It is good to import models as long as they integrate neatly across a common framework makes it complicated.
          5. Jack: Is that something you can share on the wiki?
          6. Tracy: Yes. 
          7. Jack: 2022 is a long way out.
          8. Tracy: We're following Agile there is a spec and models.  example O-1 TR adaptor is based.  The models where the open front haul.  We are not where we need to be with A1, A2 and O1 is still a work in progress.
          9. Rittwik: What about the impact to simulation.
          10. Martin: I made tutorials.
          11. Jack: If the PTLs feel it is time for them to move on then let us know and we will find others to take over.  It's been a year and it is not unusual.

       8. Alex Stancu Simulations (SIM)

          1. We are still struggling with the E2 simulator.  We will work with the data from AT&T and will continue progress in the maintenance release for the traffic steering use case.  For Bronze release it will be for data pipeline will move to bronze maintenance and xApp testing will happen in Bronze.
          2. Jack: Samsung status?
          3. Rittwik:  I will follow up with Samsung.  Lusheng may know more.

       9. Xiaohua Zhang Infrastructure (INF)

          1. Enabled Ansible bootstrap so we have an all in one single server solution.  In Cherry we will extend single server solution to multiple.  There's another target to do interoperability to do O-DU High, Low to be used by the infrastructure.

       10. weichen ni Documentation (DOC)

       11. Everything looks good.  There is a lot of help from each project preparing the documentation and I am preparing the documentation branch for bronze release. 
       12. Jack: Is there an overview document?
       Weichen: I am creating for Bronze.

       13. (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

    1. Jack: prioritize the test teams efforts.  Support Weichen with documentation.  Continue discussion with the RSAC committee with O-RAN to get  things done.
    2. In two week on June 3rd I'll be out.  Jinri if you will be available please lead the meeting and Lusheng will be my proxy.

17. Any Other Business (AOB) 

18. Any Other Business (AOB)

    1. Keep working towards completing our tests.  Get back to Lusheng to assist with integration work.  I appreciate everyones efforts and see if 

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

    1. Votes
       1. The minutes of the prior meetings were reviewed, and corrected by Farheen who replaced Jean-Paul name where Juha had seconded last 20 May 2020 meeting minutes approval vote.
          1. Vote to approve minutes for 20 May 2020 
          2. On motion made by Juha Oravainen
          3. Seconded by Ganesh Shenbagaraman
          4. VOTE: Vote taken, item passed
    2. Actions
       1. Action/ Trishan de Lanerolle provide the Insight slides to Farheen Cefalu
       2. Action/ PTLs provide one or two bullet highlights worth including in the press release.  It does not have to be long.  One or two sentences one or two bullet points.  03 Jun 2020 Should include statements from any company's.

    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 13 May 2020 
          2. On motion made by Jinri Huang
          3. Seconded by Jean Paul
          4. VOTE: Vote taken, item passed
    2. New Action Items
       1. Action/ William DIEGO update on the coordination with the O-RAN test group
       2. Action/ TOC members approve Martin's email for a repo request.
       3. Action/ Rittwik: Share the spreadsheet with Jinri and Yingying.  Regarding the topic of O-CU 5G status.