3GPP TS 29.120

3GPP TS 29.120 V5.0.
0 (2002-06)
Technical Specification
3rd Generation Partnership Project;

Technical Specification Group Core Network;
Mobile Application Part (MAP) specification for GLR
(Release 5)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this
Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
Release 1999 2 3GPP TS 29.120 V3.0.0 (2000-03)
Keywords
UMTS, network, SS7, MAP
3GPP
Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.
© 2002, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA,TTC).

All rights reserved.
3GPP
Release 1999 3 3GPP TS 29.120 V3.0.0 (2000-03)
Contents
Foreword.............................................................................................................................................................6
1 Scope.........................................................................................................................................................7
2 References.................................................................................................................................................7
3 Abbreviations............................................................................................................................................7
4 The entities and interfaces within the mobile network utilising the GLR................................................8
4.1 The entities of the mobile system..............................................................................................................................8
4.2 The Interfaces within the mobile services.................................................................................................................8
5 Overload and compatibility overview.......................................................................................................8
5.1 Overload control for MAP entities............................................................................................................................8
5.2 Compatibility.............................................................................................................................................................8
6 Requirements concerning the use of SCCP and TC.................................................................................9
6.1 Use of SCCP..............................................................................................................................................................9
6.1.1 SCCP Class..........................................................................................................................................................9
6.1.2 Sub-System Number (SSN).................................................................................................................................9
6.1.3 SCCP addressing..................................................................................................................................................9
6.2 Use of TC.................................................................................................................................................................11
7 General on MAP services........................................................................................................................12
7.1 Common MAP services...........................................................................................................................................12
7.1.1 MAP-U-ABORT service....................................................................................................................................12
8 Mobility services.....................................................................................................................................13
8.1 General.....................................................................................................................................................................13
8.2 Location Management services................................................................................................................................14
8.3 Authentication Management services.......................................................................................................................14
8.4 Subscriber management services..............................................................................................................................14
8.5 Fault recovery services............................................................................................................................................15
8.6 Subscriber Information services...............................................................................................................................15
9 Operation and maintenance services.......................................................................................................15
9.1 General.....................................................................................................................................................................15
9.2 MAP_SEND_IMSI service......................................................................................................................................15
10 Call handling services.............................................................................................................................16
10.1 General.....................................................................................................................................................................16
10.2 MAP_PROVIDE_ROAMING_NUMBER service.................................................................................................16
10.3 MAP_SET_REPORTING_STATE service.............................................................................................................16
10.4 MAP_STATUS_REPORT service..........................................................................................................................16
10.5 MAP_REMOTE_USER_FREE service..................................................................................................................16
11 Supplementary services related services.................................................................................................17
11.1 General.....................................................................................................................................................................17
11.2 MAP_REGISTER_SS service.................................................................................................................................17
11.3 MAP_ERASE_SS service........................................................................................................................................17
11.4 MAP_ACTIVATE_SS service................................................................................................................................17
11.5 MAP_DEACTIVATE_SS service...........................................................................................................................17
11.6 MAP_ INTERROGATE _SS service......................................................................................................................18
11.7 MAP_ REGISTER_PASSWORD service...............................................................................................................18
11.8 MAP_ GET_PASSWORD service..........................................................................................................................18
11.9 MAP_ PROCESS_UNSTRUCTURED_SS_REQUEST service............................................................................18
11.10 MAP_ UNSTRUCTURED_SS_REQUEST service..........................................................................................19
11.11 MAP_UNSTRUCTURED_SS_NOTIFY service..............................................................................................19
11.12 MAP_REGISTER_CC_ENTRY service...........................................................................................................19
3GPP
Release 1999 4 3GPP TS 29.120 V3.0.0 (2000-03)
11.13 MAP_ERASE_CC_ENTRY service..................................................................................................................19
12 Short message service management services..........................................................................................19

12.1 General.....................................................................................................................................................................19
12.2 MAP-READY-FOR-SM service.............................................................................................................................20
12.3 MAP-MT-FORWARD-SHORT-MESSAGE service..............................................................................................20
13 Network-Requested PDP Context Activation services...........................................................................20
13.1 General.....................................................................................................................................................................20
13.2 MAP_SEND_ROUTING_INFO_FOR_GPRS service...........................................................................................20
13.3 MAP_FAILURE_REPORT service.........................................................................................................................21
14 Void.........................................................................................................................................................21
15 Element of procedure..............................................................................................................................21
15.1 SDL descriptions......................................................................................................................................................21
16 Mapping onto TC services......................................................................................................................22
17 Abstract syntax of the MAP protocol......................................................................................................23
17.1 General.....................................................................................................................................................................23
17.2 Packages specifications............................................................................................................................................23
17.3 Application contexts................................................................................................................................................24
18 General on MAP user procedure.............................................................................................................25
19 Mobility procedures................................................................................................................................26
19.1 Location management Procedures............................................................................................................................26
19.1.1 Location updating..............................................................................................................................................28
19.1.2 Location Cancellation........................................................................................................................................42
19.1.3 Purge MS...........................................................................................................................................................48
19.2 Fault recovery procedures........................................................................................................................................53
19.2.1 RESET procedure..............................................................................................................................................53
19.2.2 VLR restoration: the restore data procedure in the GLR...................................................................................57
20 Operations and maintenance procedures.................................................................................................64
20.1 General.....................................................................................................................................................................64
20.2 Subscriber data management procedures.................................................................................................................64
20.2.1 General...............................................................................................................................................................64
20.2.2 Procedures in the GLR.......................................................................................................................................66
20.3 Subscriber Identity procedure..................................................................................................................................76
20.3.1 Subscriber identity procedure in the GLR.........................................................................................................77
21 Call handling procedures.........................................................................................................................80
21.1 General.....................................................................................................................................................................80
21.2 Retrieval of routing information..............................................................................................................................81
21.2.1 General...............................................................................................................................................................81
21.2.2 Process in the GLR to provide a roaming number.............................................................................................82
21.2.3 Process in the GLR to provide subscriber information......................................................................................85
21.3 Setting of Reporting State........................................................................................................................................88
21.3.1 General...............................................................................................................................................................88
21.3.2 Process in the GLR to set the reporting state.....................................................................................................88
21.4 Status Reporting.......................................................................................................................................................91
21.4.1 General...............................................................................................................................................................91
21.4.2 Process in the GLR for Status Reporting...........................................................................................................91
21.5 Remote User Free....................................................................................................................................................93
21.5.1 General...............................................................................................................................................................93
21.5.2 Process in the GLR for Remote User Free.........................................................................................................94
22 Supplementary services procedures........................................................................................................97
22.1 Functional supplementary service processes............................................................................................................97
22.1.1 Functional supplementary service process co-ordinator for GLR.....................................................................97
22.1.2 Call completion supplementary service process co-ordinator for GLR............................................................99
22.2 Registration procedure...........................................................................................................................................101
3GPP
Release 1999 5 3GPP TS 29.120 V3.0.0 (2000-03)
22.2.1 General.............................................................................................................................................................101
22.2.2 Procedures in the GLR.....................................................................................................................................102
22.3 Erasure procedure..................................................................................................................................................104

22.3.1 General.............................................................................................................................................................104
22.4 Activation procedure..............................................................................................................................................105
22.4.1 General.............................................................................................................................................................105
22.5 Deactivation procedure..........................................................................................................................................107
22.5.1 General.............................................................................................................................................................107
22.6 Interrogation procedure..........................................................................................................................................108
22.6.1 General.............................................................................................................................................................108
22.7 Password registration procedure............................................................................................................................108
22.7.1 General.............................................................................................................................................................108
22.8 Mobile Initiated USSD procedure.........................................................................................................................108
22.9 Network initiated USSD procedure.......................................................................................................................111
22.9.1 Procedure in the GLR.......................................................................................................................................111
22.10 Common macros for clause 22........................................................................................................................115
22.10.1 SS Password handling macros.........................................................................................................................115
22.11 Activation of a CCBS request..........................................................................................................................117
22.11.1 General.............................................................................................................................................................117
22.12 Deactivation of a CCBS request......................................................................................................................119
22.12.1 General.............................................................................................................................................................119
23 Short message service procedures.........................................................................................................123
23.1 General...................................................................................................................................................................123
23.2 The mobile terminated short message transfer procedure.....................................................................................123
23.2.1 Procedure in the Intermediate MSC.................................................................................................................123
23.3 The Short Message Alert procedure......................................................................................................................135
24 GPRS process description.....................................................................................................................138
24.1 General...................................................................................................................................................................138
24.2 Send Routing Information procedure....................................................................................................................138
24.2.1 Process in the GLR for Send Routing Information for GPRS.........................................................................138
24.2.2 Process in the IM-GSN for Send Routing Information for GPRS...................................................................139
24.3 Failure Report procedure.......................................................................................................................................142
24.3.1 Process in the GLR for Failure Report.............................................................................................................142
24.3.2 Process in the IM-GSN for Failure Report......................................................................................................143
25 General macro description.....................................................................................................................146
25.1 MAP open macros.................................................................................................................................................146
25.2 Macros to check the content of indication and confirmation primitives...............................................................146
25.3 Authentication processes........................................................................................................................................146
25.3.1 Process Obtain_Authentication_Sets_GLR......................................................................................................146
25.3.2 Process Authentication_Failure_Report_GLR..................................................................................................148
25.4 Short Message Alert procedures............................................................................................................................150
25.4.1 Subscriber_Present_GLR_AS_VLR process...................................................................................................150
25.4.2 The Mobile Subscriber is present.....................................................................................................................153
3GPP
Release 1999 6 3GPP TS 29.120 V3.0.0 (2000-03)
Foreword
This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
The present document specifies the signalling requirements and procedures used at network elements related to the
Gateway Location Register (GLR) for Mobile Application Part (MAP) within the 3GPP system. (i.e. the present
document specifies the delta against 3GPP TS 29.002.)
The contents of the present document are subject to continuing work within the TSG and may change following
formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG
with an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
Release 1999 7 3GPP TS 29.120 V3.0.0 (2000-03)
1 Scope
The present document describes the signalling requirements and procedures used at network elements related to the
GLR for MAP within the 3GPP system at the application level.
The present document gives the description of the systems needed only in the network utilising GLR as the delta
document against 3GPP TS 29.002.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
 References are either specific (identified by date of publication, edition number, version number, etc.)
or non-specific.
 For a specific reference, subsequent revisions do not apply.
 For a non-specific reference, the latest version applies.
[1] 3GPP TS 23.003: "Numbering, addressing and identification".
[2] 3GPP TS 23.007: "Restoration procedures".
[3] 3GPP TS 23.012: "Location registration procedures".
[4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)".
[5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[6] 3GPP TS 23.119: "Gateway Location Register (GLR) - stage2".
3 Abbreviations
For the purposes of the present document, the following abbreviations
apply: CCBS Completion of Call to Busy Subscriber

GLR Gateway Location Register
GPRS General Packet Radio
Service IM_GSN Intermediate GSN
IM_MSC Intermediate MSC
SGSN Serving GPRS support node
GGSN Gateway GPRS support
node
3GPP
Release 1999 8 3GPP TS 29.120 V3.0.0 (2000-03)
4 The entities and interfaces within the mobile network

utilising the GLR
4.1 The entities of the mobile system

The functional entities related to the GLR are described below. The description of each entity is detailed in 3GPP TS
23.119 (GLR stage2 specification). The other functional entities described in the present document (e.g. MSC, VLR,
and HLR) are specified in 3GPP TS 29.002.
- The Gateway location Register (GLR).
- The Intermediate MSC (IM-MSC).
- The Intermediate GSN (IM-GSN).
4.2 The Interfaces within the mobile services

The Interfaces related to the GLR are described below. The description of each interface is detailed in 3GPP TS 23.119
(GLR stage2 specification).
- Interface between the HLR and the GLR.
- Interface between the VLR and the GLR.
- Interface between the MSC and the IM_MSC.
- Interface between the SGSN and the GLR.
- Interface between the MSC and the GLR.
- Interface between the GLR and the IM_GSN.
5 Overload and compatibility overview
5.1 Overload control for MAP entities

The VLR and SGSN see the GLR as an HLR, and the HLR sees the GLR as a VLR or a SGSN. Therefore the GLR
shall behave like mobile entity as which the GLR is regarded. If overload of the GLR is detected, the responder may
ignore requests for certain MAP operations (see tables 5.1/1, 5.1/2 and 5.1/3 in 3GPP TS 29.002). The decision as to
which MAP Operations may be ignored is made by the MAP service provider and is based upon the priority of the
application context.
5.2 Compatibility
A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol
version used between two entities for supporting a MAP-user signalling procedure. The description of the version
negotiation mechanism is detailed in 3GPP TS 29.002.
3GPP
Release 1999 9 3GPP TS 29.120 V3.0.0 (2000-03)
6 Requirements concerning the use of SCCP and TC
6.1 Use of SCCP

The Mobile Application Part makes use of the services offered by the Signalling Connection Control Part of signalling
System No. 7. CCITT Blue Book or ITU-T (03/93) Recommendations Q.711 to Q.716 should be consulted for the full
specification of SCCP. In North America (World Zone 1) the national version of SCCP is used as specified in ANSI
T1.112.
6.1.1 SCCP Class

MAP will only make use of the connectionless classes (0 or 1) of the SCCP.
6.1.2 Sub-System Number (SSN)

The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are
addressed by sub-system numbers (SSNs). The SSN for MAP are specified in 3GPP TS 23.003 [1]. The specific SSN is
not needed for the GLR, IM_MSC, and IM_GSN.
6.1.3 SCCP addressing
6.1.3.1 Introduction
The format and coding of address parameters carried by SCCP are detailed in 3GPP TS 29.002.
The following subclauses describe the method of SCCP addressing appropriate for each entity both for the simple intra-
PLMN case and where an inter-PLMN communication is required. The following entities are considered for the GLR
additionally:
- the Gateway location Register (GLR);
- the Intermediate Mobile-services Switching Centre (IM_MSC);
- the Intermediate GPRS Support Node (IM_GSN).
6.1.3.2 The Gateway Location Register (GLR)
6.1.3.2.1 Addressed by the VLR

In the network utilising the GLR, when an MS that belongs to other PLMN registers in a VLR/SGSN, the VLR/SGSN
sees the GLR as the MS’s HLR. When initiating the update location dialogues, the VLR is able to address the GLR
based on the SPC of the GLR because of intra-PLMN signalling. And the VLR can address the GLR based on an E.214
Mobile Global Title originally derived by the VLR from the IMSI (when CCITT or ITU-T SCCP is used), or an E.212
number originally derived from IMSI (when ANSI SCCP is used, an IMSI). When answering with Global Title to the
VLR, the GLR shall insert its E.164 address in the Calling Party Address of the SCCP message containing the first
responding CONTINUE message. After that, the VLR can address the GLR based on an E.164 GLR address.
6.1.3.2.2 Addressed by the HLR

When a location updating dialogue initiated by a GLR has been successfully completed, the HLR sees the GLR as the
VLR. When initiating dialogues towards the VLR, the routeing information used by the HLR is derived from the E.164
VLR number received as a parameter of the MAP message initiating the update location dialogue, but in reality the HLR
addresses the GLR using the VLR number.
3GPP
Release 1999 10 3GPP TS 29.120 V3.0.0 (2000-03)
6.1.3.2.3 Addressed by the GMSC

In the case that the MS is served by the SGSN in the network utilising the GLR, the GMSC sees the GLR as the SGSN.
When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See 3GPP TS 23.003) shall be included
in the called party address. The routeing information used by the GMSC is derived from the E.164 SGSN number
received as a parameter of the MAP message initiating the forward short message procedure. But in reality the GMSC
addresses the GLR using the SGSN number.
6.1.3.2.4 Addressed by the IM-GSN

In the network utilising the GLR, the IM-GSN initiates the GPRS location information retrieval to the GLR. The IM-GSN
must have the value of the GLR address beforehand.
6.1.3.3 The Intermediate MSC (IM_MSC)
6.1.3.3.1 Addressed by the GMSC

When a short message for CS has to be routed to an MS, the GMSC addresses the MSC by an MSC identity received
from the HLR that complies with E.164 rules. But in reality the GMSC addresses the IM-MSC in the network utilising
the GLR.
6.1.3.3.2 Addressed by the GMLC

When a location request for a particular MS needs to be sent to the MS’s VMSC, the GMLC addresses the MSC using
an E.164 address received from the MS’s HLR. But in reality the GMLC addresses the IM-MSC in the network
utilising the GLR.
6.1.3.4 The Intermediate GSN (IM_GSN)

The IM-GSN provides routing of the Network-Requested PDP Context activation. If a Network-Requested PDP
Context activation fails, the GLR will alert the IM-GSN when the subscriber becomes reachable. The GLR will use the
E.164 IM-GSN number received as parameter of the MAP message reporting the failure.
6.1.3.5 Summary table

The following table summarises the SCCP address used for invoke operations. As a principle, within a PLMN either
an SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the
GT must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive the SPC.
For a response, the originating address passed in the invoke message is used as SCCP Called Party Address. For
extra-PLMN addressing the own E.164 entity address is used as SCCP Calling Party Address; for intra-PLMN
addressing an SPC derived from the entity number may be used instead. When using an SPC, the SPC may be
taken directly from MTP.
3GPP
Release 1999 11 3GPP TS 29.120 V3.0.0 (2000-03)
Table 6.1.3/1
to fixed HLR VLR MSC SGSN GGSN GLR IM-MSC IM-
from net GSN
work
fixed
network
home I:SPC/GT
location E:GT
register T:VLR NUMBER
visitor I:SPC/GT
location E:GT
register T:MGT
(outside World Zone
1)/MSISDN
(World Zone 1/)HLR
NUMBER
(note)
mobile- E:GT T:SGSN I:SPC/GT
services NUMBER E:GT
switching T:MSC
centre NUMBER
Serving I:SPC/GT
GPRS T:MGT/MSISDN/HL
Support R NUMBER
Node
Gateway Note1
GPRS
Support
Node
Gateway --- E:GT I:SPC/G --- I:SPC/G
Location T:MGT T T
register (outside T:VLR T:SGSN
World NUMBE NUMBE
Zone1)/MSISDN( R R
World Zone1/)
HLR NUMBER
(note)
Intermedia --- I:SPC/GT
te- T:MSC
MSC NUMBER
Intermedia --- I:SPC/GT
te- T:HLR
GSN NUMBER
I: Intra-PLMN E: Extra (Inter)-PLMN T: Address Type
GT: Global Title MGT: E.214 Mobile Global Title SPC: Signalling Point Code
NOTE 0: For initiating the location updating procedure and an authentication information retrieval from the HLR preceding it,
the VLR has to derive the HLR address from the IMSI of the MS. The result can be an SPC or an E.214 Mobile
Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World
Zone 1). When continuing the established update location dialogue (as with any other dialogue) the VLR must derive
the routeing information towards the HLR from the Calling Party Address received with the first responding
CONTINUE message until the dialogue terminating message is received.
For transactions invoked by the VLR after update location completion, the VLR may derive the information for
addressing the HLR from addresses received in the course of the update location procedure (MSISDN or HLR
number) or from the IMSI.
When invoking the Restore Data procedure and an authentication information retrieval from the HLR preceding it, the
VLR must derive the information for addressing the HLR from the address information received in association with
the roaming number request. This may be either the IMSI received as a parameter of the MAP message requesting the
Roaming Number or the Calling Party Address associated with the MAP message requesting the Roaming Number.
From VLR in, GLR as for T (address type) only HLR Number is used. VLR and HLR are because only the thing that
is belonging to same PLMN is thought.
NOTE1: The hatching part is the same part of 3GPP TS29.002.
6.2 Use of TC
Refer to the corresponding section in 3GPP TS 29.002.
3GPP
Release 1999 12 3GPP TS 29.120 V3.0.0 (2000-03)
7 General on MAP services

Refer to the corresponding section in 3GPP TS 29.002 with the exceptions described below.
7.1 Common MAP services

The following common services are used:
- MAP-OPEN service;
- MAP-CLOSE service;
- MAP-DELIMITER service;
- MAP-U-ABORT service;
- MAP-P-ABORT service;
- MAP-NOTICE service;
- MAP-SECURE-TRANSPORT-CLASS-1 service;
- MAP-SECURE-TRANSPORT-CLASS-4 service.
Replace the MAP-U-ABORT service as follows.
7.1.1 MAP-U-ABORT service

This service enables the service-user to request the MAP dialogue to be aborted. The service is an unconfirmed service
with service-primitives as shown in table 7.1/1. MAP service-user in the GLR may set “application context not
supported” as user reason.
Table 7.1/1: Service-primitives for the MAP-U-ABORT service
Parameters Request Indication

User reason M M(=)
Diagnostic information U C(=)
Specific information U C(=)
User reason:
This parameter can take the following values:
- resource limitation (congestion);
the requested user resource is unavailable due to congestion;
- resource unavailable;
the requested user resource is unavailable for reasons other than congestion;
- application procedure cancellation;
the procedure is cancelled for reason detailed in the diagnostic information parameter;
- application context not supported;
the requested application context is not supported;
3GPP
Release 1999 13 3GPP TS 29.120 V3.0.0 (2000-03)
- procedure error;
processing of the procedure is terminated for procedural reasons.
Diagnostic information:
This parameter may be used to give additional information for some of the values of the user-reason parameter:
Table 7.1/2: User reason and diagnostic information
User reason Diagnostic information

Resource limitation (congestion) -
Resource unavailable Short term/long term problem
Application procedure cancellation Handover cancellation/
Radio Channel release/
Network path release/ Call
release/
Associated procedure failure/ Tandem
dialogue released/ Remote operations
failure
Application context not supported -
Procedure error -
Specific information:
This parameter may be used for passing any user specific information. Establishment and processing of the Specific
information is not specified by GSM and shall be performed according to operator specific requirements.
8 Mobility services
8.1 General
Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The
interval for adoption for the GLR specification is described below. Service primitives and parameter definitions are as in
3GPP TS 29.002.
3GPP
Release 1999 14 3GPP TS 29.120 V3.0.0 (2000-03)
8.2 Location Management services
Services Interval for adoption
MAP_UPDATE_LOCATION VLR – GLR

GLR – HLR
MAP_CANCEL _LOCATION HLR – GLR
GLR – VLR
GLR – SGSN
MAP_PURGE_MS VLR – GLR
SGSN – GLR
GLR – HLR
MAP_UPDATE_GPRS_LOCATION SGSN – GLR

GLR – HLR
Figure 8.2 /1
8.3 Authentication Management services
MAP_SEND_AUTHENTICATION_IN VLR – GLR

FO
SGSN – GLR
GLR – HLR
MAP_AUTHENTICATION_FAILURE VLR – GLR
_REPORT
SGSN – GLR
GLR – HLR
Figure 8.3/1
8.4 Subscriber management services
MAP_ INSERT-SUBSCRIBER-DATA HLR – GLR

