29120-700

7/27/2019 29120-700

1/155

3GPP TS 29.120 V7.0.0 (2007-06)Technical Specification

3rd Generation Partnership Project;

Technical Specification Group Core Network;

Mobile Application Part (MAP) specification for GLR

(Release 7)

The present document has been developed within the 3rdGeneration 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 3GPPOrganisational Partners and shall not be implemented.

This Specification is provided for future development work within 3GPPonly. 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.

7/27/2019 29120-700

2/155

3GPP

2 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

Keywords

UMTS, network, SS7, MAP

3GPP

Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis

Valbonne - FRANCETel.: +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.

2007, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).

All rights reserved.

7/27/2019 29120-700

3/155

3GPP

3 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

Contents

0HForeword ............................................................................................................................................................ 154H6

1H1 Scope........................................................................................................................................................155H7

2H2 References................................................................................................................................................156H7

3H3 Abbreviations...........................................................................................................................................157H7

4H4 The entities and interfaces within the mobile network utilising the GLR............................................... 158H85H4.1 The entities of the mobile system .............................................................. .............................................................. 159H86H4.2 The Interfaces within the mobile services................................................................................................................ 160H8

7H5 Overload and compatibility overview......................................................................................................161H88H5.1 Overload control for MAP entities ............................................................................ .............................................. 162H89H5.2 Compatibility........................................................................................................................................................... 163H8

10H6 Requirements concerning the use of SCCP and TC ................................................................................ 164H911H6.1 Use of SCCP............................................................................................................................................................ 165H912H6.1.1 SCCP Class........................................................................................................................................................ 166H913H6.1.2 Sub-System Number (SSN) ................................................................ ............................................................... 167H914H6.1.3 SCCP addressing................................................................................................................................................ 168H915H6.2 Use of TC ......................................................... .............................................................. ....................................... 169H11

16H7 General on MAP services ......................................................................................................................170H1217H7.1 Common MAP services......................................................................................................................................... 171H1218H7.1.1 MAP-U-ABORT service ...................................................................... ........................................................... 172H12

19H8 Mobility services....................................................................................................................................173H1320H8.1 General ......................................................... .................................................................. ....................................... 174H1321H8.2 Location Management services ............................................................. ................................................................ 175H1422H8.3 Authentication Management services ............................................................... ..................................................... 176H1423H8.4 Subscriber management services .................................................................. ......................................................... 177H1424H8.5 Fault recovery services ............................................................... ..................................................................... ...... 178H1525H8.6 Subscriber Information services ................................................................. ........................................................... 179H15

26H9 Operation and maintenance services...................................................................................................... 180H1527H9.1 General ......................................................... .................................................................. ....................................... 181H1528H9.2 MAP_SEND_IMSI service ..................................................................... .............................................................. 182H15

29H10 Call handling services ............................................................................................................................183H1630H10.1 General ......................................................... .................................................................. ....................................... 184H1631H10.2 MAP_PROVIDE_ROAMING_NUMBER service ...................................................................... ......................... 185H1632H10.3 MAP_SET_REPORTING_STATE service ............................................................... ........................................... 186H1633H

10.4 MAP_STATUS_REPORT service........................................................................................................................187H

1634H10.5 MAP_REMOTE_USER_FREE service................................................................................................................ 188H16

35H11 Supplementary services related services................................................................................................ 189H1736H11.1 General ......................................................... .................................................................. ....................................... 190H1737H11.2 MAP_REGISTER_SS service............................................................................................................................... 191H1738H11.3 MAP_ERASE_SS service ............................................................. .................................................................. ...... 192H1739H11.4 MAP_ACTIVATE_SS service.............................................................................................................................. 193H1740H11.5 MAP_DEACTIVATE_SS service......................................................................................................................... 194H1741H

11.6 MAP_ INTERROGATE _SS service....................................................................................................................195H

1842H11.7 MAP_ REGISTER_PASSWORD service............................................................................................................. 196H1843H11.8 MAP_ GET_PASSWORD service........................................................................................................................ 197H1844H11.9 MAP_ PROCESS_UNSTRUCTURED_SS_REQUEST service.......................................................................... 198H1845H

11.10 MAP_ UNSTRUCTURED_SS_REQUEST service ......................................................................... ..............199H

1946H11.11 MAP_UNSTRUCTURED_SS_NOTIFY service............................................................................................ 200H1947H11.12 MAP_REGISTER_CC_ENTRY service......................................................................................................... 201H1948H11.13 MAP_ERASE_CC_ENTRY service .......................................................... ..................................................... 202H19

7/27/2019 29120-700

4/155

3GPP

4 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

49H12 Short message service management services......................................................................................... 203H1950H12.1 General ......................................................... .................................................................. ....................................... 204H1951H12.2 MAP-READY-FOR-SM service ............................................................ .............................................................. 205H2052H12.3 MAP-MT-FORWARD-SHORT-MESSAGE service............................................................................................ 206H20

53H13 Network-Requested PDP Context Activation services.......................................................................... 207H2054H

13.1 General ......................................................... .................................................................. .......................................208H

2055H13.2 MAP_SEND_ROUTING_INFO_FOR_GPRS service ............................................................................ ............. 209H2056H13.3 MAP_FAILURE_REPORT service ...................................................................... ................................................ 210H21

57H14 Void........................................................................................................................................................211H21

58H15 Element of procedure .............................................................................................................................212H2159H15.1 SDL descriptions ................................................................. ................................................................. ................. 213H21

