On September 4, 2025, we co-hosted a webinar on NTN NB-IoT Uncovered: What It Is, What It Isn’t, and Where It Wins with Viasat. This is emerging technology with a great deal of promise, and we had a large audience, with an accordingly large number of questions! We’ve collated these questions into several topics in this blog post, which we will keep updated as the roadmap progresses.

Quick Links:

Pricing and Licensing

What is the expected cost of hardware (e.g., modem, antenna)?

Hardware pricing varies widely depending on the capabilities your project requires. Some modules are designed purely as basic modems to connect to NTN NB-IoT networks and are relatively inexpensive, but they only provide connectivity.

Products like RockBLOCK RTU are far more than just a connection point. In addition to NTN NB-IoT access, they include:

  • Edge processing to handle data locally and reduce transmission frequency (saving airtime and battery life).
  • Configurable sensor reading and alerting, so you can trigger transmissions only when thresholds are met.
  • A plug-and-play design, enabling faster deployment and simpler integration with cloud platforms like Cloudloop.

Because of this added functionality, RockBLOCK RTU and similar devices sit at a different price point than a simple dongle, but they often reduce overall project costs by lowering airtime usage, extending battery life, and minimizing field maintenance.

In short, the “right” hardware investment depends on whether you need just connectivity or a complete field-ready solution that simplifies operations and scales with your project.

What will ongoing connectivity cost, for example at 50 KB per month or one transmission per hour?

Viasat has not yet published official NTN NB-IoT pricing, but early indications suggest it will be competitive for the specific niche of very small, infrequent data transmissions. Final rates are expected to be announced in Q1 2026.

Because of the complexity and scale of satellite infrastructure, NTN NB-IoT data will not follow the same pricing model as terrestrial NB-IoT. In practical terms, this means far less data for a higher cost, making it best suited to scenarios where devices send tiny payloads, such as tens of bytes per hour, rather than continuous data streams.

When compared to proprietary satellite services, NTN NB-IoT can be more cost effective for ultra-low data volumes (typically below 30-50 KB per month per device). This makes it a strong choice for applications like remote sensors, infrequent tracking, and metering.

Around 50 KB per month, message-based services like Iridium Messaging Transport (IMT) and NTN NB-IoT become roughly equivalent in cost.

Above 50 KB per month, proprietary services like IMT quickly become far more economical, especially for higher data throughput or near-real time applications.

In summary, NTN NB-IoT fills a valuable gap for low data, low power use cases, but it is not simply a continuation of cellular NB-IoT pricing in space. For higher data needs, traditional satellite services remain the better fit.

How does NTN NB-IoT communication cost compare to terrestrial NB-IoT and proprietary satellite solutions?

Satellite NB-IoT is designed for very small, infrequent data transmissions, such as a few tens of bytes per hour or day. Because of the complexity of delivering data over satellites, the cost per kilobyte is much higher than for terrestrial NB-IoT, which benefits from existing cellular infrastructure and is inexpensive for high volume, high frequency data.

For ultra-low data applications, Satellite NB-IoT promises to be more affordable than traditional proprietary satellite services, which are built for higher throughput, always-on connections. However, as data usage rises beyond roughly a few dozen kilobytes per month per device, the cost of satellite NB-IoT can quickly become more expensive, making other satellite solutions like Iridium Messaging Transport, or Viasat IoT Nano, more economical.

In short:

  • Terrestrial NB-IoT is the lowest cost option, but only works where there is cellular coverage.
  • Satellite NB-IoT fills the gap where coverage is missing, offering lower costs than legacy satellite services for small, infrequent messages.
  • Proprietary satellite solutions remain the best fit for higher data volumes, real time control, or truly global coverage.

Does the device include a subscription, and are any licenses required to use the service?

NTN NB-IoT works much like cellular IoT. Devices use a SIM card to authenticate on the network, and subscriptions are managed separately. These can be as short as one active month or discounted for 12 months or longer, depending on your needs.

No additional licenses are required as long as you are using a certified device. If you’re building your own hardware, it must first go through Viasat’s certification process before it can connect to the network.

Power Consumption

What are the expected power requirements for receiving and sending messages?

Final power profiles are still being confirmed, but early testing of devices shows very low power consumption, similar to cellular NB-IoT at the edge of coverage. Typical behavior is short, high-power bursts during transmission, with the device in deep sleep the rest of the time.

  • Transmit (TX): Brief bursts at a few hundred milliamps for fractions of a second per message.
  • Receive (RX): Much lower current for very short listening periods.
  • Deep Sleep: Extremely low standby current between events.

For ultra-low data use cases – such as one small (50-byte) message per day – battery life can be measured in years. Even at one message per hour, multi-year operation is still realistic with careful design, especially when payloads remain small, retries are minimized, and devices have a clear view of the sky.

Tip: Use short, infrequent messages and Non-IP Data Delivery (NIDD) where possible to maximize battery life.

Will latency in satellite NB-IoT significantly impact battery performance?

Not directly. Latency in satellite NB-IoT (typically tens of seconds) affects how long a device stays “awake” waiting for confirmation or downlink data, but it doesn’t require the radio to transmit continuously. Most of the time, the device is idle and consuming minimal power.

Where battery performance can be affected is in retry scenarios. If poor antenna placement or obstructions cause repeated failed attempts, the radio will need to re-send messages, increasing total energy used. This is why clear line of sight and well planned message scheduling are key.

For applications sending small, infrequent messages, latency has little impact on battery life, and multi-year operation remains realistic, even when end-to-end message delivery takes longer.

Data & Protocols

What counts as “small data volumes,” and how is data usage calculated (uplink vs downlink)?

For NTN NB-IoT, small data volumes generally mean 30-50 KB per month per device. This roughly equates to one small message (around 50 bytes) every hour, making it ideal for applications like periodic sensor readings or exception-based reporting.

Data usage is calculated as the total of both uplink and downlink traffic, combined.

  • Uplink: Data sent from the device, such as sensor readings or alerts.
  • Downlink: Data sent to the device, such as configuration updates or acknowledgements.

In most deployments, uplink traffic dominates, with only small amounts of downlink data needed. However, frequent acknowledgements or commands sent to the device will eat into the monthly budget, so it’s best to minimize downlink usage wherever possible.

Rule of thumb: If your device sends a 50-byte message hourly, you’ll be close to the 30-50 KB/month sweet spot, but adding regular downlink messages or retries can quickly push usage higher.

Is TCP/IP supported, or is NB-IoT limited to other protocols like UDP or NIDD?

TCP/IP is not supported for NTN NB-IoT. By avoiding the heavy overhead of TCP/IP, devices can send and receive data far more efficiently, using fewer bytes per message and significantly reducing power consumption.

Instead, NTN NB-IoT uses lightweight protocols such as UDP and NIDD (Non-IP Data Delivery), which are purpose-built for small, infrequent IoT messages. This means:

  • Lower airtime costs: No wasted data on headers or session management.
  • Lower power draw: The radio stays on for less time per message.
  • Simpler design: Devices can focus on sending just the essential payload.

Result: Your data goes further, your batteries last longer, and you stay well within the ideal 30-50 KB/month sweet spot for NTN NB-IoT.

Are message acknowledgements supported, and do they consume billable data?

In principle, acknowledgements are supported, but whether they’re available depends on the hardware and how it’s configured. Some devices, such as RockBLOCK RTU, can be programmed to generate acknowledgements, while others may not include this functionality out of the box.

Because an acknowledgement is just another downlink message, it does consume data and counts toward the device’s total monthly allowance (both uplink and downlink combined).

Frequent use of acknowledgements can quickly increase data consumption, so it’s best to:

  • Use them sparingly, such as for critical alerts where confirmation is essential.
  • Keep acknowledgement messages very small to stay within the <30 KB/month sweet spot.
  • Design systems so that most reporting is uplink-only, with acknowledgements reserved for exceptions or configuration updates.

Tip: If battery life and cost are key priorities, minimize acknowledgements and focus on efficient, uplink-driven workflows.

Coverage & Availability

What countries and regions are currently covered, and what are the rollout plans?

Currently, NTN NB-IoT service is available in the United States, Canada, New Zealand, Australia and Europe (partially). It is globally capable, but not yet globally available; effectively, there have to be enough end points / applications in a particular region for the service to be unlocked. We anticipate that coverage will expand rapidly over the next 1-3 years.

Will the service work at sea or in harsh environmental conditions (e.g., offshore, deserts, extreme temperatures)?

The service is certainly capable of this, but today it isn’t available for maritime applications (see above). Instead, explore message-based solutions like Viasat IoT Nano or Iridium Messaging Transport (IMT) for an economical alternative that has truly global coverage.

Technical

What are the main technical differences between NTN NB-IoT and cellular NB-IoT?

These are summarised in the below table, and discussed at length in the webinar (watch the recording on Youtube).

NTN NB-IoT*

Cellular NB-IoT

Proprietary Satellite IoT**

Max. Practical Payload

1,200 bytes

1,400 - 1,600 bytes

16,000 bytes

Min. Practical Payload

10-30 bytes

30-50 bytes

10 bytes

Latency

Medium (10 - 60s); MVNO scheduling could increase this to 2 - 5 mins)

Low (1 - 10s)

Medium (c. 15-60s)

Directionality

Bidirectional

Bidirectional

Bidirectional

Coverage

United States, Canada, Brazil, Australia, New Zealand and select European markets

Where supported by regional MNOs, and there is terrestrial infrastructure

Global, exc. Polar regions

Cost-Optimized Monthly Data Volume

< 50 KB

< 5 MB

< 1 MB

*Based on Viasat NB-NTN | **Based on Viasat IoT Nano

How does NTN NB-IoT compare to proprietary satellite services like Iridium SBD?

NTN NB-IoT is designed for very small, infrequent data transmissions, such as tens of bytes per hour, making it a cost effective choice for applications like remote monitoring, tracking, and metering where usage stays below roughly 30-50 KB per month. It currently offers regional coverage rather than true global reach and has moderate latency, typically tens of seconds, which is acceptable for periodic updates but not for time-critical control.

Message-based proprietary services such as Iridium SBD share some similarities with NTN NB-IoT, as they also focus on small, discrete payloads and are well-suited for remote reporting. However, SBD offers truly global coverage, including oceans and polar regions, and has both lower latency and higher throughput, making it more robust for mobile or mission-critical assets.

