EPS mobility management timers – UE side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON
EXPIRY

T3402

Default 12 min.

NOTE 1

EMM-DEREGISTERED

EMM-REGISTERED

At attach failure and the attempt counter is equal to 5.

At tracking area updating failure and the attempt counter is equal to 5.

ATTACH ACCEPT with EMM cause #16 or #17 and the attempt counter is equal to 5 for CS/PS mode 2 UE, or ATTACH ACCEPT with EMM cause #22, as described in subclause 5.5.1.3.4.3.

TRACKING AREA UPDATE ACCEPT with EMM cause #16 or #17 and the attempt counter is equal to 5 for CS/PS mode 2 UE, TRACKING AREA UPDATE ACCEPT with EMM cause #16 or #17 and the attempt counter is equal to 5 for CS/PS mode 1 UE with "IMS voice not available" and with a persistent EPS bearer context, or TRACKING AREA UPDATE ACCEPT with EMM cause #22, as described in subclause 5.5.3.3.4.3.

ATTACH ACCEPT and the attempt counter is equal to 5 as described in subclause 5.5.1.2.4A and 5.5.1.2.6A.

TRACKING AREA UPDATE ACCEPT and the attempt counter is equal to 5 as described in subclause 5.5.3.2.4A and 5.5.3.2.6A.

DETACH REQUEST with other EMM cause values than those treated in subclause 5.5.2.3.2 or no EMM cause IE and Detach type IE indicates "re-attach not required" as described in subclause 5.5.2.3.4.

ATTACH REQUEST sent

TRACKING AREA UPDATE REQUEST sent

NAS signalling connection released

 

Initiation of the attach procedure, if still required or TAU procedure

T3410

15s
NOTE 7
NOTE 8

In WB-S1/CE mode, 85s

EMM-REGISTERED-INITIATED

ATTACH REQUEST sent

ATTACH ACCEPT received

ATTACH REJECT received

Start T3411 or T3402 as described in subclause 5.5.1.2.6

T3411

10s

EMM-DEREGISTERED. ATTEMPTING-TO-ATTACH

 

EMM-REGISTERED. ATTEMPTING-TO-UPDATE

 

EMM-REGISTERED. NORMAL-SERVICE

At attach failure due to lower layer failure, T3410 timeout or attach rejected with other EMM cause values than those treated in subclause 5.5.1.2.5.

 

At tracking area updating failure due to lower layer failure, T3430 timeout or TAU rejected with other EMM cause values than those treated in subclause 5.5.3.2.5.

ATTACH ACCEPT and the attempt counter is less than 5 as described in subclause 5.5.1.2.4A and 5.5.1.2.6A.

TRACKING AREA UPDATE ACCEPT and the attempt counter is less than 5 as described in subclause 5.5.3.2.4A and 5.5.3.2.6A.

ATTACH REQUEST sent

TRACKING AREA UPDATE REQUEST sent

EMM-CONNECTED mode entered (NOTE 6)

Retransmission of the ATTACH REQUEST, if still required as described in subclause 5.5.1.2.6 or retransmission of TRACKING AREA UPDATE REQUEST

T3412

Default 54 min.

NOTE 2

NOTE 5

EMM-REGISTERED

In EMM-REGISTERED, when EMM-CONNECTED mode is left.

When entering state EMM-DEREGISTERED or when entering EMM-CONNECTED mode.

Initiation of the periodic TAU procedure if the UE is not attached for emergency bearer services or T3423 started under the conditions as specified in subclause 5.3.5.

 

Implicit detach from network if the UE is attached for emergency bearer services.

 

T3416

30s
NOTE 7
NOTE 8

In WB-S1/CE mode, 48s

EMM-REGISTERED-INITIATED

EMM-REGISTERED

EMM-DEREGISTERED-INITIATED

EMM-TRACKING-AREA-UPDATING-INITIATED

EMM-SERVICE-REQUEST-INITIATED

RAND and RES stored as a result of an EPS authentication challenge

SECURITY MODE COMMAND received

SERVICE REJECT received

SERVICE ACCEPT received

TRACKING AREA UPDATE ACCEPT received

AUTHENTICATION REJECT received

