How 3GPP NB-NTN Frequency Bands n249 n255 n256 Work for Satellite IoT

Three frequency bands, three completely different engineering trade-offs, and not a single one that works everywhere. If you’re designing an NB-NTN system and you picked your band based on a slide deck from a chipset vendor, you probably optimized for the wrong variable.

Here’s the problem: 3GPP Release 17 defined NB-IoT over non-terrestrial networks but spread the RF specifications across three bands in different parts of the spectrum. Band n249 sits in UHF, n255 in L-band, and n256 in S-band. Between them, you’re looking at 14 dB of free-space path loss difference. The regulatory environments don’t overlap cleanly across ITU regions. And the duplex arrangements, channel bandwidths, and Doppler profiles each impose distinct constraints on your UE and payload design.

This article is a practical RF-level comparison of all three NB-NTN frequency bands: their characteristics as defined in 3GPP TS 38.101-5, their propagation behavior at LEO orbital altitudes, and the regulatory reality by region.

Where These Bands Sit in the Spectrum

All three bands are defined as FDD in 3GPP TS 38.101-5, though NB-NTN UEs typically operate in half-duplex FDD mode (HD-FDD) to reduce front-end complexity and power consumption.

A critical note on n249: this band targets an extremely narrow slice of UHF spectrum (150 kHz), and its specification status within 3GPP is less mature than n255 and n256. Some parameters may still be under refinement in RAN4 contributions. Verify against the latest published revision of TS 38.101-5 before committing design decisions to this band.

HD-FDD operation means your UE doesn’t transmit and receive simultaneously, which relaxes duplex filter requirements considerably. That matters most for n256, where simultaneous TX/RX would demand a sharp, expensive duplexer to bridge the 190 MHz duplex gap.

Band n256: S-Band (~2 GHz), the Baseline NTN Band

Frequency range: 1980–2010 MHz uplink, 2170–2200 MHz downlink. 30 MHz of bandwidth in each direction.

The S-band MSS allocation at 2 GHz is the most globally harmonized spectrum for satellite mobile services. ITU has allocated it across all three regions, and it’s the band that most NTN chipset and module vendors have targeted first.

Propagation at S-band: Free-space path loss at 600 km orbital altitude runs around 164 dB (using FSPL = 20log₁₀(d) + 20log₁₀(f) + 32.45, with d in km and f in MHz). Atmospheric attenuation is negligible at 2 GHz for elevation angles above 10°. Rain fade isn’t a meaningful factor at this frequency for NB-IoT’s narrow bandwidth and low data rates.

Doppler: At LEO orbital velocity (~7.5 km/s) and 2 GHz center frequency, maximum Doppler shift runs roughly ±18 kHz. The UE must handle pre-compensation and residual tracking, well within the capabilities specified in the 3GPP NTN timing and frequency adjustment procedures.

Link budget: A typical NB-NTN link budget at S-band with a LEO satellite at 600 km, assuming 23 dBm UE EIRP and a satellite G/T of around -5 to 0 dB/K, closes with reasonable margin for outdoor and light-indoor scenarios. Deep indoor penetration is limited. Building penetration loss at 2 GHz typically runs 15–25 dB depending on construction material, which eats into your margin fast.

Regulatory status: The 2 GHz MSS bands are allocated globally, but coordination with existing S-band MSS operators is mandatory. In the US, FCC Part 25 governs these allocations and existing licensees hold priority. In Europe, CEPT/ECC decisions apply. Coordination is required but follows well-established precedent for MSS operations in this band.

n256 is where you start if you want the broadest geographic applicability and the most mature ecosystem support.

Band n255: L-Band (~1.6 GHz), Better Propagation in a Crowded Neighborhood

Frequency range: 1626.5–1660.5 MHz uplink, 1525.0–1559.0 MHz downlink. 34 MHz of bandwidth each direction, slightly more than S-band.

L-band gives you roughly 2.3 dB of FSPL advantage over S-band at the same orbital altitude (about 162 dB at 600 km). That doesn’t sound like much on paper, but 2 dB of link margin can be the difference between a message getting through a building wall or not. Vegetation and foliage penetration also improve at lower frequencies, which matters for agricultural and forestry IoT deployments.

Doppler: Maximum shift drops to roughly ±14 kHz at 1.6 GHz, slightly easier on the UE’s frequency tracking loop. The difference from S-band isn’t dramatic in practice.

The real challenge with n255 is the neighborhood. L-band MSS is occupied by Inmarsat, Iridium, and Globalstar, all holding long-established allocations and coordination agreements. Getting spectrum access means negotiating with incumbents who have decades of investment in these frequencies.

Then there’s GNSS adjacency. GPS L1 sits at 1575.42 MHz, right between your downlink band (1525–1559 MHz) and the gap before the uplink. The UE front-end filter must reject GNSS signals to avoid desensitization. If there’s a co-located GNSS receiver on the same device, it also needs protection from the NTN downlink. This filter design constraint adds cost and board area.

