LTE-M, NB-IoT, or Cat-1 bis: How to Choose for Global Rollouts

Many global IoT projects reduce cellular module selection to a simple price question: should the device use LTE-M, NB-IoT, or Cat-1 bis? That shortcut misses the constraints that actually decide whether a rollout works: whether the device moves, whether it needs regular FOTA, whether it crosses borders, whether it is installed underground or indoors, whether the target operator has certified the module, and whether the local network enables the low-power features you expect.

The practical conclusion is: NB-IoT fits static, low-frequency, small-payload devices that need deep coverage; LTE-M fits mobile or semi-mobile devices that need low power plus moderate data; Cat-1 bis fits devices that need higher throughput, broader LTE availability, and easier multi-region execution, but it is usually not the lowest-power option. For a multi-country rollout, do not start with the technology that looks best on paper. Start with target countries, operator support, certified modules, roaming strategy, and FOTA requirements.

Decision block

Choose NB-IoT first when the device is static, sends small payloads, and sits in deep indoor or underground locations. Choose LTE-M first when the device moves, needs handover, sends richer state, or requires periodic FOTA. Choose Cat-1 bis first when the device needs higher throughput, lower latency, VoLTE-like use cases, broader LTE coverage, or a more mature multi-region supply chain.

1. Put the three technologies in the right layer

LTE-M and NB-IoT are 3GPP cellular LPWA technologies designed for IoT devices that need low power, wide-area coverage, and relatively small data payloads. GSMA treats LTE-M and NB-IoT as part of the Mobile IoT ecosystem and maintains deployment resources that help teams check commercial network availability. Cat-1 bis is closer to a simplified LTE Cat 1 option: it uses one receive antenna to reduce hardware complexity while keeping higher data rates and broader LTE-network reach than LPWA.

That means the choice is not between three interchangeable technologies. It is a choice between three engineering priorities:

The real question is not which standard is newer. It is whether the device can stay operational under the actual country, operator, RF environment, and lifecycle constraints of the rollout.

2. Evaluate six constraints, not just the network name

2.1 Coverage: maps only answer the first layer

Before choosing a module, check the GSMA Mobile IoT Deployment Map, operator IoT coverage statements, and the regional certification table from the module vendor. A coverage map can tell you whether LTE-M or NB-IoT is commercially deployed, but it does not prove that your device will work inside a basement, metal cabinet, cold room, vehicle route, or cross-border logistics path.

If the device is installed underground, behind heavy infrastructure, or inside a deep indoor utility space, NB-IoT coverage may be valuable. If the device moves, LTE-M or Cat-1 bis handover, cell reselection, registration behavior, and location performance become more important. For global asset tracking, roaming availability and registration power can matter more than deep coverage at one fixed point.

2.2 Power: lowest power is not one module number

PSM and eDRX can reduce cellular standby power, but they must be supported by the module, firmware, SIM configuration, and operator network. NB-IoT and LTE-M are commonly used for multi-year battery devices. New Cat-1 bis platforms also support low-power modes, but not every Cat-1 network enables them in a way that matches your device plan.

Use business-cycle power, not sleep current, as the decision metric. One reporting cycle includes wake-up, network search, attach or resume, uplink, possible downlink, release, and sleep. If a device keeps searching or re-registering because coverage or roaming is unstable, the theoretical sleep current will not save the battery budget.

2.3 Data volume and FOTA: hundreds of bytes and hundreds of KB are different products

NB-IoT is strong for infrequent small packets. It is not a comfortable path for firmware, model configuration, diagnostic logs, or cached event uploads. LTE-M gives more margin for moderate data. Cat-1 bis is usually safer when the device needs higher throughput, lower latency, or faster FOTA windows.

If the device only sends temperature, voltage, door state, or a meter reading, low data rate is acceptable. If the device sends location history, alarm context, log fragments, configuration packages, or delta firmware, LTE-M or Cat-1 bis will usually reduce lifecycle friction.

2.4 Mobility: fixed devices and moving assets are different systems

NB-IoT is more natural for static or low-mobility devices. LTE-M is a better fit for mobile use cases such as logistics, people safety, portable medical devices, or moving industrial assets. Cat-1 bis also inherits LTE mobility and handover behavior, making it more suitable where continuous connectivity, lower latency, or vehicle movement matters.

If a device wakes once a day in one location, mobility is not the priority. If it crosses cities, operators, or countries, network reselection, roaming agreements, SIM strategy, location behavior, and search power become primary constraints.

2.5 Certification and supply chain: buying a module is not the same as shipping at scale

For overseas deployment, check three lists: supported frequency bands, operator certification for the specific module, and SIM/eSIM service support for each target country. Cat-1 bis benefits from the LTE ecosystem and a fast-growing module supply chain. Even so, some regions may still apply operator certification limits, VoLTE restrictions, or use-case constraints.

For devices expected to run for years, supply chain is not just unit price. You need replacement modules, firmware maintenance, certification updates, antenna design margin, eSIM remote provisioning, and a plan for network sunset or spectrum refarming.

2.6 Global rollout: choose connectivity together with lifecycle management

For a multi-country rollout, the radio access technology must be selected together with SIM/eSIM, remote provisioning, operator switching, and device lifecycle management. GSMA SGP.32 is an important direction for IoT eSIM remote provisioning, especially for large unattended fleets. But a standard being available does not mean every country, operator, module, and eSIM platform combination is commercially ready for your product.

The real architecture question is: how does the device activate, switch profiles, recover from bad configuration, come back after long offline periods, and prove that a regional network combination was validated before mass production?

3. A practical selection flow

flowchart TD
  A([Define device operating conditions]) --> B{Will the device move or roam across regions?}
  B -- Yes --> C{Does it need higher data rate, FOTA, or low latency?}
  B -- No --> D{Deep indoor / underground / small infrequent payloads?}
  C -- Yes --> E([Evaluate Cat-1 bis first])
  C -- No --> F([Evaluate LTE-M first])
  D -- Yes --> G([Evaluate NB-IoT first])
  D -- No --> H{Is LTE-M covered and certified in target markets?}
  H -- Yes --> F
  H -- No --> E
  E --> I([Check operator certification, bands, SIM/eSIM, and measured power])
  F --> I
  G --> I
  I --> J([Run field pilots before locking BOM])

  classDef start fill:#eef7ff,stroke:#2f80ed,stroke-width:1px,color:#18324a,rx:10,ry:10;
  classDef decision fill:#fff7e6,stroke:#f2994a,stroke-width:1px,color:#4a2a00,rx:10,ry:10;
  classDef action fill:#eefaf2,stroke:#27ae60,stroke-width:1px,color:#12351f,rx:10,ry:10;
  classDef final fill:#f4f0ff,stroke:#7b61ff,stroke-width:1px,color:#2d235f,rx:10,ry:10;
  class A start;
  class B,C,D,H decision;
  class E,F,G,I action;
  class J final;

This flow deliberately places country coverage and operator certification before BOM lock. If target markets do not have reliable LTE-M coverage, LTE-M's theoretical advantages do not help. If NB-IoT coverage is strong but the device moves or needs frequent FOTA, lifecycle cost will rise. If Cat-1 bis is affordable but certification is restricted in the target region, production timing can still fail.

4. Typical choices by scenario

This table is not a substitute for field testing. It helps teams remove obviously poor options and focus validation budget on the combinations most likely to survive production.

5. Common mistakes

5.1 "NB-IoT is lowest power, so every battery device should use it"

That is only true when the device is static, sends small infrequent payloads, has stable coverage, and can use the network's low-power features. Moving devices, frequently reporting devices, and devices that need FOTA may spend more energy searching, retrying, staying online, or waiting for upgrades.

5.2 "Cat-1 bis uses LTE, so it is always the safest option"

Cat-1 bis has real strengths in LTE reach and data rate, but its single receive chain can reduce receive sensitivity compared with traditional Cat 1, and deep-coverage scenarios may still favor LPWA. Operator certification and feature restrictions also vary by region.

5.3 "LTE-M is just the middle ground between NB-IoT and Cat-1 bis"

LTE-M is not merely a compromise. It is a better fit when mobility, moderate data, and low-power operation need to coexist. For asset tracking, alarms, medical wearables, and sensors that need OTA, LTE-M may be the more natural choice. But if LTE-M is not deployed or certified in the target market, it cannot be forced into the product.

5.4 "Global bands mean global deployment"

A module data sheet can prove that a device might work. It cannot prove that the fleet can be operated. Global execution also depends on operator networks, certification, roaming, SIM/eSIM profiles, antenna design, power behavior, and support workflows.

6. Minimum validation checklist before production

Before locking the cellular technology and module, complete at least these checks:

• Target-country and target-city LTE-M / NB-IoT / LTE coverage review.
• Operator certification for the exact module, bands, VoLTE behavior, PSM / eDRX, and Cat-1 bis restrictions.
• Real installation testing for RSSI, RSRP, RSRQ, SINR, registration time, and attach failure rate.
• Full-device power testing across the business reporting cycle, not only module sleep current.
• FOTA or configuration-package download time, failure recovery, and data cost.
• SIM/eSIM profile switching, offline recovery, and remote suspend / resume flows.
• Cross-border or multi-operator testing for network search, roaming, and re-registration power.

If these checks are missing, do not let BOM price become the final decision. The cost of truck rolls, replacements, support cases, and customer downtime after connectivity failure is usually much higher than the module price difference.

7. Conclusion

Choosing between LTE-M, NB-IoT, and Cat-1 bis is a tradeoff across coverage, power, mobility, data rate, FOTA, certification, and global operations. NB-IoT is strongest for static, small-payload, deep-coverage devices. LTE-M is strongest when mobility and low power need to coexist. Cat-1 bis is strongest when higher throughput, broad LTE availability, and multi-region execution matter more than the absolute lowest power.

For global IoT rollouts, the safest sequence is: define the device operating conditions, verify network and certification by country and operator, run a small field pilot, and only then lock the module and SIM/eSIM strategy. Do not buy the cheapest module first and let the entire product lifecycle absorb the cost of a wrong connectivity decision.

References

• GSMA Mobile IoT Deployment Map
• GSMA eSIM Consumer and IoT Specifications
• u-blox LTE-M Technology Overview
• u-blox Narrowband IoT Overview
• u-blox LTE Cat 1 and Cat 1bis Overview
• Qualcomm Understanding the Benefits of LTE Cat 1bis Technology