PS Datacom in HLR: Objectives

PS Datacom in HLR
Chapter 10
This chapter is designed to provide the student with the

knowledge of the role played by the HLR in a GPRS network.
OBJECTIVES:
Upon completion of this chapter the student will be able to
• Explain how the HLR is reused for GPRS

• Handle GPRS subscriber data in the HLR
WCDMA Systems HLR Operation, CN 1.5 / GSM HLR Operation, R 9.0
Intentionally Blank
EN/LZU 123 3977/2 A

LZM 112 122
10 PS Datacom in HLR
Table of Contents
Topic Page
GPRS SUPPORT IN HLR ..................................................................223

GENERAL...................................................................................................................223
GPRS DATA ...............................................................................................................224
GPRS SUBSCRIPTION DATA ...................................................................................224
GPRS SUBSCRIBER DATA.......................................................................................225
GPRS HLR DATA .......................................................................................................232
GPRS DATA ADMINISTRATION ......................................................233

ADMINISTRATION OF GPRS SUBSCRIPTION DATA .............................................233
ADMINISTRATION OF GPRS SUBSCRIBERDATA..................................................235
ADMINISTRATION OF GPRS HLR DATA .................................................................240
INTERWORKING OF GPRS HLR .....................................................242

NEW FUNCTION BLOCKS ........................................................................................243
APT SAES FOR GPRS...............................................................................................243
AXE EXCHANGE PARAMETERS.....................................................245
EN/LZU 123 3977/2 A –i–

LZM 112 122
Intentionally Blank
– ii – EN/LZU 123 3977/2 A

LZM 112 122
GPRS SUPPORT IN HLR
GENERAL
This optional feature introduces in the HLR the subscriber’s
data storage and mobility management capabilities essential to
provide the General Packet Radio Service (GPRS) in a GSM /
WCDMA Systems network.
The Home Location Register (HLR) is the database that holds

subscription information for every person who has bought a
subscription from the GSM/GPRS/WCDMA Systems operator.
The HLR stores information for Circuit Switched (CS) and for
Packet Switched (PS) communication. The HLR contains
information about, for example, supplementary services,
authentication parameters, and whether or not packet
communication is allowed.
Ericsson GPRS Network Architecture

Packet
Data Networks
e.g. Internet
SS
AUC EIR
GPRS
HLR
GGSN
PSTN
or/and other MSC/VLR
networks SGSN
GMSC
BSS
BTS BSC
NF 611.1 UTRAN
NF 633.1 BTS RNC
NF 636.1
Figure 10- 1 Ericsson GPRS Network Architecture.
In addition, the HLR includes information about the location of

the Mobile Subscriber. For GPRS, subscriber information is
exchanged between HLR and SGSN (Serving GPRS Support
Node). Note that the authentication triplets for GPRS are fetched
directly from the HLR to the SGSN, that is, do not use the
MSC/VLR, as is the case with CS GSM.
EN/LZU 123 3977/2 A - 223 -

LZM 112 122
The HLR stores the subscription information regarding mobile-

terminated and mobile-originated Short Message Services
(SMS), that includes the option of Short Message (SM) transfer
via the SGSN to the MS. The Short Message Service Gateway
MSC (SMS-GMSC) interrogates the HLR for routing
information and SMS information, and delivers the short
message to the MSC/VLR or SGSN of the recipient MS.
No new hardware is required in the HLR. The CP load due to a

GPRS subscriber is expected to be 25% less than the CP load
due to a non-GPRS subscriber.
GPRS DATA
GPRS SUBSCRIPTION DATA

GPRS subscription is initiated by command. MSISDN and IMSI
must be specified in the command for the mobile subscriber.
The Network Access Mode of the subscriber is added to the

subscriber’s record in HLR. It determines the type of
transmission that the subscriber is allowed to perform. For
packet mode data transmission the subscriber needs access to
the GPRS network, that is, he must be allowed to be temporarily
registered in an SGSN.
In that case, the HLR contains GPRS subscription data and

GPRS routing information for that subscriber.
If the subscriber has access to packet data transmission only, he

can not be temporarily registered in an MSC/VLR.
HLR stores information for authentication and ciphering from

the AUC, and provides it to the SGSN upon request.
An exchange property changeable by command determines in

HLR if the subscription can be initiated regardless of whether
authentication data can be allocated to the new mobile
subscriber at that moment or not. This allows connection of a
new mobile subscriber even if the communication to the
Authentication Center is not available, or IMSI is not found in
the Authentication Center.
The authentication data for those new subscribers will be

