HLR - Home Location Register
The Home Location Register is a database within the Home Public Land Mobile Network.
1. It provides routing information for Mobile Terminated calls and Short Message Service. Itis also
responsible for the maintenance of user subscription information.
2. This is distributed to the relevant VLR -Visitor Location Register or SGSN - Serving GPRS
Support Node through the attach process and mobility management procedures such as Location
Area and Routing Area updates,
3. HLR stores and manages all mobile subscriptions belonging to a specific operator. The HLR
is considered the most important database because it stores permanent data about subscribers,
including subscriber's supplementary services, location information, and. authentication
parameters buys When a person a subscription, it is registered in the operator's HLR.
4. The HLR can be implemented with the MSCIVLR or as a stand-alone database
5. AHLR contains user information such as account information, account status, user
preferences, features subscribed to by the user, user's current location, etc. The data stored in
HLRs for the different types of networks is similar but does differ in some details.
6. HLRs are used by the Mobile Switching Centers (MSCs) to originate and deliver arriving mobile
calls.
HLR Redundancy
When a single HLR fails, all subscribers with records in that HLR will not be able to roam or receive
calls. HLR Redundancy can prevent such a loss of subscriber activity. This feature is achieved by
having an additional HLR node for each HLR node in the network. HLR Redundancy provides
protection against disaster situations such as fire at an HLR site. At the same time, it will give
protection against Signalling failures towards an HLR and will also lower the lack of availability
‘caused by HLR restarts
With this feature, the subscriber can make and receive calls even in disastrous situations like an
earthquake with litle or no change in network continuity or functionality. The HLR Redundancy
feature, allows failure to be invisible to the network and the subscriber. A mated HLR is introduced
in such a way that subscribers and load are shared in normal operation, and when one HLR fails,
the other picks up all traffic normally routed to the pair.
2.VLR
A VLR is a database, similar to a HLR, which is used by the mobile network to temporarily hold
profiles of roaming users (users outside their home area). This VLR data is based on the user
information retrieved from a HLR. MSCs use a VLR to handle roaming users.
Database contains information about all mobile stations currently located in the MSC service area
VLR contains temporary subscriber information needed by the MSC to provide service for visiting
subscribers. The VLR can be seen as a distributed HLR. The Ericsson VLR is always integrated in
the MSC. When a mobile station roams into a new MSC service area, the VLR connected to that
MSC requests and stores data about the mobile station from the HLR. If the mobile station makes
a call at another time, the VLR will already have the information needed for call setup.
3. How are the HLR and VLR used?
Each mobile network has its own HLRs and VLRs. When a MSC detects a mobile user's presence
in the area covered by its network, it first checks a database to determine if the user is in his/her
home area or is roaming, i.e., the user is a visitor.a. User in Home Area: HLR has the necessary information for initiating, terminating, or receiving a
call
b. User is Roaming: VLR contacts the user's HLR to get the necessary information to set up a
temporary user profile.
The user's location is recorded in the HLR, and in case the user roaming, it is also recorded in the
VLR.
‘Suppose that the user wants to make a call
a. User in Home Area: MSC contacts the HLR prior setting up the to call.
b. User is Roaming: MSC contacts the VLR prior to setting up the call
‘Suppose that there is a call for the user (call goes to the home MSC)
a. User in Home Area: Home MSC delivers the call immediately.
b. User is Roaming: Home MSC contacts the VLR to determine the appropriate switch in the
roaming area to handle the arriving call and then transfers the call to the roaming area MSC.
Commands Via HLR
Displays User Profile:
Hosdp:msisdn= axxxx0«X.all
PRINT OUT:
HGSDP:MSISDN=919702900269,ALL;
HLR SUBSCRIBER DATA
SUBSCRIBER IDENTITY
MSISDN IMSI STATE __AUTHD
919702900269 405799008027031 CONNECTED AVAILABLE
NAM
0
PERMANENT SUBSCRIBER DATA
SsuD
CAT-10 DBSG-1 _TSMO-0 _ OBO-2
OBR-2 TS11-1 —-TS2i-1 — TS22-1
OFA-1 PWD-0000 CFU-1 — CFB-1
CFNRY-1 CFNRC-1 CAW-1 — SOCFB-0
SOCFRY-0 SOCFRC-0 SOCFU-0 SOCLIP-O
HOLD-1 MPTY-1 —CLIP-1
SCHAR-8-0
AMSISDN BS BC
NONE
SUPPLEMENTARY SERVICE DATA
BSG
TS10SS STATUS _ FNUM TIME
SADD
CAW NOT ACTIVE
CFU NOTACTIVE 919702900268
CFB NOTACTIVE
CFNRY NOTACTIVE
CFNRC NOT ACTIVE
LOCATION DATA
VLR ADDRESS MSRN MSCNUMBER —_LMSID
4-919891730001 919891730001
SGSN NUMBER
4-919891030078
PACKET DATA PROTOCOL CONTEXT DATA
APNID POPADD EQOSID VPAA PDPCH PDPTY PDPID
0 1 NO Ipv4 1
1 1 NO IPv4 2
2 1 NO IPv4 3
5 1 NO IPV4 6
END
Displays Permanent Subscriber Data (Network Set):
hgsdp:msisdn=6 14x000xxx,suda:
Displays Message Waiting Indicator (and message source)
hgmwp:msisdn=8 197020800268,
PRINT OUT:
HGMWP: MSISDN =919702900269;
HLR SUBSCRIBER MESSAGE WAITING DATA LIST
MSISDN msl MCE MNRF MNRG
919702900269 405799008027031 NO REACH REACH
SCADD
NONE
END
HLR SUBSCRIBER MESSAGE WAITING DATA LIST
MSISDN Isl MCE _MNRF MNRG
61433429052 — 505060000011555 NO NREACH REACH
SCADD
4-61430004010
ENDExecutes Call Forwarding:
gssi:msisdn=61 4xxxxxxxx, bsg=ts 10, $$=Cfu, fnLUM=O4XXXXXXXX;
(mobile or landline without country code)
bsg = variable (as below)
TS10
TS20
TS60
S20 = Asynchronous Services (MMS, email, browsing - all IP based)
S30 = Synchronous (real time video calls)
ss = variable (as below)
CFU = Call Forwarding Unconditional (overrides all others)
CEB = Call Forward Busy
CENRY = Call Forward No Reply (specify's seconds)
CFNRC = Call Forward Not Reachable (out of coverage, handset turned off)
*** Please note that unconditional call forwarding to an international number needs to be
performed using different commands. Please see page 3 of this document for details ***
Network Barring:
ngsdc:msiscin=6 14xxxxxxxx,sud=0b0-1;
OBA = BAR ALL incoming and outgoing calls
OBI = bar ALL incoming calls
OBO = bar ALL outgoing calls
O=OFF = 1=ON 2 = Intemational Barring
OBR-2 = PLMN country (restricts country via IMSI ie. would not be able to roam internationally)
OBR-1
ome PLMIN (restricts to home network via IMSI ie. would not be able to roam on Voda)
User Barring
Customers are able to activate barring via the handset, if customers are unable to perform this
function via the handset you can enable the customer to be able to perform this function via the
handset.
If customer is not enabled to perform a certain type of barring it will not appear on the list.
Eg. BAIC for SMS (TS20) is not enabled for this customer (below) therefore customer would be
unable to active barring for all incoming SMS if desired
BSG
Ts20
SS STATUS FNUM TIME
SADDBAOC NOT ACTIVE
BICRO NOT ACTIVE
BOIC NOT ACTIVE
BOIEXH NOT ACTIVE
ACTIVE-O!
NOT ACTIVE
Activated
nabled/available but not activated by user
To enable:
hgsde:msiscin=6 1 4xxxxxxxx, sud=baic-1;
Or if customer is unable to remove barring via hands.
hgsse:msisdn=614xxxxxxxx, bsg=ts10,ss=baic;
Parameters:
BAIC Barring all incoming
BAOC Barring all outgoing
BICRO Barring of all incoming calls when roaming outside the home PLMN country
BOIC Barring of all outgoing international calls
BOIEXH —_Barring of all outgoing international calls except those directed to the home PLMN
country
TS10 Voice/Telephony
7820 SMS
TS60 Fax
BS20 Asynchronous Services (MMS, email, browsing - all IP based)
BS30 Synchronous (real time video calls)
fgntp:msisdn-
‘Check msisdn against FNR (Flexible Number Registar). If msisdn is not in the FNR subscriber will
not be able to receive calls, but can make calls.
'N Prefix’ will hold a value if customer has ported out of ‘3’. 'N Prefix follows CAC values. IMSI will
hold value if subscriber is with ‘3’ network.
Subscriber on ‘3
< IMSI carrier code and RNC where subscriber last ‘seen’
STATE > Current ‘state’ of subscriber:
IDLE: Ready to nvtx calls
NOT REG: Not on VLR
DET: Detached from network (phone turned off)
BUSY: Subscriber on call
IDET: Mobile not tuned off manually. Battery ran dead or battery removed,
NB: The CPM Too! - ‘Subscriber Status’ can be used as @ shortcut to find subscribers current ‘state’ le
‘idle’, Busy’ ete
mgsre:ims
Purges subscriber from VLR (Visitor Location Register). This command is similar to
hgsir:msisdn=x; although it purges directly from the serving VLR rather than via signalling from
the HLR. This command does not allow you to purge from roaming carrier VLR's
mgsip:imsi=x;
Displays subscriber data received from the HLR. MSTAT output displays whether subscriber is.
registered at present on the MSC (Mobile services Switching Centre) / VLR.
‘Subscriber Registered on ‘3°
mgslp:imsi=505060000001884;
MT MOBILE SUBSCRIBER LIST
SUBSCRIBER IDENTITY
IMsi MSTAT MSISDN CAT
5050600001884 REG 61404936629 10,
‘Subscriber Registered Elsewhere (ie. Roaming)
-<