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

Call for Scribe (minutes owner): James Li
Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	x	David Kinsey
China Mobile	Jinri Huang Co-Chair	x	James Li
Deutsche Telekom	Jakub Nový		Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Nokia	Arunkumar Halebid	x	Thoralf Czichy
Orange	William Diego		Vincent Danno
Radisys	Ganesh Shenbagaraman	x	Ankit Barve
TIM	Andrea Buldorini	x
Wind River	Bin Yang	x	Jackie Huang
Viavi Solutions	Ultan Kelly	x	Kexuan Sun
Samsung	JinGuk Jeong	x	Avinash Bhat

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

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.
Review of Today's Agenda.
Release Votes and Approval
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.
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)
4. 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.
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.
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 Singh 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)
Collaboration with OAI
1. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time
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
Planning for Next Meeting
Any Other Business (AOB)
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

Call for Scribe (minutes owner): James Li
Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	David Kinsey
China Mobile	Jinri Huang Co-Chair	x	James Li
Deutsche Telekom	Jakub Nový	x	Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Nokia	Arunkumar Halebid	x	Thoralf Czichy
Orange	William Diego		Vincent Danno
Radisys	Ganesh Shenbagaraman	x	Ankit Barve
TIM	Andrea Buldorini	x
Wind River	Bin Yang		Jackie Huang	x
Viavi Solutions	Ultan Kelly		Kexuan Sun
Samsung	JinGuk Jeong	x	Avinash Bhat

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

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.
Review of Today's Agenda.
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.
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.
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)
4. 1. 2022-07-14 : There is no update this week
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. Ankit Barve: It's done last week and branch updated.
    3. Jack Murray: Need to have documentation and list the images that's part of the maintenance release on the F release page. Both Non RT RIC and O-DU-high needs to have the release page updated.
2. "G" Release
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-18: David Kinsey [AT&T] We found some some routing entry errors and corrected them but it didn't solve the problem. We have another session set up tomorrow to identify which server has the problem. Meanwhile we see some exchange of data, for instance, the MAC address is seen by the IXR but they don't still see the clock.
4. 5G Super Blueprint status - to be considered for H release.
  1. 2022-07-21 : David mentioned that there hasnt been any progress on this. Decided to move to H release. (Updated the title header from G to H to reflect the same)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Sridhar Rao /Release Planning: Weekly TOC Scheduling
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. But it's working in the Taiwan lab to verify the release features that were not be able to be tested in the Bedminster lab.
    5. 2022-08-18:
      1. Jack Murray We should be officially starting our Dev one sprint over the next three weeks and we hope to see people can pre-record a DEMO showing some progress
      2. David Kinsey [AT&T] The Madrid face to face is going to occur on week 15. The primary topic for next Wednesday's RSAC is trying to identify things we can show from sprint one demos.
      3. Jack Murray Anything that's significant and relevant, even from the F release that we can package up as a pre recorded demo, which is helpful to give O-RAN alliance members who don't pay much attention to OSC a sense of things that we were able to accomplish.
      4. huangjinri@chinamobile.com: Once David Kinsey [AT&T] has selected or decided on the demo please let me know in a timely manner for me to work on the agenda.
3. Report out from PTL: Stand-Up & Report Out on Blockers
  1. James Li Integration and Testing (INT) 2022-08-18 needs to add an INT section in the G release page
  2. Mahesh Jethanandani Service Management and Orchestration (SMO) 2022-08-18
    1. Mahesh Jethanandani The focus of SMO for the G release is integration: integration of O-DU on the O1 interface, and try to deploy network function that using Tacker on O2 interface. Will be a lot of interoperability testing.
    2. Jack Murray I would ask you to add two items here: 1)interface to the AI/ML project that's just starting right now -- expecting you to work with that team to deliver an analysis on what's the path forward for integration; 2) A little more description of what you think we could do with O-CU. It's critical around the orchestration to start to be able to to deploy more components. As part of the AI/ML discussion it came up about where dashboards already exist and we want to work with the existing structure. From an operation point of view, how do the operation team find the dashboards, where they are, and a consistent view? I think it's a dialogue at this point, but we may need to collect the requirements.
    3. Mahesh JethanandaniRSAC would be. agood location to have that discussion about the dashboard capabilities.
  3. John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC) : 2022-08-18 the G release page is up-to-date.
  4. Sunil Singh RIC Applications (RICAPP): 2022-08-18 Focused on the new HW-Rust xApp and created the repo. There will be a scenario that integrates multiple xApps and the discussions are still ongoing. Also geo-location information for the xApp.
  5. Thoralf Czichy RIC Platform (RIC) : 2022-08-18
    1. Thoralf Czichy There will be work on E2 and A1. One key thing is to provide a REST E2 subscription interface to replace the subscription via RMR. We will remove the RMR support early in G release, and xApp still using RMR need to adapt to the new interface.
    2. Jack Murray: Once this is done we need to validate that all xApp can still operate under the new release
    3. Sunil Singh: Yes, all xApp needs to be modified.
    4. Jack Murray Need to document this change so that people don't waste time on something that they think should work, but is not there. Maybe have a ToDo list to make sure that they're updated.
    5. Thoralf CzichyC++ HW xApp also requires changes.
  6. (TBD) O-RAN Centralized Unit (OCU)
  7. Ankit Barve O-RAN Distributed Unit High (ODUHIGH) : On Taiwan lab we started integration and reached to a point where synchronization between L1 and L2 memory issues resolved and we are trying to achieve frame synchronization slots inclination. I, along with Lewis from Intel and Taiwan team is working on it.
  8. Lvfarias (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  9. Martin Skorupski Operations and Maintenance (OAM): 2022-08-18
    1. Martin Skorupski It's all available on this page: there are new VES message WG 10; Java version update; better security; and continue discussion on the AI/ML project on how to integrate into SMO in the future.
    2. Jack MurrayDoes the current test fixture support the O1 interface?
    3. Ganesh Shenbagaraman: I'm not sure if this got tested in the last release, but this is something that is available. I'll check with our r&d team to see if we can provide a new release image
    4. David Kinsey [AT&T] We might also need some help with deployment -- we've been trying to generate the helm chart and it's been slow to get it to run on the O-cloud
    5. Martin Skorupski The Tacker team is trying to deploy it O2 interface.
    6. David Kinsey [AT&T] First is to do it manually -- Take the package builder from the helm and the other artifacts to build the onboarding package, the CSR, and then we should be able to give that CSR to Tacker and it should deploy it in theory.
  10. Alex Stancu Simulations (SIM) 2022-08-18
    1. Martin Skorupski: I can cover for Alex Stancu. There will be continuous work on O1 simulator, and some new features of E2 simulator. Also from the university team they want to have the NS3-E2 integration.
    2. Jack Murray: Do we have some sense of who's using the simulators at this point?
    3. Martin Skorupski: The simulators are currently used by the first version of the 5G super blueprint package with Jenkins to run test cases to validate after the deployment. ofcloudified network functions.
    4. Mahesh Jethanandani SMO uses in the same way
  11. Jackie Huang Infrastructure (INF): 2022-08-18 needs to add an INF section in the G release page
  12. Weichen Ni Documentation (DOC)
  13. (TBD) O-RAN Radio Unit (ORU)
  14. hoejoo.lee AI/ML 2022-08-18
    1. Avinash Bhat: Started the project creation; started the discussions with other projects; Updating the wiki pages and all the details.
    2. Jack MurrayNeeds to add a section of AI/ML project under the G release page
Collaboration with OAI
1. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time
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
Planning for Next Meeting
Any Other Business (AOB)
1. 2022-08-18:
  1. huangjinri@chinamobile.com Orange is currently preparing for two important things:1)face to face meeting in October in Madrid, anyone interested in attending can register and get their invitation letter as well as discount accommodation and hotel. 2) FUZY hosted by TIP after the week of the f2f meeting. Regarding SCCL, I had provided some comments regarding the Charter modification but unfortunately I haven't got the feedback from Stephen. I will continue to push him.
  2. Jack Murray The two steps, the CLA and the Charter changes, we should be sharing with the active companies here so that everybody can see what we're proposing to change, and they can share with their legal teams to collect feedback. We will have to bring it to the board for a vote for final approval.
  3. huangjinri@chinamobile.com I will continue to push the OSC challenges to be part of EC discussion next week.