In contrast, IP-based satellite services like Viasat IoT Pro or Iridium Certus 100 provide a continuous, always-on connection. This enables real time command and control, streaming data, and more complex integrations, something neither NTN NB-IoT nor SBD can deliver. These services are typically more expensive and consume more power, but they are essential for applications such as autonomous systems, live video feeds, or continuous telemetry.

In summary:

  • NTN NB-IoT is ideal for ultra-low power, ultra-low data needs.
  • Message-based services like SBD are better for mobile or global small data applications.
  • IP-based services are the only option for real-time control and high throughput use cases.

What frequencies are used, and how do they integrate with mobile networks?

Viasat’s NTN NB-IoT service (and indeed all of its satellite IoT services) operates in the L-band (around 1–2 GHz), a frequency range well suited for satellite IoT because it enables reliable coverage, compact, low power antennas, and resilience to weather related interference.

Because Viasat’s service follows the 3GPP NB-IoT standard, a single SIM and chipset can, in theory, support both terrestrial (TN) and satellite (NTN) networks, allowing devices to roam or fail over between them when agreements are in place.

Although TN and NTN NB-IoT share the same core standard, they operate under very different data and power constraints. TN NB-IoT supports larger, more frequent data transfers, often over IP-based protocols. NTN NB-IoT is optimized for tiny, infrequent messages and while it can utilize UDP/IP, Non-IP Data Delivery (NIDD) is desirable to keep airtime and costs low.

As a result, systems designed for terrestrial NB-IoT often need re-architecting to perform well over satellite. Key factors such as payload size, message frequency, and downlink strategy should be carefully planned to avoid unexpected performance or cost challenges.

How does network selection work when both terrestrial and satellite networks are available?

Most devices come with lowest-cost routing built in, so will use terrestrial when available, switching to satellite when cellular drops out, and allow control over when the device will attempt a satellite connection once cellular is not available.

Is NIDD part of the 3GPP standard and supported by the network?

Yes. Non-IP Data Delivery (NIDD) is fully part of the 3GPP NB-IoT standard and is supported by Viasat’s NTN NB-IoT network. We are strong advocates of NIDD because it’s the key to unlocking the true economics and efficiency of satellite IoT.

Unlike traditional IP-based messaging, which adds significant overhead to every transmission, NIDD allows devices to send only the essential data payload, with no IP headers or session management. This brings three major benefits:

  • Lower airtime costs – every byte transmitted is meaningful data.
  • Lower power consumption – shorter transmissions mean devices stay in deep sleep longer, extending battery life.
  • Simpler, leaner design – ideal for very small, infrequent messages typical of NTN NB-IoT use cases.

For ultra-low data applications like environmental sensors, asset tracking, or metering, NIDD is the preferred approach. While IP-based transport is still supported in the NB-IoT standard, it can quickly drive up airtime costs and power usage, especially over satellite links.

We’ve written a detailed explainer on why NIDD is so important for NTN NB-IoT; you can read it here: Unlocking NTN NB-IoT with NIDD.

Can we manage NTN NB-IoT devices and integrate using existing patterns in Cloudloop?

Yes. NTN NB-IoT devices can be fully managed and monitored within Cloudloop, alongside other satellite IoT devices, giving you a single, unified view of your entire deployment.

Through Cloudloop Data, information from NTN NB-IoT devices is automatically reformatted and standardized, so it can be delivered to a wide range of destinations, including cloud platforms, analytics tools, and third-party systems. This means you can continue using your existing integration patterns and workflows, with no need to rebuild or redesign your backend systems to handle NTN NB-IoT traffic.

Examples of integration destinations include:

  • AWS IoT Core
  • Azure IoT Hub
  • Google Cloud IoT
  • REST APIs and custom endpoints
  • Webhooks for custom workflows.

Because Cloudloop is network- and protocol-agnostic, it works seamlessly with both standards-based NB-IoT devices and proprietary satellite solutions, making it ideal for organizations running mixed technologies.

Use Cases & Comparisons

What applications are best suited to NTN NB-IoT?

NTN NB-IoT, whether delivered via UDP/IP or NIDD, is ideal for low data, low power applications where devices send small, infrequent messages and where a short delay (latency) is acceptable. Because the technology is optimized for tiny payloads and long battery life, it excels in deployments where maintaining coverage in remote or hard to reach locations is the priority.

The three strongest application areas are:

  • Monitoring – environmental sensors, infrastructure health checks, soil moisture, or weather stations.
  • Tracking – livestock, wildlife, or remote assets where location updates are needed periodically, not in real time.
  • Metering – water, gas, or energy usage reporting where daily or hourly readings are sufficient.

The service is designed to support large numbers of endpoints, each sending very small amounts of data. The sweet spot is around 30-50 KB per device per month, which equates to roughly one transmission per hour. This works well for applications like periodic sensor readings or basic status updates, but it’s not ideal for frequent updates, such as continuous tracking where you want to see location changes every few minutes.

How suitable is NTN NB-IoT for UAVs, HAPs, or other mobile applications?

NTN NB-IoT is not well suited for UAVs (Uncrewed Aerial Vehicles), HAPs (High-Altitude Platforms), or similar mobile applications. These platforms typically require an always-on, real time connection for tasks such as command and control, continuous telemetry, or video streaming.

NTN NB-IoT, by design, is optimized for tiny, infrequent data messages with latency measured in tens of seconds. This makes it perfect for periodic reporting, such as a water level sensor or asset tracker, but completely unsuited for dynamic, fast moving systems where constant situational awareness is required.

For UAVs, HAPs, and other highly mobile assets, you’ll need an IP-based satellite connection, which provides a continuous, reliable data link. Good options include:

  • Iridium Certus 100 – a truly global service for mobile platforms, ideal for command and control and small data streams.
  • Viasat IoT Pro – an IP-based L-band solution offering higher throughput for more complex or data-intensive applications.
  • Hardware like the RockREMOTE Mini OEM, designed specifically for integrating into UAVs or other custom mobile systems.

How does NTN NB-IoT compare to Starlink Direct to Cell?

Starlink Direct to Cell will use LTE Cat 1 and Cat 1 bis, making it well suited for higher throughput, mobile applications, particularly where devices have access to a reliable power source, such as vehicles or drones. This makes it an attractive option for use cases that require more frequent or larger data transfers than NTN NB-IoT can support.

However, Starlink D2C will not immediately offer global coverage. It relies on access to spectrum licences (often held by terrestrial Mobile Network Operators or by spectrum holders like EchoStar) to provide direct-to-cell service. For example, in a $17 billion deal announced in September 2025, SpaceX acquired EchoStar’s AWS-4 (2 GHz) and H-block spectrum in the United States, resolving part of the regulator’s concerns there. That said, such licences are country-specific, and spare spectrum is often limited, heavily regulated, or already allocated in densely populated countries, meaning availability will remain patchy and regionally concentrated.

Effectively the same considerations raised for whether NTN NB-IoT would work for your application should be raised for whether Starlink D2C (or equivalent services from AST SpaceMobile / Lynk) would work: how much data do you need; how often, and how urgently; what’s the power budget, and what’s the deployment region?

Companies like Ground Control can help you navigate these choices to identify the best network and protocol for your specific needs.

Could NTN NB-IoT replace or compete with services like Iridium or Starlink in the future?

In the foreseeable future, the answer is no. NTN NB-IoT and proprietary satellite systems are designed to solve different problems and will coexist for many years to come. Viasat continues to invest in its IoT Nano and IoT Pro services, and similarly, Iridium is planning to launch its own NTN NB-IoT service in the next two years and that will exist alongside their SBD, IMT and Certus 100 IoT services.

NTN NB-IoT opens up entirely new classes of applications that were previously cost prohibitive, thanks to its lower device and connectivity costs. However, this comes with trade-offs in data volumes, latency, coverage, and potential congestion. It is, at its core, a cellular standard adapted for satellite use, whereas proprietary systems were purpose-built for satellite, optimized to send data as efficiently as possible while conserving power and bandwidth.

Looking further ahead, in the mid-2030s, we expect to see the introduction of NTN NR (New Radio), a next-generation standard that supports much higher data rates and lower latency. While this could significantly change the landscape, it’s too early to predict what the commercial proposition will look like or whether it could compete directly with purpose-built satellite services.

Ultimately, the physics of satellite communication impose unavoidable constraints: it will always be more expensive and power hungry than terrestrial cellular networks, which limits its use to specific scenarios. The deciding factor over the next decade will not just be technology, but commercial dynamics – which service delivers the best mix of coverage, performance, and cost for a given application.

How well does it perform in environments with heavy metal or interference, such as steel plants?

No satellite IoT service – including NTN NB-IoT – can transmit reliably through heavy metal structures. For successful operation, the antenna must have a clear, unobstructed view of the sky. In environments such as steel plants or shipping yards, this usually means placing the antenna outside the structure or in a location with minimal obstructions.

For more guidance on what “clear view of the sky” really means and how to plan antenna placement, see our article: What Does a Clear View of the Sky Mean?

Antenna Requirements

Does NTN NB-IoT require direct line of sight, and how does it perform under partial obstruction (e.g., forest canopy)?

Viasat’s NTN NB-IoT service requires direct line of sight between the antenna and the satellite because it operates on GEO (geostationary) satellites. If the signal is obstructed, for example, by buildings, thick forest canopy, or even certain vehicle structures, performance will degrade significantly, and the connection may fail altogether. This makes careful antenna placement essential.

By comparison, services using LEO (Low Earth Orbit) satellites, such as Iridium’s forthcoming NB-IoT service, NTN Direct, are a little more forgiving. With multiple satellites constantly moving across the sky, a general “clear view of the sky” is sufficient, and temporary obstructions are less of a problem.

For practical guidance, see our article: What Does a Clear View of the Sky Mean? This explains how to evaluate your site and position antennas for reliable connectivity, whether you’re dealing with trees, rooftops, or industrial environments.

Are the satellites supporting NTN NB-IoT GEO, LEO, or a mix?

Viasat’s IoT satellites are currently all geostationary (GEO), meaning they orbit approximately 35,786 km above the Earth’s equator and remain fixed over a point on the planet. Once a link is established with a GEO satellite, it’s highly stable (if the endpoint is static) and reliable; however the greater distance means longer latency than satellites in Low Earth Orbit (LEO).

