Satellite Hub Architecture Explained

The central hub station is the defining element of most commercial VSAT networks. While satellite terminals, transponders, and orbital mechanics receive significant attention, the hub is where traffic aggregation, bandwidth management, and service delivery actually happen. Whether a network serves a handful of enterprise branch offices or thousands of consumer broadband subscribers, the hub's architecture determines what the network can do, how efficiently it uses satellite capacity, and how reliably it delivers services.

Despite its importance, hub architecture is often treated as a black box — operators select a platform vendor, install equipment, and move on. Engineers who understand what happens inside the hub are better positioned to design networks, troubleshoot problems, and make informed decisions about platform selection and capacity planning. If you are new to VSAT fundamentals, start with VSAT Network Architecture for broader context before diving into hub-specific detail.

This article covers what a satellite hub is, what components it contains, how it manages traffic in a hub-and-spoke network, how it compares to gateways and hubless architectures, and what deployment patterns it supports.

What Is a Satellite Hub?

A satellite hub is the central ground station in a star-topology VSAT network. It serves as the single point through which all traffic between remote terminals and external networks — and between remote terminals themselves — must pass. The hub transmits the forward-link carrier that all remote terminals receive, processes the return-link carriers that remote terminals transmit, and manages all bandwidth allocation, routing, and network control functions.

In practical terms, the hub is both a high-performance earth station and a data centre. It houses large antennas (typically 4.5 to 13 metres), high-power amplifiers capable of delivering hundreds of watts of RF output, racks of modem and processing equipment, IP routing and switching infrastructure, and the network management system that controls every remote terminal in the network.

The hub exists because of the fundamental asymmetry in satellite network economics. Building one powerful central station with a large antenna and high-power transmitter is far more cost-effective than equipping every remote site with equivalent capabilities. The hub's large antenna gain and transmit power compensate for the small aperture and limited power of remote terminals, making it possible to use inexpensive 0.75 to 1.8 metre terminals at remote sites while maintaining viable link budgets. This trade-off is the core reason star-topology networks dominate the commercial VSAT market.

For a broader discussion of how star, mesh, and hybrid topologies compare, see Satellite Network Topology.

Core Components of a Satellite Hub

A satellite hub is a complex facility with multiple subsystems working together. Understanding these components clarifies how the hub performs its functions and where potential bottlenecks or failure points exist.

Outdoor Equipment

The outdoor subsystem begins with one or more large parabolic antennas, typically ranging from 4.5 to 13 metres in diameter depending on the satellite band, coverage region, and required link performance. Larger antennas provide higher gain, improving both transmit EIRP and receive G/T.

Mounted on the antenna feed assembly are the transmit and receive chain components. The BUC (Block Up Converter) or HPA (High-Power Amplifier) converts the intermediate-frequency signal from the indoor equipment to the uplink RF frequency and amplifies it for transmission. Hub HPAs are significantly more powerful than remote terminal BUCs — typically 100 to 400 watts for Ku-band and 40 to 200 watts for Ka-band, compared to 2 to 8 watts at a typical remote. The LNB (Low Noise Block downconverter) receives the weak signals from the satellite, amplifies them with minimal noise addition, and down-converts them to intermediate frequency for processing indoors. For a detailed comparison of these RF components, see BUC vs LNB vs LNA.

Some hubs operate with multiple antennas — one per satellite or per frequency band — or use redundant antennas for failover. Antenna tracking systems maintain precise satellite pointing, although most hubs serving GEO satellites use fixed mounts with periodic realignment rather than continuous tracking.

Indoor RF Chain

The indoor RF equipment bridges the outdoor antenna system and the digital processing equipment. Up-converters translate the modulated signal from the modem pool to the intermediate frequency expected by the HPA, while down-converters translate the received intermediate frequency from the LNB to the frequency expected by the demodulators. These converters often include automatic gain control and redundancy switching.

