2022 08 25

Recording: 

Meeting Recording:

Topic: Zoom3 O-RAN SC's Personal Meeting Room

Start Time: Aug 25, 2022 09:01 AM EST

Meeting Recording:

https://zoom.us/rec/share/zoj7RVcD_3kGfb_gGQdL_TMkyS24SucF-ng4sa80-wzlSR1sLhZOLUFWT4B9pSqW.cyqdbKKGdQswG1am

Agenda

1. Call for Scribe (minutes owner): James Li

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting (18th August 2022) approval: Motion to be proposed by James, second by John-Paul and the Motion was approved.

2. Review of Today's Agenda.

3. Release Votes and Approval

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. 2022-07-14 : Need to work on clarification for SCCL license and start having O-RAN WG Material.   Refer to the website on O-RAN Alliance and update the charter Following work with TSC for contributing material to be used down stream. Setup a Meeting with Stephan (he needs to approve the CLA). (Action Point : Jinri)

      2. 2022-07-21 : Meeting planned today and there will be update on this topic next week. The current focus in on O-RAN (does'nt cover 3GPP, ETSI etc)

      3. 2022-07-28 : Meeting with O-RAN Legal Team, the draft of the Project Charter as well as CLA are ready. Once the documents are reviewed the same will be added to the process. There is a continued discussion with ETSI and O-RAN WG on how to organize the documents to make them available to O-RAN SC. Documents will be shared on the reflector . Feedback to be provided by everyone after discussing with their respective legal team.

      4. 2022-08-04: Jinri is out sick, hopefully work on that will make some progress here soon as he's feeling better.

      5. 2022-08-25

         1. @Jack Murray: Stephen generated a license and a change to the charter for the O-RAN. We may need to distribute that to the TSC members for review and comments.

         2. @huangjinri@chinamobile.com: I had a brief conversation with Stephen and he mentioned that he can distribute the material to the TOC after a confirmation from @Jack Murray. We can have 2 parallel steps here: one is the review on the legal team, and the other is the review and modification from TOC. We hope to get both done before the October F2F meeting.

         3. @Jack Murray : @huangjinri@chinamobile.com can you distribute the 2 documents to the TOC members?

         4. @huangjinri@chinamobile.com : Yes, I do have the SCCL CLA and the specification code project charter documents and I will distribute. I will need to set the review deadline for the 2 documents

         5. @Jack Murray : Next week is the US Labor Day long weekend so let's make the deadline as 9/8. Minimally we need review from TOC members, but input from others are welcome. @huangjinri@chinamobile.com please post the documents to the reflector.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting (Oct'22)

   2. Plugfest

      1. 2022-07-21 : O-RAN Alliance will initiate the Call for Host on July 24th

      2. 2022-08-11: @huangjinri@chinamobile.com: Call for host for the fall Plugfest has been issued, and there are quite a few applications for host.

   3. Challenges for the OSC community (as report to EC)

      1. 2022-07-14 : There is no update this week

      2. 2022-08-25: @huangjinri@chinamobile.com The first O-RAN spec regarding the Open FH is approved by ETSI MSG. July spec train 60-day review period started. Again, people who are interested in participating the October F2F can contact the host or the O-RAN office.