In 2027, we anticipate Iridium will launch its NTN NB-IoT service on their LEO satellites. This will create competition and allow devices to potentially connect to both GEO and LEO satellites for the same class of service.

For anyone interested in diving deeper into how satellite orbit height affects performance, our definitive guide is here: How Satellite Orbit Heights Impact Satellite Communication.

In Summary

NTN NB-IoT opens up exciting new possibilities for connecting devices in remote or hard-to-reach locations, enabling low cost, low power communication at a scale that was previously out of reach for many industries. However, like any technology, it has its strengths and limitations. It’s best suited to small, infrequent transmissions where latency is acceptable, and less suited to real time or high data volume applications.

If you’d like to explore NTN NB-IoT further, we’ve included some recommended resources below. And if you still have questions or want to discuss how NTN NB-IoT might fit into your specific project, please get in touch using the form at the bottom of this page, or email hello@groundcontrol.com; our team will be happy to help.

Further Reading About NTN NB-IoT

Any more questions?

If you didn’t find the answer you were looking for, or if you’d like to discuss how NTN NB-IoT could fit into your project, our team is here to help.

Simply fill out the form, and one of our experts will get back to you to talk through your requirements, explore possible solutions, and help you plan your next steps.

Whether you’re just starting to explore NTN NB-IoT or are ready to move ahead with a deployment, we’ll work with you to find the right approach for your application.

Name
Privacy Policy

Unmanned aerial vehicles are no longer confined to the pilot’s line of sight. Today’s drone programs, from infrastructure inspection across deserts to search and rescue in the Arctic, depend on rock solid, global data links. Satellite connectivity has gone from “nice to have” to mission critical, but integrating it brings a fresh set of challenges: regulatory approvals for BVLOS, SWaP trade-offs inside a tiny airframe, keeping latency low for real time piloting, and building in fail-safe handovers when the sky gets crowded.

In this guide, we tackle the questions drone manufacturers ask most often. We’ll show you how to:

 

Click on the above links to jump straight to your top concern, or read straight through for an end-to-end blueprint. Let’s get you connected.

Q: What Makes BVLOS so Challenging, and How Can Satellite Connectivity Help?

A: Flying Beyond Visual Line of Sight (BVLOS) introduces several core challenges which satellite connectivity can help mitigate using commercially available, aviation-tested technologies. The insights below draw on findings from Iridium’s excellent white paper, Monitored BVLOS Operations & Safe Separation, which we highly recommend reading in full.

1. Detect and Avoid (DAA)

Challenge: Drones must detect and steer clear of nearby aircraft, especially in non-segregated airspace.

Satellite role: By integrating Commercial Off-the-Shelf (COTS) avionics such as ADS-B In, and using satellite communications to deliver traffic data to the RPIC, operators can enhance situational awareness and support onboard or ground-based DAA strategies, even in regions with no ground infrastructure.

2. Reliable Command & Control (C2)

Challenge: Maintaining a robust, real-time command link is critical, but VHF is unavailable in remote areas and LTE coverage is patchy.

Satellite role: Iridium L-band communication links deliver consistent, uninterrupted C2 performance, even in remote and hostile environments where terrestrial networks fail. In test flights, satellite C2 links proved more reliable and continuous than LTE. Aircraft with dual independent L-band satcom systems also gain redundancy, ensuring control is maintained even if one link fails.

3. Communication with Air Traffic Control (ATC) and Other Aircraft

Challenge: Drones operating in controlled airspace still need to maintain communication with ATC and be aware of other traffic, even without VHF.

Satellite role: COTS satcom solutions can be used to maintain communication between RPICs and ATC where ground-based VHF isn’t an option. Integrating technologies such as ADS-B In and Out over satellite provides RPICs with the same traffic visibility expected of crewed IFR flights.

4. Regulatory and Certification Barriers

Challenge: Aircraft type certification processes were built for decades-long product cycles, not fast-evolving drone platforms. A 36 month certification timeline often means that core systems (e.g. batteries, avionics) are outdated by the time certification is complete.

Satellite role: While waiting for certification frameworks to catch up, drone operators can pursue BVLOS waivers for specific missions. Embedding a standardized Minimum Equipment List (MEL) of proven, COTS avionics and satcom hardware strengthens the case for safe, monitored BVLOS operations and supports a more scalable path toward regulatory approval.

Q: How Can I Integrate Satellite Connectivity Into My Drone Without Compromising on Size, Weight, or Power?

A: Thanks to ongoing improvements in satellite IoT hardware, it’s now possible to integrate satellite connectivity into a drone without breaking your SWaP budget, but there are trade-offs. Smaller, lighter, message-based modules like RockBLOCK 9603 and 9704 are ideal for sending telemetry or basic commands with minimal power draw. However, if your application demands real-time command and control, you’ll need a larger, IP-capable device like the RockREMOTE Mini OEM, which delivers more functionality, but at a higher cost in power and space.

1. Managing the SWaP Budget for Satellite Modules

Fortunately for UAV manufacturers, satellite IoT modules have been on a smaller, lighter, lower-power draw trajectory for several years, so it’s not usually difficult to find a module that will fit into your enclosure. Our most popular device is the RockBLOCK 9603, weighing just 36 g (1.27 oz) and measuring 45 x 45 x 15 mm. This incorporates a patch antenna, but because it usually sits within a metal enclosure, an external antenna is often deployed.

 

However, there are trade-offs between module size and capability. RockBLOCK 9603 utilizes Iridium’s Short Burst Data service (SBD), which is suitable for some drone applications, but not all.

It works well as a failover means of communication in the event that the primary means of communciation (usually radio) drops; to transmit the drone’s position, altitude and speed, and to issue basic commands (go to the nearest rally point; go home; terminate flight etc.).

If you simply need to send more data – for example, compressed images or multiple sensor readings – RockBLOCK 9704, which utilizes Iridium Messaging Transport (IMT), delivers much larger data packets, and is similarly small and light (35 g / 48 x 52 x 16 mm for the SMA – external antenna – option).

Both of these solutions are message-based, however, which makes them less suited to real-time command and control of your UAV. For this purpose you need an IP-based transmission, and that means both a larger device, which draws more power.

RockBLOCK-being-used-in-UAV

2. Trade-Offs Between Module Size, Transmit Power, and Battery Life

An IP-based connection enables near real-time communication, making it ideal for applications like command and control, or remote diagnostics. However, this comes at a cost: IP-based modules require more processing power, memory, and a more complex operating system, which increases both size and power consumption. They also transmit higher volumes of data, which typically requires more energy per transmission.

Our recommended hardware for an IP-based connection is RockREMOTE Mini OEM, as this utilizes both the Iridium Certus 100 airtime service, running at 22/88 Kbps, and Iridium Messaging Transport, giving you the option to save power and potentially costs by transmitting some data in a packet format, and reserving the IP connection for real-time applications. It’s also one of, if not *the*, smallest and lightest options for UAV IP communication.

Q: How do I Manage Latency When Designing Satellite Connectivity for Drones?

A: LEO satellites offer low latency – typically 0.5 – 1.5 seconds for IP-based services – making them ideal for real time drone control, while message-based protocols (around 10 seconds latency) are better suited to delay-tolerant data like location or telemetry. GEO satellites add more delay due to distance, but can still be effective for non-urgent communications.

Latency – the time it takes for your data to do the trip from your drone to your application – is chiefly governed by the satellite orbit height. Simply, the further away from Earth the orbit, the longer the latency. Satellite networks in Low Earth Orbit (LEO), including Iridium and Starlink, are between 160 and 2,000 km above Earth, and the typical round-trip latency for an IP-based service like Iridium Certus 100 is between 500 – 1,500 milliseconds (0.5 – 1.5 seconds). This makes LEO services ideal for time-sensitive operations like piloting or real time alerts.

It’s worth noting that LEO round-trip latency is longer for a message-based service – around 10 seconds – because the message is queued, then forwarded to a ground station, vs. an always-on transmission model. So, for drone applications, message-based protocols are better suited to delay-tolerant applications (location, altitude, speed; basic commands; failover comms), reserving IP-based connectivity for real time command and control, or live diagnostics.

Satellite Orbit Heights Diagram 2024

Satellites in Geostationary Orbit (GEO) are 35,786 km above Earth; because they’re so much further away, they can ‘see’ much more of the Earth’s surface, so fewer satellites are needed to provide wide coverage. The latency is longer – c. 2 seconds for an IP-based connection such as Viasat IoT Pro, and longer for a message-based solution such as Viasat IoT Nano – because the data has to travel further. However, if you can bake in some latency tolerance into your application, or simply reserve this means of communication for less time-sensitive telemetry, this offers an economical and often very stable means of communication.

Q: Is Satellite Connectivity Financially Viable for Drone Operations?

A: Satellite airtime can be tailored to match drone usage patterns and fleet scale, using flexible subscription models with clear pricing. For many drone operators, particularly those flying BVLOS or in low connectivity areas, satellite becomes cost effective with just 10 – 20 flight hours per month, especially when uptime is mission critical.

Flexible Subscription Models

Recognising that unmanned applications like drones are a key growth market, satellite network operators like Iridium offer increasingly diversified options for airtime. Ground Control, as a long-term Iridium partner, can offer UAV manufacturers and users monthly subscriptions, pay‑as‑you‑go, or annual commitments – all with transparent pricing and volume discounts for larger operations. Operators using existing Certus 100-compatible hardware can activate airtime instantly through Ground Control, simplifying deployment.

When Does Satcom Pay Off?

Although detailed cost breakdowns vary by mission profile, satellite connectivity often becomes cost effective at a relatively modest flight tempo. If your missions involve command/control, telemetry, or operations beyond cellular coverage, satellite ensures reliability that terrestrial networks can’t guarantee. With real time capabilities over Iridium Certus 100 and competitive airtime pricing, operational risk reduction often justifies the cost within 10 – 20 flight hours per month.

Read More About Satcoms For Drones

Connecting Drones Beyond Terrestrial Coverage

Satellite connectivity makes it possible to operate UAVs far beyond the reach of terrestrial networks, but integrating it requires thoughtful design. From managing size, weight and power to understanding latency, throughput and cost, this post outlines the key considerations for adding satcom to your drone system.

