HOME LOCATION REGISTER and

GATEWAY LOCATION REGISTER

 Objectives of the presentation
• To explain the function of the Home location Register and Visitor
Location Register in supporting Mobility management and call setup
• To outline the cost that come with inter-PLMN roaming due to Signaling
over carriers charging for authentication and Location Update
• To introduce the Gateway Location Register (GLR)as a cost mitigating
database for inter-PLMN roaming over carriers
• To explain the basic operations of GLR
 Function of HLR: Supporting seamless
mobile communications
• The home location register (HLR) is a central database that contains profiles of each mobile
subscriber authorized to use the Public Mobile Telecommunication core network.
• In the HLR MNO/PLMN subscribers are created and managed including service provision and
removal.
• Holds important data associated with the SIM known as the MSISDNs and International mobile
Subscriber Identities (IMSI), Authentication data and algorithms as well as subscriber profile
(permanent) and dynamic data (temporary).Global Title (GT) used for routing outgoing and
receiving voice calls and SMS
• Manages the mobility of subscribers by updating its record of the VMSC or VLR hosting the MS,
after a network registration following a user moving from one MSC/VLR area or MNO to
another.
 HLR data before Location Registration
CASE for NetOne
IMSI MSISDN PROFILE CURRENT
DATA VLR/MSC
REGISTER IN
MCC+MNC+HH+ MSIN CC+NDC+SNR Services ODB CC+NDC+SNR
3/2digits+2digits + HHXXXXXX and SS Customer
Controlled
e.g 648010013123456 263+71 +NXXXXX “ NIL
6480100HHXXXXXX 263+71 +NXXXXX “ NIL
6480100HHXXXXXX 263+71 +NXXXXX “ NIL
Where N is non Zero digit, and MSISDN is not any 263712191xxx numders which are reserved for
network Nodes, e.g MSC, HLR, SGSN, SMSC, CAMEL, , GLR etc
 HLR data after Location Registration
CASE for NetOne
IMSI MSISDN PROFILE CURRENT
DATA VLR/MSC
REGISTER IN
MCC+MNC+HH+ MSIN CC+NDC+SNR Services ODB CC+NDC+SNR
3/2digits+2digits + HHXXXXXX and SS Customer
Controlled
e.g 648010013123456 263+71 +NXXXXX “ 263+71+2191XXX
6480100HHXXXXXX 263+71 +NXXXXX “ 27+ NDC+XXXXX
6480100HHXXXXXX 263+71 +NXXXXX “ 86 + NDC +XXXXX
Where N is non Zero digit, and MSISDN is not any 263712191xxx numders which are reserved for
network Nodes, e.g MSC, HLR, SGSN, SMSC, CAMEL, , GLR etc
 HLR data after Location
Registration/Location Update
PLMN 1 VLR/MSC 1
PLMN Other 1
GT: 263712191400
SOURCE HLR 263712191401 SUB Number VLR/MSC GT: 27821000212
263712980241 SOURCE HLR 263712191401 SUB SUB Number
263718123XYZ

HLR GT 263712191401
Sub identity Attached VLR VLR/MSC 2 GT 263712191410
2637122XXXX 2637121914XY SOURCE HLR 263712191401 Sub Number
263712980240 263712191410 263712980240
263712980241 263712191400 VLR/MSC GT
263718123XYZ 27821000212
861390123456
26371934512XY 861390123456
PLMN Other 2
 Function of HLR :Supporting seamless
Cellular mobile communications
• A database used for permanent storage of customer information
• HLR may be implemented as a distributed database, but logically only
one HLR exist for Cellular Mobile Telecommunication network
• Stores dynamic data such as current VLR/MSC address, subscriber
network attachment status,
• Facilitates Short Message Mobile Terminating (SMMT) by identifying
the current MSC hosting the target MS
 HLR Functions continued
• Pushes/inserts subscriber data into the hosting VLR or SGSN when a
subscriber attaches following a successful Location Registration.
• Deletes/cancels subscriber data from the previous VLR when a subscriber
has roamed away from it.
• Handles and processes all incoming call routing queries through receiving
“Send Routing Information Requests” (SRI) from the GMSC getting
the routing information from the VMSC/VPLMN hosting the called
MSISDN.
 FUNCTIONS OF VIISITOR LOCATION
