3GPP NTN vs BLE Satellite for IoT

Your next satellite connectivity decision will probably cost you more than your terrestrial one did. The most visible option on the table, 3GPP NTN, drags the entire cost structure of cellular into orbit with it: module costs, carrier fees, SIM provisioning, certification timelines.

And here’s the part that stings: there’s a competing approach, BLE satellite, where the module costs 90% less, the integration is a firmware update, and there’s no carrier in the loop. Most teams evaluating satellite IoT options for 2026 are comparing two fundamentally different architectures without realizing it. They think they’re choosing between vendors. They’re actually choosing between economic models.

How 3GPP NTN Works, and What It Drags Along

3GPP NTN (Non-Terrestrial Networks) extends existing cellular protocols, specifically NB-IoT and LTE-M, to satellites. The standards work landed in 3GPP Release 17, with enhancements coming in Release 18. The basic idea: put a cell tower in orbit, and let NTN-capable devices connect to it.

Devices need a specialized cellular module (think Qualcomm 212S or similar) that can handle the longer link budget, the doppler shift, and the timing offsets inherent in talking to something moving at 7.5 km/s. Skylo, OQ Technology, and Sateliot are all building NTN services within this 3GPP framework, each with different carrier partnership models.

The pitch is appealing. If you’re already running NB-IoT or LTE-M, NTN looks like the natural satellite extension. Same protocol family, same standards body, familiar ecosystem.

But here’s what comes with it. NTN-capable modules run $8 to $15+ per unit and require a SIM or eSIM. They draw cellular-class power during transmission. You need a carrier agreement, which means carrier-dependent pricing, typically $1 to $3+ per device per month. Certification cycles run longer because you’re navigating both carrier approval and regulatory processes.

NTN is cellular with a longer link budget. That’s its strength and its burden.

How BLE Satellite Works: A Different Starting Point

BLE satellite flips the architecture. Instead of making the device speak cellular to a satellite, the satellite carries a BLE-compatible radio. Devices transmit using standard Bluetooth Low Energy chipsets, the same ones already sitting on millions of IoT devices worldwide.

Hubble Network is the clearest example of this approach. Their satellites receive BLE advertising packets directly from devices on the ground. No carrier contract. No SIM. No cellular module required.

The integration story is striking: if your device already has a BLE chip (and most IoT devices do, for commissioning, configuration, or local connectivity), you can add satellite connectivity with a firmware update to your existing BLE hardware, provided that hardware can transmit at +20 dBm. You’re not swapping modules. You’re not redesigning your PCB. You’re not negotiating with a carrier.

The tradeoff is real: BLE satellite is uplink-centric and built for small payloads. You’re not streaming video. You’re sending 20 to 50 byte location pings, sensor readings, status flags. For the vast majority of IoT use cases (asset tracking, agriculture sensors, environmental monitors, utility meters), that’s exactly what gets sent.

BLE satellite was designed ground-up for massive IoT. It didn’t inherit a protocol meant for smartphones and then get adapted.

Direct-to-Device Satellite IoT: Head-to-Head Comparison

Here’s the satellite connectivity comparison on the dimensions that drive your total cost and integration timeline:

The line items look manageable in isolation. A $10 module delta doesn’t sound catastrophic. A $2/month connectivity fee seems small.

They compound.

The Economics at Scale: Where the Gap Becomes a Chasm

Let’s run a concrete scenario. You’re deploying 50,000 asset trackers that report location and status 4 times per day. Battery-powered, expected 3 to 5 year field life.

BOM delta alone:

The module cost difference runs $7 to $13 per device. At 50,000 units, that’s $350,000 to $650,000 in hardware costs before a single packet is transmitted. BLE chipsets from Nordic, TI, or Silicon Labs cost $0.50 to $2. NTN-capable cellular modules from Qualcomm’s ecosystem cost $8 to $15+.

BOM Cost at 50,000 Devices:

  3GPP NTN  ████████████████████████████████████  $400K–$750K
  BLE Sat   █████                                  $25K–$100K

Annual connectivity fees:

At $1 to $3/month per device (typical NTN carrier pricing), you’re looking at $600,000 to $1.8 million per year for the fleet. BLE satellite pricing models are structurally different, built around fleet economics rather than per-SIM carrier billing.

Annual Connectivity (50K devices):

  3GPP NTN  ████████████████████████████████████  $600K–$1.8M/yr
  BLE Sat   ████████████                           $150K–$400K/yr

Over a 5-year device lifecycle, the total cost gap can run into the millions. For a fleet-scale IoT business, those numbers determine whether the product is viable.

“But I’m Already Cellular. Isn’t NTN the Natural Fit?”

This is the most common assumption I see. And it makes intuitive sense: if your terrestrial connectivity is NB-IoT or LTE-M, extending that same protocol family to satellite feels clean. Same tooling, same protocol stack, same mental model.

But your satellite layer doesn’t need to mirror your terrestrial layer. It needs to solve a fundamentally different problem: getting data from places where there are no cell towers. Those environments demand long battery life, low BOM, tiny payloads, and zero local infrastructure. BLE fits those constraints much better than cellular does.

A hybrid approach is often optimal. Cellular where towers exist, BLE satellite where they don’t. Your device probably already has both radios. Most IoT products ship with a cellular module for primary connectivity and a BLE chip for provisioning, configuration, or local communication. Adding satellite via BLE isn’t adding a new radio. It’s activating one you’ve already paid for.

Matching protocols across your terrestrial and satellite links is really just an aesthetic thing. It looks tidy on an architecture diagram, but it’s not an engineering requirement, and it comes with a steep cost premium.

You can register devices on Hubble’s platform and route satellite data into the same backend that handles your cellular telemetry. The data converges in the cloud regardless of which radio carried it.

Where 3GPP NTN Still Earns Its Place

There are scenarios where NTN is the right call.

If you need bidirectional satellite communication, sending commands or configuration updates down to devices, NTN supports that and BLE satellite currently doesn’t. If your payload sizes are large (firmware OTA over satellite, rich telemetry streams), NTN’s higher throughput matters. If you’re in a regulated industry where carrier relationships and 3GPP standards compliance are contractual requirements, NTN checks that box.

And for consumer handset direct-to-device (think the satellite SOS feature on recent iPhones), NTN is the right tool. But that’s a different market than IoT.

These are real use cases. They’re also niche relative to the massive volume of battery-powered sensors, trackers, and monitors that make up the bulk of IoT deployments.

Running Your Own Evaluation

If you’re actively comparing satellite IoT options for 2026, run through these questions:

1. What’s my per-device BOM budget? If it’s tight (under $20 for the whole board), a $12 NTN module is a significant chunk. A $1 BLE chip is rounding error.

2. Do my devices already have BLE? If yes, the integration cost for BLE satellite drops to near zero on the hardware side.

3. What’s my payload size and frequency? Under 50 bytes, a few times per day? That’s BLE satellite’s sweet spot.

4. Do I need bidirectional comms over satellite? If you must push commands to devices via satellite, NTN has the edge. If it’s telemetry-up, BLE wins.

5. What’s my 5-year total cost of connectivity per device? Run the math with carrier fees included. The answer tends to be clarifying.

Do your devices already have BLE?
     |
YES -+- Is your payload small (<50 bytes)?
|         |
|    YES -+- Do you need bidirectional satellite comms?
|    |         |
|    |    NO --+-->  BLE satellite is likely your best fit
|    |    YES -+--> Evaluate hybrid (BLE sat + cellular)
|    |
|    NO ------+--> Consider 3GPP NTN or hybrid
|
NO -----------+--> Evaluate full BOM: adding BLE vs NTN module

If most of your answers point toward small payloads, existing BLE hardware, and cost sensitivity, BLE satellite deserves serious evaluation. The Hubble device SDK is open and available if you want to see what integration actually looks like before committing to anything.

The satellite IoT decision isn’t theoretical anymore. It’s a procurement question with real BOM implications, real connectivity costs, and real architectural consequences that’ll stick with you for the life of your fleet.

Hubble Network enables direct-to-satellite connectivity from standard BLE chips—no additional radio hardware, no carrier negotiations. See how it works →