60H16 Mapping onto TC services .....................................................................................................................214H22

61H17 Abstract syntax of the MAP protocol .................................................................................................... 215H2362H17.1 General ......................................................... .................................................................. ....................................... 216H2363H17.2 Packages specifications ............................................................... .................................................................... ...... 217H2364H17.3 Application contexts.............................................................................................................................................. 218H24

65H18 General on MAP user procedure............................................................................................................ 219H25

66H19 Mobility procedures ...............................................................................................................................220H2667H19.1 Location management Procedures .......................................................... ............................................................... 221H2668H19.1.1 Location updating .................................................................... .................................................................. ...... 222H2869H

19.1.2 Location Cancellation ................................................................... ...................................................................223H

4270H19.1.3 Purge MS .............................................................. ............................................................... ............................ 224H4871H19.2 Fault recovery procedures .................................................................... ........................................................... ...... 225H5372H19.2.1 RESET procedure .............................................................. ............................................................. ................. 226H5373H19.2.2 VLR restoration: the restore data procedure in the GLR ......................................................................... ........ 227H57

74H20 Operations and maintenance procedures ............................................................................................... 228H6475H

20.1 General ......................................................... .................................................................. .......................................229H

6476H20.2 Subscriber data management procedures............................................................................................................... 230H6477H20.2.1 General............................................................................................................................................................. 231H6478H20.2.2 Procedures in the GLR..................................................................................................................................... 232H6679H20.3 Subscriber Identity procedure................................................................................................................................ 233H7680H20.3.1 Subscriber identity procedure in the GLR........................................................................................................ 234H77

81H21 Call handling procedures .......................................................................................................................235H8082H21.1 General ......................................................... .................................................................. ....................................... 236H8083H21.2 Retrieval of routing information........................................................................... ................................................. 237H8184H21.2.1 General............................................................................................................................................................. 238H8185H21.2.2 Process in the GLR to provide a roaming number .................................................................... ....................... 239H8286H

21.2.3 Process in the GLR to provide subscriber information ...................................................................... ..............240H

8587H

21.3 Setting of Reporting State......................................................................................................................................241H

8888H21.3.1 General............................................................................................................................................................. 242H8889H21.3.2 Process in the GLR to set the reporting state .......................................................................... ......................... 243H8890H21.4 Status Reporting .............................................................. ..................................................................... ................. 244H9191H21.4.1 General............................................................................................................................................................. 245H9192H21.4.2 Process in the GLR for Status Reporting .............................................................. ........................................... 246H9193H21.5 Remote User Free ............................................................... .................................................................. ................. 247H9394H21.5.1 General............................................................................................................................................................. 248H9395H21.5.2 Process in the GLR for Remote User Free....................................................................................................... 249H94

96H22 Supplementary services procedures....................................................................................................... 250H9797H22.1 Functional supplementary service processes .................................................................... ..................................... 251H9798H22.1.1 Functional supplementary service process co-ordinator for GLR.................................................................... 252H9799H

22.1.2 Call completion supplementary service process co-ordinator for GLR ...........................................................253H

99100H

22.2 Registration procedure.........................................................................................................................................254H

101101H22.2.1 General........................................................................................................................................................... 255H101102H22.2.2 Procedures in the GLR................................................................................................................................... 256H102

7/27/2019 29120-700

5/155

3GPP

5 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

103H

22.3 Erasure procedure................................................................................................................................................257H

104104H22.3.1 General........................................................................................................................................................... 258H104105H22.3.2 Procedures in the GLR................................................................................................................................... 259H105106H22.4 Activation procedure .............................................................. .............................................................. ............... 260H105107H22.4.1 General........................................................................................................................................................... 261H105108H22.4.2 Procedures in the GLR................................................................................................................................... 262H105109H

22.5 Deactivation procedure........................................................................................................................................263H

107110H22.5.1 General........................................................................................................................................................... 264H107111H22.5.2 Procedures in the GLR................................................................................................................................... 265H108112H22.6 Interrogation procedure ....................................................... ................................................................. ............... 266H108113H

22.6.1 General...........................................................................................................................................................267H

108114H22.6.2 Procedures in the GLR................................................................................................................................... 268H108115H22.7 Password registration procedure.......................................................................................................................... 269H108116H22.7.1 General........................................................................................................................................................... 270H108117H22.7.2 Procedures in the GLR................................................................................................................................... 271H108118H22.8 Mobile Initiated USSD procedure ............................................................. .......................................................... 272H108119H22.8.1 Procedures in the GLR................................................................................................................................... 273H108120H22.9 Network initiated USSD procedure ......................................................... ............................................................ 274H111121H22.9.1 Procedure in the GLR ................................................................ ................................................................ .... 275H111122H22.10 Common macros for clause 22....................................................................................................................... 276H115123H22.10.1 SS Password handling macros ............................................................... ........................................................ 277H115124H22.11 Activation of a CCBS request........................................................................................................................ 278H117125H22.11.1 General........................................................................................................................................................... 279H117126H22.11.2 Procedure in the GLR ................................................................ ................................................................ .... 280H117127H22.12 Deactivation of a CCBS request ................................................................... ................................................. 281H119128H22.12.1 General........................................................................................................................................................... 282H119129H22.12.2 Procedure in the GLR ................................................................ ................................................................ .... 283H120

