Description
CB-Msg3 is a Rel-19 concept defined in TS 36.300, TS 36.321, and TS 36.331 as part of the CB-Msg3-EDT (Contention-Based Msg3 Early Data Transmission) procedure. It refers to the message transmitted on the contention-based uplink shared channel (UL-SCH) during the random access procedure, carrying user data earlier than in conventional LTE access. The term is closely tied to the LTE random access channel (RACH) procedure, where Msg1 is the preamble, Msg2 is the random access response, Msg3 is the first scheduled uplink transmission, and Msg4 is the contention resolution message.
In the classical LTE random access procedure, Msg3 is transmitted on a grant provided in the random access response (Msg2). That grant is allocated from resources that may be shared among multiple UEs, and contention is resolved by Msg4. However, conventional EDT still relies on a grant scheduled by the network in Msg2.
CB-Msg3-EDT extends this idea to contention-based transmission on the UL-SCH. Instead of waiting for a dedicated grant, the UE transmits its Msg3 — including the early data — on contention-based resources. This is conceptually similar to the contention-based access mechanisms studied for latency reduction (e.g., grant-free or configured-grant transmission), but applied specifically to the Msg3 step of the random access procedure. The network must be able to detect and decode overlapping transmissions, resolve contention, and provide feedback. The procedure involves the UE selecting a contention-based resource, transmitting the CB-Msg3 with its data and identity, and the network responding with contention resolution and possibly an RRC connection setup or release depending on whether the data transfer completes the UE's needs.
Key components include the contention-based UL-SCH resource configuration, which the network broadcasts via system information (TS 36.331), the MAC procedures in TS 36.321 that govern resource selection, HARQ operation, and contention resolution, and the overall RRC and random access coordination described in TS 36.300. Because the transmission is contention-based, collision handling and fallback to grant-based procedures are essential. The UE must be able to detect failure (e.g., no contention resolution) and retry, potentially falling back to the conventional RACH procedure.
CB-Msg3-EDT is significant because it targets the latency and signalling overhead of small data transmissions in LTE-based IoT and MTC scenarios. By allowing data to be carried in a contention-based Msg3, it reduces the number of round trips needed to move a UE from idle to a data transfer and back, which is valuable for devices that transmit infrequently and in small bursts. As a Rel-19 feature, it reflects the continued evolution of LTE to support massive IoT and latency-sensitive small-data applications even as 5G NR becomes dominant.
Purpose & Motivation
CB-Msg3 exists to reduce the latency and signalling overhead of small data transmissions in LTE. Conventional random access requires a multi-step exchange — preamble, random access response, scheduled Msg3, contention resolution — before an RRC connection is established and data can flow. For machine-type devices that send small, infrequent payloads, this overhead is disproportionate to the data volume and consumes both radio resources and device battery.
Early Data Transmission (EDT) in Rel-15 addressed part of this by allowing data in Msg3, but still depended on a network-scheduled grant in Msg2. CB-Msg3-EDT goes further by permitting contention-based transmission of Msg3, removing the dependency on a dedicated grant and potentially shortening the procedure. This is motivated by the need to support massive numbers of IoT devices with bursty, small data in a resource-efficient way, and by latency-reduction goals for MTC.
The feature builds on earlier 3GPP work on contention-based access and grant-free transmission studied for latency reduction. It addresses the limitation that grant-based Msg3 requires the network to allocate resources per UE, which scales poorly with device density. By allowing contention-based Msg3 with proper contention resolution and fallback mechanisms, the network can support more efficient small-data access while retaining reliability through HARQ and retransmission procedures.
What changed in its specifications
The latest release-to-release comparison of specifications that define CB-Msg3. Each summary describes the whole specification, not only this term.
Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.
Full comparison in TS 36.300 →Rel-19 adds to TS 36.321 a contention-based Msg3 early data transmission (CB-Msg3-EDT) procedure, along with new definitions and abbreviations. This is the only feature overview provided, so no other additions can be named.
Full comparison in TS 36.321 →Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference CB-Msg3, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.321 vj30 | E-UTRA MAC Protocol Specification | Rel-19 read |
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |