HLR Configuration Volume 3 of 3

Kapsch CarrierCom AG
PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 1 of 228

State released | Version 0.16 | 05.09.2014 CONFIDENTIAL
PE/HLR/APP/027819
HLR
HLR Configuration Volume 3 of 3
Release: HLR22
Replaces: NN10300-441v3

HLR
Release: HLR22
Document number: PE/HLR/APP/027819
Document release date: September 5, 2014 10:04 AM
Copyright © 2014 Kapsch. All Rights Reserved.
The information contained in this document is the property of Kapsch CarrierCom (in the following referred to as
“Kapsch”). Except as specifically authorized in writing by Kapsch, the holder of this document shall keep the information
contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties
and use same for evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Kapsch as to the content or accuracy of the information contained herein,
including but not limited to the suitability and performance of the product or its intended application.
Kapsch and the Kapsch logo are trademarks of Kapsch and/ or its licensors. All other trademarks are the property of
their owners.

Table of contents
1 Introduction ....................................................................................................................................... 8
1.1 Navigation ........................................................................................................................................... 8
2 Subscriber Profile ............................................................................................................................. 9

2.1 Navigation ........................................................................................................................................... 9
2.2 Subscriber profile view ........................................................................................................................ 9
2.3 Profile graphical representation ........................................................................................................11
3 Data model and validations ............................................................................................................22

3.1 Navigation .........................................................................................................................................22
3.2 Profile components............................................................................................................................22
3.3 Proprietary services...........................................................................................................................26
3.4 Datatypes ..........................................................................................................................................26
3.5 Data vectors ......................................................................................................................................27
3.6 Validations introduction .....................................................................................................................27
3.7 Profile creation ..................................................................................................................................28
3.8 Profile deletion ...................................................................................................................................28
3.9 Transactional validations ...................................................................................................................28
3.10 Example component..........................................................................................................................28
3.11 HLR-wide validations.........................................................................................................................29
4 Authentication data .........................................................................................................................31

4.1 Navigation .........................................................................................................................................31
4.2 Datafill ...............................................................................................................................................31
4.3 Interactions ........................................................................................................................................32
4.4 Additional information ........................................................................................................................32
5 Profile control data ..........................................................................................................................33

5.1 Navigation .........................................................................................................................................33
5.2 Barring Control ..................................................................................................................................33
5.3 Category ............................................................................................................................................34
5.4 IMSI Status ........................................................................................................................................36
5.5 Location Measurement Unit ..............................................................................................................37
5.6 Network Access Mode.......................................................................................................................37
5.7 Password ...........................................................................................................................................38
5.8 Roaming Entitlement .........................................................................................................................38
5.9 Suppression of Announcements provisioning ...................................................................................39
6 Basic services .................................................................................................................................40

6.1 Navigation .........................................................................................................................................40
6.2 HLR supported basic services ..........................................................................................................40
6.3 Notes on basic services ....................................................................................................................42
6.4 Alternate Speech/Circuit Duplex Asynchronous data .......................................................................43
6.5 Alternate Speech/Circuit Duplex Synchronous data .........................................................................44
6.6 Alternate Speech/Fax Group 3 ..........................................................................................................45
6.7 Auxiliary Telephony ...........................................................................................................................47
6.8 Circuit Duplex Asynchronous data ....................................................................................................48

6.9 Circuit Duplex Asynchronous data 300 .............................................................................................48

6.10 Circuit Duplex Asynchronous data 1200 ...........................................................................................49
6.15 Circuit Duplex Asynchronous Data General Bearer Service.............................................................55
6.16 Circuit Duplex Synchronous ..............................................................................................................56
6.17 Circuit Duplex Synchronous data 1200 .............................................................................................56
6.21 Circuit Duplex Synchronous data General Bearer Service ...............................................................61
6.22 Facsimile Group 3 .............................................................................................................................62
6.23 Short Message Mobile Originating ....................................................................................................63
6.24 Short Message Mobile Terminating ..................................................................................................64
6.25 Speech followed by CDA data ..........................................................................................................65
6.26 Speech followed by CDS data ..........................................................................................................66
6.27 Telephony ..........................................................................................................................................67
6.28 Voice Broadcast Service ...................................................................................................................68
6.29 Voice Group Call Service ..................................................................................................................69
7 Supplementary services .................................................................................................................71

7.1 Navigation .........................................................................................................................................71
7.2 Supplementary services groups ........................................................................................................72
7.3 Accounting Codes .............................................................................................................................74
7.4 Anonymous Call Rejection ................................................................................................................74
7.5 Advice of Charge Charging ...............................................................................................................75
7.6 Advice of Charge Information ............................................................................................................75
7.7 Barring of All Incoming Calls .............................................................................................................75
7.8 Barring of All Outgoing Calls .............................................................................................................77
7.9 Barring of Incoming Calls when Roaming outside HPLMN country ..................................................78
7.10 Barring of Outgoing International Calls .............................................................................................79
7.11 Barring of Outgoing International Calls except to HPLMN Country ..................................................81
7.12 Call Forward when Busy ...................................................................................................................82
7.13 Call Forward when Not Reachable ...................................................................................................87
7.14 Call Forward when No Reply ............................................................................................................92
7.15 Call Forward Unconditionally ............................................................................................................98
7.16 Calling Line ID Presentation ............................................................................................................103
7.17 Calling Line ID Restriction ...............................................................................................................103
7.18 Calling Name Delivery .....................................................................................................................104
7.19 Connected Line ID Presentation .....................................................................................................104
7.20 Connected Line ID Restriction ........................................................................................................105
7.21 Class of Service ..............................................................................................................................105
7.22 Closed User Groups ........................................................................................................................107
7.23 Closed User Groups Subscription ...................................................................................................107
7.24 Closed User Groups Feature ..........................................................................................................108
7.25 Customized Ring Back Tone ...........................................................................................................110
7.26 Call Waiting .....................................................................................................................................111
7.27 Explicit Call Transfer .......................................................................................................................112

7.28 Enhanced Multi Level Precedence and Pre-emption ......................................................................112

7.29 Extension Services ..........................................................................................................................113
7.30 Follow Me ........................................................................................................................................118
7.31 Call Hold ..........................................................................................................................................119
7.32 Hot Billing ........................................................................................................................................119
7.33 Local Calls Only ..............................................................................................................................120
7.34 Malicious Call Trace ........................................................................................................................120
7.35 Multiparty .........................................................................................................................................121
7.36 User to User Signaling stage 1 .......................................................................................................121
7.37 Wireless Priority Service .................................................................................................................121
8 Operator-determined barrings .....................................................................................................122

8.1 Navigation .......................................................................................................................................122
8.2 Operator-determined barrings categories .......................................................................................122
8.3 Datafill .............................................................................................................................................123
8.4 Interactions ......................................................................................................................................123
9 CAMEL services ............................................................................................................................124

9.1 Navigation .......................................................................................................................................124
9.2 CAMEL subscription information services ......................................................................................124
9.3 Dialed CSI .......................................................................................................................................125
9.4 General Packet Radio Service CSI .................................................................................................126
9.5 Mobility Management CSI ...............................................................................................................128
9.6 Originating CSI ................................................................................................................................129
9.7 Short Message Service CSI ............................................................................................................134
9.8 Supplementary Service CSI ............................................................................................................135
9.9 Terminating CSI ..............................................................................................................................136
9.10 Translations Information Flag CSI ...................................................................................................139
9.11 Unstructured Supplementary Service Data CSI ..............................................................................139
10 Location Services ..........................................................................................................................141

10.1 Navigation .......................................................................................................................................141
10.2 LCS classes ....................................................................................................................................141
10.3 LCS Autonomous Self Location ......................................................................................................141
10.4 LCS Basic Self Location ..................................................................................................................142
10.5 LCS Call Related .............................................................................................................................142
10.6 LCS Call Unrelated..........................................................................................................................144
10.7 LCS GMLCs ....................................................................................................................................145
10.8 LCS PLMN Operator .......................................................................................................................145
10.9 Interactions ......................................................................................................................................146
10.10 LCS Transfer to Third Party ............................................................................................................146
10.11 LCS Universal .................................................................................................................................147
11 GPRS PDP context IDs .................................................................................................................148

11.1 Navigation .......................................................................................................................................148
11.2 Datafill .............................................................................................................................................148
12 Other services ...............................................................................................................................153

12.1 Navigation .......................................................................................................................................153

12.2 Calling Line Identification Replacement Number ............................................................................153

12.3 Equal Access ...................................................................................................................................154
12.4 Proprietary Intelligent Network service............................................................................................154
13 Other components ........................................................................................................................156

13.1 Navigation .......................................................................................................................................156
13.2 Home Subscriber Trace ..................................................................................................................156
13.3 SIM Replacement ............................................................................................................................157
14 Suppression states .......................................................................................................................159

14.1 Navigation .......................................................................................................................................160
14.2 BICRoam suppression state determination.....................................................................................160
14.3 CFB suppression state determination .............................................................................................160
14.4 CFNRy suppression state determination ........................................................................................161
14.5 CFU suppression state determination .............................................................................................161
14.6 EXT suppression state determination .............................................................................................161
14.7 ODB BICRoam suppression state determination ............................................................................162
14.8 ODB BAOCRoam suppression state determination .......................................................................162
14.9 ODB HPLMN-specific categories suppression state determination ................................................163
15 Database Implementation .............................................................................................................164

15.1 Navigation .......................................................................................................................................164
15.2 Datatypes in Database ....................................................................................................................165
15.3 Section structure .............................................................................................................................167
15.4 Schema tables listing and diagram .................................................................................................168
15.5 Guide to table sections ....................................................................................................................172
15.6 Table SUB_AUTH ...........................................................................................................................173
15.7 Table SUB_GENERAL ....................................................................................................................174
15.8 Table SUB_ODBS ...........................................................................................................................175
15.9 Table SUB_BASIC_SERVICES ......................................................................................................176
15.10 Table SUB_BAIC.............................................................................................................................177
15.11 Table SUB_BAOC ...........................................................................................................................178
15.12 Table SUB_BICROAM ....................................................................................................................179
15.13 Table SUB_BOIC ............................................................................................................................180
15.14 Table SUB_BOICEXHC ..................................................................................................................181
15.15 Table SUB_CFB ..............................................................................................................................182
15.16 Table SUB_CFNRC ........................................................................................................................183
15.17 Table SUB_CFNRY.........................................................................................................................185
15.18 Table SUB_CFU ..............................................................................................................................186
15.19 Table SUB_COS .............................................................................................................................187
15.20 Table SUB_CUG_FEATURE ..........................................................................................................188
15.21 Table SUB_CUG_SUBSCRIPTION ................................................................................................190
15.22 Table SUB_CW ...............................................................................................................................190
15.23 Table SUB_EXT ..............................................................................................................................191
15.24 Table SUB_IMSI_SS .......................................................................................................................193
15.25 Table SUB_DCSI ............................................................................................................................195
15.26 Table SUB_GPRS_CSI ...................................................................................................................196
15.27 Table SUB_MCSI ............................................................................................................................197
15.28 Table SUB_OCSI ............................................................................................................................197

15.29 Table SUB_SMS_CSI .....................................................................................................................203

15.30 Table SUB_SS_CSI ........................................................................................................................204
15.31 Table SUB_TCSI .............................................................................................................................204
15.32 Table SUB_USSD_CSI ...................................................................................................................207
15.33 Table SUB_CLIN .............................................................................................................................208
15.34 Table SUB_EA ................................................................................................................................208
15.35 Table SUB_GPRS_PROV ..............................................................................................................209
15.36 Table SUB_GPRS_PDPS ...............................................................................................................210
15.37 Table SUB_LCS_CALL_RELATED ................................................................................................210
15.38 Table SUB_LCS_CALL_UNRELATED ...........................................................................................212
15.39 Table SUB_LCS_GMLCS ...............................................................................................................215
15.40 Table SUB_LCS_MOBILE_ORIGINATING ....................................................................................216
15.41 Table SUB_LCS_PLMN_OPERATOR............................................................................................217
15.42 Table SUB_LCS_UNIVERSAL .......................................................................................................218
15.43 Table SUB_VBS ..............................................................................................................................218
15.44 Table SUB_VGCS ...........................................................................................................................222
15.45 Table SUB_SIMR ............................................................................................................................224
15.46 Routing schema ..............................................................................................................................224

1 Introduction
This document details the Home Location Register (HLR) subscriber data model, specifically
provisionable permanent profile data. This document is primarily a reference of the data model and its
validations that you can use, for example, to look up services, their dataitem syntax, and their validations.
1.1 Navigation
• “Subscriber Profile” on page 9
• “Data model and validations” on page 22
• “Authentication data” on page 31
• “Profile control data” on page 33
• “Basic services” on page 40
• “Supplementary services” on page 71
• “Operator-determined barrings” on page 122
• “CAMEL services” on page 124
• “Location Services” on page 141
• “GPRS PDP context IDs” on page 148
• “Other services” on page 153
• “Other components” on page 156
• “Suppression states” on page 159
• “Database Implementation” on page 164

2 Subscriber Profile
The subscriber profile is composed of a primary ID and a collection of profile components. A component
is a logical group of data/functionality. Components can:
• be mandatory or optional
• have datafills or not
• be a distinct area of functionality
• relate to the profile as a whole, in which case they are called profile control components
A group of optional components called basic services has a secondary ID as one of their dataitems.
These IDs can be shared across the basic services for a subscriber, but cannot be shared across
subscribers.
2.1 Navigation
• “Subscriber profile view” on page 9
• “Profile graphical representation” on page 11
2.2 Subscriber profile view

Figure 1 Subscriber profile high-level view on page 10 shows the high-level view of the profile. The top
box shows a very general view of the subscriber profile. The second box expands on the types of
components that exist. Some components are mandatory, namely Authentication data and Profile Control
components. The primary ID is also mandatory, although secondary IDs are optional. All optional
components have a "provisioned" state, to indicate whether they are present or not. This state is not
explicitly included in the data syntax tables in this document, as this state exists even if the subscriber
does not have the component (that is, it is set to false).

Figure 1 Subscriber profile high-level view
Figure 2 Subscriber profile components on page 11 further describes profile components. This section
describes service data in the context of service classifications rather than individual services. The profile
is further described in several figures in the next section. The data model and its validations are provided
in full detail in “Data model and validations” on page 22.

Figure 2 Subscriber profile components
2.3 Profile graphical representation

The subscriber profile encompasses a large number of components. These components are described in
detail in “Data model and validations” on page 22. This section provides a graphical representation of the
profile components.
Each component is listed, together with an indication of whether it is mandatory or optional, and a high-
level view of its dataitems. Individual dataitems are not indicated but are grouped into set data and other
data ("non-set data"). The section also indicates the components that have no dataitems.
2.3.1 Data sets

A component is a logical group of data items. Within a component, there are often further logical groups
of data called sets. A set is usually optional, having a provisioned state much like that of optional
components. Not all dataitems belong to a set, these are described as "non-set" data.
The syntax tables in “Data model and validations” on page 22 show the states of components and the

dataitems that they contain. Sets are named. The "optional" column has a slightly different meaning for
those dataitems in a set. It indicates that the dataitem is optional if the set is provisioned. If the set is not
provisioned, then none of the dataitems will be datafilled, so they are all optional in a wider sense. A set’s
provisioning state is not included in the syntax tables.
If a component has a set, it usually has multiple sets. Figure 3 Sets illustrated on page 12 shows a
component with two sets. It is quite common for these sets to contain a similar or identical group of
dataitems.
Figure 4 Subscriber Profile diagram examples on page 13 gives an introduction to the graphical
representation, with the components illustrated from Figure 5 Subscriber profile diagram part I -
Authentication and Profile Control on page 14 to Figure 12 Subscriber profile part VIII - miscellaneous on
page 21.
Figure 3 Sets illustrated


Figure 4 Subscriber Profile diagram examples


Figure 5 Subscriber profile diagram part I - Authentication and Profile Control


Figure 6 Subscriber profile diagram part II - ODBs


Figure 7 Subscriber profile part III - BSs


Figure 8 Subscriber profile part IV - SSs 1


Figure 9 Subscriber profile part V - SSs 2


Figure 10 Subscriber profile part VI - CAMEL


Figure 11 Subscriber profile part VII - LCS


Figure 12 Subscriber profile part VIII - miscellaneous


3 Data model and validations

This section outlines the data model and the validations involved in provisioning each profile component,
with profile components described first.
3.1 Navigation
• “Profile components” on page 22
• “Proprietary services” on page 26
• “Datatypes” on page 26
• “Data vectors” on page 27
• “Validations introduction” on page 27
• “Profile creation” on page 28
• “Profile deletion” on page 28
• “Transactional validations” on page 28
• “Example component” on page 28
• “HLR-wide validations” on page 29
3.2 Profile components

”Profile components” on page 22 lists the profile components, in order by component type and then
alphabetically. Each component is described in detail in the following sections of this document. For an
example, see ”Example component” on page 28, which also introduces many of the component types.
Table 1 Profile components
Short name Expanded name See section

Primary component
Auth Data Authentication Data “Authentication data” on page 31
Profile control “Profile control data” on page 33
Barring Control n/a “Barring Control” on page 33
Category n/a “Category” on page 34
International Mobile n/a “IMSI Status” on page 36
Subscriber Identity (IMSI)
Status
LMU Location Measurement Unit “Location Measurement Unit” on
page 37
NAM Network Access Mode “Network Access Mode” on page 37
Password n/a “Password” on page 38
Roaming Entitlement n/a “Roaming Entitlement” on page 38
SOAPROV Suppression of Announcements “Suppression of Announcements
provisioning provisioning” on page 39
Basic services “Basic services” on page 40

ALTSPCDA Alternate Speech / CDA Data “Alternate Speech/Circuit Duplex

Asynchronous data” on page 43
ALTSPCDS Alternate Speech / CDS Data “Alternate Speech/Circuit Duplex
Synchronous data” on page 44
ALTSPFAX Alternate Speech / Fax Group 3 “Alternate Speech/Fax Group 3” on
page 45
AUXTPHY Auxiliary Telephony “Auxiliary Telephony” on page 47
CDA Circuit Duplex Asynchronous Data “Circuit Duplex Asynchronous data”
on page 48
CDA 300 Circuit Duplex Asynchronous Data “Circuit Duplex Asynchronous data
300 300” on page 48
1200 1200” on page 49
1275 1275” on page 50
2400 2400” on page 51
4800 4800” on page 52
9600 9600” on page 54
CDAGBS Circuit Duplex Asynchronous Data “Circuit Duplex Asynchronous Data
General Bearer Service General Bearer Service” on page 55
CDS Circuit Duplex Synchronous “Circuit Duplex Synchronous” on
page 56
CDS 1200 Circuit Duplex Synchronous Data “Circuit Duplex Synchronous data
1200 1200” on page 56
2400 2400” on page 57
4800 4800” on page 58
9600 9600” on page 60
CDSGBS Circuit Duplex Synchronous Data “Circuit Duplex Synchronous data
General Bearer Service General Bearer Service” on page 61
FAX3 Facsimile Group 3 “Facsimile Group 3” on page 62
SMMO Short Message Mobile Originating “Short Message Mobile Originating”
on page 63
SMMT Short Message Mobile “Short Message Mobile Terminating”
Terminating on page 64
SPCHCDA Speech followed by CDA Data “Speech followed by CDA data” on
page 65
SPCHCDS Speech followed by CDS Data “Speech followed by CDS data” on
page 66

TPHY Telephony “Telephony” on page 67

VBS Voice Broadcast Service “Voice Broadcast Service” on
page 68
VGCS Voice Group Call Service “Voice Group Call Service” on
page 69
Supplementary services “Supplementary services” on page 71
ACC Accounting Codes “Accounting Codes” on page 74
ACRJ Anonymous Call Reject “Anonymous Call Rejection” on
page 74
AOCC Advice of Charge Charging “Advice of Charge Charging” on
page 75
AOCI Advice of Charge Information “Advice of Charge Information” on
page 75
BAIC Bar All Incoming Calls “Barring of All Incoming Calls” on
page 75
BAOC Bar All Outgoing Calls “Barring of All Outgoing Calls” on
page 77
BICRoam Bar Incoming Calls while Roaming “Barring of Incoming Calls when
Roaming outside HPLMN country” on
page 78
BOIC Bar Outgoing International Calls “Barring of Outgoing International
Calls” on page 79
BOICexHC Bar Outgoing International Call “Barring of Outgoing International
Except to Home Country Calls except to HPLMN Country” on
page 81
CFB Call Forward Busy “Call Forward when Busy” on page 82
CFNRC Call Forward Not Reachable “Call Forward when Not Reachable”
on page 87
CFNRY Call Forward No Reply “Call Forward when No Reply” on
page 92
CFU Call Forward Unconditional “Call Forward Unconditionally” on
page 98
CLIP Calling Line Id Presentation “Calling Line ID Presentation” on
Restriction page 103
CLIR Calling Line Id Restriction “Calling Line ID Restriction” on
page 103
CNAM Calling Name Delivery “Calling Name Delivery” on page 104
COLP Connected Line Id Presentation “Connected Line ID Presentation” on
page 104
COLR Connected Line Id Restriction “Connected Line ID Restriction” on
page 105
COS Class Of Service “Class of Service” on page 105
CRBT Customized Ring Back Tone “Customized Ring Back Tone” on
page 110

CUG Closed User Groups “Closed User Groups” on page 107

CW Call Waiting “Call Waiting” on page 111
ECT Explicit Call Transfer “Explicit Call Transfer” on page 112
EMLPP Enhanced Multi Level Precedence “Enhanced Multi Level Precedence
-Pre-emption and Pre-emption” on page 112
EXT Extension Services “Extension Services” on page 113
FM Follow Me “Follow Me” on page 118
HOLD Call Hold “Call Hold” on page 119
HOTBILL Hot billing “Hot Billing” on page 119
LCO Local Calls Only “Local Calls Only” on page 120
MCT Malicious Call Trace “Malicious Call Trace” on page 120
MPTY Multiparty “Multiparty” on page 121
UUS1 User to User Signaling stage 1 “User to User Signaling stage 1” on
page 121
WPS Wireless Priority Service “Wireless Priority Service” on
page 121
Operator-determined barrings
All ODBs (incoming, outgoing, See “Operator-determined “Operator-determined barrings” on
ECT, misc) barrings” on page 122 for page 122
specifics.
CAMEL services “CAMEL services” on page 124
D-CSI Dialled CAMEL Subscription “Dialed CSI” on page 125
Information
GPRS-CSI General Packet Radio Service “General Packet Radio Service CSI”
CAMEL Subscription Information on page 126
M-CSI Mobility Management CAMEL “Mobility Management CSI” on

Subscription Information page 128
O-CSI Originating CAMEL Subscription “Originating CSI” on page 129

Information
SMS-CSI Short Message Service CAMEL “Short Message Service CSI” on
SS-CSI Supplementary Service CAMEL “Supplementary Service CSI” on

T-CSI Terminating CAMEL Subscription “Terminating CSI” on page 136

Information
TIF-CSI Translations Information Flag “Translations Information Flag CSI”
CAMEL Subscription Information on page 139

USSD-CSI Unstructured Supplementary “Unstructured Supplementary Service

Service Data CAMEL Subscription Data CSI” on page 139
Information
Location Services (LCS) “Location Services” on page 141
LCS Autonomous Self n/a “LCS Autonomous Self Location” on

Location page 141
LCS Basic Self Location n/a “LCS Basic Self Location” on
page 142
LCS Call Related n/a “LCS Call Related” on page 142
LCS Call Unrelated n/a “LCS Call Unrelated” on page 144
LCS GMLCs LCS Gateway Mobile Location “LCS GMLCs” on page 145
Centres
LCS PLMN Operator n/a “LCS PLMN Operator145” on
page 145
LCS Transfer to Third Party n/a “LCS Transfer to Third Party” on
page 146
LCS Universal n/a “LCS Universal” on page 147
GPRS
GPRS General Packet Radio Service “GPRS PDP context IDs” on
page 148
Other services “Other services” on page 153
CLIN Calling Line Identification “Calling Line Identification
Replacement Number Replacement Number” on page 153
EA Equal Access “Equal Access” on page 154
Proprietary IN Proprietary Intelligent Network “Proprietary Intelligent Network
service service” on page 154
Other components “Other components” on page 156
HST Home Subscriber Trace “Home Subscriber Trace” on
page 156
SIMR SIM Replacement “SIM Replacement” on page 157
3.3 Proprietary services

The following are Kapsch proprietary services: ACC, ACRJ, AUXTPHNY,CLIN, CNAM, COS, CRBT, EA,
EXT, HOTBILL, LCO, MCT, and Proprietary IN.
3.4 Datatypes
The subscriber profile database is composed of a finite number of datatypes, shown in Table 2 Primitive
datatypes on page 27. There are three broad types: number, string, and enum. Strings can be composed
of characters, digits, or hex digits. Character strings are usually limited to the particular characters they
can use, typically to alphanumeric characters and underscores. Digits strings use 0..9; whereas hex

strings use 0..9 and A..F. Booleans can be viewed as a special type of enum. The column Examples in
Data Syntax Tables shows the conventions used in the Data Syntax tables in this document. Some
dataitems in the database are optional, so null (a blank) will be a valid value, regardless of their actual
datatype.
Table 2 Primitive datatypes
Datatype Format Example(s) in Data Syntax tables

Number m -n range number: 0 -255
String m -n characters (alphanumeric and 1 -20 characters 1 -20 characters
underscores unless stated otherwise) (alphanumeric, underscores, *, #)
Digit String m -n digits (0..9) 6 -15 digits

Hex String m hex digits (0..9, A..Z) 32 hex digits
Enumerated {FIRST, SECOND, THIRD, ...} {OPERATOR, USER}
Boolean Boolean (that is, true or false) Boolean
3.5 Data vectors

A vector is a collection of elements of the same type, where a variable number of elements can exist and
elements can be added or removed. An abstract example is a names vector; if the vector is datafilled, it
will contain one or more individual name elements, with a limit being imposed on the maximum number of
elements. Elements in vectors are not ordered, and there is no concept of indexes within the vector.
Elements are simply added, removed, or read from the vector.
The database contains two broad types of vector: simple and complex. Simple vectors are a collection
containing just one datatype. An example is the names vector mentioned earlier. A complex vector is
different, in that, rather than containing a collection of elements, it holds a collection of structures. A
structure is composed of two or more elements. An abstract example is a people vector; each item in the
vector is a structure of name, age, and gender elements.
In the example in the following table, the simple vector is mandatory, as indicated by the number of
elements (1 - 3). The complex vector is optional.
Table 3 Vector examples
Type Element(s) Examples

Simple 1 -3 strings, each 1 -20 {"APPLE"}
characters
"{PEAR", "APPLE", "PEACH"}
Complex 0 -3 structures of {{"RED", 123}}
-string, 1 -20 characters {{"RED", 98}}, {"GREEN", 240}}
-number, 0 -255 range
3.6 Validations introduction

Subsequent component data model sections detail datafill and provisioning validations for each
component in the subscriber profile. Operator mode validations are detailed, that is, those applicable to

operator provisioning updates. Validations for network profile updates are not covered by this document.
There are three very broad validations areas that are provided in the following table. You can create and
subsequently delete a profile by provisioning. Modify profiles by provisioning transactions. Such a
transaction can add/modify/delete multiple components.
“Example component” on page 28 provides a guide to the component data model sections.
Table 4 Validation areas
Validation area See section(s)

Profile Creation “Profile creation” on page 28
Profile Deletion “Profile deletion” on page 28
Profile Modification “Transactional validations” on page 28
3.7 Profile creation

A profile is created by datafilling authentication data. The current Kapsch HLR implementation auto-
provisions Profile Control Data with default values. See “Profile control data” on page 33. The following
checks are performed:
• The IMSI must be available for use (that is, not already in use).
• The authentication data must be valid. See “Authentication data” on page 31.
3.8 Profile deletion

To delete a subscriber profile, ensure that the following conditions are met:
• IMSI Status must be DEACTIVATED.

• No services must be provisioned.
• Subscriber must not be involved in an SIMR relationship.
You can delete a profile with Home Subscriber Trace (HST).
3.9 Transactional validations

These validations apply to all profile modification provisioning actions.
If the IMSI Status is set to REPLACEMENT, then no updates to the profile are allowed.
3.10 Example component

The following sections first outline how to datafill the component, and then discuss component
interactions. The content and structure of each subsection is described immediately thereafter. See the
service’s documentation for details on functionality.
3.10.1 Datafill
This subsection details the component’s datafill. The dataitems and their syntax are detailed in the Data
Syntax table; see Table 5 Example data syntax on page 29 for an example. The example shows one
dataitem that is not part of a set, and then two sets, each with two dataitems.
Syntax checks describe the format of the dataitem, and do not include any checks resulting from

interactions with other dataitems. They describe the checks for validating the dataitem in isolation. The
sample syntax checks are checking the dataitem in a string (of the correct length) or a number (in the
correct range) or a boolean.
This subsection also includes the intra-component validations in a bullet list. These are validations arising
from interactions between the dataitems of this component. An example intra-component interaction is
that dataitem X must be greater than dataitem Y.
Table 5 Example data syntax
Dataitem Syntax Optional

Dataitem name The syntax is described here This column indicates
for each dataitem. See whether each dataitem
Set name Dataitem name
“Datatypes” on page 26 for is optional, including
Dataitem name examples and help how many entries are
optional for vectors.
Set name Dataitem name Some components have
Dataitem name vectors; these will be indicated
in this table. For more
information, see “Data
vectors” on page 27.
The dataitems, also known as fields, are described in the Field descriptions tables. See the following
table for an example.
Table 6 Example field descriptions
Dataitem Description
Dataitem name A concise description is given for each dataitem,
including expansion of the shortened/acronym enum
Set name Dataitem name options.
Dataitem name
Set name Dataitem name
Dataitem name
3.10.2 Interactions
This subsection details the interactions with other components and system data. Provisioning side effects
are also included. An example interaction with system data is Dataitem X must exist in the YYY field of
system table ZZZ.
Example interactions with other services are
• Service A can only be provisioned if service B is also provisioned.

• The syntax of dataitem X of service A depends on dataitem M of service B.
3.11 HLR-wide validations

This subsection provides those validations that interact with other subscribers and their data. If there are
no such validations, the subsection is not included. Some examples of these validations are

• The value for a particular dataitem cannot be used by more than one subscriber; that is,
its value must be unique.
• A limit is placed on the number of subscribers that can have a particular service
provisioned.

4 Authentication data
Authentication data is a mandatory datafill for all subscribers. The Kapsch HLR includes authentication
center (AUC) functionality.
4.1 Navigation
• “Datafill” on page 31
• “Interactions” on page 32
• “Additional information” on page 32
4.2 Datafill
The Authentication data syntax is detailed in the following table. A 2G subscriber has a GSM algorithm
and hence a Ki, whereas a 3G subscriber has a UMTS algorithm and hence a K. The algorithm indirectly
indicates whether the subscriber is 2G or 3G. For more information, see “Determination of 2G/3G
algorithm” on page 32. The IMSI is composed of three parts:
• Mobile Country Code (MCC)

• Mobile Network Code (MNC)
• Mobile Subscriber ISDN (MSIN)
Table 7 Authentication data syntax