GLR – VLR
GLR – SGSN
MAP-DELETE-SUBSCRIBER-DATA HLR – GLR
GLR – VLR
GLR – SGSN
Figure 8.4/1
3GPP
Release 1999 15 3GPP TS 29.120 V3.0.0 (2000-03)
8.5 Fault recovery services
MAP_RESET HLR – GLR

GLR – VLR
GLR – SGSN
MAP_FORWARD_CHECK_SS_INDICA HLR – GLR
TION
GLR – VLR
MAP_RESTORE_DATA VLR – GLR
Figure 8.5/1
8.6 Subscriber Information services
MAP-PROVIDE-SUBSCRIBER-Info VLR – GLR

GLR – HLR
Figure 8.6/1
9 Operation and maintenance services
9.1 General
intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as
in 3GPP TS 29.002.
9.2 MAP_SEND_IMSI service

MAP_ SEND_IMSI HLR – GLR
GLR – VLR
Figure 9.2/1
3GPP
Release 1999 16 3GPP TS 29.120 V3.0.0 (2000-03)
10 Call handling services
10.1 General
in 3GPP TS 29.002.
10.2 MAP_PROVIDE_ROAMING_NUMBER service

MAP_ PROVIDE_ROAMING_NUMBER HLR – GLR
GLR – VLR
Figure 10.2/1
10.3 MAP_SET_REPORTING_STATE service

MAP_ SET_REPORTING_STATE HLR – GLR
GLR – VLR
Figure 10.3/1
10.4 MAP_STATUS_REPORT service
MAP_ STATUS_REPORT VLR – GLR

GLR – HLR
Figure 10.4/1
10.5 MAP_REMOTE_USER_FREE service

MAP_REMOTE_USER_FREE VLR – GLR
GLR – HLR
Figure 10.5/1
3GPP
Release 1999 17 3GPP TS 29.120 V3.0.0 (2000-03)
11 Supplementary services related services
11.1 General
in 3GPP TS 29.002.
11.2 MAP_REGISTER_SS service

MAP_ REGISTER_SS VLR – GLR
GLR – HLR
Figure 11.2/1
11.3 MAP_ERASE_SS service

MAP_ ERASE_SS VLR – GLR
GLR – HLR
Figure 11.3/1
11.4 MAP_ACTIVATE_SS service
Services interval for adoption

MAP_ ACTIVATE_SS VLR – GLR
GLR – HLR
Figure 11.4/1
11.5 MAP_DEACTIVATE_SS service

MAP_ DEACTIVATE_SS VLR – GLR
GLR – HLR
Figure 11.5/1
3GPP
Release 1999 18 3GPP TS 29.120 V3.0.0 (2000-03)
11.6 MAP_ INTERROGATE _SS service
MAP_ INTERROGATE_SS VLR – GLR

GLR – HLR
Figure 11.6/1
11.7 MAP_ REGISTER_PASSWORD service

MAP_ REGISTER_PASSWORD VLR – GLR
GLR – HLR
Figure 11.7/1
11.8 MAP_ GET_PASSWORD service

MAP_ GET_PASSWORD HLR – GLR
GLR – VLR
Figure 11.8/1
11.9 MAP_ PROCESS_UNSTRUCTURED_SS_REQUEST

service
MAP_ PROCESS_UNSTRUCTURED_SS_REQUEST VLR – GLR

GLR – HLR
Figure 11.9/1
3GPP
Release 1999 19 3GPP TS 29.120 V3.0.0 (2000-03)
11.10 MAP_ UNSTRUCTURED_SS_REQUEST service

MAP_ UNSTRUCTURED_SS_REQUEST HLR – GLR
GLR – VLR
Figure 11.10/1
11.11 MAP_UNSTRUCTURED_SS_NOTIFY service

MAP_ UNSTRUCTURED_SS_NOTIFY HLR – GLR
GLR – VLR
Figure 11.11/1
11.12 MAP_REGISTER_CC_ENTRY service

MAP_ UNSTRUCTURED_SS_NOTIFY VLR – GLR
GLR – HLR
Figure 11.12/1
11.13 MAP_ERASE_CC_ENTRY service

MAP_ ERASE_CC_NOTIFY VLR – GLR
GLR – HLR
Figure 11.13/1
12 Short message service management services
12.1 General
in 3GPP TS 29.002.
3GPP
Release 1999 20 3GPP TS 29.120 V3.0.0 (2000-03)
12.2 MAP-READY-FOR-SM service

MAP-READY-FOR-SM VLR – GLR
SGSN – GLR
GLR – HLR
Figure 12.2/1
12.3 MAP-MT-FORWARD-SHORT-MESSAGE service
MAP_MT_FORWARD_SHORT_MESSAGE SMS-GMSC – IM-MSC
IM-MSC – MSC
SMS-GMSC – GLR
GLR – SGSN
Figure 12.3/1
13 Network-Requested PDP Context Activation services
13.1 General
Regarding definition of each service, only the interval for adopttion shall be considered for the GLR introduction. The
in 3GPP TS 29.002.
13.2 MAP_SEND_ROUTING_INFO_FOR_GPRS service

MAP_SEND_ROUTING_INFO_FOR_GPRS IM-GSN – GLR
Figure 13.2/1
3GPP
Release 1999 21 3GPP TS 29.120 V3.0.0 (2000-03)
13.3 MAP_FAILURE_REPORT service

MAP_ FAILURE_REPORT IM-GSN – GLR
Figure 13.3/1
14 Void
15 Element of procedure
The elements of procedures for the MAP protocol are referred to the corresponding section in 3GPP TS 29.002002 with
the exceptions described below.
15.1 SDL descriptions

Replace the corresponding part of Process Secure_MAP_DSM as figure 15.1/1.
3GPP
Release 1999 22 3GPP TS 29.120 V3.0.0 (2000-03)
Process Secure_MAP_DSM_ GLR 15.1.1 (1)
Process to manage a DIALOGUE_

MAP dialogue ACCEPTED
any MAP specif ic MAP_

Any MAP specific
MAP_REQ request prim it ive MAP_rsp response primitive DELIMIT ER_
req
Secu re_
(TRUE) Secure_ T (TRUE)
Transport_
required ransport_
required TC_
CONTINUE_
(FALSE)
(FALSE) req_VIA_TC 1
Requesting_ Se cure_
MAP_SSM Requesting_
MAP_SSM
Service_ Service_ Response_ Issued_ Response_ DIALO GUE_

Invoked_ Inv oked_ VIA_Imtern1 Issued_ ESTABLISHED
VIA_Intern2 VIA_Intern4 VIA_Imtern3
DIALOGUE_
ACCEPTED
MAP_
MAP_U_
CLOSE_
ABORT_
re q
req
User-reason= ye s
AC-not-
suppoeted
no
Abort-reason : = Abort-reason : =
User-specific AC-not-
supported
User-info :=
MAP-
UserAbortInfo
TC_END_req TC_U_
VIA_T C1 ABORT _req_
VIA_TC1
(FALS eEc) ure_

(TRUE)
T ransport_
required
Terminated_ To all active PSSMs

VIA_Intern1 Terminated_ T o all active SPSSMs
VIA_Intern3
Terminated_ To all active RSSMs

VIA_Intern2 Terminated_ To all active SRSSMs
VIA_Intern4
IDL E IDLE
Figure 15.1/1: Process Secure_MAP_DSM_GLR
16 Mapping onto TC services

Dialogue control, Service specific procedures and SDL descriptions are referred to the corresponding section in 3GPP
TS 29.002.
3GPP
Release 1999 23 3GPP TS 29.120 V3.0.0 (2000-03)
17 Abstract syntax of the MAP protocol
17.1 General
Refer to the corresponding section in 3GPP TS 29.002 except Packages specifications and Application contexts.
Regarding the operations which are initiated by the VLR or SGSN toward HLR via GLR, the timer value used in the
operations should be configured enough long to guarantee the GLR specific fallback mechanism.
17.2 Packages specifications

Regarding Packages specifications, only the supplier and consumer definition shall be considered for the GLR
introduction. The supplier and consumer definition for the GLR specification are derived Table 17.2/1. For the other
definitions of the package specifications are as in 3GPP TS 29.002.
Table 17.2/1: supplier and consumer definition
Operation Package supplier consumer
LocationUpdatingPackage-v3 HLR GLR

GLR VLR
LocationCancellationPackage-v3 VLR or SGSN GLR
GLR HLR
RoamingNumberEnquiryPackage-v3 VLR GLR
GLR HLR
InfoRetrievalPackage-v2 HLR GLR
GLR VLR
GLR SGSN
InfoRetrievalPackage-v1 HLR GLR
GLR VLR
GLR SGSN
IMSIRetrievalPackage-v2 HLR GLR
GLR VLR
SubscriberDataMngtStandAlonePackage-v3 VLR or SGSN GLR
GLR HLR
SubscriberDataMngtPackage-v3 VLR or SGSN GLR
GLR HLR
ResetPackage-v2 VLR or SGSN GLR
GLR HLR
FunctionalSsPackage-v2 HLR GLR
GLR HLR
BindingPackage-v1 HLR GLR
GLR VLR
UnstructuredSsPackage-v2 HLR GLR
GLR VLR
UnstructuredSsPackage-v1 HLR GLR
GLR VLR
MTShortMsgRelayPackage-v3 IM-MSC or GMSC
GLR
MSC IM-MSC
SGSN GLR
MwdMngtPackage-v3 HLR GLR
GLR SGSN
GLR VLR
MwdMngtPackage-v1 HLR GLR
GLR VLR
DataRestorationPackage-v3 GLR VLR
PurgingPackage-v3 HLR GLR
GLR VLR
GLR SGSN
3GPP
Release 1999 24 3GPP TS 29.120 V3.0.0 (2000-03)
Operation Package supplier consumer

SubscriberInformationEnquiryPackage-v3 VLR GLR
GLR HLR
GprsLocationUpdatingPackage-v3 HLR GLR
GLR SGSN
FailureReportingPackage-v3 GLR IM-GSN
SetReportingStatePackage-v3 VLR GLR
GLR HLR
StatusReportPackage-v3 HLR GLR
GLR VLR
RemoteUserFreePackage-v3 VLR GLR
GLR HLR
CallCompletionPackage-v3 HLR GLR
GLR VLR
AuthenticationFailureReportPackage-v3 HLR GLR
GLR VLR
GLR SGSN
SecureTransportHandlingPackage-v3 This operation package includes the
operations required for the secure
transport of MAP messages between
any MAP entities.
17.3 Application contexts

Regarding Application contexts specifications, only the responder and initiator definition shall be considered for the
GLR introduction. The responder and initiator definition for the GLR specification are derived Table 17.3/1. For
the other definitions of the package specifications are as in 3GPP TS 29.002.
3GPP
Release 1999 25 3GPP TS 29.120 V3.0.0 (2000-03)
Table 17.3/1: supplier and consumer definition
Application Context Version Initiator Responder
locationCancellationContext v3 HLR GLR

GLR VLR or SGSN
imsiRetrievalContext v2 VLR GLR
GLR HLR
infoRetrievalContext v2 VLR or SGSN GLR
GLR HLR
mwdMngtContext v3 VLR or SGSN GLR
GLR HLR
msPurgingContext v3 VLR or SGSN GLR
GLR HLR
resetContext v2 HLR GLR
GLR VLR or SGSN
networkUnstructuredSsContext v2 VLR GLR
GLR HLR
HLR GLR
GLR VLR
networkFunctionalSsContext v2 VLR GLR
GLR HLR
shortMsgMT-RelayContext v3 MSC IM-MSC or GLR
IM-MSC MSC
GLR SGSN
networkLocUpContext v3 VLR GLR
GLR HLR
gprsLocationUpdateContext v3 SGSN GLR
GLR HLR
subscriberDataMngtContext v3 HLR GLR
GLR VLR or SGSN
roamingNumberEnquiryContext v3 HLR GLR
GLR VLR
gprsLocationInfoRetrievalContext v3 IM-GSN GLR
failureReportContext v3 IM-GSN GLR
subscriberInfoEnquiryContext v3 HLR GLR
GLR VLR
reportingContext v3 VLR GLR
GLR HLR
HLR GLR
GLR VLR
callCompletionContext v3 VLR GLR
GLR HLR
authenticationFailureReportContext v3 VLR or SGSN GLR
GLR HLR
SecureTransportHandlingContext v3 This application context is used for
the secure transport of MAP
messages between any MAP entities.
18 General on MAP user procedure

Refer to 3GPP TS 29.002 for general matters for procedure description such as notation convention, version handling at
dialogue establishment and interaction between MAP provider and MAP users.
3GPP
Release 1999 26 3GPP TS 29.120 V3.0.0 (2000-03)
19 Mobility procedures
19.1 Location management Procedures

For non-GPRS subscribers, this subclause comprises a number of processes to handle the mobile nature of the
subscriber. The processes will be addressed by SCCP SSN (VLR or HLR) and the Application Context. The processes
in the GLR interact with the processes in the VLR or HLR defined in 29.002. The followings show the relations
between the protocol processes in the GLR and the processes in the other node.
Process Update Location (VLR-GLR):
- Initiator: Update_Location_Area_VLR or Update_Location_HLR;
- Responder: Update_Location_GLR.
Process Update Location (GLR-HLR):
- Initiator: GLR_Update_Location_HLR;
- Responder: Update_Location_HLR.
Process Cancel Location (VLR-GLR):
- Initiator: GLR_Cancel_Location_VLR;
- Responder: Cancel_Location_VLR.
Process Cancel Location (GLR-HLR):
- Initiator: Cancel_Location_HLR;
- Responder: Cancel_Location_GLR.
Process Purge MS (VLR-GLR):
- Initiator: Purge_MS_VLR;
- Responder: Purge_MS_GLR.
Process Purge MS (GLR-HLR):
- Initiator: GLR_Purge_MS_HLR;
- Responder: Purge_MS_HLR.
A Location Management Co-ordinator in the GLR co-ordinates the two protocol processes “Update_Location_GLR”
(subclause 19.1.2) and “RESTORE_DATA_GLR” (subclause 19.2) that are addressed by the same application context.
On receipt of a dialogue request for the Location Management Application Context, the location
Management_Coordinator_GLR will:
- Terminate the process in case of parameter problems; or
- Revert to MAP version Vr protocol if the VLR requests version Vr protocol; or
- Continue as described in the following, if the dialogue is accepted.
The protocol process is created depending on the first primitive received from the MAP service provider within this
dialogue:
- Update_Location_GLR if the primitive is a MAP_UPDATE_LOCATION indication.
- RESTORE_DATA_GLR if the primitive is a MAP_RESTORE_DATA indication.
3GPP
Release 1999 27 3GPP TS 29.120 V3.0.0 (2000-03)
If a MAP_NOTICE indication is received instead, the dialogue towards the VLR is terminated and the process returns to
idle state.
After creation of the protocol process the service primitive received from the MAP service-provider is passed to the
protocol process. Henceforth, the co-ordinator will relay all service primitives from MAP service-provider to the MAP
service-user and vice versa, until a request or indication for dialogue termination is received. This last primitive will
be relayed, too, before the Co-ordinator process returns to idle state.
Process Location_Management_Coordinator_GLR 19.1.1.1(1)

Location management coordination process in the GLR
NULL
Receive_
Open_Ind Section 25.1
'Vr' 'Error'
'OK'
WAIT_FOR_ 'Perform_
SERVICE_ MAP_Vr_
PRIMITIVE Dialogue'
MAP_ MAP_
UPDATE_ MAP_ NOTICE_
RESTORE_ Ind NULL NULL
LOCATION_
Ind DATA_Ind
Update_ MAP-
Location_GLR RESTORE_ CLOSE_
DATA_GLR Req
MAP_
UPDATE_ MAP_ NULL
RESTORE_
LOCATION_Ind
DATA_Ind
RELAY_INFO
*
from * MAP-U-ABORT_Req, MAP-P-ABORT_Ind,
Provider from MAP-CLOSE_Req MAP-U-ABORT_Ind,
OFFSPRING from OFFSPRING MAP-CLOSE_Ind
-
- - -
to
to to to
OFFSPRING
Provider Provider OFFSPRING
RELAY_INFO RELAY_INFO NULL NULL
Figure 19.1.1/1: Process Location_Management_Coordinator_GLR
3GPP
Release 1999 28 3GPP TS 29.120 V3.0.0 (2000-03)
For GPRS subscribers, this subclause comprises a number of other processes to handle the mobile nature of the
subscriber. The processes will be addressed by SCCP Sub-System Number (SGSN or HLR) and the Application
Context. The processes in the GLR interact with the processes in the VLR, SGSN or HLR defined in 29.002. The
followings show the relations between the processes in the GLR and the processes in the other node:
Process GPRS Update Location (VLR or SGSN-GLR):
Initiator: GPRS_Update_Location_Area_VLR, or SGSN_Update_HLR.
Responder: Update_GPRS_Location_GLR.
Process GPRS Update Location (GLR-HLR):
Initiator: GLR_Update_GPRS_Location_HLR.
Responder: Update_GPRS_Location_HLR.
Process Cancel Location (SGSN-GLR):
Initiator: GLR_Cancel_Location_SGSN.
Responder: Cancel_Location_SGSN.
Process Cancel Location (GLR-HLR):
Initiator: Cancel_GPRS_Location_HLR.
Responder: Cancel_GPRS_Location_GLR.
Process Purge MS (SGSN-GLR):
Initiator: Purge_MS_SGSN.
Responder: Purge_MS_GLR_for_GPRS.
Process Purge MS (GLR-HLR):
Initiator: GLR_Purge_MS_HLR_for_GPRS.
Responder: Purge_MS_HLR.
19.1.1 Location updating
19.1.1.1 General
This location updating procedure is used to update the location information held in the network.
If the GLR is located between the VLR and the HLR, the MAP_UPDATE_LOCATION service is invoked towards the
GLR whose identity is contained in the VLR table. When the GLR receives a MAP_UPDATE_LOCATION indication,
it determines whether it invokes the MAP_UPDATE_LOCATION service towards the HLR, and invokes it if
necessary.
If the GLR is located between the SGSN and the HLR, the MAP_UPDATE_GPRS_LOCATION service is invoked
towards the GLR whose identity is contained in the SGSN table. When the GLR receives a
MAP_UPDATE_GPRS_LOCATION indication, it determines whether it invokes the
MAP_UPDATE_GPRS_LOCATION service towards the HLR, and invokes it if necessary.
3GPP
Release 1999 29 3GPP TS 29.120 V3.0.0 (2000-03)
+----+ +----+ +----+ +-----+

│VLR/│ | | │ │ │PGLR/│
│SGSN+-----+----------│GLR │-------+---------│HLR +-------+---------│PVLR/│
│ │ | | │ │ │PSGSN│
+----+ +----+ +----+ +-----+
│ │ │ │
│ MAP UPDATE_LOCATION │ │ │
│-------------------->│ │ │
│ or MAP UPDATE GPRS │ MAP UPDATE_LOCATION │ MAP_CANCEL_ │
│ LOCATION │ -------------------->│--------------------------------------->│
│ │or MAP UPDATE GPRS │ LOCATION │
│ │ LOCATION │ │
│ │ │ │
│ │ │ MAP_CANCEL_LOCATION │
│ │ │<----------------------│
│ │ │ ack │
│MAP INSERT SUBSCRIBER│MAP INSERT SUBSCRIBER │ │
│ DATA │ DATA │ │
│<--------------------│<---------------------│ │
│ │ │ │
│ │ │ │
│MAP INSERT SUBSCRIBER│MAP INSERT SUBSCRIBER │ │
│ DATA │ DATA │ │
│-------------------->│--------------------> │ │
│ ack │ ack │ │
│ │ │ │
│ │ │ │
│MAP CHECK SS │MAP CHECK SS │ │
│ INDICATION │ INDICATION │ │
│<--------------------│<---------------------│ │
│ │ │ │
│ │ │ │
│MAP UPDATE_LOCATION │MAP UPDATE_LOCATION │ │
│or MAP UPDATE_GPRS │or MAP UPDATE_GPRS │ │
│ LOCATION │ LOCATION │ │
│<--------------------│<-------------------- │ │
│ ack │ ack │ │
│ │ │
Figure 19.1.2/1: Interface and services for Location updating
19.1.1.2 Detailed procedure in the GLR

Figure 19.1.2/2 shows the Process Update_Location_GLR. This process is a GLR MAP prorocol machine handling
location updating and is a responder to the VLR.
3GPP
Release 1999 30 3GPP TS 29.120 V3.0.0 (2000-03)
Process Update_Location_GLR 19.1.2.2_1(3)

GLR MAP protocol machine Left to VLR
handling location updating and Right to GLR
interfaceing with VLR MAP application
protocol machine
WAIT_FOR_
SERVICE_
PRIMITIVE
MAP_Update_
Location_ind
Update
2
Location
WAIT_FOR_
APPLICATION_
RESPONSE
Update Update Location Insert_ Forward check

Location Ack Negative Response Subscriber_ SS indication Abort
Data
Set result Set Error 1

MAP_UPDATE_
LOCATION_Rsp.
MAP_CLOSE_Req.
MAP_UPDATE_ WAIT_FOR_ MAP_U_
LOCATION_Rsp. APPLICATION_ ABORT_req
MAP_CLOSE_Req. RESPONSE
MAP_FORWARD_
CHECK_SS_INDICATION_req
MAP_DELIMITER_req
Figure 19.1.2/2 (sheet 1 of 3): Process Update_Location_GLR
3GPP
Release 1999 31 3GPP TS 29.120 V3.0.0 (2000-03)

GLR MAP protocol machine
handling location updating and 1
interfaceing with VLR MAP
protocol machine
MAP_Insert_Subscriber_Data_Req
MAP_Delimiter_Req
Left to VLR
Right to GLR WAIT_FOR_ISD_Cnf_
application WAIT_FOR_SUBSEQUENT_
APPLICATION_RESPONSE
MAP_Insert_Subscriber_
Data_Cnf MAP_U_ABORT_Ind MAP_NOTICE_
MAP_P_ABORT_Ind Ind
MAP_CLOSE_Ind
Set Negative
Abort Result
System Failure
ISD
Negative Response
Check
Confirmation Section 25.2 2
OK Provider error
Data error
User error
Insert_Subscriber_
Data_Cnf
MAP User Error
to Negative
Set Negative Response
Response
System Failure
2
ISD
Negative Response
3GPP
Release 1999 32 3GPP TS 29.120 V3.0.0 (2000-03)

handling location updating and
protocol machine
Left to VLR
Right to GLR
application WAIT_FOR_ISD_Cnf_
WAIT_FOR_SUBSEQUENT_
Update
Location Ack Update Location Insert
Negative Response Subscriber Abort
Data
Set result Set Error 1

