Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · IoT

NB-IoT

Narrowband Internet of Things

IoT →

NB-IoT is a 3GPP low-power wide-area radio access technology that uses a 200 kHz channel to enable deep coverage, long battery life, and massive device density for the Internet of Things.

Introduced
Rel-13
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
11 specs
Also in
User Equipment
NB-IoT Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Narrowband Internet of Things (NB-IoT) is a cellular radio access technology standardised by 3GPP in Release 13 specifically to address the requirements of massive machine-type communication (mMTC). It allows access to network services via E-UTRA (LTE) with a channel bandwidth limited to 200 kHz, corresponding to a single Physical Resource Block (PRB). This narrow bandwidth is the defining characteristic of NB-IoT and is the key enabler of its coverage, capacity, and power-efficiency advantages.

NB-IoT can be deployed in three operation modes. In standalone operation, it uses a dedicated 200 kHz carrier, typically in spectrum refarmed from GSM. In guard-band operation, it occupies unused PRBs within the guard band of an existing LTE carrier. In in-band operation, it uses one PRB within a normal LTE carrier. This flexibility allows operators to deploy NB-IoT without acquiring new spectrum, reusing existing LTE infrastructure and sites.

The physical layer of NB-IoT is a simplified, narrowband variant of LTE. The downlink uses OFDMA with 15 kHz subcarrier spacing, 12 subcarriers (180 kHz) plus guard bands, and the uplink uses SC-FDMA with either 15 kHz or 3.75 kHz subcarrier spacing. To compensate for the reduced bandwidth and to achieve the required coverage enhancement, NB-IoT employs extensive repetition of transmissions — a single transport block may be repeated hundreds or thousands of times. This repetition, combined with power spectral density concentration in a narrow band, yields a Maximum Coupling Loss (MCL) of up to 164 dB, roughly 20 dB better than normal LTE coverage, enabling operation in basements, underground meters, and remote rural areas.

NB-IoT supports three coverage enhancement (CE) levels (CE0, CE1, CE2) corresponding to increasing amounts of repetition. The UE reports its CE level, and the network schedules accordingly. To reduce cost and complexity, NB-IoT devices use half-duplex FDD, a single receive antenna, and a simplified protocol stack. The maximum transport block size is 680 bits in the downlink and 1000 bits in the uplink, and peak data rates are around 26 kbps downlink and 66 kbps uplink (multi-tone).

Power saving is achieved through extended Discontinuous Reception (eDRX) and Power Saving Mode (PSM). With eDRX, the UE can sleep for minutes or hours between paging occasions; with PSM, the UE can remain in a deep sleep state for days while keeping its registration alive. Together these features enable battery life of up to 10 years on a single coin cell, a key requirement for remote sensors and meters.

NB-IoT also supports a control-plane CIoT optimisation (CP CIoT) where user data is carried in NAS signalling messages, avoiding the overhead of establishing a full data radio bearer. In later releases, NB-IoT gained support for positioning (Rel-14), mobility and service continuity (Rel-14), TDD operation (Rel-15), and integration with 5G core (Rel-16). It is standardised alongside LTE-M (eMTC) and complements them: NB-IoT targets ultra-low-cost, low-data-rate, delay-tolerant applications, while LTE-M targets higher data rates and voice support.

Purpose & Motivation

NB-IoT was created to serve a market that traditional cellular technologies could not address economically: massive numbers of low-cost, low-power, low-data-rate devices such as utility meters, environmental sensors, tracking tags, and agricultural monitors. Before NB-IoT, options for wide-area IoT connectivity were limited. 2G/GPRS was cheap but being sunset in many markets and offered poor coverage and battery life. Proprietary LPWAN technologies such as LoRa and Sigfox emerged, but they operated in unlicensed spectrum with limited QoS guarantees and no global standardisation.

3GPP responded in Release 13 with a family of Cellular IoT (CIoT) technologies: NB-IoT and LTE-M (eMTC). NB-IoT was designed from the ground up for the most extreme requirements: ultra-low device cost (targeting a $5 module), 10-year battery life, 20 dB coverage enhancement, and support for up to 50,000 devices per cell. The choice of a 200 kHz bandwidth was deliberate — it concentrates transmit power into a narrow band, boosting link budget, and it allows deployment in a single PRB, making refarming trivial.

By standardising NB-IoT, 3GPP gave operators a licensed-spectrum, globally interoperable solution with guaranteed QoS, security, and manageability. It also ensured a smooth evolution path: NB-IoT devices can be integrated into existing LTE and, from Rel-16, 5G core networks, protecting operator investments and enabling a single management framework for all device types.

What changed in its specifications

The latest release-to-release comparison of specifications that define NB-IoT. Each summary describes the whole specification, not only this term.

TS 36.300Rel-18 → Rel-19

Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.

Full comparison in TS 36.300 →
TS 36.302Rel-12 → Rel-13

Rel-13 added BL/enhanced-coverage exclusions, modulation limits, and new downlink reception types for MTC, plus SC-PTM downlink channel combinations and UE capability requirements.

Full comparison in TS 36.302 →

Technology family

Radio access technologies · Radio Access Network

  1. Phase 1 GSM
  2. R97 GPRS
  3. R99 EDGE, EGPRS, UTRA, UTRA-FDD, UTRA-TDD, UTRA-WTDD
  4. Rel-4 GERAN, UTRA-NTDD
  5. Rel-7 EGPRS2
  6. Rel-8 E-UTRA
  7. Rel-13 EC-GSM-IoT, LTE-M, NB-IoT
  8. Rel-15 NR
  9. Rel-17 NR RedCap
  10. Rel-18 NR eRedCap
  • NB-IoT builds on E-UTRA
    “NB-IoT allows access to network services via E-UTRA with a channel bandwidth limited to 200 kHz.” TS 36.300

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 8 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-13 introduced

