Home Location Register

Chapter 10

This chapter is designed to provide the student with an

understanding of the main functions of the Home Location
Register node.

OBJECTIVES:
At the end of this chapter the student will be able to:

Explain the MML required supporting different Basic

Services by interpreting exchange requirements.
Explain the MML for Call Forward Analysis by interpreting
exchange requirements.
Describe the data required to support HLR redundancy.
Identify the data transcript required for a stand-alone home
location register.
Explain the MML required to support AUC/EIR Connection.
GSM Data Transcript

t io
en na
I nt

lly

Bl n
a
k

EN/LZT 123 3451 R3A

 10 Home Location Register10 Home Location Register

10 Home Location Register

Table of Contents

Topic Page

INTRODUCTION ................................................................................ 231

FUNCTIONS OF THE HOME LOCATION REGISTER...................... 232

ADMINISTRATION .................................................................................................. 232
MAP COMMUNICATION ......................................................................................... 233
DATABASE.............................................................................................................. 233
ANALYSIS ............................................................................................................... 237

CALL FORWARDING........................................................................ 242

CALL FORWARD UNCONDITIONAL ...................................................................... 242
CONDITIONAL CALL FORWARD ........................................................................... 243
MOBILE INITIATED ACTIVATION OF CALL FORWARDING SERVICE................. 244

STAND-ALONE HLR ......................................................................... 246

HARDWARE REQUIREMENTS IN A STAND-ALONE HLR .................................... 246
DATA TRANSCRIPT REQUIRED FOR A STANDALONE HLR............................... 247

DATA TRANSCRIPT ......................................................................... 249

SUBSCRIBER DATA ............................................................................................... 249
CALL FORWARDING .............................................................................................. 250

AUC/EIR............................................................................................. 251
AUC CONNECTION ................................................................................................ 251
AUC DATA TRANSCRIPT ....................................................................................... 252
AUC-10 CONNECTION ........................................................................................... 252
AUC-10 DATA TRANSCRIPT.................................................................................. 253
EIR CONECTION .................................................................................................... 254
EIR DATA TRANSCRIPT ........................................................................................ 255

EN/LZT 123 3451 R3A i

GSM Data Transcript

t io
en na
lly
t
In

Bl n
a
k

ii EN/LZT 123 3451 R3A

 10 Home Location Register

INTRODUCTION
This chapter will consider the functions of the Home Location
Register (HLR) and explain the terminology used.

The HLR can be realized by being integrated into the MSC/VLR

or it can be realized as a stand-alone node. This chapter will
consider which sub-files are required to implement the stand-
alone HLR.

EN/LZT 123 3451 R3A 231

GSM Data Transcript

FUNCTIONS OF THE HOME LOCATION REGISTER

The purpose of the Home Location Register (HLR) is to keep a
record of all the subscriptions of all registered subscribers for
the network. Any changes made to their subscription data,
whether by the network operator or by the user themselves, will
be made to the HLR in the first instance and then update the
VLR where the MS is currently located.

The number of HLRs in a network will be dependent on the

number of subscribers registered with the network. The
minimum number of HLRs is one.

The HLR has a number of functions as shown in Figure 10-1.

Within each function there will be a number of function blocks.

HOME LOCATION REGISTER

GMSC
MAP VLR
DATABASE COMMUNICATION AUC
- Subscriber Data -SCCP AUC-10
- Triplets - C7 FNR
IN

ANALYSIS:
ADMINISTRATION
- MSISDN => IMSI
- Commands IOG
- Call Forward
- printouts
- Number Series

Figure 10-1. Functions in the Home Location Register

ADMINISTRATION
There are a number of function blocks that deal with command
handling. The commands will be accessed from alphanumeric
terminals connected to the IOG or via X.25 connections to a
remote terminal.

232 EN/LZT 123 3451 R3A

 10 Home Location Register

MAP COMMUNICATION
The HLR can only communicate with other nodes in the GSM
network using MAP communication. A number of function
blocks exist supporting the different MAP operation, e.g.,
HLUAP handling location updating, or HLCAP handling
location cancellation.

The HLR needs to communicate with a number of other nodes:

GMSC, VLR, AUC and SMS-SC. To support this
communication the HLR must use MTP and SCCP.