Regional nuances: L-band MSS is allocated globally by ITU, but operational licensing varies enormously. Some national administrations have essentially fully committed L-band MSS spectrum to existing operators. Others have more flexibility. Your regulatory path depends heavily on specific country-level agreements.

Choose n255 when you need better penetration than S-band and you have (or can negotiate) L-band spectrum access, perhaps through a partnership with an existing MSS operator.

Band n249: UHF/Sub-1 GHz, Maximum Range and Minimum Bandwidth

Frequency range: 399.9–400.05 MHz uplink, 387.0–387.15 MHz downlink. Just 150 kHz in each direction.

150 kHz. That’s enough for exactly one NB-IoT carrier (180 kHz NB-IoT channel bandwidth doesn’t even fit cleanly; the actual usable RF bandwidth is tighter). Capacity is extremely constrained.

But the propagation story is compelling. FSPL at 400 MHz and 600 km altitude is approximately 150 dB, a full 14 dB better than S-band. At UHF, signals diffract around obstacles more readily, penetrate buildings and vegetation with significantly less loss, and the overall link budget math gets much more favorable for low-power devices.

Doppler: Maximum shift at 400 MHz is roughly ±3.5 kHz, dramatically easier to track than S-band’s ±18 kHz. This relaxes requirements on UE oscillator stability and synchronization algorithms.

UE antenna considerations: A quarter-wave antenna at 400 MHz is about 19 cm, compared to ~3.6 cm at 2 GHz. For a small tracker or sensor, that’s a significant form factor constraint. Most UHF IoT devices use electrically short antennas with reduced efficiency, which gives back some of that 14 dB FSPL advantage.

Regulatory fragmentation is severe. The UHF band around 400 MHz is allocated to meteorological aids, space research, Earth exploration satellite services, and mobile satellite services depending on region and specific sub-band. Military use is common in many countries. ITU allocations for MSS in this range are narrow and vary significantly across Regions 1, 2, and 3. Getting a clean, coordinated allocation for commercial satellite IoT in UHF is the hardest regulatory path of the three bands.

The use cases that justify this effort: deep indoor metering, underground asset monitoring, dense urban environments where penetration loss dominates, and remote maritime/agricultural sensors where a few hundred bps is plenty but link margin is everything.

RF Trade-offs Across All Three Bands

The trade-off axes are clear: propagation improves as you go lower in frequency, while bandwidth and regulatory access improve as you go higher. Doppler compensation complexity scales linearly with frequency. Satellite payload antenna gain for a given aperture size is higher at higher frequencies (gain scales with f²), so your satellite’s antenna can be smaller at S-band for equivalent beam coverage.

For engineers working with BLE-based IoT devices that need satellite connectivity as a backhaul, understanding these RF constraints helps frame what’s realistic. Hubble’s device integration guide walks through the practical hardware considerations for getting devices connected.

Regional Regulatory Reality

A critical distinction: ITU allocation isn’t the same as spectrum availability. An allocation in the Radio Regulations means the band can be used for MSS. Actually getting a license to operate requires national-level authorization and coordination with incumbents. For n256, this process is well-trodden. For n249, it barely exists in most jurisdictions.

The spectrum licensing environment for NTN is actively evolving. National regulators are still working through how NTN fits alongside existing satellite and terrestrial services. If you’re making a band decision today, build in margin for regulatory timeline uncertainty, especially for n249 and n255.

Choosing the Right Band for Your Deployment

Start with geography. What’s actually licensed (or licensable) in your target deployment regions? This single question eliminates options faster than any RF analysis.

If you’re targeting global or multi-region coverage, n256 has the clearest regulatory path and the most mature chipset support. It’s the lowest-risk choice.

If you need best possible link budget in specific regions where you can secure UHF spectrum access, n249 delivers unmatched propagation. But plan for very limited capacity and longer regulatory timelines.

If you’re building on existing L-band MSS partnerships or need a middle ground between propagation and capacity, n255 makes sense. Budget extra effort for GNSS coexistence filtering.

Multi-band UE support is technically feasible but adds front-end complexity, cost, and board area. For most IoT devices, you’ll target one band. Work backwards from regulatory access, then use case (indoor vs. outdoor), then capacity requirements, then UE form factor constraints.

To understand how satellite connectivity fits into a broader IoT architecture alongside terrestrial networks, the Hubble network overview provides useful context on how different access technologies compose together.

Band Selection Depends on Regulation First, RF Second

Three bands, three trade-off profiles. n256 gives you the broadest regulatory access and ecosystem maturity. n255 offers better propagation if you can navigate the incumbent environment. n249 provides extraordinary link budget advantages inside a very narrow bandwidth and regulatory window.

Band selection is a system-level choice driven by where you need to operate, what your link budget demands, how much capacity you need, and what your UE can physically accommodate. The NTN spectrum environment is still maturing; the engineers who track regulatory evolution alongside the 3GPP specs will make the best calls.

Hubble Network enables satellite IoT connectivity on standard Bluetooth chips—no specialized NTN modems or spectrum licenses required. See how it works →