--- title: 'LTE-M vs NB-IoT vs LTE Cat-1: How to Choose for Cellular IoT' description: LTE-M balances power and mobility, NB-IoT minimizes power for fixed sensors, and LTE Cat-1 offers the highest data rate. Here's how to choose between them — and where LTE Cat-1 bis now fits. source_url: https://dev.blues.io/blog/differences-ltem-nbiot-cat1-cellular-iot/ canonical_url: https://dev.blues.io/blog/differences-ltem-nbiot-cat1-cellular-iot/ markdown_url: https://dev.blues.io/blog/differences-ltem-nbiot-cat1-cellular-iot.md --- # LTE-M vs NB-IoT vs LTE Cat-1: How to Choose for Cellular IoT ![LTE-M vs NB-IoT vs LTE Cat-1: How to Choose for Cellular IoT banner](https://dev.blues.io/images/blog/posts/differences-ltem-nbiot-cat1-cellular-iot/banner.jpg?v=e7e4841d) February 20, 2024 ## LTE-M balances power and mobility, NB-IoT minimizes power for fixed sensors, and LTE Cat-1 offers the highest data rate. Here's how to choose between them — and where LTE Cat-1 bis now fits. - [Cellular](https://dev.blues.io/blog/tag/cellular) [![Rob Lauer](https://dev.blues.io/images/blog/authors/rob-lauer.jpg?v=57fb21a7)](https://dev.blues.io/blog/author/rob-lauer/) [Rob LauerSenior Director of Developer Relations](https://dev.blues.io/blog/author/rob-lauer/) *Cover image credit @tonystoddard on [Unsplash](https://unsplash.com/@tonystoddard).* I'd say IoT developers are *just a bit spoiled* today when it comes to adding wireless connectivity to their physical products. Whether it's cellular, WiFi, LoRa, BLE, Zigbee, and so on, options abound. Cellular in particular is becoming a go-to choice for many developers due to its low-power nature, high penetration, and global availability. The trick is, there is an array of cellular network protocols to choose from, so selecting the right one for your specific application can be daunting at first glance. This article looks into three key cellular technologies that provide value to the IoT: **LTE-M, NB-IoT, and LTE Cat-1**, and looks into their technical nuances and suitability for different wireless product scenarios. > **Note:** > > If you're looking for an easy way to get started with [Cellular IoT](https://dev.blues.io/cellular-iot/), look no further than the [Blues Notecard](https://blues.com/products/notecard/). The [Notecard Cellular](https://shop.blues.com/collections/notecard/products/notecard?utm_source=dev-blues\&utm_medium=web\&utm_campaign=store-link) comes in different flavors, some of which support LTE Cat-1 and others that support LTE-M and NB-IoT (with the ability to fall back to 2G if needed). > > The [Notecard Cell+WiFi](https://shop.blues.com/products/notecard-cell-wifi?utm_source=dev-blues\&utm_medium=web\&utm_campaign=store-link) also lets you start with WiFi and fallback to cellular! - [LTE-M (Long Term Evolution for Machines)](#lte-m-long-term-evolution-for-machines) - [NB-IoT (Narrowband IoT)](#nb-iot-narrowband-iot) - [LTE Cat-1](#lte-cat-1) - [Where LTE Cat-1 bis Fits](#where-lte-cat-1-bis-fits) - [Quick Comparative Analysis](#quick-comparative-analysis) ## LTE-M (Long Term Evolution for Machines) [LTE-M](https://en.wikipedia.org/wiki/LTE-M), part of the 3GPP's Release 13 specification and a name (Long Term Evolution for Machines) that evokes images of the Terminator for me(!), is an IoT-centric standard offering a balanced mix of power efficiency, coverage, and data rate. LTE-M coverage is mostly available in North and South America, as well as all of Europe. Coverage in other regions is scattershot, on a [country-by-country basis](https://www.gsma.com/iot/deployment-map/). ![lte-m and nb-iot coverage map](https://dev.blues.io/images/blog/posts/differences-ltem-nbiot-cat1-cellular-iot/lte-m-coverage.png?v=d191e03d) ### What You Need to Know about LTE-M - **Data Rate:** Supports up to 1 Mbps, striking a nice balance between speed and power consumption. - **Bandwidth:** Operates on a 1.4 MHz bandwidth, enabling efficient spectrum use. - **Mobility/Tower Handoff:** Offers high mobility support, suitable for applications involving moving devices, such as fleet management. - **Latency:** Typically has a latency of 10-15 ms, sufficient for most real-time applications. - **Power Efficiency:** It includes power-saving modes like PSM (Power Saving Mode) and eDRX (extended Discontinuous Reception), which are crucial for battery-operated devices. The "narrowband" Blues Notecards (e.g. [Notecard Cellular NB](https://shop.blues.com/products/notecard?variant=43930999030001\&utm-blues\&utm_medium=web\&utm_campaign=store-link) and [Notecard Cell+WiFi NB](https://shop.blues.com/products/notecard-cell-wifi-nb?utm_source=dev-blues\&utm_medium=web\&utm_campaign=store-link)) support LTE-M natively, and it's the default connectivity protocol the Notecard will attempt to use. The [Notecard API](https://dev.blues.io/api-reference/notecard-api.md) allows you to restrict the Notecard to LTE-M only with this command: ```json { "req": "card.wireless", "mode": "m" } ``` > **Note:** > > We recommend only using the request above when you know, for a fact, that a certain cellular protocol is only available in the region of deployment, and you don't want to wait for the Notecard to cycle through available options. Ideal use cases for LTE-M include [asset tracking](https://blues.com/use-cases/building-a-gps-asset-tracking-device/), [smart city applications](https://blues.com/use-cases/ml-for-smart-city-traffic-management/), and [healthcare monitoring](https://blues.com/customer-stories/evexia-telehealth-advances-medicine-in-the-caribbean/) where a moderate data rate and mobility are required. ## NB-IoT (Narrowband IoT) [NB-IoT](https://en.wikipedia.org/wiki/Narrowband_IoT), also a brainchild of 3GPP's Release 13, is tailored for applications requiring minimal bandwidth and power usage (even more so than LTE-M). Generally speaking, unless you need to use the least possible amount of power possible, use of LTE-M is generally favorable (if it's available). NB-IoT coverage is more widely available across the globe. Most carriers provide both LTE-M and NB-IoT access, but some countries (especially across parts of Asia and Africa) only support NB-IoT. Again, consult the [LTE-M/NB-IoT coverage map](https://www.gsma.com/iot/deployment-map/) provided by GSMA for high-level country availability: *This image is slightly misleading, as it shows countries that only support NB-IoT. Combine it with the LTE-M coverage map above (which includes countries that support BOTH LTE-M and NB-IoT) for a better perspective.* ![nb-iot only coverage map](https://dev.blues.io/images/blog/posts/differences-ltem-nbiot-cat1-cellular-iot/nbiot-coverage.png?v=283b3f5b) ### Key Characteristics of NB-IoT - **Data Rate:** Offers around 250 kbps, catering to low-data-rate applications. - **Bandwidth:** Uses a narrow bandwidth of 200 kHz, significantly reducing power consumption. - **Deployment:** Can be deployed in-band, guard-band, or standalone, offering flexibility in using existing network infrastructure. - **Penetration:** Excellent penetration capabilities make it ideal for underground or indoor applications. - **Power Efficiency:** Its ultra-low power consumption makes it suitable for devices requiring long battery life, often several years. Just like with LTE-M, the ["narrowband" Blues Notecards](https://shop.blues.com/products/notecard-cell-wifi-nb?utm_source=dev-blues\&utm_medium=web\&utm_campaign=store-link) support NB-IoT, but (by default) the Notecard will only use NB-IoT after attempting to connect with LTE-M. If you are building an application around NB-IoT, you can easily restrict the Notecard to NB-IoT with this command: ```json { "req": "card.wireless", "mode": "nb" } ``` > **Note:** > > Again, this command is generally only useful when you know NB-IoT is available and you want to reduce the amount of time the Notecard spends searching for available cellular networks. > **Warning:** > > **Check NB-IoT support with your carriers before committing to it.** Carrier support has become uneven — some operators have begun retiring their NB-IoT networks while others continue to invest in them, so availability increasingly depends on your specific carrier and deployment region. For a new design, LTE-M or [LTE Cat-1 bis](#where-lte-cat-1-bis-fits) generally carry less long-term risk. Ideal use cases for NB-IoT include [smart metering](https://dev.blues.io/example-apps/accelerators/commercial-tenant-sub-metering-bridge/), [agricultural sensors](https://blues.com/customer-stories/wireless-iot-agricultural-monitor-device-infopatterns/), [smart parking](https://dev.blues.io/example-apps/accelerators/), and [environmental monitoring](https://blues.com/use-cases/iot-in-water-management/) where minimal data transfer and deep penetration are needed. ## LTE Cat-1 LTE Cat-1, part of the earlier 3GPP Release 8, is often considered a bridge between high-speed LTE categories and low-power IoT standards. It is better supported globally, offers higher bandwidth, and faster connection speeds. LTE Cat-1 is the default protocol used on all the "wideband" Notecards (e.g. [Notecard Cellular](https://shop.blues.com/products/notecard?utm_source=dev-blues\&utm_medium=web\&utm_campaign=store-link) and [Notecard Cell+WiFi](https://shop.blues.com/products/notecard-cell-wifi?utm_source=dev-blues\&utm_medium=web\&utm_campaign=store-link)). ### Important Notes on LTE Cat-1 - **Data Rate:** Supports up to 10 Mbps, which is higher than both LTE-M and NB-IoT, catering to applications requiring substantial data transfer. - **Bandwidth:** Utilizes a wider bandwidth (up to 20 MHz), which aligns with traditional LTE networks. - **Mobility/Tower Handoff:** Provides full mobility support, suitable for applications involving motion, such as vehicle tracking. - **Voice Support:** Unlike LTE-M and NB-IoT, it supports voice communication, expanding its use case scenarios. - **Power Consumption:** Higher compared to LTE-M and NB-IoT, but still lower than traditional LTE standards. Use of LTE Cat-1 is the recommended path for building most IoT solutions with the Blues Notecard (which is why we include a wideband Notecard in the [Blues Starter Kit](https://shop.blues.com/products/blues-global-starter-kit?utm_source=dev-blues\&utm_medium=web\&utm_campaign=store-link)!). Ideal use cases for LTE Cat-1 includes low latency monitoring, [telehealth applications](https://blues.com/customer-stories/wireless-iot-remote-patient-monitoring/), and any other scenario requiring high data rates and potentially voice support. ## Where LTE Cat-1 bis Fits Since this article was first published, a fourth option has become the practical default for many new designs: **LTE Cat-1 bis**. It's a cost-optimized variant of LTE Cat-1 that uses a **single antenna instead of two**, which simplifies RF design, reduces bill-of-materials cost, and lowers power consumption — without giving up Cat-1's coverage or performance. ### Important Notes on LTE Cat-1 bis - **Data Rate:** Up to 10 Mbps downlink and around 5 Mbps uplink, matching Cat-1 for practical purposes. - **Antenna Design:** A single antenna, which is the main reason it's cheaper and simpler to build around than standard Cat-1. - **Coverage:** Runs on existing LTE networks, so anywhere you have LTE access you already have Cat-1 bis access — no separate rollout to wait for. - **Availability:** More widely supported today than either NB-IoT or LTE-M, both of which still vary by region. For most new cellular IoT projects, Cat-1 bis is the sensible starting point unless you have a specific reason to choose otherwise — such as confirmed LTE-M coverage across your deployment regions, or a power budget that genuinely requires NB-IoT. > For a deeper look at Cat-1 bis and how it compares to 5G RedCap, see [Bridging the Gap: LTE Cat-1 bis and the Future of 5G](https://dev.blues.io/blog/bridging-the-gap-lte-cat-1-bis-future-5g.md). ## Quick Comparative Analysis When choosing between these protocols, several factors can come into play, depending on your product requirements. The table below summarizes the per-protocol specifications covered above. | Spec | LTE-M | NB-IoT | LTE Cat-1 | LTE Cat-1 bis | | ---------------------- | ------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------- | ---------------------------------------------------------------- | | Max data rate | Up to 1 Mbps | \~250 kbps | Up to 10 Mbps | Up to 10 Mbps down / \~5 Mbps up | | Bandwidth | 1.4 MHz | 200 kHz | Up to 20 MHz | Up to 20 MHz | | Latency | 10-15 ms | Higher | Lowest | Lowest | | Power consumption | Low | Lowest | Higher (still below traditional LTE) | Lower than Cat-1 | | Mobility/tower handoff | Yes (high) | No | Yes (full) | Yes (full) | | Voice support | No | No | Yes | Yes | | Antennas required | 1 | 1 | 2 | 1 | | Best use case | Asset tracking, smart city, healthcare monitoring | Smart metering, agricultural sensors, environmental monitoring | High data rate, low-latency monitoring, telehealth, voice | Most new designs — Cat-1 capability at lower cost and simpler RF | Below are some questions with the appropriate protocols ranked in terms of their effectiveness: **Is access to a (relatively) high data rate and bandwidth important?** - 🥇 LTE Cat-1 - 🥈 LTE-M - 🥉 NB-IoT **Is it critical to use the least amount of power as possible?** - 🥇 NB-IoT - 🥈 LTE-M - 🥉 LTE Cat-1 **Is your device going to be in motion (i.e. do you require tower handoff)?** - 🥇 LTE Cat-1 and LTE-M - 🥈 NB-IoT (doesn't support tower handoff) **Is low-latency a critical requirement?** - 🥇 LTE Cat-1 and LTE Cat-1 bis - 🥈 LTE-M - 🥉 NB-IoT **Do you want the simplest, lowest-cost path for a brand-new design?** - 🥇 LTE Cat-1 bis (single antenna, runs anywhere LTE does) - 🥈 LTE Cat-1 - 🥉 LTE-M (only where you've confirmed coverage) ## Conclusion The choice **depends on the specific requirements of your product**. LTE-M strikes a nice balance between power efficiency, data rate, and mobility. Tailored for applications requiring minimal bandwidth and power usage, NB-IoT fits the bill — though it's worth confirming your carriers still support it. LTE Cat-1 fills the gap for high-data-rate applications, and **LTE Cat-1 bis now delivers that same capability with a single antenna, lower cost, and lower power**, which makes it the practical default for most new builds. As a firmware developer or electrical engineer, understanding these nuances is crucial in designing and deploying effective IoT solutions. If you're looking for a product that handles the guesswork for you, take a look at the Notecard and get started today with a [Blues Starter Kit](https://shop.blues.com/products/blues-global-starter-kit?utm_source=dev-blues\&utm_medium=web\&utm_campaign=store-link) 💙.