Attendees & Representation

TAC Members and Project representatives should mark their attendance below 

Agenda

• Check Action Items & Topic Requests (Backlog)

• Presentation on Network Energy Savings @Tracy Van Brakle @Lincoln Lavoie

• Follow up on (OpenIDC)

• Follow up with @Fatih Nar on breakdowns and roadmaps on Observability AI Frameworks

• Any Other Topics

  • AI Readiness @Ranny Haiby

OpenIDC @cheng peng

• @cheng peng presented an updated version of the deck.

• Questions from the last TAC Meeting:

  • The TAC noted that the deck references existing repos and GSMA trial work but doesn't include links to the source code. Could you share the repo URLs so TAC members can review the codebase ahead of your formal presentation?

    • Answer: The source code repository link is: https://github.com/GSMATerminals/IMS-DC-SDK-Open-Source. Meanwhile, we will revise the PPT and send you the updated version in a timely manner later.

  • There was a question about whether the SDK targets the client/handset side, the server/network side, or both.. The architecture diagram appeared to show a handset-side implementation, but the TAC would like explicit clarification on what runs on the device versus what is required in the network.

    • Answer: All components of the SDK run on the terminal device and do not operate on network nodes. However, the SDK's operation requires support from the 5G IMS network. We will add a detailed description of this part to the PPT.

    • Summary: The SDK is implemented only on the terminal side. On the network side, it relies on various standard-compliant infrastructures to provide necessary signaling processing and data routing capabilities to respond to requests from the terminal.

  • The TAC is interested in understanding how the IMS DC SDK might integrate with or complement existing LFN projects, particularly ONAP and potentially O-RAN SC. The slides mention China Telecom's contributions to ONAP but don't describe how the SDK could tie into ONAP or other projects. Adding a section on cross-project opportunities would strengthen the proposal.

    • Answer: At present, the SDK has not yet been integrated or linked with other LFN projects such as ONAP.

  • The proposed name "OpenIDS" did not return any results in web searches, so the TAC understands this is still in progress. If you have any updates on the name, logo, or trademark status, please include them in your next presentation. If there is no registered name, logo, or trademark, that is okay. We can handle that as part of the Linux Foundation's Formation onboarding process instead of having you create them and then transfer ownership.

    • Answer: OpenIDS is only a preliminary internal name and logo designed by ourselves for the project. There are no officially registered names or logos at this stage. We will rely on LFN for the subsequent naming, logo design and trademark registration of the project.

  • Is there a specific chipset requirement or any chipset limitations?

    • Yes. The chipset protocol stack needs to support IMS Data Channel features.

  • Does this have any OS dependencies?

    • The open-source SDK is built for Android and can only run on Android systems.

• Additional Questions:

  • Why bring it to the LFN? It looks like a GSMA proof of concept.

    • Management from the LFN is needed to ensure the project's success.

AI Readiness:

• Ranny proposed a page LFN Projects Coding Agent Contribution Readiness to track project readiness and asked projects to provide their input.