Section: 5.5.3.2.6 Abnormal cases in the UE
Content: The following abnormal cases can be identified: a) Access barred because of access class barring, EAB, ACDC or NAS signalling connection establishment rejected by the network without "Extended wait time" received from lower layers In WB-S1 mode, if the tracking area updating procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable. In NB-S1 mode, if the tracking area updating procedure is started in response to a paging request from the network, access barring is not applicable. In WB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [22]), the tracking area updating procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. The tracking area updating procedure is started as soon as possible and if still necessary, e.g. when access for "originating signalling" is granted on the current cell or when the UE moves to a cell where access for "originating signalling" is granted. In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [22]), the tracking area updating procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. Further UE behaviour is implementation specific, e.g. the tracking area updating procedure is started again after an implementation dependent time. In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [22]), a request for an exceptional event is received from the upper layers, then the tracking area updating procedure shall be started. NOTE 1: In NB-S1 mode, the EMM layer cannot receive the access barring alleviation indication from the lower layers (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [22]). If access is barred because of access class barring for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [22]) and if: - one of the MO MMTEL voice call is started, MO MMTEL video call is started or MO SMSoIP is started conditions is satisfied; - the upper layers request to send a mobile originated SMS over NAS or SMS over S102; or - the upper layers request user plane radio resources, ACDC is applicable to the request and the UE supports ACDC. then the tracking area updating procedure shall be started according to clause 5.5.3.2.2. The call type used shall be per annex D of this document. NOTE 2: If more than one of MO MMTEL voice call is started, MO MMTEL video call is started or MO SMSoIP is started conditions are satisfied, it is left to UE implementation to determine the call type based on Annex D of this document. If access is barred for a certain ACDC category (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [22]), and if the upper layers request user plane radio resources for a higher ACDC category and the UE supports ACDC, then the tracking area updating procedure shall be started according to clause 5.5.3.2.2. If an access request for an uncategorized application is barred due to ACDC (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [22]), and if the upper layers request user plane radio resources for a certain ACDC category and the UE supports ACDC, then the tracking area updating procedure shall be started according to clause 5.5.3.2.2. If the trigger for the tracking area updating procedure is the response to a paging request from the network and the NAS signalling connection establishment is rejected by the network, the tracking area updating procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. The tracking area updating procedure may be started if it is still necessary when access for "terminating calls" is granted or because of a cell change. aa) Lower layer failure to establish the RRC connection and: - the UE is in its HPLMN or in an EHPLMN (if the EHPLMN list is present); - the tracking area updating request is not for initiating a PDN connection for emergency bearer services; - the UE does not have a PDN connection for for emergency bearer services; - the UE supports being configured with CustomLLFailureRetry as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ]  [15A]); and - CustomLLFailureRetry leaf is present as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ]  [15A]); The UE shall increment the UE implementation specific attempt counter. If the UE implementation specific attempt counter is less than the value of MaxMinRetry, the UE shall start T3411 with the duration of MinRetryTimer. If the UE implementation specific attempt counter is equal to the value of MaxMinRetry, the UE shall start T3402 with the duration of MaxRetryTimer. The tracking area updating procedure shall be aborted, and the UE shall proceed as described below. b) Lower layer failure not covered in case aa) or release of the NAS signalling connection without "Extended wait time" and without "Extended wait time CP data" received from lower layers before the TRACKING AREA UPDATE ACCEPT or TRACKING AREA UPDATE REJECT message is received The tracking area updating procedure shall be aborted, and the UE shall proceed as described below. c) T3430 timeout The UE shall abort the procedure. The NAS signalling connection, if any, shall be released locally. NOTE 3: The NAS signalling connection can also be released if the UE deems that the network has failed the authentication check as specified in clause 5.4.2.7. The UE shall proceed as described below. d) TRACKING AREA UPDATE REJECT, other causes than those treated in clause 5.5.3.2.5, and cases of EMM cause values #22, #25, #31 and #78, if considered as abnormal cases according to clause 5.5.3.2.5 If the tracking area updating request is not for initiating a PDN connection for emergency bearer services, upon reception of the EMM causes #95, #96, #97, #99 and #111 the UE should set the tracking area updating attempt counter to 5. The UE shall proceed as described below. e) Change of cell into a new tracking area If a cell change into a new tracking area occurs before the tracking area updating procedure is completed, the tracking area updating procedure shall be aborted and re-initiated immediately. The UE shall set the EPS update status to EU2 NOT UPDATED. The UE shall proceed as described below. f) Tracking area updating and detach procedure collision EPS detach containing detach type "re-attach required" or "re-attach not required": If the UE receives a DETACH REQUEST message before the tracking area updating procedure has been completed, the tracking area updating procedure shall be aborted and the detach procedure shall be progressed. If the DETACH REQUEST message contains detach type "re-attach not required" and EMM cause #2 "IMSI unknown in HSS", the UE will follow the procedure as described below for the detach type "IMSI detach". EPS detach containing detach type "IMSI detach": If the UE receives a DETACH REQUEST message before the tracking area updating procedure has been completed, the DETACH REQUEST message shall be ignored and tracking area updating procedure shall be progressed. The UE shall proceed as described below. g) Tracking area updating and GUTI reallocation procedure collision If the UE receives a GUTI REALLOCATION COMMAND message before the tracking area updating procedure has been completed, this message shall be ignored and the tracking area updating procedure shall be progressed. h) Transmission failure of TRACKING AREA UPDATE REQUEST message indication from lower layers The tracking area updating procedure shall be aborted and re-initiated immediately. The UE shall set the EPS update status to EU2 NOT UPDATED. i) Transmission failure of TRACKING AREA UPDATE COMPLETE message indication with TAI change from lower layers If the current TAI is not in the TAI list, the tracking area updating procedure shall be aborted and re-initiated immediately. The UE shall set the EPS update status to EU2 NOT UPDATED. If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure. j) Transmission failure of TRACKING AREA UPDATE COMPLETE message indication without TAI change from lower layers It is up to the UE implementation how to re-run the ongoing procedure. k) "Extended wait time" from the lower layers If the TRACKING AREA UPDATE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the UE shall start timer T3346 with the "Extended wait time" value and reset the tracking area updating attempt counter. If the TRACKING AREA UPDATE REQUEST message did not contain the low priority indicator set to "MS is configured for NAS signalling low priority", the UE is operating in NB-S1 mode and the UE is not a UE configured to use AC11 – 15 in selected PLMN, then the UE shall start timer T3346 with the "Extended wait time" value and reset the tracking area updating attempt counter. In other cases the UE shall ignore the "Extended wait time". The UE shall abort the tracking area updating procedure, stay in the current serving cell, set the EPS update status to EU2 NOT UPDATED, change the state to EMM-REGISTERED.ATTEMPTING-TO-UPDATE and apply the normal cell reselection process. If the UE had used eDRX before initiating tracking area updating procedure, then the UE shall continue to use the eDRX with the extended DRX parameters IE received during the last attach or tracking area updating procedure. The UE shall proceed as described below. ka) "Extended wait time CP data" from the lower layers If the UE is operating in NB-S1 mode and supports the timer T3448, the UE shall start the timer T3448 with the "Extended wait time CP data" value. If the UE is operating in NB-S1 mode and does not support the timer T3448, the UE shall start the timer T3346 with the "Extended wait time CP data" value and reset the tracking area updating attempt counter. In other cases the UE shall ignore the "Extended wait time CP data". The UE shall abort the tracking area updating procedure, stay in the current serving cell, set the EPS update status to EU2 NOT UPDATED, change the state to EMM-REGISTERED.ATTEMPTING-TO-UPDATE and apply the normal cell reselection process. If the UE had used eDRX before initiating tracking area updating procedure, then the UE shall continue to use the eDRX with the extended DRX parameters IE received during the last attach or tracking area updating procedure. The UE shall proceed as described below. l) Timer T3346 is running The UE shall not start the tracking area updating procedure unless: - the UE is in EMM-CONNECTED mode; - the UE received a paging; - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; - the UE is requested by the upper layer for a CS fallback for emergency call or a 1xCS fallback for emergency call; - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and i) the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ]  [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ]  [17]); and ii) timer T3346 was not started when NAS signalling connection was established with RRC establishment cause set to "MO exception data"; - the UE 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, the timer T3402 and the timer T3411 are not running and the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, TRACKING AREA UPDATE REQUEST or EXTENDED SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority"; or - the MUSIM UE needs to request an IMSI offset value as specified in clause 5.5.3.2.2. The UE stays in the current serving cell and applies the normal cell reselection process. NOTE 4: It is considered an abnormal case if the UE needs to initiate a tracking 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 TAI of the current serving cell is not included in the TAI list or the TIN indicates "P-TMSI", the UE shall set the EPS update status to EU2 NOT UPDATED and change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. If the tracking area updating procedure needs to be initiated for an MO MMTEL voice call or an MO MMTEL video call is started, then a notification that the procedure was not initiated due to network congestion shall be provided to upper layers. NOTE 5: This can result in the upper layers requesting establishment of the originating voice call on an alternative manner e.g. requesting establishment of a CS voice call (see 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ]  [13E]). The UE shall proceed as described below. la) Timer T3448 is running The UE shall not start the tracking area updating procedure with the "signalling active" flag set, unless: - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE which is only using EPS services with control plane CIoT EPS optimization received a paging; or - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ]  [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ]  [17]). The UE stays in the current serving cell and applies the normal cell reselection process. The UE shall proceed as described below. m) Mobile originated detach required Detach due to removal of USIM or due to switch off: The tracking area updating procedure shall be aborted, and the UE initiated detach procedure shall be performed. Detach not due to removal of USIM and not due to switch off: The UE initiated detach procedure shall be initiated after successful completion of the tracking area updating procedure. o) Timer T3447 is running The UE shall not start the tracking area updating procedure with the "signalling active" flag set or the "active" flag set, unless: - the UE received a paging; - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; or - the MUSIM UE needs to request an IMSI offset value as specified in clause 5.5.3.2.2. The UE stays in the current serving cell and applies the normal cell reselection process. The tracking area update request procedure is started, if still necessary, when timer T3447 expires. p) Tracking area updating and paging procedure collision If the UE receives a CS SERVICE NOTIFICATION message before the tracking area updating procedure has been completed, the UE shall progress the tracking area updating procedure and respond to the CS SERVICE NOTIFICATION upon successful completion of the tracking area updating procedure. For the cases aa, b, c, d, e, f with detach type "re-attach required" or "re-attach not required" with EMM cause other than #2 "IMSI unknown in HSS", k and ka, the UE shall stop any ongoing transmission of user data. For the cases aa, b, c, d, k, ka, l and la, the UE shall proceed as follows: 1) Timer T3430 shall be stopped if still running. 2) For the cases aa, b, c, d, la k when the "Extended wait time" is ignored, and ka when the "Extended wait time CP data" is ignored, if the tracking area updating request is not for initiating a PDN connection for emergency bearer services, the tracking area updating attempt counter shall be incremented, unless it was already set to 5. 3) If the tracking area updating attempt counter is less than 5, the TAI of the current serving cell is included in the TAI list, the EPS update status is equal to EU1 UPDATED, the TIN does not indicate "P-TMSI" and the tracking area updating procedure is performed not due to an inter-system change from N1 mode to S1 mode and the tracking area updating procedure is not performed due to cases g, m, n, za, zc in clause 5.5.3.2.2: - the UE shall keep the EPS update status to EU1 UPDATED and enter state EMM-REGISTERED.NORMAL-SERVICE. The UE shall start timer T3411. - If in addition the TRACKING AREA UPDATE REQUEST indicated "periodic updating" or if tracking area updating procedure was initiated to recover NAS signalling connection due to "RRC Connection failure" from the lower layers, none of the other reasons for initiating the tracking area updating procedure listed in clause 5.5.3.2.2 was applicable, and the TRACKING AREA UPDATE REQUEST message did not include T3324 value IE, T3412 extended value IE or Extended DRX parameters IE, the timer T3411 may be stopped when the UE enters EMM-CONNECTED mode. - If timer T3411 expires the tracking area updating procedure is triggered again. 4) If the tracking area updating attempt counter is less than 5, and the TAI of the current serving cell is not included in the TAI list or the EPS update status is different to EU1 UPDATED or the TIN indicates "P-TMSI" or the tracking area updating procedure is performed due to an inter-system change from N1 mode to S1 mode or if the tracking area updating procedure is performed due to cases g, m, n, za, zc in clause 5.5.3.2.2: - for the cases k and l, the tracking area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. - for the case ka, if timer T3346 is started, the tracking area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. - for the case ka, if timer T3448 is started and the "signalling active" flag is set in the TRACKING AREA UPDATE REQUEST message, the tracking area updating procedure is started, if still necessary, when timer T3448 expires or is stopped. - for the case la, if the "signalling active" flag is set in the TRACKING AREA UPDATE REQUEST message, the tracking area updating procedure is started, if still necessary, when timer T3448 expires or is stopped. - for the cases aa, b, c, d, k when the "Extended wait time" is ignored, and ka when the "Extended wait time CP data" is ignored, if the tracking area updating request is not for initiating a PDN connection for emergency bearer services, the UE shall start timer T3411, shall set the EPS update status to EU2 NOT UPDATED and change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. When timer T3411 expires the tracking area updating procedure is triggered again. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ]  [13] for the abnormal case when a normal or periodic routing area updating procedure fails and the routing area updating attempt counter is less than 5 and the GPRS update status is different from GU1 UPDATED. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ]  [54] for the abnormal cases when a registration procedure for mobility and periodic registration fails and the registration attempt counter is less than 5 and the 5GS update status is different from 5U1 UPDATED. 5) If the tracking area updating attempt counter is equal to 5: - the UE shall start timer T3402 if the value of the timer as indicated by the network is not zero, shall set the EPS update status to EU2 NOT UPDATED; - if the value of T3402 as indicated by the network is zero, the UE shall perform the actions defined for the expiry of the timer T3402; - the UE shall delete the list of equivalent PLMNs and shall change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE or optionally to EMM-REGISTERED.PLMN-SEARCH 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 ]  [6]; and - if A/Gb mode, Iu mode or N1 mode is supported by the UE: - if A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GPRS update status as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ]  [13] for the abnormal case when a normal or periodic routing area updating procedure fails and the routing area updating attempt counter is equal to 5; - if the UE is operating in single-registration mode, the UE shall in addition handle the 5GS update status as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ]  [54] for the abnormal case when a registration procedure for mobility or periodic registration update performed over 3GPP access fails and the registration attempt counter is equal to 5; and - if the UE does not change to state EMM-REGISTERED.PLMN-SEARCH, the UE shall - except for case aa attempt to select GERAN, UTRAN or NG-RAN radio access technology. For case aa the UE may attempt to select GERAN, UTRAN or NG-RAN radio access technology and proceed with appropriate GMM or 5GMM specific procedures. Additionally, if the UE selects GERAN or UTRAN radio access technology, the UE may disable the E-UTRA capability as specified in clause 4.5. If No E-UTRA Disabling In 5GS is enabled at the UE (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ]  [50] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ]  [17]) and the UE selects NG-RAN radio access technology, it shall not disable the E-UTRA capability; otherwise, the UE may disable the E-UTRA capability as specified in clause 4.5. NOTE 6: Whether the UE requests RRC to treat the active E-UTRA cell as barred (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ]  [21]) is left to the UE implementation. If a GERAN or UTRAN cell is selected: - a UE in PS mode 1 or PS mode 2 of operation shall proceed with appropriate GMM specific procedures; - a UE in CS/PS mode 1 or CS/PS mode 2 of operation shall proceed with appropriate MM or GMM specific procedures. If an NG-RAN cell is selected, the UE shall proceed with appropriate 5GMM specific procedures.