If you’re developing a satcom-enabled drone, our team can help you find the right hardware and airtime for your mission. Email hello@groundcontrol.com or complete the form, and we’ll be in touch within one working day.

Name
Privacy Policy

Flying drones Beyond Visual Line of Sight (BVLOS) is the new frontier for commercial and industrial operations. Whether you’re surveying expansive agricultural lands, monitoring critical infrastructure, or conducting environmental research in remote regions, reliable connectivity is the linchpin for mission success. Recognizing this need, we’re excited to unveil Iridium Certus 100 aeronautical airtime plans tailored specifically for drone applications.

Why Satellite Connectivity Matters for BVLOS

Traditional RF and cellular networks may falter once a drone ventures beyond visual range, leading to dropped links, latency spikes, and potential safety hazards. To mitigate these risks, many aviation authorities now mandate a secondary communication channel to serve as a failsafe if the primary link fails. For example, the EASA requires redundant communication systems for BVLOS flights to ensure operational resilience, while the UK Civil Aviation Authority’s guidance similarly calls for dual-link architectures as part of any BVLOS operational authorization. In the United States, the FAA’s UAS BVLOS Aviation Rulemaking Committee report recommends demonstrating multiple active command-and-control links – or an automated failover scheme combining cellular, radio, and satellite – to secure BVLOS waivers.

Why Iridium Works Best

Satellite networks offer coverage with no dependency on terrestrial infrastructure, but that doesn’t mean all satellite networks are the same. In this context, low latency – the time it takes for you to send a command to the drone, and for it to receive it and respond – is critical, and therefore, satellite networks in Low Earth Orbit (LEO) are preferable. This is simply because they are closer to Earth than networks in Geostationary orbit, and therefore the round trip of data takes less time.

Iridium’s satellite network is in Low Earth Orbit, and further, it utilizes the L-Band radio frequency. L-Band signals are extremely reliable, and penetrate poor weather conditions with ease; ideal for mission-critical applications where you can’t afford to lose contact with your asset.

With Iridium Certus 100, operators enjoy 22/88 Kbps of bi-directional data, low latency, and complete pole-to-pole coverage, so your drone’s telemetry, sensor data, and command/control signals remain rock solid. It can be used as a primary or failover means of communication.

Iridium-Global-Coverage-Map-2023

Our new airtime plans capitalize on our decades-long partnership with Iridium to provide flexible data bundles that scale from single drone deployments to entire fleets. Whether customers prefer monthly subscriptions, pay-as-you-go usage, or annual commitments, each plan features transparent rates, with volume discounts available for larger scale operations.

Customers who already own an Iridium Certus 100-compatible device can simply activate their chosen plan through Ground Control, eliminating the need for additional purchases or complex installation processes.

Recommended Hardware for IP Over Satellite

For those seeking an out-of-the-box solution, RockREMOTE Mini OEM provides direct board-level integration of the Iridium Certus 9770 module in a compact, 288 g form factor. Optimized for low power consumption, all non‑RF connections (Ethernet, serial, GPIO) are routed through a single 30‑way header, and installation is as simple as four screw mounts – no external gimbals or moving parts required.

Configuration and firmware updates are managed over Bluetooth LE via a companion app or API, and operators only need to attach the specified MMCX and U.FL antennas for Iridium and GNSS. Rated for operation from –40C to 70C and 95% humidity, RockREMOTE Mini OEM ensures mission-critical stability and performance across extreme environmental conditions.

RockREMOTE-Mini-OEM-with-end-cap-angle-2

Real-world use cases for these new airtime offerings span multiple industries. In agriculture, farmers can obtain real-time soil and crop health data from remote fields, optimizing inputs and maximizing yields. Renewable energy and utilities companies can conduct continuous inspections of pipelines, power lines, and wind turbines, preventing costly downtime and enhancing safety.

During emergency response missions, drones equipped with Iridium Certus 100 connectivity can relay critical situational data from disaster zones or search and rescue sites, accelerating decision-making when every second counts. Researchers performing environmental monitoring can gather long-range data on wildlife habitats, forestry conditions, and ocean patterns, undeterred by geographic isolation. And for jurisdictions that require communication redundancy, our plans serve as a reliable secondary link, providing an essential failsafe that keeps aircraft controllable even if the primary link is disrupted.

With affordable, reliable satellite connectivity and built-in redundancy now within reach, your BVLOS aspirations can become reality. Ground Control’s UAV-specific Iridium Certus 100 airtime plans can help extend your operational envelope, enhance safety, and unlock new business opportunities.

Would You Like to Know More?

If you’d like to get a quote for your UAV airtime, please complete the form, or email hello@groundcontrol.com, and we will respond within one working day.

It’s helpful if you can tell us more about your application, i.e. what sort of function do you need to perform (command and control in real-time, or the transmission of telemetry on demand, for example); any SWaP constraints; where you’ll be operating the drones etc.

Name
Privacy Policy

According to IoT Analytics, the global market for satellite IoT connectivity is projected to grow at a CAGR of 26%, reaching $4.7 billion by 2030. Currently, the satellite IoT market is dominated by proprietary modules – meaning that if you want to use Iridium’s SBD service, you need an Iridium SBD module. These modules and accompanying protocols have been tailor-made for satellite communication, and can move large data payloads quickly and reliably, making them perfect for critical IoT applications such as alerts, command and control, and critical infrastructure.

The growth projected by IoT Analytics is anticipated to largely come from standards-based, rather than proprietary, IoT connectivity. This means using standards built for cellular to move data over satellite, so you can use the same chipset that you would use for cellular NB-IoT to access non-terrestrial NB-IoT (in this context, satellite-based connectivity is almost always referred to as NTN – non-terrestrial network). Analysts believe that the lower cost of modules, ability to switch suppliers, and extremely low power requirements will facilitate new, massive IoT applications.

That said, the cost of manufacturing proprietary modules – which have historically commanded a higher premium – is falling, as scale manufacturers like u-blox and Quectel have started to produce these at a much lower cost. Any massive IoT application which is not latency-tolerant, and/or needs to move larger volumes of data, will have options to explore in the proprietary module space, too.

In this blog post, however, we’re exploring NTN NB-IoT in detail, with the goal of helping systems integrators and network architects evaluate whether this emerging technology will suit their remote connectivity application.

What is NTN NB-IoT?

NB-IoT, or Narrowband Internet of Things, is a cellular technology standardized by 3GPP Release 13 in 2016. It was specifically designed for the Internet of Things. NB-IoT falls into the category of Low Power Wide Area Network (LPWAN) technologies. LPWAN technologies are tailored for devices with specific requirements, distinct from smartphones or mobile broadband connections. Key characteristics include:

Small Data Amounts

Devices are designed to send relatively small amounts of data, typically a few bytes or kilobytes, infrequently. This is suitable for simple sensor data or control commands.

Long Battery Life

Due to minimal data transmission and optimized radio usage, these devices are built to operate for extended periods on battery and/or solar power, often for several years.

Low Hardware Cost

LPWAN technologies typically have low cost hardware costs, which is essential for IoT deployments involving hundreds or thousands of devices spread over large geographical areas.

Wide Area Coverage

LPWAN technologies offer long range, low power, small packet connectivity over extensive areas, enabling huge numbers of devices to run for years on a single battery.

NB-IoT achieves these goals by using a subset of features from traditional LTE cellular technology, operating within a narrow slice of the radio spectrum (80 kilohertz bandwidth). This narrow bandwidth and simpler protocols are key to power efficiency and low cost, reducing the complexity and power consumption of the device’s modem. However, terrestrial NB-IoT devices can only send data in areas with reliable cellular coverage.

Non-Terrestrial Network Narrowband IoT (NTN NB-IoT) combines NB-IoT’s low power, low cost cellular technology with satellite communication, enabling devices to connect via satellites in addition to, or instead of, terrestrial towers.

NTN NB-IoT will, when fully mature as a technology, enable global IoT deployments, for projects involving large numbers of simple, low power, low data devices spread across remote areas and across borders. It extends the benefits of NB-IoT beyond its terrestrial limitations, delivering (depending on the satellite network) up to 100% global coverage.

What are the Benefits of NTN NB-IoT?

In addition to being extremely power efficient, the key benefits of cellular NB-IoT is that it operates in licensed spectrum controlled by Mobile Network Operators (MNOs) and standardized by 3GPP, which offers dedicated capacity, more flexibility in the cellular network for switching and roaming, and multi-vendor support for devices and network infrastructure.

NTN NB-IoT similarly operates within licensed spectrum, in this case, controlled by Satellite Network Operators (SNOs) like Viasat and Iridium. It is actively being standardized within 3GPP; initial support for NTN was introduced in Release 17, and Release 18 (launched mid-2024) is significantly advancing NTN integration into the 5G system. It uses a narrow spectrum of the L-Band, S-Band and Ka-Band frequencies, allowing IoT devices to communicate with LEO, MEO and GEO satellite constellations.

Mobile IoT devices equipped with NTN NB-IoT modules can move from terrestrial networks to satellite networks without needing to use a proprietary module. This means IoT devices can be built with a single chipset that delivers NB-IoT connectivity over both cellular and satellite networks, reducing hardware costs because of production economies of scale.

As noted earlier, proprietary modules are also set to benefit from these scale economics, as large chipset manufacturers like u-blox and Quectel are adding the production of these to their portfolio. A key distinction, however, is that a proprietary module will only allow you to connect with one satellite constellation, whereas an NTN NB-IoT module could connect to any satellite network that supports NTN NB-IoT, which could reduce airtime pricing thanks to competition. It will be some years before there is adequate coverage for this to be realized, however.

The promise of NTN NB-IoT lowering the cost of satellite connectivity has the potential to unlock new massive IoT applications in fields such as environmental monitoring, agriculture, and global asset tracking.

Challenges for NTN NB-IoT

Like its cellular counterpart, NTN NB-IoT is designed for large scale, battery-powered deployments. However, communicating with a satellite using a standards-based module, rather than a proprietary satellite modem, brings a new set of technical and economic challenges to overcome.

Higher Latency