Meeting Summary (resolutions, new action items, etc.)

2022 08 11

Recording:

Meeting Recording:

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

Start Time: Aug 11, 2022 09:01 AM

Meeting Recording:

https://zoom.us/rec/share/WARNHqxD6zQV7pgxtJSrrlA_hsR0z-gW7tnNNMuromMlcXcZ_KOeNf6KYG1OYfLj.CknM4R_2s7KQIhXO

Agenda

Call for Scribe (minutes owner): James Li
Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	David Kinsey
China Mobile	Jinri Huang Co-Chair	x	James Li
Deutsche Telekom	Jakub Nový	x	Ondřej Hudousek
Ericsson	John-Paul Lane		John Keeney	x
NTT DOCOMO	Masafumi Masuda		Anil Umesh
Nokia	Arunkumar Halebid	x	Thoralf Czichy
Orange	William Diego		Vincent Danno
Radisys	Ganesh Shenbagaraman		Ankit Barve	x
TIM	Andrea Buldorini	x
Wind River	Bin Yang		Jackie Huang	x
Viavi Solutions	Ultan Kelly	x	Kexuan Sun
Samsung	JinGuk Jeong	x	Avinash Bhat

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

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for TOC meeting (4th August 2022) approval: Motion to be proposed by James approved by John Keeney (Ericsson EST) and the Motion was approved.
Review of Today's Agenda.
1. AI/ML Project Overview (Avinash) - The presentation to be continued
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):
    1. Avinash (Samsung): voting request posted on TOC email list, requested 8 repositories under the project: Dashboard: GUI to provide control and display status of Training manager;Training manager: Component to manage Training jobs, Models;TMS Adapter: Component to interface with TMS (Kubeflow);IMS Adapter: Component to interface with IMS (Kserve);Data Extraction: Component which retrieves required data for training from Data Lake;Feature store SDK: SDK for retrieving features required for Training;Model storage SDK: SDK for uploading and downloading Models;AI/ML Framework Deployment: Installation scripts for the AI/ML Framework components. New repo and keep a link in it/dep repository;
    2. huangjinri@chinamobile.com: two questions: 1) will this be a standalone project in G-release? 2) what's the intended interaction with relevant O-RAN alliance WGs?
    3. Avinash (Samsung): 1) yes 2) The basic framework was probably defined a year and a half back and there hasn't been much progress. We have picked up from there and have some of those implementations and some initial PoC of this whole framework. As we go along the discussions with respect to interfaces, for example, the integration with that SMO project or Non RT RIC project, we've already discussed few of the interaction points. What comes out of the RSAC discussions would need to feed back into the O-RAN alliance as well.
    4. Jack Murray: We have strong expectations that over the course of the G release that a plan be pulled together around how this fits with all the other modules and we can then decide on how to move forward beyond G. If it's approved as a project, this will give each PTL and the community a chance to have a dialogue about how this goes forward along with the O-RAN alliance WGs.
    5. Mahesh Jethanandani: I just had a question around the rationale behind the 8 repositories.
    6. Avinash (Samsung): The dashboard is the kind of main UI which will be required for managing this whole framework. Then there have certain basic training managers and inference managers, also we would recommend to provide an adapter layers to keep that as a separate adapter for TMS and IMS. The model storage and feature storage might need separate treatment, so we have kept them in two repositories to handle them independently. The AI/ML framework deployment will be some kind of scripts for the ML components to be manually deployed in G release.
    7. Jack Murray: Having this many repositories can add to your overhead versus things like adapters been organized in the same repo in a directory structure that makes sense in terms of how you use it. Mahesh Jethanandani does the SMO project have any dashboard that would be pulling other sources and things together?
    8. Mahesh Jethanandani: In SMO a dashboard is part of the O1 interface for configuration management and we don't have a separate repo for just the dashboard.
    9. John Keeney (Ericsson EST): A general comment there we do have a family of repos under portal/ for dashboards for we to try to consolidate dashboard projects. Similarly, I would suggest maybe that the dashboard project could be a sub repo on the portal/ family. In addition, all of our deployment scripts are currently in the the it/dep repo and we might want to do the same for the AI/ML framework deployment.
    10. Avinash (Samsung): We were not aware of this consolidation efforts and we could definitely comply with that.
    11. John Keeney (Ericsson EST): One other comment as well, in Non RT RIC project we started off with one repo with a heap of functions and the overhead just became too much, for instance, trying to have Sonar jobs that only refer to a sub directory. So there were pros and cons, and in the end we pulled the trigger to split it out into multiple repos as there are many advantages to having more small reports than one large repo. The approach you have here seems to make more sense having multiple repos as probably more overhead trying to keep things sorted within a single repo.
    12. Avinash (Samsung): I have the same opinion that it's better to have more structured repos and components.
    13. huangjinri@chinamobile.com: John Keeney (Ericsson EST) one question to your previous comment regarding the dashboard - is the dashboard you mentioned under the portel/ the same as the one Mahesh mentioned in the SMO O1 project?
    14. John Keeney (Ericsson EST): I wasn't aware that there was a dashboard function separately in the SMO project. If it's not too much work maybe it might make sense to consolidate the same work same ownership same project under the portel/ family repos.
    15. Jack Murray: Good conversations and very good discussion. We understand some of those challenges and can find the right balance of trade offs and can move things later if we find that it makes better sense to move things around.
    16. Jack Murray: So we have a proposal from Avinash on creating this AI/ML project and several repos. He'll continue to work in parallel with other projects to come up with a more integrated plan. But what do you think by the end of G release would you be able to demonstrate the progress and capabilities toward the first phase?
    17. Avinash (Samsung): There is already a use case for QoE optimization and already an xApp. We would demonstrate building this application in our framework and deploying it. We will reuse the same data set which is already uploaded here.
    18. Jack Murray: The data that you're using as part of your testing and the framework becomes part of the open source community even though it's artificially created data. You might have to look at Linux Foundation's open source data license.
    19. Avinash (Samsung): Actually the QoE prediction xApp exists as part of RICAPP project. We are looking at using the same data set within the repo for demonstrating this capability.
    20. Jack Murray: We just have to make sure that we have a plan around managing data, which is a little different than the software and what license it's under for people to use it. It's not directly part of what we're approving today, but we just need to make sure we're following the right processes. We have a motion to create a new project, and we have the information on the PTL and the contributors and repo organization. Who can second?
    21. huangjinri@chinamobile.com: I can second.
    22. Jack Murray: We have full agreement on creating the AI/ML project. Avinash is going to work with sridhar to set up the repos and add to the project page. As part of releases, PTLs will be responsible for creating their section here on the G release page to describes what's going on. Each project should have at least a header and a description on things to be accomplished in this release. This is very helpful as a reference to O-RAN alliance and other forums as this is kind of the place of record what each PTL is committing to and focusing on. We haven't added too many new projects lately, but this is a big one with lots of activities so great job! This will, over time, touch a lot of projects and I would like to make sure things are done in a consistent fashion like the documentation, and the "getting started" page.
    23. Avinash (Samsung): Is there some guide which could help us make sure that we cover all the points with respect to the project creation and the next steps?
    24. Jack Murray: Unfortunately no. I noticed Sridhar posted something about insights.
    25. John Keeney (Ericsson EST): Congratulations to the Samsung team! We still remain quite concerned about scope overlap and try to identify clear boundaries of scope and to avoid work duplication Do you think at this stage to set an explicit action that we can come back and check at the end of the G release to serve the H release and beyond to ensure that we've done our work?
    26. Jack Murray:I don't know there's a formal mechanism to do that. But the AI/ML project really needs to make sure its pieces can be incorporated and maintain some modularity with a cohesive plan because it has touch points to other projects such as near RT RIC, non RT RIC, OAM, SMO projets.
    27. Avinash (Samsung): I think that was one of the agreements which we had last week that we will definitely try to take this up regularly in the RSAC meetings to at least make it more integrated into other projects by the end of G release. We will take it on RSAC as an action.
    28. Sridhar Rao: This is the insights for the F release as Martin raised an issue and we got it fixed, so I just want to ensure that there are no other issues in this. Please take a look at this link and please let me knowif you see any discrepancy or a mismatch.
    29. John Keeney (Ericsson EST): I have one quick comment here, I wondered if maybe we could try to track down who are the people as the unknown category and the individual-no account category and even the others category to see if they're being correctly allocated to the correct team and project.
    30. Sridhar Rao: I think it's a valid point that I can talk to the analytics team.
    31. Jack Murray: Pleae look at it and bring it to the Linux foundation to get it fixed if you feel it doesn't make sense, as this is the information of record other people reference especially when articles are written.
    32. John Keeney (Ericsson EST): On the analytics page, can I ask Sridhar what is the difference between when counted as a commit and change list that there's nearly 25 - 30% difference in the values. In most cases, one change list results in one commit so I'm not really sure I understand what is the difference.
    33. Jack Murray: John please just send Sridhar an email to get on his list.
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.
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)
4. 1. 2022-07-14 : There is no update this week
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.
2. "G" Release
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
4. 5G Super Blueprint status - to be considered for H release.
  1. 2022-07-21 : David mentioned that there hasnt been any progress on this. Decided to move to H release. (Updated the title header from G to H to reflect the same)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Sridhar Rao /Release Planning: Weekly TOC Scheduling
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: Continue the discussion on the proposed AI/ML project
      1. Avinash (Samsung): Our objective is to build an AI/ML framework where a network operator could create use cases and easily deploy the use cases. We have broken down them into three broad categories: one is a workflow management function which will focus on the training part; a training management system to support various kind of frameworks; an inference platform. Jack's comment on this broad framework is to ensure to not to build everything from scratch, make sure that we reuse as much as possible. Our objective is not to build any new program but kind of define a framework with plugs where we can upstream some projects which are already there and that's our design philosophy as well, so I think I clarified that already. Another question with respect to ensuring that we don't build any separate APP management framework and reuse what is already there in SMO. We will reuse what is already there for deployment of applications and apart from that, there are some ML components will have to manually deploy.
      2. John Keeney (Ericsson EST): One quick comment: I think we still have a little bit of work to do around defining the boundaries around the data management and exposure. I think we would have to take some discussions there before we have agreed fully on the scope. One quick comment: I think we still have a little bit of work to do around defining the boundaries around the data management. I think we would have to take some discussions there before we have agreed fully on the scope.
      3. Avinash (Samsung): The data management and exposure is under discussion at the moment. Once that is clearly defined, we can support it. At the moment, we are looking at it to be an integral part of the framework itself. I also need to clarify that the overall scope of this project contains functionalities that are not clearly defined in the WG2, so do expect a lot of discussions and the need to work through at the specification level. But for the initial release it doesn't have any major touch points with any other projects. We propose to have Hoejoo Lee as the PTL for this project.
      4. hoejoo.lee: I've been working with Avinash develop AI/ML workflow over the past three years and look forward to working with you.
      5. Jack Murray: how familiar are you with Linux Foundation tooling and approaches? Have you done other projects or activities with Linux foundation?
      6. hoejoo.lee: About 2 years ago I joined the EdgeX project with Linux Foundation.
      7. Jack Murray: Sridhar from LF can help.
      8. Avinash (Samsung): Besides Hoejoo, we also have 4 or 5 members that can contribute to the project, and we are open to anybody who's really interested to contribute.
      9. Jack Murray: TOC members and other participants are to share this information with your companies and see if you might work directly in this area.
      10. Avinash (Samsung): Feel free to reach out to me if you're interested. A bit more on the G release scope – again there should be no impact to other projects in G, but in the future there may be impact to SMO, Near RT RIC and Non RT RIC projects.
      11. Sridhar Rao: are you considering any specific use case for demonstration?
      12. Avinash (Samsung): Yes, in the next slide, we'll reuse the QoE prediction use case with the framework.
      13. Jack Murray: I encourage you to start dialogues with other projects, like Near RT RIC, xAPP projects, and SMO, from the beginning so they are all on the same page to make sure all your development could be most effective, and to avoid recreating work.
      14. Avinash (Samsung): Sure. Even if we want to do something in the upcoming releases, we have to start the dialogues now and keeps the discussion going.
      15. Former user (Deleted): Should you use O1 to send the models to Near RT RIC and Non RT RIC?
      16. Avinash (Samsung): In G release we plan to deploy it manually.
      17. Jack Murray: The deployment is really part of the lifecycle management system. And that the configuration might be on O1.
      18. Former user (Deleted): How common APP lifecycle management works is still in the air and we have to keep an eye on that. I kind of noticed in this diagram at least you have a direct rest API between ML APP and assist APP and you're bypassing the DME in this case.
      19. Avinash (Samsung): Overall we're looking at this as one rApp. As we discussed in RSAC meeting the assistant APP in the future could potentially service many ML Apps. It might require for larger discussions in the specifications itself. As of now, we are looking at just deploying this APP like a regular rApp and the rest ML components we will deploy it manually. How they interact can be defined but REST is what we are recommending for this particular use case. For other use cases that want to use different interface and once standardized, we will support or align to it.
      20. Former user (Deleted): If we could connect it with perhaps a similar project or in some way will be a little bit better.
      21. Avinash (Samsung): From the larger orchestration perspective or from a functionality perspective, it is part of SMO. Until it is really standardized or there's a lot of discussions on that specification perspective, then integration will become more and more eminent. For now we thought was to get started with this but we welcome if any comments on that.
      22. Mahesh: I'm looking at this from an SMO perspective and the specifications will not guide implementation. As SMO already has, for example, from a data lake perspective, an influx db that you could start interacting with; and same thing about the Kafka bus.
      23. Avinash (Samsung): What we depicted here is to reuse the SMO framework, not going to redefine it.
      24. John Keeney (Ericsson EST): The influx db or Kafka bus access within SMO are only available currently to be the R1 interface.
        Your thoughts here is probably fine for the G release spoke, as it's like an end to end solution that will be essentially upstream into to OSC. We are basically postponing our discussions around where the scope overlap is, which would need ongoing over the next couple releases, they would need to be probably re-implementation of some of the solution presented here and to be more compliant with the O-RAN architecture and with the existing OSC integration environment.
      25. Avinash (Samsung): I completely agree. We never had a chance to discuss with you so any comment from you would be really valuable.
      26. Mahesh: I would welcome you to present this at the next SMO meeting.
      27. Former user (Deleted): What is the touch point with the OAM project, because they are implementing O1 protocol. This is where I'm a little confused: I can understand from a G release standpoint, it's OK as the implementation is pretty much stand alone. But my worry is, if you go down this path, later on you might have to do a whole lot of modifications to get those touch points with the Non RT RIC and SMO. I mean it's a great start, but I just feel like chicken and egg because not everything is specified in the specification.
      28. Avinash (Samsung): To keep it simple, we have internally discuss about this and we are looking at kind of manually doing the deployment right now. With respect to interface and model storage, I think the APP management needs some discussion. In terms of rework, the AI management function and the training platform, most of the components would probably continue as we don't have those touch points or integration points discussed. There might be some changes.
      29. Former user (Deleted): You have one touch point in Near RT RIC, one in SMO, and one inside the training platform so essentially three databases and the datalake outside of it. Can we consolidate the data stores?
      30. Avinash (Samsung): The datalake is purely from a training perspective and the remaining entities are more from an inference perspective. It may not be required to have both, unless both xApp and rApp use cases are supported.
      31. Jack Murray: The datalake is here for implementation, but in any production deployment, the datalake would be external.
      32. Avinash (Samsung): We have clearly called it out all the components which are marked by the gray color actually existing. We will reuse what is defined in the SMO project and we're not going to redefine the datalake when there's the influx db in the Near RT RIC. And for the APP deployment, we are looking at using the existing mechanism of deployment as well.
      33. John Keeney (Ericsson EST): Let's come back briefly to Rittwik's question about consolidating all these data stores. What we see here are the architecture picture, and a simplified view. There are a lot of steps and interfaces in the real data flow and coordination of the access. Let's try to boil this down and to fully understand all of these inter linkages, especially with existing platforms and functions.
      34. Avinash (Samsung): As we discussed, we will have a QoE prediction application to demonstrate the capability of the framework, which we will manually deploy. I think the data is in place and we will populate that into the data lake manually and use that for training and all the management will be done in a management function.I think that's broadly what we had with respect to the overall project and the overall project scope, as we all agree it's quite large and a lot of things are still under discussions and what we feel we can take it up as the initial scope for the G release.
      35. Jack Murray: Is there any any other kind of technical questions? I'd like to hear about the interest level in supporting the investment of the community towards this project, particularly from the other TOC members, and if any of the operators think that this is useful and important.
      36. Jakub Novy [DTAG]: I have to check with our colleagues and not able to give you the exact answer now.
      37. Jack Murray: I'm trying to spur the dialogue to promote the discussion and awareness to make it useful for the community. Before the H release I'm going to need to see a much better architecture on how this framework fits in as a framework, and added to the deployment without breaking things
      38. Avinash (Samsung): How do you propose to take this forward if you want to do it in G release?
      39. Jack Murray: You have roughtly 6 months to work in G release, after that I expect that architecture agreement to be in place with a lot more details, not necessarily the implementation. Also where did you post the slides?
      40. David Kinsey [AT&T]:Avinash you can post in the RSAC "G" release contribution folder.
      41. Jack Murray: I'm gonna push the vote for the project creation to the next week's TOC meeting. You can make a motion and post to the TOC reflector
    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.
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 Singh 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)
Collaboration with OAI
1. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time
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
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2022 08 04

