3GPP TS 23.012

3GPP TS 23.012 V11.1.
1 (2012-09)
Technical Specification
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Location management procedures (Release 11)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
Release 11
3GPP TS 23.012 V11.1.1 (2012-09)
Keywords
GSM, UMTS, network, location, management
3GPP Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
2012, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS is a Trade Mark of ETSI registered for the benefit of its members 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association
3GPP
Release 11
3GPP TS 23.012 V11.1.1 (2012-09)
Contents
Foreword ............................................................................................................................................................ 5 1
1.1 1.2
Scope ........................................................................................................................................................ 6
References.......................................................................................................................................................... 6 Abbreviations ..................................................................................................................................................... 7
2
2.1 2.2 2.3 2.4 2.4.1 2.4.2 2.5 2.6
Definitions................................................................................................................................................ 7
Location management ........................................................................................................................................ 7 Location area and MSC area .............................................................................................................................. 8 Location area identification ............................................................................................................................... 8 IMSI detach/attach operation ............................................................................................................................. 8 Explicit IMSI detach/attach .......................................................................................................................... 8 Implicit IMSI detach .................................................................................................................................... 8 Use of the term mobile station (MS) in the present document ........................................................................... 8 Paging area......................................................................................................................................................... 8
3
3.1 3.2 3.3 3.4 3.5 3.6 3.6.1 3.6.1.1 3.6.1.2 3.6.1.3 3.6.1.4 3.7 3.7.1 3.7.2 3.7.3 3.8 3.8.1 3.8.1.1 3.8.1.2 3.8.1.3 3.8.1.4
General procedures in the network related to Location Management ..................................................... 9

Procedures in the MSC related to Location Updating........................................................................................ 9 Procedures in the VLR related to Location Updating ........................................................................................ 9 Procedures in the HLR related to Location Updating ........................................................................................ 9 Normal Location Updating and IMSI detach/attach operation .......................................................................... 9 IMSI enquiry procedure ..................................................................................................................................... 9 Information transfer between Visitor and Home Location Registers ................................................................. 9 Procedures for location management ........................................................................................................... 9 Location updating procedure .................................................................................................................. 9 Downloading of subscriber parameters to the VLR ................................................................................ 9 Location cancellation procedure ........................................................................................................... 10 Mobile subscriber purging procedure ................................................................................................... 10 Overload Protection ......................................................................................................................................... 10 Overview .................................................................................................................................................... 10 Congestion Control during Mobility Management ..................................................................................... 10 Extended periodic LAU Signalling .................................................................................................................. 11 Information transfer between VLR and CSG Subscriber Server...................................................................... 11 Procedures for location management ......................................................................................................... 11 General ................................................................................................................................................. 11 Updating VCSG Location procedure .................................................................................................... 11 Downloading of VPLMN CSG subscription data to the VLR .............................................................. 11 VCSG Location cancellation procedure ............................................................................................... 12
Detailed Procedures in the network related to Location Management .................................................. 12
4.1 Location Updating ........................................................................................................................................... 12 4.1.1 Detailed procedure in the MSC .................................................................................................................. 12 4.1.1.1 Process Update_Location_Area_MSC ................................................................................................. 12 4.1.1.2 Procedure Authenticate_MSC .............................................................................................................. 16 4.1.2 Detailed procedure in the VLR .................................................................................................................. 17 4.1.2.1 Process Update_Location_Area_VLR .................................................................................................. 17 4.1.2.1a Procedure Retrieve_IMEISV_If_Required........................................................................................... 22 4.1.2.2 Procedure Authenticate_VLR ............................................................................................................... 23 4.1.2.3 Procedure Location_Update_Completion_VLR ................................................................................... 25 4.1.2.4 Procedure Update_HLR_VLR.............................................................................................................. 30 4.1.2.5 Procedure Insert_Subs_Data_VLR ....................................................................................................... 32 4.1.2.6 Procedure Activate_Tracing_VLR ....................................................................................................... 33 4.1.2.7 Process Send_Identification_PVLR ..................................................................................................... 34 4.1.2.8 Process Trace_Subscriber_Activity_VLR ............................................................................................ 36 4.1.2.9 Procedure Perform Relaying................................................................................................................. 36 4.1.2.10 Procedure Update_VCSG_Location_VLR .......................................................................................... 37 4.1.2.11 Procedure Insert_VCSG_Subs_Data_VLR .......................................................................................... 39
3GPP
Release 11
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.3 4.1.3.1 4.1.3.2 4.1.3.3 4.1.3.4 4.1.4 4.1.4.1 4.1.4.2 4.2 4.2.1 4.2.1.1 4.2.2 4.2.2.1 4.2A 4.2A.1 4.2A.1.1 4.2A.2 4.2A.2.1 4.3 4.3.1 4.3.1.1 4.3.2 4.3.2.1 4.4 4.4.1 4.4.1.1 4.4.2 4.4.2.1
Detailed procedure in the HLR .................................................................................................................. 41 Process Update_Location_HLR ........................................................................................................... 41 Procedure Insert_Subscriber_Data_HLR ............................................................................................. 45 Process Subscriber_Present_HLR ........................................................................................................ 47 Procedure Control_Tracing_HLR ........................................................................................................ 48 Detailed procedure in the CSS ................................................................................................................... 48 Process Update_VCSG_Location_CSS ................................................................................................ 48 Procedure Insert_VCSG_Subs_Data_CSS ........................................................................................... 50 Location Cancellation ...................................................................................................................................... 53 Detailed procedure in the VLR .................................................................................................................. 53 Process Cancel_Location_VLR ............................................................................................................ 53 Detailed procedure in the HLR .................................................................................................................. 56 Process Cancel_Location_HLR ............................................................................................................ 56 VCSG Location Cancellation........................................................................................................................... 58 Detailed procedure in the VLR .................................................................................................................. 58 Process Cancel_VCSG Location_VLR ................................................................................................ 58 Detailed procedure in the CSS ................................................................................................................... 60 Process Cancel_VCSG Location .......................................................................................................... 60 Detach IMSI..................................................................................................................................................... 62 Detailed procedure in the MSC .................................................................................................................. 62 Process Detach_IMSI_MSC ................................................................................................................. 62 Detailed procedure in the VLR .................................................................................................................. 63 Process Detach_IMSI_VLR ................................................................................................................. 63 Purge MS ......................................................................................................................................................... 65 Detailed procedure in the VLR .................................................................................................................. 65 Procedure Purge_MS_VLR .................................................................................................................. 65 Detailed procedure in the HLR .................................................................................................................. 67 Process Purge_MS_HLR ...................................................................................................................... 67
Annex A (informative):
Change history ............................................................................................... 69
3GPP
Release 11
3GPP TS 23.012 V11.1.1 (2012-09)
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.
3GPP
Release 11
3GPP TS 23.012 V11.1.1 (2012-09)
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 3GPP TS 29.002 [8]. 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 3GPP TS 23.022 [6]. The procedures between MSC, VLR and HLR utilise the Mobile Application Part (MAP) and details concerning the protocol handling are contained in 3GPP TS 29.002 [8]. The present document excludes location management procedures for the packet switched domain, which are covered in 3GPP TS 23.060 [20]. 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] [2] [3] [4] [5] [5a] [6] [7] [8] [9] 3GPP TR 21.905: "3G Vocabulary". 3GPP TS 23.002: "Network architecture". 3GPP TS 23.003: "Numbering, addressing and identification". 3GPP TS 23.007: "Restoration procedures". 3GPP TS 23.008: "Organization of subscriber data". 3GPP TS 23.018: "Basic call handling; Technical realization". 3GPP TS 23.022: "Functions related to Mobile Station (MS) in idle mode". 3GPP TS 23.116: "Super-Charger Technical Realisation; Stage 2". 3GPP TS 29.002: "Mobile Application Part (MAP) specification". 3GPP 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)".
3GPP
Release 11
3GPP TS 23.012 V11.1.1 (2012-09)
[10] [11] [11a] [12] [13] [14]
3GPP TS 43.020: "Security related network functions". 3GPP TS 23.078: " Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4 stage2". 3GPP TS 23.195: "Provision of UE Specific Behaviour Information to Network Entities". 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes". 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols - Stage 3". 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)". 3GPP TS 32.422: "Subscriber and equipment trace: Trace control and configuration management". 3GPP TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements". 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". 3GPP TR 29.994: "Recommended infrastructure measures to overcome specific Mobile Station (MS) faults". 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)". 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[15] [16] [17] [18] [19] [20]
1.2
Abbreviations
Abbreviations are listed in 3GPP TR 21.905 [1]. In addition, for the purposes of the present document, the following abbreviations apply: ADD CSG CSS PUESBINE UESBI-Iu Automatic Device Detection Closed Subscriber Group CSG Subscriber Server Provision of User Equipment Specific Behaviour Information to Network Entities User Equipment Specific Behaviour Information over the Iu interface
2
2.1
Definitions
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; the CSG Subscriber Server where the CSG subscription data are stored in the visited PLMN for inbound roaming MS, and where the current location may be stored.
See also 3GPP TS 23.002 [2] where the network architecture is described, and 3GPP TS 23.008 [5] where the data stored in the location registers are described.
3GPP
Release 11
3GPP TS 23.012 V11.1.1 (2012-09)
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 3GPP TS 23.002 [2].
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 3GPP TS 23.003 [3]).
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; when the MSC/VLR applies Mobility Management Congestion Control to a MS, the MSC/VLR may need to adjust the Implicit Detach timer as specified in clause 3.7.2. During an established radio contact, the 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.
2.6
Paging area
As an option, and for paging optimization purpose, the VLR may control Paging Areas. A Paging Area (PgA) is composed of up to 5 Location Areas, and the MSC area is composed of several Paging Areas. Paging areas may overlap each other. The Paging Area is stored in the HLR and updated at each paging area change. The Paging Area is sent by the HLR to the VLR at roaming number request and may be used by the MSC/VLR for paging (e.g. when LAI is not known, after MSC/VLR restart) (see 3GPP TS 23.018 [5a]).
3GPP
Release 11
3GPP TS 23.012 V11.1.1 (2012-09)
3
3.1
General procedures in the network related to Location Management

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
FFS
Procedures in the VLR related to Location Updating
3.3
FFS
Procedures in the HLR related to Location Updating
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 3GPP TS 29.002 [8]. 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
3.6.1
Information transfer between Visitor and Home Location Registers