While cellular NB-IoT can achieve sub-second latency, NTN NB-IoT introduces significantly higher delays due to the long round-trip to orbiting satellites. Latency can range from several seconds to tens of seconds depending on link quality, protocol, and retry mechanisms. Applications must be tolerant of delayed responses and asynchronous communication.

Increased Battery Usage

Satellite transmissions require higher power output from the radio module to maintain a stable link, particularly in marginal conditions or at low elevation angles. Combined with longer active sessions (due to higher latency), this can drain batteries faster than in terrestrial NB-IoT deployments. Efficient power management and optimized duty cycling become critical.

Antenna Positioning

Terrestrial NB-IoT signals can penetrate walls and underground spaces, allowing flexible antenna placement. NTN NB-IoT requires a clear, unobstructed view of the sky to connect to a satellite, and in many cases, line of sight to a specific satellite at a fixed angle. This can complicate deployments, especially in mountainous or forested environments.

Coverage

NTN NB-IoT coverage is currently limited to specific regions: spot beams lit over North America, Europe, parts of South America, and Australasia. Coverage is expanding, but it’s far from global. Cellular NB-IoT, by contrast, offers much broader regional coverage wherever networks have been deployed and roaming agreements are in place.

Costs

Although standards-based NTN NB-IoT is cheaper than some proprietary satellite services, it’s many times more expensive than cellular NB-IoT. It is more expensive than proprietary options if you exceed monthly data volumes ~30 kB. Cost models are evolving, but pricing will reflect the more limited spectrum and capacity available in space.

Network Congestion

Satellite networks have far less capacity than terrestrial ones, and as NTN NB-IoT adoption grows, so will contention. Congestion may lead to failed transmissions, backoff delays, or restricted access during peak times, especially in areas with high device density or where consumer direct-to-device (D2D) services compete for bandwidth.

Lower Data Rates

NTN NB-IoT operates at significantly lower physical data rates than terrestrial NB-IoT - typically 1-2 Kbps vs. tens or hundreds of Kbps - and enforces small message sizes (e.g., 256 bytes max). This makes it well-suited for small, infrequent payloads, but unsuitable for bandwidth-heavy or real-time applications.

Data Optimization for NTN NB-IoT

For remote NTN NB-IoT applications, sending occasional small data packets becomes essential to reduce signaling duration and battery energy usage, as well as to minimize costly per-byte satellite usage.

When it comes to selecting how data is transferred, there are two options provided by the key players in the industry: IP and Message-based protocols. And to meet the data constraints of remote NTN NB-IoT applications, these protocols become a choice between UDP/IP and NIDD (Non-IP Data Delivery).

Here’s an example to highlight the differences between UDP/IP and NIDD data packet sizes.

A simple water level sensor is sending a status reading and the raw data is 18 bytes long. On top of that, the application running on the device is using CoAP (Constrained Application Protocol), which adds a 4-byte header. This creates a payload of 22 bytes of application data.

To send this message using a traditional UDP/IP stack, the IP and UDP headers add a further 28 bytes, resulting in a total packet size of 50 bytes. By contrast, using NIDD the message is transmitted without any IP or UDP headers, so the total packet size remains just 22 bytes. This efficiency makes NIDD particularly well suited to low-power, low-data IoT devices operating over NTN networks, where every byte of airtime and every milliwatt of battery power matters.

UDP/IP vs NIDD for NTN NB-IoT Applications

So, the case for using NIDD for NTN NB-IoT is that it reduces the size of data packets to be sent to the satellite, and therefore reduces satellite byte costs, while drawing less power. However, the key benefit of UDP/IP is that the same IP address can be used when moving between cellular and satellite, which is useful for applications which cover devices moving in and out of cellular range, such as maritime vessels or pipeline monitoring.

Comparing UDP/IP and NIDD Benefits

Depending on their agreement with the SNO, some NTN NB-IoT service providers will be offering UDP/IP and/or NIDD solutions, and there are benefits and drawbacks to both. Here is a comparison table to highlight the key differences between each method of data transfer.

UDP/IP over NTN NB-IoT

NIDD (Non-IP) over NTN NB-IoT

Protocol Overhead

IPv4+UDP adds 28 bytes header per packet. Some NTN offerings bill with a 50-byte minimum that includes this IP/UDP header.

No IP/UDP header; payload is carried on signaling (control-plane), avoiding the 28-byte IP/UDP overhead of UDP.

Power Consumption

Higher than NIDD for tiny, intermittent messages because you transmit extra header bytes and maintain an IP data session.

Lower for small, sporadic messages by eliminating IP overhead and using signaling paths designed for low power.

Integration

Easier for standard IP apps; minor firmware/backend changes may be needed.

Requires SCEF/I-API support and backend changes to map messages to your application.

Security

Runs over the Internet path; secure with DTLS/TLS and/or VPN. NAT/VPN commonly recommended for inbound traffic.

Data doesn’t traverse the public Internet; operator exposure functions provide an extra security boundary.

Roaming

Single IP address when moving terrestrial ↔ satellite.

Satellite‑only: no IP address for cellular roam; each uplink uses the NTN pathway.

Best For...

Applications that move in/out of cellular coverage (e.g., maritime, logistics).

Ultra‑low data, stationary sensors where minimizing airtime and power is paramount.

Cost & Minimum Payload Considerations

The economics of NTN NB‑IoT hinge heavily on each provider’s minimum supported packet size. Today, Skylo enforces a 50 B floor (including headers) on every UDP/IP message, effectively eliminating NIDD’s payload‑size savings until true NIDD support arrives. Likewise, Sateliot offers standard 3GPP Rel‑17 NB‑IoT over satellite (UDP/IP only) and hasn’t published any reduced‑overhead or NIDD option, so ultra‑small packet users are forced into that same ~50 B envelope.

Until more satellite operators clarify their packet‑size limits or introduce truly NIDD‑capable services, many “tiny telemetry” applications will find themselves priced out of the savings NIDD could otherwise deliver.

The first full NIDD offerings won’t arrive until H1 2026, when Viasat IoT Direct launches its satellite‑only NB‑IoT SIM, complete with both UDP/IP and NIDD modes. Shortly after, Iridium NTN Direct – built on 3GPP Release 19 NTN enhancements – will also bring standardized NIDD support (devices expected in 2026).

In the meantime, proprietary satellite‑IoT networks such as Iridium SBD and Viasat IoT Nano bill in 10 B increments, making them the only current options for truly tiny, cost‑efficient uplinks – albeit at the price of custom hardware and vendor lock-in.

NTN NB‑IoT Service Timeline

Early 2024 – Summer 2025

  • Skylo rolls out its Release 17-based service (UDP/IP only) via partner MNOs across the United States, Canada, Brazil, Australia, New Zealand and select European markets
  • Sateliot operates a demo LEO fleet for Rel 17 NB‑IoT trials; today’s service is UDP/IP only, with no published NIDD option.

 

H2 2025 (Pilot & Dev Kits)

  • Viasat IoT Direct appears in partner POCs and developer previews (e.g., Ground Control’s Cloudloop integration), with two way NB‑IoT over L‑band. UDP/IP today, NIDD to follow.

 

H1 2026 (Projected Commercial Launch)

  • Viasat IoT Direct full release: satellite‑only NB‑IoT SIM supporting both UDP/IP and NIDD payloads
  • Iridium NTN Direct enters commercial service built on 3GPP Release 19 NTN enhancements (including standardized NIDD support).

 

Will NTN NB‑IoT Open New Markets for Satellite IoT?

NTN NB‑IoT holds clear potential to bring truly global, low‑power IoT to industries unable to leverage terrestrial networks; think widespread environmental sensing, remote infrastructure monitoring and asset tracking in the world’s most isolated regions. However, two pivotal commercial variables will determine how far it can go:

  • Cost per Byte & Minimum Packet Size: Until services offer sub‑30 B NIDD payloads at competitive rates (versus today’s 50 B UDP/IP floors or proprietary 10 B options), many micropacket use cases will remain marginal.
  • Network Capacity & Congestion Management: Supporting massive fleets of devices over narrow satellite channels requires robust scheduling, interference mitigation and priority handling – features still under development in Rel 17/18 NTN specs and vendor implementations.

 

Importantly, NTN NB‑IoT does not replace today’s proven proprietary services; it adds to the IoT toolbox. Solutions like Iridium SBD/IMT and Viasat IoT Nano will continue to serve critical, higher throughput or low latency applications, where SLAs, two‑way command/control and strong QoS are non‑negotiable. And, as discussed, the advent of scale manufacturers taking over the production of proprietary modules is set to bring down the cost of these services. NTN NB‑IoT, by contrast, unlocks a new class of latency-tolerant, very small data deployments of homogenous hardware across areas with a mix of cellular and satellite coverage.

Once Viasat IoT Direct and Iridium NTN Direct deliver standardized NIDD in 2026, expect a step‑change: low power, low cost satellite IoT scaling from niche pilots into planet‑wide solutions, while incumbent proprietary networks remain the go‑to for mission‑critical workloads.

Talk to Us About NTN NB-IoT

We’re experts in satellite IoT and asset tracking, and are actively working on new NTN NB-IoT enabled hardware and service integrations with our IoT platform, Cloudloop.

If you have questions about how NTN NB-IoT could enable your IoT projects, please email hello@groundcontrol.com or complete the form to tell us about your requirements, and we’ll reply within one working day.

Name
Privacy Policy

In today’s rapidly evolving landscape of remote monitoring and data acquisition, integrating reliable communication systems is crucial. RockBLOCK RTU integration provides a robust solution for industries such as environmental monitoring, agriculture, and industrial automation, ensuring seamless data collection and transmission from remote locations.
In this post, we will discuss the integration of RockBLOCK RTU, and show how we have configured it to work with the Campbell Scientific CR1000.

What is RockBLOCK RTU, and Why Does it Matter?

RockBLOCK RTU is a low-power, rugged, waterproof remote I/O device designed for permanent installation in harsh outdoor environments. Utilizing Iridium’s Short Burst Data (SBD) satellite service, RockBLOCK RTU supports two way communication anywhere on the globe, ensuring reliable connectivity even in the most remote locations.

Combined with Ground Control’s Cloudloop Services Suite (Subscription Manager and Cloudloop Data), RockBLOCK RTU allows users to land, visualize, store and forward their data in a flexible environment that is easy to integrate with. Aside from the Cloudloop suite, the RockBLOCK RTU supports physical analogue and digital inputs and outputs that can be locally programmed to trigger based on thresholds or actions.