Frequency references and timing systems (typically GPS-disciplined oscillators) provide the precise frequency and timing stability required for DVB-S2X modulation and MF-TDMA burst synchronisation. Even small frequency errors at the hub propagate to every remote terminal, making reference stability critical.

Modem Pool and Platform Components

The modem pool is the computational heart of the hub. It consists of modulator and demodulator cards — often dozens of them in a large hub — that process all forward-link and return-link carriers.

On the forward link (hub to remote), the modem pool generates one or more DVB-S2X carriers. Each carrier is a continuous TDM (Time Division Multiplexed) stream that carries IP packets addressed to specific remote terminals. The modulator applies the appropriate modulation and coding scheme — which may vary per terminal based on link conditions if Adaptive Coding and Modulation (ACM) is enabled — encapsulates the data into DVB-S2X frames, and outputs the modulated signal for up-conversion and transmission.

On the return link (remote to hub), the modem pool demodulates the signals received from remote terminals. In an MF-TDMA return-link scheme, multiple remote terminals share a set of return carriers by transmitting in assigned time slots. The demodulators at the hub must simultaneously process signals from many terminals, each potentially using a different modulation and coding rate, arriving at slightly different times due to varying satellite distances. This multi-carrier, multi-terminal demodulation is one of the most computationally intensive functions in the hub.

Large hub platforms process tens of thousands of remote terminals simultaneously, with modem pool capacity scaled by adding additional cards to the chassis.

Network and Control Functions

The Network Management System (NMS) is the software layer that ties the hub together. It provides the operator interface for configuring and monitoring every aspect of the network: terminal provisioning, bandwidth plan configuration, alarm management, performance monitoring, and reporting.

Bandwidth management functions control how satellite capacity is allocated across the forward and return links. On the forward link, the hub decides which packets to schedule into the DVB-S2X carrier and in what order, implementing traffic prioritisation and QoS policies. On the return link, the hub assigns time slots and frequency channels to remote terminals, controlling how much capacity each terminal can use and when.

IP routing and switching connect the satellite network to external networks — the internet, corporate WANs, VPN concentrators, and other terrestrial infrastructure. The hub typically includes routers, switches, firewalls, and potentially traffic optimisation appliances (TCP acceleration, HTTP pre-fetching, compression).

How a Hub-and-Spoke VSAT Network Works

Understanding the traffic flow through a hub-and-spoke network clarifies why the hub's architecture matters and where performance is determined.

Forward Link: Hub to Remote

When data needs to reach a remote terminal — whether it originates from the internet, a corporate data centre, or another remote terminal — it arrives at the hub through terrestrial connectivity. The hub's IP routing infrastructure directs the packets to the appropriate satellite interface. The bandwidth manager schedules the packets into the DVB-S2X forward-link carrier according to QoS policies: high-priority traffic (voice, signalling) gets scheduled first, while best-effort traffic (web browsing, file downloads) fills remaining capacity.

The modulator encapsulates the scheduled packets into DVB-S2X frames, applies the appropriate modulation and coding for each terminal's link conditions, and outputs the modulated carrier. The up-converter shifts the signal to the transmit frequency, the HPA amplifies it, and the antenna radiates it toward the satellite.

All remote terminals in the network receive the same forward-link carrier (or set of carriers). Each terminal's modem demodulates the entire carrier but only extracts the packets addressed to it. This broadcast nature of the forward link is efficient for distributing common content but means that total forward-link capacity is shared among all terminals.

Return Link: Remote to Hub

When a remote terminal needs to send data — a user uploading a file, a sensor reporting status, a VoIP packet — the terminal's modem requests bandwidth from the hub's bandwidth management system. Depending on the allocation scheme, the terminal may have pre-assigned capacity (CRA — Continuous Rate Assignment), may request additional capacity dynamically (RBDC — Rate-Based Dynamic Capacity or VBDC — Volume-Based Dynamic Capacity), or may use a demand-assigned process (DAMA).