130H23 Short message service procedures........................................................................................................ 284H123131H23.1 General ......................................................... .................................................................. ..................................... 285H123132H23.2 The mobile terminated short message transfer procedure.................................................................................... 286H123133H23.2.1 Procedure in the Intermediate MSC............................................................................................................... 287H123134H23.2.2 Procedure in the GLR ................................................................ ................................................................ .... 288H129135H23.3 The Short Message Alert procedure ................................................................ .................................................... 289H135136H

23.3.1 Procedures in the GLR...................................................................................................................................290H

136

137H24 GPRS process description .................................................................................................................... 291H138138H24.1 General ......................................................... .................................................................. ..................................... 292H138139H24.2 Send Routing Information procedure ............................................................ ...................................................... 293H138140H

24.2.1 Process in the GLR for Send Routing Information for GPRS........................................................................294H

138141H24.2.2 Process in the IM-GSN for Send Routing Information for GPRS.................................................................. 295H139142H24.3 Failure Report procedure..................................................................................................................................... 296H142143H24.3.1 Process in the GLR for Failure Report........................................................................................................... 297H142144H24.3.2 Process in the IM-GSN for Failure Report .................................................................. .................................. 298H143

145H

25 General macro description ...................................................................................................................299H

146146H25.1 MAP open macros ...................................................... ............................................................... .......................... 300H146147H25.2 Macros to check the content of indication and confirmation primitives .............................................................. 301H146148H25.3 Authentication processes ........................................................... ........................................................... ............... 302H146149H25.3.1 Process Obtain_Authentication_Sets_GLR ............................................................. ...................................... 303H146150H25.3.2 Process Authentication_Failure_Report_GLR............................................................................................... 304H148151H25.4 Short Message Alert procedures.......................................................................................................................... 305H150152H25.4.1 Subscriber_Present_GLR_AS_VLR process................................................................................................. 306H150153H25.4.2 The Mobile Subscriber is present ..................................................................... ............................................. 307H153

7/27/2019 29120-700

6/155

3GPP

6 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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 theGateway 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.

7/27/2019 29120-700

7/155

3GPP

7 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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 nodeGGSN Gateway GPRS support node

7/27/2019 29120-700

8/155

3GPP

8 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

4 The entities and interfaces within the mobile networkutilising the GLR

4.1 The entities of the mobile systemThe 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.

7/27/2019 29120-700

9/155

3GPP

9 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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 signallingSystem 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 isnot 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 MSs 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.

7/27/2019 29120-700

10/155

3GPP

10 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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 utilisingthe GLR.

6.1.3.3.2 Addressed by the GMLC

When a location request for a particular MS needs to be sent to the MSs VMSC, the GMLC addresses the MSC using

an E.164 address received from the MSs 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.

7/27/2019 29120-700

11/155

3GPP

11 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

Table 6.1.3/1

to

from

fixed

net

work

HLR VLR MSC SGSN GGSN GLR IM-MSC IM-

GSN

fixed

network

homelocationregister

I:SPC/GTE:GT

T:VLR NUMBER

visitorlocation

register

I:SPC/GTE:GT

T:MGT(outside World Zone

1)/MSISDN(World Zone 1/)HLR

NUMBER(note)

mobile-

services

switchingcentre

E:GTT:SGSN NUMBER

I:SPC/GTE:GT

T:MSCNUMBER

ServingGPRSSupport

Node

I:SPC/GTT:MGT/MSISDN/HLR NUMBER

Gateway

GPRS

SupportNode

Note1

GatewayLocation

register

--- E:GTT:MGT(outsideWorld

Zone1)/MSISDN(World Zone1/)HLR NUMBER

(note)

I:SPC/GT

T:VLRNUMBE

R

--- I:SPC/GT

T:SGSNNUMBE

R

Intermedia

te-

MSC

--- I:SPC/GTT:MSC

NUMBER

Intermedia

te-GSN

--- I:SPC/GTT:HLR

NUMBER

I: Intra-PLMN E: Extra (Inter)-PLMN T: Address TypeGT: 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 HLRpreceding it, the VLR has to derive the HLR address from the IMSI of the MS. The result can be an SPCor 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 withany 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 informationfor addressing the HLR from addresses received in the course of the update location procedure (MSISDNor HLR number) or from the IMSI.When invoking the Restore Data procedure and an authentication information retrieval from the HLRpreceding it, the VLR must derive the information for addressing the HLR from the address informationreceived in association with the roaming number request. This may be either the IMSI received as aparameter of the MAP message requesting the Roaming Number or the Calling Party Address associatedwith 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 thething 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.

7/27/2019 29120-700

12/155

3GPP

12 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

7 General on MAP services

Refer to the corresponding section in 3GPP TS 29.002 with the exceptions described below.

7.1 Common MAP servicesThe 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 servicewith 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;

7/27/2019 29120-700

13/155

3GPP

13 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

- 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 diagnos tic i nformation

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 GeneralRegarding 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.

7/27/2019 29120-700

14/155

3GPP

14 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

8.2 Location Management services

Services Interval for adoption

VLR GLRMAP_UPDATE_LOCATION

GLR HLR

HLR GLR

GLR VLR

MAP_CANCEL _LOCATION

GLR SGSN

VLR GLR

SGSN GLR

MAP_PURGE_MS

GLR HLR

SGSN GLRMAP_UPDATE_GPRS_LOCATION

GLR HLR

Figure 8.2 /1

8.3 Authentication Management services


VLR GLR

SGSN GLR

MAP_SEND_AUTHENTICATION_INFO

GLR HLR

VLR GLR

SGSN GLR

MAP_AUTHENTICATION_FAILURE_REPORT

