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

Glossary term · Protocol

RLP

Radio Link Protocol

Protocol →

RLP is a data link layer protocol for GSM circuit-switched data that provides reliable, sequenced data transfer over the radio interface using error detection and retransmission.

Introduced
Phase 1
Where
Services › IMS
Specifications
8 specs
Also in
Radio Access Network
RLP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Radio Link Protocol (RLP) is a Layer 2 (Data Link Layer) protocol specified in GSM 04.22, designed to support transparent and non-transparent circuit-switched data (CSD) services over the GSM radio interface. It operates between the Mobile Station (MS) and the Interworking Function (IWF) in the network, typically located at the Mobile Switching Center (MSC). RLP's primary function is to transform the error-prone, raw radio channel into a virtual reliable data pipe. It achieves this through a frame-based structure and an Automatic Repeat Request (ARQ) mechanism. Data from the upper layer is segmented into RLP frames, each containing a header with sequence numbers and control information, and a payload. The protocol uses selective reject (SREJ) and reject (REJ) ARQ schemes for error recovery. If a frame is received in error or is missing, the receiver can request retransmission of specific frames, ensuring data integrity. RLP operates in three modes: Transparent Mode (where no ARQ is used, and errors are passed up), Non-Transparent Basic Mode (with ARQ), and Non-Transparent Extended Mode (with enhanced window sizes and features for higher throughput). The protocol manages flow control through its window mechanism, limiting the number of unacknowledged frames in transit. It also includes procedures for initialization, synchronization, and termination of the logical link. While primarily for circuit-switched bearers, RLP's concepts influenced later packet-switched protocols. Its operation is largely invisible to the end-user application, which interacts with higher-layer protocols like PPP that run over the RLP-established link.

Purpose & Motivation

RLP was created to enable reliable data communication over the GSM network's radio interface, which is susceptible to fading, interference, and high bit error rates (BER). Before digital cellular systems, data services were impractical. GSM's digital nature opened the possibility, but the raw radio channel was unsuitable for applications like fax, modem dial-up, and early mobile data terminals that required low error rates. The protocol solved this by implementing a robust ARQ mechanism at the link layer, shielding higher-layer protocols from radio-induced errors. It addressed the limitations of a purely transparent channel, which would have rendered many data applications unusable due to corruption. RLP was a cornerstone of GSM Phase 2+ data services, enabling the first wave of mobile data before the advent of GPRS and packet-switching. Its development was motivated by the need to provide a standardized, reliable data bearer service that could interwork with the existing PSTN/ISDN data world, facilitating services like circuit-switched fax and video telephony as defined in 3GPP releases.

What changed in its specifications

The latest release-to-release comparison of specifications that define RLP. 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.271Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.271: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.271 →

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 4 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.

Phase 1 introduced

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

R99 specification text

TS 24.022 first specifies the Radio Link Protocol for circuit-switched data in GSM and UMTS, covering Layer 2 framing, multi-link substreams, REMAP and DTX handling.

  • “The present document specifies the Radio Link Protocol (RLP) for circuit switched data transmission within the GSM and UMTS PLMN.” TS 24.022 v3.5.0
  • “RLP uses one physical link (single-link) or from 1 up to 4 (multi-link) substreams on one or more physical links.” TS 24.022 v3.5.0
Rel-4 specification text

TS 23.146 first appears in Rel-4 and specifies how RLP is used for facsimile over GSM, including its establishment across the radio interface, ARQ error recovery with SREJ, and flow control between RLP entities.

  • “Furthermore, the RLP entity shall be able to make error recovery by using the SREJ command/response.” TS 23.146 v4.1.0
  • “This specifically applies between RLP entities, L2RCOP (within TAF) entities, and between the FA and the TAF entities within the UE or the IWF.” TS 23.146 v4.1.0
  • “The protocol stack at the radio interface, however, is not affected by this consideration, i.e. RLP and L2RCOP always apply.” TS 23.146 v4.1.0
Rel-5 specification text

TS 24.022 RLP was revised for UTRAN Iu mode: only 576-bit frames there, REMAP optional for Iu-only entities, any RLP version may be requested, and multi-link/version rules were reworded.

  • “RLP entities running only in an UTRAN Iu mode environment need only to support the 576 bit frame length. The REMAP function is not necessary.” TS 24.022 v5.5.0
  • “In UTRAN Iu mode, either end is allowed to request the usage of any RLP‑version.” TS 24.022 v5.5.0
  • “In UTRAN Iu mode, the RLP frame size does not depend on the channel coding, only 576 bit frames are used.” TS 24.022 v5.5.0

Defining Specifications

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

SpecificationTitleRelease
TS 03.071 v890 GSM Location Services Stage 2 R99 read
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.146 vj00 3G Facsimile Group 3 Technical Realization Rel-19 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TR 23.910 v550 CS Bearer Services in UMTS Rel-5 read
TS 24.022 vj00 Radio Link Protocol (RLP) for Circuit Switched Data Rel-19 read
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19 read
TS 27.007 vk00 AT Command Interface for Mobile Terminals Rel-20 read