HoCCA
ALL_REAL · measured Starlink paths
No synthetic path
Public measurements · sys-uos Starlink-on-the-Autobahn

Real Starlink path dynamics. Zero synthetic path.

Capacity and RTT come from published dish measurements (UDP iperf + ICMP). The MEASURED series is ground truth. CCA curves are algorithm replays on that same measured path — not a made-up LEO generator. Quantify recovery and goodput lift across every window; stress the mobile bridge harder.

Measurement window
Real Starlink Standard-plan UDP download + ICMP RTT from the same dish (paired sessions).
Stationary windows
Mobile bridge · stress harder
CCA replayDataset

Suite quantification

Lift + recovery across ALL_REAL windows. Units stay separated: HO-level bootstrap (seconds post-handover) vs sample-level freeze series (binary 0/1). Sensitivity panel varies the ≥50% recovery definition.

Run the full suite for lift tables, threshold sensitivity (≥30–80%), HO-level bootstrap CIs, and sample-level freeze series — kept on separate tabs so units never blur.

Method & scientific honesty

ALL_REAL policy — what is measured vs what is algorithm replay.

What is real
  • Capacity = published UDP iperf download (bps @ ~1 Hz) from Starlink-on-the-Autobahn Stationary.
  • RTT / loss = published ICMP series from the same dish/plan.
  • Dataset schedules UDP and ICMP in adjacent sessions; we pair the nearest sessions (offset listed per window) — both series are real, not generated.
  • Mobile bridge window uses real Autobahn obstruction loss events.
  • MEASURED curve is ground-truth goodput from the UDP file — no CCA in the loop.
What is still a model
  • CUBIC / BBR / LeoAware / LeoForge / HoCCA are algorithm replays on the measured path (same idea as LeoReplayer) — not kernel captures of those CCAs on Starlink.
  • BBR is educational, not bit-exact BBRv3.
  • Handover ticks are detected from RTT/capacity structure in the measurement, not Starlink internal reconfig logs.
  • No synthetic path generator remains in this lab.