Recording 

Meeting Recording: Link

Agenda

• Call for scribe (minutes owner):  @Avinash Bhat (Samsung)

• Next scribe:  October 2023: @Ultan.Kelly (Viavi)

• Previous scribe: September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January-2023: Ericsson, December-2022: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: Radisys

• 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 approval for last TOC meeting: Motion proposed by  @Ankit Barve seconded by @Ultan.Kelly   motion approved unanimously.

2. Review of Today's Agenda

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

   1. Collaboration with OAI (lab interconnection) @James Li @Former user (Deleted) 

      1. 2023-06-29: @huangjinri@chinamobile.com Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.

      2. Review "OSC – OAI Collaboration Proposal" @OpenAir Interface @Robert Schmidt 

      3. 2023-08-10: Joint OSC-OAI Workshop @OpenAir Interface

      4. 2023-08-17: Joint OSC-OAI Workshop: In the process of writing tentative agenda for sharing next week. @OpenAir Interface 

      5. 2023-08-24: 2023-FALL-JOINT-OSC-OAI-WORKSHOP-BOSTON @OpenAir Interface

   2.  TSC meeting 

      1. 2023-08-31: Next TSC presentation will be on next Friday (2023-09-08)

   3. Super "Simplified" Wireless RAN blueprint @Tracy Van Brakle 

      1. Work three things in parallel:  demonstrations within university labs (multiple regions); roadmap; sources of funding to assure sustain-ability

   4. 2023-08-03: OAI proposal has been presented to the TSC, TSC said no money to fund it.

   5. 2023-08-10: ONF proposal @Rittwik Jana 

   6. 2023-08-17: TSC approval for making following changes @Sridhar Rao 

      1. Set a file size limit of 5m in all repos to prevent large files from being pushed. (This is the same size we allow in other communities)

      2. Cleanup the 2 repos (it/dep, pti/rtp), which requires a history rewrite to permanently remove large files. Reason: Failing GitHub replication

         1. ric-infra/10-Nexus/etc/conf.tar  (it/dep)

         2. meta-oran/recipes-containers/kubernetes-plugins/cpu-manager-for-kubernetes/docker-img-cmk-v1.3.1.tar.bz (pti/rtp)

         3. meta-oran/recipes-containers/kubernetes-plugins/multus-cni/docker-img-multus-v3.2.tar.bz2 (pti/rtp)

         4. meta-oran/recipes-containers/kubernetes/kubernetes/docker-img-kubernetes-v1.15.2.tar.bz (pti/rtp)

      3. **Both actions require a Gerrit downtime** 

      4. motion for cleaning up the 2 repos: approved unanimously.

      5. motion for setting the size limit of 5m: approved unanimously.

   7. 2023-08-24: ONF's new open RAN initiative @Rittwik Jana 

   8. 2023-08-31: update on ONF proposal: energy saving use cases discussion, 3 data sets @Rittwik Jana 

   9. 2023-08-31: ReadtheDocs has few deprecations coming up withch will affect the ORAN-SC repos@Matt Watkins; @Thoralf Czichy put it on a wiki: Configure Repo for Documentation

   10. 2023-09-07: No new Agenda Items

   11. 2023-09-21: @David Kinsey [AT&T] & @OpenAir Interface made a call for keynote speakers & demos to O-RAN SC members. @Jackie Huang to comment on participation on the Panel Discussion on  Nephio & O-Cloud integration

4. Release Votes (checklist) and Approval

   1. 2023-07-27:  Track Maintenance Release

   2. 2023-07-27:  Release I & J planning

   3. 2023-08-03: @Sunil Kumar request for approval vote for a new xApp repo RICAPP project contributed & maintained by @alexandrehuff (Unlicensed) from UTFPR Univ. New xApp implements the E2SM-CCC service model. Motion proposed by @David Kinsey [AT&T] , seconded by @James Li , motion passed unanimously.

   4. 2023-08-03: Tack Maintenance Release: RICAPP @Sunil Kumar , ODULOW @Ankit Barve , NONRTRIC @John Keeney (Ericsson EST) all on track, will close out next week.

   5. 2023-08-10: Approval of the Maintenance Release.

   6. 2023-09-07: None of the PTLs brought any items.

   7. 2023-09-21: New Repository Request - link - (aiml-fw/awmf/modelmgmtservice) by the AIMLFW PTL @Joseph Thaliath 

      1. @John Keeney (Ericsson EST) seeked clarification on WG2 compliance and the same was provided by @Joseph Thaliath 

      2. @Joseph Thaliathconfirmed a demo can be made by mid of Nov timeframe

      3. Decision: The proposal was unanimously approved 

   8. 2023-09-21: New Repository Request - link - (ric-plt/conflictmgr) by the near-RT RIC PTL @Thoralf Czichy 

      1. Gunjan Rastogi from CapGemini mentioned that demo is mid of Nov-23 is challenging. @David Kinsey [AT&T] suggested a basic demo is a good start. 

      2. Decision : The proposal was unanimously approved 

