Key takeaways
- Specify the radio functional split before selecting transport.
- Measure sustained busy-hour capacity at the site.
- Validate timing and holdover independently of broadband access.
Backhaul is not fronthaul
A mobile base station needs transport to the mobile core, but the exact requirement depends on where radio functions run. Backhaul from a self-contained base station is different from tightly timed fronthaul between split radio components. Do not assume that an Internet satellite connection can replace every optical link in a disaggregated radio design.
Fibre offers high capacity and relatively stable delay where construction is practical. LEO can make a remote site useful before a fibre build reaches it, or provide an independent backup. Its variable capacity, delay and loss must still fit the chosen radio architecture and the operator’s service requirements.
Build a busy-hour budget
Estimate concurrent users, uplink demand and protocol overhead rather than multiplying every subscriber by the advertised radio peak. Include management traffic and failover headroom. If a site promises emergency or priority traffic, reserve capacity and test how that policy behaves when the satellite path is congested.
For example, a small radio site with 80 Mbps of measured busy-hour downlink demand cannot assume that an occasional 150 Mbps satellite speed test provides adequate sustained capacity. Run a prolonged trial at the location and evaluate the lower tail of throughput as well as the upper tail of latency.
Timing and security
Check how the base station obtains frequency, phase and time. GNSS, local holdover and network-based timing have distinct failure modes. An arbitrary Internet tunnel should not be assumed to deliver telecom-grade timing. Protect backhaul with the mobile operator’s approved authentication and encryption architecture, and account for tunnel overhead and MTU.
Deployment gate
Obtain operator acceptance of the architecture before construction. Exercise loss of the primary circuit, GNSS degradation where safely simulated, and exhausted backup capacity. Confirm alarms reach operations over the surviving path. Use a staged service profile during satellite-only operation rather than allowing the radio access network to admit more traffic than the backhaul can carry.
From concept to acceptance
Worked design exercise
A rural base station carries 60 Mbps down and 12 Mbps up during its busiest hour. Adding 20% planning headroom gives 72 Mbps and 14.4 Mbps before any additional transport assumptions. If the proposed backup cannot sustain the uplink component, the operator must define admission control or a reduced service profile; a high download result does not solve the bottleneck.
Run the traffic mix through the intended encryption and routing chain. Check radio alarms, timing status and user-session recovery while failing the primary. Approval should come from the mobile operator's transport and radio teams together.
Regional compliance & specification note
Australia / ACMA. mobile access spectrum and satellite backhaul authorisation are separate obligations; the mobile operator must approve the deployment.
Germany / BNetzA. confirm the mobile network’s frequency rights and the satellite terminal’s operating conditions independently.
These are procurement checks, not a determination that a particular installation is authorised. Confirm the current equipment, service, site and operating mode with the relevant authority and provider.
Sources & further reading
Official references for standards, programme context and service terms. Worked examples and design checklists are editorial analysis; verify project-specific inputs before implementation.
- 3GPP · Study on NR support for NTN (TR 38.811)
- ACMA · Satellites and space systems
- BNetzA · Satellite earth stations
References reviewed 03 October 2026. Operator terms and regulatory documents may change.