How we integrated the CR1000 with the RockBLOCK RTU

Step 1: Understanding the Data Format
The RockBLOCK RTU system supports a structured data format that includes:

  • Channels CH16 to CH31 mapped to General Purpose Sentence (GPS) data
  • Each channel supports 5-digit values (00000 to 65533)
  • Comma-separated values within the data string.

 

Example Data String:

STXGP0,…,GP15,ETXCHECKSUMCRLF
STX = 0x02 (HEX) – (Start of Sentence)
ETX = 0x03 (HEX) – (End of Sentence)
CHECKSUM = Between STX and ETX (Excluding them) formatted as 5 digits, zero padded
CR = 0x0D (Carriage Return)
LF = 0x0A (Line Feed)
STX00000,00000,00000,00000,00000,00000,00000,00000,00000,00000, 00000,00000,00000,00000,00000,00000,ETXCHECKSUMCRLF

Step 2: Configuring Cloudloop for RockBLOCK RTU

  1. Create Channel: Map channels 16 to 31
  2. Type: Analog Input
  3. General Purpose Data String-related Device Channel Configuration:
    • Mode: RAW
    • COV (Change of Value): 0 for no COV, 1 for COV enabled
    • Group Transmission Size: Minimum 1

 

Note: Channels should get created automatically in Cloudloop Data once valid data is passed through, although each channel can still be re-configured or pre-configured via Cloudloop Data. It is also important to note that the RTU needs to be active, powered and have a good view of the sky for it to receive the channel configurations via the satellite link.

Device Channel Configuration

Example of Cloudloop Data Insights

Cloudloop Data Insights Inputs

This screenshot showcases the Cloudloop platform’s data visualization capabilities when integrated with RockBLOCK RTU. Each channel represents a specific parameter being monitored, such as location (latitude and longitude), battery voltage, snow depth, temperature at various depths, pressure readings, and wind speed. All of which can be named and customized per your requirements. we have chosen the aforementioned parameters for illustration purposes.

Cloudloop Data Insights Altitude Air Pressure
Above – example of visualization of a channel named “Altitude (Air Pressure)”

Step 3: Setting Up Communication

  1. Connect Serial COM2 TX to RX (PINK) on RockBLOCK RTU
  2. Set baud rate to 19200, which is the default for RockBLOCK RTU

 

Step 4: Implementing the CRBasic Code

The CRBasic code constructs data strings in stages to accommodate memory constraints. Temporary strings (TempStr variables) are concentrated to form the final 16 channel DataString.

Example CRBasic Code:

This integration will allow up to 16 sensor values to transmit from the CR1000 through the RockBLOCK via SBD to Cloudloop Data (Insights) and optionally forward to a chosen destination. By introducing Cloudloop Data in the middle of the data transfer, you allow for much more than just data display or remote configuration, but the ability to set email alerts depending on thresholds and even set actions – such as controlling a separate RockBLOCK RTU anywhere in the world autonomously.

Imagine a scenario where one RockBLOCK measures the water level at a dam, and a second RockBLOCK controls a valve on pre-set thresholds.

Ready to get started?

If you’re interested in learning more about how RockBLOCK RTU can transform your remote monitoring capabilities, contact us for a personalized consultation.

Also, have a look at our RockBLOCK RTU documentation website.

Michael Mitrev - Solutions Architect

Graduating with a 1st Class Degree in Computer Systems and Networks Engineering and joining the team in 2024, Michael has been closely involved in the development of the RockREMOTE Mini and is passionate about its growth and success. He's also contributed to the RockBLOCK RTU, ensuring both devices integrate seamlessly with data loggers to create highly sought-after solutions - primarily focusing on testing with Campbell’s CR1000.

Transform your CR1000 into a powerful remote monitoring solution

Whether you’re tracking snow depth, water levels, or environmental conditions, the RockBLOCK RTU + Cloudloop integration offers reliable, global data delivery.

Complete the form, or email hello@groundcontrol.com for expert advice; we’ll respond within one working day.

Name
Privacy Policy

Water utilities worldwide are under increasing pressure to deliver more with less. Ageing infrastructure, growing demand, environmental challenges, and regulatory compliance all demand smarter, more efficient operations. Yet many of the most critical water assets, including pipelines, reservoirs, pumping stations, and metering points, are located in remote or rural areas where conventional cellular connectivity is either unreliable or unavailable.

This connectivity gap has long been a barrier to digital transformation in the water sector. Without reliable communication between remote assets and central systems, utilities face costly manual inspections, delayed responses, and fragmented data. Satellite IoT is helping to bridge that divide, bringing off-grid infrastructure online and enabling smarter, more efficient operations. While proprietary satellite IoT has served this role for decades, a newer, standards-based alternative is now emerging: NTN NB-IoT (Non-Terrestrial Network Narrowband Internet of Things).

NTN NB-IoT, part of the 3GPP standard for satellite-enabled IoT communications, allows connected sensors to communicate with satellites using the same NB-IoT protocol, and chipset, that they would use to connect to a terrestrial network. Economies of scale means that this drives down the cost of the chipset, delivering lower hardware costs, and potentially lower airtime costs too. For water utilities, this unlocks applications that might have been cost-prohibitive prior to the advent of standards-based satellite IoT.

At Ground Control, we specialize in enabling satellite-based connectivity and telemetry solutions for critical infrastructure. As NTN NB-IoT technology matures, we’re perfectly positioned to help water utilities leverage it to extend smart monitoring and control to the very edges of their networks. Here’s how NTN NB-IoT differs from proprietary satellite IoT and where it adds value to smarter water utility operations.

Rethinking Remote Connectivity

As water utilities continue to extend monitoring and automation efforts in remote and rural environments, satellite communication has been, and remains, critical to bridge connectivity gaps where cellular networks are unreliable or unavailable. Until very recently, the only option for utilizing satellites was to use a proprietary satellite module, e.g. if you wanted to utilize the Iridium satellite constellation, you would need an Iridium module.

These proprietary solutions are are built for purpose; the designers have not had to limit their modules’ capabilities to the 3GPP standard, which of course started as a cellular standard. This means you can send more data, more quickly, through a proprietary solution.

Further, if you’re using a message-based proprietary solution, such as Iridium’s Short Burst Data service, Iridium Messaging Transport (IMT), or Viasat IoT Nano, you also get the benefit of power efficiency.

Proprietary solutions, therefore, have been a trusted option for many years, providing reliable, low bandwidth satellite communication for mission critical data such as flow rates, tank levels, pump status, and alarm notifications. They have proven particularly valuable for applications requiring near real-time data or coverage in truly isolated areas.

However, when it comes to massive IoT deployments, proprietary solutions have limitations. Relatively high device and airtime costs, and proprietary integration requirements can make services like SBD, IMT and IoT Nano challenging to deploy at scale, particularly for low-power sensor networks or distributed metering systems.

Enter NTN NB-IoT (what is NTN NB-IoT?).

Proprietary-vs-NTN-NB-IoT

For water utilities, NTN NB-IoT could be a breakthrough. Water utility providers can deploy NTN NB-IoT-enabled sensors, meters, and monitoring equipment in places that were previously cost-prohibitive to connect via proprietary satellite IoT.

What are the Applications for NTN NB-IoT in Water Utilities?

For a water utility weighing NTN NB‑IoT against higher‑bandwidth proprietary satellite links, the sweet spot is infrequent, small payload telemetry where truly global reach (no cell towers) matters more than millisecond alerts. Typical deployments include:

Daily or multi‑hour meter reads
Remote or off‑grid customer meters (flow, volume) that only need to report once or twice a day for billing or usage analysis. A 200 byte payload can easily carry several readings, supporting rural homes, farms, or remote industrial sites.

Tank level and reservoir monitoring
Track water levels, detect overflow risks and monitor usage trends in storage facilities far from population centers. Gravity‑fed storage tanks in remote service areas report level and temperature every few hours – enough to plan refills without real‑time urgency.

Environmental baseline sensing
pH, turbidity, conductivity or chlorine residual sensors on remote intakes or treatment sites. These can trickle in (no pun intended!) once per shift or per day to track long term trends, enabling insight into water quality, and supporting regulatory compliance.

Pump run‑hours and basic status
Hourly or daily “I’m alive” heartbeats plus simple ON/OFF or run‑time counters to track remote booster stations or solar powered pumps, helping to reduce downtime and extend the life of critical infrastructure.

Pipeline integrity logs
Low frequency pressure, flow rate and structural vibration snapshots in isolated, hard to access terrain, allowing early detection of leaks, bursts or blockages to reduce water loss.

Asset inventory and location
Periodic GPS pings and motion/tamper alerts from mobile test vans, valve exercise robots or floating sensors in open canals, optimizing maintenance schedules and improving operational security.

Benefits-of-NTN-NB-IoT-for-Water-Utilities

Beyond NTN NB‑IoT: Scenarios Requiring Real Time Satellite Links

Here are the water‑utility applications that really demand real time links and higher data volumes – i.e. where you’d reach for a proprietary satellite IoT service such as SBD, IMT or IoT Nano, rather than NTN NB‑IoT:

Instant leak/failure alerts
Continuous pressure or flow monitoring that must trigger sub‑minute alarms when a burst or major leak occurs.

Remote valve actuation and control
Two‑way commands (open/close, throttling) with confirmation feedback to isolate sections of pipe or adjust flow on demand.

SCADA‑style telemetry
High frequency readings (e.g. every few seconds or minutes) from multiple sensors (pressure, temperature, vibration) at booster stations and treatment plants.

Video or acoustic inspection
Transmitting snapshots, short video clips or high‑resolution acoustic signatures from remote intake structures or pipeline inspection robots.

Predictive maintenance analytics
Bulk uploads of rich sensor datasets (e.g. vibration spectra, pump performance curves) to cloud analytics for failure prediction.

Bi‑directional firmware updates and diagnostics
Pushing larger firmware or configuration payloads OTA (over the air), plus logging back detailed health / status reports in real time.

Event‑driven sampling
Millisecond‑resolution burst data (e.g. transient pressure spikes) that need to be streamed offsite immediately for analysis.

Benefits-of-Proprietary-Satellite-IOT