MAP_U_ ABORT_Req.
3GPP
Release 1999 33 3GPP TS 29.120 V3.0.0 (2000-03)
MAP_UPDATE_
LOCATION_Rsp.
MAP_CLOSE_Req.
3GPP
Release 1999 34 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.2/3 shows the Process GLR_Update_Location_HLR. This process is a GLR MAP protocol machine
handling location updating and is an initiator to the HLR.
Sheet 1: If the Macro Open_Receive_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for
sending an abort message to Process Update_Location_GLR.
Process GLR_Update_Location_HLR 19.1.2.3_1(3)

GLR MAP protocol machine handling
Location Management and interfacing Signals to/from the left
to HLR MAP protocol
are to/from the GLR application.
machine, handling Location Management.
Signals to/from the right
are to/from the HLR MAP protocol
machine.
IDLE
Update Location
MAP_OPEN_Req
MAP_UPDATE_LOCATION_Req
MAP_DELIMITER_Req
Receive
Open Section 25.1
Cnf.
Vr
OK Error
Wait_For_HLR_
Response Perform MAP Vr Set error
Update Location
Negative Response
Figure 19.1.2/3 (Sheet 1 of 3): Process GLR_Update_Location_HLR
3GPP
Release 1999 35 3GPP TS 29.120 V3.0.0 (2000-03)

Signals to/from the left
Location Management and interfacing Signals to/from the right
to HLR MAP protocol
Wait_For_HLR_ are to/from the HLR MAP protocol machine.
Response
MAP_FORWARD_
MAP_INSERT_ MAP_Notice_ MAP_U_Abort_ind
Check_SS_ind
SUBSCRIBER_ Indication MAP_P_Abort_ind
DATA_ind MAP_Close_ind
Forward
Check SS Insert MAP_Close_
Subscriber request Abort
Indication
data
Idle
Set negative respon se
Update Location
negative response
Idle
Wait_For_HLR_or_
Application_ Response
MAP_Update_
Location_cnf
Section 25.2
Check Confirmation Provider Error,

User Error, Data
OK Error
Update Set negative

Location ack response
Update Location
negative response
Idle
3GPP
Release 1999 36 3GPP TS 29.120 V3.0.0 (2000-03)

GLR MAP protocol machine handling Signals to/from the left
Location Management and interfacing are to/from the GLR application.
to HLR MAP protocol
machine, handling Location Management. Signals to/from the right
Wait_For_HLR_or_ are to/from the HLR MAP protocol machine.
Application
Response
MAP_FORWARD_
MAP_INSERT_ SUBSCRIBER_
Check_SS_ind
DATA_ind
Forward
Check SS Insert Insert Insert
Indication Subscriber Subscriber Subscriber
data Data ack Data negative
response
Set user error
MAP_Insert_
Subscriber_Data_
response
Wait_For_HLR_or_
MAP_Update_
Location_cnf MAP_Notice_ MAP_U_Abort_ind
Abort Indication MAP_P_Abort_ind
Section 25.2 MAP_Close_ind
Check Confirmation Map_U_Abort_ MAP_Close_

Provider Error, Abort
User Error, request request
OK Data Error
Update
Location ack Set negative Set negative respon se
response
Update Location
negative response Update Location
negative response
Idle Idle
3GPP
Release 1999 37 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.2/4 shows the Process Update_GPRS_Location_GLR. This process is a GLR MAP protocol machine
handling location updating and is a responder to the SGSN.
Process Update_GPRS_Location_GLR 19.1.2.4_1(3)

interfaceing with SGSN MAP
protocol machine
NULL
Left to SGSN
Right to GLR Receive
application OK Open
Ind.
V2
WAIT_FOR_SERVICE_ V1
PRIMITIVE Error
MAP_Update_
GPRS_Location_ Perform_MAP_
Vr_Dialogue NULL
ind
NULL
Update GPRS Location
WAIT_FOR_
APPLICATION_ RESPONSE

Ack Update GPRS Location Insert
Data
Set result
Set error
1
MAP_UPDATE_GPRS_
LOCATION_Rsp. MAP_UPDATE_GPRS_
MAP_CLOSE_Req. LOCATION_Rsp. MAP_U_
MAP_CLOSE_Req. ABORT_req
Figure 19.1.2/4 (sheet 1 of 3): Process Update_GPRS_Location_GLR
3GPP
Release 1999 38 3GPP TS 29.120 V3.0.0 (2000-03)

protocol machine
Left to SGSN MAP_Insert_Subscriber_Data_Req

Right to GLR 3
MAP_Delimiter_Req
application
WAIT_FOR_ISD_Cnf_
MAP_Insert_Subscriber_ MAP_U_ABORT_Ind MAP_NOTICE_

Data_Cnf MAP_P_ABORT_Ind Ind
MAP_CLOSE_Ind
Set Negative
Abort Result
System Failure
ISD
Negative Response
Check
Confirmation Section 25.2 3
OK Provider error
Data error
User error
Insert_Subscriber_
Data_Cnf
MAP User Error
to Negative
Set Negative Response
Response
System Failure
2
ISD
Negative Response
3GPP
Release 1999 39 3GPP TS 29.120 V3.0.0 (2000-03)

protocol machine
Left to SGSN
Right to GLR
application WAIT_FOR_ISD_Cnf_
Update
Location Ack Update GPRS Location Insert
Data
MAP_U_
Set result Set Error 1 ABORT_req
MAP_UPDATE_
LOCATION_Rsp.
MAP_CLOSE_Req.
3GPP
Release 1999 40 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.2/5 shows the Process GLR_Update_GPRS_Location_HLR. This process is a GLR MAP protocol machine
handling location updating and is an initiator to the HLR.
sending an abort message to Process Update_GPRS_Location_GLR.
Process GLR_Update_GPRS_Location_HLR 19.1.2.5_1(3)

Location Management and interfacing are to/from the GLR application.
to HLR MAP protocol
machine, handling Location Management. Signals to/from the right
are to/from the HLR MAP protocol machine.
IDLE
MAP_OPEN_Req
MAP_UPDATE_GPRS_LOCATION_Req
MAP_DELIMITER_Req
Receive Section 25.1

Open
Cnf.
Vr
OK
Error
Wait_For_HLR_
Response Set error
Perform MAP Vr
Update GPRS Location Negative

Response
Figure 19.1.2/5 (Sheet 1 of 3): Process GLR_Update_GPRS_Location_HLR
3GPP
Release 1999 41 3GPP TS 29.120 V3.0.0 (2000-03)

to HLR MAP protocol
Wait_For_HLR_
Response
MAP_Update_GPRS_
Location_cnf MAP_INSERT_ MAP_Notice_ MAP_U_Abort_ind
Check Confirmation Section 25.2 Insert MAP_Close_

Data
OK
Provider Error,
User Error, Data
Error Set negative respon se
Update GPRS Set negative Wait_For_HLR_or_ Update GPRS Location

Location ack response Application_ negative response
Response
Idle

negative response
Idle
3GPP
Release 1999 42 3GPP TS 29.120 V3.0.0 (2000-03)

to HLR MAP protocol
Wait_For_HLR_or_ are to/from the HLR MAP protocol machine.
Application
Response
MAP_INSERT_
SUBSCRIBER_
DATA_ind
Insert
Subscriber Insert Insert Subscriber
Data Subscriber Data negative
Data ack response
Set user error
MAP_Insert_
Subscriber_Data_
response
Wait_For_HLR_or_
Application_
Response
MAP_Update_GPRS_
Location_cnf MAP_Notice_ MAP_U_Abort_ind
Abort Indication MAP_P_Abort_ind
Section 25.2
MAP_Close_ind
Provider Error, Map_U_Abort_ MAP_Close_

Ch eck Confirmat ion Abort
User Error, request request
Data Error
OK
Update GPRS
Set negative
Location ack Set negative respon se
response
Update GPRS Location Update GPRS Location negative

negative response response
Idle
Idle
3GPP
Release 1999 43 3GPP TS 29.120 V3.0.0 (2000-03)
19.1.2 Location Cancellation
19.1.2.1 General
The purpose of this process is to delete a subscriber's record from a previous GLR/VLR/SGSN after she has registered
with a new GLR/VLR/SGSN. The procedure may also be used if the subscriber's record is to be deleted for other
operator determined purposes. Location cancellation can be used to enforce location updating including updating of
subscriber data in the VLR or in the SGSN at the next subscriber access.
In all cases, the process is performed independently of the invoking process (e.g. Location Updating).
If GLR is located between the VLR or the SGSN and the HLR, the MAP_CANCEL_LOCATION service is invoked
towards the GLR whose identity is contained in the HLR table.
+----+ +----+ +----+ +----+
│VLR/│ D | | D │ │ D │ │
│GLR +-----+----------│HLR │-------+---------│PGLR+-------+---------│PVLR│
+----+ +----+ +----+ +----+
│ │ │ │
│ MAP UPDATE_LOCATION │ │ │
│-------------------->│ │ │
│ │ MAP_CANCEL_ │ MAP_CANCEL_ │
│ │ -------------------->│--------------------------------------->│
│ │ LOCATION │ LOCATION │
│ │ │ │
│ │ │ │
│ │ MAP_CANCEL_LOCATION │ MAP_CANCEL_LOCATION │
│ │<-------------------- │<----------------------│
│ │ ack │ ack │
│ │ │
NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling.
Figure 19.1.3/1: Interface and services for Location Cancellation
+-----+ +----+ +----+ +-----+

│SGSN/│ D | | D │ │ D │ │
│GLR +------+-------│HLR │-------+---------│PGLR+-------+---------│PSGSN│
+-----+ +----+ +----+ +-----+
│ │ │ │
│MAP_UPDATE_GPRS_LOCATION│ │ │
│----------------------->│ │ │
│ │ MAP_CANCEL_ │ MAP_CANCEL_ │
│ │ -------------------->│--------------------------------------->│
│ │ LOCATION │ LOCATION │
│ │ │ │
│ │ │ │
│ │ MAP_CANCEL_LOCATION │ MAP_CANCEL_LOCATION │
│ │<-------------------- │<----------------------│
│ │ ack │ ack │
│ │ │ │
NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling.
Figure 19.1.3/2: Interface and services for Location Cancellation in GPRS
Additionally, The MAP_CANCEL_LOCATION service is invoked when the GLR that stores the subscriber’s record
receives a MAP_UPDATE_LOCATION indication from a VLR other than that stored in its table for this subscriber.
Also the MAP_CANCEL_LOCATION service is invoked when the GLR that stores the subscriber’s record a
MAP_UPDATE_GPRS_LOCATION indication from a SGSN other than stored in its table for this subscriber. The
MAP_CANCEL_LOCATION service is in any case invoked towards the VLR or the SGSN whose identity is contained
in the HLR table.
3GPP
Release 1999 44 3GPP TS 29.120 V3.0.0 (2000-03)
+----+ D +----+ D +-----+

│VLR/+-----------+------------+GLR +-------+--------+PVLR/│
│SGSN| │ │ │PSGSN│
+----+ +----+ +-----+
│ MAP_UPDATE_LOCATION or │ │
│ MAP_UPDATE_GPRS_LOCATION │ │
│---------------------------->│ │
│ │ MAP_CANCEL_ │
│ │--------------------------------------->│
│ │ LOCATION │
│ │ │
│ │ │
│ │ MAP_CANCEL_LOCATION │
│ │<----------------------│
│ │ ack │
│ │ │
Figure 19.1.3/4: Interface and services for Location Cancellation in case that the GLR stores the
subscriber’s record
19.1.2.2 Detailed procedure in the GLR

Figure 19.1.3/5 shows the Process Cancel_Location_GLR. This process is a GLR MAP protocol machine handling
location cancellation and is a responder to the HLR.
3GPP
Release 1999 45 3GPP TS 29.120 V3.0.0 (2000-03)
Process Cancel_Location_GLR 19.1.3.5(1)

Location cancelation and interfacing to are to/from the GLR Location
HLR MAP protocol cancellation application.
machine, handling Location Cancelation.
are to/from the HLR MAP protocol machine,
handling Location Cancellation.
NULL
Receive
Open
OK Ind.
WAIT_FOR_SERVICE_ V2 V1
PRIMITIVE Error
MAP_CANCEL_
Perform_MAP_
LOCATION_ind MAP_NOTICE_ind Vr_Dialogue NULL
MAP_CLOSE_req NULL
Cancel Location NULL
WAIT_FOR_
APPLICATION_
RESPONSE
Cancel
Location Ack Cancel Location
Negative response Abort
MAP_CANCEL_LOCATION_Rsp.
MAP_CLOSE_Req. MAP_U_ABORT_req
NULL NULL
Figure 19.1.3/5: Process Cancel_Location_GLR
3GPP
Release 1999 46 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.3/6 shows the Process GLR_Cancel_Location_VLR. This process is a GLR MAP protocol machine
handling location cancellation and is an initiator to the VLR.
sending an abort message to Process Cancel_Location_GLR.
Process GLR_Cancel_Location_VLR 19.1.3.6(1)

handling cancel location and
interfacing with VLR MAP
protocol machine
IDLE
VLR to the Left
GLR Application to the Right
Cancel Location
MAP_OPEN_Req
MAP_CANCEL_LOCATION_Req
MAP_DELIMITER_Req
Receive
Open
Cnf.
Vr
OK Error
WAIT_FOR_
ACK Perform MAP Vr Cancel Location
Negative Response
MAP_CANCEL_
LOCATION_Cnf MAP_P_ MAP_
ABORT_Ind NOTICE_
Ind
Check_ MAP_CLOSE_
Confirmation Req
OK
Error Cancel Location Cancel Location Negative
Cancel Location Negative Response Response
Cancel Location
Ack
Negative Response
Figure 19.1.3/6: Process GLR_Cancel_Location_VLR
3GPP
Release 1999 47 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.3/7 shows the Process Cancel_GPRS_Location_GLR. This process is a GLR MAP protocol machine
handling location cancellation and is a responder to the HLR.
Process Cancel_GPRS_Location_GLR 19.1.3.7(1)

Location cancelation and interfacing to
HLR MAP protocol
machine, handling Location Cancelation.
are to/from the GLR Location
cancellation application.
NULL Signals to/from the left
are to/from the HLR MAP protocol machine,
handling Location Cancellation.
Receive
Open
Ind.
OK
V2 V1
WAIT_FOR_SERVICE_ Error
PRIMITIVE
Perform_MAP_
MAP_CANCEL_ Vr_Dialogue NULL
LOCATION_ind MAP_NOTICE_ind
NULL
Cancel Location
MAP_CLOSE_req
NULL
WAIT_FOR_
APPLICATION_
RESPONSE
Cancel
Location Ack Cancel Location
Negative Response Abort
MAP_CANCEL_LOCATION_Rsp.
MAP_CLOSE_Req. MAP_U_ABORT_req
NULL
NULL
Figure 19.1.3/7: Process Cancel_GPRS_Location_GLR
3GPP
Release 1999 48 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.3/8 shows the Process GLR_Cancel_Location_SGSN. This process is a GLR MAP protocol machine
handling location cancellation and is an initiator to the SGSN.
sending an abort message to Process Cancel_GPRS_Location_GLR.
Process GLR_Cancel_Location_SGSN 19.1.3.8(1)

handling cancel location and
interfacing with SGSN MAP
protocol machine
IDLE
SGSN to the Left

GLR Application to the Right Cancel Location
MAP_OPEN_Req
MAP_CANCEL_LOCATION_Req
MAP_DELIMITER_Req
Receive Open
Cnf.
Vr
OK Error
Cancel Location
Negative Response
Perform MAP Vr
WAIT_FOR_
ACK
MAP_CANCEL_
LOCATION_Cnf MAP_P_ MAP_
ABORT_Ind NOTICE_
Ind
Check_
Confirmation MAP_CLOSE_
Req
OK
Error Cancel Location Cancel Location Negative
Cancel Location Negative Response Response
Cancel Location
Ack
Negative Response
Figure 19.1.3/8: Process GLR_Cancel_Location_SGSN
3GPP
Release 1999 49 3GPP TS 29.120 V3.0.0 (2000-03)
19.1.3 Purge MS
19.1.3.1 General
This Purge MS procedure is used to treat any request for routing information for a mobile terminated call or a mobile
terminated short message as if the MS is not reachable.
If GLR is located between the VLR or the SGSN and the HLR, the MAP_PURGE_MS service is invoked towards the
GLR whose identity is contained in the VLR table or the SGSN table.
When the GLR receives a MAP_PURGE_MS indication, the GLR determines whether it invokes the
MAP_PURGE_MS service towards the HLR.
+----+ +----+ +----+
│VLR/│ | | │ │
│SGSN+-----+----------+GLR +--------+--------│ HLR│
+----+ +----+ +----+
│ │ │
│ MAP PURGE_MS │ │
│-------------------->│ │
│ │ MAP PURGE_MS │
│ │------------------------------------->│
│ │ │
│ │ │
│ │ │
│ │ MAP PURGE_MS ack │
│ MAP_PURGE_MS ack │<---------------------│
│<--------------------│ │
│ │ │
Figure 19.1.4/1: Interface and services for Purge MS
19.1.3.2 Detailed procedure in GLR

Figure 19.1.4/2 shows the Process Purge_MS_GLR. This process is a GLR MAP protocol machine handling purge MS
and is a responder to the VLR.
3GPP
Release 1999 50 3GPP TS 29.120 V3.0.0 (2000-03)
Process Purge_MS_GLR 19.1.4.2(1)

handling purge MS VLR to the Left
GLR Application to the Right
NULL
Receive
Open Ind.
OK
V1
Error
V2
WAIT_FOR_SERVICE_
PRIMITIVE Perform_MAP_
Vr_Dialogue NULL
NULL
MAP_NOTICE_
MAP_PURGE_
Ind
MS_Ind
MAP_CLOSE_
Req Purge MS
WAIT_FOR_
APPLICATION_
RESPONSE
Purge MS
Ack Purge MS
MAP_PURGE_MS_Rsp
MAP_CLOSE_Req MAP_U_ABORT_req
NULL NULL
Figure 19.1.4/2: Process Purge_MS_GLR
3GPP
Release 1999 51 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.4/3 shows the Process GLR_Purege_MS_HLR. This process is a GLR MAP protocol machine handling
purge MS and is an initiator to the HLR.
Process GLR_Purge_MS_HLR 19.1.4.3(1)

handling purge MS and interfacing Signals to/from the left
to HLR MAP protocol machine,
handling Purge MS.
Null
Purge MS
MAP_OPEN_Req
MAP_PURGE_MS_Req
MAP_DELIMITER_Req
Receive Section 25.1

Open
Cnf. Error
Vr
OK
Set error
Perform MAP Vr
Purge MS
Negative Response
Wait_For_HLR_
Response
MAP_Notice_ MAP_U_Abort_ind
MAP_PURGE_MS_cnf
Indication MAP_P_Abort_ind
MAP_Close_ind
Check Confirmation MAP_Close_

request
Provider Error,
OK User Error, Data
Error
Set negative
Purge MS ack response
Purge MS
negative
response
Null
Figure 19.1.4/3: Process GLR_PURGE_MS_HLR
3GPP
Release 1999 52 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.4/4 shows the Process Purge_MS_GLR_for_GPRS. This process is a GLR MAP protocol machine handling
purge MS and is a responder to the SGSN.
sending an abort message to Process PURGE_MS_GLR.
Process Purge_MS_GLR_for_GPRS 19.1.4.4(1)

GLR MAP protocol machine SGSN to the Left
handling purge MS GLR Application to the Right
NULL
Receive
Open Ind.
OK V2
V1
Error
Perform_MAP_
Vr_Dialogue
WAIT_FOR_SERVICE_
PRIMITIVE
NULL NULL
MAP_NOTICE_
Ind MAP_PURGE_
MS_Ind
MAP_CLOSE_
Req
Purge MS
WAIT_FOR_
APPLICATION_ RESPONSE
Purge MS
Ack Purge MS
MAP_PURGE_
MS_Rsp
MAP_CLOSE_Req MAP_U_ABORT_req
NULL
NULL
Figure 19.1.4/4: Process Purge_MS_GLR_for_GPRS
3GPP
Release 1999 53 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.1.4/5 shows the Process GLR_Purge_MS_HLR_for_GPRS. This process is a GLR MAP protocol machine
handling purge MS and is an initiator to the HLR.
sending an abort message to Process PURGE_MS_GLR_for_GPRS.
Process GLR_Purge_MS_HLR_for_GPRS 19.1.4.5(1)

GLR MAP protocol machine Signals to/from the left
handling purge MS and interfacing are to/from the GLR application.
to HLR MAP protocol machine,
handling Purge MS. Signals to/from the right
Null are to/from the HLR MAP protocol machine.
Purge MS
MAP_OPEN_Req
MAP_PURGE_MS_Req
MAP_DELIMITER_Req
Receive
Open
Cnf.
OK Vr
Error
Wait_For_HLR_
Response Perform MAP Vr Set error
Purge MS
Negative Response
MAP_Notice_ MAP_U_Abort_ind
MAP_PURGE_MS_cnf MAP_P_Abort_ind
Indication
MAP_Close_ind
Check Confirmation MAP_Close_

request
Provider Error,
OK
User Error, Data
Error
Set negative
Purge MS ack response
Purge MS
negative
response
Null
Figure 19.1.4/5: Process GLR_Purge_MS_HLR_for_GPRS
3GPP
Release 1999 54 3GPP TS 29.120 V3.0.0 (2000-03)
19.2 Fault recovery procedures

19.2.1 RESET procedure
This procedure is used to notify VLR, SGSN and GLR of the failure of the node for restoration of the subscriber data.
19.2.1.1 HLR failure case

In the case of HLR failure, the HLR invokes MAP_RESET service towards the affected GLR, if GLR is located
between the VLR and the HLR or between the SGSN and the HLR. When a GLR receives MAP_RESET indication, it
sends a MAP_RESET message to the affected VLR and/or SGSN.
19.2.1.2 GLR failure case

In the case of GLR failure, the GLR invokes MAP_RESET service towards the affected VLR and/or SGSN.

Figure 19.2.1/1 shows the Process RECEIVE_RESET_IN_GLR. This process is a GLR MAP protocol machine
handling reset message from HLR.
3GPP
Release 1999 55 3GPP TS 29.120 V3.0.0 (2000-03)
Process RECEIVE_RESET_IN_GLR 19.2.1.1(1)

handling reset message from HLR.
Left to GLR
application NULL
Right to HLR
Receive Open
Ind.
Vr
OK Error
WAIT_FOR_SERVICE_
PRIMITIVE Perform_MAP_
Vr_Dialogue NULL
MAP_RESET_ind
NULL
Release method:
Prearenged end MAP_CLOSE_req
Check_
Indication
OK
Error
Reset
NULL
Figure 19.2.1/1: Process RECEIVE_RESET_IN_GLR
3GPP
Release 1999 56 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.2.1/2 shows the Process SEND_RESET_TO_VLR. This process is a GLR MAP protocol machine handling
reset message to VLR.
Process SEND_RESET_TO_VLR 19.2.1.2(1)