Recording:

Meeting Recording:

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: Aug 4, 2022 09:00 AM

Meeting Recording:
https://zoom.us/rec/share/j5U9OilmWuBD1Sq7Y7d2Niz2hx57coPtVbqT1xKEet-I31nvmeJ7F9qEK678DK3U.-3WwpvIVbgvcwJDF

Agenda

Call for Scribe (minutes owner): James Li
Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	David Kinsey
China Mobile	Jinri Huang Co-Chair	x	James Li
Deutsche Telekom	Jakub Nový	x	Ondřej Hudousek
Ericsson	John-Paul Lane		John Keeney	x
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Nokia	Arunkumar Halebid		Thoralf Czichy	x
Orange	William Diego		Vincent Danno
Radisys	Ganesh Shenbagaraman		Ankit Barve	x
TIM	Andrea Buldorini
Wind River	Bin Yang		Jackie Huang	x
Viavi Solutions	Ultan Kelly		Kexuan Sun
Samsung	JinGuk Jeong		Avinash Bhat	x

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

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for TOC meeting (28th Jul 2022) approval: Motion to be proposed by Avinash approved by Thoralf and the Motion was approved.
Review of Today's Agenda.
1. AI/ML Project Overview (Avinash) - The presentation to be continued
Release Votes and Approval
1. New Project Creation for AI/ML Project
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.
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
3. Challenges for the OSC community (as report to EC)
4. 1. 2022-07-14 : There is no update this week
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.
2. "G" Release
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
4. 5G Super Blueprint status - to be considered for H release.
  1. 2022-07-21 : David mentioned that there hasnt been any progress on this. Decided to move to H release. (Updated the title header from G to H to reflect the same)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Sridhar Rao /Release Planning: Weekly TOC Scheduling
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: Continue the discussion on the proposed AI/ML project
      1. Avinash (Samsung): Our objective is to build an AI/ML framework where a network operator could create use cases and easily deploy the use cases. We have broken down them into three broad categories: one is a workflow management function which will focus on the training part; a training management system to support various kind of frameworks; an inference platform. Jack's comment on this broad framework is to ensure to not to build everything from scratch, make sure that we reuse as much as possible. Our objective is not to build any new program but kind of define a framework with plugs where we can upstream some projects which are already there and that's our design philosophy as well, so I think I clarified that already. Another question with respect to ensuring that we don't build any separate APP management framework and reuse what is already there in SMO. We will reuse what is already there for deployment of applications and apart from that, there are some ML components will have to manually deploy.
      2. John Keeney (Ericsson EST): One quick comment: I think we still have a little bit of work to do around defining the boundaries around the data management and exposure. I think we would have to take some discussions there before we have agreed fully on the scope. One quick comment: I think we still have a little bit of work to do around defining the boundaries around the data management. I think we would have to take some discussions there before we have agreed fully on the scope.
      3. Avinash (Samsung): The data management and exposure is under discussion at the moment. Once that is clearly defined, we can support it. At the moment, we are looking at it to be an integral part of the framework itself. I also need to clarify that the overall scope of this project contains functionalities that are not clearly defined in the WG2, so do expect a lot of discussions and the need to work through at the specification level. But for the initial release it doesn't have any major touch points with any other projects. We propose to have Hoejoo Lee as the PTL for this project.
      4. hoejoo.lee: I've been working with Avinash develop AI/ML workflow over the past three years and look forward to working with you.
      5. Jack Murray: how familiar are you with Linux Foundation tooling and approaches? Have you done other projects or activities with Linux foundation?
      6. hoejoo.lee: About 2 years ago I joined the EdgeX project with Linux Foundation.
      7. Jack Murray: Sridhar from LF can help.
      8. Avinash (Samsung): Besides Hoejoo, we also have 4 or 5 members that can contribute to the project, and we are open to anybody who's really interested to contribute.
      9. Jack Murray: TOC members and other participants are to share this information with your companies and see if you might work directly in this area.
      10. Avinash (Samsung): Feel free to reach out to me if you're interested. A bit more on the G release scope – again there should be no impact to other projects in G, but in the future there may be impact to SMO, Near RT RIC and Non RT RIC projects.
      11. Sridhar Rao: are you considering any specific use case for demonstration?
      12. Avinash (Samsung): Yes, in the next slide, we'll reuse the QoE prediction use case with the framework.
      13. Jack Murray: I encourage you to start dialogues with other projects, like Near RT RIC, xAPP projects, and SMO, from the beginning so they are all on the same page to make sure all your development could be most effective, and to avoid recreating work.
      14. Avinash (Samsung): Sure. Even if we want to do something in the upcoming releases, we have to start the dialogues now and keeps the discussion going.
      15. Former user (Deleted): Should you use O1 to send the models to Near RT RIC and Non RT RIC?
      16. Avinash (Samsung): In G release we plan to deploy it manually.
      17. Jack Murray: The deployment is really part of the lifecycle management system. And that the configuration might be on O1.
      18. Former user (Deleted): How common APP lifecycle management works is still in the air and we have to keep an eye on that. I kind of noticed in this diagram at least you have a direct rest API between ML APP and assist APP and you're bypassing the DME in this case.
      19. Avinash (Samsung): Overall we're looking at this as one rApp. As we discussed in RSAC meeting the assistant APP in the future could potentially service many ML Apps. It might require for larger discussions in the specifications itself. As of now, we are looking at just deploying this APP like a regular rApp and the rest ML components we will deploy it manually. How they interact can be defined but REST is what we are recommending for this particular use case. For other use cases that want to use different interface and once standardized, we will support or align to it.
      20. Former user (Deleted): If we could connect it with perhaps a similar project or in some way will be a little bit better.
      21. Avinash (Samsung): From the larger orchestration perspective or from a functionality perspective, it is part of SMO. Until it is really standardized or there's a lot of discussions on that specification perspective, then integration will become more and more eminent. For now we thought was to get started with this but we welcome if any comments on that.
      22. Mahesh: I'm looking at this from an SMO perspective and the specifications will not guide implementation. As SMO already has, for example, from a data lake perspective, an influx db that you could start interacting with; and same thing about the Kafka bus.
      23. Avinash (Samsung): What we depicted here is to reuse the SMO framework, not going to redefine it.
      24. John Keeney (Ericsson EST): The influx db or Kafka bus access within SMO are only available currently to be the R1 interface.
        Your thoughts here is probably fine for the G release spoke, as it's like an end to end solution that will be essentially upstream into to OSC. We are basically postponing our discussions around where the scope overlap is, which would need ongoing over the next couple releases, they would need to be probably re-implementation of some of the solution presented here and to be more compliant with the O-RAN architecture and with the existing OSC integration environment.
      25. Avinash (Samsung): I completely agree. We never had a chance to discuss with you so any comment from you would be really valuable.
      26. Mahesh: I would welcome you to present this at the next SMO meeting.
      27. Former user (Deleted): What is the touch point with the OAM project, because they are implementing O1 protocol. This is where I'm a little confused: I can understand from a G release standpoint, it's OK as the implementation is pretty much stand alone. But my worry is, if you go down this path, later on you might have to do a whole lot of modifications to get those touch points with the Non RT RIC and SMO. I mean it's a great start, but I just feel like chicken and egg because not everything is specified in the specification.
      28. Avinash (Samsung): To keep it simple, we have internally discuss about this and we are looking at kind of manually doing the deployment right now. With respect to interface and model storage, I think the APP management needs some discussion. In terms of rework, the AI management function and the training platform, most of the components would probably continue as we don't have those touch points or integration points discussed. There might be some changes.
      29. Former user (Deleted): You have one touch point in Near RT RIC, one in SMO, and one inside the training platform so essentially three databases and the datalake outside of it. Can we consolidate the data stores?
      30. Avinash (Samsung): The datalake is purely from a training perspective and the remaining entities are more from an inference perspective. It may not be required to have both, unless both xApp and rApp use cases are supported.
      31. Jack Murray: The datalake is here for implementation, but in any production deployment, the datalake would be external.
      32. Avinash (Samsung): We have clearly called it out all the components which are marked by the gray color actually existing. We will reuse what is defined in the SMO project and we're not going to redefine the datalake when there's the influx db in the Near RT RIC. And for the APP deployment, we are looking at using the existing mechanism of deployment as well.
      33. John Keeney (Ericsson EST): Let's come back briefly to Rittwik's question about consolidating all these data stores. What we see here are the architecture picture, and a simplified view. There are a lot of steps and interfaces in the real data flow and coordination of the access. Let's try to boil this down and to fully understand all of these inter linkages, especially with existing platforms and functions.
      34. Avinash (Samsung): As we discussed, we will have a QoE prediction application to demonstrate the capability of the framework, which we will manually deploy. I think the data is in place and we will populate that into the data lake manually and use that for training and all the management will be done in a management function.I think that's broadly what we had with respect to the overall project and the overall project scope, as we all agree it's quite large and a lot of things are still under discussions and what we feel we can take it up as the initial scope for the G release.
      35. Jack Murray: Is there any any other kind of technical questions? I'd like to hear about the interest level in supporting the investment of the community towards this project, particularly from the other TOC members, and if any of the operators think that this is useful and important.
      36. Jakub Novy [DTAG]: I have to check with our colleagues and not able to give you the exact answer now.
      37. Jack Murray: I'm trying to spur the dialogue to promote the discussion and awareness to make it useful for the community. Before the H release I'm going to need to see a much better architecture on how this framework fits in as a framework, and added to the deployment without breaking things
      38. Avinash (Samsung): How do you propose to take this forward if you want to do it in G release?
      39. Jack Murray: You have roughtly 6 months to work in G release, after that I expect that architecture agreement to be in place with a lot more details, not necessarily the implementation. Also where did you post the slides?
      40. David Kinsey [AT&T]:Avinash you can post in the RSAC "G" release contribution folder.
      41. Jack Murray: I'm gonna push the vote for the project creation to the next week's TOC meeting. You can make a motion and post to the TOC reflector
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 Singh 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)
Collaboration with OAI
1. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time
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
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2022 07 28