Emergency backup SCADA link
A full‑bandwidth failover channel when terrestrial SCADA lines go down, to keep control room visibility alive.

These use cases all hinge on low latency, two way communication and/or bulk data transfers; capabilities that proprietary satellite IoT is designed to deliver.

What is NTN NB-IoT?

Simply, NTN NB-IoT allows data to travel over satellite using the same standard as terrestrial NB-IoT. This means that the same chipset can be used for satellite or cellular connectivity, leading to lower hardware costs, and potentially, lower airtime costs.

It doesn’t, however, mean that it is identical to terrestrial NB-IoT, and network architects need to bear its limitations in mind. We’ve outlined some of the key differences in the following table:

NTN NB-IoT (via Skylo)

Cellular NB-IoT

Proprietary Satellite IoT

Max Practical Payload

256 bytes

1,400 - 1,600 bytes

100,000 bytes

Latency

High (10 - 60 s); MVNO scheduling ⟶ 2 - 5 min

Low (1 - 10 seconds)

Medium (c. 10 seconds)

Directionality

Bidirectional (protocol level) but uplink-focused in practice

Bidirectional

Bidirectional

Coverage

United States, Canada, Brazil, Australia, New Zealand and select European markets

Terrestrial (nationwide but no maritime/remote)

Global

Typical Transmissions Per Day

Common MVNO plans: ~1 - 3 uplinks/day (entry tiers)

No strict cap: supports thousands to tens of thousands of uplinks/day (limited only by data plan allowances)

No strict cap; governed by data plan allowances

In summary, users can anticipate smaller data volumes, and intermittent data transmission (e.g. a few times per day), allowing devices to operate for years on battery and solar power. NTN NB-IoT is, therefore, ideal for low bandwidth, low power, and long life IoT applications.

A Smarter Approach to Connectivity

NTN NB‑IoT shines when you need occasional, small payload uplinks from truly off-grid assets. Its standards based 3GPP Release 17 stack makes integration straightforward, devices run for years on battery, and you can monitor things like daily meter reads, tank levels, water‑quality snapshots or pump “heartbeats” in remote terrain without laying any infrastructure.

Proprietary satellite IoT earns its keep when you need low latency, high volume, two way links, for real time leak/failure alarms, remote valve control, SCADA‑style bursts, video or acoustic inspections, large OTA updates, and emergency failover.

With decades of experience in satellite communications, Ground Control offers more than just connectivity; we deliver complete, integrated solutions from device to cloud. So, whether you’re starting a pilot water management project or scaling a nationwide deployment, we’re here to help you harness the full potential of NTN NB-IoT and build a smarter, more resilient, and efficient water utility network.

Ready to explore your options?

Curious which satellite technology is right for your application? Whether you’re rolling out smart meters in rural areas or need real time alerts from critical infrastructure, we can help you choose the best fit solution.

Talk to our team for a side-by-side comparison of NTN NB-IoT and proprietary satellite IoT, based on your data needs, latency requirements, and power constraints.

Email hello@groundcontrol.com or complete the form, and we’ll be in touch within one working day.

Name
Privacy Policy

In today’s digital battlespace, Assured Positioning, Navigation, and Timing (APNT) is more than a utility; it’s the invisible infrastructure behind every mission. As adversaries grow more technologically capable, the reliability of conventional GPS-based systems is increasingly at risk. Electronic warfare tactics, such as GPS jamming and spoofing, can create blind spots and disrupt mission-critical functions. A resilient solution is needed, designed to maintain accurate, trusted location and timing data even when GPS is spoofed, faked or denied.

From satellite tracking and coordinated troop movements to secure communications and synchronized operations, reliable PNT enables modern militaries to act with speed, accuracy, and global reach.

Encapsulated within Ground Control’s RockSTAR APNT device, reliable, global, and jamming-resilient positional awareness can be achieved by military personnel in hostile, GPS-contested environments. This blog examines the modern-day need for reliable location assurance beyond GPS for military effectiveness.

 

Why PNT Is Critical for Military Success

PNT systems, chiefly GPS and GNSS, are foundational to all branches of modern defense, forming the backbone of situational awareness, coordination, and operational execution. Real-time, accurate positioning provides the precise geolocation of military forces, vehicles, and critical assets, allowing commanders to make informed decisions in real time.

Navigation enables units to move accurately and more safely across land, air, or sea to ensure missions stay on course and with optimum execution. Timing is crucial for synchronizing a wide range of activities, from encrypted communications and sensor network operations to financial transactions and time-sensitive Intelligence, Surveillance, and Reconnaissance (ISR) data processing.

Numerous military functions rely on accurate and uninterrupted PNT, including Blue Force Tracking (BFT) – a system that utilizes GPS technology to track the location of friendly forces, cybersecurity command and control (C2) systems, precision time-stamping for ISR platforms, and the coordination of multi-domain operations. Without reliable PNT systems and GPS/GNSS, these operations can quickly become disjointed, inefficient, and vulnerable, jeopardizing both mission success and the safety of military personnel.

The GPS Vulnerability Problem

While GPS remains the backbone of PNT, it is vulnerable. GPS signals are low power, unencrypted and easy to jam, spoof, or fake with relatively inexpensive equipment.

In hostile environments, such as near-peer conflict zones and congested battlespaces, adversaries often target GPS to disrupt coordination, conceal positions, or disable military tracking systems.

Even in peacetime or humanitarian missions, natural obstructions like urban canyons, mountains, and indoor locations can degrade signal reception.

APNT is different. A key component of APNT is the use of one-way, secured signals transmitted from Low Earth Orbit (LEO) satellites. These signals are significantly stronger than traditional GPS – up to 1,000 times more powerful in some systems – making them far more resistant to jamming and interference. When integrated into a layered APNT architecture, these satellite-based signals help ensure trusted timing and location data even in GPS-denied environments.

Diagram-Showing-RockSTAR-APNT-in-Military-Applications

It’s worth noting that APNT is designed to complement, not replace, GPS and GNSS-based systems. PNT and APNT signals are compatible with some of the same hardware that supports GPS, allowing for seamless integration into existing navigation solutions. This makes APNT an ideal component of a layered satellite-tracking system strategy, enhancing resilience,
security, and continuity of positioning and timing services in critical military applications.

 

RockSTAR APNT For Assured PNT Beyond GPS

 

RockSTAR APNT offers a hardened alternative to GPS-based timing and location services. By leveraging LEO satellites and cryptographic techniques to verify authenticity, the device transmits high-power signals resistant to spoofing, jamming, and signal degradation, critical for military communications when GPS is compromised. Further, it’s operable indoors and in
urban locations where GPS often fails.

RockSTAR APNT delivers real-time timing accuracy, which is a critical capability for coordinating dispersed units across multiple domains, maintaining secure communications, and operating time-sensitive radar, sensor, and surveillance systems. Positional data in real-time ensures optimum decision-making in dynamic environments.

Engineered for portability and resilience, RockSTAR APNT is compact, field-ready, dustproof and waterproof. Built to military standards, it’s ideal for manned deployments: tactical vehicles, Forward Operating Bases (FOBs), field command posts, and portable mission kits.

RockSTAR STL Close Up

The Embedded APNT Choice

For unmanned or unattended deployments, RockBLOCK APNT offers the same resilient satellite time and location capability in a compact, ruggedized form factor. Designed for integration into autonomous systems, remote infrastructure, and stationary platforms, it ensures critical operations remain synchronised and secure, even in heavily contested GNSS environments.

With the ability to transmit APNT data, as well as text-based messages and telemetry data (up to 100 KB per transmission), RockBLOCK APNT also serves as an effective failover
communication channel when primary systems are compromised or unavailable. Its versatility and resilience make it a valuable asset for mission-critical operations where assured connectivity is essential.

RockBLOCK-Pro-Web-Angled

A Layered PNT Strategy for Modern Defense

As militaries shift toward Multi-Domain Operations (MDO), the security and reliability of PNT and GPS are strategic priorities. Relying solely on GPS is no longer acceptable. The U.S. Department of Defense and allied nations are actively pursuing Assured PNT (APNT) initiatives, combining multiple sources to create a layered, fault-tolerant system. RockSTAR APNT and RockBLOCK APNT are key enablers of this strategy in providing a complementary, GPS-independent signal that strengthens the PNT architecture.

 

 

Gain The Advantage With Mission Ready Satellite IoT

For over 20 years, we’ve partnered with defense forces, government agencies, and security contractors to develop a number of military-grade devices, harnessing APNT.

Learn how this technology can give you the tactical advantage in your mission-critical operations.

READ BROCHURE
Military brochure cover

Can we help?

Our satellite-enabled RockSTAR APNT and RockBLOCK APNT solutions offer robust positional data connectivity when GPS fails, for defense applications and more. Partner with us to explore all our satellite solutions that safeguard your military operations and personnel anywhere in the world.

Complete the form or email hello@groundcontrol.com and we’ll get back to you within one working day.

Name
Privacy Policy

One of the most disruptive threats to commercial and military maritime operators is the manipulation of Global Navigation Satellite Systems (GNSS), primarily by low-cost GPS jammers, state-sponsored GPS spoofing campaigns, and cyber-physical interference. From oil tankers seized via spoofed coordinates to cargo ships disappearing from satellite tracking due to jamming, the vulnerabilities of GNSS reliant systems are no longer theoretical, they’re operational hazards. These disruptions compromise navigation, safety, and compliance monitoring, particularly in high-risk regions such as the Baltic Sea, Eastern Mediterranean, and other areas with geopolitical tensions.

GPS Jamming Issue Grows in Eastern Mediterranean and Black Seas
Daily, October 1, 2023 – April 4, 2024

Growing Number of GPS Jamming Attempts

GNSS/GPS manipulation has far-reaching implications, from compromised navigation to operational disruptions. While there are various satellite-based techniques for detecting spoofing and jamming, RockBLOCK APNT offers a truly resilient alternative. In this blog, we explore how it works and why it matters.

Key Differences Between Jamming and Spoofing

Jamming

Spoofing

Definition

Overwhelms GNSS signals with noise to block reception

Sends fake GNSS signals to mislead the calculation of a false position/time

Mechanism

High-power RF signals on GNSS frequencies disrupt signal acquisition

