Chapters

 Cellular IoT Module Guide

Radio Remi, your wireless guide

Your guide: Radio Remi

“Range, power, and data-rate is a triangle — pick two honestly, then measure the third in the real room.”

Start With the Module

Picture a cold-chain tracker that sends a small temperature record while crossing a border. A payload is the useful reading inside a message. Latency is the time from a stated event to a stated result. The tracker needs both a clear data record and a clear alarm deadline, even when the network or service changes.

Begin with that whole field path. Record the place, movement, message size, alarm deadline, battery goal, network owner, fallback, and proof needed after a restart. Carry the same case through the chapters so that each radio or service choice answers a measured need.

Keep the first plan plain. Name the place, trip, reading, and alarm. Set a battery goal. Say who owns the link. Decide what the device does when the link is lost. Then test one real route.

Cellular IoT design starts with a field question, not a radio badge: what must this device deliver, from where, for how long, and what evidence will prove it still works when coverage, roaming, power, or operator support changes? The 23 chapters move from NB-IoT foundations through LTE-M, deployment, managed LPWAN, and 5G options without treating one technology as a universal winner.

Follow Radio Remi along one real field route as its dependencies change.

  1. Radio Remi follows one temperature record leaving a moving field tracker toward its network path.

    A field device must deliver a useful record.

  2. Radio Remi reviews the tracker's location, travel route, and battery-life evidence as separate design facts.

    Its place, route, and working life all matter.

  3. Coverage, remaining battery power, and operator support each become uncertain around the field tracker.

    Coverage, power, or service support may change.

  4. Two team members inspect the received temperature record and its route trace after one real field test.

    The team needs proof that it still works.

One field record is tested against place, route, battery life, and changing service conditions.

Learning Objectives

By the end of the module, you should be able to:

  • distinguish coverage, mobility, latency, payload, power, lifecycle, and operator-dependency requirements;
  • trace an NB-IoT or LTE-M device from radio access through the mobile core to an application record;
  • choose between NB-IoT, LTE-M, Sigfox-style managed LPWAN, and 5G device classes using measured evidence;
  • plan PSM, eDRX, retries, eSIM, roaming, and service-continuity checks; and
  • produce a deployment record that states assumptions, observations, owners, and retest triggers.

Before You Start

You need a working understanding of packets, IP addressing, link budgets, and basic energy accounting. Review Networking Fundamentals if radio access and gateways are new, or Energy and Power if current profiles and duty cycles are unfamiliar. This module explains cellular-specific mechanisms; it does not replace local spectrum, operator, certification, safety, or roaming requirements.

A Worked Route Through the Module

Imagine a battery-powered cold-chain tracker that reports temperature every fifteen minutes, crosses borders, and must raise an alarm within a minute when the load warms.

  1. Use Cellular IoT Overview and Evolution to establish the generation and sunset boundary.
  2. Compare NB-IoT and LTE-M: mobility and alarm latency may favour LTE-M, while stationary deep-coverage reporting may favour NB-IoT.
  3. Trace the service path in NB-IoT Architecture, then test coverage assumptions in Coverage Enhancement.
  4. Build the reachability and energy ledger with PSM/eDRX and Cellular Power Optimization.
  5. Record border crossing, profile ownership, and recovery expectations in eSIM and Global Deployment.
  6. Close with Deployment Planning: field measurements, operator dependencies, firmware/profile owners, failure response, and retest dates become the approval evidence.

Labs and Interactives

Quick Route Check

A stationary basement meter sends a small daily reading and can tolerate delayed downlink. Where do you start?

Start with NB-IoT fundamentals, coverage enhancement, and PSM/eDRX. Then verify local operator support and measured energy; the scenario suggests a route, not an automatic approval.

A tracker moves between cells and needs prompt alarms. Which route is more useful?

Start with the evolution overview and NB-IoT/LTE-M comparison, then continue through LTE-M lab, eSIM/global deployment, and deployment planning. Mobility, latency, roaming, and current traces must all be evidenced.

Chapters by Part

NB-IoT Technology

Cellular Basics

Sigfox and Managed LPWAN

5G & Future

Choose a Starting Point

If this subject is new, follow the worked route and then the parts in order. If you already have a design or troubleshooting question, start with the chapter that owns the evidence you lack, but carry the result through deployment planning before treating it as a decision.

Use the sidebar and site search for supporting material; use this chapter map as your main route through the module.

How to Use This Material

  • Keep one deployment scenario and evidence record across the chapters.
  • Use the two labs after the relevant foundations, not as isolated demonstrations.

← Back to All Modules