10 List of system parameters
24.3013GPPNon-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)Release 18Stage 3TS
10.1 General
The description of timers in the following tables should be considered a brief summary.
10.2 Timers of EPS mobility management
Table 10.2.1: EPS mobility management timers – UE side
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON |
---|---|---|---|---|---|
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 clause 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 clause 5.5.3.3.4.3. ATTACH ACCEPT and the attempt counter is equal to 5 as described in clause 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 clause 5.5.3.2.4A and 5.5.3.2.6A. DETACH REQUEST with other EMM cause values than those treated in clause 5.5.2.3.2 or no EMM cause IE and Detach type IE indicates "re-attach not required" as described in clause 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 tracking area updating procedure |
T3410 |
15s In WB-S1/CE mode, 85s NOTE 15 |
EMM-REGISTERED-INITIATED |
ATTACH REQUEST sent |
ATTACH ACCEPT received ATTACH REJECT received |
Start T3411 or T3402 as described in clause 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 clause 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 clause 5.5.3.2.5. ATTACH ACCEPT and the attempt counter is less than 5 as described in clause 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 clause 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 clause 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 tracking area updating procedure if the UE is not attached for emergency bearer services or T3423 started under the conditions as specified in clause 5.3.5. Implicit detach from network if the UE is attached for emergency bearer services. |
T3416 |
30s In WB-S1/CE mode, 48s NOTE 15 |
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 13 In WB-S1/CE mode, 51s NOTE 15 |
EMM-SERVICE-REQUEST-INITIATED |
SERVICE REQUEST sent or EXTENDED SERVICE REQUEST sent with service type set to "packet services via S1" in case a, b, c, h, k, l and o in clause 5.6.1.1 EXTENDED SERVICE REQUEST sent in case f, g, i, j, p and q in clause 5.6.1.1 CONTROL PLANE SERVICE REQUEST sent as specified in clause 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 clause 5.6.1.4.2 |
Abort the procedure |
T3417ext |
10s |
EMM-SERVICE-REQUEST-INITIATED |
EXTENDED SERVICE REQUEST sent in case d in clause 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 clause 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 In WB-S1/CE mode, 38s NOTE 15 |
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 clause 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 clause 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 In WB-S1/CE mode, 33s NOTE 15 |
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 clause 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 clause 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 NOTE 15 |
EMM-DEREGISTERED-INITIATED EMM- |
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 In WB-S1/CE mode, 77s NOTE 15 |
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 clause 5.5.3.2.6 |
T3440 |
10s NOTE 7 (applicable to case k) in clause 5.3.1.2.1) NOTE 8 In WB-S1/CE mode, 34s (applicable to case k) in clause 5.3.1.2.1) NOTE 14 NOTE 15 |
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, #22, #25, #31, #35 or #42 SERVICE REJECT received with any of the EMM cause #3, #6, #7, #8, #11, #12, #13, #15, #22, #25, #31, #35, #39 or #42 TRACKING AREA UPDATE ACCEPT described in clause 5.3.1.2.1 case b)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 clause 5.3.1.2.1 (NOTE 9) AUTHENTICATION REJECT received SERVICE ACCEPT received as described in clause 5.3.1.2.1 case j) DETACH ACCEPT received as described in clause 5.3.1.2.1 case l) |
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 clause 5.3.1.2.1 (NOTE 9) |
Release the NAS signalling connection for the cases a), b), c) and l)as described in clause 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 clause 5.3.1.2 and initiation of the attach procedure as specified in clause 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 or enters 5GMM-CONNECTED mode with RRC inactive indication (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 clause 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 or enters 5GMM-CONNECTED mode with RRC inactive indication (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 clause 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 In WB-S1/CE mode, 51s NOTE 15 |
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 clause 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 clause 5.5.3.2.6. NOTE 7: In NB-S1 mode, the timer value shall be calculated as described in clause 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 clause 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 clause 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. NOTE 13: Based on implementation, the timer may be set to a value between 250ms and 5s when the MUSIM UE indicates "NAS signalling connection release" or "Rejection of paging" in the UE request type IE of the EXTENDED SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message. NOTE 14: Based on implementation, the timer may be set to a value between 250ms and 10s when the MUSIM UE indicated "NAS signalling connection release" or "Rejection of paging" in the UE request type IE of the EXTENDED SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message; or indicated "NAS signalling connection release" in the UE request type IE of the TRACKING AREA UPDATE REQUEST message. NOTE 15: In satellite E-UTRAN access, the value for WB-S1/CE mode shall be selected when satellite E-UTRAN RAT type is "WB-E-UTRAN(MEO)", " WB-E-UTRAN(GEO)", "NB-IoT(MEO)", "NB-IoT(GEO)", "LTE-M(MEO)" or "LTE-M(GEO)". |
Table 10.2.2: EPS mobility management timers – network side
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON THE |
T3413 |
NOTE 2 |
EMM-REGISTERED |
Paging procedure for EPS services initiated |
Paging procedure for EPS services completed Paging procedure is aborted |
Network dependent |
T3415 |
NOTE 6 |
EMM-REGISTERED |
Paging procedure for EPS services initiated for a UE which the network accepted the request to use eDRX and the UE does not have a PDN connection for emergency bearer services |
Paging procedure for EPS services completed Paging procedure is aborted |
Paging procedure is aborted and the network proceeds as specified in 3GPP TS 23.401 [10] |
T3422 |
6s In WB-S1/CE mode, 24s NOTE 11 |
EMM-DEREGISTERED-INITIATED |
DETACH REQUEST sent |
DETACH ACCEPT received |
Retransmission of DETACH REQUEST |
T3447 |
NOTE 2 |
All |
UE transitions from EMM-CONNECTED mode to EMM-IDLE mode except when UE was in EMM-CONNECTED mode due to paging, attach without PDN connection or tracking area update request without "active" or "signalling active" flag set UE transitions from 5GMM-CONNECTED mode to 5GMM-IDLE mode except when UE was in 5GMM-CONNECTED mode due to paging, 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. |
ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT without the T3447 value IE. At MME during inter-system change from S1 mode to N1 mode. 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]). At AMF during inter-system change from N1 mode to S1 mode defined in 3GPP TS 24.501 [54]). |
Allow the UE to initiate a connection for transfer of uplink user data. |
T3450 |
6s In WB-S1/CE mode, 18s NOTE 11 |
EMM-COMMON-PROC-INIT |
ATTACH ACCEPT sent TRACKING AREA UPDATE ACCEPT sent with GUTI TRACKING AREA UPDATE ACCEPT sent with TMSI GUTI REALLOCATION COMMAND sent |
ATTACH COMPLETE received TRACKING AREA UPDATE COMPLETE received GUTI REALLOCATION COMPLETE received |
Retransmission of the same message type, i.e. ATTACH ACCEPT, TRACKING AREA UPDATE ACCEPT or GUTI REALLOCATION COMMAND |
T3460 |
6s In WB-S1/CE mode, 24s NOTE 11 |
EMM-COMMON-PROC-INIT |
AUTHENTICATION REQUEST sent SECURITY MODE COMMAND sent |
AUTHENTICATION RESPONSE received AUTHENTICATION FAILURE received SECURITY MODE COMPLETE received SECURITY MODE REJECT received |
Retransmission of the same message type, i.e. AUTHENTICATION REQUEST or SECURITY MODE COMMAND |
T3470 |
6s In WB-S1 mode, 24s NOTE 11 |
EMM-COMMON-PROC-INIT |
IDENTITY REQUEST sent |
IDENTITY RESPONSE received |
Retransmission of IDENTITY REQUEST |
Mobile reachable |
NOTE 4 |
All except EMM-DEREGISTERED |
Entering EMM-IDLE mode |
NAS signalling connection established |
Network dependent, but typically paging is halted on 1st expiry if the UE is not attached for emergency bearer services. Implicitly detach the UE which is attached for emergency bearer services. |
Implicit detach timer |
NOTE 3 |
All except EMM-DEREGISTERED |
The mobile reachable timer expires while the network is in EMM-IDLE mode |
NAS signalling connection established |
Implicitly detach the UE on 1st expiry |
active timer |
NOTE 5 |
All except EMM-DEREGISTERED |
Entering EMM-IDLE mode |
NAS signalling connection established |
Network dependent, but typically paging is halted on 1st expiry |
NOTE 1: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description. NOTE 2: The value of this timer is network dependent. NOTE 3: The value of this timer is network dependent. If ISR is activated, the default value of this timer is 4 minutes greater than T3423. NOTE 4: The default value of this timer is 4 minutes greater than T3412. If T3346 is larger than T3412 and the MME includes timer T3346 in the TRACKING AREA UPDATE REJECT message or SERVICE REJECT message, the value of the mobile reachable timer and implicit detach timer is set such that the sum of the timer values is greater than T3346. If the UE is attached for emergency bearer services, the value of this timer is set equal to T3412. NOTE 5: If the MME includes timer T3324 in the ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message and if the UE is not attached for emergency bearer services and has no PDN connection for emergency bearer services, the value of this timer is equal to the value of timer T3324. NOTE 6: The value of this timer is smaller than the value of timer T3-RESPONSE (see 3GPP TS 29.274 [16D]). NOTE 7: In NB-S1 mode, then the timer value shall be calculated as described in clause 4.7. NOTE 8: In NB-S1 mode, then the timer value shall be calculated by using an NAS timer value which is network dependent. NOTE 9: 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 clause 4.8). NOTE 10: In WB-S1 mode, if the UE supports CE mode B, then the timer value shall be calculated by using an NAS timer value which value is network dependent. NOTE 11: In satellite E-UTRAN access, the value for WB-S1/CE mode shall be selected when satellite E-UTRAN RAT type is "WB-E-UTRAN(MEO)", " WB-E-UTRAN(GEO)", "NB-IoT(MEO)", "NB-IoT(GEO)", "LTE-M(MEO)" or "LTE-M(GEO)". |
10.3 Timers of EPS session management
Table 10.3.1: EPS session management timers – UE side
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON THE |
T3480 |
8s In WB-S1/CE mode, 16s NOTE 4 |
PROCEDURE TRANSACTION PENDING |
BEARER RESOURCE ALLOCATION REQUEST sent |
ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST received or MODIFY EPS BEARER CONTEXT REQUEST received or BEARER RESOURCE ALLOCATION REJECT received |
Retransmission of BEARER RESOURCE ALLOCATION REQUEST |
T3481 |
8s In WB-S1/CE mode, 16s NOTE 4 |
PROCEDURE TRANSACTION PENDING |
BEARER RESOURCE MODIFICATION REQUEST sent |
ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST received or MODIFY EPS BEARER CONTEXT REQUEST received or DEACTIVATE EPS BEARER CONTEXT REQUEST received or BEARER RESOURCE MODIFICATION REJECT received |
Retransmission of BEARER RESOURCE MODIFICATION REQUEST |
T3482 |
8s In WB-S1/CE mode, 16s NOTE 4 |
PROCEDURE TRANSACTION PENDING |
An additional PDN connection is requested by the UE which is not combined in attach procedure |
ACTIVE DEFAULT EPS BEARER CONTEXT REQUEST received or PDN CONNECTIVITY REJECT received |
Retransmission of PDN CONNECTIVITY REQUEST |
T3492 |
6s In WB-S1/CE mode, 14s NOTE 4 |
PROCEDURE TRANSACTION PENDING |
PDN DISCONNECT REQUEST sent |
DEACTIVATE EPS BEARER CONTEXT REQUEST received or PDN DISCONNECT REJECT received |
Retransmission of PDN DISCONNECT REQUEST |
T3493 |
4s In WB-S1/CE mode, 12s NOTE 4 |
PROCEDURE TRANSACTION PENDING |
REMOTE UE REPORT sent |
REMOTE UE REPORT RESPONSE received |
Retransmission of REMOTE UE REPORT |
Back-off timer |
defined in 3GPP TS 24.008 [13] |
||||
NOTE 1: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description. NOTE 2: In NB-S1 mode, then the timer value shall be calculated as described in clause 4.7. NOTE 3: 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 clause 4.8). NOTE 4: In satellite E-UTRAN access, the value for WB-S1/CE mode shall be selected when satellite E-UTRAN RAT type is "WB-E-UTRAN(MEO)", " WB-E-UTRAN(GEO)", "NB-IoT(MEO)", "NB-IoT(GEO)", "LTE-M(MEO)" or "LTE-M(GEO)". |
NOTE 1: The back-off timer is used to describe a logical model of the required UE behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp.
NOTE 2: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the UE. Whether the UE uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to UE implementation.
Table 10.3.2: EPS session management timers – network side
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON THE |
T3485 |
8s In WB-S1/CE mode, 16 NOTE 4s |
BEARER CONTEXT ACTIVE PENDING |
ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST sent ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST sent |
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT received or ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT received or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT received or ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT received |
Retransmission of the same message |
T3486 |
8s In WB-S1/CE mode, 16s NOTE 4 |
BEARER CONTEXT MODIFY PENDING |
MODIFY EPS BEARER CONTEXT REQUEST sent |
MODIFY EPS BEARER CONTEXT ACCEPT received or MODIFY EPS BEARER CONTEXT REJECT received |
Retransmission of MODIFY EPS BEARER CONTEXT REQUEST |
T3489 |
4s In WB-S1/CE mode, 12s NOTE 4 |
PROCEDURE TRANSACTION PENDING |
ESM INFORMATION REQUEST sent |
ESM INFORMATION RESPONSE received |
Retransmission of ESM INFORMATION REQUEST on 1st and 2nd expiry only |
T3495 |
8s In WB-S1/CE mode, 16s NOTE 4 |
BEARER CONTEXT INACTIVE PENDING |
DEACTIVATE EPS BEARER CONTEXT REQUEST sent |
DEACTIVATE EPS BEARER CONTEXT ACCEPT received |
Retransmission of DEACTIVATE EPS BEARER CONTEXT REQUEST |
NOTE 1: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description. NOTE 2: In NB-S1 mode, then the timer value shall be calculated as described in clause 4.7. NOTE 3: 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 clause 4.8). NOTE 4: In satellite E-UTRAN access, the value for WB-S1/CE mode shall be selected when satellite E-UTRAN RAT type is "WB-E-UTRAN(MEO)", " WB-E-UTRAN(GEO)", "NB-IoT(MEO)", "NB-IoT(GEO)", "LTE-M(MEO)" or "LTE-M(GEO)". |
Annex A (informative):
Cause values for EPS mobility management