SCCP
All MAP messaging uses SCCP to analyze the called GT. If the
called GT belongs to another node then SCCP will use the
services of MTP.

SCCP must have the GT analysis defined in order to terminate

and route MAP messages between the nodes it communicates
with. The GT analysis must specify NP=7 (MGT) to support
Location Updating from VLRs.

MTP
If the HLR is of the stand-alone type then MTP must be defined
to allow the nodes to communicate with each other.

Since PCM systems are expensive due to transmission costs, it

is advisable to allocate more than one signaling link over one
PCM system. The problem of putting too many signaling links
on the one PCM is the danger of the PCM system becoming
faulty; communication with the HLR could be put at risk.

DATABASE
A number of databases exist to support the storage of subscriber
data. The database is in effect the VLR.

Terminology
Subscriber data defines what the MS has subscribed to in the
way of Basic Services and Supplementary Services. Below is a
description of the basic terminology used regarding subscriber
data.

EN/LZT 123 3451 R3A 233

GSM Data Transcript

Basic Service
Basic services are a collection of Teleservices or Bearer
services, which define what the MS has subscribed to. An
explanation of all Basic Services are found in the Application
Information for function block HTRAN.

To help describe the Basic Services use is made of the OSI

model.

TS Application Application TS
Presentation Presentation
Session Session
Transport Transport
BS Network Network Network BS
Datalink Data Link Datalink
Physical Physical Physical

Figure 10-2. The OSI Model

Teleservice
A teleservice is a user, which has the capability to interpret the
information carried between two applications. Examples of a
teleservice would be Telephony, Telex and Short Message. The
teleservice will make use of all seven layers of the OSI model.

Bearer Service
A bearer service only transfers information between two nodes.
The bearer service does not understand the information it is
transferring, however, it will ensure that the information is
transferred correctly. The information being transferred might
be a file. There are two bearer services: Asynchronous and
Synchronous. Each of these bearer services can support different
transfer rates.

Basic Service Group

Each of the Basic Services belongs to one of six Basic Service
Groups (BSG). There are four BSGs for teleservices and two
BSGs for bearer services.

The six Basic Service Groups are as follows:

234 EN/LZT 123 3451 R3A

 10 Home Location Register

1. BSG - TS10 which supports Speech, Telephony (THY)

being one of the basic services.
2. BSG - TS20 which supports Short Message, originating
(SMSMO) and terminating (SMSMT).
3. BSG - TS60 which supports the FAX services, Alternate
Speech/Fax (ALTFAX) and FAX (AFX3).
4. BSG - TSD0 which supports Auxiliary Speech, Auxiliary
Speech (AUXTHY).
5. BSG - BS20 supports Asynchronous communication,
DCDA (Data Circuit Duplex Asynchronous)
6. BSG - BS30 supports Synchronous communication, DCDS
(Data Circuit Duplex Synchronous).

Supplementary Service
Supplementary services enhance the basic service, e.g., the MS
might already be in call but needs to make another call, for this
to happen the MS needs the supplementary service HOLD. This
puts on hold the current call allowing the MS to make a call and
then switch between the two calls.

Supplementary services work on a per BSG basis, effecting all

basic services belonging to a particular BSG.

Certain supplementary services not only require the MS to be

subscribed to the supplementary service but the supplementary
service must also be active. The Call Forwarding and Call
Barring supplementary services are examples of this.

Subscriber Data
A number of different types of subscriber data are stored in the
VLR, as shown below:

Permanent Subscriber Data

The MSISDN/IMSI number defined with the command
HGSUI.
A list of the services (SUD) that the MS is subscribed to,
command HGSDC.
If data services are required then an AMSISDN would be
allocated, command HGAMI. Also the HLR bearer
capability must have also been defined, command HGBDI.

EN/LZT 123 3451 R3A 235

GSM Data Transcript

Supplementary Service Data

Details the supplementary services that have been activated.
If the operator activates the supplementary services,
command HGSSI is used, if a subscriber activates the
service either the menu on the mobile can be used or service
codes using the * and # keys e.g. **62*085850000# for the
service Call Forward when Not ReaChable (CFNRC).
Store information about the supplementary service, e.g., the
forward to number if the Call Forwarding supplementary
service is active.