NB-IoT was specified for the first time in Rel-13, with a 200 kHz channel, in-band, guard-band and standalone operation modes, and base station RF requirements, RRC procedures and test specifications.

  • “NB-IoT allows access to network services via E-UTRA with a channel bandwidth limited to 200 kHz.” TS 36.331 v13.17.0
  • “NB-IoT standalone operation: NB-IoT is operating standalone when it utilizes its own spectrum” TS 36.104 v13.14.0
  • Introduction of support for NB-IoT TS 23.401CR2948
Rel-14 1 CR

Rel-14 extended NB-IoT with new operating bands, multiple standalone carrier channel raster, user-plane mode support, inter-RAT idle mobility, eDRX updates and RRC re-establishment for Control Plane CIoT without AS security.

  • Inter-RAT idle mode mobility to and from NB-IoT TS 23.060CR2018
  • “Channel Raster For Multiple Standalone NB-IoT Carriers (TS 36.141)” TS 36.141 v14.15.0
  • “a NB-IoT UE supporting RRC connection re-establishment for the Control Plane CIoT EPS optimisation in RRC_CONNECTED may initiate the procedure” TS 36.331 v14.18.0
Rel-15 3 CRs

Rel-15 extended NB-IoT itself: TDD support, additional operating bands (4, 14, 71), small cell support, and further enhancements across RAN and core specifications.

  • NB-IoT: Adding TDD support in TS 36.104 TS 36.104CR4782
  • CR to 36.104: Support of NB-IoT for Bands 4, 14 and 71 TS 36.104CR4717
  • Introduction of further enhancements to NB-IoT in 36.212 TS 36.212CR0293
Rel-16 3 CRs

NB-IoT gained new Rel-16 capabilities, including UE-specific DRX, inter-RAT mobility to and from NB-IoT in 5GS, UE priority-based QoS differentiation, and new test frequencies and base station requirements.

  • Introduction of support for UE-specific DRX for NB-IoT TS 23.401CR3558
  • Introduction of Inter-RAT mobility support to and from NB-IoT TS 23.501CR0895
  • Introduction of inter-UE QoS differentiation for NB-IoT using NB-IoT UE Priority TS 23.501CR0892
Rel-17 2 CRs

Rel-17 extended NB-IoT with 16QAM, non-terrestrial network support, additional enhancements, new SIB31-NB acquisition and updated BS conformance and performance requirements.

  • Introduction of Rel-17 enhancements for NB-IoT and eMTC TS 36.321CR1536
  • “Table A.16.1-2: FRC parameters for NB-IoT NPUSCH format 1 with 16QAM” TS 36.141 v17.15.0
  • Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s00-s05 TS 36.213CR1410
Rel-18 1 CR

Rel-18 extends NB-IoT with NTN support: SIB31-NB/SIB33-NB acquisition, GNSS measurement for NB-IoT over NTN, NB-IoT in-band operation with NR NTN, and satellite location reporting.

  • “For BL UEs or UEs in CE or NB-IoT UEs that are connected to NTN, GNSS measurement can be triggered aperiodically” TS 36.331 v18.11.0
  • “stop timer T318 when both SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT) and SystemInformationBlockType33 (SystemInformationBlockType33-NB in NB-IoT) are acquired;” TS 36.331 v18.11.0
  • UE location reporting for NB-IoT satellite access TS 24.301CR4044
Rel-19 1 CR

In Rel-19 NB-IoT gained NTN TDD operation and related requirements, test environment, procedures and corrections (e.g. CB-Msg3-EDT, TDD mode requirement, cell reselection measurement rules).

  • “TDD Mode is required for Rel-19 and forward NB-IoT NTN” TS 36.508 v19.3.1
  • “In NTN, a BL UE, UE in CE mode A or NB-IoT UE can initiate EDT using the CB-Msg3-EDT procedure” TS 36.331 v19.4.0
  • Clarification on a slot to be an UL slot if within UL subframe(s) for NB-IoT NTN TDD TS 36.213CR1467
Rel-20 3 CRs

Rel-20 adds IMS voice call support over NB-IoT (GEO/NTN), including dedicated and GBR bearers, emergency calls, SIP optimizations and related management and protocol support.

  • Dedicated bearer and GBR bearer support for IMS Voice over NB-IoT(GEO) TS 23.401CR4002
  • Reducing SIP message size over NB-IoT(GEO) access TS 24.229CR6823
  • Relaxation of NB-S1 mode restrictions for NB-IoT(GEO) for emergency service TS 24.301CR4714

Defining Specifications

3GPP specifications that define or reference NB-IoT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.304 vj30 LTE UE Idle Mode Procedures Rel-19 read
TS 36.306 vj30 E-UTRA UE Radio Access Capability Parameters Rel-19 read
TS 36.322 vj00 E-UTRA Radio Link Control Protocol Specification Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 36.355 vj00 LTE Positioning Protocol (LPP) Rel-19 read
TS 37.355 vj30 LTE Positioning Protocol (LPP) Rel-19 read
TR 37.911 vj00 3GPP 5G NTN Self-Evaluation Report Rel-19 read
TS 38.410 vj20 NG-RAN; NG General Aspects and Principles Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read