As LEO constellations evolve to include inter satellite links (ISL), the focus shifts from physical connectivity to intelligent traffic management. The presence of a dynamic orbital mesh introduces a new challenge: how to route traffic efficiently while maintaining 5G Quality of Service (QoS) guarantees.

Orbital routing is not simply terrestrial routing placed in space. It must account for deterministic satellite motion, dynamic topology changes, propagation delay variation, and 5G bearer level service constraints.

This article examines how routing and QoS enforcement are engineered in LEO based NTN systems.

1. Why Orbital Routing Is Different

In terrestrial networks:

• Nodes are mostly stationary
• Links are persistent
• Topology changes are event-driven

In LEO NTN:

• Satellites move continuously
• Inter satellite links form and dissolve predictably
• Gateway visibility windows change over time
• Propagation delays vary with geometry

This means routing must be both dynamic and predictive.

2. Deterministic but Dynamic Topology

Unlike terrestrial mobile networks, satellite motion follows predictable orbital mechanics.

This enables:

1. Precomputed routing tables based on orbital models
2. Scheduled path switching
3. Topology forecasting
4. Planned gateway handover

However, real time adaptation is still required due to:

• Traffic congestion
• Gateway outages
• Weather impacts
• Satellite anomalies

Modern systems often combine predictive modeling with real time Software Defined Networking (SDN) control.

3. Routing Models in LEO Constellations

Common approaches include:

• Static Snapshot Routing

Routing tables are updated at fixed intervals based on expected topology states.

• Time Evolving Graph Routing

The network is modeled as a time dependent graph where link availability changes over time.

• SDN Based Centralized Control

A centralized controller computes optimal paths and distributes forwarding rules to satellites.

• Distributed Onboard Routing

In regenerative payload systems, satellites may perform Layer 2 or Layer 3 routing locally.

The choice depends on:

• Transparent vs regenerative payload
• ISL capability
• Processing power onboard
• Latency constraints

4. QoS in 5G NTN

5G defines QoS flows with specific parameters such as:

• 5QI (5G QoS Identifier)
• Packet Delay Budget (PDB)
• Packet Error Rate (PER)
• Guaranteed Bit Rate (GBR) or non-GBR

In NTN, maintaining QoS is more complex because:

• Path length varies dynamically
• ISL hop count may change
• Propagation delay fluctuates
• Congestion may shift geographically

The routing system must ensure that bearer requirements are respected even as the topology evolves.

Ajazz AK820/AK820Pro Gaming Mechanical Keyboard Bluetooth 5.1/Wireless/C-Wired Customized Keyboard

5. Delay and Jitter Management

LEO propagation delay is significantly lower than GEO but still higher than terrestrial.

Key delay components:

• UE to satellite
• ISL hops
• Satellite processing
• Feeder link
• Core network

Routing decisions must balance:

1. Minimum hop count
2. Gateway proximity
3. Congestion level
4. QoS priority

Excessive ISL hops may increase jitter and degrade real-time services such as voice or URLLC type traffic.

6. Gateway Anchoring Strategy

In NTN, core network anchoring location impacts:

• Session continuity
• Handover complexity
• Latency
• Backhaul efficiency

Options include:

• Fixed regional anchoring
• Dynamic gateway selection
• Distributed core deployments

Orbital routing must align with anchoring policies to prevent unnecessary path stretch.

7. Transparent vs Regenerative Considerations

Transparent payload systems:

• Routing intelligence resides on the ground
• Satellites relay traffic without IP awareness
• Orbital routing primarily handled at gateway level

Regenerative payload systems:

• Satellites may inspect and forward IP packets
• ISL routing decisions can be executed onboard
• Greater flexibility but higher onboard complexity

This distinction significantly affects QoS enforcement capability.

8. Resilience and Traffic Engineering

Orbital routing enables:

• Load balancing across gateways
• Weather aware traffic shifting
• Congestion mitigation
• Disaster resilience

Advanced traffic engineering may include:

• QoS aware path computation
• Predictive congestion avoidance
• AI assisted route optimization

9. Engineering Challenges

Key challenges include:

• Fast routing convergence
• Limited onboard processing power
• Power constraints
• Doppler impact on link performance
• Synchronization across moving nodes
• Integration with 5G core QoS models

Successful NTN deployment requires tight integration between satellite transport design and 5G network engineering.

Conclusion

Inter Satellite Links create the physical space network. Orbital routing transforms it into an intelligent transport system.

In LEO based NTN, routing is no longer static path selection. It is predictive, QoS aware, and tightly integrated with 5G service models.

As NTN progresses toward 5G Advanced and future 6G architectures, orbital routing will become a defining capability for scalable, resilient, and service differentiated satellite networks.

The evolution from satellite access to orbital networking is now firmly underway.