6. Old business and Status of Open Actions

   1. "F" Maintenance Release

      1. 2022-07-14 : 

         1.  Non-RT RIC Project : Will revert back by next ToC meeting if there is a need for a maintenance release . 

         2. O-DU High also will have some maintenance

      2. 2022-07-21 :

         1. O-DU high upto fixes needs to be merged. 

         2. Target to close this maintenance by 4th Aug

      3. 2022-08-04: @John Keeney (Ericsson EST) Non RT RIC F maintenance is about ready, but found one nasty little bug at the last moment. Should have it done in the next day or two. @Ankit Barve O-DU-highis ready and will upgrade the branch.

      4. 2022-08-25: F maintenance completed. This topic should be closed out.

   2. "G" Release 

      1. 2022-08-25: @Jack MurrayWe need to have Intel to update the G release page to add the O-DU-low content.

   3. OSC Lab

      1. 2022-07-21 : David mentioned that some steps has been provided to zero in on the issues. If not resolved Ganesh from Radisys to provide support 

      2. 2022-08-25: @David Kinsey [AT&T]: The grandmaster clock is now fully functional. Our next steps will be to start looking at that O-CU package to deploy onto an O-cloud instance and probably start working with the near RT RIC to find out what resources we need to build up. @Jack Murray: it might be useful to have a table that just says where we are. 

   4. 5G Super Blueprint status - to be considered for H release.

      1. 2022-07-21 : David  mentioned that there hasn't been any progress on this. Decided to move to H release. (Updated the title header from G to H to reflect the same)

      2. 2022-08-25: 

         1. @Jack Murray we haven't officially taken on anything out of the 5G super blueprint, and it's on the table for H and see if we want to call anything out specifically within our community.

         2. @bwick There is a roadmap for the 5G super blueprint extending out to Q1 of next year. That does include continued integration with the O-RAN elements within the existing blueprint. Is there anyone on this side tracking that, or working towards that in any way? And if not, maybe we could make a connection with that group to explore the evolution of those components, to see if they're still in sync. The second timely thing around the super blueprint is that it's going to be featured at the ONES summit LF Networking in November of this year in Seattle, and the group right now is trying to determine what is the right demo to show, based on the work to date, and how the blueprint has evolved from the last version that was shown. One option looks a little more O-RAN centric. It was building upon a demo given in June by some folks from AT&T and I haven't been in contact with that group since then. I wanted to see if that might be something that group was willing to continue to contribute, so that the O-RAN element was prominent in the demo in the fall.

         3. @Martin Skorupski Alex and I contributed our help, explaining how these components can be used, which was demonstrated in the ONES demonstration. Some are from the OAM and SIM projects which has automatic test cases, a lot of are O1 specific.

         4. @John Keeney (Ericsson EST) The functions that Brandon and Martin are referring to are almost exactly the same SMO integration that we had in the it/dep repo here in OSC up until the E release. I think it's starting to evolve a little bit now with the SMO project, but it basically is an OSC contribution.

         5. @Jack Murray Brandon, maybe you should consider attending some of the RSAC meetings what's the opportunities and how things line up in a little more detail.

         6. @David Kinsey [AT&T] I'd like to put it on our RSAC agenda on 9/7 to discuss what do we want to do with the super blueprint, the ONES summit, and for the H release. If we have somebody from the infrastructure project to make sure they attend that it would probably be helpful too. @Martin Skorupskiplease join on the 9/7 RSAC call.

         7. @bwick I'll attend that, and I'm happy to be the bridge, at least at a high level between these two groups, and if appropriate, I can bring in the the technical program manager for the effort, Lewis, to kind of give an update on where we are. I can also coordinate with Sridhar offline to see how this is all under the Linux foundation Networking umbrella.

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

   1. Release Manager  @Sridhar Rao  /Release Planning: Weekly TOC Scheduling

      1. 2022-08-25: @Sridhar Rao The info.yaml file is accepted, so they just have to merge. So once that is ready the AI/ML project will be get created, and we can create the wiki pages in the confluence. I'm also working closely with @James Li on bringing some of the testing tool or test automation tool to OSC. Hopefully, we will be successful by end of this release.

   2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)

      1. "G" Release

         1. 2022-07-14 : Rittwik: Updated on the AI/ML Project and mentioned that  pro & Con of separate project were discussed and it was agreed to go with new project.

            1. Samsung will commit 3-5 resources for the AI/ML Project

            2. Call Flow, data Model, touch points should be defined

            3. Define the scope and key other projects that will have deliverables

            4. Jack : Track deliverables. How will it get integrated

            5.  what are the associated project that are tied

            6. Rittwik :  Project disclosure

            7. Tracy: Use case management with respect to AI/ML

            8. Jack : Model Management, what SMO role etc should be covered, What we can do now 

            9. Other G Release activity status was discussed.

            10. Mahesh : Overview of the SMO Plan.

            11. Jack : brought up the documentation readiness and integration touch points .

            12. Rittwik : virtualized DU and collaboration with OAI . Jack clarified the challenges

         2. 2022-07-21 : Review of all project plan are in progress

            1. primer for "G" Release (Action : David/Rittwik)

         3. 2022-08-04: Continued the discussion on the proposed AI/ML project

         4. 2022-08-11: @Jack Murray: I hope to spend a little more time reviewing we're doing in the G release. Thanks to Dave for putting the timeline together and we're getting ready for our Dev sprint 1. We will just the maintenance release status on the Non RT RIC and O-DU-high projects next week.

         5. 2022-08-25:

            1.  @Jack MurrayRSAC can start the preliminary discussion on the H release. Also we really need to start understanding how people could use our releases and look for feedback from user communities and other downstream entities on what needs to get done as well as the internal teams. Let's start early with a dialogue.

            2.  @David Kinsey [AT&T] We've been trying to identify the demos in the October meeting. The first iteration is not very noticeable from a user's perspective. It's usually the building blocks of something larger. So what exactly do we want to Demo becomes a question. We're hoping to have the demo list finalized by the end of this month. So the next RSAC meeting or two we'll be finalizing that, and then we'll have to the end of September to get them assembled. We will have a three hour slot with a fifteen minute break in the middle, so we'll try to make best use of the whole time, and work with Jinri on what that agenda should be. 

            3. @Former user (Deleted): I think we may share some works from the Taiwan lab and to showcase some of that work also in the PlugFest. I may spend some time talking about H release if there is time.

            4. @Ankit Barve: We were trying to identify new use cases and maybe take input from operators to identify new use cases. Can we have some track from that?

   3. Report out from PTL: Stand-Up & Report Out on Blockers

      1. @James Li Integration and Testing (INT)

      2. @Mahesh Jethanandani Service Management and Orchestration (SMO)

         1. Demo on SMO VES collector setup provided by @Mahesh Jethanandani . Recording available here 

      3. @John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      4. @Sunil Kumar RIC Applications (RICAPP)

      5. @Thoralf Czichy RIC Platform (RIC) 

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. @Former user (Deleted)  O-RAN Distributed Unit High (ODUHIGH)

      8. @Lvfarias (Deactivated) O-RAN Distributed Unit Low (ODULOW) 

      9. @Martin Skorupski Operations and Maintenance (OAM)

      10. @Alex Stancu Simulations (SIM)

      11. @Jackie Huang Infrastructure (INF)

      12. @Weichen Ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)

