🤖 AI Summary
This study addresses the significant challenges in evaluating congestion control algorithms for low Earth orbit (LEO) satellite networks, where high path dynamics, frequent non-congestive packet loss, and severe RTT fluctuations complicate performance assessment. For the first time, it systematically compares large-scale OMNeT++/INET simulations with Linux kernel-level emulation based on Mininet when evaluating algorithms such as Cubic, variants of BBR, LEO-specific protocols, and reinforcement learning approaches. The findings reveal that OMNeT++/INET excels in constellation-scale parameter sweeps but abstracts away critical transport stack implementation details, whereas Mininet-based emulation captures kernel-level behaviors at the cost of limited scalability and reproducibility. Building on these insights, the work proposes a hybrid best-practice methodology that effectively balances scalability, deployment fidelity, and experimental reliability.
📝 Abstract
Evaluating congestion control is inherently challenging because performance depends on the interaction between the congestion-control algorithm, transport stack, application behaviour, measurement process, and network dynamics. This challenge is growing as state-of-the-art protocols incorporate pacing, selective loss recovery, model-based control, and, more recently, reinforcement learning. Low Earth Orbit (LEO) satellite networks are a particularly demanding setting: rapidly changing paths, handovers, non-congestive loss, RTT variation, and transient hotspots all affect transport behaviour. This paper reports the lessons learned from an extensive evaluation campaign across both simulation and emulation for LEO satellite congestion control. We compare multiple classes of congestion-control algorithms, including Cubic, BBR variants, LEO-specific protocols, and reinforcement-learning-based control, using comparable implementations across OMNeT++/INET simulation and Mininet-based emulation with the Linux transport stack. This gives us a rare opportunity to examine not only protocol performance, but also the methodological strengths and limitations of each experimental environment. Our findings show that simulation is indispensable for constellation-scale exploration, controlled parameter sweeps, and future deployment studies, but can miss behaviours caused by production transport-stack mechanisms such as pacing, SACK, RACK, kernel timing, and rate sampling. Emulation exposes these implementation-dependent effects and provides a necessary validation step, but is harder to scale and less exactly repeatable. We distil these experiences into practical lessons for combining simulation and emulation to obtain results that are scalable, reproducible, and deployment-relevant.