Once the terminal has an assigned time slot and frequency, it transmits a burst containing its data. The signal travels up to the satellite, which retransmits it toward the hub's antenna. The hub's LNB receives the signal, the down-converter shifts it to intermediate frequency, and the appropriate demodulator card in the modem pool extracts the data.

The hub then routes the data to its destination — the internet, a corporate network, or back through the forward link if the destination is another remote terminal. This last case is the double-hop scenario: remote-to-satellite-to-hub, then hub-to-satellite-to-remote, introducing approximately 1,080 ms of total round-trip delay.

For a deeper look at how the ground segment fits together, see Satellite Ground Segment Architecture.

Functions of a Satellite Hub

Beyond the physical components, the hub performs several critical operational functions that determine network performance and service quality.

Inbound and Outbound Carrier Management

The hub manages the configuration and operation of all satellite carriers — both forward and return. This includes setting carrier frequencies, symbol rates, modulation schemes, and coding rates; managing carrier spacing and spectral efficiency; and coordinating frequency plans across multiple transponders when the network spans more than one. The hub also handles carrier monitoring, detecting degradation or interference and alerting operators. For background on symbol rates and spectral shaping, see Symbol Rate and Roll-Off.

Resource Allocation

Satellite bandwidth is expensive, and the hub's resource allocation function determines how efficiently it is used. The hub implements multiple allocation mechanisms simultaneously:

• CRA (Continuous Rate Assignment): guaranteed minimum bandwidth assigned to a terminal regardless of actual demand. Provides predictable performance but wastes capacity when unused.
• RBDC (Rate-Based Dynamic Capacity): terminals request additional capacity based on their current traffic rate. The hub grants requests subject to available capacity and policy limits.
• VBDC (Volume-Based Dynamic Capacity): terminals request capacity to transmit a specific volume of queued data. Suitable for bursty, delay-tolerant traffic.
• Free Capacity Assignment (FCA): the hub distributes any remaining unallocated capacity across terminals, maximising transponder utilisation.

Effective resource allocation balances guaranteed service commitments against statistical multiplexing gains — the hub must honour CRA commitments while dynamically distributing remaining capacity to maximise overall throughput.

QoS and Policy Enforcement

The hub enforces quality-of-service policies that differentiate traffic classes and ensure critical applications receive appropriate treatment. Typical QoS functions include traffic classification (identifying VoIP, video, signalling, and data streams), priority queuing, rate limiting, and traffic shaping.

Because the hub controls both the forward-link scheduler and the return-link bandwidth allocator, it can enforce end-to-end QoS across the satellite segment. A VoIP packet from a remote terminal, for example, receives priority in the return-link bandwidth allocation, priority processing through the hub, and priority scheduling on the forward link if it is destined for another remote. For a comprehensive discussion of satellite QoS techniques, see QoS over Satellite.

Monitoring and Network Control

The NMS continuously monitors every element of the network: hub equipment status, satellite link performance (C/N₀, Es/N₀, BER), remote terminal status, traffic volumes, bandwidth utilisation, and alarm conditions. This monitoring data drives both real-time operational decisions (automatically adjusting modulation when link conditions change) and longer-term planning (identifying terminals that need antenna realignment or sites experiencing chronic rain fade). For more on key link quality metrics, see C/N, C/N₀, and Eb/N₀ Explained.

Hub Architecture in Real Deployments

Hub architecture scales across a wide range of deployment sizes and use cases. The core functions remain the same, but the scale, redundancy, and configuration vary significantly.

Enterprise VSAT

Corporate networks connecting tens to hundreds of branch offices use hub platforms configured for managed services. The hub is typically operated by a service provider, with each enterprise customer allocated a defined amount of forward and return capacity, specific QoS profiles for their application mix, and a logically isolated network environment. Enterprise hubs prioritise reliability, SLA compliance, and application performance over raw throughput.

Shared Broadband Platforms

Consumer and small-business satellite broadband services deploy hubs that serve thousands to tens of thousands of terminals. These platforms maximise statistical multiplexing — oversubscribing satellite capacity based on the assumption that not all subscribers are active simultaneously. The hub's bandwidth management must handle high contention ratios while maintaining acceptable user experience. For more on how contention affects performance, see Satellite Contention Ratio.

Backhaul and Multi-Site Networks

Cellular backhaul, ATM connectivity, and distributed infrastructure networks use hub platforms configured for predictable throughput rather than bursty internet access. These deployments often use CRA-heavy bandwidth plans with dedicated capacity per site, and the hub's QoS engine must guarantee strict latency and jitter bounds for the backhauled traffic. See Satellite Backhaul Explained for deployment considerations.

Small vs Large Hub Environments

Hub architecture spans a wide range of scale. A small hub serving 50 to 200 terminals might occupy a single equipment rack with one modem chassis, one antenna, and basic redundancy. A large hub serving 10,000 or more terminals may require multiple equipment racks, multiple antennas covering different satellites or beams, fully redundant RF chains with automatic switchover, and a dedicated operations team.

The largest hub facilities — sometimes called teleport-class hubs — combine hub functions with gateway services, co-location, and interconnection to multiple terrestrial networks. These facilities blur the line between hub and teleport, which is why understanding the distinction matters.

Hub vs Gateway vs Teleport

The terms hub, gateway, and teleport are sometimes used interchangeably, but they refer to different things. Understanding the distinctions prevents confusion in network design and procurement.

A hub is the central station of a specific VSAT network. It runs the VSAT platform software, manages bandwidth for that network's remote terminals, and provides the forward-link and return-link processing for a defined set of satellite carriers. The hub is application-specific — it exists to serve a particular VSAT network.

A gateway is a broader term for any earth station that provides connectivity between a satellite system and terrestrial networks. HTS (High Throughput Satellite) systems use gateway earth stations to connect their spot beams to the internet and other terrestrial infrastructure. A gateway does not necessarily run a VSAT platform or manage remote terminals — it provides the ground-side anchor for satellite capacity.

A teleport is a facility that houses earth station infrastructure — antennas, RF equipment, connectivity — and provides services to multiple customers and multiple satellite systems. A teleport may contain one or more hubs, one or more gateways, and a range of other satellite communication equipment. It is a shared infrastructure facility rather than a specific network function.

In practice, these concepts overlap. A hub can be located inside a teleport. A gateway can also function as a hub if it runs VSAT platform software. A teleport can host both hubs and gateways for different customers. The key is understanding the functional role each term describes rather than treating them as mutually exclusive categories. For more detail on gateways and teleports, see Satellite Gateways, Teleports, and Points of Presence.

Advantages and Trade-offs

Centralized Control and Operational Simplicity

The hub's greatest advantage is centralization. All network intelligence — bandwidth management, QoS enforcement, security policies, monitoring, and control — resides in one location, operated by a skilled team. This makes it straightforward to implement consistent policies across the entire network, deploy software updates, diagnose problems, and plan capacity changes. Remote terminals can be simple and inexpensive because the hub handles the complexity.

Scale and Shared Efficiency

Hub architecture enables efficient sharing of expensive satellite capacity. Statistical multiplexing allows a hub to serve many more terminals than the raw bandwidth could support if capacity were dedicated. The hub's bandwidth management dynamically allocates capacity to terminals that need it, reclaiming it from those that do not. This shared efficiency drives down the cost per terminal and makes satellite broadband economically viable for consumer and SMB markets.

Single-Point Dependency and Resilience Considerations

The hub is a single point of failure. If the hub goes down, every remote terminal in the network loses connectivity. This risk is mitigated through redundancy — dual power feeds, redundant RF chains, hot-standby modem chassis, and sometimes geographically diverse backup hubs — but the fundamental dependency remains. Hub-based networks require careful redundancy planning and maintenance procedures to achieve the availability targets that enterprise and government customers demand.