8. Collaboration with OAI

   1. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time

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

   1. Thoralf : GS getting started "site space" cleanup: Getting Started 

      1. Update the page to notify people that it is under construction (Action : Mahesh)

      2. LF should give permission to all O_RAN SC members (Action : Sridhar)

         1. 2022-07-21 : Action Closed

10.  Planning for Next Meeting

    1.  

11. Any Other Business (AOB)

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

2022 08 18

Recording: 

Meeting Recording:

Topic: Zoom3 O-RAN SC's Personal Meeting Room

Start Time: Aug 18, 2022 09:01 AM EST

Meeting Recording: https://zoom.us/rec/share/r_Pv3Yt25OKFkEgD2EvfAIgOEDiV3jfnMZBn2ULGxWBXklvVq1iKqCzPwZlMAuFD.aTro_CtJldI01vkX

Agenda

1. Call for Scribe (minutes owner): James Li

2. Roll Call & Quorum Check 

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

1. Review and Agree to Minutes of Previous Meeting

   1. Decision: Minutes for TOC meeting (11th August 2022) approval: Motion to be proposed by James approved by Ganesh and the Motion was approved.

2. Review of Today's Agenda.

3. Release Votes and Approval

   1. New Project Creation for AI/ML Project

      1. 8/11/22 Voting request from Avinash (Samsung) for the creation of AI/ML project, proposed PTL and underlying projects (https://lists.o-ran-sc.org/g/toc/topic/voting_request_ai_ml/92954587): approved.

4. Copyright update

   1. Is SCCL discussion progressing in O-RAN Alliance? Does the Alliance have plans to publish code-like specifications under SCCL anytime soon? Need to follow up with O-RAN legal team and O-RAN EC to determine current status of SCCL.

      1. 2022-07-14 : Need to work on clarification for SCCL license and start having O-RAN WG Material.   Refer to the website on O-RAN Alliance and update the charter Following work with TSC for contributing material to be used down stream. Setup a Meeting with Stephan (he needs to approve the CLA). (Action Point : Jinri)

      2. 2022-07-21 : Meeting planned today and there will be update on this topic next week. The current focus in on O-RAN (does'nt cover 3GPP, ETSI etc)

      3. 2022-07-28 : Meeting with O-RAN Legal Team, the draft of the Project Charter as well as CLA are ready. Once the documents are reviewed the same will be added to the process. There is a continued discussion with ETSI and O-RAN WG on how to organize the documents to make them available to O-RAN SC. Documents will be shared on the reflector . Feedback to be provided by everyone after discussing with their respective legal team.

      4. 2022-08-04: Jinri is out sick, hopefully work on that will make some progress here soon as he's feeling better.

      5. 2022-08-18: Stephen created an updated CLA draft and we shared it with people to take comments and then hopefully we can get it approved.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. F2F Meeting (Oct'22)

   2. Plugfest

      1. 2022-07-21 : O-RAN Alliance will initiate the Call for Host on July 24th

      2. 2022-08-11: @huangjinri@chinamobile.com: Call for host for the fall Plugfest has been issued, and there are quite a few applications for host.

   3. Challenges for the OSC community (as report to EC)

      1. 2022-07-14 : There is no update this week

6. Old business and Status of Open Actions

   1. "F" Maintenance Release

      1. 2022-07-14 : 

         1.  Non-RT RIC Project : Will revert back by next ToC meeting if there is a need for a maintenance release . 

         2. O-DU High also will have some maintenance

      2. 2022-07-21 :

         1. O-DU high upto fixes needs to be merged. 

         2. Target to close this maintenance by 4th Aug

      3. 2022-08-04: @John Keeney (Ericsson EST) Non RT RIC F maintenance is about ready, but found one nasty little bug at the last moment. Should have it done in the next day or two. @Ankit Barve O-DU-highis ready and will upgrade the branch.

      4. 2022-08-18:

         1.  @John Keeney (Ericsson EST) The work is all done, branches all finished and just the actual release operation hasn't happened, and the maintenance release images not pushed out yet.

         2. : It's done last week and branch updated.