handling reset message to VLR.
Left to VLR
Right to GLR Null
application
Reset
MAP_OPEN_req MAP_RESET_req
MAP_DELIMITER_req
Receive_
Open_Cnf
error Vr
OK
Release method:
Prearenged end Perform
MAP_CLOSE_req Aborted Vr dialogue
Null
Figure 19.2.1/2: Process SEND_RESET_TO_VLR
3GPP
Release 1999 57 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.2.1/3 shows the Process SEND_RESET_TO_SGSN. This process is a GLR MAP protocol machine handling
reset message to SGSN.
Process SEND_RESET_TO_SGSN 19.2.1.3(1)

handling reset message to SGSN.
Left to SGSN
Right to GLR Null
application
Reset
MAP_OPEN_req MAP_RESET_req
MAP_DELIMITER_req
Receive_
Open_Cnf
error Vr
OK
Release method:
Prearenged end Perform
MAP_CLOSE_req Aborted Vr dialogue
Null
Figure 19.2.1/3: Process SEND_RESET_TO_SGSN
3GPP
Release 1999 58 3GPP TS 29.120 V3.0.0 (2000-03)
19.2.2 VLR restoration: the restore data procedure in the GLR
19.2.2.1 General
This procedure is used to restore the subscriber data for an unidentified MS (i.e. IMSI unknown in VLR), or for a known
MS whose IMSI record is marked as "Not Confirmed" by the indicator "Confirmed by HLR" in VLR.
If GLR is located between the VLR and the HLR, the MAP_RESTORE_DATA service is invoked towards the GLR
whose identity is contained in the VLR table. When the GLR receives a MAP_RESTORE_DATA indication, it
determines whether it invokes the MAP_RESTORE_DATA service towards the HLR, and invokes it if necessary.

Figure 19.2.2/1 shows the Process RESTORE_DATA_GLR. This process is a GLR MAP protocol machine handling
VLR restoration and is a responder to the VLR.
3GPP
Release 1999 59 3GPP TS 29.120 V3.0.0 (2000-03)
Process RESTORE_DATA_GLR 19.2.2.1_1(3)

VLR restoration and interfaceing with
VLR MAP protocol machine
Left to VLR
Right to GLR
application
WAIT_FOR_SERVICE_
PRIMITIVE
MAP_RESTORE_DATA_ind
Restore data 2
WAIT_FOR_
APPLICATION_
RESPONSE
Restore data Negative Insert_

Restore data Ack Response Subscriber_ Abort
Data
Set result Set error 1
MAP_RESTORE_DATA_Rsp. MAP_RESTORE_DATA_Rsp. MAP_U_

MAP_CLOSE_Req. MAP_CLOSE_Req. ABORT_req
Figure 19.2.2/1 (Sheet 1 of 3): Process RESTORE_DATA_GLR
3GPP
Release 1999 60 3GPP TS 29.120 V3.0.0 (2000-03)

handling VLR restoration and
protocol machine
Left to VLR
Right to GLR MAP_Insert_Subscriber_Data_Req
application MAP_Delimiter_Req
WAIT_FOR_ISD_Cnf_
WAIT_FOR_SUBSEQUENT
MAP_Insert_Subscriber_
Data_Cnf MAP_U_ABORT_Ind MAP_NOTICE_
MAP_P_ABORT_Ind Ind
MAP_CLOSE_Ind
Check
Confirmation Abort
Set Negative
Result
System Failure
OK Provider error
Dara error User error ISD
Negative Response
_Set Negative
Insert_Subscriber Data_Cnf
Respsonse MAP User Error
System Failure to Negative 2
Response
ISD
2
Negative Response
3GPP
Release 1999 61 3GPP TS 29.120 V3.0.0 (2000-03)

handling VLR restoration and
protocol machine
Left to VLR
Right to GLR
application
WAIT_FOR_ISD_Cnf_
Restore_Data_
Negative_Response Insert_
Restore_Data_Ack Subscriber_ Abort
Data
MAP_U_
Set result Set Error 1 ABORT_req
MAP_RESTORE_DATA_Rsp. MAP_CLOSE_Req.
3GPP
Release 1999 62 3GPP TS 29.120 V3.0.0 (2000-03)
Figure 19.2.2/2 shows the Process GLR_RESTORE_DATA_HLR. This process is a GLR MAP protocol machine
handling VLR restoration and is an initiator to the HLR.
sending an abort message to Process RESTORE_DATA_GLR.
Process GLR_RESTORE_DATA_HLR 19.2.2.2_1(3)

GLR MAP protocol machine Signals to/from the left
handling restore data and are to/from the GLR application.
interfacing to HLR MAP protocol
machine, handling restore data. Signals to/from the right
machine.
IDLE
restore data
MAP_OPEN_Req
MAP_RESTORE_DATA_Req
MAP_DELIMITER_Req
Receive
Open Section 25.1
Cnf.
Vr
OK Error
Wait_For_
HLR_Response Perform MAP Vr Set error
Restore data Negative

Response
Figure 19.2.2/2 (Sheet 1 of 3): Process GLR_RESTORE_DATA_HLR
3GPP
Release 1999 63 3GPP TS 29.120 V3.0.0 (2000-03)

handling restore data and Signals to/from the left
interfacing to HLR MAP protocol
machine, handling restore data.
machine.
Wait_For_
HLR_Response
MAP_RESTORE_
MAP_INSERT_ MAP_Notice_ MAP_U_Abort_ind
DATA_cnf
Insert MAP_Close_
Ch eck Confirmat ion Section 25.2
data
Wait_For_HLR_or_ Idle
negative respon
OK Provider Error, Application_ Set se
User Error, Response
Data Error
Restore data negative
Restore Set negative response
data ack response
Idle
Restore data
negative response
Idle
3GPP
Release 1999 64 3GPP TS 29.120 V3.0.0 (2000-03)

GLR MAP protocol machine are to/from the GLR application.
handling restore data and
interfacing to HLR MAP protocol Wait_For_HLR_or_
machine, handling restore data. are to/from the HLR MAP protocol
Application Response machine.
MAP_INSERT_
SUBSCRIBER_
MAP_RESTORE_ DATA_ind
DATA_cnf
Insert Insert Insert
Subscriber Subscriber Subscriber
Check Confirmation Section 25.2 data Data ack Data negative
response
OK Provider Error,
User Error, Set user error
Data Error
Restore Set negative

data ack response MAP_Insert_
Subscriber_Data_
response
Restore data
negative response Wait_For_HLR_or_
Idle
MAP_Notice_
Abort Indication MAP_U_Abort_ind
MAP_P_Abort_ind
MAP_Close_ind
Map_U_Abort_
request MAP_Close_
request Abort
Set
negative respon se
Update Location negative

response
Idle
3GPP
Release 1999 65 3GPP TS 29.120 V3.0.0 (2000-03)
20 Operations and maintenance procedures
20.1 General
The Operations and Maintenance procedures are needed for operating and maintaining the UMTS PLMN network.
The following procedures exist for operation and maintenance purposes:
i) Tracing procedures;
ii) Subscriber Data Management procedures;
iii) Subscriber Identity procedures.
The following application contexts refer to complex MAP Users consisting of several processes:
- subscriberDataManagementContext;
- tracingContext.
These two application contexts need a co-ordinating process in the VLR or in the SGSN. Refer to the 3GPP TS 29.002
for detail procedures.
The Subscriber Data Management procedures are only procedures that impact to the GLR. The following subclause
describes the Subscriber Identity procedures in the GLR.
20.2 Subscriber data management procedures

20.2.1 General
Two types of subscriber data management procedures exist in the Mobile Application Part
i) Subscriber Deletion;
ii) Subscriber Data Modification.
No requirements have been identified for the Subscriber creation and subscriber data interrogation procedures.
The subscriber deletion and subscriber data modification procedures are initiated by the OMC (see figures 20.2.1/1,
20.2.1/2, 20.2.1/3 and 20.2.1/4).
+-----+ +-----+ +------+ +-------+

│ VLR │ │ GLR │ │ HLR │ │ OMC │
+-----+ +-----+ +------+ +-------+
│ │ │1. │
│ │2. +<---------------│
│2. +<---------------│ │
+<---------------│ │ │
│ 3.│ │ │
+--------------->│ 3.│ │
│ +--------------->│ 4.│
│ │ +--------------->│
│ │ │ │
1) Delete Subscriber.
2) MAP_CANCEL_LOCATION.
3) MAP_CANCEL_LOCATION_ACK.
4) Subscriber Deleted.
Figure 20.2.1/1: Subscriber deletion procedure
3GPP
Release 1999 66 3GPP TS 29.120 V3.0.0 (2000-03)
In the subscriber deletion procedure the subscriber data should be removed from the VLR and from the HLR. The HLR
uses the MAP_CANCEL_LOCATION service.
+-----+ +-----+ +------+ +-------+
│SGSN │ │ GLR │ │ HLR │ │ OMC │
+-----+ +-----+ +------+ +-------+
│ │ │1. │
│ │2. +<---------------│
│2. +<---------------│ │
+<---------------│ │ │
│ 3.│ │ │
+--------------->│ 3.│ │
│ +--------------->│ 4.│
│ │ +--------------->│
│ │ │ │
1) Delete GPRS Subscriber.

2) MAP_CANCEL_LOCATION.
3) MAP_CANCEL_LOCATION_ACK.
4) GPRS Subscriber Deleted.
Figure 20.2.1/2: Subscriber deletion procedure for GPRS
In the subscriber deletion procedure the subscriber data should be removed from the SGSN and from the HLR. The
HLR uses the MAP_CANCEL_LOCATION service.
+-----+ +-----+ +------+ +-------+
│ VLR │ │ GLR │ │ HLR │ │ OMC │
+-----+ +-----+ +------+ +-------+
│ │ │1. │
│ │2. +<---------------│
│2. +<---------------│ │
+<---------------│ │ │
│ 3.│ │ │
+--------------->│ 3.│ │
│ +--------------->│ 4.│
│ │ +--------------->│
│ │ │ │
1) Modify Subscriber Data.
2) MAP_CANCEL_LOCATION, MAP_INSERT_SUBSCRIBER_DATA or
MAP_DELETE_SUBSCRIBER_DATA.
3) MAP_CANCEL_LOCATION_ACK, MAP_INSERT_SUBSCRIBER_DATA_ACK or
MAP_DELETE_SUBSCRIBER_DATA_ACK.
4) Subscriber Data Modified.
Figure 20.2.1/3: Subscriber data modification procedure
+-----+ +-----+ +------+ +-------+

│SGSN │ │ GLR │ │ HLR │ │ OMC │
+-----+ +-----+ +------+ +-------+
│ │ │1. │
│ │2. +<---------------│
│2. +<---------------│ │
+<---------------│ │ │
│ 3.│ │ │
+--------------->│ 3.│ │
│ +--------------->│ 4.│
│ │ +--------------->│
│ │ │ │
1) Modify Subscriber Data.

2) MAP_CANCEL_LOCATION, MAP_INSERT_SUBSCRIBER_DATA or
MAP_DELETE_SUBSCRIBER_DATA.
3) MAP_CANCEL_LOCATION_ACK, MAP_INSERT_SUBSCRIBER_DATA_ACK or
MAP_DELETE_SUBSCRIBER_DATA_ACK.
4) Subscriber Data Modified.
Figure 20.2.1/4: Subscriber data modification procedure for GPRS
3GPP
Release 1999 67 3GPP TS 29.120 V3.0.0 (2000-03)
In the subscriber data modification procedure the subscriber data is modified in the HLR and when necessary also in the
VLR or in the SGSN. The HLR initiates either the MAP_INSERT_SUBSCRIBER_DATA,
MAP_DELETE_SUBSCRIBER_DATA or MAP_CANCEL_LOCATION service depending on the modified data.
20.2.2 Procedures in the GLR
20.2.2.1 Subscriber deletion procedure

The subscriber deletion procedure in the GLR is described in the subclause 19.
20.2.2.2 Subscriber data modification procedure

When receiving either the MAP_INSERT_SUBSCRIBER_DATA indication or the
MAP_DELETE_SUBSCRIBER_DATA indication, the GLR checks the parameters and data in the primitive. Data
errors are reported as an unexpected data value error or a data missing error depending on the nature of the error.
After receiving the first MAP_INSERT_SUBSCRIBER_DATA indication, the GLR will check the IMSI that is
included in the primitive. If the IMSI is unknown, the error "Unidentified subscriber" is returned.
If the GLR does not support received basic or supplementary services or the network feature Operator Determined
Barring, or there is a problem with Regional Subscription Data then this is reported to the HLR.
If the entire MSC area that covered the VLR wherein the subscriber is registered is restricted due to regional
subscription, this is reported to the HLR.
If the updating of the subscriber data is not possible, the GLR will initiate the MAP_U_ABORT request primitive.
If the updating is successful in the GLR, the GLR will initiate the MAP_INSERT_SUBSCRIBER_DATA request or the
MAP_DELETE_SUBSCRIBER_DATA request to the VLR or to the SGSN wherein the subscriber is registered.
The subscriber data modification procedure in the GLR is shown in the figures 20.2.2.2/1, 20.2.2.2/2, 20.2.2.2/3,
20.2.2.2/4, 20.2.2.2/5 and 20.2.2.2/6.
3GPP
Release 1999 68 3GPP TS 29.120 V3.0.0 (2000-03)
Process INS_SUBS_DATA_GLR 20.2.2.2.1_1(3)

Figure 20.2.2.2/1: The insert subscriber data Arrows to left are to VLR
process in the GLR Arrows to right are to HLR
NULL
Receive
Open Ind
OK 'Vr' 'Error'
Wait_For_
indication NULL
MAP_INSERT_
SUBSCRIBER_ MAP MAP_U_ABORT_ind.
DATA ind NOTICE_ind MAP_P_ABORT_ind
MAP_CLOSE_ind
MAP_CLOSE_
req
Check_
Indication
Ok Error
Parameter OK
No
Yes
IMSI Known
No
Yes
Set UE= Set UE=
Unindentified Unexpected
Subscriber Data value
MAP_INSERT_SUBSCRIBER_DATA_rsp
MAP_CLOSE_Req
Figure 20.2.2.2/1 (Sheet 1 of 3): Process INS_SUBS_DATA_GLR
3GPP
Release 1999 69 3GPP TS 29.120 V3.0.0 (2000-03)

MAP_OPEN_Req
MAP_INSERT_SUBSCRIBER_DATA_Req
MAP_DELIMITER
Recieve
Open Cnf
Vr, Error
OK
MAP_U_
ABORT_req
WF_
PRIMITIVE
_OR_CLOSE
MAP_CLOSE_
MAP MAP_U_ABORT_ind. MAP_CLOSE MAP_ MAP_U_ABORT_ind.
ind.
NOTICE_ind MAP_P_ABORT_ind ind. NOTICE_ind MAP_P_ABORT_ind.
MAP_CLOSE_MAP_CLOSE_
MAP_U_ MAP_CLOSE_ MAP_CLOSE_
req req ABORT_ind req req
MAP_U_ Set Not

ABORT_ind Confirmed
by HLR
Set Not
Confirmed MAP U ABORT req
by HLR
3GPP
Release 1999 70 3GPP TS 29.120 V3.0.0 (2000-03)

WF_
PRIMITIVE
_OR_CLOSE
MAP_INSERT
SUBSCRIBER_ MAP_INSERT_
DATA_ind SUBSCRIBER_
DATA_cnf
Parameters No Check_
OK Confimation
Yes
User error, Provider error

OK Data error
MAP_INSERT_ Set UE=
SUBSCRIBER_ Unexpected
DATA_req Data Value MAP_U_
MAP_DELIMITER_ ABORT_req
req
MAP_INSERT_
SUBSCRIBER_ Service Yes MAP_U_
DATA_rsp unsupported ABORT_req
MAP_DELIMITER_ in VLR ?
req GLR
No internal
action
Roaming_restriction_due_to_
unsupported_feature_or_ Yes
MSC_are_restricted_received
GLR
No internal
action
MAP_INSERT_SUBSCRIBER_
DATA_rsp
MAP_DELIMITER_req
Save subscriber data
WF_
PRIMITIVE
_OR_CLOSE
3GPP
Release 1999 71 3GPP TS 29.120 V3.0.0 (2000-03)
Process INS_GPRS_SUBS_DATA_GLR 20.2.2.2.2_1(3)

Figure 20.2.2.2/2: The insert subscriber data Arrows to left are to SGSN
NULL
Receive
Open Ind
OK 'Vr' 'Error'
Wait_For_
indication NULL
MAP_INSET_
SUBSCRIBER_ MAP_ MAP_U_ABORT_ind.
DATA ind NOTICE_ind MAP_P_ABORT_ind
MAP_CLOSE_ind
MAP_CLOSE_
req
Check_
Indication
OK Error
Parameter OK
No
Yes
IMSI Known
No
Yes
Set UE= Set UE=
Unindentified Unexpected
Subscriber Data value
MAP_INSERT_SUBSCRIBER_DATA_rsp
MAP_CLOSE_req
Figure 20.2.2.2/2 (Sheet 1 of 3): Process INS_GPRS_SUBS_DATA_GLR
3GPP
Release 1999 72 3GPP TS 29.120 V3.0.0 (2000-03)

MAP_OPEN_Req
MAP_INSERT_SUBSCRIBER_DATA_Req
MAP_DELIMITER
Recieve
Open conf
Vr, Error
OK MAP_U_
ABORT_req
WF_
PRIMITIVE
_OR_CLOSE
MAP_CLOSE_
MAP MAP_U_ABORT_ind. MAP_CLOSE MAP_ MAP_U_ABORT_ind.
ind.
NOTICE MAP_P_ABORT_ind ind. NOTICE ind MAP_P_ABORT_ind.
MAP_CLOSE_MAP_CLOSE_ MAP_CLOSE_
MAP_U_ABORT_ind MAP_CLOSE_req
req req req
Set Not
MAP_U_ABORT_ind Confirmed
by HLR
Set Not
Confirmed MAP U ABORT req
by HLR
3GPP
Release 1999 73 3GPP TS 29.120 V3.0.0 (2000-03)

WF_
PRIMITIVE
_OR_CLOSE
MAP_INSERT
SUBSCRIBER_ MAP_INSERT_
DATA_ind SUBSCRIBER_
DATA_cnf
Parameters No
OK Check_
Confimation
Yes
User error, Provider error
OK Data error
MAP_U_
MAP_INSERT_
Set UE= ABORT_req
SUBSCRIBER_
DATA_req Unexpected
MAP_DELIMITER_ Data Value
req
MAP_U_
ABORT_req
MAP_INSERT_
SUBSCRIBER_
DATA_rsp
MAP_DELIMITER_
req Service Yes
unsupported
in VLR ? GLR
internal
No action
Roaming_restriction_due_to_
unsupported_feature_or_ Yes
MSC_are_restricted_received
GLR
No internal
action
MAP_INSERTt_SUBSCRIBER_
DATA_rsp
MAP_DELIMITER_req
Save subscriber data
WF_
PRIMITIVE
_OR_CLOSE
3GPP
Release 1999 74 3GPP TS 29.120 V3.0.0 (2000-03)
Process Delete_Subscriber_Data_GLR 20.2.2.2.3(1)

Figure 20.2.2.2/3: The delete subscriber data Arrows to left are to VLR
NULL
Receive
Open Ind
OK 'Vr' 'Error'
Wait_For_
indication NULL
MAP_DELETE_
SUBSCRIBER_
DATA ind
Check_
Indication
Error
Subscriber Know
No
Yes
Services registered in Set UE= Set Not

a GLR Unindentified Confirmed
Subscriber by HLR
Yes
No
Delete_
Subs_ Figure 20.2.2.2/5
Data_GLR
OK
Delete Subscriber Error
Data in the GLR MAP_DELETE_SUBSCRIBER_DATA_rsp
MAP_CLOSE_req
Figure 20.2.2.2/3: Process Delete_Subscriber_Data_GLR
3GPP
Release 1999 75 3GPP TS 29.120 V3.0.0 (2000-03)
Process Delete_GPRS_Subscriber_Data_GLR 20.2.2.2.4(1)

Figure 20.2.2.2/4: The delete subscriber data Arrows to left are to SGSN
NULL
Receive
Open Ind
OK
'Vr' 'Error'
Wait_For_
indication NULL
MAP_DELETE_
SUBSCRIBER_
DATA ind
Check_
Indication
Error
Subscriber Know
No
Yes
Services registered in Set UE= Set Not

a GLR Unindentified Confirmed
Subscriber by HLR
Yes
No
Delete_
GPRS_Subs_ Figure 20.2.2.2/6
Data_GLR
OK
Delete Subscriber Error
Data in the GLR MAP_DELETE_SUBSCRIBER_DATA_rsp
MAP_CLOSE_req
Figure 20.2.2.2/4: Process Delete_GPRS_Subscriber_Data_GLR
3GPP
Release 1999 76 3GPP TS 29.120 V3.0.0 (2000-03)
Macrodefinition Dele te_Subs_Data_G LR 20.2.2.2.5(1)

Figure 20.2. 2.2/ 5: The delete subscriber dat a Arrows to left are to VLR Arrows
macro in the G LR to right are to HLR
MAP_OPEN_req
MAP_DELETE_SUBSCRIBER_DATA_req
MAP_DELIMIT ER
Receive
Open c nf
Ok
W ait_For_ Vr, Error

Confirm
MAP_CLOSE_
in d. MAP_NO TICE MAP_U_ABO RT_ind. MAP_DELETE_ MAP_NO TICE MAP_U_ABO RT_ind
in d MAP_P_ABO RT_ind SUBSCRIBER_ in d MAP_P_ABO RT_ind
DATA cnf MAP_CLOSE_ind
MAP_CLOSE_req MAP_CLOSE_
re q
MAP_CLOSE_
Req MAP_U_ABO RT_ind.
Error
Error Error
No
MSC_Area_Restricted_received or "Roam
Yes
ing_Restricted_Due_
To_U nsup port ed _F ea ture"
No
Yes
MSC_Area_ MSC_Area_
Rerstrivted_Flag_ Rerstricted_Flag_ MAP U ABORT req
=not Restricted =Restricted
Error
MAP_DELETE_
SUBSCRIBER_ MAP_DELETE_
SUBSCRIBER_
DATA_Cnf
DATA_Cnf
Error
OK
Figure 20.2.2.2/5: Macro Delete_Subs_Data_GLR
3GPP
Release 1999 77 3GPP TS 29.120 V3.0.0 (2000-03)
Macrodefinition Dele te_GPRS_Subs_Data_GLR 20.2.2.2.6(1)

Figure 20.2. 2.2/ 6: The delete subscriber data Arrows to left are to SGSN Arrows
macro in the G LR to right are to HLR
MAP_OPEN_req
MAP_DELETE_SUBSCRIBER_DATA_req
MAP_DELIMIT ER
Receive
Open Cnf
Ok
W ait_For_ Vr, Error