AUTHENTICATION FAILURE sent

EMM-DEREGISTERED, EMM-NULL or

EMM-IDLE mode entered

Delete the stored RAND and RES

T3417

5s
NOTE 7
NOTE 8

In WB-S1/CE mode, 51s

EMM-SERVICE-REQUEST-INITIATED

SERVICE REQUEST sent

EXTENDED SERVICE REQUEST sent in case f, g, i and j in subclause 5.6.1.1

EXTENDED SERVICE REQUEST sent with service type set to "packet services via S1" in case a, b, c, h and k in subclause 5.6.1.1

CONTROL PLANE SERVICE REQUEST sent as specified in subclause 5.6.1.2.2

Bearers have been set up

SERVICE REJECT received

SERVICE ACCEPT received

Indication of system change from lower layer received

cdma2000® 1xCS fallback rejection received

see subclause 5.6.1.4.2

Abort the procedure

T3417ext

10s

EMM-SERVICE-REQUEST-INITIATED

EXTENDED SERVICE REQUEST sent in case d in subclause 5.6.1.1

 

Inter-system change from S1 mode to A/Gb mode or Iu mode is completed

Inter-system change from S1 mode to A/Gb mode or Iu mode is failed

SERVICE REJECT received

Select GERAN or UTRAN

T3417ext-mt

4s

EMM-SERVICE-REQUEST-INITIATED

EXTENDED SERVICE REQUEST sent in case e in subclause 5.6.1.1 and the CSFB response was set to "CS fallback accepted by the UE"

Inter-system change from S1 mode to A/Gb mode or Iu mode is completed

Inter-system change from S1 mode to A/Gb mode or Iu mode is failed

SERVICE REJECT received

Select GERAN or UTRAN

T3418

20s
NOTE 7
NOTE 8

In WB-S1/CE mode, 38s

EMM-REGISTERED-INITIATED

EMM-REGISTERED

EMM-TRACKING-AREA-UPDATING-INITIATED

EMM-DEREGISTERED-INITIATED

EMM-SERVICE-REQUEST-INITIATED

