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

Glossary term · Protocol

RRLP

Radio Resource LCS Protocol

Protocol →

RRLP is the Radio Resource LCS Protocol used in GSM and UMTS networks to exchange location information between a Mobile Station and the network, supporting methods like Cell-ID, OTDOA, and A-GPS.

Introduced
R98
Where
Radio Access Network
Specifications
4 specs
RRLP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Radio Resource LCS Protocol (RRLP) is a Layer 3 application protocol defined for the Location Services (LCS) feature in 2G GSM and 3G UMTS networks. It operates as a peer-to-peer protocol between a target Mobile Station (MS) and a Serving Mobile Location Centre (SMLC) or a Location Measurement Unit (LMU). The protocol messages are transported over the existing radio interface signaling connections, typically using the DTAP (Direct Transfer Application Part) mechanism to carry them within higher-layer messages between the MS and the core network, which then relays them to the SMLC.

RRLP defines a set of request and response messages to facilitate various positioning methods. Key procedures include the provision of assistance data from the network to the MS and the delivery of location measurements or a computed position from the MS to the network. For example, in Assisted-GPS (A-GPS) positioning, the SMLC sends an RRLP Assistance Data message containing GPS satellite ephemeris, almanac, and timing information to the MS. The MS uses this data to quickly acquire GPS signals and then responds with an RRLP Measure Position Response message containing pseudorange measurements or the calculated latitude/longitude.

The protocol supports multiple positioning methods: Cell-ID (with optional timing advance), Observed Time Difference of Arrival (OTDOA) for UMTS, and Enhanced Observed Time Difference (E-OTD) for GSM. For OTDOA, the network provides assistance data about neighboring cells' timing, and the MS measures the observed time differences of received pilot signals. RRLP carries these measurements back to the SMLC, which calculates the position. The protocol is designed to be efficient over the constrained bandwidth of the radio interface, using compact information elements (IEs) to encode assistance data and measurement results. Its operation is controlled by the LCS client request, which specifies the required quality of service (QoS) for the location fix, such as accuracy and response time.

Purpose & Motivation

RRLP was created to standardize the signaling needed for network-based and mobile-based positioning in GSM and UMTS networks, fulfilling regulatory (e.g., E911) and commercial location-based service requirements. Before standardized protocols like RRLP, proprietary solutions existed, hindering interoperability between network equipment and handsets from different vendors. RRLP provided a universal language for location-related communication over the air interface.

It solved the problem of enabling accurate positioning in handsets that may not have full, autonomous GPS capabilities. By providing network assistance (A-GPS), RRLP dramatically reduces the Time To First Fix (TTFF), improves sensitivity for indoor operation, and reduces the handset's power consumption. For network-based methods like OTDOA, it provided a mechanism for the network to request specific radio measurements from the handset to compute its location, even without GPS. The creation of RRLP was a critical step in making reliable, standardized location services a ubiquitous feature of cellular networks, enabling emergency services, navigation, fleet tracking, and a host of other applications.

What changed in its specifications

The latest release-to-release comparison of specifications that define RRLP. Each summary describes the whole specification, not only this term.

TS 43.059Rel-11 → Rel-12

Added BDS support for LCS, new PS positioning procedures for A/Gb and Iu modes, and TA and U-TDOA steps.

Full comparison in TS 43.059 →
TS 48.018Rel-17 → Rel-18

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

Full comparison in TS 48.018 →

Technology family

Location services architecture · Services

  1. R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
  2. Rel-5 PCAP, SAS
  3. Rel-6 PPR, R-GMLC
  4. Rel-7 LRF, SUPL
  5. Rel-9 E-SMLC, LCS-AP, LPP, LPPa
  6. Rel-15 LMF, NRPPa
  7. Rel-18 LCS-UPP, RSPP, SLPP

Also in this family (introduction release not pinned to a single defining specification): H-GMLC, LMC, MLP, V-GMLC

  • RRLP counterpart in another generation: LPP
    “LPP is a point to point positioning protocol with capabilities similar to those in UMTS RRC (TS 25.331 [15]) and GERAN RRLP (TS 44.031 [16]).” TS 36.305

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

R98 introduced

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

Rel-4 specification text

TS 43.059 first appears in this release, specifying how RRLP messages are carried and segmented between SMLC, BSC and MS, including RRLP pseudo-segmentation and handover handling.

  • “RRLP pseudo-segmentation: The use of several RRLP data messages to deliver a large amount of assistance data” TS 43.059 v4.7.0
  • “When the RRLP request comes to BSC from SMLC, BSC sends the "RRLP request" to the MS if there is no ongoing HO” TS 43.059 v4.7.0
  • “3GPP TS 44.031: Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP)” TS 43.059 v4.7.0
Rel-5 specification text

RRLP gained PS-domain transport via BSSGP/TOM with RRLP flags, and RRLP pseudo-segmentation with a 242-octet maximum PDU size replaced earlier segmentation handling.

  • “The position command procedure is used to convey an embedded RRLP message between the BSS and the MS.” TS 48.018 v5.14.0
  • “If more information than what fits in the RRLP maximum PDU size needs to be delivered, the RRLP pseudo-segmentation shall be used.” TS 43.059 v5.5.0
  • “Introduction of a new TOM protocol discriminator for RRLP” TS 44.064 v5.2.0
Rel-7 specification text

RRLP gained a Positioning Capability Transfer procedure so the SMLC can obtain MS positioning capabilities via RRLP, and RRLP text moved from GPS to A-GNSS.

  • “Addition of Positioning Capability Transfer using RRLP” TS 43.059 v7.3.0
  • “The SMLC may precede the RRLP MEASURE POSITION REQUEST or Assistance Data Delivery procedure with a Position Capability Transfer procedure” TS 43.059 v7.3.0
Rel-14 specification text

RRLP gains new Multilateration Timing Advance positioning messages and procedures: the SMLC sends an RRLP Positioning Multilateration Timing Advance Request to the MS, carrying assistance data, tunnelled via the BSS and SGSN.

  • “it includes assistance data in an RRLP Positioning Multilateration Timing Advance Request message (see 3GPP TS 44.031 [15]) and sends the message to the MS” TS 43.059 v14.3.0
  • “the MS is triggered to perform MTA as a result of receiving an RRLP message from an SMLC indicating the MTA positioning method is to be used” TS 43.059 v14.3.0
  • “The RRLP application in the MS examines the RRLP Positioning Multilateration Timing Advance Request message and if assistance data is present” TS 43.059 v14.3.0
Rel-15 specification text

The Multilateration Timing Advance procedure using RRLP gained access security: the SMLC includes an "MTA Access Security Method" IE in the RRLP message and handles a missing "MTA Signature" as an abnormal case.

  • “If the SMLC has included “MTA Access Security Method” IE in the RRLP message sent for a given MTA procedure and does not receive” TS 43.059 v15.2.0
  • “includes “MTA Signature” and “MTA Sequence” in this message to SGSN, if it has received these IEs from BSS” TS 43.059 v15.2.0

Defining Specifications

3GPP specifications that define or reference RRLP, 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
TS 43.059 vj00 GERAN LCS Stage 2 Specification Rel-19 read
TS 44.064 vj00 GPRS Logical Link Control (LLC) Protocol Rel-19 read
TS 48.018 vj00 BSS-SGSN Interface for GPRS Control Rel-19 read