TS 129 120 V3.0.0 (2000-03) Technical Specification Universal Mobile Telecommunications System (UMTS); Mobile Application Part (MAP) specification for Gateway Location Register (); Stage 3 (3G TS 29.120 version 3.0.0 Release 1999)
3G TS 29.120 version 3.0.0 Release 1999 1 TS 129 120 V3.0.0 (2000-03) Reference DTS/TSGN-0229120U Keywords UMTS 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.:+33492944200 Fax:+33493654716 Siret N 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on printers of the PDF version kept on a specific network drive within Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other documents is available at http://www.etsi.org/tb/status/ If you find errors in the present document, send your comment to: editor@etsi.fr 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. European Telecommunications Standards Institute 2000. All rights reserved.
3G TS 29.120 version 3.0.0 Release 1999 2 TS 129 120 V3.0.0 (2000-03) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to. The information pertaining to these essential IPRs, if any, is publicly available for members and non-members, and can be found in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to in respect of standards", which is available from the Secretariat. Latest updates are available on the Web server (http://www.etsi.org/ipr). Pursuant to the IPR Policy, no investigation, including IPR searches, has been carried out by. No guarantee can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by the 3 rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding deliverables. The cross reference between GSM, UMTS, 3GPP and identities can be found under www.etsi.org/key.
3 TS 129 120 V3.0.0 (2000-03) Contents Foreword... 7 1 Scope... 8 2 References... 8 3 Abbreviations... 8 4 The entities and interfaces within the mobile network utilising the... 9 4.1 The entities of the mobile system... 9 4.2 The Interfaces within the mobile services... 9 5 Overload and compatibility overview... 9 5.1 Overload control for MAP entities... 9 5.2 Compatibility... 9 6 Requirements concerning the use of SCCP and TC... 10 6.1 Use of SCCP... 10 6.1.1 SCCP Class... 10 6.1.2 Sub-System Number (SSN)... 10 6.1.3 SCCP addressing... 10 6.1.3.1 Introduction... 10 6.1.3.2 The Gateway Location Register ()... 10 6.1.3.2.1 Addressed by the VLR... 10 6.1.3.2.2 Addressed by the HLR... 10 6.1.3.2.3 Addressed by the GMSC... 11 6.1.3.2.4 Addressed by the IM-GSN... 11 6.1.3.3 The Intermediate MSC (IM_MSC)... 11 6.1.3.3.1 Addressed by the GMSC... 11 6.1.3.3.2 Addressed by the GMLC... 11 6.1.3.4 The Intermediate GSN (IM_GSN)... 11 6.1.3.5 Summary table... 11 6.2 Use of TC... 12 7 General on MAP services... 13 7.1 Common MAP services... 13 7.1.1 MAP-U-ABORT service... 13 8 Mobility services... 14 8.1 General... 14 8.2 Location Management services... 14 8.3 Authentication Management services... 14 8.4 Subscriber management services... 15 8.5 Fault recovery services... 15 8.6 Subscriber Information services... 15 9 Operation and maintenance services... 15 9.1 General... 15 9.2 SEND_IMSI service... 15 10 Call handling services... 16 10.1 General... 16 10.2 PROVIDE_ROAMING_NUMBER service... 16 10.3 SET_REPORTING_STATE service... 16 10.4 STATUS_REPORT service... 16 10.5 REMOTE_USER_FREE service... 16 11 Supplementary services related services... 17 11.1 General... 17 11.2 REGISTER_SS service... 17 11.3 ERASE_SS service... 17
4 TS 129 120 V3.0.0 (2000-03) 11.4 ACTIVATE_SS service... 17 11.5 DEACTIVATE_SS service... 17 11.6 INTERROGATE _SS service... 17 11.7 REGISTER_PASSWORD service... 18 11.8 GET_PASSWORD service... 18 11.9 PROCESS_UNSTRUCTURED_SS_REQUEST service... 18 11.10 UNSTRUCTURED_SS_REQUEST service...18 11.11 UNSTRUCTURED_SS_NOTIFY service... 18 11.12 REGISTER_CC_ENTRY service... 18 11.13 ERASE_CC_ENTRY service... 19 12 Short message service management services... 19 12.1 General... 19 12.2 MAP-READY-FOR-SM service... 19 12.3 MAP-MT-FORWARD-SHORT-MESSAGE service... 19 13 Network-Requested PDP Context Activation services... 19 13.1 General... 19 13.2 SEND_ROUTING_INFO_FOR_GPRS service... 19 13.3 FAILURE_REPORT service... 20 14 Void... 20 15 Element of procedure... 20 16 Mapping onto TC services... 20 16.1 SDL descriptions... 20 17 Abstract syntax of the MAP protocol... 21 17.1 General... 21 17.2 Packages specifications... 21 17.3 Application contexts... 23 18 General on MAP user procedure... 23 19 Mobility procedures... 24 19.1 Location management Procedures... 24 19.1.1 Location updating... 26 19.1.1.1 General... 26 19.1.1.2 Detailed procedure in the... 27 19.1.2 Location Cancellation... 40 19.1.2.1 General... 40 19.1.2.2 Detailed procedure in the... 42 19.1.3 Purge MS... 46 19.1.3.1 General... 46 19.1.3.2 Detailed procedure in... 47 19.2 Fault recovery procedures... 51 19.2.1 RESET procedure... 51 19.2.1.1 HLR failure case... 51 19.2.1.2 failure case... 51 19.2.1.3 Detailed procedure in... 51 19.2.2 VLR restoration: the restore data procedure in the... 55 19.2.2.1 General... 55 19.2.2.2 Detailed procedure in... 55 20 Operations and maintenance procedures... 62 20.1 General... 62 20.2 Subscriber data management procedures... 62 20.2.1 General... 62 20.2.2 Procedures in the... 64 20.2.2.1 Subscriber deletion procedure... 64 20.2.2.2 Subscriber data modification procedure... 64 20.3 Subscriber Identity procedure... 74 20.3.1 Subscriber identity procedure in the... 76
5 TS 129 120 V3.0.0 (2000-03) 21 Call handling procedures... 78 21.1 General... 78 21.2 Retrieval of routing information... 79 21.2.1 General... 79 21.2.2 Process in the to provide a roaming number... 80 21.2.3 Process in the to provide subscriber information... 83 21.3 Setting of Reporting State... 86 21.3.1 General... 86 21.3.2 Process in the to set the reporting state... 86 21.4 Status Reporting... 88 21.4.1 General... 88 21.4.2 Process in the for Status Reporting... 89 21.5 Remote User Free... 91 21.5.1 General... 91 21.5.2 Process in the for Remote User Free... 92 22 Supplementary services procedures... 95 22.1 Functional supplementary service processes... 95 22.1.1 Functional supplementary service process co-ordinator for... 95 22.1.2 Call completion supplementary service process co-ordinator for... 98 22.2 Registration procedure... 99 22.2.1 General... 99 22.2.2 Procedures in the... 100 22.3 Erasure procedure... 102 22.3.1 General... 102 22.3.2 Procedures in the... 103 22.4 Activation procedure... 103 22.4.1 General... 103 22.4.2 Procedures in the... 103 22.5 Deactivation procedure... 105 22.5.1 General... 105 22.5.2 Procedures in the... 106 22.6 Interrogation procedure... 106 22.6.1 General... 106 22.6.2 Procedures in the... 106 22.7 Password registration procedure... 106 22.7.1 General... 106 22.7.2 Procedures in the... 106 22.8 Mobile Initiated USSD procedure... 106 22.8.1 Procedures in the... 106 22.9 Network initiated USSD procedure... 110 22.9.1 Procedure in the... 110 22.10 Common macros for clause 22... 114 22.10.1 SS Password handling macros... 114 22.11 Activation of a CCBS uest... 115 22.11.1 General... 115 22.11.2 Procedure in the... 115 22.12 Deactivation of a CCBS uest... 118 22.12.1 General... 118 22.12.2 Procedure in the... 118 23 Short message service procedures... 121 23.1 General... 121 23.2 The mobile terminated short message transfer procedure... 121 23.2.1 Procedure in the Intermediate MSC... 121 23.2.2 Procedure in the... 127 23.3 The Short Message Alert procedure... 133 23.3.1 Procedures in the... 134 24 GPRS process description... 136 24.1 General... 136 24.2 Send Routing Information procedure... 136 24.2.1 Process in the for Send Routing Information for GPRS... 136
6 TS 129 120 V3.0.0 (2000-03) 24.2.2 Process in the IM-GSN for Send Routing Information for GPRS... 137 24.3 Failure Report procedure... 140 24.3.1 Process in the for Failure Report... 140 24.3.2 Process in the IM-GSN for Failure Report... 142 25 General macro description... 144 25.1 MAP open macros... 144 25.2 Macros to check the content of indication and confirmation primitives... 144 25.3 Authentication processes... 144 25.3.1 Process Obtain_Authentication_Sets_... 144 25.4 Short Message Alert procedures... 147 25.4.1 Subscriber_Present AS_VLR process... 147 25.4.2 The Mobile Subscriber is present... 148 History... 149
7 TS 129 120 V3.0.0 (2000-03) Foreword This Technical Specification (TS) has been produced by the 3 rd Generation Partnership Project (3GPP). 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 3GPP system. (i.e. the present document specifies the delta against 3G 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 z the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. the third digit is incremented when editorial only changes have been incorporated in the document.
8 TS 129 120 V3.0.0 (2000-03) 1 Scope The present document describes the signalling uirements and procedures used at network elements related to the 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 as the delta document against 3G 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] 3G TS 23.003: "Numbering, addressing and identification". [2] 3G TS 23.007: "Restoration procedures". [3] 3G TS 23.012: "Location registration procedures". [4] 3G TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". [5] 3G TS 29.002: "Mobile Application Part (MAP) specification". [6] 3G 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
9 TS 129 120 V3.0.0 (2000-03) 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 3G TS 23.119 ( stage2 specification). The other functional entities described in the present document (e.g. MSC, VLR, and HLR) are specified in 3G 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 3G 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 3G 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 3G TS 29.002.
10 TS 129 120 V3.0.0 (2000-03) 6 Requirements concerning the use of SCCP and TC 6.1 Use of SCCP The Mobile Application Part makes use of the services offered by the Signalling Connection Control Part of signalling System No. 7. CCITT Blue Book or ITU-T (03/93) Recommendations Q.711 to Q.716 should be consulted for the full specification of SCCP. In North America (World Zone 1) the national version of SCCP is used as specified in ANSI T1.112. 6.1.1 SCCP Class MAP will only make use of the connectionless classes (0 or 1) of the SCCP. 6.1.2 Sub-System Number (SSN) The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are addressed by sub-system numbers (SSNs). The SSN for MAP are specified in 3G 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 3G 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.
11 TS 129 120 V3.0.0 (2000-03) 6.1.3.2.3 Addressed by the GMSC In the case that the MS is served by the SGSN in the network utilising the, the GMSC sees the as the SGSN. When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See 3G 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.
12 TS 129 120 V3.0.0 (2000-03) 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 Intermedia te- GSN NOTE 0: NOTE1: --- E:GT T:MGT (outside World Zone1)/MSISDN( World Zone1/) HLR NUMBER (note) I:SPC/G T T:VLR NUMBE R --- I:SPC/G T T:SGSN NUMBE R Note1 I:SPC/GT T:MGT/MSISDN/HL R NUMBER --- I:SPC/GT T:MSC NUMBER --- I:SPC/GT T:HLR NUMBER I: Intra-PLMN E: Extra (Inter)-PLMN T: Address Type GT: Global Title MGT: E.214 Mobile Global Title SPC: Signalling Point Code 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. The hatching part is the same part of 3G TS29.002. 6.2 Use of TC Refer to the corresponding section in 3G TS 29.002.
13 TS 129 120 V3.0.0 (2000-03) 7 General on MAP services Refer to the corresponding section in 3G TS 29.002 with the exceptions described below. 7.1 Common MAP services 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; - 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:
14 TS 129 120 V3.0.0 (2000-03) 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 3G TS 29.002. 8.2 Location Management services Services UPDATE_LOCATION CANCEL _LOCATION PURGE_MS UPDATE_GPRS_LOCATION Interval for adoption VLR HLR HLR VLR SGSN VLR SGSN HLR SGSN HLR Figure 8.2 /1 8.3 Authentication Management services Services SEND_AUTHENTICATION_INFO Interval for adoption VLR SGSN HLR Figure 8.3/1
15 TS 129 120 V3.0.0 (2000-03) 8.4 Subscriber management services Services INSERT-SUBSCRIBER-DATA MAP-DELETE-SUBSCRIBER-DATA Interval for adoption HLR VLR SGSN HLR VLR SGSN Figure 8.4/1 8.5 Fault recovery services Services RESET FORWARD_CHECK_SS_INDICATIO N RESTORE_DATA Interval for adoption HLR VLR SGSN HLR VLR VLR Figure 8.5/1 8.6 Subscriber Information services Services MAP-PROVIDE-SUBSCRIBER-Info Interval for adoption VLR 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 introduction. The intervals for adoption for the specification are described below. Service primitives and parameter definitions are as in 3G TS 29.002. 9.2 SEND_IMSI service Services SEND_IMSI Interval for adoption HLR VLR Figure 9.2/1
16 TS 129 120 V3.0.0 (2000-03) 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 3G TS 29.002. 10.2 PROVIDE_ROAMING_NUMBER service Services PROVIDE_ROAMING_NUMBER Interval for adoption HLR VLR Figure 10.2/1 10.3 SET_REPORTING_STATE service Services SET_REPORTING_STATE Interval for adoption HLR VLR Figure 10.3/1 10.4 STATUS_REPORT service Services STATUS_REPORT Interval for adoption VLR HLR Figure 10.4/1 10.5 REMOTE_USER_FREE service Services REMOTE_USER_FREE Interval for adoption VLR HLR Figure 10.5/1
17 TS 129 120 V3.0.0 (2000-03) 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 3G TS 29.002. 11.2 REGISTER_SS service Services REGISTER_SS Interval for adoption VLR HLR Figure 11.2/1 11.3 ERASE_SS service Services ERASE_SS Interval for adoption VLR HLR Figure 11.3/1 11.4 ACTIVATE_SS service Services ACTIVATE_SS interval for adoption VLR HLR Figure 11.4/1 11.5 DEACTIVATE_SS service Services DEACTIVATE_SS Interval for adoption VLR HLR Figure 11.5/1 11.6 INTERROGATE _SS service Services INTERROGATE_SS Interval for adoption VLR HLR Figure 11.6/1
18 TS 129 120 V3.0.0 (2000-03) 11.7 REGISTER_PASSWORD service Services REGISTER_PASSWORD Interval for adoption VLR HLR Figure 11.7/1 11.8 GET_PASSWORD service Services GET_PASSWORD Interval for adoption HLR VLR Figure 11.8/1 11.9 PROCESS_UNSTRUCTURED_SS_REQUEST service Services PROCESS_UNSTRUCTURED_SS_REQUEST Interval for adoption VLR HLR Figure 11.9/1 11.10 UNSTRUCTURED_SS_REQUEST service Services UNSTRUCTURED_SS_REQUEST Interval for adoption HLR VLR Figure 11.10/1 11.11 UNSTRUCTURED_SS_NOTIFY service Services UNSTRUCTURED_SS_NOTIFY Interval for adoption HLR VLR Figure 11.11/1 11.12 REGISTER_CC_ENTRY service Services UNSTRUCTURED_SS_NOTIFY Interval for adoption VLR HLR Figure 11.12/1
19 TS 129 120 V3.0.0 (2000-03) 11.13 ERASE_CC_ENTRY service Services ERASE_CC_NOTIFY Interval for adoption VLR 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 introduction. The intervals for adoption for the specification are described below. Service primitives and parameter definitions are as in 3G TS 29.002. 12.2 MAP-READY-FOR-SM service Services MAP-READY-FOR-SM interval for adoption VLR SGSN HLR Figure 12.2/1 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 3G 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
20 TS 129 120 V3.0.0 (2000-03) 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 3G TS 29.002. 16 Mapping onto TC services Dialogue control, Service specific procedures and SDL descriptions are referred to the corresponding section in 3G TS 29.002 with the exceptions described below. 16.1 SDL descriptions Replace the corresponding part of DSM as figure 16.1/1. Process DSM_ 16.1.1(1) Figure 16.1/1 DIALOGUE_ ACCEPTED REQ RSP CLOSE_ REQ DELIMITER_ REQ U_ ABORT_ REQ REQUESTING_ SSM any MAP specific uest primitive User-reason= AC-notsuppoeted no yes SERVICE_ INVED_VIA_ INTERN2 RESPONSE_ ISSUED_VIA_ INTERN1 TC_END_REQ VIA_TC1 TC_ Abort-reason := CONTINUE_ User-specific REQ_VIA_TC1 Abort-reason := AC-notsupported DIALOGUE_ ACCEPTED DIALOGUE_ ACCEPTED 1 DIALOGUE_ ESTABLISHED User-info := MAP- UserAbortInfo any MAP specific uest primitive TC_U_ ABORT_REQ_ VIA_TC1 1 Figure 16.1/1: Process DSM_
21 TS 129 120 V3.0.0 (2000-03) 17 Abstract syntax of the MAP protocol 17.1 General Refer to the corresponding section in 3G 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 3G TS 29.002.
22 TS 129 120 V3.0.0 (2000-03) 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 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
23 TS 129 120 V3.0.0 (2000-03) 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 3G TS 29.002. 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 callcompletioncomtext v3 VLR HLR 18 General on MAP user procedure Refer to 3G 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.
24 TS 129 120 V3.0.0 (2000-03) 19 Mobility procedures 19.1 Location management Procedures For non-gprs subscribers, this subclause comprises a number of processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP SSN (VLR or HLR) and the Application Context. The processes in the 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.
25 TS 129 120 V3.0.0 (2000-03) 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_
26 TS 129 120 V3.0.0 (2000-03) For GPRS subscribers, this subclause comprises a number of other processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP Sub-System Number (SGSN or HLR) and the Application Context. The processes in the 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.
27 TS 129 120 V3.0.0 (2000-03) 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.
28 TS 129 120 V3.0.0 (2000-03) 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_
29 TS 129 120 V3.0.0 (2000-03) 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_
30 TS 129 120 V3.0.0 (2000-03) 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_
31 TS 129 120 V3.0.0 (2000-03) 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
32 TS 129 120 V3.0.0 (2000-03) 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
33 TS 129 120 V3.0.0 (2000-03) 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
34 TS 129 120 V3.0.0 (2000-03) 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_
35 TS 129 120 V3.0.0 (2000-03) 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_
36 TS 129 120 V3.0.0 (2000-03) 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_
37 TS 129 120 V3.0.0 (2000-03) 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
38 TS 129 120 V3.0.0 (2000-03) 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
39 TS 129 120 V3.0.0 (2000-03) 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
40 TS 129 120 V3.0.0 (2000-03) 19.1.2 Location Cancellation 19.1.2.1 General The purpose of this process is to delete a subscriber's record from a previous /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. 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 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.
41 TS 129 120 V3.0.0 (2000-03) Figure 19.1.3/4: Interface and services for Location Cancellation in case that the stores the subscriber's record
42 TS 129 120 V3.0.0 (2000-03) 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. 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_
43 TS 129 120 V3.0.0 (2000-03) Figure 19.1.3/6 shows the Process _Cancel_Location_VLR. This process is a MAP protocol machine handling location cancellation and is an initiator to the VLR. 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 Cancel_Location_. Process _Cancel_Location_VLR 19.1.3.6(1) MAP protocol machine handling cancel location and interfacing with VLR MAP protocol machine VLR to the Left Application to the Right IDLE Cancel Location OPEN_Req CANCEL_LOCATION_Req DELIMITER_Req WAIT_FOR_ ACK Receive Open Cnf. Vr Perform MAP Vr Error Cancel Location Negative Response CANCEL_ LOCATION_Cnf P_ ABORT_Ind NOTICE_ Ind Check_ Confirmation Cancel Location Ack Error Cancel Location Negative Response Cancel Location Negative Response CLOSE_ Req Cancel Location Negative Response Figure 19.1.3/6: Process _Cancel_Location_VLR
44 TS 129 120 V3.0.0 (2000-03) Figure 19.1.3/7 shows the Process Cancel_GPRS_Location_. This process is a MAP protocol machine handling location cancellation and is a responder to the HLR. Process Cancel_GPRS_Location_ 19.1.3.7(1) MAP protocol machine handling Location cancelation and interfacing to HLR MAP protocol machine, handling Location Cancelation. Receive Open Ind. Signals to/from the right are to/from the Location cancellation application. Signals to/from the left are to/from the HLR MAP protocol machine, handling Location Cancellation. V2 V1 Error WAIT_FOR_SERVICE_ PRIMITIVE CANCEL_ LOCATION_ind NOTICE_ind Perform_ Vr_Dialogue Cancel Location CLOSE_ WAIT_FOR_ APPLICATION_ RESPONSE Cancel Location Ack Cancel Location Negative Response Abort CANCEL_LOCATION_Rsp. CLOSE_Req. U_ABORT_ Figure 19.1.3/7: Process Cancel_GPRS_Location_