Welcome to L4SBOA Discussions!

[pradeeban]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[Jeffrin2005]

@pradeeban Hi,
My name is Jeffrin Jojo. I would like to contribute to Alaska organization. I am currently learning Full Stack Development, TypeScript, and Python Django development and interested in collaborating with the Alaska organization.

Could you let me know if L4SBOA is a continuation or improvement needed project of L4S for GSoC 2025?
What are the expected ides for GsoC 2025?

Thank You 😊

[pradeeban]

@Jeffrin2005 the project that is implemented for GSoC 2024 is largely a basic prototype. So, most work in the project idea is left to be implemented. The already listed idea should give some hints. We will likely update it further in mid January.

[ASHISH-JHA94]

Hello @pradeeban,
I hope you're doing well. I am eager to contribute to the Alaska organization and its impactful projects. I have extensive experience working with React, Python, and Java, along with strong skills in both frontend and backend development.
I was particularly interested in this repository and would like to know if there are any open issues or specific areas where I can contribute.

[saksham-gera]

I seeks permission to extend the scope of the L4SBOA project, focusing on:

1. Validation of L4S in Telehealth Deployments:
   • Investigating the applicability of L4S for telehealth scenarios such as DICOM image transfer, real-time monitoring, and teleconsultations.
   • Examining how L4S interacts with traditional non-L4S traffic in mixed network environments.
2. Prototyping and Evaluation:
   • Developing L4S-enabled endpoints for telehealth using a Linux kernel with L4S patches.
   • Testing DICOM image transfer between two endpoints as a starting point, scaling to real-world telehealth deployments.
3. Addressing Telehealth Needs in Alaska:
   • Improving telehealth access for underserved communities with an emphasis on mitigating latency, loss, and throughput challenges in rural areas.
   • Engaging with ANTHC and other partners to tailor solutions for their operational needs.

Proposed Roadmap:

Phase 1: Infrastructure Setup and Initial Tests 
 •	Goal: Deploy and evaluate basic L4S capabilities in controlled environments.
 •	Set up a pair of L4S-enabled endpoints using Linux kernel patches.
 •	Test DICOM image transfer between endpoints under controlled network conditions.
 •	Benchmark L4S performance against classic congestion control protocols (e.g., TCP Cubic, BBR).

 Phase 2: Application Integration 
 •	Goal: Develop L4S-based prototypes for diverse telehealth applications.
 •	Extend testing to telemonitoring and video calls.
 •	Address intercompatibility between L4S and non-L4S traffic.
 •	Incorporate telemetry for performance monitoring and analytics.

 Phase 3: Deployment in Telehealth Scenarios
 •	Goal: Validate L4S performance in real-world telehealth deployments.
 •	Collaborate with ANTHC to test L4S in practical scenarios (e.g., patient consultations, monitoring, diagnostics).
 •	Measure impact on key metrics: latency, loss, throughput, and user satisfaction.
 •	Identify and implement optimizations based on deployment feedback.

 Phase 4: Documentation and Dissemination
 •	Goal: Publish findings and propose a scalable telehealth framework.
 •	Compile a comprehensive report and recommendations for deploying L4S in telehealth applications.
 •	Present results at relevant conferences or journals.
 •	Engage stakeholders for future collaborations and funding opportunities.

[saksham-gera]

Hey @pradeeban , could you please share a detailed roadmap or clarify your expectations for this project? Understanding the scope and key objectives will help me align my work properly from the start. Let me know any specific deliverables or milestones you have in mind!

[pradeeban]

@saksham-gera I like your proposed vision. See how you could utilize and extend the currently implemented L4S simulation prototype (in the L4SBOA repository).

[saksham-gera]

Thank you! I’ll review the current L4S simulation prototype in the L4SBOA repository and explore ways to extend and optimize it.

[ASHISH-JHA94]

The L4SBOA project is a React-based frontend application designed for telehealth use cases, such as video consultations, DICOM image uploads, and wearable device data integration. Currently, the project only has a frontend structure, and I need guidance on setting up the backend to support L4S (Low Latency, Low Loss, Scalable Throughput) nodes for network optimization.

The backend should handle:

• Communication between L4S nodes for low-latency data transfer.
• Integration with telehealth features like video calls, DICOM image processing, and wearable device data.
• Coexistence with non-L4S traffic.

I’m unsure about:

• Where and how to set up L4S nodes.
• How to integrate L4S nodes with the frontend.
• What backend technologies or frameworks to use.

can you little elaborate about backend.

[pradeeban]

Some simple backends such as DICOM senders/receivers (for example, Orthanc PACS) can be an easier goal. Setting up L4S nodes is basically, patching the Linux kernel with L4S (check for how Kolawole did this last GSoC following the public documentation from L4S).

The L4S nodes themselves are essentially, patched Linux servers. So, integrating with frontend is like integrating with regular TCP-based communication in Linux. (i.e., no additional steps would be necessary once you have L4S in place of classic TCP).