Description
The Radio Link Control (RLC) sublayer is a key component of the Layer 2 protocol stack in 3GPP radio access networks, including UMTS, LTE, and NR. Positioned between the Medium Access Control (MAC) layer below and the Packet Data Convergence Protocol (PDCP) layer above, RLC is responsible for reliable data transfer over the radio link. It operates in three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM), each tailored to different service requirements. In TM, RLC passes data without adding headers, used for delay-sensitive services like voice. In UM, it provides segmentation and reassembly with sequence numbering but no retransmissions, suitable for streaming or broadcast. In AM, it adds error correction through Automatic Repeat Request (ARQ), ensuring reliable delivery for data services. RLC works by receiving service data units (SDUs) from PDCP, segmenting or concatenating them into protocol data units (PDUs) for transmission via MAC. It manages buffers, handles retransmissions in AM, and ensures in-sequence delivery to upper layers. Key components include the RLC entity, which maintains state variables and timers, and the RLC bearer, which corresponds to a logical channel. RLC interacts with MAC for scheduling and HARQ, adapting to radio conditions to optimize throughput and latency. Its role is fundamental in mitigating errors from the physical layer, supporting QoS differentiation, and enabling efficient use of radio resources across evolving 3GPP technologies.
Purpose & Motivation
The RLC protocol was created to address the inherent unreliability and variability of wireless radio links, which are prone to errors, delays, and packet loss due to fading, interference, and mobility. In early cellular systems, simple data transfer mechanisms were insufficient for supporting diverse services like voice, video, and internet access with varying reliability and latency needs. RLC solves this by providing a flexible, mode-based framework that ensures data integrity and order, adapting to service requirements. Historically, before 3GPP standardization, proprietary solutions led to interoperability issues. RLC, introduced in R99, established a unified approach for UMTS, evolving through releases to handle increased data rates and new use cases in LTE and NR. It addresses limitations of lower-layer protocols like PHY and MAC, which lack end-to-end reliability mechanisms, by offering ARQ and segmentation capabilities. The motivation was to enable efficient, reliable communication over the air interface, supporting the growth from circuit-switched voice to packet-switched multimedia, and later to 5G's ultra-reliable low-latency communications. RLC remains essential for maintaining link quality and enabling advanced features like carrier aggregation and dual connectivity.
Key Features
- Three operational modes: Transparent, Unacknowledged, and Acknowledged
- Segmentation and reassembly of data units for efficient transmission
- Error correction via ARQ in Acknowledged Mode
- In-sequence delivery and duplicate detection
- Buffer management for flow control and retransmissions
- Support for diverse QoS requirements across services
Evolution Across Releases
Initial introduction of RLC in UMTS, defining the three modes (TM, UM, AM) and basic procedures for reliable data transfer over WCDMA air interface. Established segmentation, ARQ, and in-order delivery as core functions for Layer 2 in 3GPP networks.
Defining Specifications
| Specification | Title |
|---|---|
| TS 03.071 | 3GPP TR 03.071 |
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.050 | 3GPP TS 23.050 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.107 | 3GPP TS 23.107 |
| TS 23.146 | 3GPP TS 23.146 |
| TS 23.207 | 3GPP TS 23.207 |
| TS 23.221 | 3GPP TS 23.221 |
| TS 23.910 | 3GPP TS 23.910 |
| TS 23.979 | 3GPP TS 23.979 |
| TS 25.201 | 3GPP TS 25.201 |
| TS 25.221 | 3GPP TS 25.221 |
| 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.423 | 3GPP TS 25.423 |
| TS 25.912 | 3GPP TS 25.912 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.804 | 3GPP TS 26.804 |
| TS 26.822 | 3GPP TS 26.822 |
| TS 26.902 | 3GPP TS 26.902 |
| TS 26.926 | 3GPP TS 26.926 |
| TS 26.935 | 3GPP TS 26.935 |
| TS 26.937 | 3GPP TS 26.937 |
| TS 29.163 | 3GPP TS 29.163 |
| TS 29.235 | 3GPP TS 29.235 |
| TS 33.105 | 3GPP TR 33.105 |
| TS 36.201 | 3GPP TR 36.201 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.306 | 3GPP TR 36.306 |
| TS 36.322 | 3GPP TR 36.322 |
| TS 36.323 | 3GPP TR 36.323 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.938 | 3GPP TR 36.938 |
| TS 37.320 | 3GPP TR 37.320 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 38.201 | 3GPP TR 38.201 |
| TS 38.306 | 3GPP TR 38.306 |
| TS 38.322 | 3GPP TR 38.322 |
| TS 38.323 | 3GPP TR 38.323 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.470 | 3GPP TR 38.470 |
| TS 43.051 | 3GPP TR 43.051 |
| TS 43.064 | 3GPP TR 43.064 |
| TS 43.129 | 3GPP TR 43.129 |
| TS 43.318 | 3GPP TR 43.318 |
| TS 43.902 | 3GPP TR 43.902 |
| TS 44.060 | 3GPP TR 44.060 |
| TS 44.160 | 3GPP TR 44.160 |
| TS 44.318 | 3GPP TR 44.318 |
| TS 45.902 | 3GPP TR 45.902 |
| TS 48.016 | 3GPP TR 48.016 |