11 List of system parameters
24.0083GPPCore network protocolsMobile radio interface Layer 3 specificationRelease 18Stage 3TS
The description of timers in the following table should be considered a brief summary. The precise details are found in clauses 3 to 6, which should be considered the definitive descriptions.
11.1 Timers and counters for radio resource management
See 3GPP TS 44.018 [84].
11.2 Timers of mobility management
Table 11.1/3GPP TS 24.008: Mobility management timers – MS-side
|
TIMER NUM. |
MM |
TIME |
CAUSE FOR START |
NORMAL STOP |
AT THE EXPIRY |
|---|---|---|---|---|---|
|
T3210 |
LOCATION UPDATING INITIATED |
20s |
– LOCATION UPDATING REQUEST sent |
– LOCATION UPDATING ACCEPT – LOCATIONG UPDATING_REJECT – AUTHTICATION _REJECT – Lower layer failure |
Start T3211 |
|
T3211 |
MM IDLE, |
15s |
– LOCATION UPDATING REJECT with other cause values as described in section 4.4.4.9 – lower layer failure or RR connection released after RR connection abort during location updating procedure |
– cell change – request for MM connection establishment – change of LA |
Restart the location updating procedure. |
|
T3212 |
MM IDLE |
Note 1 |
– termination of MM service or MM signalling |
– initiation of MM service or MM signalling |
initiate periodic updating |
|
T3213 |
LOCATION UPDATING INITIATED |
4s |
– location updating failure |
– change of BCCH parameter |
new random attempt |
|
T3214 |
LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED |
20s |
AUTHENTICATION FAILURE Cause = ‘MAC failure’ or ‘GSM authentication unacceptable’ sent |
– AUTHENTICATION REQUEST received – AUTHENTICATION REJECT received – Lower layer failure |
Consider the network as ’false’ (see 4.3.2.6.1) |
|
T3216 |
LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED |
15s |
AUTHENTICATION FAILURE Cause = Synch failure sent |
– AUTHENT REQUEST received – AUTHENTICATION REJECT received – Lower layer failure |
Consider the network as ’false’ (see 4.3.2.6.1) |
|
T3218 |
LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED |
20s |
– RAND and RES stored as a result of of a UMTS authentication challenge – RAND and SRES stored as a result of of a GSM authentication challenge |
– CIPHERING MODE COMMAND received (A/Gb mode only) – SECURITY MODE COMMAND received (Iu mode only) CM SERVICE ACCEPT received CM SERVICE REJECT received – LOCATION UPDATING ACCEPT received – AUTHENTICATION REJECT received – AUTHENTICATION FAILURE sent – enter MM IDLE or NULL |
Delete the stored RAND and either RES (if it was a UMTS authentication challenge) or SRES (if it was a GSM authentication challenge) |
|
T3220 |
IMSI DETACH INITIATED |
5s |
– IMSI DETACH |
– release from RM-sublayer |
enter Null or Idle, ATTEMPTING TO UPDATE |
|
T3230 |
WAIT FOR OUTGOING MM CONNECTION WAIT FOR ADDITIONAL OUTGOING MM CONNECTION WAIT FOR REESTABLISH |
15s |
– CM SERVICE REQUEST CM RE-ESTABLISHMENT REQUEST |
– Cipher mode setting – CM SERVICE REJECT received – CM SERVICE ACCEPT received – CM SERVICE ABORT sent |
provide release ind. |
|
T3240 |
WAIT FOR NETWORK COMMAND LOCATION UPDATE REJECTED |
10s |
see subclause 11.2.1 |
see subclause 11.2.1 |
abort the RR connection |
|
T3241 |
RR CONNECTION RELEASE NOT ALLOWED |
300s |
see subclause 11.2.1 |
see subclause 11.2.1 |
abort the RR connection |
|
T3242 |
All except NULL |
Note 5 |
eCall only MS enters MM IDLE state after an emergency call – eCall only MS capable of eCall over IMS performs intersystem change from S1 mode to Iu or A/Gb mode while timer T3444 (see 3GPP TS 24.301 [120]) is running |
– Removal of eCall only restriction – Intersystem change from Iu or A/Gb mode to S1 mode for MS capable of eCall over IMS |
Perform eCall Inactivity procedure in subclause 4.4.7 or GMM eCall inactivity procedure in subclause 4.7.15 |
|
T3243 |
All except NULL |
Note 6 |
eCall only MS enters MM IDLE state after a test/reconfiguration call – eCall only MS capable of eCall over IMS enters PMM-IDLE (Iu mode) state after a test/reconfiguration call – return to packet idle mode at eCall only MS capable of eCall over IMS after a test/reconfiguration call (A/Gb mode) – eCall only MS capabable of eCall over IMS performs intersystem change from S1 mode to Iu or A/Gb mode while timer T3445 (see 3GPP TS 24.301 [120]) is running |
– Removal of eCall only restriction – Intersystem change from Iu or A/Gb mode to S1 mode for MS capable of eCall over IMS |
Perform eCall Inactivity procedure in subclause 4.4.7 or GMM eCall inactivity procedure in subclause 4.7.15 |
|
T3245 |
All except NULL |
Note 2 |
see subclause 4.1.1.6 (A/Gb or Iu mode only) see subclause 5.3.7a in 3GPP TS 24.301[120] (S1 mode only) see subclause 5.3.19a in 3GPP TS 24.501 [167] (N1 mode only) see subclause 4.6 in 3GPP TS 24.502 [178] (N1 mode only) |
– SIM/USIM is removed |
see subclause 4.1.1.6 (A/Gb or Iu mode only) see subclause 5.3.7a in 3GPP TS 24.301[120] (S1 mode only) see subclause 5.3.19a in 3GPP TS 24.501 [167] (N1 mode only) see subclause 4.6 in 3GPP TS 24.502 [178] (N1 mode only) |
|
T3246 |
LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION WAIT FOR ADDITIONAL OUTGOING MM CONNECTION WAIT FOR REESTABLISH |
Note 3 |
LOCATION UPDATING REJECT or CM SERVICE REJECT received with a timer value for T3246; "Extended wait time" for CS domain from the lower layers |
– paging – see subclause 4.1.1.7 |
Restart the Location update procedure or CM service request procedure, dependent on MM state and update status |
|
T3247 |
All except NULL |
Note 4 |
see subclauses 4.1.1.6A, 4.3.2.5 and 4.7.7.5 (A/Gb or Iu mode only) see subclauses 5.3.7B and 5.4.2.5 in 3GPP TS 24.301 [120] (S1 mode only) see subclauses 5.3.20, 5.4.1.2.2.11, 5.4.1.2.3.1, 5.4.1.2.3A.1, 5.4.1.2.3B.1 and 5.4.1.3.5 in 3GPP TS 24.501 [167] (N1 mode only) |
– SIM/USIM is removed or the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated (see 3GPP TS 23.122 [14] and 3GPP TS 24.501 [167]); or – the MS is switched off |
see subclause 4.1.1.6A (A/Gb or Iu mode only) see subclause 5.3.7B in 3GPP TS 24.301 [120] (S1 mode only) see subclauses 5.3.20 in 3GPP TS 24.501 [167] (N1 mode only) |
|
NOTE 1: The timeout value is broadcasted in a SYSTEM INFORMATION message or received in a LOCATION UPDATING ACCEPT message. NOTE 2: The MS starts the timer with a random value, uniformly drawn from the range between 12h and 24h. NOTE 3: The timer value is provided by the network in a LOCATION UPDATING REJECT or a CM SERVICE REJECT message or as an "Extended wait time" value by the lower layers, or chosen randomly from a default value range of 15 – 30 minutes. NOTE 4: The MS starts the timer with a random value, uniformly drawn from the range between 15 minutes and 30 minutes for 5GMM cause value #74 as specified in 3GPP TS 24.501 [167] or between 30 minutes and 60 minutes for other cause values. NOTE 5: If the timer is started by an eCall only MS capable of eCall over IMS due to performing intersystem change from S1 mode to Iu or A/Gb mode while timer T3444 (see 3GPP TS 24.301 [120]) is running, the MS starts the timer with a value set to the time left on timer T3444. Otherwise the MS starts the timer with a value set to 12 hours. NOTE 6: If the timer is started by an eCall only MS capable of eCall over IMS due to performing intersystem change from S1 mode to Iu or A/Gb mode while timer T3445 (see 3GPP TS 24.301 [120]) is running, the MS starts the timer with a value set to the time left on timer T3445. Otherwise the MS starts the timer with a value set to 12 hours. |
|||||
Table 11.2/3GPP TS 24.008: Mobility management timers – network-side
|
TIMER NUM. |
MM |
TIME |
CAUSE FOR START |
NORMAL STOP |
AT THE EXPIRY |
AT THE SECOND EXPIRY |
|
T3250 |
TMSI REALLOCATION INITIATED |
12s |
TMSI REALLOCATION COMMAND or LOCATION UPDATING ACCEPT with new TMSI sent |
TMSI REALLOCATION COMPLETE received |
Optionally Release RR connection |
|
|
T3255 |
Note 2 |
LOCATION UPDATING ACCEPT sent with"Follow on Proceed" |
CM SERVICE REQUEST |
Release RR Connection or use for mobile station terminating call |
||
|
T3260 |
AUTHENTICATION INITIATED |
12s |
AUTHENTICATION REQUEST sent |
AUTHENTICATION RESPONSE received AUTHENTICATION FAILURE received |
Optionally Release RR connection |
|
|
T3270 |
IDENTIFICATION INITIATED |
12s |
IDENTITY REQUEST sent |
IDENTITY RESPONSE received |
Optionally Release RR connection |
NOTE 2: The value of this timer is not specified by this recommendation.
11.2.1 Timer T3240 and Timer T3241
Timer T3240 is started in the mobile station when:
– the mobile station receives a LOCATION UPDATING ACCEPT message completing a location updating procedure in the cases specified in subclauses 4.4.4.6 and 4.4.4.8;
– the mobile station receives a LOCATION UPDATING REJECT message in the cases specified in subclause 4.4.4.7;
– the mobile station has sent a CM SERVICE ABORT message as specified in subclause 4.5.1.7;
– the mobile station has released or aborted all MM connections in the cases specified in 4.3.2.5, 4.3.5.2, 4.5.1.1, and 4.5.3.1;
– the mobile station receives the paging message from network and enter the MM state 9 (WAIT FOR NETWORK COMMAND).
Timer T3240 is stopped, reset, and started again at receipt of an MM message.
Timer T3240 is stopped and reset (but not started) at receipt of a CM message that initiates establishment of an CM connection (an appropriate SETUP, REGISTER, or CP-DATA message as defined in 3GPP TS 24.008, 3GPP TS 24.010 [21] or 3GPP TS 24.011 [22]).
If timer T3240 expires, the MS shall abort the RR connection and enter the MM state MM IDLE.
Timer T3241 is started in the mobile station when entering MM state RR CONNECTION RELEASE NOT ALLOWED.
Timer T3241 is stopped and reset (but not started) when the MM state RR CONNECTION RELEASE NOT ALLOWED is left.
If timer T3241 expires, the MS shall abort the RR connection and enter the MM state MM IDLE.
11.2.2 Timers of GPRS mobility management
Table 11.3/3GPP TS 24.008: GPRS Mobility management timers – MS side
|
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON THE |
|
T3310 |
15s NOTE 2 |
GMM- |
ATTACH REQUEST sent |
ATTACH ACCEPT received ATTACH REJECT received |
Retransmission of ATTACH REQUEST |
|
T3311 |
15s |
GMM-DEREG ATTEMPTING TO ATTACH or GMM-REG ATTEMPTING TO UPDATE GMM-REG NORMAL SERVICE |
ATTACH REJECT with other cause values as described in chapter ‘GPRS Attach’ ROUTING AREA UPDATE REJECT with other cause values as described in chapter ‘Routing Area Update’ Low layer failure |
Change of the routing area GPRS attach procedure initiated RAU procedure initiated Iu mode – PMM CONNECTED mode entered (NOTE 1) A/Gb mode – READY timer is started (Note 1) |
Restart of the GPRS attach or the RAU procedure with updating of the relevant attempt counter |
|
T3316 |
30s NOTE 2 |
GMM- GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT |
RAND and RES stored as a result of a UMTS authentication challenge RAND and SRES stored as a result of a GSM authentication challenge |
Security mode setting SERVICE ACCEPT received. (Iu mode only) SERVICE REJECT ROUTING AREA UPDATE ACCEPT received AUTHENTICATION AND CIPHERING REJECT received AUTHENTICATION AND CIPHERING FAILURE sent Enter GMM-DEREGISTERED, |
Delete the stored RAND, and either RES (if it was a UMTS authentication challenge) or SRES (if it was a GSM authentication challenge) |
|
T3318 |
20s NOTE 2 |
GMM- GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only) |
AUTHENTICATION AND CIPHERING FAILURE (cause=’MAC failure’ or ‘GSM authentication unacceptable’) sent |
AUTHENTICATION AND CIPHERING REQUEST received AUTHENTICATION AND CIPHERING REJECT received Lower layer failure PS signalling connection released (Iu mode only) Inter-system change to S1 mode performed GPRS services suspended (Gb mode only) |
On first expiry, the MS should consider the network as false and will follow subclause 4.7.7.6.1, if the MS is not attached for emergency bearer services. On the first expiry, the MS will follow subclause 4.7.7.6, under "for items f and g", if the MS is attached for emergency bearer services. |
|
T3320 |
15s NOTE 2 |
GMM- GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only) |
AUTHENTICATION AND CIPHERING FAILURE (cause=synch failure) sent |
AUTHENTICATION AND CIPHERING REQUEST received AUTHENTICATION AND CIPHERING REJECT received Lower layer failure PS signalling connection released (Iu mode only) Inter-system change to S1 mode performed GPRS services suspended (Gb mode only) |
On first expiry, the MS should consider the network as false and will follow the subclause 4.7.7.6.1, if the MS is not attached for emergency bearer services. On the first expiry, the MS will follow subclause 4.7.7.6, under "for items f and g", if the MS is attached for emergency bearer services. |
|
T3321 |
15s NOTE 2 |
GMM- DEREG-INIT GMM-REG. |
DETACH REQUEST sent |
DETACH ACCEPT received |
Retransmission of the DETACH REQUEST |
|
T3330 |
15s NOTE 2 |
GMM-ROUTING-UPDATING-INITIATED |
ROUTING AREA UPDATE REQUEST sent |
ROUTING AREA UPDATE ACCEPT received ROUTING AREA UPDATE REJECT received |
Retransmission of the ROUTING AREA UPDATE REQUEST |
|
T3340 (Iu mode only) |
10s |
GMM-DEREG GMM-REG |
ATTACH REJECT, DETACH REQUEST, ROUTING AREA UPDATE REJECT or SERVICE REJECT with any of the causes #3, #6, #7, #8, #11, #12, #13, #15, or #25. ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT is received with "no follow-on proceed" indication and user plane radio access bearers have not been setup. DETACH ACCEPT received after the MS sent DETACH REQUEST with detach type to "IMSI detach" AUTHENTICATION AND CIPHERING REJECT received |
PS signalling connection released |
Release the PS signalling connection and proceed as described in subclause 4.7.1.9 |
|
NOTE 1: The conditions for which this applies are described in subclause 4.7.5.1.5. NOTE 2: If the MS is using EC-GSM-IoT, the timer value shall be calculated as described in subclause 4.7.2.12. |
|||||
Table 11.3a/3GPP TS 24.008: GPRS Mobility management timers – MS side
|
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON |
||||||
|
T3302 |
Default 12 min NOTE 5 |
GMM-DEREG or GMM-REG |
At attach failure and the attempt counter is greater than or equal At routing area updating failure and the attempt counter is greater than or equal to 5. ATTACH ACCEPT with MM cause #16 or #17 and the attempt counter is equal to 5, or ATTACH ACCEPT with MM cause #22, as described in subclause 4.7.3.2.3.2. ROUTING AREA UPDATE ACCEPT with MM cause #16 or #17 and the attempt counter is equal to 5, or ROUTING AREA UPDATE ACCEPT with MM cause #22, as described in subclause 4.7.5.2.3.2. DETACH REQUEST received with no cause code and detach type IE indicates "re-attach not required", as described in subclause 4.7.4.2.2. |
GPRS attach procedure initiated RAU procedure initiated |
On every expiry, initiation of the GPRS attach procedure or RAU procedure |
||||||
|
T3312 |
Default NOTE 8 |
GMM-REG |
In A/Gb mode, when READY state is left. In Iu mode, when PMM-CONNECTED mode is left. |
When entering state GMM-DEREG,READY state in A/Gb mode, or PMM-CONNECTED mode in Iu mode. |
Initiation of the Periodic RAU procedure if the MS is not attached for emergency bearer services or T3323 started under the conditions as specified in subclause 4.7.2.2. Implicit detach from network if the MS is attached for emergency bearer services. |
||||||
|
T3314 READY (A/Gb mode only) |
Default |
All except GMM-DEREG |
Transmission of a PTP PDU |
Forced to Standby |
No cell-updates are performed |
||||||
|
T3317 (Iu mode only) |
15s |
GMM-SERVICE-REQUEST-INITIATED |
SERVICE REQUEST sent |
Security mode control procedure is completed, SERVICE ACCEPT received, or SERVICE REJECT received |
Abort the procedure |
||||||
|
T3319 (Iu mode only) |
Default 30s NOTE 1 NOTE 4 |
GMM-REG |
Completion of the Security Mode Control procedure after sending a SERVICE REQUEST with service type "data". Reception of a SERVICE ACCEPT message. |
When entering PMM-IDLE mode. When the radio access bearer is released for any active PDP context. When entering state GMM-DEREG |
SERVICE REQUEST with service type "data" may be invoked again, if required. |
||||||
|
T3323 |
NOTE 6 |
GMM-REGISTERED |
T3312 expires while ISR is activated and either T3346 is running or the MS is in one of the following states: -GMM-REGISTERED.NO-CELL-AVAILABLE; -GMM-REGISTERED.PLMN-SEARCH; -GMM-REGISTERED.UPDATE-NEEDED;or -GMM-REGISTERED.LIMITED-SERVICE. |
When entering state GMM-DEREGISTERED or when entering PMM-CONNECTED mode. |
Deactivation of ISR by setting TIN to "GUTI" |
||||||
|
T3324 |
NOTE 9 |
GMM-REGISTERED.NORMAL-SERVICE EMM-REGISTERED.NORMAL-SERVICE (defined in 3GPP TS 24.301 [120]) 5GMM-REGISTERED.NORMAL-SERVICE over 3GPP access (defined in 3GPP TS 24.501 [167]) |
In A/Gb mode, when READY state is left. In Iu mode, when PMM-CONNECTED mode is left. In S1 mode, when the EMM-CONNECTED mode is left (defined in 3GPP TS 24.301 [120]). In N1 mode, when the 5GMM-CONNECTED mode over 3GPP acess is left (defined in 3GPP TS 24.501 [167]) |
When entering state GMM-DEREGISTERED, READY state in A/Gb mode, or PMM-CONNECTED mode in Iu mode, When entering state EMM-DEREGISTERED, or EMM-CONNECTED mode in S1 mode (defined in 3GPP TS 24.301 [120]). When entering state 5GMM-DEREGISTERED over 3GPP access, or 5GMM-CONNECTED mode in N1 mode over 3GPP access (defined in 3GPP TS 24.501 [167]) |
The MS may activate PSM if in GMM-REGISTERED.NORMAL-SERVICE. The MS may activate PSM if in EMM-REGISTERED.NORMAL-SERVICE (defined in 3GPP TS 24.301 [120]). The MS may activate MICO mode if in 5GMM-REGISTERED.NORMAL-SERVICE over 3GPP access (defined in 3GPP TS 24.501 [167]) |
||||||
|
T3325 |
Default 60s NOTE 10 |
GMM-REGISTERED.NORMAL-SERVICE EMM-REGISTERED.NORMAL-SERVICE (defined in 3GPP TS 24.301 [120]) |
In A/Gb mode and Iu mode when T3317 expires and service request attempt counter is greater than or equal to 5 In S1 mode when T3417 expires and service request attempt counter is greater than or equal to 5 |
When entering state other than GMM-REGISTERED. NORMAL-SERVICE state, or. When entering state other than EMM-REGISTERED. NORMAL-SERVICE state, or. MS camped to a new PLMN other than the PLMN on which timer started, or DRB established from network. |
The MS may initiate SERVICE REQUEST procedure |
||||||
|
T3346 |
NOTE 7 |
GMM-DEREGISTERED. ATTEMPTING-TO-ATTACH GMM-REGISTERED. ATTEMPTING-TO-UPDATE GMM-REGISTERED EMM-DEREGISTERED. ATTEMPTING-TO-ATTACH EMM-REGISTERED. ATTEMPTING-TO-UPDATE EMM-REGISTERED (defined in 3GPP TS 24.301 [120]). 5GMM-DEREGISTERED. ATTEMPTING-REGISTRATION 5GMM-REGISTERED. ATTEMPTING-REGISTRATION-UPDATE 5GMM-REGISTERED (defined in 3GPP TS 24.501 [167]). |
ATTACH REJECT, ROUTING AREA UPDATE REJECT or SERVICE REJECT received with a timer value for T3346; "Extended wait time" for PS domain from the lower layers (defined in 3GPP TS 25.331 [23c]). ATTACH REJECT, TRACKING AREA UPDATE REJECT or SERVICE REJECT (defined in 3GPP TS 24.301 [120]) received with a timer value for T3346; "Extended wait time" from the lower layers. (defined in 3GPP TS 36.331 [129]). REGISTRATION REJECT, DE-REGISTRATION REQUEST or SERVICE REJECT (defined in 3GPP TS 24.501 [167]) received with a timer value for T3346. |
– Paging received or DETACH REQUEST with the detach type "re-attach required" received – see subclause 4.1.1.7 (A/Gb mode or Iu mode only) – see subclause 5.3.9, subclause 5.5.1.2.5, subclause 5.5.1.3.5, subclause 5.5.3.2.5, subclause 5.5.3.3.5, subclause 5.6.1.5, and subclause 5.6.2.2.2 in 3GPP TS 24.301 [122] (S1 mode only) – see subclause 5.3.9, subclause 5.4.4.3, subclause 5.4.7.2.1, subclause 5.5.1.2.5, subclause 5.5.1.3.5, subclause 5.5.2.3.2 and subclause 5.6.1.5 in 3GPP TS 24.501 [167] (N1 mode only) |
Initiation of GPRS attach procedure, routing area updating procedure or service request procedure, dependent on GMM state and GPRS update status. Initiation of EPS attach procedure, tracking area updating procedure or service request procedure, dependent on EMM state and EPS update status. (defined in 3GPP TS 24.301 [120]) Initiation of registration procedure or service request procedure, dependent on 5GMM state and 5GS update status. (defined in 3GPP TS 24.501 [167]) |
||||||
|
NOTE 1: The default value of this timer is used if the network does not indicate another value in a GMM signalling procedure. NOTE 2: The default value of this timer is used if neither the MS nor the Network send another value, or if the Network sends this value, in a signalling procedure. NOTE 3: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description. NOTE 4: The purpose of this timer is to prevent the MS from repeating the SERVICE REQUEST message with service type "data" too early in case the request to setup the radio access bearer is queued by the radio access network. NOTE 5: The cases in which the default value of this timer is used are described in subclause 4.7.2.7. NOTE 6: The value of this timer may be provided by the network to the MS in the ATTACH ACCEPT message and ROUTING AREA UPDATE ACCEPT message. The default value of this timer is identical to the value of timer T3312. NOTE 7: The timer value is provided by the network in an ATTACH REJECT, ROUTING AREA UPDATE REJECT, TRACKING AREA UPDATE REJECT, REGISTRATION REJECT, DE-REGISTRATION REQUEST or SERVICE REJECT message or as a "Extended wait time" value by the lower layers, or chosen randomly from a default value range of 15 – 30 minutes. In this release, receipt of the "Extended wait time" as part of 5GMM from the lower layers is not defined. NOTE 8: The cases in which the default value of this timer is used are described in subclause 4.7.2.2. NOTE 9: The timer value is provided by the network in an ATTACH ACCEPT, ROUTING AREA UPDATE ACCEPT, TRACKING AREA UPDATE ACCEPT or REGISTRATION ACCEPT message. NOTE 10: The value of this timer is UE implementation specific, with a minimum value of 60 seconds. |
|||||||||||
Table 11.4/3GPP TS 24.008: GPRS Mobility management timers – network side
|
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON THE |
|
T3322 |
6s |
GMM- |
DETACH REQUEST sent |
DETACH ACCEPT received |
Retransmission of DETACH REQUEST |
|
T3350 |
6s |
GMM-COMMON-PROC-INIT |
ATTACH ACCEPT RAU ACCEPT sent with P-TMSI and/or TMSI P-TMSI REALLOCATION COMMAND |
ATTACH COMPLETE received RAU COMPLETE received P-TMSI REALLOCATION COMPLETE received |
Retransmission of the same message type, i.e. ATTACH ACCEPT, RAU ACCEPT or REALLOCATION COMMAND |
|
T3360 |
6s |
GMM- COMMON-PROC-INIT |
AUTHENTICATION AND CIPHERING REQUEST |
AUTHENTICATION AND CIPHERING RESPONSE received AUTHENTICATION-AND CIPHERING-FAILURE received |
Retransmission of AUTHENTICATION AND CIPHERING REQUEST |
|
T3370 |
6s |
GMM-COMMON-PROC-INIT |
IDENTITY REQUEST sent |
IDENTITY RESPONSE received |
Retransmission of IDENTITY REQUEST |
|
NOTE 1 If the SGSN supports EC-GSM-IoT and if the MS is using EC-GSM-IoT, the timer value is calculated as described in subclause 4.7.2.12. |
|||||
Table 11.4a/3GPP TS 24.008: GPRS Mobility management timers – network side
|
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON |
|
T3313 |
NOTE 1 |
GMM-REGISTERED |
Paging procedure initiated |
Paging procedure completed |
Network dependent |
|
T3314 READY (A/Gb mode only) |
Default |
All except GMM-DEREGISTERED |
Receipt of a PTP PDU |
Forced to Standby Completion of a successful GPRS attach or routing area updating procedure in Iu mode. Indication received from HLR/HSS that the MS performed an EPS attach or indication received from the MME that the MS is performing a tracking area updating procedure. |
The network shall page the MS if a PTP PDU has to be sent to the MS |
|
T3315 |
NOTE 7 |
GMM-REGISTERED |
Paging procedure initiated for an MS which the network accepted the request to use eDRX |
Paging procedure completed Paging procedure is aborted |
Paging procedure is aborted and the network proceeds as specified in 3GPP TS 23.060 [74] |
|
mobile reachable |
NOTE 4 |
All except GMM-DEREGISTERED |
In A/Gb mode, when entering STANDBY state In Iu mode, when entering PMM-IDLE mode. |
PTP PDU received |
Network dependent but typically paging is halted on 1st expiry if the MS is not attached for emergency bearer services. Implicitly detach the MS which is attached for the emergency bearer services. Start implicit detach timer if ISR is activated. |
|
implicit detach timer |
NOTE 5 |
All except GMM-DEREGISTERED |
The mobile reachable timer expires while the network is in PMM-IDLE mode or STANDBY state. |
PTP PDU received |
Implicitly detach the MS on 1st expiry |
|
active timer |
NOTE 6 |
All except GMM-DEREGISTERED |
In A/Gb mode, when entering STANDBY state. In Iu mode, when entering PMM-IDLE mode. |
PTP PDU received |
Network dependent but typically paging is halted on 1st expiry |
|
NOTE 1: The value of this timer is network dependent. NOTE 2: The default value of this timer is used if neither the MS nor the Network send another value, or if the Network sends this value, in a signalling procedure. The value of this timer should be slightly shorter in the network than in the MS, this is a network implementation issue. NOTE 3: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description. NOTE 4: The default value of this timer is 4 minutes greater than T3312. If T3346 is larger than T3312 and the SGSN includes timer T3346 in the ROUTING AREA UPDATE REJECT message or the 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 MS is attached for emergency bearer services, the value of this timer is set equal to T3312. NOTE 5: The value of this timer is network dependent. If ISR is activated, the default value of this timer is 4 minutes greater than T3323. NOTE 6: If the network includes timer T3324 in the ATTACH ACCEPT message or ROUTING AREA UPDATE ACCEPT message and if the MS 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 7: The value of this timer is smaller than the value of timer T3-RESPONSE (see 3GPP TS 29.274 [16D]). NOTE 8: If the SGSN supports EC-GSM-IoT and if the MS is using EC-GSM-IoT, the timer value is calculated as described in subclause 4.7.2.12. NOTE 9: If the SGSN supports EC-GSM-IoT and if the MS is using EC-GSM-IoT, then the timer value shall be calculated by using a multiplier which value is network dependent. |
|||||
11.2.3 Timers of GPRS session management
Table 11.2c/3GPP TS 24.008: GPRS session management timers – MS side
|
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON THE |
|
T3380 |
30s |
PDP- |
ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST sent |
ACTIVATE ACTIVATE |
Retransmission of ACTIVATE PDP |
|
T3381 |
8s |
PDP-MODIFY-PENDING |
MODIFY PDP CONTEXT REQUEST sent |
MODIFY PDP CONTEXT ACCEPT received |
Retransmission of MODIFY PDP CONTEXT REQUEST |
|
T3390 |
8s |
PDP- |
DEACTIVATE PDP CONTEXT REQUEST sent |
DEACTIVATE PDP CONTEXT ACC |
Retransmission of DEACTIVATE |
|
T3396 |
NOTE 1 |
PDP- PROCEDURE TRANSACTION PENDING (defined in 3GPP TS 24.301 [120]) PROCEDURE TRANSACTION PENDING (defined in 3GPP TS 24.501 [167]) |
ACTIVATE PDP CONTEXT REJECT, ACTIVATE MBMS CONTEXT REJECT, ACTIVATE SECONDARY PDP CONTEXT REJECT, DEACTIVATE PDP CONTEXT REQUEST or modify PDP context reJECT received with SM cause #26 and with a timer value for T3396 PDN CONNECTIVITY REJECT, BEARER RESOURCE MODIFICATION REJECT, BEARER RESOURCE ALLOCATION REJECT or DEACTIVATE EPS BEARER CONTEXT REQUEST (defined in 3GPP TS 24.301 [120]) received with ESM cause #26 and with a timer value for T3396 PDU SESSION ESTABLISHMENT REJECT, PDU SESSION MODIFICATION REJECT, or PDU SESSION RELEASE COMMAND (defined in 3GPP TS 24.501 [167]) received with 5GSM cause #26 and with a timer value for T3396 PDU SESSION ESTABLISHMENT REQUEST, or PDU SESSION MODIFICATION REQUEST received in a DL NAS TRANSPORT message (defined in 3GPP TS 24.501 [167]) with 5GMM cause #22 and with a timer value for T3396 |
REQUEST PDP CONTEXT ACTIVATION or REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST or REQUEST MBMS CONTEXT ACTIVATION or ACTIVE DEFAULT EPS BEARER CONTEXT REQUEST or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST or DETACH REQUEST with the detach type "re-attach required" or paging for EPS services using IMSI or paging for GPRS services using IMSI received or PDU SESSION RELEASE COMMAND or PDU SESSION MODIFICATION COMMAND or PDU SESSION AUTHENTICATION COMMAND or DEREGISTRATION REQUEST with the re-registration type "re-registration required". |
None |
|
Back-off timer |
12 min NOTE 2 |
PDP- PROCEDURE TRANSACTION PENDING (defined in 3GPP TS 24.301 [120]) |
ACTIVATE PDP CONTEXT REJECT, ACTIVATE MBMS CONTEXT REJECT, ACTIVATE SECONDARY PDP CONTEXT REJECT, or modify PDP context reJECT received with SM cause value #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported", or #33 "requested service option not subscribed", or PDN CONNECTIVITY REJECT, BEARER RESOURCE MODIFICATION REJECT or BEARER RESOURCE ALLOCATION REJECT (defined in 3GPP TS 24.301 [120]) received with ESM cause value #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported", or #33 "requested service option not subscribed", or received with an ESM cause different from #26 "insufficient resources" and with a back-off timer value as specified in 3GPP TS 24.301 [120] PDU SESSION ESTABLISHMENT REJECT or PDU SESSION MODIFICATION REJECT (defined in 3GPP TS 24.501 [167]) received with 5GSM cause value #8 "operator determined barring", #27 "missing or unknown DNN", #32 "service option not supported", #33 "requested service option not subscribed" or #70 "missing or unknown DNN in a slice", or received with an 5GSM cause different from #26 "insufficient resources", #67 "insufficient resources for specific slice and DNN", or #69 "insufficient resources for specific slice" and with a back-off timer value as specified in 3GPP TS 24.501 [167] PDU SESSION RELEASE COMMAND (defined in 3GPP TS 24.501 [167]) received with 5GSM cause value #29 " user authentication or authorization failed " and with a back-off timer value as specified in 3GPP TS 24.501 [167]. |
None |
None |
|
NOTE 1: The value of this timer or the value of this timer unit can be provided by the network operator when: – a request to activate a PDP context, a request to activate a MBMS context or a request to modify a PDP context is rejected by the network with a certain SM cause; – a request to deactivate a PDP context is received with a certain SM cause value; – a request to establish a PDN connection, a request to allocate bearer resources or a request to modify bearer resources (defined in 3GPP TS 24.301 [120]) is rejected by the network with a certain ESM cause; – a request to deactivate a EPS bearer context is received with a certain ESM cause value; – a request to establish a PDU session or a request to modify a PDU session (defined in 3GPP TS 24.501 [167]) is rejected by the network: 1) with a certain 5GSM cause; or 2) indication that the 5GSM message was not forwarded due to DNN based congestion control; or – a command to release a PDU session is received with a certain 5GSM cause value. If the timer unit is not set to indicate that the timer is deactivated, the value of the timer when included with SM cause, ESM cause, 5GSM cause #26, or due to DNN based congestion control is zero or the timer value is taken randomly from an operator dependent range not greater than 70 hours. If the PDN CONNECTIVITY REJECT was sent together with an ATTACH REJECT message and the ATTACH REJECT message was not integrity protected, MS uses a random value from a default range of 10mins to 30mins. NOTE 2: The default value of 12 minutes applies only for certain SM, ESM and 5GSM cause values as specified in subclauses 6.1.3.1.3.3, 6.1.3.2.2.3, and 6.1.3.3.3.3 in 3GPP TS 24.301 [120] and 3GPP TS 24.501 [167]. NOTE 3: If the MS is using EC-GSM-IoT, the timer value shall be calculated as described in subclause 4.7.2.12. |
|||||
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 back-off timer is used to describe a logical model of the required MS behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp.
NOTE 3: 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 MS. Whether the MS uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to MS implementation.
Table 11.2d/3GPP TS 24.008: GPRS session management timers – network side
|
TIMER NUM. |
TIMER VALUE |
STATE |
CAUSE OF START |
NORMAL STOP |
ON THE |
|
T3385 |
8s |
PDP- |
REQUEST PDP CONTEXT ACTIVATION or |
ACTIVATE PDP CONTEXT REQUEST or ACTIVATE SECONDARY PDP CONTEXT REQUEST or |
Retransmission of REQUEST PDP CONTEXT ACTIVATION or REQUEST SECONDARY PDP CONTEXT ACTIVATION or |
|
T3386 |
8s |
PDP- |
MODIFY PDP CONTEXT REQUEST sent |
MODIFY PDP CONTEXT ACC received |
Retransmission of MODIFY PDP CONTEXT REQ |
|
T3395 |
8s |
PDP- |
DEACTIVATE PDP CONTEXT REQUEST sent |
DEACTIVATE PDP CONTEXT ACC received |
Retransmission of DEACTIVATE PDP CONTEXT REQ |
|
NOTE 1: If the SGSN supports EC-GSM-IoT and if the MS is using EC-GSM-IoT, the timer value shall be calculated as described in subclause 4.7.2.12. |
|||||
NOTE 4: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.
11.3 Timers of circuit-switched call control
Table 11.3/3GPP TS 24.008: Call control timers – MS side
|
TIM NUM. |
TIM VAL |
STATE OF CALL |
CAUSE OF START |
NORMAL STOP |
AT FIRST EXPIRY |
AT SECOND EXPIRY |
|
T303 |
30s |
Call initiated |
CM SER RQ sent |
ALERT,CONN,CALL PROC, or REL COMP received |
Clear the call |
Timer is not restarted |
|
T305 |
30s |
Disconnect Request |
DISC sent |
REL or DISC received |
REL sent. |
Timer is not restarted |
|
T308 |
30s |
Release request |
REL sent |
REL COMP or REL received |
Retrans. RELEASE restart T308 |
Call ref. release |
|
T310 Note 1 |
30s |
Outgoing call Proceeding |
CALL PROC received |
ALERT,CONN, DISC or PROG rec. |
Send DISC |
Timer is not restarted |
|
T313 |
30s |
Connect Request |
CONN sent |
CONNect ACKnowledge received |
Send DISC |
Timer is not restarted |
|
T322 |
Note 2 |
All states |
STATUS ENQUIRY sent |
STATUS, REL, REL COMP or DISC received |
Retrans. STATUS ENQUIRY or Clear the call |
Clear the call |
|
T323 |
30s |
Modify Request |
MOD sent |
MOD COMP or MOD REJ received |
Clear the call |
Timer is not restarted |
|
T324 |
15s |
Modify request |
MOD received |
MOD COMP or MOD REJ sent |
MOD REJ with old bearer capability |
Timer is not restarted |
|
T332 |
30s |
Wait for network info |
START_CC sent |
CC-EST. received |
Clear the call |
Timer is not restarted |
|
T335 |
30s |
CC-Est. Confirmed |
CC-EST CONF.sent |
RECALL received |
Clear the call |
Timer is not restarted |
|
T336 |
10s |
START DTMF sent |
START DTMF ACK or START DTMF REJECT received |
Timer is not restarted |
||
|
The MS considers the DTMF Procedure (for the digit) to be terminated |
||||||
|
T337 |
10s |
STOP DTMF sent |
STOP DTMF ACK received |
The MS considers the DTMF procedure (for the current digit) to be terminated |
Timer is not restarted |
NOTE 1: T310 is not started if progress indicator #1, #2, or #64 has been delivered in the CALL PROCEEDING message or in a previous PROGRESS message.
NOTE 2: The value of this timer is implementation dependent.
Table 11.4/3GPP TS 24.008: Call control timers – network side
|
TIM NUM. |
DFT TIM VAL |
STATE OF CALL |
CAUSE FOR START |
NORMAL STOP |
AT FIRST EXPIRY |
AT SECOND EXPIRY |
|
T301 Note 1 |
Min180s |
Call received |
ALERT received |
CONN received |
Clear the call |
Timer is not restarted |
|
T303 |
Note 2 |
Call present |
SETUP sent |
CALL CONF or REL COMP received |
Clear the call |
Timer is not restarted |
|
T305 |
30s |
Disconnect Indication |
DISC without progress indic. #8 sent or CCBS Possible |
REL or DISC received |
Network sends RELEASE |
Timer is not restarted |
|
T306 |
30s |
Disconnect Indication |
DISC with progress indic. #8 sent but no CCBS possible |
REL or DISC received |
Stop the tone/ announc. Send REL |
Timer is not restarted |
|
T308 |
Note 2 |
Release request |
REL sent |
REL COMP or REL received |
Retrans. RELEASE restart T308 |
Release call reference |
|
T310 |
Note 2 |
Incoming call proceeding |
CALL CONF received |
ALERT, CONN or DISC received |
Clear the call |
Timer is not restarted |
|
T313 |
Note 2 |
Connect Indication |
CON sent |
CON ACK received |
Clear the call |
Timer is not restarted |
|
T322 |
Note 2 |
All states |
STATUS ENQUIRY sent |
STATUS, REL, REL COMP or DISC received |
Retran. STATUS ENQUIRY or Clear the call |
Clear the call |
|
T323 |
30s |
Modify request |
MOD sent |
MOD COMP or MOD REJ received |
Clear the call |
Timer is not restarted |
|
T331 |
Note 2 |
CC Connec. Pending |
CM-SERV PROMPT sent |
START CC received |
Clear the call |
Timer is not restarted |
|
T333 |
Note 2 |
CC-Est. Present |
START CC received |
CC-EST.CONF or REL COMP received |
Clear the call |
Timer is not restarted |
|
T334 Note 3 |
Min 15s |
CC-Est. Confirmed |
RECALL sent |
SETUP received |
Clear the call |
Timer is not restarted |
|
T338 |
Note 2 |
Disconnect indication |
DISC with CCBS possible |
REL or DISC received |
stop any tone/ announc. Send REL |
Timer is not restarted |
NOTE 1: The network may already have applied an internal alerting supervision function; e.g. incorporated within call control. If such a function is known to be operating on the call, then timer T301 is not used.
NOTE 2: These time values are set by the network operator.
NOTE 3: When applied to the supplementary service CCBS, the timer T334 can either represent the recall timer T4 or the notification timer T10 (see 3GPP TS 23.093 [88a]). Thus the timer T334 can take two different values. 3GPP TS 23.093 [88a] defines the range of these values.
Annex A (informative):
Example of subaddress information element coding
This annex gives an example of how the Called Party Subaddress IE is encoded to carry subaddress digits that use IA5 characters. This example is also applicable to the Calling Party Subaddress IE.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
octet |
|
0 |
1 |
1 |
0 |
1 |
1 |
0 |
1 |
1 |
|
called party subaddress IEI |
||||||||
|
0 |
0 |
0 |
0 |
0 |
1 |
1 |
1 |
2 |
|
Length |
||||||||
|
1 |
0 |
0 |
0 |
X |
0 |
0 |
0 |
3 |
|
not ext |
NSAP (X.213/ISO 8348 AD2) |
odd/ev note 1 |
note 2 |
|||||
|
0 |
1 |
0 |
1 |
0 |
0 |
0 |
0 |
4 |
|
AFI (note 3) |
||||||||
|
IA5 Character (note 4) |
5 |
|||||||
|
IA5 Character (note 4) |
6 |
|||||||
|
IA5 Character (note 4) |
9 |
|||||||
NOTE 1: The value of this bit has no significance when the type of subaddress is "NSAP".
NOTE 2: These bits are spare.
NOTE 3: The Authority and Format Identifier code 50 (in BCD) indicates that the subaddress consists of IA5 characters (see ISO standard 8348 AD2).
NOTE 4: IA5 character as defined in ITU-T Recommendation T.50 [52]/ISO 646 and then encoded into two semi-octets according to the "preferred binary encoding" defined in X.213 [144]/ISO 8348 AD2. (Each character is converted into a number in the range 32 to 127 using the ISO 646 encoding with zero parity and the parity bit in the most significant position. This number is then reduced by 32 to give a new number in the range 0 to 95. The new number is then treated as a pair of decimal digits with the value of each digit being encoded in a semi-octet.)
NOTE 5: the number of IA5 characters in the subaddress may vary, subject to an upper limit of 19 IA5 characters.
Annex B (normative):
Compatibility checking