GLR HLR

Figure 8.3/1

8.4 Subscriber management services


HLR GLR

GLR VLR

MAP_ INSERT-SUBSCRIBER-DATA

GLR SGSN

HLR GLR

GLR VLR

MAP-DELETE-SUBSCRIBER-DATA

GLR SGSN

Figure 8.4/1

7/27/2019 29120-700

15/155

3GPP

15 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

8.5 Fault recovery services


HLR GLR

GLR VLR

MAP_RESET

GLR SGSN

HLR GLRMAP_FORWARD_CHECK_SS_INDICATION

GLR VLR

MAP_RESTORE_DATA VLR GLR

Figure 8.5/1

8.6 Subscriber Information services


VLR GLRMAP-PROVIDE-SUBSCRIBER-Info

GLR HLR

Figure 8.6/1

9 Operation and maintenance services

9.1 General

Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The

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


HLR GLRMAP_ SEND_IMSI

GLR VLR

Figure 9.2/1

7/27/2019 29120-700

16/155

3GPP

16 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

10 Call handling services

10.1 General

Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. Theintervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as

in 3GPP TS 29.002.

10.2 MAP_PROVIDE_ROAMING_NUMBER service


HLR GLRMAP_ PROVIDE_ROAMING_NUMBER

GLR VLRFigure 10.2/1

10.3 MAP_SET_REPORTING_STATE service


HLR GLRMAP_ SET_REPORTING_STATE

GLR VLR

Figure 10.3/1

10.4 MAP_STATUS_REPORT service


VLR GLRMAP_ STATUS_REPORT

GLR HLR

Figure 10.4/1

10.5 MAP_REMOTE_USER_FREE service


VLR GLRMAP_REMOTE_USER_FREE

GLR HLR

Figure 10.5/1

7/27/2019 29120-700

17/155

3GPP

17 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

11 Supplementary services related services

11.1 General

Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. Theintervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as

in 3GPP TS 29.002.

11.2 MAP_REGISTER_SS service


VLR GLRMAP_ REGISTER_SS

GLR HLRFigure 11.2/1

11.3 MAP_ERASE_SS service


VLR GLRMAP_ ERASE_SS

GLR HLR

Figure 11.3/1

11.4 MAP_ACTIVATE_SS service

Services interval for adoption

VLR GLRMAP_ ACTIVATE_SS

GLR HLR

Figure 11.4/1

11.5 MAP_DEACTIVATE_SS service


VLR GLRMAP_ DEACTIVATE_SS

GLR HLR

Figure 11.5/1

7/27/2019 29120-700

18/155

3GPP

18 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

11.6 MAP_ INTERROGATE _SS service


VLR GLRMAP_ INTERROGATE_SS

GLR HLR

Figure 11.6/1

11.7 MAP_ REGISTER_PASSWORD service


VLR GLRMAP_ REGISTER_PASSWORD

GLR HLR

Figure 11.7/1

11.8 MAP_ GET_PASSWORD service


HLR GLRMAP_ GET_PASSWORDGLR VLR

Figure 11.8/1

11.9 MAP_ PROCESS_UNSTRUCTURED_SS_REQUESTservice


VLR GLRMAP_ PROCESS_UNSTRUCTURED_SS_REQUEST

GLR HLR

Figure 11.9/1

7/27/2019 29120-700

19/155

3GPP

19 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

11.10 MAP_ UNSTRUCTURED_SS_REQUEST service


HLR GLRMAP_ UNSTRUCTURED_SS_REQUEST

GLR VLR

Figure 11.10/1

11.11 MAP_UNSTRUCTURED_SS_NOTIFY service


HLR GLRMAP_ UNSTRUCTURED_SS_NOTIFYGLR VLR

Figure 11.11/1

11.12 MAP_REGISTER_CC_ENTRY service


VLR GLRMAP_ UNSTRUCTURED_SS_NOTIFY

GLR HLR

Figure 11.12/1

11.13 MAP_ERASE_CC_ENTRY service


VLR GLRMAP_ ERASE_CC_NOTIFY

GLR HLR

Figure 11.13/1

12 Short message service management services

12.1 General

Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The


in 3GPP TS 29.002.

7/27/2019 29120-700

20/155

3GPP

20 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

12.2 MAP-READY-FOR-SM service


VLR GLR

SGSN GLR

MAP-READY-FOR-SM

GLR HLR

Figure 12.2/1

12.3 MAP-MT-FORWARD-SHORT-MESSAGE service


SMS-GMSC IM-MSC

IM-MSC MSC

SMS-GMSC GLR

MAP_MT_FORWARD_SHORT_MESSAGE

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

7/27/2019 29120-700

21/155

3GPP

21 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

7/27/2019 29120-700

22/155

3GPP

22 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

Process to manage

a MAP dialogue

Process Secure_MAP_DSM_GLR 15.1.1 (1)

DIALOGUE_

AC CEPTE D

MAP_REQ

any MAP specific

request primitive

Secure_

Transport_

required

Requesting_

MAP_SSM

Service_

Invoked_

VIA_Intern2

Secure_

Requesting_

MAP_SSM

Service_

Invoked_

VIA_Intern4

MAP_rsp

An y M AP sp ecif ic

response primitive

Secure_

Transport_

required

Response_

Issued_

VIA_Imtern1

DIALOGUE_

AC CEP TED

MAP_

CLOSE_

req

TC_END_req

VIA_TC1

Secure_

Transport_

required

Terminated_

VIA_Intern1To all active PSSMs

