What is Cellular IoT? A Guide to Modules and Connectivity

Key Takeaways
- Cellular IoT uses cellular networks (LTE today, 5G increasingly) to connect IoT devices, optimized for power efficiency over high throughput.
- Four cellular IoT protocols dominate: LTE Cat-1 (up to 10 Mbps), LTE Cat-1 bis (cost-optimized), LTE-M (battery-friendly with mobility), and NB-IoT (lowest power, deepest coverage).
- Connectivity takes more than a radio. A device also needs a SIM (removable, embedded, or eSIM), a data plan, and certification for the networks and countries it ships to.
- A cellular IoT module is a certified modem you drive with AT commands. A system-on-module like Blues Notecard adds the processor, SIM, data plan, security, and cloud service.
- Blues Notecard Cellular is a 30×35 mm system-on-module that idles at ~8–18 µA @ 5V, ships with 500 MB of prepaid data and 10 years of service, and exposes a JSON API instead of AT commands. In our measurements, a Cat-1 bis Notecard used 0.263–0.320 mAh to create and sync one Note.
- The Notecard API is radio-agnostic — the same JSON interface works for Cellular, Satellite, LoRa, and WiFi Notecards, so firmware stays portable across deployments.
What is Cellular IoT?
Cellular IoT is the use of carrier cellular networks to connect machines, rather than phones, to the internet. A cellular IoT device pairs a radio module with a SIM that identifies it to a carrier and a data plan that pays for its traffic. Most of these devices spend nearly all of their lives asleep, waking to send a few hundred bytes of sensor data before powering the radio back down. Today that traffic runs over four LTE technologies built or tuned for devices: LTE Cat-1, LTE Cat-1 bis, LTE-M, and NB-IoT.
Compared with WiFi, LoRaWAN, or Bluetooth, the big draw is infrastructure you don't have to build. A cellular device can report from a field, a truck, or a basement in another country without a local gateway or anyone's WiFi password. The tradeoffs are a data plan, certification, and a radio that draws in the ~250 mA range while it's active, which is why the choice of module and the power design matter so much.
In this guide, we'll cover how cellular IoT connectivity works (SIMs, data plans, and certification), what separates a cellular modem from a module from a complete system-on-module, and how Blues approaches the problem with Blues Notecard and its companion cloud service Blues Notehub.

