Description
HLR-FE (Home Location Register Front End) is a logical network entity defined in 3GPP TS 23.335 as a front-end interface to the Home Location Register. It is placed between the HLR and the network elements or applications that require HLR data or HLR signalling. In a traditional 2G/3G core network, the HLR is the master repository for subscriber subscription, service profile, and current location information. The HLR-FE provides a standardized way for clients such as MSC/VLR, SGSN, GMLC, and service-control nodes to access that information without necessarily interacting with the HLR database implementation directly.
Functionally, the HLR-FE can be understood as a proxy or mediation layer. It receives requests that are normally associated with HLR operations, such as subscriber data retrieval, location update support, cancellation, notification, or other HLR-related signalling. It then routes those requests to the appropriate HLR, obtains the required data, and returns a response to the requesting client. Depending on implementation, the HLR-FE may terminate the signalling dialogue with the client and initiate a separate dialogue toward the HLR, or it may relay the request while preserving transaction state. This separation allows the HLR to be treated as a backend data and signalling resource while the front end handles client-facing sessions.
The architecture typically distinguishes between HLR-FE client functionality and HLR-FE server functionality. The client part resides in a network element that needs HLR access, while the server part provides the front-end service and can be co-located with the HLR or deployed as a separate logical node. The HLR-FE server may include routing logic, protocol adaptation, transaction management, and subscriber-data access functions. It can translate between the client interface and the HLR interface, and it can manage timeouts, retries, and error reporting so that clients do not need to know the internal structure or partitioning of the HLR backend.
From a signalling perspective, HLR-FE is relevant to MAP-based core network interactions. MAP is used in GSM and UMTS core networks for operations involving the HLR, VLR, SGSN, GMLC, and related entities. HLR-FE can support these operations by acting as an intermediary that presents a stable front-end interface while the HLR continues to provide authoritative subscriber data. This is important because HLR data is used for mobility management, call routing, packet-session management, location services, and service control. By front-ending HLR access, the network can better control signalling load and isolate clients from changes in HLR deployment.
The role of HLR-FE in the network is therefore primarily architectural and operational. It helps distribute access to a central subscriber-data repository, supports scalability, and enables integration of clients that need HLR information without requiring each client to implement a direct HLR interface. It can also support redundancy and load balancing by acting as a controlled point of access to one or more HLRs. In this sense, HLR-FE is not a replacement for the HLR; it is a front-end capability that sits around the HLR to make HLR access more manageable, more scalable, and more adaptable to evolving network elements and applications.
In practice, HLR-FE may be deployed to support large HLR domains, multiple HLR partitions, or migration scenarios where new applications need controlled access to legacy HLR data. It can also simplify network testing and operations by providing a common interface for HLR-related queries and updates.
In summary, HLR-FE is a Core Network concept that provides a front-end layer for Home Location Register access. It mediates between HLR clients and the HLR, supports subscriber-data and signalling access, and helps maintain a separation between client-facing interfaces and the authoritative HLR backend. Its value comes from reducing tight coupling to the HLR, improving control over HLR load, and providing a standardized architectural point for network elements that need HLR information.
Purpose & Motivation
The purpose of HLR-FE is to address the architectural limitations of direct HLR access in 2G and 3G core networks. The Home Location Register is a central subscriber-data element, but in early network designs many different nodes interacted with it directly through MAP signalling. As networks grew, this created several problems: the HLR could become a signalling bottleneck, each client had to implement complex HLR-related protocol behaviour, and changes to HLR deployment, partitioning, or redundancy were difficult to hide from clients. HLR-FE was introduced to provide a front-end layer that decouples clients from the HLR backend while still allowing them to obtain authoritative subscriber information and complete HLR-related operations.
Historically, mobility and subscription management depended on the HLR being reachable by MSC/VLR, SGSN, GMLC, and service-control entities. When those entities sent MAP requests directly to the HLR, the network had limited ability to balance load, isolate failures, or introduce new access patterns without modifying the HLR itself. HLR-FE solves this by acting as a mediation point. It can present a stable interface to clients, route requests to the appropriate HLR, and manage transaction state. This makes it easier to scale HLR access, integrate new clients, and operate the core network with clearer separation between signalling front end and subscriber-data repository.
The motivation for HLR-FE was therefore not to replace the HLR, but to make the HLR more manageable and more accessible in a network that was becoming more complex. It supports the need for controlled access to subscriber data, improved resilience, and reduced coupling between network elements. In Rel-9, this was captured as a stage-2 architecture for a front-end entity that can serve HLR clients while preserving the HLR's role as the authoritative source of subscription and location information.
Technology family
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
- HLR-FE part of HLR
“The application that is handled by an AFE determines the type of AFE, e.g. HLR-FE or HSS-FE.” TS 23.002
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 sourcesDocumented 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.
The HLR-FE is specified for the first time in TS 23.335, with CS terminating call and location update flows in which it queries and updates user data in the UDR over Ud.
- “the application specific front-end (HLR-FE) fetches all the user data it needs to perform its application logic” TS 23.335 v9.3.0
- “the HLR-FE updates the new user data (e.g. VLR number) in the UDR through a Ud Update procedure.” TS 23.335 v9.3.0
- “The HLR-FE responds to GMSC with the provided roaming number. 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 HLR-FE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.335 vj00 | User Data Convergence (UDC) Procedures | Rel-19 read |