Terminated_VIA_Intern2

To all active RSSMs

IDLE

Terminated_

VIA_Intern3To all active SPSSMs

Terminated_VIA_Intern4

To all active SRSSMs

IDLE

MAP_U_

AB OR T_

req

User-reason=

AC -no t-

suppoeted

Ab ort-reas on :=

User-specific

User-info :=

MAP-UserAbortInfo

TC_U_

AB ORT _req_

VIA_TC1

Abo rt-reas on : =

AC -not -

supported

Response_

Issued_

VIA_Imtern3

MAP_

DELIMITER_req

TC_

CONTINUE_

req_VIA_TC1

DIALOGUE_

ESTABLISHED

(FALSE)

(TRUE)

(FALSE)

(FALSE) (TRUE)

no

yes

(TRUE)

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.

7/27/2019 29120-700

23/155

3GPP

23 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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: suppl ier and consumer defini tion

Operation Package supplier consumer

HLR GLRLocationUpdatingPackage-v3

GLR VLR

VLR or SGSN GLRLocationCancellationPackage-v3

GLR HLR

VLR GLRRoamingNumberEnquiryPackage-v3

GLR HLR

HLR GLR

GLR VLR

InfoRetrievalPackage-v2

GLR SGSN

HLR GLR

GLR VLR

InfoRetrievalPackage-v1

GLR SGSN

HLR GLRIMSIRetrievalPackage-v2

GLR VLR

VLR or SGSN GLRSubscriberDataMngtStandAlonePackage-v3

GLR HLR

VLR or SGSN GLRSubscriberDataMngtPackage-v3

GLR HLR

VLR or SGSN GLRResetPackage-v2

GLR HLR

HLR GLRFunctionalSsPackage-v2

GLR HLR

HLR GLRBindingPackage-v1

GLR VLR

HLR GLRUnstructuredSsPackage-v2

GLR VLR

HLR GLRUnstructuredSsPackage-v1

GLR VLR

IM-MSC orGLR

GMSC

MSC IM-MSC

MTShortMsgRelayPackage-v3

SGSN GLR

HLR GLR

GLR SGSN

MwdMngtPackage-v3

GLR VLR

HLR GLRMwdMngtPackage-v1

GLR VLR

DataRestorationPackage-v3 GLR VLRHLR GLR

GLR VLR

PurgingPackage-v3

GLR SGSN

7/27/2019 29120-700

24/155

3GPP

24 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

Operation Package supplier consumer

VLR GLRSubscriberInformationEnquiryPackage-v3

GLR HLR

HLR GLRGprsLocationUpdatingPackage-v3

GLR SGSN

FailureReportingPackage-v3 GLR IM-GSNVLR GLRSetReportingStatePackage-v3

GLR HLR

HLR GLRStatusReportPackage-v3

GLR VLR

VLR GLRRemoteUserFreePackage-v3

GLR HLR

HLR GLRCallCompletionPackage-v3

GLR VLR

HLR GLR

GLR VLR

AuthenticationFailureReportPackage-v3

GLR SGSN

SecureTransportHandlingPackage-v3 This operation package includesthe operations required for thesecure transport of MAPmessages between any MAPentities.

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.

7/27/2019 29120-700

25/155

3GPP

25 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

Table 17.3/1: suppl ier and consumer defini tion

Application Context Version Initiator Responder

HLR GLRlocationCancellationContext v3

GLR VLR or SGSN

VLR GLRimsiRetrievalContext v2GLR HLR

VLR or SGSN GLRinfoRetrievalContext v2

GLR HLR

VLR or SGSN GLRmwdMngtContext v3

GLR HLR

VLR or SGSN GLRmsPurgingContext v3

GLR HLR

HLR GLRresetContext v2

GLR VLR or SGSN

VLR GLR

GLR HLR

HLR GLR

networkUnstructuredSsContext v2

GLR VLR

VLR GLRnetworkFunctionalSsContext v2

GLR HLR

MSC IM-MSC or GLR

IM-MSC MSC

shortMsgMT-RelayContext v3

GLR SGSN

VLR GLRnetworkLocUpContext v3

GLR HLR

SGSN GLRgprsLocationUpdateContext v3

GLR HLR

HLR GLRsubscriberDataMngtContext v3

GLR VLR or SGSN

HLR GLRroamingNumberEnquiryContext v3

GLR VLR

gprsLocationInfoRetrievalContext v3 IM-GSN GLRfailureReportContext v3 IM-GSN GLR

HLR GLRsubscriberInfoEnquiryContext v3

GLR VLR

VLR GLR

GLR HLR

HLR GLR

reportingContext v3

GLR VLR

VLR GLRcallCompletionContext v3

GLR HLR

VLR or SGSN GLRauthenticationFailureReportContext v3

GLR HLR

SecureTransportHandlingContext v3 This application context is usedfor the secure transport of MAPmessages between any MAPentities.

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.

7/27/2019 29120-700

26/155

3GPP

26 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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 thesubscriber. 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.

7/27/2019 29120-700

27/155

3GPP

27 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

Location management coordination process in the GLR

Process Location_Management_Coordinator_GLR 19.1.1.1(1)

NULL

Receive_Open_Ind

Section 25.1

WAIT_FOR_SERVICE_PRIMITIVE

'Perform_MAP_Vr_Dialogue'

MAP_

UPDATE_LOCATION_Ind

MAP_

RESTORE_DATA_Ind

MAP_

NOTICE_Ind

NULL NULL