IMSI 6 -15 digits
Ki (2G) or K (3G) 32 hex digits
Algorithm number: 0 -255
Operator-variant algorithm 32 hex digits Yes
Configuration (OPC)
The following table describes authentication data fields.
Table 8 Authentication data field descriptions
IMSI International Mobile Subscriber Identity, a unique ID specified by a
SIM card
Ki (2G) or K (3G) The key used in authentication; 2G subscribers have a Ki, whereas
3G subscribers have a K.
Algorithm This number maps to a 2G/3G authentication algorithm in system
Table GHLRALG (the relationship is not enforced).
This is also known as AlgSel and algorithm selection.
OPC Operator variant algorithm configuration, used by the UMTS
milenage algorithm.
This is also known as OPc Algorithm Parameter.

4.3 Interactions
Authentication data interacts with IMSI Status, GPRS, system tables GHLRALG, GHLRPDP, and the
office parameter GHLR_IMSI_MNC, as follows:
• The MNC portion of the IMSI must be valid according to office parameter
GHLR_IMSI_MNC (table OFCSTD). The MNC is the fourth, fifth, and possibly the sixth
digit of the IMSI. If the parameter’s MNC_SELECTOR is set to SINGLE, then the MNC
must match the parameter’s SINGLE_MNC_VALUE. If SINGLE_MNC_VALUE has two
digits, then the MNC is taken to be the IMSI’s fourth and fifth digits; whereas if
SINGLE_MNC_VALUE has three digits, then the MNC is taken to be the IMSI’s fourth,
fifth, and sixth digits. If it is set to MULTIPLE, then the IMSI’s length must be a minimum of
(4+MULTIPLE_MNC_LENGTH); the 4 originates from the length of the IMSI MCC (3
digits) added to the minimum length of the IMSI MSIN (1-digit minimum)
• The algorithm should map to an entry in the ALGSEL column of system Table GHLRALG,
but this relationship is not enforced.
• If the subscriber’s IMSI Status is set to REPLACEMENT, the algorithm cannot change
from a 2G to a 3G type, or from a 3G to a 2G type. The determination of 2G/3G requires
system Table GHLRALG as explained in “Determination of 2G/3G algorithm” on page 32.
• If the algorithm is 3G, then all of the subscriber’s Packet Data Protocols (PDP) (GPRS)
must have ExtQoS. A PDP has ExtQoS if its entry in system Table GHLRPDP
(PDPNAME field) has the EXTQOS field datafilled. The determination of 2G/3G requires
system Table GHLRALG as explained in “Determination of 2G/3G algorithm” on page 32.
• The OPC must be datafilled if the algorithm maps to the 3G algorithms:
– UMTS_MILENAGE
– UMTS_SAM
The OPC can be datafilled for the 3G algorithm UMTS_OP_MILENAGE, but in this case the value is
ignored. For all other algorithms, the OPC must not be datafilled.
4.4 Additional information
4.4.1 Determination of 2G/3G algorithm

An algorithm is 3G if it maps to an entry in system Table GHLRALG (ALGSEL field) whose
FLAVOUR.BASE_ALG begins "UMTS". Currently the 3G algorithms are:
• UMTS_XOR
• UMTS_MILENAGE
• UMTS_OP_MILENAGE
• UMTS_SAM
All other algorithms, whether they exist in GHLRALG or not, are 2G.

5 Profile control data

Profile control data are mandatory components that help define the subscriber’s profile and relate to the
profile as a whole. For instance, the IMSI Status defines the status of the subscriber in the network (for
example, activated). Profile control data components are listed in the following table, along with their
default values. These values are used for blank subscribers (essentially subscribers that only have
authentication datafill).
Table 9 Profile control data
Component Dataitem(s) Default values See section

Barring Control BICCTRL OPERATOR “Barring Control” on
page 33
BOCCTRL OPERATOR
Category Category ORDINARY ”Category” on page 34
IMSI Status IMSI Status DEACTIVATED “IMSI Status” on page 36

Cust Group null
NCOS null
LMU (Location LMU FALSE “Location Measurement
Measurement Unit) Unit” on page 37
NAM (Network Access NAM office parameter NAM_DFLT “Network Access Mode”
Mode) from table GHLRPARM on page 37
Password Password office parameter PASSDFLT “Password” on page 38
from table GHLRPARM
Roaming Entitleme nt Roaming Entitlement UNKW “Roaming Entitlement” on
page 38
SOAPROV SOAPROV FALSE “Suppression of
Announcements
provisioning” on page 39
5.1 Navigation
• “Barring Control” on page 33
• ”Category” on page 34
• “IMSI Status” on page 36
• “Location Measurement Unit” on page 37
• “Network Access Mode” on page 37
• “Password” on page 38
• “Roaming Entitlement” on page 38
• “Suppression of Announcements provisioning” on page 39
5.2 Barring Control

The Barring Control component is profile control data and is therefore a mandatory datafill. The
component indicates whether you have control over incoming/outgoing barrings.

5.2.1 Datafill
The syntax for Barring Control data is shown in the following table.
Table 10 Barring Control data syntax

BICCTRL {OPERATOR, USER}
BOCCTRL {OPERATOR, USER]
Barring Control field descriptions are provided in the following table.
Table 11 Barring Control field descriptions
BICCTRL control of barring incoming calls: operator or user
BOCCTRL control of barring outgoing calls: operator or user
5.2.2 Interactions
None
5.3 Category
The Category component is profile control data and is therefore a mandatory datafill. It is used to indicate
the subscriber category, which is used for signaling and billing.
5.3.1 Datafill
The syntax for Category data is shown in the following table.
Table 12 Category control data syntax

Category {ORDINARY, PRIORITY, TEST, PAYPHONE, DATA, ORDNCHRG,
PRINCHRG, UNKNOWN, FRENCH, ENGLISH, GERMAN, RUSSIAN,
SPANISH, RESERVED, SPARLANG1, SPARLANG2, SPARLANG3,
FIXEDACCESS, CHINAIP, CATEGORY14, CATEGORY17,
CATEGORY18 CATEGORY19, CATEGORY20, CATEGORY21,
CATEGORY22, CATEGORY23, CATEGORY24, CATEGORY25,


CATEGORY114 CATEGORY115, CATEGORY116, CATEGORY117,
CATEGORY130, CATEGORY131, CATEGORY132,
CATEGORY246, CATEGOTY247, CATEGORY248,
CATEGORY252, CATEGORY253, CATEGORY254}
Category field descriptions are provided in the following table.


Table 13 Category control field description
Category the subscriber category, used for signaling and billing
5.3.2 Interactions
None
5.4 IMSI Status

The IMSI Status component is profile control data and is therefore a mandatory datafill. It defines the
status of the subscriber within the network and hot-line routing (HLR) class of service (COS) information
for NEW subscribers (as defined by their IMSI Status dataitem).
5.4.1 Datafill
IMSI Status data syntax is detailed in the following table. The following intra-service interactions apply:
• You cannot manually set IMSI Status to REPLACEMENT; the IMSI Status is automatically
changed to REPLACEMENT when the IMSI is assigned to be the new IMSI in a SIM
Replacement (SIMR) relationship.
• If IMSI Status is not NEW, then Cust Group and NCOS must not be datafilled.
• If IMSI Status is NEW, then Cust Group must be datafilled. NCOS can optionally be
datafilled too.
Table 14 IMSI Status data syntax

IMSI Status {ACTIVATED, DEACTIVATED, NEW, REPLACEMENT}
Cust Group number: 0 - 4095 Optional
NCOS number: 0 - 255 Optional
IMSI Status field descriptions are provided in the following table.
Table 15 IMSI Status field descriptions
IMSI Status the status of the subscriber within the network: Activated, Deactivated, New,
or Replacement. (The Replacement state is only valid for “new" IMSIs in a
SIMR relationship.)
This is also known as IStatus.
Cust Group hot-line routing customer group for new subscribers defined in system tables
GSMCUST and GSMNCOS
NCOS hot-line routing network class of service for new subscribers defined in
system Table GSMNCOS

5.4.2 Interactions
IMSI Status interacts with all ODBs and system tables GSMCUST and GSMNCOS, as follows:
• If IMSI Status is NEW, then no ODBs can be provisioned.

• If IMSI Status is NEW and NCOS has not been datafilled, then the Cust Group must be an
entry from the GSM_CUSTGRP_KEY field of system Table GSMCUST, and this entry
must have the USERTYPE and XLT fields datafilled with the USERTYPE option set to
HTL.
• If IMSI Status is NEW and NCOS has been datafilled, then the Cust Group and NCOS
combined must be an entry from the GSM_NCOS_KEY field of system Table GSMNCOS.
This entry must have the USERTYPE and XLT fields datafilled with the USERTYPE option
set to HTL.
5.5 Location Measurement Unit

The Location Measurement Unit (LMU) component is profile control data and is therefore a mandatory
datafill. It is used in E911.
5.5.1 Datafill
The syntax for LMU data is shown in the following table.
Table 16 LMU controi data syntax

LMU Boolean
LMU field descriptions are provided in the following table.
Table 17 LMU field descriptions
LMU Location measurement unit, used in E911
5.5.2 Interactions
None
5.6 Network Access Mode

The Network Access Mode (NAM) component is profile control data and is therefore a mandatory datafill.
It is used to indicate whether the subscriber is entitled to GSM and/or GPRS service.
5.6.1 Datafill
The syntax for NAM data is shown in the following table.

Table 18 NAM control data syntax

NAM {MSC_ONLY, SGSN_ONLY, GSN_AND_MSC}
NAM field descriptions are provided in the following table.
Table 19 NAM field descriptions
NAM Network access mode. Shows whether the subscriber is entitled to the
GSM service only (MSC_ONLY), the GPRS service only
(SGSN_ONLY), or both (SGSN_AND_MSC).
5.7 Password
The Password component is profile control data and is therefore a mandatory datafill. It provides the
password for barring supplementary services.
5.7.1 Datafill
The syntax for Password data is shown in the following table.
Table 20 Password control data syntax

Password 4 digits
Password field descriptions are provided in the following table.
Table 21 Password field descriptions
Password password for barring supplementary services
5.7.2 Interactions
None
5.8 Roaming Entitlement

The Roaming Entitlement component is profile control data and is therefore a mandatory datafill.
5.8.1 Datafill
The syntax for Roaming Entitlement data is shown in the following table.

Table 22 Roaming Entitlement data syntax

Roaming Entitlement 1 - 16 characters
Roaming Entitlement field descriptions are provided in the following table.
Table 23 Roaming Entitlement field descriptions
Roaming Entitlement the subscriber’s roaming entitlement (can be set to unknown)
5.8.2 Interactions
Roaming Entitlement interacts with system Table GHLRRMZN. The Roaming Entitlement must either be
UNKW or an entry from the ROAM column of system Table GHLRRMZN.
5.9 Suppression of Announcements provisioning

The Suppression of Announcements provisioning (SOAPROV) component is profile control data and is
therefore a mandatory datafill. It indicates whether the suppression of announcements (to a called party)
parameter is sent in a Provide Roaming Number (PRN) v3 message.
5.9.1 Datafill
The syntax for SOAPROV data is shown in the following table.
Table 24 SOAPROV data syntax

SOAPROV Boolean
SOAPROV field descriptions are provided in the following table.
Table 25 SOAPROV field descriptions
SOAPROV Shows whether the suppression of announcements (to a called party)
parameter is sent in a PRN v3 message.
5.9.2 Interactions
None

6 Basic services
Basic services are teleservices/bearer services in the telecommunication network. Teleservices are end-
to-end services between Mobile Station (MS) handsets or other terminal devices. Service definitions
cover all seven layers of the Open Systems Interconnection (OSI) model. Bearer services are point-to-
point services between access points. Service definitions only cover layers one to three of the OSI model.
Actions at layers four to seven must be specified by user applications; they are not part of the bearer
service.
6.1 Navigation
• “HLR supported basic services” on page 40
• “Notes on basic services” on page 42
• “Alternate Speech/Circuit Duplex Asynchronous data” on page 43
• “Alternate Speech/Circuit Duplex Synchronous data” on page 44
• “Alternate Speech/Fax Group 3” on page 45
• “Auxiliary Telephony” on page 47
• “Circuit Duplex Asynchronous data” on page 48 and various sub-speeds
• “Circuit Duplex Asynchronous Data General Bearer Service” on page 55
• “Circuit Duplex Synchronous” on page 56
• “Facsimile Group 3” on page 62
• “Short Message Mobile Originating” on page 63
• “Short Message Mobile Terminating” on page 64
• “Speech followed by CDA data” on page 65
• “Speech followed by CDS data” on page 66
• “Telephony” on page 67
• “Voice Broadcast Service” on page 68
• “Voice Group Call Service” on page 69
6.2 HLR supported basic services

The HLR supports the basic services provided in the following table. The Emergency Calls service is
implicitly provisioned to all subscribers; there are no specific datafill or validations.
Table 26 Basic services
Short name Expanded name Type See section

ALTSPCDA Alternate Speech / Bearer Service “Alternate Speech/Circuit Duplex
CDA Data Synchronous data” on page 44
ALTSPCDS Alternate Speech / Bearer Service “Alternate Speech/Circuit Duplex
CDS Data Synchronous data” on page 44
ALTSPFAX Alternate Speech / Fax Teleservice “Alternate Speech/Fax Group 3” on
Group 3 page 45
AUXTPHNY Auxiliary Telephony Teleservice “Auxiliary Telephony” on page 47

CDA Circuit Duplex Bearer Service “Circuit Duplex Asynchronous data”

Asynchronous Data on page 48
CDA300 Circuit Duplex Bearer Service “Circuit Duplex Asynchronous data
Asynchronous Data 300” on page 48
300
1200
1275
2400
4800
9600
CDAGBS Circuit Duplex Bearer Service “Circuit Duplex Asynchronous Data
Asynchronous Data General Bearer Service” on page 55
General Bearer Service
CDS Circuit Duplex Bearer Service “Circuit Duplex Synchronous” on
Synchronous Data page 56
CDS1200 Circuit Duplex Bearer Service “Circuit Duplex Synchronous data
Synchronous Data 1200” on page 56
1200
2400
4800
9600
CDSGBS Circuit Duplex Bearer Service “Circuit Duplex Synchronous data
Synchronous Data General Bearer Service” on page 61
General Bearer Service
Emergency Emergency Calls Teleservice
Calls
FAX3 Facsimile Group 3 Teleservice “Facsimile Group 3” on page 62
SMMO Short Message Mobile Teleservice “Short Message Mobile Originating”
Originating on page 63
SMMT Short Message Mobile Teleservice “Short Message Mobile
Terminating Terminating” on page 64
SPCHCDA Speech followed by Bearer Service “Speech followed by CDA data” on

CDA Data page 65

SPCHCDS Speech followed by Bearer Service “Speech followed by CDS data” on
CDS Data page 66
TPHNY Telephony Teleservice “Telephony” on page 67
VBS Voice Broadcast Teleservice “Voice Broadcast Service” on
Service page 68
VGCS Voice Group Call Teleservice “Voice Group Call Service” on
Service page 69
Each basic service belongs to a basic service group (BSG); these are provided in the following table.
Emergency Calls are a speech service, although the data model only places TPHNY in the SPCH basic
service group.
Table 27 Basic service groups
Basic service group Expanded name Basic services

SPCH Speech basic service group TPHNY
AUXSPCH Auxiliary Speech basic service group AUXTPHNY
SMS Short Message Service basic service group SMMO, SMMT
CDA Circuit Duplex Asynchronous Data services ALTSPCDA, CDA, CDA300,

or basic service group CDA1200, CDA1275, CDA2400,
CDA4800, CDA9600, CDAGBS,
SPCHCDA
CDS Circuit Duplex Synchronous Data services ALTSPCDS, CDS, CDS1200,
or basic service group CDS2400, CDS4800, CDS9600,
CDSGBS, SPCHCDS
FAX Facsimile basic service group ALTSPFAX, FAX3
VGS Voice Group Service basic service group VBS, VGCS
6.3 Notes on basic services

• A datafill for a basic service has an MSISDN and bearer capability index (BCI).
• CDA1275, SMMO, and SMMT do not have a BCI.
• VBS and VGCS have an entirely different datafill. These two services are specific to GSM
Railways (GSMR).
6.3.1 BCI validation

BCI validation is rather complex but can be summarized by the following rule, with exceptions described
in this section.
If more than one service shares an MSISDN, then all their BCIs must be null. There are three exceptions:
• If a service "X" shares an MSISDN with only SMMO/SMMT/CDA1275, then "X" can have
a BCI.
• FAX3/CDA/CDS can share an MSISDN, and one of them can have a BCI.

• Sister basic services always share an MSISDN. One of them must have a BCI, the other
must not.
There are two pairs of sister basic services: ALTSPCDA and ALTSPCDS and SPCHCDA and
SPCHCDS.
6.4 Alternate Speech/Circuit Duplex Asynchronous data

The Alternate Speech/Circuit Duplex Asynchronous (ALTSPCDA) datafill defines the MSISDN and bearer
capability for alternate speech/CDA data. ALTSPCDA belongs to the CDA basic service group (BSG).
6.4.1 Datafill
ALTSPCDA data syntax is detailed in the following table. The three MSISDN fields are combined to
provide the complete MSISDN (that is CC + NDC + SN). The following intra-service validation applies.
The length of the complete MSISDN (that is CC + NDC + SN) must be 3 to 15 digits.
Table 28 ALTSPCDA data syntax

MSISDN CC 1 to 3 digits, first digit
cannot be zero
MSISDN NDC 1 to 13 digits
MSISDN SN 1 to 13 digits
BCI number: 0 -255 Optional
ALTSPCDA field descriptions are provided in the following table.
Table 29 ALTSPCDA field descriptions
MSISDN CC Mobile Subscriber ISDN, Country Code component
MSISDN NDC Mobile Subscriber ISDN, National Destination Code

component
MSISDN SN Mobile Subscriber ISDN, subscriber number
BCI Bearer Capability Index, defined in system Table

GHLRBCA
6.4.2 Interaction
ALTSPCDA interacts with all other basic services, all Basic Service Group (BSG) supplementary
services, and system Table GHLRBCA, as follows:
• The MSISDN CC must match all other basic service MSISDN CCs
• If the MSISDN matches the MSISDN of any other basic service except
SMMO/SMMT/CDA1275/ALTSPCDS, do not datafill ALTSPCDA’s BCI.
• If datafilled, the BCI must be an entry from the BCAKEY column of system Table

GHLRBCA, and the value in the system table’s BSVC field must be ALTSPCDA.
• ALTSPCDA belongs to the CDA BSG; at least one basic service from the CDA BSG must
be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam,
BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW, and EXT).
• The MSISDN must not match any Forward to Number (FTN) of CFB, CFNRc, CFNRy, or
CFU.
• When provisioning ALTSPCDA, you must supply a BCI unless ALTSPCDS is concurrently
provisioned with a BCI.
• Upon provisioning ALTSPCDA, ALTSPCDS is automatically provisioned with the same
MSISDN and a null BCI (unless explicitly provisioned also).
• ALTSPCDA and ALTSPCDS must have the same MSISDN. Upon changing the MSISDN
of one service, the other service’s MSISDN is automatically updated to match.
• One of ALTSPCDA/ALTSPCDS must have a BCI, the other must have a null BCI. Upon
changing the null BCI to a value, the other service’s BCI is automatically updated to have
a null BCI. It is not valid to change the service with the BCI so that it has a null BCI (as
then both services have a null BCI).
• Upon deprovisioning ALTSPCDA, ALTSPCDS is automatically deprovisioned too.
6.4.3 HLR-wide validations

The MSISDN cannot be used by any other subscriber (interacts with all basic services except
VBS/VGCS) for all subscribers.
6.5 Alternate Speech/Circuit Duplex Synchronous data

Alternate Speech/Circuit Duplex Synchronous (ALTSPCDS) datafill defines the MSISDN and bearer
capability for alternate speech/CDS data. ALTSPCDS belongs to the CDS basic service group (BSG).
6.5.1 Datafill
ALTSPCDS data syntax is detailed in the following table. The three MSISDN fields are combined to give
the complete MSISDN (that is CC + NDC + SN). The following intra-service validation applies.
Table 30 ALTSPCDS data syntax

MSISDN CC 1 to 3 digits, first digit cannot be zero
ALTSPCDS field descriptions are provided in the following table.


Table 31 ALTSPCDS field descriptions
MSISDN NDC Mobile Subscriber ISDN, National Destination Code component

BCI Bearer Capability Index, defined in system Table GHLRBCA
6.5.2 Interactions
ALTSPCDS interacts with all other basic services, all BSG supplementary services, and system Table
GHLRBCA, as follows:
• The MSISDN Country Code (CC) must match all other basic service MSISDN CCs.
SMMO/SMMT/CDA1275/ALTSPCDA, do not datafill ALTSPCDS’s BCI.
GHLRBCA, and the value in the system table’s BSVC field must be ALTSPCDS.
• ALTSPCDS belongs to the Circuit Duplex Synchronous (CDS) BSG; at least one basic
service from the CDS BSG must be provisioned if any BSG-SS is registered against CDS
(services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS,
CUG, CW, and EXT).
• The MSISDN must not match any FTN of CFB, CFNRc, CFNRy, or CFU.
• When provisioning ALTSPCDS, supply a BCI unless ALTSPCDA is concurrently
• Upon provisioning ALTSPCDS, ALTSPCDA is automatically provisioned with the same
• ALTSPCDS and ALTSPCDA must have the same MSISDN. Upon changing the MSISDN
of one service, the other service’s MSISDN is automatically updated to match.
• One of ALTSPCDS/ALTSPCDA must have a BCI, the other must have a null BCI. Upon
• Upon deprovisioning ALTSPCDS, ALTSPCDA is automatically deprovisioned too.

6.6 Alternate Speech/Fax Group 3

Alternate Speech/Fax Group 3 (ALTSPFAX) datafill defines the MSISDN and bearer capability for
alternate speech/fax group 3. ALTSPFAX belongs to the FAX basic service group (BSG).

6.6.1 Datafill
The ALTSPFAX data syntax is detailed in the following table. The three MSISDN fields are combined to
give the complete MSISDN (that is CC + NDC + SN). The following intra-service validation applies.
Table 32 ALTSPFAX data syntax

ALTSPFAX field descriptions are provided in the following table.
Table 33 ALTSPFAX field descriptions
component
6.6.2 Interactions
ALTSPFAX interacts with all other basic services, all BSG supplementary services, and system Table
• ALTSPFAX is mutually exclusive with FAX3.

• The MSISDN CC must match all other basic service MSISDN CCs.
SMMO/SMMT/CDA1275, then ALTSPFAX’s BCI must not be datafilled.
GHLRBCA, and the value in the system table’s BSVC field must be ALTSPFAX.
• ALTSPFAX belongs to the FAX BSG; at least one basic service from the FAX BSG must
be provisioned if any BSG-SS is registered against FAX (services BAIC, BICRoam,
• The MSISDN must not match any FTN of CFB, CFNRc, CFNRy,, or CFU.


6.7 Auxiliary Telephony

Auxiliary Telephony (AUXTPHNY) datafill defines the MSISDN and bearer capability for voice calls on an
alternate line. AUXTPHNY is an Kapsch proprietory service and belongs to the AUXSPCH basic service
group (BSG).
6.7.1 Datafill
AUXTPHNY data syntax is detailed in the following table. The three MSISDN fields are combined to give
The length of the complete MSISDN (that is, CC + NDC + SN) must be 3 to 15 digits.
Table 34 AUXTPHNY data syntax


AUXTPHNY field descriptions are provided in the following table.
Table 35 AUXTPHNY field descriptions
6.7.2 Interactions
AUXTPHNY interacts with all other basic services, all BSG supplementary services, and system Table
• TPHNY must be provisioned for AUXTPHNY to be provisioned.

SMMO/SMMT/CDA1275 then AUXTPHNY’s BCI must not be datafilled.
GHLRBCA, and the value in the system table’s BSVC field must be AUXTPHNY.
• AUXTPHNY must be provisioned if any BSG-SS is registered against AUXSPCH
(services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS,
CUG, CW, and EXT).


6.8 Circuit Duplex Asynchronous data

Circuit Duplex Asynchronous (CDA) data is a special case. Provisioning this "basic service" is equivalent
to provisioning CDA300, CDA1200, CDA1275, CDA2400, CDA4800, and CDA9600, using the datafill
specified for CDA. The individual CDAxxx services can be provisioned alongside CDA.
For example, a subscriber can have both CDA and CDA300 provisioned. The subscriber profile will
actually have all CDAxxx services. The datafill used for CDA300 will be equal to that specified for
CDA300 and not equal to the CDA datafill (that is, the CDA300 datafill takes precedence). If CDA is
subsequently deprovisioned, then all CDAxxx services are removed except CDA300, as this is still
explicitly provisioned.
See the individual service sections for datafill/interactions details. CDA does have a special case for BCI
validation; however,
SMMO/SMMT/CDA1275, do not datafill CDA’s BCI, but there is an exception:
FAX3/CDA/CDS can share an MSISDN, and one of them can have a BCI.
GHLRBCA, and the value in the system table’s BSVC field must be CDA9600.
CDA is also the name of a basic service group (BSG). When CDA is used, it typically refers to the BSG,
rather than this basic service.
6.9 Circuit Duplex Asynchronous data 300

CDA300 datafill defines the MSISDN and bearer capability for 300 bits/second CDA. CDA300 belongs to
the CDA basic service group (BSG).
6.9.1 Datafill
CDA300 data syntax is detailed in the following table. The three MSISDN fields are combined to give the
complete MSISDN (that is, CC + NDC + SN). The following intra-service validation applies.
Table 36 CDA300 data syntax

CDA300 field descriptions are provided in the following table.


Table 37 CDA300 field descriptions
component
6.9.2 Interactions
CDA300 interacts with all other basic services, all BSG supplementary services, and system Table
• CDA300 is mutually exclusive with CDAGBS.

SMMO/SMMT/CDA1275, then CDA300’s BCI must not be datafilled.
• CDA300 belongs to the CDA BSG; at least one basic service from the CDA BSG must be
provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC,
BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW, and EXT).
6.9.3 HLR-wide interactions


CDA1200 datafill defines the MSISDN and bearer capability for 1200 bits/second CDA. CDA1200 belongs
to the CDA basic service group (BSG).
6.10.1 Datafill
CDA1200 data syntax is detailed in the following table. The three MSISDN fields are combined to provide



6.10.2 Interactions

SMMO/SMMT/CDA1275, do not datafill CDA1200’s BCI.
• CDA1200 belongs to the CDA BSG; at least one basic service from the CDA BSG must


6.11.1 Datafill


component
6.11.2 Interactions
CDA1275 interacts with all other basic services and all BSG supplementary services, as follows:



6.12.1 Datafill


component
6.12.2 Interactions

• The MSISDN CC must match all other basic service MSISDN CCs



6.13.1 Datafill

6.13.2 Interactions

be provisioned if any BSG-SS is registered against CDA (services BAIC, BICR oam,



6.14.1 Datafill

6.14.2 Interactions
• CDA9600 is mutually exclusive with CDAGBS

GHLRBCA, and the value in the system table’s BSVC field must be CDA9600
BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW, and EXT)
• the MSISDN must not match any FTN of , CFNRc, CFNRy, or CFU

6.15 Circuit Duplex Asynchronous Data General Bearer Service

Circuit Duplex Asynchronous data General Bearer Service (CDAGBS) datafill defines the MSISDN and
bearer capability for the CDA General Bearer Service, that allows support for all data rates up to and
including 64 kbit/second. CDAGBS belongs to the CDA basic service group (BSG).
6.15.1 Datafill
CDAGBS data syntax is detailed in the following table. The three MSISDN fields are combined to give the
Table 48 CDAGBS data syntax


CDAGBS field descriptions are provided in the following table.
Table 49 CDAGBS field descriptions

6.15.2 Interactions
CDAGBS interacts with all other basic services, all BSG supplementary services, and system Table
GHLRBCA.
• CDAGBS is mutually exclusive with CDA (basic service), CDA300, CDA1200, CDA1275,
CDA2400, CDA4800, and CDA9600
SMMO/SMMT/CDA1275, do not datafill CDAGBS’s BCI
GHLRBCA, and the value in the system table’s BSVC field must be CDAGBS
• CDAGBS belongs to the CDA BSG; at least one basic service from the CDA BSG must
BAOC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW, and EXT)
• the MSISDN must not match any FTN of CFB, CFNRc, CFNRy, or CFU


6.16 Circuit Duplex Synchronous

Circuit Duplex Synchronous (CDS) data is a special case. Provisioning this "basic service" is equivalent
to provisioning CDS1200, CDS2400, CDS4800, and CDS9600, using the datafill specified for CDS. You
can provision the individual CDSxxx services CDS.
For example, a subscriber can have both CDS and CDS1200 provisioned. The subscriber profile will
actually have all CDSxxx services. The datafill used for CDS1200 will be equal to that specified for
CDS1200, and not equal to the CDS datafill (that is, the CDS1200 datafill takes precedence). If CDS is
subsequently deprovisioned, then all CDSxxx services are removed except CDS1200, as this is still
explicitly provisioned.
See the individual service sections for datafill/interactions details. CDS does have a special case for BCI
validation, however:
SMMO/SMMT/CDA1275, do not datafill CDS’s BCI but there is an exception:
– FAX3/CDA/CDS can share an MSISDN, and one of them can have a BCI
GHLRBCA, and the value in the system table’s BSVC field must be CDS9600.
CDS is also the name of a Basic Service Group (BSG). When CDS is used, it typically refers to the BSG,
rather than this basic service.
6.17 Circuit Duplex Synchronous data 1200

CDS1200 datafill defines the MSISDN and bearer capability for 1200 bits/second CDS. CDS1200 belongs
to the CDS basic service group (BSG).
6.17.1 Datafill
CDS1200 data syntax is detailed in the following table. The three MSISDN fields are combined to give the
Table 50 CDS1200 data syntax

CDS1200 field descriptions are provided in the following table.


Table 51 CDS1200 field descriptions

6.17.2 Interactions
CDS1200 interacts with all other basic services, all BSG supplementary services, and system Table
GHLRBCA.
• CDS1200 is mutually exclusive with CDSGBS

