L2

Layer 2 (Data Link Layer)

Protocol →
Introduced in R99 Also in: Services

L2 is the data link layer in the 3GPP protocol stack, responsible for reliable node-to-node data transfer, error and flow control, and is subdivided into the MAC, RLC, and PDCP sublayers.

Category
Protocol
Introduced
R99
Where
Radio Access Network › NG-RAN (5G)
Also touches
1 segments
Specifications
22 specs
L2 Description Purpose Specifications

Description

Layer 2, the Data Link Layer, in 3GPP systems is a complex protocol layer situated between the Physical Layer (L1) and the Network Layer (L3). It is responsible for the reliable and orderly transfer of data frames between two directly connected nodes—typically the User Equipment (UE) and the base station (NodeB, eNB, gNB). To manage its diverse responsibilities, 3GPP's Layer 2 is architecturally divided into three key sublayers: the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer. Each sublayer has distinct functions that collectively manage access to the shared medium, error correction, and data security.

The MAC sublayer is the lowest within L2. Its primary role is to control access to the shared radio resources. It performs logical channel multiplexing, mapping multiple logical channels (e.g., for different bearers or services) onto the available transport channels provided by the physical layer. The MAC layer also handles scheduling, where it decides which UE gets which radio resources and when, based on priorities and QoS requirements. It implements Hybrid Automatic Repeat Request (HARQ) for fast retransmissions at the physical layer level, providing a first line of defense against transmission errors.

Above MAC, the RLC sublayer operates in one of three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). Its core functions include segmentation and reassembly of higher-layer packets to fit the transport block size, concatenation, and in-order delivery. In AM, it provides reliable data transfer through its own ARQ mechanism, retransmitting any RLC Protocol Data Units (PDUs) that are not acknowledged by the receiver. This ensures data integrity where required. The topmost sublayer, PDCP, is responsible for header compression (using Robust Header Compression - ROHC) to improve spectral efficiency, ciphering and integrity protection for user and control plane data, and in-order delivery and duplicate removal during handovers. In 5G, PDCP also handles the duplication of data for ultra-reliable low-latency communication (URLLC) bearers.

Purpose & Motivation

Layer 2 exists to create a reliable communication link over the inherently unreliable physical layer. The physical layer transmits raw bits that are susceptible to errors, loss, and collisions in a shared medium. L2 solves these problems by implementing error control (via HARQ and RLC ARQ), flow control, and medium access coordination. Its creation was motivated by the need to support diverse services (voice, video, data) with different quality of service (QoS) requirements over a single radio interface.

Historically, the 3GPP L2 architecture evolved from the simpler L2 of GSM to the more sophisticated tri-sublayer structure in UMTS (R99), which was necessary to support packet-switched data services efficiently. The limitations of a single data link protocol were addressed by separating concerns: MAC for dynamic resource sharing, RLC for reliable segmentation and delivery, and PDCP for header efficiency and security. This modular design allowed each sublayer to be optimized independently across generations. For example, PDCP was enhanced in LTE to handle security for all traffic, and in 5G, it was further extended to support data duplication and more robust integrity protection, addressing the needs of new use cases like V2X and industrial IoT.

Evolution Across Releases

R99 Initial

Introduced the foundational three-sublayer L2 architecture for UMTS: MAC, RLC, and PDCP. Defined MAC for transport channel mapping and HARQ, RLC for segmentation and reliable transfer, and PDCP primarily for IP header compression. Established the framework for supporting both circuit-switched and packet-switched services.

Explore further

Broader topics and technologies where L2 plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TR 22.832 vh40 Study on cyber-physical control in vertical domains Rel-17
TS 25.201 vj00 UTRA Physical Layer General Description Rel-19
TS 25.222 vj00 UTRA TDD Multiplexing & Channel Coding Rel-19
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19
TS 25.302 vj00 UTRA Physical Layer Services Rel-19
TS 25.321 vj00 MAC Protocol Specification for UTRAN Rel-19
TS 25.322 vj00 RLC Protocol Specification Rel-19
TS 25.323 vj00 Packet Data Convergence Protocol (PDCP) Specification Rel-19
TS 25.324 vj00 Broadcast/Multicast Control Protocol Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 25.402 vj00 UTRAN Synchronisation Mechanisms Rel-19
TS 25.433 vj00 Node B Application Part (NBAP) Protocol Rel-19
TS 25.874 vb00 HSPA Feedback & Signalling Efficiency for LCR TDD Rel-11
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19
TR 26.937 vj00 3GPP PSS Characterization Rel-19
TS 29.274 vj50 GTPv2-C Control Plane Protocol Specification Rel-19
TS 33.836 vg10 Security Study for Advanced V2X Services Rel-16
TS 36.323 vj00 PDCP Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 36.938 v900 E-UTRAN to 3GPP2/Mobile WiMAX Mobility Rel-9
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.