Radio resource location services protocol
Open-knowledge reference entry
Radio resource location services (LCS) protocol (RRLP) applies to GSM and UMTS Cellular Networks. It is used to exchange messages between a handset and an SMLC in order to provide geolocation information; e.g., in the case of emergency calls. The protocol was developed in order to fulfil the Wireless Enhanced 911 requirements in the United States. However, since the protocol does not require any authentication, and can be used outside of a voice call or SMS transfer, its use is not restricted to emergency calls and can be used by law enforcement to pinpoint the exact geolocation of the target's mobile phone. RRLP was first specified in 3GPP TS 04.31 - Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC); Radio Resource LCS Protocol (RRLP).
Harald Welte proved at HAR2009 that many high-end smart-phones submit their GPS location to the mobile operator when requested. This happened without any sort of authentication.
RRLP parameters
Positioning methods
RRLP supports two positioning methods:
E-OTD
The Enhanced Observed Time Difference (E-OTD) is based on measurements inside the mobile phone, where the phone measures the observed time difference of arrival of bursts sent by nearby pairs of base transceiver stations.
GPS
This method uses the GPS (Global Positioning System) for achieving geolocation. To support this, the phone needs to have a built-in GPS receiver.
“Radio resource location services protocol” enters the record as open-knowledge reference entry. Crown Archives preserves that source wording while asking what Radio, resource and location can confirm, complicate or overturn.
Why this record matters
“Radio resource location services protocol” is worth following because a concise public description often conceals a longer documentary argument. Here, Radio, resource and location provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Apr 3, 2023. The linked authority identifier is Q7281196. None of the 0 selected statements returned an explicit reference.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Radio resource location services protocol”, its source revision and the description used here.
- Expand the search: follow Radio resource location services protocol primary sources, Radio resource location services protocol archive and Radio research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Radio resource location services protocol”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Radio resource location services protocol” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.