SMMO/SMMT/CDA1275, do not datafill CDS1200’s BCI
GHLRBCA, and the value in the system table’s BSVC field must be CDS1200
• CDS1200 belongs to the CDS BSG; at least one basic service from the CDS BSG must
be provisioned if any BSG-SS is registered against CDS (services BAIC, BICRoam,


6.18.1 Datafill


6.18.2 Interactions
GHLRBCA.



6.19.1 Datafill


6.19.2 Interactions
GHLRBCA.




6.20.1 Datafill

6.20.2 Interactions
GHLRBCA.
• CDS9600 is mutually exclusive with CDSGBS.

SMMO/SMMT/CDA1275, do not datafill CDS9600’s BCI.
GHLRBCA, and the value in the system Table’s BSVC field must be CDS9600.


6.21 Circuit Duplex Synchronous data General Bearer Service

Circuit Duplex Synchronous data General Bearer Service (CDSGBS) datafill defines the MSISDN and
bearer capability for the CDS General Bearer Service, that allows support for all data rates up to and
including 64 kbit/second. Use this service to support H.324-M (circuit video calls), for example. CDSGBS
belongs to the CDS basic service group (BSG).
6.21.1 Datafill
CDSGBS data syntax is detailed in the following table. The three MSISDN fields are combined to give the
Table 58 CDSGBS data syntax

CDSGBS field descriptions are provided in the following table.
Table 59 CDSGBS field descriptions
6.21.2 Interactions
CDSGBS interacts with all other basic services, all BSG supplementary services, and system Table
• CDSGBS is mutually exclusive with CDS (basic service), CDS1200, CDS2400, CDS4800,
and CDS9600
SMMO/SMMT/CDA1275, do not datafill CDSGBS’s BCI.
GHLRBCA, and the value in the system table’s BSVC field must be CDSGBS.

• CDSGBS belongs to the CDS BSG; at least one basic service from the CDS BSG must be
provisioned if any BSG-SS is registered against CDS (services BAIC, BICRoam, BAOC,

6.22 Facsimile Group 3

Facsimile Group 3 (FAX3) datafill defines the MSISDN and bearer capability for fax3. FAX3 belongs to
the FAX basic service group (BSG).
6.22.1 Datafill
FAX3 data syntax is detailed in the following table. The three MSISDN fields are combined to give the
Table 60 FAX3 data syntax

MSISDN CC 1 to 3 digits, first digit cannot be
zero
FAX3 field descriptions are provided in the following table.
Table 61 FAX3 field descriptions
6.22.2 Interactions
FAX3 interacts with all other basic services, all BSG supplementary services, and system Table
• ALTSPFAX is mutually exclusive with FAX3


SMMO/SMMT/CDA1275, do not datafill FAX3’s BCI. There is an exception:
FAX3/CDA/CDS can share an MSISDN, and one of them can have a BCI (refers to
CDA/CDS basic services, not BSGs).
GHLRBCA, and the value in the system table’s BSVC field must be FAX3.
• FAX3 belongs to the FAX BSG; at least one basic service from the FAX BSG must be
provisioned if any BSG-SS is registered against FAX (services BAIC, BICRoam, BAOC,

6.23 Short Message Mobile Originating

Short Message Mobile Originating (SMMO) datafill defines the MSISDN and bearer capability for SMMO.
SMMO belongs to the SMS basic service group (BSG).
6.23.1 Datafill
SMMO data syntax is detailed in the following table. The three MSISDN fields are combined to give the
Table 62 SMMO data syntax

SMMO field descriptions are provided in the following table.
Table 63 SMMO field descriptions

6.23.2 Interactions
SMMO interacts with all other basic services and all BSG supplementary services, as follows:
• TPHNY, SMMO, and SMMT must have the same MSISDN. If the MSISDN of SMMO is

changed, then the other two are automatically updated to match.

• SMMO belongs to the SMS BSG; at least one basic service from the SMS BSG must be
provisioned if any BSG-SS is registered against SMS (services BAIC, BICRoam, BAOC,

6.24 Short Message Mobile Terminating

Short Message Mobile Terminating (SMMT) datafill defines the MSISDN and bearer capability for SMMT.
SMMT belongs to the SMS basic service group (BSG).
6.24.1 Datafill
SMMT data syntax is detailed in the following table. The three MSISDN fields are combined to give the
Table 64 SMMT data syntax


SMMT field descriptions are provided in the following table.
Table 65 SMMT field descriptions

6.24.2 Interactions
SMMT interacts with all other basic services and all BSG supplementary services, as follows:
• TPHNY, SMMO, and SMMT must have the same MSISDN. If the MSISDN of SMMO is

• SMMT belongs to the SMS BSG; at least one basic service from the SMS BSG must be
provisioned if any BSG-SS is registered against SMS (services BAIC, BICRoam, BAOC,

6.25 Speech followed by CDA data

Speech followed by CDA (SPCHCDA) datafill defines the MSISDN and bearer capability for speech
followed by CDA data. SPCHCDA belongs to the CDA basic service group (BSG).
6.25.1 Datafill
SPCHCDA data syntax is detailed in the following table. The three MSISDN fields are combined to give
the complete MSISDN (that is, CC + NDC + SN). The following intra-service validation applies.
Table 66 SPCHCDA data syntax

SPCHCDA field descriptions are provided in the following table.
Table 67 SPCHCDA field descriptions

6.25.2 Interactions
SPCHCDA interacts with all other basic services, all BSG supplementary services, and system Table
SMMO/SMMT/CDA1275/SPCHCDS, do not datafill SPCHCDA’s BCI.

GHLRBCA, and the value in the system table’s BSVC field must be SPCHCDA.
• SPCHCDA belongs to the CDA BSG; at least one basic service from the CDA BSG must
• When provisioning SPCHCDA, you must supply a BCI unless SPCHCDS is concurrently
• Upon provisioning SPCHCDA, SPCHCDS is automatically provisioned with the same
• SPCHCDA and SPCHCDS must have the same MSISDN. Upon changing the MSISDN of
one service, the other service’s MSISDN is automatically updated to match.
• One of SPCHCDA/SPCHCDS must have a BCI; the other must have a null BCI. Upon
• Upon deprovisioning SPCHCDA, SPCHCDS is automatically deprovisioned too.

6.26 Speech followed by CDS data

Speech followed by CDS (SPCHCDS) datafill defines the MSISDN and bearer capability for speech
followed by CDS data. SPCHCDS belongs to the CDS basic service group (BSG).
6.26.1 Datafill
SPCHCDS data syntax is detailed in the following table. The three MSISDN fields are combined to give
the complete MSISDN (that is, CC + NDC + SN). The following intra-service validation applies.
Table 68 SPCHCDS data syntax

SPCHCDS field descriptions are provided in the following table.


Table 69 SPCHCDS field descriptions
6.26.2 Interactions
SPCHCDS interacts with all other basic services, all BSG supplementary services, and system Table
SMMO/SMMT/CDA1275/SPCHCDA, do not datafill SPCHCDS’s BCI.
GHLRBCA, and the value in the system table’s BSVC field must be SPCHCDS.
• SPCHCDS belongs to the CDA BSG; at least one basic service from the CDA BSG must
• When provisioning SPCHCDS, you must supply a BCI unless SPCHCDA is concurrently
• Upon provisioning SPCHCDS, SPCHCDA is automatically provisioned with the same
• SPCHCDS and SPCHCDA must have the same MSISDN. Upon changing the MSISDN of
one service, the other service’s MSISDN is automatically updated to match.
• One of SPCHCDS/SPCHCDA must have a BCI; the other must have a null BCI. Upon
• Upon deprovisioning SPCHCDS, SPCHCDA is automatically deprovisioned too.

6.27 Telephony
Telephony (TPHNY) datafill defines the MSISDN and bearer capability for voice calls. TPHNY belongs to
the SPCH basic service group (BSG).
6.27.1 Datafill
TPHNY data syntax is detailed in the following table. The three MSISDN fields are combined to give the

Table 70 TPHNY data syntax


TPHNY field descriptions are provided in the following table.
Table 71 TPHNY field descriptions

6.27.2 Interactions
TPHNY interacts with all other basic services, all BSG supplementary services, and system Table
• TPHNY must be provisioned for AUXTPHNY to be provisioned.

• TPHNY, SMMO, and SMMT must have the same MSISDN. If the MSISDN of TPHNY is
• If the MSISDN matches the MSISDN for any other basic service except
SMMO/SMMT/CDA1275, do not datafill TPHNY’s BCI.
• If datafilled, the BCI must be an entry from the BCAKEY field of system Table GHLRBCA,
and the value in the system table’s BSVC field must be TPHNY.
• TPHNY must be provisioned if any BSG-SS is registered against SPCH (services BAIC,
BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW, and
EXT).

6.28 Voice Broadcast Service

Voice Broadcast Service (VBS) belongs to the voice group services (VGS) basic service group (BSG).

VGS basic services have different datafill than all other basic services. VBS datafill defines groups that
the subscriber belongs to for VBS functionality.
6.28.1 Datafill
VBS data syntax is detailed in the following table. The following intra-service validations apply:
• All datafill is optional; however, if you datafill "Functions outside HPLMN," then you must
datafill at least one Group. (Similarly, if at least one Group is datafilled, then datafill
"Functions outside HPLMN.")
• Duplicate IDs are not allowed in the "Groups Vector."
Table 72 VBS data syntax

Functions outside HPLMN Boolean Optional
Groups Vector (0 - 50) composed of the two All 50 are optional.

dataitems below
3 digits as above
– ID
Boolean as above
– Origination Entitlement
VBS field descriptions are provided in the following table.
Table 73 VBS field descriptions
Functions outside HPLMN shows whether subscriber can use VBS when roaming out of the
HPLMN
Groups Vector (0 -50) vector of groups
a group ID
– ID
shows whether the subscriber can originate calls to this
– Origination Entitlement
group
6.28.2 Interactions
None
6.29 Voice Group Call Service

Voice Group Call Service (VGCS) belongs to the voice group services (VGS), basic service group (BSG).
VGS basic services have a different datafill than all other basic services. VGCS datafill defines groups
that the subscriber belongs to for VBS functionality.
6.29.1 Datafill
The VGCS data syntax is detailed in the following table. The following intra-service validations apply:

• All datafill is optional; however, if you datafill "Functions outside HPLMN," then you must
datafill at least one "Group." (Similarly, if at least one Group is datafilled, then datafill
"Functions outside HPLMN.")
• Duplicate IDs are not allowed in the Groups vector.
Table 74 VGCS data syntax

Functions outside HPLMN Boolean Optional
Group IDs Vector (0 -50) 3 digits All 50 are optional.
VGCS field descriptions are provided in the following table.
Table 75 VGCS field descriptions
Functions outside HPLMN shows whether subscriber can use VBS when roaming out of
the HPLMN
Group ID a group ID
6.29.2 Interactions
None

7 Supplementary services
Supplementary Services (SS) modify or enhance basic services. Each SS only applies to certain basic
service groups (BSG). There are two major SS groups: IMSI-based and BSG-based. IMSI-based services
have a datafill that applies to all the basic service groups that they apply to. BSG-based services have a
datafill specific to each basic service group that they apply to.
7.1 Navigation
• “Supplementary services groups” on page 72
• “Accounting Codes” on page 74
• “Anonymous Call Rejection” on page 74
• “Advice of Charge Charging” on page 75
• “Advice of Charge Information” on page 75
• “Barring of All Incoming Calls” on page 75
• “Barring of All Outgoing Calls” on page 77
• “Barring of Incoming Calls when Roaming outside HPLMN country” on page 78
• “Barring of Outgoing International Calls” on page 79
• “Barring of Outgoing International Calls except to HPLMN Country” on page 81
• “Call Forward when Busy” on page 82
• “Call Forward when Not Reachable” on page 87
• “Call Forward when No Reply” on page 92
• “Call Forward Unconditionally” on page 98
• “Calling Line ID Presentation” on page 103
• “Calling Line ID Restriction” on page 103
• “Calling Name Delivery” on page 104
• “Connected Line ID Presentation” on page 104
• “Connected Line ID Restriction” on page 105
• “Class of Service” on page 105
• “Closed User Groups” on page 107
• “Closed User Groups Subscription” on page 107
• “Closed User Groups Feature” on page 108
• “Customized Ring Back Tone” on page 110
• “Call Waiting” on page 111
• “Explicit Call Transfer” on page 112
• “Enhanced Multi Level Precedence and Pre-emption” on page 112
• “Extension Services” on page 113
• “Follow Me” on page 118
• “Call Hold” on page 119
• “Hot Billing” on page 119

• “Local Calls Only” on page 120

• “Malicious Call Trace” on page 120
• “Multiparty” on page 121
• “User to User Signaling stage 1” on page 121
• “Wireless Priority Service” on page 121
7.2 Supplementary services groups

BSG-SSs have registration sets, with each set having registered/activated /suppression states.
Suppression states are temporary/changeable data that are the result of interactions between the
subscribers services and location and are therefore not part of the subscriber profile. IMSI-SSs do not
have registration sets; they simply have a provisioned state.
The HLR supports the supplementary services listed in the following table. The Group column provides
the SS group type as used in the specifications. A proprietary service does not belong to one of these
groups and is marked as such. The Closed User Group (CUG) has two separate types of datafill: CUG
Feature data and CUG Subscription data.
Table 76 Supplementary services
Short name Expanded name Group Type See section

ACC Accounting Codes Proprietary IMSI “Accounting Codes” on
page 74
ACRJ Anonymous Call Proprietary IMSI “Anonymous Call
Rejection Rejection” on page 74
AOCC Advice of Charge Charging (TS IMSI “Advice of Charge
Charging 22.004/22.086) Charging” on page 75
AOCI Advice of Charge Charging (TS IMSI “Advice of Charge
Information 22.004/22.086) Information” on page 75
BAIC Barring of all Incoming Barring (TS BSG “Barring of All Incoming
Calls 22.004/22.088) Calls” on page 75
BAOC Barring of all Outgoing Barring (TS BSG “Barring of All Outgoing
Calls 22.004/22.088) Calls” on page 77
BICRoam Barring of all Incoming Barring (TS BSG “Barring of Incoming Calls
Calls when Roaming 22.004/22.088) when Roaming outside
outside HPLMN HPLMN country” on
country page 78
BOIC Barring of Outgoing Barring (TS BSG “Barring of Outgoing
International Calls 22.004/22.088) International Calls” on
page 79
BOICexHC Barring of Outgoing Barring (TS BSG “Barring of Outgoing
International Calls 22.004/22.088) International Calls except
except to HPLMN to HPLMN Country” on
Country page 81
CFB Call Forward when Forwarding (TS BSG “Call Forward when Busy”
Busy 22.004/22.082 Call on page 82
Offering SS)
CFNRc Call Forward when Not Forwarding BSG “Call Forward when Not

Reachable (TS Reachable” on page 87

22.004/22.082 Call
Offering SS)
CFNRy Call Forward when No Forwarding (TS BSG “Call Forward when No
Reply 22.004/22.082 Call Reply” on page 92
Offering SS)
CFU Call Forward Forwarding (TS BSG “Call Forward
Unconditional ly 22.004/22.082 Call Unconditionally” on
Offering SS) page 98
CLIP Calling Line ID Line Identification IMSI “Calling Line ID
Presentation (TS 22.004/22.081 Presentation” on page 103
Num Id.)
CLIR Calling Line ID Line Identification IMSI “Calling Line ID
Restriction (TS 22.004/22.081 Restriction” on page 103
Num Id.)
CNAM Calling Name Delivery Proprietary IMSI “Calling Name Delivery”
on page 104
COLP Connected Line ID Line Identification IMSI “Connected Line ID
Presentation (TS 22.004/22.081 Presentation” on page 104
Num Id.)
COLR Connected Line ID Line Identification IMSI “Connected Line ID
Restriction (TS 22.004/22.081 Restriction” on page 105
Num Id.)
COS Class Of Service Proprietary BSG “Class of Service” on
page 105
CRBT Customized Ring Back Proprietary IMSI “Customized Ring Back
Tone Tone” on page 110
CUG Closed User Groups Community of BSG “Closed User Groups” on
Interest (TS page 107
22.004/22.087)
CW Call Waiting Call Completion (T BSG “Call Waiting” on
S 22.004/22.083) page 111
ECT Explicit Call Transfer Call Offering (TS IMSI “Explicit Call Transfer” on
22.004/22.091) page 112
EMLPP Enhanced Multi Level Call Priority (spec IMSI “Enhanced Multi Level
Precedence -Pre- TS22.0004/22.072 Precedence and Pre-
emption ) emption” on page 112
EXT Extension Services Proprietary BSG “Extension Services” on

page 113
FM Follow Me Follow Me IMSI “Follow Me” on page 118
HOLD Call Hold Call Completion (T IMSI “Call Hold” on page 119
S 22.004/22.083)
HOTBILL Hot Billing Proprietary IMSI “Hot Billing” on page 119


LCO Local Calls Only Proprietary IMSI “Local Calls Only” on

page 120
MCT Malicious Call Trace Proprietary IMSI “Malicious Call Trace” on
page 120
MPTY Multi-Party MultiParty (TS IMSI “Multiparty” on page 121
22.004/22.084)
UUS1 User to User Signaling Additional Info IMSI “User to User Signaling
stage 1 Transfer (TS stage 1” on page 121
22.004/22.087)
WPS Wireless Priority Call Priority IMSI “Wireless Priority Service”
Service on page 121
7.3 Accounting Codes

Accounting Codes (ACC) datafill defines the verification of the account code entered by the subscriber
when originating a call. ACC is an Kapsch-proprietary IMSI-SS and applies to all BSGs except VGS.
7.3.1 Datafill
ACC data syntax is detailed in the following table. The following intra-service interactions apply.
Datafill "Verification Length" if the "Option" is set to VER. Do not datafill "Verification Length" for other
Options.
Table 77 ACC data syntax

Option {VER, NONVER, VOL}
Verification Length number: 1 -16 Optional
ACC field descriptions are provided in the following table.
Table 78 ACC field descriptions
Option verification of the account code option: verified (VER), non-
verified (NONVER), voluntary (VOL)
Verification Length the valid length of the account code (only used with the
verified option)
7.3.2 Interactions
None
7.4 Anonymous Call Rejection

Provisioning Anonymous Call Rejection (ACRJ) enables anonymous call reject functionality for the

subscriber. ACRJ rejects anonymous calls, that is, those where its calling line identification number
presentation is set to restricted. ACRJ is an Kapsch-proprietary IMSI-SS and applies to all BSGs except
SMS and VGS.
7.4.1 Datafill
ACRJ has no dataitems; it is simply provisioned or deprovisioned.
7.4.2 Interactions
ACRJ interacts with CLIP.
For ACRJ to be provisioned, CLIP must be provisioned and have its Override dataitem set to FALSE.
7.5 Advice of Charge Charging

Provisioning Advice of Charge Charging (AOCC) enables advice of charge charging functionality for the
subscriber. (AOCC allows a subscriber to request charging information; calls are not allowed if this
information is not available.) AOCC is an IMSI-SS and applies to all BSGs except SMS and VGS.
7.5.1 Datafill
AOCC has no dataitems; it is simply provisioned or deprovisioned.
7.5.2 Interactions
AOCC interacts with AOCI.
AOCC and AOCI are mutually exclusive.
7.6 Advice of Charge Information

Provisioning Advice of Charge Information (AOCI) enables advice of charge information functionality for
the subscriber. (AOCI allows a subscriber to request charging information; calls are allowed if this
information is not available.) AOCI is an IMSI-SS and applies to all BSGs except SMS and VGS.
7.6.1 Datafill
AOCI has no dataitems; it is simply provisioned or deprovisioned.
7.6.2 Interactions
AOCI interacts with AOCC.
AOCI and AOCC are mutually exclusive.
7.7 Barring of All Incoming Calls

Barring of All Incoming Calls (BAIC) prevents the User Equipment from receiving any incoming calls for
all BSGs datafilled against this service.
BAIC is a supplementary service based on a basic service group (BSG-SS).
7.7.1 Datafill
BAIC data syntax is detailed in the following table. Each of the registration sets is optional.

Table 79 BAIC data syntax

SPCH Reg Set Activated Boolean
AUXSPCH Reg Set Activated Boolean
SMS Reg Set Activated Boolean
CDA Reg Set Activated Boolean
CDS Reg Set Activated Boolean
FAX Reg Set Activated Boolean
BAIC field descriptions are provided in the following table.
Table 80 BAIC field descriptions
SPCH Reg Set Activated indicates whether the SPCH registration is activated
AUXSPCH Reg Set Activated indicates whether the AUXSPCH registration is

activated
SMS Reg Set Activated indicates whether the SMS registration is activated
CDA Reg Set Activated indicates whether the CDA registration is activated
CDS Reg Set Activated indicates whether the CDS registration is activated
FAX Reg Set Activated indicates whether the FAX registration is activated
7.7.2 Interactions
BAIC interacts with all basic services (except VBS and VGCS), all call forwards (CFB, CFNRc, CFNRy,
CFU), and BICRoam, as follows:
• For each registration set provisioned, provision the BSG (interacts with all basic services
except VBS and VGCS).
• Interactions with BSG-SSs are given in the following table. These interactions apply to
each BSG registration set (and where the interaction is with a BSG-SS, the interaction is
with the corresponding BSG in the interacting service). These interactions only apply to
activated BSG registrations.
Table 81 BAIC registration set interactions
Validate Against Interaction

Service State
CFU Reg Set Activated BAIC and CFU are mutually exclusive for each reg set,
unless the subscriber has Translations Information Flag
(TIF)-Forwarded-to Numbers (FTN), in which case there is
no interaction. See “Determining FTN type” on page 87.

CFB Reg Set Activated BAIC and CFB are mutually exclusive for each reg set,
unless the subscriber has TIF-FTNs, in which case there is
no interaction “Determining FTN type” on page 87.
CFNRc Reg Set Activated BAIC and CFNRc are mutually exclusive for each reg set,
CFNRy Reg Set Activated BAIC and CFNRy are mutually exclusive for each reg set,
BICRoam Reg Set Activated The BICRoam reg set is deregistered.
7.8 Barring of All Outgoing Calls

Barring of All Outgoing Calls (BAOC) is a supplementary service based on a basic service group (BSG-
SS), with its datafill defining which BSGs (supported by the service) are barred for outgoing calls.
7.8.1 Datafill
BAOC data syntax is detailed in the following table. Each of the registration sets is optional.
Table 82 BAOC data syntax
Dataitem Syntax
VGS Reg Set Activated Boolean
BAOC field descriptions are provided in the following table.
Table 83 BAOC field descriptions
activated
VGS Reg Set Activated indicates whether the VGS registration is activated

7.8.2 Interactions
BAOC interacts with all basic services, all call forwards (CFB, CFNRc, CFNRy, CFU), BOIC, and
BOICexHC, as follows:
• For each registration set provisioned, provision the BSG (because it interacts with all basic
services).
• Interactions with BSG-SSs are provided in the following table. These interactions apply to
each BSG registration set. (Where the interaction is with a BSG-SS, the interaction is with
the corresponding BSG in the interacting service.) These interactions only apply to activated
BSG registrations.
Table 84 BAIC registration set interactions

Service State
CFU Reg Set Activated BAOC and CFU are mutually exclusive for each reg set, unless
the subscriber has TIF-FTNs, in which case there is no
interaction. See “Determining FTN type” on page 87.
CFB Reg Set Activated BAOC and CFB are mutually exclusive for each reg set, unless
CFNRc Reg Set Activated BAOC and CFNRc are mutually exclusive for each reg set, unless
CFNRy Reg Set Activated BAOC and CFNRy are mutually exclusive for each reg set, unless
BOIC Reg Set Activated The BOIC reg set is deregistered.

BOICexHC Reg Set Activated The BOICexHC reg set is deregistered.
7.9 Barring of Incoming Calls when Roaming outside HPLMN country

Barring of Incoming Calls when Roaming outside HPLMN country (BICRoam) is a supplementary service
based on a basic service group (BSG-SS), with its datafill defining which BSGs (supported by the service)
are barred for incoming calls when the subscriber is roaming outside the HPLMN country.
7.9.1 Datafill
The BICRoam data syntax is detailed in the following table. Each of the registration sets is optional.
Table 85 BICRoam data syntax
Dataitem Syntax


BICRoam field descriptions are provided in the following table.
Table 86 BICRoam field descriptions

activated
7.9.2 Interactions
BICRoam interacts with all basic services (except VBS and VGCS) and BAIC, as follows:
• Interactions with BSG-SSs are provided in the following table. These interactions apply to
each BSG registration set. (Where the interaction is with a BSG-SS, the interaction is with
the corresponding BSG in the interacting service.) These interactions only apply to
Table 87 BICRoam registration set interactions

Service State
BAIC Reg Set Activated The BAIC reg set is

deregistered unless BAIC is
registered in the current
transaction, in which case
the BICRoam reg set is
deregistered.
7.10 Barring of Outgoing International Calls

Barring of Outgoing International Calls (BOIC) is a supplementary service based on a basic service group
(BSG-SS), with its datafill defining which BSGs (supported by the service) are barred for outgoing

international calls.
7.10.1 Datafill
BOIC data syntax is detailed in the following table. Each of the registration sets is optional.
Table 88 BOIC data syntax
Dataitem Syntax
BOIC field descriptions are provided in the following table.
Table 89 BOIC field descriptions
activated
7.10.2 Interactions
BOIC interacts with all basic services (except VBS and VGCS), CFU, BAOC, BOICexHC, and system
Table GHLRPCC, as follows:
except VBS and VGCS)
• The following table shows interactions with BSG-SSs. These interactions apply to each
BSG registration set. Where the interaction is with a BSG-SS, the interaction is with the
corresponding BSG in the interacting service. These interactions only apply to activated
BSG registrations.

Table 90 BOIC registration set interactions

Service State
CFU Reg Set Activated BOIC and CFU are mutually exclusive for each reg
set if the subscriber has GSM-FTNs. See
“Determining FTN type” on page 87. BOIC and
CFU are mutually exclusive for each reg set if the
CFU FTN is international with respect to the
HPLMN Country. See “Determining if an FTN is
international with respect to HPLMN country”
on page 92. This requires system Table
GHLRPCC.
BAOC Reg Set Activated The BAOC reg set is deregistered unless BAOC is
registered in the current transaction, in which case
the BOIC reg set is deregistered
BOICexHC Reg Set Activated The BOICexHC reg set is deregistered
7.11 Barring of Outgoing International Calls except to HPLMN Country

Barring of Outgoing International Calls except to HPLMN Country (BOICexHC) is a supplementary
service based on a basic service group (BSG-SS), with its datafill defining which BSGs (supported by the
service) are barred for outgoing international calls, except those to the HPLMN country.
7.11.1 Datafill
BOICexHC data syntax is detailed in the following table. Each of the registration sets is optional.
Table 91 BOICexHC data syntax
Dataitem Syntax
BOICexHC field descriptions are provided in the following table.


Table 92 BOICexHC field descriptions
AUXSPCH Reg Set Activated indicates whether the AUXSPCH registration is activated
7.11.2 Interactions
BOICexHC interacts with all basic services (except VBS and VGCS ), CFU, BAOC, BOIC, and system
Table GHLRPCC, as follows:
• The following table shows the interactions with BSG-SSs. These interactions apply to
each BSG registration set. Where the interaction is with a BSG-SS, the interaction is with
the corresponding BSG in the interacting service. These interactions only apply to
Table 93 BOICexHC registration set interactions

Service State
CFU Reg Set BOICexHC and CFU are mutually exclusive for each reg set if
Activated the subscriber has GSM-FTNs. See “Determining FTN type”
on page 87. BOICexHC and CFU are mutually exclusive for
each reg set if the CFU FTN is international with respect to the
HPLMN Country. See “Determining if an FTN is
international with respect to HPLMN country” on page
102 This requires system Table GHLRPCC.
BAOC Reg Set The BAOC reg set is deregistered unless BAOC is registered
Activated in the current transaction, in which case the BOIC reg set is
deregistered
BOIC Reg Set The BOIC reg set is deregistered unless BOIC is registered in
Activated the current transaction, in which case the BOICexHC reg set is
deregistered
7.12 Call Forward when Busy

Call Forward when Busy (CFB) is a supplementary service based on a basic service group (BSG-SS). It
allows you to datafill Forward to Numbers (FTNs) for call forwarding when busy against the BSGs that the
service supports.

7.12.1 Datafill
Table 94 CFB data syntax on page 83 details the CFB data syntax. Each of the registration sets is
optional.
The validation of CFB is complex due to its interaction with ESMR LCO translations. If these translations
are enabled, then CFB’s FTNs are passed through these translations to normalize the number (that is,
convert it to international E164 format) and to determine whether the number is "local." The syntax check-
ins apply to the post-translated number. The syntax check for pre-translated FTNs is that they contain 1
to 15 digits (with no restriction on the first digit). The "local" indication is required in the CFB’s interaction
with LCO service.
If ESMR LCO translations are not enabled, then no translations occur and the FTN defaults to being "not
local."
7.12.1.1 Meaning of ESMR LCO

There is a particular type of translation used to normalize DNs and determine whether they are
local or not. They are enabled on the HLR if key 1021 is datafilled in system Table XLAENTRY,
and there is a datafill for associated translations tables. The term "ESMR" is used due to these
translations being particularly used in the North American market.
Table 94 CFB data syntax

NCP {NONF, NF, NFWN}
NFP {NONF, NF, NFWN}
DCF ID 1 -20 characters Yes
NOA {UNKN, INTL, NTL, NTWK, SUBS,
ABBR}
NPI {UNKN, E164, X121, F69, E212,
NATL, PRIV}
FTN 1 to 15 digits
AUXSPCH Reg Activated Boolean
Set
ABBR}
NPI {UNKN, E164, X121, F69, E212,
NATL, PRIV}
FTN 1 to 15 digits
ABBR}
NPI {UNKN, E164, X121, F69, E212,
NATL, PRIV}
FTN 1 to 15 digits

ABBR}
NPI {UNKN, E164, X121, F69, E212,
NATL, PRIV}
FTN 1 to 15 digits
ABBR}
NPI {UNKN, E164, X121, F69, E212,
NATL, PRIV}
FTN 1 to 15 digits
CFB field descriptions are provided in the following table.
Table 95 CFB field descriptions
NCP Notify Calling Party option: No-notification (NONF),
Notification (NF), Notification-with-number (NFWN)
NFP Notify Forwarding Party option: No-notification (NONF),

DCF ID Default Call Forwarding ID, defined in system Table

GHLRDCF
NOA the FTN Nature Of Address for the SPCH registration;

options are
• Unknown (UNKN)
• International-number (INTL)
• National-significant-number (NTL)
• Network-specific-number (NTWK)
• Subscriber-number (SUBS)
• Abbreviated-number (ABBR)
NPI the FTN Number Plan Indicator for the SPCH

registration; options are
• Unknown (UNKN)
• ISDN/telephony-numbering-plan (E164)
• Data-numbering-plan (X121)
• Telex-numbering-plan (F69)
• Land-mobile-numbering-plan (E212)
• National-numbering-plan (NATL)
• Private-numbering-plan (PRIV)
FTN the Forward To Number for the SPCH registration, also

known as the call forward number


activated
NOA the FTN Nature Of Address for the AUXSPCH

registration.For options, see SPCH Reg Set.
NPI the FTN Number Plan Indicator for the AUXSPCH

registration. For options, see SPCH Reg Set.
FTN the Forward To Number for the AUXSPCH registration,

also known as the call forward number
NOA the FTN Nature Of Address for the CDA registration.

For options, see SPCH Reg Set.
NPI the FTN Number Plan Indicator for the CDA

FTN the Forward To Number for the CDA registration, also

NOA the FTN Nature Of Address for the CDS registration.

NPI the FTN Number Plan Indicator for the CDS

FTN the Forward To Number for the CDS registration also

NOA the FTN Nature Of Address for the FAX registration.

NPI the FTN Number Plan Indicator for the FAX

FTN the Forward To Number for the FAX registration also

7.12.2 Interactions
CFB interacts with all basic services (except VBS and VGCS), BAOC, BAIC, CFU, LCO, ODB BAIC, ODB
BAOC, ODB PremRate categories, O-CSI, and system tables GHLRDCF and GHLRODB. CFB’s
interactions are identical to those of CFNRc and CFNRy, as follows:
• If the DCF ID is datafilled, it must be an entry from the DCFID field of system Table
GHLRDCF, and the FTNCHECK field must match the subscriber’s FTN type. Matching
depends on O-CSI; See “Determining FTN type” on page 87.
• For each registration set provisioned, provision the BSG. (It interacts with all basic services
except SMMO, SMMT, VBS and VGCS.)