Recording:

Meeting Recording:

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Date: Jul 28, 2022 08:58 AM Eastern Time (US and Canada)

Meeting Recording:
https://zoom.us/rec/share/gYuNT_nmBmtCoNmdI-3BrKWK8CiJTy9HESqq2b6tA8Crb1lGAQo7WGN6Zz_SFqY_.Zkfh8k5lZ2mN2RQQ

Agenda

Call for Scribe (minutes owner): Avinash Bhat
Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	X	David Kinsey
China Mobile	Jinri Huang Co-Chair		James Li	x
Deutsche Telekom	Jakub Nový	x	Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda		Anil Umesh
Nokia	Arunkumar Halebid		Thoralf Czichy	x
Orange	William Diego		Vincent Danno
Radisys	Ganesh Shenbagaraman	x	Manasi Padhy (→Ankit) ???
TIM	Andrea Buldorini
Wind River	Bin Yang		Jackie Huang	x
Viavi Solutions	Ultan Kelly	x	Kexuan Sun
Samsung	JinGuk Jeong	x	Avinash Bhat

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

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for TOC meeting (21st Jul 2022) approval: Motion to be proposed by Avinash Bhat approved by Thoralf and the Motion was approved.
Review of Today's Agenda.
1. Magma Project wants to present to O-RAN SC. request for a 10 min slot
  1. Amar Padmanabhan (PTL of Magma Project) presented the MOCN GW Overview. Slides can be posted on the Reflector (AI : Sridhar)