AUTHENTICATION FAILURE (EMM cause = #20 "MAC failure" or #26 "non-EPS authentication unacceptable") sent

AUTHENTICATION REQUEST received or AUTHENTICATION REJECT received

or

SECURITY MODE COMMAND received

 

when entering EMM-IDLE mode

 

indication of transmission failure of AUTHENTICATION FAILURE message from lower layers

On first expiry, the UE should consider the network as false and follow item f of subclause 5.4.2.7, if the UE is not attached for emergency bearer services or access to RLOS.

 

On first expiry, the UE will follow subclause 5.4.2.7 under "For items c, d, and e:", if the UE is attached for emergency bearer services or if the UE is attached for access to RLOS.

T3420

15s
NOTE 7
NOTE 8

In WB-S1/CE mode, 33s

EMM-REGISTERED-INITIATED

EMM-REGISTERED

EMM-DEREGISTERED-INITIATED

EMM-TRACKING-AREA-UPDATING-INITIATED

EMM-SERVICE-REQUEST-INITIATED

AUTHENTICATION FAILURE (cause = #21 "synch failure") sent

AUTHENTICATION REQUEST received or AUTHENTICATION REJECT received

or

SECURITY MODE COMMAND received

 

when entering EMM-IDLE mode

 

indication of transmission failure of AUTHENTICATION FAILURE message from lower layers

On first expiry, the UE should consider the network as false and follow item f of subclause 5.4.2.7, if the UE is not attached for emergency bearer services or access to RLOS.

 

On first expiry, the UE will follow subclause 5.4.2.7 under "For items c, d, and e:", if the UE is attached for emergency bearer services or if the UE is attached for access to RLOS.

T3421

15s

NOTE 7

NOTE 8

In WB-S1/CE mode, 45s

EMM-DEREGISTERED-INITIATED

EMM-
REGISTERED.
IMSI-DETACH-
INITIATED

DETACH REQUEST sent with

the Detach type IE not indicating "switch off"

DETACH ACCEPT received

Retransmission of DETACH REQUEST

T3423

NOTE 3

EMM-REGISTERED

T3412 expires while ISR is activated and either T3346 is running or the UE is in one of the following states:

– EMM-REGISTERED.NO-CELL-AVAILABLE;

EMM-REGISTERED.PLMN-SEARCH;

EMM-REGISTERED.UPDATE-NEEDED; or

EMM-REGISTERED.LIMITED-SERVICE.

When entering state EMM-DEREGISTERED or when entering EMM-CONNECTED mode.

Set TIN to "P‑TMSI".

For A/Gb mode or Iu mode, see 3GPP TS 24.008 [13]

 

T3430

15s
NOTE 7
NOTE 8

In WB-S1/CE mode, 77s

EMM-TRACKING-AREA-UPDATING-INITIATED

TRACKING AREA UPDATE REQUEST sent

TRACKING AREA UPDATE ACCEPT received

TRACKING AREA UPDATE REJECT received

Start T3411 or T3402 as described in subclause 5.5.3.2.6

T3440

10s

EMM-DEREGISTERED EMM-REGISTERED

 

ATTACH REJECT, DETACH REQUEST, TRACKING AREA UPDATE REJECT with any of the EMM cause #3, #6, #7, #8, #11, #12, #13, #14, #15, #25, #31 or #35

SERVICE REJECT received with any of the EMM cause #3, #6, #7, #8, #11, #12, #13, #15, #25, #31, #35 or #39

TRACKING AREA UPDATE ACCEPT received after the UE sent TRACKING AREA UPDATE REQUEST in EMM-IDLE mode without the "active" flag set and without the "signalling active" flag set, and the user-plane radio bearers have not been setup

DETACH ACCEPT received after the UE sent DETACH REQUEST with detach type to "IMSI detach"

Upon receipt of ESM DATA TRANSPORT message as described in subclause 5.3.1.2.1 (NOTE 9)

AUTHENTICATION REJECT received

NAS signalling connection released

Bearers have been set up or a request for PDN connection for emergency bearer services or a CS emergency call is started

Upon receipt of ESM DATA TRANSPORT message as described in subclause 5.3.1.2.1 (NOTE 9)

Release the NAS signalling connection for the cases a), b) and c) as described in subclause 5.3.1.2

EMM-DEREGISTERED

EMM-DEREGISTERED.NORMAL-SERVICE

TRACKING AREA UPDATE REJECT, SERVICE REJECT with any of the EMM cause #9, #10 or #40

NAS signalling connection released

 

Release the NAS signalling connection for the cases d) and e) as described in subclause  5.3.1.2 and initiation of the attach procedure as specified in subclause 5.5.3.2.5, 5.5.3.3.5 or 5.6.1.5

T3442

NOTE 4

EMM-REGISTERED

SERVICE REJECT received with EMM cause #39 "CS service temporarily not available" with a non-zero T3442 value

TRACKING AREA UPDATE REQUEST sent

None

T3444

NOTE 11

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

– UE configured for eCall only mode enters EMM-IDLE mode after an eCall over IMS

– UE configured for eCall only mode moves from GERAN/UTRAN to E-UTRAN with timer T3242 (see 3GPP TS 24.008 [13]) running

– UE configured for eCall only mode enters 5GMM-IDLE mode (defined in 3GPP TS 24.501 [54]) after an eCall over IMS

– Removal of eCall only restriction

– Intersystem change from S1 mode to A/Gb or Iu mode

Perform eCall inactivity procedure in EPS as described in subclause 5.5.4.

Perform eCall inactivity procedure in 5GS as described in 3GPP TS 24.501 [54].

T3445

NOTE 12

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

– UE configured for eCall only mode enters EMM-IDLE mode after a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service

– UE configured for eCall only mode moves from GERAN/UTRAN to E-UTRAN with timer T3243 (see 3GPP TS 24.008 [13]) running

– UE configured for eCall only mode enters 5GMM-IDLE mode (defined in 3GPP TS 24.501 [54]) after a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service

Removal of eCall only restriction

– Intersystem change from S1 mode to A/Gb or Iu mode

Perform eCall inactivity procedure in EPS as described in subclause 5.5.4.

Perform eCall inactivity procedure in 5GS as described in 3GPP TS 24.501 [54].

T3447

NOTE 2