• None of the FTNs must match any of the subscriber’s basic service MSISDNs (interacts
with all basic services except VBS and VGCS).
• The FTN format and NOA/NPI combination is checked against the subscriber’s FTN-type
(interacts with O-CSI). See “Determining FTN type” on page 87.
– GSM-FTNs: the length must be 4 to 15 digits, and the first digit must not be zero; NOA
must be INTL, and NPI must be E164.
– Custom-FTNs: length must be 1 to 15 digits; NOA must be UNKN, and NPI must be
UNKN.
– IF-FTNs: the length must be 1 to 15 digits; NOA and NPI can take any values.
However, if NOA/NPI is INTL/E164, then additional checks apply to the FTN format:
must be 4 to 15 digits and the first digit must not be zero.
• The following table shows interactions with BSG-SSs and ODBs. These interactions apply
to each BSG registration set and where the interaction is with a BSG-SS, the interaction is
with the corresponding BSG in the interacting service. These interactions only apply to
Table 96 CFB registration set interactions
Validate against Interaction

Service State
BAIC Reg Set Activated CFB and BAIC are mutually exclusive for each reg set
unless the subscriber has TIF FTNs (see “Determining
FTN type” on page 87), in which case there is no
interaction.
BAOC Reg Set Activated CFB and BAOC are mutually exclusive for each reg set
interaction.
CFU Reg Set Activated CFB cannot be newly registered after CFU has been
registered.
LCO Provisioned CFB and LCO are mutually exclusive if (1) the subscriber
has GSM FTNs (see “Determining FTN type” on page
87) and (2) any CFB FTN is not local.
ODB BAIC Provisioned CFB cannot be newly registered after ODB BAIC has been
provisioned, unless the subscriber has TIF FTNs (see
“Determining FTN type” on page 87), in which case
there is no interaction.
ODB BAOC Provisioned CFB cannot be newly registered after ODB BAOC has
been provisioned, unless the subscriber has TIF FTNs
(see “Determining FTN type” on page 87), in which
case there is no interaction.
ODB Prem Provisioned CFB cannot be newly registered after ODB Prem Rate
Rate (Ent or Info) is provisioned if (1) the subscriber has GSM
categories FTNs and (2) the FTN is barred according to its lookup in
system Table GHRLODB.
FTN type determination is discussed in “Determining FTN type” on page 87.

7.12.3 Determining FTN type

A subscriber can have GSM-FTNs, TIF-FTNs, or Custom-FTNs. If the subscriber does not have O-CSI
provisioned, then they have GSM-FTNs. If the subscriber does have O-CSI provisioned, then its FTN type
is determined by the FTN Checks field. The field can be set to GSM, TIF, or Custom. Therefore, for
instance, a TIF-FTNs subscriber has O-CSI provisioned, with FTN Checks set to TIF.
7.12.4 Determining if an FTN is international with respect to HPLMN country

Whether an FTN is international with respect to the HPLMN Country is important in some interactions with
CFB. Take the following steps:
• Determine the subscriber’s primary MSISDN (requires all basic services except VBS and
VGCS).
• Map the primary MSISDN CC to a Pseudo Country Code (PCC) by doing a lookup in the
TO/FROM fields of system Table GHLRPCC.
• Map the CFB FTN to a PCC by doing a lookup in the TO/FROM fields of system Table
GHLRPCC.
• If either number does not map to a PCC then it is a translations error, and the datafill is
not valid.
• Compare the two PCCs. The FTN is international with respect to the HPLMN Country if
they differ.
7.12.5 DCF ID activation state determination

The DCF ID has an "activation" state, but it is not provisionable and is only determined on demand (for
example, when a MAP message to the HLR requests it). It is, therefore, strictly speaking, not part of the
subscriber profile. For information only, here are the details of the DCF activation state:
• For non-TIF-FTN subscribers, DCF is deactivated if the subscriber has BAOC or BAIC.
DCF is suppressed if the subscriber has BICRoam (act/not sup), ODB BAOC, ODB
BAOCRoam (act), ODB BAIC or ODB BICRoam (act).
• If the subscriber has CFU, then DCF is always deactivated.
• For GSM-FTN subscribers, DCF is suppressed if the subscriber has LCO (ESMR or non-
ESMR), BOIC (act, number intl), BOICexHC (act, number intlexHC), ODB BOIC (number
intl), ODB BOICexHC (number intlexHC), ODB PremRate (number barred), or ODB
HPLMN Spec (act, number barred).
7.13 Call Forward when Not Reachable

Call Forward when Not Reachable (CFNRc) is a supplementary service based on a basic service group
(BSG-SS). It allows you to datafill Forward to Numbers (FTNs) for call forwarding when not reachable
(that is, the MS is detached, there is radio congestion, or there is no page response/temporarily
unavailable) against the BSGs that the service supports.
7.13.1 Datafill
CFNRc data syntax is detailed in the following table: Table 97 CFNRc data syntax on page 88. Each of
the registration sets is optional.
The validation of CFNRc is complex due to its interaction with ESMR LCO Translations. If these
translations are enabled, then CFNRc’s FTNs are passed through these translations to normalize the
number (that is, convert it to international E164 format) and to determine whether the number is "local."

The syntax checks apply to the post-translated number. The syntax check for pre-translated FTNs is that
they contain 1 to 15 digits (with no restriction on the first digit). The "local" indication is required in the
CFNRc’s interaction with LCO service.
local."

These are translations of a particular type that are used to normalize DNs and determine whether
they are local or not. They are enabled on the HLR if key 1021 is datafilled in system Table
XLAENTRY and there is a datafill for associated translations tables. The term "ESMR" is used due
to these translations being particularly used in the North American market.
Table 97 CFNRc data syntax

DCF ID 1 -20 characters Optional
NOA {UNKN, INTL, NTL, NTWK,

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

SUBS, ABBR}

NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits
CFNRc field descriptions are provided in the following table.
Table 98 CFNRc field descriptions

GHLRDCF

options are
• Unknown (UNKN)

• Unknown (UNKN)


activated













7.13.2 Interactions
CFNRc interacts with all basic services (except VBS and VGCS), BAOC, BAIC, CFU, LCO, ODB BAIC,
ODB BAOC, ODB PremRate categories, O-CSI, and system tables GHLRDCF and GHLRODB. CFNRc’s
interactions are identical to those of CFB and CFNRy, as follows:
GHLRDCF, and the FTNCHECK field must match the subscriber’s FTN type (depends on
O-CSI). See “Determining FTN type” on page 97.
except SMMO, SMMT, VBS, and VGCS).
– GSM-FTNs: the length must be 4 to 15 digits, and the first digit must not be zero;

NOA must be INTL, and NPI must be E164.

– Custom-FTNs: the length must be 1 to 15 digits; NOA must be UNKN, and NPI must
be UNKN.
– TIF-FTNs: the length must be 1 to 15 digits. NOA and NPI can take any values;
however, if NOA/NPI is INTL/E164, then additional checks apply to the FTN format:
Table 99 CFNRc registration set interactions

Service State
BAIC Reg Set Activated CFB and BAIC are mutually exclusive for each reg set,
interaction.
BAOC Reg Set Activated CFB and BAOC are mutually exclusive for each reg set,
interaction.
CFU Reg Set Activated CFB cannot be newly registered after CFU has been
registered.
LCO Provisioned CFB and LCO are mutually exclusive if (1) the subscriber
has GSM FTNs (see “Determining FTN type” on page
87) and (2) any CFB FTN is not local.
ODB BAIC Provisioned CFB cannot be newly registered after ODB BAIC has been
“Determining FTN type” on page 97), in which case there
is no interaction.
ODB BAOC Provisioned CFB cannot be newly registered after ODB BAOC has been
“Determining FTN type” on page 97), in which case there
is no interaction.
ODB Prem Rate Provisioned CFB cannot be newly registered after ODB Prem Rate (Ent
categories or Info) is provisioned if (1) the subscriber has GSM FTNs
and (2) the FTN is barred according to its lookup in system
Table GHRLODB.

A subscriber can have GSM-FTNs, TIF-FTNs or Custom-FTNs. If the subscriber does not have O-CSI
provisioned, then the subscriber has GSM-FTNs. If the subscriber does have O-CSI provisioned, then its
FTN type is determined by the FTN Checks field. The field can be set to GSM, TIF, or Custom. For


VGCS).
GHLRPCC.
• If either number does not map to a PCC, then it is a translations error and the datafill is not
valid.
• Compare the two PCCs. The FTN is international with respect to the HPLMN Country if they
differ.

example when a MAP message to the HLR requests it). It is strictly speaking, not part of the subscriber
profile. For information only, here are the details of the DCF activation state:
• For non-TIF-FTN subscribers, DCF is deactivated if the subscriber has BAOC or BAIC. DCF is
suppressed if the subscriber has BICRoam (act/not sup), ODB BAOC, ODB BAOCRoam (act),
ODB BAIC or ODB BICRoam (act).
• If the subscriber has CFU, then DCF is always deactivated.
• For GSM-FTN subscribers, DCF i s suppressed if the subscriber has LCO (ESMR or non-
ESMR), BOIC (act, number intl), BOICexHC (act, number intlexHC), ODB BOIC (number intl),
ODB BOICexHC (number intlexHC), ODB PremRate (number barred) or ODB HPLMN Spec
(act, number barred).
7.14 Call Forward when No Reply

Call Forward when No Reply (CFNRy) is a supplementary service based on a basic service group (BSG-
SS), allowing forward to numbers (FTNs) to be datafilled for call forwarding when no reply is received
within a specified time against the BSGs the service supports.
7.14.1 Datafill
CFNRy data syntax is detailed in the following table: Table 100 CFNRy data syntax on page 93. Each of
the registration sets is optional.
The validation of CFNRy is complex due to its interaction with ESMR LCO translations. If these
translations are enabled, then CFNRy’s FTNs are passed through these translations to normalize the
number (that is, convert it to international E164 format) and to determine whether the number is "local."
The syntax check-ins apply to the post-translated number. The syntax check for pre-translated FTNs is
that they contain 1 to 15 digits (with no restriction on the first digit). The "local" indication is required in the
CFNRy’s interaction with LCO service.

local."

These are a particular type of translations used to normalize DNs and determine whether they are
local or not. They are enabled on the HLR if key 1021 is datafilled in system Table XLAENTRY
Table 100 CFNRy data syntax

NFP {NONF, NF, NFWN}
DCF ID 1 -20 characters Optional

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits
No Reply Time number: 5 - 30 (must be a multiple

of 5)

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

of 5)

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

of 5)


SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

of 5)

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

of 5)
CFNRy field descriptions are provided in the following table.
Table 101 CFNRy field descriptions
NFP Notify Forwarding Party option: No-notification (NONF),
GHLRDCF
options are
• Unknown (UNKN)
• Unknown (UNKN)

No Reply the no-reply time for the SPCH registration
Time
activated
TIme
TIme
TIme
TIme

7.14.2 Interactions
CFNRy interacts with all basic services (except VBS and VGCS), BAOC, BAIC, CFU, LCO, ODB BAIC,
ODB BAOC, ODB PremRate categories, O-CSI, and system tables GHLRDCF and GHLRODB. CFNRy’s
interactions are identical to that of CFB and CFNRc, as follows:
GHLRDCF, and the FTNCHECK field must match the subscriber’s FTN type (depends on
O-CSI). See “Determining FTN type” on page 102.
(interacts with O-CSI. “Determining FTN type” on page 102.
– GSM-FTNs: the length must be 4 to 15 digits, and first digit must not be zero; NOA
must be INTL, and NPI must be E164.
be UNKN.
– TIF-FTNs: the length must be 1 to 15 digits; NOA and NPI can take any values,
however if NOA/NPI is INTL/E164, then additional checks apply to the FTN format:
• The following table shows the interactions with BSG-SSs and ODBs. These interactions
apply to each BSG registration set and where the interaction is with a BSG-SS, the
interaction is with the corresponding BSG in the interacting service. These interactions
only apply to activated BSG registrations.
Table 102 CFNRy registration set interactions

Service State
BAIC Reg Set Activated CFB and BAIC are mutually exclusive for each
reg set, unless the subscriber has TIF FTNs (see
“Determining FTN type” on page 102), in
which case there is no interaction.
BAOC Reg Set Activated CFB and BAOC are mutually exclusive for each
reg set, unless the subscriber has TIF FTNs (see
“Determining FTN type” on page 102), in
which case there is no interaction.
CFU Reg Set Activated CFB cannot be newly registered after CFU has
been registered.
LCO Provisioned CFB and LCO are mutually exclusive if (1) the
subscriber has GSM FTNs (see “Determining
FTN type” on page 102) and (2) any CFB FTN
is not local.
ODB BAIC Provisioned CFB cannot be newly registered after ODB BAIC
has been provisioned, unless the subscriber has
TIF FTNs (see “Determining FTN type” on
page 102), in which case there is no interaction.
ODB BAOC Provisioned CFB cannot be newly registered after ODB

BAOC has been provisioned, unless the

subscriber has TIF FTNs (see “Determining
FTN type” on page 102), in which case there
is no interaction.
ODB Prem Rate Provisioned CFB cannot be newly registered after ODB Prem
categories Rate (Ent or Info) is provisioned if (1) the
subscriber has GSM FTNs and (2) the FTN is
barred according to its lookup in system Table
GHRLODB.

provisioned, then the subscriber has GSM-FTNs. If the subscriber has O-CSI provisioned, then its FTN
type is determined by the FTN Checks field. The field can be set to GSM, TIF, or Custom. Therefore, for

VGCS).
GHLRPCC.
not valid.
they differ.

example, when a MAP message to the HLR requests it). It is therefore, strictly speaking, not part of the
subscriber profile. For information only, here are the details regarding the DCF activation state:
• For non-TIF-FTN subscribers, DCF is deactivated if the subscriber has BAOC or BAIC.
DCF is suppressed if the subscriber has:
– BICRoam (act/not sup)
– ODB BAOC
– ODB BAOCRoam (act)
– ODB BAIC
– ODB BICRoam (act)
• If the subscriber has CFU then DCF is always deactivated.

• For GSM-FTN subscribers, DCF is suppressed if the subscriber has:

– LCO (ESMR or non-ESMR)
– BOIC (act, number intl)
– BOICexHC (act, number intlexHC)
– ODB BOIC (number intl)
– ODB BOICexHC (number intlexHC)
– ODB PremRate (number barred)
– ODB HPLMN Spec (act, number barred)
7.15 Call Forward Unconditionally

Call Forward Unconditionally (CFU) is a supplementary service based on a basic service group (BSG-
SS), allowing forward-to numbers (FTNs) to be datafilled for call forwarding unconditionally against the
BSGs the service supports.
7.15.1 Datafill
CFU data syntax is detailed in the following table: Table 103 CFU data syntax on page 98. Each of the
registration sets is optional.
The validation of CFU is complicated by its interaction with ESMR LCO Translations. If these translations
are enabled, then CFU’s FTNs are passed through these translations to normalize the number (that is,
convert it to international E164 format) and to determine whether the number is "local." The syntax check-
ins apply to the post-translated number. The syntax check for pre-translated FTNs is that they contain 1
to 15 digits (with no restriction on the first digit). The "local" indication is required in the CFU’s interaction
with LCO service.
local."

local or not. They are enabled on the HLR if key 1021 is datafilled in system Table XLAENTRY
Table 103 CFU data syntax


SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits


SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits

SUBS, ABBR}
NPI {UNKN, E164, X121, F69, E212,

NATL, PRIV}
FTN 1 to 15 digits
CFU field descriptions are provided in the following table.
Table 104 CFU field descriptions
options are
• Unknown (UNKN)


• Unknown (UNKN)
activated
7.15.2 Interactions
CFU interacts with all basic services ( except VBS and VGCS ), BAOC, BOIC, BOICexHC, BAIC, LCO,
ODB BAIC, ODB BAOC, ODB BOIC, ODB BOICexHC, ODB PremRate categories, ODB HPLMN Specific
categories, O-CSI, and system Table GHLRODB, as follows:

• None of the FTNs must match any of the subscriber’s basic service MSISDNs. (It interacts
with all basic services except VBS and VGCS.)
• Check the FTN format and NOA/NPI combination against the subscriber’s FTN-type
– GSM-FTNs: the length must be 4 to 15 digits, and the first digit must not be zero;
NOA must be INTL, and NPI must be E164.
be UNKN.
– TIF-FTNs: the length must be 1 to 15 digits; NOA and NPI can take any values.
However. if NOA/NPI is INTL/E164, then additional checks apply to the FTN format:
• Follow Me (FM) and the Call Forwarding Unconditional (CFU) Supplementary Service are
mutually exclusive. That is,
– If Follow Me is registered with respect to a remote party, registration or activation of
Call forwarding unconditional by the remote party is rejected. The remote party will
be informed of this incompatibility.
– If Call forwarding unconditional is registered or active for the remote party,
registration of Follow Me is rejected. The initiating subscriber will be informed of this
incompatibility.
Table 105 CFU registration set interactions

Service State
BAIC Reg Set CFU and BAIC are mutually exclusive for each reg set,
Activated unless the subscriber has TIF FTNs, in which case there is
no interaction.
BAOC Reg Set CFU and BAOC are mutually exclusive for each reg set,
Activated unless the subscriber has TIF FTNs, in which case there is
no interaction.
BOIC Reg Set CFU and BOIC are mutually exclusive for each reg set if (1)
Activated the subscriber has GSM FTNs and (2) the FTN is
international with respect to HPLMN country.
BOICexHC Reg Set CFU and BOICexHC are mutually exclusive for each reg set
Activated if (1) the subscriber has GSM FTNs and (2) the FTN is
international with respect to HPLMN country.
LCO Provisioned CFU and LCO are mutually exclusive if (1) the subscriber
has GSM FTNs and (2) any CFU FTN is not local.

ODB BAIC Provisioned CFU cannot be newly registered after ODB BAIC has been
provisioned, unless the subscriber has TIF FTNs, in which
ODB BAOC Provisioned CFU cannot be newly registered after ODB BAOC has been
provisioned, unless the subscriber has TIF FTNs, in which
ODB BOIC Provisioned CFU cannot be newly registered after ODB BOIC has been
provisioned if (1) the subscriber has GSM FTNs and (2) the
FTN is international with respect to HPLMN country.
ODB BOICexHC Provisioned CFU cannot be newly registered after ODB BOIC has been
provisioned if (1) the subscriber has GSM FTNs and (2) the
FTN is international with respect to HPLMN country.
ODB Prem Rate Provisioned CFU cannot be newly registered after an ODB Premium
categories Rate category has been provisioned if (1) the subscriber
has GSM FTNs and (2) the FTN is barred for that
category#.
ODB HPLMN Provisioned CFU cannot be newly registered after an ODB HPLMN
Specific Specific category has been provisioned if (1) the subscriber
categories has GSM FTNs and (2) the FTN is barred for that
category#.
Determination of whether FTN is international with respect to the HPLMN country is discussed in
“Determining if an FTN is international with respect to HPLMN country” on page 102.
Determining whether an FTN is barred for an ODB Premium Rate/ODB HPLMN Specific
categories is done by means of a lookup in digilator system Table GHLRODB

provisioned, then they have GSM-FTNs. If the subscriber does have O-CSI provisioned, then its FTN type
is determined by the FTN Checks field. The field can be set to GSM, TIF, or Custom. Therefore, for

VGCS).
GHLRPCC.
not valid.
they differ.

7.16 Calling Line ID Presentation

Calling Line ID Presentation (CLIP) datafill defines whether a Calling Line Identity Restriction (CLIR) of
the calling party is overridden. CLIP is an IMSI-SS and applies to all BSGs except SMS.
7.16.1 Datafill
CLIP data syntax is detailed in the following table.
Table 106 CLIP data syntax

Override Boolean
CLIP field descriptions are provided in the following table.
Table 107 CLIP field descriptions
Override indicates whether CLIP override is in effect
7.16.2 Interactions
CLIP interacts with ACRJ, and office parameters GSM_CLIP_SUPPORTED and
GSM_CLIP_OVR_SUPPORTED, as follows:
• For ACRJ to be provisioned, CLIP must be provisioned and have "Override" set to
FALSE.
• CLIP can only be provisioned if office parameter GSM_CLIP_SUPPORTED (table
OFCSTD) is TRUE.
• "Override" can only be set to TRUE if office parameter GSM_CLIP_OVR_SUPPORTED
(table OFCSTD) is TRUE.
7.17 Calling Line ID Restriction

A Calling Line ID Restriction (CLIR) datafill defines the presentation mode to be used for CLI restriction.
CLIR is an IMSI-SS and applies to all BSGs except SMS.
7.17.1 Datafill
CLIR data syntax is detailed in the following table.
Table 108 CLIR data syntax

Presentation Mode {P, TRES, TNRES}
CLIR field descriptions are provided in the following table.


Table 109 CLIR field descriptions
Presentation presentation mode option:
Mode permanent-CLI-presentation-restricted (P),
temporary-CLI-presentation-restricted (TRES),
temporary-CLI-presentation-not-restricted (TNRES)
7.17.2 Interactions
CLIR interacts with the office parameter GSM_CLIR_SUPPORTED.
CLIR can only be provisioned if the office parameter GSM_CLIR_SUPP ORTED (table OFCSTD) is
TRUE.
7.18 Calling Name Delivery

Provisioning Calling Name Delivery (CNAM) enables Calling Name Delivery functionality for the
subscriber. CNAM allows the calling party’s name to be displayed on the terminator’s MS. CNAM is an
Kapsch-proprietary IMSI-SS and applies to all BSGs except SMS and VGS.
7.18.1 Datafill
CNAM has no dataitems; it is simply provisioned or deprovisioned.
7.18.2 Interactions
None
7.19 Connected Line ID Presentation

Connected Line ID Presentation (COLP) datafill specifies whether the COLR service on the connected
party is overridden. COLP is an IMSI-SS and applies to all BSGs except SMS.
7.19.1 Datafill
COLP data syntax is detailed in the following table.
Table 110 COLP data syntax

Override Boolean
COLP field descriptions are provided in the following table.
Table 111 COLP field descriptions
Override indicates whether COLP override is in effect

7.19.2 Interactions
None
7.20 Connected Line ID Restriction

Provisioning Connected Line ID Restriction (COLR) enables explicit connected line ID restriction
functionality for the subscriber. COLR is an IMSI-SS and applies to all BSGs except SMS.
7.20.1 Datafill
COLR has no dataitems; it is simply provisioned or deprovisioned.
7.20.2 Interactions
None
7.21 Class of Service

Class of Service (COS) is a supplementary service based on a basic service group (BSG-SS), allowing
class of service information to be datafilled against each BSG that is supported by the service. COS is an
Kapsch-proprietary service.
7.21.1 Datafill
COS data syntax is detailed in the following table. Each of the registration sets is optional.
Table 112 COS data syntax
Dataitem Syntax
Customer Group number: 0 -4095
NCOS number: 0 -255
NCOS number: 0 -255
NCOS number: 0 -255
NCOS number: 0 -255
NCOS number: 0 -255
COS field descriptions are provided in the following table.


Table 113 COS field descriptions
SPCH Reg Set Activated indicates whether the SPCH registration is
activated
Customer Group the customer group for the SPCH registration,

defined in system Table GSMCUST or
GSMNCOS
NCOS the network class of service for the SPCH

registration, defined in system Table
GSMNCOS
activated
Customer Group the customer group for the AUXSPCH

GSMCUST or GSMNCOS
NCOS the network class of service for the AUXSPCH

GSMNCOS
CDA Reg Set Activated indicates whether the CDA registration is
activated
Customer Group the customer group for the CDA registration,

GSMNCOS
NCOS the network class of service for the CDA

GSMNCOS
CDS Reg Set Activated indicates whether the CDS registration is
activated
Customer Group the customer group for the CDS registration,

GSMNCOS
NCOS the network class of service for the CDS

GSMNCOS
FAX Reg Set Activated indicates whether the FAX registration is
activated
Customer Group the customer group for the FAX registration,

GSMNCOS
NCOS the network class of service for the FAX

GSMNCOS

7.21.2 Interactions
COS interacts with all basic services (except SMMO, SMMT, VBS, and VGCS) and system tables
GSMCUST and GSMNCOS, as follows:
• For each registration set provisioned, the BSG must be provisioned (interacts with all
basic services except SMMO, SMMT, VBS, and VGCS).
• For each registration set, if NCOS is datafilled, then Customer Group and NCOS
combined must be an entry from column GSM_NCOS_KEY of system Table GSMNCOS.
• For each registration set, if NCOS is not datafilled, then Customer Group must be an entry
from the GSMCUST_GRP_KEY column of system Table GSMCUST.
7.22 Closed User Groups

Closed User Groups (CUG) is a supplementary service based on a basic service group (BSG-SS),
allowing closed user group information to be datafilled against the BSGs that are supported by the
service.
CUG is unusual in that it has two separate groups of datafill. One group is mandatory, and is called CUG
Subscription; the other is optional, called CUG Feature.
CUG Subscription is detailed in “Closed User Groups Subscription” on page 107.
CUG Feature is detailed in “Closed User Groups Feature” on page 108.
7.23 Closed User Groups Subscription

Closed User Groups (CUG) is a basic service group based supplementary service (BSG-SS), that allows
closed user groups information to be datafilled against the BSGs that are supported by the service.
CUG Subscription is mandatory CUG data, whereas CUG Feature is optional CUG data. See “Closed
User Groups Feature” on page 108.
7.23.1 Datafill
CUG Subscription data syntax is detailed in the following table. The following intra-service validations
apply:
• Each Interlocks must be unique for each subscriber.

• Each CUG Index must be unique for each subscriber.
Table 114 CUG Subscription data syntax

Subscription Dataset vector composed of the following 9 are optional
(1 -10) ten dataitems
- Network ID number: 0 -9999
- Interlock number: 0 -65535
- CUG Index number: 0 -32767
- IntraCUG Restrictions {ICB,OCB} Optional
- SPCH Reg Boolean

- AUXSPCH Reg Boolean

- FAX Reg Boolean
- CDA Reg Boolean
- CDS Reg Boolean
- All BSG Reg Boolean
CUG Subscription field descriptions are provided in the following table.
Table 115 CUG Subscription field descriptions
Subscription Dataset vector a CUG subscription dataset, composed of the dataitems that
(1 -10) follow
- Network ID network identity
- Interlock interlock code
- CUG Index CUG index
- IntraCUG Restrictions intra-CUG restrictions; options are incoming-call-barred (ICB)
and outgoing-call-barred (OCB)
- SPCH Reg whether this subscription applies to SPCH
- AUXSPCH Reg whether this subscription applies to AUXSPCH
- FAX Reg whether this subscription applies to FAX
- CDA Reg whether this subscription applies to CDA
- CDS Reg whether this subscription applies to CDS
- All BSG Reg whether this subscription applies to BSGs
7.23.2 Interactions
• CUG Subscription interacts with all basic services (except SMMO, SMMT, VBS, and
VGCS) and the CUG Feature.
• CUG Subscription must be provisioned for CUG feature to be provisioned.
• For each <bsg> Reg set to TRUE, the corresponding BSG must be provisioned (interacts
with all basic services except SMMO, SMMT, VBS, and VGCS).
• There are complex interactions with the CUG feature. See the CUG feature interactions in
“Interactions” on page 110.
7.24 Closed User Groups Feature

Closed User Groups (CUG) is a basic service group based supplementary service (BSG-SS), that allows
closed user groups information to be datafilled against each BSG supported by the service.
The CUG Feature is optional CUG data, whereas CUG Subscription “Closed User Groups Subscription”
on page 107 is mandatory CUG data.

7.24.1 Datafill
The CUG Feature data syntax is detailed in the following table. Each of the registration sets is optional.
Table 116 CUG Feature data syntax
Dataitem Syntax
ICA {OA, IA, ALL}
PrefCUG Index number: 0 -32767
ICA {OA, IA, ALL}
ICA {OA, IA, ALL}
ICA {OA, IA, ALL}
ICA {OA, IA, ALL}
All BSG Reg Set Activated Boolean
ICA {OA, IA, ALL}
CUG Feature field descriptions are provided in the following table.
Table 117 CUG Feature field descriptions
SPCH Reg Set Activated indicates whether the registration is activated
ICA inter-CUG accessibility; options are outgoing-

access, incoming-access or all
PrefCUG Index preferred CUG index
AUXSPCH Reg Set Activated indicates whether the registration is activated

access,
incoming-access or all


FAX Reg Set Activated indicates whether the registration is activated

CDA Reg Set Activated indicates whether the registration is activated

CDS Reg Set Activated indicates whether the registration is activated

All BSG Reg Set Activated indicates whether the registration is activated

7.24.2 Interactions
• The CUG feature interacts with all basic services (except SMMO, SMMT, VBS, and
VGCS) and CUG Subscription.
• CUG Subscription must be provisioned for the CUG feature to be provisioned.
• For each Reg Set, if a PrefCUG Index is datafilled,
– The PrefCUG Index must exist at least once in a CUG Subscription as a CUG Index.
– Any CUG Subscription dataset whose CUG Index matches the PrefCUG Index must
have its <bsg> Reg dataitem set to TRUE where <bsg> corresponds to the particular
CUG Feature Reg Set and its IntraCUG Restrictions dataitem must not be set to
OCB.
• For each Reg Set provisioned except All BSG,
– The BSG must be provisioned (interacts with all basic services except SMMO,
SMMT, VBS, and VGCS).
– At least one <bsg> Reg dataitem of any CUG Subscription dataset must be set to
TRUE where <bsg> corresponds to the particular CUG feature Reg Set. If any CUG
Subscription dataset has its All BSG Reg dataitem set to TRUE, then this check will
always pass.
7.25 Customized Ring Back Tone

The Customized Ring Back Tone (CRBT) Supplementary Service enables mobile subscribers to select
music or audio to be played to the calling party in place of the existing standard Ring Back tone for voice
calls. This service is activated by the service provider as a result of provisioning.

Although this service is provisioned against the called subscriber, it is the calling subscriber who enjoys
the service.
ATTENTION
CRBT is an IMSI-SS and applies only to SPCH and
AUXSPCH BSG
7.25.1 Interactions
None
7.25.2 Datafill
CRBT has no dataitems; it is simply provisioned or deprovisioned.
7.26 Call Waiting

The Call Waiting (CW) is a basic service group based supplementary service (BSG-SS), allowing call
waiting to be given to the BSGs that are supported by the service.
7.26.1 Datafill
The CW data syntax is detailed in the following table. Each of the registration sets is optional.
Table 118 CW data syntax
Dataitem Syntax
CW field descriptions are provided in the following table.
Table 119 CW field descriptions

activated

7.26.2 Interactions
CW interacts with all basic services (except VBS and VGCS), BAIC, and ODB BAIC), as follows:
• For each registration set provisioned, the BSG must be provisioned (interacts with all
basic services except VBS and VGCS).
Table 120 CW registration set interactions

Service State
BAIC Reg Set Activated BAIC can be registered after CW but CW cannot
be registered after BAIC; CW and BAIC can be
registered together in the same transaction.
ODB BAIC Provisioned ODB BAIC can be provisioned after CW but CW

cannot be registered after ODB BAIC; CW can be
registered with ODB BAIC provisioned in the same
transaction.
7.27 Explicit Call Transfer

Provisioning Explicit Call Transfer (ECT) enables explicit call transfer functionality for the subscriber. ECT
is an IMSI-SS and applies to SPCH and AUXPSCH BSGs only.
7.27.1 Datafill
ECT has no dataitems; it is simply provisioned or deprovisioned.
7.27.2 Interactions
ECT interacts with HOLD. HOLD must be provisioned for ECT to be provisioned.
7.28 Enhanced Multi Level Precedence and Pre-emption

