NB-IoT vs LTE-M vs Cat 1 bis: IoT comparison — The Internet of Cargo The IoT Transformation Company

Choosing cellular connectivity for an IoT product is not a contest to find the newest acronym. It is a design decision about where the device will travel, how often it reports, how much data it sends, how long it must run and which networks are actually available along the route.

NB-IoT, LTE-M and LTE Cat 1 bis all use licensed cellular spectrum, but they solve different problems. NB-IoT and LTE-M are 3GPP low-power wide-area technologies introduced in Release 13. Cat 1 bis is a simplified version of LTE Cat 1 that uses one receive antenna instead of two.[1][3]

None is the universal winner. The right answer comes from the workload.

Three technologies, not three generations

It is tempting to arrange the options as a ladder: NB-IoT at the bottom, LTE-M in the middle and Cat 1 bis at the top. That misses the point.

NB-IoT is deliberately narrow. It gives small, infrequent messages a path through licensed networks while keeping device complexity and power demand low. LTE-M adds better mobility, responsiveness and throughput while retaining LPWA power-saving features. Cat 1 bis uses the broader LTE footprint and offers much more data capacity, but it is not classified as an LPWA technology by the GSMA.[1]

The comparison is closer to choosing a vehicle. A bicycle, a van and a truck can all move goods, but the payload and route decide which one makes sense.

Where NB-IoT has the advantage

NB-IoT is built for devices that sleep most of the time, wake up, send a small reading and return to sleep. 3GPP designed it for improved indoor coverage, large populations of low-throughput devices, low delay sensitivity, low device cost and low power consumption. It can run inside an LTE carrier, in the guard band or in dedicated spectrum.[2]

That profile fits applications such as:

meters and tank-level sensors;
environmental monitoring;
stationary cold-chain sensors;
returnable packaging that reports occasionally;
assets stored in basements, warehouses or other difficult radio locations.

Its narrow 180 kHz carrier and coverage-enhancement modes help when penetration matters more than speed. Power Saving Mode and extended discontinuous reception can keep the modem asleep for long periods, although real battery life still depends on signal quality, reporting frequency, retries, temperature, battery chemistry and operator settings.[1]

The trade-off is responsiveness. NB-IoT is intended for small payloads and delay-tolerant traffic. Classic Release 13 deployments do not provide the seamless handover expected by fast-moving trackers; later releases added mobility improvements, but support depends on the module and network. It is not the first choice for frequent position updates, large firmware downloads or an asset that continuously crosses cell boundaries.

Where LTE-M has the advantage

LTE-M, also called Cat-M1 in its first widely deployed form, keeps many LPWA benefits while behaving more like mobile LTE. It supports handover between cells, lower latency and higher throughput than NB-IoT. This is useful when the device is attached to a pallet, trailer, container, vehicle or piece of equipment that keeps moving.

LTE-M is a good fit for:

mobile asset and cargo tracking;
regular GNSS position and sensor updates;
alarms that need a faster response;
larger over-the-air firmware updates;
wearables and safety devices;
products that may need voice, where the operator has enabled VoLTE for LTE-M.

The GSMA describes LTE-M as an LPWA technology with low device complexity, low power use, extended coverage, low latency and support for high connection density.[1] It also supports PSM and eDRX, so a well-designed tracker can spend most of its life asleep and wake only when movement, a schedule or a sensor event requires a report.

LTE-M's weakness is not the radio specification. It is availability. Operators have deployed NB-IoT and LTE-M unevenly, and roaming support is not identical to ordinary smartphone LTE roaming. The GSMA's launch inventory shows substantial commercial deployment of both technologies, but a country appearing on a list does not prove that the required band, operator, roaming agreement or power-saving feature will work for a specific device.[5]

Where Cat 1 bis has the advantage

LTE Cat 1 bis takes a different route. It keeps Cat 1's data capability and standard LTE operation but removes the second receive chain and antenna. That reduces hardware complexity, board area and cost. The price is a coverage penalty compared with two-antenna Cat 1, particularly near the cell edge.[1][3]

Cat 1 bis can reach the Cat 1 class maximum of about 10 Mbps downlink and 5 Mbps uplink; commercial modules advertise those figures for supported networks.[4] That capacity changes what an IoT device can do:

transfer larger firmware images more quickly;
upload richer diagnostics or frequent telemetry;
support payment terminals and industrial gateways;
send audio or limited image data where the application requires it;
provide tracking and telematics across ordinary 4G LTE coverage.

It also supports mobility and standard LTE handover. Because it does not need the network to activate a separate NB-IoT or LTE-M radio feature, Cat 1 bis can be easier to deploy across regions where 4G LTE is present but LPWA coverage is incomplete.[1][3]

