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

Glossary term · Identifier

LTE-M

LTE Machine-Type Communication (LTE-M), also known as LTE-MTC, eMTC, or Cat-M1

Identifier →

LTE-M is a 3GPP radio access type identifier for E-UTRAN-based machine-type communication, optimized for low-power, wide-area IoT, and it can also cover satellite access.

Introduced
Rel-13
Where
Core Network › 5G Core
Specifications
2 specs
LTE-M Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

LTE-M (LTE for Machine-Type Communication) is a 3GPP RAT type identifier that exists solely within the Core Network context. It is defined as a sub-type of the E-UTRAN (Evolved Universal Terrestrial Radio Access Network) RAT type and is used to identify, within the Core Network, the E-UTRAN when the UE indicates Category M in its radio capability information. In other words, LTE-M is not a separate radio access technology; it is a classification mechanism that allows core network entities such as the MME (Mobility Management Entity) in EPC or the AMF (Access and Mobility Management Function) in 5GC to distinguish UEs operating with Category M1 (low-complexity, narrowband) capabilities. Category M1, defined in 3GPP TS 36.306, specifies a UE with reduced complexity, narrower bandwidth (1.08 MHz), and lower data rates, tailored for massive machine-type communication (mMTC) use cases.

The identifier itself is carried in core network signaling messages that convey RAT type information, such as in EPS Attach procedures (TS 23.401) and 5G Registration procedures (TS 23.501). When a UE attaches to the network and indicates it supports Category M, the serving core network node records the RAT type as LTE-M. This distinction enables the network to apply appropriate policies, charging, mobility management, and session management specific to the device's capabilities. For example, the network might select a different SMF (Session Management Function) or apply specific QoS rules suitable for low-power devices.

The definition has been refined across releases. Initially introduced in Release 15, the LTE-M RAT type was strictly defined to identify E-UTRAN when used by a UE indicating Category M. However, Release 17 expanded the scope to include satellite access unless otherwise stated. This aligns with 3GPP's broader integration of Non-Terrestrial Networks (NTN) into 5G, allowing IoT devices using satellite links to be identified under the same LTE-M umbrella. In Release 20, the definition was updated with new terminology: "E-UTRA" replaced "E-UTRAN" and the wording was streamlined to state it is a sub-type of E-UTRA RAT type defined to identify in the Core Network the E-UTRA when used by a UE indicating Category M. This reflects the ongoing harmonization of terminology in 3GPP specifications.

From an architectural standpoint, LTE-M is one of several RAT types defined in 3GPP, including E-UTRAN, NR, and NB-IoT (often considered a separate RAT type). The distinction among these RAT types is crucial for core network functions that must track which access technology a UE is using, especially in multi-RAT deployments, dual connectivity, and network slicing scenarios. For instance, an IoT device might move between LTE-M and NB-IoT, and the core network must be able to identify the current RAT type for proper session management and charging.

In summary, LTE-M is a label that the Core Network uses to recognize a specific class of E-UTRA-based devices. It does not alter the radio interface itself but provides essential signaling information for the network to optimize service delivery to massive IoT devices. Its evolution across releases mirrors the changing landscape of IoT connectivity, including the extension to satellite access and terminology updates aligned with 3GPP's ongoing specification evolution.

Purpose & Motivation

LTE-M as a Core Network identifier exists to allow the mobile core to differentiate between standard E-UTRAN devices and those specifically designed for machine-type communication using Category M capabilities. Prior to its introduction, the core network treated all E-UTRAN devices uniformly, which led to inefficiencies in handling low-power, low-data-rate IoT devices. Those devices often required different paging strategies, lower mobility management overhead, and specialized charging models. By introducing a distinct RAT type identifier, 3GPP enabled operators to apply differentiated treatment without modifying existing radio access specifications.