Location Data

The current location of the MS will be stored. This

information can be printed out with command HGSDP,
using an extra parameter LOC or ALL.
When the MS performs a Location Update the VLR will
inform the HLR of the new location, and the HLR will
change the address.

Triplets
The triplets are fetched from the AUC and stored in the
HLR. Up to ten triplets can be stored per MS. The triplets
are transferred to the VLR on request (a maximum of five
triplets can be transferred at a time).
The triplet consists of the random number (RAND), a
Signed RESponse (SRES) that is used for authentication
purposes, and a Ciphering key (Kc) that is one input
required to cipher the message.

Message Waiting
If the MS has a message waiting in the SMS-SC, then a flag
will be set and the SC address will also be stored.
The command HGMWP is used to see a list of the messages
that have not been received by the MS. Note: it is not
possible to see the message itself, only the information
relating to it.

236 EN/LZT 123 3451 R3A

 10 Home Location Register

ANALYSIS
A number of analysis areas exist to support the different
functions of the HLR.

IMSI to MSISDN
This analysis has the association between the MSISDN and the
IMSI. If the MS has data services then AMSISDN analysis
would be done here.

The output of the analysis is a pointer to access the database to

obtain all the relevant information about the subscribers data.
This data is used to determine whether the MS is subscribed for
the requested service.

Call Forwarding
There are four call forwarding supplementary services: Call
Forward Unconditional (CFU), Call Forward on Busy (CFB),
Call Forward on No ReplY (CFNRY) and Call Forward on Not
ReaChable (CFNRC).

In all cases the MS must have subscribed to the requested

service (HGSDC) and must then activate the service with
command (HGSSI) or from the MS. Before the subscriber can
use the Call Forwarding Supplementary Service a Call Forward
number must be entered and stored in the International Format.
When this number is entered, it is checked for the following:

1. To see if it is a restricted number, e.g., an emergency

number,
2. That it is in International Format, if it is not then it needs to
be modified accordingly prior to it being stored.

Roaming Characteristics
The use of roaming characteristics allows the HLR to know the
characteristics of a VLR or all the VLRs in one PLMN. The
Roaming characteristics are set by command HGRCI.

The following characteristics are available (see AI: HTRAN).

AOCC - Advice Of Charge (Charging) supported - This

characteristic is only applicable when MAP version 1 is used
between the HLR and VLR. When a mobile subscriber
having Advice of Charge Charging provided roams into a
VLR not characterized as AOCC, the whole PLMN may be

EN/LZT 123 3451 R3A 237

GSM Data Transcript

restricted until a new Update Location message is

performed from a VLR supporting Advice of Charge.
ROAMREST - Roaming Restrictions in this PLMN.
TRAFFV2 - Traffic with MAP Version 2 allowed - If
TRAFFV2 is active then MAP V2 signaling is allowed
between the HLR and VLR. TRAFFV2 is controlled by
exchange property MV2RESTRICTION, and is only active
if this property is set to 1.
RSERV - Roaming allowed when the Regional Services are
not supported.
TRAFFV3 - Traffic with MAP Version 3 allowed between
the HLR and the VLR.

Closed User Group

The Closed User Group (CUG) is an optional supplementary
service. A brief description will be given below.

CUG: IC=0046-000001

ICB & OA
OCB & IA

MSISDN= 46707570571
MSISDN=46707570111
CUG Index =0

NONE & OIA

MSISDN= 46707570992

Figure 10-3. Example of a Closed User Group

The Closed User Group (CUG) supplementary service allows

subscribers connected to PLMN/ISDN networks to form a group
where access is generally restricted to subscribers outside of the
CUG but not within the CUG. A subscriber can in fact be a
member of more than one CUG. To allow charging to take place

238 EN/LZT 123 3451 R3A

 10 Home Location Register

the parameter UGC can be used as a branch parameter in

charging analysis.

It is possible to put restrictions on subscribers for calls within

the CUG (Intra CUG) as well as giving a subscriber access to
others outside of the CUG (Inter CUG).

Intra CUG
Intra CUG restrictions can bar the subscriber from making calls
to other CUG members (OCB Outgoing Call Barring) or from
receiving calls from other CUG members (ICB Incoming Call
Barring). The default is to have no restrictions.