Update_Location_GLR

RESTORE_DATA_GLR

MAP-CLOSE_Req

MAP_UPDATE_LOCATION_Ind

MAP_RESTORE_DATA_Ind

NULL

RELAY_INFO

*fromProvider

*fromOFFSPRING

MAP-U-ABORT_Req,MAP-CLOSE_Reqfrom OFFSPRING

MAP-P-ABORT_Ind,MAP-U-ABORT_Ind,MAP-CLOSE_Ind

-toOFFSPRING

-toProvider

-toProvider

-toOFFSPRING

RELAY_INFO RELAY_INFO NULL NULL

'OK''Vr' 'Error'

Figure 19.1.1/1: Process Location_Management_Coordinator_GLR

7/27/2019 29120-700

28/155

3GPP

28 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

7/27/2019 29120-700

29/155

3GPP

29 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

+----+ +----+ +----+ +-----+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

7/27/2019 29120-700

30/155

3GPP

30 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

GLR MAP protocol machinehandling location updating andinterfaceing with VLR MAPprotocol machine

Process Update_Location_GLR 19.1.2.2_1(3)

Left to VLRRight to GLRapplication


MAP_Update_Location_ind

UpdateLocation

WAIT_FOR_APPLICATION_

RESPONSE

UpdateLocation Ack

Set result

MAP_UPDATE_LOCATION_Rsp.MAP_CLOSE_Req.

Update LocationNegative Response

Set Error


Insert_Subscriber_Data

1

Forward checkSS indication

MAP_FORWARD_CHECK_SS_INDICATION_reqMAP_DELIMITER_req


RESPONSE

Abort

MAP_U_ABORT_req

2

Figure 19.1.2/2 (sheet 1 of 3): Process Update_Location_GLR

7/27/2019 29120-700

31/155

3GPP

31 3GPP TS 29.120 V7.0.0 (2007-06)Release 7




1

MAP_Insert_Subscriber_Data_Req

MAP_Delimiter_Req

WAIT_FOR_ISD_Cnf_WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE

MAP_Insert_Subscriber_Data_Cnf

MAP_U_ABORT_IndMAP_P_ABORT_IndMAP_CLOSE_Ind

MAP_NOTICE_Ind

Abort Set NegativeResultSystem Failure

ISDNegative Response

CheckConfirmation

Section 25.2 2

Insert_Subscriber_Data_Cnf

Set NegativeResponse

System Failure

MAP User Errorto NegativeResponse

2


2

OK Provider error Data error

User error


7/27/2019 29120-700

32/155

3GPP

32 3GPP TS 29.120 V7.0.0 (2007-06)Release 7





UpdateLocation Ack

Set result



Set Error

InsertSubscriberData

1

Abort

MAP_U_ABORT_Req.


7/27/2019 29120-700

33/155

3GPP

33 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

GLR MAP protocol machinehandling Location Management andinterfacing to HLR MAP protocolmachine, handling Location Management.

Process GLR_Update_Location_HLR 19.1.2.3_1(3)

Signals to/from the leftare to/from the GLR application.

Signals to/from the rightare to/from the HLR MAP protocolmachine.

IDLE

Update Location

MAP_OPEN_ReqMAP_UPDATE_LOCATION_ReqMAP_DELIMITER_Req

ReceiveOpenCnf.

Section 25.1

Wait_For_HLR_Response

Perform MAP Vr Set error


OKVr

Error

Figure 19.1.2/3 (Sheet 1 of 3): Process GLR_Update_Location_HLR

7/27/2019 29120-700

34/155

3GPP

34 3GPP TS 29.120 V7.0.0 (2007-06)Release 7


Process GLR_Update_Location_HLR 19.1.2.3_2(3)Signals to/from the leftare to/from the GLR application.



MAP_FORWARD_Check_SS_ind

ForwardCheck SSIndication

Wait_For_HLR_or_Application_

Response

MAP_INSERT_SUBSCRIBER_DATA_ind

InsertSubscriberdata

MAP_Notice_Indication

MAP_Close_request

Set negative response

Update Locationnegative response

Idle

MAP_U_Abort_indMAP_P_Abort_indMAP_Close_ind

Abort

Idle

MAP_Update_Location_cnf

Check Confirmation

Section 25.2

UpdateLocation ack

Idle

Set negativeresponse


OK

Provider Error,User Error,Data Error


7/27/2019 29120-700

35/155

3GPP

35 3GPP TS 29.120 V7.0.0 (2007-06)Release 7


Process GLR_Update_Location_HLR 19.1.2.3_3(3)


Signals to/from the rightare to/from the HLR MAP protocol

machine.

Wait_For_HLR_or_

ApplicationResponse

MAP_FORWARD_Check_SS_ind

ForwardCheck SSIndication


Response


InsertSubscriberdata

InsertSubscriber

Data ack

MAP_Insert_Subscriber_Data_response

InsertSubscriberData negativeresponse

Set user error

MAP_Update_Location_cnf

Check Confirmation

Section 25.2

UpdateLocation ack

Idle



Abort

Map_U_Abort_request

Idle


MAP_Close_request




Abort

OK



7/27/2019 29120-700

36/155

3GPP

36 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

GLR MAP protocol machine

handling location updating andinterfaceing with SGSN MAPprotocol machine

Process Update_GPRS_Location_GLR 19.1.2.4_1(3)

Left to SGSNRight to GLRapplication

NULL

ReceiveOpenInd.


MAP_Update_

GPRS_Location_ind

