Description
Machine to Machine (M2M) communication describes scenarios where devices communicate directly with other devices or with backend servers without human involvement. Unlike human-centric communication (voice calls, web browsing), M2M traffic is characterized by large numbers of devices, small payloads, infrequent or bursty transmissions, and often stringent requirements on power consumption and cost. Examples include smart meters, fleet tracking, industrial sensors, and vending machine telemetry.
3GPP first addressed M2M systematically in Rel-8, when the proliferation of machine-type devices on cellular networks became apparent. The core problem was that cellular networks were designed for human users: signaling procedures for attach, bearer setup, and mobility were heavy relative to the tiny data volumes M2M devices generate. Rel-8 introduced foundational work on M2M requirements and security (captured in 22.868 for requirements and 33.834 for security aspects), identifying the need for optimizations such as low-mobility handling, small data transmission, and group-based management.
Architecturally, M2M in 3GPP involves the device (UE or MTC device), the radio access network, the core network, and one or more M2M application servers or service capability servers. The M2M device may communicate with an M2M server directly (direct model) or via a gateway (indirect model), where a gateway aggregates traffic from many constrained devices. 3GPP defined the MTC (Machine-Type Communication) architecture with entities such as the MTC-IWF (Interworking Function) and SCS (Service Capability Server) to mediate between the 3GPP network and external M2M service providers.
Security for M2M (33.834) addresses the unique threat landscape: devices may be physically accessible to attackers, may have limited cryptographic capabilities, and may operate for years without maintenance. The security framework covers device authentication, secure bootstrapping, key management, and protection of the M2M service layer. It also considers group-based authentication, where a gateway authenticates on behalf of many devices, reducing signaling overhead.
M2M is the conceptual ancestor of what is now called IoT (Internet of Things) and, in 3GPP terms, massive Machine-Type Communication (mMTC) — one of the three 5G usage scenarios. The Rel-8 M2M work laid the groundwork for later optimizations: Rel-12's MTC enhancements (power saving mode, extended DRX), Rel-13's narrowband IoT (NB-IoT) and LTE-M, and Rel-16's 5G NR support for industrial IoT and URLLC. While the term M2M has largely been superseded by IoT in marketing and by mMTC in standards, its requirements and security foundations remain embedded in the 3GPP architecture.
Purpose & Motivation
M2M exists because cellular networks were originally designed for humans, and machine devices have fundamentally different traffic characteristics. A smart meter sends a few hundred bytes per day; a human smartphone streams video. Applying human-centric signaling and bearer management to millions of meters would overwhelm the network. M2M requirements work in Rel-8 identified these mismatches and set the stage for optimization.
The security framework (33.834) was motivated by the fact that M2M devices are often deployed in physically insecure locations, have long operational lifetimes, and may be produced by many vendors with varying security maturity. A standardized security architecture was needed to ensure that M2M deployments could be trusted end-to-end, including device authentication, secure credential provisioning, and protection against cloning and tampering.
Historically, M2M predates 3GPP's involvement — early M2M used proprietary radio or 2G networks. 3GPP's contribution was to bring M2M onto standardized cellular infrastructure with defined requirements and security, enabling scale and interoperability. The limitations of early M2M (no standardized security, no efficient signaling) motivated the Rel-8 work, which in turn evolved into the IoT and mMTC frameworks used today.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference M2M, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.868 v800 | M2M Communication Requirements and Optimization | Rel-8 read |
| TR 33.834 vg10 | Long Term Key Update Procedures Study | Rel-16 read |