2. AI/ML Project Overview (Avinash) - The presentation to be continued next week
Release Votes and Approval
1. New Project Creation for AI/ML Project
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. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
  2. 2022-05-12: summary of the open issues
    1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
    2. Updating CLA for SCCL to align to the charter. This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
    3. Extend OSC SCCL. Open
  3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
  4. 2022-05-26: no news
  5. 2022-06-09: James Li: Request from SDFG co-chair to OSC PTLs to bring up any copyright requests to 3GPP/ETSI. Jack clarified on the past discussions pointing to the issue in referencing from code implementation to these source specification documents. This is still not a resolved issue. Jinri added comments to clarify that the SDFG request is more towards the list of historical requests to 3GPP. Jack and Jinri will check the past requests. PTLs are requested to forward any past request to Jinri. John Keeney pointed to challenges in determining when to make a copyright request. Jack said in view of all these challenges, the legal team is working on a broad approval for use in open source software.
  6. 2022-06-23: Jack: Copyright request is still ongoing, in next few months some progress is expected
  7. 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)
  8. 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)
  9. 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.
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
3. Challenges for the OSC community (as report to EC)
4. 1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
  2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
  3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before the discussion at the meeting.
  4. 2022-05-26 Jinri: item still open for contributions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
  5. 2022-06-02: John Keeney: Raised a question regarding status of the survey
    Jinri: EC could not take it up due to other urgent business, but some people are in process of initial analysis.
  6. 2022-07-14 : There is no update this week
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
2. "G" Release
3. OSC Lab
  1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
  2. 2022-06-02: PTP clock sync issue update
    Ankit: Checked scripts for synchronization of the clock but ptp sync still failing to get in sync with grandmaster and internal clock only used by ODU.
    David: We have checked Hardware and configuration. Server 190 is being connected to the home gateway and configured as expected. Clock sync between grandmaster and fronthaul gateway has been verified. Issue needs to be debugged further
  3. 2022-06-09: Luis: to discuss with Rich and to have a remote debug session for clock sync issue.
  4. 2022-06-16: Issue still remains, Jack to have a check what next step could be to resolve this issue
  5. 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
