Section: 4.4.4.9 Abnormal cases on the mobile station side
Content: The different abnormal cases that can be identified are the following: a) Access barred because of access class control or EAB The location updating procedure is not started. The mobile station stays in the current serving cell and applies normal cell reselection process. The procedure is started as soon as possible and if still necessary (when the barred state is ended or because of a cell change). b) The answer to random access is an IMMEDIATE ASSIGNMENT REJECT message (A/Gb mode only) The location updating is not started. The mobile station stays in the chosen cell and applies normal cell selection process. The waiting timer T3122 is reset when a cell change occurs. The procedure is started as soon as possible after T3122 timeout if still necessary. c) Random access failure (A/Gb mode only) Timer T3213 is started. When it expires the procedure is attempted again if still necessary. NOTE 1: As specified in 3GPP TS 45.008[ None ]  [34], a cell reselection then takes place, with return to the cell inhibited for 5 seconds if there is at least one other suitable cell. Typically the selection process will take the mobile station back to the cell where the random access failed after 5 seconds. If at the expiry of timer T3213 a new cell has not been selected due to the lack of valid information (see 3GPP TS 45.008[ None ]  [34]), the mobile station may as an option delay the repeated attempt for up to 8 seconds to allow cell re-selection to take place. In this case the procedure is attempted as soon as a new cell has been selected or the mobile station has concluded that no other cell can be selected. If random access failure occurs for two successive random access attempts for location updating the mobile station proceeds as specified below. d) RR connection failure The procedure is aborted and the mobile station proceeds as specified below. e) T3210 timeout The procedure is aborted, the RR connection is aborted and the MS proceeds as specified below. f) RR release without "Extended Wait Time" received from lower layers before the normal end of procedure The procedure is aborted and the mobile station proceeds as specified below, except in the following implementation option case f.1. f.1) RR release in Iu mode (i.e. RRC connection release) with, for example, cause "Normal", "User inactivity" or "Directed signalling connection re-establishment" (see 3GPP TS 25.331[ None ]  [23c] and 3GPP TS 44.118[ None ]  [111]) The location updating procedure shall be initiated again, if the following conditions apply: i) The original location updating procedure was initiated over an existing RRC connection; and ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the CS signalling connection (e.g. CS authentication procedures, see subclause 4.3.2), were received after the LOCATION UPDATING REQUEST message was transmitted. NOTE 2: The RRC connection release cause that triggers the re-initiation of the location updating procedure is implementation specific. g) Location updating reject, other causes than those treated in subclause 4.4.4.7, and cases of MM cause values #22 and #25, if considered as abnormal cases according to subclause 4.4.4.7 Upon reception of the cause codes #22, # 95, # 96, # 97, # 99 and # 111 the MS should set the location update attempt counter to 4. The MS waits for release of the RR connection as specified in subclause 4.4.4.8. The MS shall proceed as described below. h) RR connection establishment failure without "Extended Wait Time" received from lower layers (Iu mode only) The procedure is aborted and the mobile station proceeds as specified below. NOTE 3: Case h) covers all cases when the signalling connection cannot be established, including random access failure and access reject. As the RRC protocol has error specific retransmission mechanisms (see 3GPP TS 25.331[ None ]  [23c]), there is no need to distinguish between the different error cases within MM. i) "Extended wait time" for CS domain from the lower layers The MS shall abort the location updating procedure and stop timer T3210 if still running. If the LOCATION UPDATING REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3246 with the "Extended wait time" value and reset the location update attempt counter. In other cases the MS shall ignore the "Extended wait time". Additionally, the MS shall set the MM update status to U2 NOT UPDATED and change to state MM IDLE sub-state ATTEMPTING TO UPDATE. The MS stays in the current serving cell and applies normal cell reselection process. The location updating procedure is started, if still necessary, when timer T3246 expires or is stopped, and the MS proceeds as specified below. j) Timer T3246 is running The location updating procedure shall not be initiated unless the MS is establishing an emergency call or the MS is an MS configured to use AC11 – 15 in selected PLMN. The MS stays in the current serving cell and applies normal cell reselection process. The location updating procedure is started, if still necessary, when timer T3246 expires or is stopped. In cases d) to i) (except in the case f.1 and except in the case i) when timer T3246 is started) above, and, for repeated failures as defined in c) above, the mobile station proceeds as follows. Timer T3210 is stopped if still running. The RR Connection is aborted in case of timer T3210 timeout. The location update attempt counter is incremented. The next actions depend on the Location Area Identities (stored and received from the BCCH of the current serving cell) and the value of the location update attempt counter. – the update status is UPDATED, and the stored LAI is equal to the one received on the BCCH from the current serving cell and the location update attempt counter is smaller than 4: The mobile station shall keep the update status to UPDATED, the MM IDLE sub-state after the RR connection release is NORMAL SERVICE. The mobile station shall memorize the location updating type used in the location updating procedure. It shall start timer T3211 when the RR connection is released. When timer T3211 or T3246 expires the location updating procedure is triggered again with the memorized location updating type; – either the update status is different from UPDATED, or the stored LAI is different from the one received on the BCCH from the current serving cell, or the location update attempt counter is greater or equal to 4: When the RR connection is released the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM, and set the update status to NOT UPDATED. A mobile station which is not a GPRS MS shall also delete the list of equivalent PLMNs. The mobile station shall enter the MM IDLE sub-state ATTEMPTING TO UPDATE (see subclause 4.2.2.2 for the subsequent actions) or optionally the MM IDLE sub-state PLMN SEARCH (see subclause 4.2.1.2) 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 the location update attempt counter is smaller than 4, the mobile station shall memorize that timer T3211 is to be started when the RR connection is released, otherwise it shall memorize that timer T3212 is to be started when the RR connection is released.