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.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (90 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, specific corrections and clarifications were introduced for the RLC function, including a correction on the Sequence Number (SN) size for RLC Acknowledged Mode and a clarification on the RLC Unacknowledged Mode SN size for NB-IoT. Furthermore, the release introduced a procedure for reporting RLC failures and addressed the association of PDCP with RLC for radio bearers configured with PDCP duplication.
- Introduction of New Radio Access Technology in TS 36.300 TS 36.300CR0998
- Control Plane latency reduction TS 36.306CR1614
- EN-DC impacts to LTE RLC TS 36.322CR0132
- Control Plane latency reduction TS 36.331CR3453
- Introduction of support for MAC PDU containing UE contention resolution identity MAC control element without RRC response message in NB-IoT TS 36.306CR1570
- Correction on SN size for RLC AM TS 36.322CR0141
+ 27 more changes
In Release 16, the RLC function was enhanced to support new deployment scenarios, including the introduction of a Backhaul (BH) RLC Channel for Integrated Access and Backhaul (IAB) nodes and corrections to support the BAP as an upper layer. It also introduced specific handling for transmission suspension on BH RLC channels upon IAB-MT failure and clarified procedures for RLC out-of-order delivery configuration. Furthermore, security risks for RLC AM and UM bearers during termination point changes were addressed, and RLC re-establishment procedures upon RRC resume/reestablishment were defined.
- UE radio access capabilities introduction for IIOT WI (CR for 36.306) TS 36.306CR1758
- Introducing UE Radio Capability Mapping procedure for EN-DC TS 36.300CR1314
- Incorrect restriction for RLC UM radio bearers TS 36.331CR4385
- Addition of total L2 buffer size and RLC RTT for NR SL TS 38.306CR0547
- Correction on RLC spec to support the BAP as upper layer TS 38.322CR0036
- CR to 38.322 on Backhaul RLC Channel TS 38.322CR0037
+ 14 more changes
In Release 17, the RLC function saw specific corrections and clarifications, primarily focused on sidelink relay operation and bearer configuration. The changes included corrections for establishing the receiving RLC entity for SL-SRB0 and SL-SRB1, as well as a clarification on RLC bearer re-association procedures. These updates provided necessary refinements to support sidelink relay functionality and ensure correct RLC entity handling.
- Correction on PDCP Control PDU for UDC feedback TS 36.323CR0304
- Correction on RLC for SL relay TS 38.322CR0048
- RLC correction for SL relay TS 38.322CR0050
- Correction on PDCP Control PDU for UDC feedback TS 38.323CR0105
- Corrections to control plane procedures for RedCap UEs TS 38.331CR3780
- Channel Access Control for msg1/msgA in FR2-2 TS 38.331CR3827
+ 7 more changes
In Release 18, the RLC (Radio Link Control) layer was enhanced to support new functionalities like Network-Controlled Repeaters and multi-path relay, requiring specific corrections for RLC handling in these scenarios. The release also introduced updates for sidelink (PC5) communication, including corrections to RLC channel handling and release procedures. Furthermore, RLC was adapted to work with the unified Transmission Configuration Indicator (TCI) state framework, necessitating corrections for power control parameters and interactions with PDCP, such as the delay critical indication.
- Introduction of Rel-18 network-controlled repeaters TS 38.201CR0004
- Introduction of Network Controlled Repeaters in RRC spec TS 38.331CR4162
- RLC correction for multi-path relay with N3C TS 38.322CR0063
- Data volume calculation for DSR when associated with at least two RLC entities TS 38.323CR0133
- Correction for Delay Critical Indication from PDCP to RLC TS 38.323CR0144
- Miscellaneous RRC corrections for Network-controlled repeaters TS 38.331CR4617
+ 10 more changes
In Release 19, the RLC (Radio Link Control) function was enhanced to support Extended Reality (XR) traffic, with the specification receiving dedicated corrections and updates for these R19 XR enhancements. The release also included corrections for the PC5 Relay RLC channel configuration. No changes related to positioning parameters or power control, as indicated in some titles, were made to the RLC layer itself, as those pertain to other protocol layers.
- Introduction of control parameters for on-demand posSIB request [OdPosSIB_Req] TS 38.306CR1323
- Introduction of R19 XR enhancements for RLC spec. TS 38.322CR0065
- Introduction of control parameters for on-demand posSIB request [OdPosSIB_Req] TS 38.331CR5406
- Miscellaneous corrections on RLC for R19 XR TS 38.322CR0066
- Miscellaneous corrections on RLC for R19 XR TS 38.322CR0067
- Correction on PC5 Relay RLC channel configuration TS 38.331CR5510
+ 2 more changes
Explore further
Broader topics and technologies where RLC plays a role.
Defining Specifications
3GPP specifications that define or reference RLC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 03.071 v7b0 | Location Services (LCS) Stage 2 Description | Rel-7 |
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.050 v1100 | UMTS Network Principles and Architecture | R99 |
| TS 23.060 vj00 | GPRS Service Description Stage 2 | Rel-19 |
| TS 23.107 vj00 | UMTS QoS Framework | Rel-19 |
| TS 23.146 vj00 | 3G Facsimile Group 3 Technical Realization | Rel-19 |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 |
| TR 23.910 v1400 | UMTS Circuit Switched Bearer Services Overview | Rel-5 |
| TR 23.979 vj00 | PoC over 3GPP Systems Architectural Requirements | Rel-19 |
| TS 25.201 vj00 | UTRA Physical Layer General Description | Rel-19 |
| TS 25.221 vj00 | UTRA TDD Physical Layer Specification | 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.423 vj00 | UTRAN RNSAP Specification | Rel-19 |
| TR 25.912 vj00 | Evolved UTRA and UTRAN Technical Report | Rel-19 |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 26.822 vj20 | 5G RTP Configurations Study Phase 2 | Rel-19 |
| TR 26.902 vj00 | Video Codec Performance for 3GPP Packet Services | Rel-19 |
| TR 26.926 vj00 | Traffic Models & Quality Evaluation for Media/XR in 5G | Rel-19 |
| TR 26.935 vj00 | Speech Codec Performance for Packet Switched Multimedia | Rel-19 |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 |
| TS 29.163 vj00 | Interworking between 3GPP IM CN and CS networks | Rel-19 |
| TS 29.235 vj00 | SIP-I CS Core Network Interworking | Rel-19 |
| TS 33.105 vj00 | 3G Security: Cryptographic Algorithm Requirements | Rel-19 |
| TS 36.201 vj00 | LTE Physical Layer General Description | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.302 vj00 | E-UTRA Physical Layer Services | Rel-19 |
| TS 36.306 vj00 | E-UTRA UE Radio Access Capability Parameters | Rel-19 |
| TS 36.322 vj00 | E-UTRA Radio Link Control Protocol Specification | Rel-19 |
| 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 37.320 vj00 | Minimization of Drive Tests (MDT) Overview | Rel-19 |
| TR 37.901 vf10 | UE Application Layer Data Throughput Performance | Rel-15 |
| TS 38.201 vj00 | NR Physical Layer General Description | Rel-19 |
| TS 38.306 vj00 | NR UE Radio Access Capability Parameters | Rel-19 |
| TS 38.322 vj00 | NR Radio Link Control (RLC) Protocol | Rel-19 |
| TS 38.323 vj00 | Packet Data Convergence Protocol (PDCP) | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TS 38.470 vj10 | F1 Interface Introduction | Rel-19 |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | Rel-19 |
| TS 43.064 vj00 | GPRS Radio Interface Lower-Layer Functions | Rel-19 |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 |
| TR 45.902 vj00 | Flexible Layer One (FLO) for GERAN | Rel-19 |
| TS 48.016 vj00 | Gb Interface Network Service Specification | Rel-19 |