The identifier also simplifies interoperability and roaming for IoT devices. When a device roams into a visited network, the core network can quickly identify that it is an LTE-M device and thus apply the correct policies and charging rules, even if the visited network does not have detailed knowledge of the device's radio capabilities. This is particularly important for global IoT deployments where devices may operate across multiple operators.

Additionally, the extension to satellite access in Release 17 reflects the growing need to support IoT devices in remote areas where terrestrial coverage is uneconomical. By including satellite access under the LTE-M RAT type, 3GPP ensures that core network procedures remain consistent and that operators can offer seamless IoT connectivity across terrestrial and satellite links. The Rel-20 rephrasing to "E-UTRA" and updated wording aligns with the broader 5G terminology and ensures clarity in an evolving multi-access environment.

What changed in its specifications

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

TS 23.401Rel-18 → Rel-19

Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.

Full comparison in TS 23.401 →
TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →

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
  • LTE-M builds on E-UTRA
    “A bandwidth reduced low complexity (BL) UE can operate in any LTE system bandwidth but with a limited channel bandwidth of 6 PRBs” 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 5 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

Introduced in Rel-13 (release dating of the term; no individual change cited).

Rel-15 specification text

Rel-15 introduces LTE-M as a core-network RAT type sub-type of E-UTRAN, with an eNodeB LTE-M indication, MME/SGW/PGW RAT type signalling and reporting flags over S1AP and GTP.

  • “LTE-M: a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type E-UTRAN RAT type” TS 23.401 v15.13.0
  • “The MME shall set the RAT Type to LTE-M if it has received the LTE-M indication from the eNodeB” TS 29.274 v15.9.0
  • “Introduction of LTE-M (eMTC) traffic Differentiation” TS 36.413 v15.11.0
Rel-16 1 CR

Rel-16 specifies LTE-M as a core-network RAT type for 5GC: NG-RAN signals an LTE-M Indication to the AMF, which stores and propagates it, and it adds subscription-based access restriction.

  • “When the UE has provided a Category M indication to the NG-RAN during RRC Connection Establishment, the NG-RAN shall provide an LTE-M Indication to the AMF” TS 23.501 v16.20.0
  • “the AMF shall store the LTE-M Indication in the UE context, consider that the RAT type is LTE-M” TS 23.501 v16.20.0
  • Subscription based access restriction for LTE-M TS 23.501CR2158
Rel-17 specification text

Rel-17 extends LTE-M to satellite access: new LTE-M(LEO/MEO/GEO/OTHERSAT) RAT types, MME/SGW rules for reporting them to the PGW, and satellite indication flags in GTP.

  • “"LTE-M(LEO)", "LTE-M(MEO)", "LTE-M(GEO)" and "LTE-M(OTHERSAT)" are used in EPC to distinguish the different WB-E-UTRAN, NB-IoT and LTE-M satellite access types.” TS 23.401 v17.11.0
  • “The MME shall set the RAT type to LTE-M Satellite related RAT type, if the eNodeB indicated this is an LTE-M UE accessing satellite E-UTRAN” TS 29.274 v17.12.0
  • “Unless otherwise stated in this specification, LTE-M also includes satellite access.” TS 23.401 v17.11.0
Rel-18 specification text

Rel-18 adds an LTE-M UE Indication (LTEMUI) flag in GTPv2 Forward Relocation and Context Response, and extends 5GS handling of LTE-M indication, RAT type and LTE-M satellite access restrictions.

  • “if this bit is set to 1, it indicates that the UE is a LTE-M UE (see 3GPP TS 23.401 [3])” TS 29.274 v18.8.0
  • “The access restriction data for LTE-M satellite accesses above is supported only to allow the AMF to provide it to MME in case of mobility from 5GS to EPS.” TS 23.501 v18.12.0
  • “The PCF can also receive the RAT Type as LTE-M, when applicable from the AMF” TS 23.501 v18.12.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 23.501 vk30 5G System Architecture Rel-20 read