Description
An IoT device, as defined in 3GPP, is a type of User Equipment (UE) that is dedicated for a set of specific use cases or services and which is allowed to make use of certain features restricted to this type of UEs. This definition, introduced in Release 15, reflects the growing need to differentiate IoT devices from regular UEs in terms of capabilities, service requirements, and network behavior. IoT devices encompass a wide range of applications, including massive Machine-Type Communication (mMTC), industrial IoT, wearables, and low-power wide-area (LPWA) devices.
The 3GPP architecture for IoT devices includes several optimizations to support the unique characteristics of IoT, such as low power consumption, low data rates, high connection density, and extended coverage. These optimizations are realized through features like Narrowband IoT (NB-IoT), LTE-M (eMTC), and the 5G NR-based mMTC and URLLC enhancements. IoT devices may support different categories of UE, such as Cat-NB1, Cat-NB2, Cat-M1, Cat-M2, and various NR reduced capability (RedCap) devices. Each category defines specific capabilities, including bandwidth, data rate, and power class.
The network identifies IoT devices based on subscription information, device capabilities, or explicit signaling. This allows the network to apply specific policies, such as access control, mobility management, and session management tailored to IoT devices. For example, IoT devices may be configured with a specific Discontinuous Reception (DRX) cycle to save power, or they may use a control plane CIoT EPS optimization to reduce signaling overhead. The network may also restrict certain features to IoT devices, such as extended coverage enhancement (CE) modes, or allow them to use specific network slices dedicated to IoT services.
Key technical aspects include the support for various IoT-specific procedures, such as the Attach procedure with CIoT optimizations, the use of non-IP data delivery (NIDD), and the support for power saving mode (PSM) and extended DRX (eDRX). IoT devices may also support mobility restrictions, such as being stationary or only mobile within a limited area. The security framework for IoT devices is specified in TS 33.401 and TS 33.501, with considerations for constrained devices and low-power operation.
The definition of IoT device has been stable since Release 15, with no changes to its wording in subsequent releases up to Release 20. However, the ecosystem of IoT devices continues to evolve, with new device types and capabilities being introduced in later releases, such as NR RedCap in Release 17 and further enhancements in Releases 18 and beyond. The term is used in specifications like TS 22.261 (Service requirements for the 5G system), TS 22.804 (Communication for automation in vertical domains), and TS 22.859 (Study on enhancement of 5G for IoT).
Purpose & Motivation
The term IoT device was introduced to provide a clear distinction between traditional user equipment (e.g., smartphones) and devices specifically designed for IoT applications. Prior to Release 15, IoT devices were often referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) devices, but these terms did not fully capture the diversity of IoT use cases and the need for differentiated treatment in the network. The 3GPP recognized that IoT devices have unique requirements, such as low cost, low power, extended coverage, and massive connection density, which are not typically addressed by conventional UE designs.
The motivation for defining IoT device as a separate type of UE was to enable the network to apply specific features and restrictions that are only applicable to IoT devices. For example, some features like extended coverage enhancement (CE) modes or certain power saving mechanisms are only relevant to IoT devices and should not be used by regular UEs. By defining IoT device as a distinct category, 3GPP allows network operators to optimize their networks for IoT traffic while ensuring that regular UEs are not adversely affected. This also facilitates interoperability and roaming for IoT devices across different networks.
Furthermore, the definition supports the growing trend of network slicing, where IoT devices can be assigned to specific slices tailored to their service requirements. This enables operators to provide differentiated services for various IoT verticals, such as smart metering, industrial automation, and connected vehicles. The term has been widely adopted in 3GPP specifications and industry forums, and it continues to evolve as new IoT technologies emerge.
What changed in its specifications
The latest release-to-release comparison of specifications that define IoT device. Each summary describes the whole specification, not only this term.
Rel-19 adds to TS 22.261 Indirect Network Sharing, 5G satellite access Phase 3 requirements, a 5G wireless sensing service clause, signalling traffic monitoring, SNPN interconnection clauses, and Localized Mobile Metaverse Services. It also extends disaster roaming to 5G-only UEs and adds Ambient IoT device clauses.
Full comparison in TS 22.261 →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.
Initial introduction of the term IoT device in 3GPP specifications. Defined as a type of UE dedicated for a set of specific use cases or services and allowed to use certain features restricted to this type of UEs. This definition provided a clear categorization for IoT devices in the 5G era.
Defining Specifications
3GPP specifications that define or reference IoT device, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.261 vk81 | 5G Service and Operational Requirements | Rel-20 read |
| TR 22.804 vg30 | 5G Automation in Vertical Domains Study | Rel-16 read |
| TR 22.859 vi20 | Technical Report | Rel-18 read |