Enhanced Multi Level Precedence and Pre-emption (EMLPP) datafill defines priorities for the subscriber,
and you can use it to set a priority for Wireless Priority Service (WPS). EMLPP is an IMSI-SS and applies
to all BSGs except SMS.
7.28.1 Datafill
The EMLPP data syntax is detailed in the following table.
Table 121 EMLPP data syntax

Maximum Priority {A, B, 1, 2, 3, 4}
Default Priority {A, B, 1, 2, 3, 4}


EMLPP field descriptions are provided in the following table.
Table 122 EMLPP field descriptions
Maximum Priority the maximum priority for EMLPP or WPS
Default Priority the default priority for EMLPP or WPS, depending on office
parameter CPS_MODE
7.28.2 Interactions
EMLPP interacts with the office parameter CPS_MODE (table GHLRPARM), as follows:
• If the office parameter CPS_MODE is EMLPP, then the Default Priority must not be
greater than the Maximum Priority (A is highest, 4 is lowest).
• If the office parameter CPS_MODE is WPS, then the Default Priority and the Maximum
Priority must match, and their range is restricted to {B, 1, 2, 3}.
• If the office parameter CPS_MODE is HYBRID, then the Maximum Priority range is
restricted to {B, 1, 2, 3, 4}. The Maximum Priority represents the WPS setting, while the
Default Priority represents the EMLPP setting.
7.29 Extension Services

Extension Services (EXT) is a basic service group-based supplementary service (BSG-SS), allowing
MSISDN groups and timers to be datafilled for simultaneous and sequential altering (also known as
flexible altering and mobile hunting, respectively) for the BSGs supported by the service. EXT is an
7.29.1 Datafill
EXT data syntax is detailed in the following table: Table 123 EXT data syntax on page 114. Each
registration set data consists of one to three groups and also an overall registration set. Each group
consists of one to three MSISDNs and a timer.
For each registration set, only certain combinations of MSISDNs, Timers, and Groups are valid; these are
given in the following table: Table 124 Valid MSISDN/Timer/Group Combinations on page 115.
Combinations contain a maximum of five MSISDNs.
The validation of EXT is complex due to its interaction with ESMR LCO Translations. If these translations
are enabled, then EXT’s MSISDNs are passed through these translations to normalize the number (that
is, convert it to international E164 format) and to determine whether the number is "local." The syntax
check-ins apply to the post-translated number. The syntax check for pre-translated MSISDNs is that they
contain 1 to 15 digits (with no restriction on the first digit). The "local" indication is required in the EXT
interaction with LCO service.
If ESMR LCO translations are not enabled, then no translations occur and the MSISDN defaults to being
"not local."


local or not. They are enabled on the HLR if key 1021 is datafilled in system Table XLAENTRY,
Table 123 EXT data syntax

MSISDN 1.1 4 to 15 digits, cannot start

with zero
MSISDN 1.2 4 to 15 digits, cannot start Optional

with zero

with zero
Timer 1 number: 5 -90 (multiple of 5)
Group 1 {SINGLE, MULTIPLE} Optional

with zero

with zero

with zero
Timer 2 number: 5 -90 (multiple of 5) Optional

with zero

with zero

with zero
Overall Group {SINGLE, MULTIPLE} Optional
AUXSPCH Reg Activated Boolean

Set
MSISDN 1.1 4 to 15 digits, cannot start
with zero

with zero


with zero
Timer 1 number: 5 -90 (multiple of 5)

with zero

with zero

with zero

with zero

with zero

with zero
Overall Group {SINGLE, MULTIPLE} Optional
Table 124 Valid MSISDN/Timer/Group Combinations
Combination Type Sequence

Simultaneous MMTG
MMMTG
Sequential MTMTG
MTMTMTG
Mixusing5MSISDNs MMMTGMMTGG
MMTGMMMTGG
MMMTGMTMTG
MTMTMMMTGG
MTMMMTGMTG
MMTGMMTGMTG

MMTGMTMMTGG
MTMMTGMMTGG
Mix using 4 MSISDNs M M TG M TM TG
MT MMT G M T G
MT MT MMT G G
MMMT G MT G
MT MMMT G G
MMT G MMT G G
Mix using 3 MSISDNs MMT G MT G
MT MMT G G
Other MT
EXT field descriptions are provided in the following table.
Table 125 EXT field descriptions
MSISDN 1.1 first MSISDN of first group for SPCH registration
MSISDN 1.2 second MSISDN of first group for SPCH registration
MSISDN 1.3 third MSISDN of first group for SPCH registration
Timer 1 timer for first group for SPCH registration
Group 1 first group type for SPCH registration; options are

multiple or single user
MSISDN 2.1 first MSISDN of second group for SPCH registration
MSISDN 2.2 second MSISDN of second group for SPCH

registration
MSISDN 2.3 third MSISDN of second group for SPCH registration
Timer 2 timer for second group for SPCH registration
Group 2 second group type for SPCH registration; options are

MSISDN 3.1 first MSISDN of third group for SPCH registration
MSISDN 3.2 second MSISDN of third group for SPCH registration
MSISDN 3.3 third MSISDN of third group for SPCH registration


Timer 3 timer for third group for SPCH registration
Group 3 third group type for SPCH registration; options are

Overall Group overall group type for SPCH registration; options are
multiple or single user (applies to the three other
groups)
AUXSPCH Reg Activated indicates whether the AUXSPCH registration is

Set activated
MSISDN 1.1 first MSISDN of first group for AUXSPCH registration
MSISDN 1.2 second MSISDN of first group for AUXSPCH

registration
MSISDN 1.3 third MSISDN of first group for AUXSPCH registration
Timer 1 timer for first group for AUXSPCH registration
Group 1 first group type for AUXSPCH registration; options

are multiple or single user
MSISDN 2.1 first MSISDN of second group for AUXSPCH

registration
MSISDN 2.2 second MSISDN of second group for AUXSPCH

registration
MSISDN 2.3 third MSISDN of second group for AUXSPCH

registration
Timer 2 timer for second group for AUXSPCH registration
Group 2 second group type for AUXSPCH registration;

options are multiple or single user
MSISDN 3.1 first MSISDN of third group for AUXSPCH registration
MSISDN 3.2 second MSISDN of third group for AUXSPCH

registration
MSISDN 3.3 third MSISDN of third group for AUXSPCH

registration
Timer 3 timer for third group for AUXSPCH registration
Group 3 third group type for AUXSPCH registration; options

Overall Group overall group type for AUXSPCH registration; options

(applies to the three other groups)


7.29.2 Service Interactions

EXT interacts with TPHNY, AUXTPHNY, and LCO, as follows:
• For each registration set provisioned, the BSG must be provisioned. It interacts with
TPHNY and AUXTPHNY.
• The interactions are provided in the following table. This interactions apply to both BSG
registration sets. These interactions only apply to activated BSG registrations.
Table 126 EXT registration set interactions

Service State
LCO Provisioned LCO and EXT registration sets can only

coexist if each MSISDN in the registration set
is “local."
7.30 Follow Me
The Follow Me (FM) datafill allows FM classes of registrations to be specified. FM is an IMSI-SS and
applies to all BSGs except VGS.
This service is also known as Functional Addressing (FA).
7.30.1 Datafill
FM data syntax is detailed in the following table. The following intra-service interactions apply.
At least one COR value (COR x or Supervisor COR x) must be set to TRUE.
Table 127 FM data syntax

COR A Boolean
COR B Boolean
COR C Boolean
COR D Boolean
Supervisor COR A Boolean
Supervisor COR B Boolean
Supervisor COR C Boolean
Supervisor COR D Boolean
FM field descriptions are provided in the following table.


Table 128 FM field descriptions
COR A Engine/Train cab-radio basic function
COR B Maintenance function
COR C Operation support user
COR D Customer support user
Supervisor COR A Engine/Train cab-radio basic function FN force erasure
Supervisor COR B Maintenance function FN force erasure
Supervisor COR C Operation support user FN force erasure
Supervisor COR D Customer support user FN force erasure
7.30.2 Interactions
Interactions of the Follow Me feature with supplementary services can only occur for the remote party.
The interactions of the Follow Me feature with supplementary services other than Call Forwarding
Unconditional (CFU) are the same as the CFU interactions with supplementary services.
The interactions with Operator Determined barring are the same as the interaction between Operator
Determined barring and call forwarding unconditional.
The interactions with CAMEL are the same as the interaction between CAMEL and call forwarding
unconditional.
7.31 Call Hold

Provisioning Call Hold (HOLD) enables call hold functionality for the subscriber. HOLD is an IMSI-SS and
applies to SPCH and AUXSPCH BSGs only.
7.31.1 Datafill
HOLD has no dataitems; it is simply provisioned or deprovisioned.
7.31.2 Interactions
HOLD interacts with MPTY and ECT, as follows:
• HOLD must be provisioned for MPTY to be provisioned.

• HOLD must be provisioned for ECT to be provisioned.
7.32 Hot Billing

Provisioning Hot Billing (HOTBILL) enables hot billing functionality for subscriber. HOTBILL is an
Kapsch-proprietary IMSI-SS.
7.32.1 Datafill
HOTBILL has no dataitems; it is simply provisioned or deprovisioned.

7.32.2 Interactions
None
7.33 Local Calls Only

Provisioning Local Calls Only (LCO) enables local-calls-only functionality for the subscriber. LCO is an
Kapsch-proprietary IMSI-SS.
7.33.1 Datafill
LCO has no data items, it is simply provisioned or deprovisioned.
7.33.2 Interactions
LCO interacts with all call forwards and EXT.
Interactions with BSG-SSs are provided in the following table. These interactions apply to every
registration set of each BSG-SS listed.
Table 129 LCO Interactions

Service State
CFU Reg Set Activated LCO and CFU are mutually exclusive unless (1) the
subscriber does not have GSM FTNs or (2) the
subscriber has GSM FTNs but FTN is local". "
CFB Reg Set Activated LCO and CFB are mutually exclusive unless (1) the
subscriber does not have GSM FTNs or (2) the
CFNRc Reg Set Activated LCO and CFNRc are mutually exclusive unless (1)
the subscriber does not have GSM FTNs or (2) the
CFNRy Reg Set Activated LCO and CFNRy are mutually exclusive unless (1)
the subscriber does not have GSM FTNs or (2) the
EXT Reg Set Activated LCO and EXT are mutually exclusive unless all EXT
MSISDNs are local". "
For determination of subscriber FTN type see “Determining FTN type” on page 87.
For more information on whether CF FTNs/EXT MSISDNs are local or not, see “Datafill”
on page 121 and “Datafill” on page 113, respectively. If ESMR LCO Translations are
not enabled, then all FTNs/MSISDNs default to "not local," meaning that in this scenario
LCO is always mutually exclusive with all call forwards and EXT.
7.34 Malicious Call Trace

Provisioning Malicious Call Trace (MCT) enables malicious call trace functionality for the subscriber. MCT
is an Kapsch-proprietary IMSI-SS and applies to all BSGs except SMS and VGS.

7.34.1 Datafill
MCT has no dataitems; it is simply provisioned or deprovisioned.
7.34.2 Interactions
None
7.35 Multiparty
Multiparty (MPTY) datafill defines the maximum number of ports allowed on a multi-party call. MPTY is an
IMSI-SS and applies to SPCH and AUXSPCH BSGs only.
7.35.1 Datafill
MPTY data syntax is detailed in the following table.
Table 130 MPTY data syntax

Option {M3PORT, M6PORT]
MPTY field descriptions are provided in the following table.
Table 131 MPTY field descriptions
Option multiparty option: 3-ports or 6-port
7.35.2 Interactions
MPTY interacts with HOLD. HOLD must be provisioned for MPTY to be provisioned.
7.36 User to User Signaling stage 1

Provisioning User to User Signaling stage 1 (UUS1) enables user-to-user signaling stage 1 functionality
for the subscriber. UUS1 is an IMSI-SS and applies to all BSGs except SMS and VGS.
7.36.1 Datafill
UUS1 has no dataitems; it is simply provisioned or deprovisioned.
7.36.2 Interactions
None
7.37 Wireless Priority Service

On the Kapsch HLR, use the EMLPP service to provision/datafill Wireless Priority Service (WPS). See
“Enhanced Multi Level Precedence and Pre-emption” on page 112.

8 Operator-determined barrings
Operator-Determined Barrings (ODBs) define barrings that you put in place as an operator. They apply to
all basic service groups except VGS (ODB BAOC is an exception in that it applies to VGS too.)
8.1 Navigation
• “Operator-determined barrings categories” on page 122
8.2 Operator-determined barrings categories

There are four categories of ODB: incoming, outgoing, ECT, and miscellaneous.
Incoming ODBs are:
• ODB BAIC (Barring of All Incoming Calls)

• ODB BICRoam (Barring of Incoming Calls when Roaming outside HPLMN country)
Outgoing ODBs are:
• ODB BAOC (Barring of All Outgoing Calls)

• ODB BAOCRoam (Barring of [All] Outgoing Calls when Roaming outside HPLMN country)
• ODB BOIC (Barring of Outgoing International Calls)
• ODB BOICexHC (Barring of Outgoing International Calls except those to HPLMN
Country)
ECT ODBs are:
• ODB BAECT (Barring of All Explicit Call Transfer)

• ODB BCHDECT (Barring of Chargeable Explicit Call Transfer, that is, when at least one of
the calls is charged to the served subscriber)
• ODB BINTECT (Barring of International Explicit Call Transfer, that is, when at least one of
the calls is charged to the served subscriber at international rates)
• ODB BDBCECT (Barring of Doubly Chargeable Explicit Call Transfer, that is, when both
of the calls are charged to the served subscriber)
Miscellaneous ODBs are:
• ODB HPLMN Specific 1

• ODB Premium Rate Entertainment
• ODB Premium Rate Information
• ODB CCFMGT (Barring of Conditional Call Forwarding Subscriber Management)
• ODB CISSMGT (Barring of Call Independent Supplementary Services Management)

8.3 Datafill
ODBs are identical, that is, they have no dataitems. ODBs are simply provisioned or deprovisioned.
8.4 Interactions
The ECT ODBs interact with each other, as follows:
• ODB BAECT and ODB BCHDECT are mutually exclusive.

• ODB BCHDECT and ODB BINTEXT are mutually exclusive.
• ODB BAECT and ODB BINTECT are mutually exclusive.

9 CAMEL services
9.1 Navigation
• „CAMEL subscription information services” on page 124
• “Dialed CSI” on page 125
• “General Packet Radio Service CSI” on page 126
• “Mobility Management CSI” on page 128
• “Originating CSI” on page 129
• “Short Message Service CSI” on page 134
• “Supplementary Service CSI” on page 135
• “Terminating CSI” on page 136
• “Translations Information Flag CSI” on page 139
• “Unstructured Supplementary Service Data CSI” on page 139
9.2 CAMEL subscription information services

Customized Applications for Mobile Enhanced network Logic (CAMEL) services are intelligent network
(IN) services for the GSM network.
The HLR supports several individual CAMEL subscription information (CSI) services as shown in the
following table.
Table 132 CAMEL services

D-CSI Dialled CSI “Dialed CSI” on page 125
GPRS-CSI GPRS CSI “General Packet Radio Service CSI” on
page 126
M-CSI Mobility Management CSI “Mobility Management CSI” on page 128
O-CSI Originating CSI “Originating CSI” on page 129

SMS-CSI Short Message Service CSI “Short Message Service CSI” on
page 134
SS-CSI Supplementary Service CSI “Supplementary Service CSI” on
page 135
T-CSI Terminating CSI “Terminating CSI” on page 136
USSD-CSI Unstructured Supplementary “Unstructured Supplementary Service
Service Data CSI Data CSI” on page 139
CAMEL is a network feature that enables the HPLMN operator to provide some of Operator Specific
Services (OSS) that are not standardized by GSM specifications, to some or all of its subscribers when
roaming to a different PLMN. The feature can also be used to provide these services while the subscriber
is in the HPLMN.
Normally, when a subscriber roams to a different PLMN, all OSSs are lost, because the services are not

GSM-defined and therefore not supported by the VPLMN. However, CAMEL is GSM-defined, which
means that OSSs provided through CAMEL are available when the subscriber roams to a VPLMN that
supports CAMEL.
9.3 Dialed CSI

The Dialed CSI (D-CSI) datafill defines criteria for the Analyzed Information detection point (DP) in the
originating Basic Call State Machine (BCSM) for mobile-originating and forwarded calls.
9.3.1 Datafill
The D-CSI data syntax is detailed in the following table. The Criteria Names are a vector; you must at
least datafill one Criteria Name. See “Data vectors” on page 27 for more information on vectors. The
following intra-service interactions apply.
Duplicate Criteria Names are not allowed.
Table 133 D-CSI data syntax

Active Boolean
Phase {CAP3}
Unsupported VMSC behavior {RELEASE, CONTINUE,

(UNSPVMSC) CONT_HPLMN}
Unsupported GMSC {RELEASE, CONTINUE}

behavior (UNSPGMSC)
Criteria Names vector (1 -10) 1 -20 characters 9 are optional
D-CSI field descriptions are provided in the following table.
Table 134 D-CSI field descriptions
Active indicates whether the CSI is active
Phase the CAMEL Phase that is required at the gsmSCF for the service. You
must datafill this as Phase 3 (CAP3). It is also known as the CAMEL
Capability Handler (CCH).
UNSPVMSC the behavior if the VLR/MSC does not support Phase 3: is release-call,
continue-call, or continue-call-if-in-HPLMN
UNSPGMSC the behavior if the GMSC does not support Phase 3: is release-call or
continue-call
Criteria a criteria name, defined in system Table GHLRDSCR

Name(s)

9.3.2 Interactions
D-CSI interacts with system Table GHLRDCSR.
Each Criteria Name must be an entry from column DPCRNAME in the system Table GHLRDCSR.
9.4 General Packet Radio Service CSI

General Packet Radio Service CSI (GPRS-CSI) datafill defines trigger information that is required to
invoke a CAMEL service for GPRS Sessions and PDP Contexts.
9.4.1 Datafill
The GPRS-CSI data syntax is detailed in the following table. Each of the Trigger DP sets is optional,
although you must at least provision one. The following intra-service interactions apply.
Table 135 GPRS-CSI data syntax

Active Boolean
Phase {CAP3}
Unsupported SGSN behavior {RELEASE, CONTINUE,

(UNSPSGSN) CONT_HPLMN}
Trigger DP1 Set Service Control 1 - 20 characters

Function (SCF)
Name
Service Key number: 1 - 2147483647
SCF Unavailable {RELEASE, CONTINUE}

Treatment
Trigger DP2 Set SCF Name 1 - 20 characters

Treatment
Trigger DP11 Set SCF Name 1 -20 characters

Treatment

Treatment


Treatment
GPRS-CSI field descriptions are provided in the following table.
Table 136 GPRS-CSI field descriptions
Phase the CAMEL Phase that is required at the gsmSCF

for the service. This has to be datafilled as Phase 3
(CAP3) also known as the CAMEL Capability
Handler (CCH).
UNSPSGSN the behavior if the SGSN does not support Phase

3: is release-call, continue-call, or continue-call-if-
in-HPLMN
Trigger DP1 Set SCF Name the DP SCF name, defined in system Table
GHLRSCF
Service Key the DP service key
SCF Unavailable the behavior for this DP if the SCF is unavailable:

Treatment is release or continue the GPRS session/PDP
context
Trigger DP2 Set SCF Name the DP SCF name, defined in system Table
GHLRSCF

context
Trigger DP11 SCF Name the DP SCF name, defined in system Table
Set GHLRSCF

context
Set GHLRSCF

context

Set GHLRSCF

context
9.4.2 Interactions
GPRS-CSI interacts with GPRS and system Table GHLRSCF, as follows:
• GPRS must be provisioned for GPRS-CSI to be provisioned.

• Each SCF Name must be an entry from the SCF_NAME column in system Table
GHLRSCF.
9.5 Mobility Management CSI

The Mobility Management CSI (M-CSI) datafill defines which mobility events trigger a message to be sent
to the GSM Service Control Function (gsmSCF).
9.5.1 Datafill
The M-CSI data syntax is detailed in the following table.
Table 137 M-CSI data syntax

Active Boolean
Mobility Trigger Name 1 -20 characters
Suppress M-CSI {HC, HPLMN, INTL} Optional
M-CSI field descriptions are provided in the following table.
Table 138 M-CSI field descriptions
Mobility Trigger Name the mobility trigger name, defined in system Table
GHMTRIG
Suppress M-CSI indicates when to suppress M-CSI: when located in HPLMN

country, in HPLMN, or when international
9.5.2 Interactions
M-CSI interacts with system Table GHMTRIG. The Mobility Trigger Name must be an entry from the

MTNAME field of system Table GHMTRIG.
9.6 Originating CSI

Originating CSI (O-CSI) datafill defines subscriber-originating trigger information that is used by GSM
nodes to determine when to contact the GSM Service Control Function (gsmSCF), that, in turn, decides
how a call proceeds.
O-CSI datafill also encompasses TIF-CSI provisioning.
9.6.1 Datafill
O-CSI data syntax is detailed in the following table: Table 137 M-CSI data syntax on page 128. Each of
the Trigger DP sets is optional, although at least one must be provisioned. TIF-CSI is provisioned by
means of the FTN Checks dataitem. The following intra-service interactions apply:
• Provision at least one Trigger DP set.

• If FTN Checks is CUSTOM, then Active must be TRUE, UNSPVMSC must be RELEASE,
UNSPGMSC must be RELEASE, and QSCFWIHP must be TRUE.
• If FTN Checks is TIF, then Active must be TRUE, QSCFWIHP must be TRUE, and at
least one of these sets must be provisioned: TDP2 Phase2, TDP2 Phase3, TDP4 Phase3.
• For both the TDP2 Phase2 and TDP2 Phase3 sets, if DNC Matchtype is not datafilled,
then no DNC DNs should be datafilled, and no DNC Lengths should be datafilled either.
• For both the TDP2 Phase2 and TDP2 Phase3 sets, if DNC Matchtype is datafilled, then at
least one DNC DN or one DNC Length must be datafilled. (For example, it is valid to have
just one DNC DN or just one DNC Length.)
• DNC DNs (that is NOA + NPI + DN combined) must be unique for each subscriber
(includes both vectors).
• DNC Lengths must be unique for each subscriber (includes both vectors).
• BS Codes Criteria must be unique for each subscriber (include both vectors).
• For BS Codes Criteria, if a BSG is datafilled, then no BSs belonging to that BSG can also
be datafilled.
• Cause Values Criteria must be unique for each subscriber.
Table 139 O-CSI data syntax

Active Boolean
FTN Checks {GSM, CUSTOM, TIF}
UNSPVMSC {RELEASE, CONTINUE, CONT_HPLMN}
UNSPGMSC {RELEASE, CONTINUE}
QSCFWIHP Boolean
Trigger DP2 SCF Name 1 -20 characters

Phase1 Set
Service Key number: 1 -2147483647


Treatment
Send CCH Boolean

Phase2 Set