4. 5G Super Blueprint status - to be considered for H release.
  1. 2022-07-21 : David mentioned that there hasnt been any progress on this. Decided to move to H release. (Updated the title header from G to H to reflect the same)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Sridhar Rao /Release Planning: Weekly TOC Scheduling
2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
  1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.
    1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
    2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
    3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
    4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
    5. 2022-05-12: workshop likely to be on Wednesday May 18th. James Liwill check and confirm
    6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
    7. 2022-06-16:David: AI ML repo integration discussed in the RSAC and recommendation is to go ahead with AI ML as an independent project
      Jack: Assessment of capabilities, target plan to be discussed for AI ML project
      Avinash: A detailed plan to be presented
  2. "G" Release
    1. Jack: How do we track our support of MVP?
    2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
    3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
    4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack: priority should be given to those exploiting and validating OSC software capability
    5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
    6. 2022-06-02 Action point : Jack to update G release timeline calendar for review and voting
      Jack: G release planning status
      David: We are running behind for G release planning, it could not be done in the last RSAC due to limited participants
    7. 2022-06-09: Jack: Raised a question regarding O-DU-LOW new functionality under G release?
      Luis: Incremental improvements and optimization expected in G release but as of now no new feature expected on ORAN Fronthaul interface
      Jack: All PTLs to update and provide tentative G release plan to Jinri for the presentation on 13th June in f2f meeting
    8. 2022-06-16: Jack: G release page to be linked in Release section and subsequent sections to be added
      David: To schedule each project planning (in RSAC) in first three weeks of G release
      Jack: Activity to plan in G release: Deployment of all modules with health check
      Rittwik: Raised a query to have a specific use case for Taiwan lab
      Jack: Both labs repeating same use case independently helps in removing local dependency and better documentation for end user to use and replicate the system
    9. 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
    10. 2022-07-21 : Review of all project plan are in progress
      1. primer for "G" Release (Action : David/Rittwik)
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 Singh 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)
Collaboration with OAI
1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time
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
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2022 07 21

Recording:

Meeting Recording:

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Date: Jul 21, 2022 08:56 AM Eastern Time (US and Canada)

Meeting Recording:
https://zoom.us/rec/share/ULt8HnFJcVTbCXw2g9yFOn2PZF7IM_OdGqXsZ3bm5e88TcvB9tO4_lTxyxIpIgse.xLpWDLUM1RyD-2nQ

Agenda

Call for Scribe (minutes owner): Avinash Bhat
Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	X	David Kinsey
China Mobile	Jinri Huang Co-Chair	x	James Li
Deutsche Telekom	Jakub Nový	x	Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Nokia	Arunkumar Halebid	x	Thoralf Czichy
Orange	William Diego		Vincent Danno
Radisys	Ganesh Shenbagaraman	x	Manasi Padhy (→Ankit) ???
TIM	Andrea Buldorini	x
Wind River	Bin Yang		Jackie Huang
Viavi Solutions	Ultan Kelly	x	Kexuan Sun
Samsung	JinGuk Jeong		Avinash Bhat	x

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

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for TOC meeting (14th Jul 2022) approval: Motion to be proposed by Avinash Bhat seconded by Jinri Huang. Motion was approved.
Review of Today's Agenda.
1. No new agenda for this week
Release Votes and Approval
1. No Items for Approval this week.
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. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
  2. 2022-05-12: summary of the open issues
    1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
    2. Updating CLA for SCCL to align to the charter. This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
    3. Extend OSC SCCL. Open
  3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
  4. 2022-05-26: no news
  5. 2022-06-09: James Li: Request from SDFG co-chair to OSC PTLs to bring up any copyright requests to 3GPP/ETSI. Jack clarified on the past discussions pointing to the issue in referencing from code implementation to these source specification documents. This is still not a resolved issue. Jinri added comments to clarify that the SDFG request is more towards the list of historical requests to 3GPP. Jack and Jinri will check the past requests. PTLs are requested to forward any past request to Jinri. John Keeney pointed to challenges in determining when to make a copyright request. Jack said in view of all these challenges, the legal team is working on a broad approval for use in open source software.
  6. 2022-06-23: Jack: Copyright request is still ongoing, in next few months some progress is expected
  7. 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)
  8. 2022-07-21 : Meeting planned today and there will be update on this topic next week. The current focus in on O-RAN (doesnt cover 3GPP, ETSI etc)
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
3. Challenges for the OSC community (as report to EC)
4. 1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
  2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
  3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before the discussion at the meeting.
  4. 2022-05-26 Jinri: item still open for contributions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
  5. 2022-06-02: John Keeney: Raised a question regarding status of the survey
    Jinri: EC could not take it up due to other urgent business, but some people are in process of initial analysis.
  6. 2022-07-14 : There is no update this week
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
2. "G" Release
3. OSC Lab
  1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
  2. 2022-06-02: PTP clock sync issue update
    Ankit: Checked scripts for synchronization of the clock but ptp sync still failing to get in sync with grandmaster and internal clock only used by ODU.
    David: We have checked Hardware and configuration. Server 190 is being connected to the home gateway and configured as expected. Clock sync between grandmaster and fronthaul gateway has been verified. Issue needs to be debugged further
  3. 2022-06-09: Luis: to discuss with Rich and to have a remote debug session for clock sync issue.
  4. 2022-06-16: Issue still remains, Jack to have a check what next step could be to resolve this issue
  5. 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
4. 5G Super Blueprint status - to be considered for H release.
  1. 2022-07-21 : David mentioned that there hasnt been any progress on this. Decided to move to H release. (Updated the title header from G to H to reflect the same)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Sridhar Rao /Release Planning: Weekly TOC Scheduling