allocated later on when the temporary problem is solved.
– 224 – EN/LZU 123 3977/2 A

LZM 112 122
Network Access Mode (NAM)
The Network Access Mode of a subscriber defines if the

subscriber is registered to access to the GPRS network only, to
the non-GPRS network or to both.
All subscribers always have a NAM, with a default value set at

subscription initiation.
A new AXE parameter has been defined to set the initial default
value of the subscriber NAM at subscription initiation.
If the optionally ‘GPRS functionality in HLR’ is active this

AXE parameter may have the values ‘GPRS only’, ‘both non-
GPRS and GPRS’ and ‘non-GPRS’ only. Otherwise, this AXE
parameter may only have the value ‘non-GPRS’ only.
The Subscriber Initiation to GPRS is performed when the

maximum number of GPRS subscribers allowed in HLR,
limited by a new AXE parameter (defined to limit the number of
subscribers with access to the GPRS network), is not exceeded.
If surpassed, the subscription is discarded.
GPRS SUBSCRIBER DATA

The data field in the HLR for the subscriber data is extended to
handle GPRS subscriptions.
The term GPRS Subscriber Data is used to designate the GPRS

information associated with a subscriber who is stored in HLR:
- IMSI, MSISDN
- NAM, PDP-context list {PDP type (IPV4), PDP address

which may be empty, QoS for the subscribed profile, Access
Point Name and Visited PLMN Address allowed}
- Permanent subscriber data: Data that can only be changed by

