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.
Key Features
- Structured into MAC, RLC, and PDCP sublayers with distinct functions
- MAC handles dynamic scheduling, logical channel multiplexing, and HARQ
- RLC provides segmentation, ARQ-based error correction, and in-order delivery
- PDCP performs header compression, ciphering, and integrity protection
- Supports multiple RLC modes (TM, UM, AM) for different service requirements
- Manages data transfer during handover (PDCP reordering, duplication in 5G)
Evolution Across Releases
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.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.832 | 3GPP TS 22.832 |
| TS 25.201 | 3GPP TS 25.201 |
| TS 25.222 | 3GPP TS 25.222 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.302 | 3GPP TS 25.302 |
| TS 25.321 | 3GPP TS 25.321 |
| TS 25.322 | 3GPP TS 25.322 |
| TS 25.323 | 3GPP TS 25.323 |
| TS 25.324 | 3GPP TS 25.324 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.402 | 3GPP TS 25.402 |
| TS 25.433 | 3GPP TS 25.433 |
| TS 25.874 | 3GPP TS 25.874 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.937 | 3GPP TS 26.937 |
| TS 29.274 | 3GPP TS 29.274 |
| TS 33.836 | 3GPP TR 33.836 |
| TS 36.323 | 3GPP TR 36.323 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.938 | 3GPP TR 36.938 |
| TS 38.331 | 3GPP TR 38.331 |