Technical Charter for O-RAN Software Community

2020 05 27

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

   *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. Copyright updates

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

   1. Virtual Exhibition.

   2. OSC Logo status.

8. Status of Open Action Items (Old Business)

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

2020 05 20

Zoom Recording: 2020-05-20_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	x	Sachin Srivastava
   Ericsson	John-Paul Lane	x

   *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 13 May 2020 
      2. On motion made by Jinri Huang
      3. Seconded by Juha Oravainen
      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.
   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 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.
      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. 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)

          1. 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. 
          2. Jack: Is there an overview document?
          3. Weichen: I am creating for Bronze.

      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

    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.

12. Any Other Business (AOB) 

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

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

2020 05 13

Zoom recording: 2020-05-13_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	x
   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

   *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 06 May 2020 
      2. On motion made by Juha Oravainen
      3. Seconded by user-2057e
      4. VOTE: Vote taken, item passed

4. Review of Today's Agenda

   1. Add O-RAN Distributed Unit Low (ODULOW) May 31st Bronze delivery request to the top of the agenda because we ran out of time last week.
      1. The question is ODULOW will deliver before May 31st.  Who from the O-DU is going to talk about that?  Is that Zhimin?
      2. Rittwik: I thought it was covered last week.
      3. Jack: They asked if they will be included in this release.  I spoke with Zhimin last night.  The issue is Intel has to go through the Intel review process to get this released. 
      4. Their target is to deliver at the end of May which does not give them time for Integration.  They wanted to put it in their software code in the repo and consider it as a part of the Bronze release.  The code would be untested and un-integrated and finish up during the maintenance window.  This is a discussion for the TOC how we want to proceed.  I had a discussion with Intel last night for improving their process for the Cherry release and adopt open source methods for their software contributions and processes.  They are going back to work those items and express that they will be able to improve them.  In terms of a vote.  The question is assuming that they contribute all the code by May 31 and our final date is June 14 do we consider that code is a part of the Bronze release?  This is a question and the approval that they seek .  It is a question for the whole TOC how they want to proceed.  The code is there and is complete and it stretches things out from how we normally do things.  
         1. Rittwik I think the code is there.  Lusheng please comment.  Are we testing the O-DU low?  There is a bilateral agreement that happened.  Even though it is not open internal pairwise testing is happening.  We set up the servers in the lab to do the testing.  Progress has been made in May.
         2. Lusheng: The Intel team stated source code in the repo is for Amber.  They didn't provide the Bronze code.  They will install the binaries in the lab there and do their pairwise testing and integration with O-DU-HIGH.  That will happen in parallel with the source code.  We are asking for the Bronze release they will put out new version of the source code for their internal process and conclude by the end of May and provide all the unit testing and testing with simulation.  They do have some testing but not integrated with other O-SC components. That was the ask.   In terms of integration building and when integration testing with ODU-HIGH currently are having some hardware issues in labs I do not have an eta due to lockdown and no access to lab.  I can not give a timeline.   If TOC consider this request from Intel it will be where to include the software in Bronze.  The code will pass the unit test for contribution.  I do not know when the integration with O-DU HIGH will happen.  ODU-HIGH integration will happen in Bronze maintenance release.
         3. Zhimin Yuan  What Lusheng and Rittwik said is clear.  For ODU-LOW project can be published by the Intel process by the end of May.  We will pass all the unit test and Layer 2 test 2 will finish unit tests internally.  If we have chance We will use the open lab if able as well.  We are asking for you to include ODU-LOW for the B release.
         4. Jack: For other TOC members are there questions?
         5. Juha: What about the licensing voting that is still ongoing and will be completed next week.  Will that effect this vote?
         6. Jack: It's being used as a test fixture.  It's not  included as part of the software contribution for O-DU LOW but it does mean that what we had to go through to make sure we are cleared to use the intel software in our test lab and recommendation of using the lab.  The community members have to decide if they are interested in the ODU path based on the Intel approach.  The approval is based on license review and everyone is aware that we are using the software.  But it is not a part of the software contribution.  It's more or less to allow us to use it for testing.  Do you still want to wait until after we get the license approval or should we vote now?
         7. Juha: If licensing is not approved then we revisit.  I wanted to understand it a little better.
         8. Zhimin: Regarding the OSC repo we will contribute the shared between O-DU High and O-DU LOW.  We will do integration testing if we are able.

