Section: 4.4.4.6 Location updating accepted by the network
Content: If the location updating is accepted by the network a LOCATION UPDATING ACCEPT message is transferred to the mobile station. In case the identity confidentiality service is active (see subclauses 4.3.1 and 4.4.4.4), the TMSI reallocation may be part of the location updating procedure. The TMSI allocated is then contained in the LOCATION UPDATING ACCEPT message together with the location area identifier LAI. The network shall in this case start the supervision timer T3250 as described in subclause 4.3.1. In a shared network, if the MS is a network sharing supporting MS, the network shall indicate in the LAI the PLMN identity of the CN operator that has accepted the location updating; 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]). In a multi-operator core network (MOCN) with common GERAN, the network shall indicate in the LAI the common PLMN identity (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ]  [109]). If the network wishes to prolong the RR connection to allow the mobile station to initiate MM connection establishment (for example if the mobile station has indicated in the LOCATION UPDATING REQUEST that it has a follow-on request pending) the network shall send "follow on proceed" in the LOCATION UPDATING ACCEPT and start timer T3255. If the mobile station has indicated "CS fallback mobile terminating call" in the LOCATION UPDATING REQUEST message, the network shall maintain the RR connection for an implementation dependent duration to allow for mobile terminating call establishment. If the mobile station has also indicated in the LOCATION UPDATING REQUEST message that it has a follow-on request pending, it is implementation dependent whether the network proceeds with the mobile terminating call establishment or allows for a mobile initiated MM connection establishment. The mobile station receiving a LOCATION UPDATING ACCEPT message shall store the received location area identification LAI, stop timer T3210, reset the location update attempt counter and set the update status in the SIM/USIM to UPDATED. If the message contains an IMSI, the mobile station is not allocated any TMSI, and shall delete any TMSI in the SIM/USIM accordingly. If the message contains a TMSI, the mobile station is allocated this TMSI, and shall store this TMSI in the SIM/USIM and a TMSI REALLOCATION COMPLETE shall be returned to the network. If neither IMSI nor TMSI is received in the LOCATION UPDATING ACCEPT message, the old TMSI if any available shall be kept. If the MS has initiated the location updating procedure due to manual CSG selection and receives a LOCATION UPDATING ACCEPT message, and the MS sent the LOCATION UPDATING 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. If the LAI or PLMN identity contained in the LOCATION UPDATING ACCEPT message is a member of the list of "forbidden location areas for regional provision of service", the list of "forbidden location areas for roaming" or the "forbidden PLMN list" then such entries shall be deleted. If the MS receives the LOCATION UPDATING ACCEPT message from a PLMN for which a PLMN-specific attempt counter is maintained (see subclause 4.1.1.6A), then the MS shall reset this counter. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall reset this counter. The network may also send a list of "equivalent PLMNs" in the LOCATION UPDATING ACCEPT message. Each entry of the list contains a PLMN code (MCC+MNC). If the location 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 LOCATION UPDATING ACCEPT message. NOTE 1: The network can determine a location 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 2: 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, except that any PLMN code that is already in the "forbidden PLMN list" shall be removed from the "equivalent PLMNs" list before it is stored by the mobile station. If 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" before storing the list. In addition 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 LOCATION UPDATING ACCEPT message. If no list is contained in the message, then the stored list in the mobile station shall be deleted. The list shall be stored in the mobile station while switched off so that it can be used for PLMN selection after switch on. After that, the mobile station shall act according to the presence of the "Follow-on proceed" information element in the LOCATION UPDATING ACCEPT; if this element is present and the mobile station has a CM application request pending, it shall send a CM SERVICE REQUEST to the network and proceed as in subclause 4.5.1.1. Otherwise, it shall start timer T3240 and enter state WAIT FOR NETWORK COMMAND. Furthermore, the network may grant authorisation for the mobile station to use GSM-Cordless Telephony System (CTS) in the Location Area and its immediate neighbourhood. The mobile should memorise this permission in non-volatile memory. If the "CTS permission" IE is not present in the message, the mobile is not authorised to use GSM-CTS, and shall accordingly delete any memorised permission. NOTE 3: The interaction between CTS and GPRS procedures are not yet defined. The network may also send a Local Emergency Numbers List with local emergency numbers in the LOCATION UPDATING 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 LOCATION UPDATING 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 Lt 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 4: 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 5: 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.