4.7.5 Routing area updating procedure

24.0083GPPCore network protocolsMobile radio interface Layer 3 specificationRelease 18Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

This procedure is used for:

– normal routing area updating to update the registration of the actual routing area of an MS in the network. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services if the network operates in network operation mode II;

– combined routing area updating to update the registration of the actual routing and location area of an MS in the network. This procedure is used by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services provided that the network operates in network operation mode I;

– periodic routing area updating. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS or for GPRS and non-GPRS services independent of the network operation mode;

– IMSI attach for non-GPRS services when the MS is IMSI attached for GPRS services. This procedure is used by GPRS MSs in MS operation modes A or B, if the network operates in network operation mode I;

– in A/Gb mode, resuming GPRS services when the RR sublayer indicated a resumption failure after dedicated mode was left, see 3GPP TS 44.018 [84];

– in A/Gb mode, updating the network with the new MS Radio Access Capability IE when the content of the IE has changed;

– updating the network with the new DRX parameter IE when the content of the IE has changed;

NOTE 1: Such changes can be used e.g. when the MS activates a PDP context with service requirements that cannot be met with the current DRX parameter. As PDP context(s) are activated and deactivated, the GMM context will be updated with an appropriate DRX parameter;

– re-negotiation of the READY timer value;

– Iu mode to A/Gb mode and for A/Gb mode to Iu mode intersystem change, see subclause 4.7.1.7;

– in Iu mode, re-synchronizing the PMM mode of MS and network after RRC connection release with cause "Directed signalling connection re-establishment", see subclause 4.7.2.5;

– in Iu mode and A/Gb mode after intersystem change from S1 mode, and the GMM receives an indication of "RRC connection failure" from lower layers due to lower layer failure while in S1 mode;

– S1 mode to Iu mode or S1 mode to A/Gb mode intersystem change and ISR is not activated;

– S1 mode to Iu mode or S1 mode to A/Gb mode intersystem change and ISR is activated, but the MS changes to a routeing area it has not previously registered with the network;

– indicating to the network that due to a manual CSG selection the MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the MS’s Allowed CSG list or in the MS’s Operator CSG list;

– indicating to the network that the mobile station classmark 2, mobile station classmark 3 or the supported codecs have changed for a MS supporting SRVCC; or

– indicating the current radio access technology to the network for the support of terminating access domain selection for voice calls or voice sessions (for details see subclause 4.7.5.1 and subclause 4.7.5.2.1).

While an MS has a PDN connection for emergency bearer services, the MS shall not perform manual CSG selection.

The routing area updating procedure shall also be used by a MS which is attached for GPRS services if a new PLMN is entered (see 3GPP TS 23.122 [14]), unless the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112] and the new PLMN is neither the registered PLMN nor in the list of equivalent PLMNs.

An eCall only mobile station that is not capable of eCall over IMS shall not perform a normal or combined routing area updating procedure.

Subclause 4.7.5.1 describes the routing area updating procedures for updating the routing area only. The combined routing area updating procedure used to update both the routing and location area is described in subclause 4.7.5.2.

The routing area updating procedure is always initiated by the MS. It is only invoked in state GMM-REGISTERED.

To limit the number of consecutive rejected routing area update attempts, a routing area updating attempt counter is introduced. The routing area updating attempt counter shall be incremented as specified in subclause 4.7.5.1.5. Depending on the value of the routing area updating attempt counter, specific actions shall be performed. The routing area updating attempt counter shall be reset when:

– a GPRS attach or combined GPRS attach procedure is successfully completed;

– a normal or periodic routing area updating or combined routing area updating procedure is successfully completed;

– a combined GPRS attach procedure or a combined routing area updating procedure is completed for GPRS services only with cause #2 or #28;

– a normal or periodic routing area updating or combined routing updating procedure is rejected with cause #11, #12, #13, #14, #15 or #25;

– a new PLMN is selected.

and additionally when the MS is in substate ATTEMPTING-TO-UPDATE:

– a new routing area is entered;

– expiry of timer T3302;

– at request from registration function; or

– timer T3346 is started.

The mobile equipment shall contain a list of "forbidden location areas for roaming", as well as a list of "forbidden location areas for regional provision of service". The handling of these lists is described in subclause 4.4.1.

In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [14]. The MS shall construct the Routing Area Identification of the cell from this chosen PLMN identity, and the LAC and the RAC received on the BCCH. If the constructed RAI is different from the stored RAI, the MS shall initiate the routing area updating procedure. For:

– a shared GERAN, in A/Gb mode, the chosen PLMN identity is indicated to the GERAN in the first RLC data block of an upper layer PDU (see 3GPP TS 44.060 [76]) when a foreign TLLI is used by the network sharing supporting MS for the transmission.

– a shared UTRAN, the chosen PLMN identity shall be indicated to the UTRAN in the RRC INITIAL DIRECT TRANSFER message (see 3GPP TS 25.331 [23c]).

For GERAN Iu mode, network sharing is not supported.

Whenever a ROUTING AREA UPDATE REJECT message with the cause "PLMN not allowed" is received by the MS, the chosen PLMN identity shall be stored in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. Whenever a ROUTING AREA UPDATE REJECT message is received by the MS with the cause "Roaming not allowed in this location area", "Location Area not allowed", or "No suitable cells in Location Area", the LAI that is part of the constructed RAI which triggered the routing area updating procedure shall be stored in the suitable list.

In A/Gb mode, user data transmission in the MS shall be suspended during the routing area updating procedure, except if the routing area updating procedure is triggered by a PS handover procedure as described in 3GPP TS 43.129 [113]; user data reception shall be possible. User data transmission in the network may be suspended during the routing area updating procedure.

In Iu mode, user data transmission and reception in the MS shall not be suspended during the routing area updating procedure. User data transmission in the network shall not be suspended during the routing area updating procedure.

In Iu mode, when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for this MS, the network shall progress the routing area updating procedure as normal and release the previous PS signalling connection when the routing area updating procedure has been accepted by the network.

NOTE 2: The re-establishment of the radio bearers of active PDP contexts is done as described in subclause "Service Request procedure".

The network informs the MS about the support of specific features, such as LCS-MOLR, MBMS, IMS voice over PS session, emergency bearer services in Iu mode in the Network feature support information element. The information is either explicitly given by sending the Network feature support IE or implicitly by not sending it. The handling in the network is described in subclause 9.4.15.11The network can also use the Additional network feature support IE in order to inform the MS about the support of specific features such as the delivery of SMS via GPRS (GPRS-SMS) or implicitly by not sending it. The MS may use the support indications for LCS-MOLR, MBMS and GPRS-SMS to inform the user about the availability of the appropriate services. The MS shall not request the LCS-MOLR or MBMSservices, if the service has not been indicated as available. The indication for MBMS is defined in subclause "MBMS feature support indication" in 3GPP TS 23.246 [106]. In an MS with IMS voice over PS capability, the IMS voice over PS session indicator and the emergency bearer services indicator shall be provided to the upper layers. The upper layers take the IMS voice over PS session indicator into account as specified in 3GPP TS 23.221 [131], subclause 7.2a and subclause 7.2b, when selecting the access domain for voice sessions or calls in Iu mode. When initiating an emergency call in Iu mode, the upper layers also take the emergency bearer services indicator into account for the access domain selection. The MS may use the GPRS-SMS indication in order to obtain SMS.

4.7.5.1 Normal and periodic routing area updating procedure

Periodic routing area updating is used to periodically notify the availability of the MS to the network. The value of the update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "periodic updating". The procedure is controlled in the MS by timer T3312. When timer T3312 expires, the periodic routing area updating procedure is started. Start and reset of timer T3312 is described in subclause 4.7.2.2.

The normal routing area updating procedure is initiated:

– when the MS detects a change of the routing area in state GMM-REGISTERED;

– when the MS determines that GPRS resumption shall be performed;

– when the MS needs to update the network with the new MS Radio Access Capability IE;

– when the MS needs to update the network with the new DRX parameter IE;

– in Iu mode, to re-synchronize the PMM mode of MS and network after RRC connection release with cause "Directed signalling connection re-establishment", see subclause 4.7.2.5;

– in Iu mode, to re-synchronize the PMM mode of MS and network after inter-system change not due to PS handover from PMM-CONNECTED mode in Iu mode to A/Gb mode or S1 mode, if the MS performs an inter – system change back to Iu mode without sending a ROUTING AREA UPDATE REQUEST message while in A/Gb mode or a TRACKING AREA UPDATE REQUEST message while in S1 mode;

– in Iu mode and A/Gb mode, after intersystem change from S1 mode, and the GMM receives an indication of "RRC connection failure" from lower layers due to lower layer failure while in S1 mode. In this case, if the TIN indicates "RAT-related TMSI", the MS shall set the TIN to "GUTI" before initiating the routing area updating procedure;

– in A/Gb mode, after intersystem change from S1 mode if the TIN indicates "RAT-related TMSI", but the MS is required to perform routing area updating for IMS voice termination as specified in annex P.4;

– when the MS enters GMM-REGISTERED.NORMAL-SERVICE and the TIN indicates "GUTI";

– when the MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the Allowed CSG list;or in the Operator CSG list;

– when the MS supports SRVCC and changes the mobile station classmark 2, mobile station classmark 3 or the supported codecs;

– when the MS changes the MS network capability information;

– when the UE’s usage setting or the voice domain preference for E-UTRAN change in the MS;

– when the MS activates mobility management for IMS voice termination as specified in annex P.2 and the TIN indicates "RAT-related TMSI";

– upon reception of a paging indication, using P-TMSI, if the timer T3346 is running and the MS is in state GMM-REGISTERED.ATTEMPTING-TO-UPDATE and the RAI of the current cell is same as the stored RAI;

– in A/Gb mode, after intersystem change from S1 mode via cell change order procedure not due to CS fallback, if the TIN indicates "RAT-related TMSI"; in this case the MS shall set the TIN to "GUTI" before initiating the routing area updating procedure;

– in A/Gb or Iu mode in NMO I, after intersystem change from S1 mode due to CS fallback, if the TIN indicates "GUTI" or if the routing area the MS is in is different from the registered routing area;

– in A/Gb mode, after Inter RAT handover from S1 mode or Iu mode;

– when the MS needs to request the use of PSM or needs to stop the use of PSM;

– when the MS needs to request the use of eDRX or needs to stop the use of eDRX;

– when a change in the PSM usage conditions at the MS requires a different timer T3312 value or different timer T3324 value;

– when a change in the eDRX usage conditions at the MS requires different extended DRX parameters; or

NOTE 1: A change in the PSM or eDRX usage conditions at the MS can include e.g. a change in the MS configuration, a change in requirements from upper layers or the battery running low at the MS.

– when the Default_DCN_ID value changes, as specified in 3GPP TS 24.368 [135] or in USIM file NAS_CONFIG as specified in 3GPP TS 31.102 [112].

NOTE 2: The routing area updating procedure is initiated after deleting the DCN-ID list as specified in 3GPP TS 24.301 [120], annex C.

The ROUTING AREA UPDATE REQUEST message shall always be the first data sent by the MS when a routing area border is crossed. The routing area identification is broadcast on the broadcast channel(s).

A normal routing area updating shall abort any ongoing GMM procedure. Aborted GMM procedures may be repeated after the normal routing area updating procedure has been successfully performed. The value of the update type IE included in the message shall indicate "RA updating".

If the normal routing area updating procedure is initiated due to the reception of the paging indication while timer T3346 is running, the "follow-on request pending" indication shall be set to 1.

4.7.5.1.1 Normal and periodic routing area updating procedure initiation

To initiate the normal routing area updating procedure, the MS sends the message ROUTING AREA UPDATE REQUEST to the network, starts timer T3330 and changes to state GMM-ROUTING-AREA-UPDATING-INITIATED. If timer T3302 is currently running, the MS shall stop timer T3302. If timer T3311 is currently running, the MS shall stop timer T3311.

If the MS supports S1 mode, the MS shall handle the P-TMSI IE as follows:

– If the TIN indicates "GUTI" and the MS holds a valid GUTI allocated by an MME, the MS shall map the GUTI into a P-TMSI, P‑TMSI signature and RAI as specified in 3GPP TS 23.003 [10]. The MS shall include the mapped RAI in the Old routing area identification IE and the mapped P-TMSI signature in the P-TMSI signature IE. In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "mapped P-TMSI". When the routing area updating procedure is initiated in Iu mode, the MS shall also include the mapped P-TMSI in the P‑TMSI IE. Additionally, in Iu mode and A/Gb mode, if the MS holds a valid P-TMSI and RAI, the MS shall indicate the P-TMSI in the Additional mobile identity IE and the RAI in the Additional old routing area identification IE.

– If the TIN indicates "P-TMSI" or "RAT‑related TMSI" and the MS holds a valid P-TMSI and RAI, the MS shall indicate the RAI in the Old routing area identification IE. In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "native P-TMSI". When the routing area updating procedure is initiated in Iu mode, the MS shall also include the P-TMSI in the P‑TMSI IE.

If the MS does not support S1 mode, the MS shall include the P-TMSI type IE with P-TMSI type set to "native P-TMSI".

If the MS supports PSM and requests the use of PSM, the MS shall include the T3324 value IE with a requested timer value in the ROUTING AREA UPDATE REQUEST message. When the MS includes the T3324 value IE and the MS indicates support for extended periodic timer value in the MS network feature support IE, it may also include the T3312 extended value IE to request a particular T3312 value to be allocated.

If the routing area updating procedure is not initiated by the MS due to an S1 mode to Iu mode or S1 mode to A/Gb mode intersystem change, or if it is initiated due to such an intersystem change and the TIN indicates "RAT‑related TMSI", the MS shall use the existing UMTS security context for the PS domain. The ROUTING AREA UPDATE REQUEST message shall contain the P-TMSI signature when received in a previous ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message. If the MS has a valid UMTS security context, the MS shall indicate it in the GPRS ciphering key sequence number IE.

If the routing area updating procedure is initiated by the MS due to an S1 mode to Iu mode or S1 mode to A/Gb mode inter-system change in idle mode, or if it is initiated by the MS due to PS to CS domain change from S1 mode due to SRVCC or vSRVCC handover, and the TIN indicates "GUTI", the MS shall derive a UMTS security context for the PS domain from the current EPS security context as described in the subclause 4.7.7.10. The ROUTING AREA UPDATE REQUEST message shall include a P-TMSI signature filled with a NAS token as specified in 3GPP TS 33.401 [123]. Furthermore, the MS shall indicate the eKSI value, which is associated with the derived UMTS security keys, in the CKSN field of the GPRS GSM ciphering key sequence number IE in the ROUTING AREA UPDATE REQUEST message.

NOTE: When the MS includes a P-TMSI signature filled with a NAS token, 8 bits of the NAS token will be filled with bits from the M‑TMSI (see 3GPP TS 23.003 [10]).

If the routing area updating procedure is initiated by the MS due to the S1 mode to Iu mode or S1 mode to A/Gb mode inter-system change in connected mode, the MS shall derive a UMTS security context for the PS domain from the current EPS security context as described in the subclause 4.7.7.10. Furthermore, the MS shall indicate the eKSI value, which is associated with the derived UMTS security keys, in the CKSN field of the GPRS GSM ciphering key sequence number IE in the ROUTING AREA UPDATE REQUEST message.

In Iu mode, if the MS wishes to prolong the established PS signalling connection after the normal routing area updating procedure (for example, the MS has any CM application request pending), it may set a follow-on request pending indicator on (see subclause 4.7.13).

In order to indicate the new DRX parameter while in GERAN or UTRAN coverage, the MS shall send the ROUTING AREA UPDATE REQUEST message containing the DRX parameter in the DRX parameter IE to the network, with the exception of the case if the MS had indicated its MS specific DRX parameter (3GPP TS 24.301 [120]) to the network while in E-UTRAN coverage. In this case, when the MS enters GERAN or UTRAN coverage and initiates a routing area updating procedure, the MS shall not include the DRX parameter in the DRX parameter IE in the ROUTING AREA UPDATE REQUEST message.

If the MS supports eDRX and requests the use of eDRX, the MS shall include the extended DRX parameters IE in the ROUTING AREA UPDATE REQUEST message.

In A/Gb mode, if the MS supports the restriction on use of enhanced coverage, then the MS shall set the Restriction on use of enhanced coverage capability bit to "Mobile station supports restriction on use of enhanced coverage" in the MS network capability IE of the ROUTING AREA UPDATE REQUEST message

If the MS supports dual connectivity of E-UTRA with NR, then the MS shall set the Dual connectivity of E-UTRA with NR capability bit to "Mobile station supports dual connectivity of E-UTRA with NR" in the MS network capability IE of the ROUTING AREA UPDATE REQUEST message.

In A/Gb mode, if a UMTS security context is available and if the MS indicates support of integrity protection in the MS network capability IE included in the ROUTING AREA UPDATE REQUEST message, then the MS shall use the current GPRS GSM Kint key and the current GPRS GSM integrity algorithm to integrity protect the ROUTING AREA UPDATE REQUEST message in the LLC layer. If LLC layer has not yet been configured, then the GMM layer in the MS shall assign the GPRS GSM Kint key, the GPRS GSM Kc₁₂₈ key, the GPRS GSM integrity algorithm and the GPRS GSM ciphering algorithm to the LLC layer, and indicates to the LLC layer that it shall start integrity protection. This shall be done so that the LLC layer can integrity protect, but not cipher, the ROUTING AREA UPDATE REQUEST message. The MS shall include the CKSN in the CKSN IE in the ROUTING AREA UPDATE REQUEST message. If the MS has no UMTS security context available, then the MS shall not integrity protect the ROUTING AREA UPDATE REQUEST message in the LLC layer. The MS shall in this case set the CKSN IE to the value "no key is available" and send the ROUTING AREA UPDATE REQUEST message unprotected.

4.7.5.1.2 GMM Common procedure initiation

If the network receives a ROUTING AREA UPDATE REQUEST message containing the P-TMSI type IE, and the network does not follow the use of the most significant bit of the <LAC> to distinguish the node type as specified in 3GPP TS 23.003 [10] subclause 2.8.2.2.2, the network shall use the P-TMSI type IE to determine whether the mobile identity included in the P-TMSI IE, if any, or the mobile identity used by the MS to derive a foreign TLLI (see subclause 4.7.1.4.1) is a native P‑TMSI or a mapped P‑TMSI.

The network may initiate GMM common procedures, e.g. the GMM authentication and ciphering procedure.

4.7.5.1.3 Normal and periodic routing area updating procedure accepted by the network

If the routing area updating request has been accepted by the network, a ROUTING AREA UPDATE ACCEPT message shall be sent to the MS. The network may assign a new P-TMSI and/or a new P-TMSI signature for the MS. If a new P-TMSI and/or P-TMSI signature have been assigned to the MS, it/they shall be included in the ROUTING AREA UPDATE ACCEPT message together with the routing area identification.

In a shared network, if the MS is a network sharing supporting MS, the network shall indicate the PLMN identity of the CN operator that has accepted the routing area updating request in the RAI contained in the ROUTING AREA UPDATE ACCEPT message; if the MS is a network sharing non-supporting MS, the network shall indicate the PLMN identity of the common PLMN (see 3GPP TS 23.251 [109]). If the PLMN identity of the common PLMN included in the RAI does not identify the CN operator that has accepted the routing area updating request, the network may include the PLMN identity of the CN operator that has accepted the routing area updating request in the ROUTING AREA UPDATE ACCEPT message.

In a multi-operator core network (MOCN) with common GERAN, the network shall indicate in the RAI the common PLMN identity (see 3GPP TS 23.251 [109]). If the common PLMN identity included in the RAI does not identify the CN operator that has accepted the routing area updating request, the network may include the PLMN identity of the CN operator that has accepted the routing area updating request in the ROUTING AREA UPDATE ACCEPT message.

In A/Gb mode, if the MS indicates support of integrity protection in the MS network capability IE in the ROUTING AREA UPDATE REQUEST message, and if the network supports integrity protection, then the network shall store all octets received from the MS in the MS network capability IE and in the MS Radio Access Capability IE, up to the maximum length defined for the respective information element.

NOTE 1: The network needs to store the MS network capability and MS Radio Access Capability exactly as received from the MS and network is not allowed to ignore the "higher" octets sent by the MS even if the network does not support any features indicated in the higher octetst. Otherwise the replay check of the MS network capability and MS Radio Access Capability will fail in the MS.

In A/Gb mode, if a UMTS security context is available in the network and if the MS indicates support of integrity protection in the ROUTING AREA UPDATE REQUEST message and the network supports integrity protection if integrity protection of the ROUTING AREA UPDATE REQUEST message is successfully verified in the LLC layer in the network, the network may decide to continue using the stored GPRS GSM Kint integrity key, GPRS GSM Kc₁₂₈ encryption key, GPRS GSM ciphering algorithm and GPRS GSM integrity algorithm in the LLC layer without initiating an authentication and ciphering procedure. If the MS and network continue to use the same ciphering mode, ciphering or no ciphering, the ciphering mode is re-established without the need to run an authentication and ciphering procedure. The network shall replay the MS network capability IE and the MS radio access capability IE received from the MS in the ROUTING AREA UPDATE REQUEST message, by including the MS network capability IE and the MS radio access capability IE in the ROUTING AREA UPDATE ACCEPT message to the MS. The GMM layer in the network shall assign the stored GPRS GSM Kint key, the GPRS GSM Kc₁₂₈ key, the GPRS GSM integrity algorithm and the GPRS GSM ciphering algorithm to the LLC layer. The MS shall then indicate to the LLC layer that it shall start integrity protection and ciphering in the LLC layer before sending the ROUTING AREA UPDATE ACCEPT message to the MS. If the integrity protection of the ROUTING AREA UPDATE REQUEST message is not successfully verified in the LLC layer or if the ROUTING AREA UPDATE REQUEST message is received without integrity protection, then the network shall progress the routing area updating procedure and initiate an authentication and ciphering procedure to authenticate the MS and activate integrity protection and ciphering in the MS.

In A/Gb mode, if a UMTS security context is available in the network and if the MS indicates support of integrity protection in the ROUTING AREA UPDATE REQUEST message and the network supports integrity protection, and if the network is not able to verify the message authentication code in the LLC layer protecting the ROUTING AREA UPDATE REQUEST message, due to the LLC layer at the network not having been configured yet with the integrity key and integrity algorithm for this MS, then the network shall progress the ROUTING AREA UPDATE REQUEST message at GMM layer anyway. If the CKSN included in the ROUTING AREA UPDATE REQUEST message belongs to an UMTS security context available in the network, then the network may re-establish integrity protection and ciphering of layer 3 signalling messages in the LLC layer without initiating an authentication and ciphering procedure.

In A/Gb mode, if the MS indicates support of integrity protection of user plane data in the MS network capability IE in the ROUTING AREA UPDATE REQUEST message, and if the network supports and accepts integrity protection of user plane data, then the network shall indicate integrity protection of user plane data to the MS in the ROUTING AREA UPDATE ACCEPT message. The MS shall indicate to the LLC layer to start integrity protection of user plane data after the reception of the ROUTING AREA UPDATE ACCEPT message, if indicated. The same GPRS GSM Kint key and the same GPRS GSM integrity algorithm used for integrity protection of layer 3 signalling messages shall be used for integrity protection of user plane data in the LLC layer. The network shall indicate to the LLC layer to start integrity protection of user plane data after sending the ROUTING AREA UPDATE ACCEPT message to the MS. If the network does not indicate to the MS in the ROUTING AREA UPDATE ACCEPT message that it accepts the use of integrity protection of user plane data, and if the MS does not accept such a network, then the MS shall detach from the network.

If a new DRX parameter was included in the ROUTING AREA UPDATE REQUEST message, the network shall store the new DRX parameter and use it for the downlink transfer of signalling and user data.

The network shall include the extended DRX parameters IE in the ROUTING AREA UPDATE ACCEPT message only if the extended DRX parameters IE was included in the ROUTING AREA UPDATE REQUEST message, and the network supports and accepts the use of eDRX.

If the MS has indicated in the ROUTING AREA UPDATE REQUEST message that it supports PS inter-RAT handover from GERAN to UTRAN Iu mode, the network may include in the ROUTING AREA UPDATE ACCEPT message a request to provide the Inter RAT information container.

If the MS has included the MS network capability IE or the UE network capability IE or both in the ROUTING AREA UPDATE REQUEST message, the network shall store all octets received from the MS, up to the maximum length defined for the respective information element. In case the UE network capability IE indicated new information to the network, the MS shall set the TIN to "P-TMSI".

NOTE 2: This information is forwarded to the new SGSN during inter-SGSN handover or to the new MME during intersystem handover to S1 mode.

In A/Gb mode the Cell Notification information element shall be included in the ROUTING AREA UPDATE ACCEPT message in order to indicate the ability of the network to support the Cell Notification.

The network shall change to state GMM-COMMON-PROCEDURE-INITIATED and shall start the supervision timer T3350 as described in subclause 4.7.6.

If the LAI or PLMN identity contained in the ROUTING AREA UPDATE ACCEPT message is a member of any of the "forbidden" lists and the MS is not attached for emergency bearer services, then any such entry shall be deleted.

In Iu mode, the network should prolong the PS signalling connection if the mobile station has indicated a follow-on request pending in ROUTING AREA UPDATE REQUEST. The network may also prolong the PS signalling connection without any indication from the mobile terminal (for example, if user plane radio access bearers have been established for the MS).

If the PDP context status information element is included in ROUTING AREA UPDATE REQUEST message, then the network shall deactivate all those PDP contexts locally (without peer to peer signalling between the MS and the network), which are not in SM state PDP-INACTIVE on network side but are indicated by the MS as being in state PDP-INACTIVE.

If the MBMS context status information element is included in the ROUTING AREA UPDATE REQUEST message, then the network shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are not in SM state PDP-INACTIVE on the network side, but are indicated by the MS as being in state PDP-INACTIVE. If no MBMS context status information element is included, then the network shall deactivate all MBMS contexts locally which are not in SM state PDP-INACTIVE on the network side.

If a ROUTING AREA UPDATE REQUEST message is received from an MS with a LIPA PDN connection, and if:

– a L-GW Transport Layer Address is provided by the lower layer together with the ROUTING AREA UPDATE REQUEST message, and the GGSN address associated with the PDP context of the LIPA PDN connection is different from the provided L-GW Transport Layer Address (see 3GPP TS 25.413 [19c]); or

– no L-GW Transport Layer Address is provided together with the ROUTING AREA UPDATE REQUEST message by the lower layer,

then the SGSN locally deactivates all PDP contexts associated with the LIPA PDN connection. If the ROUTING AREA UPDATE REQUEST request message is accepted, the SGSN informs the MS via the PDP context status IE in the ROUTING AREA UPDATE ACCEPT message that PDP contexts were locally deactivated.

If a ROUTING AREA UPDATE REQUEST message is received from an MS with a SIPTO at the local network PDN connection, the following different cases can be distinguished:

1) If the PDN connection is a SIPTO at the local network PDN connection with collocated L-GW and if:

– a SIPTO L-GW Transport Layer Address is provided by the lower layer together with the ROUTING AREA UPDATE REQUEST message, and the GGSN address associated with the PDP context of the SIPTO at the local network PDN connection is different from the provided SIPTO L-GW Transport Layer Address (see 3GPP TS 25.413 [19c]); or

– no SIPTO L-GW Transport Layer Address is provided together with the ROUTING AREA UPDATE REQUEST message by the lower layer,

2) If the PDN connection is a SIPTO at the local network PDN connection with stand-alone GW and if:

– a LHN-ID value is provided by the lower layer together with the ROUTING AREA UPDATE REQUEST message, and the LHN-ID stored in the PDP context of the SIPTO at the local network PDN connection is different from the provided LHN-ID value (see 3GPP TS 25.413 [19c]); or

– no LHN-ID value is provided together with the ROUTING AREA UPDATE REQUEST message by the lower layer,

then the SGSN locally deactivates all PDP contexts associated with the SIPTO at the local network PDN connection. If the ROUTING AREA UPDATE REQUEST request message is accepted, the SGSN informs the MS via the PDP context status IE in the ROUTING AREA UPDATE ACCEPT message that PDP contexts were locally deactivated.

For a SIPTO at the local network PDN connection with stand-alone GW, the conditions to deactivate ISR are specified in 3GPP TS 23.401 [122], subclause 4.3.5.6.

If due to regional subscription restrictions or access restrictions the MS is not allowed to access the routing area, but the MS has a PDN connection for emergency bearer services established, the network may accept the ROUTING AREA UPDATE REQUEST message and deactivate all non-emergency PDP contexts by initiating an PDP context deactivation procedure when the routing area updating procedure is initiated in PMM-CONNECTED mode. When the routing area updating procedure is initiated in PMM-IDLE mode, the network locally deactivates all non-emergency PDP contexts and informs the MS via the PDP context status IE in the ROUTING AREA UPDATE ACCEPT message. The network shall not deactivate the PDP contexts for emergency bearer services. The network shall consider the MS to be attached for emergency bearer services only.

If the network supports delivery of SMS via GPRS (see 3GPP TS 23.060 [74]) and this delivery is enabled (see 3GPP TS 29.272 [150]), then the network shall include the Additional network feature support IE in the ROUTING AREA UPDATE ACCEPT message and set the GPRS-SMS indicator.

If the network supports the extended protocol configuration options IE and the MS indicated support of the extended protocol configuration options IE, then the network shall include the Additional network feature support IE in the ROUTING AREA UPDATE ACCEPT message and set the ePCO IE indicator to "extended protocol configuration options IE supported".

The network shall indicate "combined RA/LA updated" or "combined RA/LA updated and ISR activated" in the update result IE in the ROUTING AREA UPDATE ACCEPT message, if the following conditions apply:

– the update type IE included in the ROUTING AREA UPDATE REQUEST message indicates "periodic updating" and the MS was previously successfully attached for GPRS and non-GPRS services; and

– location area updating for non-GPRS services as specified in 3GPP TS 29.018 [149] is successful.

The network shall include the T3324 value IE in the ROUTING AREA UPDATE ACCEPT message only if the T3324 value IE was included in the ROUTING AREA UPDATE REQUEST message, and the network supports and accepts the use of PSM.

If the network supports and accepts the use of PSM, and the MS included the T3312 extended value IE in the ROUTING AREA UPDATE REQUEST message, then the network shall take into account the T3312 value requested when providing the Periodic RA update timer IE and the T3312 extended value IE in the ROUTING AREA UPDATE ACCEPT message.

NOTE 3: Besides the value requested by the MS, the network can take local configuration into account when selecting a value for T3312 (see 3GPP TS 23.060 [74] subclause 5.3.13.54).

In A/Gb mode, if the MS indicates support for restriction on use of enhanced coverage in the ROUTING AREA UPDATE REQUEST message, and the network restricts enhanced coverage for the MS, then the network shall set the RestrictEC bit to "Enhanced coverage restricted" in the Additional network feature support IE of the ROUTING AREA UPDATE ACCEPT message.

If the network includes the T3324 value IE indicating a value other than deactivated in the ROUTING AREA UPDATE ACCEPT message, the network shall indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is not activated.

Upon receipt of a ROUTING AREA UPDATE ACCEPT message, the MS shall store the received routing area identification, stops timer T3330, reset the routing area updating attempt counter, reset the service request attempt counter and set the GPRS update status to GU1 UPDATED. If the message contains a P-TMSI, the MS shall use this P-TMSI as new temporary identity for GPRS services and shall store the new P-TMSI. If no P-TMSI was included by the network in the ROUTING AREA UPDATE ACCEPT message, the old P-TMSI shall be kept. Furthermore, the MS shall store the P-TMSI signature if received in the ROUTING AREA UPDATE ACCEPT message. If no P-TMSI signature was included in the message, the old P-TMSI signature, if available, shall be deleted.

Upon receipt of a ROUTING AREA UPDATE ACCEPT message with update result IE indicating "combined RA/LA updated" or "combined RA/LA updated and ISR activated" during the periodic routing area updating procedure, the MS shall behave as follows:

– if the ROUTING AREA UPDATE ACCEPT message contains an IMSI, the MS is not allocated any TMSI. The MS shall delete any old TMSI accordingly;

– if the ROUTING AREA UPDATE ACCEPT message contains a TMSI, the MS shall use this TMSI as new temporary identity. The MS shall delete its old TMSI and shall store the new TMSI. In this case, a ROUTING AREA UPDATE COMPLETE message is returned to the network to confirm the received TMSI; or

– if neither a TMSI nor an IMSI has been included by the network in the ROUTING AREA UPDATE ACCEPT message, the old TMSI, if any is available, shall be kept.

Upon receiving a ROUTING AREA UPDATE COMPLETE message, the SGSN shall stop timer T3350 and change to state GMM-REGISTERED. The P-TMSI, if sent in the ROUTING AREA UPDATE ACCEPT message, shall be considered as valid.

NOTE 4: Upon receiving a ROUTING AREA UPDATE COMPLETE message, if a new TMSI is included in the ROUTING AREA UPDATE ACCEPT message, the SGSN sends a BSSAP+-TMSI-REALLOCATION-COMPLETE message as specified in 3GPP TS 29.018 [149].

If the PDP context status information element is included in ROUTING AREA UPDATE ACCEPT message, then the MS shall deactivate all those PDP contexts locally (without peer to peer signalling between the MS and network), which are not in SM state PDP-INACTIVE in the MS but are indicated by the network as being in state PDP-INACTIVE. If there is a default PDP context among the PDP contexts to be deactivated, an MS supporting S1 mode shall locally deactivate all PDP contexts associated to the same PDP address and APN as the default PDP context without peer-to-peer SM signalling to the network; an MS not supporting S1 mode may apply the same behaviour. If only the PDN connection for emergency bearer services remains established, the MS shall consider itself attached for emergency bearer services only.

If the MBMS context status information element is included in the ROUTING AREA UPDATE ACCEPT message, then the MS shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are not in SM state PDP-INACTIVE in the MS, but are indicated by the network as being in state PDP-INACTIVE. If no MBMS context status information element is included, then the MS shall deactivate all those MBMS contexts locally which are not in SM state PDP-INACTIVE in the MS.

If the ROUTING AREA UPDATE ACCEPT message contains the T3312 extended value IE, then the MS shall use the T3312 extended value IE as periodic routing area update timer (T3312). If the ROUTING AREA UPDATE ACCEPT message does not contain the T3312 extended value IE, then the MS shall use value in the Periodic RA update timer IE as periodic routing area update timer (T3312).

If the MS receives the ROUTING AREA UPDATE ACCEPT message from a PLMN for which a PLMN-specific attempt counter or PLMN-specific PS-attempt counter is maintained (see subclause 4.1.1.6A), then the MS shall reset these counters. If the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall reset this counter.

If the ROUTING AREA UPDATE ACCEPT message contains the T3324 value IE, then the MS shall use the timer value for T3324 as specified in subclause 4.7.2.8.

If the ROUTING AREA UPDATE ACCEPT message contains the DCN-ID IE, then the MS shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301 [120], annex C.

In a shared network or in a multi-operator core network (MOCN) with common GERAN, if the ROUTING AREA UPDATE ACCEPT message contains the DCN-ID IE and the PLMN identity of the CN operator IE, the MS shall store the included DCN-ID value with the PLMN identity indicated in the PLMN identity of the CN operator IE, and the included DCN-ID value with the PLMN identity indicated in the RAI in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301 [120], annex C.

In A/Gb mode, if the ROUTING AREA UPDATE ACCEPT message contains the Cell Notification information element, then the MS shall start to use the LLC NULL frame to perform cell updates.

If the MS has initiated the routing area updating procedure due to manual CSG selection and receives a ROUTING AREA UPDATE ACCEPT message, and the MS sent the ROUTING AREA UPDATE REQUEST message in a CSG cell, the MS shall check if the CSG ID and associated PLMN identity of the cell are contained in the Allowed CSG list. If not, the MS shall add that CSG ID and associated PLMN identity to the Allowed CSG list and the MS may add the HNB Name (if provided by lower layers) to the Allowed CSG list if the HNB Name is present in neither the Operator CSG list nor the Allowed CSG list.

The network may also send a list of "equivalent PLMNs" in the ROUTING AREA UPDATE ACCEPT message. Each entry of the list contains a PLMN code (MCC+MNC). If the routing area updating procedure is initiated during a CS fallback procedure and the network is configured to support the return to the last registered E-UTRAN PLMN after CS fallback as specified in 3GPP TS 23.272 [133], and the PLMN identity which is provided as part of the RAI contained in the ROUTING AREA UPDATE ACCEPT message differs from the last registered E-UTRAN PLMN identity, the network shall include the last registered E-UTRAN PLMN identity in the list of "equivalent PLMNs" in the ROUTING AREA UPDATE ACCEPT message.

NOTE 5: The network can determine a routing area updating procedure is initiated during a CS fallback procedure as specified in 3GPP TS 23.272 [133].

NOTE 6: The last registered E-UTRAN PLMN identity can be derived by the network as specified in 3GPP TS 23.272 [133].

The mobile station shall store the list, as provided by the network, and further handle the list as follows:

– if there is no PDN connection for emergency bearers established, the mobile station shall remove from the list of "equivalent PLMNs" any PLMN code that is already in the "forbidden PLMN" list. If the mobile station is operating in MS operation mode C or the mobile station is supporting S1 mode, it shall also remove any PLMN code that is already in the list of "forbidden PLMNs for GPRS service";

– if the MS is not attached for emergency bearer services and there is a PDN connection for emergency bearer services established, the MS shall remove from the list of "equivalent PLMNs" any PLMN code present in the "forbidden PLMN" list when the PDN connection for emergency bearer services is released. If the mobile station is operating in MS operation mode C or the mobile station is supporting S1 mode, it shall also remove any PLMN code present in the list of "forbidden PLMNs for GPRS service" when the PDN connection for emergency bearer services is released; and

– in addition, for all cases the mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list.

All PLMNs in the stored list shall be regarded as equivalent to each other for PLMN selection, cell selection/re-selection and handover. The stored list in the mobile station shall be replaced on each occurrence of the ROUTING AREA UPDATE ACCEPT message. If no list is contained in the message, then the stored list in the mobile station shall be deleted. An MS attached for emergency bearer services only shall delete the stored list when the MS enters the state GMM-DEREGISTERED. The list shall be stored in the mobile station while switched off so that it can be used for PLMN selection after switch on.

A ROUTING AREA UPDATE COMPLETE message shall be returned to the network if the ROUTING AREA UPDATE ACCEPT message contained any of:

– a P-TMSI;

– a TMSI;

– receive N‑PDU Numbers (see 3GPP TS 44.065 [78] and 3GPP TS 25.322 [19b]); or

– a request for the provision of Inter RAT handover information.

If Receive N‑PDU Numbers were included, the Receive N‑PDU Numbers values valid in the MS, shall be included in the ROUTING AREA UPDATE COMPLETE message.

If the network has requested the provision of Inter RAT handover information, the MS shall return a ROUTING AREA UPDATE COMPLETE message including the Inter RAT handover information IE to the network.

NOTE 7: In Iu mode, after a routing area updating procedure, the mobile station can initiate Service Request procedure to request the resource reservation for the active PDP contexts if the resources have been released by the network or send upper layer message (e.g. ACTIVATE PDP CONTEXT REQUEST) to the network via the existing PS signalling connection.

In Iu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has indicated "follow-on request pending" in ROUTING AREA UPDATE REQUEST message or if user plane radio access bearers have been established for the MS) the network shall indicate the "follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. If the network wishes to release the PS signalling connection, the network shall indicate "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message.

After that in Iu mode, the mobile station shall act according to the follow-on proceed flag included in the Update result information element in the ROUTING AREA UPDATE ACCEPT message (see subclause 4.7.13).

The network may also send a Local Emergency Numbers List with local emergency numbers in the ROUTING AREA UPDATE ACCEPT, by including the Emergency Number List IE. The mobile equipment shall store the Local Emergency Numbers List, as provided by the network. The Local Emergency Numbers List stored in the mobile equipment shall be replaced on each receipt of the Emergency Number List IE. The received Local Emergency Numbers List shall be provided to the upper layers.

The emergency number(s) received in the Emergency Number List IE are valid only in networks in the same country as the cell on which this IE is received. If no list is contained in the ROUTING AREA UPDATE ACCEPT message, then the stored Local Emergency Numbers List in the mobile equipment shall be kept, except if the mobile equipment has successfully registered to a PLMN in a country different from that of the PLMN that sent the Local Emergency Numbers List.

The mobile equipment shall use the stored Local Emergency Numbers List of emergency numbers received from the network in addition to the emergency numbers stored on the SIM/USIM or ME to detect that the number dialled is an emergency number.

NOTE 8: The mobile equipment may use the Local Emergency Numbers List to assist the end user in determining whether the dialled number is intended for an emergency service or for another destination, e.g. a local directory service. The possible interactions with the end user are implementation specific.

NOTE 9: An MS that supports procedures specified in 3GPP TS 24.302 [156], can get additional local emergency numbers through those procedures, which can be used based on operator policy (see 3GPP TS 24.302 [156]) to detect that the number dialled is an emergency number.

The Local Emergency Numbers List shall be deleted at switch off and removal of the SIM/USIM. The mobile equipment shall be able to store up to ten local emergency numbers received from the network.

In order to indicate to the MS that the GUTI and TAI list assigned to the MS remain registered with the network and are valid in the MS, the network shall indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is activated.

If the MS is attached for emergency bearer services or if the network has deactivated all non-emergency PDP contexts, the network shall indicate in the update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is not activated.

If the ROUTING AREA UPDATE ACCEPT message contains:

i) no indication that ISR is activated, an MS supporting S1 mode shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 or T3423, if running; or

ii) an indication that ISR is activated, then:

– if the MS is required to perform tracking area updating for IMS voice termination as specified in annex P.5, the MS shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 or T3423, if running;

– if the MS had initiated the routing area updating procedure due to a change in DRX parameters, the MS shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 or T3423 if running;

– if the MS had initiated the routing area updating procedure due to a change in the UE’s usage setting or the voice domain preference for E-UTRAN, the MS shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 or T3423, if running; or

– the MS shall regard the available GUTI and TAI list as valid and registered with the network. If the TIN currently indicates "GUTI" and the periodic tracking area update timer T3412 is running or is deactivated, the MS shall set the TIN to "RAT-related TMSI". If the TIN currently indicates "GUTI" and the periodic tracking area update timer T3412 has already expired, the MS shall set the TIN to "P-TMSI".

In A/Gb mode, if a UMTS security context is available, if the MS indicates support of integrity protection in the ROUTING AREA UPDATE REQUEST message and the network supports integrity protection, then if the MS receives replayed capability IE’s in ROUTING AREA UPDATE ACCEPT message, then the MS shall check if the replayed MS network capability IE and the replayed MS Radio Access Capability IE received in the ROUTING AREA UPDATE ACCEPT message has not been altered compared to the MS network capability IE and the MS Radio Access Capability IE that the MS sent to the network in ROUTING AREA UPDATE REQUEST message. If the replayed MS network capability IE and the replayed MS Radio Access Capability IE are not the same, then the MS shall ignore the ROUTING AREA UPDATE ACCEPT message.

4.7.5.1.4 Normal and periodic routing area updating procedure not accepted by the network

If the routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT message to the MS. An MS, which receives a ROUTING AREA UPDATE REJECT message with a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3330. If a ROUTING AREA UPDATE REJECT message containing a reject cause other than GMM cause value #25 is received or the message is integrity protected, the MS shall stop any ongoing transmission of user data.

If the ROUTING AREA UPDATE REJECT message containing GMM cause value cause #25 was received without integrity protection, then the MS shall discard the message.

If the routing area update request is rejected due to general NAS level mobility management congestion control, the network shall set the GMM cause value to #22 "congestion" and assign a back-off timer T3346.

The MS shall then take different actions depending on the received reject cause value:

# 3 (Illegal MS);

# 6 (Illegal ME);

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The MS shall consider the SIM/USIM as invalid for GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. The MS shall delete the list of equivalent PLMNs, and shall enter the state GMM-DEREGISTERED.NO-IMSI.

If the MS is IMSI attached, the MS shall in addition set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the SIM/USIM is removed or the timer T3245 expires as described in subclause 4.1.1.6. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301 [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value.

NOTE 1: The possibility to configure a MS so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the MS, is out of scope of the present specification.

# 7 (GPRS services not allowed);

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2.9) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed. The MS shall enter the state GMM-DEREGISTERED. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value.

A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network.

If the update type is "periodic updating", a GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure.

NOTE 2: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9.

# 8 (GPRS services and non-GPRS services not allowed);

The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value.

NOTE 3: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301 [120] for the case when the tracking area procedure is rejected with the EMM cause with the same value.

# 9 (MS identity cannot be derived by the network);

The MS shall set the GPRS update status to GU2 NOT UPDATED (and shall store it according to subclause 4.1.3.2), enter the state GMM-DEREGISTERED.NORMAL-SERVICE, and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.

A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network.

If the rejected request was not for initiating a PDN connection for emergency bearer services, then

– a GPRS MS operating in MS operation mode A in network operation mode I shall proceed with appropriate MM specific procedures. Additionally, the MS shall initiate a normal or combined GPRS attach procedure depending on whether it is in an ongoing circuit-switched transaction. If the MS is in an ongoing circuit-switched transaction, it shall initiate the appropriate MM specific procedure after the circuit-switched transaction has been released. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered;

– if the update type is "periodic updating", a GPRS MS operating in MS operation mode B in network operation mode I shall proceed with appropriate MM specific procedures. Additionally, the MS shall initiate a combined GPRS attach procedure. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered;

– a GPRS MS operating in MS operation mode A or B in network operation mode II which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and which did not perform a successful generic location updating procedure since the last intersystem change from S1 mode to A/Gb or Iu mode shall proceed with appropriate MM specific procedures. Additionally, a GPRS MS operating in MS operation mode A or B in network operation mode II shall initiate a GPRS attach procedure; and

– a GPRS MS operating in MS operation mode A or B in network operation mode II which is not configured to use CS fallback and SMS over SGs, or SMS over SGs only, and a GPRS MS operating in MS operation mode C may subsequently, automatically initiate the GPRS attach procedure.

# 10 (Implicitly detached);

If the update type is "periodic updating", a GPRS MS operating in MS operation mode B in network operation mode I, is IMSI detached for both GPRS and CS services in the network.

A GPRS MS operating in MS operation mode A in network operation mode I is detached for GPRS services. If no RR connection exists then the MS is also IMSI detached for the CS services.

The MS shall enter the state GMM-DEREGISTERED.NORMAL-SERVICE. If the rejected request was not for initiating a PDN connection for emergency bearer services, then

– regardless of the MS operation mode and the network operation mode, the MS shall then perform a new attach procedure. The MS should also activate PDP context(s) that were originally activated by the MS to replace any previously MS activated PDP context(s). The MS should also perform the procedures needed in order to activate any previously active multicast service(s); and

– additionally, a GPRS MS operating in MS operation mode A in network operation mode I which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and which is in an ongoing circuit-switched transaction shall initiate the appropriate MM specific procedure after the circuit-switched transaction has been released. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered.

If S1 mode is supported in the MS, the MS shall handle the EMM state as specified in 3GPP TS 24.301 [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value.

NOTE 4: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS context(s) automatically.

# 11 (PLMN not allowed);

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the routing area updating attempt counter, shall delete the list of equivalent PLMNs, and enter the state GMM-DEREGISTERED.

The MS shall store the PLMN identity in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value.

The MS shall start timer T3340 as described in subclause 4.7.1.9.

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released:

– If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE.

– The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14].

An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318 [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122 [14].

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value.

# 12 (Location area not allowed);

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM-DEREGISTERED.LIMITED-SERVICE.

The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service".

The MS shall start timer T3340 as described in subclause 4.7.1.9.

– If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE.

– The MS shall perform a cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98].

NOTE 5: The cell selection procedure is not applicable for an MS in GAN mode.

# 13 (Roaming not allowed in this location area);

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2) and shall delete the list of equivalent PLMNs. The MS shall reset the routing area updating attempt counter, and shall enter the state GMM-REGISTERED.LIMITED-SERVICE.

The MS shall store the LAI in the list of "forbidden location areas for roaming".

The MS shall start timer T3340 as described in subclause 4.7.1.9.

– If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE.

– The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14].

An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318 [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122 [14].

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value.

# 14 (GPRS services not allowed in this PLMN);

The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM-DEREGISTERED.

The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the MS is configured to use timer T3245 (see 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. A GPRS MS operating in MS operation mode C shall perform a PLMN selection instead of a cell selection. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific PS-attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value.

A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network.

If the update type is "periodic updating" a GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure.

As an implementation option, a GPRS MS operating in operation mode A or B may perform the following additional action. If no RR connection exists the MS may perform the action immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS may only perform the action when the RR connection is subsequently released:

– The MS may perform a PLMN selection according to 3GPP TS 23.122 [14].

If an MS in GAN mode performs a PLMN selection, it shall request a PLMN list in GAN (see 3GPP TS 44.318 [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122 [14].

The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause is:

– On the "User Controlled PLMN Selector with Access Technology " or,

– On the "Operator Controlled PLMN Selector with Access Technology " list or,

– A PLMN identified as equivalent to any PLMN, within the same country, contained in the lists above.

# 15 (No Suitable Cells In Location Area);

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) shall reset the routing area updating attempt counter and shall change to state GMM-REGISTERED.LIMITED-SERVICE.

The MS shall store the LAI in the list of "forbidden location areas for roaming".

The MS shall start timer T3340 as described in subclause 4.7.1.9.

– If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE.

– The MS shall search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98] or 3GPP TS 36.304 [121].

NOTE 6: The cell selection procedure is not applicable for an MS in GAN mode.

#22 (Congestion);

If the T3346 value IE is present in the ROUTING AREA UPDATE REJECT message and the value indicates that this timer is neither zero nor deactivated, the MS shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the MS for this case is specified in subclause 4.7.5.1.5.

The MS shall abort the routing area updating procedure, reset the routing area updating attempt counter and set the GPRS update status to GU2 NOT UPDATED. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE.

The MS shall stop timer T3346 if it is running.

If the ROUTING AREA UPDATE REJECT message is integrity protected, the MS shall start timer T3346 with the value provided in the T3346 value IE.

If the ROUTING AREA UPDATE REJECT message is not integrity protected, the MS shall start timer T3346 with a random value from the default range specified in table 11.3a.

The MS stays in the current serving cell and applies the normal cell reselection process. The routing area updating procedure is started, if still necessary, when timer T3346 expires or is stopped.

A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value.

A GPRS MS operating in MS operation mode A or B in network operation mode II which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and which did not perform a successful generic location updating procedure since the last intersystem change from S1 mode to A/Gb or Iu mode shall proceed with appropriate MM specific procedures.

# 25 (Not authorized for this CSG)

Cause #25 is only applicable in UTRAN Iu mode and when received from a CSG cell. Other cases are considered as abnormal cases and the specification of the mobile station behaviour is given in subclause 4.7.5.1.5.

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and store it according to subclause 4.1.3.2) and shall reset the routing area updating attempt counter. The state is changed to GMM-REGISTERED.LIMITED-SERVICE.

If the CSG ID and associated PLMN identity of the cell where the MS has sent the ROUTING AREA UPDATE REQUEST message are contained in the Allowed CSG list stored in the MS, the MS shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list.

If the CSG ID and associated PLMN identity of the cell where the MS has sent the ROUTING AREA UPDATE REQUEST message are contained in the Operator CSG list, the MS shall proceed as specified in 3GPP TS 23.122 [14] subclause 3.1A.

The MS shall start timer T3340 as described in subclause 4.7.1.9.

– If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE.

– The MS shall search for a suitable cell according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98].

Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in subclause 4.7.5.1.5.

4.7.5.1.4a Routing area updating procedure for initiating a PDN connection for emergency bearer services not accepted by the network (UTRAN Iu mode only)

If the routing area updating request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the MS shall perform the procedures as described in subclause 4.7.5.1.4. Then if the MS is in the same selected PLMN where the last routing area updating was attempted, the MS shall:

a) inform the upper layers of the failure of the procedure; or

NOTE 1: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229 [95] that can result in the emergency call being attempted to another IP-CAN.

b) detach locally, if not detached already, attempt GPRS attach for emergency bearer services.

If the routing area updating request for initiating a PDN connection for emergency bearer services fails due to abnormal case a) in subclause 4.7.5.1.5, the MS shall perform the procedures as described in subclause 4.7.5.1.5 and inform the upper layers of the failure to access the network.

NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229 [95] that can result in the emergency call being attempted to another IP-CAN.

If the routing area updating request for initiating a PDN connection for emergency bearer services fails due to abnormal cases b), c) or d) in subclause 4.7.5.1.5, the MS shall perform the procedures as described in subclause 4.7.5.1.5. Then if the MS is in the same selected PLMN where the last routing area updating was attempted, the MS shall:

a) inform the upper layers of the failure of the procedure; or

NOTE 3: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229 [95] that can result in the emergency call being attempted to another IP-CAN.

b) detach locally, if not detached already, attempt GPRS attach for emergency bearer services.

4.7.5.1.5 Abnormal cases in the MS

The following abnormal cases can be identified:

a) Access barred because of access class control, EAB or ACDC

If the routing area updating procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable.

The routing area updating procedure shall not be started. The MS stays in the current serving cell and applies the normal cell reselection process. The procedure is started as soon as possible and if still necessary, i.e. when the barred state is removed or because of a cell change.

If access is barred because of access class control, the upper layers request PS signalling connection, ACDC is applicable to the request and the MS supports ACDC, then the routing area updating procedure shall be started according to subclause 4.7.5.1.1.

If access is barred for a certain ACDC category, and if the upper layers request PS signalling connection for a higher ACDC category and the MS supports ACDC, then the routing area updating procedure shall be started according to subclause 4.7.5.1.1.

If an access request for an uncategorized application is barred due to ACDC , and if the upper layers request PS signalling connection for a certain ACDC category and the MS supports ACDC, then the routing area updating procedure shall be started according to subclause 4.7.5.1.1.

b) Lower layer failure without "Extended Wait Time" received from lower layers before the ROUTING AREA UPDATE ACCEPT or ROUTING AREA UPDATE REJECT message is received

The procedure shall be aborted and the MS shall proceed as described below, except in the following implementation option cases b.1 and b.2.

b.1) Release of PS signalling connection before the completion of the routing area updating procedure

The routing area updating procedure shall be initiated again, if the following conditions apply:

i) The original routing area update procedure was initiated over an existing PS signalling connection; and

ii) The routing area update procedure was not due to timer T3330 expiry; and

iii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection were (e.g. PS authentication procedure, see subclause 4.7.7) received after the ROUTING AREA UPDATE REQUEST message was transmitted.

b.2) RR release in Iu mode (i.e. RRC connection release) with, for example, cause "Normal", or "User inactivity" or "Direct signalling connection re-establishment" (see 3GPP TS 25.331 [23c] and 3GPP TS 44.118 [111])

The routing area updating procedure shall be initiated again, if the following conditions apply:

i) The original routing area update procedure was initiated over an existing RRC connection; and

ii) The routing area update procedure was not due to timer T3330 expiry; and

iii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the ROUTING AREA UPDATE REQUEST message was transmitted.

NOTE 1: The RRC connection release cause that triggers the re-initiation of the routing area update procedure is implementation specific.

c) T3330 time-out

The procedure is restarted four times, i.e. on the fifth expiry of timer T3330, the MS shall abort the procedure and, in Iu mode, release the PS signalling connection (see 3GPP TS 25.331 [23c]). The MS shall proceed as described below.

d) ROUTING AREA UPDATE REJECT, other causes than those treated in subclause 4.7.5.1.4, and cases of GMM cause values #22 and #25, if considered as abnormal cases according to subclause 4.7.5.1.4

If the routing area updating request is not for initiating a PDN connection for emergency bearer services, upon reception of the cause codes # 95, # 96, # 97, # 99 and # 111 the MS should set the routing area updating attempt counter to 5.

The MS shall proceed as described below.

e) If a routing area border is crossed, when the MS is in state GMM-ROUTING-AREA-UPDATE-INITIATED, the routing area updating procedure shall be aborted and re-initiated immediately. The MS shall set the GPRS update status to GU2 NOT UPDATED.

f) In A/Gb mode, if a cell change occurs within the same RA, when the MS is in state GMM-ROUTING-AREA-UPDATE-INITIATED, the cell update procedure is performed, before completion of the routing area updating procedure.

g) Routing area updating and detach procedure collision

GPRS detach containing detach type "re-attach required" or "re-attach not required":

If the MS receives a DETACH REQUEST message before the routing area updating procedure has been completed, the routing area updating procedure shall be aborted and the GPRS detach procedure shall be progressed. If the DETACH REQUEST message contains detach type "re-attach not required" and GMM cause #2 "IMSI unknown in HLR", the MS will follow the procedure as described below for the detach type "IMSI detach".

GPRS detach containing detach type "IMSI detach":

If the MS receives a DETACH REQUEST message before the routing area updating procedure has been completed, the routing area updating procedure shall be progressed, i.e. the DETACH REQUEST message shall be ignored.

The MS shall proceed as described below.

h) Routing area updating and P-TMSI reallocation procedure collision

If the MS receives a P-TMSI REALLOCATION C0MMAND message before the routing area updating procedure has been completed, the P-TMSI reallocation procedure shall be aborted and the routing area updating procedure shall be progressed.

i) "Extended wait time" for PS domain from the lower layers

If the ROUTING AREA UPDATE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3346 with the "Extended wait time" value and reset the routing area updating attempt counter.

In other cases the MS shall ignore the "Extended wait time".

The MS shall abort the routing area updating procedure, stay in the current serving cell, set the GPRS update status to GU2 NOT UPDATED, change the state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE and apply the normal cell reselection process.

If the MS had used eDRX before initiating routing area updating procedure, then the MS shall continue to use the eDRX with the extended DRX parameters IE received during the last attach or routing area updating procedure.

The MS shall proceed as described below.

j) Timer T3346 is running

The MS shall not start the routing area updating procedure unless:

– the MS is an MS configured to use AC11 – 15 in selected PLMN;

– the MS is in PMM-CONNECTED mode (Iu mode);

– the MS receives a paging;

– the MS has a PDN connection for emergency bearer services established;

– the MS is establishing a PDN connection for emergency bearer services; or

– the MS has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication and if the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, ROUTING AREA UPDATE REQUEST or SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority".

The MS stays in the current serving cell and applies the normal cell reselection process.

NOTE 2: It is considered an abnormal case if the MS needs to initiate an routing area updating procedure while timer T3346 is running independent on whether timer T3346 was started due to an abnormal case or a non successful case.

If the stored RAI is different to the RAI of the current serving cell or the TIN indicates "GUTI", the MS shall set the GPRS update status to GU2 NOT UPDATED and change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE.

The MS shall proceed as described below.

k) Mobile originated detach required

GPRS detach due to removal of the USIM or due to switch off:

If the MS is in the state GMM-ROUTING-AREA-UPDATE-INITIATED, the routing area updating procedure shall be aborted and the GPRS detach procedure shall be performed (see subclause 4.7.4.1).

GPRS detach not due to removal of the USIM and not due to switch off:

The MS shall initiate the MS initiated detach procedure after successful completion of the routing area updating procedure.

l) Routing area updating and paging for non-GPRS services procedure collision

If a GPRS MS in MS operation mode B receives a paging for non-GPRS services before the normal or periodic routing area updating procedure has been completed, the MS shall progress the routing area updating procedure and respond to the paging for non-GPRS services when it has completed the routing area updating procedure or aborted the procedure for other reasons.

In cases b, c, d, e, g with detach type "re-attach required" or "re-attach not required" with GMM cause other than #2 "IMSI unknown in HLR", and i, the MS shall stop any ongoing transmission of user data.

In cases b, c, d, i and j the MS shall proceed as follows:

Timer T3330 shall be stopped if still running.

For the cases b, c, d, and i when the "Extended wait time" is ignored, if the routing area updating request is not for initiating a PDN connection for emergency bearer services, the routing area updating attempt counter shall be incremented.

If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current serving cell and the GPRS update status is equal to GU1 UPDATED and the TIN does not indicate "GUTI":

– the MS shall keep the GPRS update status to GU1 UPDATED and changes state to GMM-REGISTERED.NORMAL-SERVICE. The MS shall start timer T3311.

– If in addition the ROUTING AREA UPDATE REQUEST message indicated "periodic updating", none of the other reasons for initiating the routing area updating procedure listed in subclause 4.7.5.1 was applicable, and the ROUTING AREA UPDATE REQUEST message did not include a Requested READY timer value IE, T3324 value IE, T3312 extended value IE or Extended DRX parameters IE,

– in Iu mode, the timer T3311 may be stopped when the MS enters PMM-CONNECTED mode;

– in A/Gb mode, the timer T3311 may be stopped when the READY timer is started.

– If timer T3311 expires the routing area updating procedure is triggered again.

If the routing area updating attempt counter is less than 5, and the stored RAI is different to the RAI of the current serving cell or the GPRS update status is different to GU1 UPDATED or the TIN indicates "GUTI":

– for the cases i and j, the routing area updating procedure is started, if still necessary, when timer T3346 expires or is stopped.

– for the cases b, c, d, and i when the "Extended wait time" is ignored, if the routing area updating request is not for initiating a PDN connection for emergency bearer services, the MS shall start timer T3311, shall set the GPRS update status to GU2 NOT UPDATED and changes state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE.

– If S1 mode is supported by the MS, the MS shall in addition handle the EPS update status as specified in 3GPP TS 24.301 [120] for the abnormal case when a normal or periodic tracking area updating procedure fails and the tracking area updating attempt counter is less than 5 and the EPS update status is different from EU1 UPDATED.

If the routing area updating attempt counter is greater than or equal to 5:

– the MS shall start timer T3302, and shall set the GPRS update status to GU2 NOT UPDATED. An MS which is a GPRS MS in MS operation modes C shall also delete the list of equivalent PLMNs. The MS shall also enter the state GMM-REGISTERED.ATTEMPTING-TO-UPDATE or optionally the GMM-REGISTERED.PLMN-SEARCH state (see subclause 4.2.5.1.8) in order to perform a PLMN selection according to 3GPP TS 23.122 [14].

– If the MS does not enter the state GMM-REGISTERED.PLMN-SEARCH, then

– a GPRS MS operating in MS operation mode A in network operation mode I shall proceed with appropriate MM specific procedures. If the MS operating in MS operation mode A is in an ongoing circuit-switched transaction, it shall initiate the appropriate MM specific procedure after the circuit-switched transaction has been released. The MM sublayer of the MS operating in MS operation mode A shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered;

– if the update type is "periodic updating", a GPRS MS operating in MS operation mode B in network operation mode I shall proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered; and

4.7.5.1.6 Abnormal cases on the network side

The following abnormal cases can be identified:

a) If a lower layer failure occurs before the message ROUTING AREA UPDATE COMPLETE has been received from the MS and a P-TMSI and/or PTMSI signature has been assigned, the network shall abort the procedure and shall consider both, the old and new P-TMSI and the corresponding P-TMSI signatures as valid until the old P-TMSI can be considered as invalid by the network (see subclause 4.7.1.5). During this period the network may use the identification procedure followed by a P-TMSI reallocation procedure if the old P-TMSI is used by the MS in a subsequent message.

NOTE 1: Optionally, paging with IMSI may be used if paging with old and new P-TMSI fails. Paging with IMSI causes the MS to re-attach as described in subclause 4.7.9.1.

b) Protocol error

If the ROUTING AREA UPDATE REQUEST message has been received with a protocol error, the network shall return a ROUTING AREA UPDATE REJECT message with one of the following reject causes:

#96: Mandatory information element error;

#99: Information element non-existent or not implemented;

#100: Conditional IE error;

#111: Protocol error, unspecified.

c) T3350 time-out

On the first expiry of the timer, the network shall retransmit the ROUTING AREA UPDATE ACCEPT message and shall reset and restart timer T3350. The retransmission is performed four times, i.e. on the fifth expiry of timer T3350, the routing area updating procedure is aborted. Both, the old and the new P-TMSI and the corresponding P-TMSI signatures shall be considered as valid until the old P-TMSI can be considered as invalid by the network(see subclause 4.7.1.5). During this period the network acts as described for case a above.

Figure 4.7.5/1 3GPP TS 24.008: Routing and combined routing area updating procedure

d.1) ROUTING AREA UPDATE REQUEST received after the ROUTING AREA UPDATE ACCEPT message has been sent and before the ROUTING AREA UPDATE COMPLETE message is received

– If one or more of the information elements in the ROUTING AREA UPDATE REQUEST message differ from the ones received within the previous ROUTING AREA UPDATE REQUEST message, the previously initiated routing area updating procedure shall be aborted if the ROUTING AREA UPDATE COMPLETE message has not been received and the new routing area updating procedure shall be progressed, or

– If the information elements do not differ, then the ROUTING AREA UPDATE ACCEPT message shall be resent and the timer T3350 shall be restarted if an ROUTING AREA UPDATE COMPLETE message is expected. In that case, the retransmission counter related to T3350 is not incremented.

d.2) More than one ROUTING AREA UPDATE REQUEST received and no ROUTING AREA UPDATE ACCEPT or ROUTING AREA UPDATE REJECT message has been sent

– If one or more of the information elements in the ROUTING AREA UPDATE REQUEST message differs from the ones received within the previous ROUTING AREA UPDATE REQUEST message, the previously initiated routing area updating procedure shall be aborted and the new routing area updating procedure shall be progressed;

– If the information elements do not differ, then the network shall continue with the previous routing area updating procedure and shall not treat any further this ROUTING AREA UPDATE REQUEST message.

e) DETACH REQUEST message received before the ROUTING AREA UPDATE ACCEPT message is sent or before the ROUTING AREA UPDATE COMPLETE message (in case of P-TMSI and/or TMSI was allocated) is received.

GPRS detach containing cause "power off":

The network shall abort the signalling for the routing area updating procedure towards the MS and shall progress the detach procedure as described in subclause 4.7.4.1.

NOTE 2: Internally in the network, before processing the detach request, the SGSN can perform the necessary signalling procedures for the routing area updating procedure before progressing the detach procedure.

GPRS detach containing other causes than "power off":

The network shall proceed with the routing area updating procedure and shall progress the detach procedure after successful completion of the routing area updating procedure.

f) ROUTING AREA UPDATE REQUEST message with update type IE indicating "periodic updating" is received by the network, the network does not have the GMM context data related to the subscription, and the network operates in network operation mode I.

The network may send the ROUTING AREA UPDATE REJECT message with GMM cause value #10 "Implicitly detached".

4.7.5.2 Combined routing area updating procedure

4.7.5.2.0 General

Within a combined routing area updating procedure the messages ROUTING AREA UPDATE ACCEPT and ROUTING AREA UPDATE COMPLETE carry information for the routing area updating and the location area updating.

4.7.5.2.1 Combined routing area updating procedure initiation

The combined routing area updating procedure is initiated only by a GPRS MS operating in MS operation modes A or B, if the MS is in state GMM-REGISTERED and MM-IDLE, and if the network operates in network operation mode I:

– when a GPRS MS that is IMSI attached for GPRS and non-GPRS services detects a change of the routing area in state GMM-REGISTERED and MM-IDLE, unless the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112] and is entering a routing area in a new PLMN that is neither the registered PLMN nor in the list of equivalent PLMNs;

– when a GPRS MS that is IMSI attached for GPRS services wants to perform an IMSI attach for non-GPRS services;

– after termination of a non-GPRS service via non-GPRS channels to update the association if the MS has changed the RA during that non-GPRS service transaction;

– after termination of a non-GPRS service via non-GPRS channels to update the association if GPRS services were suspended during the non-GPRS service but no resume is received. See 3GPP TS 23.060 [74] subclause 16.2.1;

– after termination of a non-GPRS service via non-GPRS channels to update the association, if the GPRS MS in MS operation mode A performed a normal GPRS attach or a normal routing area updating procedure during the circuit-switched transaction;

– after a CM SERVICE REJECT message with cause value #4 is received by the mobile station (see subclause 4.5.1.1); in this case the update type IE shall be set to "Combined RA/LA updating with IMSI attach";

– when a GPRS MS needs to update the network with the new MS Radio Access Capability IE;

– when a GPRS MS needs to update the network with a new DRX parameter IE;

– in Iu mode, to re-synchronize the PMM mode of MS and network after RRC connection release with cause "Directed signalling connection re-establishment", see subclause 4.7.2.5;

– in Iu mode, to re-synchronize the PMM mode of MS and network after inter-system change not due to PS handover from PMM-CONNECTED mode in Iu mode to A/Gb mode or S1 mode, if the MS performed an inter – system change back to Iu mode without sending a ROUTING AREA UPDATE REQUEST message while in A/Gb mode or a TRACKING AREA UPDATE REQUEST message while in S1 mode;

– when the MS enters GMM-REGISTERED.NORMAL-SERVICE and the TIN indicates "GUTI";

– when the MS supports SRVCC and changes the mobile station classmark 2, mobile station classmark 3 or the supported codecs;

– when the MS which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, enters a GERAN or UTRAN cell and timer T3423 has expired, or is in the GERAN or UTRAN cell when timer T3423 expires;

– when due to a manual CSG selection the GPRS MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the MS’s Allowed CSG list or in the MS’s Operator CSG list;

– when the MS changes the MS network capability information;

– when the UE’s usage setting or the voice domain preference for E-UTRAN change in the MS;

– when the MS activates mobility management for IMS voice termination as specified in annex P.2 and the TIN indicates "RAT-related TMSI";

– upon reception of a paging indication using P-TMSI, if the timer T3346 is running and the MS is in state GMM-REGISTERED.ATTEMPTING-TO-UPDATE and the RAI of the current cell is same as the stored RAI;

– when the MS which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, enters a GERAN or UTRAN cell, after intersystem change from S1 mode to Iu or A/Gb mode not due to CS fallback, and the location area of the current cell is different from the location area stored in the MS;

– in A/Gb mode, after Inter RAT handover from S1 mode or Iu mode;

– when the MS needs to request the use of PSM or needs to stop the use of PSM;

– when the MS needs to request the use of eDRX or needs to stop the use of eDRX;

– when a change in the eDRX usage conditions at the MS requires different extended DRX parameters;

– when a change in the PSM usage conditions at the MS requires a different timer T3312 value or different timer T3324 value; or

NOTE 1: A change in the PSM or eDRX usage conditions at the MS can include e.g. a change in the MS configuration, a change in requirements from upper layers or the battery running low at the MS.

– when the Default_DCN_ID value changes, as specified in 3GPP TS 24.368 [135] or in USIM file NAS_CONFIG as specified in 3GPP TS 31.102 [112].

NOTE 2: The routing area updating procedure is initiated after deleting the DCN-ID list as specified in 3GPP TS 24.301 [120], annex C.

In A/Gb mode, the routing and location area identification are broadcast on the broadcast channel(s). A combined routing area updating procedure shall abort any ongoing GMM procedure. Aborted GMM procedures shall be repeated after the combined routing area updating procedure has been successfully performed. The ROUTING AREA UPDATE REQUEST message shall always be the first message sent from the MS in the new routing area after routing area change.

In Iu mode, the routing and location area identification are broadcast on the broadcast channel(s) or sent to the MS via the PS signalling connection. A combined routing area updating procedure shall abort any ongoing GMM procedure. Aborted GMM procedures may be repeated after the combined routing area updating procedure has been successfully performed. The ROUTING AREA UPDATE REQUEST message shall always be the first GMM message sent from the MS in the new routing area after routing area change.

To initiate a combined routing area updating procedure the MS sends the message ROUTING AREA UPDATE REQUEST to the network, starts timer T3330 and changes to state GMM-ROUTING-UPDATING-INITIATED and MM LOCATION UPDATING PENDING. The value of the Update type IE in the message shall indicate "combined RA/LA updating" unless explicitly specified otherwise. If for the last attempt to update the registration of the location area a MM specific procedure was performed, the value of the Update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "combined RA/LA updating with IMSI attach". Furthermore the MS shall include the TMSI status IE if no valid TMSI is available. If the MS has stored a valid LAI and the MS supports EMM combined procedures, the MS shall include it in the Old location area identification IE in the ROUTING AREA UPDATE REQUEST message. If timer T3302 is currently running, the MS shall stop timer T3302. If timer T3311 is currently running, the MS shall stop timer T3311.

If the MS has stored a valid TMSI, the MS shall include the TMSI based NRI container IE in the ROUTING AREA UPDATE REQUEST message.

A GPRS MS in MS operation modes B that is in an ongoing circuit-switched transaction, shall initiate the combined routing area updating procedure after the circuit-switched transaction has been released, if the MS has changed the RA during the circuit-switched transaction and if the network operates in network operation mode I.

A GPRS MS in MS operation mode A shall initiate the combined routing area updating procedure with IMSI attach after the circuit-switched transaction has been released, if a normal GPRS attach or a normal routing area updating procedure was performed during the circuit-switched transaction and provided that the network operates in network operation mode I.

A GPRS MS in MS operation mode A shall perform the normal routing area update procedure during an ongoing circuit-switched transaction.

If the MS initiates the combined routing area updating procedure for GPRS services and "SMS-only service", the MS shall indicate "SMS only" in the Additional update type IE.

In Iu mode, when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for this MS, the network shall progress the routing area update procedure as normal and release the previous PS signalling connection when the routing area update procedure has been accepted by the network.

NOTE 3: The re-establishment of the radio bearers of active PDP contexts is done as described in subclause "Service Request procedure".

If the combined routing area updating procedure is initiated due to the reception of the paging indication while T3346 is running, the "follow-on request pending" indication shall be set to 1.

4.7.5.2.2 GMM Common procedure initiation

The network may initiate GMM common procedures, e.g. the GMM authentication and ciphering procedure.

4.7.5.2.3 Combined routing area updating procedure accepted by the network

Depending on the value of the update result IE received in the ROUTING AREA UPDATE ACCEPT message, two different cases can be distinguished:

Case 1) The update result IE value indicates "combined RA/LA": Routing and location area updating is successful;

Case 2) The update result IE value indicates "RA only": Routing area updating is successful, but location area updating is not successful.

A ROUTING AREA UPDATE COMPLETE message shall be returned to the network if the ROUTING AREA UPDATE ACCEPT message containsany of:

– a P-TMSI and/or a TMSI;

– Receive N‑PDU Numbers (see 3GPP TS 44.065 [78] and 3GPP TS 25.322 [19b]); or

– a request for the provision of Inter RAT handover information.

If Receive N‑PDU Numbers were included, the Receive N‑PDU Numbers that are valid in the MS shall be included in the ROUTING AREA UPDATE COMPLETE message.

If the network has requested the provision of Inter RAT handover information the MS shall return a ROUTING AREA UPDATE COMPLETE message including the Inter RAT handover information IE, as applicable, to the network.

In Iu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has indicated "follow-on request pending" in ROUTING AREA UPDATE REQUEST message) the network shall indicate the "follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. If the network wishes to release the PS signalling connection, the network shall indicate "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message.

If the network supports CS Fallback, and the mobile station has indicated support of EMM combined procedures in MS network capability, the network shall indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is not activated.

4.7.5.2.3.1 Combined routing area updating successful

The description for normal routing area update as specified in subclause 4.7.5.1.3 shall be followed. In addition, the following description for location area updating applies.

The handling at the receipt of the ROUTING AREA UPDATE ACCEPT depends on the value received in the update result IE as specified below.

The TMSI reallocation may be part of the combined routing area updating procedure. The TMSI allocated is then included in the ROUTING AREA UPDATE ACCEPT message together with the location area identification (LAI). The network shall, in this case, change to state GMM-COMMON-PROCEDURE-INITIATED and shall start the timer T3350 as described in subclause 4.7.6.

The MS, receiving a ROUTING AREA UPDATE ACCEPT message, stores the received location area identification, stops timer T3330, enters state MM IDLE, reset the location update attempt counter and sets the update status to U1 UPDATED. If the ROUTING AREA UPDATE ACCEPT message contains an IMSI, the mobile station is not allocated any TMSI, and shall delete any TMSI accordingly. If the ROUTING AREA UPDATE ACCEPT message contains a TMSI, the MS shall use this TMSI as new temporary identity. The MS shall delete its old TMSI and shall store the new TMSI. In this case, an ROUTING AREA UPDATE COMPLETE message is returned to the network. If neither a TMSI nor an IMSI has been included by the network in the ROUTING AREA UPDATE ACCEPT message, the old TMSI, if any is available, shall be kept.

If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events (see subclause 4.1.1.6A), then the MS shall reset this counter.

If the MS is not configured for NAS signalling low priority, and any of the following conditions is fulfilled:

– the MS initiated the combined routing area updating procedure due to a change of the registered location area;

– the value of the Update type IE in the ROUTING AREA UPDATE REQUEST message indicated "combined RA/LA updating with IMSI attach"; or

– the MS indicated support of EMM combined procedures in the MS network capability;

then the MS may stop timer T3246 if running.

Any timer used for triggering the location updating procedure (e.g. T3211, T3212) shall be stopped if running.

The network receiving a ROUTING AREA UPDATE COMPLETE message stops timer T3350, changes to GMM-REGISTERED state

NOTE: Upon receiving a ROUTING AREA UPDATE COMPLETE message, the SGSN sends a BSSAP+-TMSI-REALLOCATION-COMPLETE message as specified in 3GPP TS 29.018 [149].

4.7.5.2.3.2 Combined routing area updating successful for GPRS services only

Apart from the actions on the routing area updating attempt counter, the description for normal routing area update as specified in subclause 4.7.5.1.3 shall be followed. In addition, the following description for location area updating applies.

The SGSN shall use GMM cause #28 "SMS provided via GPRS in this routing area" in the ROUTING AREA UPDATE ACCEPT message only if the MS requested "SMS-only service" by including the Additional update type IE in the ROUTING AREA UPDATE REQUEST message. The SGSN may indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is activated.

The MS receiving the ROUTING AREA UPDATE ACCEPT message takes one of the following actions depending on the GMM cause:

#2 (IMSI unknown in HLR);

The MS shall stop timer T3330 if still running and shall reset the routing area updating attempt counter. The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The MS shall enter state GMM-REGISTERED.NORMAL-SERVICE. The new MM state is MM IDLE. The SIM/USIM shall be considered as invalid for non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value.

#16 (MSC temporarily not reachable); or

#17 (Network failure)

The MS shall stop timer T3330 if still running, and shall enter state MM-IDLE. The routing area updating attempt counter shall be incremented.

If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current serving cell and the GMM update status is equal to GU1 UPDATED:

– the MS shall keep the GMM update status GU1 UPDATED and changes state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T3311 expires the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach" is triggered again.

If the routing area updating attempt counter is greater than or equal to 5:

– the MS shall start timer T3302 and shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM;

– a GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures.
The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered.

# 22 (Congestion);

The MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, shall stop timer T3330 if still running, and shall enter state MM-IDLE. The MS shall set the routing area updating attempt counter to 5 and shall start timer T3302.

# 28 (SMS provided via GPRS in this routing area);

The MS stays in the current serving cell and applies the normal cell reselection process.

Other GMM causevalues and the case that no GMM cause IE was received are considered as abnormal cases. The combined routing area updating shall be considered as failed for non-GPRS services. The specification of the MS behaviour in those cases is specified in subclause 4.7.5.2.5.

4.7.5.2.4 Combined routing area updating not accepted by the network

If the combined routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT message to the MS. An MS that receives a ROUTING AREA UPDATE REJECT message containing a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3330, and shall enter the state MM IDLE. If a ROUTING AREA UPDATE REJECT message containing a reject cause other than GMM cause value #25 is received or the message is integrity protected, the MS shall stop any ongoing transmission of user data.

If the ROUTING AREA UPDATE REJECT message containing GMM cause value #25 was received without integrity protection, then the MS shall discard the message.

The MS shall then take different actions depending on the received reject cause:

# 3 (Illegal MS);

# 6 (Illegal ME), or

# 8 (GPRS services and non GPRS services not allowed);

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and the update status to U3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key sequence number and GPRS ciphering key sequence number. The MS shall consider the SIM/USIM as invalid for GPRS and non GPRS services until switching off or the SIM/USIM is removed or the timer T3245 expires as described in subclause 4.1.1.6. The MS shall delete the list of equivalent PLMNs, and shall enter the state GMM-DEREGISTERED.NO-IMSI.

If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value.

NOTE 1: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9 for reject cause #8.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

# 7 (GPRS services not allowed);

A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services is still IMSI attached for CS services in the network.

A GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure.

NOTE 2: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

# 9 (MS identity cannot be derived by the network);

A GPRS MS operating in MS operation mode A or B in network operation mode I which is already IMSI attached for CS services in the network, is still IMSI attached for CS services in the network.

If the rejected request was not for initiating a PDN connection for emergency bearer services, then

– a GPRS MS operating in MS operation mode A or B shall proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered; and

– the MS may subsequently, automatically initiate the GPRS attach procedure.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

# 10 (Implicitly detached);

A GPRS MS operating in MS operation mode A or B in network operation mode I, is IMSI detached for both GPRS and CS services in the network.

The MS shall enter the state GMM-DEREGISTERED.NORMAL-SERVICE. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS shall then perform a new attach procedure. The MS should also activate PDP context(s) that were originally activated by the MS to replace any previously MS activated PDP context(s). The MS should also perform the procedures needed in order to activate any previously active multicast service(s).

If S1 mode is supported in the MS, the MS shall handle the EMM state as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

NOTE 3: In some cases, user interaction may be required and then the MS cannot activate the PDP/MBMS context(s) automatically.

# 11 (PLMN not allowed);

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and the update status to U3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and enter the state GMM-DEREGISTERED. Furthermore, the MS shall delete any P-TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key sequence number GPRS ciphering key sequence number, shall delete the list of equivalent PLMNs, and shall reset the routing area updating attempt counter and the location update attempt counter.

The MS shall start timer T3340 as described in subclause 4.7.1.9.

The MS shall then perform a PLMN selection according to 3GPP TS 23.122 [14].

An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318 [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122 [14].

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

# 12 (Location area not allowed);

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM-DEREGISTERED.LIMITED-SERVICE.

The MS shall in addition set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE.

The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service".

The MS shall start timer T3340 as described in subclause 4.7.1.9.

The MS shall perform a cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98].

NOTE 4: The cell selection procedure is not applicable for an MS in GAN mode.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

# 13 (Roaming not allowed in this location area);

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2), and shall delete the list of equivalent PLMNs. The MS shall reset the routing area updating attempt counter, and shall enter the state GMM-REGISTERED.LIMITED-SERVICE.

The MS shall in addition set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE.

The MS shall store the LAI in the list of "forbidden location areas for roaming".

The MS shall start timer T3340 as described in subclause 4.7.1.9.

The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14].

The MS shall indicate the Update type IE "combined RA/LA updating with IMSI attach" when performing the routing area updating procedure following the PLMN selection.

An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318 [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122 [14].

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

# 14 (GPRS services not allowed in this PLMN);

The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the MS is configured to use timer T3245 (see 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112]) then the MS shall start timer T3245 and proceed as described subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific PS-attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value.

A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services is still IMSI attached for CS services in the network.

A GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure.

As an implementation option, a GPRS MS operating in operation mode A or B may perform a PLMN selection according to 3GPP TS 23.122 [14].

If an MS in GAN mode performs a PLMN selection, it shall request a PLMN list in GAN (see 3GPP TS 44.318 [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122 [14].

The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause is:

– On the "User Controlled PLMN Selector with Access Technology " or,

– On the "Operator Controlled PLMN Selector with Access Technology " list or,

– A PLMN identified as equivalent to any PLMN, within the same country, contained in the lists above.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

# 15 (No Suitable Cells In Location Area);

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM-REGISTERED.LIMITED-SERVICE.

The MS shall in addition set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE.

The MS shall store the LAI in the list of "forbidden location areas for roaming".

The MS shall start timer T3340 as described in subclause 4.7.1.9.

The MS shall search for a suitable cell in another location area according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98].

NOTE 5: The cell selection procedure is not applicable for an MS in GAN mode.

The MS shall indicate the Update type IE "combined RA/LA updating with IMSI attach" when performing the routing area updating procedure.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

#22 (Congestion);

The MS shall stop timer T3346 if it is running.

If the ROUTING AREA UPDATE REJECT message is integrity protected, the MS shall start timer with the value provided in the T3346 value IE.

If the ROUTING AREA UPDATE REJECT message is not integrity protected, the ME shall start timer T3346 with a random value from the default range specified in table 11.3a.

The MS stays in the current serving cell and applies the normal cell reselection process. The routing area updating procedure is started, if still necessary, when timer T3346 expires or is stopped.

#25 (Not authorized for this CSG)

The MS shall start timer T3340 as described in subclause 4.7.1.9.

If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE.

The MS shall search for a suitable cell according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98].

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the combined tracking area update procedure is rejected with the EMM cause with the same value.

Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in subclause 4.7.5.2.5.

4.7.5.2.5 Abnormal cases in the MS

The MS shall proceed as follows:

1) If the combined routing area update was successful for GPRS services only and the ROUTING AREA UPDATE ACCEPT message contained a cause value not treated in subclause 4.7.5.2.3.2 or the GMM Cause IE is not included in the message, the MS shall proceed as follows:

a) The MS shall stop timer T3330 if still running, and shall enter state MM IDLE. The routing area updating attempt counter shall be incremented;

b) If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current serving cell and the GMM update status is equal to GU1 UPDATED:

c) If the routing area updating attempt counter is greater than or equal to 5:

– the MS shall start timer T3302 and shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM; and

– a GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II or as long as the combined GMM procedures are not successful and no new RA is entered;

2) Combined routing area updating and paging for non-GPRS services procedure collision

If the MS receives a paging for non-GPRS services before the routing area updating procedure has been completed, the MS shall progress the routing area updating procedure and respond to the paging for non-GPRS services when the MS has completed the routing area updating procedure or aborted the procedure for other reasons. The MS shall return to MM state MM IDLE and proceed with the appropriate MM specific procedures to respond to the paging for non-GPRS services; and

3) otherwise, the abnormal cases specified in subclause 4.7.5.1.5 apply with the following modification.

If the GPRS routing area updating attempt counter is incremented according to subclause 4.7.5.1.5 the next actions depend on the Location Area Identities (stored on SIM/USIM and the one of the current serving cell) and the value of the routing area updating attempt counter.

– if the update status is U1 UPDATED, and the stored LAI is equal to the one of the current serving cell and the routing area updating attempt counter is smaller than 5, then the mobile station shall keep the update status to U1 UPDATED, the new MM state is MM IDLE substate NORMAL SERVICE;

– if the routing area updating attempt counter is smaller than 5 and, additionally, the update status is different from U1 UPDATED or the stored LAI is different from the one of the current serving cell, the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and list of equivalent PLMNs and set the update status to U2 NOT UPDATED. The MM state remains MM LOCATION UPDATING PENDING; or

– if the routing area updating attempt counter is greater or equal to 5, the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and the list of equivalent PLMNs, and shall set the update status to U2 NOT UPDATED.
A GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures.
The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered. The new MM state is MM IDLE substate ATTEMPTING TO UPDATE or optionally MM IDLE substate PLMN SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [14].

4.7.5.2.6 Abnormal cases on the network side

The abnormal cases specified in subclause 4.7.5.1.6 apply.