A meter is installed once, in a basement or a cabinet, and expected to report for fifteen years on a battery nobody will change. That single sentence eliminates most connectivity options, and the remaining choice is decided by coverage in the worst location rather than by throughput in the best.
| Technology | Suits | Limits |
|---|---|---|
| NB-IoT | Static meters in poor coverage sending small readings infrequently | Very low data rate and high latency; no mobility and limited voice or firmware transfer capability |
| LTE-M | Meters needing larger payloads, firmware update or occasional mobility | Higher power draw than NB-IoT and less deep-indoor penetration |
| 5G RedCap | Higher-bandwidth industrial endpoints on a 5G core | Newer, so coverage and module availability vary by market; more capable than a meter typically needs |
| LPWAN alternatives | Sites where an operator network is absent or unaffordable | Requires the gateway network to exist or be built, which shifts the cost rather than removing it |
For most metering the deciding factor is penetration into the specific basement or cabinet the meter sits in, not the headline data rate.
Metering payloads are tiny. A reading is a handful of bytes, and even generous sampling produces data volumes any of these technologies handles comfortably.
So specifying on throughput picks the wrong technology almost every time. The question that matters is whether the module attaches reliably in the worst basement in the estate, on a battery, for the length of the contract, with a path to update it and a supply of parts.
The corollary is that a coverage trial is worth more than a datasheet comparison. Instrumenting a representative sample of the actual install locations, including the difficult ones, answers the question that decides the project.
It depends on coverage at the hardest install location rather than on data rate. NB-IoT suits static meters in poor coverage sending small readings; LTE-M suits larger payloads and firmware transfer; RedCap suits higher-bandwidth endpoints on a 5G core and is usually more capable than a meter requires.
Because metering payloads are tiny — a reading is a handful of bytes. Any of these technologies handles the data volume comfortably, so specifying on throughput picks the wrong technology. Penetration into the specific basement or cabinet decides it.
Through reporting policy rather than cell capacity. Transmission frequency, payload size and how deeply the module sleeps between reports determine lifetime, and each additional daily transmission is multiplied by the fleet and by the years.
The deployment is stranded unless a migration path was designed in. Because a meter outlives at least one network generation, sunset commitments for the chosen technology are a procurement question rather than a technical footnote.
They must be, or they become a security liability. NB-IoT can carry an update slowly; whether that is acceptable depends on image size and fleet size. Where the meter is used for billing, changes touching the measurement path may require requalification.
Written for engineers. Share it with one.
Range against power, compared.
SOLUTIONWater, waste and municipal metering.
SOLUTIONDistributed asset telemetry.
INDUSTRYWhere a site visit costs more than the device.
KNOWLEDGEUpdate as a design decision.
PRODUCTWhere an LPWAN alternative needs one.
Tell us the specification, the constraint and the deadline. Programmes that cross silicon, radio, embedded and AI are where Faststream is strongest.