Description
Logical Link Control (LLC) is a protocol sublayer defined in 3GPP specifications for GSM/GPRS and UMTS packet-switched services. It resides above the Medium Access Control (MAC) and Radio Link Control (RLC) sublayers and below the network layer (IP). The primary role of LLC is to provide a reliable logical link between the Mobile Station (MS) and the Serving GPRS Support Node (SGSN) across the Um/Gb (for GPRS) or Iu-PS (for UMTS) interfaces. It operates independently of the underlying radio technology, abstracting the details of the radio interface from the upper layers.
The LLC layer is responsible for several key functions. First, it provides multiplexing through Service Access Point Identifiers (SAPI), allowing multiple higher-layer entities (like different protocol stacks for signaling and user data) to share a single logical link. Second, it ensures data integrity and sequenced delivery through acknowledged mode operation, employing mechanisms like error detection (using Frame Check Sequences), retransmission (Go-Back-N ARQ), and flow control. In unacknowledged mode, it provides a simpler, connectionless service without retransmissions. The LLC frame structure includes fields for the destination and source addresses (typically derived from the MS's TLLI), control information for frame type (I, S, U frames), and the payload.
In the GPRS architecture, the LLC link extends from the MS to the SGSN. This means the LLC protocol is terminated at the SGSN, not at the Base Station Subsystem (BSS). This design allows mobility management (like routing area updates) to be handled transparently at the LLC layer without re-establishing the link. The BSS transparently relays LLC frames between the MS and SGSN using the BSS GPRS Protocol (BSSGP) over the Gb interface. In UMTS, a similar concept applies over the Iu-PS interface, though the RLC layer in UTRAN takes on more reliability functions.
With the evolution to LTE (EPS) and 5G (5GS), the LLC layer was made obsolete in the user plane. Its functions were redistributed or rendered unnecessary by more efficient protocols. Reliability and multiplexing are now primarily handled by the PDCP (Packet Data Convergence Protocol) and RLC layers in the radio protocol stack, which terminate at the base station (eNodeB/gNB), not the core network. However, LLC may still be referenced in legacy system specifications and for certain control plane aspects in earlier releases.
Purpose & Motivation
The LLC layer was created for GPRS to provide a reliable data link suitable for the characteristics of the early packet-switched cellular radio interface. The radio interface in 2G systems was prone to high error rates and variable delays. LLC was designed to shield upper-layer protocols (particularly IP, which assumes a relatively reliable link) from these radio-specific impairments by providing error correction, retransmission, and in-order delivery over the logical link between the MS and the core network node (SGSN).
A key problem LLC solved was supporting multiple concurrent packet data protocols (PDP contexts) over a single physical radio connection. Its multiplexing capability via SAPIs allowed a single MS to run different applications (e.g., IP, PPP) simultaneously. Furthermore, by terminating the logical link at the SGSN—a node that remains constant during intra-SGSN mobility—LLC provided a stable anchor point. This meant the logical connection could be maintained as the MS moved between different BTSs, simplifying mobility management compared to having the link break and re-establish with every cell change.
As radio technology advanced with 3G (UTRAN) and especially 4G (E-UTRAN), the underlying physical layer became more robust and capable of lower latency. The design philosophy shifted towards a flatter architecture with protocol termination at the base station to reduce latency and complexity. The functions of LLC were either integrated into the more efficient RLC/PDCP layers (which handle ARQ at the radio link) or became redundant. Therefore, while LLC was a critical enabler for early mobile data, its purpose was superseded by more integrated and optimized Layer 2 protocols in subsequent 3GPP generations, leading to its deprecation in the user plane for LTE and 5G NR.
What changed in its specifications
The latest release-to-release comparison of specifications that define LLC. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 23.018: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.018 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference LLC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.018 vj00 | Basic call handling in 3GPP CS domain | Rel-19 read |
| TS 23.050 | 3GPP TS 23.050 | R99 read |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 read |
| TS 23.527 vk00 | 5G Restoration Procedures for N4 Interface | Rel-20 read |
| TS 23.725 vg20 | Study on URLLC Architecture Enhancements | Rel-16 read |
| TS 23.852 vc00 | Study on GTP-based S2a for WLAN Access | Rel-12 read |
| TR 23.923 v300 | Mobile IP+ Feasibility Study for UMTS/GPRS | R99 read |
| TS 24.065 v310 | GPRS Subnetwork Dependent Convergence Protocol | R99 read |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 read |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 read |
| TS 27.060 vj00 | TE-MT Interworking for Packet Domain | Rel-19 read |
| TS 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 read |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 read |
| TS 33.863 ve20 | Security for Battery-Efficient IoT Device to Enterprise | Rel-14 read |
| TS 43.064 vj00 | GPRS Radio Interface Lower-Layer Functions | Rel-19 read |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 read |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 read |
| TS 43.802 vc00 | GERAN Enhancements for Mobile Data Applications | Rel-12 read |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 read |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 read |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 read |
| TS 44.064 vj00 | GPRS Logical Link Control (LLC) Protocol | Rel-19 read |
| TS 44.065 vj00 | GPRS SNDCP Specification | Rel-19 read |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 read |
| TS 48.016 vj00 | Gb Interface Network Service Specification | Rel-19 read |
| TS 52.402 vj00 | GSM Performance Management Measurements | Rel-19 read |