Confirm
MAP_CLOSE_
in d. MAP_NO TICE MAP_U_ABO RT_ind. MAP_DELETE_ MAP_NO TICE MAP_U_ABO RT_ind
in d MAP_P_ABO RT_ind SUBSCRIBER_ in d MAP_P_ABO RT_ind
DATA Cnf MAP_CLOSE_ind
MAP_CLOSE_req MAP_CLOSE_
re q
MAP_CLOSE_
Req MAP_U_ABO RT_ind.
Error
Error Error
No
Yes SGSN_Area_Res tricted_received or "Roam
ing_Restricted_Due_
No To_U nsup port ed _F ea ture"
Yes
SGSN _Are a_ SG SN_Area_

Rerstrivted_Flag_ Rerstricted_Flag_ MAP U ABORT req
=not Restricted =Restricted
Error
MAP_DELETE_
SUBSCRIBER_ MAP_DELETE_
SUBSCRIBER_
DATA_Cnf
DATA_Cnf
Error
OK
Figure 20.2.2.2/6: Macro Delete_GPRS_Subs_Data_GLR
20.3 Subscriber Identity procedure

In the subscriber identity procedure the IMSI of the subscriber is retrieved from the HLR. The procedure is shown in
figure 20.3/1.
3GPP
Release 1999 78 3GPP TS 29.120 V3.0.0 (2000-03)
+-----+ +------+ +------+ +------+

¦ OMC ¦ ¦ VLR ¦ ¦ GLR ¦ ¦ HLR ¦
¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦
+-----+ +------+ +------+ +------+
¦ 1.¦ ¦ ¦
+ - - - - >¦ 2.¦ 2.¦
¦ +------------->¦------------>¦
¦ ¦ 3. ¦ 3. ¦
¦ 4. +<-------------+<------------¦
+< - - - - ¦ ¦ ¦
¦ ¦ ¦ ¦
1) Identity request.
2) MAP_SEND_IMSI.
3) MAP_SEND_IMSI_ACK.
4) Identity confirm.
Figure 20.3/1: The subscriber identity procedure
20.3.1 Subscriber identity procedure in the GLR

The subscriber identity procedure in the GLR is shown in figure 20.3/2.
3GPP
Release 1999 79 3GPP TS 29.120 V3.0.0 (2000-03)
Process Send_IMSI_GLR 20.3.2_1(2)

Figure 20.3/2: The send IMSI process in the GLR
Idle Arrows to left are to VLR
Arrows to right are to HLR
Receive
Open_ind
Wait For
Response Vr Error
MAP_NOTICE_
MAP_SEND_ Perform Vr
ind
IMSI_ind Dialogue
MAP_CLOSE_
Check
req Idle Idle
Indigation
OK
Subscriber Error
Idle Known
No
Yes
Set UE=
Unknown
Subscriber
MAP_SEND_IMSI_rsp
MAP_CLOSE_req
MAP_OPEN_req
MAP_SEND_IMSI_req
MAP_SWLIMITER_req
Receive_
Open_Cnf
Vr, Error Ok
MAP_U_
ABORT_req WF_IDENTITY_
RESULT Idle
Idle
Figure 20.3/2 (Sheet 1 of 2): Process Send_IMSI_GLR
3GPP
Release 1999 80 3GPP TS 29.120 V3.0.0 (2000-03)
Process Send_IMSI_GLR 20.3.2_2(2)

Figure 20.3/2: The send IMSI process in the GLR Arrows to left are to VLR
Arrows to right are to HLR
WF_IDENTITY_
RESULT
MAP_SEND_
MAP_NOTICE_ MAP_CLOSE_ind
IMSI_cnf
ind MAP_U_ABORT_ind
MAP_P_ABORT_ind
Check MAP_CLOSE_
Confirmation req
OK Error
Set error
MAP_U_
ABORT_req
MAP_SEND_IMSI_rsp
MAP_CLOSE_req
Idle
Idle
Figure 20.3/2 (Sheet 2 of 2): Process Send_IMSI_GLR
3GPP
Release 1999 81 3GPP TS 29.120 V3.0.0 (2000-03)
21 Call handling procedures
21.1 General
The MAP call handling procedures are used:
1. to retrieve routeing information to handle a mobile terminating call;
2. to transfer control of a call back to the GMSC if the call is to be forwarded;
3. to retrieve and transfer information between anchor MSC and relay MSC for inter MSC group calls /
broadcast calls;
4. to allocate resources in an SIWFS;
5. to handle the reporting of MS status for call completion services;
6. to handle the notification of remote user free for CCBS.
Items 1, 5 and 6 are only procedures that have impact to the GLR. The following subclause describes the function of the
GLR related to these procedures.
3GPP
Release 1999 82 3GPP TS 29.120 V3.0.0 (2000-03)
21.2 Retrieval of routing information

21.2.1 General
The message flows for successful retrieval of routeing information for a mobile terminating call are shown in figure
21.2.1/1 (mobile terminating call which has not been optimally routed) and 21.2.1/2 (mobile-to-mobile call which has
been optimally routed).
Network Gateway
MSC HLR GLR VLR
I_IAM (note2) MAP_SEND_ROUTING

INFO
MAP_PROVIDE_SUB- MAP_PROVIDE_SUB-
(note 1) SCRIBER_INFO SCRIBER_INFO
MSC
MAP_SEND_ROUTING SCRIBER_INFO ack SCRIBER_INFO ack
INFO ack
MAP_SEND_ROUTING
INFO
MAP_PROVIDE_ROAMING MAP_PROVIDE_ROAMING
NUMBER NUMBER
MAP_SEND_ROUTING NUMBER ack NUMBER ack
INFO ack
I_IAM
Notes:
xxx = Optional Procedure
NOTE 1: This service may also be used by an ISDN exchange for obtaining routing information from the HLR. NOTE 2:
TUP or ISUP may be used in signalling between MSCs, depending on the network type between the
MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations and ETSI
specification:
Q.721-725 - Telephone User Part (TUP);
ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP)
version 2 for the international interface; Part 1: Basic services.
NOTE 3: As a network operator option, the HLR sends
MAP_PROVIDE_SUBSCRIBER_INFORMATION to the VLR. For further details on the CAMEL procedures
refer to GSM 3GPP TS 03.78.
Figure 21.2.1/1: Message flow for retrieval of routeing information (non-optimally routed call)
3GPP
Release 1999 83 3GPP TS 29.120 V3.0.0 (2000-03)
Network Gateway
MSC HLR GLR VLR
I_IAM (note) MAP_SEND_ROUTING

INFO
SCRIBER_INFO SCRIBER_INFO
SCRIBER_INFO ack SCRIBER_INFO ack
OR
NUMBER NUMBER
MSC
MAP_SEND_ROUTING NUMBER ack NUMBER ack
INFO ack
I_IAM
Figure 21.2.1/2: Message flow for retrieval of routeing information (optimally routed call)
Notes:
xxx = Optional Procedure.
For Optimal Routeing phase 1, only one of the information flows for Provide Subscriber Info and Provide Roaming
Number is used. For later phases of Optimal Routeing, the HLR may return a
MAP_SEND_ROUTEING_INFORMATION ack after the Provide Subscriber Info information flow, and the GMSC
may send a second MAP_SEND_ ROUTEING_INFORMATION, which will trigger the Provide Roaming Number
information flow.
TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For
further details on the TUP and ISUP procedures refer to the following CCITT. Recommendations & ETSI
specification:
Q.721-725 - Telephone User Part (TUP);
ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP)
version 2 for the international interface; Part 1: Basic services.
21.2.2 Process in the GLR to provide a roaming number

The MAP process in the GLR to provide a roaming number for a mobile terminating call is shown in figure 21.2.2/1
(Process PRN_Receive_GLR) and figure 21.2.2/2 (Process PRN_Send_GLR). The MAP process invokes a macro not
defined in this subclause; the definition of this macro can be found as follows:
- Receive_Open_Ind see subclause 25.1.
- Receive_Open_Cnf see subclause 25.1.
- Check_Confirmation see subclause 25.2.
3GPP
Release 1999 84 3GPP TS 29.120 V3.0.0 (2000-03)
Process PRN_Receive_GLR 21.2.2.1(1)

Figure 21.2.2/1: Process in the GLR
to respond to a requet Signals to/from the left are
routeing information to/from the HLR; signals
to/from the right are
to/from the GLR Call
process
Idle
Receive
Open Ind
Vr Error
OK
Perform MAP Wait For
Vr Dialogue Service Idle
Indication
Idle
MAP_P_
ABORT_ind MAP_
MAP_PROVIDE_ROAMING_NUMBER_ind. NOTICE_ind
Provide Roaming Number MAP_

Idle To GLR Call process CLOSE_req
Wait For
Response Idle
Provide Roaming
Number ack Provide Roaming
Number negative Abort
response
MAP_U_
Set result Set error ABORT_req
Idle
MAP_PROVIDE_ROAMING_NUMBER_rsp.
Idle
Figure 21.2.2/1: Process PRN_Receive_GLR
3GPP
Release 1999 85 3GPP TS 29.120 V3.0.0 (2000-03)
Process PRN_Send_GLR 21.2.2.2(1)

Figure 21.2.2/2: Process in the GLR Signals to/from the left
to respond to a requet are to/from the GLR Call; process
routeing information signals to/from the right
are to/from the VLR
Idle
Provide
Roaming
Number
MAP_Open_req MAP_PROVIDE_ROAMING_NUMBER_req.
MAP_DELIMITER_req
Receive
Open cnf
Vr Error
OK
Provide Roaming
Perform MAP Vr Number negative
response
Wait For
Response
MAP_PROVIDE_
ROAMING_ NUMBER_ MAP_U_ABORT_ind.
MAP_P_ABORT_ind MAP_NOTICE_ind.
cnf
Check
Confrmation MAP_CLOSE_req.
OK Error
Provide Roaming
Number ack Provide Roaming
Number negative Abort Abort
response
Figure 21.2.2/2: Process PRN_Send_GLR
3GPP
Release 1999 86 3GPP TS 29.120 V3.0.0 (2000-03)
21.2.3 Process in the GLR to provide subscriber information

The MAP process in the GLR to provide subscriber information for a mobile terminating call is shown in figure 21.2.3/1
(Process PSI Receive_GLR) and figure 21.2.3/2 (Process PSI Send_GLR). The MAP process invokes a macro not
defined in this subclause; the definition of this macro can be found as follows:
Receive_Open_Ind see subclause 25.1.
Receive_Open_Cnf see subclause 25.1.
Check_Confirmation see subclause 25.2.
3GPP
Release 1999 87 3GPP TS 29.120 V3.0.0 (2000-03)
Process PSI_Receive_GLR 21.2.3.1(1)

routeing information to/from the HLR; signals
process
Idle
Receive
Open Ind
Vr Error
OK
Indication
Idle
MAP_P_
ABORT_ind MAP_
MAP_PROVIDE_SUBSCRIBER_INFO_ind NOTICE_ind
Idle Provide Subscriber Info To MAP_

GLR Call process CLOSE_req
Wait For
Response Idle
Provide_Subscriber
Provide_Subscriber
_Info ack Abort
_Info negative
response
MAP_U_
Idle
MAP_PROVIDE_SUBSCRIBER_INFO_rsp.
Idle
Figure 21.2.3/1 : Process PSI_Receive GLR
3GPP
Release 1999 88 3GPP TS 29.120 V3.0.0 (2000-03)
Process PSI_Send_GLR 21.2.3.2(1)

routeing information signals to/from the right
are to/from the VLR
Idle
Provide
Subscriber
Info
MAP_Open_req MAP_PROVIDE_SUBSCRIBER_INFO_req
MAP_DELIMITER_req
Receive
Open cnf
Vr Error
OK
Provide Subscriber
Perform MAP Vr Info negative
response
Wait For
Response
MAP_PROVIDE_
SUBSCRIBER_INFO_ MAP_U_ABORT_ind
MAP_P_ABORT_ind MAP_NOTICE_ind.
cnf
Check
Confrmation MAP_CLOSE_req.
OK Error
Provide
Subscriber Provide Subscriber
Info negative Abort Abort
Info ack
response
Figure 21.2.3/2 : Process PSI_Send_GLR
3GPP
Release 1999 89 3GPP TS 29.120 V3.0.0 (2000-03)
21.3 Setting of Reporting State

21.3.1 General
In case the HLR received the CCBS request message from the other HLR for CCSB monitoring, the message flow for
setting the reporting state is shown in figure 21.3.1/1. The message flow shown in figure 21.3.1/1 shall also be applied in
case for stop monitoring. The stage2 specification for the interaction with CCBS in a GLR is in 3GPP TS 23.119.
VLR GLR HLR
MAP_SET_REPORTING_STATE MAP_SET_REPORTING_STATE
< <
MAP_SET_REPORTING_STATE ack MAP_SET_REPORTING_STATE ack
------------------------------------------------>--------------------------------------------------------------->
Figure 21.3.1/1: Message Flow for Setting the Reporting State
21.3.2 Process in the GLR to set the reporting state

The MAP process in the GLR to set the reporting state is shown in figures 21.3.2/1 and 21.3.2/2. The MAP
process invokes a macro not define in this subclause; the definition of this macro can be found as follows:
Receive_Open_Cnf see subclause 25.1.
Check_Confirmation see subclause 25.2.
Set the reporting state
When receiving the MAP_SET_REPORTING_STATE indication, the MAP user in the GLR transfers the information
to the VLR in the MAP_ SET_REPORTING_STATE request.
The GLR then awaits the receipt of the MAP_ SET_REPORTING_STATE confirm from the VLR. The MAP user in
the GLR shall transfer the information contained in this primitive to the HLR in the MAP_ SET_REPORTING_STATE
response without checking its contents.
3GPP
Release 1999 90 3GPP TS 29.120 V3.0.0 (2000-03)
Process Reporting_State_Receive_GLR 21.3.2.1(1)

reporting state to/from the HLR; signals
process
Idle
Receive
Open Ind
Vr Error
OK
Indication
Idle
MAP_P_
ABORT_ind MAP_
MAP_SET_REPORTING_ind NOTICE_ind
Idle Set Reporting MAP_

To GLR Call process CLOSE_req
Wait For
Response Idle
Set Reporting
ack Set Reporting
negative response Abort
MAP_U_
Idle
MAP_SET_REPORTING_rsp
Idle
Figure 21.3.2/1: Process Reporting_State_Receive_GLR
3GPP
Release 1999 91 3GPP TS 29.120 V3.0.0 (2000-03)
Process Reporting_State_Send_GLR 21.3.2.2(1)

reporting state signals to/from the right
are to/from the VLR
Idle
Set Reporting
MAP_Open_req
MAP_SET_REPORTING_req
MAP_DELIMITER_req
Receive
Open cnf
Vr Error
OK
Set Reporting negative
Perform MAP Vr response
Wait For
Response
MAP_SET_REPORTING_
MAP_U_ABORT_ind
cnf MAP_NOTICE_ind
MAP_P_ABORT_ind
Check
Confrmation MAP_CLOSE_req
OK Error
Set Reporting
ack Set Reporting
negative response Abort Abort
Figure 21.3.2/2: Process Reporting_State_Send_GLR
3GPP
Release 1999 92 3GPP TS 29.120 V3.0.0 (2000-03)
21.4 Status Reporting

21.4.1 General
In case that the monitored subscriber becomes to the idle state, the message flow for reporting subscriber's state to the
HLR is shown in figure 21.4.1/1. The stage2 specification for the interaction with CCBS in a GLR is in 3GPP TS
23.119.
VLR GLR HLR
MAP_STATUS_REPORT MAP_ STATUS_REPORT
> ->
MAP_STATUS_REPORT ack MAP_ STATUS_REPORT ack
< <
- --
Figure 21.4.1/1: Message Flow for Status Reporting
21.4.2 Process in the GLR for Status Reporting

The MAP process in the GLR to send the status report to the HLR is shown in figures 21.4.1/1 and 21.4.2/2.
Send Status report
When receiving the MAP_STATUS_REPORT indication, the MAP user in the GLR transfers the information to the
HLR in the MAP_ STATUS_REPORT request.
The GLR then awaits the receipt of the MAP_ STATUS_REPORT confirm from the HLR. The MAP user in the GLR
shall transfer the information contained in this primitive to the VLR in the MAP_ STATUS_REPORT response without
checking its contents.
3GPP
Release 1999 93 3GPP TS 29.120 V3.0.0 (2000-03)
Process Status_Report_Receive_GLR 21.4.2.1(1)

status report to/from the HLR; signals
process
Idle
Receive
Open Ind
Vr Error
OK
Indication
Idle
MAP_P_
ABORT_ind MAP_
MAP_STATUS_REPORT_ind NOTICE_ind
Idle Status Report MAP_

To GLR Call process CLOSE_req
Wait For
Response Idle
Status Report
ack Status Report
MAP_U_
Idle
MAP_STATUS_REPORT_rsp
Idle
Figure 21.4.2/1: Process Status_Report_Receive_GLR
3GPP
Release 1999 94 3GPP TS 29.120 V3.0.0 (2000-03)
Process Status_Report_Send_GLR 21.4.2.2(1)

status report signals to/from the right
are to/from the HLR
Idle
Status Report
MAP_Open_req
MAP_STATUS_REPORT_req
MAP_DELIMITER_req
Receive
Open cnf
Vr Error
OK
Status Report negative
Abort response
Wait For
Response
MAP_STATUS_REPORT_
MAP_U_ABORT_ind
cnf MAP_NOTICE_ind
MAP_P_ABORT_ind
Check
OK Error
Status Report
ack Status Report
Figure 21.4.2/2: Process Status_Report_Send_GLR
21.5 Remote User Free

21.5.1 General
The message flow for handling remote user free is shown in figure 21.5.1/1.
3GPP
Release 1999 95 3GPP TS 29.120 V3.0.0 (2000-03)
VLR GLR HLR
MAP_REMOTE_USER_FREE MAP_ REMOTE_USER_FREE
< <
--
MAP_ REMOTE_USER_FREE ack MAP_ REMOTE_USER_FREE ack
------------------------------------------------> -------------------------------------------------
->
Figure 21.5.1/1: Message Flow for Remote User Free
21.5.2 Process in the GLR for Remote User Free

The MAP process in the GLR to handling Remote User Free is shown in figures 21.5.2/1 and 21.5.2/2.
Remote User Free
When receiving the MAP_REMOTE_USER_FREE indication, the MAP user in the GLR transfers the information to
the VLR in the MAP_ REMOTE_USER_FREE request.
The GLR then awaits the receipt of the MAP_REMOTE_USER_FREE confirm from the VLR. The MAP user in the
GLR shall transfer the information contained in this primitive to the HLR in the MAP_REMOTE_USER_FREE
response without checking its contents.
3GPP
Release 1999 96 3GPP TS 29.120 V3.0.0 (2000-03)
Process Remote_User_Free_Receive_GLR 21.5.2.1(1)

remote user free to/from the HLR; signals
process
Idle
Receive
Open Ind
Vr Error
OK
Indication
Idle
MAP_P_
ABORT_ind MAP_
MAP_REMOTE_USER_FREE_ind NOTICE_ind
Idle Remote User Free To MAP_

GLR Call process CLOSE_req
Wait For
Response Idle
Remote User Free

ack Remote User Free
MAP_U_
Idle
MAP_REMOTE_USER_FREE_rsp
Idle
Figure 21.5.2/1: Process Remote_User_Free_Receive_GLR
3GPP
Release 1999 97 3GPP TS 29.120 V3.0.0 (2000-03)
Process Remote_User_Free_Send_GLR 21.5.2.2(1)

remote user free signals to/from the right
are to/from the VLR
Idle
Remote User Free
MAP_Open_req
MAP_REMOTE_USER_FREE_req
MAP_DELIMITER_req
Receive
Open cnf
Vr Error
OK
Remote User Free negative
Perform MAP Vr response
Wait For
Response
MAP_U_ABORT_ind
MAP_REMOTE_USER_FREE_ MAP_P_ABORT_ind
cnf MAP_NOTICE_ind
Check
OK Error
Remote User Free
ack Remote User Free
Figure 21.5.2/2: Process Remote_User_Free_Send_GLR
3GPP
Release 1999 98 3GPP TS 29.120 V3.0.0 (2000-03)
22 Supplementary services procedures
22.1 Functional supplementary service processes

22.1.1 Functional supplementary service process co-ordinator for GLR
Any functional SS process in the GLR starts by the GLR receiving a MAP-OPEN service indication. If that service is
successful, the GLR can handle supplementary service indications from the VLR. Table 21.1/1 shows the co-ordinating
process' reaction on receipt of specific SS service indications from the VLR. After the relevant process is invoked, the
received service indication is sent to that process, and the co-ordinating process terminates.
Table 21.1/1: Relationship between received service indication and invoked process in the GLR
Service indication received Process invoked
MAP_REGISTER_SS_ind REGISTER_SS_GLR
MAP_ERASE_SS_ind ERASE_SS_GLR
MAP_ACTIVATE_SS_ind ACTIVATE_SS_GLR
MAP_DEACTIVATE_SS_ind DEACTIVATE_SS_GLR
MAP_INTERROGATE_SS_ind INTERROGATE_SS_GLR
MAP_REGISTER_PASSWORD REGISTER_PASSWORD_GLR
Figure 22.1/1 shows the co-ordinating process in the GLR.
3GPP
Release 1999 99 3GPP TS 29.120 V3.0.0 (2000-03)
Process SS_Coordinator_GLR 22.1.1_1(2)

Figure 22.1/1: Supplementary Service Coordination process in the GLR, to identity which
functional supplementary service process be invoked.

are to/from the VLR via
the MAP provider;
signals to/from the right
are to/from the child process
NULL
Receive_
Open_ind Section25.1
Error v1
Wait_for_ Perform_
service_ind MAP_V1_
Dialogue
NULL
MAP_
REGISTER_ MAP_ MAP_ MAP_ MAP_INTER- MAP_REGISTER_ PASSWARD_
SS_ind ERASE_ ACTIVATE_ DEACTIVATE_ ROGATE_ SS_ind
SS_ind SS_ind SS_ind SS_ind
Register_ Register_
SS_GLR Erase_ Activate_ Deactivate_ Interrogate_ Passward_
SS_GLR SS_GLR SS_GLR SS_GLR SS_GLR
MAP_ MAP_ MAP_ MAP_ MAP_ MAP_REGISTER_

REGISTER_ ERASE_ ACTIVATE_ DEACTIVATE_ INTERROGATE_ PASSWARD_
SS_ind SS_ind SS_ind SS_ind SS_ind SS_ind
Relay_Info
MAP_
NOTICE_ MAP_U_ABORT_ind
ind MAP_P_ABORT_ind
MAP_CLOSE_ind
MAP_
CLOSE_
ind
NULL
Figure 22.1/1 (sheet 1 of 2): Process SS_Coordinator_GLR
3GPP
Release 1999 100 3GPP TS 29.120 V3.0.0 (2000-03)
Process SS_Coordinator_GLR 22.1.1_2(2)

