Subscriber Data Tables, and

Datafill

Lesson 1

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004
Objectives

Using
Usingsite-specific
site-specificinformation
informationand
andappropriate
appropriate documentation,
documentation,the
the
student
studentwill
willadd
addsubscribers
subscribersto tothe
theHLR
HLR database
databaseas asfollows:
follows:
•• Register
Registersubscribers
subscriberswith
withbasic
basicservices.
services.
•• Activate
Activatesubscribers.
subscribers.
•• Deactivate
Deactivatesubscribers.
subscribers.
•• Delete
Deletesubscriber
subscriberdata.
data.
•• Replace
ReplaceaaSubscriber’s
Subscriber’sSIM
SIMcard.
card.

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-2
Outline

The datafilling subscriber data information is divided into the following

sections:
• Datafilling subscriber data
• Provisioning and registering supplementary services
• Call Forwarding
• Call Barring
• Datafill Restrictions on Supplementary Services
• Deleting subscriber datafill
• Deregistering and Deactivating supplementary services

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-3
Subscriber Data Datafill Order
Step 1: Add entry for each
subscriber GHLRALG

Automatically GHLRDATA
Step 2: Add entry for each basic Creates Entry In (default deactivated)
service in subscription GHLRAUTH
profile

Step 3: Add entry for each

supplementary service GHLRBSVC
in subscription profile

Step 4: Change IMSI status in

table GHLRDATA to GHLRSSOP
activate (A) or
new/naughty (N) service

Step 5: Check partition information GHLRPRTN

in Table GHLRPRTN

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-4
UMTS Algorithm Framework

Authentication
Subscriber Specific vectors
Inputs
Authentication Algorithm Encryption engine
RAND, XRES, CK, IK, AUTN
SQN, AMF, RAND, K, OPc

Datafilling flavor information is

modified to use standard table
control via table GHLRALG.

As the new table GHLRALG

contains sensitive information that
Flavor information must not be changed
unnecessarily, it is accessible only
to authorized users of an access
C1, C2, C3…C5 level defined in table CUSTPROT.
Algorithm constants
R1, R2, R3…R5

To datafill the authentication algorithm:

1. Datafill GHLRALG table.
2. Use an ALGSEL field in table GHLRAUTH.

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-5
Table GHLRALG: Datafill Example
The ‘AuC Robustness and Algorithm Configurability’ feature implements the new
table: HLRALG to configure the algorithm parameters.
Table GHLRALG contains the flavor information for each subscriber
authentication algorithm.
>table ghlralg
>table ghlralg
TABLE:
TABLE: GHLRALG
GHLRALG
>TOP
>TOP
ALGSEL FLAVOUR
ALGSEL FLAVOUR
--------------
--------------
11 GSM_XOR
GSM_XOR GSM_XOR
GSM_XOR
2 GSM_MOU GSM_MOU
2 GSM_MOU GSM_MOU
33 GSM_FLEET
GSM_FLEET GSM_FLEET
GSM_FLEET
44 GSM_CAVE38
GSM_CAVE38 GSM_CAVE38
GSM_CAVE38
5 GSM_IDEA GSM_IDEA
5 GSM_IDEA GSM_IDEA
6 GSM_IDEA54 GSM_IDEA54
6 GSM_IDEA54 GSM_IDEA54
77 GSM_COMP128_2
GSM_COMP128_2 GSM_COMP128_2
GSM_COMP128_2
88 GSM_CAVE38_2
GSM_CAVE38_2 GSM_CAVE38_2
GSM_CAVE38_2
100 UMTS_XOR UMTS_XOR 0 0 NO
100 UMTS_XOR UMTS_XOR 0 0 NO
101
101 UMTS_MILENAGE
UMTS_MILENAGE UMTS_MILENAGE
UMTS_MILENAGE 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 22 00 00 00 00 00 00 00 00 00 00
0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 64 0 32 64 96
0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 64 0 32 64 96
102 UMTS_MILENAGE UMTS_MILENAGE 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
102 UMTS_MILENAGE UMTS_MILENAGE 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
00 00 00 00 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 22 00 00 00 00 00 00 00 00 00 00
0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 64 0 32 64 96
0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 64 0 32 64 96
103 UMTS_MILENAGE UMTS_MILENAGE 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
103 UMTS_MILENAGE UMTS_MILENAGE 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
00 00 00 00 00 00 00 00 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 22 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 88 64
64 00 32
32 6464 96
96
BOTTOM
BOTTOM
411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-6
Table GHLRAUTH: Datafill Example
Table GHLRAUTH:
• Contains subscriber authentication data that includes information to verify subscriber identity
and prevent unauthorized subscriber access to the network.
For each subscriber there is one tuple in this table.
Upon datafilling table GHLRAUTH, an entry is automatically made in table GHLRDATA. The
automatic entry is non-restricted general subscriber data.
TABLE: GHLRAUTH
TOP
MCC MNC MSIN KI CS MKVER ALGSEL ALGPARM
---------------------------------------
208 11 0000000000 0000 0000 0000 0000 0000 0000 0000 0000 NULL 0 100 NIL
208 11 0000000001 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF NULL 0 102 OPC
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
208 11 0000000002 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF NULL 0 1 NIL
208 11 0000000003 0000 0000 0000 0000 0000 0000 0000 0001 NULL 0 1 NIL
208 11 0000000005 0000 0000 0000 0000 0000 0000 0000 0001 NULL 0 1 NIL
208 11 0000000006 0000 0000 0000 0000 0000 0000 0000 0001 NULL 0 1 NIL
208 11 0000000010 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF NULL 0 100 NIL
208 11 0000000021 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF NULL 0 100 NIL
208 11 0000000022 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF NULL 0 101 OPC
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-7
Table GHLRBSVC: Datafill Example
Table GHLRBSVC:
• Contains the basic services and associated data for a subscriber.
• Allows basic services to be added against an IMSI along with an MSISDN.