Inter CUG
Inter CUG access allows a subscriber to make or receive a call
to another subscriber outside of the CUG. The options being
Incoming Access (IA), Outgoing Access (OA), or Outgoing and
Incoming Access (OIA). The default setting is to have no
access.

Example of Commands

HGCUI:MSISDN=46707570111,INDEX=0,IC=0046-1;
HGCSC:MSISDN=46707570111,BSG=TS10,ACCESS=IA;
HGCUC:MSISDN=46707570111,INDEX=0,RESTR=OCB;

Regional Services
Regional Services are a collection of different services that use
similar functions. Regional services require the use of functions
in both the HLR and the VLR. To allow the subscriber to use
the service, then subscriber data REGSER is added to MSs
profile. The parameter RCO is used as a branch parameter in
charging analysis.

A brief description of each of the services will be found in the

following paragraphs.

The data transcript required in the HLR, is standard for each of

the three following services, but differs for each service in the
MSC/VLR. The commands HGZNI, HGSDC and HGEPC are
required in the HLR. Zone codes are used to uniquely identify a
geographical area in the PLMN, defined using the command
HGZCI.

EN/LZT 123 3451 R3A 239

GSM Data Transcript

Note: Emergency calls are not restricted by these regional

services.

Local Subscription
Local subscriptions allow the operator to restrict where an MS
can be used. It would usually be limited to a small number of
cells. In return for the restricted service it is likely that the
subscriber is offered a cheaper tariff charge.

Regional Subscription
Regional subscriptions allow the MS to have access to the
network over a larger area but may be restricted from using a
very busy cell. Again, it is likely that the subscriber will agree
to the reduced service due to a smaller tariff charge. By offering
cheaper tariffs, the operator is able to increase the number of
subscribers in the network without impacting already very busy
cells.

Both regional and local subscriptions allow the operator to

restrict access to the network for the MS.

Regional Differential Charging

Regional differential charging allows the MS complete access
to the network. However, different calls could be charged at a
different rate, depending on where the call was initiated. For
example, a very busy cell might have a higher tariff than a cell
in a rural location.

HLR Redundancy
If an HLR fails, subscribers with records in that HLR will not be
able to roam or receive calls. For this reason HLR Redundancy
can be implemented so as to safeguard subscriber data. This is
achieved by using two HLRs working in a load-sharing manner
referred to as a mated HLR pair. In normal operation, both
HLRs are used to enable access to subscriber data. However
when one HLR fails the mated HLR picks up all traffic normally
routed to the failed HLR (in addition to its own traffic).

This setup can be used to protect against disasters such as fire,

as well as signaling failures towards an HLR and lack of
availability due to HLR restarts.

The mated HLRs must both contain / support the same

functionality, the data must be compatible including the mated

240 EN/LZT 123 3451 R3A

 10 Home Location Register

subscriber data. To support this feature SCCP routing data and

the mated HLR address must be entered into each HLR. There
must also exist a connection (direct or indirect) to enable the
HLRs to communicate with one another for example Update
Subscriber Data MAP messages.

Subscribers are allocated a primary and a redundant HLR.

The primary HLR holds the permanent and temporary
subscriber data and automatically updates the redundant HLR
with the temporary data.

The Number Series Analysis, on the IMSI-series, is used to

determine if an IMSI is defined as redundant. The block
HNSAN contains functionality for the general-purpose number
analysis in the HLR. Commands used for this function are
HGNSI and HGPAI, an example is shown below:

HGNSI: ONSA=1, NS=2400770120, CHAR=REDUN;

HGPAI: USRF=REDUN, NAPI=2, NAI=4, ONSA=1;

The HLR Redundancy function is activated (to mated HLRs) by

the command HGRFI.

HGRFI:WMODE=MATED;

EN/LZT 123 3451 R3A 241

GSM Data Transcript

CALL FORWARDING
Two examples of the use of Call Forwarding now follow with
an explanation.

CALL FORWARD UNCONDITIONAL

HLR CFU-1

1 G
PSTN
MSC VLR
4

1
4

BSC
B-Subscriber
46 70 757 0000

A-Subscriber
C-Subscriber
46 8 585 0000

Figure 10-4. Unconditional Call Forwarding

