A diagram illustrating the hybrid architecture of ground-based sensors communicating with a LoRaWAN gateway, which then uses a satellite link for internet backhaul.

LoRaWAN Gateway via Satellite: Future of Remote IoT

Written by: Robert Liao

|

Published on

|

Time to read 5 min

Author: Robert Liao, Technical Support Engineer

Robert Liao is an IoT Technical Support Engineer at Robustel with hands-on experience in industrial networking and edge connectivity. Certified as a Networking Engineer, he specializes in helping customers deploy, configure, and troubleshoot IIoT solutions in real-world environments. In addition to delivering expert training and support, Robert provides tailored solutions based on customer needs—ensuring reliable, scalable, and efficient system performance across a wide range of industrial applications.

Summary

Cellular networks cover less than 15% of the Earth's surface. For the ocean, the desert, or the polar caps, 4G is useless. This guide explores the frontier of "LoRaWAN over Satellite." We distinguish between "Direct-to-Satellite" (sensors talking to space) and "Satellite Backhaul" (sensors talking to a LoRaWAN gateway, which talks to space). We argue that for industrial applications, the Gateway approach is superior. It allows for real-time local control, significantly lower satellite data costs, and higher sensor density. We also discuss how to connect a standard LoRaWAN gateway to LEO services like Starlink for high-speed remote backhaul.

Key Takeaways

The 85% Gap: Most of the planet has no cellular signal. Satellite is the only option for maritime and deep remote logistics.

Backhaul vs. Direct: Direct-to-satellite sensors use high power. Using a LoRaWAN gateway to aggregate local data and send a compressed batch via satellite is far more energy-efficient.

Cost Control: Satellite data is expensive. An industrial LoRaWAN gateway with Edge Computing can filter noise locally, sending only critical alerts to space to save money.

LEO Revolution: New Low Earth Orbit (LEO) satellites (Starlink, Swarm) reduce latency, making satellite backhaul for gateways affordable and fast.

LoRaWAN Gateway via Satellite: Future of Remote IoT

What do you do when you need to monitor a buoy in the middle of the Pacific Ocean? Or a pipeline in the Sahara Desert?

You cannot run a cable. You cannot find a 4G signal.

For a long time, the answer was "you don't." But the New Space Race has changed the equation. Satellite connectivity is becoming cheaper and faster.

While there is hype around sensors talking directly to satellites, the most robust industrial solution remains the LoRaWAN gateway.

By using a gateway as the local "Hub" and a satellite link as the "Pipe," you can deploy a network literally anywhere on Earth. This guide explains the architecture of Satellite IoT.


A diagram illustrating the hybrid architecture of ground-based sensors communicating with a LoRaWAN gateway, which then uses a satellite link for internet backhaul.


The Architecture: Satellite Backhaul

In this model, the LoRaWAN gateway functions exactly as it does in a city. It listens to sensors on the ground (or ship).

The difference is the Backhaul. Instead of plugging into a 4G modem or fiber switch, the LoRaWAN gateway Ethernet port connects to a Satellite Terminal (like a Starlink Dish, Iridium Edge, or BGAN).

  1. Sensors: Talk to the gateway via LoRa (Free, Low Power).
  2. LoRaWAN gateway: Aggregates and filters the data.
  3. Sat Terminal: Sends the filtered data to the Cloud via Space.

Why this beats Direct-to-Satellite: Direct sensors need a clear view of the sky and high transmit power. A sensor buried inside a ship's hold cannot see the sky. But it can reach a LoRaWAN gateway mounted on the bridge. The gateway handles the heavy lifting of the satellite link.

LEO vs. GEO: Choosing Your Satellite

Not all satellites are equal.

  • GEO (Geostationary): High orbit (35,000km). High latency (600ms+). Good for small, bursty data.
  • LEO (Low Earth Orbit): Low orbit (500km). Low latency (30ms). Examples: Starlink, OneWeb. For a LoRaWAN gateway managing real-time industrial data, LEO is the game-changer. It offers "fiber-like" speeds, allowing you to not just send sensor data, but remote desktop into the gateway for maintenance.

The Critical Role of Edge Computing

Satellite data is expensive. You pay per Megabyte. You cannot afford to send every "Keep Alive" heartbeat from 1,000 sensors over satellite.

This is where the intelligence of the LoRaWAN gateway saves your budget.

  • Edge Filtering: Using an Embedded LNS or Node-RED on the gateway, you configure logic: "Only send data if Temperature > 50°C."
  • Compression: The LoRaWAN gateway can batch 100 readings into a single compressed file before uploading.
  • Result: You reduce satellite data usage by 90%, making the business model viable.

A conceptual graphic showing how a LoRaWAN gateway filters and compresses data to reduce expensive satellite bandwidth usage.


Use Case: Maritime Logistics

Container ships are floating cities.

  • The Challenge: Monitoring the temperature of "Reefer" containers deep in the stack while crossing the ocean.
  • The Setup: A network of LoRaWAN gateways is installed on the ship (Bow, Stern, Bridge).
  • The Data: Sensors inside the containers report to the nearest gateway.
  • The Link: The master LoRaWAN gateway connects to the ship's VSAT or Starlink connection to report data to the shipping company HQ.
  • The Result: Zero spoilage, total visibility, even in the middle of a storm.

Hardware Compatibility

The good news is that you don't need a "Space Gateway." Any standard industrial LoRaWAN gateway with an Ethernet WAN port (like the Robustel R3000 LG) is compatible with satellite terminals.

  • Starlink: Plug the Starlink Ethernet adapter into the LoRaWAN gateway WAN port.
  • BGAN/Iridium: Connect via Ethernet or RS232 (for low-bandwidth serial modems). The gateway simply sees it as an internet connection. It doesn't care if the IP address comes from Verizon or SpaceX.

A visual showing the simple ethernet connection between an industrial LoRaWAN gateway and a Starlink satellite terminal for remote connectivity.


Conclusion: No More Dead Zones

The combination of LoRaWAN (for local density) and Satellite (for global reach) is the final piece of the IoT puzzle.

It eliminates the concept of "Remote." With a rugged LoRaWAN gateway and a view of the sky, any asset on the planet can be brought online. Whether you are tracking polar bears in the Arctic or pumps in the Amazon, the sky is no longer the limit—it is the link.

Frequently Asked Questions: About LoRaWAN gateway

Q1: What is LR-FHSS?

A1: Long Range Frequency Hopping Spread Spectrum (LR-FHSS) is a new modulation designed for sensors to talk directly to satellites, bypassing the gateway. While promising, it has very low capacity and high latency. For industrial sites with hundreds of sensors, a local LoRaWAN gateway using satellite backhaul is still superior for cost and reliability.

Q2: How much power does a satellite setup use?

A2: A lot. A Starlink terminal consumes 50-100 Watts. A LoRaWAN gateway consumes 5 Watts. If you are off-grid, you need a substantial solar array and battery bank to power the satellite terminal. The gateway itself is the minor load in this equation.

Q3: Can I update firmware over satellite?

A3: Technically yes, but be careful. Firmware files are large (10MB+). On a pay-per-MB satellite plan (like BGAN), this could cost $50. On a flat-rate LEO plan (like Starlink), it is free. Always check your data plan before pushing updates to a satellite-connected LoRaWAN gateway.