What is the handover strategy between satellites in a LEO constellation for continuous service?
LEO Handover
Inter-satellite links (ISLs) add another dimension to handover: traffic can be routed through the constellation mesh between satellites, so a handover at the user terminal does not necessarily require a handover at the gateway. This reduces the gateway handover frequency and enables global routing without ground relays. SpaceX's Starlink V2 satellites include laser ISLs operating at 100+ Gbps, enabling global mesh networking above the atmosphere.
| Parameter | GEO | MEO | LEO |
|---|---|---|---|
| Altitude | 35,786 km | 2,000-35,786 km | 200-2,000 km |
| Latency (one-way) | ~270 ms | 50-150 ms | 1-20 ms |
| Coverage per Sat | Full hemisphere | Regional | Local footprint |
| Handover | None | Periodic | Frequent |
| Path Loss (Ku-band) | ~206 dB | 190-206 dB | 170-190 dB |
- Performance verification: confirm specifications against the application requirements before finalizing the design
- Environmental factors: temperature range, humidity, and vibration affect long-term reliability and parameter drift
- Cost vs. performance: evaluate whether the application demands premium components or standard commercial grades
Frequently Asked Questions
How does handover affect latency?
During a well-executed make-before-break handover: the latency increase is minimal (< 50 ms). During a break-before-make handover: there is a brief outage (100-500 ms) that may cause TCP retransmissions and noticeable glitches in real-time applications. The network-level protocol stack must handle these transitions gracefully with buffering and multi-path redundancy.
What happens at high latitudes?
At high latitudes (> 60°), inclined-orbit LEO satellites have more frequent overpasses and longer visibility windows, actually improving the handover situation. Polar regions may have coverage gaps with non-polar orbits (the Starlink constellation includes a polar shell for coverage at > 70° latitude).