Procedures for location management
Detailed procedures for exchange of and location updating information between visitor and home location registers are given in 3GPP TS 29.002 [8]. Below follows an overview of these procedures.
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 3GPP TS 23.003 [3]).
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
3GPP
Release 11
10
3GPP TS 23.012 V11.1.1 (2012-09)
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 3GPP TS 29.007 [9]) and stored in the HLR. Among these MSISDNs, the Basic MSISDN Indicator as part of the HLR subscriber data (see 3GPP TS 23.008 [5]) 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. If the HPLMN applies the Administrative Restriction of Subscribers Access feature, the HLR shall convey the subscriber access restriction parameter (AccessRestrictionData) to the VLR. The VLR shall check this subscription parameter against the radio access technology that supports the LA/RA in which the UE is roaming to decide whether the location update should be allowed or rejected. For further information of the Subscriber access restriction see 3GPP TS 23.008[5].
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 nonvolatile back-up that is performed when the HLR restarts after a failure.
3.7
3.7.1
Overload Protection
Overview
As the number of mobile devices increase and become more automated (Machine Type Communication, MTC type devices) the network is at greater risk of becoming overloaded. Additional mechanisms may be deployed to prevent and or control overload and congestion. This sub-clause describes such optional mechanisms. The succeeding descriptions applies to Network Mode of Operation II (requesting CS only). For NMO I (requesting both CS and PS) the procedures are described in 3GPP TS 23.060 [20].
3.7.2
Congestion Control during Mobility Management
The MSC or VLR may support the capability to reject Location Updating Requests or IMSI Attach messages from an MS if the node is experiencing congestion. The MSC/VLR may indicate the rejection is due to congestion with a specific congestion cause value and a specific back-off timer, see 3GPP TS 24.008 [13]. The Mobility Management back-off timer shall not impact Cell/RAT and PLMN change. Cell/RAT and RA change do not stop the Mobility Management back-off timer. The Mobility Management back-off timer shall not be a trigger for PLMN reselection. The back-off timer is stopped as defined in 3GPP TS 24.008 [13] when a new PLMN that is not an equivalent PLMN is accessed.
3GPP
Release 11
11
3GPP TS 23.012 V11.1.1 (2012-09)
While the Mobility Management back-off timer is running, the MS shall not initiate any Mobility Management procedures. However, the MS is allowed to initiate Mobility Management procedures for priority/emergency services and mobile terminated services even when the Mobility Management back-off timer is running. If the MS receives a paging request from the MSC/VLR while the Mobility Management back-off timer is running, the MS shall stop the Mobility Management back-off timer and initiate the CM Service Request procedure.To avoid that large amounts of MSs initiate deferred requests (almost) simultaneously, the MSC/VLR should select the Mobility Management back-off timer value so that deferred requests are not synchronised. The decision to apply congestion control is made by the MSC/VLR, the detailed criteria for which is outside the scope of this specification but may for example take into account the low access priority indication if signalled by MSs. The MSC/VLR should use implicit detach timer values that are larger than the Mobility Management back-off timer values to avoid that the MSC/VLR implicitly detaches the MS before the MS has performed a LAU procedure, which could lead to unneccessary signalling after the back-off timer expires.
3.7.3
Extended periodic LAU Signalling
To reduce network load from periodic location updating (LAU) signalling and to increase the time until the MS detects a potential need for changing the RAT or PLMN (e.g. due to network problems) longer values of the periodic LAU timer and implicit detach timer should be supported. A long periodic LAU timer value may be locally configured at the MSC/VLR for MS configured for low access priority (see 3GPP TS 24.368 [19]) or may be stored as part of the subscription data in the HLR. During the IMSI Attach and Location Updating procedures, the MSC/VLR should allocate the periodic LAU timer value for the MS based on VPLMN operator policy, low access priority indication from the MS, and subscription information received from the HSS. If the allocated periodic LAU timer value is longer than T3212, the MSC/VLR shall provide the MS with the periodic LAU timer in the Location Updating Accept message as specified in 3GPP TS 24.008 [13]. If the subscriber is not roaming and the MSC/VLR receives a subscribed periodic LAU timer value from the HSS, it should allocate the subscribed value to the MS as periodic LAU timer. If the subscriber is roaming and the MSC/VLR receives a subscribed periodic LAU timer value from the HSS, the MSC/VLR may use the subscribed periodic LAU timer value as an indication to decide for allocating a locally configured periodic LAU timer value to the MS.
3.8
3.8.1
3.8.1.1
Information transfer between VLR and CSG Subscriber Server