5. AP Review

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

      1. OSFG discussions  @huangjinri@chinamobile.com 

         1. O-RAN SCCL enforcement

            1. Publishing O-RAN code-like segments under SCCL CLA @huangjinri@chinamobile.com 

               1. 2023-05-18: waiting for a feedback from O-RAN Office

               2. 2023-09-14: @Jakub Novy [DTAG] @David Kinsey [AT&T] mentioned it was more of an introductory meeting (setting our position) . Next meeting is scheduled on Sep 21, 2023 post the ToC Meeting

            2. Naming and directory structure has been agreed upon and next step will be to get it approve.

            3. Anything else?

         2. Collaboration with OAI (lab interconnection) @James Li @Former user (Deleted) 

            1. 2023-06-29: @huangjinri@chinamobile.com Discussion with OAI went well, OSC expressed willingness for collaboration which was supported by OAI. For implementation, OAI is to provide a repository mail so that OSC can leverage it once legal conditions are met.

            2. Review "OSC – OAI Collaboration Proposal" @OpenAir Interface @Robert Schmidt 

            3. 2023-09-07: @OpenAir Interface shared the updates on the event details. This is an "in person only" event, refer to Link for detailed Agenda. Action: @huangjinri@chinamobile.com to send invite on O-RAN SC and relevant folks in O-RAN Alliance based on the format to be shared by @OpenAir Interface 

            4. 2023-09-14: @OpenAir Interface provided an update on Committee Meeting.

               1. Plan is to follow a workshop mode, 3 sessions (RAN, OAM and Lab Status) and demo.

               2. Made call for speakers and panels.

               3. Provide OAI ~Nephio and proposed a joint discussion on the topic.

               4. @David Kinsey [AT&T] Proposed to showcase some O-RAN SC F2F demos at the event.

            5. 2023-09-28: @David Kinsey [AT&T] highlighted the low participation from O-RAN SC in demo and keynote point of view. RIC, X-APP, AIML could be potential area. @OpenAir Interface said O-RAN SC participation will be accommodated. 

               1. @John Keeney (Ericsson EST) requested for clarification on OAI,OSFG & ORAN SC relationship. @David Kinsey [AT&T] clarified that the objective is to support the common goal of O-RAN Proliferation and showcase of O-RAN Capabilities with reference design.

               2. @John Keeney (Ericsson EST) requested to get a clarification on the MoU. @OpenAir Interface mentioned that it is very generic and is between O-RAN Alliance & OAI, doesn't cover any licensing details. 

               3. @John Keeney (Ericsson EST) requested clarification on licensing terms. @OpenAir Interface clarified that each community will follow their respective community guidelines.

         3. OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle 

            1. Link to O-RAN OSFG meeting minutes 7/21

            2. Work three things in parallel:

               1. demonstrations within university labs (multiple regions) - concurrent with O-RAN Fall 2023 PoC/Plugfest (readout week of November 26)

                  1. AsiaPac - Taiwan and other locations

                  2. EU

                  3. North America

               2. sources of funding to assure sustain-ability

                  1. O-RAN nGRG - application due August __, 2023

                  2. Public Sector - NSF? NTIA?

               3. Whitepaper (2023-09-14: It was clarified to be a whitepaper)

      2. O-RAN next phase - prepare for upcoming F2F in Phoenix AZ, USA, October 17 to 19

         1. 2023-08-03: Next F2F registration is now opened. @Rittwik Jana mentioned ONF reached out for the energy saving topics. @Martin Skorupski put it on the agenda of OSFG meeting to talk about energy savings and the collaboration with ONF.

         2. 2023-08-17: Discussed about Demos, the type of env screens needed. @David Kinsey [AT&T] @OpenAir Interface 

         3. 2023-09-07: @David Kinsey [AT&T] made a call for sessions and requested members to update them directly in the event page. Refer Link for updates. AIML, SMO de-compositions within O-Cloud & Energy Saving sessions were discussed and added to the list. Proposal is to have 6 slots. @David Kinsey [AT&T] proposed to cancel the ToC Call during the event week.

         4. 2023-09-14: @David Kinsey [AT&T] mentioned that we should have at least 5 sessions for the planned items (Refer Link). The schedule is yet to be finalized.  Details to be updated so that event can be planned better.

         5. 2023-09-21: @David Kinsey [AT&T] reminded everyone to take care of hotel accommodations in advance as it is sold out. 

         6. 2023-09-28: @David Kinsey [AT&T] clarified that we have received 5 session (against the 7 requested) . @huangjinri@chinamobile.com to invite all the O-RAN Alliance WGs for the sessions. @David Kinsey [AT&T] will organize the schedule and update the F2F Event Page. 

   2. Others