MCC
MCC MNC
MNC MSIN
MSIN BSVC
BSVC CC
CC NDC
NDC SN
SN BCI
BCI
--------------------------------------------------
--------------------------------------------------
310
310 44
44 628770770
628770770 TPHNY
TPHNY 11
11 44
44 628770770
628770770 NIL
NIL
310 46 628776125 TPHNY
310 46 628776125 TPHNY 15
15 46 628776125 NIL
46 628776125 NIL
310 46 628776125 SMMT
310 46 628776125 SMMT 15
15 46
46 628776125
628776125 NIL
NIL
310
310 44
44 628782555
628782555 TPHNY
TPHNY 11
11 44
44 628782555
628782555 NIL
NIL
310 44 628846443 CDA
310 44 628846443 CDA 11
11 44
44 628846443 BCI 33
628846443 BCI
325
325 46
46 628795001
628795001 TPHNY
TPHNY 15
15 46
46 628795001
628795001 NIL
NIL
325 46 628795001 FAX
325 46 628795001 FAX 15
15 46
46 628850016 BCI 44
628850016 BCI
331
331 46
46 628795000
628795000 TPHNY
TPHNY 11
11 44
44 628795000
628795000 NIL
NIL
331
331 46
46 628795000
628795000 SMMO
SMMO 11
11 44
44 628795000
628795000 NIL
NIL

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-8
Table GHLRBCA: Datafill Example
Table GHLRBCA stores BC information that may be used when none is available.
• For mobile-terminated data calls to be completed, it is helpful to have details about
network resources required for the data call to be transferred properly.
However, mobile-terminated data calls from the PSTN do not include BC
information.

