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

Glossary term · Core Network

SLF

Subscription Location Function

Core Network →

SLF is a core network function in IMS and 5G that locates the appropriate HSS or UDM for a given subscriber to route queries to the correct user data repository.

Introduced
Rel-5
Where
Core Network › Evolved Packet Core
Specifications
29 specs
Also in
Services, Management, Security
SLF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Subscription Location Function (SLF) is a critical component within the IP Multimedia Subsystem (IMS) and 5G Core (5GC) architectures, specifically designed to resolve which Home Subscriber Server (HSS) or Unified Data Management (UDM) function holds the subscription data for a given user. It operates as a simple query-response mechanism. When an IMS Call Session Control Function (CSCF) or a 5G Network Function (NF) like the Authentication Server Function (AUSF) needs to access subscriber data but does not know the specific HSS/UDM instance, it sends a Diameter or HTTP-based query to the SLF. This query contains a user identifier, such as the IMS Private User Identity (IMPI) or Subscription Permanent Identifier (SUPI). The SLF, using a configured mapping database or algorithm, returns the address (e.g., hostname, IP address) of the HSS or UDM that serves that subscriber. This process is transparent to the end-user and is a foundational element for subscriber data management in multi-HSS/UDM environments.

Architecturally, the SLF is defined as a standalone logical function but can be co-located with an HSS for simplicity in smaller deployments. In a pure 5G Core network, the UDM incorporates the SLF functionality internally through its UDR (Unified Data Repository) discovery mechanisms, making a standalone SLF less common. However, in IMS and during interworking scenarios between 4G EPC and 5GC, the SLF remains a vital entity. Its primary interface is the Dx interface (based on Diameter protocol) towards the I-CSCF and S-CSCF in IMS, and the N10/N11 interfaces (based on HTTP/2) in the 5G Service-Based Architecture (SBA) when interacting with the UDM.

The SLF's role is purely for discovery and does not store actual subscriber profile data itself. This separation of concerns allows for flexible network scaling. Operators can deploy multiple HSS/UDM instances to handle large subscriber bases or for redundancy, with the SLF providing the necessary indirection layer. It supports load balancing and geographic distribution of user data. For instance, subscribers in different regions can be homed to different HSS instances, and the SLF ensures that queries from the network are always directed to the correct regional database. This capability is crucial for maintaining low-latency access to subscriber data and for implementing disaster recovery schemes where user data is replicated across sites.

Purpose & Motivation

The SLF was introduced to solve a fundamental scaling problem in early IMS deployments. As networks grew beyond a single HSS, there was no standard mechanism for network functions to determine which HSS instance contained the data for a specific user. Without an SLF, network elements would need pre-configured, static mappings or would have to broadcast queries to all HSS instances, which is inefficient and does not scale. The SLF provides a centralized, standardized lookup service, enabling the deployment of multiple, independent HSS databases. This allows operators to scale their subscriber capacity horizontally by adding more HSS nodes without reconfiguring every CSCF in the network.

Its creation was motivated by the move towards distributed, carrier-grade architectures. In 2G/3G circuit-switched cores, the HLR (Home Location Register) was typically a monolithic, centralized database. IMS, designed for IP-based multimedia services, required a more flexible and scalable approach. The SLF facilitated this by decoupling the subscriber location logic from the service logic in the CSCFs. This design principle carried forward into 5G, where the concept is embedded within the UDM's service-based architecture. The SLF addresses the limitations of monolithic databases by enabling stateless, scalable control plane functions (like CSCFs) to dynamically locate stateful data repositories, which is a cornerstone of cloud-native network design.

What changed in its specifications

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

TS 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →
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

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF

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.

Rel-5 introduced

The SLF is specified for the first time: I-CSCF and S-CSCF query it over the Dx interface (DX_SLF_QUERY/RESP) to obtain the HSS name holding a user's subscription data.

  • “To get the HSS name the I-CSCF and the S-CSCF query the Subscription Locator Functional (SLF) entity.” TS 23.228 v5.15.0
  • “By the Dx-operation DX_SLF_RESP the SLF responds with the HSS name.” TS 23.228 v5.15.0
  • “The Dx interface is the standard interface between the CSCF and the SLF.” TS 23.228 v5.15.0
Rel-6 specification text

The SLF gained a new Dh interface so that Application Servers can query it to find the right HSS (DH_SLF_QUERY/DH_SLF_RESP), alongside the existing Dx use by CSCFs.

  • “By the Dh-operation DH_SLF_RESP the SLF responds with the HSS name. The AS continues by querying the selected HSS.” TS 23.228 v6.16.0
  • “the Dh interface is the standard interface between the AS and the SLF” TS 23.228 v6.16.0
  • “To get the HSS address the AS sends to the SLF the Sh requests aimed for the HSS.” TS 29.328 v6.15.0
