Description
Control Plane Early Data Transmission (CP-EDT) is a foundational technology for massive Machine-Type Communication (mMTC) in 5G and evolved 4G networks. It fundamentally changes how small, infrequent data packets are handled by allowing their transmission to be piggybacked on the control plane signaling messages used during the initial connection setup, specifically during the Random Access Channel (RACH) procedure and the subsequent Non-Access Stratum (NAS) signaling exchange. This approach bypasses the traditional and resource-intensive process of establishing a full Data Radio Bearer (DRB), which involves multiple Radio Resource Control (RRC) signaling steps, security activation, and bearer configuration.
Architecturally, CP-EDT operates across the User Equipment (UE), the Radio Access Network (RAN - eNB/gNB), and the Core Network's Mobility Management Entity (MME) in 4G or Access and Mobility Management Function (AMF) in 5G. The procedure is initiated when a UE in RRC_IDLE or RRC_INACTIVE state has a small amount of uplink data to send. The UE indicates its capability and intent to use CP-EDT within the RRCConnectionResumeRequest or RRCConnectionRequest message (via a specific establishment cause). The network authorizes the procedure based on subscription data and network policies. The actual user data is then encapsulated within a NAS message, specifically the UL NAS TRANSPORT message, which is carried transparently by the RAN to the core network.
The core network node (MME/AMF) extracts the user data from the NAS container and forwards it to the appropriate User Plane Function (UPF) or Serving Gateway (SGW) for delivery to the application server. For downlink response data, the process can work in reverse, with the core network including the downlink packet within a NAS message (DL NAS TRANSPORT) sent in the RRCConnectionRelease message, which carries the UE back to idle/inactive state. This entire transaction is secured using the existing NAS security context (integrity protection and ciphering), ensuring data confidentiality without the need to establish separate AS security. A key enabler is the pre-established UE context stored in both the RAN and the Core Network, which contains necessary security and capability information, allowing the procedure to be executed rapidly.
CP-EDT's role is to minimize the signaling footprint and latency for sporadic data transfers. It is tightly coupled with features like RRC Inactive state and UE Assistance Information, where the UE can indicate its expected data traffic pattern. The RAN decides whether to grant CP-EDT based on factors like data size (with a maximum transport block size limit), radio conditions, and network load. By collapsing data transmission into the connection resume/setup and release signaling, it reduces the number of required signaling messages by approximately half compared to a conventional service request procedure, leading to direct benefits in network efficiency, UE battery life, and air interface resource utilization for the massive scale envisioned for IoT deployments.
Purpose & Motivation
CP-EDT was created to address the fundamental inefficiency of using legacy LTE/5G connection procedures for Internet of Things (IoT) and Machine-Type Communication (MTC) devices. These devices, such as sensors, meters, and trackers, typically generate very small data payloads (e.g., a few tens or hundreds of bytes) at infrequent intervals (e.g., hourly or daily). The traditional mobile-originated data transfer requires a UE in idle mode to perform a full service request procedure: establishing an RRC connection, performing NAS signaling for service request, activating AS security, and setting up at least one data radio bearer. This process involves 10-15 signaling messages before the first bit of application data is sent, making the signaling overhead vastly disproportionate to the payload size. This is wasteful of radio resources, increases UE power consumption, and limits the number of devices a cell can support.
The historical context stems from 3GPP's work on LTE enhancements for MTC (eMTC) in Release 13 and subsequent releases. While features like Power Saving Mode (PSM) and Extended Discontinuous Reception (eDRX) were developed to reduce device energy consumption in idle mode, the signaling overhead during active transmission remained a major bottleneck. CP-EDT, introduced in Release 15 as part of the broader Early Data Transmission (EDT) framework, directly attacks this overhead problem. It was motivated by the need to support Massive IoT (mMTC) as a key 5G use case, requiring the network to handle millions of low-cost, battery-efficient devices per square kilometer.
CP-EDT solves the problem by re-purposing the control plane, which is inherently optimized for reliable, secure, and efficient signaling transport, to carry small user data packets. This leverages the existing security and reliability mechanisms of NAS signaling. It addresses the limitations of previous approaches where the only option was the lengthy user-plane path. By minimizing the time the radio is active and reducing the number of processing steps required in both the UE and network, CP-EDT dramatically extends battery life—often by years for devices with long sleep intervals—and increases network capacity for IoT traffic, enabling the scalable deployment envisioned for smart cities, utilities, and agriculture.
Key Features
- Transmits user data piggybacked on NAS signaling messages (UL/DL NAS TRANSPORT)
- Eliminates the need to establish a Data Radio Bearer (DRB) for small packets
- Utilizes existing NAS security context for integrity protection and ciphering
- Triggered via specific RRC establishment cause (e.g., mo-Data, mo-ExceptionData, delayTolerant)
- Defines a maximum transport block size limit for uplink data to qualify
- Supports both uplink-only and uplink-with-downlink response transaction models
Evolution Across Releases
Introduced the foundational CP-EDT procedure for LTE (NB-IoT and eMTC). Defined the mechanism for uplink data transmission within the RRC Connection Resume procedure for UEs in RRC_IDLE with a suspended RRC context. Established the use of the UL NAS TRANSPORT message to carry user data and the network's ability to respond with downlink data in the RRC Connection Release message. Set initial maximum data size limits.
Enhanced CP-EDT for 5G NR, integrating it with the RRC_INACTIVE state. Introduced support for CP-EDT during the initial RRC Setup procedure (for UEs without a stored context). Added improvements for reliability and expanded the applicable scenarios. Aligned the procedures between LTE and NR for consistent IoT device behavior.
Further optimized CP-EDT for enhanced coverage and power efficiency. Introduced support for CP-EDT with 2-step Random Access Channel (RACH) in NR, reducing access latency. Defined enhancements for downlink-heavy IoT applications and improved coexistence with other IoT features like Wake-Up Signal (WUS).
Focused on network energy savings and system capacity enhancements for CP-EDT. Introduced more dynamic network control over EDT parameters based on load and device type. Explored tighter integration with network slicing for IoT and enhancements for mobile IoT devices (e.g., trackers).
Continued evolution for extreme IoT requirements, investigating support for even smaller signaling footprints and latency reductions. Worked on enhancements for CP-EDT in non-terrestrial networks (NTN) and for redundancy/reliability in industrial IoT scenarios. Explored AI/ML-based network optimization for EDT parameter configuration.
Defining Specifications
| Specification | Title |
|---|---|
| TS 24.301 | 3GPP TS 24.301 |
| TS 36.331 | 3GPP TR 36.331 |