Procedures for location management
General
Detailed procedures for exchange of and location updating information between VLR and CSG Subscriber Server are given in 3GPP TS 29.002[8]. This clause follows an overview of these procedures.
3.8.1.2
Updating VCSG Location procedure
This procedure is used when an MS registers with a Visitor Location Register and there is a need to do a registration with the CSS. The VLR provides its address to the CSS.
3.8.1.3
Downloading of VPLMN CSG subscription data to the VLR
As a part of the location updating procedure, the CSG Subscriber Server shall convey the VPLMN CSG subscription data of the roaming MS which needs to be known by the visitor location register for determine whether the MS can access the current cell to have CS services. This procedure is also used whenever there is a change in the VPLMN CSG subscription data that needs to be conveyed to the VLR.
3GPP
Release 11
12
3GPP TS 23.012 V11.1.1 (2012-09)
3.8.1.4
VCSG Location cancellation procedure
The procedure is used by the CSS to remove a MS from a CSS. The procedure will normally be used when there is a removal of the CSG subscription data in CSS and of the MS registration including the case where a MS was registered in CSS but without CSG data.
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 3GPP TS 29.002 [8]. 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 3GPP TS 29.002 [8]. 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.
4.1
4.1.1
4.1.1.1
Location Updating
Detailed procedure in the MSC
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 1: The procedures Check_IMEI_MSC, Obtain_IMEI_MSC and Obtain_IMSI_MSC are specified in 3GPP TS 23.018 [5a]. Sheet 1: The input signal "Send UESBI-Iu to Access Network" carries the IMEISV. Sheet 1: The task "Convert IMEISV to UESBI" is defined in 3GPP TS 23.195 [11a]. Sheet 2: The procedure Check_IMEI_MSC is specified in 3GPP TS 23.018 [5a]. 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. Sheet 2: The Forward new TMSI may also be received prior to Update Location Area negative response if the option "TMSI reallocation in case of Location Update reject with cause #13 (roaming not allowed in Location Area) or #15 (no suitable cells in Location Area)" is applicable (see 4.1.2.3). The new TMSI is forwarded together with the new LAI. They are kept in the UE/SIM on receipt of the Location Update reject with cause #13 or #15 (see 3GPP TS 24.008 [13]). Sheet 2: IMEISV trace list shall be made available to the MSC. The list may contain IMEISV entries if Management Based Trace Activation is supported in RAN and MSC has received the trace list in the Uplink Information Transfer message (See 3GPP TS 32.422 [15] and 25.413 [17]). The test "Current IMEISV included in IMEISV trace list?" will follow the "no" case when no entries exist. Sheet 2: For Trace Invocation in RAN concepts and procedures see 3GPP TSs 32.421 [16], 32.422[15] and 25.413[17].
3GPP
Release 11
13
3GPP TS 23.012 V11.1.1 (2012-09)
Sheet 2: IMEISV trace list
3GPP
Release 11
14
3GPP TS 23.012 V11.1.1 (2012-09)
process Update_Location_Area_MSC
Process in the MSC to handle an incoming Location Update Request, and trigger the correct application process
ULA_MSC1(2)
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
Send UESBI-Iu to Access Network
Trace subscriber activity
Check IMEI
Provide IMEI
Provide IMSI
Authenticate
Convert IMEISV to UESBI-Iu
See 3GPP TS 23.195
Start activity tracing
Check_IMEI_ MSC
Obtain_IMEI_ MSC
Obtain_IMSI_ MSC
Authenticate_ MSC
UESBI-Iu
Yes Result= Pass?
No
MM Release
Update Location Area negative response
Update Location Area ack
Forward check SS
Set CipheringMode
Abort
Location Update reject
Check SS
Cipher Command
Idle
Wait_For_ TMSI
Idle
Figure 4.1.1.1 (sheet 1 of 2): Process Update_Location_Area_MSC
3GPP
Release 11
15
3GPP TS 23.012 V11.1.1 (2012-09)
process Update_Location_Area_MSC
Process in the MSC to handle an incoming Location Update Request, and trigger the correct application process Wait_For_ TMSI
ULA_MSC2(2)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR Update Location Area negative response Location Update reject Update Location Area ack
MM Release
New TMSI
Forward check SS
Check IMEI
From VLR
Abort
Save TMSI
Check SS
Check_IMEI_ MSC
Idle
Wait_For_ Location_Updating_ Completion
Yes Result= Pass? No Location Update reject
Idle
Update Location Area ack
Wait_For_ TMSI
Cause #13 or #15 to send and TMSI option supported ? Location Update ack Yes New TMSI & LAI No Wait_For_ TMSI_ Acknowledge Including new LAI & new TMSI Idle Current IMEISV included in IMEISV trace list?
Wait_For_ TMSI_Ack_2
New TMSI rejected New TMSI accepted Forward new TMSI ack Forward new TMSI negative response
New TMSI accepted
No Yes
New TMSI rejected Forward new TMSI negative response
Forward new TMSI ack
Invoke Tracing in RAN
Release transaction A
Location Update ack
Idle
Idle
Figure 4.1.1.1 (sheet 2 of 2): Process Update_Location_Area_MSC
3GPP
Release 11
16
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.1.2
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
Procedure Authenticate_MSC
Procedure in the MSC to obtain an authentication response from the MS and relay it to the VLR
Authenticate
Wait_For_ Auth_Response
Authenticate ack
Authenticate negative response
Release transaction
Authenticate ack
Authenticate negative response
Result:= Pass
Result:= Aborted
Figure 4.1.1.2 (sheet 1 of 1): Procedure Authenticate_MSC
3GPP
Release 11
17
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.2
4.1.2.1
Detailed procedure in the VLR

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. 2. If a successfully authenticated radio connection is already established before the Abort message is received, the VLR shall ignore the message. 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. The Automatic Device Detection (ADD) function is an optional feature that allows the HLR to be updated with the current User Equipment (IMEISV) and thus enables the network to configure the subscribers equipment based on a predefined profile. The mechanism for the IMEISV retrieval by device management system (either from HLR or VLR) is outside the scope of this specification. As an optimisation, the VLR may optionally store whether or not the HLR supports the ADD feature and use this information to decide whether or not to send an update to the HLR. The Paging Area function is an optional feature that allows the HLR to be updated with the current Paging Area (PgA) (see subclause 2.6). If supported, whenever the paging area changes, the VLR shall send a MAP Update Location request with the Paging Area parameter set to the location areas belonging to the new paging area. The Paging Area is then sent by the HLR (if available) to the VLR in the MAP Provide Roaming Number and may be used for paging optimisation after a MSC/VLR restart (see 3GPP TS 23.018 [5a]). Sheet 1: The usage of a Hop Counter is an optional optimization. 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. Sheet 2: : The execution of the test "HLR supports ADD?" and the action "set: skip subscriber data update" is an optional optimisation and depends on the presence of the relevant indication from the HLR that ADD functionality is supported. If this optimisation is not supported on the VLR or no indication is received, both are bypassed in which case processing continues at connector 4. Sheet 2: The execution of the test "HLR supports PgA?" and the action "set: skip subscriber data update" depends on the presence of the relevant indication from the HLR that PgA functionality is supported. Sheet 2: The "Subscriber data dormant" flag is an optional parameter that shall at least be supported by VLR implementing the Mobile Terminating Roaming Retry feature (see 3GPP TS 23.018 [5a]). A VLR not supporting this flag shall behave as if the flag is set to false. Sheet 2: A VLR supporting the Mobile Terminating Roaming Retry feature sets the "Cancel Location received" flag to false after authenticating the radio connection. This is used to determine whether to trigger MT roaming retry upon receipt of an incoming call, see subclause 7.3.2.1 of 3GPP TS 23.018 [5a]. Sheet 3: the procedure Obtain_IMSI_VLR is specified in 3GPP TS 23.018 [5a]. The type of Location Update is retrieved in 3GPP TS 23.078 [11] procedure Set_Notification_Type and is returned into the Notify variable; this information is necessary for the CAMEL Mobility Management event notification procedure 3GPP TS 23.078 [11] Notify_gsmSCF.
3GPP
Release 11
18
3GPP TS 23.012 V11.1.1 (2012-09)
process Update_Location_Area_VLR
Process in the VLR to handle an incoming Update Location Area Request, and trigger the correct application process Idle
ULA_VLR1(4)
Signals to/from the left are to/from the MSC
Update Location Area
Retrieve_ IMEISV_If_ Required Result= Pass? Yes PUESBINE supported? No Yes Send UESBI-Iu to Access Network
No
PUESBINE supported?
Yes Update Location Area negative response
No IMSI
Identity used? TMSI Previous No LAI in this VLR? Yes
Idle No Subscriber known in VLR? Yes No Previous LAI in this VLR? Yes NRI received from MS? Yes NRI allocated by this VLR? No Location info confirmed in HLR:=False No No
TMSI known? Yes MSC area change? Yes Location info confirmed in HLR:=False No Subscriber tracing active? Yes Trace subscriber activity
No Subscriber data confirmed by HLR:=False No Location info confirmed in HLR:=False PVLR address derivable? Yes IuFlex supported? No Yes Set Hop Counter to maximum value
Yes
Figure 4.1.2.1 (sheet 1 of 3): Process Update_Location_Area_VLR
3GPP
Release 11
19
3GPP TS 23.012 V11.1.1 (2012-09)
Process in the VLR to handle an incoming Update Location Area Request, and trigger the correct application process 1
ULA_VLR2(4)
Signals to/from the left are to/from the MSC; signals to/from th e right are to/from the ARC timer application process
No
Auth entication required? Yes Auth enticate_ VLR No
Confirmed by Radio contact:=True Yes Update LAI
Result= Pass?
Result?
Aborted Illegal Subscriber set Subscriber data dormant :=false Idle
Unknown Subscriber Delete subscriber record Procedure Error
set Cancel Location Received :=false B Yes HLR upda te need ed? No ADD supported? Yes 4 IMEISV changed? Yes Check for ADD support? Yes HLR supports ADD? Yes A set: skip subscriber data update No No No IMEISV or PgA to send ? No Yes
Set nega tive response: Illegal subscriber Location_ Update_ Completion_VLR Result= Pass? No
Set nega tive response: Unknown subscriber Update Location Area negative response
Set nega tive response: Syate m failure
Yes Idle Update register See 3GPP TS 23.07 8
Set_ Notification_ Type Notify_ gsmSCF
No
See 3GPP TS 23.07 8
Auth enticated Radio Contact Established
Idle IMEISV to send A
3GPP
Release 11
20
3GPP TS 23.012 V11.1.1 (2012-09)
Process in the VLR to handle an incoming Update Location Area Request, and trigger the correct application process Yes 4
ULA_VLR3(4)
In the upper subtree, signals to/from the left are to/from the MSC; signals to/from the right are to/from the ARC timer application process
Unknown HLR? No Update_ HLR_VLR
Result?
Roaming not allowed Unknown Subscriber Delete subscriber record Set negative response: Roaming not allowed Delete subscriber record Set negative response: Unknown subscriber
Abort No
Procedure Error Standalone mode? Yes
Pass
Location_ Update_ Completion_VLR
Set negative response: Syatem failure
Location_ Update_ Completion_VLR
In the lower subtree, signals to/from the right are to/from the PVLR
Subscriber data Update confirmed by Location Area negative HLR:=False response
No
Result= Pass? Yes
Send Identification
Idle Update register Set_ Notification_ Type Notify_ gsmSCF Authenticated Radio Contact Established
Wait_For_ PVLR_Response
See 3GPP TS 23.078
Send Identification ack
Send Identification negative response
See 3GPP TS 23.078
Obtain_ IMSI_VLR No
See 3GPP TS 23.018
Idle Result= Pass? Yes
Idle
3GPP
Release 11
21
3GPP TS 23.012 V11.1.1 (2012-09)
Process in the VLR to handle an incoming Update Location Area Request, and trigger the correct application process
ULA_VLR4(4)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the ARC timer application process A
PgA supported? Yes PgA changed? Yes HLR supports PgA? Yes set: skip subscriber data update
No
No
No
PgA to send
3GPP
Release 11
22
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.2.1a
Procedure Retrieve_IMEISV_If_Required
The decision box "received IMEISV = stored IMEISV" takes the "No" exit if no IMEISV is stored.
procedure Retrieve_IMEISV_If_Required
Procedure in the VLR to retrieve IMEISV if required
R_IMEISV_IR1(1)
No Yes
Location Update Type= Periodic Location Update?
No
IMEISV stored?
Provide IMEI
See 3GPP TS 23.018
Yes
Wait_For_ IMEI
Abort
Provide IMEI ack
See 3GPP TS 23.018 ADD supported?
Yes No received IMEISV := stored IMEISV? Yes
No IMEISV changed := True
Store IMEISV
Result:= Fail
Result:= Pass
Figure 4.1.2.1A: Procedure Retrieve_IMEISV_If_Required
3GPP
Release 11
23
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.2.2
Procedure Authenticate_VLR
Sheet 2: The procedure Obtain_IMSI_VLR is specified in 3GPP TS 23.018 [5a].
Procedure in the VLR to authenticate an MS via the MSC Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR.
AUT_VLR1(2)
Authentication sets available? No
Yes
Obtain_ Authentication_ Sets_VLR
No Yes Result= Aborted? No
Result= Pass? Yes
Authenticate Result:= Aborted Yes Result= Procedure Error? No Result:= Procedure Error Result:= Unknown Subscriber
Wait_For_ Authenticate_ Result
Authenticate ack No Yes More authentication sets needed? No Yes Fetch_ Authentication_ Sets_VLR More authentication sets needed?
Authenticate negative response Authentication Failure Report
Received SRES= expected SRES?
No Yes
Authentication accepted
Fetch_ Authentication_ Sets_VLR
Result:= Pass
Result:= Aborted
Figure 4.1.2.2 (sheet 1 of 2): Procedure Authenticate_VLR
3GPP
Release 11
24
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure in the VLR to authenticate an MS via the MSC Signals to the left are to the MSC. Identity=IMSI? No Retry with IMSI? Yes 1
AUT_VLR2(2)
Yes
No
Obtain_ IMSI_VLR
No
Result= Pass? Yes
No
IMSI known? Yes IMSI matches TMSI? No
Yes Authentication rejected Authentication Failure Report
Authentication accepted
Result:= Aborted
Result:= Unidentified Subscriber
Identity:= IMSI
Result:= Illegal Subscriber
Figure 4.1.2.2 (sheet 2 of 2): Procedure Authenticate_VLR
3GPP
Release 11
25
3GPP TS 23.012 V11.1.1 (2012-09)
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 "Access-Restriction-Data permits current RAT?" performs a check on the subscribers AccessRestrictionData information received from the HLR and either allows the operation to continue or rejects the Location Update. The decision is taken according to the following: -If AccessRestrictionData value includes "GERAN not allowed" and the LA/RA, where the MS accesses the network, is served by GERAN, then the subscribers access is not permitted. -If AccessRestrictionData value includes "UTRAN not allowed" and the LA/RA, where the MS accesses the network is served by UTRAN, then the subscribers access is not permitted. Sheet 1: When the Location Update is not allowed because the subscriber access is restricted due to Administrative Restriction of Subscribers Access feature, the flow results in the sending of "Update Location Area Negative Response" toward the MSC (and the MS). The recommended cause code is "RAT not allowed", but cause codes "PLMN not allowed" or "National Roaming Not allowed" may also be used based on operator configuration and the required MS behaviour. Note: For the mapping of MAP Process cause code values to values on the MM protocol interface see 3GPP TS 29.010 [14]. For the MS behaviour determined on the received cause code see 3GPP TS 24.008[13]. 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. Sheet 1: Causes "National Roaming Not Allowed" and "RAT not allowed" lead to sending of cause #13 (roaming not allowed in the Location Area) and #15 (no suitable cells in Location Area) respectively to the MS (see 3GPP TS 29.010 [14]). On receipt of cause #13 or #15 the TMSI and LAI currently stored in the MS are not deleted (see 3GPP TS 24.008 [13]). As an option (referred-to as "TMSI option"), for these two reject causes, the VLR may forward a new TMSI (with the new LAI) together with the sending of "Update Location Area Negative Response" toward the MSC. The Location Updating Reject is sent to the MS after forwarding of the new TMSI (and new LAI) (see subclause 4.1.1.1). This optional TMSI allocation (with new LAI) ensures that: a pre-Rel-8 MS will initiate a location updating if it roams back to the previous Location Area (allowed), i.e. to the location area whose identity is already stored in the MS, after having received the reject cause #13 or #15; otherwise the location updating may not be initiated and mobile terminated calls may not be delivered until the next mobile originated activity or periodic location update (see 3GPP TR 29.994 [18]). the next location update enables the new VLR to address the correct previous VLR (which controls the not allowed Location Area) and to obtain the right IMSI and security context; otherwise a wrong VLR is addressed (corresponding to the TMSI/LAI of the VLR that controlled the previous allowed LA) and a wrong IMSI / security context would be obtained if the TMSI was reallocated.
Sheet 2: If the MS performs a location update procedure in a VPLMN supporting Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN (via Service Level Agreement) and if the VLR needs to retrieve the CSG Subscription Data of the MS from the CSS, the VLR shall initiate the Update VCSG Location
3GPP
Release 11
26
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure with the CSS and store the CSG Subscription data if any received from the CSS. The stored CSG Subscription data is used by VLR to perform access control for the MS. If the Update VCSG Location Procedure fails, the VLR continues the location update procedure. Sheet 3: The procedure Check_IMEI_VLR is specified in 3GPP TS 23.018 [5a].
3GPP
Release 11
27
3GPP TS 23.012 V11.1.1 (2012-09)
procedure Location_Update_Completion_VLR
Procedure in the VLR to complete L ocation Update
LUC_VLR1(3)
Yes No Yes No Set negative re sponse: National Roaming Not allowed Re gional subscription restriction? Yes
National roaming restrictions e xist?
Roaming restriction Due To Unsupporte d Feature rece ived in subscriber data?
No Admin istrative restriction of su bscribers' access feature supported? No Yes No Yes Yes 1 AccessRestrictionData permits cu rren t RAT? AccessRestrictionData parameter available?
Set negative re sponse: Location Area Not Allowed
No Set negative response: RAT not allo wed
LA Allowed:= False
Result=Pass
Update Re gister Set Ciphering Mode Yes Cause 'National roaming not allowed' or 'R AT not allowed' and TMSI option supported ? No Update Location Area ne gative response
New TMSI & LAI
Update Location Area ne gative response WAIT_FOR_ TMSI_C nf
Figure 4.1.2.3 (sheet 1 of 3): Procedure Location_Update_Completion_VLR
3GPP
Release 11
28
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure in the VLR to complete Location Update
LUC_VLR2(3)
Autonomous CSG supported in VPLMN and allowed by HPLMN Yes Update_VCSG_ Location_VLR
Serving cell? Hybrid cell Normal cell Indicate CSG membership status CSG Id of the serving cell in the subscribed CSGs? No CSG cell
Set negative response: Not allowed for this CSG
3GPP
Release 11
29
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure in the VLR to complete Location Update 2
LUC_VLR3(3)
LA Allowed:= True
IMSI Detached:= False
Subscriber_ Present_VLR
See TS 29.002
Trace_Subscriber_ Activity_VLR
TMSI to be reallocated? Yes Set Ciphering Mode
No
IMEI check required? Yes No
IMEI check required? No
Yes
See 3GPP TS 23.018 CHECK_IMEI_VLR CHECK_IMEI_VLR
Result? Pass Fail New TMSI Result=Pass Result=Fail Aborted Aborted Result:=Aborted
Result? Pass Fail Result=Fail Result=Pass
Update Location Area Ack
TMEI check Fail VLR Application (Detach IMSi VLR) Set negative response: Illegal Equipment Update Location Area negative response
TMEI check Fail
Update Location Area Ack
WAIT_FOR_ TMSI_Cnf
Set negative response: Illegal Equipment Update Location Area negative response
Forward new TMSI ack
3GPP
Release 11
30
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.2.4
Procedure Update_HLR_VLR
Sheet 1: The procedure Check_User_Error_In_Serving_Network_Entity is specific to Super-Charger; it is specified in 3GPP TS 23.116 [7]. Sheet 1: A VLR supporting the MT Roaming Forwarding feature (see 3GPP TS 23.018 [5a]) includes the "MTRF supported" flag in the MAP Update Location message sent to the HLR. After sending this message, the VLR may receive at any time an MT Provide Roaming Number request including the MTRF Indicator from the old VLR in the WAIT_FOR_DATA state (not represented in the SDL).
3GPP
Release 11
31
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure U pdate_H LR _VLR

