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

Glossary term · Core Network

HSS-FE

Home Subscriber Server Front End

Core Network →

HSS-FE is a front-end interface component of the HSS that handles direct signaling communication with other network entities, acts as a protocol gateway, and may load-balance while hiding backend HSS database complexity.

Introduced
Rel-9
Where
Core Network › 5G Core
Specifications
1 specs
HSS-FE Description Purpose Family Neighbours Detected Changes Specifications

Description

The Home Subscriber Server Front End (HSS-FE) is a functional decomposition of the traditional monolithic Home Subscriber Server (HSS), specified in 3GPP Release 9 as part of the HSS architectural enhancements. It is defined as the entity that terminates the Diameter-based signaling interfaces (such as S6a, Cx, Sh, etc.) from various core network nodes like the MME, CSCF, or AS. The HSS-FE acts as a single point of contact for these external entities, presenting a standardized HSS interface regardless of the underlying subscriber data storage architecture. Its primary operational role involves receiving Diameter requests, performing necessary protocol adaptations, and forwarding these requests to the appropriate backend subscriber database, which could be a Subscription Locator Function (SLF) or a specific User Data Repository (UDR/UDR-FE). It may also consolidate responses from the backend. Architecturally, the HSS-FE separates the signaling and protocol handling functions from the actual data storage and management functions. This allows for significant scalability and flexibility: multiple HSS-FE instances can be deployed to handle high signaling loads and provide redundancy, while the subscriber data itself can be centralized in a separate, scalable database layer (UDR). The HSS-FE may also implement features like load balancing across multiple backend data repositories, caching of frequently accessed data to reduce latency, and acting as a firewall to protect the backend data layer from direct exposure to the core network.

Purpose & Motivation

The HSS-FE was introduced to address scalability, performance, and flexibility limitations inherent in the traditional, integrated HSS design. As networks grew and services like IMS became widespread, the HSS became a critical bottleneck, handling signaling from an increasing number of network elements (MME, CSCF, AS). The monolithic design, where signaling interfaces and data storage were tightly coupled, made it difficult to scale the signaling capacity independently of the database storage. The creation of the HSS-FE, alongside the User Data Repository (UDR), was motivated by the need for a more distributed, cloud-friendly subscriber data management architecture. It solves the problem of signaling congestion by allowing operators to deploy multiple front-end instances. It also future-proofs the network by abstracting the data layer, enabling the introduction of new, centralized data repositories (like UDR) without requiring changes to all the core network nodes that communicate with the HSS. This separation aligns with trends towards network function virtualization (NFV) and software-defined networking (SDN).

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
  • HSS-FE part of HSS
    “The application that is handled by an AFE determines the type of AFE, e.g. HLR-FE or HSS-FE.” TS 23.002
  • HSS-FE used together with UDR
    “UDR provides a unique reference point to one or more Applications Front Ends, such as: one or more HSS/HLR/AuC-FEs, and one or more AS- FEs.” TS 23.335

Security functions and anchors · Security

  1. Phase 1 AuC
  2. R99 HLR/AuC
  3. Rel-5 HSS
  4. Rel-6 3GPP AAA Server, BSF
  5. Rel-8 ASME, MME
  6. Rel-9 HSS-FE
  7. Rel-15 AMF, ARPF, AUSF, SEAF, SEPP, SIDF
  8. Rel-16 AAnF

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.

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 1 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-9 introduced

TS 23.335 first appears in Rel-9 (v930), defining the HSS-FE in the UDC architecture: it handles Sh/Cx signalling, queries and updates user data in the UDR over Ud, and is selected for load sharing or failover.

  • “networks that support UDC may deploy several HSS-FEs all of which have access to the UDR and hence can serve any user.” TS 23.335 v9.3.0
  • “the HSS-FE checks the AS-permission list to see whether the AS is allowed to contact the HSS.” TS 23.335 v9.3.0
  • “The HSS-FE sends the response to Sh-Update to AS. No user data is kept in the front-end after the procedure is ended.” TS 23.335 v9.3.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.335 vj00 User Data Convergence (UDC) Procedures Rel-19 read