Figure 22.1/1: Supplementary Service Coordination process in the GLR, to identity which
functional supplementary service process be invoked.

are to/from the VLR via
the MAP provider;
Relay_Info
*FROM
PROVIDER MAP_U_ABORT_ind *FROM MAP_U_ABORT_ind
MAP_P_ABORT_ind OFFSPRING MAP_CLOSE_ind
MAP_CLOSE_ind
*TO
OFFSPRING *TO *TO *TO
OFFSPRING PROVIDER PROVIDER
Relay_Info
NULL Relay_Info NULL
Figure 22.1/1 (sheet 2 of 2): Process SS_Coordinator_GLR
22.1.2 Call completion supplementary service process co-ordinator for GLR

The MAP co-ordinating process in the GLR to handle a dialogue opened with the call Completion application context is
shown in figure 22.1/2. The MAP process invokes a macro not defined in this subclause; the definition of this macro
can be found as follows:
3GPP
Release 1999 101 3GPP TS 29.120 V3.0.0 (2000-03)
Any call completion SS process in the GLR starts by the GLR receiving a MAP-OPEN service indication. If that
service is successful, the GLR can handle call completion supplementary service indications from the VLR. Table
22.1/2 shows the co-ordinating process' reaction on receipt of specific call completion SS service indications from the
VLR. After the relevant process is invoked, the received service indication is sent to that process.
Table 22.1/2: Relationship between received service indication and invoked process in the GLR
Service indication received Process invoked

MAP_REGISTER_CC_ENTRY_ind REGISTER_CC_ENTRY_GLR
MAP_ERASE_CC_ENTRY_ind ERASE_CC_ENTRY_GLR
After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked
process until a request or an indication for dialogue termination is received.
The Call_Completion Co-ordinator is shown in figure 22.1/2.
3GPP
Release 1999 102 3GPP TS 29.120 V3.0.0 (2000-03)
Process CC_Coord_GLR 22.1.2(1)

Figure 22.1/2: Coordinating process in the GLR to Signals to/from the left
handle dialogue opened with are to/from the VLR via
the AC Call Completion Context the MAP provider;
Idle
Receive_
Open_ Section 25.1
ind
OK Vr, Error
Wait_for_
service_ind Idle
MAP_
REGISTER_ MAP_ MAP_ MAP_U_ABORT_ind
CC_ENTRY_ ERASE_ NOTICE_ MAP_P_ABORT_ind
ind CC_ENTRY_ ind MAP_CLOSE_ind
ind
Register_CC_ MAP_
RNTRY_GLR Erase_CC_
ENTRY_GLR CLOSE_
ind
MAP_REGISTER MAP_ERASE_
Idle
CC_ENTRY_ind CC_ENTRY_ind
Relay_Info
*FROM
PROVIDER MAP_U_ABORT_ind *FROM MAP_U_ABORT_ind
MAP_P_ABORT_ind OFFSPRING MAP_CLOSE_ind
MAP_CLOSE_ind
*TO
OFFSPRING *TO *TO *TO
OFFSPRING PROVIDER PROVIDER
Relay_Info
NULL Relay_Info NULL
Figure 22.1/2: Process_CC_Coord_GLR
22.2 Registration procedure

22.2.1 General
The registration procedure is used to register data related to a supplementary service in the HLR. The registration
procedure is a fully transparent communication between the MS and the HLR.
3GPP
Release 1999 103 3GPP TS 29.120 V3.0.0 (2000-03)

Supplementary service registration
When receiving the MAP_REGISTER_SS indication from VLR, the MAP user in the GLR transfers the information to
the HLR in the MAP_REGISTER_SS request without checking the contents of the service indication.
The GLR then awaits the receipt of the MAP_REGISTER_SS confirm from the HLR. The MAP user in the GLR shall
transfer the information contained in this primitive to the VLR in the MAP_REGISTER_SS response without
checking its contents.
Error handling
If at any time during this procedure a MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE or unexpected

MAP_CLOSE indication is received from the VLR concerning the process, a MAP_U_ABORT request indicating
application procedure cancellation is sent to the HLR (if a connection exists). If a MAP_NOTICE indication was
received from the VLR, that dialogue must be closed by sending a MAP_CLOSE request towards the VLR. The process
is terminated.
If a MAP_P_ABORT, MAP_U_ABORT or MAP_CLOSE indication is received from the HLR, a

MAP_U_ABORT request shall be sent to the VLR terminating the process. If a MAP_NOTICE indication was
received from the HLR, that dialogue must be closed by sending a MAP_CLOSE request towards the HLR. The
process terminates.
The registration procedure in the GLR is shown in figure 22.2/1.
3GPP
Release 1999 104 3GPP TS 29.120 V3.0.0 (2000-03)
Process SS_REGISTER_GLR 22.2.1_1(2)

Figure 22.2/1: Mobile Initiated registeration of Signals to/from the left
supplementary service in the GLR are to/from the VLR
are to/from the HLR
unless otherwise stated
NULL
MAP_
REGISTER_ MAP_ MAP_U_ABORT_ind
SS_ind NOTICE_ MAP_P_ABORT_ind
ind MAP_CLOSE_ind
MAP_ MAP_
Including
OPEN_req CLOSE_
- Destination reference = subscriber's IMSI
- Originating reference = GLR number req
MAP_
REGISNTER_
req
MAP_
DELIMITER_
req
Receive_
Open_ Section 25.1
Confirm
OK Vr, Error
Wait_for_
ss_cnf MAP_U_
ABORT_
req
Figure 22.2/1 (sheet 1 of 2): Procedure SS_Register_GLR
3GPP
Release 1999 105 3GPP TS 29.120 V3.0.0 (2000-03)
Process SS_REGISTER_GLR 22.2.1_2(2)

Figure 22.2/1: Mobile Initiated registeration of Signals to/from the left are
supplementary service in the GLR to/from the VLR signals
to/from the HLR unless
otherwise stated
Wait_for_
ss_cnf
MAP_
REGISTER_ MAP_U_ABORT_ind MAP_
SS_cnf MAP_P_ABORT_ind NOTICE_
ind
MAP_P_ yes MAP_

ERROR CLOSE_
req
no
MAP_U_
1 ABORT_
req
MAP_
REGISTER_
SS_rsp
MAP_
CLOSE_
req
MAP_
ind MAP_P_ABORT_ind
MAP_CLOSE_ind
MAP_
CLOSE_
req
MAP_U_
ABORT_
req
Figure 22.2/1 (sheet 2 of 2): Procedure SS_Register_GLR
22.3 Erasure procedure

22.3.1 General
The erasure procedure is used to erase data related to a supplementary service in the HLR. The erasure procedure is a
fully transparent communication between the MS and the HLR.
3GPP
Release 1999 106 3GPP TS 29.120 V3.0.0 (2000-03)

The GLR procedures for erasure are identical to those specified for registration in subclause 22.2. The text and diagrams
in subclause 22.2 apply with all references to registration changed to erasure.
22.4 Activation procedure

22.4.1 General
The activation procedure is used to activate a supplementary service in the HLR. The activation procedure is a fully
transparent communication between the MS and the HLR.

Supplementary service activation
When receiving the MAP_ACTIVATE_SS indication, the MAP user in the GLR transfers the information to the HLR in
the MAP_ACTIVATE_SS request without checking the contents of the service indication.
The GLR may then receive the MAP_GET_PASSWORD indication. This information is transferred to the VLR in the
MAP_GET_PASSWORD request. If a MAP_GET_PASSWORD confirm primitive is received from the VLR, the VLR
initiates the MAP_GET_PASSWORD response towards the HLR.
The GLR will receive the MAP_ACTIVATE_SS confirm from the HLR. The MAP user in the GLR shall transfer the
information contained in this primitive to the VLR in the MAP_ACTIVATE_SS response without checking its contents.
Error handling
The handling of MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE and unexpected MAP_CLOSE in this procedure
is identical to the handling in the Registration procedure in the GLR, see subclause 22.2 of the present document.
The activation procedure in the GLR is shown in figure 22.4/1.
3GPP
Release 1999 107 3GPP TS 29.120 V3.0.0 (2000-03)
Process SS_ACTIVATE_GLR 22.4.1_1(2)

Figure 22.4/1: Activation of supplementary service Signals to/from the left
procedure in the GLR are to/from the VLR via
the MAP provider;
NULL
MAP_
ACTIVATE_ MAP_ MAP_U_ABORT_ind
SS_ind NOTICE_ MAP_P_ABORT_ind
ind MAP_CLOSE_ind
MAP_ MAP_
To HLR, Including
OPEN_req CLOSE_
MAP_
ACTIVATE_
req
MAP_
DELIMITER_
req
Receive_
Open_ Section 25.1
Confirm
OK Vr,Error
Wait_for_
ss_cnf MAP_U_
ABORT_
req
Figure 22.4/1 (sheet 1 of 2): Procedure Activate_SS_GLR
3GPP
Release 1999 108 3GPP TS 29.120 V3.0.0 (2000-03)
Process SS_ACTIVATE_GLR 22.4.1_2(2)

Figure 22.4/1: Activation of supplementary service Signals to/from the left
procedure in the GLR are to/from the VLR via
the MAP provider;
Wait_for_
ss_cnf
MAP_
REGISTER_ MAP_U_ABORT_ind MAP_
SS_cnf MAP_P_ABORT_ind NOTICE_
ind
MAP_P_ yes MAP_

ERROR CLOSE_
req
no
MAP_U_
1 ABORT_
req
MAP_
REGISTER_
SS_rsp
MAP_
CLOSE_
req
MAP_ GET_
MAP_P_ABORT_ind PASSWARD_ Section 22.10
ind GLR
MAP_CLOSE_ind
MAP_
CLOSE_
req
OK NULL
MAP_U_
ABORT_ Wait_for_
req ss_cnf
Figure 22.4/1 (sheet 2 of 2): Procedure SS_Activate_GLR
22.5 Deactivation procedure

22.5.1 General
The deactivation procedure is used to deactivate a supplementary service in the HLR. The deactivation procedure is a
3GPP
Release 1999 109 3GPP TS 29.120 V3.0.0 (2000-03)

The GLR procedures for deactivation are identical to those specified for activation in subclause 22.4. The text and
diagrams in subclause 22.4 apply with all references to activation changed to deactivation.
22.6 Interrogation procedure

22.6.1 General
The interrogation procedure is used to retrieve information related to a supplementary service from the VLR or the
HLR. The interrogation procedure in the GLR is a fully transparent communication between the VLR and the HLR.

The GLR procedures for interrogation are identical to those specified for registration in subclause 22.2. The text and
diagrams in subclause 22.2 apply with all references to registration changed to interrogation.
22.7 Password registration procedure

22.7.1 General
The password registration procedure is used to register a password in the HLR. The password registration procedure is a

The password registration procedure in the GLR is identical to that for activation specified in subclause 22.4. All the
text and diagrams in subclause 22.4 apply with all references to activation changed to password registration.
22.8 Mobile Initiated USSD procedure

The initiation of the process is shown in subclause 22.1.
In the case that a GLR is located between the VLR and the HLR, the Mobile Initiated USSD procedure in the GLR is a
fully transparent communication between the VLR and the HLR.
When receiving the MAP_PROCESS_UNSTRUCTURED_SS_REQUEST indication from VLR, the MAP user in the
GLR transfers the information to the HLR in the MAP_PROCESS_UNSTRUCTURED_SS_REQUEST request without
checking the contents of the service indication.
The GLR may subsequently receive one or more MAP_UNSTRUCTURED_SS_REQUEST or

MAP_UNSTRUCTURED_SS_NOTIFY indications from the HLR. These shall be sent transparently to the VLR.
When a confirmation is received from the VLR this shall be returned to the HLR.
When the GLR receives a MAP_PROCESS_UNSTRUCTURED_SS_REQUEST confirmation from the HLR then it
shall pass this to the VLR and closes the MAP provider service.
Error Handling
Both the VLR and the HLR may initiate release of the MAP service at any time. This is handled as shown in the
diagrams.
The procedure in the HLR is shown in figure 22.8/1.
3GPP
Release 1999 110 3GPP TS 29.120 V3.0.0 (2000-03)
Process MS_INIT_USSD_GLR 22.8.1_1(2)

Figure 22.8/1: Handling of mobile initiated USSD at Signals to/from the left
GLR. are to/from the VLR
are to/from the HLR
NULL
Receive_
OK
Vr, Error
Wait_for_
service_ind NULL
MAP_PROCESS_
UNST'D_SS_ MAP_ MAP_U_ABORT_ind
REQUEST_ind NOTICE_ MAP_P_ABORT_ind
ind MAP_CLOSE_ind
MAP_
OPEN_ Including MAP_
req -Destination reference = subscriber's IMSI CLOSE_
-Originating reference = GLR number ind
MAP_PROCESS_
UNST'D_SS_
REQUEST_req
MAP_
DELIMITER_
req
Receive_
Open_ cnf Section25.1
OK Vr Error
Wait_for_
pussd_cnf MAP_U_ Set UE=
ABORT_ System Failure
req
MAP_PROCESS_
UNST'D_SS_
REQUEST_rsp
NULL
Figure 22.8/1 (sheet 1 of 2): Procedure MI_USSD_GLR
3GPP
Release 1999 111 3GPP TS 29.120 V3.0.0 (2000-03)
Process MS_INIT_USSD_GLR 22.8.1_2(2)

Figure 22.8/1: Handling of mobile initiated USSD at Signals to/from the left
are to/from the HLR
Wait_for_
pussd_cnf
MAP_PROCESS_ MS_Receive_
UNST'D_SS_ MAP_UNST'D_ MAP_UNST'D_ SS_REQUEST_ Error_at_
SS_NOTIFY_ ind GLR
REQUEST_cnf
ind
MAP_P_
no MAP_UNST'D_ MAP_UNST'D_
ERROR
SS_NOTIFY_ SS_REQUEST_ NULL
yes req req
MAP_U_
MAP_PROCESS_MAP_ MAP_
ABORT_ UNST'D_SS_ DELIMITER_ DELIMITER_
req REQUEST_rsp req req
MAP_U_ MAP_ Wait_for_ Wait_for_

ABORT_ CLOSE_ ussdn_cnf ussdn_cnf
req req
MAP_UNST'D _MS_Receive_ MAP_UNST'D_ MS_Receive_

NULL SS_NOTIFY_ Error_at_ SS_REQUEST_ Error_at_
cnf GLR cnf GLR
MAP_UNST'D_
MAP_UNST'D_
SS_NOTIFY_ NUL NULL
SS_REQUEST_
rsp L rsp
MAP_
MAP_
DELIMITER_
DELIMITER_
req
req
Wait_for_
Wait_for_
pussd_cnf
pussd_cnf
Figure 22.8/1 (sheet 2 of 2): Procedure MI_USSD_GLR
3GPP
Release 1999 112 3GPP TS 29.120 V3.0.0 (2000-03)
Macrodefinition MS_Receive_Error_at_GLR 22.8.2(1)

Figure 22.8/2: Handling of error at GLR for MS initiated USSD Signals to/from the left
are to/from the VLR
are to/from the HLR
Wait_for_
cnf
MAP_
CLOSE_ MAP_U_ABORT_ind MAP_
ind MAP_P_ABORT_ind NOTICE_
ind
MAP_
CLOSE_ MAP_
req CLOSE_
req
MAP_U_
ABORT_
req
MAP_
ind MAP_P_ABORT_ind
MAP_CLOSE_ind
From VLR
MAP_
CLOSE_
req
MAP_U_
ABORT_
req
Figure 22.8/2: Macro MS_Receive_ERROR_at_GLR
22.9 Network initiated USSD procedure

22.9.1 Procedure in the GLR
In the case that a GLR is located between the VLR and the HLR, the Network initiated USSD procedure in the GLR is a
fully transparent communication between the VLR and the HLR.
3GPP
Release 1999 113 3GPP TS 29.120 V3.0.0 (2000-03)
The procedure may be invoked by the HLR. It may start by using either the
MAP_UNSTRUCTURED_SS_REQUEST or MAP_UNSTRUCTURED_SS_NOTIFY service.
The GLR may subsequently receive one or more MAP_UNSTRUCTURED_SS_REQUEST_ind or

MAP_UNSTRUCTURED_SS_NOTIFY_ind indications from the VLR. These shall be sent transparently to the HLR.
When a confirmation is received from the HLR this shall be returned to the VLR.
When the GLR receives a MAP_CLOSE_ind from the HLR then it shall pass this to the VLR and close the MAP
dialogue.
Error Handling
Both the VLR and the HLR may initiate release of the MAP service at any time. This is handled as shown in the
diagrams.
The Network initiated USSD procedure in the GLR is shown in figure 22.9/1.
3GPP
Release 1999 114 3GPP TS 29.120 V3.0.0 (2000-03)
Process NW_INIT_USSD_GLR 22.9.1_1(2)

Figure 22.9/1: Handling of network initiated USSD at Signals to/from the left
are to/from the HLR
NULL
Receive_
OK
Vr, Error
Wait_for_
service_ind NULL
MAP_UNST'D_
SS_NOTIFY_ MAP_UNST'D_ MAP_ MAP_U_ABORT_ind
ind SS_REQUEST_ NOTICE_ MAP_P_ABORT_ind
ind ind MAP_CLOSE_ind
MAP_
OPEN_ MAP_ MAP_
req OPEN_ CLOSE_
req req
MAP_UNST'D_
SS_NOTIFY_ MAP_UNST'D_
req SS_REQUEST_
req
MAP_
DELIMITER_
req
Receive_
Open_ cnf Section25.1
OK Vr, Error
Wait_for_
ussdn_cnf MAP_U_
ABORT_
req
NULL
Figure 22.9/1 (sheet 1 of 2): Procedure NI_USSD_GLR
3GPP
Release 1999 115 3GPP TS 29.120 V3.0.0 (2000-03)
Process NW_INIT_USSD_GLR 22.9.1_2(2)

Figure 22.9/1: Handling of network initiated USSD at Signals to/from the left are
GLR. to/from the VLR signals
otherwise stated
Wait_for_
pussd_cnf
MAP_UNST'D_ MAP_UNST'D_ NW_Receive_

SS_NOTIFY_ SS_REQUEST_ Error_at_
ind ind GLR
NULL
MAP_UNST'D_ MAP_UNST'D_
SS_NOTIFY_ SS_REQUEST_
req req
MAP_ MAP_
DELIMITER_ DELIMITER_
req req
Wait_for_ Wait_for_
ussdn_cnf ussdn_cnf NW_Receive_
Error_at_
GLR
MAP_UNST'D_ NW_Receive_ MAP_UNST'D_
SS_NOTIFY_ Error_at_ SS_REQUEST_
cnf GLR cnf
3GPP
Release 1999 116 3GPP TS 29.120 V3.0.0 (2000-03)
MAP_UNST'D_
SS_NOTIFY_ MAP_UNST'D_
NUL SS_REQUEST_ NULL
rsp L rsp
MAP_
DELIMITER_ MAP_
req DELIMITER_
req
Wait_for_
pussd_cnf Wait_for_
pussd_cnf
Figure 22.9/1 (sheet 2 of 2): Procedure NI_USSD_GLR
3GPP
Release 1999 117 3GPP TS 29.120 V3.0.0 (2000-03)
Macrodefinition NW_Receive_Error_at_GLR 22.9.2(1)

Figure 22.9/2: Handling of error at GLR for NW initiated USSD Signals to/from the left
are to/from the VLR
are to/from the HLR
Wait_for_
cnf
MAP_
CLOSE_ MAP_U_ABORT_ind MAP_
ind MAP_P_ABORT_ind NOTICE_
ind
MAP_
CLOSE_ MAP_
req CLOSE_
req
MAP_U_
ABORT_
req
MAP_
ind MAP_P_ABORT_ind
MAP_CLOSE_ind
From VLR
MAP_
CLOSE_
req
MAP_U_
ABORT_
req
Figure 22.9/2: Marco NW_Receive_Rrror_at_GLR
22.10 Common macros for clause 22

22.10.1 SS Password handling macros
Macro Get_Password_GLR
3GPP
Release 1999 118 3GPP TS 29.120 V3.0.0 (2000-03)
This macro is used by the GLR to relay a request for password from the HLR to the VLR, and to relay a response
from the VLR back to the HLR. The macro is described in figure 22.10/1.
Macrodefinition GET_PASSWORD_GLR 22.10.1(1)

Figure 22.10/1: Macro which relay a GET Password request from the HLR to the VLR and Signals to/from the left
relay a GET Password response from the VLR to the HLR are to/from the VLR
are to/from the HLR
MAP_GET_
PASSWORD_
ind
MAP_GET_
PASSWORD_
req
MAP_
DELIMITER_
req
Wait_for_
password
MAP_GET_
PASSWORD_ MAP_U_ABORT_ind MAP_
cnf MAP_P_ABORT_ind NOTICE_
ind
MAP_GET_
PASSWORD_ MAP_
rsp CLOSE_
req
MAP_
DELIMITER_ MAP_U_
req ABORT_
req
OK NULL
MAP_
ind MAP_P_ABORT_ind
MAP_CLOSE_ind
MAP_
CLOSE_
req
MAP_U_
ABORT_
req
NULL
Figure 22.10/1: Macro Get_PW_GLR
3GPP
Release 1999 119 3GPP TS 29.120 V3.0.0 (2000-03)
22.11 Activation of a CCBS request

22.11.1 General
The Activation of a CCBS request procedure in the GLR is a fully transparent communication between the VLR and the
HLR.

When receiving the MAP_REGISTER_CC_ENTRY indication from VLR, the MAP user in the GLR transfers the
information to the HLR in the MAP_REGISTER_CC_ENTRY request without checking the contents of the service
indication.
When the GLR receives a MAP_REGISTER_CC_ENTRY confirmation from the HLR then it shall pass this to the VLR
and closes the MAP provider service.
The activation of a CCBS request procedure in the GLR is shown in figure 22.11/1.
3GPP
Release 1999 120 3GPP TS 29.120 V3.0.0 (2000-03)
Process Register_CC_Entry_GLR 22.11.1_1(2)

Figure 22.11/1: Handling of Register_CC_Entry at GLR Signals to/from the left
are to/from the VLR
are to/from the HLR
NULL
MAP_
REGISTER_CC_ MAP_ MAP_U_ABORT_ind
ENTRY_ind NOTICE_ MAP_P_ABORT_ind
ind MAP_CLOSE_ind
MAP_
To HLR, Including MAP_
OPEN_req
- Destination reference = subscriber's IMSI CLOSE_
MAP_
REGISNTER_CC_
ENTRY_req
MAP_
DELIMITER_
req
Receive_
Open_ Section 25.1
Confirm
1
OK Vr, Error
Wait_for_
cnf MAP_U_
ABORT_
req
Figure 22.11/1 (sheet 1 of 2): Process Register_CC_Entry_GLR
3GPP
Release 1999 121 3GPP TS 29.120 V3.0.0 (2000-03)
Process Register_CC_Entry_GLR 22.11.1_2(2)

