Emulation vs Simulation: A Case Study from Congestion Control Algorithms in Low Earth Orbit Satellite Networks
2026-08-03 • Networking and Internet Architecture
Networking and Internet Architecture
AI summaryⓘ
The authors studied different methods for controlling internet traffic in Low Earth Orbit (LEO) satellite networks, which are tricky because of changing paths and delays. They tested many types of congestion-control algorithms using both simulations and emulations to see how they perform and to understand the strengths and weaknesses of each testing method. They found that simulations are great for large-scale and repeated tests but can miss some details of real systems, while emulations reveal these details but are harder to run at big scales. The authors shared useful advice on how to best combine both approaches to get reliable and practical results.
congestion controlLEO satellite networkssimulationemulationtransport stackpacingselective acknowledgment (SACK)reinforcement learninground-trip time (RTT)protocol evaluation
Authors
Aiden Valentine, Mihai Mazilu, James Knowles, Ian Wakeman, George Parisis
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.