2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
  1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.
    1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
    2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
    3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
    4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
    5. 2022-05-12: workshop likely to be on Wednesday May 18th. James Liwill check and confirm
    6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
    7. 2022-06-16:David: AI ML repo integration discussed in the RSAC and recommendation is to go ahead with AI ML as an independent project
      Jack: Assessment of capabilities, target plan to be discussed for AI ML project
      Avinash: A detailed plan to be presented
  2. "G" Release
    1. Jack: How do we track our support of MVP?
    2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
    3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
    4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack: priority should be given to those exploiting and validating OSC software capability
    5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
    6. 2022-06-02 Action point : Jack to update G release timeline calendar for review and voting
      Jack: G release planning status
      David: We are running behind for G release planning, it could not be done in the last RSAC due to limited participants
    7. 2022-06-09: Jack: Raised a question regarding O-DU-LOW new functionality under G release?
      Luis: Incremental improvements and optimization expected in G release but as of now no new feature expected on ORAN Fronthaul interface
      Jack: All PTLs to update and provide tentative G release plan to Jinri for the presentation on 13th June in f2f meeting
    8. 2022-06-16: Jack: G release page to be linked in Release section and subsequent sections to be added
      David: To schedule each project planning (in RSAC) in first three weeks of G release
      Jack: Activity to plan in G release: Deployment of all modules with health check
      Rittwik: Raised a query to have a specific use case for Taiwan lab
      Jack: Both labs repeating same use case independently helps in removing local dependency and better documentation for end user to use and replicate the system
    9. 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
    10. 2022-07-21 : Review of all project plan are in progress
      1. primer for "G" Release (Action : David/Rittwik)
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 Singh 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)
Collaboration with OAI
1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time
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
Planning for Next Meeting
1. Magma Project wants to present to O-RAN SC. request for a 10 min slot (Sridhar)
2. AI/ML Project Overview
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2022 07 14

Recording:

Meeting Recording:

Topic: Zoom3 O-RAN SC's Personal Meeting Room
Start Time: Jul 14, 2022 08:57 AM

Meeting Recording:
https://zoom.us/rec/share/USiCKncwcJ_Z2NfW24BB5t4bZtliKpd5EiZResUGJ6HyT-bkMFJBo55HQ61eBSs9.LEQyzxS89jtxngbP

Agenda

Call for Scribe (minutes owner): Avinash Bhat
Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	X	David Kinsey
China Mobile	Jinri Huang Co-Chair		James Li	X
Deutsche Telekom	Jakub Nový	X	Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Nokia	Arunkumar Halebid	x	Thoralf Czichy
Orange	William Diego		Vincent Danno
Radisys	Ganesh Shenbagaraman	x	Manasi Padhy (→Ankit) ???
TIM	Andrea Buldorini	x
Wind River	Bin Yang		Jackie Huang	x
Viavi Solutions	Ultan Kelly	x	Kexuan Sun
Samsung	JinGuk Jeong	x	Avinash Bhat

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

Review and Agree to Minutes of Previous Meeting
1. Decision: Minutes for TOC meeting (30 Jun 2022) approval: Motion was proposed by Ganesh Shenbagaraman seconded by John-Paul. Motion was approved
Review of Today's Agenda.
1. GS getting started "site space" cleanup: Getting Started (Proposed by Thoralf/Mahesh)
2. From RSAC Meeting : Creation of new project for AI/ML
Release Votes and Approval
1. No Items for Approval this week.
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. This is currently stalled and we are waiting on updates from O-RAN legal team. 2022-04-06, 2022-04-13, 2022-04-20 : no major progress/updates.
  2. 2022-05-12: summary of the open issues
    1. Response from O-RAN has not addressed it yet. It is clarified that O-RAN EC is in charge of it.
    2. Updating CLA for SCCL to align to the charter. This was approved by TOC but not updated to the OSC site – equivalent to the one already there in Specification Code Project. Refer to Stephan (with support from the community).
    3. Extend OSC SCCL. Open
  3. 2022-05-19: Jinri: O-RAN (Brian) is addressing previous request from TOC
  4. 2022-05-26: no news
  5. 2022-06-09: James Li: Request from SDFG co-chair to OSC PTLs to bring up any copyright requests to 3GPP/ETSI. Jack clarified on the past discussions pointing to the issue in referencing from code implementation to these source specification documents. This is still not a resolved issue. Jinri added comments to clarify that the SDFG request is more towards the list of historical requests to 3GPP. Jack and Jinri will check the past requests. PTLs are requested to forward any past request to Jinri. John Keeney pointed to challenges in determining when to make a copyright request. Jack said in view of all these challenges, the legal team is working on a broad approval for use in open source software.
  6. 2022-06-23: Jack: Copyright request is still ongoing, in next few months some progress is expected
  7. 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)
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
1. F2F Meeting
  1. Jack: We need to be prepared for the June one. We have some items as part of the F Release and planning for the G Release.
  2. 2022-04-06: Jack and Jinri confirmed that it's still a virtual meeting. Action Point: Rittwik and RSAC to prepare for this meeting. 2022-04-20 : Open
  3. 2022-05-05: Jinri: no details on the agenda for the June vF2F are available yet.
  4. 2022-05-19: if people have topics to raise to the F2F, they are invited to share with Jinri and the group by email
  5. 2022-05-26; Jinri: dates are set to June 13th-17^th. David: proposal to hold OSC session on Monday 13^th , time slot#2. One hour should be sufficient for status and workplan presentation
  6. 2022-06-02: David: As first slot of O-RAN vf2f is on June 13, all PTLs to provide slides to David for F release update and G release plan
  7. 2022-06-09: David: Copied F release update from the F release status page update. But for G release tentative plan most of the projects do not have any update.
    Luis will be updating F release status page
    All PTLs to update tentative G release plan to be presented on 13th June in f2f meeting
  8. 2022-06-16: Jack: Thanks David and other members part of f2f participation (13th June)
    John Keeney: Raised a question about mechanism for getting feedback for f2f presentation
    David: MVP and TIFG are two ways to get feedbacks but as TIFG is more focus on testing hence with MVP there is a better chance to get feedback.
    Jack: Suggested to figure out ways to get feedback from real users of software
  9. 2022-06-23: RSAC committee to track MVP items and have a tracker table
  10. 2002-07-14: Jinri : Updated on PR and O-RAN Alliance F2F Meeting (Oct 17-21 @Madrid, Spain). G Release planning and H Release
2. O-RAN ALLIANCE industry summit will take place in June, with both live and virtual events.
3. Plugfest
  1. Jinri: There are 2 plugfests this year. It will be great if we can have regular updates on the preparation work.
  2. Jack: 2022-03-30: I don't see Tracy today. We will talk about it next week.
  3. 2022-04-06: Action Point: Jinri to check details and come back with more information. O-RAN members should have received call for participation (with deadline and host information). 2022-04-20: Open
  4. 2022-05-19 Information about the Spring Plug Fest shared by Tracy
4. O-RAN spending
  1. 2022-04-06
    1. O-RAN is collecting spending request. Jinri sent e-mail on this to TOC mailing list.
    2. David responded with potential need for simulation tool
    3. Jinri reminded participants of the meeting to check for any additional spending needs.
    4. 2022-04-20: David sent inquiry to Viavi regarding replacing on-loan "network appliance" solution with software. No response. We assume to continue with the "network appliance" model. Ultan requested some additional information from David (cc James+Jinri).
    5. 2022-05-05: David got info from Viavi. Benefits on the solution are still under evaluation.
5. Challenges for the OSC community (as report to EC)
  1. 2022-04-20 James and Jinri: are starting the work on identifying any challenges for the OSC community (as report to EC). Jinri might request help from PTLs (via reflector/mailing list).
  2. 2022-05-05 Jinri sent out a survey. PTLs are invited to contribute with identified issues.
  3. 2022-05-19 Jinri gives a summary of the survey. AP Jinri will start a review on TOC email reflector. Members are invited to review the list of issues and identify potential way forward before the discussion at the meeting.
  4. 2022-05-26 Jinri: item still open for contibutions. On Licensing issues, it could be beneficial to list the individual licenses that need to be addressed by O-RAN. This would speed up O-RAN review
  5. 2022-06-02: John Keeney: Raised a question regarding status of the survey
    Jinri: EC could not take it up due to other urgent business, but some people are in process of initial analysis.
  6. 2022-07-14 : There is no update this week