Update GPRSLocation

WAIT_FOR_APPLICATION_RESPONSE

Update GPRSLocation Ack

Set result

MAP_UPDATE_GPRS_LOCATION_Rsp.MAP_CLOSE_Req.

Update GPRSLocationNegative Response

Set error

MAP_UPDATE_GPRS_LOCATION_Rsp.MAP_CLOSE_Req.


1

Abort

MAP_U_ABORT_req

Perform_MAP_Vr_Dialogue

NULL

NULL

2

OK

V2V1Error

Figure 19.1.2/4 (sheet 1 of 3): Process Update_GPRS_Location_GLR

7/27/2019 29120-700

37/155

3GPP

37 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

GLR MAP protocol machinehandling location updating andinterfaceing with SGSN MAPprotocol machine



1

3MAP_Insert_Subscriber_Data_ReqMAP_Delimiter_Req


MAP_Insert_Subscriber_Data_Cnf MAP_U_ABORT_IndMAP_P_ABORT_IndMAP_CLOSE_Ind

MAP_NOTICE_Ind

AbortSet Negative

ResultSystem Failure


CheckConfirmation

Section 25.2 3

Insert_Subscriber_Data_Cnf

Set NegativeResponse

System Failure

MAP User Errorto NegativeResponse

2


2

OK Provider error Data error

User error


7/27/2019 29120-700

38/155

3GPP

38 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

GLR MAP protocol machinehandling location updating andinterfaceing with SGSN MAPprotocol machine




UpdateLocation Ack

Set result


Update GPRS LocationNegative Response

Set Error


1

Abort

MAP_U_ABORT_req


7/27/2019 29120-700

39/155

3GPP

39 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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)



IDLE

Update GPRS Location

MAP_OPEN_ReqMAP_UPDATE_GPRS_LOCATION_ReqMAP_DELIMITER_Req

ReceiveOpenCnf.

Section 25.1


Set error

Update GPRS LocationNegative Response

Perform MAP Vr

OK Error Vr

Figure 19.1.2/5 (Sheet 1 of 3): Process GLR_Update_GPRS_Location_HLR

7/27/2019 29120-700

40/155

3GPP

40 3GPP TS 29.120 V7.0.0 (2007-06)Release 7




Signals to/from the right

are to/from the HLR MAP protocolmachine.


MAP_Update_GPRS_Location_cnf

Check Confirmation Section 25.2

Update GPRSLocation ack

Idle


Update GPRS Locationnegative response




Response


MAP_Close_request



Idle


Abort

OKProvider Error,User Error,Data Error


7/27/2019 29120-700

41/155

3GPP

41 3GPP TS 29.120 V7.0.0 (2007-06)Release 7





are to/from the HLR MAP protocolmachine.

Wait_For_HLR_or_ApplicationResponse




Response

InsertSubscriberData ack

MAP_Insert_Subscriber_Data_response

Insert SubscriberData negativeresponse

Set user error

MAP_Update_GPRS_

Location_cnf

Check Confirmation

Section 25.2

Update GPRSLocation ack

Idle



Abort

Map_U_Abort_request

Idle

MAP_Notice_

Indication

MAP_Close_request



MAP_U_Abort_ind

MAP_P_Abort_indMAP_Close_ind

Abort

OK



7/27/2019 29120-700

42/155

3GPP

42 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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 ---------------------> LOCATION LOCATION MAP_CANCEL_LOCATION MAP_CANCEL_LOCATION

7/27/2019 29120-700

43/155

3GPP

43 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

+----+ D +----+ D +-----+VLR/+-----------+------------+GLR +-------+--------+PVLR/SGSN| PSGSN+----+ +----+ +-----+

MAP_UPDATE_LOCATION or MAP_UPDATE_GPRS_LOCATION ----------------------------> MAP_CANCEL_

---------------------> LOCATION MAP_CANCEL_LOCATION

7/27/2019 29120-700

44/155

3GPP

44 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

GLR MAP protocol machinehandling Location cancelation andinterfacing to HLR MAP protocolmachine, handling Location Cancelation.

Process Cancel_Location_GLR 19.1.3.5(1)

Signals to/from the leftare to/from the GLR Locationcancellation application.


are to/from the HLR MAP protocolmachine, handling Location Cancellation.

NULL

ReceiveOpenInd.


MAP_CANCEL_LOCATION_ind MAP_NOTICE_ind Perform_MAP_Vr_Dialogue NULL

MAP_CLOSE_req NULL

Cancel Location NULL

WAIT_FOR_

APPLICATION_RESPONSE

CancelLocation Ack

Cancel LocationNegative response

Abort

MAP_CANCEL_LOCATION_Rsp.MAP_CLOSE_Req.

MAP_U_ABORT_req

NULL NULL

OK

V2 V1Error

Figure 19.1.3/5: Process Cancel_Location_GLR

7/27/2019 29120-700

45/155

3GPP

45 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

GLR MAP protocol machinehandling cancel location andinterfacing with VLR MAPprotocol machine

Process GLR_Cancel_Location_VLR 19.1.3.6(1)

VLR to the LeftGLR Application to the Right

IDLE

CancelLocation

MAP_OPEN_Req

MAP_CANCEL_LOCATION_ReqMAP_DELIMITER_Req

ReceiveOpenCnf.

WAIT_FOR_ACK Perform MAP Vr

Cancel LocationNegative Response

MAP_CANCEL_LOCATION_Cnf

MAP_P_ABORT_Ind