The compromise is power. New Cat 1 bis modules may support PSM and eDRX, but Cat 1 bis is not an LPWA category and network support for those modes is not uniform. Its faster transfer can reduce radio-on time for a large payload, yet a small sensor sending a few bytes may still get better energy economics from NB-IoT or LTE-M. The only reliable answer comes from measuring the complete duty cycle on the target networks.

The comparison in one view

NB-IoT

Primary strength: deep coverage and very low power for small, infrequent messages.
Mobility: best for stationary or slowly changing deployments; support for later-release mobility features varies.
Typical data: tiny, delay-tolerant telemetry.
Power profile: usually strongest for long sleep cycles and sparse reporting.
Voice: not supported.
Coverage dependency: requires an operator's NB-IoT deployment and compatible bands.
Best starting point: static sensors, metering, storage and hard-to-reach locations.

LTE-M

Primary strength: low-power mobility with moderate throughput and faster response.
Mobility: seamless handover between cells.
Typical data: regular telemetry, GNSS positions, alarms and manageable firmware updates.
Power profile: a strong balance of battery life and mobile operation.
Voice: possible when the operator supports VoLTE on LTE-M.
Coverage dependency: requires LTE-M deployment, compatible bands and suitable roaming agreements.
Best starting point: cargo and asset tracking that moves between cells.

LTE Cat 1 bis

Primary strength: higher throughput across ordinary LTE infrastructure.
Mobility: standard LTE mobility and handover.
Typical data: frequent telemetry, large firmware images, logs, audio or limited image data.
Power profile: sleep modes are possible, but active and network behaviour need closer power budgeting.
Voice: possible on some modules and operator profiles.
Coverage dependency: uses standard LTE, but bands, certification and roaming still need validation.
Best starting point: higher-data IoT or global products where LTE-M availability is insufficient.

These are design tendencies, not procurement guarantees. A module data sheet cannot tell you whether a roaming SIM will access a feature in a particular port, warehouse or border corridor.

What to test before choosing

A connectivity decision should begin with a route and workload model.

Map the real network footprint. Check every country, operator and LTE band in the planned deployment. Test roaming, not just home-network attachment. An operator may support a technology domestically but restrict access to roaming devices.

Model the complete energy budget. Include network search, registration, TLS setup, retransmissions, GNSS acquisition, sensor warm-up and firmware downloads. The lowest sleep current does not rescue a device that repeatedly searches for a missing network.

Use the real payload. Protocol headers and security handshakes may be larger than the sensor message. Compression, batching and event-driven reporting can change the best radio choice.

Plan firmware updates on day one. A product expected to remain deployed for years will need security and application updates. Estimate the worst-case image size, transfer time and energy cost before fixing the modem architecture.

Test cell edges and movement. Laboratory signal levels do not reproduce a metal container, a refrigerated trailer, a basement or a device moving between countries. Antenna placement and enclosure design can matter as much as the modem category.

What this means for cargo and asset tracking

A stationary temperature logger in a warehouse and a high-value shipment crossing five countries are both IoT devices, but they do not have the same connectivity problem.

NB-IoT can be the right choice when the asset remains within known coverage, messages are small and long battery life has priority. LTE-M is often the stronger fit when a tracker moves, reports position and condition regularly, and must keep sessions alive through cell changes. Cat 1 bis becomes attractive when the route has broad LTE but inconsistent LTE-M availability, or when the device needs larger updates and richer data.

Some products should support more than one radio mode. A multimode design can prefer LTE-M for mobility, use NB-IoT where available for sparse telemetry, or select Cat 1 bis for a separate high-throughput product family. That flexibility has a cost in hardware, certification, firmware and testing, so it should solve a real deployment problem rather than become a feature-list exercise.

At Sensefinity, connectivity is part of the Internet of Cargo, not the whole solution. The useful outcome is verified information about location, temperature, humidity, shock, opening events and custody, delivered with the right balance of coverage, energy and cost. Our NB-IoT trackers and cargo-monitoring work begin with that operational question: what must the customer know, where and how quickly?

The decision rule

Choose NB-IoT when the message is small, the device sleeps for long periods and coverage penetration matters more than mobility or speed.

Choose LTE-M when the asset moves and the application needs LPWA power consumption with handover, lower latency and enough throughput for regular tracking and updates.

Choose Cat 1 bis when higher data rates and the ordinary LTE footprint matter more than achieving the lowest possible power profile.

Then verify the choice on the target operators, bands, routes and enclosures. A technology comparison narrows the field. Field testing makes the decision.