HL R up da ting in VL R
U _HLR_VLR 1(1)
Sig na ls to /from th e rig ht a re t o/fro m t he H LR Sig na ls to /from th e le ft a re to /fro m t he MS C
U p dat e Lo ca tio n
W A IT_ FO R _ D ATA
Ins ert Su b sc rib er D at a
Activa te Tra ce M od e
Fo rwa rd C h eck SS In dicat ion
U p dat e L o ca tio n a ck
U pd ate L oca tion n eg ati ve respo n se
In sert_ Sub s_ D ata _ VLR
Activa te _T racin g_ VL R
Fo rwa rd C h eck SS In dicat io n
Fa ilure Ca se ?
W AIT _ FOR _ D ATA
W AIT_ FOR _ DA TA
W AIT_ FOR _ DA TA
R oa min g n ot Allow ed
Un kno w n Su bscribe r
Proced u re Erro r
A bo rt
R esult := R o am ing N ot Allow ed
R e sult: = U n know n Su bscribe r
R es ult: = Pro ced ure Error
R esu lt:= Ab ort
R esu lt := Pass
C h eck_ Use r_E rror_ I n_ Se rving _ N e two rk_E ntity
S ee TS 2 3 .1 1 6
Da ta Co nf irm ed by H L R :=T rue
D a ta C o nfirme d b y H LR := False
Loca tio n In fo Co nf irm ed in H L R: =True
L oca tion In fo C o nfirme d in H LR := F al se
Figure 4.1.2.4 (sheet 1 of 1): Procedure Update_HLR_VLR
3GPP
Release 11
32
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.2.5
Procedure Insert_Subs_Data_VLR
The procedure Check_Parameters is specified in 3GPP TS 23.018 [5a].
Procedure Insert_Subs_Data_VLR
Procedure to receive and store subscriber data in the VLR
Insert_Subs_Data_VLR(1)
Signals to/from the right are to/from the HLR
Check_Parameters
See TS 23.018
Result= Pass? No Yes
All received features & services supported ?
No
Yes
Update Subscriber Data
Update subscriber data for supported feature(s)
Set parameters for unsupported features
MSC area restricted by regional subscription?
Yes
No
Set MSC Area Restricted
Insert Subscriber Data Ack
Insert Subscriber Data negative response
Figure 4.1.2.5 (sheet 1 of 1): Procedure Insert_Subs_Data_VLR
3GPP
Release 11
33
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.2.6
Procedure Activate_Tracing_VLR
Procedure Activate_Tracing_VLR
Handling the Activate Trace Mode in the 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? Yes
No
Subscriber Known? No Yes
Tracing supported No Yes
Set negative response Facility not supported
Set negative response Unidentified subscriber
Tracing buffer full? No No Set negative response Tracing buffer full
Set Subscriber Tracing := Active
Active Trace Mode Ack
Active Trace Mode negative response
Figure 4.1.2.6 (sheet 1 of 1): Procedure Activate_Tracing_VLR
3GPP
Release 11
34
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.2.7 Process Send_Identification_PVLR

Sheet 1: The procedure Check_Parameters is specified in 3GPP TS 23.018 [5a]. Sheet 1: Decision "IuFlex applied?" distinguishes whether or not the PVLR applies "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" as described in 3GPP TS 23.236 [12]. If this feature is applied, the VLR shall extract the NRI from the TMSI and attempt to derive the VLR address of the VLR where the subscriber was previously registered, denoted in the following as the "real PVLR". Sheet 1: Decision "Result = success?" distinguishes whether the NRI could be successfully converted into the "real PVLR" address. In case of successful conversion, the PVLR shall relay the received Send_Identification message to the "real PVLR" as specified in 3GPP TS 23.236 [12]. The new VLR and the "real PVLR" shall not perceive that relaying is being performed, i.e. they shall not notice the presence of the relaying node. The actual mechanism used to perform the relay is an implementation choice. A possible mechanism is described in section 4.1.2.9. Sheet 1: If supported by the VLR, the "Subscriber data dormant" flag shall be set to true to reflect that the MS has moved outside the VLR area. A VLR not supporting this flag shall behave as if the flag is set to false. NOTE: HLRs compliant with this release of the specification and supporting mobile terminating roaming retry and Super-Charger will always send a Cancel Location message to the old VLR even in a supercharged network (see 3GPP TS 23.018 [5a]). HLRs compliant with an earlier release of the specification may not always send a Cancel Location message in a supercharged network. To support mobile terminating roaming retry with such HLR implementations, the old VLR can start a timer upon receipt of the MAP Send Identification message while on-going paging to trigger the sending of an internal Cancel Location to the old MSC and thus the sending of a MAP Resume Call Handling message by the old MSC to the GMSC after the sending of the MAP Update Location by the new VLR to the HLR.
3GPP
Release 11
35
3GPP TS 23.012 V11.1.1 (2012-09)
process Send_Identification_PVLR
Handling of the Send Identifiction in the Previous VLR (PVLR)
SI_PVLR1(1)
Signals to/from the left are to/from the new VLR
Idle
Send Identification
Check Parameters No
Result = Pass? Yes TMSI Known? Yes Set IMSI
No
IuFlex applied? Yes
No
set Subscriber data dormant := true No
Extract NRI from TMSI
Authentication sets available? Yes Set Authentication Info
Convert NRI Into VLR Address
Result = Success? Yes
No
Send Current Security Context Yes Set Current Security Context Send Identification ack
Perform_Relaying
No Set negative response unidentified subscriber
Idle
Figure 4.1.2.7 (sheet 1 of 1): Process Send_Identification_PVLR
3GPP
Release 11
36
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.2.8
Process Trace_Subscriber_Activity_VLR
1(1)
Sig na ls to /from th e le ft are to/ from th e M SC
Pro cedure Trace_S ubscriber_Activity_VLR

Proce du re in th e V LR to jud ge w h eth er to sen d tra ce su b scrib er a ctivity or n ot
S ub scrib er Tra ce= a ctive ?
No
Yes
T ra ce S ub scrib er A ctivity
Figure 4.1.2.8 (sheet 1 of 1): Process Trace_Subscriber_Activity_VLR
4.1.2.9
Procedure Perform Relaying
The relay may be performed by opening a new MAP dialogue to the "real PVLR" and keeping it linked to the existing MAP dialogue between the new VLR and the PVLR. Every message received for one of these dialogues shall be relayed to the other one, until the two dialogues are closed. This mechanism is described in figure 4.1.2.9. In order to improve the signalling efficiency of the relaying function, alternative mechanisms may be implemented as long as no difference shall be perceived by the new VLR and the "real PVLR".
3GPP
Release 11
37
3GPP TS 23.012 V11.1.1 (2012-09)
The usage of a Hop Counter is an optional optimization.
procedure Perform_Relaying
Procedure to perform the relaying of the Send Identification message from/to the new VLR and the "real PVLR", as specified in 3GPP TS 23.236 "Intra Domain Connection of RAN Nodes to Multiple CN Nodes
PR_PVLR1(1)
Signals to/from the left are to/from the new VLR. Signals to/from the right are to/from the "real PVLR".
No
Hop Counter received?
Yes Yes Received Hop Counter = 0?
No
Set Hop Counter to maximum -1
decrement Hop Counter
Prepare Send Identification
The Send Identification message is prepared by copying all parameters (except Hop Counter) received with Send Identification from the new VLR
Send Identification
Sent to the "real PVLR identified by means of the NRI extracted from TMSI, as specified in 3GPP TS 23.236
Wait for Send Identification Result
Send Identification Ack
The Send Identification Ack is prepared by copying all parameters received with Send Identification Ack from the "real PVLR"
Prepare Send Identification Ack
Prepare Send Identification negative response
The Send Identification negative response is prepared by copying all parameters received with Send Identification negative response from the "real PVLR"
Set Error: Unidentified Subscriber
Send Identification Ack
Figure 4.1.2.9 (sheet 1 of 1): Procedure Perform Relaying
4.1.2.10
Procedure Update_VCSG_Location_VLR
The VLR uses this procedure to register the MS with the CSG Subscriber Server and may retrieve the CSG subscription data from CSS. When using this procedure, the VLR sends an Update VCSG Location request towards the CSS, and waits for the answer from the CSS.
3GPP
Release 11
38
3GPP TS 23.012 V11.1.1 (2012-09)
If the VLR receives a negative Update VCSG Location response from the CSS, the VLR sets the result with failure cause and ends this procedure. If the VLR receives an Insert VCSG Subscriber Data request, it shall update the CSG Subscription Data and returns a response message to CSS. The CSG Subscription Data received from the CSS is stored and managed in the VLR independently from the CSG Subscription Data received from the HLR. If the same CSG ID exists in both CSG Subscription Data from the CSS and CSG Subscription Data from the HLR, the CSG Subscription Data from the HLR shall take precedence over the CSG Subscription Data from the CSS. If the VLR receives a successful Update VCSG Location ACK message, it ends the procedure. If the successful Update VCSG Location ACK message indicates that there is no CSG Subscription data, the VLR shall not send any subsequent Update VCSG Location Request message to the CSS.
3GPP
Release 11
39
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure Update_VCSG_Location_VLR
Prodedure in VLR to handle the VCSG location updating with CSS
UVL_VLR1(1)
Signals to/from the right are to/from the CSS
Update VCSG Location req
wait for CSS response
update VCSG location ACK
insert VCSG subs req
update VCSG location negative response
Result= pass update VCSG subscription data
Failure cause? unknown subscriber procedure error Result= procedure error
Abort
Result= unknown subscriber
Result= Abort
insert VCSG subs ACK
wait for CSS response
Figure 4.1.2.10 (sheet 1 of 1): Procedure Update_VCSG_Location_VLR
4.1.2.11
Procedure Insert_VCSG_Subs_Data_VLR
Whenever the CSG subscription data is changed for a MS in the CSS, and the changes affect the CSG subscription data stored in the VLR, the CSS shall inform the VLR about the changes by the means of an Insert VCSG Subscriber Data request (IMSI, CSG subscription data) which initiates the procedure Insert_VCSG_Subs_Data_VLR. The VLR checks the received parameters. If the MS is unknown, the VLR shall send a negative Insert VCSG Subscriber Data response message to the CSS that deregisters the VLR for this MS. If the MS is known, the VLR shall update the stored CSG subscription data and acknowledge the Insert VCSG Subscriber Data request by returning an Insert VCSG Subscriber Data Ack.
3GPP
Release 11
40
3GPP TS 23.012 V11.1.1 (2012-09)
The CSG Subscription Data received from the CSS is stored and managed in the VLR independently from the CSG Subscription Data received from the HLR. The Insert VCSG Subscriber Data procedure shall only affect the CSG Subscription Data received from the CSS. If the same CSG ID exists in both CSG Subscription Data from the CSS and CSG Subscription Data from the HLR, the CSG Subscription Data from the HLR shall take precedence over the CSG Subscription Data from the CSS.
procedure Insert_VCSG_Subs_Data_VLR
Procedure to receive and store VCSG subscriber data in the VLR
1(1)
Signals to/from the right are to/from the CSS
Check_Parameters
See TS 23.018
Result= pass? Yes Update VCSG subscriber data
No
Insert VCSG subscriber data Ack
Insert VCSG subscriber data negtive response
Figure 4.1.2.11 (sheet 1 of 1): Procedure Insert_VCSG_Subs_Data_VLR
3GPP
Release 11
41
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.3
4.1.3.1
Detailed procedure in the HLR

Process Update_Location_HLR
The Paging Area function is an optional feature that allows the HLR to be updated with the current Paging Area (PgA) (see subclause 2.6). If supported, the HLR shall store the Paging Area received from the VLR in MAP Update Location requests. If the Paging Area parameter is not included in a MAP Update Location request and the VLR has not changed, the HLR shall keep the stored Paging Area. If the Paging Area parameter is not included in a MAP Update Location request and the VLR has changed, the HLR shall delete the stored Paging Area. Sheet 1: The procedure Check_Parameters is specified in 3GPP TS 23.018 [5a]. Sheet 1: The procedure Super_Charged_Cancel_Location_HLR is specific to Super-Charger; it is specified in 3GPP TS 23.116 [7]. Sheet 2: The procedure Super_Charged_Location_Updating_HLR is specific to Super-Charger; it is specified in 3GPP 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?". Sheet 2: The execution of the test "skip subscriber data update?" is optional and depends on the presence of the relevant indication from the VLR. If no indication is received, then the result of the test is "No". The HLR may additionally skip the procedures Update_Routing_Info and Control_Tracing_HLR if this indication is received from the VLR. Sheet 2: If the HLR supports the Administrative Restriction of Subscribers Access feature and roaming is allowed in the VPLMN then the HLR may check the "Supported RAT Types" received from the VLR against the access restriction parameters. If this check fails then the decision box "Roaming allowed in this PLMN" shall take the exit "No".
3GPP
Release 11
42
3GPP TS 23.012 V11.1.1 (2012-09)
Process U pdate_Location_HLR
Proces s In th e H L R App licatio n to h an dlle L oca tion U pd atin g Sig na ls to /from th e le ft a re to /fro m th e VLR
1(3)
I DL E
U p da te L oca tio n
C h eck_ P aram ete rs
Se e TS 2 3.0 18
No R e sult = P ass? Yes No S ub scrib er K now n ?
S ubs crib er Tra cin g A ctive in V LR = False
Yes N e tw ork A cc ess M od e= GP RS O nly?
No Yes N e w VLR ? S et ne ga tive re spo nse : U nk now n S ub sc rib er
No Su per_ C harg ed _ Ca n cel_L oc atio n_ HL R Se e TS 23 .11 6
Re sult : Pa ss? No
Ye s
U pd ate L oca tion N eg at ive R es po nse
Ca n ce l_L oca tio n_ HL R
ID L E
Figure 4.1.3.1 (sheet 1 of 3): Process Update_Location_HLR
3GPP
Release 11
43
3GPP TS 23.012 V11.1.1 (2012-09)
process Update_Location_HLR
Process in the HLR Application to handle Location Updating 1
2(3)
Signals to/from the left are to/from the VLR
Subscriber Allowed to Roam into PLMN? Yes Update Routeing Info Reset Flag MS Purged Control_ Tracing_ HLR Result = Pass? Yes Super_Charged_ Location_Updating_ See TS 23.116 HLR
No Set Negative Response: Roaming Not Allowed
Delete Routeing Info
Update Location Negative Response
No
IDLE
IDLE
Result = Pass? No Yes MSC Area Restricted? or Roaming Restricted Due to Unsupported Feature? ADD or PgA supported Yes No Subscriber_Present_ HLR No Yes skip subscriber data update? No Insert_ Subscriber_ Data_HLR Result = Pass? Yes No Result = Aborted? No Update Location Negative Response IDLE Yes
Yes
3GPP
Release 11
44
3GPP TS 23.012 V11.1.1 (2012-09)
Process Update_Location_HLR
Process In the HLR Application to handlle Location Updating Signals to/from the left are to/from the VLR
3(3)
True Check_SS_ Required
False
Forward Check SS Indication
Check_SS_ Required:= False
Update Location Ack
Location Updating Complete
To Process CCBS_ Coordinator_HLR See 3GPP 23.093
Idle
3GPP
Release 11
45
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.3.2
Procedure Insert_Subscriber_Data_HLR
1(2)
Procedure in the HLR Application for handling the insertion of subscriber data into the VLR
Insert Subscriber Data
Count:=1
3 Yes
More Data To Send?
No Insert Subscriber Data
Count:= Count + 1
WAIT_FOR_ ISD_Ack
ISD_Ack
Abort
ISD Negative Response
Count:= Count - 1
Result:= Aborted
Set Negative Response System Failure
Result:= Fail
Figure 4.1.3.2 (sheet 1 of 2): Procedure Insert_Subscriber_Data_HLR
3GPP
Release 11
46
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure in the HLR Application for handling the insertion of subscriber data into the VLR
2(2)
Yes Any services not supported in VLR? No Ignore Unsupported Service? Yes No
Replace Service In VLR? No Yes
MSC Area Restricted? Yes No No
Unsupported Service Critical? Yes
Replace Service
Set MSC Area Restricted
HLR Internal Action
Count>0? No Yes Roaming Restricted Due To Unsupported Feature=True; MSC Area Restricted= True 2
WAIT_FOR_ ISD_Ack
More data to send? Yes No Result:= Pass
Figure 4.1.3.2 (sheet 2 of 2): Procedure Insert_Subscriber_Data_HLR
3GPP
Release 11
47
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.3.3
Process Subscriber_Present_HLR
The macro Alert_Service_Centre_HLR is specified in 3GPP TS 29.002 [8].
process Subscriber_Present_HLR
Process in the HLR to alert SMS service centres if required as part of the location updati ng process
SP_HLR1(1)
No Message Waiting Data set? Yes
Alert_Service_ Centre_HLR
See 3GPP TS 29.002
Figure 4.1.3.3: Process Subscriber_Present_HLR
3GPP
Release 11
48
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.3.4
Procedure Control_Tracing_HLR
1(1)
Signal to/from the left are to/from the VLR
Procedure Control_Tracing_HLR
Procedure for controlling Tracing in the HLR Application
Subscriber Tracing active in HLR? Yes Subscriber Tracing active in VLR? No Subscriber in HPLMN area? Yes Active Trace Mode
Result:=Pass
WAIT_FOR_ ATM_RESULT
ATM_ack
ATM Negative Response
Set Subscriber Tracing Active in VLR
Set Subscriber Tracing inactive in VLR
Report Error To O&M Center Result:=Pass Failure Cause?
Provider Error Result:=Fail
Data Error
User Error Result:=Pass
Result:=Pass
Figure 4.1.3.4 (sheet 1 of 1): Procedure Control_Tracing_HLR
4.1.4
4.1.4.1
Detailed procedure in the CSS

Process Update_VCSG_Location_CSS
The Update_VCSG_Location_CSS process takes place when the VLR needs to register the MS with the CSS and retrieve the CSG Subscription Data of the MS from the CSS.
3GPP
Release 11
49
3GPP TS 23.012 V11.1.1 (2012-09)
The CSS receives an Update VCSG Location Request from the VLR. If the MS is unknown in the CSS, and if the CSS supports creating the temporary empty subscription data for the MS, the CSS should create subscription data and sends successful update VCSG Location ACK message, otherwise the CSS shall sends a negative Update VCSG Location response message. If the MS is known in the CSS, the CSS stores the received VLR number and initiates the Process Insert_VCSG_Subs_Data _CSS and at the end of the process acknowledges the Update VCSG Location request by sending an Update VCSG Location ACK message to the VLR.
Process Update_VCSG_Location_CSS
Process in the CSS to handle the VCSG Location Updating Signals to/from the left are to/from the VLR
idle
Update VCSG Locatoin Req
Check parametes
See TS 23.018
Result=Pass? No Yes Yes Subscriber Known? No Create Empty Subscription Data? Yes
Has Subscriber Data? No Yes Insert the VCSG Subscriber Data No
Set negative response Unknown Subscriber
Result= Pass? Yes
No
Result= Aborted? Yes Update VCSG Locaton Negative Response Update VCSG Locaton Ack Update VCSG Locaton Ack
No Update VCSG Locaton Negative Response Update VCSG Locaton Ack
idle
Figure 4.1.4.1 (sheet 1 of 1): Process Update_VCSG_Location_CSS
3GPP
Release 11
50
3GPP TS 23.012 V11.1.1 (2012-09)
4.1.4.2
Procedure Insert_VCSG_Subs_Data_CSS
Whenever the CSG subscription data is changed for a MS in the CSS, and the changes affect the CSG subscription data stored in the VLR, the CSS initiates the Procedure Insert_VCSG_Subs_Data_CSS. The Procedure Insert_VCSG_Subs_Data_CSS is also triggered by the Update_VCSG_Location_CSS process as specified in subclause 4.1.4.1. When executing this procedure, the CSS sends an Insert VCSG Subscriber Data Request containing the CSG Subscription Data of the MS to the VLR and waits for the response from the VLR. If the VLR successfully updates the received CSG Subscription Data from the CSS, it acknowledges the Insert VCSG Subscriber Data Request by returning an Insert VCSG Subscriber Data Ack. The CSS may wait for each request to be acknowledged before it ends the procedure. If the CSS receives a negative response from the VLR, it sets the result with failure cause and ends this procedure.
3GPP
Release 11
51
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure in the CSS for handling the insertion of VCSG subscriber data in to the VLR
1(2)
Insert VCSG Subscriber Data
Count:=1 2
Yes
More Data To Send? No
Insert VCSG Subscriber Data
Count:= Count+1 WAIT_For_ IVSD_Ack
IVSD_Ack
Abort
IVSD Negative Response
Count:= Count-1
Result:= Aborted
Set Negative Response System Failure
Result:= Fail
Figure 4.1.4.2 (sheet 1 of 2): Procedure Insert_VCSG_Subs_Data_CSS
3GPP
Release 11
52
3GPP TS 23.012 V11.1.1 (2012-09)
Procedure in the CSS for handling the insertion of VCSG subscriber data in to the VLR 1 Signals to/from the right are to/from the VLR
2(2)
Count>0? No Yes WAIT_FOR_ IVSD_Ack More data to send? No Result:= Pass
Yes
Figure 4.1.4.2 (sheet 2 of 2): Procedure Insert_VCSG_Subs_Data_CSS
3GPP
Release 11
53
3GPP TS 23.012 V11.1.1 (2012-09)
4.2
4.2.1
4.2.1.1
Location Cancellation
Process Cancel_Location_VLR
The procedure Check_Parameters is specified in 3GPP TS 23.018 [5a]. Sheet 1: If supported by the VLR, the "Subscriber data dormant" flag shall be set to true to allow triggering Mobile Terminating Roaming Retry. A VLR not supporting this flag shall behave as if the flag is set to false. Sheet 1: A VLR not supporting the Mobile Terminating Roaming Retry feature and the Mobile Terminating Roaming Forwarding fearture (see 3GPP TS 23.018 [5a]) may not send Cancel Location to MSC. Sheet 1: A VLR supporting the Mobile Terminating Roaming Retry feature sets the "Cancel Location received" flag to true when receiving the Cancel Location message from the HLR. This is used to determine whether to trigger MT roaming retry upon receipt of an incoming call, see subclause 7.3.2.1 of 3GPP TS 23.018 [5a]. Sheet 1: A VLR supporting the Mobile Terminating Roaming Forwarding feature may include the MTRF Supported And Authorized flag or the MTRF Supported And Not Authorized flag in the Cancel Location message it sends to the MSC if received in the Cancel Location message from the HLR.
3GPP
Release 11
54
3GPP TS 23.012 V11.1.1 (2012-09)
process Cancel_Location_VLR
Handling of Cancel Location in the VLR
1(2)
Signals to/from the right are to/from the HLR; signals to/from the left are to/from the MSC
Cancellation Type = Yes Subscription Withdrawn No MSRN allocated and CFNR active No Idle
Cancel Location set Subscriber data dormant := true Check_Parameters set Cancel Location received := true Result= Pass? Yes Subscriber registered Yes delayed deletion of subscriber record supported Yes No No No See TS 23.018
Mark subscriber detached
configurable value, e.g. 2min
Start Timer Tx
Release TMSI
Cancel Location ack
Cancel Location Delete subscriber from register Release TMSI Cancel Location negative response
Wait for timeout
Send Info for incomming call (MSRN) Stop timer Tx
timeout Tx
Update Location Area Stop timer Tx
Cancel Location ack Idle Cancel Location 2
Delete subscriber from register
Idle
Figure 4.2.1.1 (Sheet 1 of 2): Process Cancel_Location_VLR
3GPP
Release 11
55
3GPP TS 23.012 V11.1.1 (2012-09)
process Cancel_Location_VLR
Handling of Cancel Location in the VLR
2(2)
MT Roaming Retry supported Yes No GMSC supports MT Roaming Retry Yes set MT Roaming Retry Indicator perform call forwarding
No
Send Info for Incoming Call Ack
Figure 4.2.1.1 (Sheet 2 of 2): Process Cancel_Location_VLR
3GPP
Release 11
56
3GPP TS 23.012 V11.1.1 (2012-09)
4.2.2
4.2.2.1

Process Cancel_Location_HLR
1(1)
Process Cancel_Location_HLR
Process in the HLR application to initiate cancellation of location registration in a VLR
Cancel Location
WAIT_FOR_ ACK
Cancel Location Ack
Abort
Cancel Location Negative Response
Repeat Location Cancellation? Yes No
Wait for time expiry
Figure 4.2.2.1: Process Cancel_Location_HLR
3GPP
Release 11
57
3GPP TS 23.012 V11.1.1 (2012-09)
3GPP
Release 11
58
3GPP TS 23.012 V11.1.1 (2012-09)
4.2A
4.2A.1
4.2A.1.1
VCSG Location Cancellation

Process Cancel_VCSG Location_VLR
3GPP
Release 11
59
3GPP TS 23.012 V11.1.1 (2012-09)
process Cancel_VCSG_Location_VLR
Handling of Cancel VCSG Location in the VLR Signals to/from the right are to/from the CSS;
1(1)
Idle
Cancel VCSG Location
Check_Parameters
See TS 23.018
Result= Pass? Yes
N o
Subscriber VCSG registered
Yes
N o
Delete subscriber VCSG Registered and CSG subscription data Release TMSI Cancel VCSG Location negative response
Cancel VCSG Location ack
Idle
Cancel VCSG Location
Idle
Figure 4.2A.1.1 (Sheet 1 of 1): Process Cancel_VCSG_Location_VLR
3GPP
Release 11
60
3GPP TS 23.012 V11.1.1 (2012-09)
4.2A.2
4.2A.2.1
Detailed procedure in the CSS

Process Cancel_VCSG Location
If the CSS determines to delete the registration of the MS which does not have the valid CSG subscription data, the CSS shall send the Cancel VCSG Location to the VLR. NOTE: How the CSS determines when to remove the registration of the MS is implementation dependent.
3GPP
Release 11
61
3GPP TS 23.012 V11.1.1 (2012-09)
Process Cancel_VCSG_Location
Process in the CSS application to initiate cancellation of VCSG location registration in a VLR Signals to/from the left are to/from the VLR
1(1)
Cance VCSGl Location
WAIT_FOR_ ACK
Cancel VCSG Location Ack
Abort
Cancel VCSG Location Negative Response
Repeat VCSG Location Cancellation? Yes No
Wait for time expiry
Figure 4.2A.2.1: Process Cancel_Location_CSS
3GPP
Release 11
62
3GPP TS 23.012 V11.1.1 (2012-09)
4.3
4.3.1
4.3.1.1
Detach IMSI
Detailed procedure in the MSC
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
Process Detach_IMSI_MSC
Process in the MSC to handle an IMSI detach
Idle
IMSI detach
Explicit IMSI detach
Idle
Figure 4.3.1.1 (Sheet 1 of 1): Process Detach_IMSI_MSC
3GPP
Release 11
63
3GPP TS 23.012 V11.1.1 (2012-09)
4.3.2
4.3.2.1

Process Detach_IMSI_VLR
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 procedure "Notify_gsmSCF" is specified in 3GPP TS 23.078 [11]. The "Notify" parameter indicates whether the IMSI detach was explicit or implicit.
3GPP
Release 11
64
3GPP TS 23.012 V11.1.1 (2012-09)
Process Detach_IMSI_VLR
Process in the VLR to handle an Detach IMSI timer
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
From Process Update_ Location_Area_VLR or Procedure Process_ Access_Request
From VLR application when IMEI check failed Idle
Authenticated Radio Contact Established
Authenticated Radio Contact terminated
IMEI check fail
Timer Expired
Explicit IMSI detach
Notify = implicit IMSI detach
Notify = explicit IMSI detach
Notify_gsmSCF
Procedure defined in 3G TS 23.078
Stop timer Reload timer
IMSI Detached =False
IMSI Detached =True
Restart timer
Stop timer
Idle
Idle
Idle
Figure 4.3.1.1 (Sheet 1 of 1): Process Detach_IMSI_VLR
3GPP
Release 11
65
3GPP TS 23.012 V11.1.1 (2012-09)
4.4
4.4.1
4.4.1.1
Purge MS
Procedure Purge_MS_VLR
Sheet 1: The procedure Purge_MS_In_Serving_Network_Entity is specific to Super-Charger; it is specified in 3GPP 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?".
3GPP
Release 11
66
3GPP TS 23.012 V11.1.1 (2012-09)
Pro cess Purge_MS_ VLR

Proces s in t he VL R to p urg e M S. Sig nal s to /from th e rig ht a re to/ from th e HL R
1(1)
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_I n_ S ervin g_ Ne tw ork_ E ntity
S ee TS 23 .11 6
Yes
R e su lt:= P ass? No
P urge M S
W A IT_FO R_ A CK
Purg e M S Ack
Pu rge _M S n eg ative resp o nse
De let e Sub scribe r Da ta
Se t Pu rge Fa ile d
TMS I t o b e frozen ? No
Ye s
Fre eze TM SI
Set Purg ing Suc ce ssfu l
O&M Pu rge MS ack
O &M Purg e M S n eg ative resp o nse
Idle
Id le
Figure 4.4.1.1 (Sheet 1 of 1): Procedure Purge_MS_VLR
3GPP
Release 11
67
3GPP TS 23.012 V11.1.1 (2012-09)
4.4.2
4.4.2.1

Process Purge_MS_HLR
The procedure Check_Parameters is specified in 3GPP TS 23.018 [5a]. 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. 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.
3GPP
Release 11
68
3GPP TS 23.012 V11.1.1 (2012-09)
Process Purge_MS_HLR
Process in the HLR Application for handling the purging of MS data from a VLR Signals to/from the left are to/from the VLR
1(1)
Idle
Purge MS
Check_ Parameters
See TS 23.018
No Result= Pass?
No
Yes Subscriber Known? Yes Purge MS Negative Response
Received VLR No. = Stored VLR No.? No Yes Set Flag MS Purged for nonGPRS
Idle
Set Negative Response= Unknown Susbcriber
Report Error to O&M
Set Flag Freeze TMSI
Purge MS Negative Response Yes No Idle Set Flag MS Purged for GPRS
Received SGSN No. = Stored SGSN No.?
Set Flag Freeze P-TMSI
Purge MS Ack.
Idle
Figure 4.4.2.1 (Sheet 1 of 1): Procedure Purge_MS_HLR
3GPP
Release 11
69
3GPP TS 23.012 V11.1.1 (2012-09)
Annex A (informative): Change history

TSG CN# Spec Version CR Apr 1999 GSM 03.12 6.0.0 CN#03 23.012 CN#06 23.012 3.0.0 001r1 CN#06 CN#07 CN#07 CN#07 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 23.012 3.0.0 3.1.0 3.1.0 3.1.0 3.2.0 3.2.1 3.3.0 4.0.0 5.0.0 5.1.0 5.1.0 5.2.0 6.0.0 6.2.0 6.2.0 6.2.0 6.3.0 7.0.0 7.0.0 7.1.0 7.2.0 7.3.0 8.0.0 8.1.0 8.2.0 9.0.0 9.1.0 9.1.0 10.0.0 10.0.0 10.1.0 11.0.0 11.0.0 11.0.0 002 003r3 004 005 Change history <Phase> New Version 3.0.0 3.1.0 3.1.0 3.2.0 3.2.0 3.2.0 3.2.1 3.3.0 4.0.0 5.0.0 5.1.0 5.2.0 5.2.0 6.0.0 6.1.0 6.2.0 6.3.0 6.3.0 7.0.0 7.1.0 7.1.0 7.2.0 7.3.0 8.0.0 8.1.0 8.2.0 9.0.0 9.1.0 10.0.0 10.0.0 10.1.0 10.1.0 11.0.0 11.1.0 11.1.0 11.1.0 Subject/Comment Transferred to 3GPP CN1 Approved at CN#03 Restructuring of MAP Location Management Procedures, Stage 2 Introduction of Super-Charger into TS 23.012 Introduction of Enhanced User Identity Confidentiality Addition of Current Security Context Data to Send_Identification_PVLR Introduction of Authentication Failure Report CR 23.012-003r3 removed because implemented in error Introduction of Mobility Management event notification into 23.012 procedures Release 4 after CN#11 Relaying of SendIdentification when IuFlex is applied Addition of procedure to retrieve UE-specific behaviour data Correction of misaligned signal names between VLR and PVLR Corrections to "Early UE" handling Include administrative restriction subscription parameter Addition of ADD feature Clarification of the Automatic Device Detection feature Introduction of Hop Counter for Send Identification Management Based Activation Impacts Enhancement of the administrative restriction of subscribers access feature Use of cause #12 in VPLMNs Skipping Update Location and Control Tracing for SkipSubscriberData Change to CANCEL_LOCATION procedure in VLR Mobile Termination whilst the MS is moving to another MSC Paging optimization with A/Iu flex TMSI re-allocation during Location Updating Reject with cause #13 or #15 MAP Update Location w/o the PgA parameter Update to Rel-9 version (MCC) Correction to Tracing Control Handling Behaviour of HLR in CS Domain MT Roaming Retry and Super Charger Mobile Terminating Roaming Forwarding Periodic LAU timer in HSS subscription Inclusion of congestion control and back-off timer for CS attach requests Retrieval of VPLMN CSG subscription information for CS domain Cancel VCSG Location Temporary empty CSG subscription data Indicator Support for MSC in Pool to avoid dual VLR registration
R99 R99 R99 R99 R99 R99 R99 Rel-4 Rel-5 Rel-5 Rel-5 Rel-5 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-7 Rel-7 Rel-7 Rel-7 Rel-7 Rel-8 Rel-8 Rel-8 Rel-9 Rel-10 Rel-10 Rel-10 Rel-10 Rel-11 Rel-11 Rel-11 Rel-11
CN#08 CN#11 CN#11 CN#20 CN#21 CN#21 CN#23 CN#24 CN#25 CN#27 CN#27 CT#31 CT#32 CT#32 CT#34 CT#36 CT#40 CT#42 CT#44 CT#46 CT#49 CT#51 CT#51 CT#52 CT#52 CT#56 CT#57 CT#57 CT#57
006
008r1 010r1 012 013r1 014r1 015r6 016r1 018r2 018r2 0020 0022 0021 0024r1 0026r2 0027r1 0029 0030r1 0034r4 0035r1 0036r1 0037r1 0038r2 0040r2 0041r1 0042r2 0043r1
3GPP
Release 11
70
3GPP TS 23.012 V11.1.1 (2012-09)
TSG CN#
Spec 23.012
Version 11.1.0
CR
Change history <Phase> New Version Subject/Comment Rel-11 11.1.1 Missing SDLs added
3GPP

3GPP TS 23.012

Uploaded by

Copyright:

Available Formats

3GPP TS 23.012

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3GPP TS 23.012

Uploaded by

Copyright:

Available Formats

3GPP TS 23.012 V11.1.

3GPP TS 23.012 V11.1.1 (2012-09)

3GPP Postal address

3GPP support office address

3GPP TS 23.012 V11.1.1 (2012-09)

General procedures in the network related to Location Management ..................................................... 9

Detailed Procedures in the network related to Location Management .................................................. 12

3GPP TS 23.012 V11.1.1 (2012-09)

Change history ............................................................................................... 69

3GPP TS 23.012 V11.1.1 (2012-09)

3GPP TS 23.012 V11.1.1 (2012-09)

3GPP TS 23.012 V11.1.1 (2012-09)

[10] [11] [11a] [12] [13] [14]

[15] [16] [17] [18] [19] [20]

3GPP TS 23.012 V11.1.1 (2012-09)

Location area and MSC area

Location area identification

IMSI detach/attach operation

Explicit IMSI detach/attach

Implicit IMSI detach

Use of the term mobile station (MS) in the present document

3GPP TS 23.012 V11.1.1 (2012-09)

General procedures in the network related to Location Management

Procedures in the VLR related to Location Updating

Procedures in the HLR related to Location Updating

Normal Location Updating and IMSI detach/attach operation

IMSI enquiry procedure

Information transfer between Visitor and Home Location Registers

Location updating procedure

Downloading of subscriber parameters to the VLR

3GPP TS 23.012 V11.1.1 (2012-09)

Location cancellation procedure

Mobile subscriber purging procedure

Congestion Control during Mobility Management

3GPP TS 23.012 V11.1.1 (2012-09)

Extended periodic LAU Signalling

Information transfer between VLR and CSG Subscriber Server

Updating VCSG Location procedure

Downloading of VPLMN CSG subscription data to the VLR

3GPP TS 23.012 V11.1.1 (2012-09)

VCSG Location cancellation procedure

Detailed Procedures in the network related to Location Management

3GPP TS 23.012 V11.1.1 (2012-09)

Sheet 2: IMEISV trace list

3GPP TS 23.012 V11.1.1 (2012-09)

Update Location Area

Wait_For_ Location_ Updating_Result

Send UESBI-Iu to Access Network

Trace subscriber activity

Convert IMEISV to UESBI-Iu

See 3GPP TS 23.195

Start activity tracing

Yes Result= Pass?

Wait_For_ Location_ Updating_Result

Wait_For_ Location_ Updating_Result

Update Location Area negative response

Update Location Area ack

Location Update reject

Location Update reject