Home » Blog » Learning » NTN » Blog # 137 – NTN – Mobility Management and Handover Challenges in LEO-Based Non-Terrestrial Networks

As I continue my structured exploration of Non-Terrestrial Networks (NTN), the next critical dimension is mobility management in LEO systems.

As Non-Terrestrial Networks (NTN) evolve under 3GPP Release 17 and Release 18 enhancements, mobility management has emerged as one of the most defining engineering challenges in Low Earth Orbit (LEO) systems.

Unlike terrestrial cellular networks, mobility in LEO-based NTN is fundamentally redefined.

In terrestrial systems:

The user moves.
The cell remains fixed.

In LEO NTN:

The satellite (and its beams) move at orbital velocity.
The user may be stationary.
Or both the satellite and the user may move simultaneously.

This multi-dimensional mobility changes radio design, signaling strategy, synchronization mechanisms, and architectural decisions.

1. LEO Mobility Dynamics: Orbital Mechanics Meets RAN Design

Typical LEO constellations operate at altitudes between 500 km and 1,200 km.

At these altitudes:

Orbital velocity ≈ 7.5 km/s
Satellite visibility window per user ≈ 5–15 minutes
Spot beams continuously sweep across the Earth

This results in:

Frequent beam transitions
Predictable but rapid satellite changes
Time varying Doppler shift
Dynamic propagation delay

Unlike terrestrial systems where mobility is Randomised, LEO mobility is deterministic, governed by orbital mechanics.

However, deterministic does not mean simple.

2. Mobility Scenarios in LEO NTN

Scenario A: Stationary User, Moving Satellite

This is the most discussed case in NTN:

Rural broadband
Fixed enterprise terminals
Remote IoT deployments

Here:

The UE remains static.
The beam footprint moves.
Handover occurs because the satellite exits visibility.

This inverts terrestrial logic, mobility is network driven, not user driven.

Scenario B: Moving User, Moving Satellite (Dual Mobility)

This scenario is equally important and operationally more complex.

Examples include:

In-flight connectivity
Maritime broadband
Connected vehicles in remote regions

Here:

The satellite moves at ~7.5 km/s.
The user may move at:
- 250 m/s (aircraft)
- 15 m/s (vehicle)
- Variable maritime speeds

This creates compound Doppler effects and dynamic link geometry.

Implications:

✔ Rapidly changing elevation angle

✔ Combined Doppler contributions

✔ Increased handover frequency

✔ Complex beam selection strategy

✔ Higher risk of synchronization drift

Mobility management must now account for both orbital prediction and terrestrial movement.

3. Types of Handover in LEO NTN

Mobility in NTN is multi-layered.

A - Beam-Level Handover

As spot beams sweep across Earth, the UE may transition between beams within the same satellite.

Characteristics:

Short duration transitions
High frequency
Geometry driven triggers
Requires predictive beam timing

This is similar to intra-cell beam management but at much larger footprint scale.

B - Beam Hopping and Its Impact on Mobility

Beyond classical beam level and satellite level handovers, modern LEO systems increasingly employ beam hopping techniques.

Beam hopping allows the satellite to dynamically illuminate different ground areas in time multiplexed fashion rather than keeping all spot beams continuously active.

Implications for mobility:

• Cell availability becomes time dependent

• Users may experience scheduled coverage windows

• Handover decisions must account for beam activation timing

• Mobility events can be capacity-driven, not only geometry-driven

In high demand regions, beam hopping supports:

✔ Capacity concentration

✔ Power optimization

✔ Spectrum reuse efficiency

However, it also introduces an additional dimension to mobility:

A user may not only hand over due to satellite movement, but also due to dynamic beam activation patterns.

This makes mobility management tightly coupled with scheduling strategy and traffic load balancing.

C - Satellite-Level Handover

When a satellite exits visibility, service transfers to the next satellite in the constellation.

Characteristics:

Occurs every few minutes
Doppler profile changes abruptly
Timing advance must be recalculated
Control plane continuity becomes critical

