Section: 4.7.5 Routing area updating procedure
Content: 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[ None ]  [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[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ]  [14]), unless the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ]  [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ]  [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[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ]  [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[ None ]  [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[ None ]  [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[ Non-Access Stratum (NAS) configuration Management Object (MO) ]  [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ]  [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[ None ]  [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[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ]  [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[ Architectural requirements ]  [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.