Figure 22.11/1: Handling of Register_CC_Entry at GLR Signals to/from the left
are to/from the VLR
are to/from the HLR
Wait_for_
cnf
MAP_REGISTER_
CC_ENTRY_ MAP_U_ABORT_ind MAP_
ind
MAP_P_
ERROR yes MAP_
CLOSE_
no req
MAP_U_
1 ABORT_
req
MAP_
REGISTER_CC_
ENTRY_rsp
MAP_
CLOSE_
req
MAP_
ind MAP_P_ABORT_ind
MAP_CLOSE_ind
MAP_
CLOSE_
req
MAP_U_
ABORT_
req
Figure 22.11/1 (sheet 2 of 2): Process Register_CC_Entry_GLR
22.12 Deactivation of a CCBS request

22.12.1 General
The Deactivation of a CCBS request procedure in the GLR is a fully transparent communication between the VLR
and the HLR.
3GPP
Release 1999 122 3GPP TS 29.120 V3.0.0 (2000-03)

When receiving the MAP_ ERASE _CC_ENTRY indication from VLR, the MAP user in the GLR transfers the
information to the HLR in the MAP_ ERASE _CC_ENTRY request without checking the contents of the service
indication.
When the GLR receives a MAP_ ERASE _CC_ENTRY confirmation from the HLR then it shall pass this to the VLR
and closes the MAP provider service.
The deactivation of a CCBS request procedure in the GLR is shown in figure 22.12/1.
3GPP
Release 1999 123 3GPP TS 29.120 V3.0.0 (2000-03)
Process Erase_CC_Entry_GLR 22.12.1_1(2)

Figure 22.12/1: Handling of Erase_CC_Entry at GLR Signals to/from the left
are to/from the VLR
are to/from the HLR
NULL
MAP_
ERASE_CC_ MAP_ MAP_U_ABORT_ind
ENTRY_ind NOTICE_ MAP_P_ABORT_ind
ind MAP_CLOSE_ind
MAP_ MAP_
Including
OPEN_req CLOSE_
MAP_
ERASE_CC_
ENTRY_req
MAP_
DELIMITER_
req
Receive_
Open_ Section 25.1
Confirm
1
OK Vr, Error
Wait_for_
cnf MAP_U_
ABORT_
req
Figure 22.12/1 (sheet 1 of 2): Process Erase_CC_Entry_GLR
3GPP
Release 1999 124 3GPP TS 29.120 V3.0.0 (2000-03)
Process Erase_CC_Entry_GLR 22.12.1_2(2)

Figure 22.12/1: Handling of Erase_CC_Entry at GLR Signals to/from the left are
to/from the VLR signals
otherwise stated
Wait_for_
cnf
MAP_REGISTER_
CC_ENTRY_ MAP_U_ABORT_ind MAP_
ind
MAP_P_
ERROR yes MAP_
CLOSE_
no req
MAP_U_
1 ABORT_
req
MAP_
REGISTER_CC_
ENTRY_rsp
MAP_
CLOSE_
req
MAP_
ind MAP_P_ABORT_ind
MAP_CLOSE_ind
MAP_
CLOSE_
req
MAP_U_
ABORT_
req
Figure 22.12/1 (sheet 2 of 2): Process Erase_CC_Entry_GLR
3GPP
Release 1999 125 3GPP TS 29.120 V3.0.0 (2000-03)
23 Short message service procedures
23.1 General
The short message service procedures are used to control both mobile originated and mobile terminated short message
transfer.
Four procedures exist for short message services (see 29.002) but only the following two procedures are involved in the
GLR and the IM-MSC:
- mobile terminated short message service transfer;
- short message alert procedure.
23.2 The mobile terminated short message transfer procedure

The mobile terminated short message transfer procedure is used for forwarding a short message or several short
messages from a Service Centre to a mobile subscriber. This subclause includes the description of the procedures in
the IM-MSC and the GLR. The procedures in the other existing entities are entirely the same as in the network without
the GLR and are described in 29.002.
23.2.1 Procedure in the Intermediate MSC

When initiating the dialogue with the IM-MSC, the SMS Gateway MSC must provide the IMSI of the subscriber to
whom the short message is directed.
The IMSI can be included either in the Destination Reference of the MAP_OPEN indication received from the SMS
Gateway MSC or in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE indication.
When receiving a MAP_OPEN indication primitive that is not associated with any MAP service indication primitive
and if the dialogue is accepted, the MAP service-user in the IM-MSC issues a MAP_DELIMITER request primitive in
order to trigger the local MAP service-provider to confirm the dialogue.
When receiving the first MAP_MT_FORWARD_SHORT_MESSAGE indication from the gateway MSC, the IM- MSC
retrieves the E.164 Number of the servicing MSC from the GLR if the MAP service primitive is accepted.
The MAP_MT_FORWARD_SHORT_MESSAGE indication primitive is checked by the macro "Check_Indication". If

the received MAP service primitive contains errors, the service is aborted and an unexpected data value error or data
missing error is returned to the GMSC.
The subscriber identity information that may be included in the MAP_OPEN indication primitive and in the MAP
service indication primitive is checked by the macro "Check_Subscr_Identity_For_MT_SMS" as follows.
If a Destination Reference has been received in the MAP_OPEN indication, an LMSI must be present in the sm-RP-DA
information field of the MAP_MT_FORWARD_SHORT_MESSAGE indication. The LMSI shall be key information
for retrieving the MSC Number in the GLR.
Otherwise, if the IMSI is included in the sm-RP-DA information field of the

MAP_MT_FORWARD_SHORT_MESSAGE indication, it is used to retrieve the MSC Number in the GLR.
If:
a Destination Reference has been received in the IM-MSC and the sm-RP-DA information field of the
MAP_MT_FORWARD_SHORT_MESSAGE indication does not include an LMSI, or
no Destination Reference has been received and the sm-RP-DA information field does not cover an IMSI;
the service is aborted in the IM-MSC and the error "Unexpected Data Value" is returned to the SMS GMSC.
3GPP
Release 1999 126 3GPP TS 29.120 V3.0.0 (2000-03)
The interaction between the IM-MSC and the GLR for the MSC Number retrieval is described in 3GPP TS
23.119 GLR-stage2.
If the IM-MSC is successfully retrieves the MSC Number it initiates the forward short message procedure to the
servicing MSC. The presence of the Destination Reference in the MAP_OPEN request and the LMSI or IMSI in the
first MAP_MT_FORWARD_SHORT_MESSAGE request follows the message received from the GMSC. The More
Messages To Send flag is set to TRUE or FALSE depending on the information received from the GMSC.
If the grouping of MAP_OPEN request and MAP_MT_FORWARD_SHORT_MESSAGE request together would need
segmenting, these primitives must not be grouped together. The MAP_OPEN request primitive is sent first without any
associated MAP service request primitive and the dialogue confirmation must be received before the
MAP_MT_FORWARD_SHORT_MESSAGE request is sent.
As a response to the procedure, the IM-MSC will receive the MAP_MT_FORWARD_SHORT_MESSAGE

confirmation indicating:
- a successful forwarding of the short message. This indication is passed to the GMSC;
- unsuccessful forwarding of the short message. This indication is passed to the GMSC.
The IM-MSC informs the delivery failure to the GLR, if an absent subscriber_SM, an unidentified subscriber or SM
delivery failure with error cause MS memory capacity exceeded indication is received from the servicing MSC. That
enables the GLR set the MNRF. The interaction between the IM-MSC and the GLR regarding the procedure is
described in 3GPP TS 23.119 GLR-stage2.
Unexpected data value, system failure errors and other errors are simply passed to the GMSC.
If the More Messages To Send flag was TRUE in the MAP_MT_FORWARD_SHORT_MESSAGE request and the
previous short message transfer succeeded, then the IM-MSC awaits the next short message.
When receiving the next short message from the GMSC, the IM-MSC sets the More Messages To Send flag according
to the information received and starts the service MAP_MT_FORWARD_SHORT_MESSAGE again.
If the More Messages To Send flag was FALSE or the service MAP_MT_FORWARD_SHORT_MESSAGE ends
unsuccessfully, the transaction to the gateway MSC is terminated.
The mobile terminated short message transfer procedure in the IM-MSC is shown in figure 23.2/1 and 23.2/2.
3GPP
Release 1999 127 3GPP TS 29.120 V3.0.0 (2000-03)
Process MT_SM_Transfer_IMMSC 23.2.1_1(3)

Figure 23.2/1: The mobile terminated short messa Signals to/from the left
service in the IM-MSC are to/from the SMS-GMSC; signals
to/from the right
are to/from the MSC
NULL
Receive_ Section 25.1

Open_
ind Error
OK
Dest_Ref_
received no NULL
yes
'Store_
Destination_
Reference'
WAIT_FOR_
SERVICE_
PRIMITIVE_
MAP_
DELIMITER_ MAP_MT_ MAP_U_ABORT_ind MAP_NOTICE
ind FROWARD_ MAP_P_ABORT_ind _ind
SHORT_ MAP_CLOSE_ind
MESSAGE_ind
MAP_
DELIMITER_ Check_ MAP_
Indication Section 25.2 CLOSE_
req
ind
WAIT_FOR_ ok error
SERVICE_ MT_SM_
IM-MSC Figure 23.2/2
PRIMITIVE_
error
ok More_msg_
to_sent
NULL
yes no
MAP_MT_FORWARD_SHORT
_MESSAGE_rsp MAP_MT_FORWARD_SHORT
MAP_DELIMITER_req _MESSAGE_rsp
MAP_CLOSE_req
WAIT_FOR_
MORE_ NULL
MESSAGES
Figure 23.2/1 (sheet1 of 3): Procedure_MT_SM_Transfer_IM-MSC
3GPP
Release 1999 128 3GPP TS 29.120 V3.0.0 (2000-03)

Figure 23.2/1: The mobile terminated short message
service in the IM-MSC
WAIT_FOR_
MORE_
MESSAGES
MAP_MT_FORWARD_
SHORT_MESSAGE_ind
Check_
Indication Section 25.2
ok
error MAP_MT_FORWARD_SHORT
_MESSAGE_req MAP_DELIMITER_req
WAIT_FOR_
MT_SMS_
CONFIRM
_MESSAGE_cnf
Check_
Confirmation Section 25.2
Provider error
Data error ok
User error
Absent More_msg
no Subscriber? to_sent yes
yes no
Inform SM to GLR Application
Delivery Process in TS23.119
Failure
_MESSAGE_rsp
_MESSAGE_rsp MAP_DELIMITER_req
MAP_CLOSE_req
WAIT_FOR_
NULL MORE_
MESSAGES
Figure 23.2/1 (sheet 2 of 3): Procedure MT_SM_Transfer_IM-MSC
3GPP
Release 1999 129 3GPP TS 29.120 V3.0.0 (2000-03)

service in the IM-MSC
WAIT_FOR_MORE_MESSAGES
WAIT_FOR_MT_SMS_COMFIRM
MAP_U_ABORT_ind
MAP_P_ABORT_ind MAP_NOTICE
_ind from SMS-GMSC
from SMS-GMSC
MAP_CLOSE
_req to SMS-GMSC
MAP_U_
ABORT_ to VMSC
req
MAP_NOTICE
from VMSC MAP_U_ABORT_ind
_ind MAP_P_ABORT_ind
fMAP_CLOSE_ind
from VMSC
MAP_
CLOSE_ to VMSC
req
MAP_U_
ABORT_ to SMS-GMSC
req
Figure 23.2/1 (sheet 3 of 3): Procedure MT_SM_Transfer_IM-MSC
3GPP
Release 1999 130 3GPP TS 29.120 V3.0.0 (2000-03)
Macrodefinition MT_SM_IMMSC 23.2.2_1(2)

Figure 23.2/2: Macro which transfer short message PDUs to VMSC in the Signals to/from the right
IM-MSC are to/from the MSC
Obtain MSC
Number to GLR Application Process
in TS23.119
WAIT_FOR_
RESPONSE
from GLR Application Process in

RESPONSE TS23.119
MSC Number
Obtained ?
yes no
Message
segmenting User Error =
no needed ? Unidentified User
yes
MAP_OPEN_req MAP_OPEN_req ERR
MAP_MT_FORWARD_ MAP_DELIMITER OR
SHORT_MESSAGE_req _req
MAP_DELIMITER_req
Receive_ Receive_
Open_ Open_
Cnf error error Cnf
ok ok
WAIT_FOR_ Error = MAP_MT_FORWARD_ SHORT_MESSAGE_req
MT_SMS_ System Failure MAP_DELIMITER_req
CONFIRM
ERR
OR WAIT_FOR_
MT_SMS_
CONFIRM
MAP_MT_FORWARD_SHORT_MESSAGE_Cnf
1
page2
Figure 23.2/2 (sheet1 of 2): Macro MT_SM_IM-MSC
3GPP
Release 1999 131 3GPP TS 29.120 V3.0.0 (2000-03)
Macrodefinition MT_SM_IMMSC 23.2.2_2(2)

Figure 23.2/2: Macro which transfer short message PDUs to VMSC in the
IM-MSC
1
page1
Check_
Provider Error
Data Error User Error ok
Absent
Subscriber? OK
no
yes
Inform SM
Delivery Failure to GLR Application Process
in TS 23.119
ERR
OR
Figure 23.2/2 (sheet2 of 2): Macro MT_SM_IM-MSC

When initiating the dialogue with the GLR, the SMS Gateway MSC must provide the IMSI of the subscriber to whom
the short message is directed.
The IMSI is included in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE

indication.
3GPP
Release 1999 132 3GPP TS 29.120 V3.0.0 (2000-03)
When receiving a MAP_OPEN indication primitive that is not associated with any MAP service indication primitive
and if the dialogue is accepted, the MAP service-user in the GLR issues a MAP_DELIMITER request primitive in
order to trigger the local MAP service-provider to confirm the dialogue.
When receiving the first MAP_MT_FORWARD_SHORT_MESSAGE indication from the gateway MSC, the GLR
performs some subscriber data checks, if the MAP service primitive is accepted.
The MAP_MT_FORWARD_SHORT_MESSAGE indication primitive is checked by the macro "Check_Indication". If

the received MAP service primitive contains errors, the service is aborted and an unexpected data value error or data
missing error is returned to the GMSC.
The subscriber identity information that is included in the MAP service indication primitive is checked by the macro
"Check_Subscr_Identity_For_MT_SMS" as follows:
If the IMSI is included in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE

indication, the MAP_OPEN indication received from the gateway MSC shall not include a Destination Reference.
If no Destination Reference has been received and the sm-RP-DA information field does not cover an IMSI the
service is aborted in the GLR and the error "Unexpected Data Value" is returned to the GMSC.
The following outcomes from the subscriber data checks can occur in GLR:
- if the mobile subscriber is unknown, the unidentified subscriber error is forwarded to the GMSC;
- if the “Confirmed by HLR” indicator is set to “Not Confirmed”, the unidentified subscriber error is forwarded
to the GMSC.
If the mobile subscriber is known and “Confirmed by HLR” indicator is set to “Confirmed”, the GLR shall successfully
retrieves the SGSN Number.
If the GLR is successfully retrieves the SGSN Number it initiates the forward short message procedure to the SGSN.
The IMSI is included in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE
request. More Messages To Send flag is set to TRUE or FALSE depending on the information received from the
GMSC.
If the grouping of MAP_OPEN request and MAP_MT_FORWARD_SHORT_MESSAGE request together would need
segmenting, these primitives must not be grouped together. The MAP_OPEN request primitive is sent first without any
associated MAP service request primitive and the dialogue confirmation must be received before the
MAP_MT_FORWARD_SHORT_MESSAGE request is sent.
As a response to the procedure, the GLR will receive the MAP_MT_FORWARD_SHORT_MESSAGE confirmation
indicating:
- a successful forwarding of the short message. This indication is passed to the GMSC;
- unsuccessful forwarding of the short message. This indication is passed to the GMSC.
The GLR sets MNRG, if an absent subscriber_SM (except for the case that absent subscriber reason is PurgedMS), an
unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded indication is received
from the SGSN.
If the GLR receives an absent subscriber_SM and absent subscriber reason is PurgedMS, the GLR deletes the subscriber
data for the user.
Unexpected data value, system failure errors and other errors are simply passed to the GMSC.
If the More Messages To Send flag was TRUE in the MAP_MT_FORWARD_SHORT_MESSAGE request and the
previous short message transfer succeeded, then the GLR awaits the next short message.
When receiving the next short message from the GMSC, the GLR sets the More Messages To Send flag according to the
information received and starts the service MAP_MT_FORWARD_SHORT_MESSAGE again.
If the More Messages To Send flag was FALSE or the service MAP_MT_FORWARD_SHORT_MESSAGE ends
unsuccessfully, the transaction to the gateway MSC is terminated.
The mobile terminated short message transfer procedure in the GLR is shown in figure 23.2/3 and 23.2/4.
3GPP
Release 1999 133 3GPP TS 29.120 V3.0.0 (2000-03)
Process MT_SM_Transfer_GLR 23.2.3_1(3)

Figure 23.2/3: The mobile terminated short message Signals to/from the left
service in the GLR are to/from the SMS-GMSC; signals
to/from the right
are to/from the SGSN
NULL

Open_
ind Error
OK
Dest_Ref_
received no NULL
yes
'Store_
Destination_
Reference'
WAIT_FOR_
SERVICE_
PRIMITIVE_
MAP_
DELIMITER_ MAP_MT_ MAP_U_ABORT_ind MAP_NOTICE
ind FROWARD_ MAP_P_ABORT_ind _ind
SHORT_ MAP_CLOSE_ind
MESSAGE_ind
MAP_
DELIMITER_ Check_ MAP_
Indication Section 25.2 CLOSE_
req
ind
WAIT_FOR_ ok error
SERVICE_ MT_SM_
GLR Figure 23.2/4
PRIMITIVE_
error
ok More_msg_
to_sent
NULL
yes no
_MESSAGE_rsp MAP_MT_FORWARD_SHORT
MAP_DELIMITER_req _MESSAGE_rsp
MAP_CLOSE_req
WAIT_FOR_
MORE_ NULL
MESSAGES
Figure 23.2/3 (sheet 1 of 3): Procedure MT_SM_Transfer_GLR
3GPP
Release 1999 134 3GPP TS 29.120 V3.0.0 (2000-03)

service in the GLR
WAIT_FOR_
MORE_
MESSAGES
MAP_MT_FORWARD_
SHORT_MESSAGE_ind
Check_
Section 25.2
Indication
ok
error MAP_MT_FORWARD_SHORT
_MESSAGE_req MAP_DELIMITER_req
WAIT_FOR_
MT_SMS_
CONFIRM
_MESSAGE_cnf
Check_
Section 25.2
Confirmation
Provider error ok
Data error User error
Absent More_msg
no Subscriber? to_sent yes
yes no
set MNRG
Check_Absent_
SubscriberSM See TS 23.119
_In_GLR
_MESSAGE_rsp
MAP_CLOSE_req
NULL MAP_MT_FORWARD_SHORT WAIT_FOR_

_MESSAGE_rsp MORE_ MESSAGES
MAP_DELIMITER_req
3GPP
Release 1999 135 3GPP TS 29.120 V3.0.0 (2000-03)

service in the GLR
WAIT_FOR_MORE_MESSAGES
WAIT_FOR_MT_SMS_COMFIRM
MAP_U_ABORT_ind
MAP_P_ABORT_ind MAP_NOTICE
_ind from SMS-GMSC
from SMS-GMSC
MAP_CLOSE
_req to SMS-GMSC
MAP_U_
ABORT_ to SGSN
req
MAP_NOTICE
from SGSN MAP_U_ABORT_ind
_ind MAP_P_ABORT_ind
fMAP_CLOSE_ind
from SGSN
MAP_
CLOSE_ to SGSN
req
MAP_U_
ABORT_ to SMS-GMSC
req
3GPP
Release 1999 136 3GPP TS 29.120 V3.0.0 (2000-03)
Macrodefinition MT_SM_GLR 23.2.4_1(2)

Figure 23.2/4: Macro which transfer short message PDUs to SGSN in the Signals to/from the right
GLR are to/from the SGSN
Subscriber
known ?
yes no
Confirmed by
HLR ?
yes no
Retrieve and set

SGSN Number User Error =
Unidentified User
Message
segmenting
no needed ?
yes
MAP_OPEN_req MAP_OPEN_req ERR
MAP_MT_FORWARD_ MAP_DELIMITER OR
SHORT_MESSAGE_req _req
MAP_DELIMITER_req
Receive_ Receive_
Open_ Open_
Cnf error error Cnf
ok ok
WAIT_FOR_ Error = MAP_MT_FORWARD_
MT_SMS_ System Failure SHORT_MESSAGE_req
CONFIRM MAP_DELIMITER_req
ERR WAIT_FOR_
OR MT_SMS_
CONFIRM
MAP_MT_FORWARD_SHORT_MESSAGE_Cnf
1
page2
Figure 23.2/4 (sheet1 of 2): Macro MT_SM_GLR
3GPP
Release 1999 137 3GPP TS 29.120 V3.0.0 (2000-03)
Macrodefinition MT_SM_GLR 23.2.4_2(2)

Figure 23.2/4: Macro which transfer short message PDUs to SGSN in the
GLR
1
page1
Check_
Section 25.2
Confirmati on
Provider Error
Data Error
User Error ok
Absent
OK
Subscriber?
no
yes
set MNRG
Check_Absent_
SubscriberSM_In_ See TS 23.119
GLR
ERR
OR
Figure 23.2/4 (sheet2 of 2): Macro MT_SM_GLR
23.3 The Short Message Alert procedure

The Short Message Alert procedure is used for alerting the Service Centre when the mobile subscriber is active after a
short message transfer has failed because the mobile subscriber is not reachable or when the MS has indicated that it has
memory capacity to accept a short message.
3GPP
Release 1999 138 3GPP TS 29.120 V3.0.0 (2000-03)

When the GLR receives MAP_READY_FOR_SM indication from the VLR or the SGSN and it has MNRF or
MNRG, it sends MAP_READY_FOR_SM request to the HLR.
If the outcome is successful, the MNRF or MNRG is cleared.
The short message alert procedure in the GLR is shown in figure 23.3/1.
Process SM_Alert_GLR 23.3.1_1(2)

Figure 23.3/1: The short message alert process in the Signals to/from the left
GLR are to/from the VLR/SGSN; signals
to/from the right
are to/from the HLR
NULL
Receive_
Open_ Section 25.1
ind Error
ok
WAIT_FOR_
SERVICE_ NULL
PRIMITIVE_
MAP_READY_ MAP_U_ABORT_ind MAP_NOTICE