This resembles inter-gNB handover but with orbital periodicity.

D - Inter-Gateway Handover

Particularly in transparent payload architectures:

The satellite acts as RF relay.
gNB resides on ground.
Feeder link gateway may change during satellite movement.

Impacts:

Core network re-routing
Backhaul latency shift
Session anchoring considerations

This dimension does not exist in terrestrial RAN.

4. Doppler Dynamics in LEO Mobility

At LEO speeds, Doppler shift magnitude can reach:

Several tens of kHz in Ku/Ka bands
Lower in S-band but still non-negligible

Key characteristics:

Maximum Doppler at low elevation angles
Near-zero Doppler at zenith
Time varying during each pass

In dual mobility scenarios:

UE motion adds secondary Doppler component
Frequency compensation must be adaptive

3GPP NTN specifications introduce:

Pre compensation mechanisms
GNSS-assisted correction
Extended synchronization procedures

Without effective Doppler handling, mobility robustness collapses.

5. Propagation Delay and Timing Advance

One-way propagation delay in LEO typically ranges:

~2–4 ms (500–600 km, high elevation)
~6–8 ms at lower elevation angles

Compared to terrestrial macro cells (~100 µs), this is significantly higher.

Impact areas:

Extended Timing Advance support
HARQ timing adaptations
RACH procedure adjustments
MAC scheduling window modifications

Release 17 introduced NTN specific timing extensions to address these challenges.

6. Transparent vs Regenerative Payload Impact

Mobility behavior depends heavily on payload architecture.

Transparent Payload

Satellite acts as bent pipe relay
gNB located on ground
Mobility anchored terrestrially

Implications:

Gateway dependency
Feeder link sensitivity
Higher latency variation

Regenerative Payload

gNB functionality onboard satellite
Reduced feeder link dependency
Faster localized decision making

This reduces control plane roundtrip but introduces satellite resource constraints.

Architectural choice directly affects handover latency and interruption time.

7. Engineering Challenges in LEO Mobility

✔ Minimizing handover interruption time

✔ Ensuring seamless session continuity

✔ Managing signaling overhead

✔ Handling Doppler under dual mobility

✔ Supporting power-limited IoT devices

✔ Synchronizing prediction models with orbital ephemeris

Mobility in NTN is predictable, but prediction must be accurate and tightly integrated with RAN control.

8. Commercial and Service Impact

Mobility robustness directly influences:

Aviation broadband reliability
Maritime connectivity
Defense and emergency communications
Rural broadband experience

If handover reliability degrades:

SLA performance drops
Latency-sensitive services fail
User perception declines

Mobility reliability becomes a competitive differentiator.

Why This Matters for 6G

Future 6G networks envision:

Seamless terrestrial and non-terrestrial integration
Always-on connectivity
Global mobility continuity

Without robust NTN mobility mechanisms:

Vertical handover will be unstable.
Session continuity across layers will degrade.
Global coverage promises will remain theoretical.

Mobility is the glue between link budget, interference, and service continuity.

My Learning Focus Moving Forward

To deepen expertise in this domain, I am focusing on:

Beam level handover modeling
Orbital prediction assisted mobility optimization
NTN ↔ TN vertical mobility strategies
Delay-aware RRC parameter tuning
AI assisted mobility forecasting

Coming from an RF optimization background, NTN mobility feels like SON optimization extended into orbital mechanics.

The geometry has changed.

The optimization mindset remains the same.

Conclusion

In LEO based Non-Terrestrial Networks, mobility is not an edge case, it is the defining system condition.

Unlike terrestrial systems that optimize for user movement, LEO NTN must optimize for orbital dynamics and, increasingly, dual mobility environments.

Successful deployment requires:

Predictive handover strategies
Doppler-aware scheduling
Extended timing frameworks
Architecture aligned mobility anchoring
Tight NTN–TN integration

Mobility engineering will determine whether LEO NTN scales into mainstream 6G infrastructure or remains a specialized connectivity layer.