administrative means, for example, operator determined
barrings applying to GPRS, subscription or not subscription
to Basic Services (Teleservice Short Message MT/PP
(Mobile Terminating/Point-to-Point)-TS21- and (Teleservice
Short Message MO/PP (Mobile Originating/Point-to-Point)-
TS22-Transfer of Short Message Option- TSMO-.
- GPRS Location Data
EN/LZU 123 3977/2 A - 225 -

LZM 112 122
Home Location Register
GPRS Subscriber Data:

IMSI,MSISDN
NAM
PDP-context Subscription Record
Other permanent subscriber data
Figure 10- 2 GPRS Subscriber Data in HLR
The HLR updates the SGSN with that information upon a

location-updating information from the SGSN or when it is
changed by administrative means
GPRS Service Subscriptions

The IMSI of a subscriber who has access to the GPRS network
may be associated with this IP address (es) and the other
necessary subscription information for packet mode
transmission
Packet Data Protocol (PDP) Context

Subscription data required to establish routing information in
nodes involved in the transfer of Packet Data Unit for a
particular Packet Data Protocol (PDP). The PDP contains the
information describing the connection between an MS and an
external network.
The elements of a PDP-context subscription Record (referred

to as PDP context) are:
• Access Point Name

• PDP type
• PDP Address
– 226 – EN/LZU 123 3977/2 A

LZM 112 122
• Visitor PLMN Address Allowed Flag

• Quality of Service
Access Point Name (APN)
Label or full-qualified domain name according to Domain Name

System naming conventions that identifies the packet data
network to which the GPRS user wants to connect. The Access
Point Name is used to determine which GGSN (Gateway GPRS
Support Node) to use.
PDP type
This parameter indicates which type of protocol the mobile
subscriber uses. It is always Internet Protocol version 4.
PDP Address
This parameter indicates the IP address. At this point, we have
to distinguish:
- Dynamic PDP Addressing
The Packet data Protocol Address associated with the user's

Mobile Id is allocated on a per need basis.
- Static PDP Addressing
The Packet Data Protocol Address associated with the user's

Mobile Id is allocated at PDP Context subscription and is stored
in HLR by the Home PLMN operator.
VPLMN Address Allowed (VPLMNA)

Specifies whether the MS is allowed to use an APN in the
domain of the HPLMN only or additionally the APN in the
domain of the Visitor PLMN.
Quality of Service (QoS)

The set of performance parameters that can be directly observed
and measured at the point where the service is accessed by the
user.
Subscribers may have the choice of paying a premium for a high

QoS or benefiting from a lower tariff and reduced QoS. This
enables the operator to differentiate GPRS services.
EN/LZU 123 3977/2 A - 227 -

LZM 112 122
The Quality of Service consists of multiple data transfer

attributes:
• Reliability class
• Delay class
• Precedence class
• Peak throughput class
• Mean throughput class
Reliability class
Data reliability is defined in terms of the residual error rates for

the following cases:
• Probability of data loss

• Probability of data delivered out of sequence
• Probability of duplicate data delivery
• Probability of corrupted data
The reliability class specifies the requirements of the various
network protocol layers. The combinations of the GTP, LLC
and RLC transmission modes support the reliability class
performance requirements.
The GSNs support the reliability Classes 2,3,4 and 5.
Delay class
Technical Specification GSM 02.60 defines four delay classes

(1 to 4). The network operator should provision adequate
transmission resources on the radio and network communication
channels in order to support the expected number of subscribers
within each cell at a given delay class.
Precedence class
Indicates the relative importance of maintaining the service

commitments under abnormal conditions for example which
packets are discarded in the event of problems such as limited
resources or network congestion.
Throughput Classes
User data throughput is specified in terms of a set of throughput

classes that characterize the expected bandwidth required for a
PDP context.
– 228 – EN/LZU 123 3977/2 A

LZM 112 122
• Peak throughput class is measured in units of octets per

second. It specifies the maximum rate at which data is
expected to be transferred across the network for an
individual PDP context.
• Mean throughput class is measured in units of octets per
hour. It specifies the average rate at which data is expected
to be transferred across the GPRS network during the
remaining lifetime of an activated PDP context.
The SGSN negotiates the QoS with the MS. This happens at
PDP context activation and at inter-SGSN routing area updates.
This may also happen if an operator in the HLR changes the
QoS parameter. The negotiated QoS offered to the MS will
depend on the stored subscriber data, the requested QoS, and the
statistically averaged bandwidth per cell reported from the BSC.
Subscriber's PDP-Context List

Subscriber data stored in HLR as permanent data for the GPRS.
Other GPRS Service Subscriptions
Basic Services
A set of permanent data is given to the mobile subscriber by
means of a specific profile or default one if it is not specified.
Using one of these profiles the subscriber may be subscribed to
one or several Basic Services.
The Basic Services that are applicable to GPRS are:
• Teleservice MT/PP (Mobile Terminating/Point-to-Point)

Short Message
• Teleservice MO/PP (Mobile Originating/Point-to-Point)
Short Message
Transfer of SM Option
The transfer of SM Option is a new parameter in subscriber data

indicating which path should be used for transfer of Terminating
Short Messages (SM).
Two values are possible:
• Transfer of SM via the MSC

• Transfer of SM via the SGSN.
This parameter is valid only in case the subscriber has NAM set
to both GPRS and non-GPRS networks.
EN/LZU 123 3977/2 A - 229 -

LZM 112 122
Operator Determined Barring Services (ODBs)

These ODBs refer to the administrative means used by the
service provider in order to bar a mobile subscriber for outgoing
and/ or incoming calls/short messages and to bar a mobile
subscriber for roaming (outside the Home PLMN or the Home
PLMN country) for administrative reasons.
The ODBs that are applicable to GPRS are:
• Operator Determined Barring of incoming calls services

• Operator Determined Barring of outgoing calls services
• Operator Determined Barring of roaming
Operator Specific Barring Services (OSBs)

The feature Operator Specific Barring (OSB) refers to the
administrative means used by the service provider in order to
bar a mobile subscriber for outgoing calls and/or Short
Messages within its Home PLMN.
The feature Operator Specific Barring provides an operator

flexible means to restrict subscriber activities. The barring can
be applied per subscriber for different types of events.
Updating of the SGSN

When a barring of roaming feature is activated for a subscriber,
SGSN number is analyzed and if the barring condition is
fulfilled, the subscriber location is set to 'barred' and a cancel
location message is sent to the SGSN.
When a barring of roaming feature is deactivated for a

subscriber, if the location was barred the subscriber location is
set to 'Unknown'.
When a location updating is received and a barring of roaming

feature is active, SGSN number is analyzed and if the barring
condition is fulfilled, the received operation is not accepted and
the subscriber location is set to 'barred'.
– 230 – EN/LZU 123 3977/2 A

LZM 112 122
GPRS Subscriber Location Data

HLR performs mobility management for GPRS subscribers by
storing routing information for GPRS subscribes at location-
updating from the SGSN, and informing the old SGSN of the
subscriber’s change of location.
The existing printout LOCATION DATA has been modified to

contain non-GPRS location data and/or GPRS location data.
The GPRS location data will be only printed if the NAM for the
mobile subscriber is ‘only GPRS’ or ‘both GPRS and non-
GPRS’.
The GPRS Subscriber Location Data consists of:
• SGSN Number (ISDN number corresponding to the SGSN

node that handles the area where the mobile subscriber is
roaming)
• Location code:
• Known (when subscriber location is known, that is,
SGSN number is known).
• Unknown (when subscriber location is unknown).
• Restricted (when subscriber location is restricted for
roaming, for example, due to SGSN characterized with
a roaming area characteristic that restricts the mobile to
roam into the SGSN area).
• Barred (when subscriber location is barred for roaming,
for example due to an active Operator Determined
Barring of Roaming for the mobile subscriber).
• MS Purge Indicator (when the mobile subscriber has
been purged in the serving SGSN).
The printout of GPRS subscriber location survey can be
performed by means of the existing command HGLSP. It lists
the location, number of subscribers and characteristics when
optional parameter GPRS is specified. Answer printout HLR
GPRS MOBILE SUBSCRIBER LOCATION SURVEY is
received if this parameter is specified.
If the location is known, the SGSN number is printed. Otherwise

only the word “Unknown”, “Restricted”or “Barred” is printed.
The GPRS location data indicates where a mobile station is

located in the system area. This implies the SGSN number.
EN/LZU 123 3977/2 A - 231 -

LZM 112 122
GPRS HLR DATA
APN Data List

The Access Point Name can be defined in the HLR by a new
command HGAPI. Optionally it can be assigned an APN
identifier.
As already mentioned, this APN data is used in the subscriber

PDP-contexts.
Roaming Area Characterization for GPRS networks

The existing command HGRCI initiates the characterization of a
roaming area.
There exists a roaming area characteristic, which is applicable to

the GPRS network to characterize SGSN roaming areas as
roaming restricted for all defined mobile subscribers in the
HLR.
– 232 – EN/LZU 123 3977/2 A

LZM 112 122
GPRS DATA ADMINISTRATION
ADMINISTRATION OF GPRS SUBSCRIPTION DATA
Initiate/End/Print GPRS subscription: HGSUI/E/P

The initiation of a new subscription will be performed by means
of the existing command HGSUI:
HGSUI: MSISDN=msisdn, IMSI=imsi, [PROFILE=profile];
MSISDN and IMSI must be specified in the command for the

mobile subscriber.
There is no restriction on how MSISDN and IMSI can be

combined.
A set of permanent data is given to the mobile subscriber by

means of a specific profile or a default profile if it is not
specified. Using one of these profiles the subscriber may be
subscribed to one or several Basic Services. The default NAM is
assigned to the mobile subscriber, and the GPRS location code
is set to unknown.
End of subscription is initiated by command HGSUE.
To end the subscription of a mobile subscriber in HLR, the

MSISDN must be specified in the command.
If the subscriber has access to the GPRS network and the

location is known in this network, the CANCEL LOCATION
MAP message (handled by the Location Cancellation sub-
function) towards the SGSN, is sent.
Change Subscription Type(NAM)

A new command is required to indicate which network the
subscribers are allowed access to: GPRS and / or GSM. The
command HGSNC is used, with the parameter NAM – Network
Access Mode - indicating the network(s).
This default value is defined with an AXE parameter. It can

never be initiated or removed by command, only changed by the
command HGSNC. It has the format:
HGSNC:{IMSI=imsi|MSISDN=msisdn}, NAM=nam, [KEEP];
EN/LZU 123 3977/2 A - 233 -

LZM 112 122
NAM = 0 - the subscriber can access GPRS and Non-GPRS

networks.
NAM = 1 - the subscriber can only access Non-GPRS networks

(i.e. GSM).
NAM = 2 - the subscriber only has GPRS access.
Note: All the mobile terminals mentioned below could be used

irrespective of the NAM value assigned to the mobile
subscriber. Old terminals with only circuit-switched capabilities
are not useful when access subscription was to GPRS network.
Mobile terminals with capabilities for packet-switched and/or

circuit-switched traffic:
Class A terminal, which supports simultaneous circuit-switched

and packet-switched traffic.
Class B terminal, which supports either circuit-switched or

packet-switched traffic (simultaneous network attachment) but
does not support both kinds of traffic simultaneously.
Class C terminal, which is attached either as a packet-switched

or circuit-switched terminal.
Example:
HGSNC : MSISDN=36302000444, NAM=2, KEEP;

NAM for the mobile subscriber with MSISDN 36302000444 is
changed to GPRS. Subscriber data related to the non-GPRS
network is not removed since KEEP is part of the command.
SMS over GPRS

It is now possible to assign short messages to be sent either via
the MSC (non-GPRS network) or the SGSN (GPRS network).
If SUD=TSMO-1, the messages will go via GPRS. If

SUD=TSMO-0, short messages will be sent via the MSC/VLR.
Example:
HGSDC:MSISDN=msisdn, SUD=TSMO-1;
Enables SMS delivery capability via GPRS network!
Subscriber TSMO value can only be changed if the subscriber

has access to both GPRS and non-GPRS networks and SMS
over GPRS functionality is supported.
– 234 – EN/LZU 123 3977/2 A
LZM 112 122
Ericsson GPRS handles SMS traffic!
MSC/VLR MAP
HLR
BTS BSC/
RNC SMS-C
Gs (BSSAP+) Gd Gr (MAP)
(MAP) IP
Feature Network
SGSN GGSN
Backbone
NF 611.1 Network
NF 633.1
NF 636.1
IP
Figure 10- 3 SMS over GPRS
ADMINISTRATION OF GPRS SUBSCRIBERDATA
Administration of subscriber PDP-context data list

The command HGPDI is used to define a subscriber Packet
Data Protocol (PDP) context. This is required for each GPRS
subscriber. The PDP-context is needed to establish routing
information in nodes, involved in the transfer of Packet Data
Units. The PDP-context consists of the following information:
• Quality of Service - The parameter QOS relates to the

Quality of Service and is expressed in five parts: rc-dc-pc-
pt-mt.
• PDP-Address - PDPADD is the Packet Data Protocol (PDP)
address, and is defined using the Internet Protocol (IP)
format version 4:
7 to 15 characters in the form: “xxx.xxx.xxx.xxx”
(where xxx = 0 to 255). E.g. 123.12.1.123
• Access Point Name (access point to external data network) -

APNID is the Access Point Name identifier, as defined in
the previous command HGAPI (0-2047).
EN/LZU 123 3977/2 A - 235 -

LZM 112 122
• Visitor PLMN Address Allowed Flag - VPAA is the Visited

Public Land Mobile Network Address allowed parameter.
Up to five subscribers’ PDP-contexts can be defined per
subscriber.
Example:
HGPDI:MSISDN=12345678,QOS=3-3-2-1-1,APNID=1200,
PDPADD="5.120.212.40",VPAA;
A subscriber PDP context with APN identifier 1200, specific

QOS and PDP address 5.120.212.40 for a mobile subscriber
with MSISDN 12345678 is defined.
The QOS is set with reliability class to unacknowledged GTP

and LLC; acknowledged RLC; protected data, delay class to
delay class 3, precedence class to normal priority, peak
throughput to 1000 octet/s and mean throughput to 100 octet/h.
rc Reliability class
1 Acknowledged General Packet Radio Service Tunneling Protocol (GTP), Logical Link
Control (LLC) and Radio Link Control (RLC); protected data
2 Unacknowledged GTP; acknowledged LLC and RLC; protected data
3 Unacknowledged GTP and LLC; acknowledged RLC; protected data
4 Unacknowledged GTP, LLC and RLC; protected data
5 Unacknowledged GTP, LLC and RLC; unprotected data
dc Delay class mt Mean throughput
1 Delay class 1 1 100 octet/h

2 Normal priority 2 200 octet/h
4 Delay class 4 (best effort) 4 1000 octet/h
5 2000 octet/h
pc Precedence class 6 5000 octet/h
1 High priority 7 10000 octet/h
3 Low priority 9 50000 octet/h
10 100000 octet/h
pt Peak throughput 11 200000 octet/h
1 Up to 1000 octet/s 12 500000 octet/h
8 Up to 128000 octet/s 31 Best effort
Table 10- 1 Quality of Service for PDP-context
– 236 – EN/LZU 123 3977/2 A

LZM 112 122
Ending of subscriber PDP-Contexts (HGPDE)

The command HGPDE allows the operator to end one, several
or all PDP-Contexts defined for a mobile subscriber on an
IMSI/MSISDN basis.
Printout of subscriber PDP-Contexts (HGPDP)

The command HGPDP allows the operator to print the PDP-
Context list of a mobile subscriber or an IMSI/MSISDN series.
Administration of other GPRS subscriber data
Modification of GPRS subscriber data (HGSDC)

Modification of GPRS Subscriber Data can be initiated by the
existing command HGSDC.
In order to change subscriber data, MSISDN must be specified

in the command. The GPRS subscriber data to be modified are
the permanent subscriber data: operator determined barring
applying to GPRS, subscription or not subscription to Basic
Services TS21 and TS22, and TSMO.
Massive Change of subscriber data (HGMCI)

Permanent subscriber data are changed for a large number of
connected subscribers.
All the subscribers in the HLR, or the subscribers with an

MSISDN or IMSI within an MSISDN or IMSI series, that have
a certain value for some subscriber data can be changed
specifying new subscriber data to change.
The command HGMCI was modified to allow updating the

SGSNs after making the subscriber changes.
HGMCI:MSISDNS=341510, NEWSUD=OBO-4;
Operator determined Barring of All Outgoing Calls when

Roaming Outside HPLMN Country is provided and activated
for the connected subscribers within the MSIDN series 341510.
EN/LZU 123 3977/2 A - 237 -

LZM 112 122
Printing of GPRS subscriber Data (HGSDP)

Printout of subscriber data is initiated by command. Subscriber
data for one or more MSISDNs or IMSISs can be printed.
Subscriber data TSMO is only printed if the subscriber has

access to both GPRS and non-GPRS networks and SMS over
GPRS functionality is supported.
As the NAM can be considered as a basic datum of the mobile

subscriber, it will be possible to print it using the existing
command HGSDP.
HGSDP can be used to print the Mobile GPRS Subscription

Data. It lists the subscriber location data. This printout is
received when parameter ALL or LOC is specified in the
command.
The existing printout HLR SUBSCRIBER DATA was modified

to contain information about the NAM of the mobile subscriber.
The NAM information will only be printed if the GPRS
functionality is supported.
The printouts PERMANENT SUBSCRIBER DATA and

SUPPLEMENTARY SERVICE DATA are not modified.
Modification of Profile Data (HGSPC)

In order to change data in the profile, the profile must be
specified in the command.
Printing of Profile Data (HGSPP)

Printout of profile data for one, several or all profiles is initiated
by the existing HGSPP command.
Resetting of the mobile GPRS subscriber location (HGSLR)

It is initiated by the existing HGSLR command. The MSISDN
or IMSI must be specified in the command. If the location in
this network is known, the CANCEL LOCATION message is
sent towards the SGSN.
HGSLR:IMSI=24450100000004;
The location of the mobile subscriber whose IMSI is

24450100000004 is set to unknown.
– 238 – EN/LZU 123 3977/2 A

LZM 112 122
Printing of Conditional Subscriber list (HGLIP)

Printout of the conditional subscriber list is initiated by the
existing HGLIP command.
A list of all the subscribers in HLR or a list of the subscribers

with a MSISDN or IMSI series that have a certain value for
some subscriber data is printed.
File Output of GPRS subscriber data
Initiate File Output of Subscriber data (HGPFI)

It is possible to output the existing file printout HPSDFOAFILE
with the permanent subscriber data that are applicable to a
GPRS subscriber (for example, NAM, TSMO, PDP-Context
list, Teleservice Short Message MT/PP, Teleservice Short
Message MO/PP, Operator Determined Barrings, Operator
Specific Barrings).
HGPFI:MSISDNS=34151, TIME=0200;
Permanent subscriber data for connected subscribers whose

main MSISDN number starts with ‘34151’ will be output to file
HPSDFOAFILE. File output will start at 2 a.m.
End File Output of Subscriber data (HGPFE)

The command HGPFE allows the operator to end File output of
permanent subscriber data for connected subscribers, either
ongoing or scheduled.
EN/LZU 123 3977/2 A - 239 -

LZM 112 122
ADMINISTRATION OF GPRS HLR DATA
Administration of APN data
Initiate APN data (HGAPI)

The APN names should be defined in the Home Location
Register by a new command HGAPI. The command is used to
define the Access Point Name (APN) and the Access Point
Name Identifier (APNID). An example of an Access Point
Name is the subscriber’s Internet Service Provider. In our
example the APN is “GPRS.ERICSSON.SE” and the identifier
is 25. The identifier is a numerical value, assigned to this APN.
Example:
HGAPI : APN1=”GPRS.ERICSSON.SE”, APNID=25;
End APN data (HGAPE)

Ending of APN data is also initiated by a new command. In
order to end APN data in the HLR, the APN or the APN
identifier must be specified in the command.
HGAPE
Print APN data (HGAPP)

Printout of APN data is initiated by command.
HGAPP
APN data for one or all defined APNs can be printed.
HGAPP:APNID=ALL
All the APNs defined in the HLR and their corresponding APN
identifiers are printed.
HGAPP:APNID=5,MSUSERS;
The MSISDN and the IMSI of all mobile subscribers using the
APN corresponding to the APNID 5 in any of their defined PDP
contexts and the corresponding PDP context identifiers are
printed.
– 240 – EN/LZU 123 3977/2 A

LZM 112 122
HGAPP:MSUSERS;
The MSISDN and the IMSI of all the mobile subscribers having
any PDP context defined that allows the mobile subscriber to
request a non-subscribed APN and the corresponding PDP
context identifiers are printed.
Administration of roaming area characteristics (HGRCI/E/P)

The existing commands to administer the roaming area
characteristics HGRCI (Initiate Roaming Area Characteristic to
a roaming area), HGRCE (End Roaming Area Characteristic to
a roaming area) and HGRCP (Print defined Roaming Area
Characteristic of roaming areas) are used for GPRS.
In the example below all VLRs and SGSNs with an

International Global Title address starting 30487123 will have
roaming restricted.
HGRCI:AREA=4-30487123,CHAR=ROAMREST;
EN/LZU 123 3977/2 A - 241 -

LZM 112 122
INTERWORKING OF GPRS HLR

These procedures are covered in chapter 1.
Mobility Services
Location Management Services
MAP_CANCEL_LOCATION
MAP_PURGE_MS SERVICE
MAP_UPDATE_GPRS_LOCATION SERVICE
Authentication Management Services
MAP_SEND_PARAMETERS
MAP_SEND_AUTHENTICATION_INFO SERVICE
Subscriber Management Services
MAP_INSERT_SUBSCRIBER_DATA SERVICE
MAP_DELETE_SUBSCRIBER_DATA SERVICE
Fault Recovery services
MAP_RESET
Short Message Service Management Services

MAP_SEND_ROUTING_INFO_FOR_SM
MAP_REPORT_SM_DELIVERY_STATUS SERVICE
MAP_READY_FOR_SM SERVICE
MAP_ALERT_SERVICE_CENTRE SERVICE
MAP_INFORM_SERVICE_CENTRE SERVICE
MAP_SET_MESSAGE_WAITING_DATA
– 242 – EN/LZU 123 3977/2 A

LZM 112 122
NEW FUNCTION BLOCKS

• HGLUAP handles the GPRS LU request message received
from SGSN.
• HGPRSA handles the administration of PDP Context Data
for subscribers in HLR.
• HGPRSD stores GPRS location data and PDP Context list
for each subscriber having access to GPRS network.
• HGSDH fetches from the database the subscriber data
requested by the user function blocks (that is, HISDAP3,
HDSDAP3, HGLUAP), prepares and inserts them in a
TCAP dynamic buffer. This function block is initiated when
a user function block needs to send some subscriber data to
SGSN.
• HGAPNA handles the administration of Access Point
Names in HLR. It enables the mobile operator to initiate a
new Access Point Name, end a defined Access Point Name
and print Access Point Name data in HLR.
• HGAPND Home Access Point Name Data, stores the
complete name of all the Access Point Names defined in the
HLR, as well as the number of Packet Data Protocol-
Contexts using a certain Access Point Name.
• HRFSAP3 handles the received message 'Ready For SM'
MAP v3 from MSC/VLR or SGSN.
• HMSPAP3 handles the reception of MS Purge message
version 3 operation from MSC/VLR or SGSN.
APT SAES FOR GPRS

• HGLUAP
SAE 260 Number of SGSN’s
SAE 500 Number of tasks individuals
• HGPRSD
SAE 261 Number of Mobile Subscribers
SAE 600 Subscriber location data within GPRS network.
SAE 601 PDP context list defined for a GPRS subscriber.
• HGSDH
EN/LZU 123 3977/2 A - 243 -

LZM 112 122
SAE 500 Number of tasks individuals (MAP V3 operations

for SGSN updating (Insert/Delete Subscriber Data MAP version
3).
SAE 604 Buffers used for packing the messages.
• HRFSAP3
• HMSPAP3
SAE 260
– 244 – EN/LZU 123 3977/2 A

LZM 112 122
AXE EXCHANGE PARAMETERS

There are various parameters that need to be assigned to support
the GPRS Feature.
• To determine if the GPRS functionality is supported in the

HLR
DBTSC:TAB=AXEPARS,
SETNAME=GSMHRSF,NAME=HLRNF633, VALUE=1;
VALUE 0 = not supported

1 = supported
• To control the maximum number of GPRS subscription

allowed in the HLR
DBTSC:TAB=AXEPARS,
SETNAME=GSMHRSS,NAME=CAPGPRSINHLR,
VALUE=200;
The value of this AXE parameter is given in units of

kSubscribers (x1000).
• To control the default value set to the subscriber NAM at

subscription initiation
DBTSC:TAB=AXEPARS,
SETNAME=GSMHRSC,NAME=NAMBYDEFAULT,
VALUE=1;
• To determine if the MS over GPRS functionality is

supported
DBTSC:TAB=AXEPARS,
SETNAME=GSMHRSF,NAME=HLRNF636, VALUE=1;
EN/LZU 123 3977/2 A - 245 -

LZM 112 122
Intentionally Blank
– 246 – EN/LZU 123 3977/2 A

LZM 112 122

PS Datacom in HLR: Objectives

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PS Datacom in HLR: Objectives

Uploaded by

Copyright:

Available Formats

PS Datacom in HLR

This chapter is designed to provide the student with the

• Explain how the HLR is reused for GPRS

EN/LZU 123 3977/2 A

GPRS SUPPORT IN HLR ..................................................................223

GPRS DATA ADMINISTRATION ......................................................233

INTERWORKING OF GPRS HLR .....................................................242

AXE EXCHANGE PARAMETERS.....................................................245

EN/LZU 123 3977/2 A –i–

– ii – EN/LZU 123 3977/2 A

GPRS SUPPORT IN HLR

The Home Location Register (HLR) is the database that holds

Ericsson GPRS Network Architecture

Figure 10- 1 Ericsson GPRS Network Architecture.

In addition, the HLR includes information about the location of

EN/LZU 123 3977/2 A - 223 -

The HLR stores the subscription information regarding mobile-

No new hardware is required in the HLR. The CP load due to a

GPRS SUBSCRIPTION DATA

The Network Access Mode of the subscriber is added to the

In that case, the HLR contains GPRS subscription data and

If the subscriber has access to packet data transmission only, he

HLR stores information for authentication and ciphering from

An exchange property changeable by command determines in

The authentication data for those new subscribers will be

– 224 – EN/LZU 123 3977/2 A

Network Access Mode (NAM)

The Network Access Mode of a subscriber defines if the

All subscribers always have a NAM, with a default value set at

If the optionally ‘GPRS functionality in HLR’ is active this

The Subscriber Initiation to GPRS is performed when the

GPRS SUBSCRIBER DATA

The term GPRS Subscriber Data is used to designate the GPRS

- NAM, PDP-context list {PDP type (IPV4), PDP address

- Permanent subscriber data: Data that can only be changed by

- GPRS Location Data

EN/LZU 123 3977/2 A - 225 -

Home Location Register

GPRS Subscriber Data:

Figure 10- 2 GPRS Subscriber Data in HLR

The HLR updates the SGSN with that information upon a

GPRS Service Subscriptions

Packet Data Protocol (PDP) Context

The elements of a PDP-context subscription Record (referred

• Access Point Name

– 226 – EN/LZU 123 3977/2 A

• Visitor PLMN Address Allowed Flag

Label or full-qualified domain name according to Domain Name

- Dynamic PDP Addressing

The Packet data Protocol Address associated with the user's

- Static PDP Addressing

The Packet Data Protocol Address associated with the user's

VPLMN Address Allowed (VPLMNA)

Quality of Service (QoS)

Subscribers may have the choice of paying a premium for a high

EN/LZU 123 3977/2 A - 227 -

The Quality of Service consists of multiple data transfer

Data reliability is defined in terms of the residual error rates for

• Probability of data loss

The GSNs support the reliability Classes 2,3,4 and 5.

Technical Specification GSM 02.60 defines four delay classes

Indicates the relative importance of maintaining the service

User data throughput is specified in terms of a set of throughput