1. The A-subscriber dials 46707570000 and will be routed to

an MSC with Gateway functionality (GMSC) belonging to
the PLMN of the MS being called.
2. The call will be routed to the GRI route and a MAP message
Send Routing Information or Routing Information Request
will be sent to the HLR.
3. When the HLR checks the MSs subscription, the
supplementary service CFU is found to be active. The HLR
returns the C-number to the GMSC instead of an MSRN.
4. The GRI will now control how the C-number is to be
handled. In the GRI route data, parameters MIS1 points to
the B-origin and MIS2 gives the Charge Origin, for a C-
number. Since the C-number is returned in the international

242 EN/LZT 123 3451 R3A

 10 Home Location Register

format, the B-origin chosen to analyze the number could be

the origin containing international numbers or point to the
origin used for MO calls. The call will then be routed in the
normal way.
Function block GRR is involved in the handling of the call. The
block will on reception of the C-number generate an end-of-
selection code 2844. This ES can then be used for routing to an
announcement informing the A-subscriber that the call is being
re-routed. See figure 9-12, in chapter 9, for example of Call
Forwarding data transcript.

CONDITIONAL CALL FORWARD

CFNRY-1
HLR

3 3

1 G
PSTN
MSC VLR
5

1 4
4
5
4
BSC
B-Subscriber
46 70 757 0000

A-Subscriber
C-Subscriber
46 8 585 0000

Figure 10-5. Conditional Call Forward

1. The A-subscriber dials 46707570000. This will be routed to

an MSC with Gateway functionality (GMSC) belonging to
the PLMN of the MS.
2. The call will be routed to the GRI route and a MAP message
Send Routing Information or Routing Information Request
will be sent to the HLR.

EN/LZT 123 3451 R3A 243

GSM Data Transcript

3. The HLR will carry out subscription checks for the MS, then
ask the VLR for an MSRN. The MSRN will be returned to
the GMSC and then routed to the correct MSC/VLR.
4. The MSRN will be terminated and then the MS will be
paged.
5. When the user does not answer the phone the MSC/VLR
will then, with the help of function block MRR, route the
call to a C-number. The C-number will use parameter BO
from IMSI number series analysis (MGISI) to start the
analysis of the B-number. This can be treated as a MO call.
Function block MRR will generate the CO parameter.
Function block MRR will generate one of three end-of-selection
codes which can be used to send an announcement that the call
is being re-routed. The three ES codes are as follows:

ES=1615 for call forwarding on mobile subscriber busy.

ES=1616 for call forward on no reply.
ES=1617 for call forward on mobile subscriber not
reachable.
See figure 9-13, in chapter 9, for example of Call Forwarding
data transcript.

MOBILE INITIATED ACTIVATION OF CALL FORWARDING SERVICE

Before the Call Forwarding activation is accepted checks are
made on the forward-to-number, ensuring that it is in the
international format and that the number is not restricted. If the
number is not in the international format then the activation
should be converted in the CF analysis.

244 EN/LZT 123 3451 R3A

 10 Home Location Register

HLR

2 3

G
MSC VLR

2 3 3
3
BSC 2

Figure 10-6. Activation of Call Forwarding from MS

1. The subscriber wishes to activate unconditional call

forwarding. This can be done from the menu or by dialing
**21*085850000#.
2. The MS will generate the message and send it to the HLR
where its subscription is held.
3. The HLR will check the C-number in an analysis table. It
ought to be noted that the C-number sent, in this example, is
in an unknown format. Before the C-number can be stored
and the MS informed, the number must be converted into the
international format, by removing the 0 and inserting the
country code.
The three conditional call forward services have the following
codes:

**62*085850000# call forward when not reachable.

**61*085850000# call forward on no reply.

**67*085850000# call forward on busy.

EN/LZT 123 3451 R3A 245

GSM Data Transcript

STAND-ALONE HLR
The main reasons for having a stand-alone HLR is to reduce the
processor load on the integrated MSC/VLR and also to increase
the number of subscribers defined in the HLR. A theoretical
maximum of 500 000 subscribers but usually limited to around
200 000 subscribers.

The hardware required for the stand alone HLR is shown in

Figure 10-7 and then the DT is required.

HARDWARE REQUIREMENTS IN A STAND-ALONE HLR