Old business and Status of Open Actions
1. "F" Release:
  1. 2022-05-18: Timeplan review
    1. Release is planned by end of June. Large scale software changes should be completed by the end of this week, in order to have time to test and release
    2. Integration and testing page for F release in https://lf-o-ran-sc.atlassian.net/wiki/display/IAT/F+Release+Integration+and+Testing
  2. 2022-05-19: Jack: by end of june we will also have to prepare the usual Press Release. It is expected that PTLs would have to update their project content and status in the release table (within 1 week). This will be used as baseline for the press release
  3. 2022-05-26: at the next meeting we will go through the status of the individual projects so as to start the code scan in the following days
  4. 2022-06-02: Jack: Tracking F release status page update
    Near-Real-time RIC: To be updated
    Near-Real-time RAN Intelligent Controller Platform: To be updated
    Non-Real time RIC: Updated
    OAM: To be updated
    OCU: To be updated
    ODU-HIGH: To be updated
    ODU-Low: To be updated
    SIM: To be updated
    INF: To be updated
    INT: James and Sridhar: To continue exploring tools and solution for cross platform test framework for integration and testing
    DOC: All project individually documents for each release but to have a consolidated documentation is an open topic
    SMO: To be updated
    All PTLs should update F release status in the release table to start code and license scan in following days
  5. 2022-06-09: Sridhar: To coordinate software scan activity for all projects to have a report next week
    Jack: Branching for F release on 20th June 2022 followed by package and documentation release on 30th June 2022
  6. 2022-06-16: Sridhar: Scanning is ongoing and report expected to be released next week
    Jack: PTLs to quickly respond to any issues reported in scanning as it may delay “F” release plan
  7. 2022-06-23: Sridhar: License scan completed for all except com projects (com/golog, com/log, com/pylog) and expected to complete this week. There is no issue to be reported
    Mahesh: For SMO there are 4 repo two are ready for branch and remaining are being discussed with Sridhar regarding permission issue
    Luis: L1 binary for F release is expected at the end of the week. To update F release page as well the for O-DU-LOW part by next week
    Jack: Branching for all projects to be done by 30th June before TOC
    Thoralf: Docker image links are to be placed in F Release Integration and Testing
    Xiaohua: Jinri asked PTLs to share all F release highlight points for upcoming press release
  8. 2022-06-30: Sridhar: License scanning is completed and approved with LF
    Branching status for all projects:
    Near-Real-time RIC: KPI MON-GO not branched. Jack: to be pushed in maintenance F release
    Near-Real-time RAN Intelligent Controller Platform: Done
    Non-Real time RIC: Done
    OAM: Done
    OCU: NA
    ODU-HIGH: Done
    ODU-Low: Done
    SIM: Done
    INF: Done
    INT: NA
    DOC: NA
    SMO: Done
2. "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
3. OSC Lab
  1. 2022-05-26: Jack: : Lab issues for O-DU low integration should be solved. Also access to the lab is now available for interested members involved in integration and testing activity
  2. 2022-06-02: PTP clock sync issue update
    Ankit: Checked scripts for synchronization of the clock but ptp sync still failing to get in sync with grandmaster and internal clock only used by ODU.
    David: We have checked Hardware and configuration. Server 190 is being connected to the home gateway and configured as expected. Clock sync between grandmaster and fronthaul gateway has been verified. Issue needs to be debugged further
  3. 2022-06-09: Luis: to discuss with Rich and to have a remote debug session for clock sync issue.
  4. 2022-06-016: Issue still remains, Jack to have a check what next step could be to resolve this issue
4. 5G Super Blueprint status - to be considered for G release.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Sridhar Rao /Release Planning: Weekly TOC Scheduling
2. Requirements Software Architecture Committee (RSAC, link incl. meeting details)
  1. OTF Workshop scheduled for RSAC call on May-4 (8AM EDT) did not take place due to technical difficulties. It will be rescheduled.
    1. 2022-04-06: James talked about David Kinsey's mail on possible delay in OTF adoption. O-cloud usage should help with the current OTF-related issues. Details see David's e-mail.
    2. 2022-04-06: Rittwik reported issues with PTP standup not yet done. They are also trying to "templatize" the Viavi deploment to make it easier to deploy.
    3. 2022-04-13: Jack brought up: if Infrastructure (Jackie Huang ) area :Interest in the community to consider integration of any new upstream projects etc. and open to evaluate such opportunities. ; This would help this community for Ex. SMO : how to manage infra easily - kind of questions;.
    4. 2022-04-20: Environment not yet ready (OTF team and infrastructure team working on this)
    5. 2022-05-12: workshop likely to be on Wednesday May 18th. James Liwill check and confirm
    6. 2022-05-19: James: OTF workshop did not take place. Code base was out of date and need update
    7. 2022-06-16:David: AI ML repo integration discussed in the RSAC and recommendation is to go ahead with AI ML as an independent project
      Jack: Assessment of capabilities, target plan to be discussed for AI ML project
      Avinash: A detailed plan to be presented
  2. "G" Release
    1. Jack: How do we track our support of MVP?
    2. David Kinsey: Rittwik and I do coordinate, but do not measure. We will work to see how we measure.
    3. 2022-04-06: Jack called for first input. RSAC planning committee will again coordinate.
    4. 2022-05-12: Rittwik: for “G” release with do not expect to implement many MVP use cases. Which ones still TBD. Jack: priority should be given to those exploiting and validating OSC software capability
    5. 2022-05-26: James Li : in preparation for release G software, PTLs should plan providing information about the characteristics of the code that could help planning integration and testing activity beforehand
    6. 2022-06-02 Action point : Jack to update G release timeline calendar for review and voting
      Jack: G release planning status
      David: We are running behind for G release planning, it could not be done in the last RSAC due to limited participants
    7. 2022-06-09: Jack: Raised a question regarding O-DU-LOW new functionality under G release?
      Luis: Incremental improvements and optimization expected in G release but as of now no new feature expected on ORAN Fronthaul interface
      Jack: All PTLs to update and provide tentative G release plan to Jinri for the presentation on 13th June in f2f meeting
    8. 2022-06-16: Jack: G release page to be linked in Release section and subsequent sections to be added
      David: To schedule each project planning (in RSAC) in first three weeks of G release
      Jack: Activity to plan in G release: Deployment of all modules with health check
      Rittwik: Raised a query to have a specific use case for Taiwan lab
      Jack: Both labs repeating same use case independently helps in removing local dependency and better documentation for end user to use and replicate the system
    9. 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
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 Singh 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)
Collaboration with OAI
1. 2022-05-05: James and Jinri got in touch with OAI about contributions in the area of O-CU development. First contributions in the context of F release are under evaluation. Jack reminded that licensing approach of OAI need to be verified before source-code adoption is agreed. Binary/test fixture solution are possible as an alternative
2. 2022-05-12: Meeting with OAI is planned later this week. One agenda item will be clarifying options to use OAI code in OSC projects
3. 2022-05-19: call rescheduled to tomorrow (May 20th). Christian (Orange) is in OAI board and will take the action to handle the bilateral communication
4. 2022-05-26: discussed with OAI last week. Licensing will be addressed by OAI and reported next time
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)
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)

2022 07 07

Recording:

The Meeting was cancelled

Meeting Recording:

As there was no meeting there is no recording updated

Browser not supported