Between the ultra-lean narrowband tier and full-throughput LTE sits a class purpose-built for field telemetry that needs a bit more headroom - some real bandwidth, the ability to move, and still-frugal power. That class is LTE Cat-M1. It is the cellular IoT tier that many modern RTUs and gateways default to because it strikes a workable balance for the messy realities of the field. This guide explains what Cat-M1 is, when to choose it over NB-IoT, its coverage and power characteristics, and the role it plays in connecting cellular RTUs and gateways in SCADA.
LTE Cat-M1 in one line: LTE Cat-M1, also written LTE-M or Cat-M, is a low-power cellular IoT category that offers higher throughput and full mobility compared with NB-IoT, while still drawing far less power than standard LTE. It supports moving assets, moderate data rates, and handover between cell towers, which makes it a common choice for cellular RTUs and gateways that need more than a narrowband trickle but far less than a full LTE connection.
LTE Cat-M1 belongs to the same low-power cellular IoT family as NB-IoT, but it is deliberately more capable. It uses a wider channel, which gives it meaningfully higher throughput - enough to move moderate amounts of data rather than just a handful of bytes - and lower latency than a narrowband link. That extra headroom lets Cat-M1 do things NB-IoT cannot comfortably do, such as carry a firmware update, handle a short burst of higher-rate data after an event, or support an occasional interactive exchange, all without stepping up to full LTE.
The other defining feature is mobility. Cat-M1 supports handover, meaning a device can move from the coverage of one cell tower to the next and keep its connection alive, the way a phone does. NB-IoT, by contrast, is built for fixed installations and does not manage that movement well. For any asset that travels - a mobile pump unit, a truck-mounted monitor, a rented piece of equipment that moves between sites, a tracked container - mobility is not optional, and it is the single clearest reason to pick Cat-M1 over the narrowband alternative.
Cat-M1 still keeps the low-power discipline that defines the IoT tiers. It works with the same cellular sleep mechanisms that let a device dormant between reports, so a Cat-M1 device can be battery-powered and long-lived even though it can move more data than NB-IoT. It draws more power than narrowband when it is actively transmitting, simply because it is doing more, but it is a world away from the constant power appetite of a full LTE modem. The result is a genuine middle ground: more capability than NB-IoT, far less power than LTE.
The decision between Cat-M1 and NB-IoT comes down to a few concrete questions about the site. Does the asset move? If yes, Cat-M1 is effectively required because NB-IoT does not handle handover. Does the device need to send more than tiny periodic payloads - a firmware push, a data burst, a moderate stream? If yes, Cat-M1's higher throughput earns its place. Does the site need lower, more predictable latency for something like a control interaction? Cat-M1 again. NB-IoT wins when none of those apply and the priorities are instead the deepest possible coverage and the absolute longest battery life on the smallest payloads.
Coverage is a subtler part of the choice. NB-IoT's narrow band gives it the strongest link budget and the deepest penetration into remote or enclosed locations, so a sensor buried in a metal enclosure or at the fringe of coverage may connect on NB-IoT where Cat-M1 struggles. Cat-M1 still has excellent coverage - far better than standard LTE - but the very deepest, most marginal spots are where narrowband keeps its edge. For most field sites Cat-M1's coverage is more than adequate, and its added capability is worth more than the last increment of penetration.
Carrier availability also shapes real deployments. Not every network supports both classes equally in every region, so the practical choice is sometimes made by which technology the local carrier actually offers on the bands and towers covering a given site. Many operators standardize on Cat-M1 as the default for its flexibility and mobility, reaching for NB-IoT specifically for the deep-coverage, ultra-low-power stationary sensors where its strengths pay off, and treating the two as a pair rather than an either-or across a whole fleet.
In modern SCADA, a great deal of remote data now travels over cellular, and Cat-M1 has become a common backhaul for RTUs and gateways that sit above the sensor level. Where a single leaf sensor might use NB-IoT, an RTU that reads multiple instruments at a wellsite, or a gateway that concentrates several field devices and forwards their data, benefits from Cat-M1's higher throughput to move the combined traffic and from its mobility if the unit is ever relocated. The extra bandwidth also makes remote maintenance practical - pushing a configuration change or a firmware update to a field unit over Cat-M1 is realistic in a way it is not over a narrowband link.
Cat-M1 also supports the kind of report-then-sleep operation that keeps field units efficient. A cellular RTU on Cat-M1 can spend most of its time dormant, wake on schedule or on an event, connect, exchange its data, and drop back to sleep, using power-saving features to keep its draw low between reports. This lets a Cat-M1 unit run on battery or a modest solar setup while still being able to move more than a trickle of data when it does wake, which fits the rhythm of unmanned oil and gas sites that report periodically but occasionally need to send more.
For a cloud SCADA platform such as Merobix, Cat-M1 is one of several radio classes feeding the same ingestion path. A Cat-M1 gateway backhauls its site's Modbus, DNP3, or MQTT traffic over the cellular network to the platform, which stores and presents it alongside data arriving via NB-IoT, full LTE, satellite, or radio from other sites. Because the platform treats the backhaul as plumbing, an operator can put mobile and moderate-data sites on Cat-M1, keep deep-coverage sensors on NB-IoT, and reserve full LTE for the heaviest gateways, matching each connection to its job without complicating the data layer above.
LTE Cat-M1 connects cellular IoT devices that need more than a narrowband trickle but far less than full LTE - RTUs and gateways at remote sites, mobile or relocatable equipment, and devices that must occasionally push firmware or a burst of data. It offers moderate throughput, low latency, and mobility while keeping power draw low. That balance makes it a common default for cellular field telemetry.
Choose Cat-M1 if the asset moves, needs moderate throughput, or needs lower latency, since NB-IoT does not handle mobility and carries only tiny payloads. Choose NB-IoT if the priorities are the deepest coverage and the longest battery life on very small, infrequent messages from a fixed location. Many operators default to Cat-M1 for flexibility and use NB-IoT specifically for deep-coverage stationary sensors.
Yes, considerably less. Cat-M1 is a low-power IoT class that works with cellular sleep mechanisms, letting a device stay dormant between reports so it can run on battery or modest solar. It draws more power than NB-IoT when actively transmitting because it moves more data, but it is far more frugal than a full LTE modem, which is built for constant high-throughput connectivity.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.