The hub also creates a geographic dependency. All traffic routes through the hub's physical location, which means the hub must have reliable power, physical security, and sufficient terrestrial connectivity to handle the aggregate traffic of the entire network.

Hub-Based vs Hubless / Mesh Networks

Not all VSAT networks require a hub. Hubless (mesh) architectures allow remote terminals to communicate directly through the satellite without routing traffic through a central hub station. The choice between hub-based and hubless depends on the network's primary traffic pattern and operational requirements.

Hub-based networks are preferred when the primary traffic flow is between remote terminals and a central resource — the internet, a data centre, or a headquarters location. This is the dominant pattern for enterprise branch connectivity, consumer broadband, and most managed VSAT services. Hub-based networks are also preferred when minimising per-terminal cost is important, when centralised operational control is valued, and when the network must scale to thousands of terminals.

Hubless networks are preferred when the primary traffic flow is between remote terminals themselves. Site-to-site industrial communications, tactical military networks, and emergency response deployments benefit from eliminating the double-hop delay (approximately 1,080 ms round-trip reduced to approximately 540 ms) and removing the hub as a single point of failure. However, hubless terminals are more expensive, network management is more complex, and internet access requires a separate gateway arrangement.

Many modern VSAT platforms support hybrid configurations that combine a hub-based star topology for internet and centralised traffic with a mesh overlay for direct terminal-to-terminal communication. This provides single-hop latency for site-to-site traffic while maintaining hub-based internet access and centralised management. For a full treatment of hubless architectures, see Hubless VSAT Networks Explained.

Common Misunderstandings

Assuming every gateway is a hub. A gateway earth station provides connectivity between a satellite and terrestrial networks, but it does not necessarily run a VSAT platform or manage remote terminals. HTS gateways, for example, terminate satellite beams and route traffic to the internet but may not perform the bandwidth management, terminal provisioning, or QoS enforcement functions that define a hub. Treating all earth stations as hubs leads to confusion in network design and vendor discussions.

Assuming hubless is always more efficient. Hubless architecture eliminates the double hop for terminal-to-terminal traffic, but this advantage only matters when terminal-to-terminal traffic is the dominant pattern. For the vast majority of commercial VSAT deployments where terminals primarily access internet or centralised resources, hub-based architecture is more efficient because it enables cheaper terminals, better statistical multiplexing, and simpler operations. Hubless is a specialised architecture for specific use cases, not a general-purpose improvement.

Ignoring operational and management benefits of hub-based systems. The engineering discussion around hub vs hubless often focuses on latency and single-point-of-failure concerns while overlooking the operational advantages of centralised management. A hub provides a single point of visibility into the entire network, a single place to implement policy changes, and a single team responsible for network operations. These operational benefits translate directly into lower operating costs and faster problem resolution, which are often more important in practice than the latency difference.

Frequently Asked Questions

What is a satellite hub?

A satellite hub is the central ground station in a star-topology VSAT network. It transmits the forward-link carrier to all remote terminals, receives and demodulates the return-link carriers from remote terminals, manages bandwidth allocation, enforces QoS policies, and provides the connection between the satellite network and terrestrial infrastructure such as the internet or corporate WANs.

How is a hub different from a gateway?

A hub runs a VSAT platform that actively manages a network of remote terminals — handling bandwidth allocation, terminal provisioning, QoS enforcement, and network monitoring. A gateway is a broader term for any earth station that connects a satellite system to terrestrial networks. A gateway may simply terminate satellite capacity and route traffic without the terminal management functions that define a hub. All hubs are gateways, but not all gateways are hubs.

Why do VSAT networks use hub-and-spoke?

