Machine Type Communication Feature

Description

MTC Features are network functions designed to optimize the 3GPP network specifically for use by Machine-to-Machine (M2M) applications. Defined in 3GPP TS 22.368 and related MTC specifications such as TR 37.868 and TR 43.868, they represent a modular set of capabilities that can be selected and combined based on the needs of a particular MTC application. Each feature addresses one or more of the distinctive characteristics of MTC devices—such as low mobility, small data volumes, infrequent transmission, and group-based behavior—and provides mechanisms in the core network and radio access network to serve those devices more efficiently. MTC Features are not features of the device itself, but rather network functions that the network may apply to MTC Devices that are subscribed to or configured for them.

The 3GPP MTC Feature framework, primarily specified in TS 22.368, defines a list of features with associated requirements. Common MTC Features include: Low Mobility, which avoids mobility management overhead for stationary or nomadic devices; Time Controlled, which allows the network to restrict access to specific time periods; Time Tolerant, which permits deferral of data transmission; Packet Switched (PS) Only, which eliminates circuit-switched fallback for MTC devices; Small Data Transmission, which optimizes signaling for small payloads; Mobile Originated Only, which restricts devices to initiating communications; Infrequent Transmission, which reduces signaling and paging overhead; Group Based Features (e.g., group-based policing and group-based addressing); and Priority Alarm, which allows prioritized access for alarm reporting. Each feature is described with normative requirements in TS 22.368 and impacts the design of core network elements such as MME, SGSN, PGW, and HSS.

Implementation of MTC Features relies on subscription information stored in the HSS/HLR and on network policies. For example, a device subscribed to the Low Mobility feature will not be required to perform tracking area updates as frequently, and the network may apply relaxed mobility management. A device subscribed to Time Controlled communication will be barred or allowed based on a schedule defined by the MTC Service Provider. Group-based features allow the network to apply aggregate policies, such as a maximum bit rate for a group of devices, which is useful for traffic shaping and overload control. These features often interact—for instance, a group of low-mobility, time-controlled devices with small data transmission can be managed with minimal signaling overhead.

From an architectural perspective, MTC Features are realized through interactions between the MTC Device, the Radio Access Network, the Core Network, and possibly the MTC Server. The SCEF (Service Capability Exposure Function) in later releases (Rel-13 onwards) provides a standardized way for MTC Servers to request certain features and for the network to expose capabilities. The MTC Interworking Function (MTC-IWF) also plays a role in triggering devices and controlling group-based features. In 5G, many of these features have been subsumed into broader capabilities such as network slicing, CIoT optimizations, and the NEF (Network Exposure Function) for external exposure.

MTC Features are essential because they allow operators to differentiate their networks for a wide range of IoT use cases without requiring dedicated infrastructure per application. They provide the flexibility to tailor network behavior through subscription and policy, which is critical in an environment where a single network must serve both high-throughput human users and massive numbers of low-power, low-data devices. The concept has been continuously refined across releases, and its principles influence current 5G IoT features and network slicing.

Purpose & Motivation

MTC Features exist to bridge the gap between the generic capabilities of 3GPP networks and the specific, often contrasting requirements of M2M applications. Traditional cellular networks were optimized for human users who are mobile, require high data rates, and tolerate some signaling overhead. MTC devices, by contrast, are often stationary, transmit small amounts of data, and require extremely long battery life and low cost. Without dedicated features, the network would waste resources on unnecessary mobility management, paging, and bearer setup, and devices would consume excessive power, shortening their operational life.

The MTC Feature framework, standardized starting in Release 10 with TS 22.368, provided a structured approach to solve these problems. It allowed mobile operators to offer a menu of network capabilities that can be activated per device or per group based on subscription. This modularity ensures that the network does not need to be re-architected for each new IoT use case; instead, operators can enable the relevant feature set for a given customer or device type. It also enables differentiated charging and QoS, which is essential for commercially viable IoT connectivity.

Historically, MTC Features were the first comprehensive attempt by 3GPP to accommodate machine-type traffic within existing cellular systems. They addressed limitations of the pre-Release 10 networks, which had no standardized way to handle the massive scale, low power, and diverse traffic patterns of M2M. The features laid the groundwork for later, more radical optimizations such as NB-IoT and LTE-M, and they continue to be relevant as building blocks in the 5G era, where network slicing and CIoT optimizations inherit and extend many of the same concepts.