YateHSS/HLR redundancy and load balancing
The YateHSS/HLR provides application-level redundancy and load balancing. The YateHSS/HLR server uses commodity hardware and manages subscriber data for GSM, UMTS, LTE, IMS, and WiFi networks.
The YateHSS/HLR can be configured in a cluster of equal nodes, providing load balancing and application-level redundancy.
The YateHSS/HLR nodes communicate with each other over a dedicated protocol – Cluster Connection.
Each subscriber profile introduced or updated in a YateHSS/HLR is replicated in all the other YateHSS/HLR nodes.
Scalability:
A new YateHSS/HLR server configured in the network is automatically synchronized with the existing nodes.
Load balancing:
In case of congestion of a YateHSS/HLR node, subscribers start to be registered to any available YateHSS/HLR in the network.
Geographical distribution:
Nodes can be located in different locations serving preferentially local resources while remaining synchronized.
Redundancy:
The YateHSS/HLR supports automatic synchronization after failure.
Many to many relationships between the core network, SS7 STP/Diameter routers, and the Yate HSS/HLR nodes eliminate single points of failure from the network.
Redundancy in typical HLR / HSS
Conventional Home Location Register (HLR) and Home Subscriber Server (HSS) equipment is based on specialized hardware and software.
Redundancy is ensured by backing each HLR/HSS component with another component.
HLR/HSS nodes in a network don’t communicate to other HLR/HSS nodes.
Subscriber groups are distributed between HLR/HSS components.
Changes to a subscriber profile are not visible in other HLR or HSS server in the network.
While conventional HLR and HSS components provide redundancy, they do not provide load balancing.
Redundancy is based on adding distinct hardware equipment, which leads to longer time for servicing and higher costs.
Each SS7 and Diameter router is connected to one core network and to one HLR or HSS, allowing single points of failure in the network.