VLR HLR EIR

ST_HLR
TS1 TS2
2MBit Q.703 ST2
ETC MUX RP
64kBit

V.35

EIR
GS CP
AUC

V.35
ST2 HLR
PCDD MUX Q.703
ST2 EIR ST2 RP
MUX 64kBit
RP RP RP

CP

Figure 10-7. Connection of the Stand alone HLR

The hardware of the stand-alone HLR consists of a CP pair,

IOG, C7 signal terminals and MultipleXors (MUXs).

The MUXs are required because the HLR does not have a
Group Switch. The purpose of the MUX is to insert/drop a
number of 64 Kbit/sec circuits from signal terminals to/from a 2
Mbit/sec PCM. The MUXs require no DT, as they do not belong
to AXE.

246 EN/LZT 123 3451 R3A

 10 Home Location Register

Typically, the EIR and AUC are realized on a common VAX

platform, even though they are separate nodes. Both the EIR and
the AUC will have their own software. The VLR is the only
node to communicate with the EIR; similarly, the HLR is the
only node to communicate with the AUC.

From Figure 10-7, it can be seen that two timeslots are being
used between the VLR and the HLR; timeslot 1 is used to
communicate to the HLR and timeslot 2 is used to communicate
to the EIR.

DATA TRANSCRIPT REQUIRED FOR A STANDALONE HLR

IOG, file and alarm definition.

APZ, C7 ,OMS (if any) and HRS SAE
HRS properties (HGEPC)
C7 definition + de-blocking
HLR Bearer Capability Data
RP, EM, ST2 definition + de-blocking
Own calling address + Roaming characteristic (if any)
SCCP-analysis
Subscriber definition (customer)
Counters and Statistics (if any)
Call Forward Analysis

Figure 10-8. DT Required for Stand-Alone HLR

The DT is fairly self-explanatory, but take into account the

comments below.

Sub-file 00001: There is no charging in the HLR, so no

charging volumes shall be defined. This means that usually
the ST_HLR only has one SPG. The volume
RELVOLUMSW can take the extra size from the
CALLVOLUME (if exists) or steal some space from
EXCHVOLUME if necessary. The reason to have a big
RELVOLUMSW is that the reload (consists of all subscriber
data) files for an ST_HLR is much bigger than for a VLR.

EN/LZT 123 3451 R3A 247

GSM Data Transcript

Sub-file 12000 only files belonging to blocks used in the

HLR are defined. Files that belong to traffic (speech and
data transmission) and charging are not defined. Do not
forget to define the file HLRDUMP
When defining a VLR without HLR no commands starting
with HG shall be defined. The HRS SAE shall not be
defined.
Everything else can be defined the same way as a combined
HLR/VLR.

248 EN/LZT 123 3451 R3A

 10 Home Location Register

DATA TRANSCRIPT

SUBSCRIBER DATA
Examples of defining subscriber data has been covered in a
previous chapter. Figure 10-9 is for completeness only.

!80000,1!
!**** HLR, SUBSCRIBER DATA ****!
!**** DEFINITION OF PROFILES ****!

HGSPC:PROFILE=1, SUD=BAIC-1&OFA-1&TS11-1;
HGSPC:PROFILE=2, SUD=BICRO-1&OFA-1&TS11-1;
HGSPC:PROFILE=3, SUD=CFU-1&OFA-1&TS11-1;

!**** DEFINITION OF SUBSCRIPTION ****!

HGSUI:MSISDN=46 70 7570000, IMSI=240 01 0000000000, PROFILE=1;

!**** ADDITIONAL MSISDN SUBSCRIPTION ****!

HGAMI:MSISDN=46 70 7570000, AMSISDN=46 70 7570002, BC=221;

!16200,1!
!**** HLR GSM BEARER CAPABILITY DATA ****!

HGBDI:BC=221, RCR=0, UDI, RC=1-0-2, ACC=1-3-1, ACCST=1-0-0-2, ITN=0;

Figure 10-9. Example of the Definition of Subscriber Data

EN/LZT 123 3451 R3A 249

GSM Data Transcript

CALL FORWARDING
!**** DEFINITION OF SUBSCRIBER DATA ****!