Hub-and-spoke architecture concentrates expensive equipment — large antennas, high-power amplifiers, sophisticated processing — at a single central location. This allows remote terminals to use small, inexpensive hardware while still achieving viable link budgets. Centralisation also simplifies network management, enables efficient bandwidth sharing through statistical multiplexing, and provides a natural enforcement point for QoS and security policies.

Can a satellite network operate without a hub?

Yes. Hubless (mesh) VSAT networks allow terminals to communicate directly through the satellite without a central hub. Each terminal must be powerful enough to close the link with other terminals of similar size, making terminals more expensive and complex. Hubless networks are used when site-to-site communication is the primary requirement and double-hop latency is unacceptable. Internet access in a hubless network requires a separate gateway arrangement.

What equipment is inside a satellite hub?

A satellite hub contains outdoor equipment (large antenna, HPA or BUC, LNB, feed assembly), indoor RF equipment (up-converters, down-converters, frequency references), a modem pool (modulator and demodulator cards for forward and return link processing), IP routing and switching infrastructure, and a Network Management System (NMS). Large hubs also include redundant power systems, environmental controls, and monitoring equipment.

How does a hub handle QoS?

The hub enforces QoS by controlling both the forward-link scheduler and the return-link bandwidth allocator. Traffic is classified into priority levels (voice, video, signalling, data), and the scheduler ensures high-priority traffic is transmitted first. On the return link, the hub can grant priority bandwidth requests from terminals carrying time-sensitive traffic. This centralised control enables consistent end-to-end QoS across the satellite segment.

What is the difference between a hub and a teleport?

A hub is a functional role — the central station of a specific VSAT network that runs platform software and manages remote terminals. A teleport is a physical facility that houses satellite communication infrastructure and provides services to multiple customers. A teleport may contain one or more hubs, along with gateways, co-location space, and terrestrial connectivity. A hub can exist inside a teleport, but a teleport is not itself a hub.

How many remote terminals can a single hub support?

This depends on the hub platform, satellite capacity, and service profile. Small hub deployments serve 50 to 200 terminals. Mid-range platforms handle 500 to 5,000 terminals. Large-scale broadband platforms can support 10,000 to 100,000 or more terminals from a single hub facility, using multiple modem chassis and satellite carriers. The practical limit is usually determined by available satellite bandwidth and the contention ratio rather than by the hub hardware itself.

Key Takeaways

• The hub is the central brain of star-topology VSAT networks — it handles all traffic routing, bandwidth management, QoS enforcement, and network control for every remote terminal in the network.
• Hub architecture trades centralisation for efficiency — concentrating expensive equipment at one location enables inexpensive remote terminals and efficient bandwidth sharing through statistical multiplexing.
• Core hub components span outdoor RF, indoor processing, modem pool, and network management — each subsystem must be properly engineered and maintained for the network to perform reliably.
• Hub-based networks dominate commercial VSAT — the economics of centralised infrastructure, simple remotes, and integrated internet access make hub-and-spoke the right architecture for the majority of satellite communication deployments.
• Hubs, gateways, and teleports serve different functions — understanding these distinctions prevents confusion in network design, vendor evaluation, and procurement.
• Hub dependency is the primary trade-off — single-point-of-failure risk and double-hop latency for terminal-to-terminal traffic are inherent limitations that must be addressed through redundancy planning or hybrid architectures.

Related Articles

• Satellite Network Topology — comparison of star, mesh, and hybrid topologies in satellite communications
• VSAT Network Architecture — end-to-end overview of how VSAT networks are designed and operated
• Satellite Gateways, Teleports, and Points of Presence — detailed guide to satellite ground infrastructure beyond the hub
• Hubless VSAT Networks Explained — engineering guide to mesh satellite architectures without central hubs
• Satellite Backhaul Explained — how satellite connects cellular towers and remote infrastructure to core networks
• Satellite Ground Segment Architecture — comprehensive look at the ground-side components of satellite communication systems