Why use satellites for smart meters instead of NB-IoT or LoRaWAN on the ground?

Terrestrial NB-IoT and LoRaWAN networks cover urban cores well but leave roughly a third of utility infrastructure — rural pipelines, irrigation pumps, remote substations — without coverage, according to GSMA data. A sovereign LEO constellation solves the coverage gap without waiting for commercial carriers to extend their networks into commercially unattractive areas. It also removes the dependency on a private operator who can reprice, deprioritise, or terminate the service contract.

What data rates do satellite IoT links actually deliver for utility applications?

Most satellite IoT services in this class operate in the 100 bps to 50 kbps range — ample for a smart meter's typical 50–200 byte daily payload but insufficient for continuous waveform monitoring or high-resolution power quality data. Systems requiring broader bandwidth, such as distribution-automation relays, should be designed with satellite as the fallback channel and a wired or terrestrial wireless primary link.

How many satellites does a nation actually need to build a viable utility IoT constellation?

Modelling by Kepler and academic analyses published through UN-OOSA suggest that 18–24 satellites in a Walker-delta configuration at 500–600 km altitude provide 2–4 daily passes over any point on Earth, sufficient for non-real-time utility telemetry. A nation with a mid-latitude geography and fewer than 10 million endpoints could consider starting with a 6-satellite pilot plane and expanding incrementally as launch costs fall.

Is the ITU frequency coordination process a serious obstacle for a new sovereign constellation?

Yes, and it is frequently underestimated. Filing a new satellite network with the ITU Radiocommunication Bureau under the Radio Regulations requires submission of API/A coordination documents, potential bilateral negotiations with existing operators in the same orbital arc, and waits that can stretch to 3–5 years for contested spectrum. Nations should file early, engage ITU-R Study Group 4 expertise, and consider starting operations under a licensed domestic spectrum authority while international coordination proceeds.

Can a sovereign satellite IoT constellation also serve sectors beyond utilities?

Absolutely — and it should, to achieve the payload economics that make the business case viable. The same nanosatellite transponders that collect smart meter data can simultaneously relay agricultural soil sensors, vessel AIS messages, environmental monitoring nodes, and logistics asset trackers. Multi-tenant architecture allows the government to lease capacity to private operators while retaining priority access for critical national infrastructure.

What cybersecurity standards apply to the satellite-to-ground link for utility data?

The CCSDS Security Architecture (CCSDS 351.0-M-1) and the Space Data Link Security Protocol (CCSDS 355.0-B-1) define authentication and encryption for the space segment. On the ground, utility data aggregators should comply with IEC 62351 (Power Systems Security) and national frameworks such as NIST SP 800-82 (Industrial Control System Security). End-to-end encryption must be in place before any meter payload touches the satellite link — the space segment is not inherently secure.

How does a nation handle spectrum licensing for the meter-side radio if it is using a non-standard waveform?

Meter-side radios transmitting to a sovereign LEO constellation typically operate in sub-GHz ISM bands (433 MHz, 868 MHz, 915 MHz) or licensed UHF bands coordinated through the national telecommunications regulator in alignment with ITU Radio Regulations Appendix 18. If the constellation uses the 3GPP NB-IoT-NTN standard (Release 17), devices can reuse certified commercial chipsets, dramatically reducing national type-approval burden and accelerating deployment.

What is the realistic procurement timeline from decision to first operational satellite?

For a nation contracting a nanosatellite bus from an established manufacturer (e.g., GomSpace, AAC Clyde Space, or a domestic integrator using ESA-qualified subsystems), the path from signed contract to on-orbit commissioning is typically 24–36 months for the first unit, with subsequent spacecraft in a batch delivered faster. Full constellation deployment of 18–24 satellites across two to three launch batches realistically takes 4–6 years from programme start to global-coverage milestone.

1.5.5Live

Smart Utility IoT

Utility worker inspecting a smart meter on a wall in a rural setting — A technician monitors solar output on his smartphone, showing how satellite IoT keeps remote energy infrastructure connected in real time.

Satellite IoT Links Remote Utility Sensors

1
IoT Sensor
Meter transmits usage data via radio
2
LEO Constellation
Small satellites relay low-power signals
3
Cloud Analytics
Platform detects faults, calculates billing
4
Utility Dashboard
Operator and customer receive live alerts

Low-power sensors on remote meters uplink through LEO satellites, delivering real-time utility data to operators and customers.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

1.5.4 · Previous

Maritime IoT Networks

All in space-based iot networks

1.5.6 · Next

Environmental Sensor Networks

Bring this into your sovereign programme.

All solutions Speak with engineering