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

Glossary term · Protocol

SLP

Service Location Protocol

Protocol →

SLP is a 3GPP protocol for discovering and selecting location-based services and servers, such as positioning servers, within a network to enable location-based applications and efficient service discovery.

Introduced
Rel-7
Where
Services › IMS
Specifications
18 specs
Also in
Radio Access Network, Core Network
SLP Description Purpose What changed Neighbours Specifications

Description

The Service Location Protocol (SLP) is an IETF-defined protocol (RFC 2608) adopted and profiled by 3GPP for use within its architecture, primarily to facilitate service discovery. In the 3GPP context, SLP is a key enabler for location services (LCS), allowing a client, such as User Equipment (UE) or a network entity, to discover the address of a location server, most notably the Secure User Plane Location (SUPL) Location Platform (SLP). The protocol operates in a client-server model where User Agents (UAs) issue service requests and Service Agents (SAs) advertise services. Directory Agents (DAs) can optionally be used as centralized repositories for service advertisements, improving scalability in large networks. The protocol uses service URLs and attributes to describe services, and discovery can be performed via multicast or unicast. For 3GPP, SLP is often used in the SUPL architecture, where a SUPL Enabled Terminal (SET) uses SLP to discover the address of its Home SLP (H-SLP) or a Discovered SLP (D-SLP) to initiate a positioning session. This discovery is crucial for establishing a secure user-plane connection for delivering location information. The protocol supports authentication and provides a flexible framework for finding various types of services beyond just location, though its primary 3GPP application is within the SUPL ecosystem. Its integration allows for decentralized service discovery without requiring pre-configuration of server addresses in every device, enhancing flexibility and manageability for network operators.

Purpose & Motivation

SLP was introduced to solve the problem of dynamic service discovery in IP-based networks, which became increasingly relevant with the rise of mobile data services and location-based applications. Prior to standardized service discovery, devices often required manual configuration of server addresses (like a home location server), which was inflexible, difficult to manage at scale, and hindered service portability and roaming. The protocol provides a standardized, automated method for clients to find necessary network services. Within 3GPP, its adoption, particularly starting in Release 7 with SUPL 1.0, was motivated by the need for an efficient user-plane location solution. SLP enables a SUPL Enabled Terminal to dynamically discover its appropriate SLP, whether it's the home network's SLP or a visited network's SLP during roaming. This capability is essential for emergency services (e.g., E911), commercial location services, and regulatory compliance, as it ensures a device can always find a positioning server without user intervention. It decouples the client from a static network configuration, allowing operators to deploy and relocate servers more freely and support a growing ecosystem of location-based services.

What changed in its specifications

The latest release-to-release comparison of specifications that define SLP. 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.167Rel-17 → Rel-18

Rel-18 adds signal level Enhanced Network Selection, covering emergency-session and eCall-over-IMS behaviour for UEs in limited service state, tied to the ims-EmergencySupport broadcast bit. The overview lists only this one feature, so no further items can be named from the provided material.

Full comparison in TS 23.167 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Initially introduced in 3GPP for SUPL 1.0. Defined the use of SLP for the SUPL Enabled Terminal (SET) to discover the address of the Secure User Plane Location (SUPL) Location Platform (SLP). Established the basic framework for user-plane location service discovery, supporting emergency and commercial services.

Defining Specifications

3GPP specifications that define or reference SLP, 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.167 vk10 IMS Emergency Services Rel-20 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.303 vj00 Proximity Services (ProSe) Stage 2 Rel-19 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TR 23.730 ve00 Study on extended CIoT architecture Rel-14 read
TS 23.868 v900 Study on IMS Emergency Calls Rel-9 read
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19 read
TS 29.171 vj10 LCS-AP between MME and E-SMLC (SLs) Rel-19 read
TS 29.278 vj00 CAMEL Application Part (CAP) for IMS Phase 4 Rel-19 read
TS 29.819 vd00 Diameter Base Protocol Update Analysis Rel-13 read
TS 33.533 vj00 Security for 5G Ranging & Sidelink Positioning Rel-19 read
TS 36.305 vj00 UE Positioning in E-UTRAN Stage 2 Rel-19 read
TS 36.355 vj00 LTE Positioning Protocol (LPP) Rel-19 read
TS 36.809 vc00 Study on RF Pattern Matching for LTE Positioning Rel-12 read
TS 36.840 vc10 LTE 450 MHz Band Technical Requirements for Brazil Rel-12 read
TS 37.355 vj30 LTE Positioning Protocol (LPP) Rel-19 read
TS 38.305 vj30 NG-RAN UE Positioning Stage 2 Rel-19 read