All except EMM-NULL

NAS signalling connection release that was not established for paging, attach without PDN connection or tracking area update request without "active" or "signalling active" flag set.

N1 NAS signalling connection release that was not established due to paging, or REGISTRATION REQUEST for initial registration with Follow-on request indicator set to "No follow-on request pending", or REGISTRATION REQUEST for mobility and periodic registration update with Follow-on request indicator set to "No follow-on request pending" and without Uplink data status IE included (defined in 3GPP TS 24.501 [54]).

ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT without the T3447 value IE.

Inter-system change from S1 mode to A/Gb mode or Iu mode is completed

REGISTRATION ACCEPT without the T3447 value IE (defined in 3GPP TS 24.501 [54]). CONFIGURATION UPDATE COMMAND with the T3447 value IE set to zero or deactivated (defined in 3GPP TS 24.501 [54]).

Allowed to initiate transfer of uplink user data

T3448

NOTE 10

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message or SERVICE ACCEPT message received with a non-zero T3448 value.

SERVICE REJECT message received with EMM cause #22 "Congestion" and a non-zero T3448 value.

REGISTRATION ACCEPT message or SERVICE ACCEPT message received with a non-zero T3448 value(defined in 3GPP TS 24.501 [54])

SERVICE REJECT message received with 5GMM cause #22 "Congestion" and a non-zero T3448 value(defined in 3GPP TS 24.501 [54])

SERVICE ACCEPT message or TRACKING AREA UPDATE ACCEPT message received without T3448 value

SERVICE ACCEPT message or REGISTRATION ACCEPT message received without T3448 value(defined in 3GPP TS 24.501 [54])

 

Allowed to initiate transfer of user data via the control plane

T3449

5s

NOTE 7
NOTE 8

In WB-S1/CE mode, 51s

EMM-REGISTERED

Bearers have been set up

SECURITY MODE COMMAND message received

 

SERVICE ACCEPT message received

Security protected ESM message or a security protected EMM message not related to an EMM common procedure received

SERVICE ACCEPT message considered as a protocol error and EMM STATUS returned

NOTE 1: The cases in which the default value of this timer is used are described in subclause 5.3.6.

NOTE 2: The value of this timer is provided by the network operator during the attach and tracking area updating procedures.

NOTE 3: The value of this timer may be provided by the network in the ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT message. The default value of this timer is identical to the value of T3412.

NOTE 4: The value of this timer is provided by the network operator when a service request for CS fallback is rejected by the network with EMM cause #39 "CS service temporarily not available".

NOTE 5: The default value of this timer is used if the network does not indicate a value in the TRACKING AREA UPDATE ACCEPT message and the UE does not have a stored value for this timer.

NOTE 6: The conditions for which this applies are described in subclause 5.5.3.2.6.

NOTE 7: In NB-S1 mode, the timer value shall be calculated as described in subclause 4.7.

NOTE 8: In WB-S1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this table for the case of WB-S1/CE mode (see subclause 4.8).

NOTE 9: It is possible that the UE does not stop or start timer T3440 upon receipt of ESM DATA TRANSPORT message as described in subclause 5.3.1.2.1.

NOTE 10: The timer value is provided by the network in the ATTACH ACCEPT, TRACKING AREA UPDATE ACCEPT, SERVICE ACCEPT, SERVICE REJECT or REGISTRATION ACCEPT message, or chosen randomly from a default value range of 15 – 30 minutes.

NOTE 11: If the timer is started due to a UE configured for eCall only mode moving from GERAN/UTRAN to E-UTRAN with timer T3242 (see 3GPP TS 24.008 [13]) running, the UE starts the timer with a value set to the time left on timer T3242. Otherwise the UE starts the timer with a value set to 12 hours.

NOTE 12: If the timer is started due to a UE configured for eCall only mode moving from GERAN/UTRAN to E-UTRAN with timer T3243 (see 3GPP TS 24.008 [13]) running, the UE starts the timer with a value set to the time left on timer T3243. Otherwise the UE starts the timer with a value set to 12 hours.

 

Source: 3GPP 24.301, for latest update please visit 3GPP official file location 

Leave a Reply

Your email address will not be published. Required fields are marked *