IoT-NTN Call Flow (NB-IoT) — Attach to Data

Introduction

The steady state for most NB-IoT devices, terrestrial or satellite, is asleep. This flow starts at the moment a device wakes on its own schedule (or on a mobile-terminated trigger it was paged for) and ends when it has sent its payload and dropped back into PSM or a long eDRX cycle. Every stage below reuses the terrestrial NB-IoT/EPS procedure grammar — the satellite link changes timing and coarse RF parameters, not message content.

Before RACH: waking up and finding the satellite

1. Wake & (re)synchronize. The device leaves PSM/eDRX sleep and re-acquires NB-IoT synchronization signals from the satellite cell.
2. System information. It reads (or recalls, if still valid) the broadcast common timing/Doppler compensation parameters and the Koffset-equivalent scheduling gap described in RRC (NB-IoT NTN).
3. Local pre-compensation. Using whatever position information is available (GNSS if fitted, or leaning more heavily on network-broadcast common terms if not), the device prepares its NPRACH transmission timing and frequency.

NPRACH: single-tone random access

NB-IoT’s NPRACH uses a single-tone, frequency-hopping preamble rather than NR’s wideband sequences. Over satellite the procedure keeps its terrestrial shape — preamble, RAR, Msg3, Msg4 — with the same timing-advance pre-compensation principle as NR-NTN’s Timing Advance & Koffset, scaled to NB-IoT’s narrowband resource grid and typically coarser TA step sizes given the device class’s lower cost radio.

RRC connection setup

Msg3 carries RRCConnectionRequest (or, for a returning device with a suspended context, a resume request). Msg4 delivers RRCConnectionSetup (or RRCConnectionResume), and the device replies with RRCConnectionSetupComplete, piggybacking its first NAS message exactly as in the NR-NTN flow — see NR-NTN Call Flow for the direct comparison.

NAS Attach and default bearer

1. Attach Request (or, for a resumed context, straight to data) reaches the MME.
2. Authentication & Security Mode — run only on a fresh Attach; a resumed RRC connection with valid security context skips this, which is exactly why Suspend/Resume matters so much more over satellite than terrestrially.
3. Attach Accept with default EPS bearer context — establishes the always-on bearer the device will use for its payload.
4. Attach Complete confirms.

Data transfer and return to sleep

With the default bearer active, the device sends its payload (often just a few dozen to a few hundred bytes — a meter reading, a status flag). Once acknowledged, it either releases the RRC connection outright or, if it expects to transmit again soon, requests RRC Suspend to preserve its security context for a fast resume next time. The device then re-enters PSM or a long eDRX cycle, timed where possible against the satellite’s next expected visibility window — see Mobility & Feeder-Link Switch for how that visibility is tracked on non-GEO constellations.

Reading the flow as a log

Representative sequence for a LEO IoT-NTN pass — illustrative, exact timings vary by vendor and orbit:

Summary

The NB-IoT NTN transaction is the terrestrial NPRACH-to-Attach-to-data sequence, unchanged in message grammar, with satellite timing/Doppler pre-compensation bolted onto access and a scheduling gap sized to the cell’s round trip protecting every grant. RRC Suspend/Resume does disproportionate work here: for a device that already skips full Attach on most wake cycles, avoiding even one satellite round trip of authentication signalling is a meaningful battery and latency win. The eMTC/LTE-M flow follows the same shape with MPDCCH-scheduled access and optional CE Mode repetition in place of NPRACH.