Fake signals mimic legitimate ones, often stronger, to deceive the vessel

Goal

Denial of service (DoS) – prevents GNSS-based operation

Deceives the receiving vessel into believing a false position or time

Effect on receiving vessel

Loss of satellite lock; receiving vessel cannot determine position/time

The receiving vessel continues to operate, but with incorrect data

Detection Difficulty

Often easy to detect due to complete signal loss

Harder to detect, may go unnoticed as the vessel operates normally

Signal power

High (to overpower weak satellite signals, typically > -100 dBm)

High (to overpower weak satellite signals, typically > -100 dBm)

Legality

Illegal in most countries

Also illegal, often more complex to execute and trace

Hardware Requirements

Relatively simple - can be handheld or vehicle-mounted

More complex, requires GNSS signal generation and precise timing

Use Cases (Malicious)

Disrupt vessel navigation, leave crew and cargo vulnerable to attack

Mislead ships, expose ships to hijacking, steer vessels into dangerous waters

Implications for the Shipping Industry

The interception and denial of GNSS/GPS connectivity pose significant risks to the commercial shipping industry. GPS spoofing, for example, misleads shipping vessels into believing they are on a safe course when in reality, they may be heading into dangerous waters or restricted areas. Reports indicate that vessels in the Eastern Mediterranean have been falsely located at airports, and other instances have shown ships being misled into high-risk territories. Many vessels, especially those without backup navigation systems, are vulnerable to these attacks.

In July 2019, the UK-flagged oil tanker Stena Impero, operated by Stena Bulk, was seized by Iranian forces while transiting the Strait of Hormuz. Investigations suggest that the vessel’s navigation systems were subjected to GPS spoofing, causing it to deviate into Iranian territorial waters. Analysis of AIS data indicated anomalies consistent with spoofing attacks, where counterfeit signals misled the ship’s navigation systems. This incident highlighted the vulnerabilities in maritime navigation and the potential for state actors to exploit them.

Later in 2019, vessels operating near Chinese ports, particularly around Shanghai, reported widespread GPS anomalies. Ships experienced sudden changes in reported positions, with some appearing to move erratically or vanish from tracking systems. Investigations revealed that these anomalies were due to GPS spoofing attacks, affecting hundreds of vessels and disrupting port operations. The incidents raised concerns about the potential for such attacks to be used for strategic or economic purposes, with the United Nations urging the protection of satellite navigation from interference.

Spoofing and Jamming Detection via Satellite

Satellite systems can detect GNSS/GPS spoofing and jamming by identifying inconsistencies via a number of indicators and parameters.

Positional behavior can indicate spoofing or jamming. Satellite systems can identify positional and movement abnormalities and send alerts when ships “jump” positions, show physically impossible maneuvers, such as a 90° turn at high speed, or appear in two locations simultaneously, known as ghost ships. Further, comparison with terrestrial radar and sensors is a method of spoofing detection. Satellites compare reported Automatic Identification System (AIS) data with ground radar or visual surveillance, and mismatches may indicate spoofing.

To avoid and prevent spoofing and jamming attacks, commercial shipping companies can support risk-based routing. Here, shipping companies use historical spoofing “heat maps” to reroute vessels around known interference zones, such Baltic Sea, Eastern Mediterranean, and any other region or zone with geopolitical tensions.

These detection techniques are effective, but the vulnerabilities of GNSS/GPS signals remain. A secure and resilient solution is required for complete visibility and confidence of vessel positioning at sea.

Iridium PNT For GNSS/GPS Protection at Sea

While satellite-enabled detections exist to combat traditional GNSS/GPS spoofing and jamming, Iridium offers an uncontested solution – a secure alternative for acquiring positioning, navigation, and timing (PNT) information anywhere in the world.

Iridium PNT is a one-way signal broadcast via the Iridium satellite constellation, 1,000 times stronger than GPS, making it far more resilient to jamming. Leveraging Iridium’s LEO satellite constellation and thus, a signal 25 times closer to the Earth than GNSS, Iridium PNT delivers accurate time and position data without needing traditional GNSS visibility, giving commercial ships and maritime systems trusted positioning even when GPS is denied.

Iridium PNT is not designed to replace GNSS; rather, it’s designed to complement it. Many existing GPS/GNSS receivers are capable of receiving Iridium PNT signals, making it easy to incorporate as part of a layered approach to reliable, secure and resilient tracking and positioning.

Diagram-of-RockBLOCK-APNT-in-Maritime-Application

How RockBLOCK Utilizes Iridium PNT for Jamming-Resilient Maritime Tracking

RockBLOCK APNT is a ruggedized, compact satellite-based tracking solution that harnesses the power of Iridium PNT to deliver a secure signal independent of terrestrial or GNSS infrastructure. This PNT service offers an alternative when GPS or GNSS Global signals are absent, denied, or disrupted.

Traditional GPS signals are vulnerable and easy to overpower or imitate with spoofing equipment. Iridium PNT, by contrast, resists these threats through cryptographic techniques so spoofers cannot easily mimic the signals. Complementing traditional GPS / GNSS and delivering a reliable backup, RockBLOCK APNT enables transmission of vessel location updates even when GPS / GNSS is being denied, spoofed, or jammed.

This is vital for commercial ships as well as vessels transiting piracy or cyber-prone regions, unmanned surface vehicles (USVs) operating in contested waters and NATO and allied vessels conducting patrols in high-risk areas.

RockBLOCK-Pro-Web-Angled

The technology encapsulated within RockBLOCK APNT is designed for ease of integration with existing maritime equipment. The solution delivers RS232 / RS485 and USB-C serial interfaces for easy integration with existing hardware, IP66 waterproofing – ideal for harsh marine conditions – and a compact, low-power design for permanent and portable deployments. It’s a secure and rugged solution for shipping companies to tackle the ongoing threat of GPS spoofers and jammers.

Operational Scenarios with RockBLOCK APNT

There are several operational scenarios where RockBLOCK APNT provides an uncontested, reliable solution to GPS-denied environments, spoofing, and jamming:

Anti-Spoofing for Cargo Ships: A container vessel approaching a spoofing hotspot in the Eastern Mediterranean receives conflicting GPS signals. RockBLOCK APNT continues to deliver trusted positioning, allowing the bridge crew and HQ to detect the spoof and maintain safe routing.

Naval Operations in Denied Environments: A patrol vessel operating under electronic warfare conditions near contested maritime borders loses GPS functionality. Utilizing RockBLOCK APNT, onboard systems retain accurate time and position data, crucial for navigation, targeting, and tactical coordination.

Unmanned Maritime Drones: An autonomous surface vessel in the Arctic Circle cannot acquire GPS due to interference. RockBLOCK APNT ensures connectivity, continuity and remote GPS monitoring via Iridium.

Secure Positioning When GPS Goes Dark

From bulk carriers drifting off-course in the Black Sea to naval vessels being targeted in the Red Sea, GNSS/GPS interference has shifted from a rare anomaly to a strategic weapon. The rise of low-cost jammers, state-sponsored spoofing campaigns, and cyber-physical interference has exposed a serious blind spot in global shipping: overdependence on vulnerable, unprotected GNSS/GPS satellite signals. RockBLOCK APNT provides an essential layer of protection, ensuring a secure, resilient, and critical connection to vessels at sea.

With RockBLOCK APNT, Ground Control offers a compact, secure, and rugged satellite-based solution that ensures maritime assets stay online, stay located, and stay safe, even when GPS goes dark.

Can we help?

Partner with us to implement satellite technology that safeguards your maritime operations and enhances secure, real-time data transmission wherever your journey takes you.

Complete the form or email us at hello@groundcontrol.com and we’ll get back to you within one working day.

Name
Privacy Policy

Ground Control has launched the RockBLOCK Pro, the first certified Iridium Certus 9704 device available through an Iridium partner. This rugged satellite IoT gateway utilizes the new Iridium Certus® 9704 module and Iridium Messaging Transport (IMT). The RockBLOCK Pro delivers enhanced performance compared to earlier RockBLOCK versions, and features faster speeds, substantially increased message size capabilities, and improved power efficiency. This makes it well-suited for critical remote operations.

RockBLOCK Pro utilizes the Iridium 9704 module to send bi-directional messages from 25 bytes up to 100 KB, supporting aggregated sensor data, imagery and audio clips while maintaining end-to-cloud latency under 10 seconds. Compared to the Iridium 9602 and 9603 modules, the 9704 achieves up to an 83% reduction in idle power consumption, making it the most power-efficient Iridium module ever.

Engineered for harsh outdoor and industrial use, RockBLOCK Pro is rated IP66 and can be specified with either the built-in high-gain antenna or an external antenna. Full support for the legacy Iridium AT command set ensures a drop-in upgrade path for existing SBD deployments, with no need to alter host firmware or development toolchains.

RockBLOCK-Pro-First-Image

For seamless end-to-end messaging, RockBLOCK Pro integrates tightly with our Cloudloop Data platform, which delivers messages via direct cloud-platform integrations, including AWS, Azure and Google Cloud environment, or can be routed via HTTP webhooks, MQTT streams, or even email. Onboard GNSS, Bluetooth, and configurable digital I/O further expand its utility in telemetry, asset tracking, environmental monitoring, and autonomous applications.

Alastair MacLeod, CEO of Ground Control, said: “RockBLOCK Pro redefines the satellite IoT gateway category by bringing together power efficiency, rugged design, and data capacity in a compact footprint, unlocking smarter, more responsive systems in the world’s most remote places. As the first partner to bring a certified Iridium Certus 9704 product to market, we’re proud to lead the next chapter of global IoT.”

“The Iridium Certus 9704 packs a lot of power in a compact module, making it ideal for IoT applications that require real-time data analysis, analytics and automated decision-making,” said Tim Last, executive vice president of sales and marketing, Iridium. “Ground Control has been a trusted Iridium partner for many years, with a proven track record of delivering high quality developer hardware built on Iridium technology. We’re excited to see them leading the way with innovative solutions that bring high performance satellite IoT connectivity to the most remote parts of the world.”

RockBLOCK Pro is now open for early access inquiries.

The initial production run begins in May, followed by full production starting July 2025.

To learn more or reserve your unit, please contact Ground Control or complete our early access form at groundcontrol.com/product/rockblock-pro/

Name
Privacy Policy