MAP_NOTICE_Ind

Check_Confirmation

MAP_CLOSE_Req



Cancel LocationAck


OKVr

Error

OKError

Figure 19.1.3/6: Process GLR_Cancel_Location_VLR

7/27/2019 29120-700

46/155

3GPP

46 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.


handling Location cancelation andinterfacing to HLR MAP protocolmachine, handling Location Cancelation.

Process Cancel_GPRS_Location_GLR 19.1.3.7(1)

Signals to/from the rightare to/from the GLR Locationcancellation application.

Signals to/from the leftare to/from the HLR MAP protocolmachine, handling Location Cancellation.

NULL

ReceiveOpenInd.


MAP_CANCEL_LOCATION_ind

Cancel Location

WAIT_FOR_APPLICATION_RESPONSE

CancelLocation Ack

MAP_CANCEL_LOCATION_Rsp.MAP_CLOSE_Req.

NULL


Abort

MAP_U_ABORT_req

NULL

MAP_NOTICE_ind

MAP_CLOSE_req

NULL


NULL

NULL

OK V2 V1Error

Figure 19.1.3/7: Process Cancel_GPRS_Location_GLR

7/27/2019 29120-700

47/155

3GPP

47 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

GLR MAP protocol machinehandling cancel location andinterfacing with SGSN MAPprotocol machine

Process GLR_Cancel_Location_SGSN 19.1.3.8(1)

SGSN to the LeftGLR Application to the Right

IDLE

CancelLocation

MAP_OPEN_Req

MAP_CANCEL_LOCATION_ReqMAP_DELIMITER_Req

ReceiveOpenCnf.


Perform MAP Vr

WAIT_FOR_ACK

MAP_CANCEL_LOCATION_Cnf

Check_Confirmation

Cancel LocationAck


MAP_P_ABORT_Ind


MAP_NOTICE_Ind

MAP_CLOSE_Req


ErrorVr

OK

OKError

Figure 19.1.3/8: Process GLR_Cancel_Location_SGSN

7/27/2019 29120-700

48/155

3GPP

48 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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

7/27/2019 29120-700

49/155

3GPP

49 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

GLR MAP protocol machinehandling purge MS

Process Purge_MS_GLR 19.1.4.2(1)

VLR to the LeftGLR Application to the Right

NULL

ReceiveOpen Ind.



NULL

NULL

MAP_NOTICE_Ind

MAP_PURGE_MS_Ind

MAP_CLOSE_Req

Purge MS


RESPONSE

Purge MSAck

Purge MSNegative Response

Abort

MAP_PURGE_MS_RspMAP_CLOSE_Req MAP_U_ABORT_req

NULL NULL

OK

V2

V1Error

Figure 19.1.4/2: Process Purge_MS_GLR

7/27/2019 29120-700

50/155

3GPP

50 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.


handling purge MS andinterfacing to HLR MAP protocolmachine, handling Purge MS.

Process GLR_Purge_MS_HLR 19.1.4.3(1)



Null

Purge MS

MAP_OPEN_ReqMAP_PURGE_MS_ReqMAP_DELIMITER_Req

ReceiveOpen

Cnf.

Section 25.1

Set error


Perform MAP Vr


MAP_PURGE_MS_cnf

Check Confirmation

Purge MS ack

Null


Purge MSnegativeresponse


MAP_Close_request


ErrorVr

OK


Figure 19.1.4/3: Process GLR_PURGE_MS_HLR

7/27/2019 29120-700

51/155

3GPP

51 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

GLR MAP protocol machinehandling purge MS

Process Purge_MS_GLR_for_GPRS 19.1.4.4(1)

SGSN to the LeftGLR Application to the Right

NULL

ReceiveOpen Ind.

Perform_MAP_

Vr_Dialogue

NULLWAIT_FOR_SERVICE_

PRIMITIVE

MAP_NOTICE_Ind

MAP_CLOSE_Req

MAP_PURGE_MS_Ind

Purge MS


RESPONSE

Purge MSAck

MAP_PURGE_MS_RspMAP_CLOSE_Req

NULL


Abort

MAP_U_ABORT_req

NULL

NULL

V2OK V1

Error

Figure 19.1.4/4: Process Purge_MS_GLR_for_GPRS

7/27/2019 29120-700

52/155

3GPP

52 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

GLR MAP protocol machinehandling purge MS andinterfacing to HLR MAP protocolmachine, handling Purge MS.

Process GLR_Purge_MS_HLR_for_GPRS 19.1.4.5(1)



Null

Purge MS

MAP_OPEN_ReqMAP_PURGE_MS_ReqMAP_DELIMITER_Req

ReceiveOpenCnf.


MAP_PURGE_MS_cnf

Check Confirmation

Purge MS ack

Null


Purge MSnegativeresponse


MAP_Close_request


Perform MAP Vr Set error


OK


VrError

Figure 19.1.4/5: Process GLR_Purge_MS_HLR_for_GPRS

7/27/2019 29120-700

53/155

3GPP

53 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

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.

19.2.1.3 Detailed procedure in GLR

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.

7/27/2019 29120-700

54/155

3GPP

54 3GPP TS 29.120 V7.0.0 (2007-06)Release 7

GLR MAP protocol machinehandling reset message from HLR.

Process RECEIVE_RESET_IN_GLR 19.2.1.1(1)

Left to GLRapplicationRight to HLR

NULL

ReceiveOpenInd.

WAIT_FOR_SERVICE_PRIMITI

29120-700

Documents