Rel-7 specification text

SLF behaviour changed: it returns an ordered list of HSS identities for the I-CSCF, S-CSCF and AS to try in turn, and it derives the Public Identity in canonical form for lookup.

  • “the I-CSCF or the S-CSCF shall send the Cx Request to the first HSS identity in the ordered list received in the Cx Response from the SLF.” TS 29.228 v7.18.0
  • “If the Public-Identity AVP contains a Tel URI in E.164 format, the HSS and SLF shall remove visual separators and remove all URI parameters.” TS 29.228 v7.18.0
  • “The I‑CSCF sends a DX_SLF_QUERY to the SLF and includes as parameter the user identity which is stated in the INVITE request.” TS 23.228 v7.16.0
Rel-8 specification text

The SLF resolution mechanism was extended so a Diameter Proxy Agent can be used as an alternative to the SLF, and the SLF's Dx/Dh redirect-agent behaviour was restated.

  • “This resolution mechanism is implemented using a Subscription Locator Function (SLF) or a Diameter Proxy Agent that proxies the request to the HSS.” TS 23.228 v8.12.0
  • “The resolution mechanism described in 3GPP TS 23.228 [1] shall use a Subscription Locator Function (SLF) or a Diameter Proxy Agent.” TS 29.228 v8.19.0
  • “The SLF functionality shall use the routing mechanism provided by an enhanced Diameter redirect agent.” TS 29.328 v8.18.0
Rel-13 specification text

HSS/SLF gained Diameter message priority handling: it must comply with RFC 7944 and send, prioritise and respond to requests and responses according to the DRMP AVP priority level.

  • “the HSS/SLF shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request” TS 29.228 v13.5.0
  • “When the HSS/SLF receives a request, it shall handle the request according to the received DRMP AVP priority level.” TS 29.228 v13.5.0
  • “the HSS/SLF shall prioritize the request according to priority level received within the DRMP AVP” TS 29.328 v13.12.0
Rel-14 specification text

The HSS/SLF gained support for Diameter message priority-based DSCP marking of requests and responses, and the Dx/Dh interfaces now reference the Diameter base protocol of IETF RFC 6733.

  • “then the HSS/SLF shall set the DSCP marking for transport of the request or response according to the required priority level.” TS 29.228 v14.6.0
  • “the HSS/SLF supports using the Diameter message priority mechanism for DSCP marking purposes,” TS 29.228 v14.6.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.417 v700 IMS Core Component for NGN Architecture Rel-7 read
TS 23.517 v800 IMS Core Architecture for TISPAN NGN Rel-8 read
TS 23.682 vj30 Architecture for MTC and SCEF Enhancements Rel-19 read
TS 23.845 va00 UDC Evolution Study Rel-10 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.407 v830 OIP and OIR Simulation Services Protocol Rel-8 read
TS 24.508 v820 TIP and TIR Service Protocol Description Rel-8 read
TS 24.524 vj00 Hosted Enterprise Services Architecture Rel-19 read
TS 28.620 vj20 FMC Federated Network Information Model (FNIM) UIM Rel-19 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 28.705 vj00 IMS NRM IRP Information Service Rel-19 read
TS 29.109 vj00 GAA Bootstrapping Interfaces (Zh, Dz, Zn, Zpn) Rel-19 read
TS 29.228 vk00 IMS Cx and Dx Interface Procedures Rel-20 read
TS 29.229 vj10 Diameter Protocol for Cx/Dx Interfaces Rel-19 read
TS 29.328 vk00 IMS Sh, Dh and Ph Interface Procedures Rel-20 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.632 vb00 Core Network Resources NRM Rel-11 read
TS 32.732 vb00 IMS Network Resource Model Information Service Rel-11 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.820 v801 Study on Evolved 3GPP Charging Architecture Rel-8 read
TS 33.110 vj00 UICC-Terminal Key Establishment Rel-19 read
TS 33.220 vj10 Generic Authentication Architecture (GAA) Security Rel-19 read
TS 33.259 vj00 Key Establishment between UICC Hosting & Remote Device Rel-19 read
TS 33.804 vc00 Non-UICC SSO using SIP Digest credentials Rel-12 read
TR 33.924 vj00 GBA-OpenID Interworking Specification Rel-19 read
TS 33.978 v800 Early IMS Security Interim Solution Rel-8 read