FOR_SM_ind MAP_P_ABORT_ind _ind
MAP_CLOSE_ind
Check_
Indication MAP_
Section 25.2 CLOSE_
req
ok
error
Subscriber
known ? NULL
no
yes
SET UE =
UNKNOWN
SUBSCRIBWR
MAP_OPEN_req
MAP_READY_FOR_SM_req MAP_READY_FOR_SM_rsp
MAP_DELIMITER_req MAP_CLOSE_req
Receive_
Open_ Section 25.1
Cnf
error
ok
SET UE =
system failure NULL
1
page2
Figure 23.3/1 (sheet 1 of 2): Process SM_Alert_GLR
3GPP
Release 1999 139 3GPP TS 29.120 V3.0.0 (2000-03)
Process SM_Alert_GLR 23.3.1_2(2)

Figure 23.3/1: The short message alert process in the
GLR
1
page1
WF_RESULT
MAP_READY_
FOR_SM_Cnf
Check_
error
ok
MNRF or
MNRG set ? SET
USER ERROR
yes
no
REASON
non-GPRS GPRS
Clear
MNRF Clear
MNRG
MAP_READY_FOR_SM_rsp
MAP_CLOSE_req
NULL
Figure 23.3/1 (sheet 2 of 2): Process SM_Alert_GLR
3GPP
Release 1999 140 3GPP TS 29.120 V3.0.0 (2000-03)
24 GPRS process description
24.1 General
The MAP GPRS procedures are used for the Network Requested PDP-Context Activation procedures.
The stage 2 specification for Packet Switched Service involving GLR is in 3GPP TS 23.119.
24.2 Send Routing Information procedure

24.2.1 Process in the GLR for Send Routing Information for GPRS
The MAP process in the GLR to provide routing information for a network-requested PDP context activation is shown
in figure 24.2/1. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be
found as follows:
- Receive_Open_Ind see subclause 25.1;
- Check_Indication see subclause 25.2.
Successful outcome
When the MAP process receives a MAP_OPEN indication with the application context gprsLocationInfoRetrieval, it
checks it by invoking the macro Receive_Open_Ind.
If the macro takes the OK exit, the MAP process waits for a service indication.
If a MAP_SEND_ROUTING_INFO_FOR_GPRS service indication is received, the GLR sends a Send Routing Info
For Gprs request to the GPRS application process in the GLR, and wait for a response. The Send Routing Info For Gprs
request contains the parameter received in the MAP_SEND_ROUTING_INFO_FOR_GPRS service indication.
If the GPRS application process in the GLR returns a positive response containing the routing information, the MAP
process constructs a MAP_SEND_ROUTING_INFO_FOR_GPRS service response containing the routing info,
constructs a MAP_CLOSE service request, sends them to the IM-GSN and returns to the idle state.
Negative response from GLR GPRS application process
If the GPRS application process in the GLR returns a negative response, the MAP process constructs a
MAP_SEND_ROUTING_INFO_FOR_GPRS service response containing the appropriate error, constructs a
MAP_CLOSE service request, sends them to the IM-GSN and returns to the idle state.
Failure of dialogue opening with the IM-GSN
If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state.
If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP
process returns to the idle state.
If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP
process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
3GPP
Release 1999 141 3GPP TS 29.120 V3.0.0 (2000-03)
Process Send_Routing_Info_For_Gprs_GLR 24.2.1(1)

Figure 24.2/1: The Send Routing Info For Signals to/from the right
Gprs process in the GLR are to/from the GPRS
application process
Idle
Receive_
Vr, Error
OK
Wait_For_
Service_ Idle
Indication
MAP_P_
ABORT_ind MAP_SEND_ROUTING_INFO_ MAP_
FOR_GPRS_ind NOTICE_ind
Idle Send Routing MAP_

Info For Gprs CLOSE_req
Wait For
Routing Info Idle
Send Routing Info

For Gprs Send Routing
negative response Info For Gprs
ack
Set Routing
Set UE Info
MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp
MAP_CLOSE_req
Idle
Figure 24.2/1: Process Send Routing Info For Gprs_GLR
24.2.2 Process in the IM-GSN for Send Routing Information for GPRS
Successful Outcome
3GPP
Release 1999 142 3GPP TS 29.120 V3.0.0 (2000-03)
When the MAP process receives a Send Routing Info For Gprs request from the GPRS application process in the IM-
GSN, it:
- requests a dialogue with the GLR whose identity is contained in the Send Routing Info For Gprs request
by sending a MAP_OPEN service request;
- requests routeing information using a MAP_SEND_ROUTING_INFO_FOR_GPRS service request, and
- invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request.
If the dialogue opening is successful, the MAP process waits for a response from the GLR.
If the MAP process receives a MAP_SEND_ROUTING_INFO_FOR_GPRS service confirm from the GLR, the MAP
process invokes the macro Check_Confirmation to check the content of the confirmation.
If the macro Check_Confirmation takes the OK exit, the MAP process sends a Send Routing Info For Gprs ack
containing the routing information received from the GLR to the GPRS application process in the IM-GSN and
returns to the idle state.
Failure of dialogue opening with the GLR
If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the
GPRS application process in the IM-GSN and returns to the idle state.
Error in MAP_SEND_ROUTING_INFO_FOR_GPRS confirm
If the MAP_SEND_ROUTING_INFO_FOR_GPRS service confirm contains a user error or a provider error, or the
macro Check_Confirmation indicates that there is a data error, the MAP process sends a Send Routing Info For Gprs
negative response to the GPRS application process in the IM-GSN and returns to the idle state.
Abort of GLRdialogue
After the dialogue with the GLR has been established, the MAP service provider may abort the dialogue by issuing a
MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP process sends a Send Routing Info For Gprs
negative response to the GPRS application process in the IM-GSN and returns to the idle state.
If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the
dialogue with the GLR, sends a Send Routing Info For Gprs negative response indicating system failure to the GPRS
application process in the IM-GSN and returns to the idle state.
3GPP
Release 1999 143 3GPP TS 29.120 V3.0.0 (2000-03)
Process Send_Routing_Info_For_Gprs_IMGSN 24.2.2(1)

Figure 24.2/2: The Send Routing Info For Signals to/from the right
Gprs process in the IMGSN are to/from the GPRS
application process
Idle
Send Routing
Info For Gprs
MAP_OPEN_req MAP_SEND_ROUTING_INFO_FOR_GPRS_req
MAP_DELIMITER_req

Open_cnf Vr, Error
OK Send Routing
Wait_For_ Info For Gprs
Ack negative response Idle
MAP_SEND_ROUTING_ MAP_P_
INFO_FOR_GPRS_cnf MAP_
ABORT_ind NOTICE_i nd
MAP_U_
ABORT_ind
Section 25.2 Check_ MAP_
Confirmation CLOSE_re q
OK Provider
User Error,
Data Error
Send Routing
Info For Gprs Send Routing
ack Info For Gprs
negative response
Idle
Figure 24.2/2: Process Send_Routing_Info_For_Gprs_IM-GSN
3GPP
Release 1999 144 3GPP TS 29.120 V3.0.0 (2000-03)
24.3 Failure Report procedure

24.3.1 Process in the GLR for Failure Report
The MAP process in the GLR to set the MNRG (Mobile station Not Reachable for GPRS) flag for the subscriber is
shown in figure 24.3/1. The MAP process invokes a macro not defined in this subclause; the definition of this macro can
be found as follows:
- Receive_Open_Ind see subclause 25.1;
- Check Indication see subclause 25.2.
Successful outcome
When the MAP process receives a MAP_OPEN indication with the application context failureReport, it checks it by
invoking the macro Receive_Open_Ind.
If the macro takes the OK exit, the MAP process waits for a service indication.
If a MAP_FAILURE_REPORT service indication is received, the GLR sends a Failure Report request to the GPRS
application process in the GLR, and wait for a response. The Failure Report request contains the parameter received in
the MAP_FAILURE_REPORT service indication.
If a positive response is received, the MAP process constructs a MAP_FAILURE_REPORT service response,
constructs a MAP_CLOSE service request, sends them to the IM-GSN and returns to the idle state.
Negative response from GLR GPRS application process
If the GPRS application process in the GLR returns a negative response, the MAP process constructs a
MAP_FAILURE_REPORT service response containing the appropriate error, constructs a MAP_CLOSE service
request, sends them to the IM-GSN and returns to the idle state.
Failure of dialogue opening with the IM-GSN
If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state.
If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP
process returns to the idle state.
If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP
process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
3GPP
Release 1999 145 3GPP TS 29.120 V3.0.0 (2000-03)
Process Failure_Report_GLR 24.3.1(1)

Figure 24.3/1: The Failure Report process in the GLR Signals to/from the right
are to/from the
application process
Idle
Receive_
Vr, Error
OK
Wait_For_
Service_ Idle
Indication
MAP_P_
ABORT_ind MAP_
MAP_FAILURE_REPORT_ind NOTICE_ind
Idle MAP_
Failure Report CLOSE_req
Wait For
Response Idle
Failure Report
negative response Failure Report
ack
Set UE
MAP_FAILURE_REPORT_rsp
MAP_CLOSE_req
Idle
Figure 24.3/1: Process Failure_Report_GLR
24.3.2 Process in the IM-GSN for Failure Report

Successful Outcome
3GPP
Release 1999 146 3GPP TS 29.120 V3.0.0 (2000-03)
When the MAP process receives a Failure Report request from the GPRS application process in the IM-GSN, it
requests a dialogue with the GLR whose identity is contained in the Failure Report request by sending a MAP_OPEN
service request, sending failure information using a MAP_FAILURE_REPORT service request and invokes the macro
Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the
MAP process waits for a response from the GLR.
If the MAP process receives a MAP_FAILURE_REPORT service confirm from the GLR, the MAP process invokes the
macro Check_Confirmation to check the content of the confirmation.
If the macro Check_Confirmation takes the OK exit, the MAP process sends a Failure Report ack containing the
information received from the GLR to the GPRS application process in the IM-GSN and returns to the idle state.
Failure of dialogue opening with the GLR
If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the
GPRS application process in the IM-GSN and returns to the idle state.
Error in MAP_FAILURE_REPORT confirm
If the MAP_FAILURE_REPORT service confirm contains a user error or a provider error, or the macro
Check_Confirmation indicates that there is a data error, the MAP process sends a Failure Report negative response to
the GPRS application process in the IM-GSN and returns to the idle state.
Abort of GLR dialogue
After the dialogue with the GLR has been established, the MAP service provider may abort the dialogue by issuing a
MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP process sends a Failure Report negative
response to the GPRS application process in the IM-GSN and returns to the idle state.
If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the
dialogue with the GLR, sends a Failure Report negative response indicating system failure to the GPRS application
process in the IM-GSN and returns to the idle state.
3GPP
Release 1999 147 3GPP TS 29.120 V3.0.0 (2000-03)
Process Failure_Report_IMGSN 24.3.2(1)

Figure 24.3/2: The Failure Report process in the IMGSN Signals to/from the right
are to/from the GPRS
application process
Idle
Failure Report
MAP_OPEN_req
MAP_FAILURE_REPORT_req
MAP_DELIMITER_req
Receive_
Open_cnf Section 25.1
Vr, Error
OK
Wait_For_ Failure Report
Ack negative response
Idle
MAP_P_ MAP_
MAP_FAILURE_REPORT_cnf
ABORT_ind NOTICE_i nd
MAP_U_
ABORT_ind
Section 25.2 Check_ MAP_

Confirmation CLOSE_re q
OK Provider
User Error,
Data Error
Failure Report
ack Failure Report
negative response
Idle
Figure 24.3/2: Process Failure_Report_IM-GSN
3GPP
Release 1999 148 3GPP TS 29.120 V3.0.0 (2000-03)
25 General macro description
25.1 MAP open macros

This subclause refers 3GPP TS 29.002.
25.2 Macros to check the content of indication and confirmation

primitives
This subclause refers 3GPP TS 29.002.
25.3 Authentication processes

25.3.1 Process Obtain_Authentication_Sets_GLR
This process is initiated by the GLR to fetch authentication vectors from a subscriber's HLR to the VLR. The process is
described in figure 25.3/1.
3GPP
Release 1999 149 3GPP TS 29.120 V3.0.0 (2000-03)
Process Obtain_Authent_Sets_GLR 25.3.1_1(2)

Figure 25.3/1: The Process to obtain authetication sets
from the HLR to the VLR via the GLR
Left from/to VLR
Right from/to HLR
NULL
Receive_
Open_ind Section 25.1
Vr, Error
OK
Wait_For_
Service_ NULL
Primitive
MAP_P_ABORT_ind
MAP_U_ABORT_ind MAP_SEND_ MAP_
MAP_CLOSE_ind AUTHENTICATION_ NOTICE_ind
INFO_ind
MAP_
NULL CLOSE_req
MAP_OPEN_req MAP_SEND_
AUTHENTICATION_INFO_req NULL
MAP_DELIMITER_req
Receive_
Section 25.1
Open_cnf
OK
Vr, Error
MAP_U_
ABORT_req
WAIT_FOR_
AUTHENTICATION_ NULL
INFO
Figure 25.3.1/1 (sheet 1 of 2): Process Obtain_Authentication_Sets_GLR
3GPP
Release 1999 150 3GPP TS 29.120 V3.0.0 (2000-03)
Process Obtain_Authent_Sets_GLR 25.3.1_2(2)

Figure 25.3/1: The Process to obtain authetication sets
from the HLR to the VLR via the GLR
Left from/to VLR
Right from/to HLR
WAIT_FOR_
AUTHENTICATION_
INFO
MAP_SEND_
AUTHENTICATION_ MAP_SEND_ MAP_ MAP_
INFO_cnf AUTHENTICATION_ CLOSE_ind CLOSE_ind
INFO_ind
MAP_SEND_
MAP_SEND_ MAP_ MAP_
AUTHENTICATION_ AUTHENTICATION_ CLOSE_req CLOSE_req
INFO_cnf INFO_req
WAIT_FOR_
AUTHENTICATION_ NULL
INFO
MAP_
MAP_ MAP_P_ABORT_ind MAP_P_ABORT_ind
NOTICE_ind
NOTICE_ind MAP_U_ABORT_ind MAP_U_ABORT_ind
MAP_
MAP_ MAP_U_ MAP_U_
CLOSE_req
CLOSE_req ABORT_req ABORT_req
MAP_U_
MAP_U_
ABORT_req NULL
ABORT_req
NULL
Figure 25.3.1/2 (sheet 2 of 2): Process Obtain_Authentication_Sets_GLR
25.3.2 Process Authentication_Failure_Report_GLR

This process is initiated by the GLR to notify a subscriber's HLR about the occurrence of an authentication failure in the
VLR or SGSN. The process is described in figure 25.3/2.
3GPP
Release 1999 151 3GPP TS 29.120 V3.0.0 (2000-03)
Process Authenticatio n_Failure_Report_GLR 25.3.2 _1(2)
Figure 25 .3 .2 /1: The Process to notify authetication

failure re port from the VLR/SGSN to t he HLR via the GLR
Left from/to VLR or SGSN
Righ t from /to HLR
NULL

O pen _ind
OK Vr, Error
W ait_ For_
Service_
Prim itive NULL
MAP_P_ABORT _ind
MAP_U_ABO RT_ind MAP_ MAP_
MAP_CLO SE_ind AUTHENTICATIO N_ NOT ICE_ind
F AILURE_REPORT_ind
MAP_
NULL
CLOSE_req
MAP_OPEN_req
MAP_AUTHENT ICAT ION_ NULL
FAILURE_REPORT_req
MAP_DELIMIT ER_req
Section 25 .1 Receiv e_
O pen_cnf
OK Vr, Error
MAP_U_
ABORT _req
WAIT_FO R_
RESPONSE NULL
Figure 25.3.2/1 (sheet 1 of 2): Process Authentication_Failure_Report_GLR
3GPP
Release 1999 152 3GPP TS 29.120 V3.0.0 (2000-03)
Proc ess Authentication_Failure_Report_G LR 25.3.2_2(2)

Figure 25.3. 2/1: The Process to notify authetication
failure report from the VLR/SGSN to the HLR via the GLR
Left from/ to VLR or SG SN
Right from/to HLR
WAIT_FOR_
RESPONSE
MAP_AUTHENT ICAT ION_ MAP_ MAP_

FAILURE_REPO RT _cnf CLO SE_ind CLOSE_ind
MAP_AUTHENT ICAT ION_ MAP_ MAP_

FAILURE_REPO RT_cnf CLOSE_req CLOSE_req
NULL
MAP_ MAP_ MAP_P_ABO RT_ind MAP_P_ABO RT_ind

NOTICE_ind NOTICE_ind MAP_U_ABO RT_ind MAP_U_ABORT_ind
MAP_ MAP_ MAP_U_ MAP_U_

CLOSE_req CLOSE_req ABORT_req ABO RT_req
MAP_U_ MAP_U_
ABOR T_req ABORT_req
NULL
Figure 25.3.2/2 (sheet 2 of 2): Process Authentication_ Failure_Report _GLR
25.4 Short Message Alert procedures

25.4.1 Subscriber_Present_GLR_AS_VLR process
The Subscriber_Present_GLR_AS_VLR process is invoked by the GLR, when GLR receives Update Location from
VLR and the MNRF flag is set. The general description of the short message alert procedures is in the subclause 23.3.
3GPP
Release 1999 153 3GPP TS 29.120 V3.0.0 (2000-03)
The GLR sends the MAP_READY_FOR_SM request to the HLR and waits for the HLR to answer. When receiving the
answer, the GLR will act as follows:
- the MNRF flag is cleared if the procedure is successful;
- the MNRF flag is not cleared if the procedure is not successful.
The Subscriber_Present_GLR_AS_VLR process is shown in the figure 25.4/1.
3GPP
Release 1999 154 3GPP TS 29.120 V3.0.0 (2000-03)
Process Subscriber_Present_GLR_AS_VLR 25.4.1(1)

GLR for mobile present situation
No MNRF
set
Yes
MAP_OPEN_req MAP_READY_FOR_SM_req
MAP_DELIMITER_req

Open_cnf
Error V1 OK
WF_
RESPONSE
Perform_
MAP_V1_ MAP_READY_ MAP_P_ABORT_ind
Dialogue FOR_SM_rsp MAP_U_ABORT_ind
MAP_CLOSE_ind
Yes
Error
No
Clear MNRF
Figure 25.4/1: Process Subscriber_Present_GLR_AS_VLR
3GPP
Release 1999 155 3GPP TS 29.120 V3.0.0 (2000-03)
25.4.2 The Mobile Subscriber is present

When GLR receives Update GPRS Location from SGSN, while the MS not reachable for GPRS (MNRG) flag is set,
the GLR will send the MAP_READY_FOR_SM request towards the HLR. The Alert Reason is set to indicate that the
mobile subscriber is present for GPRS.
When receiving the answer, the GLR will act as follows:
- MNRG is cleared if the procedure is successful.
- MNRG is not cleared if the procedure is not successful.
The Subscriber_Present_GLR_AS_SGSN process is shown in the figure 25.4/2.
3GPP
Release 1999 156 3GPP TS 29.120 V3.0.0 (2000-03)
Process Subscriber_Present_GLR_AS_SGSN 25.4.2(1)

GLR for mobile present situation
No MNRG
set
Yes
MAP_OPEN_req MAP_READY_FOR_SM_req
MAP_DELIMITER_req

Open_cnf
Error V1 OK
WF_
RESPONSE
Perform_
MAP_V1_ MAP_READY_ MAP_P_ABORT_ind
Dialogue FOR_SM_rsp MAP_U_ABORT_ind
MAP_CLOSE_ind
Yes
Error
No
Clear MNRG
Figure 25.4/2: Process Subscriber_Present_GLR_AS_SGSN
3GPP
Release 1999 157 3GPP TS 29.120 V3.0.0 (2000-03)
Annex A (informative):
Change history
Change history
TSG CN# Spec Version CR <Phase> New Version Subject/Comment
CN#07 29.120 2.0.0 R99 3.0.0 Approved at TSGN#07
CN#09 29.120 3.0.0 001r1 R99 3.1.0 Changes to support Authentication Failure
Report for GLR
CN#09 29.120 3.1.0 002 Rel-4 4.0.0 Changes to support secure transport MAP for
GLR
CN#16 29.120 4.0.0 Rel-5 5.0.0 Rel-5 created after CN#16
3GPP

3GPP TS 29.120

Uploaded by

Copyright:

Available Formats

3GPP TS 29.120

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

3GPP TS 29.120

Uploaded by

Copyright:

Available Formats

3GPP TS 29.120 V5.0.

3rd Generation Partnership Project;

3GPP support office address

No part may be reproduced except as authorized by written permission.

© 2002, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA,TTC).

12 Short message service management services..........................................................................................19

22.3 Erasure procedure..................................................................................................................................................104

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

 For a specific reference, subsequent revisions do not apply.

 For a non-specific reference, the latest version applies.

[1] 3GPP TS 23.003: "Numbering, addressing and identification".

[2] 3GPP TS 23.007: "Restoration procedures".

[3] 3GPP TS 23.012: "Location registration procedures".

[5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".

[6] 3GPP TS 23.119: "Gateway Location Register (GLR) - stage2".

apply: CCBS Completion of Call to Busy Subscriber

4 The entities and interfaces within the mobile network

4.1 The entities of the mobile system

- The Gateway location Register (GLR).

- The Intermediate MSC (IM-MSC).

- The Intermediate GSN (IM-GSN).

4.2 The Interfaces within the mobile services

- Interface between the HLR and the GLR.

- Interface between the VLR and the GLR.

- Interface between the MSC and the IM_MSC.

- Interface between the SGSN and the GLR.

- Interface between the MSC and the GLR.

- Interface between the GLR and the IM_GSN.

5 Overload and compatibility overview

5.1 Overload control for MAP entities

6 Requirements concerning the use of SCCP and TC

6.1 Use of SCCP

6.1.1 SCCP Class

6.1.2 Sub-System Number (SSN)

6.1.3 SCCP addressing

- the Gateway location Register (GLR);

- the Intermediate Mobile-services Switching Centre (IM_MSC);

- the Intermediate GPRS Support Node (IM_GSN).

6.1.3.2 The Gateway Location Register (GLR)

6.1.3.2.1 Addressed by the VLR

6.1.3.2.2 Addressed by the HLR

6.1.3.2.3 Addressed by the GMSC

6.1.3.2.4 Addressed by the IM-GSN

6.1.3.3 The Intermediate MSC (IM_MSC)

6.1.3.3.1 Addressed by the GMSC

6.1.3.3.2 Addressed by the GMLC

6.1.3.4 The Intermediate GSN (IM_GSN)

6.1.3.5 Summary table

7 General on MAP services

7.1 Common MAP services

Replace the MAP-U-ABORT service as follows.

7.1.1 MAP-U-ABORT service

Table 7.1/1: Service-primitives for the MAP-U-ABORT service

Parameters Request Indication

This parameter can take the following values:

- resource limitation (congestion);