6. Standing/old business

   1. OSC Lab

      1. 2023-08-17: Our Bedminster Lab is in the process of move @David Kinsey [AT&T] 

      2. 2023-09-21: No update on the move this week.

   2. Release Planning: Weekly TOC Scheduling @Sridhar Rao 

      1. 2023-05-26 Issues on moderation/permission for comments on the wiki (see message from @John Keeney (Ericsson EST) )

         1. Matt Wilkins: the problem is acknowledged but due to the nature of the wiki, a solution to prevent unintended post/comments is not trivial.  Matt will keep on working on this and update the group.

      2. 2023-06-08 @Sridhar Rao License scanning completed and report has been sent to all PTLs
         @James Li Patch has been submitted for the AI raised under integration project

      3. 2023-06-15 All PTLs to update H release page and notify through email to get it review, if this gets done over the next week then we can call for the release vote on the 2023-06-29 TOC following the F2F.

      4. 2023-06-29 Integration, RICAPP, DOC, and O-DU Low PTLs to update the H release page.
         @David Kinsey [AT&T] to send reminder  to above project PTLs to update the H release page and also to create I release page with project template.
         H release to be postponed on next TOC July 6th 
         @Sridhar Rao created release checklist page, all PTLs expected to review and provide feedback if any.
         @huangjinri@chinamobile.com to check regarding PR statement.

      5. 2023-08-03: @Rittwik Jana Focus on energy savings; Figure out a plan of execution to get the metrics; ML modeling; SMO discussion.

      6. 2023-08-31: @Seshu Kumar Mudiganti @David Kinsey [AT&T] Stretch to get the O-Cloud energy savings using policies into the I or J release. @Jackie Huang need to check if it's doable.

      7. 2023-09-07: @David Kinsey [AT&T] made a call to PTL to update the I Release plan. PTLs to complete this before the F2F Meeting.  @Rittwik Jana provided updates on the data set.

      8. 2023-09-14: @Rittwik Jana updated that there are 2 datasets Alex is working on one dataset and Viavi is working on the other. Ritwik to follow up with Ultan (Viavi)

      9. 2023-09-21: @Rittwik Jana confirmed on behalf of @Ultan.Kelly about the new dataset availability. (The old dataset cannot be make available). Next step would be to discuss with @Joseph Thaliath 

      10. 2023-09-28 @Rittwik Jana provided an offline update:

          • the TIM data set that would allow training of the AI/ML models is ready (it needed parsing). I will upload it to Nexus3 once we figure out how (LF is working on making Nexus3 host datasets - Sridhar will update once it is ready). Then, the AI/ML team will be able to play with that dataset.

          • Other dataset (synthetic) still to be produced by Viavi - maybe Rittwik has more information here

          • Discussions ongoing about the PM streaming (flow details here). Once we finalize the discussions there, implementation can start in the SIM and OAM projects.

   3. Project reports (by features)

      1. 2023-08-03: Project reports in groups will be strike out, and it will be done by features, which will need to be restructured.

      2. 2023-08-17: Features grouped as in RSAC.

      3. Project Reports

Recording 

Meeting Recording: Link

Agenda

• Call for scribe (minutes owner):  @Avinash Bhat (Samsung)

• Next scribe:  October 2023:

• Previous scribe: September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January-2023: Ericsson, December-2022: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: Radisys

• Roll Call & Quorum Check