5. Release Votes and Approval

   1. We have a mothing to include the Intel contribution if it's made by 01 Jun 2020  to the repos.  That is the motion that Intel has made.  Vote on including O-RAN Distributed Unit Low (ODULOW) in the Bronze Release.
      1. seconded by Ganesh Shenbagaraman 
      2. VOTE: Vote taken, item passed
   2. If it is not by 01 Jun 2020  or else it will not be included as a part of the Bronze release.
6. Copyright updates
   1. We covered copyright updates in the New agenda items.

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

   1. Virtual Exhibition.

      1. Jinri:  I checked the email and found that  21 May 2020  will be the deadline for WG1 in O-RAN Alliance contributions for the demo.  Contact Jinri for the virtual exhibition.  Paul Smith will organize teleconference and review submissions.
      2. That will be for the end of June virtual exhibition.
   2. OSC Logo status.

8. Status of Open Action Items (Old Business)

   1. Action/ Farheen Cefalu add copyright updates to the agenda. (See item 6 added above)
   2. Action/ Farheen Cefaluadd link to the Virtual Exhibition site.   (Completed on 28 Apr 2020 on Events)
   3. Action/ Farheen add reviewing Bronze release highlights to the agenda (See item 9.ii added below)
      1. Issue for Bronze gets back to the marketing.  If there are companies that want to make statements as a part of Bronze release, it takes time to get them cleared internally and over to us.  We do tha through O-RAN Alliance.  Jinri is our contact for that.  I assume that they will get information to you and we will work on figuring out on the press release and we should have that on the EC meeting as well.
      2. Jinri: They have a communication.  Let's double check with Zhiminik.
      3. John-Paul Lane: Who should we contact?
      4. Jack: Send an email to Jinri and copy Jack.  Jack will get a list together and we'll go from there.  You don't need the complete list.  We want to know everybody's input for tracking purposes.
   4. Action/ Farheen Add the O-RAN-SC logo request to the marketing agenda. (See 7b above)
   5. Action/ William DIEGO update on the coordination with the O-RAN test group
      1. Jack: You heard the feedback from TSC meeting where they want to get a more coordinated view with the test group and the OTIG and other activities.  You can work with Rittwik whose been working with the simulator and anyone else interested in participating in that discussion reach out to Rittwik and William.  I know Viavi will participate.  Since they are the target I'd like Rittwik and William to organize the long term discussion.  We'll follow up on the short term discussion at the Monday EC meeting.  Is everyone OK with that? 
      2. William: Yes
      3. Rittwik: Yes
      4. 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.

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.

      1. Cherry release requirements gathering has started.  I have spoken to Matti, Thoralf, and the O-DU folks.  I am setting up a few meetings individually to gather requirements.  By mid-June we should be in a better position for votes.  TOC should consider what kind of themes the Cherry release will be responsible for.  We will continue traffic steering, and healthcheck use cases.  Things that have not been percolated through all components.  We have a few extra epics.  If the TOC has suggestions then let me know.  
      2. Bronze release the final integration will be done for call flows for healthcheck and traffic steering.  We have truncated some of those flows.  Lusheng understands the subflows that need to be tested.  The RSAC wiki has been updated to reflect this.
      3. Jack: I'd like to continue to see the ETE use cases evolve to drive the community to more ETE operations.  There are OAM capabilities such as healthcheck that continue to advance.  I would hope O-DU and O-CU can start those initial use cases.  I hope we can get a new use case to demonstrate more either near Real Time RIC and xAPPs and non Real Time RIC and rApps activities so we can demonstrate the work that is going on in the non Real time RIC.  I would like to make sure we are pushing the projects forward as a larger system in the general guidelines.  They should be done around useful functions like traffic steering and OAM.  If different people have different use cases then provide the input.  It is key that each release advances the overall stack and elements.  We only do two a year so it is important to push ourselves.

   3. user-d3360  Integration and Test

      1. Gerrit review process improvement
         1. I will table this for now.  We will start it in Cherry.
      2. Integration and testing status report
         
         1. We have a good understanding of the flows to be tested for the Bronze release.
            1. Healthcheck there are 3 use cases to be tested.
            2. Traffic use case has one
            3. O-DU will be planned out as well.
            4. T-lab has near Real time RIC.  We are getting close to making the test call flows.
            5. Integration lab O-DU test hardware installed and cards are installed but we are having hardware compatibility problems that we are looking into. As soon as they are fixed we will install Intel's O-DU Low binary code so O-DU High and Low can continue with integration testing. 

   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) 

         1. Matti: We got a two week extension for RIC App and simulator.  It looks like part of the RIC App traffic steering use case will slide into the maintenance release.  We still don't have the KPI MON from Samsung which has not been tested with the simulator we are planning the maintenance release. We also don't have legal approval.  We have a couple xApps traffic steering use cases will be tested as a part of Bronze release.
            1. Jack: How many xApps  between Bronze and Amber do we have available in open source for people to evaluate?
            2. Matti: In Bronze there are 4 xApps that are reasonably solid.  In Amber we had one xApp Admission Control that we have not upgraded to the latest E2 specs that is left over and does not apply to any of the use cases .  There is a demo Hello World xApp on using a lot of features in RIC such as E2, A1, messaging SDL.  There is a measurement campaign xApp in the Amber release that has been extended to generate more reports based on X2 messages.  We have two xApps related to traffic steering use case that are already in the repo.  Main traffic steering xApp in C++ that drives the QP driver which is pulling the data from the SDL for the ML part.  The ML app is still not in the repo but promised any day now.  It might still be testable before the end of the month.  The KPI MON is bigger because it will use the simulator that Ron just completed.  I expect there will be some bugs.  Our extended code freeze deadline passed.  I want to move this to the maintenance release. 

      3. Thoralf Czichy RIC Platform (RIC) 

         1. Reviewed status on Jira items moved to Cherry.  The links are in the RIC Platform status report.
         2. Thoralf: I went through all the epics and double checked with all the teams.  Of the 65 epics planned for Bronze 36 are implemented as of yesterday.  13 have started that are in Cherry.  9 have not been started to Cherry.  8 more have been moved to backlog.  There is a link for the first phase of Cherry.  We are still planning the second phase of Cherry.  In this first phase we have a list of what will be worked on.  I don't see important dependencies on other project.  If you are curious you can find them for the status report.
         3. Jack: Two of the projects are further along then others.  OAM is also moving along pretty rapidly. We will discuss other projects next week.  The biggest question right now... 
         4. Jack: Jinri is any of the O-CU code going to start making it back to the repos soon for the 5G?
         5. Jinri: I remember contribution started 15 May 2020 for O-CU part I will double check with my colleagues .  Action/ Jinri Huang talk about the O-CU 5G contributions this week.
         6. 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. 

    1. OAI/OSA purposed Meeting
       1. OSA community had a call.  Introductions and I talked about our process.  They talked about where they are in their process.
          1. Overall they were happy with us cleaning up the issue we had with our code in our repos.
          2. They would like to talk about a strategic alliance announcement and agreement between them and the O-RAN Alliance.  I made it clear that it's an O-RAN Alliance activity.  For that particular component should come from O-RAN Alliance.  They asked about copyright use and access to the O-RAN specifications.  One way to do that is if they contribute the interfaces under a project in OSC.  Software contributions can be pulled into the integration process.  They were more interested in people working outside of OSC and maybe interested in participating.  
          3. I described the Intel model on the O-DU.  There is a license issue.  They do have some higher level code in Apache but their lower level code that is in debate follows their license which is different from our license.  There are US universities being funded by the Power project and others that are interested in using the OAI and O-RAN code in make something work.  My concern is if work takes place outside of the community that benefits, much like Intel's FAPI code that can be re-used by the community becomes more complicated.  They told me they have copyright permission from 3GPP material that allows them to generate code.  I will pass that information along to the people who are working for us.  I did not get very positive feedback from 3GPP that is what they were thinking.  I will pass along to O-RAN Alliance 3GPP.  
          4. In the end they were unable to articulate a very strong ask from us.  It is mostly from a copyright and agreement perspective.  They didn't have a plan for software contributions.  Anyone who attended feel free to add or correct. 
             1. Jinri agrees.
          5. It would be great to have more code on a lower layer but that is hard to do.  They are going to go off and think about it and get back to us.  The next steps are between them and Zbynek.  
          6. I am hoping it will turn into something more for the universities that I talked to on the Power project.  Hopefully we will get more university participation.  They don't care about patent rights and 3GPP issues they can contribute to the open project.  Hopefully we'll get more university participation.  Let Jack know if there are any other universities that will contribute.  We should look to expand.
    2. Jean-Paul: The discussion about replicating O-RAN Alliance specifications.  It was brought up as part of the TSC meeting and discussed.  Was that discussed? 
       1. Jack: The copyright aspect of it where we talked about what we can do was the operating feature. 2 votes.  Acceptance of Intel binary software for Flexran to test our approach.  Other was the copyright vote.  Board meeting coming up.  There were 2 issues with copyright approval.
          1. It stalled half way thru.  Not enough board members voted to pass it before a question came up about it.  We got some clarification and I don't know if they had to go back and reset the vote because they changed the wording slightly.  I have to find out.  Both are active.  The vote for O-RAN using Intel ends this Friday.  When I looked at it last there were +10 votes and none against last weekend.  I don't expect a problem.  It has gone into the process where I only know when it comes out.
    3. Rittwik: Can we get an update of the Viavi contract that was discussed in the EC?
       1. Jack: It was brought up as a part of the TSC and discussed. I don't control when they get to the topic.  Jinri was there for that discussion but I was not.  They didn't approve it they kicked it back for further discussion.
       2. Jinri:
          1. Regarding Intel license, the deadline will be this Friday.  Currently we all have the yes vote.  Next Monday will be the EC call for further approval.
          2. Regarding Copyright permission.  I don't have any idea regarding vote process.  Next Monday we can raise on the EC call.
          3. Regarding Viavi contract.  At the time I didn't receive confirmation from Viavi.  This is tentative.  Next Monday is the EC call we will raise this.  I have forwarded this message during the TSC call. 
             1. Jack: Did they have any particular questions...
                1. Jinri: No.They raised a another request for two collaborations.  One is short term collaboration targeted for Bronze release and the other is long term collaboration can be used with WGs, TSC, and OTIC.  For the long term solution the TSC Co chair asked us how we want to use this from OSC perspective.  for example: What software will be needed for Cherry and software for OTIC and other WGs have?  We need to combine these requirements and discuss further before presenting to Viavi.

11. Planning for Next Meeting

12. Any Other Business (AOB) 

13. 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 06 May 2020 
          2. On motion made by Juha Oravainen
          3. Seconded by user-2057e
          4. VOTE: Vote taken, item passed
       2. Vote on including O-RAN Distributed Unit Low (ODULOW) in the Bronze Release.
          1. On motion made by Ganesh Shenbagaraman for the O-DU LOW contribution made by 01 Jun 2020  to the repos.
          2. user-2057e seconded the motion
          3. VOTE: Vote taken, item passed
    2. Actions
       1. Action/ William DIEGO update on the coordination with the O-RAN test group
       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.
       4. Action/ TOC continue last weeks review of projects.