Low-Latency Volumetric Video Conferencing in Congested Networks Through L4S

Current networking solutions are unable to satisfy the low-latency requirements of real-time volumetric video conferencing when faced with heavy congestion scenarios. Traditional congestion controllers use packet loss or the change in round-trip time (RTT) to estimate the bandwidth. Commonly, this method is too slow as congestion has already occurred and the receiving user has already experienced a latency spike. Low latency, low loss and scalable throughput (L4S), recently published as RFC 9330, wants to alleviate this problem by aiming for sub 1 ms queuing delay for low-latency traffic by using accurate explicit congestion notification (AccECN) packet marking to notify applications of early congestion. We propose an L4S-based pipeline for volumetric video delivery, which achieves a more consistent latency under congestion compared to web real-time communication (WebRTC). In addition, L4S bandwidth estimation achieves a 45% faster convergence compared to Google congestion control (GCC) estimation, commonly used in WebRTC. Furthermore, in our detailed evaluation setup the L4S application experiences no packet loss, while the WebRTC-based version suffers from irrecoverable packet loss, resulting in 3% of frames being undecodable.

Authors

Institutions

Publication Details

Published
2025-03-26
DOI
https://doi.org/10.1145/3712676.3714443
Primary Topic
Telecommunications and Broadcasting Technologies
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Low-Latency Volumetric Video Conferencing in Congested Networks Through L4S

Chia‐Yu Chang, Jeroen van der Hooft, Patrice Rondão Alface, Filip De Turck et al.
Telecommunications and Broadcasting Technologies
article

Low-Latency Volumetric Video Conferencing in Congested Networks Through L4S

Chia‐Yu Chang, Jeroen van der Hooft, Patrice Rondão Alface, Filip De Turck, Koen De Schepper, Danny De Vleeschauwer, Tim Wauters, Peter Steenkiste, Matthias De Fré
article en

Abstract

Current networking solutions are unable to satisfy the low-latency requirements of real-time volumetric video conferencing when faced with heavy congestion scenarios. Traditional congestion controllers use packet loss or the change in round-trip time (RTT) to estimate the bandwidth. Commonly, this method is too slow as congestion has already occurred and the receiving user has already experienced a latency spike. Low latency, low loss and scalable throughput (L4S), recently published as RFC 9330, wants to alleviate this problem by aiming for sub 1 ms queuing delay for low-latency traffic by using accurate explicit congestion notification (AccECN) packet marking to notify applications of early congestion. We propose an L4S-based pipeline for volumetric video delivery, which achieves a more consistent latency under congestion compared to web real-time communication (WebRTC). In addition, L4S bandwidth estimation achieves a 45% faster convergence compared to Google congestion control (GCC) estimation, commonly used in WebRTC. Furthermore, in our detailed evaluation setup the L4S application experiences no packet loss, while the WebRTC-based version suffers from irrecoverable packet loss, resulting in 3% of frames being undecodable.

Ghent University (BE), Nokia (Belgium) (BE)
Openalex Percentile: Top 92%
Telecommunications and Broadcasting Technologies
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Low-Latency Volumetric Video Conferencing in Congested Networks Through L4S — Chia‐Yu Chang, Jeroen van der Hooft, et al. · (2025) | TGRS Research Map | TGRS