HGSPC:PROFILE=2, SUD=CFU-1&CFB-1&CFNRC-1&CFNRY-1&OFA-1;
HGSDC:MSISDN=46 70 5850000,PROFILE=2;

!**** ACTIVATION OF SUBSCRIBER SERVICE (BY COMMAND) ****!

HGSSI:MSISDN=46 70 5850000, SS=CFU, FNUM=087570000;

!**** DEFINITION OF CALL FORWARD ANALYSIS TABLE ****!

HGFZI;

!**** ANALYSIS OF NUMBERS IN INTERNATIONAL FORMAT ****!

HGFSI:FW=0-46 112, REST; !EMERGENCY NUMBER RESTRICTED !

HGFSI:FW=0-46 7075701, REST; !ROAMING NUMBERS RESTRICTED !

HGFSI:FW=1-08, M=1-46, F=0; !CONVERT TO INTERNATIONAL FORMAT !

HGFSI:OFA=2; !ORIGIN 2 IS OPEN FOR ALL NUMBERS!

HGFAI;

Figure 10-10. Definition and Use of Call Forward Analysis

Tables

Profile 2 has been given all four call-forward supplementary

services. Origin of Forward Analysis (OFA) is also given which
directs the analysis to origin 1.

The CFU supplementary service is activated, the Forward

NUMber is given in the unknown format.

The FNUM is analyzed in origin 1. If a number begins with 08

(FW=1-08), then one digit is removed and 46 is added (M=1-46)
and then forwarded to origin 0 (F=0) to check if any restrictions
apply. In this instance there are no restrictions so it is a valid
number.

250 EN/LZT 123 3451 R3A

 10 Home Location Register

AUC/EIR
The AUC and EIR are often realized on the same VAX
computer platform. Both have their own node identity with
different subsystem numbers (parameter SSN in the called or
calling address).

The AUC can also be realized within the AXE using an RPD,
this is referred to as AUC-10 and is realized as an Application
Module.

AUC CONNECTION
The AUC generates triplets at the request of the HLR.

SP=2-500
HLR
AUC
/EIR
MAP
MAP

The HLR asks the MSC/

AUC for triplets. VLR
MS

BSC
BTS
Signalling path
Traffic path

Figure 10-11. Connection of AUC

1. When the HLR requires more triplets, a MAP operation is

sent from the HLR to the AUC. The AUC will generate the
triplets and then return them to the HLR.
2. At the request of the VLR, then the HLR will send triplets to
the requested VLR. The number sent is determined by
exchange property AUTOMAXTRIPLETS.

EN/LZT 123 3451 R3A 251

GSM Data Transcript

AUC DATA TRANSCRIPT

In Figure 10-12, only the extra or changed data transcript is
shown to introduce the connection to the AUC. Sub-files 13000
(Exchange Properties) and 75500 (SCCP Data) are affected.

!*** EXCHANGE PROPERTIES ***!

HGEPC:PROP=AUCTRANTYPE-2; !** SCCP TT USED FOR AUC **!

!*** SCCP ***!

C7NPI:SP=2-500, CON; !** AUC **!
C7NSI:SP=2-500,SSN=10; !** SSN FOR AUC **!
C7GCI:GTRC=2, PSP=2-500, PTERM; !** GT ROUTING CASE **!

!*** GT ANALYSIS FOR AUC, IMSI NUMBERING PLAN (NP=6) ***!

C7GSI:TT=2,NP=6,NA=4,NS=240 01 ,GTRC=2;

Figure 10-12. AUC Data Transcript

1. Exchange property AUCTRANTYPE is used to determine

the value of the translation type (TT) is used in GT analysis
when sending message to the AUC.
2. The AUC is defined as cooperating at SCCP level and then
defined as being an AUC (SSN=10). The SCCP message
will be terminated at the AUC on the DPC and the SSN
using the parameter PTERM.
3. The GT analysis uses a very short number series as a unique
TT value is being used.

AUC-10 CONNECTION
The AUC-10 uses an RPD to generate the triplets. For
redundancy purpose two RPDs will be defined. However,
adding more RPDs can increase the capacity.

The MAP interface is still used between the HLR and the AUC-
10.

252 EN/LZT 123 3451 R3A

 10 Home Location Register

AUC-10 DATA TRANSCRIPT

