Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

LLC

Logical Link Control

Protocol →

LLC is the Logical Link Control sublayer of the data link layer in 3GPP systems like GPRS and UMTS, providing multiplexing, flow control, and error recovery for logical links between the mobile station and SGSN.

Introduced
R97
Where
Core Network › Legacy Core
Specifications
28 specs
Also in
Radio Access Network, Services, Management
LLC Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

TR 21.905Rel-17 → Rel-18

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 →
TS 23.018Rel-18 → Rel-19

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 →

Technology family

Radio user-plane layer 2 protocols · Radio Access Network

  1. Phase 1 RLP
  2. R97 LLC, SNDCP
  3. R99 UTRA MAC, UTRA PDCP, UTRA RLC
  4. Rel-8 E-UTRA MAC, E-UTRA PDCP, E-UTRA RLC
  5. Rel-15 NR MAC, NR PDCP, NR RLC, NR SDAP

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 9 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R97 introduced

Introduced in R97 (release dating of the term; no individual change cited).

Rel-4 specification text

TS 44.064 text appears for the first time in this release, specifying the LLC sublayer: HDLC-based procedures, acknowledged and unacknowledged modes, and a reliable MS-SGSN logical link with ciphering.

  • “LLC shall provide a highly reliable logical link between the MS and the SGSN.” TS 44.064 v4.4.0
  • “LLC shall support both acknowledged and unacknowledged data transfers.” TS 44.064 v4.4.0
  • “LLC shall provide user data confidentiality by means of a ciphering function.” TS 44.064 v4.4.0
Rel-6 specification text

LLC gained PS handover support in Rel-6: new LLGMM-PSHO primitives for local TLLI, IOV-UI selection and ciphering, plus LLC parameter reset handling after PS handover.

  • “LLGMM-PSHO-REQ shall be used by GMM to provide LLC with the local TLLI to be associated with the mobile station in the new cell.” TS 44.064 v6.3.0
  • “the MS shall perform the actions described above and shall send the XID response on one of the active SAPIs once the PS handover procedure has been successfully completed” TS 44.064 v6.3.0
  • “LLGMM-PSHO-IND shall be used by LLC to indicate the Ciphering Algorithm.” TS 44.064 v6.3.0
Rel-7 specification text

GSM 44.064 added LLC procedures for XID reset without old XID indicator and use of the LLC UI dummy command, changing LLC layer parameter negotiation behaviour.

  • “If Reset of LLC layer paramers and layer-3 parameters without old XID indicator has been performed, following the sending of the XID response” TS 44.064 v7.4.0
  • “the LLE shall proceed according to the negotiation of LLC layer and layer-3 parameters described in the subclause 8.5.3.” TS 44.064 v7.4.0
Rel-8 specification text

Rel-8 24.008 lists a change titled 'Removal of LLC Acknowledged mode', altering LLC's supported operation, and adds an 'LLC or SNDCP failure' cause value.

Rel-9 specification text

LLC's ciphering interface was extended to support GEA algorithms with 128-bit keys (Kc128), with GMM now indicating the GEA algorithm and Kc or Kc128 to LLC.

  • “This annex specifies how LLC shall interface with the GPRS ciphering algorithm.” TS 44.064 v9.1.0
  • “It is further used to assign the ciphering key (Kc or Kc128) and the ciphering algorithm.” TS 44.064 v9.1.0
  • “the GMM layer shall also notify the LLC sublayer which GEA algorithm and which ciphering key (i.e. GPRS GSM ciphering key or GPRS GSM Kc128)” TS 24.008 v9.13.0
Rel-10 specification text

The LLC SAPI rule changed from 'capable of both A/Gb and Iu mode' to 'capable of A/Gb mode' versus not capable, which now also covers S1-mode-capable MSs.

  • “An MS, which is capable of operating in A/Gb mode, shall use a valid LLC SAPI, while an MS which is not capable of operating in A/Gb mode” TS 24.008 v10.16.0
  • “An MS, which is capable of operating in both A/Gb mode and Iu mode, shall use a valid LLC SAPI” TS 24.008 v10.16.0
Rel-11 specification text

The 44.064 text added in Rel-11 states that LLC acknowledged mode is optional, a change to the LLC sublayer's own capability requirements.

Rel-13 specification text

Rel-13 adds integrity protection to the LLC layer: a MAC field in the frame format, i-IOV-UI negotiation in XID, and GMM-controlled activation of LLC integrity protection.

  • “The LLC layer may provide integrity protection of the frame header and the information field of data frames:” TS 44.064 v13.6.0
  • “LLGMM-RESET-REQ shall be used to order LLC in the SGSN to perform an XID negotiation of Reset and IOV‑UI (if ciphering is used)” TS 44.064 v13.6.0
  • “The GMM layer activates integrity protection in the LLC layer by providing an indication when integrity protection shall be started.” TS 24.008 v13.13.0

Defining Specifications

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

SpecificationTitleRelease
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 GTP-Based S2a for WLAN-EPC 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