REGISTER
• The Visitor Location Register (VLR) is a temporary repository for user profile, inserted
from HLR following successful location update and used for mobile originated and
terminated calls
• VLR performs user Location Update with the HLR and as a result informs the HLR or
HPLMN of the current network and VMSC GT to which user is attached
• The VLR/SGSN can authenticate the user by obtaining security information from
HLR/Authentication Centre and this facilitates roaming for the subscriber in visited
networks
• LU can be done with the HLR over the SCCP/SS7 signaling network as frequently as the
MS changes VMSC, and can be measured in minutes
 VLR Continued
• Authentication procedure of the MS involves the visited network VMSC and the
HPMN HLR and can also be done as regularly as authentication information in the
VLR is finished and this can even be in a matter of minutes
• This translates into large number of MAP SCCP signaling messages over the
Signaling carrier network and especially for remote HPLMN and VPLMN over
international carriers that charge for such SCCP Signaling information message
units transfer
• The cost of sharing such signaling messages units add to the cost of operating the
network and hence eat into ROI.
 THE NEED FOR GLR
 From the foregoing presentation it may be appreciated that there is a lot of Mobile Application MAP SCCP
signaling message units traffic shared between HLR and VLR, both intra PLMN and inter-PLMN. For Inter-
PLMN traffic with international roaming partners this traffic is carried by international carriers for a cost to the
partners.
 To appreciate, an illustration will help. If an AUTHENTICATION data request between VLR and roaming
partner HLR requires 512Bytes and Location Update 2 048Bytes, Total= 2,5KBytes. If inbound roamers in a
VPLMN number 10 000 then 2,5kB x 10 000= 25MB.
 If the roaming users travel regularly or are attached on the boarder of VLR so that they do frequent inter-VLR
LU , say n times/day then the MAP SCCP signaling traffic will total (25n)MB
 If this number of roamers (10 000) stays in the VPLMN for 30 days the total MAP SCCP traffic is (30
x25n)MB= (750n)MB. Assuming n=5 then 3.75GB authentication and LU only before we talk of actual payload
 This costs money
 The need for GLR continued

 To reduce a count of international roaming signaling traffic there is need for a hybrid device which acts a Virtual
HLR to the VPLMN, while a virtual VLR to the HPLMN and this is where the device Gateway Location Register
comes in.

 The Gateway Location Register (GLR) within the visited PLMN Core network is a means of reducing the
amount of MAP signaling traffic associated with Location Management carried over inter-PLMN roaming link
by users.

 It helps reduce the costs incurred by MNO due to users AUTHENTICATION message communication between
the VPLMN and HPLMN HLR over the SCCP links and SCCP STPs by international carrier organizations ( e.g.
BICS)
 The need for GLR continued
• Gateway Location Register is an entity that handles location management of
roaming subscriber without frequent direct involvement of HLR
• The GLR (Gateway Location Register) is a node between the VLR/SGSN and
HLR
• used to optimize location update and the handling subscriber data across network
boundaries.
• When subscriber is roaming the GLR plays the role of HLR towards the VLR and
SGSN in the visited network and the role of VLR and/or SGSN towards the HLR
of the home network (two faced network node)
 GLR node location

HPLMN VPLMN
HLR Virtual Virtual VLR
VLR HLR

GLR
• The GLR is an network edge node located in the visited PLMN
• Its an optional entity within a VPLMN and in the network architecture the GLR is not visible to the HLR.
 Roaming Scenario
• Figure 1 shows GLR is deployed at the edge of a PLMN network
• It contains roamers subscriber profile and location information, and
handles management in the visited network much the same way as HLR.
HLR, GLR and VLR/SGSN Relationship

HPLMN A HPLMN B HPLMN C

HLR HLR HLR
VPLMN a GLR VPLMN b GLR

VLR/SGSN VLR/SGSN
VLR/SGSN VLR/SGSN
 HLR, GLR and VLR/SGSN Relationship
continued
• The subscriber information is downloaded from HLR to GLR at the first location
update procedure (Location Registration).
• Using this information the GLR handles Update Location request message from
VLR as if it is the HLR of the subscriber at second and subsequent update
procedures.
• GLR enables the LU procedure invisible from the HPLMN so that this location
management can reduce the inter-network signaling for location management.
• The GLR maintains the User profile and camped VLR/SGSN information until it
receives Cancel Location message from the HPLMN HLR
 Relationship Between GLR and HLR
