Section: 4.7.5.1.5 Abnormal cases in the MS
Content: 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[ None ]  [23c] and 3GPP TS 44.118[ None ]  [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[ None ]  [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[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ]  [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[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ]  [14]. - 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[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ]  [120] for the abnormal case when a normal or periodic tracking area updating procedure fails and the tracking area updating attempt counter is equal to 5. - 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 - 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.