HLR Eir MSC VLR SGSN

MSCDOCM14PDFCD
MSC/HLR, Rel. M14.0, Product Documentation,

v.2
HLR/EIR - MSC/VLR/SGSN/
gsmSCF/GMLC Mobile
Application Part
DN98628099
Issue 10-1 en
# Nokia Siemens Networks
1 (264)
HLR/EIR - MSC/VLR/SGSN/gsmSCF/GMLC Mobile Application Part
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given as is and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT
NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners,
and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2008. All rights reserved.
2 (264)
DN98628099
Issue 10-1 en
Contents
Contents
Contents 3
List of tables 6
Summary of changes 7
1
Introduction 9
2
2.1
2.1.1
Interface modifications 11
Use of MAP operations and their parameters
Call handling operations 11
3
3.1
3.1.1
3.1.1.1
3.1.1.2
3.1.1.3
3.1.1.4
3.1.1.5
3.1.1.6
3.1.1.7
3.1.1.8
3.1.2
3.1.3
3.1.4
3.1.5
3.2
3.2.1
3.2.1.1
3.2.1.2
3.2.1.3
3.2.1.4
3.2.1.5
3.2.1.6
3.2.2
3.2.2.1
3.2.2.2
3.2.2.3
3.2.2.4
3.2.2.5
3.2.2.6
3.2.2.7
3.2.2.8
3.2.2.9
3.2.2.10
3.2.2.11
3.2.2.12
Interface description 13
General 13
Supported application context versions 13
HLR VLR, D-interface 14
HLR MSC, C-interface 16
HLR GMLC, Lh-interface 16
HLR gsmSCF, J-interface 17
HLR HLR interface 18
HLR SGSN, Gr-interface 18
EIR MSC, F-interface 20
EIR SGSN, Gf-interface 20
Application contexts for ANSI MAP 21
Version control 21
General behaviour in MAP procedures 22
Proprietary parameters 23
Dialogue information 24
MAP-Open 24
MAP-Accept 26
MAP-Close 26
MAP-Refuse 26
MAP-UserAbort 26
MAP-ProviderAbort 27
Mobile Service operations 27
UpdateLocation 27
CancelLocation 31
PurgeMS 33
UpdateGPRSLocation 34
ProvideSubscriberInfo 37
AnyTimeInterrogation 40
AnyTimeSubscriptionInterrogation 44
AnyTimeModification 47
NoteSubscriberDataModified 52
SendAuthenticationInfo 54
AuthenticationFailureReport 55
CheckIMEI 57
DN98628099
Issue 10-1 en
11
23
3 (264)
3.2.2.13
3.2.2.14
3.2.2.15
3.2.2.16
3.2.2.17
3.2.2.18
3.2.2.19
3.2.2.20
3.2.2.21
3.2.3
3.2.3.1
3.2.3.2
3.2.3.3
3.2.4
3.2.4.1
3.2.4.2
3.2.4.3
3.2.4.4
3.2.4.5
3.2.5
3.2.5.1
3.2.5.2
3.2.5.3
3.2.5.4
3.2.5.5
3.2.5.6
3.2.5.7
3.2.5.8
3.2.5.9
3.2.5.10
3.2.5.11
3.2.5.12
3.2.5.13
3.2.5.14
3.2.5.15
3.2.6
3.2.6.1
3.2.6.2
3.2.6.3
3.2.6.4
3.2.6.5
3.2.6.6
3.2.6.7
3.2.6.8
3.2.7
3.2.7.1
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
4 (264)
InsertSubscriberData 58
DeleteSubscriberData 75
Reset 77
ForwardCheckSSIndication 78
RestoreData 78
SendRoutingInfoForGprs 80
FailureReport 80
NoteMsPresentForGprs 80
SendParameters 80
Operation and Maintenance operations 83
ActivateTraceMode 83
DeactivateTraceMode 85
SendIMSI 87
Call handling operations 89
SendRoutingInfo 89
ProvideRoamingNumber 110
SetReportingState 113
StatusReport 114
RemoteUserFree 115
Supplementary service operations 117
BeginSubscriberActivity 117
RegisterSS 118
EraseSS 122
ActivateSS 124
DeactivateSS 126
InterrogateSS 129
ProcessUnstructuredSS-Data 131
ProcessUnstructuredSS-Request 132
UnstructuredSS-Request 135
UnstructuredSS-Notify 137
RegisterPassword 138
GetPassword 139
SS-InvocationNotification 140
RegisterCC-Entry 141
EraseCC-Entry 143
Short messages operations 144
SendRoutingInfoForSM 144
SetMessageWaitingData 148
ReportSM-DeliveryStatus 149
AlertServiceCentreWithoutResult 152
AlertServiceCentre 153
InformServiceCentre 153
NoteMSPresent 154
ReadyForSM 155
Location service operations 156
SendRoutingInfoForLCS 156
Formal definition of data types 158
Dialogue information 159
Mobile Service data types 160
Operation and Maintenance data types 199
Call Handling data types 201
Supplementary Service data types 208
DN98628099
Issue 10-1 en
Contents
3.3.6
3.3.7
3.3.8
3.3.9
3.3.10
3.3.11
3.3.12
3.3.13
3.3.14
3.3.15
Supplementary Service codes 216

Short Message Service data types 219
Error data types 224
Common data types 228
Teleservice codes 236
Bearer Service codes 238
Extension data types 240
Group Call data types 251
Location Service data types 251
Secure transport data types 258
4
4.1
4.2
4.3
Support protocol description 259

TCAP 259
SCCP 260
MTP 261
References 263
DN98628099
Issue 10-1 en
5 (264)
List of tables
6 (264)
Table 1.
Supported application context versions and operations in the HLR-VLR, Dinterface 14
Table 2.
Supported application context versions and operations in the HLR-MSC,

C-interface 16
Table 3.
Supported application context version and operation in the HLR-GMLC,

Lh-interface 17
Table 4.
Supported application context versions and operations in the HLRgsmSCF, J-interface 17
Table 5.
Supported application context versions and operations in the HLR-HLR

interface 18
Table 6.
Supported application context versions and operations in the HLR

SGSN, Gr-interface 19
Table 7.
Supported application context version and operation in the EIR-MSC, Finterface 20
Table 8.
Supported application context version and operation in the EIR-SGSN, Gfinterface 20
DN98628099
Issue 10-1 en
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest
document issue contains all changes made to previous issues.
Changes made between issues 10-1 and 10-0
Several M13 Top features have been implemented.

Changes made between issues 100 and 94
The document has been updated from M13.5 to M14.0.

Refer to Chapter Interface modifications for changes made after the
previous software release.
Changes made between issues 94 and 93
New Section Changes in M13.5 has been added to Chapter Interface

modifications.
For changes made after the previous software release, refer to Chapter
Interface modifications.
DN98628099
Issue 10-1 en
7 (264)
8 (264)
DN98628099
Issue 10-1 en
Introduction
Introduction
This document describes the use of Mobile Application Part (MAP)
protocol operations and operation parameters in the HLR/EIR.
Specifically, the document describes MAP interfaces from HLR/EIR
towards the following network elements:
.
D-interface: HLR (subsystem 6) VLR (subsystem 7)
C-interface: HLR (subsystem 6) MSC (subsystem 8)
Lh-interface: HLR (subsystem 6) GMLC (subsystem 145)
J-interface: HLR (subsystem 6) gsmSCF, IN SCP (subsystem

147)
J-interface: HLR (subsystem 6) gsmSCF, USSDC (subsystem 5)

The gsmSCF subsystem number, which is used by the HLR, can be
configured. The default value is 5.
DN98628099
Issue 10-1 en
Interface HLR (subsystem 6) HLR (subsystem 6)
Gr-interface: HLR (subsystem 6) SGSN (subsystem 149)
F-interface: EIR (subsystem 9) MSC (subsystem 8)
Gf-interface: EIR (subsystem 9) SGSN (subsystem 149)
9 (264)
10 (264)
DN98628099
Issue 10-1 en
Interface modifications
Interface modifications
This section describes MAP interface changes from software release M13
to software release M14.
2.1
2.1.1
Call handling operations

SendRoutingInfo
.
Error codes
.
OLCM report generation in all Unsuccessful Call Attempt case
The support has been implemented for transferring the
proprietary On-Line Call Monitoring information as an
extension in the error codes SystemFailure,
FacilityNotSupported, BusySubscriber, CallBarred, CUGReject and ForwardingViolation.
{ &ExtensionType; ErrOlcmInfoTableExt,
&extensionId;
{0 34 23} }
ErrOlcmInfoTableExt ::= [PRIVATE 0] SEQUENCE {
olcmInfoTable [0] OlcmInfoTable OPTIONAL,
imsi
[1] IMSI OPTIONAL,
...}
DN98628099
Issue 10-1 en
11 (264)
12 (264)
DN98628099
Issue 10-1 en
Interface description
The MAP interface description is covered in three parts.
.
The implemented MAP protocol and the aspects that apply to all
MAP procedures

This part describes how individual MAP parameters are used in the
sending and/or the receiving entities.
Formal definition of data types

This part contains ASN.1 descriptions of MAP operations and data
types.
3.1
General
This section provides a general description of the implemented MAP
protocol and the aspects that apply to all MAP procedures.
3.1.1
Supported application context versions

The following application contexts specified in 3GPP TS 29.002, Mobile
Application Part (MAP) Specification, Release 5 are not implemented:
DN98628099
Issue 10-1 en
gprsLocationInfoRetrievalContext, version 3 and version 4. HLR

GGSN, Gc-interface.
failureReportContext, version 3. HLR GGSN, Gc-interface.
gprsNotifyContext, version 3. HLR GGSN, Gc-interface.
istAlertingContext, version 3. HLR MSC, C-interface.
13 (264)
3.1.1.1
serviceTerminationContext, version 3. HLR MSC, C-interface.
secureTransportHandlingContext, version 3. Between any MAP

entities
HLR VLR, D-interface

The following table summarises the supported application context versions
and operations in the HLR-VLR, D-interface.
Table 1.
Supported
version
1, 2, 3
Supported application context versions and operations in the HLRVLR, D-interface
Application context
Operation
networkLocUpContext
updateLocation
activateTraceMode
insertSubscriberData
forwardCheckSs-Indication
restoreData
1, 2, 3
locationCancellationContext
cancelLocation
1, 2, 3
roamingNumberEnquiryContext
provideRoamingNumber
resetContext
reset
imsiRetrievalContext
sendIMSI
1, 2, 3
infoRetrievalContext
sendAuthenticationInfo
(SendParameters in version1)
1, 2, 3
subscriberDataMngtContext
1, 2
deleteSubscriberData
1, 2, 3
tracingContext
activateTraceMode
deactivateTraceMode
14 (264)
DN98628099
Issue 10-1 en
Table 1.
Supported
version
1, 2
Supported application context versions and operations in the HLRVLR, D-interface (cont.)
Application context
Operation
networkFunctionalSsContext
registerSS
eraseSS
activateSS
deactivateSS
interrogateSS
registerPassword
getPassword
networkUnstructuredSsContext
processUnstructuredSS-Request
unstructuredSS-Request
unstructuredSS-Notify
1, 2, 3
mwdMngtContext
readyForSM (noteMSPresent in version

1)
2, 3
msPurgingContext
purgeMS
subscriberInfoEnquiryContext
provideSubscriberInfo
reportingContext
setReportingState
statusReport
remoteUserFree
callCompletionContext
registerCC-Entry
eraseCC-Entry
DN98628099
Issue 10-1 en
authenticationFailureReportContext
authenticationFailureReport
15 (264)
Note
The default version, which is set using MAP parameter management
MML commands, is used for all initiated outgoing dialogues.
Version 1, however, is always used to initiate dialogues for
resetContext, unless the result of the destination address analysis
indicates a higher version. For more information, see Version control.
The reason for that is that version 2 (and higher) does not provide better
functionality for this application context and version 1 messages use
less link capacity.
3.1.1.2
HLR MSC, C-interface

and operations in the HLR-MSC, C-interface.
Table 2.
Supported application context versions and operations in the HLRMSC, C-interface
Application context
Operation
1, 2, 3
locationInfoRetrievalContext
sendRoutingInfo
1, 2, 3
shortMsgGatewayContext
sendRoutingInfoForSM
Supported
version
reportSM-DeliveryStatus
(setMessageWaitingData in version 1)
InformServiceCentre
1, 2
3.1.1.3
shortMsgAlertContext
alertServiceCentre
(alertServiceCentreWithoutResult in
version 1)
HLR GMLC, Lh-interface

and operations in the HLR-GMLC, Lh-interface.
16 (264)
DN98628099
Issue 10-1 en
Table 3.
Supported
version
3.1.1.4
Supported application context version and operation in the HLRGMLC, Lh-interface
Application context
Operation
locationSvcGatewayContext
sendRoutingInfoForLCS
HLR gsmSCF, J-interface

and operations in the HLR-gsmSCF, J-interface.
Table 4.
Supported
version
1, 2
Supported application context versions and operations in the HLRgsmSCF, J-interface
Application context
Operation
networkFunctionalSsContext
registerSS
eraseSS
activateSS
deactivateSS
interrogateSS
registerPassword
getPassword
unstructuredSS-Request
unstructuredSS-Notify
anyTimeInfoEnquiryContext
1, 3
anyTimeInterrogation
anyTimeInfoHandlingContext
anyTimeSubscriptionInterrogation
anyTimeModification
DN98628099
Issue 10-1 en
17 (264)
Table 4.
Supported
version
Supported application context versions and operations in the HLRgsmSCF, J-interface (cont.)
Application context
subscriberDataModificationNotification
Context
Operation
noteSubscriberDataModified
ss-InvocationNotificationContext
3
ss-InvocationNotification
locationInfoRetrievalContext
sendRoutingInfo
The support for the anyTimeInfoEnquiryContext in version 1 is proprietary.

3.1.1.5
HLR HLR interface

and operations in the HLR-HLR interface.
Table 5.
Supported
version
3.1.1.6
Supported application context versions and operations in the HLRHLR interface
Application context
Operation
HLR SGSN, Gr-interface

and operations in the HLR-SGSN, Gr-interface.
18 (264)
DN98628099
Issue 10-1 en
Table 6.
Supported
version
Supported application context versions and operations in the HLR

SGSN, Gr-interface
Application context
Operation
gprsLocationUpdateContext
updateGprsLocation
activateTraceMode
1, 2
1, 2, 3
locationCancellationContext
cancelLocation
resetContext
reset
infoRetrievalContext
sendAuthenticationInfo
(SendParameters in version1)
subscriberDataMngtContext
deleteSubscriberData
1, 2, 3
tracingContext
activateTraceMode
deactivateTraceMode
1, 2, 3
mwdMngtContext
readyForSM (noteMSPresent in version

1)
msPurgingContext
purgeMS
authenticationFailureReportContext
authenticationFailureReport
subscriberInfoEnquiryContext
ProvideSubscriberInfo
DN98628099
Issue 10-1 en
19 (264)
Note
The default version (which is set using MAP, parameter management,
MML commands) is used for all initiated outgoing dialogues.
Version 1, however, is always used to initiate dialogues for
resetContext, unless the result of the destination address analysis
indicates a higher version. For more information, see Version control.
The reason for that is that version 2 (and higher) does not provide better
functionality for this application context and version 1 messages use
less link capacity.
3.1.1.7
EIR MSC, F-interface

and operations in the EIR-MSC, F-interface.
Table 7.
Supported application context version and operation in the EIRMSC, F-interface
Supported
version
Application context
Operation
1, 2
equipmentMngtContext
checkIMEI
3.1.1.8
EIR SGSN, Gf-interface

and operations in the EIR-SGSN, Gf-interface.
Table 8.
Supported application context version and operation in the EIRSGSN, Gf-interface
Supported
version
Application context
Operation
1, 2
equipmentMngtContext
checkIMEI
20 (264)
DN98628099
Issue 10-1 en
3.1.2
Application contexts for ANSI MAP

The ANSI MAP protocol uses object identifiers allocated by ANSI. The root
of the object identifier tree differs from the ETSI/3GPP MAP specification.
However, the values following the mobile domain in the tree are the same
as in the ETSI/3GPP specification.
.
ETSI/3GPP MAP OBJECT IDENTIFIER

{ccitt (0) identified-organization (4) etsi (0) mobile-domain (0) }
ANSI MAP OBJECT IDENTIFIER

{iso (2) member-body (16) usa (840) ansi (1) tia (113737) mobiledomain (0) }
The operator can define which ObjectIdentifier value is used, either ANSI
MAP or ETSI/3GPP MAP.
When a MAP user initiates a new dialogue, MAP selects the used object
identifier using a network entity address analysis. If an analysis is not
found, or if the analysis result does not define an object identifier, MAP
reads the used object identifier from the default configuration, defined by
the operator.
When a dialogue initiation is received from the network, both the ETSI/
3GPP MAP object identifier and the ANSI MAP object identifier are
supported in the message, regardless of the default configuration or of the
network entity address analysis configuration.
3.1.3
Version control
Selecting the version used for outgoing dialogues
The MAP user (for example the HLR application) can request MAP to use
version 1, 2, 3, or 4. The version which the MAP user requests is used for
the dialogue, unless the default MAP version is lower. If the default MAP
version is lower than the version requested by the MAP user, the default
version is used. The default version is set individually for each Application
Context with MAP parameter handling (OP) MML commands.
If an address analysis exists for the destination address, the result of the
analysis is used to select the version. In this case both the version
requested by the MAP user and the version defined as the default version
is ignored. The version used as a result of the address analysis may be 1,
DN98628099
Issue 10-1 en
21 (264)
2, 3, or 4. The address analysis may also lead to value 'denied', in which

case the dialogue is not sent at all, or to value 'default', in which case the
default version is used. Address analyses are created and modified with
MAP parameter handling (OP) MML commands.
Using version control when a dialogue initiation is received from the
network
The dialogue continues if an address analysis for the originating address
exists and leads to the requested version, or to a higher version. If the
analysis leads to a lower version, the dialogue is aborted due to
applicationContextNotSupported and the lower version is offered. The
address analysis can also lead to value 'denied', in which case the
dialogue is aborted due to applicationContextNot Supported, or to value
'default', in which case the default version is checked to determine whether
to continue or abort the dialogue.
If no address analysis exists for the originating address, the default version
is checked to determine whether to continue or abort the dialogue.
3.1.4
General behaviour in MAP procedures

In an overload situation, incoming dialogue invocations are either
discarded (this is the default behavior) or aborted by sending a TC-Abort.
The handling is set with MAP parameter handling MML commands. In
version 2 (or higher) dialogues the detailed abort diagnostic is included,
and it has value resource limitation.
An alarm is triggered when an UnexpectedDataValue or DataMissing error
is sent or received.
If the type of a received parameter (for example, an unspecified
ENUMERATED value, or string length violating the size constraint) is not
the one defined for the parameter, the component is rejected using the TCU-REJECT primitive.
Overdecadic hexadecimal digits (A, B, C, D or E) in AddressStings are
allowed only in certain cases (in those cases, it is explicitly mentioned in
the parameter description). As a general rule, if overdecadic values are
received, an error UnexpectedDataValue is sent.
22 (264)
DN98628099
Issue 10-1 en
When msisdn numbers (MAP message parameters, which are of type

ISDN-AddressString) are received from the network, they are allowed only
in international or national format, and national numbers are converted to
international before handling in the application. If the functionality is
different in case of certain parameters, that is explicitly mentioned in the
parameter description.
The operation timer value (see the description for each operation in
section Use of MAP operations and their parameters) is greater than zero
seconds also for class 4 operations, for which no response from the peer
node is normally expected, but a reject component can however be
received.
3.1.5
Proprietary parameters
When MAP version 2 is used, extended parameters (for example,
proprietary parameters) are placed at the extension marker (see GSM
09.02, Mobile Application Part (MAP) Specification, GSM phase 2).
In MAP versions higher than 2, the extended parameters are placed inside
the extension container (see GSM 09.02, Mobile Application Part (MAP)
Specification, GSM phase 2+). Each extension container has a unique
identifier, which is called the object identifier. For proprietary extensions
the value of the object identifier is {0 34 x}, the value of the 'x' depends on
the operation and the extension type.
Parameters following an extension marker are used only in version 2 (or
higher) dialogues, except private numbering index, call redirection index
and alternate line service. These can also be used in InsertSubscriberData
and DeleteSubscriberData in version 1 dialogues. Undefined extension
parameters, which are not used in the HLR/EIR implementation, are not
checked. These parameters, after ellipsis notation, are also allowed in
version 1 dialogues.
3.2

This section describes how each parameter is used in the HLR/EIR on a
functional level. For a formal description of message contents and
parameters (in ASN.1 notation), see section Formal definition of data
types.
DN98628099
Issue 10-1 en
23 (264)
3.2.1
Dialogue information
3.2.1.1
MAP-Open
Used in supplementary service operations (both functional SS and
unstructured SS).
As an optional feature, this parameter is used also in CheckIMEI
operation.
Parameter use in the receiving entity

.
destinationReference
Used for subscription checking in the HLR. In error cases, MAPRefuse is sent with reason invalidDestinationReference.
In mobile-originated cases (received from the VLR), it contains the
subscriber's IMSI.
As an optional feature, the IMSI may be either the Database IMSI or
an Alias IMSI (according to the HLR configuration).
In mobile-terminated cases (received from the gsmSCF), it contains
either the IMSI (numbering plan E.212) or, as an optional feature
(Feature 448: MAP Interface for SCP in HLR), the subscriber's
MSISDN (numbering plan E.164).
When the USSD is received from another HLR (Feature 1609:
Follow Me), the destinationReference contains the subscriber's
MSISDN.
As an option (Feature 1048: Extended Handling for Subscriber
Identity (MSISDN) in the HLR), the received MSISDN may be
modified before the HLR database enquiry.
As an optional feature, this parameter is allowed also with the
CheckIMEI operation. In that case the parameter is handled as the
subscriber's IMSI.
originationReference
Presence is allowed in mobile-originated supplementary service
operations, and in USSD operations. In error cases, MAP-Refuse is
sent with reason invalidOriginatingReference.
24 (264)
DN98628099
Issue 10-1 en
The received originationReference is used as the

originationReference, in cases when the message is further
forwarded from the HLR towards the gsmSCF.
As an optional feature, this parameter is allowed also with the
CheckIMEI operation. In that case the parameter is handled as the
subscriber's MSISDN.
Parameter use in the sending entity
.
This parameter is used in the procedure initiations for mobileoriginated supplementary service operations (functional SS or
USSD), when the message is forwarded to the gsmSCF. The
parameter is also used in the procedure initiations for mobileterminated USSD operations when the message is forwarded to the
VLR.
It contains the subscriber's IMSI, the numbering plan indicator is set
to E.212.
aAs an optional feature in USSD operations (Feature 448: MAP
Interface for SCP in HLR), when the mobile-originated operation is
forwarded to the gsmSCF, the IMSI may be replaced with the
subscriber's MSISDN or with the ringing group's common MSISDN.
In this case the numbering plan indicator is set to E.164.
In Network Initiated USSDs, the IMSI which is received from the
gsmSCF is forwarded to the VLR. As an optional feature, if the
request from the gsmSCF contains an MSISDN instead of the IMSI,
in the message towards the VLR is sent the IMSI which is in the
database (not Alias IMSI), even if the Alias IMSI is marked as active
in the subscriber data in the HLR database.
If the mobile-originated USSD is forwarded from the HLR to another
HLR (because of the Feature 1609: Follow Me), the
destinationReference parameter contains the recipient subscriber's
MSISDN.
originationReference
It is used in the procedure initiations for mobile-originated
supplementary service operations (functional SS or USSD), when
the message is forwarded to the gsmSCF.
In mobile-originated cases, the received VLR address is forwarded
to the gsmSCF.
DN98628099
Issue 10-1 en
25 (264)
3.2.1.2
MAP-Accept
It is never sent. If MAP-Accept is received, it is ignored.
3.2.1.3
MAP-Close
It is never sent. If MAP-Close is received, it is ignored.
3.2.1.4
MAP-Refuse
The refuse reason is stored to MAP statistics in receiving and sending
entities.
In sending entities, one of the following reasons is used:
.
invalidDestinationReference
If the IMSI is unknown in the HLR, or if the destinationReference in
MAP-Open contradicts the requirements in 3GPP TS 29.002, Mobile
Application Part (MAP) Specification.
invalidOriginatingReference
If the originationReference in MAP-Open contradicts the
requirements in 3GPP TS 29.002, Mobile Application Part (MAP)
Specification.
3.2.1.5
MAP-UserAbort
The abort reason is stored to MAP statistics in receiving and sending
entities.
In sending entities, one of the following reasons is used:
.
userSpecificReason
This parameter is used in the following situations:
.
MAP detects an internal error in the MAP-user behaviour.
.
In USSD dialogues:
UserSpecificReason is sent to the VLR (or the gsmSCF) when
an abort or a reject is received from the gsmSCF (or the VLR).
It is sent to the VLR in MO-USSD dialogue if the
Supplementary Service access is barred by the operator.
26 (264)
DN98628099
Issue 10-1 en
resourceUnavailable, shortTermResourceLimitation
This parameter is used when a temporary resource limitation
prevents the handling of an incoming dialogue invocation (version 2
or higher).
applicationProcedureCancellation, associatedProcedureFailure
This parameter is sent towards the VLR during a mobile-terminated
USSD dialogue if no dialogue ending is received from the gsmSCF.
3.2.1.6
MAP-ProviderAbort
In the receiving and sending entities the abort reason is stored to MAP
statistics.
In the sending entity the following reason may be used:
.
abnormalDialogue
This parameter is sent if the parameters related to the dialogue
information are in contradiction to 3GPP TS 29.002, Mobile
Application Part (MAP) Specification, in version 2 (or higher)
dialogues, for example, the presence/absence/value of a parameter
is not as expected in the context.
3.2.2
Mobile Service operations
3.2.2.1
UpdateLocation
This operation is implemented in version 1, 2, and 3 dialogues.
It is invoked by the VLR and confirmed by the HLR.
The MAP version used by the VLR for location updating is stored to the
HLR database. In forthcoming dialogue initiations for stand-alone
InsertSubscriberData and DeleteSubscriberData from the HLR towards
the VLR, the HLR assumes the stored version as the highest version
supported by the VLR.
The Signalling Point Code (SPC) is stored as a VLR_SPC in the HLR data,
if the SPC of the VLR is received in the calling party address field of the
Signalling Connection Control Part (SCCP) message. The SPC is used to
address the VLR in forthcoming transactions initiated by the HLR.
DN98628099
Issue 10-1 en
27 (264)
Invocation parameters
.
imsi
This parameter is a key to subscriber data in the HLR database. The
error UnknownSubscriber is returned if the IMSI is unknown.
As an optional feature, the IMSI is analysed to see if it is an Alias
IMSI or a Database IMSI, and the information of the active IMSI
(Alias or Database) will be stored in the subscriber data in the HLR
database.
locationInfo
The received MSC number is stored to subscriber data. In version 1
the locationInfo may contain roamingNumber, which is interpreted by
the HLR as the MSC number.
vlrNumber
This parameter is stored to subscriber data and used as an index to
the visited PLMN parameters for roaming and service checking by
the HLR.
lmsi
This parameter is ignored, not stored to subscriber data.
extensionContainer
May contain the UlArgType. The extension identifier is {iso(1)
member-body(2) bsi(826) disc(0) ericsson(1249)
gsmNetworkApplicationsDefinition(58) gsm-Map(1) gsm-Map-Ext
(0)}.
.
adc
Handled similarly as the imeisv parameter inside the standard
add-Info parameter.
28 (264)
vlr-Capability
.
supportedCamelPhases
Phase 1 is assumed if supportedCamelPhases parameter is
not received.
Supported values are: phase1, phase2, phase3, and phase4.
.
solsaSupportIndicator
This parameter is ignored.
.
istSupportIndicator
.
superChargerSupportedInServingNetworkEntity
DN98628099
Issue 10-1 en
The presence of this parameter indicates that the VLR

supports Super Charger functionality.
.
sendSubscriberData
If received, the HLR updates the subscriber data
normally to the VLR.
.
subscriberDataStored
This parameter contains the Age Indicator which is
stored in the subscriber data in the VLR. The HLR
compares this Age Indicator to the ones stored in the
HLR (subscriber data specific Age Indicator, and HLR
network element specific Age Indicators). If the Age
Indicator received from the VLR is outdated, the
subscriber data is inserted normally to the VLR, in the
location updating dialogue.
If this parameter is not received, the HLR will not include the
Age Indicator in the InsertSubscriberData message.
longFTN-Supported
supportedLCS-CapabilitySets
The information about the supported LCS capability sets is
stored in the HLR database, per VLR address basis. When
this parameter is present, it may indicate that the VLR
supports LCS capability set 1, or set 2, or set 3, or a
combination of those, or none of those. If this parameter is not
received, the HLR assumes that the VLR supports LCS
capability set 1.
offeredCamel4CSIs
It indicates the CAMEL 4 CSIs offered in the VMSC/VLR. May
contain o-csi, d-csi, vt-csi and mt-sms-csi.
It is stored to the subscriber data in the HLR database. The
HLR will take this information into account when indicating
CAMEL subscription information towards the VLR (with
InsertSubscriberData operation).
informPreviousNetworkEntity
If this indication is received, the HLR will cancel the location from the
previous network entity. Otherwise, the previous network entity will
not be informed of the location update, if the HLR data shows that
the previous network entity supports Super Charger functionality.
cs-LCS-NotSupportedByUE
DN98628099
Issue 10-1 en
29 (264)
v-gmlc-Address
add-Info
This information is used for the Terminal Management service.
When the data in the HLR database indicates that this is the first
location update of the subscriber (either from a VLR or from an
SGSN), the Terminal Management Server is informed.
.
imeisv
The IMEISV is stored to the subscriber data in the HLR
database. When the data in the HLR database indicates that
the IMEISV has been changed, the Terminal Management
Server is informed.
.
skipSubscriberDataUpdate
If this parameter is present, it indicates that the service is
solely used to inform the HLR about the change of IMEISV. In
that case the HLR does not update the subscriber data to the
VLR, but answers directly with an UpdateLocation-result.
Result parameters
.
hlr-Number
It contains the HLR address from the HLR configuration data.
As an optional feature the value of the hlr-Number may be modified
(instead of using the default value from HLR configuration), and the
possible modification is based on the analysis of the subscriber's
IMSI.
ulResExtension (proprietary)
This parameter may be sent in version 2 results and it contains the
following items:
.
mwd-Set
This parameter is sent from the HLR database only if Message
Waiting Data is set for the subscriber.
extensionContainer
This parameter may contain the ulResExtension in version 3. The
extensionId is {0 34 2}.
add-Capability
This parameter is sent if the Automatic Device Detection feature is
active in the HLR.
30 (264)
DN98628099
Issue 10-1 en
Error causes
The possible error causes are as follows:
.
SystemFailure
It is sent if InsertSubscriberData operation fails between HLR and
VLR.
DataMissing
It is not used.
UnexpectedDataValue
It is sent if an erroneous value is found in the invocation parameters.
UnknownSubscriber
It is sent if the IMSI is unknown, or if the subscriber status in the HLR
is deactivated.
3.2.2.2
RoamingNotAllowed
.
plmnRoamingNotAllowed
It is sent if the MS is not allowed to roam into the PLMN
indicated by the VLR-number.
.
operatorDeterminedbarring
It is sent if the subscriber has an active barring, which causes
the roaming to be denied.
CancelLocation
It is invoked by the HLR and confirmed by the VLR or SGSN.
.
Operation timer: 15 seconds
Re-attempts in case procedure fails: the MMI-initiated operation (that

is, CancelLocation is not triggered by a location update) repeated
0..3 times (depending on HLR configuration)
SCCP address: VLR address in subscriber data used as Global

Title, or VLR SPC used if it is known in the HLR
.
imsi
From subscriber data in the HLR.
DN98628099
Issue 10-1 en
31 (264)
As an optional feature, if the CancelLocation is made because of a

location update, an Alias IMSI or a Database IMSI is sent,
depending on which one was marked active in the subscriber data
before the location update.
.
imsi-WithLMSI
This parameter is sent in version 2 dialogues if proprietary extension
canLocExtension is sent.
lmsi
This parameter is sent in version 2 dialogues inside the imsiWithLMSI SEQUENCE, with value '00000000'O (not used).
cancellationType
This parameter is sent when the CancelLocation is sent towards an
SGSN.
.
updateProcedure
This parameter indicates that the CancelLocation results from
location update and the SGSN has to wait until it has
forwarded all the packets for the subscriber.
.
subscriptionWithdraw
This parameter indicates that the CancelLocation results from
subscriber removal/deactivation in the HLR.
canLocExtension (proprietary)
This parameter may be sent in version 2 invocations (if Feature 777:
Termination of Calls on MAP_cancel_location is active). It contains:
.
termination
Bit 1 is set when the termination of calls is requested, other bits
are not used.
extensionContainer
This parameter may contain the canLocExtension in version 3. The
Result parameters
The result is empty in versions 1 and 2.
The possible extension parameters in a version 3 result are ignored.
Error causes
32 (264)
DN98628099
Issue 10-1 en
3.2.2.3
DataMissing
UnexpectedDataValue
UnidentifiedSubscriber
PurgeMS
This operation is implemented in version 2 and 3 dialogues. No
corresponding version 1 operation exists.
It is invoked by the VLR or SGSN and confirmed by the HLR.
.
imsi
This parameter is a key to the subscriber data in the HLR database.
In error cases an Abort is sent with userSpecificReason (if the IMSI
is not known in the HLR, or if it is the IMSI of a sequential/parallel/
intelligent alerting group).
IMSI or a Database IMSI, and whether Alias or Database IMSI is
marked as active in the subscriber data. If the PurgeMS contains an
IMSI which is not active, the purging is not done, instead an Abort is
sent back to the VLR (or SGSN).
vlr-Number
If the received vlr-Number matches the VLR-number in the
subscriber data, the VLR-number is deleted from the subscriber
data.
sgsn-Number
If the received sgsn-Number matches the SGSN-number in the
subscriber data, the SGSN-number is deleted from the subscriber
data.
Result parameters
A positive result is sent also when the VLR-number or SGSN-number in
the subscriber data does not match the received number.
.
freezeTMSI
This parameter is sent if the received vlr-Number matches the stored
VLR-number.
DN98628099
Issue 10-1 en
33 (264)
freezeP-TMSI
This parameter is sent if the received sgsn-Number matches the
stored SGSN-number.
Error causes
.
DataMissing
It is never sent.
UnexpectedDataValue
It is sent if an inappropriate value is received in one of the invocation
parameters.
UnknownSubscriber
It is never sent.
3.2.2.4
UpdateGPRSLocation
This operation is implemented in version 3 dialogues only. No
corresponding version 1 or 2 operation exists.
It is invoked by the SGSN and confirmed by the HLR.
If the SPC of the SGSN is received in the calling party address field of the
SCCP message, the SPC is stored as a SGSN_SPC in the HLR data. It is
used to address the SGSN in forthcoming transactions initiated by the
HLR.
.
imsi
This parameter is a key to subscriber data in the HLR database. If
the IMSI is unknown, the error UnknownSubscriber is returned.
IMSI or a Database IMSI, and the information of the active IMSI
(Alias or Database) will be stored in the subscriber data in the HLR
database.
34 (264)
sgsn-Number
DN98628099
Issue 10-1 en
This parameter is stored to subscriber data. It is used as an index to

the visited PLMN parameters for roaming and service checking by
the HLR.
.
sgsn-Address
This parameter is ignored and not stored to subscriber data.
sgsn-Capability
This parameter contains:
.
.
The presence of this parameter indicates that the SGSN
.
sendSubscriberData
If received, the HLR updates the subscriber data
normally to the SGSN.
.
subscriberDataStored
This parameter contains the Age Indicator which is
stored in the subscriber data in the SGSN. The HLR
compares this Age Indicator to the ones stored in the
HLR (subscriber data specific Age Indicator, and HLR
network element specific Age Indicators). If the Age
Indicator received from the SGSN is outdated, the
subscriber data is inserted normally to the SGSN, in the
location updating dialogue.
If this parameter is not received, the HLR will not include the
Age Indicator in the InsertSubscriberData message.
.
gprsEnhancementsSupportIndicator
This parameter is stored to HLR data.
.
This parameter is stored to HLR data.
.
This information is stored to the HLR database, per SGSN
address basis.
Only the lcsCapabilitySet2 and lcsCapabilitySet3 information
is checked, the lcsCapabilitySet1 information is ignored. If this
parameter is not present, the HLR assumes that the SGSN
does not support LCS at all.
.
offeredCamel4CSIs
It indicates the CAMEL 4 CSIs offered in the SGSN. May
contain mg-csi, mt-sms-csi and psi-enhancements.
DN98628099
Issue 10-1 en
35 (264)
It is stored to the subscriber data in the HLR database. The

HLR will take this information into account when indicating
CAMEL subscription information towards the SGSN (with
InsertSubscriberData operation).
.
If this indication is received, the HLR will cancel the location from the
previous network entity. Otherwise, the previous network entity will
not be informed of the location update, if the HLR data shows that
the previous network entity supports Super Charger functionality.
ps-LCS-NotSupportedByUE
v-gmlc-Address
add-Info
This information is used for the Terminal Management service.
When the data in the HLR database indicates that this is the first
location update of the subscriber (either from a VLR or from an
SGSN), the Terminal Management Server is informed.
.
imeisv
The IMEISV is stored to the subscriber data in the HLR
database. When the data in the HLR database indicates that
the IMEISV has been changed, the Terminal Management
Server is informed.
.
skipSubscriberDataUpdate
If this parameter is present, it indicates that the service is
solely used to inform the HLR about the change of IMEISV. In
that case the HLR does not update the subscriber data to the
SGSN, but answers directly with an UpdateLocation-result.
Result parameters
.
hlr-Number
IMSI.
36 (264)
DN98628099
Issue 10-1 en
extensionContainer
This parameter is never sent.
add-Capability
This parameter is sent if the Automatic Device Detection feature is
active in the HLR.
Error causes
.
SystemFailure
It is sent if the InsertSubscriberData operation fails between the HLR
and SGSN.
UnexpectedDataValue
UnknownSubscriber
contains:
.
imsiUnknown
Sent if the IMSI is not known in the HLR.
.
gprsSubscriptionUnknown
Sent if the subscriber has no GPRS subscription (only GSM or
UMTS subscription).
3.2.2.5
RoamingNotAllowed
.
It is sent if the MS is not allowed to roam into the PLMN
indicated by the sgsn-Number.
.
operatorDeterminedbarring
It is sent if the subscriber has an active barring which causes
roaming to be denied.
ProvideSubscriberInfo
DN98628099
Issue 10-1 en
37 (264)
Re-attempts in case procedure fails: not used
SCCP address: SPC or GT, VLR address or SGSN address from

subscriber data
.
imsi
This parameter is from subscriber data in the HLR database.
As an optional feature, an Alias IMSI is sent instead of the IMSI
which is in the database, if the Alias IMSI is marked as active in the
subscriber data in the HLR database.
lmsi
requestedInfo
This parameter contains:
.
locationInformation
This parameter is sent if indicated by the HLR's 'Subscriber
Information in SRI ack indicator' for location information.
This parameter is sent if requested by the gsmSCF in
AnyTimeInterrogation invocation.
.
subscriberState
This parameter is sent if indicated by the HLR's 'Subscriber
Information in SRI ack indicator' for subscriber state.
Sent if requested by the gsmSCF in AnyTimeInterrogation
invocation.
.
currentLocation
This parameter is sent if the HLR supports the function 'current
location retrieval' and if the HLR receives the 'Current
Location' parameter in AnyTimeInterrogation invocation.
As an optional feature, if the Current Location Provided flag is
set for the subscriber, the currentLocation parameter is
included in the ProvideSubscriberLocation, even if it is not
present in the AnyTimeInterrogation invocation. However, the
currentLocation parameter is not included in the
ProvideSubscriberLocation (even if it is present in the
AnyTimeInterrogation invocation), if the current location query
is not allowed according to the subscriber data and PLMN
parameters corresponding to the subscriber's current VLR
address.
38 (264)
DN98628099
Issue 10-1 en
imei
This parameter is sent if the HLR received the 'imei' parameter
in AnyTimeInterrogation invocation, and if the related feature is
configured as supported in the HLR.
Result parameters
The received data is not stored in the HLR but is forwarded to the GMSC
(in SendRoutingInfo result) or gsmSCF (in AnyTimeInterrogation result).
Note that the vlr-number received in the ProvideSubscriberInfo-result is
not used in the SRI-result or ATI-result, instead, the VLR address from the
subscriber data in HLR database is sent in the vlr-number parameter in
SRI-result or ATI-result.
.
locationInformation
This parameter is supported.
subscriberState
extensionContainer
This parameter is ignored and not forwarded to the gsmSCF /
GMSC.
locationInformationGPRS
ps-SubscriberState
imei
ms-Classmark2
GMSC.
gprs-MS-Class
GMSC.
Error causes
DN98628099
Issue 10-1 en
39 (264)
DataMissing
UnexpectedDataValue
In an error situation (an error cause is received from the VLR, or no

response is received from the VLR):
3.2.2.6
LocationInformation value 'VLRNumber' is returned if

LocationInformation was requested by the HLR's 'Subscriber
Information in SRI ack indicator' for location information, or by
AnyTimeInterrogation from the gsmSCF.
SubscriberState value 'NotProvidedFromVLR' is returned if

SubscriberState was request by the HLR's 'Subscriber Information in
SRI ack indicator' for subscriber state, or by AnyTimeInterrogation
from the gsmSCF.
The error SystemFailure is returned, if only the imei was requested

in AnyTimeInterrogation.
AnyTimeInterrogation
As an optional feature because of multivendor interworking, also nonstandard version 1 dialogue is supported.
It is invoked by the gsmSCF and confirmed by the HLR.
.
subscriberIdentity
This parameter contains one of the followings:
.
imsi
This parameter is a key to subscriber data in the HLR
database. An UnknownSubscriber error is sent in error cases
(if the IMSI is not known in the HLR, or if it is the IMSI of a
sequential/parallel/intelligent alerting group).
As an optional feature, also an Alias IMSI (according to the
HLR configuration) can be used as a key to the subscriber
data.
.
msisdn
database. An UnknownSubscriber error is sent in error cases.
40 (264)
DN98628099
Issue 10-1 en
If the MSISDN is the number of a sequential/parallel/intelligent

alerting group, the operation is performed for the member,
which is the primary device for Location Services.
.
requestedInfo
This parameter is forwarded to the VLR (or SGSN) in
ProvideSubscriberInfo.
As an optional feature, if the ProvideSubscriberInfo is denied
according to the subscriber data and the PLMN parameters
corresponding to the subscriber's current VLR address, the HLR
does not initiate the ProvideSubscriberInfo request, but responses to
the AnyTimeInterrogation based on the subscriber data in the HLR.
.
locationInformation
This parameter is supported and forwarded to the VLR (or
SGSN).
.
subscriberState
SGSN).
.
extensionContainer
This parameter is ignored and not forwarded to the VLR (or
SGSN).
.
currentLocation
SGSN).
As an optional feature, the currentLocation parameter is not
forwarded to the VLR, if the current location query is not
allowed according to the subscriber data and PLMN
parameters corresponding to the subscriber's current VLR
address.
.
requestedDomain
This parameter is checked to see whether the
ProvideSubscriberInfo is to be sent to the VLR or to the SGSN.
If the requestedDomain parameter is not received, the default
value cs-Domain is assumed.
If the requestedDomain indicates PS domain, the
ProvideSubscriberInfo operation is sent to the SGSN only if
the SGSN has indicated the support of CAMEL phase 4 (if not,
the error ATI-NotAllowed is returned).
.
imei
This parameter is optionally supported and forwarded to the
VLR (or SGSN).
.
ms-classmark
DN98628099
Issue 10-1 en
41 (264)
This parameter is ignored and not forwarded to the VLR (or

SGSN).
.
gsmSCF-Address
Result parameters
The parameters inside the subscriberInfo received from the VLR or SGSN
in ProvideSubscriberInfo are sent to the gsmSCF in AnyTimeInterrogation
result, except in the belowmentioned cases when parameter values are
derived by the HLR:
.
locationInformation
From ProvideSubscriberInfo-result.
.
ageOfLocationInformation
.
geographicalInformation
.
vlr-number
The vlr-number received in the locationInformation in
ProvideSubscriberInfo-result is not used in the ATI-result,
instead, the VLR address from the subscriber data in the HLR
database is sent in the vlr-number parameter in ATI-result.
.
locationNumber
.
cellGlobalIdOrServiceAreaIdOrLAI
.
selectedLSA-Id
.
msc-Number
The msc-Number received in the locationInformation in
ProvideSubscriberInfo-result is not used in the ATI-result,
instead, the MSC address from the subscriber data in the HLR
database is sent in the msc-number parameter in ATI-result.
.
geodeticInformation
.
currentLocationRetrieved
.
sai-Present
subscriberState
This parameter is from ProvideSubscriberInfo-result.
If no subscriber state information is received from the VLR, the value
notProvisionedFromVLR is sent.
42 (264)
DN98628099
Issue 10-1 en
.
.
.
.
.
.
.
.
.
cellGlobalIdOrServiceAreaIdOrLAI
routeingAreaIdentity
sgsn-Number
If this information is not received from the SGSN (for example,
the ProvideSubscriberInfo dialogue fails), the SGSN address
from the subscriber data in the HLR is sent.
selectedLSAIdentity
sai-Present
geodeticInformation
ps-SubscriberState
.
notProvidedFromSGSN
If the state information is not received from the SGSN (for
example, the ProvideSubscriberInfo dialogue fails), parameter
notProvidedFromSGSN is sent.
.
ps-Detached
This parameter is sent if there is no SGSN address, or if the
'SGSN area restricted' flag is on in the subscriber data in the
HLR.
.
ps-AttachedNotReachableForPaging
.
ps-AttachedReachableForPaging
.
ps-PDP-ActiveNotReachableForPaging
.
ps-PDP-ActiveReachableForPaging
.
netDetNotReachable
imei
This parameter is forwarded from ProvideSubscriberInfo-result to the
gsmSCF.
ms-Classmark2
gprs-MS-Class
If no VLR number is stored in the subscriber data, ProvideSubscriberInfo

operation is not started, and either of the following results is produced:
DN98628099
Issue 10-1 en
43 (264)
if LocationInformation was requested by the HLR's 'Subscriber

Information in SRI ack indicator' for location information, or by
AnyTimeInterrogationArg from the gsmSCF, no LocationInformation
is returned
if SubscriberState was request by the HLR's 'Subscriber Information

in SRI ack indicator' for subscriber state or by
AnyTimeInterrogationArg from the gsmSCF, SubscriberState value
'NetDetNotReachable = MS Purged' is returned.
Error causes
.
SystemFailure
It is sent if only the imei was requested in AnyTimeInterrogation, but
the ProvideSubscriberInfo dialogue towards the VLR (or the SGSN)
fails to retrieve the imei.
ATI-NotAllowed
It is sent if the HLR setting indicates that AnyTimeInterrogation is not
allowed or if CAMEL service is not active in the HLR.
DataMissing
It is sent if neither LocationInformation nor SubscriberState is
requested.
UnexpectedDataValue
UnknownSubscriber
It is sent if the IMSI is not known in the HLR, or if it is the IMSI of a
sequential/parallel/intelligent alerting group.
3.2.2.7
AnyTimeSubscriptionInterrogation
This operation is implemented in version 3 dialogues. No corresponding
version 1 or 2 operations exist.
It is invoked by the gsmSCF and confirmed by the HLR.
44 (264)
DN98628099
Issue 10-1 en
.
subscriberIdentity
This parameter is a key to subscriber data in the HLR database,
either IMSI or MSISDN. The error UnknownSubscriber is returned if
the IMSI/MSISDN is unknown.
requestedSubscriptionInfo
This parameter indicates the type(s) of subscriber information being
requested.
.
requestedSS-Info
This parameter indicates a Call Forwarding or a Call Barring
supplementary service.
.
odb
.
requestedCAMEL-SubscriptionInfo
This parameter indicates which CSI is requested. Values oCSI, t-CSI, vt-CSI, tif-CSI, gprs-CSI, mo-sms-CSI, ss-CSI, mCSI, d-csi and mt-sms-csi are supported. If other values are
received, the parameter is ignored.
.
supportedVLR-CAMEL-Phases
.
supportedSGSN-CAMEL-Phases
.
additionalRequestedCAMEL-SubscriptionInfo
This parameter indicates which CSI is requested. Values mtsms-CSI and mg-csi are supported. If other values are
received, the parameter is ignored.
gsmSCF-Address
This parameter indicates the address of the interrogating gsmSCF. It
is checked against a list of allowed gsmSCFs in the subscriber data
in the HLR database, and in error cases the error ATSI-NotAllowed
is sent.
longFTN-Supported
Result parameters
.
callForwardingData
DN98628099
Issue 10-1 en
45 (264)
callBarringData
odb-Info
camel-SubscriptionInfo
The value of this parameter is read from the HLR database,
indicates the supported CAMEL phases of the VMSC/VLR where
the subscriber is roaming. When the supportedVLR-CAMEL-Phases
parameter indicates the support of CAMEL phase 4, the
offeredCamel4CSIsInVLR parameter is also sent.
indicates the supported CAMEL phases of the SGSN where the
subscriber is roaming. When the supportedSGSN-CAMEL-Phases
parameter indicates the support of CAMEL phase 4, the
offeredCamel4CSIsInSGSN parameter is also sent.
offeredCamel4CSIsInVLR
indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR where
the subscriber is roaming. Sent if the supportedVLR-CAMELPhases parameter indicates the support of CAMEL phase 4.
It may contain o-csi, d-csi, vt-csi and mt-sms-csi.
offeredCamel4CSIsInSGSN
indicates the CAMEL phase 4 CSIs offered in the SGSN where the
subscriber is roaming. Sent if the supportedSGSN-CAMEL-Phases
parameter indicates the support of CAMEL phase 4.
May contain mg-csi, mt-sms-csi and psi-enhancements.
Error causes
46 (264)
DN98628099
Issue 10-1 en
ATSI-NotAllowed
It is sent if the operation is not allowed for the subscriber from the
indicated gsmSCF (the received gsmSCF-Address is checked
against a list of allowed gsmSCFs in the subscriber data in the HLR
database).
DataMissing
It is never sent.
UnexpectedDataValue
UnknownSubscriber
It is sent if the IMSI/MSISDN in the invocation is unknown.
BearerServiceNotProvisioned
TeleserviceNotProvisioned
CallBarred
IllegalSS-Operation
SS-NotAvailable
InformationNotAvailable
It is sent if the requested information is not available in the HLR.
3.2.2.8
AnyTimeModification
IIt is ivoked by the gsmSCF and is confirmed by the HLR.
As an optional feature, this operation is invoked by the HLR (emulating a
gsmSCF) towards another HLR, to modify the data of a hunting group, or a
hunting group member. In the receiving HLR, the presence of the
proprietary MSISDN extension for sender MSISDN differentiates normal
AnyTimeModification operation sent by a gsmSCF from the operation for
hunting group data synchronization purpose.
DN98628099
Issue 10-1 en
47 (264)
.
subscriberIdentity
This parameter is a key to subscriber data in the HLR database,
either IMSI or MSISDN. The error UnknownSubscriber is returned if
the IMSI/MSISDN is unknown.
This parameter contains the group MSISDN of the hunting group (or
the member MSISDN of the hunting group), when the
AnyTimeModification is sent from the HLR towards another HLR to
update the data of all members of the hunting group (or one member
of the hunting group).
gsmSCF-Address
This parameter indicates the address of the interrogating gsmSCF. It
is checked against a list of allowed gsmSCFs in the subscriber data
in the HLR database, and in error cases the error ATM-NotAllowed is
sent.
This parameter contains a dummy address, when the
AnyTimeModification is sent from the HLR towards another HLR to
update the data of the hunting group. In this case the list of allowed
gsmSCFs is not checked.
modificationRequestFor-CF-Info
This parameter indicates the data of call forwarding.
.
ss-Code
If only the ss-Code is present, or only the ss-Code and the
basicService are present in the ATM request, all Call
Forwarding data belonging to this Supplementary Service and
Basic Service is erased.
.
basicService
If only the ss-Code and the basicService are present in the
ATM request, all Call Forwarding data belonging to this
Supplementary Service and Basic Service is erased.
.
ss-Status
If a valid ss-Status is present in the ATM request, the
Supplementary Status state transition is performed. Activation/
deactivation and registration/erasure are allowed from the
gsmSCF.
.
forwardedToNumber
48 (264)
DN98628099
Issue 10-1 en
The modification of forwardedToNumber is accepted only if the

ss-Status is registered. If the ss-Status is not received with the
forwardedToNumber, it is interpreted as registration.
.
forwardedToSubaddress
This parameter is ignored if the forwardedToNumber
parameter was also received. If only the
forwardedToSubaddress is received (without the
forwardedToNumber) the error InformationNotAvailable is
sent.
.
noReplyConditionTime
The modification of noReplyConditionTime is accepted only if
the ss-Status is registered.
.
modifyNotificationToCSE
This parameter indicates whether or not the change of CF data
has to trigger the NoteSubscriberDataModified operation.
When the AnyTimeModification is sent from the HLR towards
another HLR to update the data of the hunting group, this data
contains the information about the modified data: ss-Code and ssStatus, and optionally also basicService and forwardedToNumber.
.
modificationRequestFor-CB-Info
This parameter indicates the data of call barring.
.
ss-Code
If only the ss-Code is present, or only the ss-Code and the
basicService are present in the ATM request, then all Call
Barring data belonging to this Supplementary Service and
Basic Service is erased.
.
basicService
If only the ss-Code and the basicService are present in the
ATM request, then all Call Barring data belonging to this
Supplementary Service and Basic Service is erased.
.
ss-Status
If a valid ss-Status is present in the ATM request, then the
Supplementaty Status state transition is performed. Activation/
deactivation is allowed from the gsmSCF.
.
password
The received password is stored to the subscriber data in the
HLR database.
.
wrongPasswordAttemptsCounter
The received counter value is stored to the subscriber data in
the HLR database.
.
DN98628099
Issue 10-1 en
49 (264)
This parameter indicates whether or not the change of CB data

has to trigger the NoteSubscriberDataModified operation.
When the AnyTimeModification is sent from the HLR towards
another HLR to update the data of the hunting group, this data
contains the information about the modified data: ss-Code and ssStatus, and optionally basicService and password.
.
modificationRequestFor-CSI
This parameter indicates the CAMEL subscription information.
CAMEL phase 3 and phase 4 services are supported.
.
requestedCamel-SubscriptionInfo
Values o-CSI, t-CSI, vt-CSI, tif-CSI, gprs-CSI, mo-sms-CSI,
ss-CSI, m-CSI, d-csi and mt-sms-csi are supported.
This parameter is ignored, if also the
additionalRequestedCAMEL-SubscriptionInfo parameter is
received.
.
This parameter is stored to subscriber data and indicates
whether or not the change of CSI data has to trigger the
NoteSubscriberDataModified operation.
.
modifyCSI-State
This parameter indicates whether the CSI is to be activated or
deactivated and the information is stored to subscriber data.
The data is updated to the VLR or SGSN with
InsertSubscriberData operation.
.
additionalRequestedCAMEL-SubscriptionInfo
Values mt-sms-CSI and mg-csi are supported.
extensionContainer
This parameter contains the AnyTimeModArgExt, when the
operation is sent from the HLR to another HLR. The extension
identifier is {0 34 26}.
.
senderMSISDN
This parameter contains the primary MSISDN of the hunting
group member, who has made a Supplementary Service
modification; or the MSISDN of the hunting group, if the
hunting group data has been modified by a gsmSCF or if the
data of all members have to be synchronized because of a
modification in the data of one member.
longFTN-Supported
50 (264)
modificationRequestFor-ODB-data
DN98628099
Issue 10-1 en
This parameter indicates the modification of ODB data.

.
odb-data
If the modified ODB categories are configured as supported in
the HLR, the new data is stored to subscriber data (the existing
ODB data is overwritten), and the data is updated to the VLR
or SGSN with InsertSubscriberData operation.
If the modifed data contains categories that are not supported
in the HLR, those are indicated as deactive in the
AnyTimeModification result. If none of the modified categories
are supported, the error InformationNotAvailable is sent.
.
This parameter is stored to subscriber data and it indicates
whether or not the change of ODB data has to trigger the
NoteSubscriberDataModified operation.
Result parameters
.
ss-InfoFor-CSE
This parameter contains the call forwarding or call barring data after
modification.
This parameter contains the CAMEL subscription data after
modification. CAMEL phase 3 and phase 4 services are supported.
odb-Info
This parameter contains the ODB subscription data after
modification.
Error causes
.
ATM-NotAllowed
It is sent if the operation is not allowed for the subscriber from the
indicated gsmSCF (the received gsmSCF-Address is checked
against a list of allowed gsmSCFs in the subscriber data in HLR
database).
DataMissing
It is never sent.
DN98628099
Issue 10-1 en
UnexpectedDataValue
51 (264)
Sent if an erroneous value is found in the invocation parameters.

.
UnknownSubscriber
It is sent if the IMSI/MSISDN in the invocation is unknown.
CallBarred
IllegalSS-Operation
SS-SubscriptionViolation
SS-ErrorStatus
SS-Incompatibility
InformationNotAvailable
It is sent if the indicated information does not exist in the HLR.
3.2.2.9
NoteSubscriberDataModified
it is invoked by the HLR and confirmed by the gsmSCF.
.
SCCP address: GT, the gsmSCF address from subscriber's CAMEL

CSI subscription data in the HLR database
The HLR maintains a list of gsmSCF address(es) for Call Forwarding
Data, Call Barring Data, ODB data, OCCF data and CSI. When any
of these items has been modified, a notification is sent to each
gsmSCF in the list.
.
imsi
This parameter is the IMSI from the subscriber data in the HLR
database.
52 (264)
DN98628099
Issue 10-1 en

.
msisdn
This parameter is the MSISDN from the subscriber data in the HLR
database.
forwardingInfoFor-CSE
This parameter is sent when the forwarding information has been
modified.
callBarringInfoFor-CSE
This parameter is sent when the barring information has been
modified.
odb-Info
This parameter is sent when the ODB information has been
modified.
This parameter is sent when the CAMEL information has been
modified.
allInformationSent
This indicator is always included (the result is never split into several
segments).
Result parameters
.
extensionContainer
Error causes
DN98628099
Issue 10-1 en
DataMissing
UnexpectedDataValue
UnknownSubscriber
53 (264)
3.2.2.10
SendAuthenticationInfo
This operation is implemented in version 2 and 3 dialogues. The
SendParameters operation is used in version 1.
Invoked by the VLR or SGSN and confirmed by the HLR.
In case of a segmented dialogue, the timer for waiting the subsequent
invocation (after the response has been sent) is 30 seconds. If the timer
expires, the dialogue towards the VLR is aborted.
.
imsi
This parameter is a key to subscriber data in the Authentication
Centre database. In error cases UnknownSubscriber is returned.
numberOfRequestedVectors
This parameter indicates how many vectors should be sent to the
requesting node.
In UMTS, only 1 quintuplet fits into one response message, but the
VLR/SGSN can request up to 5 quintuplets. If the requested amount
of quintuplets cannot fit into a single response, and segmentation is
supported by the requesting node (the segmentationProhibited
parameter is not present in the invocation), AuC sends only one
segment (1 quintuplet) at a time, and waits for subsequent requests
from the VLR/SGSN.
segmentationProhibited
If received, the HLR does not send the result within a TCCONTINUE message, in which case the number of returned vectors
may be smaller than requested by the VLR/SGSN with the
numberOfRequestedVectors parameter.
immediateResponsePreferred
re-synchronisationInfo
If received, the HLR checks and re-synchronises the authentication
sequence number, before returning the new authentication vectors.
54 (264)
requestingNodeType
DN98628099
Issue 10-1 en
This information is used as part of the sequence number generation

procedure.
If not received, the requesting node type is treated as unknown.
Result parameters
In version 3 dialogues, the result is sent in more than one segment, if
'segmentationProhibited' was not received in the invocation, and if the
requested vectors do not fit in one result message.
.
AuthenticationSetList
Either the tripletList or the quintupletList is returned from the AuC
database depending on whether the subscriber is marked as a GSM
or as a UMTS subscriber.
Error causes
.
SystemFailure
It is never sent.
DataMissing
It is never sent.
UnexpectedDataValue
It is sent if a semantically erroneous value is found in the imsi
parameter of the invocation.
UnknownSubscriber
It is sent if the IMSI is not known in the AuC.
3.2.2.11
AuthenticationFailureReport
DN98628099
Issue 10-1 en
55 (264)
.
imsi
This parameter is a key to subscriber data in the HLR database. In
error cases, an UnknownSubscriber error is sent (if the IMSI is not
known in the HLR, or if it is the IMSI of a sequential/parallel/
intelligent alerting group).
failureCause
The received cause value is checked against the configuration in the
HLR to determine whether location cancellation for the subscriber
has to be made. The location cancellation is made only if the
received VLR/SGSN address matches the address in the subscriber
data in the HLR database.
re-attempt
accessType
rand
vlr-Number
This parameter identifies the network element where the
authentication failure occurred. It is used to determine whether
location cancellation needs to be made (see parameter
failureCause).
sgsn-Number
This parameter identifies the network element where the
authentication failure occurred. It is used to determine whether
location cancellation needs to be made (see parameter
failureCause).
Result parameters
there are no parameters sent in the result.
56 (264)
DN98628099
Issue 10-1 en
Error causes
.
SystemFailure
It is never sent.
UnexpectedDataValue
It is sent if an erroneous value is found in the imsi parameter of the
invocation.
UnknownSubscriber
It is sent if the IMSI in the invocation is unknown, or if it is the IMSI of
a sequential/parallel/intelligent alerting group.
3.2.2.12
CheckIMEI
This operation is implemented in version 1 and 2 dialogues.
It is invoked by the MSC or SGSN and confirmed by the EIR.
If the optional feature (Feature 143: EIR Functions; Full EIR) is not active,
the reception of an invocation to this operation causes a TC-Abort to be
returned.
.
imei
This parameter is a key to white, grey and black lists in the EIR
database. In error cases UnknownEquipment is returned.
The software version number is accepted but discarded in version 2
dialogues.
As an optional feature, the received imei and imsi are forwarded to
an external system for further processing.
imsi
As an optional feature, the received imei and imsi are forwarded to
an external system for further processing.
Result parameters
.
DN98628099
Issue 10-1 en
EquipmentStatus
57 (264)
From EIR database. It contains one of the following values:

.
whiteListed
.
blackListed
.
greyListed
Error causes
.
UnknownEquipment
It is sent if the IMEI is not found on any of the lists in the EIR
database.
SystemFailure
It is never sent.
UnexpectedDataValue
It is sent if an erroneous value is found in the imei parameter of the
invocation and used only in version 1 dialogues.
DataMissing
It is never sent.
3.2.2.13
InsertSubscriberData
.
Re-attempts in case procedure fails:

It is not used in location updating procedure initiated
InsertSubscriberData.
HLR initiated independent operation is repeated 0..3 times in a 0..10
seconds interval (depending on HLR configuration). The re-attempt
is made in all failure cases, except when the VLR reports
'UnidentifiedSubscriber'.
58 (264)
SCCP address: SPC or GT, VLR or SGSN address from subscriber

data, or calling party address in update location, or supplementary
service operation
DN98628099
Issue 10-1 en
.
imsi
This parameter is from HLR database. It is used only in the first
invocation in a segmented dialogue.
SubscriberData
See SubscriberData.
DN98628099
Issue 10-1 en
extensionContainer
.
May contain the EMO-IN OICK information, the
SubscriptionType information, and/or the DualNumbering
information: the ExtensionType is IsdArgType. The extension
identifier is {iso(1) member-body(2) bsi(826) disc(0) ericsson
(1249) gsmNetworkApplicationsDefinition(58) gsm-Map(1)
gsm-Map-Ext(0)}. Optional feature. When this extension is
included, it is placed as the first extension in the
extensionContainer (if also the IsdArgExt extension is
included, it is placed as the second extension in the same
extensionContainer).
The IsdArgData in IsdArgType contains:
.
privateFeatureCode
Contains the privateFeatureCode '00000110'B (OICK) or
'00000010'B (STYPE). When the DualNumbering
information is sent in the privateFeatureData, this
parameter privateFeatureCode is not included.
.
privateFeatureData
Contains the OickInfo, the SubscriptionTypeInfo or the
DualNumberingInfo.
OickInfo contains:
.
ss-status
It is provisioned and activated.
.
inCategoryKey
It contains a decadic value (only decimal digits).
SubscriptionTypeInfo contains:
.
subscriptionType
It contains a value between 1..127, converted from
the internal RoutingCategory value from the
59 (264)
DualNumberingInfo contains:
.
dualMsisdn
The MSISDN of the alternate line.
This parameter may contain the IsdArgExt in version 3. The
extension identifier is {0 34 0}.
See section IsdArgExt.
naea-PreferredCI
The subscriber's preferred carrier ID is sent in the ETSI-specified
naea-PreferredCI parameter. For backward compatibility, this
information is also sent in the proprietary parameter ansiIsdArgExt.
.
naea-PreferredCIC
This parameter is from subscriber data in HLR database.
gprsSubscriptionData
See GprsSubscriptionData.
roamingRestrictedInSgsnDueToUnsupported Feature
networkAccessMode
This parameter is from subscriber data in HLR database. This
parameter is sent in the first invocation in a segmented dialogue.
lsaInformation
lmu-Indicator
lcsInformation
See LcsInformation.
istAlertTimer
superChargerSupportedInHLR
Contains the Age Indicator of the subscriber data. The length of this
parameter is always 6 octets.
60 (264)
DN98628099
Issue 10-1 en
When the subscriber data is updated in the HLR, also Age Indicator
is updated and sent to the serving network entity with changed data,
in case Super Charger is supported in the serving network and
Super Charger functionality is allowed to be used in the HLR
towards the network entity in question.
.
mc-SS-Info
cs-AllocationRetentionPriority
From the subscriber data in the HLR database. Possible values are
'01'O, '02'O and '03'O.
It is sent only when the subscriber is roaming in HPLMN.
sgsn-CAMEL-SubscriptionInfo
See sgsn-CAMEL-SubscriptionInfo.
chargingCharacteristics
accessRestrictionData
From the subscriber data in the HLR database.
isdArgExt (proprietary)
See IsdArgExt.
ansiIsdArgExt (proprietary)
See AnsiIsdArgExt.
SubscriberData
.
msisdn
This is subscriber's primary service MSISDN from the HLR
database.
Optionally the subscriber's common MSISDN from HLR database
may be sent in this parameter and the own MSISDN is included in
the IsdArgExt if the sending of the common MSISDN is allowed in
the PLMN-specific definitions. Optional feature is Feature 1541:
Same CLI for Multiple Subscribers.
category
From subscriber data in HLR database.
DN98628099
Issue 10-1 en
61 (264)
Non-standard category values are available as optional features.

The category values Private Numbering Service, Ordinary No
Charge, Priority No Charge and Telemetric subscribers are
converted to Ordinary when sent towards a visited PLMN. The
extended category values are converted to ordinary, if they are not
supported by the VPLMN (according to the HLR configuration).
.
subscriberStatus
odb-GeneralData is also present, if subscriberStatus is
operatorDeterminedBarring.
It is also used in a stand alone InsertSubscriberData, when the
status of ODB is changed.
bearerServiceList
At least one bearer service code or teleservice code is sent (group
codes are not used) during location updating procedure.
teleserviceList
At least one bearer service code or teleservice code is sent (group
codes are not used) during location updating procedure.
provisionedSS
See ProvisionedSS.
odb-Data
roamingRestrictionDueToUnsupportedFeature
regionalSubscriptionData
vbsSubscriptionData
vgscSubscriptionData
62 (264)
vlrCamelSubscriptionInfo
DN98628099
Issue 10-1 en
See VlrCamelSubscriptionInfo.
ProvisionedSS
ForwardingInfo
.
ss-Code
Either CFBusy, CFNoReply, CFNotReachable or CallDeflection.
forwardingFeatureList
ForwardingFeature information is sent separately for each basic
service.
.
basicService
In case of CallDeflection, the basicService parameter is not
sent (CallDeflection is automatically applicable to all basic
services).
.
ss-Status
.
forwardedToNumber
The forwardedToNumber is sent for CFBusy, CFNoReply and
CFNotReachable. The maximum length of the
forwardedToNumber is 16 digits (which can be restricted to 15
digits as an optional feature ).
.
.
forwardingOptions
.
If the value for the noReplyConditionTime is not individually set
for the subscriber, the default value is fetched from the HLR
data (the default value is configurable).
As an optional feature, for Operator Controlled Call Forwarding
the maximum value of the timer is 100 seconds.
.
longForwardedToNumber
CallBarringInfo
From subscriber data in the HLR database.
CUG-Info
DN98628099
Issue 10-1 en
63 (264)
SS-Data
It is used for other standard supplementary services than Call Forwarding,
Call Barring, Closed User Group (CUG) or eMLPP. Also used for
proprietary supplementary services.
.
ss-Code
It indicates the provided service.
The ss-code values for proprietary services are listed in Formal
definion of data types, supplementary service codes. Those services
are:
.
Call Transfer Recall (ss-code 'callTransferRecall')
.
Mobile IN Categories (ss-code 'emoIn-mo-ick')
Sent only if the dialogue version is 2 or 3.
With this ss-code the proprietary parameter
emoInCategoryKey in sS-DataEmoInExt is also present.
.
Core INAP (ss-code 'inService')
With this ss-code the proprietary parameter inTriggerKey in
sS-DataExtension is also present.
.
Charging Based on Home Area (ss-code 'homeArea')
With this ss-code the proprietary parameter
regionalChargingData in sS-DataExtension is also present.
.
Hot Billing (ss-code 'hotBilling')
.
Mobile Centrex (ss-code 'pnpService')
If the ss-Status parameter indicates that the service is
provisioned, the proprietary parameter pnpIndex in sSDataExtension is also present.
.
Automatic Call Redirection (ss-code 'rdiService')
If the ss-Status parameter indicates that the service is
provisioned, the proprietary parameter callRedirectionIndex in
sS-DataExtension is also present.
.
USSD Barring based on PLMN specific SS code (ss-code
'ussdBarred')
64 (264)
ss-Status
ss-SubscriptionOption
basicServiceGroupList
DN98628099
Issue 10-1 en
sS-DataExtension (proprietary)
It contains data related to a proprietary supplementary service:
.
inTriggerKey
The related SS code is 'inService' and the related SS status is
'provisioned & active'.
It is sent to both the VLR and the SGSN.
.
pnpIndex
The related SS code is 'pnpIndex'.
.
callRedirectionIndex
The related SS code is 'rdiService'.
.
regionalChargingData
The related SS code is 'homeArea'.
sS-DataEmoInExt (proprietary)
Tag [PRIVATE 1] is used in versions 2 and 3 (the extensionContainer
is not used for this service).
.
emoInCategoryKey
The related SS code is 'emoIn-mo-ick'.
As an optional feature in multivendor environments, the EMO-IN
OICK may be sent in the extensionContainer in the main level of
InsertSubscriberDataArg.
extensionContainer
It may contain the sS-DataExtension in version 3. The extension
EMLPP-Info
EMLPP-Info contains the eMLPP Maximum Entitled Priority level and the
eMLPP Default Priority level. The value range for both parameters is: A, B,
0, 1, 2, 3 or 4.
CosInfo
As an optional feature, the information in the cosInfo is mapped from the
Routing Category and Additional Routing Category in the subscriber data
in the HLR database. This data is sent during location update only.
.
ss-Code
This parameter is sent with value 251 ('FB' hexadecimal).
DN98628099
Issue 10-1 en
65 (264)
cos-FeatureList
One cosFeature per each subscribed basic service group is sent.
.
basicServiceCode
This parameter contains a basic service group code, derived
from the list of subscriber's teleservices and bearer services.
.
ss-Status
This parameter is sent with value '07' (provisioned + registered
+ active).
.
customerGroupID
Bit 0 (the formatIndicator) is sent with value network format.
Bits 16..31 contain the Additional Routing Category value,
within value range 1..65534. Other bits are set to zero.
.
subGroupID
.
classOfServiceID
Bit 0 (the formatIndicator) is sent with value network format.
Bits 8..15 contain the Routing Category value, within value
range 1..254. Other bits are set to zero.
VlrCamelSubscriptionInfo
It is sent if the VLR has indicated that it supports CAMEL and if the HLR
configuration shows that the CAMEL functionality towards the VPLMN is
allowed (or as an optional feature, if the subscriber data contains an
indicator that the VPLMN definition can be ignored).
CAMEL phase 4 CSIs O-CSI, D-CSI, VT-CSI and MT-SMS-CSI are sent
only if the VLR has indicated that it supports these phase 4 CSIs. If the
phase 4 CSIs are not supported by the VLR, the HLR checks from its
configuration if those CSIs can be sent with lower CAMEL phase.
As an optional feature, the Camel Capability Handling information in a CSI
is not sent at all, when CAMEL phase 1 information is sent in the CSI.
As an optional feature, it is possible to configure per subscriber different
Default Call/SMS/Session Handling (the defaultCallHandling paremeter)
based on the VPLMN, for each CSI separately.
.
o-CSI
66 (264)
DN98628099
Issue 10-1 en
The O-CSI is not sent to the VLR, if the HLR Triggering Criteria in the
O-CSI restricts the usage of CAMEL by disabling the sending of the
O-CSI. The restriction is based on the VLR address.
In CAMEL phase1 only one o-BcsmCamelTDPData is supported.
.
ss-CSI
The ss-EventList may contain ect, multiPTY and cd.
o-BcsmCamelTDP-CriteriaList
The addresses in destinationNumberList may contain overdecadic
hexadecimal values.
tif-CSI
From the subscriber data in the HLR database. Sent if at least
CAMEL phase 2 is supported by the VLR.
m-CSI
mo-sms-CSI
vt-CSI
t-BCSM-CAMEL-TDP-CriteriaList
d-CSI
mt-sms-CSI
.
sms-CAMEL-TDP-DataList
The sms-TriggerDetectionPoint has value smsDeliveryRequest.
The serviceKey identifies to the gsmSCF the service logic that
has to be applied. Possible values are from 1 to 2147483647.
DN98628099
Issue 10-1 en
67 (264)
The gsmSCF-Address is the address (E.164 number,

maximum length is 15 digits) of the gsmSCF, where the MT
SMS CAMEL Service associated with this TDP, is located for
this subscriber.
The defaultSMS-Handling indicates whether the MT SMS
submission request has to be rejected or continued in the case
of error in the dialogue between the gsmSSF (or the gprsSSF)
and gsmSCF.
camelCapabilityHandling
This parameter indicates the phase of CAMEL which is asked
by the gsmSCF for the service. This parameter is set to
'CAMEL Phase 4'.
mt-smsCAMELTDP-CriteriaList
.
sms-TriggerDetectionPoint
The sms-TriggerDetectionPoint has value smsDeliveryRequest.
.
tpdu-TypeCriterion
This parameter indicates on which TPDUs the gsmSSF has to
access the gsmSCF. Possible values are sms-DELIVER and
sms-STATUS-REPORT.
GprsSubscriptionData
.
completeDataListIncluded
CompleteDataListIncluded is set if all the subscriberGprsData is to
be replaced by the new data included in the list. (SGSN does not
have to make any comparison with the existing data.)
gprsDataList
Maximum 50 PDP-Contexts per subscriber are supported.
.
pdp-ContextId
.
pdp-Type
.
pdp-Address
.
qos-Subscribed
This parameter contains the Release97/Release98 Quality Of
Service information from the subscriber's QoS profile.
.
vplmnAddressAllowed
.
apn
.
ext-QoS-Subscribed
68 (264)
DN98628099
Issue 10-1 en
.
.
This parameter contains the Release99 Quality Of Service

information from the subscriber's QoS profile. It indicates the
enhanced QoS subscribed, and is an extension to the qosSubscribed.
The first octet contains the Allocation/Retention priority
information. The remaining octets contain the Quality of
Service information.
As an optional feature, when the subscriber is roaming outside
the home country an operator configured default value for the
Allocation/Retention priority is sent.
pdp-ChargingCharacteristics
ext2-QoS-Subscribed
This parameter contains the Release5 Quality Of Service
information from the subscriber's QoS profile. It indicates the
additional QoS information to the ext-QoS-Subscribed
parameter, and is a further extension to the ext-QoSSubscribed. This parameter shall be used when the maximum
bit rate exceeds 8640 kbps.
The first octet contains the Source Statistics Descriptor from
the subscriber's QoS profile. The second and third octets are
optionally present, and contain the maximum bit rate for
downlink and quaranteed bit rate for downlink information from
the subscriber's QoS profile.
LcsInformation
.
gmlc-List
Gmlc-List contains the addresses of the GMLCs that are permitted to
issue a non-call-related MT-location request for the subscriber.
lcs-PrivacyExceptionList
LCS-PrivacyClass:
.
ss-Code
The class of Location Application which is allowed to locate
the subscriber. It can be either universal, callrelated,
callunrelated, plmnoperator, basicSelfLocation,
autonomousSelfLocation or transferToThirdParty.
.
ss-Status
.
notificationToMSUser
DN98628099
Issue 10-1 en
69 (264)
This parameter may be included for callRelated and

callUnrelated classes.
externalClientList
This parameter is sent for Call Related class only if the VLR /
SGSN has indicated (during location update) the support of at
least Release 4 LCS capability. The maximum number of
external LCS clients in the HLR is 40 (the first five are sent in
the externalClientList parameter, the remaining are sent in the
ext-externalClientList parameter).
.
clientIdentity
ExternalAddress in clientIdentity identifies the allowed
LCS client.
.
gmlc-Restriction
This parameter indicates the LCS client serving
restrictions for the subscriber.
.
This parameter specifies if privacy verification or
notification is performed for the LCS client.
NotificationToMSUser is applicable to callRelated and
callUnrelated classes.
plmnClientList
LCSClientInternalID: Indicates the identity of an internal PLMN
operator client that is allowed to locate the subscriber.
ext-externalClientList
The maximum number of external LCS clients in the HLR is 40
(the first five are sent in the externalClientList parameter, the
remaining are sent in the ext-externalClientList parameter).
Sent if the VLR (or SGSN) has indicated the support of at least
LCS capability set 2 (Release 4).
serviceTypeList
A maximum of 32 service types, sent if the VLR (or SGSN) has
indicated the support of at least LCS capability set 3 (Release
5). Each Service Type includes the information whether the
location is allowed or not, and if the location is allowed with
notification or verification.
molr-List
70 (264)
DN98628099
Issue 10-1 en
Sgsn-CAMEL-SubscriptionInfo
It is sent if the SGSN has indicated that it supports CAMEL and if the HLR
configuration shows that the CAMEL functionality towards the VPLMN is
allowed (or as an optional feature, if the subscriber data contains an
indicator that the VPLMN definition can be ignored).
As an optional feature, it is possible to configure per subscriber different
Default Call/SMS/Session Handling (the defaultCallHandling paremeter)
based on the VPLMN, for each CSI separately.
.
gprs-CSI
.
gprs-CamelTDPDataList
.
.
notificationToCSE
.
csi-Active
mo-sms-CSI
mt-sms-CSI
This CSI is sent with phase 4 only if the SGSN has indicated that it
supports phase 4 MT-SMS-CSI. If the phase 4 CSI is not supported
by the SGSN, the HLR checks from its configuration if this CSI can
be sent with lower CAMEL phase.
mg-CSI
This parameter is from the subscriber data in the HLR database. It is
sent if the SGSN supports CAMEL phase 4, and if the SGSN has
also indicated the support of the MG-CSI.
.
mobilityTriggers
This parameter indicates which events have to result in a
notification towards the gsmSCF. Possible values are
Routeing-Area-update-in-same-SGSN, Routeing-Areaupdate-to-other-SGSN-update-from-new-SGSN, RouteingArea-update-to-other-SGSN-disconnect-by-detach, GPRSAttach, MS-initiated-GPRS-Detach, Network-initiated-GPRSDetach, and Network-initiated-transfer-to-MS-not-reachablefor-paging.
.
serviceKey
DN98628099
Issue 10-1 en
71 (264)
.
.
This parameter identifies the service logic in the gsmSCF.

gsmSCF-Address
notificationToCSE
This parameter is not sent to the SGSN.
csi-Active
This parameter is not sent to the SGSN.
IsdArgExt
It is proprietary.
In version 3 the IsdArgExt is sent inside the extensionContainer.
.
alsLineIndicator
routingCategory
This parameter is the routing category from subscriber data in the
HLR database.
serviceList
serv-info-list
.
serviceCode
mKey = '03'O, smsKey = '04'O, fraudData = '05'O, cellUpdate
= '06'O.
.
versionInfo
Value '01'O is always used.
.
in-Key
Mobile-IN-key / MmTdpName: It indicates whether Detection
Point is set for Inter-VLR location update (bit 1) and/or IntraVLR location update (bit 2).
Mobile-IN-key / LocupType: IMSI attach (bit 1), periodic
location update (bit 2), normal location update (bit 3).
Sms-IN-key / smsTdpName: MT-SMS DP (bit 1), MO-SMS DP
(bit 2), SR-SMS-DP (bit 3).
.
fraudInfo
Fraud control data for moc (mobile-originated call), cf (call
forwarding) or ct (call transfer).
72 (264)
DN98628099
Issue 10-1 en
Time parameter indicates the time limit in minutes. Value 0 =

use VLR default, 'FFFF'H = no restriction.
TimeAction: report (bit 1) and/or reject (bit 2) is set. Value 'FF'O
= use VLR default.
maxCount: Value 0 = use VLR default, 255 = no restriction.
maxCountAction: report (bit 1) and/or reject (bit 2) is set. Value
'FF'O = use VLR default.
.
extRoutingCategory
This parameter is the extended routing category from subscriber
ownMSISDN
This parameter is the subscriber's own MSISDN from the HLR
database and sent if the common MSISDN is included in the msisdn
parameter in SubscriberData. Optional feature is Feature: 1541,
Same CLI for Multiple Subscribers.
AnsiIsdArgExt
Proprietary.
This extension is sent with the tag [PRIVATE 30] in version 2 and 3 (the
extension container is not used in version 3).
.
prefCarrierIdList
This parameter is from subscriber data in the HLR database. It
contains the preferred Carrier Id.
This information is sent also in the standardised naea-PreferredCI
parameter.
Result parameters
.
teleserviceList
HLR application may replace not supported services depending on
the HLR configuration.
bearerServiceList
HLR configuration.
DN98628099
Issue 10-1 en
ss-List
73 (264)

HLR configuration.
.
If CUG is received, activated BAOC is sent to all basic service
groups which do not have outgoing access.
.
If another SS-code is received in location updating procedure,
location registration can be denied to certain VLRs depending
on whether the service is a 'roaming not allowed' service
(parameterised).
.
odb-GeneralData
If the VLR or SGSN returns ODB, depending on the HLR
configuration, the HLR performs one of the following actions:
.
It continues normally.
.
It sends a new InsertSubscriberData, including BAOC, to all
basic services
.
It returns an error to UpdateLocation operation:
RoamingNotAllowed with cause operatorDeterminedBarring.
regionalSubscriptionResponse
.
networkNode-AreaRestricted
'MSC area restricted' flag in subscriber data is set to
'restricted'.
.
tooManyZoneCodes
An alarm is set in the HLR.
.
zoneCodesConflict
.
regionalSubscNotSupported
This parameter is stored in the HLR data on a VLR address basis
during location updating or stand-alone InsertSubscriberData (not
stored during data restoration procedure). The supported CAMEL
phases informed by the VLR in InsertSubscriberData result are not
checked if the MSC/VLR has informed the supported CAMEL
phases in UpdateLocation argument.
extensionContainer
Ignored.
offeredCamel4CSIs
Indicates the CAMEL 4 CSIs offered in the VMSC/VLR or in the
SGSN.
74 (264)
DN98628099
Issue 10-1 en
The VMSC/VLR may indicate the support of o-csi, d-csi, vt-csi and
mt-sms-csi.
The SGSN may indicate the support of mg-csi, mt-sms-csi and psienhancements.
Error causes
.
DataMissing
UnexpectedDataValue
If an error cause is received during location update procedure, the error

cause SystemFailure for UpdateLocation operation is returned to the VLR
(or SGSN).
3.2.2.14
DeleteSubscriberData
This operation is implemented in version 1, version 2, and version 3
dialogues.
.
Re-attempts in case procedure fails: 0..3 times in a 0..10 seconds

interval (depending on HLR configuration)
SCCP address: SPC or GT, VLR or SGSN address from subscriber

data
.
imsi
basicServiceList
This parameter may contain one basic service code, which is
withdrawn from the subscriber data. Only individual basic service
codes are used (not group codes).
DN98628099
Issue 10-1 en
75 (264)
ss-List
This parameter may contain one supplementary service code, which
is withdrawn from the subscriber data.
This parameter is not used.
regionalSubscriptionIdentifier
This parameter is sent with a dummy value when the Zone Codes
are removed from the subscriber.
vbsGroupIndication
vgcsGroupIndication
camelSubscriptionInfoWithdraw
This parameter is sent when a CAMEL service for the subscriber is
deleted or deactivated (if CAMEL functionality towards the visited
PLMN is allowed).
extensionContainer
.
This parameter may contain the dsdArgExt in version 3. The
.
May contain an indication of the deletion of the EMO-IN OICK
service, or the SubscriptionType service; the ExtensionType is
DsdArgType. The extension identifier is {iso(1) member-body
(2) bsi(826) disc(0) ericsson(1249)
gsmNetworkApplicationsDefinition(58) gsm-Map(1) gsm-MapExt(0)}. (Optional feature.)
The dsdArgData in dsdArgType contains the
privateFeatureCode '00000110'B (OICK) or '00000010'B
(SubscriptionType).
gprsSubscriptionDataWithdraw
roamingRestrictedInSgsnDueToUnsupportedFeature
lsaInformationWithdraw
76 (264)
hplmn-GMLC-List-Withdraw
istInformationWithdraw
DN98628099
Issue 10-1 en

.
specificCSI-Withdraw
This parameter indicates the withdrawn CSI.
dsdArgExt (proprietary)
This parameter is used in version 2, while in version 3 it is sent inside
the extensionContainer.
.
alsLineIndicator
This parameter indicates that the removed service applies to
the ALS.
.
serviceList
This parameter indicates that a proprietary service is removed.
'01'O = picLock, '02'O = prefCarrierId, '03'O = mKey, '04'O =
smsKey, '05'O = fraudData, '06'O = cellUpdateInformation .
Result parameters
.
regionalSubscriptionResponse
Error causes
3.2.2.15
DataMissing
UnexpectedDataValue
Reset
This operation is implemented in version 1 and version 2 dialogues. Note
that for this operation version 1 is always used, unless explicitly specified
otherwise with the MAP parameter management (see Version control).
It is invoked by the HLR and handled by the VLR or SGSN.
DN98628099
Issue 10-1 en
Operation timer: 1 second
SCCP address: SPC or GT, VLR address or SGSN address in the

subscriber data
77 (264)
.
networkResource
This parameter is sent in version 1 dialogues with value 'HLR (1)'.
hlr-Number
It contains the HLR address from the HLR configuration data, in
cases when the Reset is sent automatically because of an HLR
restart. If the Reset is sent manually, the hlr-Number contains the
address which is given by MMI.
hlr-List
3.2.2.16
ForwardCheckSSIndication
This operation is implemented in version 1, 2, and 3 dialogues
It is invoked by the HLR and handled by the VLR.
ForwardCheckSSIndication is sent in the same TC-End primitive with
UpdateLocation result.
.
SCCP address: calling party address in UpdateLocation result
The invocation contains no parameters.
3.2.2.17
RestoreData
SendParameters operation is used in version 1 dialogues.
.
imsi
This parameter is a key to subscriber data in the HLR database. If
the IMSI is unknown, the error UnknownSubscriber is returned.
78 (264)
DN98628099
Issue 10-1 en

.
lmsi
vlr-Capability
.
If supportedCamelPhases parameter is not received, phase 1
is assumed. Supported values: phase1, phase2, phase3, and
phase4.
.
.
istSupportIndicator
.
The presence of this parameter indicates that the VLR
If received, the Age Indicator can be sent to the VLR in the
InsertSubscriberData message.
.
longFTN-Supported
.
SupportedLCS-CapabilitySets indicates what type of LCS data
the HLR can send in the InsertSubscriberData operation.
When this parameter is present, it may indicate that the VLR
supports LCS capability set 1, or set 2, or set 3, or a
combination of those, or none of those. If this parameter is not
received, the HLR assumes that the VLR supports LCS
capability set 1.
.
offeredCamel4CSIs
Indicates the CAMEL 4 CSIs offered in the VMSC/VLR. May
contain o-csi, d-csi, vt-csi and mt-sms-csi.
hlrNumber
Result parameters

IMSI.
DN98628099
Issue 10-1 en
79 (264)
msNotReachable
This parameter is sent if the subscriber's Message Waiting List
contains Service Centre addresses.
Error causes
.
SystemFailure
It is sent if the InsertSubscriberData fails between HLR and VLR.
DataMissing
It is never sent.
UnexpectedDataValue
UnknownSubscriber
It is sent if the IMSI is unknown, or if the subscriber status in the HLR
is deactivated.
3.2.2.18
SendRoutingInfoForGprs
This operation is not implemented.
3.2.2.19
FailureReport
3.2.2.20
NoteMsPresentForGprs
3.2.2.21
SendParameters
This operation is implemented in version 1 dialogues only. In version 2 or
higher, RestoreData or SendAuthenticationInfo operation is used.
80 (264)
DN98628099
Issue 10-1 en
.
subscriberId
.
imsi
This parameter is a key to subscriber data either in the HLR
database (a request for subscriber data), or in the AuC
database (a request for the authentication info). In error cases
an UnknownSubscriber error is sent (if the IMSI is not known in
the HLR, or is the IMSI of a sequential/parallel/intelligent
alerting group).
As an optional feature, the IMSI may be either the Database
IMSI or an Alias IMSI (according to the HLR configuration).
.
tmsi
It is not relevant to the HLR. If received, an
UnexpectedDataValue error is sent.
requestParameterList
Two request types are accepted but only the first one in the list is
handled.
.
requestIMSI
If received, an empty result is sent.
.
requestAuthenticationSet
Indicates that the request is for authentication information.
.
requestSubscriberData
It indicates that the request is for subscriber data.
.
requestKi
If received, an empty result is sent.
Result parameters
The result is not segmented, that is, TC-Result-NotLast primitive is not
used.
.
imsi
authenticationSet
1..5 (by default 4) authentication sets are returned by the AuC.
DN98628099
Issue 10-1 en
subscriberData
.
msisdn
This parameter is subscriber's primary service MSISDN from
the HLR database.
81 (264)
category
From subscriber data in HLR database.
Non-standard category values are available as optional
features. The category values Private Numbering Service,
Ordinary No Charge, Priority No Charge and Telemetric
subscribers are converted to Ordinary when sent towards a
visited PLMN. The extended category values are converted to
ordinary, if they are not supported by the VPLMN (according to
the HLR configuration).
subscriberStatus
bearerServiceList
teleserviceList
provisionedSS
Only the information for CF Busy or CF Not Reachable is sent.
The forwardingFeatureList for each call forwarding type may
contain the forwardingFeature for a maximum of 5 different
basic services.
For details, see ProvisionedSS in InsertSubscriberData.
odb-Data
ki
Error causes
.
UnknownSubscriber
It is sent if the IMSI in the invocation is unknown, or if it is the IMSI of
a sequential/parallel/intelligent alerting group.
It is never sent.
82 (264)
DN98628099
Issue 10-1 en
UnexpectedDataValue
3.2.3
Operation and Maintenance operations
3.2.3.1
ActivateTraceMode
.
Re-attempts in case procedure fails: HLR-initiated independent

operation repeated 0..3 times in a 0..10 seconds interval (depending
on HLR configuration)
It is not used in location update procedure-initiated
ActivateTraceMode.
SCCP address: GT or SPC, VLR address in the subscriber data
.
imsi
traceReference
traceType
The following values are used in MAP version 1:
.
0 = allEvents
.
1 = onlyCalls
.
128 = OLCM record
.
129 = OLCM record and report
In higher MAP versions the bits 'kszzxxyy' in the trace type
parameter have the following definitions:
DN98628099
Issue 10-1 en
83 (264)
.
.
s = spare bit, always set to 0

yy = 00, 01 or 10
.
k, priority bit. 1 = priority record, 0 = non-priority record
.
zz, BSS trace record type: 00 = basic record type, 01 =
handover record type, 10 = radio record type, 11 = no
BSS trace
.
xx, MSC trace record type. 00 = basic record type, 11 =
no MSC trace
.
yy = 00: tracing for all events
.
yy = 01: tracing for call, short message and SS events
.
yy = 10: tracing for location updates, IMSI attach/detach
events
yy = 11: On-line Call Monitoring (Feature 703: On-line Call
Monitoring)
.
kszzxxyy = 00000011: OLCM record
.
kszzxxyy = 00000111: OLCM record and report
.
kszzxxyy = 00001011: OLCM report
omc-Id
atmExtension (proprietary)
This parameter is used in version 2, while in version 3 this parameter
is inside the extensionContainer.
.
traceReference
This parameter contains the Trace Reference for an OLCM
trace, and is used only if the subscriber also has a normal
GSM trace active. (If the subscriber does not have a normal
GSM trace active, this information is sent in the standard
traceReference parameter in the ActivateTraceMode
argument.)
.
traceType
This parameter contains the Trace Type for an OLCM trace,
and is used only if the subscriber also has a normal GSM trace
active. (If the subscriber does not have a normal GSM trace
active, this information is sent in the standard traceType
parameter in the ActivateTraceMode argument.)
.
leaId
This parameter indicates the Law Enforcement Agency for the
first OLCM trace set.
.
olcmInfoTable
This parameter contains the traceReference, traceType, and
leaId for 6 additional OLCM trace sets.
84 (264)
DN98628099
Issue 10-1 en
extensionContainer
This parameter contains the atmExtension in version 3. The
Result parameters
In version 1 and version 2 the result contains no parameters.
In version 3 the extensionContainer may contain:
.
atmResExtension
In version 3 the extension identifier is {0 34 16}.
.
olcmActive
This parameter indicates that the OLCM activation in the VLR
was successful. If not received, and if more than 1 OLCM was
sent in the ActivateTraceMode argument, the HLR assumes
that the OLCM activation was not successful in the VLR.
Error causes
.
SystemFailure
DataMissing
UnexpectedDataValue
FacilityNotSupported
TracingBufferFull
If an error cause is received during a location update dialogue, the location

update procedure is continued normally.
3.2.3.2
DeactivateTraceMode
DN98628099
Issue 10-1 en
85 (264)
Re-ttempts in case procedure fails: 0..3 times in a 0..10 seconds

interval (depending on HLR configuration)
SCCP address: GT or SPC, VLR address in the subscriber data
.
imsi
traceReference
dtmExtension (proprietary)
This parameter is used in version 2,while in version 3 the
dtmExtension parameter is inside the extensionContainer.
.
traceType
This parameter indicates the type of the deactivated trace.
.
leaId
This parameter indicates the Law Enforcement Agency of the
deactivated trace.
extensionContainer
This parameter contains the dtmExtension in version 3. The
Result parameters
In version 1, 2, and 3 the result contains no parameters.
In version 3, any possible parameters in the result are ignored by the HLR.
Error causes
86 (264)
SystemFailure
DataMissing
DN98628099
Issue 10-1 en
3.2.3.3
UnexpectedDataValue
SendIMSI
Operation in the responding HLR

In a Mobile Number Portability environment (Feature 1080: SRF in HLR),
the SCCP Called Party Address Translation Type and Numbering Plan
may have special values (depending on configuration). Depending on the
SRF check for the subscriber, the SendIMSI may be forwarded towards
another HLR (SCCP level re-routing).
.
msisdn
This parameter is a key to subscriber (or sequential/parallel/
intelligent alerting group) data in the HLR database. In error cases
an UnknownSubscriber error is sent.
As an optional feature (Feature 1048: Extended Handling for
Subscriber Identity (MSISDN) in the HLR), the received MSISDN
may be modified before the HLR database enquiry.
Result parameters
.
imsi
If the SendIMSI request was received for the common MSISDN of a
ringing group, then the common IMSI is returned in the response.
DN98628099
Issue 10-1 en
87 (264)
Error causes
.
DataMissing
It is never sent.
UnexpectedDataValue
UnknownSubscriber
It is sent if the MSISDN is unknown in the HLR.
Operation in the initiating HLR

It is invoked by the VLR and confirmed by the HLR. As an optional feature
(Feature 626: GSM Supplementary Services Phase 2 Extensions), the
HLR initiates this operation, using the VLR's subsystem number in the
SCCP level Calling Party Address.
.
SCCP address: GT (E.164), derived from the operation argument's

msisdn parameter
.
msisdn
This parameter is from HLR application, the SMS CFU C-number.
Result parameters
.
imsi
The MCC and MNC from IMSI are checked to see if this is a HPLMN
subscriber.
Error causes
88 (264)
DN98628099
Issue 10-1 en
DataMissing
UnexpectedDataValue
UnknownSubscriber
3.2.4
Call handling operations
3.2.4.1
SendRoutingInfo
It is invoked by the MSC and confirmed by the HLR.
In a Mobile Number Portability environment (Feature 1080: SRF in HLR),
may have special values (depending on configuration). Depending on SRF
check for the subscriber, the SendRoutingInfo may be forwarded towards
another HLR (SCCP level re-routing).
.
msisdn
This parameter is a key to subscriber data, or to ringing group data
(optional features - Features 1545 and 1576: Sequential and Parallel
Alerting), in HLR database. In error cases an UnknownSubscriber
error is sent.
cug-CheckInfo
.
cug-Interlock
This parameter is a key to the subscriber A's CUG-information.
.
cug-OutgoingAccess
This parameter indicates that the subscriber A is allowed to
originate non-CUG calls.
numberOfForwarding
This parameter is checked against the maximum number of allowed
call forwardings (as configured in the HLR). In error cases a
ForwardingViolation error is sent.
DN98628099
Issue 10-1 en
interrogationType
89 (264)
It indicates the type of interrogation: basic or forwarding. This

information is used for the checking of the parameters
callReferenceNumber, forwardingReason and basicServiceGroup.
.
or-Interrogation
It indicates that the interrogation is from a GMSC which is not in the
same PLMN as the HLR.
If the Optimal Routing is not allowed from the GMSC, the error ORNotAllowed is sent. The SCCP level Calling Party Address is
checked against the HLR configuration, to see if Optimal Routing is
allowed from the GMSC. Additionally, optimal routing is allowed only
if the GMSC is from another PLMN, and if the GMSC and the VMSC,
where the called subscriber is roaming, are in the same country, and
if the Basic Optimal Routing service is provisioned for the called
subscriber.
The optimal routing may be rejected by the HLR as a result of the
Closed User Group checking, CAMEL checking, OLCM checking, or
if a Call Forwarding is invoked and the forwarded-to-number is not in
international format. In these cases the error OR-NotAllowed is sent.
or-Capability
It indicates the phase of Optimum Routing which the GMSC
supports. If this parameter is not received, the
orNotSupportedInGMSC parameter is included in the
ProvideRoamingNumber invocation.
gmsc-Address
This parameter is forwarded to the VLR in ProvideRoamingNumber
operation.
callReferenceNumber
This parameter is forwarded to the VLR in ProvideRoamingNumber
operation.
It has to be present if the interrogationType is basic, otherwise has to
be absent. If the interrogationType is forwarding and the
callReferenceNumber is present, the error UnexpectedDataValue is
sent to the GMSC. If the interrogationType is basic and the
callReferenceNumber is absent, the error DataMissing is sent to the
GMSC.
90 (264)
forwardingReason
DN98628099
Issue 10-1 en
It has to be present if the interrogationType is forwarding, otherwise

has to be absent. If the interrogationType is basic and the
forwardingReason is present, the error UnexpectedDataValue is
sent to the GMSC. If the interrogationType is forwarding and the
forwardingReason is absent, the error DataMissing is sent to the
GMSC.
.
basicServiceGroup
It has to be present if the interrogationType is forwarding, otherwise
has to be absent. If the interrogationType is basic and the
basicServiceGroup is present, the error UnexpectedDataValue is
sent to the GMSC. If the interrogationType is forwarding and the
basicServiceGroup is absent, the error DataMissing is sent to the
GMSC.
networkSignalInfo
The ISDN BC information received from the GMSC is translated into
the basic service that is used for the call. If the basic service is not
provisioned for the susbcriber, the error
BearerServiceNotProvisioned is returned.
The ISDN BC information is used in the HLR to construct the GSM
BC, which is sent towards the VLR in ProvideRoamingNumber.
camelInfo
.
.
suppress-T-CSI
If received, the HLR does not send the T-CSI in the
SendRoutingInfo result.
.
offeredCamel4CSIs
It indicates the CAMEL 4 CSIs offered in the GMSC. May
contain o-csi, d-csi and t-csi.
This parameter is used to check if the subscription information
of those CSIs can be included in the SendRoutingInfo-result.
It is forwarded to the VLR in the ProvideRoamingNumber
operation.
suppressionOfAnnouncement
This parameter is forwarded to the VLR in the
ProvideRoamingNumber operation.
DN98628099
Issue 10-1 en
extensionContainer
91 (264)
Contains the sriExtension in version 3. The extension identifier

is {0 34 5}.
Contains the extraSignalInfo in version 3. The extension
Contains the EMO-IN OICK and TICK extensions,
ExtensionType is SriArgType. The extension identifier is {iso
(1) member-body(2) bsi(826) disc(0) ericsson(1249)
gsmNetworkApplicationsDefinition(58) gsm-Map(1) gsm-MapExt(0)}. (Optional feature.)
The privateFeatureCode '00000110'B (OICK) indicates that
the multivendor MAP version 3 OICK parameter is requested
from the HLR.
The privateFeatureCode '00000111'B (TICK) indicates that the
multivendor MAP version 3 TICK parameter is requested from
the HLR.
alertingPattern
ccbs-Call
supportedCCBS-Phase
All received values are interpreted as phase 1.
additionalSignalInfo
This parameter may contain Calling Line Identity and Generic
Number.
The supported formats of the numbers are E.164 international,
national or unknown. If a number in a not supported format is
received, the SendRoutingInfo is rejected.
The parameter is forwarded to the VLR in ProvideRoamingNumber
invocation if the subscriber has CLI-E provisioned, and if the PLMNspecific parameters allow sending of CLI and Generic Number to the
VLR.
As an optional feature, if subscriber B has an active T-CSI and is
roaming in the HPLMN, subscriber A's Calling Line Identity is
analysed to see if the T-CSI has to be suppressed from the
92 (264)
istSupportIndicator
pre-pagingSupported
callDiversionTreatmentIndicator
DN98628099
Issue 10-1 en
If 'callDiversionNotAllowed' is received, HLR-controlled call

forwarding is not done.
.
longFTN-Supported
suppress-VT-CSI
This parameter is forwarded to the VLR in ProvideRoamingNumber,
if also the gsmSCF-InitiatedCall parameter is received in the
SendRoutingInfo invocation.
suppressIncomingCallBarring
The barrings are not checked by the HLR (this concerns both
Operator Determined Barrings and subscriber controlled barrings), if
also the gsmSCF-InitiatedCall parameter is received in the
gsmSCF-InitiatedCall
This parameter indicates that the HLR enquiry is initiated by a
gsmSCF.
sriExtension (proprietary)
This parameter is used in version 2. In version 3, the sriExtension
parameter is inside the extensionContainer.
.
callForwardingOverride
If present, call forwarding is not done.
.
in-Capability
If present, and if the subscriber has services triggered from the
Gateway-TBCSM, the HLR returns the inTriggerKey,
vlrNumber and activeSs from subscriber data in the HLR
database, and the CUG information, and the same MSISDN
that was received in SendRoutingInfo invocation.
.
callingCategory
Value 'E9'hex indicates that no special handling for the CLIInquiry Service is to be made, but the HLR enquiry has to be
handled normally in the HLR: a roaming number is requested
from the VLR and returned to the GMSC.
.
internalServiceIndicator
If the indicator for the support of sequential/parallel/intelligent
alerting is received, the MSISDN is checked to see if the call is
targeted to a ringing group (Features 1545 and 1576:
Sequential and Parallel Alerting).
If the indicator for member interrogation is received, the call is
treated as a normal call.
DN98628099
Issue 10-1 en
93 (264)
srbtSupportIndicator
If this parameter is received, it indicates that the GMSC is
configured to support the SRBT feature. In this case, if the
subscriber has the SRBT service, the SRBT ss-code is
returned in the acknowledgement to the GMSC (the SRBT sscode is not returned if early call forwarding or CAMEL handling
occurs).
If this parameter is not received, but the subscriber has the
SRBT service, the SRBT ss-code is returned in the
acknowledgement to the GMSC only if the HLR configuration
shows that it has to be returned without checking the
srbtSupportIndicator.
gmscSupportIndicator
It indicates that the GMSC is capable of handling proprietary
services.
If this parameter is not received, but the homing functionality is
active in the HLR and the subscriber has a service which
requires the call to be handled by a GMSC supporting the
service, the HLR returns to the GMSC a roaming number
which is formed by concatenating a prefix (configured by the
operator) and the called MSISDN.
extraSignalInfo (proprietary)
This parameter is used in version 2. In version 3, the extraSignalInfo
parameter is inside the extensionContainer.
The ISDN BC information received from the GMSC is used in the
HLR to construct the GSM BC, which is sent towards the VLR in
ProvideRoamingNumber.
Result parameters
In version 3, the result may be segmented (that is, the components,
excluding the last one, are sent in a TC-Result-NotLast primitive).
As an optional feature, some subscription information (see the parameter
descriptions below) may be left out from the SendRoutingInfo-result,
based on the PLMN-specific configuration in the HLR. The checking is
based on the Gateway MSC address.
.
imsi
From the HLR database (subscriber database or Number Portability
database).
94 (264)
DN98628099
Issue 10-1 en
As an optional feature (Features 1545 and 1576: Sequential and

Parallel Alerting), this parameter contains the IMSI of the ringing
group when the call is targeted to the ringing group.
It is sent in the first SendRoutingInfoRes if the result is segmented.
.
extentedRoutingInfo
This parameter is sent in the first SendRoutingInfoRes if the result is
segmented.
.
routingInfo
This parameter is sent if the HLR does not return CAMEL data.
See RoutingInfo.
.
camelRoutingInfo
This parameter is sent if the HLR returns CAMEL O-CSI, TCSI or D-CSI data. See CamelRoutingInfo
cug-CheckInfo
.
cug-Interlock
This parameter is from the invocation parameters, or from HLR
database, if changed.
.
cug-OutgoingAccess
This parameter is from the invocation parameters, or from HLR
database, if changed.
cugSubscriptionFlag
This parameter is sent if the original called party has a CUG
subscription and the T-CSI is active and included in the
DN98628099
Issue 10-1 en
subscriberInfo
.
locationInformation
The parameters received from the VLR in
ProvideSubscriberInfo result are returned in SendRoutingInfo
result. If the vlr-number is not received from the VLR, it is
fetched from the subscriber data in the HLR database.
The vlr-number parameter is always returned, if the address is
available.
Note that the vlr-number received in the
ProvideSubscriberInfo-result is not used in the SRI-result,
instead, the VLR address from the subscriber data in HLR
database is sent in the vlr-number parameter in SRI-result.
95 (264)
subscriberState
This parameter is sent if available (if received from the VLR in
ProvideSubscriberInfo result) and indicated by HLR's
Subscriber Information in SRI ack indicator for subscriber
state.
The parameters received from the VLR in
ProvideSubscriberInfo result are returned in SendRoutingInfo
result. If no subscriber state information is received from the
VLR, the parameter notProvidedFromVLR is returned.
If there is no VLR address in subscriber data in the HLR, the
netDetNotReachable with value msPurged is returned.
If the mscAreaRestircted flag is set in the subscriber data in
the HLR, the netDetNotReachable with value restrictedArea is
returned.
ss-List
This parameter is used in version 3 dialogues. In version 2, the
information is sent in the proprietary sriResExtension, activeSsList.
For detailed information about the usage and content of the ss-List,
see the description for the activeSs parameter.
ext-BasicService
This parameter identifies the basic service related to this call.
It is used in version 3 dialogues. In version 2, the information is sent
in the proprietary sriResExtension, basicServiceCode.
forwardingInterrogationRequired
vmsc-Address
96 (264)
extensionContainer
.
Contains the sriResExtension in version 3. The extension
.
May contain an extension for the SubscriptionType service
(multivendor interworking), ExtensionType is SriResType. The
extension identifier is {iso(1) member-body(2) bsi(826) disc(0)
ericsson(1249) gsmNetworkApplicationsDefinition(58) gsmMap(1) gsm-Map-Ext(0)}. Optional feature. If the
SubscriptionType data is included, the same value is included
also in the RoutingCategory parameter inside the proprietary
SriResExtension.
The SriResData contains the following:
DN98628099
Issue 10-1 en
privateFeatureCode
The privateFeatureCode is '00000010'B
(SubscriptionType).
subscriptionType
Contains a value between 1..127, converted from the
internal RoutingCategory value from the subscriber data
in the HLR database.
naea-PreferredCI
The subscriber's preferred carrier ID is sent in the ETSI-specified
naea-PreferredCI parameter. For backward compatibility, this
information is also sent in the proprietary parameter ansiSriResExt.
The sending of this parameter may be prevented with the PLMNspecific configuration in the HLR.
.
naea-PreferredCIC
ccbs-Indicators
msisdn
numberPortabilityStatus
This parameter is sent in a Mobile Number Portability environment
(Feature 1080: SRF in HLR).
.
notKnownToBePorted
This parameter is sent when the MSISDN in the
SendRoutingInfo invocation belongs to a number portability
cluster, and the number is neither ported in to this HLR, nor
ported out from this HLR. This information is retrieved from the
Number Portability database in the HLR.
.
ownNumberPortedOut
This parameter is sent when the MSISDN in the
SendRoutingInfo invocation is ported out from this HLR. This
information is retrieved from the Number Portability database
in the HLR.
.
foreignNumberPortedToForeignNetwork
DN98628099
Issue 10-1 en
istAlertTimer
supportedCamelPhasesInVMSC
97 (264)

indicates the supported CAMEL phases of the VMSC/VLR where
the subscriber is roaming.
.
offeredCamel4CSIsInVMSC
indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR where
the subscriber is roaming. Sent if the
ssupportedCamelPhasesInVMSC parameter indicates the support
of CAMEL phase 4.
It may contain o-csi, d-csi, vt-csi and mt-sms-csi.
routingInfo2
ss-List2
basicService2
allowedServices
unavailabilityCause
releaseResourcesSupported
gsm-BearerCapability
This parameter contains the GSM BC related to the called MSISDN
from the subscriber data in the HLR database, or converted from the
ISDN BC received in the SendRoutingInfo invocation.
sriResExtension (proprietary)
This parameter is used in version 2. In version 3, the
sriResExtension is inside the extensionContainer. See
SriResExtension
ansiSriResExt (proprietary)
This parameter contains the preferred carrier ID code from
98 (264)
DN98628099
Issue 10-1 en
This extension is sent with the tag [PRIVATE 30] in version 2 and 3
(that is, the extension container is not used in version 3).
This information is sent also in the standardised naea-PreferredCI
parameter.
RoutingInfo
.
roamingNumber
The roaming number is requested from the VLR with
ProvideRoamingNumber, and is returned to the GMSC in
The subscriber's MSISDN number is returned in the roamingNumber
parameter in the following cases:
.
If optimumRoutingPreventation prevents SendRoutingInfo
request from the originating MSC.
.
If the received MSISDN is defined as a service number.
.
If the SendRoutingInfo invocation did not contain the calling
party's Calling Line Identity (in the additionalSignalInfo), and if
the subscriber B has the CLI-Inquiry Service (optional feature Feature 1547: SN and Subscription-based CLI inquiry).
As an optional feature in Mobile Number Portability environments
(Feature 1080: SRF in HLR), the routing number is created by
adding a prefix from the HLR database in front of the MSISDN.
As an optional feature (Feature 1080: SRF in HLR), the prefix may
contain overdecadic hexadecimal digits.
As an optional feature in multivendor networks where homing to a
specific GMSC is required, the routing number is formed by
concatenating a prefix (configured by the operator) and the called
MSISDN. See invocation parameter sriExtension /
gmscSupportIndicator.
If the iN-Capability parameter is present in SendRoutingInfoArg, and
if the subscriber has a MT IN Trigger Key, it is returned in the
proprietary extension, and the roamingNumber parameter contains
an address with no digits (just the first octet with the Nature of
Address and the Numbering Plan is included).
forwardingData
This parameter is sent in the following cases:
DN98628099
Issue 10-1 en
99 (264)
Call Forwarding Unconditional is registered.

Call Forwarding MS Not Reachable is registered and
AbsentSubscriber or NoRoamingNumberAvailable error is
received from the VLR to the ProvideRoamingNumber
operation, or no location info is stored in the subscriber data.
It contains the following items:
.
forwardedToNumber
This parameter is the C-number from subscriber data in the
HLR database.
As a part of Operator Controlled Call Forwarding feature, in a
Call Forwarding MS Not Reachable case, a prefix (from HLR
configuration) may be added in front of the C-number.
The sending of the OCCF C-number may be prevented with
the PLMN-specific configuration in the HLR.
.
.
forwardingOptions
.
extensionContainer
It may contain the EMO-IN OICK and TICK extensions,
ExtensionType is SriResType. The extension identifier is {iso
(1) member-body(2) bsi(826) disc(0) ericsson(1249)
gsmNetworkApplicationsDefinition(58) gsm-Map(1) gsm-MapExt(0)}. Optional feature. If the TICK data is included, the
same trigger key value is included also in the inTriggerKey
parameter inside the SriResExtension.
The sending of the EMO IN triggers may be prevented with the
PLMN-specific configuration in the HLR.
Maximum two SriResData are sent in the SriResType:
The OICK data is sent if it was requested, and if the subscriber
has the EMO IN KEY stored in the HLR database, and if an
early call forwarding is done by the HLR. The SriResData
contains:
.
privateFeatureCode
The privateFeatureCode is '00000110'B (OICK).
.
inCategoryKey
A decadic value (only decimal digits), carrying the EMO
IN KEY.
.
.
100 (264)
DN98628099
Issue 10-1 en
The TICK data is sent always if it was requested, and if the

subscriber has the Trigger Key (SSET) stored in the HLR
database. The TICK data is also sent if it was not requested,
but the subscriber has the Trigger Key (SSET) stored in the
HLR database, and an early call forwarding is done by the
HLR. The SriResData in contains:
.
privateFeatureCode
The privateFeatureCode is '00000111'B (TICK).
.
inCategoryKey
A decadic value (only decimal digits), carrying the
Trigger Key (SSET) from the subscriber data in the HLR
database.
CamelRoutingInfo
.
forwardingData
See the definition of forwardingInfo in routingInfo.
gmscCamelSubscriptionInfo
It contains the subscriber's CAMEL subscription information. In case
of a call to an ringing group with intelligent hunting, the CAMEL data
of the ringing group is returned.
It is based on subscriber data and on the HLR configuration for the
PLMN (of the Gateway MSC), it is decided which CAMEL phase
data is included in the SendRoutingInfo-result.
As an optional feature, it is possible to configure per subscriber
different Default Call/SMS/Session Handling (the
defaultCallHandling paremeter) based on the VPLMN, for each CSI
separately.
.
t-CSI
This parameter is from the subscriber data in the HLR
database.
It is sent if the T-CSI is active and no suppress-T-CSI is
received in the invocation, and if there is no other reason to
suppress the T-CSI (see the Invocation parameter
additionalSignalInfo).
The T-CSI is not sent to the GMSC, if the HLR Triggering
Criteria in the T-CSI restricts the usage of CAMEL by disabling
the sending of the T-CSI. The restriction is based on the VLR
address in the subscriber data.
Only one t-BcsmCamelTDPData is sent in the tBcsmCamelTDPDataList.
.
o-CSI
DN98628099
Issue 10-1 en
101 (264)

It is sent if O-CSI is active, and either CFUnconditional or
CFNotReachable has been registered, or if both O-CSI and TCSI are active.
The O-CSI is not sent to the GMSC, if the HLR Triggering
Criteria in the O-CSI restricts the usage of CAMEL by disabling
the sending of the O-CSI. The restriction is based on the
GMSC address.
Only one o-BcsmCamelTDPData is sent in the oBcsmCamelTDPDataList.
d-csi
SriResExtension
.
inTriggerKey
It contains the IN SSET from subscriber data in the HLR database.
It is sent if the proprietary parameter iN-Capability is received in the
vlrNumber
It is sent if the iN-Capability parameter is received in the
activeSs
It contains the list of active supplementary services for the
subscriber.
The following standard supplementary services may be sent: CFU,
CFB, CFNRY, CFNRC, BAIC, BIRO, BAOC, BOIC, BOIH, CW, CLIP,
CLIR, HOLD, MPTY, AOCI, AOCC, CTR and CT.
Also the PLMN specific service Collect Call Restriction (ss-code
249) may be included.
102 (264)
DN98628099
Issue 10-1 en
The standard services are sent if the iN-Capability parameter is

received in the SendRoutingInfo invocation. The CCR is sent
always, if it is provisioned for the subscriber.
The PLMN-specific ss-code for the SRBT service (the ss-code value
is operator configurable) may also be returned, for conditions see
the invocation parameter sriExtension / srbtSupportIndicator
In version 3 dialogues, this information is sent in the standard ss-List
parameter in the SendRoutingInfo result.
.
traceReference
This parameter is from subscriber data in the HLR database. It is
sent when the On-line Call Monitoring tracing is active for the
subscriber. It is the trace reference of the first OLCM trace.
traceType
This parameter is from subscriber data in the HLR database. It is
sent when the On-line Call Monitoring tracing is active for the
subscriber. It is the trace type of the first OLCM trace.
Possible values: record (3), record&report (7).
omc-Id
hotBilling
This parameter subscriber data in HLR database. It is sent if the
service is provisioned for the subscriber.
cfoIsDone
This parameter is sent if SendRoutingInfo invocation contains the
callForwardingOverride parameter, and CF Unconditional is active.
cfInCug
This parameter is sent if the calling and the called subscribers are
members of the same CUG, and if call forwarding is active and calls
are not barred.
basicService
This parameter identifies the basic service related to this call.
In version 3 dialogues, this information is sent in the standard
basicService parameter in the SendRoutingInfo result.
category
DN98628099
Issue 10-1 en
103 (264)
As an optional feature, non-standard category values may be used.

.
routingCategory
pnpIndex
nokia-CUG
.
cug-Interlock
This parameter is the CUG interlock code of the subscriber B
and returned if call forwarding is active (Call Forwarding
Unconditional, or Call Forwarding Not Reachable).
.
cug-OutgoingAccess
.
cug-CallInfo
The two least significant bits of cug-CallInfo: 00 = not used, 01
= CUG call, 10 = non CUG call, 11 = maybe a CUG call.
noBarrings
This parameter is sent if the forwarding subscriber has no active
outgoing call barring.
odb-Data
This parameter is sent if the forwarding subscriber has operator
determined outgoing call barring.
fraudData
This parameter is fraud data for call forwarding.
For details, see the definition of fraudData in InsertSubscriberData /
IsdArgExt.
extRoutingCategory
104 (264)
DN98628099
Issue 10-1 en
.
leaId
This parameter is the Law Enforcement Agency of the first OLCM
trace.
olcmInfoTable
This parameter contains the traceReference, traceType and leaId for
the maximum of 6 additional OLCM traces.
callingCategory
This parameter is sent with value 'E8'hex if the SendRoutingInfo
invocation did not contain the calling party's Calling Line Identity (in
the additionalSignalInfo) and an indication that the call is forwarded
(numberOfForwarding parameter), and if the subscriber B has the
CLI-Inquiry Service (optional feature - Feature 1547: SN and
Subscription-based CLI inquiry), and if no call forwarding by HLR
occurs.
In this case, the subscriber's MSISDN number is returned in the
roamingNumber parameter.
commonMSISDN
This parameter is the subscriber's common MSISDN from the
rgData
This parameter contains the ringing group data.
Sent if the SendRoutingInfo invocation contained the indicator for
the support of sequential/parallel alerting, and if the called MSISDN
was the ringing group number. If intelligent hunting is defined for the
ringing group, rgData is sent if the SendRoutingInfo invocation
contained the indicator for the support of intelligent alerting.
.
noAnswerTimer
This parameter is the Hunting Time from ringing group data
depending on the ringing group type. It is sent if the GMSC
indicated the support for the corresponding alerting type. The
value range is from 1 to 255 seconds.
.
memberList
DN98628099
Issue 10-1 en
105 (264)
This parameter contains the MSISDNs of the ringing group

members, from the ringing group data in the HLR database.
Only the active members are included.
alertingMethod
The alerting method selection is based on the GMSC
capability and the ringing group type (sequential, parallel,
parallel preferred or intelligent).
userType
A single user with several devices, or multiple users with their
own devices. This information is from the ringing group data.
divertedToNbr
The Operator Controlled Call Forwarding number for the
ringing group if the forwarding is active.
memberOfSuppression
No (member's own call forwarding has higher priority than next
member alerting) or yes (next member alerting has higher
priority), information from the ringing group data.
ringbacktone
Basic tone or individual tone, information from the ringing
group data.
Error causes
.
SystemFailure
It is sent if the ProvideRoamingNumber operation between HLR and
VLR fails.
.
extensionContainer
In version 3 dialogues the subscriber's IMSI and the On-line
Call Monitoring data (from subscriber data in HLR database)
may be sent in the proprietary ErrOlcmInfoTableExt in the
extensionContainer. Maximum of seven olcmInfo are included,
each containing parameters traceReference, traceType, and
leaId.
The extension identifier for the ErrOlcmInfoTableExt is {0 34
23}.
DataMissing
It is never sent.
UnexpectedDataValue
106 (264)
DN98628099
Issue 10-1 en
It is sent if a FacilityNotSupported is received from the VLR for
ProvideRoamingNumber operation.
.
extensionContainer
leaId.
23}.
OR-NotAllowed
It is sent if the SendRoutingInfo was optimally routed, but Optimal
Routing is not allowed by the HLR. Sent also if the call was optimally
routed, and the error OR-NotAllowed was received from the VLR in
ProvideRoamingNumber response.
UnknownSubscriber
It is sent if the MSISDN in the SendRoutingInfo invocation is
unknown in the HLR.
NumberChanged
It is never sent.
BearerServiceNotProvisioned: sent if the received ISDN BC

information indicates that the call is for a basic service which is not
provisioned for the subscriber.
It is never sent.
AbsentSubscriber
It is sent if subscriber data contains no VLR address, or if an
AbsentSubscriber error is received from the VLR for
ProvideRoamingNumber operation, or if the request is for a ringing
group and all the group members are inactive (and the CFNRC is not
registered for the subscriber, or the CFNRC cannot be invoked
because the callForwardingOverride indicator was received in the
invocation).
.
extensionContainer
DN98628099
Issue 10-1 en
107 (264)
In version 3 dialogues the extensionContainer is used. The

subscriber's IMSI and the On-line Call Monitoring data (from
subscriber data in HLR database) are sent in the proprietary
AbsentSubscriberExt. Maximum of seven olcmInfo are
included, each containing parameters traceReference,
traceType, and leaId.
The extension identifier for the AbsentSubscriberExt is {0 34
17}.
.
BusySubscriber
It is sent if the call is rejected because of CCBS.
.
extensionContainer
leaId.
23}.
NoSubscriberReply
It is never sent.
108 (264)
CallBarred
.
callBarringCause
.
barringServiceActive
It is sent if the subscriber has an active call barring
supplementary service applicable to this call.
.
operatorbarring
It is sent if the subscriber has active operator-determined
call barring applicable to this call, or if the subscriber or
the ringing group is deactivated.
.
extensionContainer
leaId.
23}.
DN98628099
Issue 10-1 en
CUG-Reject
.
cug-RejectCause
.
incomingCallsBarredWithinCUG
It is sent if the subscriber is not allowed to receive
incoming calls from other members of the same CUG.
.
subscriberNotMemberOfCUG
It is sent if the calling and called subscribers are not
members of the same CUG, and the calling subscriber
has no outgoing access and/or the called subscriber has
no incoming access.
.
requestedBasicServiceViolatesCUG-Constraints
It is sent if CUG is provisioned but CUG interlock is not
received and called subscriber has no incoming access.
.
calledPartySS-InteractionViolation
It is sent if the subscriber is a member of CUG, call
forwarding is set, and CF/CUG interaction fails. For more
detailed use of this CUG-RejectCause, see GSM 03.85,
Closed User Group (CUG) Supplementary Services,
stage 2.
.
extensionContainer
leaId.
23}.
ForwardingViolation
Sent if the maximum number of allowed call forwardings for one call
(as configured in the HLR) is exceeded.
.
extensionContainer
leaId.
23}.
DN98628099
Issue 10-1 en
109 (264)
3.2.4.2
ProvideRoamingNumber
It is invoked by the HLR and confirmed by the VLR.
.
Operation timer: 15 seconds.

As an optional feature, the timer value can be modified to any value
between 1 and 29 seconds.
SCCP address: SPC or GT, VLR address from subscriber data
.
imsi
msc-Number
msisdn
It contains the subscriber's common MSISDN, if the MSISDN in the
SendRoutingInfo belongs to the primary basic service and the
sending of the common MSISDN is allowed towards the VLR in the
PLMN-specific parameters in the HLR.
previousRoamingNumber
lmsi
This parameter is the GSM BC related to the called MSISDN from
subscriber data in the HLR database, or converted from the ISDN
BC received in SendRoutingInfo operation.
110 (264)
DN98628099
Issue 10-1 en
Used for a data call, contains the GSM-BC. The protocolId is gsm0408.
.
networkSignalInfo
This parameter is used for a data call and it contains the ISDN-BC,
HLC and LLC. The protocolId is ets-300102-1.
This parameter is sent if received from the GMSC in
It indicates to the VLR that announcements or tones generated as a
result of unsuccessful call setups have to be suppressed.
gmsc-Address
This parameter is sent if received from the GMSC in a
callReferenceNumber
This parameter is sent if received from the GMSC in a
or-Interrogation
It is sent if the SendRoutingInfo was optimally routed, and Optimal
Routing is allowed for the call.
alertingPattern
ccbs-Call
supportedCamelPhasesInInterrogatingNode
From SendRoutingInfo invocation.
This parameter contains Calling Line Identity and Generic Number
received from the GMSC in a SendRoutingInfo invocation.
Forwarded to the VLR in ProvideRoamingNumber invocation if the
subscriber has CLI-E provisioned, and if the PLMN-specific
parameters allow sending of CLI and Generic Number to the VLR.
DN98628099
Issue 10-1 en
orNotSupportedInGMSC
111 (264)
This parameter is sent if the SendRoutingInfo invocation did not

contain the 'or-capability' parameter.
.
pre-pagingSupported
longFTN-Supported
suppress-VT-CSI
This parameter is sent if this parameter is received in the
offeredCamel4CSIsInInterrogatingNode
It indicates the CAMEL 4 CSIs offered in the GMSC, the parameter
value is from the SendRoutingInfo invocation. May contain o-csi, dcsi and t-csi.
Result parameters
.
roamingNumber
This parameter is forwarded to the gateway MSC in a
Error causes
.
SystemFailure
If received, a SystemFailure error for the SendRoutingInfo operation
is sent to the GMSC.
DataMissing
UnexpectedDataValue
If received, a FacilityNotSupported error for the SendRoutingInfo
operation is sent to the GMSC.
112 (264)
OR-NotAllowed
DN98628099
Issue 10-1 en

is sent to the GMSC. If the SendRoutingInfo was optimally routed,
and this error is received from the VLR, the OR-NotAllowed error for
the SendRoutingInfo operation is sent to the GMSC.
.
AbsentSubscriber
If received, the Call Forwarding Not Reachable registration status is
checked. If Call Forwarding Not Reachable is active,
forwardedToNumber is sent to the Gateway MSC in
SendRoutingInfo result. If CF is not active, AbsentSubscriber error is
forwarded to the Gateway MSC.
If this error is qualified with the reason purgedMS, the VLR address
is removed from the subscriber data in the HLR database. If an error
AbsentSubscriber is sent to the GMSC, it is qualified with the reason
imsiDetach.
NoRoamingNumberAvailable
If received, the Call Forwarding Not Reachable registration status is
checked. If Call Forwarding Not Reachable is active,
forwardedToNumber is sent to the Gateway MSC in
SendRoutingInfo result. If CF is not active, SystemFailure error is
sent to the Gateway MSC.
BusySubscriber: if received, the Call Forwarding Busy status is

checked. If Call Forwarding Busy is active, the forwardedToNumber
is sent to the Gateway MSC in the SendRoutingInfo result. If CFB is
not active, an AbsentSubscriber error is sent to the Gateway MSC.
The support for this proprietary error code for the
ProvideRoamingNumber operation is optional (used for IS-41
interworking).
3.2.4.3
SetReportingState
corresponding version 1 or 2 operations exist.
DN98628099
Issue 10-1 en
113 (264)
.
imsi
lmsi
ccbs-Monitoring
This parameter is from CCBS application.
Result parameters
.
ccbs-SubscriberStatus
This parameter is stored to subscriber data in the HLR database.
Error causes
3.2.4.4
SystemFailure
UnexpectedDataValue
DataMissing
ResourceLimitation
StatusReport
This operation is implemented in version 3 dialogue only. No
.
imsi
This parameter is a key to the subscriber data in the HLR database.
In error cases an UnknownSubscriber error is sent.
114 (264)
DN98628099
Issue 10-1 en
eventReportData
The ccbs-SubscriberStatus is forwarded to the CCBS application.
callReportData
The monitoringMode and callOutcome are forwarded to the CCBS
application.
Result parameters
The result contains no parameters (the empty SEQUENCE is not sent).
Error causes
.
UnknownSubscriber
It is sent if the IMSI in the StatusReport invocation is unknown in the
HLR.
SystemFailure
It is never sent.
UnexpectedDataValue
DataMissing
It is never sent.
3.2.4.5
RemoteUserFree
.
Operation timer: 3 minutes
.
imsi
DN98628099
Issue 10-1 en
callInfo
115 (264)
This parameter contains the ISDN-BC, HLC and LLC related to the
call.
.
ccbs-Feature
.
ccbs-index
This parameter is from CCBS
.
b-subscriberNumber
.
b-subscriberSubaddress
.
basicServiceCode
application.
application.
application.
application.
translateB-Number
replaceB-Number
This parameter is sent if CAMEL service is not active and MS is in
detached state.
alertingPattern
Result parameters
.
ruf-Outcome
This parameter is forwarded to CCBS application.
Error causes
116 (264)
UnexpectedDataValue
DataMissing
IncompatibleTerminal
AbsentSubscriber
SystemFailure
BusySubscriber
DN98628099
Issue 10-1 en
3.2.5
Supplementary service operations
3.2.5.1
BeginSubscriberActivity
This operation is implemented in version 1 dialogues only. In version 2 the
related information is sent in MAP-Open PDU in TCAP dialogue portion
(see Dialogue information). The used version for the MAP dialogue
between the HLR and the gsmSCF depends on the version in which the
Supplementary Service operation invocation is received from the VLR.
If ss-code is PLMN-specific in RegisterSS, EraseSS, ActivateSS,
DeactivateSS, InterrogateSS or RegisterPassword the message is
forwarded to the gsmSCF-interface. If the gsmSCF interface is not in use,
HLR aborts the dialogue.
It is invoked by the VLR and handled by the HLR.
.
SCCP address: GT, gsmSCF's address from HLR data
.
imsi
error cases:
.
UnknownSubscriber is sent for operations RegisterSS,
EraseSS, ActivateSS, DeactivateSS and InterrogateSS.
.
The dialogue is aborted with a TC-U-ABORT for
RegisterPassword operation.
If the mobile-originated operation is forwarded to the gsmSCF, the
subscriber's MSISDN or the ringing group's common MSISDN may
be sent instead of the IMSI (optional feature - Feature 448: MAP
Interface for SCP in HLR).
originatingEntityNumber
If the message is forwarded to the gsmSCF, the
originatingEntityNumber contains the same value which was
received from the VLR.
DN98628099
Issue 10-1 en
117 (264)
As an optional feature, based on a subscriber specific indicator the

subscriber's MSISDN is used as a value of the
originatingEntityNumber, when the message is forwarded to the
gsmSCF.
3.2.5.2
RegisterSS
One TC-Begin primitive may contain several RegisterSS invocation
components.
Registration overrides the old data if the service has already been
registered.
.
ss-Code
This parameter is used for subscription/provision checking. In error
cases an SSErrorStatus error is sent.
The ss-code can be any of the implemented call forwarding
supplementary services. Otherwise, an IllegalSS-Operation error is
sent.
As an optional feature (Feature 626: GSM Supplementary Services
Phase 2 Extensions; SMS forwarding) the Call Forwarding
Unconditional can be registered for the Mobile Terminated SMS
service. See the explanation for the parameter basicService for
more details.
basicService
Individual basic services are interpreted as the corresponding basic
service group.
If not received, the registration is to all applicable basic services.
118 (264)
DN98628099
Issue 10-1 en

service, basicService T21. The registration is accepted if the Csubscriber (as indicated by the parameter forwardedToNumber)
belongs to an allowed PLMN.
.
forwardedToNumber
This parameter is stored as a FORWARDED TO NUMBER in
subscriber data.
Checked against call barring supplementary services. In error cases
an SS-Incompatibility error is sent.
Checked against Operator Determined Barring services. In case
'Barring of changing a call forwarding number' (proprietary) is active,
and if the forwardedToNumber is not the same as already stored in
the subscriber data in the HLR database, error CallBarred is sent.
Checked in the FORWARDED TO NUMBER analysis for allowed
destinations. Checked also that a ringing group member does not
set forwarding to the own group number. In error cases a CallBarred
error is sent.
service. The forwardedToNumber parameter is used as the msisdn
in the SendIMSI operation, which is done for the PLMN checking. If
the forwardedToNumber is not received in an international format, it
is converted to international before the SendIMSI. Registration is
accepted if the C-subscriber (as indicated by the parameter
'forwardedToNumber') belongs to an allowed PLMN.
The maximum allowed length of the forwardedToNumber is 15 or 16
digits, depending on HLR configuration. In error cases an
As an optional feature, the maximum allowed length for the
forwardedToNumber parameter is 18 digits. However, after
conversion to international format, the length must not exceed 16
digits.
If the forwardedToNumber parameter is not present, a DataMissing
error is sent.
DN98628099
Issue 10-1 en
119 (264)
This parameter is stored as the NO REPLY CONDITION TIME in the

subscriber data.
If not received, the default value from HLR data is stored to
subscriber data.
.
defaultPriority
nbrUser
This parameter indicates the maximum number of simultaneous CS
bearers allowed (Multicall), as requested by the subscriber.
longFTN-Supported
forwardingInfo
Result parameters
The status of the forwarding data after the registration is returned.

The forwardingOptions parameter is sent for CF No Reply.
.
callBarringInfo
ss-Data
.
ss-Status
This parameter is sent in case of Multicall registration.
.
nbrUser
This parameter is sent if the Multicall registration is accepted.
UnknownSubscriber
Error causes
It is sent if the IMSI in the BeginSubscriberActivity operation is not

known in the HLR.
.
IllegalSS-Operation
It is sent if the ss-Code in the invocation is not Call Forwarding.
SS-ErrorStatus
It is sent if the service in the invocation is not provisioned for the
subscriber.
120 (264)
DN98628099
Issue 10-1 en
The additional parameter ss-Status is sent with value 'not

provisioned + not registered + not active'.
.
Never sent.
Never sent.
It is never sent.
CallBarred
It is sent with cause value operatorBarring, if 'Supplementary
Service access' is barred by the operator, or if 'Barring of changing a
call forwarding number' (proprietary) is active and if the
forwardedToNumber is not the same as already stored in the
subscriber data in the HLR database (in version 1 dialogues, the
IllegalSS-Operation error cause is used).
Phase 2 Extensions; SMS forwarding) this error is sent if the PLMN
checking of the C-subscriber fails, either because of a failed
SendIMSI operation, or because the PLMN checking results in a not
allowed PLMN (see the invocation parameter basicService).
SS-Incompatibility
It is sent if a call barring or a registered Call Forwarding
Unconditional prevents the requested registration.
The ss-Code parameter contains the service, which prevents the
requested registration.
The received basic service is returned in the basicService
parameter.
The ss-Status parameter has value 'provisioned + not registered +
active', if call barring prevents registration, and 'provisioned +
registered + active', if call forwarding prevents registration.
UnexpectedDataValue
DataMissing
It is sent if the received invocation did not contain the
forwardedToNumber.
DN98628099
Issue 10-1 en
121 (264)
SystemFailure
It is never sent.
3.2.5.3
EraseSS
One TC-Begin primitive may contain several EraseSS invocation
components.
.
ss-Code
Applicable to all implemented call forwarding supplementary
services. In error cases an IllegalSS-Operation error is sent.
basicService
service group.
If not received, the erasure is to all applicable basic services.
longFTN-Supported
Result parameters
The positive result is sent even if already before the erasure procedure the
state of the service is not registered.
.
forwardingInfo
If there was no basic service code in the EraseSS invocation, an
empty result is sent. If there was a basic service code in the request,
forwardingInfo is included in the result, containing the ss-code and
the ss-status for each applicable elementary basic service group.
callBarringInfo
122 (264)
DN98628099
Issue 10-1 en
ss-Data
Error causes
.
UnknownSubscriber
known in the HLR.
IllegalSS-Operation
It is sent if the ss-Code in the invocation is not Call Forwarding.
SS-ErrorStatus
subscriber.
It is never sent.
UnexpectedDataValue
SystemFailure
It is never sent.
DataMissing
It is never sent.
It is never sent.
It is never sent.
CallBarred
It is sent with cause value operatorBarring if Supplementary Service
access is barred by the operator (in version 1 dialogues, the
IllegalSS-Operation error is used).
DN98628099
Issue 10-1 en
123 (264)
3.2.5.4
ActivateSS
One TC-Begin primitive may contain several ActivateSS invocation
components.
.
ss-Code
Applicable to call forwarding, call barring and call waiting
supplementary services. In error cases an IllegalSS-Operation error
is sent.
basicService
service group.
If not received, the activation is to all applicable basic services. If the
HLR notices that the activation cannot be accepted for some basic
services (e.g. because of the active state of some other
supplementary services), the result message contains those basic
services, for which the activation was successful.
Since partial acceptance cannot be carried with Call Waiting, the
following approach is adopted. If CW activation cannot be accepted
for all basic service groups that are requested, the activation is
rejected.
longFTN-Supported
Result parameters
The result is sent even if the service was already activated.
124 (264)
DN98628099
Issue 10-1 en
forwardingInfo
If there was no basic service code in the ActivateSS invocation, and
the activation can be accepted for all applicable basic services, an
empty result is sent.
In case of partial acceptance, the result message contains those
basic service groups, for which the activation was successful.
If there was a basic service code in the request, forwardingInfo is
included in the result, containing the ss-code and the ss-status, the
forwardedToNumber and the forwardingOptions (in case of CF no
reply) for each applicable elementary basic service group.
callBarringInfo
The status of call barring data after activation is returned.
In case of partial acceptance, the result message contains those
basic services, for which the activation was successful.
ss-Data
The status of call waiting data after activation is returned.
Error causes
.
UnknownSubscriber
known in the HLR.
NegativePW-Check
It is sent if a wrong password is received from the MS during
activation of call barring services.
NumberOfPW-AttemptsViolation
It is never sent.
IllegalSS-Operation
Sent if the ss-Code in the invocation is not call forwarding, call
barring, or call waiting.
SS-ErrorStatus
subscriber.
DN98628099
Issue 10-1 en
125 (264)

.
It is sent if the subscriber does not have 'Use of password' option.
SS-Incompatibility
It is sent if a call barring or a registered Call Forwarding
Unconditional prevents the requested registration.
The ss-Code parameter contains the service which prevents the
requested registration.
The received basic service is returned in the basicService
parameter.
The ss-Status parameter has value 'provisioned + not registered +
active', if call barring prevents registration, and 'provisioned +
registered + active', if call forwarding prevents registration.
UnexpectedDataValue
It is never sent.
SystemFailure
It is never sent.
DataMissing
It is never sent.
It is never sent.
It is never sent.
CallBarred
It is sent with cause value operatorBarring, if Supplementary Service
3.2.5.5
DeactivateSS
126 (264)
DN98628099
Issue 10-1 en
One TC-Begin primitive may contain several DeactivateSS invocation

components.
.
ss-Code
Applicable to call forwarding, call barring and call waiting
supplementary services. In error cases an IllegalSS-Operation error
is sent.
basicService
service group.
If not received, the activation is to all applicable basic services.
longFTN-Supported
Result parameters
The result is sent even if the service was already deactivated.
.
forwardingInfo
The status of the forwarding data after the deactivation is returned.
ForwardedToNumber, forwardingOptions and
noReplyConditionTime parameters are not sent.
callBarringInfo
The status of call barring data after deactivation is returned.
ss-Data
The status of call waiting data after deactivation is returned.
DN98628099
Issue 10-1 en
127 (264)
Error cases
.
UnknownSubscriber
known in the HLR.
IllegalSS-Operation
It is sent if the ss-Code in the invocation is not call forwarding, call
barring, or call waiting.
SS-ErrorStatus
subscriber.
It is sent if the subscriber does not have 'Use of password' option.
NegativePW-Check
It is sent if a wrong password is received from the MS during
deactivation of call barring services.
It is never sent.
UnexpectedDataValue
It is never sent.
SystemFailure
It is never sent.
DataMissing
It is never sent.
It is never sent.
It is never sent.
128 (264)
CallBarred
DN98628099
Issue 10-1 en
Sent with cause value operatorBarring if Supplementary Service

access is barred by the operator (in version 1 dialogues the
3.2.5.6
InterrogateSS
One TC-Begin primitive may contain several InterrogateSS invocation
components.
.
ss-Code
This parameter is used for subscription/provision and status
checking.
The interrogation can be done for CFU, BAIC or BIRO. If some other
specified supplementary services are interrogated, the error
IllegalSS-Operation is sent. If the ss-Code contains an unspecified
value, the error UnexpectedDataValue is sent.
basicService
cases the result is returned indicating ss-Status as 'not provisioned'.
service group.
If not received, the activation is to all applicable basic services.
longFTN-Supported
ss-Status
Result parameters
The status is returned in this parameter in the following cases:

.
The service is not provisioned.
.
The interrogated call barring is provisioned but not activated.
.
The interrogated call forwarding is provisioned but not
activated.
.
The status of call waiting is interrogated.
.
DN98628099
Issue 10-1 en
forwardedToNumber
129 (264)

.
In case of call barring interrogation, it contains the basic services
that have a call barring active.
In case of call forwarding interrogation, it contains the status of the
forwarding data.
The forwarded ToNumber, forwardingOptions and
noReplyConditionTime parameters are not sent.
genericServiceInfo
.
ss-Status
It is never sent.
.
cliRestrictionOption
It is never sent.
.
maximumEntitledPriority
.
defaultPriority
.
ccbs-FeatureList
This parameter is used in case of CCBS.
.
nbrSB
.
nbrUser
.
nbrSN
UnknownSubscriber
Error cases
Sent if the IMSI in the BeginSubscriberActivity operation is not

known in the HLR.
.
IllegalSS-Operation
Sent if the supplementary service cannot be interrogated from the
HLR.
SS-NotAvailable
It is never sent.
130 (264)
DN98628099
Issue 10-1 en
UnexpectedDataValue
It is sent if the ss-Code in the invocation contains an unspecified
value.
SystemFailure
It is never sent.
DataMissing
It is never sent.
It is never sent.
It is never sent.
CallBarred
access is barred by the operator (in version 1 dialogue, the
3.2.5.7
ProcessUnstructuredSS-Data
higher, ProcessUnstructuredSS-Request is used.
Invoked by the VLR and forwarded by the HLR to gsmSCF. Confirmed by
the gsmSCF.
This operation is received from the VLR and forwarded to gsmSCF. If the
gsmSCF-interface is not in use, the HLR aborts the dialogue.
As an optional feature (Features 1545 and 1576: Sequential and Parallel
Alerting), the USSD is handled in the HLR, for ringing group interrogation
or modification.
.
SCCP address: GT, gsmSCF's address as a result of the USSD

string analysis
If the result of the USSD string analysis gives a routing address, the
destination subsystem number is also received from the analysis
result (if not specified in the analysis result, the default value is 5).
DN98628099
Issue 10-1 en
131 (264)
.
ss-UserData
This parameter is analysed in the HLR to see whether the USSD is
to be handled locally, or forwarded to the gsmSCF.
Result parameters
.
ss-UserData
If the result message is received from the gsmSCF and is to be
forwarded towards the VLR, the content of ss-UserData is not
checked by the HLR.
If the USSD was handled locally in the HLR, the string content
depends on the functionality which is done as the result of the USSD
string analysis.
Error causes
If an error cause is received from the gsmSCF, it is forwarded to the VLR.
The possible error causes are:
.
SystemFailure
This error cause is sent by the HLR to the VLR, if the subscriber has
the Mobile Initiated USSD barring service active.
3.2.5.8
UnexpectedDataValue
ProcessUnstructuredSS-Request
This operation is implemented in version 2 dialogues only. In version 1
ProcessUnstructuredSS-Data is used.
This operation is received from the VLR and forwarded to gsmSCF. If the
gsmSCF-interface is not in use (if the feature is not activated), the HLR
aborts the dialogue indicating that the Application Context is not
supported.
As an optional feature, based on a subscriber specific indicator only phase
1 USSDs are accepted, in which case the HLR aborts the version 2
dialogue indicating that the Application Context is not supported, and that
only version 1 is supported.
132 (264)
DN98628099
Issue 10-1 en
As an optional feature (Features 1545 and 1576: Sequential and Parallel

Alerting), the USSD is handled in the HLR, for ringing group interrogation
or modification.
As an optional feature (Feature 1609: Follow Me), the USSD is forwarded
to another HLR, which handles the USSD and responds to it.
.
SCCP address: GT, gsmSCF's address as a result of the USSD

string analysis
If the result of the USSD string analysis gives a routing address, the
destination subsystem number is also received from the analysis
result (if not specified in the analysis result, the default value is 5).
When the USSD is forwarded from HLRa to HLRb, because of the
Feature 1609: Follow Me, the MSISDN of the subscriber in HLRb is
used as the Global Title. In that case the Subsystem Number 6
(HLR) is used in both the Called Party Address and the Calling Party
Address.
.
ussd-DataCodingScheme
This parameter is used for decoding the ussd-String to make the
USSD string analysis in the HLR.
Supported coding schemes are:
.
7 bit coding, ussd-DataCodingScheme values (hexadecimal):
00..0F, 10, 40..43, 50..53, F0..F3
.
8 bit coding (normal ASCII), ussd-DataCodingScheme values
(hexadecimal): 44..47, 54..57, F4..F7
.
16 bit coding, ussd-DataCodingScheme values (hexadecimal):
11, 48..4B, 58..5B. Characters 0000..007E with this coding
scheme are supported
ussd-String
This parameter is analysed in the HLR to see whether the USSD is
to be handled locally, or forwarded to the gsmSCF.
Due to limitations on the underlying layers (MTP, SCCP and TCAP),
the maximum feasible length of the ussd-String in
ProcessUnstructuredSS-Request argument is 134 bytes. Otherwise
the overall MTP message length may exceed the limit of 272 bytes,
DN98628099
Issue 10-1 en
133 (264)
unless SCCP segmentation is used. When the mobile originated

USSD message is forwarded from the HLR to the gsmSCF, the HLR
may also add the msisdn parameter into the message (see the
description for the msisdn parameter below); that further reduces the
size available for the ussd-String.
If the string contains a command for the Feature 1609: Follow Me,
the rest of the message parameters are checked to see whether the
message is to be forwarded from this HLR (HLRa) to another HLR
(HLRb), or handled locally in this HLR (HLRb).
.
alertingPattern
This parameter is ignored if received from the VLR, it is not sent to
the gsmSCF.
msisdn
This parameter is from subscriber data or from the ringing group data
in the HLR database. This parameter is sent if so configured with the
SCP interface configuration (an optional feature is Feature 448:
MAP Interface for SCP in HLR).
The same MSISDN may also be sent instead of the IMSI as the
destinationReference (in the MAP-Open dialogue PDU) if so
configured with the SCP interface configuration.
When the USSD is forwarded from HLRa to HLRb, because of the
Feature 1609: Follow Me, this parameter contains the MSISDN of
the subscriber in HLRa (the MSISDN of the recipient subscriber, in
HLRb, is sent in MAP-Open in the destinationReference parameter).
ussd-Extension (proprietary)
.
routingCategory
This parameter is from subscriber data in the HLR database if
optional feature - Feature 503: Routing Categories, is active. It
is sent if so configured with the SCP interface configuration (an
optional feature is Feature 448: MAP Interface for SCP in
HLR).
Result parameters

forwarded towards the VLR, the content of ussdDataCodingScheme is not checked by the HLR.
If the USSD was handled locally in the HLR, the same coding
scheme as in the invocation is used.
134 (264)
DN98628099
Issue 10-1 en
ussd-String
forwarded towards the VLR, the content of ussd-String is not
checked by the HLR.
If the USSD was handled locally in the HLR, the string content
depends on the functionality which is done as the result of the USSD
string analysis.
(See the note for the ussd-String parameter in the invocation.) The
maximum feasible length of the ussd-String in
ProcessUnstructuredSS-Request result is 157 bytes (first response
from the USSD center), or 160 bytes (UnstructuredSS-Request or
UnstructuredSS-Notify has been sent before
ProcessUnstructuredSS-Request result, during the same dialogue).
Error causes
If an error cause is received from the gsmSCF, it is forwarded to the VLR.
.
SystemFailure
DataMissing
UnexpectedDataValue
UnknownAlphabet
CallBarred
This error cause is sent by the HLR to the VLR, if the subscriber has
the Mobile Initiated USSD barring service active.
3.2.5.9
UnstructuredSS-Request
It is invoked by the gsmSCF and forwarded by the HLR to VLR. Confirmed
by the VLR.
DN98628099
Issue 10-1 en
135 (264)
.
Contents are not checked by the HLR. Forwarded to the VLR.
ussd-String
the maximum feasible length of the ussd-String in UnstructuredSSRequest is 145 bytes (when UnstructuredSS-Request is sent as the
first message in a network-initiated USSD dialogue), 154 bytes
(when UnstructuredSS-Request is the first response to a mobileoriginated USSD) or 160 bytes (subsequent messages in USSD
dialogues, either mobile-originated or network-initiated). Otherwise
unless SCCP segmentation is used.
alertingPattern
This parameter is ignored if received from the gsmSCF. This
parameter is not sent to the VLR.
Result parameters
.
Contents are not checked by the HLR. Forwarded to the gsmSCF.
ussd-String
Contents are not checked by the HLR. Forwarded to the gsmSCF.
(See the note for the ussd-String parameter in the invocation.) The
maximum feasible length of the ussd-String in UnstructuredSSRequest result is 145 bytes (first response from the mobile station,
during a network-initiated USSD dialogue) or 160 bytes (responses
from the mobile station in other situations).
Error causes
If an error cause is received from the VLR, it is forwarded to the gsmSCF.
136 (264)
SystemFailure
DataMissing
UnexpectedDataValue
DN98628099
Issue 10-1 en
3.2.5.10
AbsentSubscriber
IllegalSubscriber
IllegalEquipment
UnknownAlphabet
USSD-Busy
UnstructuredSS-Notify
This operation is implemented in version 2 dialogue only. No
It is invoked by the gsmSCF and forwarded by the HLR to VLR. Confirmed
by the VLR.
.
.
ussd-String
the maximum feasible length of the ussd-String in UnstructuredSSRequest is 145 bytes (when UnstructuredSS-Request is sent as the
first message in a network-initiated USSD dialogue), 154 bytes
(when UnstructuredSS-Request is the first response to a mobileoriginated USSD) or 160 bytes (subsequent messages in USSD
dialogues, either mobile-originated or network-initiated). Otherwise
unless SCCP segmentation is used.
alertingPattern
This parameter is ignored if received from the gsmSCF, it is not sent
to the VLR.
DN98628099
Issue 10-1 en
137 (264)
Result parameters
The result contains no parameters. The empty TC-Result from VLR is
forwarded to the gsmSCF.
Error causes
If an error cause is received from the VLR, it is forwarded to the gsmSCF.
3.2.5.11
SystemFailure
DataMissing
UnexpectedDataValue
AbsentSubscriber
IllegalSubscriber
IllegalEquipment
UnknownAlphabet
USSD-Busy
RegisterPassword
Linked operation: GetPassword. If the GetPassword fails, the dialogue is
aborted.
.
ss-Code
This parameter is used for 'use of password' option checking. In
error cases an SS-SubscriptionViolation error is sent.
It contains a call barring service. In error cases an
Result parameters
.
138 (264)
newPassword
DN98628099
Issue 10-1 en
This parameter contains the new password received from the MS

with GetPassword operation.
Error causes
.
NegativePasswordCheck
It is sent if a wrong password is received from the MS when
requesting an old password.
PasswordRegistrationFailure
It is sent if there is problem in a new password or any syntactical
error in the GetPassword operation.
The diagnostic parameter is sent with value
newPasswordsMismatch (2).
It is sent if the subscriber does not have the 'Use of password'
option.
UnexpectedDataValue
It is sent if the invocation contains a supplementary service other
than call barring.
SystemFailure
It is never sent.
DataMissing
It is never sent.
CallBarred
PasswordRegistrationFailure error is used).
It is never sent.
3.2.5.12
GetPassword
Linked to operation: RegisterPassword.
DN98628099
Issue 10-1 en
139 (264)
SCCP address: Calling party address in RegisterPassword,

ActivateSS or DeactivateSS operation
.
GuidanceInfo
.
enterPW
This parameter is sent in the first GetPassword during a
dialogue.
.
enterNewPW
This parameter is sent in the second GetPassword during a
dialogue.
.
enterNewPW-Again
This parameter is sent in the third GetPassword during a
dialogue.
.
badPW-TryAgain
.
badPW-FormatTryAgain
currentPassword
Result parameters
In mismatched cases the appropriate error cause is sent to

RegisterPassword, ActivateSS or DeactivateSS operation.
3.2.5.13
SS-InvocationNotification
Invoked by the HLR and confirmed by the gsmSCF.
140 (264)
SCCP address: GT, the gsmSCF address from subscriber's SS-CSI

subscription data in HLR database
DN98628099
Issue 10-1 en
.
imsi
msisdn
ss-Event
This parameter identifies the event which triggers the transaction:
ccbs= '01000100'B.
ss-EventSpecification
b-subscriberNumber
This parameter indicates the destination address of the CCBS
request.
ccbs-RequestState
This parameter indicates the current state of the CCBS request.
Result parameters
Any possible parameters in the result are ignored.
Error causes
3.2.5.14
DataMissing
UnexpectedDataValue
UnknownSubscriber
RegisterCC-Entry
DN98628099
Issue 10-1 en
141 (264)
.
ss-Code
It indicates either ccbs-A or ccbs-B service. In error cases an
IllegalSS-Operation error is sent.
ccbs-Data
.
ccbs-Feature
The received parameters ccbs-index, b-subscriberNumber
and basicServiceGroup are forwarded to the CCBS
application.
.
translatedB-Number
This parameter is forwarded to the CCBS application.
.
serviceIndicator
.
callInfo
.
networkSignallInfo
ccbs-Feature
Result parameters
This parameter contains the parameters ccbs-index, bsubscriberNumber and basicServiceGroup from the CCBS
application.
Error causes
.
SystemFailure
It is never sent.
DataMissing
Sent if the translatedB-Number is not received in the invocation.
UnexpectedDataValue
Sent if an erroneous value is found in the invocation parameters.
142 (264)
CallBarred
DN98628099
Issue 10-1 en
It is never sent.
.
IllegalSS-Operation
It is sent if the ss-Code in the invocation is not ccbs.
SS-ErrorStatus
subscriber.
SS-Incompatibility
It is never sent.
ShortTermDenial
It is never sent.
LongTermDenial
It is never sent.
It is never sent.
3.2.5.15
EraseCC-Entry
.
ss-Code
It indicates either ccbs-A or ccbs-B service. In error cases an
IllegalSS-Operation error is sent.
ccbs-index
This parameter indicates the CCBS entry to be erased. In error
cases an UnexpectedDataValue error is sent.
DN98628099
Issue 10-1 en
143 (264)
Result parameters
.
ss-Code
ss-Status
Error causes
.
SystemFailure
It is never sent.
DataMissing
It is never sent..
UnexpectedDataValue
CallBarred
It is never sent.
IllegalSS-Operation
It is sent if the ss-Code in the invocation is not ccbs.
SS-ErrorStatus
subscriber.
3.2.6
Short messages operations
3.2.6.1
SendRoutingInfoForSM
This operation is implemented in version 1, 2 and 3 dialogues.
As an optional feature, if the SendRoutingInfoForSM is sent to a ringing
group or to a member of a ringing group, HLR checks the type of the
SMSC based on the sender's SCCP level address to see if the operation is
allowed for the recipient. In error cases the error
TeleserviceNotProvisioned is returned.
144 (264)
DN98628099
Issue 10-1 en
As an optional feature (Feature 626: GSM Supplementary Services Phase

2 Extensions; SMS forwarding), the HLR (of the subscriber B for MT-SMS)
may forward the request to another HLR (of the C-subscriber for MT-SMS),
using the MSC's subsystem number in the SCCP level Calling Party
Address. The response from the other HLR is handled in this HLR, before
responding to the GMSC. Between the two HLRs, only version 3 is
supported: the initiating HLR always uses version 3, and the responding
HLR understands the proprietary extension parameters only in version 3.
In a Mobile Number Portability environment (Feature 1080: SRF in HLR)
may have special values (depending on configuration). Depending on the
SRF check for the subscriber, the SendRoutingInfoForSM may be
forwarded towards another HLR (SCCP level re-routing).
.
msisdn
error cases an UnknownSubscriber error is sent.
Subscriber Identity (MSISDN) in the HLR), the MSISDN may be
modified before checking the HLR database.
If the MSISDN is the number of a sequential/parallel alerting group,
the operation is performed for the primary member of the group.
If the MSISDN is the number of an intelligent alerting group, the
operation is acknowledged with a Proxy SCP address or is routed to
the primary device with hunting type of SMS/MMS.
If the MSISDN is a number of a ringing group member, and if the
direct SMS with member number is denied in the ringing group data,
the operation is not allowed. In that case the error CallBarred
(OperatorDeterminedBarring) is sent.
When the request is forwarded to another HLR, the MSISDN
contains the C-number from the subscriber data in the HLR
database.
sm-RP-PRI
If TRUE, the routing info is returned even if the Mobile Station Not
Reachable flag is set in the subscriber data.
DN98628099
Issue 10-1 en
serviceCentreAddress
145 (264)
This parameter is stored in the Message Waiting Data list when smRP-PRI is FALSE and the list is not empty.
.
extensionContainer
This parameter may contain the SriForSMArgExt in version 3. The
.
cfuSMSCounter
If this parameter is not received, the operation is handled as a
normal request from the GMSC (SMS forwarding may occur, if
the forwarding is registered for the subscriber). This parameter
is set with value '0' is when the operation is forwarded to
another HLR.
If this parameter is received with value '0', no more forwardings
are allowed.
If this parameter is received with a value greater than '0',
further forwardings are allowed, and the received value is
decreased by one before putting the value into the outgoing
message.
.
cfusmcfo
If this flag is received, the SM forwarding is not done.
.
memberInterrogate
If this flag is received, the HLR does not check the Deny Direct
SM parameter, but allows the MT SM sending directly to a
ringing group member.
teleservice
gprsSupportIndicator
This parameter indicates that the SMS-GMSC supports receiving
two routing numbers from the HLR.
sm-RP-MTI
sm-RP-SMEA
Result parameters
.
imsi
This parameter is from the subscriber data or from the ringing group
146 (264)
DN98628099
Issue 10-1 en
As an optional feature, if the subscriber has Prepaid MT-SM service,

and if the HLR configuration shows that the MT-SM needs to be
routed to a special SMS-Relay node, the imsi parameter contains
the subscriber's primary MSISDN digits.
.
locationInfoWithLMSI
.
networkNode-Number
The MSC address or SGSN address from subscriber data. If
both addresses are known, the preferred one is selected
based on HLR configuration.
As an optional feature, if the subscriber has Prepaid MT-SM
service, and if the HLR configuration shows that the MT-SM
needs to be routed to a special SMS-Relay node, the address
of the SMS-Relay node from HLR configuration is returned.
.
lmsi
.
gprsNodeIndicator
This parameter is set if the SGSN number is sent as the
networkNode-Number.
.
additional-Number
MscNumber is sent in additional-Number parameter if
gprsSupportIndicator was received in the invocation, and both
'network access mode' and 'MT-SM via SGSN suppressed' in
HLR database allow access to both SGSN and MSC address,
and the SGSN address is sent in the networkNode-Number
parameter.
Sgsn-Number is sent in additional-Number parameter if
gprsSupportIndicator was received in the invocation, and both
'network access mode' and 'MT-SM via SGSN suppressed' in
HLR database allow access to both SGSN and MSC address,
and the MSC address is sent in the networkNode-Number
parameter.
mwd-Set
This parameter is used in version 1 dialogues (in higher versions the
information is sent using the InformSC operation). TRUE in priority
short messages if the same service centre address is already stored
in the Message Waiting Data List for the subscriber.
DN98628099
Issue 10-1 en
147 (264)
Error causes
.
SystemFailure
It is never sent.
DataMissing
It is never sent.
UnexpectedDataValue
It is never sent.
UnknownSubscriber
It is sent if the MSISDN in the invocation is not known in the HLR.
It is sent if the subscriber does not have Mobile Terminated short
message service, or if the subscriber or the ringing group is not
allowed to receive a short message from the originating SMSC type.
AbsentSubscriber
It is sent if the subscriber data in the HLR does not contain location
information, or if there are service centre addresses in the
subscriber's message waiting list and no priority has been indicated
in the sm-RP-PRI parameter.
If this error cause is received from the HLR-C to which the
SendRoutingInfoForSM was forwarded, the message waiting data is
set for the subscriber in this HLR.
CallBarred
It is sent if the subscriber has activated incoming call barring
supplementary service, or if incoming calls are barred by the
operator, or if the subscriber or the ringing group status is
deactivated.
3.2.6.2
SetMessageWaitingData
This operation is implemented in version 1 dialogues only. In version 2 and
version 3, ReportSM-DeliveryStatus operation is used.
148 (264)
DN98628099
Issue 10-1 en
When HLR receives SetMessageWaitingData (which is a version 1

operation) and stores the SC-address to subscriber's MWD list, the version
of the SMS-GMSC is stored (in this case version 1). This information is
used later, and version 1 will be used for AlertSC operation.
.
msisdn
As an option (Feature 1048: Extended Handling for Subscriber
Identity (MSISDN) in the HLR), the received MSISDN may be
modified before the HLR database enquiry.
This parameter is stored in the Message Waiting Data list.
Result parameters
The result contains no parameters.
Error causes
.
UnknownSubscriber
MessageWaitingListFull
It is never sent.
UnexpectedDataValue
It is sent if an erroneous value is found in invocation parameters.
3.2.6.3
ReportSM-DeliveryStatus
This operation is implemented in version 2 and 3 dialogues. In version 1,
SetMessageWaitingData operation is used.
DN98628099
Issue 10-1 en
149 (264)

2 Extensions), the HLR may forward the request to another HLR, using the
MSC's subsystem number in the SCCP level Calling Party Address. The
response from the other HLR is handled in this HLR before responding to
the GMSC. Between the two HLRs, only version 3 is supported: the
initiating HLR always uses version 3, and the responding HLR
understands the proprietary extension parameters only in version 3.
When HLR receives a ReportSM-DeliveryStatus (version 2 or 3) and
stores the SC-address to subscriber's MWD list, the version of the SMSGMSC is stored (in this case, version 2). This information is used later, and
version 2 will be used for AlertSC operation.
As an optional feature, if the ReportSM-DeliveryStatus is sent to a ringing
group, HLR checks the type of the SMSC based on the sender's SCCP
level address.
.
msisdn
When the request is forwarded to another HLR, the MSISDN
contains the C-number from the subscriber data in the HLR
database.
This parameter is stored in the Message Waiting Data list if the smDeliveryOutcome parameter indicates an unsuccessful outcome.
150 (264)
sm-DeliveryOutcome
.
memoryCapacityExceeded
The MCE flag is set in the subscriber data.
.
absentSubscriber
The MNR flag is set in the subscriber data.
.
SuccessfulTransfer
The AlertSC operation is started, and the MCE and MNR flags
are cleared.
DN98628099
Issue 10-1 en
absentSubscriberDiagnosticSM
This parameter indicates the reason why the subscriber is absent.
MNRReason information is updated in the subscriber data.
extensionContainer
This parameter may contain the ReportSMDelStatArgExt in version
3. The extensionId is {0 34 19}.
.
cfuSMSCounter
If this parameter is not received, the operation is handled as a
normal request from the GMSC (SMS forwarding may occur, if
the forwarding is registered for the subscriber). This parameter
is set with value '0' is when the operation is forwarded to
another HLR.
If this parameter is received with value '0', no more forwardings
are allowed.
If this parameter is received with a value greater than '0',
further forwardings are allowed, and the received value is
decreased by one before putting the value into the outgoing
message.
.
cfusmcfo
If this flag is received, the SM forwarding is not done.
This parameter indicates that SMS-GMSC supports handling of two
delivery outcomes. If not received, the HLR interprets the received
data as GPRS data if SMS routing to SGSN is the preferred setting
in the HLR (that is, if the SGSN address was returned as the only
address in the SendRoutingInfoForSM result).
deliveryOutcomeIndicator
This parameter indicates that the SM-DeliveryOutcome is for GPRS.
additionalSM-DeliveryOutcome
This is the information for GPRS.
additionalAbsentSubscriberDiagnosticSM
This is the information for GPRS.
Result parameters
.
storedMSISDN
This parameter contains the MSISDN which is stored to the
Message Waiting Data list.
DN98628099
Issue 10-1 en
151 (264)
In case of unsuccessful delivery (sm-DeliveryOutcome was

memoryCapacityExceeded or absentSubscriber), this parameter is
always returned, even if the storedMSISDN is the same as the
msisdn in the invocation.
Error causes
.
DataMissing
It is sent if the sm-DeliveryOutcome parameter is not received in the
invocation.
UnexpectedDataValue
UnknownSubscriber
MessageWaitingListFull
It is never sent.
3.2.6.4
AlertServiceCentreWithoutResult
This operation is implemented in version 1 dialogues only.
In GSM TS 09.02, Mobile Application Part (MAP) Specification, GSM
Phase 1, the name of this operation was AlertServiceCentre.
It is invoked by the HLR and confirmed by the MSC.
.
SCCP address: GT, Service Centre address from the MWD list
.
msisdn
This parameter is from subscriber (or sequential/parallel/intelligent
alerting group) data in the HLR database.
This parameter is from subscriber's Message Waiting Data list.
152 (264)
DN98628099
Issue 10-1 en
3.2.6.5
AlertServiceCentre
This operation is implemented in version 2 dialogues only. In version 1,
AlertServiceCentreWithoutResult operation is used.
Invoked by the HLR and confirmed by the MSC.
.
If the procedure fails, it is repeated once (after a delay of 15

seconds).
SCCP address: GT, Service Centre address from the MWD list
.
msisdn
This parameter is from subscriber (or sequential/parallel/intelligent
alerting group) data in the HLR database.
This parameter is from subscriber's Message Waiting Data list.
Result parameters
Error causes
3.2.6.6
SystemFailure
DataMissing
UnexpectedDataValue
InformServiceCentre
This operation is implemented in version 2 and 3 dialogues only. No
It is invoked by the HLR towards the MSC.
DN98628099
Issue 10-1 en
153 (264)

2 Extensions), the HLR (HLR-B) may receive this operation from another
HLR (HLR-C), together with the SendRoutingInfoForSM response. The
operation from the other HLR is forwarded to the GMSC. The HLR-C
always includes this operation with the result to the routing information
enquiry for a forwarded MT-SM.
.
Operation timer: not applicable (this operation invocation is sent in a

dialogue closing message).
Re-attempts in case procedure fails: not applicable (this operation is

sent in a dialogue closing message).
SCCP address: Calling party address in SendRoutingInfoForSM

result.
.
storedMSISDN
This parameter is the MSISDN which is stored to the Message
Waiting Data list if it is different than the one received in the
invocation.
Phase 2 Extensions), if the cfuSMSCounter parameter in the
SendRoutingInfoForSM indicates that the request was forwarded by
another HLR, the InformSC operation is returned and the
subscriber's MSISDN is returned in the storedMSISDN parameter.
mw-Status
Sc-AddressNotIncluded is set when the routing information is
returned because of a priority Short Message, and if there are
service centre addresses in the Message Waiting Data list, but not
the SC-address which was received in the SendRoutingInfoForSM
invocation.
The flags mnrf-Set, mcef-Set and mnrg-Set are set based on the
information in subscriber data.
3.2.6.7
NoteMSPresent
higher, ReadyForSM operation is used.
It is invoked by the VLR and handled by the HLR.
154 (264)
DN98628099
Issue 10-1 en
If the subscriber has a Service Centre Address in the mwd-list, AlertSC is

sent.
.
imsi
intelligent alerting group) data in the HLR database.
If the subscriber has service centre addresses in the Message
Waiting Data list, AlertSC operation is sent towards the SMS-GMSC.
3.2.6.8
ReadyForSM
This operation is implemented in version 2 and 3 dialogues. In version 1,
NoteMSPresent operation is used.
.
imsi
If the subscriber has service centre addresses in the Message
Waiting Data list, AlertSC operation is sent towards the SMS-GMSC.
DN98628099
Issue 10-1 en
alertReason
.
ms-Present
If this indication is received, the Mobile Station Not Reachable
flag is reset in the subscriber data.
.
memoryAvailable
If this indication is received, the Memory Capacity Exceeded
flag is reset in the subscriber data.
alertReasonIndicator
155 (264)
This parameter indicates that the alertReason is for GPRS.

Result parameters
Error causes
.
DataMissing
It is never sent.
UnexpectedDataValue
It is never sent.
UnknownSubscriber
It is sent if the IMSI in the invocation is not known in the HLR.
3.2.7
Location service operations
3.2.7.1
SendRoutingInfoForLCS
This operation is implemented in version 3 dialogues.
It is invoked by the GMLC and confirmed by the HLR.
.
mlcNumber
this parameter is ignored.
targetMS
This parameter contains one of the following:
.
imsi
database. An UnknownSubscriber error is sent in error cases
(if the IMSI is not known in the HLR, or is the IMSI of a
sequential/parallel/intelligent alerting group).
156 (264)
DN98628099
Issue 10-1 en
As an optional feature, the IMSI may be either the Database

IMSI or an Alias IMSI (according to the HLR configuration).
msisdn
database. An UnknownSubscriber error is sent in error cases.
If the MSISDN is the number of a sequential/parallel/intelligent
alerting group, the operation is performed for the member,
which is the primary device for Location Services.
extensionContainer
Result parameters
.
targetMS
.
imsi
This parameter is sent if an MSISDN was received in the
invocation.
As an optional feature, an Alias IMSI is sent instead of the
IMSI which is in the database, if the Alias IMSI is marked as
active in the subscriber data in the HLR database.
.
msisdn
This parameter is sent if an IMSI was received in the
invocation.
lcsLocationInfo
.
networkNode-Number
Contains the MSC address if available. If MSC address is not
available, it contains the SGSN address (if available). If the
networkNode-Number contains the SGSN address,
gprsNodeIndicator parameter is also sent.
.
lmsi
.
gprsNodeIndicator
This parameter is sent if the networkNode-Number contains
the SGSN address.
.
additional-Number
This parameter contains the MSC address or the SGSN
address if both addresses are to be returned. The other
address is included in the networkNode-Number parameter.
extensionContainer
It is never sent.
DN98628099
Issue 10-1 en
157 (264)
v-gmlc-Address
It is never sent.
h-gmlc-Address
It is never sent.
ppr-Address
The Privacy Profile Register number from the subscriber data in the
HLR database. The ppr-Address is an IPv4 or an IPv6 address.
This parameter is sent if the HLR data allows the sending of the PPR
number to the GMLC.
Error causes
.
SystemFailure
DataMissing
It is never sent.
UnexpectedDataValue
It is sent if the Location Services feature is not activated in the HLR.
UnknownSubscriber
It is sent if the subscriber is not known in the HLR, or if the IMSI of a
sequential/parallel/intelligent alerting group was received in the
invocation.
AbsentSubscriber
It is sent if there is no location information (MSC address or SGSN
address) in the subscriber data.
3.3
UnauthorizedRequestingNetwork
Formal definition of data types

The ASN.1 descriptions for the main part of the implementation are based
on 3GPP TS 29.002, Mobile Application Part (MAP) Specification, Release
5. Some newer Release 6 and Release 7 parameters are also supported.
158 (264)
DN98628099
Issue 10-1 en
When MAP dialogue version 1 is used, the syntax of MAP messages and
parameters comply with GSM 09.02, Mobile Application Part (MAP)
Specification, GSM phase 1.
When MAP dialogue version 2 is used, the syntax of MAP messages and
parameters comply with GSM 09.02, Mobile Application Part (MAP)
Specification, GSM phase 2.
3.3.1
Dialogue information
These data types are used by MAP, but are transferred on the TCAP level
in the Dialogue Portion of TCAP messages.
DEFINITIONS IMPLICIT TAGS ::=

BEGIN
map-DialogueAS OBJECT IDENTIFIER ::=
{ ccitt (0) identified-organization (4) etsi (0) mobileDomainId (0)
gsm-NetworkId (1) as-Id (1) map-DialoguePDU (1) version1 (1) }
MAP-DialoguePDU ::= CHOICE {
map-open
[0] MAP-OpenInfo,
map-accept
[1] MAP-AcceptInfo,
map-close
[2] MAP-CloseInfo,
map-refuse
[3] MAP-RefuseInfo,
map-userAbort
[4] MAP-UabortInfo,
map-providerAbort
[5] MAP-PabortInfo }
MAP-OpenInfo ::= SEQUENCE {
[0] AddressString
originatingReference
[1] AddressString
...}
OPTIONAL,
OPTIONAL,
MAP-AcceptInfo ::= SEQUENCE {

...}
MAP-CloseInfo ::= SEQUENCE {
...}
MAP-RefuseInfo ::= SEQUENCE {
reason
Reason,
...}
Reason ::= ENUMERATED {
noReasonGiven
(0),
invalidDestinationReference (1),
invalidOriginatingReference (2) }
MAP-UabortInfo ::= SEQUENCE {
map-UserAbortChoice
MAP-UserAbortChoice,
...}
MAP-UserAbortChoice ::= CHOICE {
DN98628099
Issue 10-1 en
159 (264)
userSpecificReason
userResourceLimitation
resourceUnavailable
applicationProcedureCancel
[0]
[1]
[2]
[3]
NULL,
NULL,
ResourceUnavailReason,
ProcedureCancelReason }
ResourceUnavailReason ::= ENUMERATED {

shortTermResourceLimitation (0),
longTermResourceLimitation
(1) }
ProcedureCancelReason ::= ENUMERATED {
handoverCancellation
(0),
radioChannelRelease
(1),
networkPathRelease
(2),
callRelease
(3),
associatedProcedureFailure
(4),
tandemDialogueRelease
(5),
remoteOperationsFailure
(6) }
MAP-PabortInfo ::= SEQUENCE {
map-ProviderAbortReason
...}
MAP-ProviderAbortReason,
MAP-ProviderAbortReason ::= ENUMERATED {

abnormalDialogue
(0),
invalidPDU
(1) }
END
3.3.2
Mobile Service data types
MAP-MS-DataTypes
BEGIN
-- location registration types
-- version 1:
UpdateLocationArg ::= SEQUENCE {
imsi
IMSI,
locationInfo
LocationInfo,
vlr-Number
ISDN-AddressString,
lmsi
[10] LMSI OPTIONAL }
-- version 2:
imsi
IMSI,
locationInfo
LocationInfo,
vlr-Number
ISDN-AddressString,
lmsi
[10] LMSI OPTIONAL,
...}
-- version 3:
160 (264)
DN98628099
Issue 10-1 en
imsi
locationInfo
vlr-Number
lmsi
extensionContainer
...,
vlr-Capability
cs-LCS-NotSupportedByUE
v-gmlc-Address
add-Info
IMSI,
LocationInfo,
ISDN-AddressString,
[10] LMSI
OPTIONAL,
ExtensionContainer OPTIONAL,
[6]
[11]
[12]
[2]
[13]
VLR-Capability
OPTIONAL,
NULL
OPTIONAL,
NULL OPTIONAL,
GSN-Address OPTIONAL,
ADD-Info OPTIONAL }
VLR-Capability ::= SEQUENCE {

[0] SupportedCamelPhases OPTIONAL,
extensionContainer
ExtensionContainer
OPTIONAL,
solsaSupportIndicator [2] NULL OPTIONAL,
istSupportIndicator
[1] IST-SupportIndicator OPTIONAL,
superChargerSupportedInServingNetworkEntity [3] SuperChargerInfo OPTIONAL,
longFTN-Supported
[4] NULL
OPTIONAL,
supportedLCS-CapabilitySets [5] SupportedLCS-CapabilitySets OPTIONAL,
offeredCamel4CSIs
[6] OfferedCamel4CSIs OPTIONAL,
...}
SuperChargerInfo ::= CHOICE {
sendSubscriberData
[0] NULL,
subscriberDataStored [1] AgeIndicator }
AgeIndicator ::= OCTET STRING (SIZE (1..6))
-- The internal structure of this parameter is implementation specific.
IST-SupportIndicator ::= ENUMERATED {
basicISTSupported
(0),
istCommandSupported (1),
...}
-- exception handling:
-- reception of values > 1 shall be mapped to 'istCommandSupported'
SupportedLCS-CapabilitySets ::= BIT STRING {
lcsCapabilitySet1 (0),
lcsCapabilitySet2 (1),
lcsCapabilitySet3 (2) } (SIZE (2..16))
-- Core network signalling capability set1 indicates LCS Release98 or
-- Release99 version.
-- Core network signalling capability set2 indicates LCS Release4.
-- Core network signalling capability set3 indicates LCS Release5 or later
-- version.
-- A node shall mark in the BIT STRING all LCS capability sets it supports.
-- If no bit is set then the sending node does not support LCS.
-- If the parameter is not sent by an VLR then the VLR may support at most
-- capability set1.
-- If the parameter is not sent by an SGSN then no support for LCS is assumed.
-- An SGSN is not allowed to indicate support of capability set1.
-- Other bits than listed above shall be discarded.
-- version 1:
UpdateLocationRes ::= ISDN-AddressString
DN98628099
Issue 10-1 en
161 (264)
-- hlr-Number
-- hlr-Number must not be used in version greater
-- versions 2 and 3:
UpdateLocationRes ::= ExtensibleUpdateLocationRes
-- extensibleUpdateLocationRes
-- extensibleUpdateLocationRes must not be used in version 1
-- version 2:
ExtensibleUpdateLocationRes ::= SEQUENCE {
hlr-Number
ISDN-AddressString,
ulResExt
[PRIVATE 0] UlResExt
-- proprietary }
-- version 3:
ExtensibleUpdateLocationRes
hlr-Number
extensionContainer
...,
add-Capability
::= SEQUENCE {
ISDN-AddressString,
ExtensionContainer
OPTIONAL
OPTIONAL,
NULL OPTIONAL }
ADD-Info ::= SEQUENCE {

imeisv
[0] IMEI,
skipSubscriberDataUpdate [1] NULL OPTIONAL,
... }
CancelLocationArg ::= CHOICE {
imsi
IMSI,
imsi-WithLMSI
IMSI-WithLMSI}
-- version 3:
CancelLocationArg ::= [3] SEQUENCE {
identity
Identity,
cancellationType
CancellationType
extensionContainer
ExtensionContainer
...}
OPTIONAL,
OPTIONAL,
-- version 1 and version 2 CancelLocationRes is empty;

-- version 3:
CancelLocationRes ::= SEQUENCE {
...}
Identity ::= CHOICE {
imsi
imsi-WithLMSI
IMSI,
IMSI-WithLMSI }
CancellationType ::= ENUMERATED {

updateProcedure
(0),
subscriptionWithdraw
(1),
...}
-- version 2:
PurgeMS-Arg ::= SEQUENCE {
imsi
IMSI,
vlr-Number ISDN-AddressString,
162 (264)
DN98628099
Issue 10-1 en
...}
-- version 3:
PurgeMS-Arg ::= [3] SEQUENCE {
imsi
IMSI,
vlr-Number
[0] ISDN-AddressString
OPTIONAL,
sgsn-Number
OPTIONAL,
extensionContainer ExtensionContainer OPTIONAL,
...}
-- version 2 PurgeMS-Res is empty;
-- version 3:
PurgeMS-Res ::= SEQUENCE {
freezeTMSI
[0] NULL
OPTIONAL,
freezeP-TMSI
[1] NULL
OPTIONAL,
...}
IMSI-WithLMSI ::= SEQUENCE {
imsi
IMSI,
lmsi
LMSI,
ext
[PRIVATE 0 ] CanLocArgExt
-- proprietary
...}
OPTIONAL,
-- version 2:
SendIdentificationArg ::= TMSI
-- version 3:
SendIdentificationArg ::= SEQUENCE {
tmsi
TMSI,
numberOfRequestedVectors NumberOfRequestedVectors OPTIONAL,
-- if segmentation is used, numberOfRequestedVectors shall be present in
-- the first segment and shall not be present in subsequent segments.
-- If received in a subsequent segment it shall be discarded.
NULL
OPTIONAL,
-- if segmentation is prohibited the previous VLR shall not send the result
-- within a TC-CONTINUE message.
extensionContainer
...}
-- version 2:
SendIdentificationRes ::= SEQUENCE {
imsi
IMSI,
authenticationSetList
AuthenticationSetList
...}
OPTIONAL,
-- version 3:
SendIdentificationRes ::= [3] SEQUENCE {
imsi
IMSI OPTIONAL,
-- IMSI must be present if SendIdentificationRes is not segmented.
-- If the TC-Continue segmentation option is taken the IMSI must be
-- present in one segmented transmission of SendIdentificationRes.
authenticationSetList
AuthenticationSetList OPTIONAL,
currentSecurityContext [2] CurrentSecurityContext OPTIONAL,
extensionContainer
[3] ExtensionContainer OPTIONAL,
DN98628099
Issue 10-1 en
163 (264)
...}
-- version 2:
AuthenticationSetList ::= SEQUENCE SIZE (1..5) OF
AuthenticationTriplet
-- version 3:
AuthenticationSetList ::= CHOICE {
tripletList
[0] TripletList,
quintupletList [1] QuintupletList }
TripletList ::= SEQUENCE SIZE (1..5) OF
AuthenticationTriplet
QuintupletList ::= SEQUENCE SIZE (1..5) OF
AuthenticationQuintuplet
AuthenticationTriplet ::= SEQUENCE {
rand
RAND,
sres
SRES,
kc
Kc,
...}
AuthenticationQuintuplet ::= SEQUENCE {
rand
RAND,
xres
XRES,
ck
CK,
ik
IK,
autn
AUTN,
...}
CurrentSecurityContext ::= CHOICE {
gsm-SecurityContextData
[0] GSM-SecurityContextData,
umts-SecurityContextData [1] UMTS-SecurityContextData }
GSM-SecurityContextData ::= SEQUENCE {
kc
Kc,
cksn
Cksn,
... }
UMTS-SecurityContextData ::= SEQUENCE {
ck
CK,
ik
IK,
ksi
KSI,
... }
RAND ::= OCTET STRING (SIZE (16))
SRES ::= OCTET STRING (SIZE (4))
Kc ::= OCTET STRING (SIZE (8))
XRES ::= OCTET STRING (SIZE (4..16))
CK ::= OCTET STRING (SIZE (16))
164 (264)
DN98628099
Issue 10-1 en
IK ::= OCTET STRING (SIZE (16))

AUTN ::= OCTET STRING (SIZE (16))
AUTS ::= OCTET STRING (SIZE (14))
Cksn ::= OCTET STRING (SIZE (1))
-- The internal structure is defined in 3G TS 24.008
KSI ::= OCTET STRING (SIZE (1))
-- The internal structure is defined in 3G TS 24.008
AuthenticationFailureReportArg ::= SEQUENCE {
imsi
IMSI,
failureCause
FailureCause,
re-attempt
BOOLEAN
OPTIONAL,
accessType
AccessType
OPTIONAL,
rand
RAND
OPTIONAL,
vlr-Number
[0] ISDN-AddressString OPTIONAL,
sgsn-Number
...}
AuthenticationFailureReportRes ::= SEQUENCE {
...}
AccessType ::= ENUMERATED {
call
(0),
emergencyCall
(1),
locationUpdating
(2),
supplementaryService
(3),
shortMessage
(4),
...}
-- received values greater than 4 shall be ignored.
FailureCause ::= ENUMERATED {
wrongUserResponse
(0),
wrongNetworkSignature
(1)}
-- gprs location registration types
UpdateGprsLocationArg ::= SEQUENCE {
imsi
IMSI,
sgsn-Number
ISDN-AddressString,
sgsn-Address
GSN-Address,
extensionContainer
sgsn-Capability
[0] SGSN-Capability OPTIONAL,
informPreviousNetworkEntity [1] NULL OPTIONAL,
ps-LCS-NotSupportedByUE
[2] NULL OPTIONAL,
v-gmlc-Address
[3] GSN-Address OPTIONAL,
add-Info
[4] ADD-Info OPTIONAL,
...}
SGSN-Capability ::= SEQUENCE {
DN98628099
Issue 10-1 en
165 (264)
NULL
OPTIONAL,
extensionContainer
superChargerSupportedInServingNetworkEntity [2] SuperChargerInfo OPTIONAL,
gprsEnhancementsSupportIndicator
[3] NULL OPTIONAL,
[5] SupportedLCS-CapabilitySets OPTIONAL,
offeredCamel4CSIs
... }
GSN-Address ::= OCTET STRING (SIZE (5..17))
UpdateGprsLocationRes ::= SEQUENCE {
hlr-Number
ISDN-AddressString,
add-Capability
NULL OPTIONAL,
...}
-- handover types
ForwardAccessSignalling-Arg ::= ExternalSignalInfo
-- bss-APDU
-- version 3:
ForwardAccessSignalling-Arg ::= [3]
an-APDU
integrityProtectionInfo
[0]
encryptionInfo
[1]
keyStatus
[2]
allowedGSM-Algorithms
[4]
allowedUMTS-Algorithms
[5]
radioResourceInformation
[6]
extensionContainer
[3]
...,
radioResourceList
[7]
bssmap-ServiceHandover
[9]
ranap-ServiceHandover
[8]
bssmap-ServiceHandoverList [10]
currentlyUsedCodec
[11]
iuSupportedCodecsList
[12]
rab-ConfigurationIndicator [13]
iuSelectedCodec
[14]
SEQUENCE {
AccessNetworkSignalInfo,
IntegrityProtectionInformation OPTIONAL,
EncryptionInformation OPTIONAL,
KeyStatus OPTIONAL,
AllowedGSM-Algorithms OPTIONAL,
AllowedUMTS-Algorithms OPTIONAL,
RadioResourceInformation OPTIONAL,
RadioResourceList OPTIONAL,
BSSMAP-ServiceHandover OPTIONAL,
RANAP-ServiceHandover OPTIONAL,
BSSMAP-ServiceHandoverList OPTIONAL,
Codec OPTIONAL,
SupportedCodecsList OPTIONAL,
NULL OPTIONAL,
Codec OPTIONAL}
KeyStatus ::= ENUMERATED {

old (0),
new (1),
...}
-- reception of values in range 2-31 shall be treated as old
-- reception of values greater than 31 shall be treated as new
-- version 2:
PrepareHO-Arg ::= SEQUENCE {
targetCellId
GlobalCellId
ho-NumberNotRequired
NULL
bss-APDU
ExternalSignalInfo
166 (264)
OPTIONAL,
OPTIONAL,
OPTIONAL,
DN98628099
Issue 10-1 en
ext
...}
[PRIVATE 0] HO-Ext
-- version 3:
PrepareHO-Arg ::= [3] SEQUENCE
targetCellId
ho-NumberNotRequired
targetRNCId
an-APDU
multipleBearerRequested
imsi
integrityProtectionInfo
encryptionInfo
allowedGSM-Algorithms
allowedUMTS-Algorithms
radioResourceList
extensionContainer
...,
rab-Id
bssmap-ServiceHandover
ranap-ServiceHandover
bssmap-ServiceHandoverList
asciCallReference
geran-classmark
iuCurrentlyUsedCodec
iuSupportedCodecsList
rab-ConfigurationIndicator
uesbi-Iu
OPTIONAL,
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[9]
[10]
[11]
[8]
GlobalCellId OPTIONAL,
NULL
OPTIONAL,
RNCId OPTIONAL,
AccessNetworkSignalInfo OPTIONAL,
NULL OPTIONAL,
IMSI OPTIONAL,
IntegrityProtectionInformation OPTIONAL,
EncryptionInformation OPTIONAL,
RadioResourceInformation OPTIONAL,
AllowedGSM-Algorithms OPTIONAL,
AllowedUMTS-Algorithms OPTIONAL,
RadioResourceList OPTIONAL,
[12]
[13]
[14]
[15]
[20]
[16]
[17]
[18]
[19]
[21]
RAB-Id OPTIONAL,
BSSMAP-ServiceHandover OPTIONAL,
RANAP-ServiceHandover OPTIONAL,
BSSMAP-ServiceHandoverList OPTIONAL,
ASCI-CallReference OPTIONAL,
GERAN-Classmark OPTIONAL,
Codec OPTIONAL,
SupportedCodecsList OPTIONAL,
NULL OPTIONAL,
UESBI-Iu OPTIONAL }
UESBI-Iu ::= SEQUENCE {

uesbi-IuA [0] UESBI-IuA OPTIONAL,
uesbi-IuB [1] UESBI-IuB OPTIONAL,
... }
UESBI-IuA ::= BIT STRING (SIZE (1..128))
-- See 3GPP TS 25.413
UESBI-IuB ::= BIT STRING (SIZE (1..128))
-- See 3GPP TS 25.413
GERAN-Classmark ::= OCTET STRING (SIZE (2..87))
-- Octets are coded according the GERAN Classmark information element in 3GPP TS
48.008
SupportedCodecsList ::= SEQUENCE {
utranCodecList
[0] CodecList OPTIONAL,
geranCodecList
[1] CodecList OPTIONAL,
extensionContainer [2] ExtensionContainer OPTIONAL,
... }
CodecList ::= SEQUENCE {
codec1
[1] Codec,
codec2
[2] Codec OPTIONAL,
codec3
[3] Codec OPTIONAL,
codec4
[4] Codec OPTIONAL,
DN98628099
Issue 10-1 en
167 (264)
codec5
codec6
codec7
codec8
extensionContainer
... }
-- Codecs are sent
[5]
[6]
[7]
[8]
[9]
Codec OPTIONAL,
Codec OPTIONAL,
Codec OPTIONAL,
Codec OPTIONAL,
in priority order where codec1 has highest priority
Codec ::= OCTET STRING (SIZE (1..4))

-- The internal structure is defined as follows:
-- octet 1 Coded as Codec Identification code in 3GPP TS 26.103
-- octets 2,3,4 Parameters for the Codec as defined in 3GPP TS
-- 26.103, if available, length depending on the codec
BSSMAP-ServiceHandoverList ::= SEQUENCE SIZE (2.. maxNumOfServiceHandovers) OF
BSSMAP-ServiceHandoverInfo
BSSMAP-ServiceHandoverInfo ::= SEQUENCE {
bssmap-ServiceHandover BSSMAP-ServiceHandover,
rab-Id
RAB-Id,
-- RAB Identity is needed to relate the service handovers with the radio
-- access bearers.
...}
maxNumOfServiceHandovers
INTEGER ::= 7
BSSMAP-ServiceHandover ::= OCTET STRING (SIZE (1))

-- Octets are coded according the Service Handover information element in
-- GSM 48.008.
RANAP-ServiceHandover ::= OCTET STRING (SIZE (1))
-- Octet contains a complete Service-Handover data type
-- as defined in 3GPP TS 25.413, encoded according to the encoding scheme
-- mandated by 3GPP TS 25.413
-- Padding bits are included in the least significant bits.
AllowedGSM-Algorithms ::= OCTET STRING (SIZE (1))
-- internal structure is coded as Algorithm identifier octet from
-- Permitted Algorithms defined in GSM 48.008
-- A node shall mark all GSM algorithms that are allowed in MSC-B
AllowedUMTS-Algorithms ::= SEQUENCE {
integrityProtectionAlgorithms [0]
PermittedIntegrityProtectionAlgorithms OPTIONAL,
encryptionAlgorithms
[1] PermittedEncryptionAlgorithms OPTIONAL,
extensionContainer
[2] ExtensionContainer
OPTIONAL,
...}
PermittedIntegrityProtectionAlgorithms ::=
OCTET STRING (SIZE (2..maxPermittedIntegrityProtectionAlgorithmsLength))
-- Octets are coded according to Permitted Integrity Protection Algorithms
-- in Integrity
-- Protection Information information element in 3G TS 25.413
maxPermittedIntegrityProtectionAlgorithmsLength INTEGER ::= 9
168 (264)
DN98628099
Issue 10-1 en
PermittedEncryptionAlgorithms ::=
OCTET STRING (SIZE (2..maxPermittedEncryptionAlgorithmsLength))
-- Octets are coded according to Permitted Encryption Algorithms in Encryption
-- Information information element in 3G TS 25.413
maxPermittedEncryptionAlgorithmsLength INTEGER ::= 9
RadioResourceList ::= SEQUENCE SIZE (2.. maxNumOfRadioResources) OF
RadioResource
maxNumOfRadioResources INTEGER ::= 7
RadioResource ::= SEQUENCE {
RadioResourceInformation,
rab-Id
RAB-Id,
-- RAB Identity is needed to relate the radio resources with the radio
-- access bearers.
...}
PerformHO-Arg ::= SEQUENCE {
targetCellId
servingCellId
channelType
classmarkInfo
handoverPriority
[11]
kc
[12]
GlobalCellId,
GlobalCellId,
ChannelType,
ClassmarkInfo,
HandoverPriority
Kc
OPTIONAL,
OPTIONAL}
ChannelType ::= OCTET STRING (SIZE (1..10))

-- concatenation of
-- speech data indicator
-- channel rate
-- speech encoding algorithm/ data rate
-- and transparency indicator
-- as defined in GSM 48.008
ClassmarkInfo ::= OCTET STRING (SIZE (1..2))
-- classmark information element type 1 or 2 contents as defined
-- in GSM 48.008
HandoverPriority ::= OCTET STRING (SIZE (1))
-- The internal structure is defined in GSM 48.008.
PerformHO-Res ::= SEQUENCE {
handoverNumber
ISDN-AddressString,
accessSignalInfo
ExternalSignalInfo}
-- version 2:
PrepareHO-Res ::= SEQUENCE {
handoverNumber ISDN-AddressString
bss-APDU
ExternalSignalInfo
ext [PRIVATE 0] HO-Ext
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
-- version 3:
PrepareHO-Res ::= [3] SEQUENCE {
handoverNumber
DN98628099
Issue 10-1 en
169 (264)
relocationNumberList
[1]
an-APDU
[2]
multicallBearerInfo
[3]
multipleBearerNotSupported
selectedUMTS-Algorithms
[5]
chosenRadioResourceInformation
extensionContainer
[4]
...,
iuSelectedCodec
[7]
iuAvailableCodecsList
[8]
RelocationNumberList OPTIONAL,
AccessNetworkSignalInfo OPTIONAL,
MulticallBearerInfo OPTIONAL,
NULL
OPTIONAL,
SelectedUMTS-Algorithms OPTIONAL,
[6] ChosenRadioResourceInformation OPTIONAL,
Codec OPTIONAL,
CodecList OPTIONAL}
PerformSubsequentHO-Arg ::= SEQUENCE {

targetCellId
GlobalCellId,
servingCellId
GlobalCellId,
targetMSC-Number
ISDN-AddressString,
classmarkInfo
[10]
ClassmarkInfo
OPTIONAL}
-- version 2:
PrepareSubsequentHO-Arg
targetCellId
targetMSC-Number
bss-APDU
...}
::= SEQUENCE {
GlobalCellId,
ISDN-AddressString,
ExternalSignalInfo,
-- version 3:
PrepareSubsequentHO-Arg ::= [3] SEQUENCE {
targetCellId
[0] GlobalCellId,
targetMSC-Number
[1] ISDN-AddressString,
targetRNCId
[2] RNCId OPTIONAL,
an-APDU
[3] AccessNetworkSignalInfo OPTIONAL,
selectedRab-Id
[4] RAB-Id OPTIONAL,
extensionContainer
...,
geran-classmark
[6] GERAN-Classmark OPTIONAL,
rab-ConfigurationIndicator [7] NULL OPTIONAL}
-- version 2:
PrepareSubsequentHO-Res ::= ExternalSignalInfo
-- bss-APDU
-- version 3:
PrepareSubsequentHO-Res ::= [3] SEQUENCE {
an-APDU
...}
ProcessAccessSignalling-Arg ::= ExternalSignalInfo
-- bss-APDU
-- version 3:
ProcessAccessSignalling-Arg ::= [3] SEQUENCE {
an-APDU
selectedUMTS-Algorithms [1] SelectedUMTS-Algorithms OPTIONAL,
selectedGSM-Algorithm
[2] SelectedGSM-Algorithm OPTIONAL,
chosenRadioResourceInformation [3] ChosenRadioResourceInformation OPTIONAL,
170 (264)
DN98628099
Issue 10-1 en
selectedRab-Id
extensionContainer
...,
iUSelectedCodec
iuAvailableCodecsList
[4] RAB-Id OPTIONAL,

OPTIONAL,
[5] Codec OPTIONAL,

[6] CodecList OPTIONAL}
-- version 1 SendEndSignal-Arg is empty;

-- version 2:
SendEndSignal-Arg ::= ExternalSignalInfo
-- bss-APDU
-- version 3:
SendEndSignal-Arg ::= [3] SEQUENCE {
an-APDU
...}
-- version 1 and version 2 SendEndSignal-Res is empty;
-- version 3:
SendEndSignal-Res ::= SEQUENCE {
...}
RNCId ::= OCTET STRING (SIZE (7))
-- octet 1 bits 4321
Mobile Country Code 1st digit
-bits 8765
Mobile Country Code 2nd digit
Mobile Country Code 3rd digit
-bits 8765
Mobile Network Code 3rd digit
-or filler (1111) for 2 digit MNCs
Mobile Network Code 1st digit
-bits 8765
Mobile Network Code 2nd digit
-- octets 4 and 5
Location Area Code according to 3G TS 24.008
-- octets 6 and 7
RNC Id value according to 3G TS 25.413
RelocationNumberList ::= SEQUENCE SIZE (1..maxNumOfRelocationNumber) OF
RelocationNumber
MulticallBearerInfo ::= INTEGER (1..maxNumOfRelocationNumber)
RelocationNumber ::= SEQUENCE {
handoverNumber ISDN-AddressString,
rab-Id
RAB-Id,
-- RAB Identity is needed to relate the calls with the radio access
-- bearers.
...}
RAB-Id ::= INTEGER (1..maxNrOfRABs)
maxNrOfRABs INTEGER ::= 255
maxNumOfRelocationNumber
INTEGER ::= 7
RadioResourceInformation ::= OCTET STRING (SIZE (3..13))

-- Octets are coded according the Channel Type information element in
-- 3G TS 48.008
DN98628099
Issue 10-1 en
171 (264)
IntegrityProtectionInformation ::= OCTET STRING (SIZE (18..maxNumOfIntegrityInfo))

-- Octets are coded according to 3G TS 25.413
maxNumOfIntegrityInfo INTEGER ::= 100
EncryptionInformation ::= OCTET STRING (SIZE (18..maxNumOfEncryptionInfo))
-- Octets are coded according to 3G TS 25.413
maxNumOfEncryptionInfo INTEGER ::= 100
SelectedGSM-Algorithm ::= OCTET STRING (SIZE (1))
-- internal structure is coded as Algorithm identifier octet from
-- Chosen Encryption
-- Algorithm defined in GSM 48.008
-- A node shall mark only the selected GSM algorithm
SelectedUMTS-Algorithms ::= SEQUENCE
integrityProtectionAlgorithm [0]
encryptionAlgorithm
[1]
extensionContainer
[2]
...}
{
ChosenIntegrityProtectionAlgorithm OPTIONAL,
ChosenEncryptionAlgorithm OPTIONAL,
ExtensionContainer
OPTIONAL,
ChosenIntegrityProtectionAlgorithm ::= OCTET STRING (SIZE (1))

-- Octet is coded according to 3G TS 25.413
ChosenEncryptionAlgorithm ::= OCTET STRING (SIZE (1))
-- Octet is coded according to 3G TS 25.413
ChosenRadioResourceInformation ::= SEQUENCE {
chosenChannelInfo
[0] ChosenChannelInfo OPTIONAL,
chosenSpeechVersion
[1] ChosenSpeechVersion OPTIONAL,
...}
ChosenChannelInfo ::= OCTET STRING (SIZE (1))
-- Octets are coded according the Chosen Channel information element in
-- GSM 48.008
ChosenSpeechVersion ::= OCTET STRING (SIZE (1))
-- Octets are coded according the Speech Version (chosen) information element
-- in GSM 48.008
-- authentication management types
-- version 2:
SendAuthenticationInfoArg ::= IMSI
-- version 3:
SendAuthenticationInfoArg ::= SEQUENCE {
imsi
[0] IMSI,
numberOfRequestedVectors
NumberOfRequestedVectors,
NULL
OPTIONAL,
-- if segmentation is prohibited the HLR shall not send the result within
-- a TC-CONTINUE message.
immediateResponsePreferred [1] NULL OPTIONAL,
-- if present, the HLR may send an immediate response with the available
172 (264)
DN98628099
Issue 10-1 en
-- authentication vectors
re-synchronisationInfo
Re-synchronisationInfo OPTIONAL,
extensionContainer
requestingNodeType
[3] RequestingNodeType OPTIONAL,
...}
RequestingNodeType ::= ENUMERATED {
vlr
(0),
sgsn
(1),
...}
-- received values in the range 2-15 shall be treated as "vlr"
-- received values greater than 15 shall be treated as "sgsn"
NumberOfRequestedVectors ::= INTEGER (1..5)
Re-synchronisationInfo ::= SEQUENCE {
rand
RAND,
auts
AUTS,
...}
-- version 2:
SendAuthenticationInfoRes ::= AuthenticationSetList
-- version 3:
SendAuthenticationInfoRes ::= [3] SEQUENCE {
authenticationSetList AuthenticationSetList OPTIONAL,
extensionContainer
...}
Ki ::= OCTET STRING (SIZE (16))
-- security management types
CheckIMEI-Arg ::= CHOICE {
imei
IMEI,
imei-withIMSI
IMEI-withIMSI }
IMEI-withIMSI ::= SEQUENCE {
imei
IMEI,
imsi
IMSIChoice OPTIONAL,
... }
IMSIChoice
imsi
imsiOS
::= CHOICE {
[PRIVATE 1] IMSI,
[0]
IMSI }
CheckIMEI-Res ::= EquipmentStatus

EquipmentStatus
whiteListed
blackListed
greyListed
::= ENUMERATED {
(0),
(1),
(2)}
-- subscriber management types
DN98628099
Issue 10-1 en
173 (264)
SendParametersArg ::= SEQUENCE {

subscriberId
SubscriberId,
requestParameterList
RequestParameterList}
SentParametersRes ::= SentParameterList
RequestParameterList ::= SEQUENCE SIZE (1..2) OF
RequestParameter
RequestParameter ::= ENUMERATED
requestIMSI
requestAuthenticationSet
requestSubscriberData
requestKi
{
(0),
(1),
(2),
(4)}
SentParameterList ::= SEQUENCE SIZE (1..maxNumOfSentParameter) OF

SentParameter
SentParameter ::= CHOICE {
imsi
[0]
authenticationSet
[1]
subscriberData
[2]
ki
[4]
IMSI,
AuthenticationSet,
SubscriberData,
Ki}
maxNumOfSentParameter INTEGER ::= 6

-- This NamedValue corresponds to the maximum number of
-- authentication set which may be returned by a HLR plus 1
-- version 1:
InsertSubscriberDataArg ::= SEQUENCE {
imsi
[0] IMSI
COMPONENTS OF
SubscriberData }
-- version 2:
InsertSubscriberDataArg ::= SEQUENCE
imsi
[0]
COMPONENTS OF
isdArgExt
[PRIVATE 0]
-- proprietary
ansiIsdArgExt
[PRIVATE 30]
-- proprietary
...}
OPTIONAL,
{
IMSI
SubscriberData,
IsdArgExt
OPTIONAL,
ANSIIsdArgExt
OPTIONAL,
OPTIONAL,
-- version 3:
InsertSubscriberDataArg ::= SEQUENCE {
imsi
[0] IMSI
OPTIONAL,
COMPONENTS OF
SubscriberData,
extensionContainer
OPTIONAL,
naea-PreferredCI
[15] NAEA-PreferredCI
OPTIONAL,
gprsSubscriptionData
[16] GPRSSubscriptionData
OPTIONAL,
roamingRestrictedInSgsnDueToUnsupportedFeature [23] NULL OPTIONAL,
networkAccessMode
[24] NetworkAccessMode
OPTIONAL,
-- If the Network Access Mode parameter is sent, it shall be present
-- only in the first sequence if the segmentation is used
lsaInformation
[25] LSAInformation
OPTIONAL,
lmu-Indicator
[21] NULL
OPTIONAL,
174 (264)
DN98628099
Issue 10-1 en
lcsInformation
[22] LCSInformation
OPTIONAL,
istAlertTimer
[26] IST-AlertTimerValue
OPTIONAL,
superChargerSupportedInHLR
[27] AgeIndicator
OPTIONAL,
mc-SS-Info
[28] MC-SS-Info
OPTIONAL,
cs-AllocationRetentionPriority [29] CS-AllocationRetentionPriority OPTIONAL,
sgsn-CAMEL-SubscriptionInfo [17] SGSN-CAMEL-SubscriptionInfo OPTIONAL,
chargingCharacteristics
[18] ChargingCharacteristics OPTIONAL,
accessRestrictionData
[19] AccessRestrictionData
OPTIONAL,
ansiIsdArgExt
[PRIVATE 30] ANSIIsdArgExt
OPTIONAL,
-- proprietary
...}
LCSInformation ::= SEQUENCE {
gmlc-List
[0]
lcs-PrivacyExceptionList [1]
molr-List
[2]
...}
GMLC-List
OPTIONAL,
LCS-PrivacyExceptionList OPTIONAL,
MOLR-List
OPTIONAL,
IST-AlertTimerValue ::= INTEGER (15..255)

MC-SS-Info ::= SEQUENCE {
ss-Code
ss-Status
nbrSB
nbrUser
extensionContainer
...}
[0]
[1]
[2]
[3]
[4]
SS-Code,
Ext-SS-Status,
MaxMC-Bearers,
MC-Bearers,
CS-AllocationRetentionPriority ::= OCTET STRING (SIZE (1))

-- This data type encodes each priority level defined in TS 23.107 as the
-- binary value of the priority level.
GMLC-List ::= SEQUENCE SIZE (1..maxNumOfGMLC) OF
ISDN-AddressString
maxNumOfGMLC
INTEGER ::= 5
NetworkAccessMode ::= ENUMERATED {

bothMSCAndSGSN
(0),
onlyMSC
(1),
onlySGSN
(2),
...}
-- if unknown values are received in NetworkAccessMode
-- they shall be discarded
GPRSDataList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF
PDP-Context
maxNumOfPDP-Contexts
INTEGER ::= 50
PDP-Context ::= SEQUENCE {

pdp-ContextId
pdp-Type
pdp-Address
qos-Subscribed
vplmnAddressAllowed
DN98628099
Issue 10-1 en
[16]
[17]
[18]
[19]
ContextId,
PDP-Type,
PDP-Address
QoS-Subscribed,
NULL
OPTIONAL,
OPTIONAL,
175 (264)
apn
[20] APN,
extensionContainer
ext-QoS-Subscribed
[0] Ext-QoS-Subscribed
pdp-ChargingCharacteristics
[1] ChargingCharacteristics
ext2-QoS-Subscribed
[2] Ext2-QoS-Subscribed
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
APN ::= OCTET STRING (SIZE (2..63))

PDP-Type ::= OCTET STRING (SIZE (2))
PDP-Address ::= OCTET STRING (SIZE (1..16))
QoS-Subscribed ::= OCTET STRING (SIZE (3))
-- Octets are coded according to TS GSM 04.08.
Ext-QoS-Subscribed ::= OCTET STRING (SIZE (1..9))
-- OCTET 1:
-- Allocation/Retention Priority (This octet encodes each priority level
-- defined in 23.107 as the binary value of the priority level, declaration
-- in 29.060) Octets 2-9 are coded according to 3G TS 24.008
-- Quality of Service Octets 6-13.
Ext2-QoS-Subscribed ::= OCTET STRING (SIZE (1..3))
-- Octets 1-3 are coded according to 3GPP TS 24.008 [35] Quality of Service Octets
14-16.
-- If Quality of Service information is structured with 14 octet length, then
-- Octet 1 is coded according to 3GPP TS 24.008 [35] Quality of Service Octet 14.
ContextId ::= INTEGER (1..maxNumOfPDP-Contexts)
ChargingCharacteristics ::= OCTET STRING (SIZE (2))
-- Octets are coded according to TS 3GPP 32.015.
GPRSSubscriptionData::= SEQUENCE {
NULL
OPTIONAL,
-- If segmentation is used, completeDataListIncluded may only be
-- present in the first segment
gprsDataList
[1] GPRSDataList,
extensionContainer
...}
SGSN-CAMEL-SubscriptionInfo ::=
gprs-CSI
mo-sms-CSI
extensionContainer
...,
mt-sms-CSI
mg-csi
GPRS-CSI ::= SEQUENCE {
gprs-CamelTDPDataList
extensionContainer
notificationToCSE
176 (264)
[0]
[1]
[2]
[3]
SEQUENCE {
[0] GPRS-CSI OPTIONAL,
[1] SMS-CSI OPTIONAL,
[3] SMS-CSI OPTIONAL,
[4] MT-smsCAMELTDP-CriteriaList OPTIONAL,
[5] MG-CSI OPTIONAL}
GPRS-CamelTDPDataList
CamelCapabilityHandling
ExtensionContainer
NULL
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
DN98628099
Issue 10-1 en
csiActive
[4] NULL
OPTIONAL,
...}
-- notificationToCSE and csi-Active shall not be present when GPRS-CSI is
-- sent to SGSN.
-- They may only be included in ATSI/ATM ack/NSDC message.
-- GPRS-CamelTDPData and camelCapabilityHandling shall be present in
-- the GPRS-CSI sequence.
-- If GPRS-CSI is segmented, gprs-CamelTDPDataList and
-- camelCapabilityHandling shall be
-- present in the first segment
GPRS-CamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
GPRS-CamelTDPData
-- GPRS-CamelTDPDataList shall not contain more than one instance of
-- GPRS-CamelTDPData containing the same value for gprs-TriggerDetectionPoint.
GPRS-CamelTDPData ::= SEQUENCE
gprs-TriggerDetectionPoint
serviceKey
gsmSCF-Address
defaultSessionHandling
...}
{
[0]
[1]
[2]
[3]
GPRS-TriggerDetectionPoint,
ServiceKey,
ISDN-AddressString,
DefaultGPRS-Handling,
DefaultGPRS-Handling ::= ENUMERATED {

continueTransaction
(0),
releaseTransaction
(1),
...}
-- reception of values in range 2-31 shall be treated as
-- "continueTransaction"
-- reception of values greater than 31 shall be treated as
-- "releaseTransaction"
GPRS-TriggerDetectionPoint ::= ENUMERATED {
attach
(1),
attachChangeOfPosition
(2),
pdp-ContextEstablishment
(11),
pdp-ContextEstablishmentAcknowledgement (12),
pdp-ContextChangeOfPosition
(14),
...}
-- For GPRS-CamelTDPData sequences containing this parameter with any
-- other value than the ones listed the receiver shall ignore the whole
-- GPRS-CamelTDPDatasequence.
LSAOnlyAccessIndicator::= ENUMERATED {
accessOutsideLSAsAllowed
(0),
accessOutsideLSAsRestricted (1)}
LSADataList ::= SEQUENCE SIZE (1..maxNumOfLSAs) OF
LSAData
maxNumOfLSAs INTEGER ::= 20
LSAData ::= SEQUENCE {
lsaIdentity
DN98628099
Issue 10-1 en
[0] LSAIdentity,
177 (264)
lsaAttributes
lsaActiveModeIndicator
...}
[1] LSAAttributes,
[2] NULL OPTIONAL,
LSAInformation::= SEQUENCE {
NULL OPTIONAL,
-- If segmentation is used, completeDataListIncluded may only be present in
-- the first segment.
lsaOnlyAccessIndicator
[1] LSAOnlyAccessIndicator OPTIONAL,
lsaDataList
[2] LSADataList OPTIONAL,
...}
LSAIdentity ::= OCTET STRING (SIZE (3))
-- Octets are coded according to TS GSM 03.03
LSAAttributes ::= OCTET STRING (SIZE (1))
-- Octets are coded according to TS GSM 48.008
SubscriberData ::= SEQUENCE {
msisdn
category
[2] Category
OPTIONAL,
subscriberStatus
[3] SubscriberStatus
OPTIONAL,
bearerServiceList
[4] BearerServiceList
OPTIONAL,
-- The exception handling for reception of unsupported / not allocated
-- bearerServiceCodes is defined in section 6.8.1
teleserviceList
[6] TeleserviceList
OPTIONAL,
-- The exception handling for reception of unsupported / not allocated
-- teleserviceCodes is defined in section 6.8.1
provisionedSS
[7] Ext-SS-InfoList
OPTIONAL,
-- the following are only in version 2 and version 3:
odb-Data
[8] ODB-Data
OPTIONAL,
[9] NULL
OPTIONAL,
[10] ZoneCodeList
OPTIONAL,
-- the following are only in version 3:
vbsSubscriptionData
[11] VBSDataList
OPTIONAL,
vgcsSubscriptionData
[12] VGCSDataList
OPTIONAL,
vlrCamelSubscriptionInfo
[13] VlrCamelSubscriptionInfo
OPTIONAL }
SubscriberStatus ::= ENUMERATED {
serviceGranted
(0),
operatorDeterminedBarring
(1)}
Ext-SS-InfoList ::= SEQUENCE SIZE (1..maxNumOfSS) OF
Ext-SS-Info
Ext-SS-Info ::= CHOICE {
forwardingInfo
[0]
callBarringInfo
[1]
cug-Info
[2]
ss-Data
[3]
emlpp-Info
[4]
cosInfo [PRIVATE 10]
proprietary
}
Ext-ForwInfo,
Ext-CallBarInfo,
CUG-Info,
EExt-SS-Data,
EMLPP-Info,
CosInfo
Ext-ForwInfo ::= SEQUENCE {
178 (264)
DN98628099
Issue 10-1 en
ss-Code
SS-Code,
Ext-ForwFeatureList,
extensionContainer
...}
Ext-ForwFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF
Ext-ForwFeature
Ext-ForwFeature ::= SEQUENCE {
basicService
ss-Status
[4]
forwardedToNumber
[5]
[8]
forwardingOptions
[6]
[7]
extensionContainer
[9]
[10]
...}
Ext-BasicServiceCode
Ext-SS-Status,
ISDN-AddressString
ISDN-SubaddressString
Ext-ForwOptions
Ext-NoRepCondTime
ExtensionContainer
FTN-AddressString
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
Ext-ForwOptions ::= OCTET STRING (SIZE (1..5))

-- OCTET 1:
-- bit 8: notification to forwarding party
-0 no notification
-1 notification
-- bit 7: 0 (unused)
-- bit 6: notification to calling party
-0 no notification
-1 notification
-- bits 43: forwarding reason
-00 ms not reachable
-01 ms busy
-10 no reply
-11 unconditional
-- bits 21: 00 (unused)
-- OCTETS 2-5: reserved for future use. They shall be discarded if
-- received and not understood.
Ext-NoRepCondTime ::= INTEGER (1..100)
-- Values in the range 1-4 are reserved for future use
-- If received:
-values 1-4 shall be mapped on to value 5
Ext-CallBarInfo ::= SEQUENCE {
ss-Code
SS-Code,
callBarringFeatureList Ext-CallBarFeatureList,
...}
Ext-CallBarFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF
Ext-CallBarringFeature
Ext-CallBarringFeature ::= SEQUENCE {
basicService
ss-Status
[4] Ext-SS-Status,
...}
DN98628099
Issue 10-1 en
OPTIONAL,
179 (264)
maxNumOfExt-BasicServiceGroups
INTEGER ::= 32
Ext-SS-Data ::= SEQUENCE {

ss-Code
ss-Status
[4]
sS-DataExtension
[PRIVATE 0]
-- proprietary
sS-DataEmoInExt
[PRIVATE 1]
-- proprietary
extensionContainer
[5]
...}
SS-Code,
Ext-SS-Status,
SS-SubscriptionOption
OPTIONAL,
Ext-BasicServiceGroupList OPTIONAL,
SS-DataExtension
OPTIONAL,
SS-DataEmoInExt
OPTIONAL,
ExtensionContainer
OPTIONAL,
LCS-PrivacyExceptionList ::= SEQUENCE SIZE (1..maxNumOfPrivacyClass) OF

LCS-PrivacyClass
maxNumOfPrivacyClass
INTEGER ::= 4
LCS-PrivacyClass ::= SEQUENCE {

ss-Code
SS-Code,
ss-Status
Ext-SS-Status,
[0] NotificationToMSUser OPTIONAL,
-- notificationToMSUser may be sent only for SS-codes callrelated and
-- callunrelated.
-- If not received for SS-codes callrelated and callunrelated,
-- the default values according to 3G TS 23.271 shall be assumed.
externalClientList
[1] ExternalClientList OPTIONAL,
-- externalClientList may be sent only for SS-code callunrelated to a
-- visited node that does not support LCS Release 4 or later versions.
-- externalClientList may be sent only for SS-codes callunrelated and
-- callrelated to a visited node that supports LCS Release 4 or later
-- versions.
plmnClientList
[2] PLMNClientList OPTIONAL,
-- plmnClientList is expected only for SS-code plmn operator
extensionContainer
ext-externalClientList [4] Ext-ExternalClientList OPTIONAL,
-- Ext-externalClientList is present when the visited node supports
-- LCS Release 4 or later versions, user specifies more than 5 clients and
-- White Book SCCP is used.
serviceTypeList
[5] ServiceTypeList OPTIONAL
-- serviceTypeList may be sent only for SS-code servicetype and if the
-- visited node supports LCS Release 5 or later versions.
-- if segmentation is used, the complete LCS-PrivacyClass shall be sent
-- in one segment
...}
ServiceTypeList ::= SEQUENCE SIZE (1..maxNumOfServiceType) OF
ServiceType
maxNumOfServiceType
INTEGER ::= 32
ServiceType ::= SEQUENCE {

serviceTypeIdentity
LCSServiceTypeID,
gmlc-Restriction
[0] GMLC-Restriction OPTIONAL,
notificationToMSUser [1] NotificationToMSUser OPTIONAL,
180 (264)
DN98628099
Issue 10-1 en
-- If notificationToMSUser is not received, the default value according to

-- 3G TS 23.271 shall be assumed.
extensionContainer
... }
ExternalClientList ::= SEQUENCE SIZE (0..maxNumOfExternalClient) OF
ExternalClient
maxNumOfExternalClient
INTEGER ::= 5
PLMNClientList ::= SEQUENCE SIZE (1..maxNumOfPLMNClient) OF

LCSClientInternalID
maxNumOfPLMNClient
INTEGER ::= 5
Ext-ExternalClientList ::= SEQUENCE SIZE (1..maxNumOfExt-ExternalClient) OF

ExternalClient
maxNumOfExt-ExternalClient INTEGER ::= 35
ExternalClient ::= SEQUENCE {
clientIdentity
LCSClientExternalID,
gmlc-Restriction
[0] GMLC-Restriction OPTIONAL,
notificationToMSUser [1] NotificationToMSUser OPTIONAL,
extensionContainer
...}
GMLC-Restriction ::= ENUMERATED {
gmlc-List
(0),
home-Country
(1),
...}
-- At reception of any other value than the ones listed the receiver shall
-- ignore GMLC-Restriction.
NotificationToMSUser ::= ENUMERATED {
notifyLocationAllowed
(0),
notifyAndVerify-LocationAllowedIfNoResponse
(1),
notifyAndVerify-LocationNotAllowedIfNoResponse (2),
...
locationNotAllowed (3)}
-- At reception of any other value than the ones listed the receiver shall
-- ignore NotificationToMSUser.
MOLR-List ::= SEQUENCE SIZE (1..maxNumOfMOLR-Class) OF
MOLR-Class
maxNumOfMOLR-Class
INTEGER ::= 3
MOLR-Class ::= SEQUENCE {

ss-Code
SS-Code,
ss-Status
Ext-SS-Status,
extensionContainer
...}
DN98628099
Issue 10-1 en
OPTIONAL,
181 (264)
ZoneCode ::= OCTET STRING (SIZE (2))

-- internal structure is defined in GSM 03.03
maxNumOfZoneCodes
INTEGER ::= 10
ZoneCodeList ::= SEQUENCE SIZE (1..maxNumOfZoneCodes) OF

ZoneCode
-- version 1 InsertSubscriberDataRes
-- version 2:
InsertSubscriberDataRes ::= SEQUENCE
teleserviceList
[1]
bearerServiceList
[2]
ss-List
[3]
odb-GeneralData
[4]
regionalSubscriptionResponse [5]
...}
-- version 3:
InsertSubscriberDataRes ::= SEQUENCE
teleserviceList
[1]
bearerServiceList
[2]
ss-List
[3]
odb-GeneralData
[4]
regionalSubscriptionResponse [5]
[6]
extensionContainer
[7]
offeredCamel4CSIs
[8]
...}
is empty;
{
TeleserviceList
OPTIONAL,
BearerServiceList
OPTIONAL,
SS-List
OPTIONAL,
ODB-GeneralData
OPTIONAL,
RegionalSubscriptionResponse OPTIONAL,
{
TeleserviceList
OPTIONAL,
BearerServiceList
OPTIONAL,
SS-List
OPTIONAL,
ODB-GeneralData
OPTIONAL,
RegionalSubscriptionResponse OPTIONAL,
SupportedCamelPhases
OPTIONAL,
ExtensionContainer
OPTIONAL,
OfferedCamel4CSIs
OPTIONAL,
SupportedCamelPhases ::= BIT STRING {

phase1 (0),
phase2 (1),
phase3 (2),
phase4 (3) } (SIZE (1..16))
-- A node shall mark in the BIT STRING all CAMEL Phases it supports.
-- Other values than listed above shall be discarded.
OfferedCAMEL4CSIs ::= BIT STRING {
o-csi
(0),
d-csi
(1),
vt-csi
(2),
t-csi
(3),
mt-sms-csi
(4),
mg-csi
(5),
psi-enhancements (6) } (SIZE (7..16))
-- A node supporting Camel ph4 shall mark in the BIT STRING all Camel4 CSIs
-- it offers.
OfferedCamel4Functionalities ::= BIT STRING {
ica-new-party
(0),
split-leg
(1),
move-leg
(2),
disconnect-leg
(3),
entity-released
(4),
182 (264)
DN98628099
Issue 10-1 en
dfc-with-argument
(5),
play-tone
(6),
dtmf-mid-call
(7),
charging-indicator
(8),
alerting-dp
(9),
location-at-alerting
(10),
change-of-position-dp
(11),
or-interactions
(12),
warning-tone-enhancements (13),
cf-enhancements
(14) } (SIZE (15..32))
-- A node supporting Camel phase 4 shall mark in the BIT STRING all Camel4
-- functionalities it offers.
SMS-CSI ::= SEQUENCE {
sms-CAMEL-TDP-DataList
[0] SMS-CAMEL-TDP-DataList OPTIONAL,
camelCapabilityHandling [1] CamelCapabilityHandling OPTIONAL,
extensionContainer
notificationToCSE
[3] NULL OPTIONAL,
csiActive
[4] NULL OPTIONAL,
...}
-- notificationToCSE and csiActive shall not be present when SMS-CSI is sent
-- to VLR/SGSN.
-- SMS-CAMEL-TDP-Data and camelCapabilityHandling shall be present in
-- the SMS-CSI sequence.
-- If SMS-CSI is segmented, sms-CAMEL-TDP-DataList and
-- camelCapabilityHandling shall be present in the first segment
SMS-CAMEL-TDP-DataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
SMS-CAMEL-TDP-Data
-- SMS-CAMEL-TDP-DataList shall not contain more than one instance of
-- SMS-CAMEL-TDP-Data containing the same value for sms-TriggerDetectionPoint.
SMS-CAMEL-TDP-Data ::= SEQUENCE {
sms-TriggerDetectionPoint [0]
serviceKey
[1]
gsmSCF-Address
[2]
defaultSMS-Handling
[3]
extensionContainer
[4]
...}
SMS-TriggerDetectionPoint,
ServiceKey,
ISDN-AddressString,
DefaultSMS-Handling,
SMS-TriggerDetectionPoint ::= ENUMERATED {

sms-CollectedInfo (1),
...}
-- For SMS-CAMEL-TDP-Data sequences containing this parameter with any
-- SMS-CAMEL-TDP-Data sequence.
DefaultSMS-Handling ::= ENUMERATED {
continueTransaction (0) ,
releaseTransaction
(1) ,
...}
-- reception of values in range 2-31 shall be treated as
DN98628099
Issue 10-1 en
183 (264)
-- "continueTransaction"
-- reception of values greater than 31 shall be treated as
-- "releaseTransaction"
M-CSI ::= SEQUENCE {
mobilityTriggers
MobilityTriggers,
serviceKey
ServiceKey,
gsmSCF-Address
notificationToCSE
[2] NULL OPTIONAL,
csiActive
[3] NULL OPTIONAL,
...}
-- notificationToCSE and csiActive shall not be present when M-CSI is
-- sent to VLR.
MobilityTriggers
MM-Code
::= SEQUENCE SIZE (1..maxNumOfMobilityTriggers) OF
maxNumOfMobilityTriggers INTEGER ::= 10

RegionalSubscriptionResponse ::= ENUMERATED {
networkNode-AreaRestricted
(0),
tooManyZoneCodes
(1),
zoneCodesConflict
(2),
regionalSubscNotSupported
(3)}
-- version 1:
DeleteSubscriberDataArg ::= SEQUENCE {
imsi
[0] IMSI,
basicServiceList
[1] BasicServiceList
ss-List
[2] SS-List
-- version 2:
imsi
[0] IMSI,
basicServiceList
ss-List
[2] SS-List
[4] NULL
[5] ZoneCode
dsdArgExt
[PRIVATE 0] DsdArgExt
-- proprietary
...}
OPTIONAL,
OPTIONAL }
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
-- version 3:
imsi
[0] IMSI,
basicServiceList
OPTIONAL,
ss-List
[2] SS-List
OPTIONAL,
[4] NULL
OPTIONAL,
[5] ZoneCode
OPTIONAL,
vbsGroupIndication
[7] NULL
OPTIONAL,
vgcsGroupIndication
[8] NULL
OPTIONAL,
camelSubscriptionInfoWithdraw
[9] NULL
OPTIONAL,
extensionContainer
OPTIONAL,
gprsSubscriptionDataWithdraw
[10] GPRSSubscriptionDataWithdraw OPTIONAL,
184 (264)
DN98628099
Issue 10-1 en
roamingRestrictedInSgsnDueToUnsupportedFeature [11] NULL

lsaInformationWithdraw
[12] LSAInformationWithdraw
hplmn-GMLC-List-Withdraw
[13] NULL
istInformationWithdraw
[14] NULL
specificCSI-Withdraw
[15] SpecificCSI-Withdraw
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
-- version 1 DeleteSubscriberDataRes is empty;

-- version 2 and version 3:
DeleteSubscriberDataRes ::= SEQUENCE {
regionalSubscriptionResponse [0] RegionalSubscriptionResponse
...}
OPTIONAL,
SpecificCSI-Withdraw ::= BIT STRING {

o-csi
(0),
ss-csi
(1),
tif-csi
(2),
d-csi
(3),
vt-csi
(4),
mo-sms-csi (5),
m-csi
(6),
gprs-csi
(7),
t-csi
(8),
mt-sms-csi (9),
mg-csi
(10)} (SIZE (8..32))
-- bits 11 to 31 shall be ignored if received
-- Bit 8 is only applicable for the NoteSubscriberDataModified operation.
GPRSSubscriptionDataWithdraw ::= CHOICE {
allGPRSData
NULL,
contextIdList
ContextIdList}
ContextIdList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF
ContextId
LSAInformationWithdraw ::= CHOICE {
allLSAData
NULL,
lsaIdentityList LSAIdentityList }
LSAIdentityList::= SEQUENCE SIZE (1..maxNumOfLSAs) OF
LSAIdentity
VlrCamelSubscriptionInfo ::= SEQUENCE

o-CSI
[0]
extensionContainer
[1]
ss-CSI
[2]
[4]
tif-CSI
[3]
m-CSI
[5]
mo-sms-CSI
[6]
vt-CSI
[7]
t-BCSM-CAMEL-TDP-CriteriaList [8]
d-CSI
[9]
mt-sms-CSI
[10]
DN98628099
Issue 10-1 en
{
O-CSI OPTIONAL,
SS-CSI OPTIONAL,
O-BcsmCamelTDPCriteriaList OPTIONAL,
NULL OPTIONAL,
M-CSI OPTIONAL,
SMS-CSI OPTIONAL,
T-CSI OPTIONAL,
T-BCSM-CAMEL-TDP-CriteriaList OPTIONAL,
D-CSI OPTIONAL,
SMS-CSI OPTIONAL,
185 (264)
...}
[11] MT-smsCAMELTDP-CriteriaList OPTIONAL,
MT-smsCAMELTDP-CriteriaList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF

MT-smsCAMELTDP-Criteria
MT-smsCAMELTDP-Criteria ::= SEQUENCE {
sms-TriggerDetectionPoint SMS-TriggerDetectionPoint,
mt-sms-TPDU-Type
[0] MT-SMS-TPDU-Type OPTIONAL,
...}
MT-SMS-TPDU-Type ::= ENUMERATED {
sMS-DELIVER
(0),
sMS-SUBMIT-REPORT
(1),
sMS-STATUS-REPORT
(2),
...}
-- For MT-SMS-TPDU-Type sequences containing this parameter with any
-- other value than the ones listed above the receiver shall ignore
-- the whole MT-SMS-TPDU-Type sequence.
-- In the CAMEL phase 4, SMS-SUBMIT-REPORT shall not be used.
D-CSI ::= SEQUENCE {
dp-AnalysedInfoCriteriaList [0] DP-AnalysedInfoCriteriaList OPTIONAL,
[1] CamelCapabilityHandling OPTIONAL,
extensionContainer
notificationToCSE
[3] NULL OPTIONAL,
csi-Active
[4] NULL OPTIONAL,
...}
-- Csi-active shall not be present when D-CSI is sent to VLR/GMSC.
-- It may only be included in ATSI/ATM ack/NSDC message.
-- DP-AnalysedInfoCriteria and camelCapabilityHandling shall be present in
-- the D-CSI sequence.
-- If D-CSI is segmented, dp-AnalysedInfoCriteriaList and
-- camelCapabilityHandling shall be present in the first segment
DP-AnalysedInfoCriteriaList ::=
SEQUENCE SIZE (1..maxNumOfDP-AnalysedInfoCriteria) OF DP-AnalysedInfoCriterium
maxNumOfDP-AnalysedInfoCriteria INTEGER ::= 10
DP-AnalysedInfoCriterium
dialledNumber
serviceKey
gsmSCF-Address
defaultCallHandling
extensionContainer
...}
::= SEQUENCE {
ISDN-AddressString,
ServiceKey,
ISDN-AddressString,
DefaultCallHandling,
SS-CSI ::= SEQUENCE {

ss-CamelData
SS-CamelData,
extensionContainer
notificationToCSE [0] NULL OPTIONAL,
csi-Active
[1] NULL OPTIONAL,
...}
-- notificationToCSE and csi-Active shall not be present when SS-CSI
186 (264)
DN98628099
Issue 10-1 en
-- is sent to VLR.
SS-CamelData ::= SEQUENCE {
ss-EventList
SS-EventList,
gsmSCF-Address ISDN-AddressString,
...}
SS-EventList ::= SEQUENCE SIZE (1..maxNumOfCamelSSEvents) OF
SS-Code
-- Actions for the following SS-Code values are defined in CAMEL Phase 2:
-- ect
SS-Code ::= '00110001'B
-- multiPTY
SS-Code ::= '01010001'B
-- cd
SS-Code ::= '00100100'B
-- all other SS codes shall be ignored
maxNumOfCamelSSEvents INTEGER ::= 10
O-CSI ::= SEQUENCE {
o-BcsmCamelTDPDataList
O-BcsmCamelTDPDataList,
extensionContainer
notificationToCSE
[1] NULL OPTIONAL,
csiActive
[2] NULL OPTIONAL,
...}
-- notificationtoCSE and csiActive shall not be present when O-CSI is sent
-- to VLR/GMSC.
-- They may only be included in ATSI/ATM ack/NCSD message.
O-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
O-BcsmCamelTDPData
-- O-BcsmCamelTDPDataList shall not contain more than one instance of
-- O-BcsmCamelTDPData containing the same value for
-- o-BcsmTriggerDetectionPoint.
-- For CAMEL Phase 2, this means that only one instance of
-- O-BcsmCamelTDPData is allowed
-- with o-BcsmTriggerDetectionPoint being equal to DP2.
maxNumOfCamelTDPData
INTEGER ::= 10
O-BcsmCamelTDPData ::= SEQUENCE

o-BcsmTriggerDetectionPoint
serviceKey
gsmSCF-Address
defaultCallHandling
extensionContainer
...}
{
O-BcsmTriggerDetectionPoint,
ServiceKey,
[1] DefaultCallHandling,
OPTIONAL,
O-BcsmTriggerDetectionPoint ::= ENUMERATED {

spare
(1) ,
collectedInfo
(2),
routeSelectFailure (4),
...}
-- For O-BcsmCamelTDPData sequences containing this parameter with any
DN98628099
Issue 10-1 en
187 (264)
-----
O-BcsmCamelTDPDatasequence.
For O-BcsmCamelTDP-Criteria sequences containing this parameter with any
other value than the ones listed the receiver shall ignore the whole
O-BcsmCamelTDP-Criteria sequence.
O-BcsmCamelTDPCriteriaList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF

O-BcsmCamelTDP-Criteria
T-BCSM-CAMEL-TDP-CriteriaList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
T-BCSM-CAMEL-TDP-Criteria
O-BcsmCamelTDP-Criteria ::= SEQUENCE {

o-BcsmTriggerDetectionPoint
O-BcsmTriggerDetectionPoint,
destinationNumberCriteria
[0] DestinationNumberCriteria OPTIONAL,
basicServiceCriteria
[1] BasicServiceCriteria OPTIONAL,
callTypeCriteria
[2] CallTypeCriteria OPTIONAL,
o-CauseValueCriteria
[3] O-CauseValueCriteria OPTIONAL,
extensionContainer
...}
T-BCSM-CAMEL-TDP-Criteria ::= SEQUENCE {
t-BCSM-TriggerDetectionPoint T-BcsmTriggerDetectionPoint,
basicServiceCriteria
[0] BasicServiceCriteria OPTIONAL,
t-CauseValueCriteria
[1] T-CauseValueCriteria OPTIONAL,
...}
DestinationNumberCriteria ::= SEQUENCE {

matchType
[0] MatchType,
destinationNumberList
[1] DestinationNumberList
OPTIONAL,
destinationNumberLengthList
[2] DestinationNumberLengthList OPTIONAL,
...}
DestinationNumberList ::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumbers) OF
ISDN-AddressString
-- The receiving entity shall not check the format of a number in
-- the dialled number list
DestinationNumberLengthList ::=
SEQUENCE SIZE (1..maxNumOfCamelDestinationNumberLengths) OF
INTEGER (1..maxNumOfISDN-AddressDigits)
BasicServiceCriteria
::= SEQUENCE SIZE (1..maxNumOfCamelBasicServiceCriteria) OF
maxNumOfISDN-AddressDigits
INTEGER ::= 15
maxNumOfCamelDestinationNumbers
INTEGER ::= 10
maxNumOfCamelDestinationNumberLengths
maxNumOfCamelBasicServiceCriteria
INTEGER ::= 3
INTEGER ::= 5
CallTypeCriteria ::= ENUMERATED {

forwarded
(0),
188 (264)
DN98628099
Issue 10-1 en
notForwarded
(1)}
MatchType ::= ENUMERATED {

inhibiting
(0),
enabling
(1)}
O-CauseValueCriteria ::= SEQUENCE SIZE (1..maxNumOfCAMEL-O-CauseValueCriteria) OF
CauseValue
T-CauseValueCriteria ::= SEQUENCE SIZE (1..maxNumOfCAMEL-T-CauseValueCriteria) OF
CauseValue
maxNumOfCAMEL-O-CauseValueCriteria
INTEGER ::= 5
maxNumOfCAMEL-T-CauseValueCriteria
INTEGER ::= 5
CauseValue ::= OCTET STRING (SIZE (1))

-- Type extracted from Cause parameter in ITU-T Recommendation Q.763.
-- For the use of cause value refer to ITU-T Recommendation Q.850.
DefaultCallHandling ::= ENUMERATED {
continueCall (0) ,
releaseCall
(1),
...}
-- reception of values in range 2-31 shall be treated as "continueCall"
-- reception of values greater than 31 shall be treated as "releaseCall"
CamelCapabilityHandling ::= INTEGER (1..16)
-- value 1 = CAMEL phase 1,
-- value 2 = CAMEL phase 2,
-- value 3 = CAMEL Phase 3,
-- value 4 = CAMEL Phase 4:
-- reception of values greater than 4 shall be treated as CAMEL phase 4.
-- fault recovery types
-- version 1:
ResetArg ::= SEQUENCE {
networkResource NetworkResource,
hlr-Number
ISDN-AddressString,
hlr-List
HLR-List
OPTIONAL,
...}
-- version 2:
ResetArg ::= SEQUENCE {
-- networkResource must be present in version 1
-- networkResource must be absent in version greater 1
hlr-Number
ISDN-AddressString,
hlr-List
HLR-List
OPTIONAL,
...}
-- ForwardCheckSS-IndicationArg is empty
-- version 2:
RestoreDataArg ::= SEQUENCE {
DN98628099
Issue 10-1 en
189 (264)
imsi
lmsi
...}
IMSI,
LMSI
-- version 3:
RestoreDataArg ::= SEQUENCE {
imsi
IMSI,
lmsi
LMSI
extensionContainer ExtensionContainer
vlr-Capability
[6] VLR-Capability
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
RestoreDataRes ::= SEQUENCE {

hlr-Number
ISDN-AddressString,
msNotReachable NULL
OPTIONAL,
...}
-- VBS/VGCS types
VBSDataList ::= SEQUENCE SIZE (1..maxNumOfVBSGroupIds) OF
VoiceBroadcastData
VGCSDataList ::= SEQUENCE SIZE (1..maxNumOfVGCSGroupIds) OF
VoiceGroupCallData
maxNumOfVBSGroupIds
maxNumOfVGCSGroupIds
VoiceGroupCallData
groupId
...}
INTEGER ::= 50
INTEGER ::= 50
::= SEQUENCE {
GroupId,
VoiceBroadcastData ::= SEQUENCE {

groupid
GroupId,
broadcastInitEntitlement
NULL OPTIONAL,
...}
GroupId ::= OCTET STRING (SIZE (3))
-- Refers to the Group Identification as specified in GSM TS 03.03
-- and 03.68/ 03.69
-- provide subscriber info types
ProvideSubscriberInfoArg ::= SEQUENCE {
imsi
[0] IMSI,
lmsi
[1] LMSI
OPTIONAL,
requestedInfo
[2] RequestedInfo,
...}
ProvideSubscriberInfoRes ::= SEQUENCE {
subscriberInfo SubscriberInfo,
...}
SubscriberInfo ::= SEQUENCE {
locationInformation
[0] LocationInformation OPTIONAL,
190 (264)
DN98628099
Issue 10-1 en
subscriberState
extensionContainer
... ,
ps-SubscriberState
imei
[1] SubscriberState OPTIONAL,

[3] LocationInformationGPRS OPTIONAL,
[4] PS-SubscriberState OPTIONAL,
[5] IMEI OPTIONAL }
LocationInformationGPRS ::= SEQUENCE

{
cellGlobalIdOrServiceAreaIdOrLAI [0]
CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL,
routeingAreaIdentity
[1] RAIdentity OPTIONAL,
[2] GeographicalInformation OPTIONAL,
sgsn-Number
selectedLSAIdentity
[4] LSAIdentity OPTIONAL,
extensionContainer
...,
sai-Present
[6] NULL OPTIONAL,
geodeticInformation
[7] GeodeticInformation OPTIONAL,
currentLocationRetrieved [8] NULL OPTIONAL,
ageOfLocationInformation [9] AgeOfLocationInformation OPTIONAL }
-- sai-Present indicates that the cellGlobalIdOrServiceAreaIdOrLAI
-- parameter contains a Service Area Identity.
-- currentLocationRetrieved shall be present if the location information
-- was retrieved after successful paging.
RAIdentity ::= OCTET STRING (SIZE (6))
-- Routing Area Identity is coded in accordance with 3GPP TS 29.060 [105].
-- It shall contain the value part defined in 3GPP TS 29.060 only.
-- I.e. the 3GPP TS 29.060 type identifier octet shall not be included.
GeographicalInformation ::= OCTET STRING (SIZE (8))
-- Refers to geographical Information defined in 3GPP TS 23.032.
-- Only the description of an ellipsoid point with uncertainty circle
-- as specified in 3GPP TS 23.032 is allowed to be used
-- The internal structure according to 3GPP TS 23.032 is as follows:
-- Type of shape (ellipsoid point with uncertainty circle) 1 octet
-- Degrees of Latitude
3 octets
-- Degrees of Longitude
3 octets
-- Uncertainty code
1 octet
GeodeticInformation ::= OCTET STRING (SIZE (10))
-- Refers to Calling Geodetic Location defined in Q.763 (1999).
-- Only the description of an ellipsoid point with uncertainty circle
-- as specified in Q.763 (1999) is allowed to be used
-- The internal structure according to Q.763 (1999) is as follows:
-- Screening and presentation indicators 1 octet
-- Type of shape (ellipsoid point with uncertainty circle) 1 octet
-- Degrees of Latitude
3 octets
-- Degrees of Longitude
3 octets
-- Uncertainty code
1 octet
-- Confidence
1 octet
PS-SubscriberState ::= CHOICE
{
notProvidedFromSGSN
ps-Detached
ps-AttachedNotReachableForPaging
DN98628099
Issue 10-1 en
[0] NULL,
[1] NULL,
[2] NULL,
191 (264)
ps-AttachedReachableForPaging
[3] NULL,
ps-PDP-ActiveNotReachableForPaging [4] PDP-ContextInfoList,
ps-PDP-ActiveReachableForPaging
[5] PDP-ContextInfoList,
netDetNotReachable
NotReachableReason }
PDP-ContextInfoList ::= SEQUENCE
PDP-ContextInfo
PDP-ContextInfo ::= SEQUENCE {
pdp-ContextIdentifier
[0]
pdp-ContextActive
[1]
pdp-Type
[2]
pdp-Address
[3]
apn-Subscribed
[4]
apn-InUse
[5]
nsapi
[6]
transactionId
[7]
teid-ForGnAndGp
[8]
teid-ForIu
[9]
ggsn-Address
[10]
qos-Subscribed
[11]
qos-Requested
[12]
qos-Negotiated
[13]
chargingId
[14]
chargingCharacteristics [15]
rnc-Address
[16]
extensionContainer
[17]
qos2-Subscribed
[18]
qos2-Requested
[19]
qos2-Negotiated
[20]
...}
SIZE (1..maxNumOfPDP-Contexts) OF
ContextId,
NULL OPTIONAL,
PDP-Type,
PDP-Address OPTIONAL,
APN OPTIONAL,
APN OPTIONAL,
NSAPI OPTIONAL,
TransactionId OPTIONAL,
TEID OPTIONAL,
TEID OPTIONAL,
Ext-QoS-Subscribed OPTIONAL,
GPRSChargingID OPTIONAL,
ChargingCharacteristics OPTIONAL,
Ext2-QoS-Subscribed OPTIONAL,
NSAPI ::= INTEGER (0..15)

-- This type is used to indicate the Network layer Service Access Point
TransactionId ::= OCTET STRING (SIZE (1..2))
-- This type carries the value part of the transaction identifier which is
-- used in the session management messages on the access interface. The
-- encoding is defined in 3GPP TS 24.008
TEID ::= OCTET STRING (SIZE (4))
-- This type carries the value part of the Tunnel Endpoint Identifier which
-- is used to distinguish between different tunnels between the same pair of
-- entities which communicate using the GPRS Tunnelling Protocol The encoding
-- is defined in 3GPP TS 29.060.
GPRSChargingID ::= OCTET STRING (SIZE (4))
-- The Charging ID is a unique four octet value generated by the GGSN when
-- a PDP Context is activated. A Charging ID is generated for each activated
-- context. The encoding is defined in 3GPP TS 29.060.
AdditionalRequestedCAMEL-SubscriptionInfo ::= ENUMERATED {
mt-sms-CSI (0),
mg-csi
(1),
...}
-- exception handling: unknown values shall be discarded by the receiver.
192 (264)
DN98628099
Issue 10-1 en
MG-CSI ::= SEQUENCE {

mobilityTriggers
MobilityTriggers,
serviceKey
ServiceKey,
gsmSCF-Address
notificationToCSE
[2] NULL OPTIONAL,
csi-Active
[3] NULL OPTIONAL,
...}
-- notificationToCSE and csi-Active shall not be present when MG-CSI is sent
-- to SGSN. They may only be included in ATSI/ATM ack/NSDC message.
ModificationRequestFor-ODB-data
odb-data
[0]
modifyNotificationToCSE [1]
extensionContainer
[2]
...}
::= SEQUENCE {
ODB-Data OPTIONAL,
ModificationInstruction OPTIONAL,
LocationInformation ::= SEQUENCE {

AgeOfLocationInformation
OPTIONAL,
[0] GeographicalInformation
OPTIONAL,
vlr-number
OPTIONAL,
locationNumber
[2] LocationNumber
OPTIONAL,
cellGlobalIdOrServiceAreaIdOrLAI [3] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL,
extensionContainer
OPTIONAL,
selectedLSA-Id
[5] LSAIdentity
OPTIONAL,
msc-Number
OPTIONAL,
geodeticInformation
[7] GeodeticInformation
OPTIONAL,
[8] NULL
OPTIONAL,
sai-Present
[9] NULL
OPTIONAL }
-- sai-Present indicates that the cellGlobalIdOrServiceAreaIdOrLAI
-- parameter contains a Service Area Identity
-- currentLocationRetrieved shall be present if the location
-- information were retrieved after a successfull paging.
AgeOfLocationInformation ::= INTEGER (0..32767)
-- the value represents the elapsed time in minutes since the last
-- network contact of the mobile station (i.e. the actuality of the
-- location information).
-- value "0" indicates that the MS is currently in contact with the
-network
-- value "32767" indicates that the location information is at least
-32767 minutes old
GeographicalInformation ::= OCTET STRING (SIZE (8))
-- Refers to geographical Information defined in GSM 03.32.
-- Only the description of a circle (point;radius) as specified
-- 03.32 is allowed to be used
-- The internal structure according to GSM 03.32 is as follows:
-Length Indicator/Type of shape (circle) 1 octet
-Point description
-Degrees of Longitude
-Degrees of Latitude
-Radius
in GSM
3 octets
3 octets
1 octet
GeodeticInformation ::= OCTET STRING (SIZE (10))
DN98628099
Issue 10-1 en
193 (264)
-----------
Refers to Calling Geodetic Location defined in Q.763 (1999).

Only the description of an ellipsoid point with uncertainty circle
as specified in Q.763 (1999) is allowed to be used
The internal structure according to Q.763 (1999) is as follows:
Screening and presentation indicators 1 octet
Type of shape (ellipsoid point with uncertainty circle) 1 octet
Degrees of Latitude 3 octets
Degrees of Longitude 3 octets
Uncertainty code 1 octet
Confidence
RequestedInfo ::= SEQUENCE {

locationInformation [0] NULL OPTIONAL,
subscriberState
[1] NULL OPTIONAL,
extensionContainer
...,
currentLocation
[3] NULL OPTIONAL,
requestedDomain
[4] DomainType OPTIONAL,
imei
[6] NULL OPTIONAL,
ms-classmark
[5] NULL OPTIONAL }
-- currentLocation shall be absent if locationInformation is absent
DomainType ::= ENUMERATED {
cs-Domain
(0),
ps-Domain
(1),
...}
-- reception of values > 1 shall be mapped to 'cs-Domain'
LocationNumber ::= OCTET STRING (SIZE (2..10))
-- the internal structure is defined in CCITT Rec Q.763
SubscriberState ::= CHOICE {
assumedIdle
[0]
camelBusy
[1]
netDetNotReachable
notProvidedFromVLR
[2]
NotReachableReason
msPurged
imsiDetached
restrictedArea
notRegistered
NULL,
NULL,
NotReachableReason,
NULL}
::= ENUMERATED {
(0),
(1),
(2),
(3)}
-- any time interrogation info types

AnyTimeInterrogationArg ::= SEQUENCE {
subscriberIdentity
[0] SubscriberIdentity,
requestedInfo
[1] RequestedInfo,
gsmSCF-Address
...}
AnyTimeInterrogationRes ::= SEQUENCE {
subscriberInfo SubscriberInfo,
...}
194 (264)
DN98628099
Issue 10-1 en
AnyTimeSubscriptionInterrogationArg ::= SEQUENCE {

subscriberIdentity
requestedSubscriptionInfo [1] RequestedSubscriptionInfo,
gsmSCF-Address
extensionContainer
longFTN-Supported
[4] NULL OPTIONAL,
...}
AnyTimeSubscriptionInterrogationRes ::= SEQUENCE {
callForwardingData
[1] CallForwardingData OPTIONAL,
callBarringData
[2] CallBarringData OPTIONAL,
odb-Info
[3] ODB-Info OPTIONAL,
[4] CAMEL-SubscriptionInfo OPTIONAL,
extensionContainer
...,
offeredCamel4CSIsInVLR
offeredCamel4CSIsInSGSN
[9] OfferedCamel4CSIs OPTIONAL }
RequestedSubscriptionInfo ::= SEQUENCE {
requestedSS-Info
[1] SS-ForBS-Code OPTIONAL,
odb
[2] NULL OPTIONAL,
requestedCAMEL-SubscriptionInfo [3] RequestedCAMEL-SubscriptionInfo OPTIONAL,
[4] NULL OPTIONAL,
[5] NULL OPTIONAL,
extensionContainer
... ,
additionalRequestedCAMEL-SubscriptionInfo [7]
AdditionalRequestedCAMEL-SubscriptionInfo OPTIONAL
-- CAMEL phase 4}
RequestedCAMEL-SubscriptionInfo ::= ENUMERATED {
o-CSI
(0),
t-CSI
(1),
vt-CSI
(2),
tif-CSI
(3),
gprs-CSI
(4),
mo-sms-CSI (5),
ss-CSI
(6),
m-CSI
(7),
d-csi
(8)}
CallForwardingData ::= SEQUENCE {
forwardingFeatureList Ext-ForwFeatureList,
notificationToCSE
NULL
OPTIONAL,
extensionContainer [0] ExtensionContainer
OPTIONAL,
...}
CallBarringData ::= SEQUENCE {
callBarringFeatureList
password
wrongPasswordAttemptsCounter
notificationToCSE
extensionContainer
...}
DN98628099
Issue 10-1 en
Ext-CallBarFeatureList,
Password OPTIONAL,
WrongPasswordAttemptsCounter OPTIONAL,
NULL OPTIONAL,
195 (264)
WrongPasswordAttemptsCounter ::= INTEGER (0..4)

ODB-Info ::= SEQUENCE {
odb-Data
ODB-Data,
notificationToCSE
NULL OPTIONAL,
...}
CAMEL-SubscriptionInfo ::= SEQUENCE {
o-CSI
[0]
[1]
d-CSI
[2]
t-CSI
[3]
[4]
vt-CSI
[5]
vt-BCSM-CAMEL-TDP-CriteriaList [6]
tif-CSI
[7]
tif-CSI-NotificationToCSE
[8]
gprs-CSI
[9]
mo-sms-CSI
[10]
ss-CSI
[11]
m-CSI
[12]
extensionContainer
[13]
...,
specificCSIDeletedList
[14]
mt-sms-CSI
[15]
[16]
mg-csi
[17]
-- CAMEL phase 4 }
AnyTimeModificationArg ::= SEQUENCE
subscriberIdentity
gsmSCF-Address
modificationRequestFor-CF-Info
modificationRequestFor-CB-Info
modificationRequestFor-CSI
extensionContainer
longFTN-Supported
...,
modificationRequestFor-ODB-data
-- CAMEL ph4
}
AnyTimeModificationRes ::=
ss-InfoFor-CSE
extensionContainer
...,
odb-Info
-- CAMEL phase 4}
{
[0]
[1]
[2]
[3]
[4]
[5]
[6]
O-CSI OPTIONAL,
O-BcsmCamelTDPCriteriaList OPTIONAL,
D-CSI OPTIONAL,
T-CSI OPTIONAL,
T-CSI OPTIONAL,
NULL OPTIONAL,
NULL OPTIONAL,
GPRS-CSI OPTIONAL,
SMS-CSI OPTIONAL,
SS-CSI OPTIONAL,
M-CSI OPTIONAL,
SpecificCSI-Withdraw OPTIONAL,
SMS-CSI OPTIONAL,
MT-smsCAMELTDP-CriteriaList OPTIONAL,
MG-CSI OPTIONAL
SubscriberIdentity,
ISDN-AddressString,
ModificationRequestFor-CF-Info OPTIONAL,
ModificationRequestFor-CB-Info OPTIONAL,
ModificationRequestFor-CSI OPTIONAL,
NULL OPTIONAL,
[7] ModificationRequestFor-ODB-data OPTIONAL
SEQUENCE {
[0] Ext-SS-InfoFor-CSE OPTIONAL,
[1] CAMEL-SubscriptionInfo OPTIONAL,
[3] ODB-Info OPTIONAL
ModificationRequestFor-CF-Info ::= SEQUENCE {

ss-Code
[0] SS-Code,
basicService
[1] Ext-BasicServiceCode OPTIONAL,
ss-Status
[2] Ext-SS-Status OPTIONAL,
196 (264)
DN98628099
Issue 10-1 en
forwardedToNumber
extensionContainer
...}
[3]
[4]
[5]
[6]
[7]
AddressString OPTIONAL,
ISDN-SubaddressString OPTIONAL,
Ext-NoRepCondTime OPTIONAL,
ModificationInstruction OPTIONAL,
ModificationRequestFor-CB-Info ::= SEQUENCE {

ss-Code
[0] SS-Code,
basicService
ss-Status
[2] Ext-SS-Status OPTIONAL,
password
[3] Password OPTIONAL,
wrongPasswordAttemptsCounter [4] WrongPasswordAttemptsCounter OPTIONAL,
[5] ModificationInstruction OPTIONAL,
extensionContainer
...}
ModificationRequestFor-CSI ::= SEQUENCE {
requestedCamel-SubscriptionInfo [0] RequestedCAMEL-SubscriptionInfo,
modifyCSI-State
extensionContainer
... ,
additionalRequestedCAMEL-SubscriptionInfo [4]
AdditionalRequestedCAMEL-SubscriptionInfo OPTIONAL
-- CAMEL phase 4}
ModificationInstruction ::= ENUMERATED {
deactivate
(0),
activate
(1)}
Ext-SS-InfoFor-CSE ::= CHOICE {
[0] Ext-ForwardingInfoFor-CSE,
callBarringInfoFor-CSE [1] Ext-CallBarringInfoFor-CSE
}
Ext-ForwardingInfoFor-CSE
ss-Code
notificationToCSE
extensionContainer
...}
::=
[0]
[1]
[2]
[3]
SEQUENCE {
SS-Code,
Ext-ForwFeatureList,
NULL OPTIONAL,
Ext-CallBarringInfoFor-CSE ::= SEQUENCE {

ss-Code
[0] SS-Code,
callBarringFeatureList
[1] Ext-CallBarFeatureList,
password
[2] Password OPTIONAL,
wrongPasswordAttemptsCounter [3] WrongPasswordAttemptsCounter OPTIONAL,
notificationToCSE
[4] NULL OPTIONAL,
extensionContainer
...}
-- subscriber data modification notification types
NoteSubscriberDataModifiedArg ::= SEQUENCE {
imsi
IMSI,
DN98628099
Issue 10-1 en
197 (264)
msisdn
callBarringInfoFor-CSE
odb-Info
allInformationSent
extensionContainer
...}
[0]
[1]
[2]
[3]
[4]
ISDN-AddressString,
Ext-ForwardingInfoFor-CSE OPTIONAL,
Ext-CallBarringInfoFor-CSE OPTIONAL,
ODB-Info OPTIONAL,
CAMEL-SubscriptionInfo OPTIONAL,
NULL OPTIONAL,
NoteSubscriberDataModifiedRes ::= SEQUENCE {

extensionContainer
...}
SubscriberIdentity ::= CHOICE {
imsi
[0] IMSI,
msisdn
[1] ISDN-AddressString }
-- mobility management event notification info types
NoteMM-EventArg ::= SEQUENCE {
serviceKey
eventMet
imsi
msisdn
locationInformation
supportedCAMELPhases
extensionContainer
offeredCamel4Functionalities
...}
[0]
[1]
[2]
[3]
[5]
[6]
[7]
[8]
ServiceKey,
MM-Code,
IMSI,
ISDN-AddressString,
LocationInformation
SupportedCamelPhases
ExtensionContainer
LocationInformationGPRS
OfferedCamel4Functionalities
NoteMM-EventRes ::= SEQUENCE {

extensionContainer ExtensionContainer
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
MM-Code ::= OCTET STRING (SIZE (1))

-- This type is used to indicate a Mobility Management event.
-- Actions for the following MM-Code values are defined in CAMEL Phase 4:
--- CS domain MM events:
-Location-update-in-same-VLR
MM-Code ::= '00000000'B
-Location-update-to-other-VLR
MM-Code ::= '00000001'B
-IMSI-Attach
MM-Code ::= '00000010'B
-MS-initiated-IMSI-Detach
MM-Code ::= '00000011'B
-Network-initiated-IMSI-Detach
MM-Code ::= '00000100'B
--- PS domain MM events:
-Routeing-Area-update-in-same-SGSN
MM-Code ::= '10000000'B
-Routeing-Area-update-to-other-SGSN-update-from-new-SGSN
-MM-Code ::= '10000001'B
-Routeing-Area-update-to-other-SGSN-disconnect-by-detach
-MM-Code ::= '10000010'B
-GPRS-Attach
MM-Code ::= '10000011'B
-MS-initiated-GPRS-Detach
MM-Code ::= '10000100'B
-Network-initiated-GPRS-Detach
MM-Code ::= '10000101'B
-Network-initiated-transfer-to-MS-not-reachable-for-paging
198 (264)
DN98628099
Issue 10-1 en
-------
MM-Code ::= '10000110'B

If
CS
If
PS
the MSC receives any other MM-code than the ones listed above for the
domain, then the MSC shall ignore that MM-code.
the SGSN receives any other MM-code than the ones listed above for the
domain, then the SGSN shall ignore that MM-code.
T-CSI ::= SEQUENCE {

t-BcsmCamelTDPDataList
T-BcsmCamelTDPDataList,
extensionContainer
notificationToCSE
[1] NULL OPTIONAL,
csi-Active
[2] NULL OPTIONAL,
...}
-- notificationToCSE and csi-Active shall not be present when T-CSI is sent
-- to VLR/GMSC. They may only be included in ATSI/ATM ack/NSDC message.
T-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
T-BcsmCamelTDPData
-- T-BcsmCamelTDPDataList shall not contain more than one instance of
-- T-BcsmCamelTDPData containing the same value for
-- t-BcsmTriggerDetectionPoint.
-- For CAMEL Phase 2, this means that only one instance of
-- T-BcsmCamelTDPData is allowed
-- with t-BcsmTriggerDetectionPoint being equal to DP12.
-- For CAMEL Phase 3, more TDP's are allowed.
T-BcsmCamelTDPData ::= SEQUENCE {
t-BcsmTriggerDetectionPoint
T-BcsmTriggerDetectionPoint,
serviceKey
ServiceKey,
gsmSCF-Address
[0]
ISDN-AddressString,
defaultCallHandling
[1]
DefaultCallHandling,
...}
T-BcsmTriggerDetectionPoint ::= ENUMERATED {
spare
(1) ,
termAttemptAuthorized (12),
tBusy
(13),
tNoAnswer
(14),
...}
-- For T-BcsmCamelTDPData sequences containing this parameter with any other
-- value than the ones listed above, the receiver shall ignore the whole
-- T-BcsmCamelTDPData sequence.
END
3.3.3
Operation and Maintenance data types

MAP-OM-DataTypes
BEGIN
DN98628099
Issue 10-1 en
199 (264)
-- version 1:
ActivateTraceModeArg ::= SEQUENCE {
imsi
[0] IMSI
OPTIONAL,
traceReference
[1] TraceReference,
traceType
[2] TraceType,
omc-Id
[3] AddressString
OPTIONAL }
-- version 2:
imsi
[0] IMSI
OPTIONAL,
traceReference
[1] TraceReference,
traceType
[2] TraceType,
omc-Id
[3] AddressString
OPTIONAL,
ext
[PRIVATE 0] ATMargExt
OPTIONAL,
-- proprietary
...}
-- version 3:
imsi
[0] IMSI
OPTIONAL,
traceReference
[1] TraceReference,
traceType
[2] TraceType,
omc-Id
[3] AddressString
OPTIONAL,
...}
-- version 1 and version 2 ActivateTraceModeRes is empty;
-- version 3:
ActivateTraceModeRes ::= SEQUENCE {
...}
-- version 1:
DeactivateTraceModeArg ::= SEQUENCE {
imsi
[0] IMSI
OPTIONAL,
traceReference
[1] TraceReference }
-- version 2:
DeactivateTraceModeArg ::=
imsi
[0]
traceReference
[1]
ext
[PRIVATE 0]
-- proprietary
...}
-- version 3:
DeactivateTraceModeArg
imsi
traceReference
extensionContainer
...}
::=
[0]
[1]
[2]
SEQUENCE {
IMSI
OPTIONAL,
TraceReference,
DTMargExt OPTIONAL,
SEQUENCE {
IMSI
OPTIONAL,
TraceReference,
-- version 1 and version 2 DeactivateTraceModeRes is empty;

-- version 3:
DeactivateTraceModeRes ::= SEQUENCE {
...}
200 (264)
DN98628099
Issue 10-1 en
TraceSubscriberActivityArg ::= SEQUENCE

imsi
[0] IMSI
traceReference
[1] TraceReference,
traceType
[2] TraceType,
omc-Id
[3] AddressString
callReference
[4] CallReference
{
OPTIONAL,
OPTIONAL,
OPTIONAL}
CallReference ::= OCTET STRING (SIZE (1..3))

NoteInternalHO-Arg ::= SEQUENCE {
handoverType
HandoverType,
targetCellId
[1] GlobalCellId
channelId
[2] ExternalSignalInfo
OPTIONAL,
OPTIONAL}
HandoverType ::= ENUMERATED {

interBSS
(0),
intraBSS
(1)}
SendIMSI-Arg ::= ISDN-AddressString
-- msisdn
SendIMSI-Res ::= IMSI
END
3.3.4
Call Handling data types
MAP-CH-DataTypes
BEGIN
-- version 1:
SendRoutingInfoArg ::= SEQUENCE {
msisdn
cug-CheckInfo
[1] CUG-Interlock
numberOfForwarding
[2] NumberOfForwarding
networkSignalInfo
-- version 2:
msisdn
cug-CheckInfo
[1] CUG-CheckInfo
numberOfForwarding
networkSignalInfo
sriExtension
[PRIVATE 0] SriExtension
-- proprietary
extraSignalInfo
[PRIVATE 1] ExtraSignalInfo
-- proprietary
...}
OPTIONAL,
OPTIONAL,
OPTIONAL }
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
-- version 3:
DN98628099
Issue 10-1 en
201 (264)
msisdn
cug-CheckInfo
[1] CUG-CheckInfo
OPTIONAL,
numberOfForwarding
OPTIONAL,
interrogationType
[3] InterrogationType
OPTIONAL,
or-Interrogation
[4] NULL
OPTIONAL,
or-Capability
[5] OR-Phase
OPTIONAL,
gmsc-Address
OPTIONAL,
callReferenceNumber
[7] CallReferenceNumber OPTIONAL,
forwardingReason
[8] ForwardingReason
OPTIONAL,
basicServiceGroup
networkSignalInfo
OPTIONAL,
camelInfo
[11] CamelInfo
OPTIONAL,
suppressionOfAnnouncement [12] SuppressionOfAnnouncement OPTIONAL,
extensionContainer
OPTIONAL,
alertingPattern
[14] AlertingPattern
OPTIONAL,
ccbs-Call
[15] NULL
OPTIONAL,
supportedCCBS-Phase
[16] SupportedCCBS-Phase OPTIONAL,
[17] Ext-ExternalSignalInfo OPTIONAL,
istSupportIndicator
[18] IST-SupportIndicator OPTIONAL,
pre-pagingSupported
[19] NULL OPTIONAL,
callDiversionTreatmentIndicator [20] CallDiversionTreatmentIndicator OPTIONAL,
longFTN-Supported
[21] NULL
OPTIONAL,
suppress-VT-CSI
[22] NULL
OPTIONAL,
suppressIncomingCallBarring [23] NULL
OPTIONAL,
gsmSCF-InitiatedCall
[24] NULL
OPTIONAL,
...}
-- version 1:
SendRoutingInfoRes ::= SEQUENCE {
imsi
routingInfo
-- version 2:
SendRoutingInfoRes ::= SEQUENCE {
imsi
routingInfo
cug-CheckInfo
sriResExtension
[PRIVATE 0]
-- proprietary
numberPorted
[PRIVATE 20]
-- proprietary
ansiSriResExt
[PRIVATE 30]
-- proprietary
...}
IMSI,
RoutingInfo }
IMSI,
RoutingInfo,
CUG-CheckInfo
SriResExtension
OPTIONAL,
OPTIONAL,
NumberPorted
OPTIONAL,
ANSISriResExt
OPTIONAL,
-- version 3:
SendRoutingInfoRes ::= [3] SEQUENCE {
imsi
[9] IMSI
OPTIONAL,
-- IMSI must be present if SendRoutingInfoRes is not segmented.
-- If the TC-Result-NL segmentation option is taken the IMSI must be
-- present in one segmented transmission of SendRoutingInfoRes.
extendedRoutingInfo
ExtendedRoutingInfo
OPTIONAL,
cug-CheckInfo
[3] CUG-CheckInfo
OPTIONAL,
cugSubscriptionFlag
[6] NULL
OPTIONAL,
subscriberInfo
[7] SubscriberInfo
OPTIONAL,
ss-List
[1] SS-List
OPTIONAL,
202 (264)
DN98628099
Issue 10-1 en
basicService
forwardingInterrogationRequired [4] NULL
OPTIONAL,
vmsc-Address
OPTIONAL,
extensionContainer
OPTIONAL,
naea-PreferredCI
[10] NAEA-PreferredCI
OPTIONAL,
-- naea-PreferredCI is included at the discretion of the HLR operator.
ccbs-Indicators
[11] CCBS-Indicators
OPTIONAL,
msisdn
OPTIONAL,
numberPortabilityStatus
[13] NumberPortabilityStatus OPTIONAL,
istAlertTimer
[14] IST-AlertTimerValue OPTIONAL,
supportedCamelPhasesInVMSC [15] SupportedCamelPhases OPTIONAL,
offeredCamel4CSIsInVMSC
[16] OfferedCamel4CSIs
OPTIONAL,
routingInfo2
[17] RoutingInfo OPTIONAL,
ss-List2
[18] SS-List OPTIONAL,
basicService2
allowedServices
[20] AllowedServices OPTIONAL,
unavailabilityCause
[21] UnavailabilityCause OPTIONAL,
releaseResourcesSupported
[22] NULL OPTIONAL,
[23] ExternalSignalInfo OPTIONAL,
ansiSriResExt
[PRIVATE 30] ANSISriResExt
OPTIONAL,
-- proprietary
...}
NumberOfForwarding ::= INTEGER (1..5)
NumberPortabilityStatus ::= ENUMERATED {
notKnownToBePorted
(0),
ownNumberPortedOut
(1),
foreignNumberPortedToForeignNetwork (2),
...,
ownNumberNotPortedOut (4),
foreignNumberPortedIn (5)}
-- reception of other values than the ones listed the receiver shall ignore
-- the whole NumberPortabilityStatus
CCBS-Indicators ::= SEQUENCE {
ccbs-Possible
[0]
keepCCBS-CallIndicator
[1]
...}
NULL
NULL
OPTIONAL,
OPTIONAL,
SuppressionOfAnnouncement ::= NULL

InterrogationType ::= ENUMERATED {
basicCall
(0),
forwarding
(1),
collectCall (2)}
OR-Phase ::= INTEGER (1..127)
CallReferenceNumber ::= OCTET STRING (SIZE (1..8))
ForwardingReason ::= ENUMERATED {
notReachable
(0),
busy
(1),
noReply
(2)}
DN98628099
Issue 10-1 en
203 (264)
SupportedCCBS-Phase ::= INTEGER (1..127)

-- Only value 1 is used.
-- Values in the ranges 2-127 are reserved for future use.
-- If received values 2-127 shall be mapped on to value 1.
CallDiversionTreatmentIndicator ::= OCTET STRING (SIZE (1))
-- callDiversionAllowed (xxxx xx01)
-- callDiversionNotAllowed (xxxx xx10)
-- network default is call diversion allowed
RoutingInfo ::= CHOICE {
roamingNumber
ISDN-AddressString,
forwardingData ForwardingData}
-- version 1:
ProvideRoamingNumberArg ::= SEQUENCE {
imsi
[0] IMSI,
msc-Number
msisdn
-- previousRoamingNumber must be absent in version 1
lmsi
[4] LMSI
networkSignalInfo
-- version 2:
imsi
[0] IMSI,
msc-Number
-- msc-Number must be present in version greater 1
msisdn
lmsi
[4] LMSI
networkSignalInfo
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL }
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
-- version 3:
imsi
[0] IMSI,
msc-Number
OPTIONAL,
-- msc-Number must be present in version greater 1
msisdn
OPTIONAL,
lmsi
[4] LMSI
OPTIONAL,
OPTIONAL,
networkSignalInfo
OPTIONAL,
[7] SuppressionOfAnnouncement
OPTIONAL,
gmsc-Address
OPTIONAL,
callReferenceNumber
[9] CallReferenceNumber
OPTIONAL,
or-Interrogation
[10] NULL
OPTIONAL,
extensionContainer
OPTIONAL,
alertingPattern
[12] AlertingPattern
OPTIONAL,
ccbs-Call
[13] NULL
OPTIONAL,
supportedCamelPhasesInInterrogatingNode [15] SupportedCamelPhases OPTIONAL,
204 (264)
DN98628099
Issue 10-1 en
[14] Ext-ExternalSignalInfo
orNotSupportedInGMSC
[16] NULL
pre-pagingSupported
[17] NULL
longFTN-Supported
[18] NULL
suppress-VT-CSI
[19] NULL
offeredCamel4CSIsInInterrogatingNode [20] OfferedCamel4CSIs
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
-- version 1 and version 2:

ProvideRoamingNumberRes ::= ISDN-AddressString
-- roamingNumber
-- version 3:
ProvideRoamingNumberRes ::= SEQUENCE {
roamingNumber
ISDN-AddressString,
...}
-- version 3:
ResumeCallHandlingArg ::= SEQUENCE {
callReferenceNumber
[0] CallReferenceNumber,
basicServiceGroup
[1] Ext-BasicServiceCode,
forwardingData
[2] ForwardingData,
imsi
[3] IMSI,
cug-CheckInfo
[4] CUG-CheckInfo
OPTIONAL,
o-CSI
[5] O-CSI
OPTIONAL,
extensionContainer
OPTIONAL,
ccbs-Possible
[8] NULL
OPTIONAL,
...}
-- version 4:
ResumeCallHandlingArg ::= SEQUENCE {
callReferenceNumber
[0] CallReferenceNumber
basicServiceGroup
[1] Ext-BasicServiceCode
forwardingData
[2] ForwardingData
imsi
[3] IMSI
cug-CheckInfo
[4] CUG-CheckInfo
o-CSI
[5] O-CSI
extensionContainer
ccbs-Possible
[8] NULL
msisdn
uu-Data
[10] UU-Data
allInformationSent
[11] NULL
d-csi
[12] D-CSI
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
ResumeCallHandlingRes ::= SEQUENCE {

...}
UU-Data ::= SEQUENCE {
uuIndicator
uui
uusCFInteraction
extensionContainer
...}
DN98628099
Issue 10-1 en
[0]
[1]
[2]
[3]
UUIndicator
UUI
NULL
ExtensionContainer
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
205 (264)
UUIndicator ::= OCTET STRING (SIZE (1))

-- Octets are coded according to ETS 300 356
UUI
::= OCTET STRING (SIZE (1..131))

-- Octets are coded according to ETS 300 356
CamelInfo ::= SEQUENCE {

SupportedCamelPhases,
suppress-T-CSI
NULL
...,
offeredCamel4CSIs
[0] OfferedCamel4CSIs
OPTIONAL,
OPTIONAL }
ExtendedRoutingInfo ::= CHOICE {

routingInfo
RoutingInfo,
camelRoutingInfo
[8] CamelRoutingInfo}
CamelRoutingInfo ::= SEQUENCE {
forwardingData
ForwardingData OPTIONAL,
gmscCamelSubscriptionInfo
[0] GmscCamelSubscriptionInfo,
...}
GmscCamelSubscriptionInfo ::= SEQUENCE {
t-CSI
[0] T-CSI OPTIONAL,
o-CSI
[1] O-CSI OPTIONAL,
extensionContainer
[3] O-BcsmCamelTDPCriteriaList OPTIONAL,
t-BCSM-CAMEL-TDP-CriteriaList [4] T-BCSM-CAMEL-TDP-CriteriaList OPTIONAL,
d-csi
[5] D-CSI OPTIONAL,
...}
SetReportingStateArg ::= SEQUENCE {

imsi
[0] IMSI
lmsi
[1] LMSI
ccbs-Monitoring
[2] ReportingState
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
ReportingState ::= ENUMERATED {

stopMonitoring
(0),
startMonitoring
(1),
...}
-- reception of values 2-10 shall be mapped to 'stopMonitoring'
-- reception of values > 10 shall be mapped to 'startMonitoring'
SetReportingStateRes ::= SEQUENCE {
[0] CCBS-SubscriberStatus
...}
OPTIONAL,
CCBS-SubscriberStatus ::= ENUMERATED {

ccbsNotIdle
(0),
ccbsIdle
(1),
ccbsNotReachable
(2),
...}
-- reception of values 3-10 shall be mapped to 'ccbsNotIdle'
206 (264)
DN98628099
Issue 10-1 en
---
reception of values 11-20 shall be mapped to 'ccbsIdle'

reception of values > 20 shall be mapped to 'ccbsNotReachable'
StatusReportArg ::= SEQUENCE {

imsi
[0] IMSI,
eventReportData
[1] EventReportData
callReportdata
[2] CallReportData
...}
OPTIONAL,
OPTIONAL,
EventReportData ::= SEQUENCE {

[0] CCBS-SubscriberStatus
...}
CallReportData ::= SEQUENCE {
monitoringMode
[0] MonitoringMode
callOutcome
[1] CallOutcome
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
MonitoringMode ::= ENUMERATED {

a-side
(0),
b-side
(1),
...}
-exception handling:
-- reception of values 2-10 shall be mapped 'a-side'
-- reception of values > 10 shall be mapped to 'b-side'
CallOutcome ::= ENUMERATED {
success
(0),
failure
(1),
busy
(2),
...}
-exception handling:
-- reception of values 3-10 shall be mapped to 'success'
-- reception of values 11-20 shall be mapped to 'failure'
-- reception of values > 20 shall be mapped to 'busy'
StatusReportRes ::= SEQUENCE {
...}
RemoteUserFreeArg ::= SEQUENCE {
imsi
[0] IMSI,
callInfo
[1] ExternalSignalInfo,
ccbs-Feature
[2] CCBS-Feature,
translatedB-Number
replaceB-Number
[4] NULL
alertingPattern
[5] AlertingPattern
...}
OPTIONAL,
OPTIONAL,
RemoteUserFreeRes ::= SEQUENCE {

ruf-Outcome
[0] RUF-Outcome,
...}
RUF-Outcome ::= ENUMERATED {
accepted
(0),
rejected
(1),
noResponseFromFreeMS (2), -- T4 Expiry
DN98628099
Issue 10-1 en
207 (264)
noResponseFromBusyMS (3), -- T10 Expiry

udubFromFreeMS
(4),
udubFromBusyMS
(5),
...}
-- reception of values 6-20 shall be mapped to 'accepted'
-- reception of values 21-30 shall be mapped to 'rejected'
-- reception of values 31-40 shall be mapped to 'noResponseFromFreeMS'
-- reception of values 41-50 shall be mapped to 'noResponseFromBusyMS'
-- reception of values 51-60 shall be mapped to 'udubFromFreeMS'
-- reception of values > 60 shall be mapped to 'udubFromBusyMS'
END
3.3.5
Supplementary Service data types
MAP-SS-DataTypes
BEGIN
-- version 1:
RegisterSS-Arg ::= SEQUENCE {
ss-Code
basicService
forwardedToNumber
[4]
[5]
-- version 2:
RegisterSS-Arg ::= SEQUENCE {
ss-Code
basicService
forwardedToNumber
[4]
[6]
[5]
defaultPriority
[7]
nbrUser
[8]
longFTN-Supported
[9]
...}
SS-Code,
BasicServiceCode
AddressString
NoReplyConditionTime
OPTIONAL,
OPTIONAL,
OPTIONAL }
SS-Code,
BasicServiceCode
AddressString
NoReplyConditionTime
EMLPP-Priority
MC-Bearers
NULL
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
-- version 1:
RegisterSS-Res ::= SS-Info
-- OPTIONAL
NoReplyConditionTime ::= INTEGER (5..30)
SS-Info ::= CHOICE {
forwardingInfo
[0] ForwardingInfo,
callBarringInfo [1] CallBarringInfo,
cug-Info
[2] CUG-Info,
-- cug-info must not be used in version 1
ss-Data
[3] SS-Data}
ForwardingInfo ::= SEQUENCE {
208 (264)
DN98628099
Issue 10-1 en
ss-Code
...}
SS-Code
ForwardingFeatureList,
OPTIONAL,
ForwardingFeatureList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF

ForwardingFeature
ForwardingFeature ::= SEQUENCE {
basicService
BasicServiceCode
OPTIONAL,
ss-Status
[4] SS-Status
OPTIONAL,
-- ss-Status must be present in version 1
forwardedToNumber
OPTIONAL,
[8] ISDN-SubaddressString
OPTIONAL,
-- forwardedToSubaddress must be absent in version 1
forwardingOptions
[6] ForwardingOptions
OPTIONAL,
[7] NoReplyConditionTime
OPTIONAL,
[9] FTN-AddressString
OPTIONAL,
...}
SS-Status ::= OCTET STRING (SIZE (1))
-- bits 8765: 0000 (unused)
-- bits 4321: Semantic of one bit shall not be implied
-by the semantic of any other bit
-- bit 4: quiescent/operative indicator
-0 operative
-1 quiescent
-- bit 3: provision indicator
-0 not provisioned
-1 provisioned
-- bit 2: registration indicator
-0 not registered
-1 registered
-- bit 1: activation indicator
-0 not active
-1 active
ForwardingOptions ::= OCTET STRING (SIZE (1))
-- v1: bits 87: notification to forwarding party
-00 no notification
-01 notification
-10 notification
-- v2: bit 8: notification to forwarding party
-0 no notification
-1 notification
-- v2: bit 7: 0 (unused)
-- v1: bits 65: notification to calling party
-00 no notification
-01 notification
-10 notification
-- v2: bit 6: v2: notification to calling party
-0 no notification
-1 notification
-- v2: bit 5: 0 (unused)
-- v2: bits 43: forwarding reason
-00 ms not reachable
-01 ms busy
DN98628099
Issue 10-1 en
209 (264)
-10 no reply
-11 unconditional
CallBarringInfo ::= SEQUENCE {
ss-Code
SS-Code
OPTIONAL,
-- ss-Code must be present in version 1
callBarringFeatureList CallBarringFeatureList,
...}
CallBarringFeatureList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF
CallBarringFeature
CallBarringFeature ::= SEQUENCE {
basicService
BasicServiceCode
OPTIONAL,
ss-Status
[4] SS-Status
OPTIONAL,
-- ss-Status must be present in version 1
...}
CUG-Info ::= SEQUENCE {
cug-SubscriptionList
cug-FeatureList
...}
CUG-SubscriptionList,
CUG-FeatureList
OPTIONAL,
CUG-SubscriptionList ::= SEQUENCE SIZE (0..maxNumOfCUG) OF

CUG-Subscription
CUG-Subscription ::= SEQUENCE {
cug-Index
CUG-Index,
cug-Interlock
CUG-Interlock,
intraCUG-Options
IntraCUG-Options,
Ext-BasicServiceGroupList
...}
OPTIONAL,
CUG-Index ::= INTEGER (0..32767)

-- The internal structure is defined in ETS 300 138.
IntraCUG-Options ::= ENUMERATED {
noCUG-Restrictions
(0),
cugIC-CallBarred
(1),
cugOG-CallBarred
(2) }
maxNumOfCUG
INTEGER ::= 10
CUG-FeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF

CUG-Feature
maxNumOfExt-BasicServiceGroups
INTEGER ::= 32
CUG-Feature ::= SEQUENCE {

basicService
preferentialCUG-Indicator
interCUG-Restrictions
...}
CUG-Index
InterCUG-Restrictions,
OPTIONAL,
OPTIONAL,
InterCUG-Restrictions::= OCTET STRING (SIZE (1))
210 (264)
DN98628099
Issue 10-1 en
---------
bits 876543: 000000 (unused)

Exception handling:
bits 876543 shall be ignored if received and not understood
bits 21
00 CUG only facilities
01 CUG with outgoing access
10 CUG with incoming access
11 CUG with both outgoing and incoming access
Ext-BasicServiceGroupList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups)

OF Ext-BasicServiceCode
SS-Data ::= SEQUENCE {
ss-Code
SS-Code
OPTIONAL,
-- ss-Code must be present in version 1
ss-Status
[4] SS-Status
OPTIONAL,
SS-SubscriptionOption
OPTIONAL,
-- ss-SubscriptionOption must be absent in version 1
BasicServiceGroupList
OPTIONAL,
-- basicServiceGroupList must be absent in version 1
defaultPriority
EMLPP-Priority
OPTIONAL,
nbrUser
[5] MC-Bearers
OPTIONAL,
sS-DataExtension
[PRIVATE 0] SS-DataExtension
OPTIONAL,
-- proprietary
sS-DataEmoInExt
[PRIVATE 1] SS-DataEmoInExt
OPTIONAL,
-- proprietary
...}
SS-SubscriptionOption ::= CHOICE {
[2] CliRestrictionOption,
-- used only in version greater than 1
overrideCategory
[1] OverrideCategory
-- used only in version greater than 1 }
UserToUserServiceIndicator ::= OCTET STRING (SIZE (1))
-- Bit 8
: service 1
-- Bit 7
: service 2
-- Bit 6
: service 3
-- Bit 5-1 : Reserved
-- Bit 8 to 6 coded "1" if the service
-- is available to the subscriber
-- Additional type compatible with GSM 09.02 v 3.8-0
MaximumConfereesNumber ::= INTEGER (1..10)
HuntGroupAccessSelectionOrder ::= ENUMERATED {
random (0),
sequential (1) }
CliRestrictionOption ::= ENUMERATED {
permanent
(0),
temporaryDefaultRestricted
(1),
temporaryDefaultAllowed
(2) }
DN98628099
Issue 10-1 en
211 (264)
OverrideCategory ::= ENUMERATED {

overrideEnabled
(0),
overrideDisabled
(1) }
EraseSS-Arg ::= SS-ForBS-Code
EraseSS-Res ::= SS-Info
-- OPTIONAL
-- version 1:
SS-ForBS-Code ::= SEQUENCE {
ss-Code
SS-Code,
basicService
BasicServiceCode
-- version 2:
SS-ForBS-Code ::= SEQUENCE {
ss-Code
SS-Code,
basicService
BasicServiceCode
longFTN-Supported [4] NULL
...}
OPTIONAL }
OPTIONAL,
OPTIONAL,
ActivateSS-Arg ::= SS-ForBS-Code

ActivateSS-Res ::= SS-Info
-- OPTIONAL
DeactivateSS-Arg ::= SS-ForBS-Code
DeactivateSS-Res ::= SS-Info
-- OPTIONAL
InterrogateSS-Arg ::= SS-ForBS-Code
-- version 1:
InterrogateSS-Res ::= CHOICE {
ss-Status
[0]
forwardedToNumber
[1]
[2]
[3]
SS-Status,
ISDN-AddressString,
BasicServiceGroupList,
ForwardingFeatureList }
-- version 2:
InterrogateSS-Res ::= CHOICE {
ss-Status
[0] SS-Status,
forwardedToNumber
-- forwardedToNumber must not be used in version greater 1
[2] BasicServiceGroupList,
[3] ForwardingFeatureList,
genericServiceInfo
[4] GenericServiceInfo }
-- genericServiceInfo must not be used in version 1
GenericServiceInfo ::= SEQUENCE {
ss-Status
SS-Status,
CliRestrictionOption
maximumEntitledPriority
[0] EMLPP-Priority
defaultPriority
[1] EMLPP-Priority
ccbs-FeatureList
[2] CCBS-FeatureList
212 (264)
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
DN98628099
Issue 10-1 en
nbrSB
nbrUser
nbrSN
...}
[3] MaxMC-Bearers
[4] MC-Bearers
[5] MC-Bearers
OPTIONAL,
OPTIONAL,
OPTIONAL,
CCBS-FeatureList ::= SEQUENCE SIZE (1..maxNumOfCCBS-Requests) OF CCBS-Feature

maxNumOfCCBS-Requests
INTEGER ::= 5
CCBS-Feature::= SEQUENCE {
ccbs-Index
b-subscriberNumber
b-subscriberSubaddress
basicServiceGroup
...}
CCBS-Index
[0]
[1]
[2]
[3]
CCBS-Index
ISDN-AddressString
BasicServiceCode
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
::= INTEGER (1..maxNumOfCCBS-Requests)
Cli-RestrictionInfo ::= SEQUENCE {

ss-Status
SS-Status,
CliRestrictionOption
...}
OPTIONAL,
ProcessUnstructuredSS-Data-Arg ::= SS-UserData

ProcessUnstructuredSS-Data-Res ::= SS-UserData
-- OPTIONAL
ProcessUnstructuredSS-Request-Arg ::= USSD-Arg
ProcessUnstructuredSS-Request-Res ::= USSD-Res
UnstructuredSS-Request-Arg ::= USSD-Arg
UnstructuredSS-Request-Res ::= USSD-Res
-- OPTIONAL
UnstructuredSS-Notify-Arg ::= USSD-Arg
-- UnstructuredSS-Notify-Res is empty
SS-UserData ::= IA5String (SIZE (1.. maxSignalInfoLength))
USSD-Arg ::= SEQUENCE {
USSD-DataCodingScheme,
ussd-String
USSD-String,
alertingPattern
AlertingPattern OPTIONAL,
msisdn
ussd-Extension
[PRIVATE 10] USSD-Extension OPTIONAL,
-- proprietary
...}
USSD-Res ::= SEQUENCE {
ussd-String
...}
DN98628099
Issue 10-1 en
USSD-String,
213 (264)
-- OPTIONAL
USSD-DataCodingScheme ::= OCTET STRING (SIZE (1))
-- The structuree of the USSD-DataCodingScheme is described
-- in GSM 03.41
USSD-String ::= OCTET STRING (SIZE (1..maxUSSD-StringLength))
-- The structure of the contents of the USSD-String is dependent
-- on the USSD-DataCodingScheme as described in GSM 03.41.
maxUSSD-StringLength
INTEGER ::= 160
RegisterPasswordArg ::= SS-Code

RegisterPasswordRes ::= Password
-- newPassword
Password ::= NumericString (FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9"))
(SIZE (4))
GetPasswordArg ::= GuidanceInfo
GetPasswordRes ::= Password
-- currentPassword
GuidanceInfo ::= ENUMERATED {
enterPW
(0),
enterNewPW
(1),
enterNewPW-Again
(2),
badPW-TryAgain
(3),
-- badPW-TryAgain must not be used in version greater 1
badPW-FormatTryAgain
(4)}
-- badPW-FormatTryAgain must not be used in version greater 1
-- How this information is really delivered to the subscriber
-- (display, announcement, ...) is not part of this
-- specification.
BeginSubscriberActivityArg ::= SEQUENCE {
imsi
IMSI,
originatingEntityNumber ISDN-AddressString}
SS-InfoList ::= SEQUENCE SIZE (1..maxNumOfSS) OF SS-Info
ForwardingData ::= SEQUENCE {
forwardedToNumber
OPTIONAL,
-- forwardedToNumber must be present in version 1
[4] ISDN-SubaddressString
OPTIONAL,
-- forwardedToSubaddress must be absent in version 1
forwardingOptions
[6] ForwardingOptions
OPTIONAL,
extensionContainer
OPTIONAL,
...}
SS-InvocationNotificationArg ::= SEQUENCE {
imsi
[0] IMSI,
msisdn
ss-Event
[2] SS-Code,
214 (264)
DN98628099
Issue 10-1 en
-- The following SS-Code values are allowed :

-- ect
SS-Code ::= '00110001'B
-- multiPTY
SS-Code ::= '01010001'B
-- cd
SS-Code ::= '00100100'B
-- ccbs
SS-Code ::= '01000100'B
ss-EventSpecification
[3] SS-EventSpecification
extensionContainer
b-subscriberNumber
ccbs-RequestState
[6] CCBS-RequestState
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
CCBS-RequestState ::= ENUMERATED {

request
(0),
recall
(1),
active
(2),
completed
(3),
suspended
(4),
frozen
(5),
deleted
(6) }
SS-InvocationNotificationRes ::= SEQUENCE {
...}
SS-EventSpecification ::= SEQUENCE SIZE (1..maxEventSpecification) OF
AddressString
maxEventSpecification
INTEGER ::= 2
RegisterCCEntryArg ::= SEQUENCE {

ss-Code
[0] SS-Code,
ccbs-Data
[1] CCBS-Data
...}
OPTIONAL,
CCBS-Data ::= SEQUENCE {

ccbs-Feature
[0] CCBS-Feature,
translatedB-Number
serviceIndicator
[2] ServiceIndicator
callInfo
networkSignalInfo
...}
OPTIONAL,
ServiceIndicator ::= BIT STRING {

clir-invoked
(0),
camel-invoked (1)} (SIZE (2..32))
-- bits 2 to 31 shall be ignored if received and not understood
RegisterCCEntryRes ::= SEQUENCE {
ccbs-Feature
[0] CCBS-Feature
...}
EraseCCEntryArg ::= SEQUENCE {
ss-Code
[0] SS-Code,
ccbs-Index
[1] CCBS-Index
...}
DN98628099
Issue 10-1 en
OPTIONAL,
OPTIONAL,
215 (264)
EraseCCEntryRes ::= SEQUENCE {

ss-Code
[0] SS-Code,
ss-Status
[1] SS-Status
...}
OPTIONAL,
END
3.3.6
Supplementary Service codes
MAP-SS-Code
DEFINITIONS ::=
BEGIN
SS-Code ::= OCTET STRING (SIZE (1))
-- This type is used to represent the code identifying a single
-- supplementary service, a group of supplementary services, or
-- all supplementary services. The services and abbreviations
-- used are defined in GSM 02.04. The internal structure is
-- defined as follows:
--- bits 87654321: group (bits 8765), and specific service
-- (bits 4321)
allForwardingSS
SS-Code ::= '00100000'B
-- all forwarding SS
cfu
SS-Code ::= '00100001'B
-- call forwarding unconditional
allCondForwardingSS
SS-Code ::= '00101000'B
-- all conditional forwarding SS
cfb
SS-Code ::= '00101001'B
-- call forwarding on mobile subscriber busy
cfnry
SS-Code ::= '00101010'B
-- call forwarding on no reply
cfnrc
SS-Code ::= '00101011'B
-- call forwarding on mobile subscriber not reachable
cd
SS-Code ::= '00100100'B
-- call deflection
allCallOfferingSS
SS-Code ::= '00110000'B
-- reserved for possible future use
-- all call offering SS includes also all forwarding SS
ect
SS-Code ::= '00110001'B
ct
SS-Code ::= '00110001'B
-- explicit call transfer
mah
SS-Code ::= '00110010'B
-- mobile access hunting
allCallCompletionSS
SS-Code ::= '01000000'B
-- all Call completion SS
cw
SS-Code ::= '01000001'B
-- call waiting
216 (264)
DN98628099
Issue 10-1 en
hold
-ccbs-A
-ccbs-B
--mc
--
SS-Code ::= '01000010'B

call hold
SS-Code ::= '01000011'B
completion of call to busy subscribers, originating side
SS-Code ::= '01000100'B
completion of call to busy subscribers, destination side
this SS-Code is only used in InsertSubscriberData
SS-Code ::= '01000101'B
multicall
allMultiPartySS
SS-Code ::= '01010000'B
-- all multiparty SS
multiPTY
SS-Code ::= '01010001'B
-- multiparty
allCommunityOfInterest-SS SS-Code ::= '01100000'B
-- all community of interest SS
cug
SS-Code ::= '01100001'B
-- closed user group
allChargingSS
SS-Code ::= '01110000'B
-- all charging SS
aoci
SS-Code ::= '01110001'B
-- advice of charge information
aocc
SS-Code ::= '01110010'B
-- advice of charge charging
allAdditionalInfoTransferSS SS-Code ::= '10000000'B
-- all additional information transfer SS
uus
SS-Code ::= '10000001'B
-- UUS user-to-user signalling
allBarringSS
SS-Code ::= '10010000'B
-- all barring SS
barringOfOutgoingCalls SS-Code ::= '10010001'B
-- barring of outgoing calls
baoc
SS-Code ::= '10010010'B
-- barring of all outgoing calls
boic
SS-Code ::= '10010011'B
-- barring of outgoing international calls
boicExHC
SS-Code ::= '10010100'B
-- barring of outgoing international calls except those directed
-- to the home PLMN
barringOfIncomingCalls SS-Code ::= '10011001'B
-- barring of incoming calls
baic
SS-Code ::= '10011010'B
-- barring of all incoming calls
bicRoam
SS-Code ::= '10011011'B
-- barring of incoming calls when roaming outside home PLMN
-- Country
DN98628099
Issue 10-1 en
217 (264)
-- *plmn-specific* must not be used in version 1

allPLMN-specificSS
SS-Code ::= '11110000'B
callTransferRecall
SS-Code ::= '11110001'B
-- Call Transfer Recall
plmn-specificSS-2
SS-Code ::= '11110010'B
emoIn-mo-ick
SS-Code ::= '11110011'B
-- Mobile IN Categories
emoIn-mt-ick
SS-Code ::= '11110100'B
-- Mobile IN Categories
inService
SS-Code ::= '11110101'B
-- CORE INAP
homeArea
SS-Code ::= '11110110'B
-- Charging Based on Home Area
hotBilling
SS-Code ::= '11110111'B
-- Hot Billing
pnpService
SS-Code ::= '11111000'B
-- Mobile Centrex
rdiService
SS-Code ::= '11111001'B
-- Automatic Call Redirection
collectCallRestriction SS-Code ::= '11111001'B
-- Automatic Collect Call Functionality
ussdBarred
SS-Code ::= '11111101'B
-- USSD Barring based on PLMN specific SS code
plmn-specificSS-A
SS-Code ::= '11111010'B
plmn-specificSS-B
SS-Code ::= '11111011'B
plmn-specificSS-C
SS-Code ::= '11111100'B
plmn-specificSS-D
SS-Code ::= '11111101'B
plmn-specificSS-E
SS-Code ::= '11111110'B
plmn-specificSS-F
SS-Code ::= '11111111'B
allCallPrioritySS
SS-Code ::= '10100000'B
-- all call priority SS
emlpp
SS-Code ::= '10100001'B
-- enhanced Multilevel Precedence Pre-emption (EMLPP) service
allLCSPrivacyException SS-Code ::= '10110000'B
-- all LCS Privacy Exception Classes
universal
SS-Code ::= '10110001'B
-- allow location by any LCS client
callSessionRelated
SS-Code ::= '10110010'B
-- allow location by any value added LCS client to which a call/session
-- is established from the target MS
callSessionUnrelated
SS-Code ::= '10110011'B
-- allow location by designated external value added LCS clients
plmnoperator
SS-Code ::= '10110100'B
-- allow location by designated PLMN operator LCS clients
serviceType
SS-Code ::= '10110101'B
-- allow location by LCS clients of a designated LCS service type
maxNumOfSS
INTEGER ::= 30
SS-List ::= SEQUENCE SIZE (1..maxNumOfSS) OF

SS-Code
END
218 (264)
DN98628099
Issue 10-1 en
3.3.7
Short Message Service data types
MAP-SM-DataTypes
BEGIN
-- version 1:
RoutingInfoForSM-Arg ::= SEQUENCE {
msisdn
sm-RP-PRI
[1] BOOLEAN,
[2] AddressString,
-- cug-Interlock
[3] CUG-Interlock
OPTIONAL,
-- cug-Interlock parameter is not used
teleservice
[5] TeleserviceCode
OPTIONAL }
-- version 2:
RoutingInfoForSM-Arg::= SEQUENCE {
msisdn
sm-RP-PRI
[1] BOOLEAN,
[2] AddressString,
teleservice
[5] TeleserviceCode
OPTIONAL,
-- teleservice must be absent in version greater 1
...}
-- version 3:
RoutingInfoForSM-Arg::= SEQUENCE {
msisdn
sm-RP-PRI
[1] BOOLEAN,
[2] AddressString,
teleservice
[5] TeleserviceCode
OPTIONAL,
-- teleservice must be absent in version greater 1
extensionContainer
[7] NULL
OPTIONAL,
-- gprsSupportIndicator is set only if the SMS-GMSC supports
-- receiving of two numbers from the HLR
sm-RP-MTI
[8] SM-RP-MTI OPTIONAL,
sm-RP-SMEA
[9] SM-RP-SMEA OPTIONAL,
...}
-- version 1:
RoutingInfoForSM-Res::= SEQUENCE {
imsi
IMSI,
[0] LocationInfoWithLMSI,
mwd-Set
[2] BOOLEAN
OPTIONAL }
-- version 2:
imsi
IMSI,
mwd-Set
[2] BOOLEAN
OPTIONAL
-- mwd-Set must be absent in version greater 1 }
-- version 3:
DN98628099
Issue 10-1 en
219 (264)
imsi
IMSI,
mwd-Set
[2] BOOLEAN
OPTIONAL,
-- mwd-Set must be absent in version greater 1
extensionContainer
...}
SM-RP-MTI ::= INTEGER (0..10)
-- 0 SMS Deliver
-- 1 SMS Status Report
-- other values are reserved for future use and shall be discarded if
-- received
SM-RP-SMEA ::= OCTET STRING (SIZE (1..12))
-- this parameter contains an address field which is encoded
-- as defined in GSM 03.40. An address field contains 3 elements :
-address-length
-type-of-address
-address-value
-- version 1:
LocationInfoWithLMSI ::= SEQUENCE {
locationInfo
LocationInfo,
lmsi
LMSI
-- version 2:
locationInfo
LocationInfo,
lmsi
LMSI
...}
OPTIONAL }
OPTIONAL,
-- version 3:
locationInfo
LocationInfo,
lmsi
LMSI
OPTIONAL,
extensionContainer
gprsNodeIndicator
[5] NULL
OPTIONAL,
-- gprsNodeIndicator is set only if the SGSN number is sent as the
-- Network Node Number
additional-Number
[6] Additional-Number
OPTIONAL,
-- NetworkNode-number can be either msc-number or sgsn-number
...}
Additional-Number ::= CHOICE {
msc-Number
sgsn-Number
-- additional-number can be either msc-number or sgsn-number
-- if received networkNode-number is msc-number then the additional number
-- is sgsn-number
-- if received networkNode-number is sgsn-number then the additional number
-- is msc-number
}
-- version 1:
ForwardSM-Arg ::= SEQUENCE {
sm-RP-DA
SM-RP-DA,
220 (264)
DN98628099
Issue 10-1 en
sm-RP-OA
sm-RP-UI
SM-RP-OA,
SignalInfo }
-- version 2:
ForwardSM-Arg ::= SEQUENCE {
sm-RP-DA
sm-RP-OA
sm-RP-UI
moreMessagesToSend
forwardSM-ArgExt [PRIVATE 0]
...}
SM-RP-DA,
SM-RP-OA,
SignalInfo,
NULL
OPTIONAL,
MO-ForwardSM-ArgExt OPTIONAL,
-- version 3:
MO-ForwardSM-Arg ::= SEQUENCE {
sm-RP-DA
SM-RP-DA,
sm-RP-OA
SM-RP-OA,
sm-RP-UI
SignalInfo,
moreMessagesToSend NULL
OPTIONAL,
imsi
IMSI
OPTIONAL,
...}
-- version 3:
MT-ForwardSM-Arg ::= SEQUENCE {
sm-RP-DA
SM-RP-DA,
sm-RP-OA
SM-RP-OA,
sm-RP-UI
SignalInfo,
moreMessagesToSend NULL
OPTIONAL,
...}
-- version 1 and version 2 ForwardSM-Res is empty;
-- version 3:
ForwardSM-Res ::= SEQUENCE {
sm-RP-UI
SignalInfo
OPTIONAL,
...}
SM-RP-DA ::= CHOICE {
imsi
[0] IMSI,
lmsi
[1] LMSI,
roamingNumber
-- roaming number must not be used in version greater 1
serviceCentreAddressDA
[4] AddressString,
noSM-RP-DA
[5] NULL}
-- noSM-RP-DA must not be used in version 1
SM-RP-OA ::= CHOICE {
msisdn
[2]
serviceCentreAddressOA
[4]
noSM-RP-OA
[5]
-- noSM-RP-OA must not be
ISDN-AddressString,
AddressString,
NULL}
used in version 1
-- version 1:
SetMessageWaitingData-Arg ::= SEQUENCE {
msisdn
DN98628099
Issue 10-1 en
ISDN-AddressString,
AddressString }
221 (264)
-- version 2:
ReportSM-DeliveryStatusArg ::= SEQUENCE {
msisdn
ISDN-AddressString,
AddressString,
sm-DeliveryOutcome
SM-DeliveryOutcome OPTIONAL,
-- sm-DeliveryOutcome must be absent in version 1
-- sm-DeliveryOutcome must be present in version greater 1
...}
-- version 3:
ReportSM-DeliveryStatusArg ::= SEQUENCE {
msisdn
ISDN-AddressString,
AddressString,
sm-DeliveryOutcome
SM-DeliveryOutcome
OPTIONAL,
-- sm-DeliveryOutcome must be absent in version 1
-- sm-DeliveryOutcome must be present in version greater 1
[0] AbsentSubscriberDiagnosticSM OPTIONAL,
extensionContainer
OPTIONAL,
[2] NULL
OPTIONAL,
-- gprsSupportIndicator is set only if the SMS-GMSC
-- supports handling of two delivery outcomes
deliveryOutcomeIndicator
[3] NULL
OPTIONAL,
-- DeliveryOutcomeIndicator is set when the SM-DeliveryOutcome is for GPRS
additionalSM-DeliveryOutcome
[4] SM-DeliveryOutcome
OPTIONAL,
-- If received, additionalSM-DeliveryOutcome is for GPRS
additionalAbsentSubscriberDiagnosticSM [5]
AbsentSubscriberDiagnosticSM OPTIONAL,
-- If received, additionalAbsentSubscriberDiagnosticSM is for GPRS
...}
-- version 1 SetMessageWaitingData-Res is empty;
-- version 2:
ReportSM-DeliveryStatusRes ::= ISDN-AddressString
-- storedMSISDN
-- version 3:
ReportSM-DeliveryStatusRes ::= SEQUENCE {
storedMSISDN
ISDN-AddressString
extensionContainer
ExtensionContainer
...}
OPTIONAL,
OPTIONAL,
SM-DeliveryOutcome ::= ENUMERATED {

(0),
absentSubscriber
(1),
successfulTransfer
(2)}
NoteMSPresent ::= IMSI
-- version 1:
AlertServiceCentreArg ::= SEQUENCE {
msisdn
ISDN-AddressString,
AddressString }
-- version 2:
AlertServiceCentreArg ::= SEQUENCE {
222 (264)
DN98628099
Issue 10-1 en
msisdn
...}
ISDN-AddressString,
AddressString,
-- version 2:
InformServiceCentreArg ::= SEQUENCE {
storedMSISDN
ISDN-AddressString
mw-Status
MW-Status
...}
-- version 3:
InformServiceCentreArg ::= SEQUENCE {
storedMSISDN
ISDN-AddressString
mw-Status
MW-Status
extensionContainer
ExtensionContainer
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
-- version 2:
MW-Status ::= BIT STRING {
sc-AddressNotIncluded
(0),
mnrf-Set
(1),
mcef-Set
(2) } (SIZE (6))
-- version 3:
MW-Status ::= BIT STRING {
sc-AddressNotIncluded
(0),
mnrf-Set
(1),
mcef-Set
(2),
mnrg-Set
(3) } (SIZE (6..16))
-- bits 4 to 15 shall be ignored if received and not understood
-- version 2:
ReadyForSM-Arg ::= SEQUENCE {
imsi
[0] IMSI,
alertReason
AlertReason,
...}
-- version 3:
ReadyForSM-Arg ::= SEQUENCE {
imsi
[0] IMSI,
alertReason
AlertReason,
alertReasonIndicator
NULL OPTIONAL,
-- alertReasonIndicator is set only when the alertReason
-- sent to HLR is for GPRS
...}
-- version 2 ReadyForSM-Res is empty;
-- version 3:
ReadyForSM-Res ::= SEQUENCE {
...}
AlertReason ::= ENUMERATED {
DN98628099
Issue 10-1 en
223 (264)
ms-Present
(0),
memoryAvailable (1)}
END
3.3.8
Error data types
MAP-ER-DataTypes
BEGIN
RoamingNotAllowedParam ::= SEQUENCE {
roamingNotAllowedCause RoamingNotAllowedCause,
...}
RoamingNotAllowedCause ::= ENUMERATED {
(0),
operatorDeterminedBarring
(3)}
CallBarredParam ::= CHOICE {
callBarringCause
CallBarringCause,
-- call BarringCause must not be used in version 3
extensibleCallBarredParam
ExtensibleCallBarredParam
-- extensibleCallBarredParam must not be used in version <3
}
CallBarringCause ::= ENUMERATED {
barringServiceActive
(0),
operatorBarring
(1)}
ExtensibleCallBarredParam ::= SEQUENCE {
callBarringCause
CallBarringCause
OPTIONAL,
extensionContainer
unauthorisedMessageOriginator [1] NULL
OPTIONAL,
...}
CUG-RejectParam ::= SEQUENCE {
cug-RejectCause CUG-RejectCause OPTIONAL,
...}
CUG-RejectCause ::= ENUMERATED {
incomingCallsBarredWithinCUG
(0),
subscriberNotMemberOfCUG
(1),
requestedBasicServiceViolatesCUG-Constraints
(5),
calledPartySS-InteractionViolation
(7)}
-- calledPartySS-InteractionViolation must not be used in
-- version 1
SS-IncompatibilityCause
ss-Code
[1]
basicService
ss-Status
[4]
...}
224 (264)
::= SEQUENCE {
SS-Code
BasicServiceCode
SS-Status
OPTIONAL,
OPTIONAL,
OPTIONAL,
DN98628099
Issue 10-1 en
PW-RegistrationFailureCause
undetermined
invalidFormat
newPasswordsMismatch
::= ENUMERATED {
(0),
(1),
(2)}
SM-DeliveryFailureCause ::= CHOICE {

sm-DelivFailCauseWithDiagnostic SM-DeliveryFailureCauseWithDiagnostic,
-- SM-DeliveryFailureCauseWithDiagnostic must not be used in
-- version 1
sm-EnumDelivFailCause
SM-EnumeratedDeliveryFailureCause }
-- SM-EnumeratedDeliveryFailureCause must not be used in version
-- greater 1
SM-EnumeratedDeliveryFailureCause ::= ENUMERATED {
(0),
equipmentProtocolError
(1),
equipmentNotSM-Equipped
(2),
unknownServiceCentre
(3),
sc-Congestion
(4),
invalidSME-Address
(5),
subscriberNotSC-Subscriber
(6)}
SM-DeliveryFailureCauseWithDiagnostic ::= SEQUENCE {
sm-EnumDelivFailCause
SM-EnumeratedDeliveryFailureCause,
diagnosticInfo
SignalInfo
OPTIONAL,
...}
Mwd-Set ::= BOOLEAN
BusySubscriberParam ::= SEQUENCE {
extensionContainer
ExtensionContainer
OPTIONAL,
ccbs-Possible
[0] NULL
OPTIONAL,
ccbs-Busy
[1] NULL
OPTIONAL,
...
}
-- BusySubscriberParam is for V3, but also used in
-- V1 and V2 with Feature 905, Support for IS-41 Interworking
AbsentSubscriberSM-Param ::= SEQUENCE {
AbsentSubscriberDiagnosticSM
-- AbsentSubscriberDiagnosticSM can be either for non-GPRS or
extensionContainer
ExtensionContainer
additionalAbsentSubscriberDiagnosticSM [0]
AbsentSubscriberDiagnosticSM OPTIONAL,
-- if received, additionalAbsentSubscriberDiagnosticSM is for
-- and absentSubscriberDiagnosticSM is for non-GPRS
...}
OPTIONAL,
for GPRS
OPTIONAL,
GPRS
AbsentSubscriberDiagnosticSM ::= INTEGER (0..255)

-- AbsentSubscriberDiagnosticSM values are defined in ETS 300 536 (GSM 03.40)
SystemFailureParam ::= CHOICE {
networkResource NetworkResource,
-- networkResource must not be used in version 3
extensibleSystemFailureParam
ExtensibleSystemFailureParam
DN98628099
Issue 10-1 en
225 (264)
-- extensibleSystemFailureParam must not be used in version <3

}
ExtensibleSystemFailureParam ::= SEQUENCE {
networkResource NetworkResource OPTIONAL,
...}
DataMissingParam ::= SEQUENCE {
...}
UnexpectedDataParam ::= SEQUENCE {
...}
FacilityNotSupParam ::= SEQUENCE {
...}
OR-NotAllowedParam ::= SEQUENCE {
...}
UnknownSubscriberParam ::= SEQUENCE {
extensionContainer
ExtensionContainer
unknownSubscriberDiagnostic
UnknownSubscriberDiagnostic
...}
OPTIONAL,
OPTIONAL,
UnknownSubscriberDiagnostic ::= ENUMERATED {

imsiUnknown
(0),
gprsSubscriptionUnknown
(1),
npdbMismatch
[2]}
-- if unknown values are received in
-- unknownSubscriberDiagnostic they shall be discarded
NumberChangedParam ::= SEQUENCE {
...}
UnidentifiedSubParam ::= SEQUENCE {
...}
IllegalSubscriberParam ::= SEQUENCE {
...}
IllegalEquipmentParam ::= SEQUENCE {
...}
BearerServNotProvParam ::= SEQUENCE {
...}
TeleservNotProvParam ::= SEQUENCE {
...}
TracingBufferFullParam ::= SEQUENCE {
...}
NoRoamingNbParam ::= SEQUENCE {
...}
AbsentSubscriberParam ::= SEQUENCE {
226 (264)
DN98628099
Issue 10-1 en
extensionContainer
absentSubscriberReason
...}
ExtensionContainer
[0] AbsentSubscriberReason
OPTIONAL,
OPTIONAL,
AbsentSubscriberReason ::= ENUMERATED {

imsiDetach
(0),
restrictedArea (1),
noPageResponse (2),
purgedMS
(3),
...}
-- exception handling: at reception of other values than the ones listed the
-- AbsentSubscriberReason shall be ignored.
NoSubscriberReplyParam ::= SEQUENCE {
...}
ForwardingViolationParam ::= SEQUENCE {
...}
ForwardingFailedParam ::= SEQUENCE {
...}
ATI-NotAllowedParam ::= SEQUENCE {
...}
SubBusyForMT-SMS-Param ::= SEQUENCE {
extensionContainer
gprsConnectionSuspended
NULL
OPTIONAL,
-- If GprsConnectionSuspended is not understood it shall be discarded
...}
MessageWaitListFullParam ::= SEQUENCE {
...}
IncompatibleTerminalParam ::= SEQUENCE {
...}
ShortTermDenialParam ::= SEQUENCE {
...}
LongTermDenialParam ::= SEQUENCE {
...}
ResourceLimitationParam ::= SEQUENCE {
...}
UnauthorizedLCSClient-Param ::= SEQUENCE {
unauthorizedLCSClient-Diagnostic [0]
UnauthorizedLCSClient-Diagnostic OPTIONAL,
extensionContainer
... }
OPTIONAL,
UnauthorizedLCSClient-Diagnostic ::= ENUMERATED {

noAdditionalInformation (0),
clientNotInMSPrivacyExceptionList (1),
callToClientNotSetup (2),
DN98628099
Issue 10-1 en
227 (264)
privacyOverrideNotApplicable (3),
disallowedByLocalRegulatoryRequirements (4),
...,
unauthorizedPrivacyClass (5),
unauthorizedCallSessionUnrelatedExternalClient (6),
unauthorizedCallSessionRelatedExternalClient (7) }
-- any unrecognized value shall be ignored
PositionMethodFailure-Param ::= SEQUENCE {
positionMethodFailure-Diagnostic [0]
PositionMethodFailure-Diagnostic OPTIONAL,
extensionContainer [1] ExtensionContainer
OPTIONAL,
... }
PositionMethodFailure-Diagnostic ::= ENUMERATED {
congestion
(0),
insufficientResources
(1),
insufficientMeasurementData
(2),
inconsistentMeasurementData
(3),
locationProcedureNotCompleted
(4),
locationProcedureNotSupportedByTargetMS
(5),
qoSNotAttainable
(6),
positionMethodNotAvailableInNetwork (7),
positionMethodNotAvailableInLocationArea (8),
... }
-- any unrecognized value shall be ignored
UnauthorizedRequestingNetwork-Param ::= SEQUENCE {
...}
UnknownOrUnreachableLCSClient-Param ::= SEQUENCE {
...}
MM-EventNotSupported-Param ::= SEQUENCE {
...}
TargetCellOutsideGCA-Param ::= SEQUENCE {
...}
END
3.3.9
Common data types
MAP-CommonDataTypes
BEGIN
TBCD-STRING ::= OCTET STRING (SIZE (1..50))
-- TBCD-STRING ::= OCTET STRING
-- This type (Telephony Binary Coded Decimal String) is used to
-- represent several digits from 0 through 9, *, #, a, b, c, two
228 (264)
DN98628099
Issue 10-1 en
------
digits per octet, each digit encoded 0000 to 1001 (0 to 9),

1010 (*), 1011 (#), 1100 (a), 1101 (b) or 1110 (c); 1111 used
as filler when there is an odd number of digits.
bits 8765 of octet n encoding digit 2n
bits 4321 of octet n encoding digit 2 (n-1) +1
AddressString ::= OCTET STRING (SIZE (1..maxAddressLength))

-- This type is used to represent a number for addressing
-- purposes. It is composed of
-a) one octet for nature of address, and numbering plan
-indicator.
-b) digits of an address encoded as TBCD-String.
-- a) The first octet includes a one bit extension indicator, a
-3 bits nature of address indicator and a 4 bits numbering
-plan indicator, encoded as follows:
-bit 8: 1
(no extension)
-bits 765: nature of address indicator
-000 unknown
-001 international number
-010 national significant number
-011 network specific number
-100 subscriber number
-101 reserved
-110 abbreviated number
-111 reserved for extension
-bits 4321: numbering plan indicator
-0000 unknown
-0001 ISDN/Telephony Numbering Plan (Rec CCITT E.164)
-0010 spare
-0011 data numbering plan (Rec CCITT X.121)
-0100 telex numbering plan (Rec CCITT F.69)
-0101 spare
-0110 land mobile numbering plan (REC CCITT E.212)
-0111 spare
-1000 national numbering plan
-1001 private numbering plan
-1111 reserved for extension
-all other values are reserved.
-- b) The following octets representing digits of an address
-encoded as a TBCD-STRING.
maxAddressLength INTEGER ::= 20
ISDN-AddressString ::= AddressString (SIZE (1..maxISDN-AddressLength))
-- This type is used to represent ISDN numbers.
maxISDN-AddressLength INTEGER ::= 9
FTN-AddressString ::= AddressString (SIZE (1..maxFTN-AddressLength))
-- This type is used to represent forwarded-to numbers.
maxFTN-AddressLength INTEGER ::= 15
ISDN-SubaddressString ::= OCTET STRING (SIZE (1..maxISDN-SubaddressLength))
-- This type is used to represent ISDN subaddresses.
-- It is composed of
DN98628099
Issue 10-1 en
229 (264)
---------------------------
a) one octet for type of subaddress and odd/even indicator.

b) 20 octets for subaddress information.
a) The first octet includes a one bit extension indicator, a
3 bits type of subaddress and a one bit odd/even indicator,
encoded as follows:
bit 8: 1
(no extension)
bits 765: type of subaddress
000 NSAP (X.213/ISO 8348 AD2)
010 User Specified
All other values are reserved
bit 4: odd/even indicator
0 even number of address signals
1 odd number of address signals
The odd/even indicator is used when the type of subaddress
is "user specified" and the coding is BCD.
bits 321: 000 (unused)
b) Subaddress information.
The NSAP X.213/ISO8348AD2 address shall be formatted as specified
by octet 4 which contains the Authority and Format Identifier
(AFI). The encoding is made according to the "preferred binary
encoding" as defined in X.213/ISO834AD2. For the definition
of this type of subaddress, see Rec. CCITT I.334.
For User-specific subaddress, this field is encoded according
to the user specification, subject to a maximum length of 20
octets. When interworking with X.25 networks BCD coding should
be applied.
maxISDN-SubaddressLength
INTEGER ::= 21
ExternalSignalInfo ::= SEQUENCE {

protocolId
ProtocolId,
signalInfo
SignalInfo,
ext [PRIVATE 0] HO-Ext OPTIONAL,
used in v2 ProcessAccessSignalling and PrepareSubsequentHO-result
...}
SignalInfo ::= OCTET STRING (SIZE (1..maxSignalInfoLength))
maxSignalInfoLength INTEGER ::= 200
-- This NamedValue represents the theoretical maximum number of octets which
-- is available to carry a single instance of the SignalInfo data type,
-- without requiring segmentation to cope with the network layer service.
-- However, the actual maximum size available for an instance of the data
-- type may be lower, especially when other information elements
-- have to be included in the same component.
ProtocolId ::= ENUMERATED {
gsm-0408
(1),
gsm-0806
(2),
gsm-BSSMAP
(3),
-- Value 3 must not be used in version 1 and
-- must not be used in version 2.
ets-300102-1
(4)}
Ext-ExternalSignalInfo ::= SEQUENCE {
ext-ProtocolId Ext-ProtocolId,
230 (264)
DN98628099
Issue 10-1 en
signalInfo
...}
SignalInfo,
Ext-ProtocolId ::= ENUMERATED {

ets-300356
(1),
...}
-- For Ext-ExternalSignalInfo sequences containing this parameter with any
-- Ext-ExternalSignalInfo sequence.
AlertingPattern ::= OCTET STRING (SIZE (1))
-- This type is used to represent Alerting Pattern
-- bits 8765 : 0000 (unused)
-- bits 43 : type of Pattern
-00 level
-01 category
-10 category
-all other values are reserved.
-- bits 21 : type of alerting
alertingLevel-1
AlertingPattern ::= '00000000'B
alertingLevel-2
alertingLevel-3
-- all other values of Alerting level are reserved
-- Alerting Levels are defined in GSM 02.07
alertingCategory-1
alertingCategory-2
alertingCategory-3
alertingCategory-4
alertingCategory-5
-- all other values of Alerting Category are reserved
-- Alerting categories are defined in GSM 02.07
AccessNetworkSignalInfo ::= SEQUENCE {
accessNetworkProtocolId AccessNetworkProtocolId,
signalInfo
LongSignalInfo,
...}
LongSignalInfo ::= OCTET STRING (SIZE (1..maxLongSignalInfoLength))
maxLongSignalInfoLength INTEGER ::= 2560
-- This Named Value represents the maximum number of octets which is
-- available to carry a single instance of the LongSignalInfo data type using
-- White Book SCCP with the maximum number of segments. It takes account of
-- the octets used by the lower layers of the protocol, and
-- other information elements which may be included in the same component.
AccessNetworkProtocolId ::= ENUMERATED {
ts3G-48006 (1),
ts3G-25413 (2),
...}
-- For AccessNetworkSignalInfo sequences containing this parameter with any
DN98628099
Issue 10-1 en
231 (264)
-- AccessNetworkSignalInfo sequence.
-- data types for numbering and identification
IMSI ::= TBCD-STRING (SIZE (3..8))
-- digits of MCC, MNC, MSIN are concatenated in this order.
TMSI ::= OCTET STRING (SIZE (1..4))
SubscriberId ::= CHOICE {
imsi
[0] IMSI,
tmsi
[1] TMSI}
IMEI ::= TBCD-STRING (SIZE (8))
-- The internal Structure is defined as follows:
-type approval code: 6 digits
-manufacturer place: 2 digits
-individual serial number: 6 digits
-unassigned: 1 digit
LocationInfo ::= CHOICE {
roamingNumber
-- roamingNumber must not be used in version greater 1
msc-Number
[1] ISDN-AddressString}
HLR-Id ::= IMSI
-- leading digits of IMSI, i.e. (MCC, MNC, leading digits of
-- MSIN) forming HLR Id defined in GSM 03.03.
HLR-List ::= SEQUENCE SIZE (1..maxNumOfHLR-Id) OF HLR-Id
maxNumOfHLR-Id
INTEGER ::= 50
LMSI ::= OCTET STRING (SIZE (4))

LCSClientExternalID ::= SEQUENCE {
externalAddress
... }
LCSClientInternalID ::= ENUMERATED {
broadcastService (0),
o-andM-HPLMN
(1),
o-andM-VPLMN
(2),
anonymousLocation (3),
targetMSsubscribedService (4),
... }
CellGlobalIdOrServiceAreaIdOrLAI ::= CHOICE {
cellGlobalIdOrServiceAreaIdFixedLength [0]
CellGlobalIdOrServiceAreaIdFixedLength,
laiFixedLength
[1] LAIFixedLength}
CellGlobalIdOrServiceAreaIdFixedLength ::= OCTET STRING (SIZE (7))
-- Refers to Cell Global Identification or Service Are Identification
-- defined in 3G TS 23.003.
232 (264)
DN98628099
Issue 10-1 en
------------
octet 1 bits 4321 Mobile Country Code 1st digit

bits 8765 Mobile Country Code 2nd digit
octet 2 bits 4321 Mobile Country Code 3rd digit
bits 8765 Mobile Network Code 3rd digit
or filler (1111) for 2 digit MNCs
octet 3 bits 4321 Mobile Network Code 1st digit
bits 8765 Mobile Network Code 2nd digit
octets 4 and 5 Location Area Code according to 3G TS 24.008
octets 6 and 7 Cell Identity (CI) value or
Service Area Code (SAC) value
according to 3G TS 23.003
LAIFixedLength ::= OCTET STRING (SIZE (5))

-- Refers to Location Area Identification defined in TS GSM 03.03.
-- octet 1 bits 4321 Mobile Country Code 1st digit
-bits 8765 Mobile Country Code 2nd digit
-- octet 2 bits 4321 Mobile Country Code 3rd digit
-bits 8765 Mobile Network Code 3rd digit
-- octet 3 bits 4321 Mobile Network Code 1st digit
-bits 8765 Mobile Network Code 2nd digit
-- octets 4 and 5 Location Area Code according to TS GSM 04.08
GlobalCellId ::= OCTET STRING (SIZE (5..7))
-- Refers to Cell Global Identification defined in TS GSM 03.03.
-- octet 1 bits 4321 Mobile Country Code 1st digit
-bits 8765 Mobile Country Code 2nd digit
-- octet 2 bits 4321 Mobile Country Code 3rd digit
-bits 8765 Mobile Network Code 3rd digit
-- octet 3 bits 4321 Mobile Network Code 1st digit
-bits 8765 Mobile Network Code 2nd digit
-- octets 4 and 5 Location Area Code according to TS GSM 04.08
-- octets 6 and 7 Cell Identity (CI) according to TS GSM 04.08
NetworkResource ::=
plmn
hlr
vlr
pvlr
controllingMSC
vmsc
eir
rss
ENUMERATED {
(0),
(1),
(2),
(3),
(4),
(5),
(6),
(7)}
NAEA-PreferredCI ::= SEQUENCE {

naea-PreferredCIC
[0] NAEA-CIC,
...}
NAEA-CIC ::= OCTET STRING (SIZE (3))
-- The internal structure is defined by the Carrier Identification
-- parameter in ANSI T1.113.3. Carrier codes between "000" and "999" may
-- be encoded as 3 digits using "000" to "999" or as 4 digits using
-- "0000" to "0999". Carrier codes between "1000" and "9999" are encoded
DN98628099
Issue 10-1 en
233 (264)
-- using 4 digits
-- data types for CAMEL
CellIdOrLAI ::= CHOICE {
cellIdFixedLength
laiFixedLength
[0] CellIdFixedLength,
[1] LAIFixedLength}
CellIdFixedLength ::= OCTET STRING (SIZE (7))

-- Refers to Cell Global Identification defined in
-- Octets are coded according to TS GSM 04.08.
-Mobile Country Code:
3 digits according
-1 digit filler (1111)
-Mobile Network Code:
2 digits according
-Location Area Code:
2 octets according
-Cell Identity: 2 octets (CI) according to
TS GSM 03.03.
to CCITT Rec E.212

to CCITT Rec E.212
to TS GSM 04.08
TS GSM 04.08
-- data types for subscriber management

Category ::= OCTET STRING (SIZE (1))
-- The internal structure is defined in CCITT Rec Q.763.
BearerServiceList ::= SEQUENCE SIZE (1..maxNumOfBearerServices) OF
Ext-BearerServiceCode
maxNumOfBearerServices
INTEGER ::= 50
TeleserviceList ::= SEQUENCE SIZE (1..maxNumOfTeleservices) OF

Ext-TeleserviceCode
maxNumOfTeleservices
INTEGER ::= 20
BasicServiceCode ::= CHOICE {

bearerService
[2] BearerServiceCode,
teleservice
[3] TeleserviceCode}
Ext-BasicServiceCode ::= CHOICE {
ext-BearerService
[2] Ext-BearerServiceCode,
ext-Teleservice
[3] Ext-TeleserviceCode}
EMLPP-Info ::= SEQUENCE {
maximumentitledPriority EMLPP-Priority,
defaultPriority
EMLPP-Priority,
extensionContainer
...}
EMLPP-Priority ::= INTEGER (0..15)
-- The mapping from the values A,B,0,1,2,3,4 to the integer-value is
-- specified as follows where A is the highest and 4 is the lowest
-- priority level
-- the integer values 7-15 are spare and shall be mapped to value 4
priorityLevelA
priorityLevelB
priorityLevel0
EMLPP-Priority ::= 6
234 (264)
DN98628099
Issue 10-1 en
priorityLevel1
priorityLevel2
priorityLevel3
priorityLevel4
EMLPP-Priority
EMLPP-Priority
EMLPP-Priority
EMLPP-Priority
::=
::=
::=
::=
1
2
3
4
BasicServiceList ::= SEQUENCE SIZE (1..maxNumOfBasicServices)

maxNumOfBasicServices
OF
INTEGER ::= 70
BasicServiceGroupList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF

BasicServiceCode
maxNumOfBasicServiceGroups
INTEGER ::= 13
TraceReference ::= OCTET STRING (SIZE (1..2))

TraceType ::= INTEGER (0..255)
-- Trace types are more fully defined in TS GSM 12.08.
CUG-Interlock ::= OCTET STRING (SIZE (4))
CUG-CheckInfo ::= SEQUENCE {
cug-Interlock
CUG-Interlock,
cug-OutgoingAccess NULL
...}
OPTIONAL,
ODB-Data ::= SEQUENCE {

odb-GeneralData ODB-GeneralData,
odb-HPLMN-Data ODB-HPLMN-Data OPTIONAL,
...}
ODB-GeneralData ::= BIT STRING {
allOG-CallsBarred
(0),
internationalOGCallsBarred
(1),
internationalOGCallsNotToHPLMN-CountryBarred
(2),
interzonalOGCallsBarred (6),
interzonalOGCallsNotToHPLMN-CountryBarred (7),
interzonalOGCallsAndInterzonalOGCallsNotToHPLMN-CountryBarred (8),
premiumRateInformationOGCallsBarred
(3),
premiumRateEntertainementOGCallsBarred
(4),
ss-AccessBarred
(5),
allECT-Barred (9),
chargeableECT-Barred (10),
internationalECT-Barred (11),
interzonalECT-Barred (12),
doublyChargeableECT-Barred (13),
multipleECT-Barred (14),
allPacketOrientedServicesBarred (15),
roamerAccessToHPLMN-AP-Barred (16),
roamerAccessToVPLMN-AP-Barred (17),
roamingOutsidePLMNOG-CallsBarred
(18),
allIC-CallsBarred
(19),
roamingOutsidePLMNIC-CallsBarred
(20),
roamingOutsidePLMNICountryIC-CallsBarred
(21),
roamingOutsidePLMN-Barred
(22),
DN98628099
Issue 10-1 en
235 (264)
roamingOutsidePLMN-CountryBarred
(23),
registrationAllCF-Barred
(24),
registrationCFNotToHPLMN-Barred
(25),
registrationInterzonalCF-Barred
(26),
registrationInterzonalCFNotToHPLMN-Barred
(27) } (SIZE (6..32))
-- exception handling: reception of unknown bit assignments in the
-- ODB-GeneralData type shall be treated like unsupported ODB-GeneralData
-- When the ODB-GeneralData type is removed from the HLR for a given
-- subscriber, in NoteSubscriberDataModified operation sent toward the
-- gsmSCF all bits shall be set to "O".
ODB-HPLMN-Data ::= BIT STRING {
plmn-SpecificBarringType1
(0),
(1),
(2),
(3)} (SIZE (4..32))
-- exception handling: reception of unknown bit assignments in the
-- ODB-HPLMN-Data type shall be treated like unsupported ODB-HPLMN-Data
MaxMC-Bearers ::= INTEGER (2..maxNumOfMC-Bearers)
MC-Bearers ::= INTEGER (1..maxNumOfMC-Bearers)
maxNumOfMC-Bearers
INTEGER ::= 7
Ext-SS-Status ::= OCTET STRING (SIZE (1..5))

-- OCTET 1:
-- bits 8765: 0000 (unused)
-- bits 4321: Used to convey the "P bit","R bit","A bit" and "Q bit",
-representing supplementary service state information
-as defined in TS GSM 03.11
-bit 4: "Q bit"
-bit 3: "P bit"
-bit 2: "R bit"
-bit 1: "A bit"
-- OCTETS 2-5: reserved for future use. They shall be discarded if
-- received and not understood.
ASCI-CallReference ::= TBCD-STRING (SIZE (1..8))
-- digits of VGCS/VBC-area,Group-ID are concatenated in this order.
END
3.3.10
Teleservice codes
MAP-TS-Code
DEFINITIONS ::=
BEGIN
TeleserviceCode ::=
-- This type is
-- teleservice,
-- services are
236 (264)
OCTET STRING (SIZE (1))

used to represent the code identifying a single
a group of teleservices, or all teleservices. The
defined in GSM 02.03.
DN98628099
Issue 10-1 en

-- bits 87654321: group (bits 8765) and specific service
-- (bits 4321)
Ext-TeleserviceCode ::= OCTET STRING (SIZE (1..5))
-- teleservice, a group of teleservices, or all teleservices. The
-- services are defined in TS GSM 02.03.
-- OCTET 1:
-- bits 87654321: group (bits 8765) and specific service
-- (bits 4321)
-- OCTETS 2-5: reserved for future use. If received the
-- Ext-TeleserviceCode shall be
-- treated according to the exception handling defined for the
-- operation that uses this type.
-- Ext-TeleserviceCode includes all values defined for TeleserviceCode.
allTeleservices
TeleserviceCode ::= '00000000'B
allSpeechTransmissionServices
telephony
emergencyCalls

allShortMessageServices
shortMessageMT-PP
shortMessageMO-PP

allFacsimileTransmissionServices
facsimileGroup3AndAlterSpeech
automaticFacsimileGroup3
facsimileGroup4
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
::=
::=
::=
::=
'01100000'B
'01100001'B
'01100010'B
'01100011'B
-- The following non-hierarchical Compound Teleservice Groups

-- are defined in TS GSM 02.30:
allDataTeleservices
-- covers Teleservice Groups 'allFacsimileTransmissionServices'
-- and 'allShortMessageServices'
allTeleservices-ExeptSMS
-- covers Teleservice Groups 'allSpeechTransmissionServices' and
-- 'allFacsimileTransmissionServices'
-----
Compound Teleservice Group Codes are only used in call

independent supplementary service operations, i.e. they
are not used in InsertSubscriberData or in
DeleteSubscriberData messages.
allVoiceGroupCallServices
voiceGroupCall
voiceBroadcastCall

allPLMN-specificTS
plmn-specificTS-1
plmn-specificTS-2
plmn-specificTS-3
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
DN98628099
Issue 10-1 en
::=
::=
::=
::=
'11010000'B
'11010001'B
'11010010'B
'11010011'B
237 (264)
plmn-specificTS-4
plmn-specificTS-5
plmn-specificTS-6
plmn-specificTS-7
plmn-specificTS-8
plmn-specificTS-9
plmn-specificTS-A
plmn-specificTS-B
plmn-specificTS-C
plmn-specificTS-D
plmn-specificTS-E
plmn-specificTS-F
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
TeleserviceCode
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
'11010100'B
'11010101'B
'11010110'B
'11010111'B
'11011000'B
'11011001'B
'11011010'B
'11011011'B
'11011100'B
'11011101'B
'11011110'B
'11011111'B
END
3.3.11
Bearer Service codes
MAP-BS-Code
DEFINITIONS ::=
BEGIN
BearerServiceCode ::= OCTET STRING (SIZE (1))
-- bearer service, a group of bearer services, or all bearer
-- services. The services are defined in GSM 02.02.
--- v1: bit 8: Transparency indicator (If applicable)
-0
transparent (postfix T) or if not applicable
-(no postfix T or NT)
-1
non transparent (postfix NT)
--- v2: bit 8: 0 (unused)
-- plmn-specific bearer services:
-- bits 87654321: defined by the HPLMN operator
-- rest of bearer services:
--- bits 7654321: group (bits 7654), and rate, if applicable
-- (bits 321)
-- symbolic constants are assigned only for v2
Ext-BearerServiceCode ::= OCTET STRING (SIZE (1..5))
-- bearer service, a group of bearer services, or all bearer
-- services. The services are defined in TS GSM 02.02.
--- OCTET 1:
-- plmn-specific bearer services:
-- bits 87654321: defined by the HPLMN operator
--- rest of bearer services:
238 (264)
DN98628099
Issue 10-1 en
--------
bits 7654321: group (bits 7654), and rate, if applicable

(bits 321)
OCTETS 2-5: reserved for future use. If received the
Ext-TeleserviceCode shall be
treated according to the exception handling defined for the
operation that uses this type.
Ext-BearerServiceCode includes all values defined for BearerServiceCode.
allBearerServices
BearerServiceCode ::= '00000000'B
allDataCDA-Services
dataCDA-300bps
dataCDA-1200bps
dataCDA-1200-75bps
dataCDA-2400bps
dataCDA-4800bps
dataCDA-9600bps
general-dataCDA
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
::=
::=
::=
::=
::=
::=
::=
::=
'00010000'B
'00010001'B
'00010010'B
'00010011'B
'00010100'B
'00010101'B
'00010110'B
'00010111'B
allDataCDS-Services
dataCDS-1200bps
dataCDS-2400bps
dataCDS-4800bps
dataCDS-9600bps
general-dataCDS
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
::=
::=
::=
::=
::=
::=
'00011000'B
'00011010'B
'00011100'B
'00011101'B
'00011110'B
'00011111'B
allPadAccessCA-Services
padAccessCA-300bps
padAccessCA-1200bps
padAccessCA-1200-75bps
padAccessCA-2400bps
padAccessCA-4800bps
padAccessCA-9600bps
general-padAccessCA
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
::=
::=
::=
::=
::=
::=
::=
::=
'00100000'B
'00100001'B
'00100010'B
'00100011'B
'00100100'B
'00100101'B
'00100110'B
'00100111'B
allDataPDS-Services
dataPDS-2400bps
dataPDS-4800bps
dataPDS-9600bps
general-dataPDS
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
::=
::=
::=
::=
::=
'00101000'B
'00101100'B
'00101101'B
'00101110'B
'00101111'B
allAlternateSpeech-DataCDA
allAlternateSpeech-DataCDS
allSpeechFollowedByDataCDA
allSpeechFollowedByDataCDS
-- The following non-hierarchical Compound Bearer Service

-- Groups are defined in TS GSM 02.30:
allDataCircuitAsynchronous
-- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA" and
-- "allSpeechFollowedByDataCDA"
allAsynchronousServices BearerServiceCode ::= '01100000'B
-- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA",
DN98628099
Issue 10-1 en
239 (264)
-- "allSpeechFollowedByDataCDA" and "allPadAccessCDA-Services"

allDataCircuitSynchronous
-- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS" and
-- "allSpeechFollowedByDataCDS"
allSynchronousServices
-- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS",
-- "allSpeechFollowedByDataCDS" and "allDataPDS-Services"
-----
Compound Bearer Service Group Codes are only used in call

independent supplementary service operations, i.e. they
are not used in InsertSubscriberData or in
DeleteSubscriberData messages.
allPLMN-specificBS
plmn-specificBS-1
plmn-specificBS-2
plmn-specificBS-3
plmn-specificBS-4
plmn-specificBS-5
plmn-specificBS-6
plmn-specificBS-7
plmn-specificBS-8
plmn-specificBS-9
plmn-specificBS-A
plmn-specificBS-B
plmn-specificBS-C
plmn-specificBS-D
plmn-specificBS-E
plmn-specificBS-F
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
BearerServiceCode
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
'11010000'B
'11010001'B
'11010010'B
'11010011'B
'11010100'B
'11010101'B
'11010110'B
'11010111'B
'11011000'B
'11011001'B
'11011010'B
'11011011'B
'11011100'B
'11011101'B
'11011110'B
'11011111'B
END
3.3.12
Extension data types
MAP-Extensions
BEGIN
MAP-EXTENSION ::= CLASS {
&ExtensionType; OPTIONAL,
&extensionId;
OBJECT IDENTIFIER }
ExtensionContainer ::= SEQUENCE {
privateExtensionList
[0] PrivateExtensionList OPTIONAL,
pcs-Extensions
[1] PCS-Extensions
OPTIONAL,
...}
SLR-ArgExtensionContainer ::= SEQUENCE {
privateExtensionList
[0] PrivateExtensionList
OPTIONAL,
slr-Arg-PCS-Extensions [1] SLR-Arg-PCS-Extensions OPTIONAL,
...}
SLR-Arg-PCS-Extensions ::= SEQUENCE {
240 (264)
DN98628099
Issue 10-1 en
...,
na-ESRK-Request [0] NULL OPTIONAL }
maxNumOfPrivateExtensions
INTEGER ::= 10
PrivateExtensionList ::= SEQUENCE SIZE (1..maxNumOfPrivateExtensions) OF

PrivateExtension
ExtensionSet MAP-EXTENSION ::= {
{ &ExtensionType; IsdArgExt,
&extensionId;
{0 34 0} } |
{ &ExtensionType; DsdArgExt,
&extensionId;
{0 34 1} } |
{ &ExtensionType; UlResExt,
&extensionId;
{0 34 2} } |
{ &ExtensionType; SS-DataExtension,
&extensionId;
{0 34 4} } |
{ &ExtensionType; SriExtension,
&extensionId;
{0 34 5} } |
{ &ExtensionType; ExtraSignalInfo,
&extensionId;
{0 34 6} } |
{ &ExtensionType; SriResExtension,
&extensionId;
{0 34 7} } |
{ &ExtensionType; CanLocArgExt,
&extensionId;
{0 34 10} } |
{ &ExtensionType; ATMargExt,
&extensionId;
{0 34 11} } |
{ &ExtensionType; DTMargExt,
&extensionId;
{0 34 12} } |
{ &ExtensionType; NumberPorted,
&extensionId;
{0 34 13} } |
{ &ExtensionType; HO-Ext,
&extensionId;
{0 34 15} } |
{ &ExtensionType; ATMresExt,
&extensionId;
{0 34 16} } |
{ &ExtensionType; AbsentSubscriberExt,
&extensionId;
{0 34 17} } |
{ &ExtensionType; SriForSMArgExt,
&extensionId;
{0 34 18} } |
{ &ExtensionType; ReportSMDelStatArgExt, &extensionId;
{0 34 19} } |
{ &ExtensionType; UdlArgExt,
&extensionId;
{0 34 20} } |
{ &ExtensionType; RoamNotAllowedExt,
&extensionId;
{0 34 21} } |
{ &ExtensionType; MO-ForwardSM-ArgExt,
&extensionId;
{0 34 22} } |
{ &ExtensionType; ErrOlcmInfoTableExt,
&extensionId;
{0 34 23} } |
{ &ExtensionType; AnyTimeModArgExt,
&extensionId;
{0 34 26} } |
{ &ExtensionType; ExtensionType,
&extensionId;
{1 2 826 0 1249 58 1 0}
},
...}
-- ExtensionSet is the set of all defined private extensions
-- Unsupported private extensions shall be discarded if received.
PrivateExtension ::= SEQUENCE {
extId
MAP-EXTENSION.&extensionId;
({ExtensionSet}),
extType MAP-EXTENSION.&ExtensionType; ({ExtensionSet} {@extId}) OPTIONAL }
PCS-Extensions ::= SEQUENCE {
...}
RoutingCategory ::= OCTET STRING (SIZE (1))
-- value 0 means that RoutingCategory is released
maxNumOfActiveSS
INTEGER ::= 30
ActiveSS-List ::= OCTET STRING (SIZE (1..maxNumOfActiveSS))

ExtRoutingCategory ::= INTEGER (0..2147483647)
IsdArgExt ::= [PRIVATE 0] SEQUENCE {
alsLineIndicator
[0] NULL
routingCategory
[1] RoutingCategory
serviceList
[2] MAPserviceList
DN98628099
Issue 10-1 en
OPTIONAL,
OPTIONAL,
OPTIONAL,
241 (264)
serv-info-list
[3] ServiceListWithInfo OPTIONAL,
extRoutingCategory
[5] ExtRoutingCategory
OPTIONAL,
ownMSISDN
OPTIONAL,
...}
-- Note : additional routing category is removed from VLR by
-sending ISD with add-RC value zero (0).
DsdArgExt ::= [PRIVATE 0] SEQUENCE {
alsLineIndicator [0] NULL
OPTIONAL,
serviceList
[1] MAPserviceList OPTIONAL,
...}
UlResExt ::= [PRIVATE 0] SEQUENCE {
mwd-Set
[0] NULL
...}
OPTIONAL,
EmoInCategoryKey ::= TBCD-STRING (SIZE (1..3))

SS-DataEmoInExt ::= [PRIVATE 1] SEQUENCE {
emoInCategoryKey
[PRIVATE 2] EmoInCategoryKey OPTIONAL,
...}
InTriggerKey ::= INTEGER (1..65535)
PnpIndex ::= OCTET STRING (SIZE (3))
-- digits 0 through 9, two digits per octet,
-- each digit encoded 0000 to 0001,
-- 5 digits, 1111 used as filler for last digit.
CallRedirectionIndex ::= INTEGER (0..255)
ChargingArea ::= INTEGER (1..9999)
maxNumOfCA INTEGER ::= 3
ChargingAreaList ::= SEQUENCE SIZE (1..maxNumOfCA) OF
ChargingArea
RegionalChargingData ::= SEQUENCE {
chargingAreaList
[0] ChargingAreaList
...}
OPTIONAL,
SS-DataExtension ::= [PRIVATE 0] SEQUENCE {

inTriggerKey
[0] InTriggerKey
pnpIndex
[1] PnpIndex
callRedirectionIndex
[2] CallRedirectionIndex
regionalChargingData
[3] RegionalChargingData
...}
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
SriExtension ::= [PRIVATE 0] SEQUENCE {

callForwardingOverride
[0] NULL OPTIONAL,
in-Capability
[1] NULL OPTIONAL,
callingCategory
[2] CallingCategory OPTIONAL,
internalServiceIndicator
[3] InternalServiceIndicator OPTIONAL,
srbtSupportIndicator
[4] NULL OPTIONAL,
gmscSupportIndicator
[5] NULL OPTIONAL,
242 (264)
DN98628099
Issue 10-1 en
...}
CallingCategory ::= OCTET STRING (SIZE (1))
-- 'E9'hex used in SRI-arg
-- 'E8'hex used in SRI-res
InternalServiceIndicator ::= OCTET STRING (SIZE (1))
-- bits 8765: 0000 (unused)
-- bit 4: intelligent alerting
-- bit 3: parallel alerting
-- bit 2: member interrogation
-- bit 1: sequential alerting
-- 1 set
-- 0 not set
ExtraProtocolId ::= INTEGER { q763 (1)} (1..20)
ExtraSignalInfo ::= [PRIVATE 1] SEQUENCE {
protocolId ExtraProtocolId,
signalInfo SignalInfo }
CUG-CallInfo ::= OCTET STRING (SIZE (1..4))
-- xxxx xx00
- not used
-- xxxx xx01
- CUG call
-- xxxx xx10
- non CUG call
-- xxxx xx11
- maybe a CUG call
Nokia-CUG-Data ::= SEQUENCE {
cug-Interlock
[0] CUG-Interlock OPTIONAL,
cug-OutgoingAccess
[1] BOOLEAN
OPTIONAL,
cug-CallInfo
[2] CUG-CallInfo
OPTIONAL,
...}
-- cug-OutgoingAccess must be BOOLEAN (not NULL), because
-- it must be possible to transfer cug-CallInfo without
-- the other parameters
SriResExtension ::= [PRIVATE 0] SEQUENCE {
inTriggerKey
[0] InTriggerKey
vlrNumber
activeSs
[2] ActiveSS-List
traceReference
[3] TraceReference
traceType
[4] TraceType
omc-Id
[5] AddressString
hotBilling
[6] BOOLEAN
cfoIsDone
[7] BOOLEAN
cfInCug
[8] BOOLEAN
basicService
[9] BasicServiceCode
category
[10] Category
routingCategory
[11] RoutingCategory
pnpIndex
[12] PnpIndex
nokia-CUG
[13] Nokia-CUG-Data
noBarrings
[14] NULL
odb-Data
[15] ODB-Data
fraudData
[16] FraudData
extRoutingCategory
[17] ExtRoutingCategory
leaId
[18] LeaId
DN98628099
Issue 10-1 en
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
243 (264)
olcmInfoTable
callingCategory
commonMSISDN
rgData
...}
RgData ::= SEQUENCE {
noAnswerTimer
memberList
alertingMethod
userType
divertedToNbr
memberOfSuppression
ringbacktone
...}
[19]
[20]
[21]
[22]
[0]
[1]
[2]
[3]
[4]
[5]
[6]
OlcmInfoTable
CallingCategory
ISDN-AddressString
RgData
NoAnswerTimer
MemberList
AlertingMethod
UserType
ISDN-AddressString
NULL
NULL
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
NoAnswerTimer ::= OCTET STRING (SIZE (1))

MemberList ::= SEQUENCE SIZE (1..5) OF
ISDN-AddressString
AlertingMethod ::= OCTET STRING (SIZE (1))
-- '00' = sequential
-- '01' = parallel
-- '02' = sequential / parallel
-- '03' = intelligent
UserType ::= OCTET STRING (SIZE (1))
-- '00' = single
-- '01' = multiple
MAPserviceCode ::= OCTET STRING (SIZE (1))
picLock
prefCarrierId
mKey
smsKey
fraud-Data
cell-update
MAPserviceCode
MAPserviceCode
MAPserviceCode
MAPserviceCode
MAPserviceCode
MAPserviceCode
::=
::=
::=
::=
::=
::=
'00000001'B
'00000010'B
'00000011'B
'00000100'B
'00000101'B
'00000110'B
maxnumOfMAPservices INTEGER ::= 256

MAPserviceList ::= OCTET STRING (SIZE (0..maxnumOfMAPservices))
CarrierIdCode ::= OCTET STRING (SIZE (3))
-- the internal structure is defined in T1.113
PrefCarrierIdList ::= SEQUENCE {
prefCarrierIdCode1
[0] CarrierIdCode,
...}
ANSIIsdArgExt ::= [PRIVATE 30] SEQUENCE {
prefCarrierIdList
[0] PrefCarrierIdList
...}
OPTIONAL,
ANSISriResExt ::= [PRIVATE 30] SEQUENCE {
244 (264)
DN98628099
Issue 10-1 en
prefCarrierIdList
...}
[0] PrefCarrierIdList
OPTIONAL,
CanLocArgExt ::= [PRIVATE 0] SEQUENCE {

termination
[0] OCTET STRING (SIZE (1)) OPTIONAL,
...}
ATMargExt ::= [PRIVATE 0] SEQUENCE {
traceReference
[0] TraceReference
traceType
[1] TraceType
leaId
[2] LeaId
olcmInfoTable
[3] OlcmInfoTable
... }
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
LeaId ::= INTEGER (0..65535)

OlcmInfoTable ::= SEQUENCE SIZE (1..maxNumOfLEAs) OF
OlcmInfo
maxNumOfLEAs INTEGER ::= 7
OlcmInfo ::= SEQUENCE {
traceReference
[0] TraceReference,
traceType
[1] TraceType,
leaId
[2] LeaId OPTIONAL,
... }
ATMresExt ::= [PRIVATE 0] SEQUENCE {
olcmActive
[0] NULL OPTIONAL,
... }
DTMargExt ::= [PRIVATE 0] SEQUENCE {
traceType
[0] TraceType
OPTIONAL,
leaId
[1] LeaId
OPTIONAL,
... }
VersionInfo ::= OCTET STRING (SIZE (1))
-- 0000 0001 : version 1
maxNumOfServicesWithInfo INTEGER ::= 20
FraudInfo ::= SEQUENCE {
moc
[0] FraudData OPTIONAL,
cf
ct
...}
FraudData ::= SEQUENCE {
time
[0]
timeAction
[1]
maxCount
[2]
maxCountAction
[3]
...}
TimeLimit
ActionType
FraudMaxCount
ActionType
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
TimeLimit ::= INTEGER (0..64800)
DN98628099
Issue 10-1 en
245 (264)
ActionType ::= OCTET STRING (SIZE (1..10))

-- only 1st octet is used to transfer action type in M10
-- other octets are reserved for future use
FraudMaxCount ::= INTEGER (0..255)
ServiceWithInfo ::= SEQUENCE {
serviceCode
[0] MAPserviceCode
versionInfo
[1] VersionInfo
in-key
INKey
fraudInfo
FraudInfo
...}
OPTIONAL,
DEFAULT '1'B,
OPTIONAL,
OPTIONAL,
ServiceListWithInfo ::= SEQUENCE SIZE (1..maxNumOfServicesWithInfo) OF

ServiceWithInfo
INKey ::= CHOICE {
mobile-IN-key [2] MKey,
sms-IN-key
[3] SMSKey }
MmTdpName ::= OCTET STRING (SIZE (1..8))
-- bits 876543: 000000 (unused)
--- bit 2: Intra-VLR-Locup-DP
-- 1 DP is set
-- 0 DP is not set
--- bit 1: Inter-VLR-Locup-DP
-- 1 DP is set
-- 0 DP is not set
ServiceKey ::= INTEGER (0..2147483647)
-- 4 bytes
MKeyVer ::= OCTET STRING (SIZE (1))
-- 0000 0001 : version 1
LocupType ::= OCTET STRING (SIZE (1..8))
-- bits 87654: 00000 (unused)
--- bit 3: Normal-Locup
-- 1 LocupType is set (default)
-- 0 LocupType is not set
--- bit 2: Periodic-Locup
-- 1 LocupType is set
-- 0 LocupType is not set (default)
--- bit 1: IMSI-attach-Locup
-- 1 LocupType is set
-- 0 LocupType is not set (default)
MKey::= SEQUENCE {
mKeyVer
mmScfAddress
mmTdpName
246 (264)
[0]
[1]
[2]
MKeyVer
ISDN-AddressString
MmTdpName
DEFAULT '1'B,
OPTIONAL,
OPTIONAL,
DN98628099
Issue 10-1 en
serviceKey
[3] ServiceKey
OPTIONAL,
locupType
[4] LocupType
OPTIONAL,
...}
-- if mKeyVer parameter is missing, it is interpreted as
-- "version 1".
-- mmScfAddress, mmTtdpId and serviceKey parameters must be
-- present on version 1.
--- Feature 742 : IN Mobility Management
SmsTdpName ::= OCTET STRING (SIZE (1..8))
-- bits 87654: 00000 (unused)
--- bit 3: SR-SMS-DP
-- 1 DP is set
-- 0 DP is not set
--- bit 2: MO-SMS-DP
-- 1 DP is set
-- 0 DP is not set
--- bit 1: MT-SMS-DP
-- 1 DP is set
-- 0 DP is not set
SMSKey ::= SEQUENCE {
mmSCPAddress
[0]
smsTdpName
[1]
serviceKey
[2]
mmsFlag
[3]
...}
ISDN-AddressString
SmsTdpName
ServiceKey
NULL
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
NumberPorted ::= [PRIVATE 20] ENUMERATED {

notPorted
(0),
ported
(1),
...}
USSD-Extension ::= [PRIVATE 10] SEQUENCE {
routingCategory
[0] RoutingCategory
OPTIONAL,
cellId
[1] CellGlobalIdOrServiceAreaIdFixedLength OPTIONAL,
sai-Present
[2] NULL
OPTIONAL,
...}
HO-Ext ::= [PRIVATE 0]
map-Opt
[0]
codec-List
[1]
selected-Codec [2]
uma-access
[3]
uma-ip-address [4]
uma-ip-port-nb [5]
... }
SEQUENCE {
MapOptFields OPTIONAL,
CodecListExt
OPTIONAL,
SelectedCodec OPTIONAL,
NULL OPTIONAL,
OCTET STRING (SIZE (5..17)) OPTIONAL,
IPPortNb OPTIONAL,
MapOptFields ::= OCTET STRING (SIZE (1))

-- bit 6: codec
-- 1
set
DN98628099
Issue 10-1 en
247 (264)
-----------------
0
bit
1
0
bit
1
0
bit
1
0
bit
1
0
bit
1
0
not set
5: tfo_set
set
not set
4: tfo_not_set
set
not set
3: emerg
set
not set
2: usim
set
not set
1: sim
set
not set
CodecListExt ::= SEQUENCE (SIZE (0..maxNumOfCodec)) OF

CodecExt
maxNumOfCodec INTEGER ::= 8
CodecExt ::= OCTET STRING (SIZE (1))
SelectedCodec ::= SEQUENCE {
codec
[0] CodecExt,
modes
[1] Modes,
...}
Modes ::= OCTET STRING (SIZE (9))
IPPortNb ::= INTEGER (0..65535)
AbsentSubscriberExt ::= [PRIVATE 0] SEQUENCE {
imsi
[1] IMSI OPTIONAL,
...}
ErrOlcmInfoTableExt ::= [PRIVATE 0] SEQUENCE {
imsi
[1] IMSI OPTIONAL,
...}
ExtensionType ::= CHOICE {
isdArgType [1] IsdArgType,
isdResType [2] IsdResType,
dsdArgType [3] DsdArgType,
sriArgType [4] SriArgType,
sriResType [5] SriResType,
ulArgType
[7] ULArgType }
IsdArgType ::= SEQUENCE (SIZE (1..50)) OF
IsdArgData
IsdArgData ::= SEQUENCE {
privateFeatureCode
248 (264)
[1] PrivateFeatureCode
OPTIONAL,
DN98628099
Issue 10-1 en
privateFeatureData
...}
PrivateFeatureData
OPTIONAL,
PrivateFeatureCode ::= OCTET STRING (SIZE (1))

privateFeatureCode for STYPE has value '00000010'B
-- privateFeatureCode for OICK has value '00000110'B
-- privateFeatureCode for TICK has value '00000111'B
privateFeatureCode for CLI has value
'00001001'B
-- privateFeatureCode for ADD has value
'00001111'B
PrivateFeatureData ::= CHOICE {
oickInfo
subscriptionTypeInfo
OickInfo ::= SEQUENCE {
ss-Status
inCategoryKey
[7] OickInfo,
[3] SubscriptionTypeInfo }
Ext-SS-Status,
INCategoryKey }
INCategoryKey ::= TBCD-STRING (SIZE (1..3))

SubscriptionTypeInfo ::= SEQUENCE {
subscriptionType
SubscriptionType }
SubscriptionType ::= OCTET STRING (SIZE (1))
IsdResType ::= SEQUENCE (SIZE (1..50)) OF
IsdResData
IsdResData ::= SEQUENCE {
supportedPrivateFeature [1] PrivateFeatureCode OPTIONAL,
... }
DsdArgType ::= SEQUENCE (SIZE (1..50)) OF
DsdArgData
DsdArgData ::= SEQUENCE {
privateFeatureWithdraw
PrivateFeatureCode }
SriArgType ::= SEQUENCE (SIZE (1..50)) OF

SriArgData
SriArgData ::= SEQUENCE {
privateFeatureCode
extraNetworkInfo
... }
[2] ExtraSignalInfo
OPTIONAL,
OPTIONAL,
SriResType ::= SEQUENCE (SIZE (1..50)) OF

SriResData
SriResData ::= SEQUENCE {
privateFeatureCode
inCategoryKey
subscriptionType
... }
[2] INCategoryKey
[3] SubscriptionType
OPTIONAL,
OPTIONAL,
OPTIONAL,
UlArgType ::= SEQUENCE (SIZE (1..50)) OF
DN98628099
Issue 10-1 en
249 (264)
UlArgData
UlArgData ::= SEQUENCE {
privateFeatureCode
[1] PrivateFeatureCode OPTIONAL,
privateFeatureUlArgData PrivateFeatureUlArgData OPTIONAL,
... }
PrivateFeatureUlArgData ::= CHOICE {
adc [3] IMEI }
SriForSMArgExt ::= [PRIVATE
cfuSMSCounter
cfusmcfo
memberInterrogate
... }
0] SEQUENCE {
[0] CfuSMSCounter OPTIONAL,
[2] NULL OPTIONAL,
[3] NULL OPTIONAL,
ReportSMDelStatArgExt ::= [PRIVATE 0] SEQUENCE {

cfuSMSCounter
[0] CfuSMSCounter OPTIONAL,
cfusmcfo
[2] NULL OPTIONAL,
... }
CfuSMSCounter ::= OCTET STRING (SIZE (1))
MO-ForwardSM-ArgExt ::= [PRIVATE 0] SEQUENCE {
locationAreaCode [0] LocationAreaCode OPTIONAL,
... }
LocationAreaCode ::= OCTET STRING (SIZE (2))
-- octets 1 and 2 of LocationAreaCode according to 3GPP TS 24.008
UdlArgExt ::= [PRIVATE 0] SEQUENCE {
lai
[0] LAIFixedLength OPTIONAL,
sendImmResp [1] NULL
OPTIONAL,
... }
RoamNotAllowedExt ::= [PRIVATE 0] SEQUENCE {
rejectCause [0] OCTET STRING (SIZE (1)) OPTIONAL,
... }
AnyTimeModArgExt ::= [PRIVATE 0] SEQUENCE {
senderMSISDN [0] ISDN-AddressString OPTIONAL,
... }
CosInfo::= SEQUENCE {
ss-Code
SS-Code OPTIONAL,
cos-FeatureList COS-FeatureList }
COS-FeatureList ::= SEQUENCE SIZE (1..maxNumberOfCOSFeatures) OF
COS-Feature
maxNumberOfCOSFeatures INTEGER ::= 13
-- This reflects the number of basic service groups, and is
-- consistent with other features (i.e., Forwarding Features,
-- CallBarring Features, etc.).
COS-Feature ::= SEQUENCE {
250 (264)
DN98628099
Issue 10-1 en
basicServiceCode
ss-Status
customerGroupID
subGroupID
classOfServiceID
[4]
[5]
[6]
[7]
BasicServiceCode OPTIONAL,
SS-Status,
CustomerGroupID OPTIONAL,
SubGroupID OPTIONAL,
ClassOfServiceID OPTIONAL }
CustomerGroupID ::= BIT STRING {

formatIndicator (0),
idHighBit (8),
netidHighBit (16),
idLowBit (31) } (SIZE (32))
-- formatIndicator is encoded as follows:
-0 : International Format
-1 : Network Format
-- Bits 1-7 Unused (encoded as 0000000)
-- The remaining bits (3 octets) are the bit representation of the
-- Customer Group Identifier. All bits are significant.
SubGroupID ::= BIT STRING (SIZE (16))
ClassOfServiceID ::= BIT STRING {
formatIndicator (0),
idHighBit (8),
idLowBit (15) } (SIZE (16))
-- formatIndicator is encoded as follows:
-0 : International Format
-1 : Network Format
-- Bits 1-7 Unused (encoded as 0000000)
-- The remaining bits (one octet) is the bit representation of the
-- Class Of Service Identifier. All bits are significant.
END
3.3.13
Group Call data types

Not implemented.
3.3.14
Location Service data types
MAP-LCS-DataTypes
BEGIN
RoutingInfoForLCS-Arg ::= SEQUENCE {
mlcNumber
targetMS
extensionContainer
...}
RoutingInfoForLCS-Res ::= SEQUENCE {
targetMS
DN98628099
Issue 10-1 en
251 (264)
lcsLocationInfo
extensionContainer
v-gmlc-Address
h-gmlc-Address
ppr-Address
...}
[1]
[2]
[3]
[4]
[5]
LCSLocationInfo,
ExtensionContainer
GSN-Address
GSN-Address
GSN-Address
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
LCSLocationInfo ::= SEQUENCE {

networkNode-Number
ISDN-AddressString,
lmsi
[0] LMSI
OPTIONAL,
extensionContainer
gprsNodeIndicator
[2] NULL
OPTIONAL,
-- gprsNodeIndicator is set only if the SGSN number is sent
-- as the Network Node Number
additional-Number
[3] Additional-Number OPTIONAL,
...}
ProvideSubscriberLocation-Arg ::= SEQUENCE {
locationType
LocationType,
mlc-Number
ISDN-AddressString,
lcs-ClientID
[0] LCS-ClientID
privacyOverride
[1] NULL
imsi
[2] IMSI
msisdn
lmsi
[4] LMSI
imei
[5] IMEI
lcs-Priority
[6] LCS-Priority
lcs-QoS
[7] LCS-QoS
extensionContainer
...,
supportedGADShapes
[9] SupportedGADShapes
lcs-ReferenceNumber [10] LCS-ReferenceNumber
lcsServiceTypeID
[11] LCSServiceTypeID
lcsCodeword
[12] LCSCodeword
-- one of imsi or msisdn is mandatory
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL }
LocationType ::= SEQUENCE {

locationEstimateType [0] LocationEstimateType,
...,
deferredLocationEventType [1] DeferredLocationEventType OPTIONAL }
LocationEstimateType ::= ENUMERATED {
currentLocation (0),
currentOrLastKnownLocation (1),
initialLocation (2),
...,
activateDeferredLocation (3),
cancelDeferredLocation (4) }
-- a ProvideSubscriberLocation-Arg containing an unrecognized
-- LocationEstimateType shall be rejected by the receiver with
-- a return error cause of unexpected data value
DeferredLocationEventType ::= BIT STRING {
msAvailable (0) } (SIZE (1..16))
252 (264)
DN98628099
Issue 10-1 en
-- a ProvideSubscriberLocation-Arg containing other values than listed above

-- in DeferredLocationEventType shall be rejected by the receiver with a
-- return error cause of unexpected data value.
LCS-ClientID ::= SEQUENCE {
lcsClientType
[0] LCSClientType,
lcsClientExternalID
[1] LCSClientExternalID
lcsClientDialedByMS
[2] AddressString
lcsClientInternalID
[3] LCSClientInternalID
lcsClientName
[4] LcsClientName
...,
lcsAPN
[5] APN
lcsRequestorID
[6] LCSRequestorID
LCSRequestorID ::= SEQUENCE
dataCodingScheme
[0]
requestorIDString
[1]
...,
lcs-FormatIndicator [2]
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL }
{
RequestorIDString,
LCS-FormatIndicator OPTIONAL }
RequestorIDString ::= USSD-String (SIZE (1..maxRequestorIDStringLength))

maxRequestorIDStringLength
INTEGER ::= 63
LCSClientType ::= ENUMERATED {

emergencyServices
(0),
valueAddedServices
(1),
plmnOperatorServices
(2),
lawfulInterceptServices (3),
...}
-- unrecognized value shall be treated as unexpected data by a receiver
-- a return error shall then be returned if received in a MAP invoke
LCSClientName ::= SEQUENCE {
dataCodingScheme
[0] USSD-DataCodingScheme,
nameString
[2] NameString,
...,
lcs-FormatIndicator [3] LCS-FormatIndicator OPTIONAL }
-- The USSD-DataCodingScheme shall indicate use of the default alphabet
-- through the following encoding
-- bit 7 6 5 4 3 2 1 0
-0 0 0 0 1 1 1 1
NameString ::= USSD-String (SIZE (1..maxNameStringLength))
maxNameStringLength INTEGER ::= 63
LCS-FormatIndicator ::= ENUMERATED {
logicalName
(0),
e-mailAddress (1),
msisdn
(2),
url
(3),
sipUrl
(4),
... }
DN98628099
Issue 10-1 en
253 (264)
LCS-Priority ::= OCTET STRING (SIZE (1))

-- 0 = highest priority
-- 1 = normal priority
-- all other values treated as 1
LCS-QoS ::= SEQUENCE {
horizontal-accuracy
verticalCoordinateRequest
vertical-accuracy
responseTime
extensionContainer
...}
[0]
[1]
[2]
[3]
[4]
Horizontal-Accuracy
NULL
Vertical-Accuracy
ResponseTime
ExtensionContainer
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
Horizontal-Accuracy ::= OCTET STRING (SIZE (1))

-- bit 8 = 0
-- bits 7-1 = 7 bit Uncertainty Code defined in 3G TS 23.032. The horizontal
-- location error should be less than the error indicated by the uncertainty
-- code with 67 % confidence
Vertical-Accuracy ::= OCTET STRING (SIZE (1))
-- bit 8 = 0
-- bits 7-1 = 7 bit Uncertainty Code defined in 3G TS 23.032.
-- The vertical location error should be less than the error indicated
-- by the uncertainty code with 67 % confidence
ResponseTime ::= SEQUENCE {
responseTimeCategory
ResponseTimeCategory,
...}
ResponseTimeCategory ::= ENUMERATED {
lowdelay
(0),
delaytolerant
(1),
...}
-- an unrecognized value shall be treated the same as value 1 (delaytolerant)
SupportedGADShapes ::= BIT STRING {
ellipsoidPoint (0),
ellipsoidPointWithUncertaintyCircle (1),
ellipsoidPointWithUncertaintyEllipse (2),
polygon (3),
ellipsoidPointWithAltitude (4),
ellipsoidPointWithAltitudeAndUncertaintyElipsoid (5),
ellipsoidArc (6) } (SIZE (7..16))
-- A node shall mark in the BIT STRING all Shapes defined in 3G TS 23.032 it
-- supports. Exception handling: bits 7 to 15 shall be ignored if received.
ProvideSubscriberLocation-Res ::= SEQUENCE {
locationEstimate
Ext-GeographicalInformation,
ageOfLocationEstimate
[0] AgeOfLocationInformation
OPTIONAL,
extensionContainer
OPTIONAL,
add-LocationEstimate
[2] Add-GeographicalInformation OPTIONAL,
deferredmt-lrResponseIndicator [3] NULL OPTIONAL,
geranPositioningData
[4] PositioningDataInformation OPTIONAL,
utranPositioningData
[5] UtranPositioningDataInfo
OPTIONAL,
cellIdOrSai
[6] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL,
254 (264)
DN98628099
Issue 10-1 en
sai-Present
[7] NULL
OPTIONAL,
...}
-- if deferredmt-lrResponseIndicator is set, locationEstimate is ignored
-- the add-LocationEstimate parameter shall not be sent to a node that did
-- not indicate the geographic shapes supported in
-- the ProvideSubscriberLocation-Arg
Ext-GeographicalInformation ::=
OCTET STRING (SIZE (1..maxExt-GeographicalInformation))
-- Refers to geographical Information defined in 3G TS 23.032.
-- This is composed of 1 or more octets with an internal structure according
-- to 3G TS 23.032
-- Octet 1: Type of shape, only the following shapes in 3G TS 23.032 are
-- allowed:
-(a) Ellipsoid point with uncertainty circle
-(b) Ellipsoid point with uncertainty ellipse
-(c) Ellipsoid point with altitude and uncertainty ellipsoid
-(d) Ellipsoid Arc
-(e) Ellipsoint Point
-- Any other value in octet 1 shall be treated as invalid
-- Octets 2 to 8 for case (a) - Ellipsoid point with uncertainty circle
3 octets
3 octets
-Uncertainty code
1 octet
-- Octets 2 to 11 for case (b) - Ellipsoid point with uncertainty ellipse:
3 octets
3 octets
-Uncertainty semi-major axis
1 octet
-Uncertainty semi-minor axis
1 octet
-Angle of major axis
1 octet
-Confidence
1 octet
-- Octets 2 to 14 for case (c) - Ellipsoid point with altitude and
-- uncertainty ellipsoid
3 octets
3 octets
-Altitude
2 octets
-Uncertainty semi-major axis
1 octet
-Uncertainty semi-minor axis
1 octet
-Angle of major axis
1 octet
-Uncertainty altitude
1 octet
-Confidence
1 octet
-- Octets 2 to 13 for case (d) - Ellipsoid Arc
3 octets
3 octets
-Inner radius
2 octets
-Uncertainty radius
1 octet
-Offset angle
1 octet
-Included angle
1 octet
-Confidence
1 octet
-- Octets 2 to 7 for case (e) - Ellipsoid Point
3 octets
3 octets
--- An Ext-GeographicalInformation parameter comprising more than one octet
-- and containing any other shape or an incorrect number of octets or coding
-- according to 3G TS 23.032 shall be treated as invalid data by a receiver.
DN98628099
Issue 10-1 en
255 (264)
---------
An Ext-GeographicalInformation parameter comprising one octet shall be

discarded by the receiver if an Add-GeographicalInformation parameter is
received in the same message.
An Ext-GeographicalInformation parameter comprising one octet shall be
treated as invalid data by the receiver if an Add-GeographicalInformation
parameter is not received in the same message.
maxExt-GeographicalInformation INTEGER ::= 20

-- the maximum length allows for further shapes in 3G TS 23.032 to be
-- included in later versions of 3G TS 23.032
PositioningDataInformation ::=
OCTET STRING (SIZE (2..maxPositioningDataInformation))
-- Refers to the Positioning Data defined in 3GPP TS 49.031.
-- to 3GPP TS 49.031.
maxPositioningDataInformation INTEGER ::= 10
UtranPositioningDataInfo ::= OCTET STRING (SIZE (3..maxUtranPositioningDataInfo))
-- Refers to the Position Data defined in 3GPP TS 25.413.
-- This is composed of the positioningDataDiscriminator and the
-- positioningDataSet included in positionData as defined in 3GPP TS 25.413.
maxUtranPositioningDataInfo INTEGER ::= 11
Add-GeographicalInformation ::=
-- OCTET STRING (SIZE (1..maxAdd-GeographicalInformation))
-- Refers to geographical Information defined in 3G TS 23.032.
-- to 3G TS 23.032
-- Octet 1: Type of shape, all the shapes defined in 3G TS 23.032 are allowed
-- Octets 2 to n (where n is the total number of octets necessary to encode
-- the shape according to 3G TS 23.032) are used to encode the shape itself
-- in accordance with the encoding defined in 3G TS 23.032
--- An Add-GeographicalInformation parameter, whether valid or invalid,
-- received together with a valid Ext-GeographicalInformation parameter in
-- the same message shall be discarded.
--- An Add-GeographicalInformation parameter containing any shape not defined
-- in 3G TS 23.032 or an incorrect number of octets or coding according to
-- 3G TS 23.032 shall be treated as invalid data by a receiver if not
-- received together with a valid Ext-GeographicalInformation parameter in
-- the same message.
maxAdd-GeographicalInformation INTEGER ::= 91
-- the maximum length allows support for all the shapes currently defined
-- in 3G TS 23.032
SubscriberLocationReport-Arg ::= SEQUENCE {
lcs-Event
LCS-Event,
lcs-ClientID
LCS-ClientID,
lcsLocationInfo
LCSLocationInfo,
256 (264)
DN98628099
Issue 10-1 en
msisdn
OPTIONAL,
imsi
[1] IMSI
OPTIONAL,
imei
[2] IMEI
OPTIONAL,
na-ESRD
OPTIONAL,
na-ESRK
OPTIONAL,
locationEstimate
[5] Ext-GeographicalInformation OPTIONAL,
ageOfLocationEstimate
[6] AgeOfLocationInformation
OPTIONAL,
slr-ArgExtensionContainer [7] SLR-ArgExtensionContainer OPTIONAL,
add-LocationEstimate
[8] Add-GeographicalInformation OPTIONAL,
deferredmt-lrData
[9] Deferredmt-lrData
OPTIONAL,
lcs-ReferenceNumber
[10] LCS-ReferenceNumber
OPTIONAL,
geranPositioningData
[11] PositioningDataInformation OPTIONAL,
utranPositioningData
[12] UtranPositioningDataInfo
OPTIONAL,
cellIdOrSai
[13] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL,
h-gmlc-Address
[14] GSN-Address
OPTIONAL,
lcsServiceTypeID
[15] LCSServiceTypeID
OPTIONAL,
sai-Present
[17] NULL
OPTIONAL,
...}
-- one of msisdn or imsi is mandatory
-- a location estimate that is valid for the locationEstimate parameter
-- should be transferred in this parameter in preference to the
-- add-LocationEstimate the deferredmt-lrData parameter shall be included if
-- and only if the lcs-Event indicates a deferredmt-lrResponse.
Deferredmt-lrData ::= SEQUENCE {
deferredLocationEventType DeferredLocationEventType,
terminationCause
[0] TerminationCause OPTIONAL,
lcsLocationInfo
[1] LCSLocationInfo OPTIONAL,
...}
-- lcsLocationInfo may be included only if a terminationCause is present
-- indicating mt-lrRestart.
LCS-Event ::= ENUMERATED {
emergencyCallOrigination
(0),
emergencyCallRelease
(1),
mo-lr
(2),
...}
-- a SubscriberLocationReport-Arg containing an unrecognized LCS-Event
-- shall be rejected by a receiver with a return error cause of unexpected
-- data value
TerminationCause ::= ENUMERATED {
normal
(0),
errorundefined
(1),
internalTimeout
(2),
congestion
(3),
mt-lrRestart
(4),
privacyViolation (5),
... }
-- exception handling
-- an unrecognized value shall be treated the same as value 1 (errorundefined)
SubscriberLocationReport-Res ::= SEQUENCE {
extensionContainer
ExtensionContainer
...,
DN98628099
Issue 10-1 en
OPTIONAL,
257 (264)
na-ESRK
OPTIONAL }
LCS-ReferenceNumber::= OCTET STRING (SIZE (1))

LCSServiceTypeId ::= INTEGER (0..127)
-- the integer values 0-63 are reserved for Standard LCS service types
-- the integer values 64-127 are reserved for Non Standard LCS service types
emergencyServices
LCSServiceTypeId ::=
emergencyAlertServices
personTracking
fleetManagement
assetManagement
trafficCongestionReporting
roadsideAssistance
routingToNearestCommercialEnterprise
navigation
citySightseeing
localizedAdvertising
mobileYellowPages
-- The values of LCSServiceTypeId are defined according to 3G
0
1
2
3
4
5
6
7
8
9
10
11
TS 22.071.
LCSCodeword ::= SEQUENCE {

dataCodingScheme
[0] USSD-DataCodingScheme,
lcsCodewordString [1] LCSCodewordString,
...}
LCSCodewordString ::= USSD-String (SIZE (1..maxLCSCodewordStringLength))
maxLCSCodewordStringLength
INTEGER ::= 20
END
3.3.15
Secure transport data types

Not implemented.
258 (264)
DN98628099
Issue 10-1 en
Support protocol description

Mobile Application Part (MAP) uses the services of the Transaction
Capabilities Application Part (TCAP), Signalling Connection Control Part
(SCCP), and Message Transfer Part (MTP) underlying layers.
MAP requirements concerning the use of the underlying layers are
described in:
.
4.1
3GPP TS 29.002, Mobile Application Part (MAP) Specification,

Release 5.
TCAP
White Book ITU-T TCAP and ANSI TCAP are supported.
The operator can define which TCAP standard is used by MAP: ITU-T or
ANSI. When a MAP user initiates a new dialogue, MAP uses a network
entity address analysis to select the TCAP standard to be used. If no
analysis is defined for the destination address or if the analysis result does
not define a TCAP standard, MAP reads the TCAP standard from the
default setting, defined by the operator with the MAP Parameter Handling
MML commands.
According to the ANSI TCAP specifications, it is possible to send class 4
operations without an invoke ID. This feature is not supported in MAP. If an
operation invocation is received without an invoke ID, map-ProviderAbort
(Abnormal Dialogue) is returned.
When a TCAP message includes the DialoguePortion, the optional
parameter ProtocolVersion is present by default. As an optional feature,
the ProtocolVersion may be omitted, to reduce the length of TCAP level
data in the overall message with 4 bytes.
DN98628099
Issue 10-1 en
259 (264)
4.2
SCCP
White Book ITU-T SCCP (including Chinese variant with support for 24 bit
Signalling Point Codes), and ANSI SCCP are supported.
The operator can define which SCCP address format is used by MAP. The
address format is either GSM/UMTS 900/1800 network (ITU-T) or GSM/
UMTS 1900 network (ANSI). When a MAP user initiates a new dialogue,
MAP uses a network entity address analysis to select the SCCP address
format to be used. If no analysis is defined for the destination address or if
the analysis result does not define the SCCP address format, MAP reads
the SCCP address format from the default setting, defined by the operator
with the MAP Parameter Handling MML commands.
The GT indicator defines the Global Title (GT) address format in the SCCP
level. The GT indicator value 0100 is used in GSM/UMTS 900/1800
networks (ITU-T SCCP), which means that the GT includes the Translation
Type, Numbering Plan, Encoding Scheme, Nature of Address indicator
and digits. By default the Translation Type is set to zero value in GSM/
UMTS 900/1800. For some MAP operations special Translation Type
values can be used (see section Interface description). The GT indicator
value 0010 is used in GSM/UMTS 1900 networks (ANSI SCCP), which
means that the GT includes the Translation Type and the digits of the
address.
In outgoing dialogue initiation messages, and in dialogue confirmation
messages when the dialogue continues (the first response to a dialogue
initiation), the Calling Party Address (CgPA) is read from HLR
configuration. As an optional feature - Feature 1546: Multiple Own
Network Element Addresses, the CgPA digits may be modified, based on
the analysis of the subscriber's IMSI.
The SCCP layer can use a Signalling Point Code (SPC) as the destination
SCCP address even when the functional application and the MAP layer
uses a GT. This depends on the result of the GT analysis, and on other
SCCP level configuration.
On the SCCP level, the Called Party Address can be modified, to forward a
received message to another destination. The re-routing is based on the
SCCP level Called Party Address, Feature 1080: SRF in HLR.
All MAP messages are sent using SCCP class 0 (the transmitting order of
the messages is not important), except for the following messages which
are sent with SCCP class 1:
260 (264)
DN98628099
Issue 10-1 en
StatusReport result
SetReportingState argument
SendRoutingInformation result (when version 3 is used)
The default value of the return option is 'discard message on error' but it
can be set to 'return message on error'.
SCCP level segmentation is available as an operator option, and is
controlled by SCCP level configuration. The configuration is done
independently for each destination signalling point, with SCCP signalling
point parameters. When SCCP determines the message length, to see if
segmentation is needed, a space of 24 digits (12 bytes) is assumed for the
Called Party Address Global Title digits. This is to allow possible Global
Title modification later. For the other parts of the message, the actual
length is used in the total message length calculation. As an optional
feature, the actual CdPA length may be used in the message length
calculation, to enable the maximum possible amount of user data to be
transmitted without the need for segmentation.
4.3
MTP
ITU-T MTP (support for both 14 bit and 24 bit Signalling Point Codes),
ANSI MTP (support for 24 bit Signalling Point Codes) and Japanese MTP
(support for 16 bit Signalling Point Codes) are supported.
MTP may be replaced by the SIGTRAN protocol stack (M3UA, SCTP, IP)
to transfer SS#7 signalling traffic over IP networks.
DN98628099
Issue 10-1 en
261 (264)
262 (264)
DN98628099
Issue 10-1 en
References
References
DN98628099
Issue 10-1 en
1.
GSM 03.85, Closed User Group (CUG) Supplementary Services,

stage 2.
2.
GSM 09.02, Mobile Application Part (MAP) Specification, GSM

phase 1.
3.

phase 2.
4.

phase 2+, Release 97.
5.

phase 2+, Release 98.
6.

Release 99.
7.

Release 4.
8.

Release 5.
9.

Release 6.
10.

Release 7.
11.
Feature 143: EIR Functions, Full EIR, Feature Description.
12.
Feature 448: MAP Interface for SCP in HLR, Feature Description.
13.
Feature 503: Routing Categories, Feature Description.
14.
Feature 626: GSM Supplementary Services Phase 2 Extension,

Feature Description.
15.
Feature 703: On-Line Call Monitoring, Feature Description.
16.
Feature 777: Termination of Calls on MAP_cancel_location, Feature

Description.
263 (264)
264 (264)
17.
Feature 1048: Extended Handling for Subscriber Identity (MSISDN)

in the HLR, Feature Activation Manual.
18.
Feature 1080: SRF in HLR, Feature Description.
19.
Feature 1541: Same CLI for Multiple Subscribers, Feature

Description.
20.
Features 1545 and 1576: Sequential and Parallel Alerting, Feature

Description.
21.
Feature 1546: Multiple Own Network Element Addresses, Feature

Description.
22.
Feature 1547: SN and Subscription-based CLI inquiry, Feature

Description.
23.
Feature 1569: Support of Optimal Routing for Basic Call Cases,

Feature Description.
24.
Feature 1609: Follow Me, Feature Description.
DN98628099
Issue 10-1 en

HLR Eir MSC VLR SGSN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HLR Eir MSC VLR SGSN

Uploaded by

Copyright:

Available Formats

MSCDOCM14PDFCD

MSC/HLR, Rel. M14.0, Product Documentation,

# Nokia Siemens Networks