• A GLR helps Visited PLMN (VPLMN) operators lower cost and optimize inbound
roaming LU and Autherntication traffic through significantly reducing the amount
of signaling messages across network towards HPLMN.
• GLR is a node between the Visited Location register (VLR) and/or Serving GPRS
Support Node (SGSN) and the HLR used to optimize Location Updating and
handling of subscriber profile data across roaming partner network boundaries.
• To a roaming subscriber, the GLR functions as an HLR towards the VLR and
SGSN in the visited networks and as the VLR and/or SGSN towards the HLR in
the Home network.
 GLR interfacing
• A GLR interacts with multiple HLRs which will be located in different
HPLMNs
• The relationship between the GLR and HLR is the same as that between
the VLR and GLR.
 Relationship between GLR and VLR
• A GLR interacts with multiple VLRs of only one VPLMN
 Roaming to VPMN with GLR

HPLMN A HPLMN B HPLMN C

HLR HLR HLR
VPLMN a GLR VPLMN b GLR

VLR/SGSN VLR/SGSN
VLR/SGSN VLR/SGSN
 GLR
• The GLR is a pseudo-HLR located in the visited network and roamers information is
stored in it and handles location management of it within the network
• Presence of GLR is invisible from the Home network therefore interface between HLR
and GLR is the same as between HLR and VLR.
• Similarly interface between VLR and GLR is same as VLR and HLR
• The GLR is a logical node and acts as a VLR for MAP signaling ( e.g. PRN) from the
HPLMN point of view.
• The GLR acts as a HLR for MAP signaling ( e.g. Register SS) from the VPLMN point
of view.
 GLR Continued
• The GLR acts as an SGSN for MAP signaling only from the HPLMN
point of view
• The GLR terminates all TC dialogues and start new dialogues towards the
HLR or VLR.
 First Location Update Procedure
VLR Visited network GLR HPLMN Network HLR

in Country B IN Country A
1. Update Location
1. Update Location
2. Insert Subscriber Data
2. Insert Subscriber data
2. Insert Sub data Ack
2. Insert Sub data Ack
First Location Update Procedure continued

3. Update Location ACK

3. Update Location ACK

First LU procedure in the Netork

 First Location Update Procedure steps
• When the GLR receives an Update Location request message from a VLR and does not hold the subscriber’s
information for the user (i.e. at first location updating to the GLR), the GLR:
- stores the VLR Number and serving MSC Number included in the received message, and
- sends an Update Location message to the HLR with the GLR Number as VLR Number, and IM-MSC Number as
MSC Number.
• The HLR stores the GLR Number and IM-MSC Number from received message as respectively VLR Number and
serving MSC Number. Thereafter the HLR initiates insert subscriber data procedure and cancel location procedure.
• When the GLR receives Insert Subscriber Data message from the HLR, the GLR stores the subscriber’s
information in the message and transport it to the VLR.
• After these procedures, the HLR replies to an Update Location message from the GLR and the GLR transports the
response to the VLR.
 Second and further Location Updating
Procedure signal flow
• The second and further location updating procedure in the network.
VLR OLD VLR NEW GLR HLR
1. Update Location
2. Cancel Location
2. Cancel Location ACK
3. Insert Subscriber data
3. Insert Subscriber data ACK
4.Update location ACK
 Second and further Location Updating
Procedure.
• Procedure:
• 1) When Subscriber moves to a new VLR or VMSC of the same VPMN, the GLR receives
an Update Location message from newly visited VLR.
• information for the user (i.e. at second or further location updating with the GLR), the GLR
stores the new VLR
• Number and new serving MSC Number included in the received message.
• 2) Thereafter the GLR initiates insert subscriber data procedure and cancel location
procedure.
• 3) After these procedures, the GLR replies to an Update Location message from the VLR.
 Summary
• The Gateway Location Register within the GSM/UMTS Core Network as
a means of reducing the amount of MAP Signaling traffic associated with
location management carried over inter-PLMN SCCP links
 Abbreviations
• MSISDN : Mobile Station Integrated Subscriber Digital Number
• IMSI: International Mobile Subscriber Identity
• VMSC: Visited Mobile Switching Centre
• VPLMN: Visited Public Land Mobile Network
• MNO: Mobile Network Operator
• SRI: Send Routing Information
 Abbriviations
• GMSC: Gateway Mobile Switching Centre
• SCCP: Signaling Connection Control Part
• HLR: Home Location Register
• VLR: Visitor Location Register
• HPLMN: Home Public Land Mobile Network
• LU: Location Update
 Abreviations
• PRN: Provide Roaming Number
• MAP: Mobile Application Part