Treatment
DNC Matchtype {ENABLING, INHIBITING} Optional
DNC DNs vector composed of the three dataitems below All 10 are
(0 -10) optional
- NOA {INTL, UNKN} as above
- NPI {E164, E212, F69, NATL, PRIV, UNKN, as above

X121}
- DN 1 -15 characters (0..9, *, #, A, B, C) as above
DNC Lengths number: 1 -15 All three

vector (0 -3) are
optional
BS Codes {CDA, CDA300, CDA1200, CDA2400, All five

Criteria vector (0 CDA4800, CDA9600, CDAGBS, are
-5) ALTSPCDA, SPCHCDA, CDS, CDS1200, optional.
CDS2400, CDS4800, CDS9600,
CDSGBS, ALTSPCDS, SPCHCDS,
SPCH, TPHNY, AUXSPCH, AUXTPHNY,
FAX, FAX3, ALTSPFAX}
Call Type {FWD, NOT_FWD} Optional

Criteria
Phase3 Set

Treatment
DNC Matchtype {ENABLING, INHIBITING} Optional
DNC DNs vector composed of the three dataitems below All 10 are
(0 -10) optional
- NOA {ABBR, INTL, NATL, NTWK, SUBS, as above

UNKN}
- NPI {E164, E212, F69, NATL, PRIV, UNKN, as above

X121}
- DP 1 -15 characters (0..9, *, #, A, B, C) as above


DNC Lengths number: 1 -15 All three

vector (0 -3) are
optional
BS Codes {CDA, CDA300, CDA1200, CDA2400, All five

Criteria vector (0 CDA4800, CDA9600, CDAGBS, are
-5) ALTSPCDA, SPCHCDA, CDS, CDS1200, optional.
CDS2400, CDS4800, CDS9600,
CDSGBS, ALTSPCDS, SPCHCDS,
SPCH, TPHNY, AUXSPCH, AUXTPHNY,
FAX, FAX3, ALTSPFAX}
Call Type {FWD, NOT_FWD} Optional

Criteria
Phase3 Set

Treatment
Cause Values number: 1 -127 All 5 are

Criteria vector (0 optional.
-5)
O-CSI field descriptions are provided in the following table.
Table 140 O-CSI field descriptions
FTN Checks whether the subscriber has GSM FTNs, TIF-CSI FTNs
(also known as TIF FTNs) or custom FTNs; relates to
valid NOA/NPI formats. TIF-CSI is provisioned by
setting this dataitem to TIF.
UNSPVMSC unsupported VLR/MSC behavior: is release-call,

continue-call, or continue-call-if-in-HPLMN
UNSPGMSC the behavior if the GMSC does not support the O-CSI
phase: is release-call or continue-call
QSCFWIHP indicates whether to query the SCF when in HPLMN
Trigger DP2 SCF Name the DP SCF name, defined in system Table GHLRSCF
Phase1 Set
SCF Unavailable the behavior for this DP if the SCF is unavailable: is

Treatment release or continue the call
Send CCH indicates whether to send the CCH (CAP1) to the VLR

Phase2 Set
Service Key the behavior for this DP if the SCF is unavailable: is
release or continue the call

DNC Matchtype indicates whether the Destination Number Criteria is

enabling or inhibiting
DNC DNs vector destination-number-criteria destination numbers, each

(0 -10) composed of NOA, NPI, and DN
- NOA the DN Nature Of Address; options are International-

number (INTL) and Unknown (UNKN)
- NPI the DN Number Plan Indicator; options are

• Unknown (UNKN)
- DN the destination number itself
DNC Lengths destination-number-criteria destination number lengths

vector (0 -3)
BS Codes basic service codes criteria

Criteria vector (0
-5)
Call Type indicates whether call type criteria is forwarding or not

Criteria forwarding
Phase3 Set

DNC Matchtype indicates whether the Destination Number Criteria is

enabling or inhibiting
DNC DNs vector destination-number-criteria destination numbers, each

(0 -10) composed of NOA, NPI, and DN

- NOA the DN Nature Of Address; options are

• National-significant-number (NATL)
• Unknown (UNKN)
- NPI the DN Number Plan Indicator; options are

• Unknown (UNKN)
- DP the destination number itself
DNC Lengths destination-number-criteria destination number lengths

vector (0 -3)
BS Codes basic service codes criteria

Criteria vector (0
-5)
Call Type indicates whether call type criteria is forwarding or not

Criteria forwarding
Phase3 Set

Cause Values cause values criteria

Criteria vector (0
-5)
9.6.2 Interactions
O-CSI interacts with all call forwards (CFB, CFNRc, CFNRy, CFU) and system Table GHLRSCF. The
vast majority of interactions relate (directly or indirectly) to TIF-CSI, as follows:
• O-CSI cannot be newly provisioned with FTN Checks as CUSTOM if the subscriber has any
call forward FTNs (that is any CF registration data).
• O-CSI cannot be newly provisioned with FTN Checks as TIF if the subscriber has any call
forward FTNs (that is any CF registration data).
• O-CSI cannot be deprovisioned if FTN Checks is CUSTOM and the subscriber has any call
• O-CSI cannot be deprovisioned if FTN Checks is TIF and the subscriber has any call


• O-CSI cannot be deprovisioned if the subscriber has any call forwards with a DCF ID
datafilled.
• FTN Checks cannot be changed if the subscriber has any call forward FTNs (that is any CF
registration data).
• FTN Checks cannot be changed if the subscriber has any call forwards with a DCF ID
datafilled.
• Each SCF Name must be an entry from the SCF_NAME column of system Table
GHLRSCF.
9.7 Short Message Service CSI

Short Message Service CSI (SMS-CSI) datafill defines trigger information required to invoke CAMEL
service logic for mobile short message submissions. This is subscription information for subscribers that
require CAMEL support of Mobile Originating Short Message Service (MO-SMS) and Mobile Terminating
Short Message Service (MT-SMS).
9.7.1 Datafill
SMS-CSI data syntax is detailed in the following table.
Table 141 SMS-CSI data syntax

DP {DP1,DP11}
Active Boolean
Phase {NONE,CAP1,CAP2,CAP3,CAP4}
Unsupported Node behavior {RELEASE, CONTINUE, CONT_HPLMN}

(UNSPNODE)
SCF Name 1 - 20 characters
SCF Unavailable Treatment {RELEASE, CONTINUE}
Although the Phase value range is NONE, CAP1, CAP2, and CAP3, it can only have the values CAP3 for
MO SMS CSI and CAP4 for MT SMS CSI. 2 multiple tuples can be defined each for DP1 MO SMS CSI
and DP11 MT SMS CSI subscription.
SMS-CSI field descriptions are provided in the following table.
Table 142 SMS-CSI field descriptions
DP Indicates the trigger DP1 for MO SMS CSI or DP11 for MT
SMS CSI.

Phase the CAMEL Phase that is required at the gsmSCF for the
service. Datafill this as Phase 3 (CAP3) for MO SMS CSI
and DP11 for MT SMS CSI. It is also known as the
CAMEL Capability Handler (CCH).
UNSPNODE the behavior if the VLR/MSC or SGSN does not support
Phase 3 or Phase 4: is release-call, continue-call, or
continue-call-if-in-HPLMN
SCF Name the DP1 / DP11 SCF name, defined in system Table
GHLRSCF
Service Key the DP1 / DP11 service key
SCF Unavailable Treatment the behavior for DP1 / DP11 if the SCF in unavailable: is
release or continue the GPRS session/PDP context
9.7.2 Interactions
SMS-CSI interacts with system Table GHLRSCF, as follows:
The SCF Name must be an entry from the SCF_NAME column in system Table GHLRSCF.
9.8 Supplementary Service CSI

Supplementary Service CSI (SS-CSI) datafill defines supplementary service notification criteria.
9.8.1 Datafill
SS-CSI data syntax is detailed in the following table. The following intra-service validations apply.
At least one of ECT Option and MPTY Option must be set to TRUE.
Table 143 SS-CSI data syntax

Active Boolean
ECT Option Boolean
MPTY Option Boolean
SCF Name 1 - 20 characters
SS-CSI field descriptions are provided in the following table.
Table 144 SS-CSI field descriptions
ECT Option indicates whether the CSI is active
MPTY Option indicates whether notifications are sent for MPTY
SCF Name the SCF name, defined in system Table GHLRSCF

9.8.2 Interactions
SS-CSI interacts with system Table GHLRSCF, as follows:
The SCF Name must be an entry from the SCF_NAME column of system Table GHLRSCF.
9.9 Terminating CSI

The Terminating CSI (T-CSI) datafill defines subscriber-terminating trigger information that is used by
GSM nodes to determine when to contact the GSM Service Control Function (gsmSCF); that in turn
decides how a call proceeds.
9.9.1 Datafill
T-CSI data syntax is detailed in Table 145 T-CSI data syntax on page 136. Each of the Trigger DP sets is
optional, although at least one must be provisioned. The following intra-service validations apply.
• Provision at least one Trigger DP set.

• Datafill a particular BS Code once across both the TDP12 Phase2 and Phase3 sets.
• For each BS Codes vector, if a BSG code is datafilled, then a BS belonging to that BSG
cannot also be datafilled.
• Datafill a particular Cause Value once across both the TDP13 and TDP14 sets.
In the original Kapsch HLR O-CSI/T-CSI implementation, QSCFWIHP was shared between these two
services, whereas now it is seen as being specific to O-CSI. Also the Kapsch HLR shares the
UNSPGMSC across both T-CSI and O-CSI (that is, there is a single value, used by both T-CSI and O-
CSI).
Table 145 T-CSI data syntax

Active Boolean
Provide Location Info Boolean
Page for Cell ID Boolean
Provide Subscriber State Boolean
Provide Current Location Boolean
Suppress T-CSI {HC, HPLMN} Optional
UNSPGMSC {RELEASE, CONTINUE}
Trigger DP12 SCF Name 1 - 20 characters

Phase1 Set

Treatment
Send CCH Boolean



Phase2 Set

Treatment
BS Codes Criteria {CDA, CDA300, CDA1200, CDA2400, All 5 are

vector (0 -5) CDA4800, CDA9600, CDAGBS, optional.
ALTSPCDA, SPCHCDA, CDS,
CDS1200, CDS2400, CDS4800,
CDS9600, CDSGBS, ALTSPCDS,
SPCHCDS, SPCH, TPHNY,
AUXSPCH, AUXTPHNY, FAX, FAX3,
ALTSPFAX}

Phase3 Set

Treatment
BS Codes Criteria {CDA, CDA300, CDA1200, CDA2400, All 5 are

vector (0 -5) CDA4800, CDA9600, CDAGBS, optional
ALTSPCDA, SPCHCDA, CDS,
CDS1200, CDS2400, CDS4800,
CDS9600, CDSGBS, ALTSPCDS,
SPCHCDS, SPCH, TPHNY,
AUXSPCH, AUXTPHNY, FAX, FAX3,
ALTSPFAX}

Phase3 Set

Treatment
Cause Values number: 1 - 127 All 5 are

Criteria vector (0 - optional
5)

Phase3 Set

Treatment
Cause Values number: 1 - 127 All 5 are

Criteria vector (0 - optional
5)
T-CSI field descriptions are given in the following table.


Table 146 T-CSI field descriptions
Provide Location Info indicates whether provide location info is in effect
Page for Cell ID indicates whether page for cell ID is in effect
Provide Subscriber State indicates whether provide subscriber state is in

effect
Provide Current Location indicates whether provide current location is in
effect
Suppress T-CSI indicates when T-CSI is to be suppressed: when-
located-in-HPLMN-country or when-located-in-
HPLMN
UNSPGMSC the behavior if the GMSC does not support the T-

CSI phase: is release-call or continue-call
Phase1 Set GHLRSCF

Send CCH indicates whether to send the CCH (CAP1) to the

VLR
Phase2 Set GHLRSCF

BS Codes Criteria basic service [group] codes criteria

vector (0 -5)
Phase3 Set GHLRSCF

BS Codes Criteria basic service [group] codes criteria

vector (0 -5)
Phase3 Set GHLRSCF




Criteria vector (0 -
5)
Phase3 Set GHLRSCF


Criteria vector (0 -
5)
9.9.2 Interactions
T-CSI interacts with system Table GHLRSCF.
Each SCF Name must be an entry from the SCF_NAME column in system Table GHLRSCF.
9.10 Translations Information Flag CSI

Translations Information Flag CSI (TIF-CSI) datafill defines that the usual GSM (conforming to E164)
number checks on forwarding-to numbers are suppressed.
The Kapsch HLR implements TIF-CSI as a dataitem of O-CSI (FTN Checks). See “Originating CSI” on
page 129.
9.11 Unstructured Supplementary Service Data CSI

Unstructured Supplementary Service Data CSI (USSD-CSI) datafill defines how the PUSSR (Process
Unstructured Supplementary Service Request) message is handled.
9.11.1 Datafill
The USSD-CSI data syntax is detailed in the following table. The IDs are a vector; at least one ID must be
datafilled. See “Data vectors” on page 27 for more information on vectors. The following intra-service
validations apply.
Duplicate IDs are not allowed.
Table 147 USSD-CSI data syntax

IDs vector (1 -10) 1 -10 characters 9 are optional
USSD-CSI field descriptions are provided in the following table.


Table 148 USSD-CSI field descriptions
ID an ID, defined in system Table GHLRUSSD
9.11.2 Interactions
USSD-CSI interacts with system Table GHLRUSSD.
Each ID must be an entry from the USSD_STR.UCSI_ID field in system Table GHLRUSSD; also, each ID
must be from a different USSD_STR from system Table GHLRUSSD. Each USSD_STR can have
multiple UCSI_IDs.

10 Location Services
Location Services (LCS) provide value-added, vicinity-specific services to the subscriber.
10.1 Navigation
• “LCS classes” on page 141
• “LCS Autonomous Self Location” on page 141
• “LCS Basic Self Location” on page 142
• “LCS Call Related” on page 142
• “LCS Call Unrelated” on page 144
• “LCS GMLCs” on page 145
• “LCS PLMN Operator145” on page 145
• “LCS Transfer to Third Party” on page 146
• “LCS Universal” on page 147
10.2 LCS classes

Location services are composed of four privacy classes and three mobile-originating (MO) classes, as
shown in the following table: Table 149 Location Services classes on page 141. Privacy classes indicate
what type of clients are allowed to make location requests. MO classes indicate whether/how the
subscriber can make MO location requests. Each privacy/MO class is treated as a distinct service. LCS
datafill is supplemented by a list of Gateway Mobile Location Centres (GMLCs); they are treated as a
separate profile component. See “LCS GMLCs” on page 145.
Table 149 Location Services classes
Class Type See section

Autonomous Self Location MO “LCS Autonomous Self Location” on page 141
Basic Self Location MO “LCS Basic Self Location” on page 142
Call Related Privacy “LCS Call Related” on page 142
Call Unrelated Privacy “LCS Call Unrelated” on page 144
PLMN Operator Privacy “LCS PLMN Operator145” on page 145
Transfer to Third Party MO “LCS Transfer to Third Party” on page 146
Universal Privacy “LCS Universal” on page 147
10.3 LCS Autonomous Self Location

The LCS Autonomous Self Location class specifies that the subscriber does not need to interact with the
network for each location request. A single interaction enables the subscriber to obtain multiple location
requests during a predetermined period of time.
10.3.1 Datafill
The LCS Autonomous Self Location data syntax is detailed in the following table.

Table 150 LCS Autonomous Self Location data syntax

Active Boolean
LCS Autonomous Self Location field descriptions are provided in the following table.
Table 151 LCS Autonomous Self Location field descriptions
Active whether this class is active
10.3.2 Interactions
None
10.4 LCS Basic Self Location

The LCS Basic Self Location class specifies that the subscriber needs to with the network for each
location request.
10.4.1 Datafill
The LCS Basic Self Location data syntax is detailed in the following table.
Table 152 LCS Basic Self Location data syntax

Active Boolean
LCS Basic Self Location field descriptions are provided in the following table.
Table 153 LCS Basic Self Location field descriptions
10.4.2 Interactions
None
10.5 LCS Call Related

The LCS Call Related class allows an LCS client to request the subscriber’s location if the subscriber
originated a call to the client and the call is still established.
10.5.1 Datafill
The LCS Call Related data syntax is detailed in the following table. There are two external client name

vectors. For more information on vectors, see “Data vectors” on page 27. The following intra-service
validations apply.
Duplicate external client names are not allowed. Names from both vectors are pooled together for this
check.
Table 154 LCS Call Related data syntax

Active Boolean
Notification To User LOC_NOT_ALLOW

- Location is not allowed
LOC_ALLOW_WITHOUT_NOTIF
- Location is not allowed without notification
LOC_ALLOW_WITH_NOTIF
- Location is allowed with notification
NOTIF_PRVCY_LOC_IF_NO_RSP
-Location with notification and privacy
verification; location allowed if no response
NOTIF_PRVCY_LOC_REST_IF_NO_RSP
verification; location restricted if no response
External Client 1 -8 characters All 5 are optional.

Names vector (0 -5)
Extended External 1 -8 characters All 35 are optional.

Client Names vector
(0 -35)
LCS Call Related field descriptions are provided in the following table.
Table 155 LCS Call Related field descriptions
Notification To User the notification to the user
External Client Name external client name, defined in system Table GHLRR4EC
Extended External Client Name external client name, defined in system Table GHLRR4EC
(The term extended" is simply used to identify a separate
vector of names.) "
10.5.2 Interactions
LCS Call Related interacts with GMLCs and LCS Call Unrelated.
GMLCs can only be provisioned if at least one of LCS Call Related/LCS Call Unrelated is also
provisioned.

10.6 LCS Call Unrelated

LCS Call Unrelated class allows the LCS client to be defined in such a way that they are able to request
the subscriber’s location.
10.6.1 Datafill
The LCS Call Unrelated data syntax is detailed in the following table. There are two external client name
vectors. For more information on vectors, see “Data vectors” on page 27. The following intra-service
validations apply.
Duplicate external client names are not allowed. Names from both vectors are pooled together for this
check.
Table 156 LCS Call Unrelated data syntax

Active Boolean
Notification To User LOC_NOT_ALLOW

- Location is not allowed
LOC_ALLOW_WITHOUT_NOTIF
- Location is not allowed without notification
LOC_ALLOW_WITH_NOTIF
- Location is allowed with notification
NOTIF_PRVCY_LOC_IF_NO_RSP
verification; location allowed if no response
NOTIF_PRVCY_LOC_REST_IF_NO_RSP
verification; location restricted if no response
External Client Names 1 -20 characters All 5 are optional.

vector (0 -5)
Extended External Client 1 -8 characters All 35 are optional.

Names vector (0 -35)
LCS Call Unrelated field descriptions are provided in the following table.
Table 157 LCS Call Unrelated field descriptions
Notification To User the notification to the user
External Client external client name, defined in system Table GHLRLSEC

Name
Extended External external client name, defined in system Table GHLRR4EC. The term
Client Name “extended" is simply used to identify a separate vector of names.
10.6.2 Interactions
LCS Call Related interacts with GMLCs and LCS Call Related.

provisioned.
10.7 LCS GMLCs

The GMLCs component provides the Gateway Mobile Location Centers used by LCS Call Related and
LCS Call Unrelated.
10.7.1 Datafill
The LCS GMLCs data syntax is detailed in the following table. The GMLC Names are a vector. See “Data
vectors” on page 27 for more information on vectors. The following intra-service validations apply.
• At least one GLMC Name must be datafilled.

• Duplicate GLMC Names are not allowed.
Table 158 LCS GMLCs data syntax

GMLC Names vector (1 -5) 1 -20 characters 4 are optional.
LCS GMLCs field descriptions are provided in the following table.
Table 159 LCS GMLCs field descriptions
GMLC Name a Gateway Mobile Location Center name, an entry from
system Table GHLRGMLC
10.7.2 Interactions
LCS GMLCs interact with LCS Call Related and LCS Call Unrelated.
provisioned.
10.8 LCS PLMN Operator

The LCS PLMN Operator class allows positioning by specific types of clients indicated in the subscriber’s
privacy profile.
10.8.1 Datafill
The LCS PLMN Operator data syntax is detailed in the following table. The following dataitems are known
as Internal Client IDs (ICIDs): Broadcast, OMH, OMV, Anonymous, Target MS. The following intra-service
validations apply.
At least one of the ICIDs must be true: Broadcast, OMH, OMV, Anonymous, Target MS.

Table 160 LCS PLMN Operator data syntax

Active Boolean
Broadcast Boolean
OMH Boolean
OMV Boolean
Anonymous Boolean
Target MS Boolean
LCS PLMN Operator field descriptions are provided in the following table.
Table 161 LCS PLMN Operator field descriptions
Active indicates whether this class is active
Broadcast indicates whether an LCS client broadcasting location

related information is allowed to locate the MS
OMH indicates whether an O and M LCS client in the HPLMN is

allowed to locate the MS
OMV indicates whether an O and M LCS client in the VPLMN is

allowed to locate the MS
Anonymous indicates whether an LCS client recording anonymous

location information is allowed to locate the MS
Target MS indicates whether an LCS client supporting a bearer

service, teleservice, or supplementary service to target the
MS is allowed to locate the MS
10.9 Interactions
None
10.10 LCS Transfer to Third Party

The LCS Transfer to Third Party class specifies that the subscriber’s location is transferred to another
LCS client.
10.10.1 Datafill
LCS Transfer to Third Party data syntax is detailed in the following table.

Table 162 LCS Transfer to Third Party data syntax

Active Boolean
LCS Transfer to Third-Party field descriptions are provided in the following table.
Table 163 LCS Transfer to Third Party field descriptions
10.10.2 Interactions
None
10.11 LCS Universal

The LCS Universal class allows all LCS clients to request the subscriber’s location.
10.11.1 Datafill
The LCS Universal data syntax is detailed in the following table..
Table 164 LCS Universal data syntax

Active Boolean
LCS Universal field descriptions are given in the following table.
Table 165 LCS Universal field description
10.11.2 Interactions
None

11 GPRS PDP context IDs

Provisioning General Packet Radio Service (GPRS) makes the subscriber a GPRS network subscriber.
The GPRS datafill allows Packet Data Protocol (PDP) context IDs to be specified for the subscriber.
11.1 Navigation
11.2 Datafill
The GPRS data syntax is detailed in the following table. Each of the Context ID sets is optional.
Table 166 GPRS data syntax

Context ID1 Set PDP Name 1 -16 characters
PDP Static Address 1 -63 characters Optional

(0..9, dot)

(0..9, dot)

(0..9, dot)
PDP Static Address Optional

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)


(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

(0..9, dot)

GPRS field descriptions are provided in the following table.
Table 167 GPRS field descriptions
Context ID1 Set PDP Name PDP name for this context ID, defined in
system
Table GHLRPDP
PDP Static Address PDP static address for this context ID, can be
IPv4, IPv6, or X25 format
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP

system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP

system
Table GHLRPDP
system
Table GHLRPDP
system
Table GHLRPDP
11.2.1 Interactions
GPRS interacts with Auth data, GPRS-CSI, and system tables GHLRPDP and GHLRALG, as follows:
• GPRS must be provisioned for GPRS-CSI to be provisioned.

• For each Static Address datafilled, their format is checked against the PDP type.
Determine the PDP type by looking up the PDP Name in system Table GHLRPDP and
checking the PDPTYPE (FORMAT) field.
– For IPv4 types, the address must be in the format "x.x.x.x", where "x" is (0-255).
– For IPv6 types, the address must be in the format "x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x",
where each of the 16 x’s is (0-255).
– For X25 types, the address must be 1 - 14 digits.
– For PPP types, the address must not be datafilled.
• If the subscriber is 3G, then all PDP Names must have ExtQoS and
– The determination of 2G/3G requires Auth data and system Table GHLRALG. See
“Determination of 2G/3G algorithm” on page 32.

12 Other services
Other services are those that do not fit within the following categories:
• basic services
• supplementary services
• CAMEL service
• Location Services
• GPRS
A list of these services is given in the following table.
Table 168 Other services

CLIN Calling Line Identification “Calling Line Identification
Replacement Number Replacement Number” on page 153
EA Equal Access “Equal Access” on page 154
Proprietary IN Proprietary Intelligent Network “Proprietary Intelligent Network
service service” on page 154
12.1 Navigation
• “Calling Line Identification Replacement Number” on page 153
• “Equal Access” on page 154
• “Proprietary Intelligent Network service” on page 154
12.2 Calling Line Identification Replacement Number

Provisioning Calling Line Identification Replacement Number (CLIN) enables CLI Replacement Number
functionality for the subscriber. CLIN allows an alternative number to be used for TPHNY’s CLI, that is not
TPHNY’s actual MSISDN. The CLIN service is distinct and quite different from the common use of the
word CLIN as a calling line ID number. CLIN is an Kapsch-proprietary service.
12.2.1 Datafill
CLIN data syntax is detailed in the following table.
Table 169 CLIN data syntax

CLI 1 to 15 digits
CLIN field descriptions are provided in the following table.


Table 170 CLIN field descriptions
CLI the replacement calling line identity for telephony
12.2.2 Interactions
CLIN interacts with TPHNY.
TPHNY must be provisioned for CLIN to be provisioned.
12.3 Equal Access

Equal Access (EA) datafill allows a primary interexchange carrier to be given to the subscriber. EA is an
12.3.1 Datafill
EA data syntax is detailed in the following table.
Table 171 EA data syntax

PIC 4 digits
EA field descriptions are provided in the following table.
Table 172 EA field descriptions
PIC Primary Interexchange Carrier
12.3.2 Interactions
None
12.4 Proprietary Intelligent Network service

Proprietary Intelligent Network (Proprietary IN) service provides Kapsch-proprietary IN, allowing an IN
platform to be specified for both originating and terminating calls.
12.4.1 Datafill
The Proprietary IN data syntax is detailed in the following table.

Table 173 Proprietary IN data syntax

INORIG number: 0 -1023 Optional
INTERM number: 0 -1023 Optional
Proprietary IN field descriptions are given in the following table.
Table 174 Proprietary IN field descriptions
INORIG IN index for IN platform originating calls
INTERM IN index for IN platform terminating calls
12.4.2 Interactions
None
– The determination of PDP ExtQoS requires you to look up the PDP Name in system Table
GHLRPDP and check whether the EXTQOS field is null or datafilled.

13 Other components
The concept of other components is introduced in “Data model and validations” on page 22. A list of these
components is provided in the following table.
Table 175 Other components

HST Home Subscriber Trace “Home Subscriber Trace” on page 156
SIMR SIM Replacement “SIM Replacement” on page 157
13.1 Navigation
• “Home Subscriber Trace” on page 156
• “SIM Replacement” on page 157
13.2 Home Subscriber Trace

Home Subscriber Trace (HST) is used to track subscribers within the HPLMN.
13.2.1 Datafill
The HST data syntax is detailed in the following table. The following intra-service validations apply.
None of the dataitems can be changed once provisioned. However, you can deprovision HST.
Table 176 HST data syntax

Trace Reference number: 0 - 65535
DestinationOperator 0 -38 digits (0..9)

Maintenance Center
Destination (OMC)
Trace Type number: 0 - 255
HST field descriptions are provided in the following table.
Table 177 HST field descriptions
Trace Reference trace reference (used as an identifier)
OMC Destination Operator Maintenance Center Destination address
Trace Type trace type identification


13.2.2 Interactions
None

A maximum of 1024 subscribers can be provisioned with HST at any one time.
13.3 SIM Replacement

A SIM Replacement (SIMR) entry is used to set up a relationship between two IMSIs, whereby one IMSI
will replace an old IMSI at a certain date. The Kapsch HLR specifies that the new IMSI must exist in the
database, thereby placing restrictions on the new IMSI’s profile.
ATTENTION
Kapsch strongly recommends that the SIMR documentation is used to set up
SIMR relationships; the information in the present guide is provided as a guide
only.
13.3.1 Datafill
SIMR data syntax is detailed in the following table. The following intra-service validations apply.
• The new IMSI must be present in the database.

• The old IMSI must be present in the database. This is the subscriber’s current profile.
• The new IMSI and old IMSI must be different.
• The Activation Date must not be datafilled if Option is FIXED.
• The Activation Date must be datafilled if Option is USER.
• If datafilled, the Activation Date must precede the Invocation Date.
Table 178 SIMR data syntax

New IMSI 6 -15 digits
Old IMSI 6 -15 digits
Option {FIXED, USER}
Invocation Date Date (nearest hour)
Activation Date Date (nearest hour) Optional
SIMR field descriptions are provided in the following table.


Table 179 SIMR field description
New IMSI the new International Mobile Subscriber Identity, the
replacement IMSI for the subscriber
Old IMSI the old International Mobile Subscriber Identity, the current
IMSI for the subscriber
Option how the swapover will occur. The fixed option swaps IMSIs
on a (fixed) invocation date; the user option swaps IMSIs on
activation of the new IMSI (by means of using new SIM) or
on the invocation date if activation has not yet occurred.
Invocation Date the time the swapover will occur (For the user option, this
only applies if there was not an update location for the new
SIM/IMSI.)
Activation Date the time from which a subscriber can use its new SIM (and
hence an update location will trigger a SIMR swap)
13.3.2 Interactions
Because the Kapsch HLR requires the new IMSI to be present in the database, the following restrictions
have to apply to the new IMSI profile:
• The IMSI Status must not be ACTIVATED.

• If the IMSI Status is DEACTIVATED, all profile control data must be set to their defaults.
For more information, see “Profile control data” on page 33.
• No services can be provisioned.
• HST cannot be provisioned.
• There are several interactions with mated-pair:
– The new IMSI must not be SIMR blocked.
– The acting status for both old IMSI and new IMSI must match.
– The maintenance blocked status for old IMSI and new IMSI must match.
– Partition numbers for old IMSI and new IMSI must match and not be equal to zero.
The following requires you to check on the old IMSI: if the new IMSI is 3G (see “Determination of 2G/3G
algorithm” on page 32 for details), then the old IMSI’s GPRS PDPs (if any) must all have ExtQoS. For
more information, see “Interactions” on page 32.

• A maximum of 10,000 SIMR relationships can be set up at any one time.
• The new IMSI cannot be defined as an old IMSI in an existing SIMR relationship.
• The old IMSI cannot be defined as an old IMSI or new IMSI in an existing SIMR
relationship.

14 Suppression states
Each Basic Service Group (BSG) registration set of each BSG-supplement ary service has a suppression
state. These states are used in conjunction with registration and activation states within the network.
Suppression states are not part of the subscriber profile and are provided here as extra information.
Each time a BSG registration set is added or updated, its suppression state must be recalculated. This
can involve interactions with several other services. A suppression state only applies to activated
registration sets. The following supplementary services have suppression states: BICRoam, CFB,
CFNRc, CFNRy, and EXT.
Some Operator-Determined call Barrings (ODB) also have a single suppression state, although this is
sometimes called an "activation" state. Those ODBs are ODB BICRoam, ODB BAOCRoam, and ODB
HPLMN-specific categories.
Suppression state determination is provided for each service in their own subsection. The following
diagram shows all suppression interactions:
Figure 13 Service suppressions


14.1 Navigation
• “BICRoam suppression state determination” on page 160
• “CFB suppression state determination” on page 160
• “CFNRy suppression state determination” on page 161
• “CFU suppression state determination” on page 161
• “EXT suppression state determination” on page 161
• “ODB BICRoam suppression state determination” on page 162
• “ODB BAOCRoam suppression state determination” on page 162
• “ODB HPLMN-specific categories suppression state determination” on page 163
14.2 BICRoam suppression state determination

BICRoam suppression state determination is detailed in the following table.
Table 180 Determine BICRoam registration set suppression
Suppressed by Conditions
Service State
Subscriber Location N/A location is in HPLMN Country
CFU Activated and not none

Suppressed
14.3 CFB suppression state determination

CFB suppression state determination is detailed in the following table.
Table 181 Determine CFB registration set suppression
Service State
CFU Activated none (always suppressed)
BOIC Activated has GSM-FTNs and FTN is
international with regard to current
location
BOICexHC Activated has GSM-FTNs and FTN is not in
HPLMN and is international with
regard to current location
BICRoam Activated and Not does not have TIF-FTNs
Suppressed
ODB BAIC Provisioned does not have TIF-FTNs
ODB BICRoam Provisioned and Activated does not have TIF-FTNs

ODB BAOC Provisioned does not have TIF-FTNs

ODB BOIC Provisioned has GSM-FTNs and FTN is
international with regard to current
location
ODB BOICexHC Provisioned has GSM-FTNs and FTN is not in
HPLMN and is international with
regard to current location
ODB BAOCRoam Provisioned and Not does not have TIF-FTNs
Suppressed
ODB Prem Rate Provisioned has GSM-FTNs and FTN is barred for
categories the category in system Table
GHLRODB
ODB HPLMN Provisioned and Not has GSM-FTNs and FTN is barred for
Specific categories Suppressed the category in system Table
GHLRODB
14.4 CFNRy suppression state determination

CFNRy suppression state determination is identical to that of CFB. For more information, see Table 181
Determine CFB registration set suppression on page 160.
14.5 CFU suppression state determination

CFU suppression state determination is detailed in the following table.
Table 182 Determine CFB registration set suppression
Service State
ODB BAOC Provisioned does not have TIF-FTNs
ODB BOIC Provisioned has GSM-FTNs and FTN is international

with regard to HPLMN Country
ODB BOICexHC Provisioned has GSM-FTNs and FTN is international

with regard to HPLMN Country
ODB BAIC Provisioned does not have TIF-FTNs
ODB Prem Rate categories Provisioned has GSM-FTNs and FTN is barred for the
category in system Table GHLRODB
ODB HPLMN Specific Provisioned has GSM-FTNs and FTN is barred for the
categories category in system Table GHLRODB
14.6 EXT suppression state determination

EXT suppression state determination is detailed in the following table. EXT is a special case in that every
MSISDN has a suppression state, rather than each registration set.

Table 183 Determine EXT MSISDN suppression
Service State
ODB BAOC Provisioned All MSISDNs except Pilot MSISDNs are

suppressed only if office parameter
EXTODBON (GHLRPARM) is true.
ODB BOIC Provisioned MSISDNs international with regard to

HPLMN Country are suppressed. Pilot
MSISDNs will never be suppressed
because they are in HPLMN.
ODB BOICexHC Provisioned MSISDNs international with regard to

HPLMN Country are suppressed. Pilot
MSISDNs will never be suppressed
because they are in HPLMN.
ODB BAIC Provisioned All MSISDNs are suppressed.
ODB Prem Rate categories Provisioned MSISDNs that are barred for ODB Prem
Rate are suppressed (using system
Table GHLRODB).
ODB HPLMN Specific Provisioned MSISDNs that are barred for ODB
categories HPLMN Specific are suppressed (using
system Table GHLRODB).
14.7 ODB BICRoam suppression state determination

ODB BICRoam suppression state determination is detailed in the following table. ODB suppression states
can also be called activation states, and, therefore, "not suppressed" is equivalent to "activated".
Table 184 Determine ODB BICRoam suppression
Service State
14.8 ODB BAOCRoam suppression state determination

ODB BAOCRoam suppression state determination is detailed in the following table. ODB suppression
states can also be called activation states; therefore "not suppressed" is equivalent to "activated".
Table 185 Determine ODB BAOCRoam suppression
Service State

14.9 ODB HPLMN-specific categories suppression state determination

ODB HPLMN-specific categories suppression state determination is detailed in the following table. ODB
suppression states can also be called activation states; therefore, "not suppressed" is equivalent to
"activated".
Table 186 Determine ODB HPLMN-specific categories suppression
Service State

15 Database Implementation
The subscriber data schema comprises 40 tables and stores authentication data, profile control data,
services data, and SIMR data. The schema is a logical database composed of Oracle views, based on
the actual physical tables. This document uses the term "table" when referring to the views. The schema
tables are listed in Table 190 Subscriber data schema tables on page 168, and presented in a diagram in
Figure 14 Oracle schema diagram on page 171. The routing schema are described later in “Routing
schema” on page 224.
Most tables store just one particular service, and are named sub_<service>. Other tables store more than
one service, while some services are actually datafilled across more than one table. Exceptions to the
sub_<service> format are as follows:
• Three tables store more than one service. Table sub_odbs stores all ODBs. Table
sub_basic_services stores all basic services. Table sub_imsi_ss stores all IMSI-SSs.
• Three services are split across more than one table. CUG is datafilled in table
sub_cug_subscription and table sub_cug_feature. GPRS is datafilled in table
sub_gprs_prov and sub_gprs_pdps. LCS can be seen as one service, or a collection of
services; it is datafilled in six tables all prefixed with sub_lcs_.
Profile control data, along with some service data, is grouped into one table, sub_general.
15.1 Navigation
• “Datatypes in Database” on page 165
• “Section structure” on page 167
• “Schema tables listing and diagram” on page 168
• “Guide to table sections” on page 172
• “Table SUB_AUTH” on page 173
• “Table SUB_GENERAL” on page 174
• “Table SUB_ODBS” on page 175
• “Table SUB_BASIC_SERVICES” on page 176
• “Table SUB_BAIC” on page 177
• “Table SUB_BAOC” on page 178
• “Table SUB_BICROAM” on page 179
• “Table SUB_BOIC” on page 180
• “Table SUB_BOICEXHC” on page 181
• “Table SUB_CFB” on page 182
• “Table SUB_CFNRC” on page 183
• “Table SUB_CFNRY” on page 185
• “Table SUB_CFU” on page 186
• “Table SUB_COS” on page 187
• “Table SUB_CUG_FEATURE” on page 188
• “Table SUB_CUG_SUBSCRIPTION” on page 190

• “Table SUB_CW” on page 190

• “Table SUB_EXT” on page 191
• “Table SUB_IMSI_SS” on page 193
• “Table SUB_DCSI” on page 195
• “Table SUB_GPRS_CSI” on page 196
• “Table SUB_MCSI” on page 197
• “Table SUB_OCSI” on page 197
• “Table SUB_SMS_CSI” on page 203
• “Table SUB_SS_CSI” on page 204
• “Table SUB_TCSI” on page 204
• “Table SUB_USSD_CSI” on page 207
• “Table SUB_EA” on page 208
• “Table SUB_GPRS_PROV” on page 209
• “Table SUB_GPRS_PDPS” on page 210
• “Table SUB_LCS_CALL_RELATED” on page 210
• “Table SUB_LCS_CALL_UNRELATED” on page 212
• “Table SUB_LCS_GMLCS” on page 215
• “Table SUB_LCS_MOBILE_ORIGINATING” on page 216
• “Table SUB_LCS_PLMN_OPERATOR” on page 217
• “Table SUB_LCS_UNIVERSAL” on page 218
• “Table SUB_VBS” on page 218
• “Table SUB_VGCS” on page 222
• “Table SUB_SIMR” on page 224
• “Routing schema” on page 224
15.2 Datatypes in Database

The subscriber profile database is composed of a finite number of datatypes. They are listed in Table 187
Datatypes and their Oracle implementation on page 166 further down, including their mapping to Oracle
types. The "x" values indicate the maximum length of the particular string/enum/number. A discussion of
datatypes in the data model is provided in “Datatypes” on page 26.
The Dataitem syntax is described in the data model section of this document. The schema description in
the following sections provides the Oracle types for each dataitem (that is, column). Strings and enum
options are always stored in uppercase, as are booleans (TRUE and FALSE). Time dataitems can be to
the nearest day or hour and hence have two format types.
Data model definitions -------------------------------------------------------- Oracle schema definitions


Table 187 Datatypes and their Oracle implementation
Data model definitions Oracle schema definitions
Datatype Format Oracle type Syntax

Number m -n range number(x) number: m -n
String m -n characters varchar2(x) m -n characters (what chars)
Digit String m -n digits varchar2(x) m -n digits
Hex Digit String m digits varchar2(x) m hex digits
Enum {a, b, c, , z} varchar2(x) enum: A, B, C, Z
Boolean {true, false} varchar2(5) boolean
Time to nearest second varchar2(20) DD-Mon-YYYY 24HH:MM:SS

or hour
varchar2(17) DD-Mon-YYYY 24HH:MM
15.2.1 Vectors in Database

One column is assigned to each possible value, with a number appended to the Column name to
differentiate the different columns. For example, a nodes vector of one to four elements is represented by
columns node1, node2, node3, and node4. The number is simply there to differentiate the columns, it has
no other meaning because vectors are not ordered.
As elements are datafilled, they use up positions in numerical order (that is, 1 first, then 2, then 3, and
finally 4). If an element is removed, then the elements "after" that element shift down one position. See
the following table for an example of how this works. The initial state shows the vector as not being
datafilled. If two elements are added in the same transaction, then there is no guarantee of the order in
which they are datafilled. You cannot provision an element at an explicit position.
Table 188 Datafilling vectors example
Column name Initial State Add A Add B Add C Remove A Remove C

node1 null A A A B B
node2 null null B B C null
node3 null null null C null null
node4 null null null null null null
A small number of vectors are complex vectors; that is, the elements are actually structures that
themselves contain two or more elements. An example of such a vector is provided in the following table.
The vector has 1 - 3 structures, with each structure being composed of elements color and style.

Table 189 Complex vector example
Column name
color
style1
color
style2
color
style3
Vectors in the data model are discussed in “Data vectors” on page 27.
15.2.2 Sets in Database

All sets are named, and such names are used to qualify Column names belonging to a particular set. For
example, a set can be named Code A and have dataitems activated and option. The Column names will
be codeA_activated and codeA_option.
An additional boolean column is used to indicate whether the set is provisioned or not. It is named
<setname>_prov, or <setname>_reg. The _reg naming convention is used for services that have
registration data (as named by GSM specifications); the _prov convention is used for all other sets. If a
set-provisioned column is set to FALSE, then the set dataitems will always be all set to null.
Sets are introduced in “Data sets” on page 11.
15.3 Section structure

A schema guide is presented in “Guide to table sections” on page 172. A sample table section is provided
with explanations. There is also an overview of the datatypes used in the subscriber database.
Tables are described in detail starting with “Table SUB_AUTH” on page 173. The order of tables is as
follows:
• Authentication Data
• General Data
• ODBs
• Basic Services
• Supplementary Services
– Barrings
- Incoming (alphabetical)
- Outgoing (alphabetical)
– Call Forwards (alphabetical)
– Other BSG-SSs (alphabetical)
– IMSI-SSs
• CAMEL Services (alphabetical)
• CLIN

• EA
• GPRS
• LCS
• GSMR Basic Services
• SIMR
15.4 Schema tables listing and diagram

Subscriber profile data schema tables are listed in the following table. Indications of any changes in the
current release, brief descriptions, and page number references are given. A diagram of the schema is
provided in Figure 14 Oracle schema diagram on page 171. Services that span multiple tables are
indicated.
Table 190 Subscriber data schema tables
Changed/
Table name UnChanged Description See section
sub_auth Unchanged mandatory table “Table SUB_AUTH” on page
storing authentication 173
data
sub_general Changed mandatory table “Table SUB_GENERAL” on
storing general data page 174
sub_odbs Unchanged stores ODB “Table SUB_ODBS” on page
provisioning statuses 175
sub_basic_se Unchanged stores all basic “Table
rvices service data SUB_BASIC_SERVICES” on
page 176
sub_baic Unchanged stores BAIC data “Table SUB_BAIC” on page
177
sub_baoc Unchanged stores BAOC data “Table SUB_BAOC” on page
178
sub_bicroam Unchanged stores BICRoam “Table SUB_BICROAM” on
data page 179
sub_boic Unchanged stores BOIC data “Table SUB_BOIC” on page
180
sub_boicexhc Unchanged stores BOICexHC “Table SUB_BOICEXHC” on
data page 181
sub_cfb Unchanged stores CFB data “Table SUB_CFB” on page
182
sub_cfnrc Unchanged stores CFNRc data “Table SUB_CFNRC” on
page 183
sub_cfnry Unchanged stores CFNRy data “Table SUB_CFNRY “ on
page 185
sub_cfu Unchanged stores CFU data “Table SUB_CFU” on page
186
sub_cos Unchanged stores COS data “Table SUB_COS” on page

187
sub_cug_feat Unchanged stores CUG feature “Table
ure data SUB_CUG_FEATURE” on
page 188
sub_cug_sub Unchanged stores CUG “Table
scription subscription data SUB_CUG_SUBSCRIPTION
” on page 190
sub_cw Unchanged stores CW data “Table SUB_CW” on page
190
sub_ext Unchanged stores EXT data “Table SUB_EXT” on page
191
sub_imsi_ss Changed stores all IMSI-SS “Table SUB_IMSI_SS” on
data page 193
sub_dcsi Unchanged stores D-CSI data “Table SUB_DCSI” on page
195
sub_gprs_csi Unchanged stores GPRS-CSI “Table SUB_GPRS_CSI” on
data page 196
sub_mcsi Unchanged stores M-CSI data “Table SUB_MCSI” on page
197
sub_ocsi Unchanged stores O-CSI data “Table SUB_OCSI” on page
197
sub_sms_csi Unchanged stores SMS-CSI data “Table SUB_SMS_CSI” on
page 203
sub_ss_csi Unchanged stores SS-CSI data “Table SUB_SS_CSI” on
page 204
sub_tcsi Unchanged stores T-CSI data “Table SUB_TCSI” on page
204
sub_ussd_csi Unchanged stores USSD-CSI “Table SUB_USSD_CSI” on
data page 207
sub_clin Unchanged stores CLIN data “Table SUB_CLIN” on page
208
sub_ea Unchanged stores EA data “Table SUB_EA” on page
208
sub_gprs_pro Unchanged stores GPRS “Table SUB_GPRS_PROV”
v provisioning on page 209
indications
sub_gprs_pd Unchanged stores GPRS data “Table SUB_GPRS_PDPS”
ps on page 210
sub_lcs_call_ Unchanged stores LCS call- “Table
related related privacy class SUB_LCS_CALL_RELATED
data ” on page 210
sub_lcs_call_ Unchanged stores LCS call- “Table
unrelated unrelated privacy SUB_LCS_CALL_UNRELAT
class data ED” on page 212
sub_lcs_gmlc Unchanged stores LCS GMLCs “Table SUB_LCS_GMLCS”
s on page 215

sub_lcs_mobi Unchanged stores LCS mobile- “Table

le originating data SUB_LCS_MOBILE_ORIGI
_originating NATING” on page 216
sub_lcs_plmn Unchanged stores LCS PLMN “Table
_ operator operator privacy SUB_LCS_PLMN_OPERAT
class data OR” on page 217
sub_lcs_univ Unchanged stores LCS universal “Table
ersal privacy class data SUB_LCS_UNIVERSAL” on
page 218
sub_vbs Unchanged stores VBS data “Table SUB_VBS” on page
218
sub_vgcs Unchanged stores VGCS data “Table SUB_VGCS” on page
222
sub_simr Unchanged stores SIMR “Table SUB_SIMR” on page
relationships data 224
The Oracle Schema is as follows:


Figure 14 Oracle schema diagram


15.5 Guide to table sections

Case conventions used in this document are outlined in “Case conventions” on page 172. An example
table section with help is provided in “Table EXAMPLE_TAB” on page 172. The schema tables are each
presented in their own section, starting with “Table SUB_AUTH” on page 173.
15.5.1 Case conventions

The table names and Column names in Oracle are case-insensitive. This document uses the following
conventions for these names, primarily to aid readability. Names are presented in either all uppercase or
all lowercase, and never a mix of the two. Oracle internally stores all names as uppercase. This affects
SQL select statements for instance.
Table names in headings and paragraphs are all uppercase (SUB_GENERAL). In tables, they are bold
italic lowercase (sub_general).
Column names in paragraph text are italic lowercase (imsi_status). In tables, they are either lowercase
(imsi_status) or all uppercase (IMSI_STATUS).
System table names in paragraph text are bold small uppercase (GHLRDCFB), while system table
Column names in paragraph text are small uppercase (DCFID).
15.5.2 Table EXAMPLE_TAB

An introduction briefly describes the table, indicating which services the table stores.
Table 191 Table EXAMPLE_TAB information
Number of Columns the total number of columns in the table, including key columns
Rows for each the range for the number of rows any one subscriber can have,
subscriber and whether they are mandatory or optional
Primary Key the primary key column(s)

Information tables (see the following table for an example) contain
general information about the table, such as the number of
columns, the rows for each subscriber, and the primary key.
Foreign Keys foreign key columns and what tables/columns they reference
Indexes the indexes on this table
Also See Table(s) used when a service spans multiple tables; lists the other tables
Field details tables (see the following table for an example) show all column (that is, field/dataitem)
names, with their Oracle type and constraints. Two examples are also provided. Some tables can have
multiple rows for each subscriber, but the examples are obviously limited to showing a single row each.

Table 192 Table EXAMPLE_TAB field details
Column name Oracle type Constraints Example 1 Example 2

column_a (This is the Oracle type Oracle Example Alternative
the primary key, for this column, constraints, the datafill set of
identified by the the examples example being example
grey background; being varchar2(x), “not null”, datafill
the primary key number(x), and which means
can be composed date; x indicates the column
of multiple the max number must be
columns.) of digits/chars datafilled
column_b as above as above as above as above
column_c as above as above as above as above
column_d as above as above as above as above
15.6 Table SUB_AUTH

This table stores authentication data for both 2G and 3G subscribers. This is the primary subscriber table
and denotes the existence of a subscriber. A row in this table is mandatory for all subscribers. General
table information is provided in the following table.
Table 193 Table SUB_AUTH information
Number of Columns 3
Rows for each subscriber One Mandatory
Primary Key IMSI
Foreign Keys None
Indexes IMSI
Also See Table(s) None
Field details for SUB_AUTH are provided in the following table, along with example values. Field
descriptions and validations are given in “Authentication data” on page 31.
Table 194 Table SUB_AUTH field details
Column
name Oracle type Constraints Example 1 Example 2
imsi varchar2(15) not null 456231234567890 234109920024844
algorithm number(3) not null 2 101
opc varchar2(32) null 11AB11E111CD21231E1

11544141132A1

15.7 Table SUB_GENERAL

This table stores miscellaneous provisioning data, such as profile control data and timestamps. A row in
this table is mandatory for all subscribers. General table information is provided in the following table.
Table 195 Table SUB_General information
Number of Columns 21
Primary Key IMSI
Foreign Keys IMSI to table sub_auth, column IMSI
HLR_ID to table hlrs, column ID

Indexes IMSI
Field details for SUB_GENERAL appear in “Table SUB_GENERAL” on page 174, along with example
values. Field descriptions and validations are provided in the following sections:
• imsi_status, cust_group, and ncos, “IMSI Status” on page 36

• roaming_ent, “Roaming Entitlement” on page 38
• category, ”Category” on page 34
• bicctrl, bocctrl, “Barring Control” on page 33
• password, “Password” on page 38
• inorig, interm, “Proprietary Intelligent Network service” on page 154
• soa_prov, “Suppression of Announcements provisioning” on page 39
• nam, “Network Access Mode” on page 37
• lmu, “Location Measurement Unit” on page 37
The hlr_id shows the HLR Core that the subscriber resides on. See “Table HLRS” on page 225. Column
network_active indicates whether the subscriber has had its first network activity.
The creation_time is a timestamp for creation of the subscriber in the database. The sub_last_modified is
a timestamp for the last modification made to the subscriber’s profile in the Oracle database; null change
provisioning requests will not update the subscriber’s profile in the database and so will not update this
timestamp.
The imsi_status_last_modified is a timestamp for the last modification to the imsi_status; a null change
will not update the timestamp. The imsi_status_last_activated is a timestamp for when the imsi_status
was last set to ACTIVATED; a null change will not update the timestamp.
Table 196 Table SUB_GENERAL field details

imsi_status varchar2(11) not null DEACTIVATED ACTIVATED
cust_group number(4) null null
ncos number(3) null null
hlr_id varchar2(10) not null 1234567890 1231231234

roaming_ent varchar2(16) not null UNKW MYHPLMN

category varchar2(12) not null ORDINARY ORDINARY
bicctrl varchar2(8) not null OPERATOR USER
bocctrl varchar2(8) not null OPERATOR OPERATOR
password varchar2(4) not null 1234 1234
inorig number(4) null 567
interm number(4) null 567
soa_prov varchar2(5) not null FALSE TRUE
nam varchar2(12) not null MSC_ONLY SGSN_AND_MSC
lmu varchar2(5) not null FALSE TRUE
network_active varchar2(5) not null FALSE TRUE
creation_time varchar2(20) not null 25-Dec-2003 05-Jan-2004
21:30:58 21:30:58
sub_last_modif varchar2(20) not null 25-Dec-2003 29-Mar-2004
i ed 23:01:20 07:31:18
imsi_status_la varchar2(20) not null 25-Dec-2003 25-Feb-2004
st _ modified 21:30:58 15:30:00
imsi_status_la varchar2(20) null 2/25/2004 15:30
st_ activated
varchar2(15) null 1010101010
secondary_hlr sec_hlr_id
_id
15.8 Table SUB_ODBS

This table stores Operator-Determined Barrings (ODB) provisioning statuses. A row in this table is
mandatory for all subscribers. General table information is provided in the following table.
Table 197 Table SUB_ODBS
Primary Key IMSI
Indexes IMSI
Field details for SUB_ODBS appear in the following table, along with example values. ODB validations
are discussed in “Operator-determined barrings” on page 122.

Table 198 Table SUB_ODBS field details

7890 4844
odb_baic_prov varchar2(5) not null TRUE FALSE
odb_bicroam_prov varchar2(5) not null FALSE TRUE
odb_boac_prov varchar2(5) not null FALSE FALSE
odb_boic_prov varchar2(5) not null FALSE FALSE
odb_boicexhc_prov varchar2(5) not null FALSE TRUE
odb_boacroam_prov varchar2(5) not null FALSE FALSE
odb_incoming varchar2(7) BAIC BICROAM
odb_outgoing varchar2(8) null BOICEXHC
odb_baect_prov varchar2(5) not null FALSE FALSE
odb_bchdect_prov varchar2(5) not null FALSE FALSE
odb_bintect_prov varchar2(5) not null FALSE FALSE
odb_bdbcect_prov varchar2(5) not null FALSE FALSE
odb_premrate_info_prov varchar2(5) not null FALSE TRUE
odb_premrate_ent_prov varchar2(5) not null FALSE TRUE
odb_hplmnspec1_prov varchar2(5) not null FALSE TRUE
odb_hplmnspec2_prov varchar2(5) not null FALSE FALSE
odb_bcissmgt_prov varchar2(5) not null FALSE FALSE
odb_bccfmgt_prov varchar2(5) not null FALSE TRUE
15.9 Table SUB_BASIC_SERVICES

This table stores all basic services. One row is datafilled for each provisioned basic service. General table
information is provided in the following table.
Table 199 Table SUB_BASIC_SERVICES information
Number of Columns 7
Rows for each Zero to 19 (A theoretical maximum and very unlikely in reality;
subscriber a typical subscriber will have one to five rows.)
One row for each basic service

Primary Key IMSI+BS
Indexes IMSI+BS
MSISDN

Field details for SUB_BASIC_SERVICES appear in the following table, along with example values. Show
one row only; a subscriber can have multiple rows, of course. Field descriptions and validations are
provided from “Basic services” on page 40 to “Voice Group Call Service” on page 69.
Table 200 Table SUB_BASIC_SERVICES field details

bs varchar2(8) not null TPHNY FAX3
msisdn_cc varchar2(3) not null 61 44
msisdn_ndc varchar2(13) not null 123 7
msisdn_sn varchar2(13) not null 555555 123456
msisdn varchar2(15) not null 61123555555 447123456
bci number(3) null 123
15.10 Table SUB_BAIC

This table stores BAIC data. A row in this table indicates that the subscriber has BAIC provisioned.
General table information is provided in the following table.
Table 201 Table SUB_BAIC information
Rows for each Zero or One
subscriber One row if BAIC is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_BAIC appear in the following table, along with example values. BAIC datafill is
composed of six sets, each with a registered status (_reg fields). For more information on sets, see “Sets
in ” on page 167. Field descriptions and validations are provided in “Voice Group Call Service” on
page 69.

Table 202 Table SUB_BAIC field details

spch_reg varchar2(5) not null FALSE TRUE
spch_act varchar2(5) null TRUE
auxspch_reg varchar2(5) not null FALSE FALSE
auxspch_act varchar2(5) null null
sms_reg varchar2(5) not null FALSE TRUE
sms_act varchar2(5) null FALSE
cda_reg varchar2(5) not null FALSE FALSE
cda_act varchar2(5) null null
cds_reg varchar2(5) not null FALSE FALSE
cds_act varchar2(5) null null
fax_reg varchar2(5) not null FALSE FALSE
fax_act varchar2(5) null null
15.11 Table SUB_BAOC

This table stores BAOC data. A row in this table indicates that the subscriber has BAOC provisioned.
Table 203 Table SUB_BAOC information
subscriber One row if BAOC is provisioned
Primary Key IMSI

Indexes IMSI
Field details for SUB_BAOC appear in the following table, along with example values. BAOC datafill is
composed of seven sets, each with a registered status (_reg fields). For more information on sets, see
“Sets in ” on page 167. Field descriptions and validations are provided in “Barring of All Outgoing Calls”
on page 77.

Table 204 Table SUB_BAOC field details

sms_reg varchar2(5) not null FALSE TRUE
vgs_reg varchar2(5) not null FALSE TRUE
vgs_act varchar2(5) null TRUE
15.12 Table SUB_BICROAM

This table stores BICRoam data. A row in this table indicates that the subscriber has BICRoam
provisioned. General table information is provided in the following table.
Table 205 Table SUB_BAOC information

subscriber One row if BICRoam is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_BICROAM appear in the following table, along with example values. BICRoam
datafill is composed of six sets, each with a registered status (_reg fields). For more information on sets,
see “Sets in ” on page 167. Field descriptions and validations are provided in “Barring of Incoming Calls
when Roaming outside HPLMN country” on page 78.

Table 206 Table SUB_BICROAM field details

sms_reg varchar2(5) not null FALSE FALSE
sms_act varchar2(5) null null
fax_reg varchar2(5) not null FALSE TRUE
15.13 Table SUB_BOIC

This table stores BOIC data. A row in this table indicates that the subscriber has BOIC provisioned.
Table 207 Table SUB_BOIC information
Rows for each subscriber Zero or One
One row if BOIC is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_BOIC appear in the following table, along with example values. BOIC datafill is
in ” on page 167. Field descriptions and validations are provided in “Barring of Outgoing International
Calls” on page 79.

Table 208 Table SUB_BOIC field details

cda_reg varchar2(5) not null FALSE TRUE
cda_act varchar2(5) null FALSE
fax_act varchar2(5) null TRUE
15.14 Table SUB_BOICEXHC

This table stores BOICexHC data. A row in this table indicates that the subscriber has BOICexHC
Table 209 Table SUB_BOICEXHC information

subscriber One row if BOICeXHC is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_BOICEXHC are provided in the following table, along with example values.
BOICexHC datafill is composed of six sets, each with a registered status (_reg fields). For more
information on sets, see “Sets in ” on page 167. Field descriptions and validations are provided in “Barring
of Outgoing International Calls except to HPLMN Country” on page 81.

Table 210 Table SUB_BOICEXHC field details

auxspch_reg varchar2(5) not null FALSE TRUE
auxspch_act varchar2(5) null TRUE
cds_reg varchar2(5) not null FALSE TRUE
cds_act varchar2(5) null TRUE
fax_act varchar2(5) null TRUE
15.15 Table SUB_CFB

This table stores CFB data. A row in this table indicates that the subscriber has CFB provisioned. General
Table 211 Table SUB_CFB information
One row if CFB is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_CFB are provided in the following table, along with example values. CFB datafill
includes five sets, each with a registered status (_reg fields). For more information on sets, “Sets in ” on
page 167. Field descriptions and validations are provided in “Call Forward when Busy” on page 82.
Table 212 Table SUB_CFB field details

ncp varchar2(4) not null NONF NF

nfp varchar2(4) not null NONF NFWN

dcf_id varchar2(20) null DCF_ID1
spch_noa varchar2(4) null INTL
spch_npi varchar2(4) null E164
spch_ftn varchar2(15) null 44123888888
auxspch_noa varchar2(4) null INTL
auxspch_npi varchar2(4) null E164
auxspch_ftn varchar2(15) null 44123888777
cda_noa varchar2(4) null null
cda_npi varchar2(4) null null
cda_ftn varchar2(15) null null
cds_noa varchar2(4) null null
cds_npi varchar2(4) null null
cds_ftn varchar2(15) null null
fax_noa varchar2(4) null null
fax_npi varchar2(4) null null
fax_ftn varchar2(15) null null
15.16 Table SUB_CFNRC

This table stores CFNRc data. A row in this table indicates that the subscriber has CFNRc provisioned.
Table 213 Table SUB_CFNRC information
subscriber One row if CFNRc is provisioned
Primary Key IMSI

Indexes IMSI
Field details for SUB_CFNRC are provided in the following table, along with example values. CFNRc
datafill includes five sets, each with a registered status (_reg fields). For more information on sets, see
“Sets in Database” on page 167. Field descriptions and validations are provided in “Call Forward when
Not Reachable” on page 87.
Table 214 Table SUB_CFNRC field details

dcf_id varchar2(20) null null

15.17 Table SUB_CFNRY

This table stores CFNRy data. A row in this table indicates that the subscriber has CFNRy provisioned.
Table 215 Table SUB_CFNRY information

subscriber One row if CFNRy is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_CFNRY are provided in the following table, along with example values. CFNRy
datafill includes five sets, each with a registered status (_reg fields). For more information on sets, see
“Sets in Database” on page 167. Field descriptions and validations are provided in “Call Forward when
No Reply” on page 92.
Table 216 Table SUB_CFNRY field details

nfp varchar2(4) not null NONF NFWN
dcf_id varchar2(20) null DCF_ID2
spch_reg varchar2(5) not null TRUE TRUE
spch_act varchar2(5) TRUE TRUE
spch_noa varchar2(4) NTL INTL
spch_npi varchar2(4) PRIV E164
spch_ftn varchar2(15) 885566 44123888888
spch_nr_time number(2) 5 30
auxspch_nr_time number(2) null 25
cda_reg varchar2(5) not null TRUE FALSE
cda_act varchar2(5) TRUE null
cda_noa varchar2(4) INTL null

cda_npi varchar2(4) E164 null

cda_ftn varchar2(15) 61123555444 null
cda_nr_time number(2) 20 null
cds_nr_time number(2) null null
fax_nr_time number(2) null null
15.18 Table SUB_CFU

This table stores CFU data. A row in this table indicates that the subscriber has CFU provisioned.
Table 217 Table SUB_CFU information
One row if CFU is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_CFU are provided in the following table, as example values. CFU datafill includes
five sets, each with a registered status (_reg fields). For more information on sets, see “Sets in ” on page
167. Field descriptions and validations are provided in “Call Forward Unconditionally” on page 98.
Table 218 Table SUB_CFU field details



auxspch_noa varchar2(4) null null
auxspch_npi varchar2(4) null null
auxspch_ftn varchar2(15) null null
15.19 Table SUB_COS

This table stores COS data. A row in this table indicates that the subscriber has COS provisioned.
Table 219 Table SUB_COS information
subscriber One row if COS is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_COS are provided in the following table, along with example values. COS datafill is
composed of five sets, each with a registered status (_reg fields). For more information on sets, see “Sets

in ” on page 167 Field descriptions and validations are provided in “Class of Service” on page 105.
Table 220 Table SUB_COS field details

spch_cust_group number(4) null 1000
spch_ncos number(3) null null

auxspch_cust_ number(4) null 56
group
auxspch_ncos number(3) null 45
cda_cust_group number(4) null null
cda_ncos number(3) null null

cds_cust_group number(4) null null
cds_ncos number(3) null null
fax_cust_group number(4) null null
fax_ncos number(3) null null
15.20 Table SUB_CUG_FEATURE

This table stores CUG Feature data. A row in this table indicates that the subscriber has CUG Feature
provisioned. General table information is provided in the following table. CUG Feature is optional CUG
data — mandatory CUG data is CUG Subscription, that is stored in a separate table,
SUB_CUG_SUBSCRIPTION. See table “Table SUB_CUG_SUBSCRIPTION” on page 190.
Table 221 Table SUB_CUG information
One row if CUG Feature is provisioned
Primary Key IMSI


Indexes IMSI
Also See Table(s) sub_cug_subscription
Field details for SUB_CUG_FEATURE are provided in the following table, along with example values.
CUG Feature is composed of six sets, each with a registered status (_reg fields). For more information on
sets, see “Sets in ” on page 167. Field descriptions and validations are provided in “Closed User Groups”
on page 107.
Table 222 Table SUB_CUG_FEATURE field details

spch_reg varchar2(5) not null TRUE FALSE
spch_act varchar2(5) TRUE null
spch_ica varchar2(3) NONE null
spch_prefcug_index number(5) 345 null
auxspch_reg varchar2(5) not null TRUE FALSE
auxspch_act varchar2(5) TRUE null
auxspch_ica varchar2(3) ALL null
auxspch_prefcug_ind number(5) null null
ex
cda_ica varchar2(3) null null
cda_prefcug_index number(5) null null
cds_ica varchar2(3) null null
cds_prefcug_index number(5) null null
fax_ica varchar2(3) null null
fax_prefcug_index number(5) null null
allbsg_prov varchar2(5) not null FALSE TRUE
allbsg_act varchar2(5) null TRUE
allbsg_ica varchar2(3) null OA
allbsg_prefcug_index number(5) null null

15.21 Table SUB_CUG_SUBSCRIPTION

This table stores CUG Subscription data. One or more rows in this table indicates that the subscriber has
CUG Subscription provisioned (and hence has CUG provisioned). General table information is provided in
the following table. CUG Feature data (optional CUG data) is stored separately in table
SUB_CUG_FEATURE — see “Table SUB_CUG_FEATURE” on page 188.
Table 223 Table SUB_CUG_SUBSCRIPTION information

subscriber One row for each CUG Subsription dataset provisioned
Primary Key IMSI+NETWORK_ID+INTERLOCK
Indexes IMSI+NETWORK_ID+INTERLOCK
Also See Table(s) sub_cug_feature
Field details for SUB_CUG_SUBSCRIPTION are provided in the following table, along with example
values (a subscriber can have multiple rows in this table). Field descriptions and validations are provided
in “Closed User Groups Subscription” on page 107.
Table 224 Table SUB_CUG_SUBSCRIPTION field details

network_id varchar2(4) not null 567 9800
interlock number(5) not null 17 65000
cug_index number(5) not null 1234 32000
intracug_restricti varchar2(3) null ICB

ons
spch_reg varchar2(5) not null TRUE FALSE
allbsg_reg varchar2(5) not null FALSE TRUE
15.22 Table SUB_CW

This table stores CW data. A row in this table indicates that the subscriber has CW provisioned. General

Table 225 Table SUB_CW information

subscriber One row if CW is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_CW are provided in the following table, along with example values. CW datafill is
in ” on page 167. Field descriptions and validations are provided in “Call Waiting” on page 111.
Table 226 Table SUB_CW field details

15.23 Table SUB_EXT

This table stores EXT data. A row in this table indicates that the subscriber has EXT provisioned. General

Table 227 Table SUB_EXTinformation
One row if EXT is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_EXT are provided in the following table, along with example values. EXT datafill is
composed of two sets, each with a registered status (_reg fields). For more information on sets, see “Sets
in Database” on page 167. Field descriptions and validations are provided in “Extension Services” on
page 113.
Table 228 Table SUB_EXT field details

spch_reg varchar2(5) not null TRUE TRUE
spch_act varchar2(5) TRUE TRUE
spch_msisdn1_1 varchar2(15) 61123777777 4477111111
spch_msisdn1_2 varchar2(15) 61123777788 4477222222
spch_msisdn1_3 varchar2(15) null null
spch_timer1 number(2) 30 30
spch_group1 varchar2(2) SINGLE SINGLE
spch_msisdn2_1 varchar2(15) null 4477333333
spch_timer2 number(2) null 35
spch_group2 varchar2(2) null null
spch_timer3 number(2) null 40
spch_group3 varchar2(2) null SINGLE
spch_group_over varchar2(2) null MULTIPLE
all
auxspch_act varchar2(5) TRUE null
auxspch_msisdn varchar2(15) 6112377111 null
1_1


1_2
1_3
auxspch_timer1 number(2) 5 null
auxspch_group1 varchar2(2) MULTIPLE null
2_1
2_2
auxspch_msisdn varchar2(15) null null
2_3
auxspch_timer2 number(2) 20 null
auxspch_group2 varchar2(2) SINGLE null
3_1
3_2
3_3
auxspch_timer3 number(2) null null
auxspch_group3 varchar2(2) null null
auxspch_group_o varchar2(2) MULTIPLE null
verall
15.24 Table SUB_IMSI_SS

This table stores all IMSI-Supplementary Services, both provisioning indications and service data. A row
in this table is mandatory for all subscribers, even if no IMSI-SSs are provisioned. General table
information is provided in the following table.
Table 229 Table SUB_EXTinformation
Primary Key IMSI
Indexes IMSI
Field details for SUB_IMSI_SS are provided in the following table, along with example values. The
<service>_prov fields indicate whether the particular service is provisioned. See “Supplementary
services” on page 71 for a list of section references.

Table 230 Table SUB_IMSI_SS field details

acc_prov varchar2(5) not null FALSE TRUE
acc_option varchar2(5) null VOL
acc_ver_length number(2) null null
acrj_prov varchar2(5) not null FALSE TRUE
aocc_prov varchar2(5) not null FALSE TRUE
aoci_prov varchar2(5) not null FALSE FALSE
clip_prov varchar2(5) not null FALSE TRUE
clip_override varchar2(5) null FALSE
clir_prov varchar2(5) not null FALSE FALSE
clir_pm varchar2(4) null null
cnam_prov varchar2(5) not null FALSE FALSE
colp_prov varchar2(5) not null FALSE FALSE
colp_override varchar2(5) null null
colr_prov varchar2(5) not null FALSE FALSE
ect_prov varchar2(5) not null FALSE TRUE
emlpp_prov varchar2(5) not null FALSE TRUE
emlpp_max_pri varchar2(1) null B
ori ty
emlpp_def_prior varchar2(1) null 2
it y
fm_prov varchar2(5) not null FALSE FALSE
fm_cor_a varchar2(5) null null
fm_cor_b varchar2(5) null null
fm_cor_c varchar2(5) null null
fm_cor_d varchar2(5) null null
fm_sup_cor_a varchar2(5) null null
fm_sup_cor_b varchar2(5) null null
fm_sup_cor_c varchar2(5) null null
fm_sup_cor_d varchar2(5) null null
hold_prov varchar2(5) not null TRUE TRUE
hotbill_prov varchar2(5) not null FALSE FALSE
lco_prov varchar2(5) not null FALSE TRUE
mct_prov varchar2(5) not null FALSE FALSE
mpty_prov varchar2(5) not null TRUE TRUE
mpty_option varchar2(6) M3PORT M6PORT

uus1_prov varchar2(5) not null FALSE FALSE

crbt_prov varchar2(5) not null TRUE FALSE
15.25 Table SUB_DCSI

This table stores D-CSI data. A row in this table indicates that the subscriber has D-CSI provisioned.
Table 231 Table SUB_DCSI information
One row if D-CSI is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_DCSI are provided in the following table, along with example values. The
criteria_name<x> columns make up the criteria names vector. For more information on vectors see “Data
vectors” on page 27. The criteria names are datafilled in numerical order, as indicated in the examples.
Field descriptions and validations are provided in “Dialed CSI” on page 125.
Table 232 Table SUB_DCSI field details

active varchar2(5) not null TRUE TRUE
phase varchar2(4) not null CAP3 CAP3
unspvmsc varchar2(10) not null CONT_HPLMN RELEASE
unspgmsc varchar2(8) not null CONTINUE RELEASE
criteria_name1 varchar2(20) not null CRIT_NAMEA CRIT_NAMEZ
criteria_name2 varchar2(20) CRIT_NAMEC null
criteria_name3 varchar2(20) CRIT_NAMEB null
criteria_name4 varchar2(20) CRIT_NAMEZ null
criteria_name5 varchar2(20) null null

15.26 Table SUB_GPRS_CSI

This table stores GPRS-CSI data. A row in this table indicates that the subscriber has GPRS-CSI
Table 233 Table SUB_GPRS_CSI information
One row if GPRS-CSI is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_GPRS_CSI are provided in the following table, along with example values. GPRS-
CSI has five sets, each having a provisioned status (named tdp<x>_prov; ). For more information on sets,
see “Sets in Database” on page 167. Field descriptions and validations are provided in “General Packet
Radio Service CSI” on page 126.
Table 234 Table SUB_GPRS_CSI field details

unspsgsn varchar2(10) not null RELEASE CONTINUE
tdp1_prov varchar2(5) not null TRUE TRUE
tdp1_scf_name varchar2(20) MYSCF1 MYSCF1
tdp1_service_key number(10) 345345344 1113322
tdp1_scf_unavail varchar2(8) RELEASE RELEASE
tdp2_prov varchar2(5) not null FALSE FALSE
tdp2_scf_name varchar2(20) null null
tdp2_service_key number(10) null null
tdp2_scf_unavail varchar2(8) null null
tdp12_prov varchar2(5) not null TRUE FALSE
tdp12_scf_name varchar2(20) MYSCF99 null
tdp12_service_key number(10) 423422 null
tdp12_scf_unavail varchar2(8) CONTINUE null


15.27 Table SUB_MCSI

This table stores M-CSI data. A row in this table indicates that the subscriber has M-CSI provisioned.
Table 235 Table SUB_MCSI information
Number of Columns 4

subscriber One row if M-CSI is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_MCSI are provided in the following table, along with example values. Field
descriptions and validations are provided in “Mobility Management CSI” on page 128.
Table 236 Table SUB_MCSI field details

active varchar2(5) not null TRUE FALSE
mobility_trigger_ varchar2(20) not null TRIGGER_NAMEA TRIGGER_NAMEZ

name
suppress_mcsi varchar2(5) null HC
15.28 Table SUB_OCSI

This table stores O-CSI data. A row in this table indicates that the subscriber has O-CSI provisioned.

Table 237 Table SUB_OCSI information

subscriber One row if O-CSI is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_OCSI are provided in Table 238 Table SUB_OCSI field details on page 198, along
with example values. O-CSI has four sets, TDP2 Phase1, TDP2 Phase2, TDP2 Phase3, and TDP4
Phase3. Each has a provisioned status, named tdp<x>_phase<y>_prov.
There are several vectors in O-CSI datafill. The simple vectors are destination number length criteria (2
vectors), BS codes criteria (2 vectors) and cause values criteria:
• tdp2_ph2_dnc_length<x>
• tdp2_ph2_bs_code_cri<x>
• tdp2_ph3_dnc_length<x>
• tdp2_ph3_bs_code_cri<x>
• tdp4_ph3_cause_value_cri<x>
O-CSI also has two complex vectors for destination number criteria:
• tdp2_ph2_dnc_dn<x>_noa + tdp2_ph2_dnc_dn<x>_npi + tdp2_ph2_dnc_dn<x>
• tdp2_ph3_dnc_dn<x>_noa + tdp2_ph3_dnc_dn<x>_npi + tdp2_ph3_dnc_dn<x>
For more information on vectors, see “Vectors in Database” on page 166.
Field descriptions and validations are provided in “Originating CSI” on page 129.
Table 238 Table SUB_OCSI field details

ftn_checks varchar2(6) not null GSM TIF
unspvmsc varchar2(10) not null CONTINUE CONT_HPLMN
unspgmsc varchar2(8) not null CONTINUE CONTINUE
qscfwihp varchar2(5) not null TRUE FALSE
tdp2_ph1_prov varchar2(5) not null FALSE FALSE
tdp2_ph1_scf_n varchar2(20) null null
ame
tdp2_ph1_servi number(10) null null
ce_key

tdp2_ph1_scf_u varchar2(8) null null

navail
tdp2_ph1_send varchar2(5) null null
_cch
tdp2_ph2_prov varchar2(5) not null TRUE FALSE
tdp2_ph2_scf_n varchar2(20) MYSCF99 null
ame
tdp2_ph2_servi number(10) 1234567 null
ce_key
tdp2_ph2_scf_u varchar2(8) RELEASE null
navail
tdp2_ph2_dnc_ varchar2(10) null null
match _type
dn1 _noa
dn1_npi
dn1
dn2 _noa
dn2_npi
dn2
dn3 _noa
dn3_npi
dn3
dn4 _noa
dn4_npi
dn4
dn5 _noa
dn5_npi
dn5
dn6 _noa

dn6_npi
dn6
dn7 _noa
dn7_npi
dn7
dn8 _noa
dn8_npi
dn8
dn9 _noa
dn9_npi
dn9
dn10 _noa
dn10 _npi
dn10
tdp2_ph2_dnc_l number(2) null null
ength1
ength2
ength3
tdp2_ph2_bs_c varchar2(8) null null
ode _cri1
ode _cri2
ode _cri3
ode _cri4
ode _cri5
tdp2_ph2_call_t varchar2(7) null null
ype_cri
tdp2_ph3_prov varchar2(5) not null TRUE TRUE

tdp2_ph3_scf_n varchar2(20) MYSCFA MYSCF1

ame
tdp2_ph3_servi number(10) 257 33221100
ce_key
tdp2_ph3_scf_u varchar2(8) RELEASE CONTINUE
navail
tdp2_ph3_dnc_ varchar2(10) null ENABLING
match _type
tdp2_ph3_dnc_ varchar2(4) null INTL
dn1 _noa
tdp2_ph3_dnc_ varchar2(4) null E164
dn1_npi
tdp2_ph3_dnc_ varchar2(15) null 4.47891E+13
dn1
dn2 _noa
dn2_npi
tdp2_ph3_dnc_ varchar2(15) null 44789333333
dn2
dn3 _noa
dn3_npi
dn3
dn4 _noa
dn4_npi
dn4
dn5 _noa
dn5_npi
dn5
dn6 _noa
dn6_npi
dn6
dn7 _noa


dn7_npi
dn7
dn8 _noa
dn8_npi
dn8
dn9 _noa
dn9_npi
dn9
dn10 _noa
dn10 _npi
dn10
ength1
ength2
ength3
tdp2_ph3_bs_c varchar2(8) TPHNY null
ode _cri1
tdp2_ph3_bs_c varchar2(8) CDA null
ode _cri2
ode _cri3
ode _cri4
ode _cri5
tdp2_ph3_call_t varchar2(7) null FWD
ype_cri
tdp4_ph3_prov varchar2(5) not null TRUE TRUE
tdp4_ph3_scf_n varchar2(20) MYSCFB MYSCFZ
ame
tdp4_ph3_servi number(10) 12 1234533233
ce_key
tdp4_ph3_scf_u varchar2(8) CONTINUE RELEASE

navail
tdp4_ph3_caus number(3) null 34
e_value _cri1
e_value _cri2
e_value _cri3
tdp4_ph3_caus number(3) null null
e_value _cri4
e_value _cri5
15.29 Table SUB_SMS_CSI

This table stores SMS-CSI data. A row in this table indicates that the subscriber has SMS-CSI
Table 239 Table SUB_SMS_CSI information
Number of Columns 8

One row if SMS-CSI is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_SMS_CSI are provided in the following table, along with example values. Field
descriptions and validations are provided in “Short Message Service CSI” on page 134.
Table 240 Table SUB_SMS_CSI field details
Constraint
Column name Oracle type s Example 1 Example 2
unspnode varchar2(10) not null RELEASE CONTINUE
tdp1_prov varchar2(5) not null TRUE TRUE
tdp1_scf_name varchar2(20) MYSCF5 MYSCF1
tdp1_service_key number(10) 12345678 889988441
tdp1_scf_unavail varchar2(8) RELEASE RELEASE

15.30 Table SUB_SS_CSI

This table stores SS-CSI data. A row in this table indicates that the subscriber has SS-CSI provisioned.
Table 241 Table SUB_SS_CSI information
Number of Columns 8
subscriber One row if SS-CSI is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_SS_CSI are provided in the following table, along with example values. Field
descriptions and validations are provided in “Supplementary Service CSI” on page 135.
Table 242 Table SUB_SS_CSI field details

ect_option varchar2(5) TRUE TRUE
mpty_option varchar2(5) FALSE TRUE
scf_name varchar2(20) MYSCF99 MYSCFA
15.31 Table SUB_TCSI

This table stores T-CSI data. A row in this table indicates that the subscriber has T-CSI provisioned.
Table 243 Table SUB_TCSI information

subscriber One row if T-CSI is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_TCSI are provided in the following table, along with example values. T-CSI has five
sets, each having a provisioned status (named tdp<x>_ph<y>_prov):

• TDP12 Phase1
• TDP12 Phase2
• TDP12 Phase3
• TDP13 Phase3
• TDP14 Phase3
For more information on sets, see “Sets in Database” on page 167.
T-CSI has four simple vectors:
• tdp12_ph2_bs_code<x>
• tdp12_ph3_bs_code<x>
• tdp13_ph3_cause_value<x>
• tdp14_ph3_cause_value<x>
For more information on vectors, see “Vectors in Database” on page 166. Field descriptions and
validations are provided in “Terminating CSI” on page 136.
Table 244 Table SUB_TCSI field details

provide_location varchar2(5) not null TRUE FALSE
_info
page_for_cell_id varchar2(5) not null TRUE FALSE
provide_subscrib varchar2(5) not null TRUE TRUE
er _state
provide_current varcahr2(5) not null TRUE FALSE
_location
suppress_tcsi varchar2(5) null HC
unspgmsc varchar2(8) CONTINUE CONTINUE
tdp12_ph1_prov varchar2(5) not null FALSE FALSE
tdp12_ph1_scf_ varchar2(20) null null
name
tdp12_ph1_servi number(10) null null
ce _key
tdp12_ph1_scf_ varchar2(8) null null
unavail
tdp12_ph1_send varchar2(5) null null
_cch
tdp12_ph2_prov varchar2(5) not null TRUE FALSE
tdp12_ph2_scf_ varchar2(20) MYSCF1 null
name
tdp12_ph2_servi number(10) 45111111232 null

ce _key
tdp12_ph2_scf_ varchar2(8) CONTINUE null
unavail
tdp12_ph2_bs_c varchar2(8) TPHNY null
ode _cri1
tdp12_ph2_bs_c varchar2(8) FAX null
ode _cri2
tdp12_ph2_bs_c varchar2(8) CDS9600 null
ode _cri3
ode _cri4
ode _cri5
tdp12_ph3_prov varchar2(5) not null FALSE TRUE
tdp12_ph3_scf_ varchar2(20) null MYSCF8

name
tdp12_ph3_servi number(10) null 122231112
ce _key
tdp12_ph3_scf_ varchar2(8) null CONTINUE
unavail
ode _cri1
ode _cri2
ode _cri3
ode _cri4
ode _cri5

name
ce _key
tdp13_ph3_scf_ varchar2(8) null RELEASE
unavail
e _value_cri1
e _value_cri2
e _value_cri3


e _value_cri4
e _value_cri5

name
ce _key
tdp14_ph3_scf_ varchar2(8) null RELEASE
unavail
e_value_cri1
e_value_cri2
e_value_cri3
e_value_cri4
e_value_cri5
15.32 Table SUB_USSD_CSI

This table stores USSD-CSI data. A row in this table indicates that the subscriber has USSD-CSI
Table 245 Table SUB_USSD_CSI information
One row if USSD-CSI is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_USSD_CSI are provided in the following table, along with example values. USSD-
CSI has one simple vector, id<x>. For more information on vectors, see “Vectors in Database” on page
166. The ids are datafilled in numerical order, as indicated in the examples. Field descriptions and
validations are provided in “Unstructured Supplementary Service Data CSI” on page 139.
Table 246 Table SUB_USSD_CSI field details


id1 varchar2(10) not null MYID1 MYIDB

id2 varchar2(10) MYIDZ MYIDC
id3 varchar2(10) MYIDA null
id4 varchar2(10) MYID99 null
id5 varchar2(10) null null
15.33 Table SUB_CLIN

This table stores CLIN data. A row in this table indicates that the subscriber has CLIN provisioned.
Table 247 Table SUB_USSD_CSI information
Number of Columns 2
One row if CLIN is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_CLIN are provided in the following table, along with example values. Field
descriptions and validations are provided in “Calling Line Identification Replacement Number” on
page 153.
Table 248 Table SUB_CLIN field details

cli varchar2(15) not null 61123666777 44757123123
15.34 Table SUB_EA

This table stores EA data. A row in this table indicates that the subscriber has EA provisioned. General

Table 249 Table SUB_EA information
Number of Columns 2

subscriber One row if EA is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_EA are provided in the following table, along with example values. Field
descriptions and validations are provided in “Equal Access” on page 154.
Table 250 Table SUB_EA field details

pic varchar2(4) not null 1234 8888
15.35 Table SUB_GPRS_PROV

This table stores GPRS provisioning indications. A row in this table indicates that the subscriber has
GPRS provisioned. General table information is provided in the following table. GPRS datafill (that is,
PDP Context information) is stored separately in table SUB_GPRS_PDPS. See “Table
SUB_GPRS_PDPS” on page 210.
Table 251 Table SUB_GPRS_PROV information
Number of Columns 1

subscriber One row if GPRS is provisioned
Primary Key IMSI
Indexes IMSI
Also See Table(s) sub_gprs_pdps
Field details for SUB_GPRS_PROV are provided in the following table.
Table 252 Table SUB_GPRS_PROV field details


15.36 Table SUB_GPRS_PDPS

This table stores GPRS PDP context data. One row is datafilled for each PDP context for the subscriber.
GPRS provisioning indications are stored in table SUB_GPRS_PROV. See “Table SUB_GPRS_PROV”
on page 209. General table information is provided in the following table.
Table 253 Table SUB_GPRS_PDPS information
Number of Columns 4
Rows for each subscriber Zero to twenty
One row for each PDP context
Primary Key IMSI+CONTEXT_ID
Indexes IMSI+CONTEXT_ID
Also See Table(s) sub_gprs_prov
Field details for SUB_GPRS_PDPS are provided in the following table, along with example values (for a
particular row). GPRS has twenty sets, each set being context_id information. Field descriptions and
validations are provided in “GPRS PDP context IDs” on page 148.
Table 254 Table SUB_GPRS_PDPS field details

context_id number(2) not null 1 20
name varchar2(16) not null MYPDP1 MYPDP99
static_address varchar2(63) null 123.34.55.1
15.37 Table SUB_LCS_CALL_RELATED

This table stores LCS Call Related class data. A row in this table indicates that the subscriber has LCS
Call Related class provisioned. General table information is provided in the following table, including the
several tables that the LCS datafill is spread across.
Table 255 SUB_LCS_CALL_RELATED information
subscriber One row if LCS Call Related is provisioned
Primary Key IMSI
Indexes IMSI
Also See Table(s) sub_lcs_universal
sub_lcs_call_unrelated
sub_lcs_plmn_operator

sub_lcs_gmlcs
sub_lcs_mobile_originating
Field details for SUB_LCS_CALL_RELATED are provided in the following table, along with example
values. LCS Call Related has two simple vectors, external_client<x> and external_client_ex<x>, the latter
being the so-called "extended" clients vector. For more information on vectors, see “Vectors in Database”
on page 166. Field descriptions and validations are provided in “LCS Call Related” on page 142.
Table 256 Table SUB_LCS_CALL_RELATED field details

notification_to_user varchar2(30) not null LOC_NOT _ALLOW LOC_ALLOW_WITH

_NOTIF
external_client1 varchar2(8) CLIENT8 CLIENT45
external_client2 varchar2(8) CLIENT7 CLIENT12
external_client3 varchar2(8) CLIENT34 null
external_client_ex1 varchar2(8) CLIENT12 null
external_client_ex3 varchar2(8) CLIENTAA null
external_client_ex9 varchar2(8) null null


15.38 Table SUB_LCS_CALL_UNRELATED

This table stores LCS Call Unrelated class data. A row in this table indicates that the subscriber has LCS
Call Unrelated class provisioned. General table information is provided in the following table, including the

Table 257 SUB_LCS_CALL_UNRELATED information
subscriber One row if LCS Call Unrelated is provisioned
Primary Key IMSI
Indexes IMSI
sub_lcs_call_related
sub_lcs_gmlcs
Field details for SUB_LCS_CALL_UNRELATED are provided in the following table, along with example
values. LCS Call Unrelated has two simple vectors, external_client<x> and external_client_ex<x>, the
latter being the so-called "extended" names vector. For more information on vectors, see “Vectors in ” on
page 166. Field descriptions and validations are provided in “LCS Call Unrelated” on page 144.
Table 258 Table SUB_LCS_CALL_UNRELATED field details

notification_to_u varchar2(30) not null LOC_NOT_ALLOW LOC_ALLOW_WIT
ser H_NOTIF
external_client1 varchar2(20) EXTERNALCLIENT 8 EXTERNALCLIENT
45
external_client2 varchar2(20) EXTERNALCLIENT 7 EXTERNALCLIENT
12
external_client3 varchar2(20) EXTERNALCLIENT null
34
10
11
external_client_e varchar2(8) CLIENT12 null
x1
x2
external_client_e varchar2(8) CLIENTAA null
x3
x4


x5
x6
x7
x8
external_client_e varchar2(8) null null
x9
x10
x11
x12
x13
x14
x15
x16
x17
x18
x19
x20
x21
x22
x23
x24
x25
x26
x27


x28
x29
x30
x31
x32
x33
x34
x35
15.39 Table SUB_LCS_GMLCS

This table stores LCS GMLC data. A row in this table indicates that the subscriber has LCS GMLCs
provisioned. General table information is provided in the following table, including the several tables that
the LCS datafill is spread across.
Table 259 SUB_LCS_GMLCS information
Number of Columns 6
subscriber One row if one or more GLMCs is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_LCS_GMLCS are provided in the following table, along with example values. Field
descriptions and validations are provided in “LCS GMLCs” on page 145.
Table 260 Table SUB_LCS_GMLCS field details


gmlc1 varchar2(20) not null MYGMLC1 MYGMLC9

gmlc2 varchar2(20) MYGMLC5 null
gmlc5 varchar2(20) null null
15.40 Table SUB_LCS_MOBILE_ORIGINATING

This table stores all LCS Mobile Originating data, that is, all three classes: Basic Self Location,
Autonomous Self Location, and Transfer to Third Party. A row in this table indicates that the subscriber
has at least one mobile-originating class provisioned. General table information is provided in the
following table, including the several tables that the LCS datafill is spread across.
Table 261 Table SUB_LCS_MOBILE_ORIGINATING information
Number of Columns 7
One row if one or more LCS Mobile originating classes are
provisioned
Primary Key IMSI
Indexes IMSI
sub_lcs_gmlcs
Field details for SUB_LCS_MOBILE_ORIGINATING are provided in the following table, along with
example values. Field descriptions and validations are provided in “LCS Basic Self Location” on page 142
(basic self location), “LCS Autonomous Self Location” on page 141 (autonomous self location), and “LCS
Transfer to Third Party” on page 146 (transfer to third party).
Table 262 Table SUB_LCS_MOBILE_ORIGINATING field details

basic_self_loc_p varchar2(5) not null TRUE FALSE
rov
basic_self_loc_a varchar2(5) TRUE null
ct
autonomous_self varchar2(5) not null TRUE FALSE
_loc _prov
autonomous_self varchar2(5) FALSE null

_loc _act
transfer_3rd_par varchar2(5) not null TRUE TRUE
t y_prov
transfer_3rd_par varchar2(5) TRUE TRUE
t y_act
15.41 Table SUB_LCS_PLMN_OPERATOR

This table stores LCS PLMN Operator class data. A row in this table indicates that the subscriber has
LCS PLMN Operator class provisioned. General table information is provided in the following table,
including the several tables that the LCS datafill is spread across.
Table 263 Table SUB_LCS_PLMN_OPERATOR information
Number of Columns 7

subscriber One row if one or more LCS PLMN Operator is provisioned
Primary Key IMSI
Indexes IMSI
sub_lcs_gmlcs
sub_lcs_plmn_originating
Field details for SUB_LCS_PLMN_OPERATOR are provided in the following table, along with example
values. Field descriptions and validations are provided in “LCS PLMN Operator145” on page 145.
Table 264 Table SUB_LCS_PLMN_OPERATOR field details
Column
broadcast varchar2(5) not null TRUE FALSE
omh varchar2(5) not null TRUE FALSE
omv varchar2(5) not null FALSE TRUE
anonymous varchar2(5) not null TRUE FALSE
target_ms varchar2(5) not null FALSE TRUE

15.42 Table SUB_LCS_UNIVERSAL

This table stores LCS Universal class data. A row in this table indicates that the subscriber has LCS
Universal class provisioned. General table information is provided in the following table, including the
Table 265 Table SUB_LCS_UNIVERSAL information
Number of Columns 2

subscriber One row if LCS Universal is provisioned
Primary Key IMSI
Indexes IMSI
Also See Table(s) sub_lcs_call_related
sub_lcs_gmlcs
Field details for SUB_LCS_UNIVERSAL are provided in the following table, along with example values.
Field descriptions and validations are provided in “LCS Universal” on page 147.
Table 266 Table SUB_LCS_UNIVERSAL field details
Column
15.43 Table SUB_VBS

This table stores VBS data. A row in this table indicates that the subscriber has VBS provisioned. General
Table 267 Table SUB_VBS information

subscriber One row if VBS is provisioned
Primary Key IMSI
Indexes IMSI

Field details for SUB_VBS are provided in the following table, along with example values. VBS has
complex vector of groups, composed of group<x>_id + group<x>_orig_ent. For more information on
vectors, see “Vectors in ” on page 166. Field descriptions and validations are provided in “Voice
Broadcast Service” on page 68.
Table 268 Table SUB_VBS field details

functions_outside varchar2(5) TRUE FALSE

_hplmn
group1_id varchar2(3) 334 567
group1_orig_ent varchar2(5) TRUE TRUE
group2_orig_ent varchar2(5) TRUE TRUE

group3_id varchar2(3) 8 null
group3_orig_ent varchar2(5) TRUE null



group10_id varchar2(3) null null
group10_orig_ent varchar2(5) null null

































15.44 Table SUB_VGCS

This table stores VGCS data. A row in this table indicates that the subscriber has VGCS provisioned.
General table information is given in the following table.
Table 269 Table SUB_VGCS information
Number of columns 52
Rows for each subscriber Zero or One One row if VGCS is provisioned
Primary Key IMSI
Indexes IMSI
Field details for SUB_VGCS are provided in the following table, along with example values. VBS has
simple vector of group<x>_id. For more information on vectors, see “Vectors in Database” on page 166.
Field descriptions and validations are provided in “Voice Group Call Service” on page 69.
Table 270 Table SUB_VGCS field details

functions_outside varchar2(5) TRUE FALSE
_hplmn




15.45 Table SUB_SIMR

This table stores SIMR data. A row in this table indicates that the subscriber is involved in an SIMR
relationship (the subscriber’s current IMSI is not the key in this table). General table information is
provided in the following table.
Table 271 Table SUB_SIMR information
Number of columns 5

One row if the subscriber is in a SIMR relationship
Primary Key NEW_IMSI
Foreign Keys NEW_IMSI to table sub_auth, column IMSI
Indexes NEW_IMSI
OLD_IMSI
Field details for SUB_SIMR are provided in the following table, along with example values. The current
subscriber profile is indicated by the old_imsi field. Field descriptions and validations are provided in “SIM
Replacement” on page 157.
Table 272 Table SUB_SIMR field details

new_imsi varchar2(15) not null 456231234567890 234109920024844
old_imsi varchar2(15) not null 456231231231234 231109950005000
simr_option varchar2(5) not null FIXED USER
invocation_time varchar2(17) not null 15-Mar-2004 12:00 15-Mar-2004 15:00
activation_time varchar2(17) null 01-Feb-2004 09:00
15.46 Routing schema

The routing schema is composed of four tables, listed in the table below. Table HLRS denotes the HLR
Cores in the system. Tables IMSIS, MSISDNS, and SIMR are mapping tables used for provisioning
routing to an unmastered HLR or to HLR where mastering is in progress.

Table 273 Routing Schema Tables
New/
Changed/
Table name Deleted Description See page
hlrs Unchanged stores all HLR Core IDs
imsis Unchanged stores IMSIs mappings
msisdns Unchanged stores MSISDNs mappings
simr Unchanged stores time deadlines for
SIMR relationships
15.46.1 Table HLRS

This table stores the HLR Cores present in the HLR system. General table information is provided in the
following table.
Table 274 Table HLRS information
Number of columns 2
Rows for each subscriber Not applicable
(not a subscriber data table)
Primary Key ID
Foreign Keys None
Indexes ID
Field details for table HLRS are provided in the following table, along with descriptions.
Table 275 Table HLRS field details
Column name Oracle type Constraints Syntax Description

id varchar2(10) not null 10 hex digits the HLR Core ID
name varchar2(50) not null 1 - 50 characters a descriptive name
for the HLR Core
15.46.2 Table IMSIS

This table stores the IMSIs mappings. General table information is provided in the following table.
Table 276 Table IMSIS information
Number of columns 2
Rows for each subscriber Zero or one
Primary Key IMSI
Foreign Keys HLR_ID to table hlrs, column ID
Indexes IMSI

Also See Table(s) hlrs
Field details for table IMSIS are provided in the following table, along with descriptions.
Table 277 Table IMSIS field details

imsi varchar2(15) not null 6 -15 digits International Mobile
Subscriber Identity
hlr_id varchar2(10) not null 10 hex digits HLR ID for this

subscriber
15.46.3 Table MSISDNS

This table stores the MSISDNs mappings. General table information is provided in the following table.
Table 278 Table MSISDNS information
Number of columns 2
Rows for each subscriber Zero to 19 (A theoretical maximum and very unlikely in reality;
a typical subscriber will have one to five rows.) One row for
each basic service
Primary Key MSISDN
Foreign Keys IMSI to table imsis, column IMSI
Indexes IMSI
MSISDN
Also See Table(s) imsis
Field details for table MSISDNS are provided in the following table, along with descriptions.
Table 279 Table MSISDNS field details

msisdn varchar2(15) not null 3 -15 Mobile Subscriber
digits ISDN number
imsi varchar2(15) not null 6 -15 International Mobile Subscriber
digits Identity (IMSI) that the MSISDN
relates to
15.46.4 Table SIMR

This table stores deadlines for SIMR relationships and becomes redundant once all subscribers have
been remastered. The full set of SIMR data is stored in table SUB_SIMR in the subscriber schema. See
“Table SUB_SIMR” on page 224. General table information is provided in the following table.

Table 280 Table SIMR information
Number of columns 3
Rows for each subscriber Zero or one
Primary Key NEW_IMSI
Foreign Keys NEW_IMSI to table imsis, column IMSI
OLD_IMSI to table imsis, column IMSI
Indexes NEW_IMSI
OLD_IMSI
Field details for table SIMR are provided in the following table, along with descriptions.
Table 281 Table SIMR field details

new_imsi varchar2(15) not null 6 -15 digits new IMSI for a subscriber
old_imsi varchar2(15) not null 6 -15 digits the subscriber’s old IMSI,
that is to be replaced
deadline date not null date (nearest hour) the time at which the SIMR
swap is mandatory

 END OF DOCUMENT PE/HLR/APP/027819 

HLR Configuration Volume 3 of 3

Uploaded by

Document Information

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

HLR Configuration Volume 3 of 3

Uploaded by

Copyright:

Available Formats

Kapsch CarrierCom AG

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 1 of 228

HLR Configuration Volume 3 of 3

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 2 of 228

Copyright © 2014 Kapsch. All Rights Reserved.

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 3 of 228

2 Subscriber Profile ............................................................................................................................. 9

3 Data model and validations ............................................................................................................22

4 Authentication data .........................................................................................................................31

5 Profile control data ..........................................................................................................................33

6 Basic services .................................................................................................................................40

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 4 of 228

6.9 Circuit Duplex Asynchronous data 300 .............................................................................................48

7 Supplementary services .................................................................................................................71

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 5 of 228

7.28 Enhanced Multi Level Precedence and Pre-emption ......................................................................112

8 Operator-determined barrings .....................................................................................................122

9 CAMEL services ............................................................................................................................124

10 Location Services ..........................................................................................................................141

11 GPRS PDP context IDs .................................................................................................................148

12 Other services ...............................................................................................................................153

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 6 of 228

12.2 Calling Line Identification Replacement Number ............................................................................153

13 Other components ........................................................................................................................156

14 Suppression states .......................................................................................................................159

15 Database Implementation .............................................................................................................164

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 7 of 228

15.29 Table SUB_SMS_CSI .....................................................................................................................203

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 8 of 228

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 9 of 228

2.2 Subscriber profile view

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 10 of 228

Figure 1 Subscriber profile high-level view

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 11 of 228

Figure 2 Subscriber profile components

2.3 Profile graphical representation

2.3.1 Data sets

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 12 of 228

Figure 3 Sets illustrated

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 13 of 228

Figure 4 Subscriber Profile diagram examples

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 14 of 228

Figure 5 Subscriber profile diagram part I - Authentication and Profile Control

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 15 of 228

Figure 6 Subscriber profile diagram part II - ODBs

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 16 of 228

Figure 7 Subscriber profile part III - BSs

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 17 of 228

Figure 8 Subscriber profile part IV - SSs 1

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 18 of 228

Figure 9 Subscriber profile part V - SSs 2

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 19 of 228

Figure 10 Subscriber profile part VI - CAMEL

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 20 of 228

Figure 11 Subscriber profile part VII - LCS

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 21 of 228

Figure 12 Subscriber profile part VIII - miscellaneous

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 22 of 228

3 Data model and validations

3.2 Profile components

Table 1 Profile components

Short name Expanded name See section

PE/HLR/APP/027819 | HLR Configuration Volume 3 of 3 Page 23 of 228

ALTSPCDA Alternate Speech / CDA Data “Alternate Speech/Circuit Duplex