CI:
CI:
>table
>table ghlrbca
ghlrbca
TABLE: GHLRBCA
TABLE: GHLRBCA
>list
>list 55
BCAKEY
BCAKEY BSVC
BSVC ITC
ITC RCR
RCR STR
STR SAP
SAP RA
RA SYNC_M
SYNC_M UR
UR DATA
DATA STOP
STOP PARITY
PARITY IR
IR MODEM
MODEM CE
CE
ORD
ORD
-----------------------------------------------------------------------
-----------------------------------------------------------------------
11 CDAGBS
CDAGBS 3KAudio
3KAudio FRFR UU I440
I440 NONE
NONE AA 9600
9600 77 11 EVENEVEN 16K
16K V32V32 TT $$
22 CDSGBS
CDSGBS UDI
UDI FRFR UU X21X21 V110
V110 SS 1200
1200 $$ $$ $$ 8K 8K NONE
NONE TT $$
33 CDAGBS
CDAGBS 3KAudio
3KAudio FRFR UU I440
I440 NONE
NONE AA 4800
4800 77 11 EVENEVEN 8K
8K V32V32 TT $$
44 CDAGBS
CDAGBS UDI
UDI FRFR UU I440
I440 V110
V110 AA 14400
14400 $$ $$ $$ 16K 16K NONE
NONE TT $$
55 CDSGBS
CDSGBS 3KAudio
3KAudio FRFR UU I440
I440 NONE
NONE SS 4800
4800 $$ $$ $$ 8K 8K V32
V32 TT $$

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-9
Table GHLRDATA
Table GHLRDATA contains general subscriber data.
• There is a one-to-one relationship between IMSIs and tuples in table
GHLRDATA.

• Data specific to Basic Services and the provisioning of Supplementary

Services is maintained in other tables.

To add a subscriber in table GHLRDATA:

1. Enter all subscribers in table GHLRAUTH.

2. A tuple is automatically added into table GHLRDATA.

The automatic default entry into table GHLRDATA is the IMSI in a

“deactivated” status.

To modify or delete subscriber data from table GHLRDATA:

1. Change the IMSI status of a subscriber to deactivated.
2. Delete the tuple.
The corresponding tuple in table GHLRAUTH is automatically deleted.
411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-10
Table GHLRDATA: Datafill Example

TABLE:
TABLE: GHLRDATA
GHLRDATA
MCC
MCC MNC
MNC MSIN
MSIN ISTATUS
ISTATUS ROAMING
ROAMING CATEGORY
CATEGORY BICCTRL
BICCTRL BOCCTRL
BOCCTRL PASSWORD
PASSWORD ODBOG
ODBOG ODBIC
ODBIC
ODBMISC ODBECT INORIG INTERM PRTN SOAPROV ASTATUS
ODBMISC ODBECT INORIG INTERM PRTN SOAPROV ASTATUS NAM LMU NAM LMU
--------------------------------------------------------------------------
--------------------------------------------------------------------------
505
505 02
02 3501205000
3501205000 AA UNKW
UNKW ORDINARY
ORDINARY USER
USER USER
USER 1234
1234 NONE
NONE NONE
NONE $$ $$ NONE
NONE NONE
NONE 00 NN
ACTING
ACTING MSC_ONLY
MSC_ONLY NN
505
505 02
02 3501205001
3501205001 AA UNKW
UNKW ORDINARY
ORDINARY USER
USER USER
USER 1234
1234 NONE
NONE NONE
NONE $$ $$ NONE
NONE NONE
NONE 00 NN
ACTING
ACTING MSC_ONLY
MSC_ONLY NN
505
505 02
02 3501205002
3501205002 AA UNKW
UNKW ORDINARY
ORDINARY USER
USER USER
USER 1234
1234 NONE
NONE NONE
NONE $$ $$ NONE
NONE NONE
NONE 00 NN
ACTING
ACTING MSC_ONLY
MSC_ONLY NN
505
505 02
02 3501205003
3501205003 AA UNKW
UNKW ORDINARY
ORDINARY USER
USER USER
USER 1234
1234 NONE
NONE NONE
NONE $$ $$ NONE
NONE NONE
NONE 00 NN
ACTING
ACTING MSC_ONLY
MSC_ONLY NN
505
505 02
02 3501205004
3501205004 AA UNKW
UNKW ORDINARY
ORDINARY USER
USER USER
USER 1234
1234 NONE
NONE NONE
NONE $$ $$ NONE
NONE NONE
NONE 00 NN
ACTING
ACTING MSC_ONLY
MSC_ONLY NN

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-11
Table GHLRPRTN
Table GHLRPRTN allows:
• The DMS-HLR subscriber datafill to be partitioned into between 1 and 255
partitions.
Each partition can be assigned to a status value of: ACTIVE or
STANDBY.
By default, all subscribers datafilled in the DMS-HLR are allocated a
partition value of 0 in table GHLRDATA. Table GHLRPRTN, on IPL,
defines partition 0 to be ACTIVE.

