Beyond DVB versus 5G: choosing the right architecture for the next generation of satellite network
- Satellite Evolution Group
- 4 days ago
- 5 min read
Operators need to extract as much useful capacity as possible from constrained RF resources. They also need to support services that move between satellite and terrestrial networks, work with mobile operators, and remain compatible with standards that are still developing. The choice affects the air interface, along with terminals, payloads, gateways, operations and commercial partnerships.
By Paul Tindall, Advanced Technology Lead for 5G NTN at TTP Plc
When a satellite operator specifies a new constellation, refreshes an existing network, or defines the next generation of user terminals, the waveform decision comes up early. It shapes modem design, payload processing, gateway architecture, terminal cost, silicon choices and the way services will be operated for years.
DVB-S2X and 5G NTN are now being considered for many of the same programs because they answer different pressures. DVB-S2X has been developed around efficient use of satellite spectrum and payload power. 5G NTN brings satellite access into the 3GPP system, with established mechanisms for identity, mobility, authentication, policy, quality of service, and integration with mobile networks.
Two standards with different starting points
DVB-S2X starts with the satellite link. It reflects decades of work on coding gain, roll-off, adaptive coding and modulation, rain fade, amplifier operation, and efficient forward-link delivery. Its design assumes that capacity and payload power are valuable and that small losses in link efficiency can have a direct effect on service economics.
The standard has continued to develop. DVB-S2X extends DVB-S2 with finer MODCOD (MODulation + CODing) steps, sharper roll-off filtering, and support for features such as beam hopping, which allows multi-beam systems to direct resources towards changing demand.
5G NTN begins with the mobile network. It inherits the 3GPP approach to subscriber identity, roaming, mobility, policy, QoS and core-network integration. Release 17 established normative support for NR-based NTN, with later releases extending coverage, capacity, broadcast support, regenerative payloads, and support for RedCap devices.
These starting points lead to different strengths. DVB-S2X concentrates on making the satellite bearer efficient. 5G NTN concentrates on making satellite access behave as part of a wider mobile system.
Why DVB-S2X remains difficult to displace
DVB-S2X remains a strong choice for high-throughput forward links, managed broadband, VSAT, aero, maritime, cellular backhaul, and content distribution. Operators understand its link adaptation, terminal models and operating practices, and a mature supplier base supports those deployments.
However, its value cannot be judged through bits per Hertz alone. Delivered capacity depends on the whole RF chain: power-amplifier back-off, EVM, phase noise, payload linearity, rain fade, antenna performance, terminal power, and usable link margin. A MODCOD that looks attractive in a simulation may deliver less capacity once those constraints are included.
DVB-S2X has been developed around these trade-offs. Coding, modulation, framing and adaptive operation are treated as parts of the same satellite problem. For an operator focused on moving large volumes of traffic efficiently through constrained spectrum and payload power, that experience carries real weight.
Why 5G NTN is attractive
Many new services require closer integration with terrestrial networks. Direct-to-device connectivity, mobile roaming, emergency coverage, IoT, sovereign networks and hybrid satellite-terrestrial services all benefit from common identity, policy, and mobility mechanisms.
5G NTN gives operators a route into the mobile supply chain and the 3GPP service model. It may simplify partnerships with mobile network operators, support access from standardized device classes, and reduce the amount of proprietary integration needed above the satellite link.
There are costs, however. NR was created for terrestrial cellular networks and has to accommodate satellite delay, Doppler, moving beams, large cells, constrained uplinks, and long terminal lifecycles. The relevant comparison is therefore economic as well as technical. Operators need to know how much spectrum, payload power, terminal power, silicon, and operational effort are required to deliver a given service.
A 5G NTN link may work technically and still be unattractive for a high-capacity satellite service. A highly efficient DVB-S2X bearer may also be the wrong foundation for a service that depends on roaming, mobile-network integration, or standard handset support.
LEO makes the system architecture more important
LEO introduces moving coverage, frequent beam changes, rapid geometry changes, Doppler, gateway handovers and choices around inter-satellite routing. The physical layer (PHY) remains critical, although the performance of the complete network now depends heavily on mobility, session continuity, scheduling, routing, and service assurance.
This strengthens the case for 5G NTN in networks that need to behave like mobile access systems. It also keeps the satellite link budget firmly in view. Poor Power-Added Efficiency (PAE), weak link adaptation, or excessive terminal power can damage the economics of a constellation regardless of the sophistication of the core network.
The service model provides a useful guide. DVB-S2X may suit managed enterprise connectivity, aero, maritime, backhaul, and high-throughput forward links. 5G NTN becomes more compelling where the service depends on mobile roaming, direct-to-device access, 5G core integration, or a longer-term route towards 6G.
Hybrid architectures need a clear boundary
Many operators will use both families of technology during the transition. The important decision is where the boundary sits.
An operator might run DVB-S2X on the satellite bearer and map services into a 5G core through a gateway. A terminal might support both waveforms. A digital payload might carry several waveform families. A future 5G NTN profile might also add satellite-specific optimization while retaining compatibility with the wider 3GPP system.
Each option moves cost and complexity to a different place. Gateway interworking introduces policy, QoS, latency, and assurance work. Dual-mode terminals add RF hardware, processing, power consumption, and certification. Multi-waveform payloads preserve options, while making onboard resource management harder. Service-layer integration can reuse an efficient bearer, with careful mapping required between satellite and mobile-network behavior.
A vague hybrid strategy can leave operators with duplicated systems and unclear ownership. The boundary should be chosen against specific services, terminal classes, and upgrade plans.
The PHY and operating model still decide the business case
Higher-layer integration cannot rescue a link that is too expensive to operate. Operators need to compare waveform efficiency under real RF conditions, terminal bill of materials, power consumption, hardware acceleration, observability, and field-upgrade options.
Operating expenditure deserves the same attention. A highly efficient bearer may require specialist tools and manual optimization. A 5G NTN system may bring familiar mobile-network processes, while adding complexity that produces little value for the intended service. Provisioning, diagnostics, software releases, vendor dependence, and terminal support can shape lifetime cost as much as headline spectral efficiency.
This makes flexibility valuable in areas where standards and markets are moving. Software-defined PHY functions, adaptable LDPC acceleration, open interfaces, detailed RF observability, and upgradeable terminal software can give operators room to change direction without replacing the full platform.
Choosing a practical route
DVB-S2X remains well suited to services where satellite efficiency, high throughput, and established operating models dominate. 5G NTN is stronger where mobile integration, roaming, common identity, and standardized device access are central to the service.
Some networks will need a deliberate combination. Operators should start with the service, terminal and payload constraints, then decide where each standard earns its place. Designs can retain room for change through the modem, gateway interfaces, terminal software, and payload scheduling.
