Bent-Pipe NTN
Also known as: Bent Pipe Non-Terrestrial Network, Transparent NTN Payload
Definition
A non-terrestrial network payload architecture in which the satellite relays signals transparently between the feeder link and service link — performing frequency conversion and amplification only — with all RAN baseband processing, demodulation, and routing performed at a ground gateway rather than onboard the satellite.
Key Points
- The satellite performs only frequency conversion and amplification; all demodulation, decoding, and RAN processing happens at the ground gateway
- Simpler and lower-cost to manufacture than a regenerative payload, since no onboard baseband processing hardware is required
- Every bit of user traffic transits the feeder link, making feeder link capacity and availability the binding constraint on total satellite throughput
- The dominant architecture for current commercial 5G NTN and high-throughput satellite deployments, though regenerative payloads are gaining adoption for latency-sensitive and resilience use cases
- A feeder link or gateway outage takes down every user under that satellite's beams simultaneously, since there is no onboard processing fallback
Concept
In a bent-pipe NTN deployment, the gNB (or the RAN function serving that role) runs at the ground gateway, not on the satellite. The satellite simply receives whatever RF signal arrives on the feeder link uplink, shifts it in frequency and amplifies it, and retransmits it on the service link downlink toward user equipment — and does the reverse for the return path. This means the satellite has no awareness of the data it is carrying; it is functionally identical to a very large, very high, RF repeater.
Explainer
The defining operational consequence of bent-pipe architecture is that satellite capacity is bounded by feeder link capacity, not by the payload's RF hardware — a satellite with abundant service-link spectrum still cannot exceed what its feeder link can carry to and from the ground, because every bit must cross that link. This also means gateway availability is a direct availability constraint on the entire satellite's service: a rain-faded or failed feeder link takes every user under that satellite's coverage offline simultaneously, which is why bent-pipe deployments depend on gateway diversity as a resilience measure rather than an optional enhancement. The tradeoff against regenerative payloads is straightforward — bent-pipe satellites are cheaper and faster to manufacture and qualify, since there is no onboard baseband processing chain to develop, test, and radiation-harden, which is why the majority of current commercial NTN and high-throughput satellite systems still use bent-pipe architecture despite the feeder-link bottleneck it introduces. For CE verticals, this matters most where a single point of gateway or feeder link failure would be operationally unacceptable — maritime and aviation broadband services built on bent-pipe NTN need dual-gateway diversity engineered in from the outset, since there is no onboard fallback path if the ground processing link fails.