Figure 10-13 shows the data required defining the AUC-10.
This is not a complete list. There are a number of properties and
size alterations, which also need to be considered but are not
shown. These could be found using the AI.

!**HARDWARE ALLOCATION**!
EXRPI:RP=36, TYPE=RPD1A;
EXRPI:RP=37, TYPE=RPD1A;

EXRUI:RP=36&37, SUID="CAA 140 002 R7A01"; !RPFDR!

EXRUI:RP=36&37, SUID="CAA 140 004 R6A01"; !RPEXR!
EXRUI:RP=36&37, SUID="CAA 140 124 R1A02"; !AGENR!

EXEMI:EQM=AGEN-0&-1, RP=36, EM=0; !AUCS !

EXEMI:EQM=AGEN-2&-3, RP=37, EM=0; !AUCS !

BLEME:RP=36, EM=0;
BLEME:RP=37, EM=0;

BLRPE:RP=36;
BLRPE:RP=37;

!**SCCP**!
C7GSI:TT=2, NP=6, NA=4, NS=24001751, LSSN=10,GTRC=10;
C7GCI:GTRC=10, PSP=OWNSP, PSSN=10;

!**SUBSCRIBER DATA**!
AGKDI:DESKEY=0000000000028080,KIND=1;

AGSUI:IMSI=240017510000000, EKI=356C6B11393F272BC4136B003330DBF5,
KIND=1,A3A8IND=0;

HGAIC:IMSI=240017510000000, SUBAI=MAP, CHECK;

Figure 10-13 Example of Data Transcript Defining the AUC-10

1. The hardware allocation is defining the RPD, software, EM

and de-blocking it. Again, note that the EM is de-blocked
before the RPD.
2. Since a MAP interface is used, GT analysis needs to be
defined as well. The address information (AI) contains the
IMSI, E.212 number plan.
3. The subscriber data is used as an example. In reality
commands AGSUI and HGAIC need to be entered for each
subscriber. This would be done automatically when a new
subscription is taken out.

EN/LZT 123 3451 R3A 253

GSM Data Transcript

EIR CONNECTION
The EIR is a database storing information on the mobile
handsets, based on the IMEI. If a handset is stolen the IMEI is
entered in the black list, thus barring the handset from being
used.

EIR address: 46 705 540 0000

HLR SP=2-500
EIR IMEI is sent from
MAP
MAP MS.
MSC/
VLR
MS
The MSC/VLR
sends the IMEI to BSC
BTS
the EIR for check.
Signalling path
Traffic path

Figure 10-14. EIR Connection

1. At the request of the system the MS sends the IMEI up to the

MSC/VLR. The MSC/VLR then forwards the IMEI in a
MAP operation to the EIR. The EIR responds with a MAP
operation indicating whether the IMEI is in the Black, Grey
or White list. The MSC/VLR will act according to its own
parameter settings.

254 EN/LZT 123 3451 R3A

 10 Home Location Register

EIR DATA TRANSCRIPT

Only the data transcript required for the EIR is considered. The
affected sub-files are 75400 (Own Calling Addresses) and
75500 (SCCP Data). Remember that the data shown below is
entered into the HLR as only the HLR node can communicate
with the EIR.

!**** EIR ADDRESS ****!

MGEAI:EIRADDR=4-46 705 5500000;

!**** SCCP ****!

C7NPI:SP=2-500,CON; !EIR!
C7NSI:SP=2-500,SSN=9; !SSN FOR EIR!

!**** GT ANALYSIS FOR EIR ****!

C7GCI:GTRC=2, PSP=2-500, PTERM;
C7GSI:TT=0, NP=1, NA=4, NS=46705500000,GTRC=2;

Figure 10-15. EIR Data Transcript

1. The EIR address must be entered by command. The address

is entered as an international number, indicated by 4-46.
2. SCCP data then needs to be added. The EIR needs to be
defined as cooperating at SCCP level and then define the
subsystem number (SSN=9). PTERM indicates that the MAP
message will be terminated using the DPC + SSN.
3. The GT analysis is added in the same way as usual.

EN/LZT 123 3451 R3A 255

GSM Data Transcript

t io
en na
lly
t
In

Bl n
a
k

256 EN/LZT 123 3451 R3A