Description
CB-Msg4 is the network response message to one or more contention-based Msg3 transmissions in LTE, introduced in Rel-19 alongside CB-Msg3-EDT and specified in 3GPP TS 36.300, 36.321 and 36.331. In the contention-based early data transmission procedure, a UE in RRC_IDLE transmits its small data payload in a contention-based Msg3 without a preceding random access preamble and without receiving a random access response. Because multiple UEs may select the same contention-based uplink resource, the network must provide a response that acknowledges the Msg3 and resolves any contention. CB-Msg4 serves this role.
The message is transmitted by the eNB on the downlink shared channel and is handled at the MAC layer (TS 36.321), with RRC (TS 36.331) configuring the relevant parameters and the overall procedure. CB-Msg4 can respond to one or more CB-Msg3 transmissions, meaning the network may bundle acknowledgements for multiple UEs or multiple transmissions into a single response message. This bundling is efficient when several devices have transmitted on contention-based resources in the same time window.
Contention resolution is a key function of CB-Msg4. When two or more UEs transmit on the same contention-based resource, their Msg3 transmissions collide. The network decodes the received signal, identifies the UE(s) whose transmission was successfully received, and includes the corresponding UE identity in CB-Msg4. A UE that finds its identity in CB-Msg4 considers its transmission successful; a UE that does not find its identity assumes a collision and may retry according to the configured backoff and retransmission rules. This mechanism allows the network to recover from collisions without a separate random access procedure.
CB-Msg4 also carries the acknowledgement for the early data transmission, allowing the UE to complete the small data transfer while remaining in RRC_IDLE or transitioning as needed. The message may include timing advance information, uplink grants for subsequent transmissions, and other MAC control elements. Because the UE did not receive a random access response, CB-Msg4 may also need to provide the timing alignment information that would normally have been delivered in Msg2.
The design of CB-Msg4 reflects the trade-off between efficiency and reliability in contention-based access. By responding to multiple Msg3 transmissions in a single message, the network reduces downlink signaling overhead. At the same time, the contention resolution mechanism ensures that collisions are detected and resolved, maintaining reliability for the data transfer. CB-Msg4 is therefore an essential complement to CB-Msg3-EDT, completing the contention-based early data transmission procedure.
Purpose & Motivation
CB-Msg4 exists to provide a reliable downlink response and contention resolution mechanism for contention-based Msg3 early data transmissions. When a UE transmits data in a contention-based Msg3 without a random access preamble and response, the network needs a way to acknowledge successful reception and to resolve collisions that occur when multiple UEs use the same resource. CB-Msg4 fulfills both roles in a single message.
In legacy random access, contention resolution is performed through Msg4 after a preamble-based Msg3. The preamble helps the network distinguish UEs and allocate resources, reducing collision probability. In CB-Msg3-EDT, the preamble step is removed, so collisions are more likely and must be handled explicitly. CB-Msg4 provides the UE identity echo and acknowledgement needed for each UE to determine whether its transmission succeeded.
The ability of CB-Msg4 to respond to one or more CB-Msg3 transmissions is motivated by efficiency. In dense IoT deployments, many devices may transmit small data packets in a short period. Bundling responses into a single CB-Msg4 reduces downlink control overhead and improves spectral efficiency. This design supports the goal of CB-Msg3-EDT to enable low-latency, low-energy small data transmission at scale, while maintaining the reliability required for network operation.
What changed in its specifications
The latest release-to-release comparison of specifications that define CB-Msg4. 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 (1 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-Msg4, 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 |