Section: 4.7.5.1.3 Normal and periodic routing area updating procedure accepted by the network
Content: 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[ Network sharing; Architecture and functional description ]  [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[ Network sharing; Architecture and functional description ]  [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, and if integrity protection of the ROUTING AREA UPDATE REQUEST message is successfully verified in the LLC layer in the network, then if the network decides to re-authenticate the MS or select a new integrity algorithm or ciphering algorithm, the network shall initiate an authentication and ciphering procedure. 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 Kc128 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 Kc128 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[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ]  [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[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ]  [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[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ]  [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[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ]  [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[ General Packet Radio Service (GPRS); Service description; Stage 2 ]  [74]) and this delivery is enabled (see 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ]  [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[ General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification ]  [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[ General Packet Radio Service (GPRS); Service description; Stage 2 ]  [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[ General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification ]  [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[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ]  [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[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ]  [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[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ]  [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[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ]  [133]. NOTE 6: The last registered E-UTRAN PLMN identity can be derived by the network as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ]  [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[ Mobile Station (MS) - Serving GPRS Support Node (SGSN);  Subnetwork Dependent Convergence Protocol (SNDCP) ]  [78] and 3GPP TS 25.322[ None ]  [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[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ]  [156], can get additional local emergency numbers through those procedures, which can be used based on operator policy (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ]  [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.