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 (Release 7) The present document has been developed within the 3 rd Generation Partnership Project ( TM ) and may be further elaborated for the purposes of. The present document has not been subject to any approval process by the Organisational Partners and shall not be implemented. This Specification is provided for future development work within only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the TM system should be obtained via the Organisational Partners' Publications Offices.
2 TS 29.120 V7.0.0 (2007-06) Keywords UMTS, network, SS7, MAP Postal address 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. 2007, Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved.
3 TS 29.120 V7.0.0 (2007-06) Contents 0HForeword... 154H6 1H1 2H2 3H3 Scope... 155H7 References... 156H7 Abbreviations... 157H7 4H4 The entities and interfaces within the mobile network utilising the... 158H8 5H4.1 The entities of the mobile system... 159H8 6H4.2 The Interfaces within the mobile services... 160H8 7H5 Overload and compatibility overview... 161H8 8H5.1 Overload control for MAP entities... 162H8 9H5.2 Compatibility... 163H8 10H6 Requirements concerning the use of SCCP and TC... 164H9 11H6.1 Use of SCCP... 165H9 12H6.1.1 SCCP Class... 166H9 13H6.1.2 Sub-System Number (SSN)... 167H9 14H6.1.3 SCCP addressing... 168H9 15H6.2 Use of TC... 169H11 16H7 General on MAP services... 170H12 17H7.1 Common MAP services... 171H12 18H7.1.1 MAP-U-ABORT service... 172H12 19H8 Mobility services... 173H13 20H8.1 General... 174H13 21H8.2 Location Management services... 175H14 22H8.3 Authentication Management services... 176H14 23H8.4 Subscriber management services... 177H14 24H8.5 Fault recovery services... 178H15 25H8.6 Subscriber Information services... 179H15 26H9 Operation and maintenance services... 180H15 27H9.1 General... 181H15 28H9.2 SEND_IMSI service... 182H15 29H10 Call handling services... 183H16 30H10.1 General... 184H16 31H10.2 PROVIDE_ROAMING_NUMBER service... 185H16 32H10.3 SET_REPORTING_STATE service... 186H16 33H10.4 STATUS_REPORT service... 187H16 34H10.5 REMOTE_USER_FREE service... 188H16 35H11 Supplementary services related services... 189H17 36H11.1 General... 190H17 37H11.2 REGISTER_SS service... 191H17 38H11.3 ERASE_SS service... 192H17 39H11.4 ACTIVATE_SS service... 193H17 40H11.5 DEACTIVATE_SS service... 194H17 41H11.6 INTERROGATE _SS service... 195H18 42H11.7 REGISTER_PASSWORD service... 196H18 43H11.8 GET_PASSWORD service... 197H18 44H11.9 PROCESS_UNSTRUCTURED_SS_REQUEST service... 198H18 45H11.10 UNSTRUCTURED_SS_REQUEST service... 199H19 46H11.11 UNSTRUCTURED_SS_NOTIFY service... 200H19 47H11.12 REGISTER_CC_ENTRY service... 201H19 48H11.13 ERASE_CC_ENTRY service... 202H19
4 TS 29.120 V7.0.0 (2007-06) 49H12 Short message service management services... 203H19 50H12.1 General... 204H19 51H12.2 MAP-READY-FOR-SM service... 205H20 52H12.3 MAP-MT-FORWARD-SHORT-MESSAGE service... 206H20 53H13 Network-Requested PDP Context Activation services... 207H20 54H13.1 General... 208H20 55H13.2 SEND_ROUTING_INFO_FOR_GPRS service... 209H20 56H13.3 FAILURE_REPORT service... 210H21 57H14 Void... 211H21 58H15 Element of procedure... 212H21 59H15.1 SDL descriptions... 213H21 60H16 Mapping onto TC services... 214H22 61H17 Abstract syntax of the MAP protocol... 215H23 62H17.1 General... 216H23 63H17.2 Packages specifications... 217H23 64H17.3 Application contexts... 218H24 65H18 General on MAP user procedure... 219H25 66H19 Mobility procedures... 220H26 67H19.1 Location management Procedures... 221H26 68H19.1.1 Location updating... 222H28 69H19.1.2 Location Cancellation... 223H42 70H19.1.3 Purge MS... 224H48 71H19.2 Fault recovery procedures... 225H53 72H19.2.1 RESET procedure... 226H53 73H19.2.2 VLR restoration: the restore data procedure in the... 227H57 74H20 Operations and maintenance procedures... 228H64 75H20.1 General... 229H64 76H20.2 Subscriber data management procedures... 230H64 77H20.2.1 General... 231H64 78H20.2.2 Procedures in the... 232H66 79H20.3 Subscriber Identity procedure... 233H76 80H20.3.1 Subscriber identity procedure in the... 234H77 81H21 Call handling procedures... 235H80 82H21.1 General... 236H80 83H21.2 Retrieval of routing information... 237H81 84H21.2.1 General... 238H81 85H21.2.2 Process in the to provide a roaming number... 239H82 86H21.2.3 Process in the to provide subscriber information... 240H85 87H21.3 Setting of Reporting State... 241H88 88H21.3.1 General... 242H88 89H21.3.2 Process in the to set the reporting state... 243H88 90H21.4 Status Reporting... 244H91 91H21.4.1 General... 245H91 92H21.4.2 Process in the for Status Reporting... 246H91 93H21.5 Remote User Free... 247H93 94H21.5.1 General... 248H93 95H21.5.2 Process in the for Remote User Free... 249H94 96H22 Supplementary services procedures... 250H97 97H22.1 Functional supplementary service processes... 251H97 98H22.1.1 Functional supplementary service process co-ordinator for... 252H97 99H22.1.2 Call completion supplementary service process co-ordinator for... 253H99 100H22.2 Registration procedure... 254H101 101H22.2.1 General... 255H101 102H22.2.2 Procedures in the... 256H102
5 TS 29.120 V7.0.0 (2007-06) 103H22.3 Erasure procedure... 257H104 104H22.3.1 General... 258H104 105H22.3.2 Procedures in the... 259H105 106H22.4 Activation procedure... 260H105 107H22.4.1 General... 261H105 108H22.4.2 Procedures in the... 262H105 109H22.5 Deactivation procedure... 263H107 110H22.5.1 General... 264H107 111H22.5.2 Procedures in the... 265H108 112H22.6 Interrogation procedure... 266H108 113H22.6.1 General... 267H108 114H22.6.2 Procedures in the... 268H108 115H22.7 Password registration procedure... 269H108 116H22.7.1 General... 270H108 117H22.7.2 Procedures in the... 271H108 118H22.8 Mobile Initiated USSD procedure... 272H108 119H22.8.1 Procedures in the... 273H108 120H22.9 Network initiated USSD procedure... 274H111 121H22.9.1 Procedure in the... 275H111 122H22.10 Common macros for clause 22... 276H115 123H22.10.1 SS Password handling macros... 277H115 124H22.11 Activation of a CCBS uest... 278H117 125H22.11.1 General... 279H117 126H22.11.2 Procedure in the... 280H117 127H22.12 Deactivation of a CCBS uest... 281H119 128H22.12.1 General... 282H119 129H22.12.2 Procedure in the... 283H120 130H23 Short message service procedures... 284H123 131H23.1 General... 285H123 132H23.2 The mobile terminated short message transfer procedure... 286H123 133H23.2.1 Procedure in the Intermediate MSC... 287H123 134H23.2.2 Procedure in the... 288H129 135H23.3 The Short Message Alert procedure... 289H135 136H23.3.1 Procedures in the... 290H136 137H24 GPRS process description... 291H138 138H24.1 General... 292H138 139H24.2 Send Routing Information procedure... 293H138 140H24.2.1 Process in the for Send Routing Information for GPRS... 294H138 141H24.2.2 Process in the IM-GSN for Send Routing Information for GPRS... 295H139 142H24.3 Failure Report procedure... 296H142 143H24.3.1 Process in the for Failure Report... 297H142 144H24.3.2 Process in the IM-GSN for Failure Report... 298H143 145H25 General macro description... 299H146 146H25.1 MAP open macros... 300H146 147H25.2 Macros to check the content of indication and confirmation primitives... 301H146 148H25.3 Authentication processes... 302H146 149H25.3.1 Process Obtain_Authentication_Sets_... 303H146 150H25.3.2 Process Authentication_Failure_Report_... 304H148 151H25.4 Short Message Alert procedures... 305H150 152H25.4.1 Subscriber_Present AS_VLR process... 306H150 153H25.4.2 The Mobile Subscriber is present... 307H153
6 TS 29.120 V7.0.0 (2007-06) Foreword This Technical Specification (TS) has been produced by the 3 rd Generation Partnership Project (). The present document specifies the signalling uirements and procedures used at network elements related to the Gateway Location Register () for Mobile Application Part (MAP) within the system. (i.e. the present document specifies the delta against 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 TS 29.120 V7.0.0 (2007-06) 1 Scope The present document describes the signalling uirements and procedures used at network elements related to the for MAP within the system at the application level. The present document gives the description of the systems needed only in the network utilising as the delta document against 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] TS 23.003: "Numbering, addressing and identification". [2] TS 23.007: "Restoration procedures". [3] TS 23.012: "Location registration procedures". [4] TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". [5] TS 29.002: "Mobile Application Part (MAP) specification". [6] TS 23.119: "Gateway Location Register () - stage2". 3 Abbreviations For the purposes of the present document, the following abbreviations apply: CCBS GPRS IM_GSN IM_MSC SGSN GGSN Completion of Call to Busy Subscriber Gateway Location Register General Packet Radio Service Intermediate GSN Intermediate MSC Serving GPRS support node Gateway GPRS support node
8 TS 29.120 V7.0.0 (2007-06) 4 The entities and interfaces within the mobile network utilising the 4.1 The entities of the mobile system The functional entities related to the are described below. The description of each entity is detailed in TS 23.119 ( stage2 specification). The other functional entities described in the present document (e.g. MSC, VLR, and HLR) are specified in TS 29.002. - The Gateway location Register (). - The Intermediate MSC (IM-MSC). - The Intermediate GSN (IM-GSN). 4.2 The Interfaces within the mobile services The Interfaces related to the are described below. The description of each interface is detailed in TS 23.119 ( stage2 specification). - Interface between the HLR and the. - Interface between the VLR and the. - Interface between the MSC and the IM_MSC. - Interface between the SGSN and the. - Interface between the MSC and the. - Interface between the and the IM_GSN. 5 Overload and compatibility overview 5.1 Overload control for MAP entities The VLR and SGSN see the as an HLR, and the HLR sees the as a VLR or a SGSN. Therefore the shall behave like mobile entity as which the is regarded. If overload of the is detected, the responder may ignore uests for certain MAP operations (see tables 5.1/1, 5.1/2 and 5.1/3 in 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 TS 29.002.
9 TS 29.120 V7.0.0 (2007-06) 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 TS 23.003 [1]. The specific SSN is not needed for the, 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 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 uired. The following entities are considered for the additionally: - the Gateway location Register (); - the Intermediate Mobile-services Switching Centre (IM_MSC); - the Intermediate GPRS Support Node (IM_GSN). 6.1.3.2 The Gateway Location Register () 6.1.3.2.1 Addressed by the VLR In the network utilising the, when an MS that belongs to other PLMN registers in a VLR/SGSN, the VLR/SGSN sees the as the MS s HLR. When initiating the update location dialogues, the VLR is able to address the based on the SPC of the because of intra-plmn signalling. And the VLR can address the 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 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 based on an E.164 address. 6.1.3.2.2 Addressed by the HLR When a location updating dialogue initiated by a has been successfully completed, the HLR sees the 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 using the VLR number.
10 TS 29.120 V7.0.0 (2007-06) 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, the GMSC sees the as the SGSN. When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See 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 using the SGSN number. 6.1.3.2.4 Addressed by the IM-GSN In the network utilising the, the IM-GSN initiates the GPRS location information retrieval to the. The IM-GSN must have the value of the 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. 6.1.3.3.2 Addressed by the GMLC When a location uest 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. 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 will alert the IM-GSN when the subscriber becomes reachable. The 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.
11 TS 29.120 V7.0.0 (2007-06) to from fixed network home location register visitor location register mobileservices switching centre fixed net work Table 6.1.3/1 HLR VLR MSC SGSN GGSN IM-MSC IM- GSN I:SPC/GT E:GT T:VLR NUMBER I:SPC/GT E:GT T:MGT (outside World Zone 1)/MSISDN (World Zone 1/)HLR NUMBER (note) E:GT T:SGSN NUMBER I:SPC/GT E:GT T:MSC NUMBER Serving GPRS Support Node Gateway GPRS Support Node Gateway Location register Intermedia te- MSC --- E:GT T:MGT (outside World Zone1)/MSISDN( World Zone1/) HLR NUMBER (note) I:SPC/G T T:VLR NUMBE R --- I:SPC/GT T:MSC NUMBER --- I:SPC/G T T:SGSN NUMBE R Note1 I:SPC/GT T:MGT/MSISDN/HL R 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 uest. This may be either the IMSI received as a parameter of the MAP message uesting the Roaming Number or the Calling Party Address associated with the MAP message uesting the Roaming Number. From VLR in, 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 TS29.002. 6.2 Use of TC Refer to the corresponding section in TS 29.002.
12 TS 29.120 V7.0.0 (2007-06) 7 General on MAP services Refer to the corresponding section in 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-2 service; - MAP-SECURE-TRANSPORT-CLASS-3 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 uest 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 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 uested user resource is unavailable due to congestion; - resource unavailable; the uested 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 uested application context is not supported;
13 TS 29.120 V7.0.0 (2007-06) - 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 uirements. 8 Mobility services 8.1 General Regarding definition of each service, only the interval for adoption shall be considered for the introduction. The interval for adoption for the specification is described below. Service primitives and parameter definitions are as in TS 29.002.
14 TS 29.120 V7.0.0 (2007-06) 8.2 Location Management services Services UPDATE_LOCATION CANCEL _LOCATION PURGE_MS UPDATE_GPRS_LOCATION Figure 8.2 /1 Interval for adoption VLR HLR HLR VLR SGSN VLR SGSN HLR SGSN HLR 8.3 Authentication Management services Services SEND_AUTHENTICATION_IN FO AUTHENTICATION_FAILURE _REPORT Figure 8.3/1 Interval for adoption VLR SGSN HLR VLR SGSN HLR 8.4 Subscriber management services Services INSERT-SUBSCRIBER-DATA MAP-DELETE-SUBSCRIBER-DATA Figure 8.4/1 Interval for adoption HLR VLR SGSN HLR VLR SGSN
15 TS 29.120 V7.0.0 (2007-06) 8.5 Fault recovery services Services RESET FORWARD_CHECK_SS_INDICA TION RESTORE_DATA Figure 8.5/1 Interval for adoption HLR VLR SGSN HLR VLR VLR 8.6 Subscriber Information services Services MAP-PROVIDE-SUBSCRIBER-Info Figure 8.6/1 Interval for adoption VLR HLR 9 Operation and maintenance services 9.1 General Regarding definition of each service, only the interval for adoption shall be considered for the introduction. The intervals for adoption for the specification are described below. Service primitives and parameter definitions are as in TS 29.002. 9.2 SEND_IMSI service Services SEND_IMSI Figure 9.2/1 Interval for adoption HLR VLR
16 TS 29.120 V7.0.0 (2007-06) 10 Call handling services 10.1 General Regarding definition of each service, only the interval for adoption shall be considered for the introduction. The intervals for adoption for the specification are described below. Service primitives and parameter definitions are as in TS 29.002. 10.2 PROVIDE_ROAMING_NUMBER service Services PROVIDE_ROAMING_NUMBER Figure 10.2/1 Interval for adoption HLR VLR 10.3 SET_REPORTING_STATE service Services SET_REPORTING_STATE Figure 10.3/1 Interval for adoption HLR VLR 10.4 STATUS_REPORT service Services STATUS_REPORT Figure 10.4/1 Interval for adoption VLR HLR 10.5 REMOTE_USER_FREE service Services REMOTE_USER_FREE Figure 10.5/1 Interval for adoption VLR HLR
17 TS 29.120 V7.0.0 (2007-06) 11 Supplementary services related services 11.1 General Regarding definition of each service, only the interval for adoption shall be considered for the introduction. The intervals for adoption for the specification are described below. Service primitives and parameter definitions are as in TS 29.002. 11.2 REGISTER_SS service Services REGISTER_SS Figure 11.2/1 Interval for adoption VLR HLR 11.3 ERASE_SS service Services ERASE_SS Figure 11.3/1 Interval for adoption VLR HLR 11.4 ACTIVATE_SS service Services ACTIVATE_SS Figure 11.4/1 interval for adoption VLR HLR 11.5 DEACTIVATE_SS service Services DEACTIVATE_SS Figure 11.5/1 Interval for adoption VLR HLR
18 TS 29.120 V7.0.0 (2007-06) 11.6 INTERROGATE _SS service Services INTERROGATE_SS Figure 11.6/1 Interval for adoption VLR HLR 11.7 REGISTER_PASSWORD service Services REGISTER_PASSWORD Figure 11.7/1 Interval for adoption VLR HLR 11.8 GET_PASSWORD service Services GET_PASSWORD Figure 11.8/1 Interval for adoption HLR VLR 11.9 PROCESS_UNSTRUCTURED_SS_REQUEST service Services PROCESS_UNSTRUCTURED_SS_REQUEST Figure 11.9/1 Interval for adoption VLR HLR
19 TS 29.120 V7.0.0 (2007-06) 11.10 UNSTRUCTURED_SS_REQUEST service Services UNSTRUCTURED_SS_REQUEST Figure 11.10/1 Interval for adoption HLR VLR 11.11 UNSTRUCTURED_SS_NOTIFY service Services UNSTRUCTURED_SS_NOTIFY Figure 11.11/1 Interval for adoption HLR VLR 11.12 REGISTER_CC_ENTRY service Services UNSTRUCTURED_SS_NOTIFY Figure 11.12/1 Interval for adoption VLR HLR 11.13 ERASE_CC_ENTRY service Services ERASE_CC_NOTIFY Figure 11.13/1 Interval for adoption VLR HLR 12 Short message service management services 12.1 General Regarding definition of each service, only the interval for adoption shall be considered for the introduction. The intervals for adoption for the specification are described below. Service primitives and parameter definitions are as in TS 29.002.
20 TS 29.120 V7.0.0 (2007-06) 12.2 MAP-READY-FOR-SM service Services MAP-READY-FOR-SM Figure 12.2/1 interval for adoption VLR SGSN HLR 12.3 MAP-MT-FORWARD-SHORT-MESSAGE service Services MT_FORWARD_SHORT_MESSAGE interval for adoption SMS-GMSC IM-MSC IM-MSC MSC SMS-GMSC 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 introduction. The intervals for adoption for the specification are described below. Service primitives and parameter definitions are as in TS 29.002. 13.2 SEND_ROUTING_INFO_FOR_GPRS service Services SEND_ROUTING_INFO_FOR_GPRS Interval for adoption IM-GSN Figure 13.2/1
21 TS 29.120 V7.0.0 (2007-06) 13.3 FAILURE_REPORT service Services FAILURE_REPORT Interval for adoption IM-GSN 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 TS 29.002002 with the exceptions described below. 15.1 SDL descriptions Replace the corresponding part of Process Secure_DSM as figure 15.1/1.
22 TS 29.120 V7.0.0 (2007-06) Process Secure_DSM_ 15.1.1(1) Process to manage a MAP dialogue DIALOGUE_ ACCEPTED REQ any MAP specific uest primitive rsp Any MAP specific response primitive DELIMITER_ Secure_ (TRUE) Transport_ uired (FALSE) Requesting_ SSM Secure_ Requesting_ SSM Secure_ Transport_ uired (FALSE) (TRUE) TC_ CONTINUE VIA_TC1 Service_ Invoked_ VIA_Intern2 Service_ Inv oked_ VIA_Intern4 Response_ Issued_ VIA_Imtern1 Response_ Issued_ VIA_Imtern3 DIALOGUE_ ESTABLISHED DIALOGUE_ ACCEPTED CLOSE_ re q U_ ABORT_ User-reason= AC-notsuppoeted no yes Abort-reason := User-specific Abort-reason := AC-notsupported User-info := MAP- UserAbortInfo TC_END_ VIA_TC1 TC_U_ ABORT VIA_TC1 (FALSE) Secure_ Transport_ uired (TRUE) Terminated_ VIA_Intern1 To all active PSSMs Terminated_ VIA_Intern3 To all active SPSSMs Terminated_ VIA_Intern2 To all active RSSMs Terminated_ VIA_Intern4 To all active SRSSMs IDLE IDLE Figure 15.1/1: Process Secure_DSM_ 16 Mapping onto TC services Dialogue control, Service specific procedures and SDL descriptions are referred to the corresponding section in TS 29.002.
23 TS 29.120 V7.0.0 (2007-06) 17 Abstract syntax of the MAP protocol 17.1 General Refer to the corresponding section in TS 29.002 except Packages specifications and Application contexts. Regarding the operations which are initiated by the VLR or SGSN toward HLR via, the timer value used in the operations should be configured enough long to guarantee the specific fallback mechanism. 17.2 Packages specifications Regarding Packages specifications, only the supplier and consumer definition shall be considered for the introduction. The supplier and consumer definition for the specification are derived Table 17.2/1. For the other definitions of the package specifications are as in TS 29.002. Table 17.2/1: supplier and consumer definition Operation Package supplier consumer LocationUpdatingPackage-v3 HLR VLR LocationCancellationPackage-v3 VLR or SGSN HLR RoamingNumberEnquiryPackage-v3 VLR HLR InfoRetrievalPackage-v2 HLR VLR SGSN InfoRetrievalPackage-v1 HLR VLR SGSN IMSIRetrievalPackage-v2 HLR VLR SubscriberDataMngtStandAlonePackage-v3 VLR or SGSN HLR SubscriberDataMngtPackage-v3 VLR or SGSN HLR ResetPackage-v2 VLR or SGSN HLR FunctionalSsPackage-v2 HLR HLR BindingPackage-v1 HLR VLR UnstructuredSsPackage-v2 HLR VLR UnstructuredSsPackage-v1 HLR VLR MTShortMsgRelayPackage-v3 IM-MSC or GMSC MSC IM-MSC SGSN MwdMngtPackage-v3 HLR SGSN VLR MwdMngtPackage-v1 HLR VLR DataRestorationPackage-v3 VLR PurgingPackage-v3 HLR VLR SGSN
24 TS 29.120 V7.0.0 (2007-06) Operation Package supplier consumer SubscriberInformationEnquiryPackage-v3 VLR HLR GprsLocationUpdatingPackage-v3 HLR SGSN FailureReportingPackage-v3 IM-GSN SetReportingStatePackage-v3 VLR HLR StatusReportPackage-v3 HLR VLR RemoteUserFreePackage-v3 VLR HLR CallCompletionPackage-v3 HLR VLR AuthenticationFailureReportPackage-v3 HLR VLR SGSN SecureTransportHandlingPackage-v3 This operation package includes the operations uired 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 introduction. The responder and initiator definition for the specification are derived Table 17.3/1. For the other definitions of the package specifications are as in TS 29.002.
25 TS 29.120 V7.0.0 (2007-06) Table 17.3/1: supplier and consumer definition Application Context Version Initiator Responder locationcancellationcontext v3 HLR VLR or SGSN imsiretrievalcontext v2 VLR HLR inforetrievalcontext v2 VLR or SGSN HLR mwdmngtcontext v3 VLR or SGSN HLR mspurgingcontext v3 VLR or SGSN HLR resetcontext v2 HLR VLR or SGSN networkunstructuredsscontext v2 VLR HLR HLR VLR networkfunctionalsscontext v2 VLR HLR shortmsgmt-relaycontext v3 MSC IM-MSC or IM-MSC MSC SGSN networklocupcontext v3 VLR HLR gprslocationupdatecontext v3 SGSN HLR subscriberdatamngtcontext v3 HLR VLR or SGSN roamingnumberenquirycontext v3 HLR VLR gprslocationinforetrievalcontext v3 IM-GSN failurereportcontext v3 IM-GSN subscriberinfoenquirycontext v3 HLR VLR reportingcontext v3 VLR HLR HLR VLR callcompletioncontext v3 VLR HLR authenticationfailurereportcontext v3 VLR or SGSN 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 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.
26 TS 29.120 V7.0.0 (2007-06) 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 interact with the processes in the VLR or HLR defined in 29.002. The followings show the relations between the protocol processes in the and the processes in the other node. Process Update Location (VLR-): - Initiator: Update_Location_Area_VLR or Update_Location_HLR; - Responder: Update_Location_. Process Update Location (-HLR): - Initiator: _Update_Location_HLR; - Responder: Update_Location_HLR. Process Cancel Location (VLR-): - Initiator: _Cancel_Location_VLR; - Responder: Cancel_Location_VLR. Process Cancel Location (-HLR): - Initiator: Cancel_Location_HLR; - Responder: Cancel_Location_. Process Purge MS (VLR-): - Initiator: Purge_MS_VLR; - Responder: Purge_MS_. Process Purge MS (-HLR): - Initiator: _Purge_MS_HLR; - Responder: Purge_MS_HLR. A Location Management Co-ordinator in the co-ordinates the two protocol processes Update_Location_ (subclause 19.1.2) and RESTORE_DATA_ (subclause 19.2) that are addressed by the same application context. On receipt of a dialogue uest for the Location Management Application Context, the location Management_Coordinator_ will: - Terminate the process in case of parameter problems; or - Revert to MAP version Vr protocol if the VLR uests 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_ if the primitive is a UPDATE_LOCATION indication. - RESTORE_DATA_ if the primitive is a RESTORE_DATA indication.
27 TS 29.120 V7.0.0 (2007-06) If a 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 uest 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_ 19.1.1.1(1) Location management coordination process in the Receive_ Open_Ind Section 25.1 '' 'Vr' 'Error' WAIT_FOR_ SERVICE_ PRIMITIVE 'Perform_ Vr_ Dialogue' UPDATE_ LOCATION_ Ind RESTORE_ DATA_Ind NOTICE_ Ind Update_ Location_ RESTORE_ DATA_ MAP- CLOSE_ Req UPDATE_ LOCATION_Ind RESTORE_ DATA_Ind RELAY_INFO * from Provider * from OFFSPRING MAP-U-ABORT_Req, MAP-CLOSE_Req from OFFSPRING MAP-P-ABORT_Ind, MAP-U-ABORT_Ind, MAP-CLOSE_Ind - to OFFSPRING - to Provider - to Provider - to OFFSPRING RELAY_INFO RELAY_INFO Figure 19.1.1/1: Process Location_Management_Coordinator_
28 TS 29.120 V7.0.0 (2007-06) 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 interact with the processes in the VLR, SGSN or HLR defined in 29.002. The followings show the relations between the processes in the and the processes in the other node: Process GPRS Update Location (VLR or SGSN-): Initiator: GPRS_Update_Location_Area_VLR, or SGSN_Update_HLR. Responder: Update_GPRS_Location_. Process GPRS Update Location (-HLR): Initiator: _Update_GPRS_Location_HLR. Responder: Update_GPRS_Location_HLR. Process Cancel Location (SGSN-): Initiator: _Cancel_Location_SGSN. Responder: Cancel_Location_SGSN. Process Cancel Location (-HLR): Initiator: Cancel_GPRS_Location_HLR. Responder: Cancel_GPRS_Location_. Process Purge MS (SGSN-): Initiator: Purge_MS_SGSN. Responder: Purge_MS for_gprs. Process Purge MS (-HLR): Initiator: _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 is located between the VLR and the HLR, the UPDATE_LOCATION service is invoked towards the whose identity is contained in the VLR table. When the receives a UPDATE_LOCATION indication, it determines whether it invokes the UPDATE_LOCATION service towards the HLR, and invokes it if necessary. If the is located between the SGSN and the HLR, the UPDATE_GPRS_LOCATION service is invoked towards the whose identity is contained in the SGSN table. When the receives a UPDATE_GPRS_LOCATION indication, it determines whether it invokes the UPDATE_GPRS_LOCATION service towards the HLR, and invokes it if necessary.
29 TS 29.120 V7.0.0 (2007-06) +----+ +----+ +----+ +-----+ VLR/ P/ SGSN+-----+---------- -------+--------- HLR +-------+--------- PVLR/ PSGSN +----+ +----+ +----+ +-----+ MAP UPDATE_LOCATION --------------------> or MAP UPDATE GPRS MAP UPDATE_LOCATION CANCEL_ LOCATION --------------------> ---------------------> or MAP UPDATE GPRS LOCATION LOCATION 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 Figure 19.1.2/2 shows the Process Update_Location_. This process is a MAP prorocol machine handling location updating and is a responder to the VLR.
30 TS 29.120 V7.0.0 (2007-06) Process Update_Location_ MAP protocol machine handling location updating and interfaceing with VLR MAP protocol machine Left to VLR Right to application 19.1.2.2_1(3) WAIT_FOR_ SERVICE_ PRIMITIVE Update_ Location_ind Update Location 2 WAIT_FOR_ APPLICATION_ RESPONSE Update Location Ack Update Location Negative Response Insert_ Subscriber_ Data Forward check SS indication Abort Set result Set Error 1 UPDATE_ LOCATION_Rsp. CLOSE_Req. UPDATE_ LOCATION_Rsp. CLOSE_Req. WAIT_FOR_ APPLICATION_ RESPONSE U_ ABORT_ FORWARD_ CHECK_SS_INDICATION_ DELIMITER_ Figure 19.1.2/2 (sheet 1 of 3): Process Update_Location_
31 TS 29.120 V7.0.0 (2007-06) Process Update_Location_ MAP protocol machine handling location updating and interfaceing with VLR MAP protocol machine 1 Insert_Subscriber_Data_Req Delimiter_Req 19.1.2.2_2(3) Left to VLR Right to application WAIT_FOR_ISD_Cnf_ WAIT_FOR_SUBSEQUENT_ APPLICATION_RESPONSE Insert_Subscriber_ Data_Cnf U_ABORT_Ind P_ABORT_Ind CLOSE_Ind NOTICE_ Ind Abort Set Negative Result System Failure ISD Negative Response Check Confirmation Section 25.2 2 Provider error Data error User error Insert_Subscriber_ Data_Cnf Set Negative Response System Failure MAP User Error to Negative Response 2 ISD Negative Response 2 Figure 19.1.2/2 (sheet 2 of 3): Process Update_Location_
32 TS 29.120 V7.0.0 (2007-06) Process Update_Location_ 19.1.2.2_3(3) MAP protocol machine handling location updating and interfaceing with VLR MAP protocol machine Left to VLR Right to application WAIT_FOR_ISD_Cnf_ WAIT_FOR_SUBSEQUENT_ APPLICATION_RESPONSE Update Location Ack Update Location Negative Response Insert Subscriber Data Abort Set result Set Error 1 U_ ABORT_Req. UPDATE_ LOCATION_Rsp. CLOSE_Req. Figure 19.1.2/2 (sheet 3 of 3): Process Update_Location_
33 TS 29.120 V7.0.0 (2007-06) Figure 19.1.2/3 shows the Process _Update_Location_HLR. This process is a 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 uests to perform MAP Vr. It causes a uest for sending an abort message to Process Update_Location_. Process _Update_Location_HLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. 19.1.2.3_1(3) Signals to/from the left are to/from the application. Signals to/from the right are to/from the HLR MAP protocol machine. IDLE Update Location OPEN_Req UPDATE_LOCATION_Req DELIMITER_Req Receive Open Cnf. Vr Section 25.1 Error Wait_For_HLR_ Response Perform MAP Vr Set error Update Location Negative Response Figure 19.1.2/3 (Sheet 1 of 3): Process _Update_Location_HLR
34 TS 29.120 V7.0.0 (2007-06) Process _Update_Location_HLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. Wait_For_HLR_ Response Signals to/from the left are to/from the application. Signals to/from the right are to/from the HLR MAP protocol machine. 19.1.2.3_2(3) FORWARD_ Check_SS_ind INSERT_ SUBSCRIBER_ DATA_ind Notice_ Indication U_Abort_ind P_Abort_ind Close_ind Forward Check SS Indication Insert Subscriber data Close_ uest Abort Set negative response Update Location negative response Wait_For_HLR_or_ Application_ Response Update_ Location_cnf Section 25.2 Check Confirmation Update Location ack Provider Error, User Error, Data Error Set negative response Update Location negative response Figure 19.1.2/3 (Sheet 2 of 3): Process _Update_Location_HLR
35 TS 29.120 V7.0.0 (2007-06) Process _Update_Location_HLR 19.1.2.3_3(3) MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. Wait_For_HLR_or_ Application Response Signals to/from the left are to/from the application. Signals to/from the right are to/from the HLR MAP protocol machine. FORWARD_ Check_SS_ind INSERT_ SUBSCRIBER_ DATA_ind Forward Check SS Indication Insert Subscriber data Insert Subscriber Data ack Insert Subscriber Data negative response Set user error Insert_ Subscriber_Data_ response Wait_For_HLR_or_ Application_ Response Update_ Location_cnf Section 25.2 Abort Notice_ Indication U_Abort_ind P_Abort_ind Close_ind Check Confirmation Provider Error, User Error, Data Error Map_U_Abort_ uest Close_ uest Abort Update Location ack Set negative response Set negative response Update Location negative response Update Location negative response Figure 19.1.2/3 (Sheet 3 of 3): Process _Update_Location_HLR
36 TS 29.120 V7.0.0 (2007-06) Figure 19.1.2/4 shows the Process Update_GPRS_Location_. This process is a MAP protocol machine handling location updating and is a responder to the SGSN. Process Update_GPRS_Location_ 19.1.2.4_1(3) MAP protocol machine handling location updating and interfaceing with SGSN MAP protocol machine Left to SGSN Right to application WAIT_FOR_SERVICE_ PRIMITIVE Receive Open Ind. V2 V1 Error Update_ GPRS_Location_ ind Perform_ Vr_Dialogue Update GPRS Location 2 WAIT_FOR_ APPLICATION_ RESPONSE Update GPRS Location Ack Update GPRS Location Negative Response Insert Subscriber Data Abort Set result Set error 1 UPDATE_GPRS_ LOCATION_Rsp. CLOSE_Req. UPDATE_GPRS_ LOCATION_Rsp. CLOSE_Req. U_ ABORT_ Figure 19.1.2/4 (sheet 1 of 3): Process Update_GPRS_Location_
37 TS 29.120 V7.0.0 (2007-06) Process Update_GPRS_Location_ 19.1.2.4_2(3) MAP protocol machine handling location updating and interfaceing with SGSN MAP protocol machine 1 Left to SGSN Right to application 3 WAIT_FOR_ISD_Cnf_ WAIT_FOR_SUBSEQUENT_ APPLICATION_RESPONSE Insert_Subscriber_Data_Req Delimiter_Req Insert_Subscriber_ Data_Cnf U_ABORT_Ind P_ABORT_Ind CLOSE_Ind NOTICE_ Ind Abort Set Negative Result System Failure ISD Negative Response Check Confirmation Section 25.2 3 Provider error Data error User error Insert_Subscriber_ Data_Cnf Set Negative Response System Failure MAP User Error to Negative Response 2 ISD Negative Response 2 Figure 19.1.2/4 (sheet 2 of 3): Process Update_GPRS_Location_
38 TS 29.120 V7.0.0 (2007-06) Process Update_GPRS_Location_ 19.1.2.4_3(3) MAP protocol machine handling location updating and interfaceing with SGSN MAP protocol machine Left to SGSN Right to application WAIT_FOR_ISD_Cnf_ WAIT_FOR_SUBSEQUENT_ APPLICATION_RESPONSE Update Location Ack Update GPRS Location Negative Response Insert Subscriber Data Abort Set result Set Error 1 U_ ABORT_ UPDATE_ LOCATION_Rsp. CLOSE_Req. Figure 19.1.2/4 (sheet 3 of 3): Process Update_GPRS_Location_
39 TS 29.120 V7.0.0 (2007-06) Figure 19.1.2/5 shows the Process _Update_GPRS_Location_HLR. This process is a 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 uests to perform MAP Vr. It causes a uest for sending an abort message to Process Update_GPRS_Location_. Process _Update_GPRS_Location_HLR 19.1.2.5_1(3) MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. Signals to/from the left are to/from the application. Signals to/from the right are to/from the HLR MAP protocol machine. IDLE Update GPRS Location OPEN_Req UPDATE_GPRS_LOCATION_Req DELIMITER_Req Receive Open Cnf. Vr Section 25.1 Error Wait_For_HLR_ Response Perform MAP Vr Set error Update GPRS Location Negative Response Figure 19.1.2/5 (Sheet 1 of 3): Process _Update_GPRS_Location_HLR
40 TS 29.120 V7.0.0 (2007-06) Process _Update_GPRS_Location_HLR 19.1.2.5_2(3) MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. Signals to/from the left are to/from the application. Wait_For_HLR_ Response Signals to/from the right are to/from the HLR MAP protocol machine. Update_GPRS_ Location_cnf INSERT_ SUBSCRIBER_ DATA_ind Notice_ Indication U_Abort_ind P_Abort_ind Close_ind Check Confirmation Section 25.2 Insert Subscriber Data Close_ uest Abort Provider Error, User Error, Data Error Set negative response Update GPRS Location ack Set negative response Wait_For_HLR_or_ Application_ Response Update GPRS Location negative response Update GPRS Location negative response Figure 19.1.2/5 (Sheet 2 of 3): Process _Update_GPRS_Location_HLR
41 TS 29.120 V7.0.0 (2007-06) Process _Update_GPRS_Location_HLR 19.1.2.5_3(3) MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. Wait_For_HLR_or_ Application Response INSERT_ SUBSCRIBER_ DATA_ind Signals to/from the left are to/from the application. Signals to/from the right are to/from the HLR MAP protocol machine. Insert Subscriber Data Insert Subscriber Data ack Insert Subscriber Data negative response Set user error Insert_ Subscriber_Data_ response Wait_For_HLR_or_ Application_ Response Update_GPRS_ Location_cnf Section 25.2 Abort Notice_ Indication U_Abort_ind P_Abort_ind Close_ind Check Confirmation Provider Error, User Error, Data Error Map_U_Abort_ uest Close_ uest Abort Update GPRS Location ack Set negative response Set negative response Update GPRS Location negative response Update GPRS Location negative response Figure 19.1.2/5 (Sheet 3 of 3): Process _Update_GPRS_Location_HLR
42 TS 29.120 V7.0.0 (2007-06) 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 /VLR/SGSN after she has registered with a new /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 is located between the VLR or the SGSN and the HLR, the CANCEL_LOCATION service is invoked towards the whose identity is contained in the HLR table. +----+ +----+ +----+ +----+ VLR/ D D D +-----+---------- HLR -------+--------- P+-------+--------- PVLR +----+ +----+ +----+ +----+ MAP UPDATE_LOCATION --------------------> CANCEL_ CANCEL_ --------------------> ---------------------> LOCATION LOCATION CANCEL_LOCATION 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 +------+------- HLR -------+--------- P+-------+--------- PSGSN +-----+ +----+ +----+ +-----+ UPDATE_GPRS_LOCATION -----------------------> CANCEL_ CANCEL_ --------------------> ---------------------> LOCATION LOCATION CANCEL_LOCATION 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 CANCEL_LOCATION service is invoked when the that stores the subscriber s record receives a UPDATE_LOCATION indication from a VLR other than that stored in its table for this subscriber. Also the CANCEL_LOCATION service is invoked when the that stores the subscriber s record a UPDATE_GPRS_LOCATION indication from a SGSN other than stored in its table for this subscriber. The CANCEL_LOCATION service is in any case invoked towards the VLR or the SGSN whose identity is contained in the HLR table.
43 TS 29.120 V7.0.0 (2007-06) +----+ D +----+ D +-----+ VLR/+-----------+------------+ +-------+--------+PVLR/ SGSN PSGSN +----+ +----+ +-----+ UPDATE_LOCATION or UPDATE_GPRS_LOCATION ----------------------------> CANCEL_ ---------------------> LOCATION CANCEL_LOCATION <--------------------- ack Figure 19.1.3/4: Interface and services for Location Cancellation in case that the stores the subscriber s record 19.1.2.2 Detailed procedure in the Figure 19.1.3/5 shows the Process Cancel_Location_. This process is a MAP protocol machine handling location cancellation and is a responder to the HLR.
44 TS 29.120 V7.0.0 (2007-06) Process Cancel_Location_ 19.1.3.5(1) MAP protocol machine handling Location cancelation and interfacing to HLR MAP protocol machine, handling Location Cancelation. Signals to/from the left are to/from the Location cancellation application. Signals to/from the right are to/from the HLR MAP protocol machine, handling Location Cancellation. Receive Open Ind. WAIT_FOR_SERVICE_ PRIMITIVE V2 V1 Error CANCEL_ LOCATION_ind NOTICE_ind Perform_ Vr_Dialogue CLOSE_ Cancel Location WAIT_FOR_ APPLICATION_ RESPONSE Cancel Location Ack Cancel Location Negative response Abort CANCEL_LOCATION_Rsp. CLOSE_Req. U_ABORT_ Figure 19.1.3/5: Process Cancel_Location_