Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

Msg3

Message 3 (Random Access Procedure)

Radio Access Network →

Msg3 is the third message of the random access procedure, transmitted on UL-SCH, and carries a C-RNTI MAC CE or a CCCH SDU, optionally multiplexed with DTCH for UP-EDT, and is associated with the UE Contention Resolution Identity.

Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Specifications
3 specs
Msg3 Description Purpose What changed Detected Changes Specifications

Description

Msg3 is the third message of the 3GPP random access (RA) procedure, transmitted by the UE on the Uplink Shared Channel (UL-SCH) after receiving the Random Access Response (Msg2). It is defined in TS 36.321 (LTE MAC), TS 38.321 (NR MAC), and described at stage 2 in TS 38.300. Msg3 is the first message in the RA procedure that is scheduled by an uplink grant rather than transmitted on the random access channel, and it is the message that allows the network to identify the UE and resolve contention.

The content of Msg3 depends on the type of random access procedure. In a contention-based random access (CBRA) procedure, Msg3 carries either a C-RNTI MAC Control Element (when the UE already has a valid C-RNTI, e.g. during RRC reconfiguration or after beam failure recovery) or a Common Control Channel (CCCH) Service Data Unit (when the UE is establishing an RRC connection and does not yet have a C-RNTI). The CCCH SDU typically contains an RRCConnectionRequest (LTE) or RRCSetupRequest (NR). Since Release 15, Msg3 may also optionally multiplex a Dedicated Traffic Channel (DTCH) SDU for User Plane Early Data Transmission (UP-EDT), allowing small user data payloads to be sent before the RRC connection is fully established.

Msg3 is associated with the UE Contention Resolution Identity. The network uses the Msg3 content to resolve contention among multiple UEs that may have selected the same random access preamble. In the contention resolution procedure, the network echoes the CCCH SDU (or part of it) in Msg4, and the UE compares the received Contention Resolution Identity with the one it transmitted in Msg3. If they match, the UE considers contention resolved and the RA procedure successful. If the UE transmitted a C-RNTI MAC CE in Msg3, contention resolution is instead based on the C-RNTI in the PDCCH addressed to that C-RNTI.

In NR, Msg3 is transmitted on the PUSCH using the uplink grant provided in the Random Access Response, and its transmission is subject to timing alignment and power control rules. The size of Msg3 is limited by the grant size and by the configured maximum message size; if the CCCH SDU does not fit, segmentation or a different RA procedure may be required. Msg3 also plays a role in the 2-step random access procedure (MsgA), where the equivalent payload is transmitted together with the preamble in MsgA rather than as a separate Msg3.

Msg3 is a critical point in the RA procedure because it is where the UE first provides its identity to the network and where contention is ultimately resolved. Its correct design and handling are essential for reliable connection establishment, mobility, and recovery procedures in both LTE and NR.

Purpose & Motivation

The random access procedure exists so that a UE can obtain uplink synchronisation and a valid uplink grant before transmitting scheduled data. In the earliest LTE releases, the procedure was designed with four messages: Msg1 (preamble), Msg2 (Random Access Response), Msg3 (scheduled uplink transmission), and Msg4 (contention resolution). Msg3 was created to carry the UE's identity or connection request in a scheduled, grant-based manner, which is more spectrally efficient and reliable than transmitting identity information on the random access channel itself.

Msg3 solves the contention problem: multiple UEs may select the same preamble, so the network needs a subsequent message to distinguish them. By carrying either a C-RNTI MAC CE or a CCCH SDU, Msg3 lets the network identify the UE and echo the identity back in Msg4 for contention resolution. This design has remained stable across LTE and NR because it balances simplicity, robustness, and efficiency.

The Release 15 enhancement to allow DTCH multiplexing for UP-EDT addressed the limitation that small data transmissions required a full connection establishment. By permitting user data in Msg3, 3GPP enabled early data transmission for CIoT and reduced signalling overhead and latency for small-payload applications.

What changed in its specifications

The latest release-to-release comparison of specifications that define Msg3. Each summary describes the whole specification, not only this term.

TS 36.321Rel-18 → Rel-19

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 →
TS 38.300Rel-18 → Rel-19

Rel-19 adds multi-hop L2 UE-to-Network relay for NR sidelink as the largest item. It also adds low-power wake-up signal and receiver (LP-WUS/WUR) text, on-demand SSB and SIB1 for network energy savings, and sub-band full duplex for TDD carriers.

Full comparison in TS 38.300 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 6 changes
  • Corrections to EDT for definition, Msg3, preambles, and MAC header structure TS 36.321CR1363
  • Msg3 buffer handling for EDT in 36.321 TS 36.321CR1384
  • Msg3 handling for switching from CBRA to CFRA TS 38.321CR0303
  • Correction for Msg3 grant overlapping with another UL grant TS 38.321CR0421
  • Handling of Msg3 size allocated by RAR mismatch during CBRA procedure TS 38.321CR0575
  • Clarification on RA and Msg3 with PUSCH Enhancements TS 36.321CR1457
Rel-19 3 changes
  • Corrections for CB-MSG3 EDT TS 36.321CR1599
  • Corrections on IoT NTN TDD for CB-Msg3 EDT and DRX TS 36.321CR1600
  • Corrections for CB-MSG3-EDT TS 36.321CR1601

Defining Specifications

3GPP specifications that define or reference Msg3, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 36.321 vj30 E-UTRA MAC Protocol Specification Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.321 vj40 NR MAC Protocol Specification Rel-19 read