The Rise of Cellular IoT
In the early days of IoT, devices often relied on short-range communication technologies like Bluetooth, Zigbee, WiFi, or LoRa and LoRaWAN. While effective in localized environments, these solutions quickly revealed their limitations when projects scaled geographically or required mobility. As cellular technology matured, developers started experimenting with traditional 2G and 3G networks to connect devices. However, these networks weren't built for IoT use cases and required complex, power-hungry hardware stacks, making them unfeasible for many use cases.
With the global phase-out of 2G and 3G and the rise of 4G LTE, the cellular industry responded by defining new LTE categories optimized for IoT: LTE Cat-1 bis, LTE-M, and NB-IoT. These protocols brought lower power usage, reduced bandwidth needs, and simplified modules, all while leveraging the existing infrastructure of cellular towers. Today, cellular IoT stands at the forefront of global IoT deployments, bridging the gap between isolated sensors and the cloud, no matter the geography.
According to IoT Analytics, the number of licensed cellular IoT connections surpassed 4 billion in 2024, and that number is expected to double in the next five years. Applications range from agriculture and smart cities to transportation and logistics, driven by the global availability, mobility, and security inherent in cellular networks.
The Basics of Cellular IoT
Cellular IoT refers to the use of cellular networks, such as LTE today and 5G tomorrow, for connecting IoT devices to the wider Internet. Unlike traditional mobile devices, IoT endpoints often prioritize characteristics like power efficiency, long-range connectivity, and low bandwidth, rather than high data throughput. These endpoints are often embedded systems that perform specific tasks: monitoring sensor data, reporting equipment status, tracking assets, or automating industrial processes.
To meet the needs of IoT use cases, specialized cellular protocols have emerged within the LTE family as previously mentioned:
-
LTE Cat-1: A reasonably high-bandwidth (or "wideband") option offering reliable coverage and high data rates (up to 10 Mbps downlink), suitable for many general-purpose IoT use cases.
-
LTE Cat-1 bis: A cost-optimized (or "midband") version of LTE Cat-1 that uses a single antenna, simplifying RF design and reducing BOM cost. Cat-1 bis is ideal for small-form-factor devices.
-
LTE-M (a.k.a. LTE Cat-M1): A low-power wide-area network (LPWAN or "narrowband") technology with deep coverage, low power consumption, and mobility support. Excellent for battery-powered applications and global roaming.
-
NB-IoT: Ultra-low power, low bandwidth, and deep indoor coverage (like LTE-M considered "narrowband"). Perfect for simple sensors that transmit small packets infrequently, but falling out of favor with some carriers.
Let's break these down a bit further in terms of high-level use cases:
LTE Cat-1 is best for use cases needing moderate data throughput, such as smart video doorbells or real-time POS terminals. LTE Cat-1 bis serves similar functions but at lower cost and with simpler antenna design, making it a favorite for compact and cost-sensitive products like GPS trackers. LTE-M shines in applications requiring long battery life and mobility, like asset tracking or wearable health monitors. NB-IoT is ideal for fixed-location sensors that only need to transmit tiny bursts of data every few hours, like utility meters or parking space sensors.
For a decision table, measured power per sync, and which carriers run each network, see how to choose between LTE-M and NB-IoT.
Cellular IoT Technologies at a Glance
The table below puts the four side by side. The last column is what one Notecard of each type measured to create and sync a single Note on our test bench (Notecard firmware v11.4.1, 4.2V supply, measured with Blues Mojo and including the Notecarrier A it was mounted on).
| Technology | Peak data rate | Channel bandwidth | Tower handoff | Antennas | Measured charge per sync |
|---|---|---|---|---|---|
| LTE Cat-1 | Up to 10 Mbps | Up to 20 MHz | Yes | 2 | 0.723–0.967 mAh |
| LTE Cat-1 bis | Up to 10 Mbps down / ~5 Mbps up | Up to 20 MHz | Yes | 1 | 0.263–0.320 mAh |
| LTE-M | Up to ~1 Mbps | 1.4 MHz | Yes | 1 | 0.516 mAh |
| NB-IoT | ~127 kbps down / ~159 kbps up | 200 kHz | No | 1 | Not measured |
The per-sync ranges cover three Cat-1 Notecards and four Cat-1 bis Notecards. The LTE-M figure comes from a single model, Notecard for Skylo (NOTE-NBGLWX), which also carries WiFi and a satellite radio, so it isn't a pure LTE-M part.
Which Cellular Technology is Best for Battery-Powered Devices?
The usual answer is LTE-M or NB-IoT, because both were designed for low power and both support the network sleep features covered in the next section. That answer holds for a device that must accept commands within a bounded delay (eDRX keeps it reachable at low power), or one deep indoors where NB-IoT's extra coverage is the only way to get a signal.
For a sensor that wakes a few times a day to report, though, battery life comes down to two numbers: the charge each sync costs and the current the device draws while it sleeps. Measure those rather than trusting the label on the modem. On our bench, the Cat-1 bis Notecards used about half to two-thirds of the charge per sync of the LTE-M one and less than half that of the Cat-1 ones, while every Notecard we measured idled at roughly 27–35 µA (including the Notecarrier). To turn numbers like these into an estimate for your own device, use the calculator in How to Estimate Battery Life for a Cellular IoT Device.
Cellular IoT Connectivity: SIMs, Data Plans, and Certification
Getting a device onto a cellular network takes more than a radio. Before a single byte reaches your cloud, four things have to line up: a SIM the network trusts, a data plan with a carrier that serves the region, a radio certified for that network, and firmware that manages the connection without draining the battery.
SIM Cards, Embedded SIMs, and eSIM
Every cellular device needs a SIM to identify itself to a carrier, but the SIM doesn't have to be a card you can pull out:
- Removable SIM: a nano-SIM in a socket. It's easy to swap, but the socket adds height and a mechanical contact that can be a weak point under vibration.
- Embedded SIM (MFF2): the same SIM function in a chip soldered to the board, so it can't be removed or shaken loose.
- eSIM (eUICC): describes what the SIM can do rather than its shape. It can hold carrier profiles that are changed remotely, so a device can switch carriers without a technician visiting it.
- iSIM: the SIM function built into the modem chipset itself.
Notecard Cellular uses an embedded MFF2 SIM that isn't user-removable. For a region outside its coverage, or for network redundancy, most Notecarriers include a Nano-SIM socket, and Notecard can fail over to that external SIM and back again on a schedule you set.
Data Plans and Carriers
There are three common ways to pay for a device's data. You can contract with a carrier directly, which gets the best rates at volume but means a negotiation (and usually a different contract) for each region. You can buy SIMs from an IoT connectivity provider whose SIMs roam onto several carriers' networks. Or you can buy hardware with the data already bundled.
Notecard takes the third route. Each Notecard Cellular has a 10-year data plan with 500 MB of cellular data embedded, with more available for applications that need it, and nothing to activate. There are no "know your customer" restrictions, so you can embed it in a product without knowing who the end customer will be. Each Notecard's datasheet lists the countries it covers (the North American models, for example, cover the United States, Canada, and Mexico), though coverage can change over time because of local technical and regulatory restrictions.
Roaming
Most IoT SIMs that work in more than one country do it by roaming. The SIM belongs to one home operator, and the device connects through a local carrier under a roaming agreement between the two. It's the simplest way for a connectivity provider to offer wide coverage, and the device can't tell the difference.
Roaming has two catches for IoT devices. First, LTE-M and NB-IoT roaming need their own agreements between operators, so a SIM that roams onto a carrier's LTE network may not reach its LTE-M or NB-IoT network (see which carriers run LTE-M and NB-IoT). The visited network also sets the PSM and eDRX timers, so a device's power behavior can change from one country to the next (GSMA).
Second, roaming was designed for travelers, not for devices that stay abroad for years. Regulators in Brazil, China, India, and Turkey, among others, have prohibited permanent roaming, and in the US, Canada, and Australia the operators decide whether to allow it (Transforma Insights). The usual fixes are a local SIM or an eSIM that can switch to a local profile.
Check a module's coverage list before you ship to a new country. The datasheets for Notecard's global models, for example, list the countries their embedded SIM doesn't cover, including Brazil, China, India, and Turkey. In those countries, use a local SIM in the Notecarrier's Nano-SIM socket.
Certification
A cellular product has to pass more than the usual radio emissions tests. Regulators such as the FCC in the US, ISED in Canada, and the EU's Radio Equipment Directive (CE RED) cover the radio itself. Industry certification, PTCRB in North America and GCF in much of the rest of the world, confirms that the device behaves correctly on cellular networks. Some carriers then add a certification of their own.
A pre-certified module carries a large share of that work. Each Notecard Cellular datasheet lists the certifications that apply to its regions; NOTE-MBGLN, for example, lists FCC, ISED, CE RED, and PTCRB. Depending on your market and carrier, your finished product may still need some testing of its own, so talk to your test lab early.
Power-Saving Features: PSM and eDRX
LTE-M and NB-IoT networks can offer two standard power-saving features, and they differ in whether the network can reach the device. Power Saving Mode (PSM) lets a device stay registered with the network while its radio sleeps for hours or even days, so it can wake and send without reconnecting from scratch. While it's in PSM, though, the device doesn't listen for paging at all, so nothing sent to it arrives until it wakes on its own schedule. Extended Discontinuous Reception (eDRX) instead stretches the interval at which a device listens for incoming messages, from a couple of seconds to minutes or even hours. The device is still unreachable while it sleeps, but each listening window caps how long a message waits.
That makes the choice a question about downlinks. PSM suits a device that only reports, and eDRX suits one that has to accept commands within a known delay. Both depend on the network supporting them, and the network has the final say on the timers.
Notecard takes a simpler route in its low-power modes. It powers the modem on
for a sync and off again afterward, so between syncs the cost is Notecard's own
idle current rather than a modem that is registered but sleeping. Like PSM,
that means inbound data waits for the next sync, whose cadence you set with
hub.set. That's
why the measured charge per sync in the table above is the figure to compare.
2G and 3G Shutdowns
If you're replacing older hardware, check which network generation it uses. Carriers in many countries have shut down their 2G and 3G networks, taking devices that relied on them offline. The LTE technologies above are the current path for new designs, and LTE-M and NB-IoT carry forward into 5G standards. For more on where Cat-1 bis fits, see Bridging the Gap: LTE Cat-1 bis and the Future of 5G IoT.
Cellular IoT Modules, Modems, and Devices
Ask five engineers what a "cellular IoT module" is and you'll get three different parts. The term covers everything from a bare modem in a solderable package to a complete device with a SIM, a data plan, and a cloud service. The difference is how much of the connectivity stack you build yourself.
| Layer | What it is | Examples | What you still build |
|---|---|---|---|
| Cellular module | A modem chipset, RF front end, and firmware on a certified, solderable package, controlled with AT commands | Quectel BG95, EG915Q, and EG916Q; Telit LE910C1 (the modems inside Notecard) | SIM and data plan, AT-command driver, connection and retry logic, TLS, cloud backend, OTA updates, end-product certification |
| System-in-package (SiP) | A cellular module with an application processor alongside, so your firmware runs on the same part | Nordic nRF9151 | Connectivity plan, cloud backend, OTA pipeline, firmware built on the vendor's SDK |
| System-on-module (SoM) | Modem, processor, SIM, data plan, security, and a cloud service designed in together | Blues Notecard | Host firmware that sends JSON requests, plus a route from Notehub to your cloud |
| Development board or kit | A module or SoM on a carrier board with power, antennas, and headers for prototyping | Blues Notecarrier and Starter Kits | Your production board, once you leave the prototype |
Starting at the module layer gives you the most control and the lowest per-unit hardware cost, and it makes sense if you have RF and modem-firmware experience and enough volume to justify the certification and integration work. Starting at the system-on-module layer trades some of that control for time. We compared the two approaches in code, step by step, in Notecard vs DIY Arduino.
Choosing a Notecard Cellular
Notecard Cellular comes in several models that differ by cellular technology, region, and whether WiFi is on board. The measured charge per sync comes from the same bench tests described above.
| Notecard | Technology | Region | Modem | WiFi | Charge per sync |
|---|---|---|---|---|---|
| NOTE-MBGLN | LTE Cat-1 bis | Global | Quectel EG916Q-GL | No | 0.263 mAh |
| NOTE-MBNAN | LTE Cat-1 bis | North America | Quectel EG915Q-NA | No | 0.271 mAh |
| NOTE-MBNAW | LTE Cat-1 bis | North America | Quectel EG915Q-NA | Yes | 0.303 mAh |
| NOTE-MBGLW | LTE Cat-1 bis | Global | Quectel EG916Q-GL | Yes | 0.320 mAh |
| NOTE-NBGLWX | LTE-M, NB-IoT, GPRS, and Skylo satellite | Global | Quectel BG95-S5 | Yes | 0.516 mAh (LTE-M) |
| NOTE-WBGLWT | LTE Cat-1 | Global | Telit LE910C1-WWXD | Yes | 0.723 mAh |
| NOTE-WBNAN | LTE Cat-1 | North America | Quectel EG91-NAXD | No | 0.893 mAh |
| NOTE-WBNAW | LTE Cat-1 | North America | Quectel EG91-NAXD | Yes | 0.967 mAh |
The EMEA models (NOTE-WBEXN, NOTE-WBEXW, and NOTE-WBEXWT) and NOTE-WBNAWT weren't part of this round of measurements. The Notecard product family page lists every model's cellular bands.
For most new designs, start with a Cat-1 bis Notecard. It measured the lowest charge per sync of any Notecard and runs on the same LTE networks as Cat-1. Choose Notecard for Skylo when you need LTE-M or NB-IoT specifically, or want satellite fallback in the same module. The Cat-1 Notecards cost more per sync; pick one when your region or carrier calls for Cat-1, or when you need the EMEA and global models' fallback to 2G and 3G networks where those still run. You can order any of them from the Blues store.
Deployment Challenges with Traditional Cellular IoT
Before Blues hit the market in 2019, developers faced a daunting list of challenges when launching a cellular IoT device:
- Navigating cellular carrier negotiations and provisioning SIM cards across different regions.
- Managing billing, roaming fees, and opaque pricing models.
- Handling carrier certifications, RF tuning, and antenna design.
- Wrestling with AT command sets and modem firmware.
- Building secure OTA update pipelines and cloud connectivity layers.
- Designing ultra-low power sleep/wake cycles from scratch.
Worse yet, every component of this system often came from a different vendor. The modem, antenna, SIM, carrier, TLS stack, and backend cloud infrastructure... each introduced risk, complexity, and integration overhead. The cost of mistakes was high, and the time to deploy often stretched into months or years.
Blues: Cellular IoT, Simplified
Blues is legitimately redefining cellular IoT by eliminating complexity and providing a developer-first experience. The centerpiece of this approach is Blues Notecard Cellular: a tiny, fully integrated system-on-module that handles all aspects of cellular connectivity. It measures just 30x35mm but includes a cellular modem, embedded SIM, antenna interfaces, embedded secure element, GPS, and accelerometer. Think of it as a cellular IoT module or an LTE-M dev kit (but with the option to use other cellular protocols as well).
What makes Notecard Cellular revolutionary isn't just the hardware, it's the design philosophy. Every unit ships prepaid with 500MB of data and 10 years of cellular service, with no connection fees or SIM activation costs. Developers can go from concept to prototype without ever dealing with a mobile carrier.
Different Notecard Cellular variants support LTE Cat-1, Cat-1 bis, LTE-M, and NB-IoT, allowing you to choose the ideal cellular protocol for your product. Whether you need high bandwidth for high-res images or ultra-low power for remote sensors, there's a Notecard to match.
Because every Notecard is pre-certified and includes embedded cryptographic keys, you avoid the pain of carrier certification, SIM provisioning, or secure key exchange. And thanks to Notecard's store-and-forward architecture, devices can queue data for transmission when connectivity is available, ensuring reliability even in low-signal or offline environments.
But what's it like to develop a product around Notecard?
JSON-Based Development with Cross-RAT APIs
One of the most frustrating aspects of cellular modem programming is dealing with AT command sets. With Blues, that's gone. All interaction with Notecard happens via a developer-friendly JSON API. You send and receive JSON messages over UART, USB, or I2C with no modem programming or proprietary protocols to learn.
Each data packet you create is referred to as a Note, and Notes are organized into logical groupings called Notefiles. These Notefiles are then synced with Notehub, Blues' secure cloud service that routes your data to any cloud endpoint.
For example, you may need to sync your device's sensor data with the cloud like so:
{
"req": "note.add",
"file": "sensor.qo",
"body": { "temp":35.5, "humid":56.23 },
"sync": true
}This JSON interface remains consistent whether you're using a Nordic nRF, STM32, ESP32, or even a Raspberry Pi. Blues supports SDKs for C, Arduino, Go, Python, and Zephyr RTOS. Developers can get started quickly, and firmware complexity stays low even as feature sets grow.
Why JSON is the Right Interface for IoT
Choosing JSON as the universal interface for Notecard wasn't accidental: it was deliberate, practical, and developer-centric.
JSON is human-readable, which means developers can interact with the Notecard API using nothing more than a serial terminal and text editor. When you're debugging in the field or over a USB/UART bridge, being able to see and edit commands without compiling firmware is invaluable.
It's also language-agnostic. JSON plays well with C, Python, JavaScript, Go, and nearly every platform. Whether you're prototyping on a Raspberry Pi or building production firmware on an STM32, the data model remains the same. Moreover, JSON reduces context switching. IoT developers already deal with plenty of protocols, SDKs, and configuration systems. A single JSON-based API means fewer abstractions to learn and less documentation to juggle.
Finally, JSON aligns with how the cloud works. Since your Notes eventually get routed to cloud services, most of which are JSON-first, there's no need for translation layers, protobuf schemas, or binary decoders. The data stays consistent from device to cloud.
Routing, Transforming, and Managing Data with Notehub
Once your data gets from device (Notecard) to cloud (Notehub), what happens then? Let's take a closer look at Notehub and its capabilities.
For starters, Notehub is not a bloated cloud platform. It's a lean, purpose-built intermediary that facilitates secure communication between Notecards and your preferred cloud destination. Whether you're using AWS, Azure, GCP, Snowflake, or a low-code IoT platform like Losant, Datacake, or Ubidots, Notehub makes routing data effortless.
The secure transport path looks like this:
- Notes are collected on-device using Notecard.
- When connectivity is established, accumulated Notes are synced with Notehub.
- Notehub routes that data to your chosen endpoint, applying transformations if necessary.
Notehub also supports bi-directional communication, so your cloud app can send configuration updates, environment variables, or control commands back to the device in the field.
And because Notecard and Notehub handle TLS, retries, and secure identity management automatically, your data stays protected in transit without you needing to manage certs or rotate keys.
Notehub: Secure by Default
Speaking of security, the unfortunate reality of today is that security isn't optional, it's essential. Every Notecard ships with a unique identity and cryptographic keys embedded at the point of manufacture. That means no device claiming, key rotation, or OTA certificate installs.
With the bundled SIM, traffic between Notecard and Notehub travels over the
cellular carriers' private network and never crosses the public internet.
Notecard configuration is always encrypted in transit, and you can encrypt all
of your data in transit too by using Notefiles whose names end in "s", such as
.qos. If your data must stay opaque even to Notehub, Notecard can also
encrypt each Note body on-device with a public key you supply,
so only your cloud application, which holds the private key, can decrypt it.
Blues also enables fine-grained access control at the Notehub layer, allowing you to define access policies per project or per device group. This multi-layered approach ensures that devices in the field remain trustworthy, tamper-resistant, and unbrickable.
Notehub: Seamless OTA Firmware Updates and Fleet Management
With Notehub, you can securely push firmware updates to both Notecards and their attached hosts. These updates are version-controlled and resilient, minimizing the risk of bricked devices. OTA is often an afterthought in IoT projects, but Blues bakes it in from day one.
Update delivery is conditional. You can push updates only when a device is idle, in range, or at full battery. This ensures your fleet stays online and healthy without risking uptime.
Notehub also gives you visibility into your fleet: connection frequency, last sync timestamp, data usage, firmware version, and custom metadata. Whether you're monitoring 10 devices or 10,000, you get clear operational insights without building infrastructure.
Notehub: Visualizing the Notecard Data Flow
To illustrate the simplicity of Blues' architecture, imagine a fictional smart parking sensor deployed in a city block:
- A car arrives in a spot. The sensor detects the change via a magnetic switch.
- Your host MCU formats a JSON object like
{ "occupied": true }and sends it to Notecard. - Notecard stores the Note locally in a Notefile called
parking.qo. - Every 15 minutes (or on a triggered sync), Notecard connects to the nearest LTE tower and transmits the Notefile to Notehub.
- Notehub transforms the message, attaches metadata like GPS location and/or timestamp, and routes it to your chosen cloud endpoint.
- Your application receives the data and updates a live dashboard. It can also send a downlink Note back to the device to change LED behavior or log occupancy time.
This flow (device --> Notecard --> Notehub --> cloud --> back to device) requires no carrier negotiation, no certificate provisioning, and no infrastructure maintenance.
Blues Notecard Features
Let's take a closer look at a few key features that are standard on Blues Notecard Cellular.
Built-in GPS and Motion Sensing
Notecard Cellular includes a GPS/GNSS module and accelerometer in every variant. This is invaluable for asset tracking, condition monitoring, or geofencing applications. You can acquire location data or wake the device on movement without additional components, reducing BOM complexity and battery power budget.
GPS data can be attached to Notes and sent to Notehub, or used locally to guide application logic. With integrated motion detection, you can design smarter tracking devices that only ascertain their location and/or transmit when they have moved.
Designed for Low Power from Day One
Battery life is non-negotiable for many IoT applications. Notecard Cellular is engineered to be low-power out of the box. In idle mode, it draws just 8-18uA@5V, orders of magnitude lower than most cellular modules. This makes it ideal for battery-powered sensors, remote monitoring stations, or portable asset trackers.
You don't need to build complex power management routines. Notecard handles sleep modes, wake triggers, and data batching automatically. The result? Long-lasting devices with minimal firmware complexity.
One API, Any Network
Blues understands that your network requirements may evolve. That's why the Notecard API is radio-agnostic. The same API is used for Notecards supporting cellular, WiFi, LoRa, or even the cellular and satellite combination powered by Blues Starnote. You can switch between radios without rewriting firmware or retooling your backend infrastructure.
This ability to switch radios is a game-changer when you're designing a family of products for different environments. Deploy the same firmware across a global fleet, and simply swap in the appropriate Notecard!
Cellular vs Satellite, LoRa, and WiFi
While cellular IoT offers unparalleled reach and simplicity, it's not always the only—or even the best—connectivity option (depending on your product's environment). Let's examine where cellular stands relative to WiFi, LoRa, and satellite communications.
| Technology | Range | Notecard Idle Current | Data Rate | Infrastructure | Best For |
|---|---|---|---|---|---|
| Cellular LTE Cat-1, Cat-1 bis, LTE-M, NB-IoT | Global (wherever cellular coverage exists) | ~9 µA @ 5V (Notecard Cellular); ~18 µA @ 5V (Cell+WiFi) | Peak rates from ~127 kbps (NB-IoT) to ~10 Mbps (LTE Cat-1) | Carrier networks (pre-existing) | Mobile, outdoor, or geographically distributed deployments |
| Satellite Skylo NTN, Iridium | Iridium: global, including oceans and both poles. Skylo: its supported regions | ~4 µA @ 5V for Starnote for Skylo, plus its host Notecard | Small packets: up to 256 bytes (Skylo) or 10,000 bytes (Iridium) | Skylo (existing GEO satellites); Iridium (66-satellite LEO constellation) | Remote, off-grid, or cellular-dark locations; fallback for hybrid deployments |
| LoRaWAN 868 MHz EU, 915 MHz US | Up to ~5 km in cities; up to 15 km in rural line of sight | ~8 µA on VIO (Notecard for LoRa) | ~0.25–50 kbps in EU868 (the 50 kbps rate uses FSK) | LoRaWAN gateway on The Things Stack | Dense, low-power sensor networks in a fixed geographic area |
| WiFi 2.4 GHz 802.11b/g/n | ~20 m indoors (less through walls and congestion) | ~18 µA @ 5V (Notecard Cell+WiFi) | Mbps class, the highest of the four | WiFi access point (pre-existing) | Indoor, high-bandwidth, infrastructure-present products |
WiFi excels in indoor environments with infrastructure already in place. It's a logical choice for smart home devices, appliances, or building automation, but it fails in remote or mobile scenarios, and power consumption is often higher due to constant connection requirements.
LoRa and LoRaWAN are optimized for ultra-low power and long-range transmission in fixed applications like agriculture, industrial telemetry, or smart cities. However, they require dedicated gateways, and offer limited bandwidth.
Satellite connectivity reaches far beyond cellular coverage (and, with Iridium, the entire globe), but it tends to come with high latency and higher cost. It's a great fallback for extreme conditions where no other networks exist, but not ideal for always-on communication.
Cellular hits a sweet spot across these trade-offs. It offers global infrastructure, bidirectional communication, mobility, security, and a balance of performance and power efficiency. And with Blues' multi-radio Notecards, you're not locked in. If your product needs WiFi in urban settings and LTE-M in rural ones, or cellular with satellite fallback, Blues makes that effectively invisible.
How Blues Customers Deploy with Confidence
Let's look at a few examples that mirror real-world deployments with Blues Notecard:
A precision agriculture company deploys 10,000 soil sensors across remote farmland. Each device uses a Cat-1 bis Notecard Cellular to transmit environmental data every 4 hours. The devices sleep deeply between transmissions, drawing just microamps, and wake on schedule. No SIM management, no cellular contracts: just plug, program, and deploy.
A logistics firm installs Notecards in shipping pallets for real-time asset tracking. Using LTE Cat-1 bis, they get consistent global coverage and location data via Notecard's integrated GPS. Notecard queues data when in transit and uploads when connectivity resumes. OTA firmware updates are pushed via Notehub during warehouse stops.
A wildlife researcher uses solar-powered sensors with cellular connectivity in remote national parks with a satellite backup via Blues Starnote. The devices only transmit once a day and rely on store-and-forward and bi-directional messaging to adjust behavior based on cloud-defined schedules. Power consumption is minimal, and battery replacements are rare.
Design Tips for Building with Cellular IoT
Launching a product on cellular brings unique hardware and software design considerations. Here are some best practices developers should follow when working with Notecard Cellular:
Antenna selection and placement are crucial. Always place the cellular antenna away from high-speed digital traces or metal enclosures. Follow the guidance provided by Blues or your antenna manufacturer to avoid detuning and performance issues. Then verify the result in the field with RSRP and SINR rather than signal bars (see Reading Cellular Signal Quality in the IoT).
Power budgeting matters more than you think. Cellular modules experience current spikes during transmission (up to 2A depending on the network). Make sure your power supply (especially in battery-powered applications) can handle peak draw, and use low-dropout regulators where needed.
Take advantage of Notecard's built-in store-and-forward capability. You don't need to maintain a persistent connection. Batch your Notes locally using the ample flash storage and let Notecard handle timing and retry logic. This not only saves power but improves overall reliability in flaky coverage zones.
If you're deploying globally, test multiple protocol options (Cat-1 vs Cat-1 bis vs LTE-M vs NB-IoT) in your target regions. Some operators disable NB-IoT or only offer LTE-M in specific countries. The Blues Notecard datasheets offer country-by-country support information to help you plan.
Frequently Asked Questions
What is cellular IoT?
Cellular IoT is the use of cellular networks (LTE today, 5G increasingly) to connect Internet of Things devices to the cloud. Unlike consumer mobile devices, cellular IoT endpoints prioritize power efficiency, long-range connectivity, and low bandwidth rather than high data throughput — making them ideal for embedded, battery-powered systems in remote or mobile deployments.
What is the difference between LTE Cat-1, LTE-M, and NB-IoT?
LTE Cat-1 offers higher bandwidth (up to 10 Mbps downlink) suitable for general-purpose IoT. LTE Cat-1 bis is a cost-optimized variant using a single antenna for compact devices. LTE-M is a low-power wide-area network (LPWAN) with deep coverage and mobility support, ideal for battery-powered asset trackers. NB-IoT offers the lowest power and deepest indoor coverage for simple sensors sending tiny bursts of data infrequently.
How much power does Notecard Cellular use in idle mode?
Notecard Cellular draws just 8–18 µA at 5V in idle mode (when the radio module is powered off and not transmitting). That's orders of magnitude lower than most cellular modules, making it suitable for battery-powered sensors, remote monitoring stations, and portable asset trackers.
What is a cellular IoT module?
A cellular IoT module is a modem chipset, RF front end, and firmware on a certified, solderable package that a product's processor controls with AT commands. You still supply the SIM, data plan, connection logic, security, and cloud backend. A system-on-module such as Blues Notecard builds those in and exposes a JSON API instead.
What kind of SIM does a cellular IoT device need?
Any SIM from a carrier or IoT connectivity provider whose network covers the device's region. Removable nano-SIMs are easy to swap, embedded MFF2 SIMs are soldered down so they can't shake loose, and eSIMs (eUICC) can change carrier profiles remotely. Notecard Cellular has an embedded MFF2 SIM and can fail over to an external SIM in a Notecarrier's Nano-SIM socket.
Which cellular technology uses the least power for a battery-powered sensor?
It depends on how often the device talks to the network, and whether the network needs to reach it. LTE-M and NB-IoT support two network sleep features: PSM, which leaves a device unreachable until it wakes, and eDRX, which keeps it reachable at set listening intervals. For a sensor that syncs a few times a day, compare the measured charge per sync instead: in Blues' tests on Notecard firmware v11.4.1, Cat-1 bis Notecards used 0.263–0.320 mAh per sync, the LTE-M Notecard for Skylo used 0.516 mAh, and Cat-1 Notecards used 0.723–0.967 mAh.
What certifications does a cellular IoT device need?
Typically regulatory certification for each market (FCC in the US, ISED in Canada, CE RED in the EU), industry certification for cellular networks (PTCRB in North America, GCF elsewhere), and sometimes a carrier's own certification. Building on a pre-certified module or system-on-module covers much of this, though the finished product may still need some testing.
Does Notecard Cellular include a SIM card and data plan?
Yes. Every Notecard ships with an embedded SIM, prepaid with 500 MB of data and 10 years of cellular service, with no connection fees or SIM activation costs. Developers can go from concept to prototype without dealing with a mobile carrier.
How many cellular IoT connections are there globally?
According to IoT Analytics, the number of licensed cellular IoT connections surpassed 4 billion in 2024 and is expected to double over the next five years. Applications range from agriculture and smart cities to transportation and logistics.
Do I need to write AT commands to use Notecard Cellular?
No. All interaction with Notecard happens via a developer-friendly JSON API over UART, USB, or I2C. You send and receive JSON messages with no modem programming, AT command sets, or proprietary protocols to learn.
Can I switch between cellular and other networks without rewriting firmware?
Yes. The Notecard API is radio-agnostic. The same JSON API is used for Notecards supporting cellular, satellite, LoRa, or WiFi connectivity. You can switch between radios by swapping in a different Notecard variant, without rewriting firmware or retooling your backend infrastructure.
Final Thoughts
Cellular IoT has never been more accessible. Blues removes the traditional pain points—from RF design to carrier negotiation to cloud integration—by providing a plug-and-play solution that just works. With Notecard Cellular, you get a prepaid, pre-provisioned, secure system-on-module that pairs seamlessly with any host device and any cloud.
Combined with Notehub, you gain secure data routing, fleet management, and over-the-air updates without building a backend from scratch. Add in support for the latest cellular protocols like LTE Cat-1, Cat-1 bis, LTE-M, and NB-IoT, and the result is a platform purpose-built for the real world.
Cellular IoT is no longer the domain of telecom giants and enterprise engineering teams. With Blues, it's in your hands. Visit blues.com to learn more, or just start building with a Blues Starter Kit and our complete developer documentation.