hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 2.4.2 Invocation of Barring | ................................................................................................................................. 12 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 2.4.3 Operator Determined Barring of access to supplementary service not supported in VLR | ......................... 14 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 2.5 Interactions of Operator Determined Barring with Supplementary Services | ................................................... 14 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 2.5.1 Call Forwarding | ......................................................................................................................................... 14 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 2.5.2 Closed User Group | ..................................................................................................................................... 15 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 2.5.3 Call Barring | ................................................................................................................................................ 16 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 3 Information stored in location registers | .................................................................................................16 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 3.1 Information stored in the HLR | ......................................................................................................................... 16 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 3.2 Information stored in the VLR | ......................................................................................................................... 17 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 3.3 Information stored in the SGSN | ...................................................................................................................... 18 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 3.4 Transfer of Subscription Information from HLR to VLR | ................................................................................ 18 |
bc33b2e39df9a1ee69d546541c2c34f1 | 123 015 | 3.5 Transfer of Subscription Information from HLR to SGSN | .............................................................................. 19 Annex A: Change history......................................................................................................................20 History..............................................................................................................................................................21 (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 4 3G TS 23.015 version 3.1.0 Foreword This Technical Specification has been produced by the 3GPP. This TS describes the network feature Operator Determined Barring which allows a network operator or service provider to regulate access by subscribers to services within the 3GPP system. 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 this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 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 specification; (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 5 3G TS 23.015 version 3.1.0 1 Scope The network feature Operator Determined Barring (ODB) allows a network operator or service provider to regulate access by subscribers to GSM services, by the barring of certain categories of incoming or outgoing traffic or of roaming. Operator Determined Barring applies to all bearer services and teleservices except the Emergency Call teleservice; the teleservice Short Message Point-to-Point is therefore subject to Operator Determined Barring in the same way as circuit-switched calls. The application of specific categories of Operator Determined Barring to a subscription is controlled by the network operator or service provider, using administrative interaction at the HLR; this interface is not standardised. 1.1 Normative references References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.41: "Digital cellular telecommunications system (Phase 2+); Operator determined barring". [3] GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point-to-Point (PP)". 1.2 Definitions and abbreviations Abbreviations used in this specification are listed in GSM 01.04. 2 Method of realisation The GSM entities which control the application of Operator Determined Barring (ODB), and the methods used, are described in this clause. Two cases are considered for each type of barring: the effect of administrative action in the HLR to modify the application of the category to a particular subscription, and the effect of the category on the handling of calls or other traffic involving the subscriber. 2.1 Barring of Outgoing Calls or Mobile Originated Short Messages Barring of outgoing calls or mobile originated short messages includes the categories "outgoing calls" and "outgoing premium rate calls" defined in GSM 02.41, and the "operator specific barring" category where this is defined by the PLMN operator to apply to outgoing calls or mobile originated short messages. (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 6 3G TS 23.015 version 3.1.0 2.1.1 Application or Change of Barring in the HLR If barring of outgoing calls or mobile originated short messages is applied to a subscription (or existing barring of outgoing calls or mobile originated short messages is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and transfer the updated subscription information to the VLR and the SGSN using one or more Insert Subscriber Data operations, as shown in figure 1. If operator specific barring is applied to a subscription (or existing operator specific barring is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. If the mobile subscriber is registered in the home PLMN, the HLR will transfer the updated subscription information to the VLR and the SGSN using one or more Insert Subscriber Data operations, as shown in figure 1. If the VPLMN does not support Operator Determined Barring of outgoing calls, the VLR and the SGSN shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HLR shall then, as an operator option, apply the Outgoing Calls Barred supplementary service, apply barring of roaming as described in subclause 2.3 or take any other action decided by the operator of the HPLMN. MS MSC VLR or SGSN HLR ODB of outgoing calls applied, modified or removed Insert Subscriber <----------- data Figure 1: Transfer of updated subscription information to VLR or SGSN 2.1.2 Invocation of Barring Barring of outgoing calls or mobile originated short messages is invoked in the VLR. If the VLR receives a request for subscription information for an outgoing call or mobile originated short message which is prohibited by Operator Determined Barring, the VLR will return a negative response to the request for subscription information, with an appropriate error indication. The MSC may relay this error indication via the BSS to the mobile station over the radio path, or (in the case of an outgoing call) may connect the mobile station to an address to be determined by the network operator. Barring of mobile originated short messages is invoked in the SGSN. If the SGSN receives a request for a mobile originated short message which is prohibited by Operator Determined Barring, the SGSN will return a negative response to the request with an appropriate error indication via the BSS to the mobile station over the radio path. Barring of all international calls, barring of all international calls except those directed to the home PLMN country, barring of all premium rate (information) calls or barring of all premium rate (entertainment) calls requires the VLR or the SGSN to analyse the called number to determine whether the requested call is barred. Barring of all outgoing calls when roaming outside the home PLMN country requires the HLR to determine whether a request for location updating originates from a PLMN outside the home PLMN country. If the request does originate from a PLMN outside the home PLMN country, the HLR will transfer subscription information to the requesting node to indicate that the mobile station is subject to barring of all outgoing calls. Operator Specific Barring may apply to outgoing or incoming calls, or mobile originated or mobile terminated short messages; if it applies to outgoing calls or mobile originated short messages, it is invoked in the VLR or the SGSN, as described above. If the barring applies to calls directed to a specific class of destination, the called number must be analysed to determine whether the requested call is barred. Indicative message flow diagrams for the handling of Operator Determined Barring of outgoing calls or mobile originated short messages are given in figures 2a and 2b. For the case where the mobile station is connected to an address determined by the network operator, this address is assumed to be directly connected to the MSC, so that no inter-MSC signalling is required. (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 7 3G TS 23.015 version 3.1.0 MS MSC VLR Outgoing call or MO SMS request barred because of ODB O/G Request -----------------> Send Info for ----------------> O/G Call Reject <---------------- (cause) Operator option: error indication returned to MS Reject <----------------- (Cause) Figure 2a: Operator Determined Barring of Outgoing Calls or Mobile Originated Short Messages invocation in the VLR MS SGSN MO SMS request barred because of ODB MO Short -----------------> Message Error indication returned to MS Reject <----------------- (cause) Figure 2b: Operator Determined Barring of Mobile Originated Short Messages invocation in the SGSN (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 8 3G TS 23.015 version 3.1.0 2.2 Barring of Incoming Calls or Mobile Terminated Short Messages 2.2.1 Application or Change of Barring in the HLR If barring of incoming calls or mobile terminated short messages is applied to a subscription (or existing barring of incoming calls or mobile terminated short messages is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. It is not necessary to transfer the updated subscription information to the VLR or the SGSN. 2.2.2 Invocation of Barring Barring of incoming calls is invoked in the HLR. If the HLR receives a request for routing information for a call directed to a mobile station which is subject to barring of incoming calls, the HLR will return a negative response to the request for routing information, with an appropriate error indication. The Gateway MSC may relay this error indication to the originating network using the appropriate telephony signalling system, or may connect the call to a recorded announcement to be determined by the network operator. Barring of mobile terminated short messages is invoked in the HLR. If the HLR receives a request for routing information for a short message directed to a mobile station which is subject to barring of incoming calls, the HLR will return a negative response to the request for routing information, with an appropriate error indication. This error indication will be relayed to the originating Short Message service centre by the Gateway MSC using the protocol defined in GSM 03.40. Operator Specific Barring may apply to outgoing or incoming calls, or mobile originated or mobile terminated short messages; if it applies to incoming calls or mobile terminated short messages, it is invoked in the HLR, as described above. An indicative message flow diagram for the handling of Operator Determined Barring of incoming calls is given in figure 3. For the case where the call is connected to an address determined by the network operator, this address is assumed to be directly connected to the GMSC, so that no inter-MSC signalling is required. HLR GMSC N/W Incoming call request barred because of ODB Incoming call <--------------- (address) Send routing <---------------- info request Reject ----------------> (cause) Operator option: error indication returned to network Reject ---------------> (cause) Figure 3: Operator Determined Barring of Incoming Calls (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 9 3G TS 23.015 version 3.1.0 (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 10 3G TS 23.015 version 3.1.0 An indicative message flow diagram for the handling of Operator Determined Barring of mobile terminated short messages is given in figure 4. HLR SMS GMSC SMS SC MT short message request barred because of ODB MT short <--------------- message Send routing info for SM <---------------- request Reject ----------------> (cause) Reject ---------------> (cause) Figure 4: Operator Determined Barring of Mobile Terminated Short Messages 2.3 Barring of Roaming 2.3.1 Application or Change of Barring in the HLR If barring of roaming is applied to a subscription (or modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. If the HLR determines from the identity of the VLR and/or the SGSN that the mobile subscriber is currently registered in a barred PLMN, the HLR will put the barring into effect by using a Cancel Location operation to the VLR and/or the SGSN, as shown in figure 5. If the mobile subscriber is not currently registered in a barred PLMN, the HLR will take no further action. MS MSC VLR or SGSN HLR ODB of roaming applied Cancel <----------- location Figure 5: Immediate Application of Barring of Roaming 2.3.2 Invocation of Barring Barring of roaming is invoked in the HLR. If the HLR receives a request from a VLR for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HLR will reject the location updating request with an appropriate error indication and this error indication will be relayed by the MSC and the BSS to the mobile station over the radio path. If the HLR receives a request from a SGSN for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HLR will reject the location updating request with an appropriate error indication and this error indication will be relayed by the SGSN and the BSS to the mobile station over the radio path. (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 11 3G TS 23.015 version 3.1.0 Indicative message flow diagrams for the handling of Operator Determined Barring of roaming are given in figures 6a and 6b. MS MSC VLR HLR Roaming barred because of ODB LR request -------------> Location update ----------------> request Update Location -----------> request Reject <----------- (cause) Reject <---------------- (cause) Reject <------------- (cause) Figure 6a: Operator Determined Barring of Roaming invocation in HLR. Roaming in a prohibited VLR MS SGSN HLR Roaming barred because of ODB LR request -------------> GPRS Update Location ----------------> request Reject <---------------- (cause) Reject <------------- (cause) Figure 6b: Operator Determined Barring of Roaming invocation in HLR. Roaming in a prohibited SGSN (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 12 3G TS 23.015 version 3.1.0 2.4 Barring of Supplementary Services Access Barring of supplementary services access encompasses the general barring of supplementary services management category specified in GSM 02.41 and the specific categories of barring of registration of a call forwarded-to number and barring of invocation of call transfer. 2.4.1 Application or Change of Barring in the HLR If barring of supplementary services access is applied to a subscription (or existing barring of supplementary services access is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and, if necessary, transfer the updated subscription information to the VLR using one or more Insert Subscriber Data operations, as shown in figure 1. If the VPLMN does not support Operator Determined Barring of supplementary service access, the VLR shall indicate this in the acknowledgement to the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in subclause 2.3 or take any other action decided by the operator of the HPLMN. 2.4.2 Invocation of Barring Barring of supplementary services access is invoked in the HLR or the VLR, depending on the supplementary service operation. Barring of access to the following supplementary service operations is invoked in the HLR: - registration; - erasure; - activation; - deactivation; - password registration; - processing unstructured SS data. An indicative message flow diagram for the handling in the HLR of Operator Determined Barring of access to supplementary services is given in figure 7. (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 13 3G TS 23.015 version 3.1.0 MS MSC VLR HLR Access to Supplementary Services barred because of ODB SS request -------------> SS activity ----------------> request SS activity -----------> request Reject <----------- (cause) Reject <---------------- (cause) Reject <------------- (cause) Figure 7: Operator Determined Barring of Access to Supplementary Services in the HLR NOTE 1: Although the HLR handles interrogation of some supplementary services, Operator Determined Barring of interrogation of all supplementary services is invoked in the VLR. This reduces the amount of analysis which the VLR must perform on supplementary service requests before deciding whether to relay a supplementary service request to the HLR or reject it because of Operator Determined Barring of access to supplementary services. Operator Determined Barring of control of PLMN specific supplementary services is invoked in the VLR for the same reason. NOTE 2: Although the VLR handles some processing of unstructured SS data, and therefore has to check for Operator Determined Barring of access to supplementary services, a check is also specified in the HLR to guard against the case where the VLR does not support Operator Determined Barring of access to supplementary services. Barring of access to the following supplementary service operations is invoked in the VLR: - interrogation; - invocation; - control of PLMN specific supplementary services; - processing unstructured SS data. An indicative message flow diagram for the handling in the VLR of Operator Determined Barring of access to supplementary services is given in figure 8. (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 14 3G TS 23.015 version 3.1.0 MS MSC VLR Access to Supplementary Services barred because of ODB SS request -------------> SS activity ----------------> request Reject <---------------- (cause) Reject <----------------- (Cause) Figure 8: Operator Determined Barring of Access to Supplementary Services in the VLR 2.4.3 Operator Determined Barring of access to supplementary service not supported in VLR If the VLR does not support Operator Determined Barring of access to supplementary services the HLR shall take the following actions: The VLR supports only phase 1: If the HLR receives a request which should normally be barred by the VLR the HLR shall reject the request with the appropriate phase 1 error (illegal SS operation or system failure). The VLR supports phase 2 but does not support this Operator Determined Barring category: If the HLR receives a request which should normally be barred by the VLR the HLR shall reject the request instead of the VLR. Note that requests handled locally by the VLR (e.g. interrogation) will not be barred. 2.5 Interactions of Operator Determined Barring with Supplementary Services The following interactions of Operator Determined Barring with supplementary services have been identified: 2.5.1 Call Forwarding The interactions between Operator Determined Barring and Call Forwarding are specified in GSM 02.41. The interaction where Operator Determined Barring is applied when there is an existing Call Forwarding programme which is in contravention of the Operator Determined Barring programme is shown in the message flow diagram in figure 9. The HLR modifies the subscription information for the mobile subscriber to show that the contravening call forwarding programme is quiescent, and forwards the modified subscription information to the VLR. No indication is forwarded to the mobile station or the user. (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 15 3G TS 23.015 version 3.1.0 MS MSC VLR HLR ODB applied when Call Forwarding programme contravenes ODB Insert Subscriber <----------- data Figure 9: Effect of Operator Determined Barring on Call Forwarding programme The interaction where the user attempts to activate or register a call forwarding programme which is in contravention of an operator determined barring category is shown in the message flow diagram in figure 10. MS MSC VLR HLR Request for Call Forwarding programme contravening ODB SS request (register or -------------> activate CF) SS activity ----------------> request SS activity -----------> request Reject <----------- (cause) Reject <---------------- (cause) Operator option: error indication returned to MS Reject <------------- (cause) Figure 10: Interaction between Operator Determined Barring and Call Forwarding 2.5.2 Closed User Group The interaction between Operator Determined Barring and Closed User Group is specified in GSM 02.41. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for Closed User Group. (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 16 3G TS 23.015 version 3.1.0 2.5.3 Call Barring The interaction between Operator Determined Barring and the Call Barring supplementary service is specified in GSM 02.41. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for the Call Barring supplementary service. 3 Information stored in location registers 3.1 Information stored in the HLR The HLR must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other: Barring of outgoing calls (including mobile originated short messages) - one of: - Barring of all outgoing calls; - Barring of all outgoing international calls; - Barring of all outgoing international calls except those directed to the home PLMN country; - Barring of all outgoing calls when roaming outside the home PLMN country; - Barring of all outgoing inter-zonal calls; - Barring of all outgoing inter-zonal calls except those directed to the home PLMN country; - Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls. Barring of incoming calls (including mobile terminated short messages) - one of: - Barring of all incoming calls; - Barring of all incoming calls when roaming outside the home PLMN country; - Barring of all incoming calls when roaming outside the zone of the home PLMN country. Barring of roaming - one of: - Barring of roaming outside the home PLMN; - Barring of roaming outside the home PLMN country. Barring of outgoing premium rate calls - one or both of: - Barring of outgoing premium rate (information) calls; - Barring of outgoing premium rate (entertainment) calls. Barring specific to the home PLMN - when the mobile station is registered in its home PLMN, any one or more of: - Operator Specific Barring (Type 1); - Operator Specific Barring (Type 2); - Operator Specific Barring (Type 3); - Operator Specific Barring (Type 4). Barring of Supplementary Services Management. Barring of registration of call forwarding - one of: (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 17 3G TS 23.015 version 3.1.0 - Barring of registration of any forwarded-to number; - Barring of registration of any international forwarded-to number; - Barring of registration of any international forwarded-to number except a number within the HPLMN country; - Barring of registration of any inter-zonal forwarded-to number; - Barring of registration of any inter-zonal forwarded-to number except a number within the HPLMN country. Barring of invocation of call transfer: one of: - Barring of invocation of any call transfer; - Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber; - Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country; - Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN; and independently: - Barring of invocation of call transfer where both calls are calls charged to the served subscriber; and independently: - Barring of invocation of call transfer when there is an existing transferred call for the served subscriber in the same MSC/VLR. 3.2 Information stored in the VLR The VLR must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other: Barring of outgoing calls (including mobile originated short messages) - one of: - Barring of all outgoing calls; - Barring of all outgoing international calls; - Barring of all outgoing international calls except those directed to the home PLMN country; - Barring of all outgoing inter-zonal calls; - Barring of all outgoing inter-zonal calls except those directed to the home PLMN country; - Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls. Barring of outgoing premium rate calls - one or both of: - Barring of outgoing premium rate (information) calls; - Barring of outgoing premium rate (entertainment) calls. Barring specific to the home PLMN - when the mobile station is registered in its home PLMN, any one or more of: - Operator Specific Barring (Type 1); - Operator Specific Barring (Type 2); (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 18 3G TS 23.015 version 3.1.0 - Operator Specific Barring (Type 3); - Operator Specific Barring (Type 4). Barring of Supplementary Services Management. Barring of invocation of call transfer: one of: - Barring of invocation of any call transfer; - Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber; - Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country; - Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN. and independently: - Barring of invocation of call transfer where both calls are calls charged to the served subscriber; and independently: - Barring of invocation of call transfer when there is an existing transferred call for the served subscriber in the same MSC/VLR. 3.3 Information stored in the SGSN The SGSN must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other: Barring of mobile originated short messages - one of: - Barring of all outgoing calls; - Barring of all outgoing international calls; - Barring of all outgoing international calls except those directed to the home PLMN country; - Barring of all outgoing inter-zonal calls; - Barring of all outgoing inter-zonal calls except those directed to the home PLMN country; - Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls. Barring specific to the home PLMN of mobile originated short messages - when the mobile station is registered in its home PLMN, any one or more of: - Operator Specific Barring (Type 1); - Operator Specific Barring (Type 2); - Operator Specific Barring (Type 3); - Operator Specific Barring (Type 4). 3.4 Transfer of Subscription Information from HLR to VLR The following subscription information for Operator Determined Barring must be transferred from the HLR to the VLR when a mobile station registers in a VLR: - Barring of outgoing calls; (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 19 3G TS 23.015 version 3.1.0 - Barring of outgoing premium rate calls; - Barring of supplementary services management; - Barring of invocation of call transfer. In addition, when a mobile station registers in a VLR in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN must be transferred from the HLR to the VLR. The following subscription information for Operator Determined Barring must be transferred from the HLR to the SGSN when a mobile station registers in a SGSN: - Barring of outgoing calls (which leads to barring of mobile originated short messages). In addition, when a mobile station registers in a SGSN in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN must be transferred from the HLR to the SGSN. (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 3GPP 3G TS 23.015 V3.1.0 (1999-09) 20 3G TS 23.015 version 3.1.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 03.15 6.0.0 Transferred to 3GPP CN1 CN#03 23.015 3.0.0 Approved at CN#03 CN#04 23.015 3.0.0 001 3.1.0 Corrections to text to introduce barring of SMS calls for GPRS (3G TS 23.015 version 3.1.0 Release 1999) ETSI TS 123 015 V3.1.0 (2000-01) ETSI 21 ETSI ETSI TS 123 015 V3.1.0 (2000-01) (3G TS 23.015 version 3.1.0 Release 1999) History Document history V3.1.0 January 2000 Publication |
148fa1179989b1c16824d457a74e1069 | 123 012 | 1 Scope | ........................................................................................................................................................6 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 1.1 References | .......................................................................................................................................................... 6 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 1.2 Abbreviations | ..................................................................................................................................................... 7 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 2 Definitions | ...............................................................................................................................................7 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 2.1 Location management | ........................................................................................................................................ 7 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 2.2 Location area and MSC area | .............................................................................................................................. 7 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 2.3 Location area identification | ............................................................................................................................... 7 2.4 IMSI detach/attach operation............................................................................................................................. 7 2.4.1 Explicit IMSI detach/attach.......................................................................................................................... 7 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 2.4.2 Implicit IMSI detach | .................................................................................................................................... 7 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 2.5 Use of the term mobile station (MS) in the present docum | ent........................................................................... 8 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3 General procedures in the network related to Location Mana | gement .....................................................8 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.1 Procedures in the MSC related to Location Updating | ....................................................................................... 8 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.2 Procedures in the VLR related to Location Updating | ........................................................................................ 8 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.3 Procedures in the HLR related to Location Updating | ........................................................................................ 8 3.4 Normal Location Updating and IMSI detach/attach operation .......................................................................... 8 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.5 IMSI enquiry procedure | ..................................................................................................................................... 8 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.6 Information transfer between Visitor and Home Location R | egisters................................................................. 8 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.6.1 Procedures for location management | ........................................................................................................... 8 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.6.1.1 Location updating procedure | .................................................................................................................. 9 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.6.1.2 Downloading of subscriber parameters to the VLR | ............................................................................... 9 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.6.1.3 Location cancellation procedure | ............................................................................................................. 9 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 3.6.1.4 Mobile subscriber purging procedure | ..................................................................................................... 9 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4 Detailed Procedures in the network related to Location Man | agement ....................................................9 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1 Location Updating | ........................................................................................................................................... 10 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.1 Detailed procedure in the MSC | .................................................................................................................. 10 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.1.1 Process Update_Location_Area_MSC | ................................................................................................. 10 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.1.2 Procedure Authenticate_MSC | .............................................................................................................. 14 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2 Detailed procedure in the VLR | .................................................................................................................. 15 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2.1 Process Update_Location_Area_VLR | .................................................................................................. 15 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2.2 Procedure Authenticate_VLR | ............................................................................................................... 20 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2.3 Procedure Location_Update_Completion_VLR | ................................................................................... 22 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2.4 Process Update_HLR_VLR | ................................................................................................................. 25 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2.5 Process Insert_Subs_Data_VLR | ........................................................................................................... 26 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2.6 Process Activate_Tracing_VLR | ........................................................................................................... 27 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2.7 Process Send_Identification_PVLR | ..................................................................................................... 28 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.2.8 Process Trace_Subscriber_Activity_VLR | ............................................................................................ 29 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.3 Detailed procedure in the HLR | .................................................................................................................. 30 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.3.1 Process Update_Location_HLR | ........................................................................................................... 30 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.3.2 Procedure Insert_Subscriber_Data_HLR | ............................................................................................. 34 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.3.3 Process Subscriber_Present_HLR | ........................................................................................................ 36 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.1.3.4 Procedure Control_Tracing_HLR | ........................................................................................................ 37 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.2 Location Cancellation | ...................................................................................................................................... 38 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.2.1 Detailed procedure in the VLR | .................................................................................................................. 38 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.2.1.1 Process Cancel_Location_VLR | ............................................................................................................ 38 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.2.2 Detailed procedure in the HLR | .................................................................................................................. 39 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.2.2.1 Process Cancel_Location_HLR | ............................................................................................................ 39 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.3 Detach IMSI | ..................................................................................................................................................... 40 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.3.1 Detailed procedure in the MSC | .................................................................................................................. 40 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.3.1.1 Process Detach_IMSI_MSC | ................................................................................................................. 40 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.3.2 Detailed procedure in the VLR | .................................................................................................................. 41 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.3.2.1 Process Detach_IMSI_VLR | ................................................................................................................. 41 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.4 Purge MS | ......................................................................................................................................................... 43 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.4.1 Detailed procedure in the VLR | .................................................................................................................. 43 ETSI ETSI TS 123 012 V3.3.0 (2000-06) 4 3G TS 23.012 version 3.3.0 Release 1999 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.4.1.1 Procedure Purge_MS_VLR | .................................................................................................................. 43 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.4.2 Detailed procedure in the HLR | .................................................................................................................. 45 |
148fa1179989b1c16824d457a74e1069 | 123 012 | 4.4.2.1 Procedure Purge_MS_HLR | .................................................................................................................. 45 Annex A (informative): Change history...............................................................................................47 ETSI ETSI TS 123 012 V3.3.0 (2000-06) 5 3G TS 23.012 version 3.3.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document defines the location management procedures within the 3GPP system. 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. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 6 3G TS 23.012 version 3.3.0 Release 1999 1 Scope The present document describes the location management procedures for the circuit switched domain, with respect to the application level functional behaviour. This is to be distinguished from the corresponding protocol handling behaviour, which is specified in 3G TS 29.002. The following location management procedures are included: - location updating; - location cancellation; - MS purging; - IMSI attach/detach. The procedures in the Mobile Station (MS) are described in GSM 03.22. The procedures between MSC, VLR and HLR utilise the Mobile Application Part (MAP) and details concerning the protocol handling are contained in 3G TS 29.002. The present document excludes location management procedures for the packet switched domain, which are covered in 3G TS 23.060. The descriptions herein depict a logical separation between the MSC and VLR. This logical separation, as well as the messages transferred between the two logical entities are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which a may be a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour. 1.1 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. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] 3G TR 21.905: "3G Vocabulary". [2] 3G TS 23.002: "Network architecture". [3] 3G TS 23.003: "Numbering, addressing and identification". [4] 3G TS 23.007: "Restoration procedures". [5] 3G TS 23.008: "Organization of subscriber data". [6] 3G TS 23.022: "Functions related to Mobile Station (MS) in idle mode". [7] 3G TS 23.116: "Super-Charger Technical Realisation; Stage 2". [8] 3G TS 29.002: "Mobile Application Part (MAP) specification". [9] 3G TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". [10] GSM 03.20: "Digital cellular telecommunication system (Phase 2+); Security related network functions". ETSI ETSI TS 123 012 V3.3.0 (2000-06) 7 3G TS 23.012 version 3.3.0 Release 1999 [11] 3G TS 23.078: "CAMEL phase3 – stage2 " 1.2 Abbreviations Abbreviations are listed in 3G TR 21.905. 2 Definitions 2.1 Location management Location management means that the PLMNs keep track of where the MSs are located in the system area. The location information for each MS is stored in functional units called location registers. Functionally, there are two types of location registers: - the Home Location Register where all subscriber parameters of an MS are permanently stored, and where the current location may be stored; - the Visitor Location Register where all relevant data concerning an MS are stored as long as the station is within the area controlled by that visitor location register. See also GSM 03.02 where the network architecture is described, and GSM 03.08 where the data stored in the location registers are described. The action taken by a MS in order to provide location information to the PLMN will be referred to as location updating. 2.2 Location area and MSC area The MSC area is composed of the area covered by all base stations controlled by the MSC. An MSC area may consist of several location areas. A location area is an area in which, after having performed a location update once, MSs may roam without being required to perform subsequent location updates for reason of location change. A location area consists of one or more cells. For further details of the network architecture, see GSM 03.02. 2.3 Location area identification The Location Area Identification (LAI) plan is part of the base station identification plan. The base stations are identified uniquely (see GSM 03.03). 2.4 IMSI detach/attach operation The support of IMSI detach/attach operation is mandatory in MSs. The facility is optional in the fixed infrastructure of the PLMN. 2.4.1 Explicit IMSI detach/attach Explicit IMSI detach operation is the action taken by an MS to indicate to the PLMN that the station has entered an inactive state (e.g. the station is powered down). Explicit IMSI attach operation is the action taken by an MS to indicate that the station has re-entered an active state (e.g. the station is powered up). 2.4.2 Implicit IMSI detach Implicit IMSI detach operation is the action taken by the VLR to mark an MS as detached when there has been no successful contact between the MS and the network for a time determined by the implicit detach timer. The value of the implicit detach timer is derived from the periodic location updating timer. During an established radio contact, the ETSI ETSI TS 123 012 V3.3.0 (2000-06) 8 3G TS 23.012 version 3.3.0 Release 1999 implicit detach timer shall be prevented from triggering implicit detach. At the release of the radio connection, the implicit detach timer shall be reset and restarted. Implicit IMSI detach shall also be performed in the case of a negative response to an IMEI check. 2.5 Use of the term mobile station (MS) in the present document In order to simplify the text the term Mobile Station (MS) as used in relation to location management refers to the entity where the IMSI is stored, i.e., in card operated MSs the term Mobile Station (MS) refers to the card. 3 General procedures in the network related to Location Management 3.1 Procedures in the MSC related to Location Updating The MSC shall pass messages related to location updating between the MS and the VLR. 3.2 Procedures in the VLR related to Location Updating FFS 3.3 Procedures in the HLR related to Location Updating FFS 3.4 Normal Location Updating and IMSI detach/attach operation When receiving a Location Updating Request or an IMSI detach/attach message from an MS, the MSC shall convey the message to its associated Visitor Location Register. Any response from the location register shall similarly be conveyed to the MS. 3.5 IMSI enquiry procedure The MS shall identify itself by either the IMSI or the TMSI plus Location Area Identification of the previous VLR. In the latter case the new VLR shall attempt to request the IMSI and authentication parameters from the previous VLR by the methods defined in GSM 09.02. If this procedure fails, or if the TMSI is not allocated, the VLR shall request that the MS identifies itself by use of the IMSI. 3.6 Information transfer between Visitor and Home Location Registers 3.6.1 Procedures for location management Detailed procedures for exchange of and location updating information between visitor and home location registers are given in GSM 09.02. Below follows an overview of these procedures. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 9 3G TS 23.012 version 3.3.0 Release 1999 3.6.1.1 Location updating procedure This procedure is used when an MS registers with a Visitor Location Register. The VLR provides its address to the HLR. The VLR may also allocate an optional identity for the MS at location updating: the Local Mobile Station Identity (see GSM 03.03). 3.6.1.2 Downloading of subscriber parameters to the VLR As a part of the location updating procedure, the Home Location Register will convey the subscriber parameters of the MS which need to be known by the visitor location register for proper call handling. This procedure is also used whenever there is a change in the subscriber parameters that need to be conveyed to the VLR (e.g. change in subscription, a change in supplementary services activation status). If the HPLMN applies the multinumbering option, different MSISDNs are allocated for different Basic Services (see GSM 09.07) and stored in the HLR. Among these MSISDNs, the Basic MSISDN Indicator as part of the HLR subscriber data (see GSM 03.08) marks the 'Basic MSISDN' to be sent to the VLR at location update. It is used in the VLR for call handling as calling party and as line identity. 3.6.1.3 Location cancellation procedure The procedure is used by the home location register to remove a MS from a visitor location register. The procedure will normally be used when the MS has moved to an area controlled by a different location register. The procedure can also be used in other cases, e.g. an MS ceases to be a subscriber of the Home PLMN. 3.6.1.4 Mobile subscriber purging procedure A VLR may purge the subscriber data for an MS which has not established radio contact for a period determined by the network operator. Purging means to delete the subscriber data and to "freeze" the TMSI that has been allocated to the purged MS in order to avoid double TMSI allocation. The VLR shall inform the HLR of the purging. When the HLR is informed of the purging, it shall set the flag "MS purged" in the IMSI record of the MS concerned. Presence of the "MS purged" flag will cause any request for routing information for a call or short message to the MS to be treated as if the MS were not reachable. In the VLR, the "frozen" TMSI is freed for usage in the TMSI allocation procedure by location updating for the purged MS in the same VLR, location cancellation for the purged MS or, in exceptional cases, by O&M. In the HLR, the "MS purged" flag is reset by the location updating procedure and after reload of data from the non- volatile back-up that is performed when the HLR restarts after a failure. 4 Detailed Procedures in the network related to Location Management The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. This specification shows the location management application processes interworking with the MAP protocol handler, which is specified in 3G TS 29.002. The MAP protocol defines supervision timers. If a supervision timer expires before a distant entity responds to a signal, the handling is as defined in 3G TS 29.002. In general, the protocol handler reports timer expiry to the application as an error condition or negative response. Where a timer is shown in this specification, therefore, it is an application timer rather than a protocol timer. Interworking with the protocol handlers uses functional signal names which do not necessarily have a one-to-one correspondence with the names of messages used in the MAP protocols. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 10 3G TS 23.012 version 3.3.0 Release 1999 4.1 Location Updating 4.1.1 Detailed procedure in the MSC 4.1.1.1 Process Update_Location_Area_MSC Sheet 1: Location Update corresponds to a Location_Registration_Request indicating any of the following: - Normal location update; - Periodic location update; - IMSI attach. Sheet 2: When the MSC receives a Set Ciphering Mode request from the VLR, it sends a Start ciphering request towards the MS. After that, the Forward new TMSI and Update Location Area ack may be received in any order. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 11 3G TS 23.012 version 3.3.0 Release 1999 Process in the MSC to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_MSC 1(3) Signals to/from the left are to/from the BSS Signals to/from the right are to/from the VLR Idle Location Update Update Location Area Wait_for_Location_ Updating_result Update Location Area ack Location Update ack Idle Update Location Area negative reponse Location Update reject Idle Trace Subscriber Activity 'Start active tracing' Wait_for_Location_ Updating_result Check IMEI Check_IMEI_ MSC See TS 23.018 Result= Pass? Idle Provide IMSI Obtain_IMSI_ MSC Authenticate Authenticate_ MSC Set Ciphering Mode 1 2 Yes No Figure 4.1.1.1 (sheet 1 of 3): Process Update_Location_Area_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 12 3G TS 23.012 version 3.3.0 Release 1999 Process in the MSC to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_MSC 2(3) Signals to/from the left are to/from the BSS Signals to/from the right are to/from the VLR Wait_for_Location_ Updating_result Forward check SS Check SS Wait_for_Location_ Updating_result MM release Abort Idle Figure 4.1.1.1 (sheet 2 of 3): Process Update_Location_Area_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 13 3G TS 23.012 version 3.3.0 Release 1999 Process in the MSC handle an incoming Location Update Req Process Update_Location_Area_MSC 3(3) Signals to/from the left are to/from the BSS Signals to/from the right are to/from the VLR 1 Cipher Command Wait_for_TMSI New TMSI Save TMSI Continue_to_Wait_ for_Location_ Updating_result Update Location Area ack Location Update ack Including new LAI and new TMSI Wait_for_TMSI_ Acknowledge_ from_MS New TMSI accepted Forward new TMSI ack Release Transaction Idle New TMSI rejected Forward new TMSI negative response Update Location Area negative response 2 Check IMEI Check_IMEI_MSC Result=Pass? Wait_for_TMSI Forward check SS Check SS MM release Abort Idle Update Location Area negative response 2 Update Location Area ack From VLR No Yes Figure 4.1.1.1 (sheet 3 of 3): Process Update_Location_Area_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 14 3G TS 23.012 version 3.3.0 Release 1999 4.1.1.2 Procedure Authenticate_MSC Procedure in the MSC to obtain an authentication response from the MS and relay it to the VLR Procedure Authenticate_MSC AUT_MSC1(1) Signals to/from the left are to/from the BSS; Signals to/from the right are to/from the VLR Authenticate Wait_For_ Auth_Response Authenticate ack Authenticate ack Result:= Pass Authenticate negative response Release transaction Authenticate negative response Result:= Aborted Figure 4.1.1.2 (sheet 1 of 1): Procedure Authenticate_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 15 3G TS 23.012 version 3.3.0 Release 1999 4.1.2 Detailed procedure in the VLR 4.1.2.1 Process Update_Location_Area_VLR General comment: at any stage in the location updating process the MSC may receive an indication from the BSS that the MM transaction has been released. The MSC then sends an Abort signal to the VLR. Upon receipt of this message, the VLR shall follow one of two possible courses of action. The two possible courses of action and the conditions determining which course shall be taken are as follows: 1. If a successfully authenticated radio connection is already established before the Abort message is received, the VLR shall ignore the message. 2. If a successfully authenticated radio connection has not been established before the Abort message is received, the VLR shall abort the Update Location Area process and return to the idle state. Sheet 1: the location area updating process will be activated by receiving an Update Location Area indication from the MSC. If there are parameter errors in the indication, the process is terminated with the appropriate error sent in the Update Location Area response to the MSC. Else, the behaviour will depend on the subscriber identity received, either an IMSI or a TMSI. Sheet 2: at the decision "HLR updating required?" the "True" branch shall be taken if and only if one or more of the following conditions is true: (1) Location Info Confirmed in HLR is false. (2) Data Confirmed by HLR is false. The type of Location Update is retrieved in 3G TS 23.078 procedure ‘Set_Notification_Type’ and is returned into the ‘Notify’ variable; this information is necessary for the CAMEL Mobility Management event notification procedure 3G TS 23.078 ‘Notify_gsmSCF’. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 16 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_VLR ULA_VLR1(4) Signals to/from the left are to/from the MSC Idle Update Location Area Identity used Previous LAI in this VLR? TMSI known? MSC area change? Location Info Confirmed in HLR:=False Subscriber Tracing active? Trace Subscriber Actibity 1 Data Confirmed by HLR:=False 2 Location Info Confirmed in HLR:=False PVLR address derivable? 3 Subscriber known in VLR? Previous LAI in this VLR? Location Info Confirmed in HLR:=False TMSI Yes Yes Yes Yes No No No No No Yes IMSI Yes No Yes No Figure 4.1.2.1 (sheet 1 of 4): Process Update_Location_Area_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 17 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_VLR ULA_VLR2(4) Signals to/from the left are to/from the MSC 1 Authentication_ required? Authenticate_ VLR Authentication Result? Failure case? Idle Delete subscriber record Set negative response: Unknown Subscriber Update Location negative response Idle Set negative response: Illegal Subscriber Set negative response: system failure Confirmed by Radio Contact:=True Update LAI HLR updating required? 4 Location_Update_ Completion_VLR Result= Pass? Update Register Set_Notification_ _Type Procedure defined in 3G TS 23.078 Notify_gsmSCF Procedure defined in 3G TS 23.078 Authenticated Radio Contact Established ARC timer Application process Yes Fail Aborted Unknown Subscriber Illegal Subscriber Procedure Error Pass True False Yes No No Figure 4.1.2.1 (sheet 2 of 4): Process Update_Location_Area_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 18 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_VLR ULA_VLR3(4) Signals to/from the right are to/from the PVLR 3 Request IMSI Attempt to retrieve IMSI from PVLR Wait_For_ PVLR_Response Request IMSI ack 1 Request IMSI negative response Obtain_IMSI_VLR See TS 23.018 Result= Pass? 1 Idle 2 Yes No Figure 4.1.2.1 (sheet 3 of 4): Process Update_Location_Area_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 19 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an incoming Location Update Request and trigger the correct application process Process Update_Location_Area_VLR ULA_VLR4(4) Signals to/from the left are to/from the MSC 4 Unknown HLR Update_HLR_VLR Result? Location_Update_ Completion_VLR Result= Pass? Update Register Set_Notification_ _Type Procedure defined in 3G TS 23.078 Notify_gsmSCF Procedure defined in 3G TS 23.078 Authenticated Radio Contact Established ARC timer Application process Idle Stand alone mode Set negative response: System Failure Update Location Area negative response Location_Update_ Completion_VLR Data confirmed by HLR:=False Delete Subscriber record Set negative response: Roaming Not Allowed Delete Subscriber record Set negative response: Unknown Subscriber 5 5 No Pass Yes No Procedure Error no Yes Roaming Not Allowed Unknown Subscriber Abort Yes Figure 4.1.2.1 (sheet 4 of 4): Process Update_Location_Area_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 20 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.2 Procedure Authenticate_VLR Procedure in the VLR to authenticate an MS via the MSC Procedure Authenticate_VLR AUT_VLR1(2) Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR. Authentication Failure Report Authentication sets available? Obtain_ Authentication_ Sets_VLR Result= Pass? Result= Aborted? Result:= Aborted Result= Procedure Error? Result:= Procedure Error Result:= Unknown Subscriber Authenticate Wait_For_ Authenticate_ Result Authenticate ack Received SRES= expected SRES? More authentication sets needed? Fetch_ Authentication_ Sets_VLR Authentication accepted Result:= Pass 1 Authenticate negative response More authentication sets needed? Fetch_ Authentication_ Sets_VLR Result:= Aborted 2 No No Yes No Yes No Yes Yes Yes No No Yes No Yes Figure 4.1.2.2 (sheet 1 of 2): Procedure Authenticate_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 21 3G TS 23.012 version 3.3.0 Release 1999 Procedure in the VLR to authenticate an MS via the MSC Procedure Authenticate_VLR AUT_VLR2(2) Signals to the left are to the MSC. Authentication Failure Report 1 Identity=IMSI? Retry with IMSI? Obtain_ IMSI_VLR Result= Pass? IMSI known? IMSI matches TMSI? Authentication rejected Result:= Illegal Subscriber Identity:= IMSI 2 Authentication accepted Result:= Unidentified Subscriber Result:= Aborted No Yes Yes Yes Yes No No No No Yes Figure 4.1.2.2 (sheet 2 of 2): Procedure Authenticate_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 22 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.3 Procedure Location_Update_Completion_VLR Sheet 1: Decision "National Roaming Restrictions Exist?" distinguishes whether or not the subscriber is allowed service in the target LA, based on the current location of the MS and the VLR's knowledge of other networks. The "Yes" branch results in the sending of "Update Location Area Negative Response" toward the MSC (and the MS), with cause "National Roaming Not Allowed." However, subscriber data shall not be deleted from the VLR. This is to avoid unnecessary HLR updating should the subscriber be allowed subsequently to roam in other LAs of the same MSC. Sheet 1: Decision "Roaming restriction due to Unsupported Feature received in subscriber data?" distinguishes whether or not the subscriber data received from the HLR indicates "roaming restriction due to unsupported feature." The "Yes" branch results in the sending of "Update Location Area Negative Response" toward the MSC (and the MS), with cause "National Roaming Not Allowed." However, subscriber data shall not be deleted from the VLR. This is to avoid unnecessary HLR updating should the subscriber be allowed subsequently to roam in other LAs of the same MSC. Sheet 1: Decision "Regional subscription restriction" distinguishes whether or not the subscriber is allowed service in the target LA, which the VLR deduces based on regional subscription information received from the HLR. The "Yes" branch results in the sending of "Update Location Area Negative Response" toward the MSC (and the MS), with cause "location area not allowed." However, subscriber data shall not be deleted from the VLR. This is to avoid unnecessary HLR updating should the subscriber be allowed subsequently to roam in other LAs of the same MSC. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 23 3G TS 23.012 version 3.3.0 Release 1999 Procedure in the VLR to complete Location Update Procedure Location_Update_Completion_VLR LUC_VLR1(2) Signals to/from the left are to/from the MSC National roaming restrictions exist? Roaming restriction Due To Unsupported Feature received in subscriber data? Set negative response: National Roaming Not Allowed LA Allowed:= False Result:=Pass Update Register Update Location Area negative response Regional subscription restriction 1 Set negative response: Location Area Not Allowed No Yes No No Yes Yes Figure 4.1.2.3 (sheet 1 of 2): Procedure Location_Update_Completion_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 24 3G TS 23.012 version 3.3.0 Release 1999 Procedure in the VLR to complete Location Update Procedure Location_Update_Completion_VLR LUC_VLR2(2) Signals to/from the left are to/from the MSC 1 LA Allowed:=True IMSI Detached := False Subscriber_ _Present_VLR See TS 29.002 Trace_Subscriber_ Activity_VLR TMSI to be reallocated? IMEI check required? Check_IMEI_VLR See TS 23.018 Result? Result:=Fail TMEI check Fail VLR application (Detach IMSI VLR) Set negative response: Illegal Equipment Update Location Area negative response Result:=Aborted Result:=Pass Update Location Area ack Set Ciphering Mode IMEI check required? Check_IMEI_VLR Result? Result:=Pass New TMSI Update Location Area ack WAIT_FOR_ _TMSI_Cnf Forward new TMSI ack Forward new TMSI negative response Freeze old TMSI No Yes Fail Aborted Pass No Yes Yes Pass Fail Aborted No Figure 4.1.2.3 (sheet 2 of 2): Procedure Location_Update_Completion_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 25 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.4 Process Update_HLR_VLR Sheet 1: The procedure Check_User_Error_In_Serving_Network_Entity is specific to Super-Charger; it is specified in 3G TS 23.116 [7]. HL R up da ting in VL R Procedure U pdate_H LR _VLR U_HLR_VLR1(1) Sig na ls to /from th e rig ht a re to/fro m the H LR Sig na ls to /from th e le ft a re to /fro m the MS C Up dat e Lo ca tio n W A IT_ FO R _ DATA Ins ert Su b sc rib er Dat a Activa te Tra ce M od e Fo rwa rd Ch eck SS In dication Up dat e L o ca tio n a ck Upd ate L oca tion n eg ati ve respo n se In sert_ Sub s_ Data _ VLR Activa te _Tracin g_ VL R Fo rwa rd Ch eck SS In dicatio n Fa ilure Ca se ? W AIT_ FOR_ DATA W AIT_ FOR_ DA TA W AIT_ FOR_ DA TA R esult:= Ro am ing Not Allowed Re sult:= Un known Su bscribe r Res ult:= Pro ced ure Error Resu lt:= Ab ort Resu lt := Pass Ch eck_ Use r_E rror_ I n_ Se rving _ Ne two rk_E ntity S ee TS 2 3 .1 1 6 Da ta Co nfirm ed by H L R:=True Da ta Co nfirme d b y HLR:=False Loca tio n In fo Co nfirm ed in HL R: =True L oca tion In fo Co nfirme d in HLR:=Fal se Roa min g n ot Allowed Un kno wn Su bscribe r Proced u re Erro r A bo rt Figure 4.1.2.4 (sheet 1 of 1): Process Update_HLR_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 26 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.5 Process Insert_Subs_Data_VLR Procedure to receive and store subscriber data in the VLR Procedure Insert_Subs_Data_VLR Insert_Subs_Data_VLR(1) Signals to/from the right are to/from the HLR Check_Parameters See TS 23.018 Result= Pass? All received features & services supported ? Update Subscriber Data MSC area restricted by regional subscription? Set MSC Area Restricted Insert Subscriber Data Ack Update subscriber data for supported feature(s) Set parameters for unsupported features Insert Subscriber Data negative response Yes Yes Yes No No No Figure 4.1.2.5 (sheet 1 of 1): Process Insert_Subs_Data_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 27 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.6 Process Activate_Tracing_VLR Handling the Activate Trace Mode in the VLR Procedure Activate_Tracing_VLR 1(1) Signals to/from the right are to/from the HLR Signals to/from the left are to/from the MSC Check_Parameters See TS 23.018 Result= Pass? Subscriber Known? Tracing supported Set negative response Facility not supported Active Trace Mode negative response Tracing buffer full? Set Subscriber Tracing := Active Active Trace Mode Ack Set negative response Tracing buffer full Set negative response Unidentified subscriber Yes Yes No Yes No No No No Figure 4.1.2.6 (sheet 1 of 1): Process Activate_Tracing_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 28 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.7 Process Send_Identification_PVLR Handling of the Send in the Previous VLR (PVLR) Process Send_Identification_PVLR SI_PVLR1(1) Signals to/from the are to/from the new Idle Send Identification Check Parameters Result= Pass? TMSI Known? Set IMSI Authentication sets available? Set Authentication Info Send Identification ack Idle Set negative unidentified subscriber Send Identification negative response Yes Yes Yes No No No Send Current SecurityContext Set Current Security Context Yes No Figure 4.1.2.7 (sheet 1 of 1): Process Send_Identification_PVLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 29 3G TS 23.012 version 3.3.0 Release 1999 4.1.2.8 Process Trace_Subscriber_Activity_VLR Proce du re in th e V LR to jud ge wh eth er to sen d tra ce su b scrib er a ctivity or n ot Pro cedure Trace_Subscriber_Activity_VLR 1(1) Sig na ls to /from th e le ft are to/ from th e M SC S ub scrib er Tra ce= a ctive ? T ra ce S ub scrib er A ctivity Yes No Figure 4.1.2.8 (sheet 1 of 1): Process Trace_Subscriber_Activity_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 30 3G TS 23.012 version 3.3.0 Release 1999 4.1.3 Detailed procedure in the HLR 4.1.3.1 Process Update_Location_HLR Sheet 1: The procedure Super_Charged_Cancel_Location_HLR is specific to Super-Charger; it is specified in TS 23.116 [7]. If the previous VLR and the originating HLR support the Super-Charger functionality, processing continues from the "Yes" exit of the test "Result=Pass?". Sheet 2: The procedure Super_Charged_Location_Updating_HLR is specific to Super-Charger; it is specified in TS 23.116 [7]. If subscription data needs to be sent to the VLR, processing continues from the "No" exit of the test "Result=Pass?". ETSI ETSI TS 123 012 V3.3.0 (2000-06) 31 3G TS 23.012 version 3.3.0 Release 1999 Proces s In th e HL R App licatio n to h an dlle L oca tion Upd atin g Process Update_Location_HLR 1(3) Sig na ls to /from th e le ft a re to /fro m th e VLR I DL E Up da te L oca tio n Ch eck_ P aram ete rs Se e TS 2 3.0 18 Re sult = P ass? S ub scrib er K nown ? S ubs crib er Tra cin g A ctive in V LR =False Ne twork A cc ess M od e= GP RS O nly? Ne w VLR ? S et ne ga tive re spo nse : Unk nown S ub sc rib er Su per_ Charg ed _ Ca n cel_L oc atio n_ HL R Se e TS 23 .11 6 Re sult : Pa ss? Upd ate L oca tion Neg at ive Res po nse Ca n ce l_L oca tio n_ HL R IDL E 1 Yes No No No Yes Yes No No Ye s Figure 4.1.3.1 (sheet 1 of 3): Process Update_Location_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 32 3G TS 23.012 version 3.3.0 Release 1999 Proces s In th e HL R App licatio n to h an dlle L oca tion Upd atin g Process Update_Location_HLR 2(3) Sig na ls to /from th e le ft a re to /fro m th e VLR 1 Su bscribe r Allo we d to Roa m in to PL MN? Upda te Ro ute ing Inf o S et Ne ga tive Re spo nse : Ro amin g Not Allow e d Re set Flag MS Purg ed Dele te Routein g I nfo Co ntro l_ Tra cin g _ HL R Upd ate L oca tion Neg a tive Re spo nse Re su lt = Pas s? I DL E IDLE Sup er_Ch arge d_ Lo ca tio n_ Upd atin g_ HL R See TS 23 .11 6 Re sult: = P ass? I nse rt_ S ub scrib er_ Da ta_ HLR Re sult = P ass? MSC A rea Re stricte d? OR Ro am ing Restricte d Du e t o Un sup po rted Fea tu re ? Resu lt= Ab orte d? Sub scribe r_ Pres ent _ HL R Upd ate L oca tion Neg at ive Res po nse IDLE 3 IDL E Ye s No No Ye s No Ye s Yes No No Yes No Y es Figure 4.1.3.1 (sheet 2 of 3): Process Update_Location_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 33 3G TS 23.012 version 3.3.0 Release 1999 Process In the HLR Application to handlle Location Updating Process Update_Location_HLR 3(3) Signals to/from the left are to/from the VLR 3 Check_SS_ Required Forward Check SS Indication Check_SS_ Required:= False Update Location Ack Location Updating Complete To Process CCBS_ Coordinator_HLR See 3GPP 23.093 Idle True False Figure 4.1.3.1 (sheet 3 of 3): Process Update_Location_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 34 3G TS 23.012 version 3.3.0 Release 1999 4.1.3.2 Procedure Insert_Subscriber_Data_HLR Procedure in the HLR Application for handling the insertion of subscriber data into the VLR Procedure Insert_Subscriber_Data_HLR 1(2) Signals to/from the left are to/from the VLR Insert Subscriber Data Count:=1 More Data To Send? Insert Subscriber Data Count:= Count + 1 WAIT_FOR_ ISD_Ack ISD_Ack Count:= Count - 1 1 Abort Result:= Aborted ISD Negative Response Set Negative Response System Failure Result:= Fail 2 3 Yes No Figure 4.1.3.2 (sheet 1 of 2): Procedure Insert_Subscriber_Data_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 35 3G TS 23.012 version 3.3.0 Release 1999 Procedure in the HLR Application for handling the insertion of subscriber data into the VLR Procedure Insert_Subscriber_Data_HLR 2(2) Signals to/from the left are to/from the VLR 1 Any services not supported in VLR? Ignore Unsupported Service? Replace Service In VLR? Unsupported Service Critical? HLR Internal Action MSC Area Restricted? Set MSC Area Restricted Count>0? WAIT_FOR_ ISD_Ack More data to send? Result:= Pass 3 Roaming Restricted Due To Unsupported Feature=True; MSC Area Restricted= True 2 Replace Service Yes No No No Yes Yes No No Yes No Yes Yes Yes No Figure 4.1.3.2 (sheet 2 of 2): Procedure Insert_Subscriber_Data_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 36 3G TS 23.012 version 3.3.0 Release 1999 4.1.3.3 Process Subscriber_Present_HLR Process in the HLR Application to perform actions required for short message alerting Process Subscriber_Present_HLR 1(1) MWD Set? Alert_Service_ Centre_HLR See TS 29.002 Section 25.10.2 Yes No Figure 4.1.3.3: Process Subscriber_Present_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 37 3G TS 23.012 version 3.3.0 Release 1999 4.1.3.4 Procedure Control_Tracing_HLR Procedure for Controlling Tracing in the HLR Application Procedure Control_Tracing_HLR 1(1) Signals to/from the left are to/from the VLR Subscriber tracing active in HLR? Subscriber Tracing active in VLR? Subscriber in HPLMN area? Result:=Pass Activate Trace Mode WAIT_FOR_ ATM_RESULT ATM_ack. Set Subscriber Tracing Active in VLR Result:=Pass ATM Negative Response Set Subscriber Tracing Inctive in VLR Report Error To O&M Center Result:=Fail Yes No Yes Figure 4.1.3.4 (sheet 1 of 1): Procedure Control_Tracing_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 38 3G TS 23.012 version 3.3.0 Release 1999 4.2 Location Cancellation 4.2.1 Detailed procedure in the VLR 4.2.1.1 Process Cancel_Location_VLR Handlig of the Cancel Location in the VLR Process Cancel_Location_VLR 1(1) Signals to/from the right are to/from the HLR Idle Cancel Location Check_Parameters See TS 23.018 Result= Pass? Subscriber registered Delete subscriber from register Release TMSI Cancel Location ack Idle Cancel Location negative response Idle Yes Yes No No Figure 4.2.1.1 (Sheet 1 of 1): Process Cancel_Location_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 39 3G TS 23.012 version 3.3.0 Release 1999 4.2.2 Detailed procedure in the HLR 4.2.2.1 Process Cancel_Location_HLR Process in the HLR application to initiate cancellation of location registration in a VLR Process Cancel_Location_HLR 1(1) Signals to/from the left are to/from the VLR Cancel Location WAIT_FOR_ ACK Cancel Location Ack Abort Repeat Location Cancellation? Wait for time expiry Cancel Location Negative Response Yes No Figure 4.2.2.1: Process Cancel_Location_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 40 3G TS 23.012 version 3.3.0 Release 1999 4.3 Detach IMSI 4.3.1 Detailed procedure in the MSC 4.3.1.1 Process Detach_IMSI_MSC Process in the MSC to handle an IMSI detach Process Detach_IMSI_MSC 1(1) Signals to/from the left are to/from the BSS Signals to/from the right are to/from the VLR Idle IMSI detach Explicit IMSI detach Idle Figure 4.3.1.1 (Sheet 1 of 1): Process Detach_IMSI_MSC ETSI ETSI TS 123 012 V3.3.0 (2000-06) 41 3G TS 23.012 version 3.3.0 Release 1999 4.3.2 Detailed procedure in the VLR 4.3.2.1 Process Detach_IMSI_VLR Sheet 1: The signal "Authenticated Radio Contact Terminated" is sent to Process Detach_IMSI_VLR from RR handling in the MSC whenever authenticated radio contact is terminated, e.g. at the release of a call. The 3G TS 23.078 procedure ‘Notify_gsmSCF’ with ‘Notify’ variable set either to ‘explicit’ or to ‘implicit detach’ allows the handling of CAMEL Mobility Management events notification. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 42 3G TS 23.012 version 3.3.0 Release 1999 Process in the VLR to handle an Detach IMSI timer Process Detach_IMSI_VLR 1(1) Signals to/from the left are to/from the MSC unless marked otherwise Signals to/from the right are to/from the detach timer Idle Authenticated Radio Contact Established From Process Update_ Location_Area_VLR or Procedure Process_ Access_Request Stop timer Reload timer Idle Authenticated Radio Contact terminated IMSI Detached =False Restart timer Idle IMEI check fail From VLR application when IMEI check failed IMSI Detached =True Stop timer Idle Timer Expired Notify = implicit IMSI detach Notify_gsmSCF Procedure defined in 3G TS 23.078 Explicit IMSI detach Notify = explicit IMSI detach Figure 4.3.1.1 (Sheet 1 of 1): Process Detach_IMSI_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 43 3G TS 23.012 version 3.3.0 Release 1999 4.4 Purge MS 4.4.1 Detailed procedure in the VLR 4.4.1.1 Procedure Purge_MS_VLR Sheet 1: The procedure Purge_MS_In_Serving_Network_Entity is specific to Super-Charger; it is specified in TS 23.116 [7]. If the VLR and the originating HLR support the Super-Charger functionality, processing continues from the "Yes" exit of the test "Result=Pass?". ETSI ETSI TS 123 012 V3.3.0 (2000-06) 44 3G TS 23.012 version 3.3.0 Release 1999 Proces s in t he VL R to p urg e M S. Pro cess Purge_MS_ VLR 1(1) Sig nal s to /from th e rig ht a re to/ from th e HL R Sig na ls to /from th e le ft a re to /fro m t he Op eratio n & M aint en an ce Ce nt re I dle O &M Pu rg e MS P urge _M S_In_ S ervin g_ Ne tw ork_ E ntity S ee TS 23 .11 6 Re su lt:= P ass? P urge M S W A IT_FO R_ A CK Purg e M S Ack De lete Sub scribe r Da ta TMS I t o b e frozen ? Fre eze TM SI Set Purg ing Suc ce ssfu l O&M Pu rge MS ack Idle Pu rge _M S n eg ative resp o nse Se t Pu rge Fa ile d O &M Purg e M S n eg ative resp o nse Id le No Ye s No Yes Figure 4.4.1.1 (Sheet 1 of 1): Procedure Purge_MS_VLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 45 3G TS 23.012 version 3.3.0 Release 1999 4.4.2 Detailed procedure in the HLR Sheet 1: If the received VLR number and the stored VLR number do not match, the HLR sends Purge MS ack containing an empty result to indicate successful outcome. Since the MS is known by the HLR to be in a different VLR area, it is not appropriate to block mobile terminated calls or short messages to the MS, but the VLR which initiated the purging procedure can safely purge its record for the MS without freezing the TMSI. Sheet 1: If the received SGSN number and the stored SGSN number do not match, the HLR sends a Purge MS ack containing an empty result to indicate successful outcome. Since the MS is known by the HLR to be in a different SGSN area, it is not appropriate to block short messages to the MS, but the SGSN which initiated the purging procedure can safely purge its record for the MS without freezing the P-TMSI. ETSI ETSI TS 123 012 V3.3.0 (2000-06) 46 3G TS 23.012 version 3.3.0 Release 1999 Process in the HLR Application for handling the purging of MS data from a VLR Process Purge_MS_HLR 1(1) Signals to/from the left are to/from the VLR Idle Purge MS Check_ Parameters See TS 23.018 Result= Pass? Subscriber Known? Received VLR No. = Stored VLR No.? Set Flag MS Purged for non- GPRS Set Flag Freeze TMSI Received SGSN No. = Stored SGSN No.? Set Flag MS Purged for GPRS Set Flag Freeze P-TMSI Purge MS Ack. Idle Set Negative Response= Unknown Susbcriber Report Error to O&M Purge MS Negative Response Idle Purge MS Negative Response Idle Yes Yes Yes Yes No No No No Figure 4.4.2.1 (Sheet 1 of 1): Procedure Purge_MS_HLR ETSI ETSI TS 123 012 V3.3.0 (2000-06) 47 3G TS 23.012 version 3.3.0 Release 1999 Annex A (informative): Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 03.12 6.0.0 Transferred to 3GPP CN1 CN#03 23.012 3.0.0 Approved at CN#03 CN#06 23.012 3.0.0 001r1 R99 3.1.0 Restructuring of MAP Location Management Procedures, Stage 2 CN#06 23.012 3.0.0 002 R99 3.1.0 Introduction of Super-Charger into TS 23.012 CN#07 23.012 3.1.0 003r3 R99 3.2.0 Introduction of Enhanced User Identity Confidentiality CN#07 23.012 3.1.0 004 R99 3.2.0 Addition of Current Security Context Data to Send_Identification_PVLR CN#07 23.012 3.1.0 005 R99 3.2.0 Introduction of Authentication Failure Report 23.012 3.2.0 R99 3.2.1 CR 23.012-003r3 removed because implemented in error CN#08 23.012 3.2.1 006 R99 3.3.0 Introduction of Mobility Management event notification into 23.012 procedures 48 ETSI ETSI TS 123 012 V3.3.0 (2000-06) 3G TS 23.012 version 3.3.0 Release 1999 History Document history V3.1.0 January 2000 Publication V3.2.0 March 2000 Publication V3.3.0 June 2000 Publication |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 1 Scope | ........................................................................................................................................................5 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 2 References | ................................................................................................................................................5 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 3 Definitions and abbreviations | ..................................................................................................................6 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 3.1 Definitions | ......................................................................................................................................................... 6 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 3.2 Abbreviations | ..................................................................................................................................................... 6 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 4 Applicability | ............................................................................................................................................8 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 5 Description | ...............................................................................................................................................8 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 6 Normal procedures with successful outcome | ...........................................................................................9 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 7 Exceptional procedures | ............................................................................................................................9 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 8 Addressing | ...............................................................................................................................................9 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9 Supplementary Services and Service Interworking | .................................................................................9 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.1 Calling line identification presentation (CLIP) | .................................................................................................. 9 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.2 Calling line identification restriction (CLIR) | ..................................................................................................... 9 9.3 Connected line identification presentation COLP) .......................................................................................... 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.4 Connected line identification restriction (COLR) | ............................................................................................ 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.5 Call Forwarding Unconditional (CFU) | ............................................................................................................ 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.6 Call Forwarding on mobile subscriber Busy (CFB) | ........................................................................................ 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.7 Call Forwarding on No Reply (CFNRy) | .......................................................................................................... 10 9.8 Call Forwarding on mobile subscriber Not Reachable (CFNRc)..................................................................... 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.9 Call Waiting (CW) | ........................................................................................................................................... 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.10 Call hold (HOLD) | ............................................................................................................................................ 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.11 Multiparty services (MPTY) | ............................................................................................................................ 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.12 Closed User Group | .......................................................................................................................................... 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.13 Advice of Charge services | ............................................................................................................................... 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.14 Barring of All Outgoing Calls (BAOC) | ........................................................................................................... 10 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.15 Barring of Outgoing International Calls (BOIC) | ............................................................................................. 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.16 Barring of Outgoing International Calls except those di | rected to the Home PLMN Country (BOIC- exHC)............................................................................................................................................................... 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.17 Barring of All Incoming Calls (BAIC) | ............................................................................................................ 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.18 Barring of Incoming Calls when roaming outside the home | PLMN country (BIC-Roam) ............................. 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.19 Explicit Call Transfer (ECT) | ........................................................................................................................... 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.20 Completion of Calls to Busy Subscriber (CCBS) | ............................................................................................ 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.21 Support of Private Numbering Plan (SPNP) | .................................................................................................... 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.22 Multiple Subscriber Profile (MSP) | .................................................................................................................. 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 9.23 enhanced Multi-Level Priority and Pre-emption (eMLPP) | .............................................................................. 11 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 10 Interworking with other network features | ..............................................................................................12 |
c2b2d90a0f1db38b8cdf511166e9abaa | 122 066 | 10.1 Customised Applications for Mobile network Enhanced Log | ic (CAMEL)..................................................... 12 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.