Fields
• PARTITION_NUMBER (this field is the key)
• PARTITION_NAME (this field assigns an operator defined ‘name’ to the
partition)
• PARTITION_STATUS (this field indicates whether a partition is ACTIVE or
AWAY)

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-12
Table GHLRPRTN: Datafill Example

Table
Table GHLRPRTN
GHLRPRTN
PNUMBER
PNUMBER PNAME
PNAME PSTATUS
PSTATUS
00 DEFAULT_PARTITION_(read_only)
DEFAULT_PARTITION_(read_only) $$
22 PRTN_B
PRTN_B (AWAY)$
(AWAY)$
33 PRTN_C
PRTN_C (HOME)$
(HOME)$

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-13
Datafill Restrictions to SS
Several datafill restrictions apply to registering and provisioning supplementary services
against a single MSISDN:
• certain features override or cancel an existing feature. Thus, not all the supplementary
services can be registered or provisioned against a single MSISDN.
For example, registration and activation of CFU override all other supplementary services
assigned to a particular MSISDN during a mobile-terminated call. Furthermore, if a
subscriber wants to add a service such as BAIC while maintaining an active CFU feature,
the request for BAIC is rejected.
In a mobile-originated call, if a subscriber wants to activate the BAOC but one of the
following items has been actived:
• CFU
• CFB
• CFNRY
• CFNRC
The network rejects the subscriber request until these services have been
deactivated.
411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-14
Table GHLRSIMR and Related SIM Replacement Tables
Table GHLRAUTH Table OFCSTD
mcc mnc msin Ki Cs ghlr_imsi_mnc ghlr_imsi_mcc
Already-existing

New entry to GHLRAUTH creates new entry in GHLRDATA

Table GHLRDATA
mcc mnc msin
Isatus

Table GHLRSIMR
newmcc newmnc newmsin oldmcc oldmnc oldmsin
option
GHLRSIMR manually
datafilled with already-existing
and new mnc/msin and mcc/msin  When and how the
After the entry is entered into GHLRSIMR the
«newmcc/newmsin » and «newmnc/newmsin»
istatus in GHLRDATA changes to « R » may replace
the «oldmcc/oldmsin» and «oldmnc/oldmsin».
After condition in « option » are met newmcc/newmsn and newmnc/newmsin and
replaces oldmcc/oldmsin and oldmnc/oldmsin. Table GHLRDATA field istatus is automatically changed:

Table GHLRDATA
mcc mnc msin
Isatus
(old) Entry deleted
A (activated)
(new) Istatus changed to whatever the istatus
A (replacement)
of the old IMSI was
411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-15
Table GHLRSIMR

TOP
NEWMCC NEWMNC NEWMSIN OLDMCC OLDMNC OLDMSIN OPTION
230234567890 23021111111FIXED 2001 09 07 14
230234567891 230987654321USER 2001 10 11 13 2010 02 05
13
230234567892 23024444444FIXED 2010 12 25 16

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-16
Subscriber Data Deletion Order
Step 1:
GHLRDATA Change IMSI status in
table GHLRDATA to
D (deactivated)

Step 2:
GHLRSSOP Delete all supplementary
services attached to the
subscriber’s IMSI

Step 3:
GHLRBSVC Delete all basic services
attached to the subscriber’s
IMSI

Step 4:
GHLRDATA Delete subscriber's IMSI
from table GHLRDATA

GHLRAUTH

Automatically Deletes Entry In

411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL January, 2004 1-17
 411-UM972-001.1703
NORTEL NETWORKS CONFIDENTIAL 1-18
NORTEL NETWORKS CONFIDENTIAL January, 2004