timers mobility gsm

Timers of mobility management

3GPP TS 24.008: Mobility management timers – MS-side

TIMER MM TIMESTATE OUT

NUM. VAL.T3210 LOCATION UPDATING INITIATED 20s

T3211 MM IDLE, 15s

T3212 MM IDLE Note 1

T3213 LOCATION UPDATING INITIATED 4s

T3214 LOCATION UPDATING INITIATED 20s

WAIT FOR OUTGOING MM CONNECTION

IMSI DETACH INITIATEDT3216 LOCATION UPDATING INITIATED 15s


IMSI DETACH INITIATEDT3218 LOCATION UPDATING INITIATED 20s


IMSI DETACH INITIATED

T3220 IMSI DETACH INITIATED 5s

T3230 WAIT FOR OUTGOING MM CONNECTION 15s

WAIT FOR REESTABLISH

WAIT FOR ADDITIONAL OUTGOING MM CONNECTION

T3240 WAIT FOR NETWORK COMMAND 10s

LOCATION UPDATE REJECTEDT3241 RR CONNECTION RELEASE NOT ALLOWED 300s

T3242 All except NULL 3600s

T3243 All except NULL 900s

3GPP TS 24.008: Mobility management timers – network-side

TIMER MM TIMESTATE OUT

NUM. VAL.T3250 TMSI REALLOCATION INITIATED 12s

T3255 Note

T3260 AUTHENTICATION INITIATED 12s

T3270 IDENTIFICATION INITIATED 12s

Timer T3240 and Timer T3241

Timer T3240 is started in the mobile station when:

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]).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.

Timers of GPRS mobility management

3GPP TS 24.008: GPRS Mobility management timers – MS side

TIMER NUM. STATE TIMER VALUE

T3310 GMM- 15sREG-INIT

NOTE 1: The timeout value is broadcasted in a SYSTEM INFORMATION message.

NOTE 2: The value of this timer is not specified by this recommendation.

- 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.

T3311 GMM-DEREG ATTEMPTING TO ATTACH or 15s

GMM-REG ATTEMPTING TO UPDATE


GMM-REG

GMM-DEREG-INIT

GMM-RA-UPDATING-INT

GMM-SERV-REQ-INIT

(Iu mode only)


GMM-REGGMM-DEREG-INITGMM-RA-UPDATING-INTGMM-SERV-REQ-INIT (Iu mode only)


GMM-REGGMM-DEREG-INITGMM-RA-UPDATING-INTGMM-SERV-REQ-INIT (Iu mode only)

T3321 GMM- 15s

DEREG-INITT3330 GMM-ROUTING-UPDATING-INITIATED 15s

T3340 GMM- 10s

REG-INIT

(Iu mode only)

GMM-DEREG-INITGMM-RA-UPDATING-INTGMM-SERV-REQ-INIT (Iu mode only)GMM-ATTEMPTING-TO-UPDATE-MMGMM-REG-NORMAL-SERVICE

3GPP TS 24.008: GPRS Mobility management timers – MS side


T3302 GMM-DEREG Default 12 min

or Note 1

GMM-REG Note 5

T3312 GMM-REG Default

54 min

Note1T3314 All except GMM-DEREG Default

44 secREADY Note 2

(A/Gb mode only)T3317 GMM-SERVICE-REQUEST-INITIATED 15s

(Iu mode only)

T3319 GMM-REG Default 30s

(Iu mode only) Note 1

Note 4

T3323 GMM-REGISTERED NOTE 6

3GPP TS 24.008: GPRS Mobility management timers – network side


T3322 GMM- 6sDEREG-INIT

T3350 GMM-COMMON-PROC-INIT 6s

NOTE 1: The 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: In Iu mode, the default value of this timer is used if the network provides a value for this timer in a non-integrity protected Iu mode GMM message.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.


T3360 GMM- COMMON-PROC-INIT 6s


3GPP TS 24.008: GPRS Mobility management timers – network side


T3313 GMM_REGT3314 All except GMM-DEREG Default

44 secREADY

(A/Gb mode only)Mobile Reachable All except GMM-DEREG

All except GMM-DEREG

Timers of GPRS session management

3GPP TS 24.008: GPRS session management timers – MS side


T3380 PDP- 30sACTIVE-PEND or MBMS ACTIVE-PENDING

T3381 PDP-MODIFY-PENDING 8s

Note 1

Note 2

Default 4 min greater than T3312

Implicit Detach timer

Default 4 min greater than T3323

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.

T3390 PDP- 8s

INACT-PEND

3GPP TS 24.008: GPRS session management timers – network side


T3385 PDP- 8s

ACT-PEND or MBMS ACTIVE-PENDING

T3386 PDP- 8sMOD-PEND

T3395 PDP- 8sINACT-PEND or MBMS INACTIVE-PENDING

Timers of circuit-switched call control

3GPP TS 24.008: Call control timers – MS side

TIM STATE OF CALL TIM VAL

NUM.T303 Call initiated 30s

T305 Disconnect Request 30sT308 Release request 30sT310 Outgoing call Proceeding 30s

Note 1T313 Connect Request 30s

T323 Modify Request 30s

T324 Modify request 15s

T332 Wait for network info 30sT335 CC-Est. Confirmed 30sT336 10s

T337 10s

3GPP TS 24.008: Call control timers – network side

TIM STATE OF CALL DFT TIM VAL

NOTE: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.


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.

STATE OF CALL DFT TIM VAL

NUM.T301 Call received Min180s

Note 1T303 Call present Note 2

T305 Disconnect Indication 30s

T306 Disconnect Indication 30s

T308 Release request Note 2T310 Incoming call proceeding Note 2

T313 Connect Indication Note 2T323 Modify request 30s

T331 CC Connec. Pending Note 2T333 CC-Est. Present Note 2

T334 CC-Est. Confirmed Min 15s

Note 3T338 Disconnect indication Note 2

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.

CAUSE FOR START NORMAL STOP AT THE EXPIRY

- LOC_UPD_REQ sent - LOC_UPD_ACC Start T3211

- LOC_UPD_REJ

- AUTH_REJ

- Lower layer failure- LOC_UPD_REJ with cause#17 netw. failure - Time out Restart the Location update proc.

- cell change

- change of LA- termination of MM service or MM signalling initiate periodic updating

- location updating failure - expiry new random attempt

- change of BCCH parameterAUTHENT FAILURE AUTHENT REQ received

AUTHENT FAILURE AUTHENT REQ received

Cause = Synch failure sent

Delete the stored RAND and RES

- AUTHENT REJ received- AUTHENT FAIL sent- enter MM IDLE or NULL

- IMSI DETACH - release from RM-sublayer

- CM SERV REQ - Cipher mode setting provide release ind.

CM RE-EST REQ - CM SERV REJ

- CM SERV ACC

- lower layer failure or RR conn. released after RR conn. abort during loc. updating

- request for MM connection establishment

- initiation of MM service or MM signalling

Consider the network as ’false’ (see 4.3.2.6.1)

Cause = ‘MAC failure’ or ‘GSM authentication unacceptable’ sent

Consider the network as ’false’ (see 4.3.2.6.1)

RAND and RES stored as a result of of a UMTS authentication challenge

- Cipher mode setting (A/Gb mode only)

- Security mode setting (Iu mode only)

- CM_SERV_ACCEPT received- CM SERVICE REJECT received

- LOCATION UPDATING ACCEPT received

enter Null or Idle, ATTEMPTING TO UPDATE

see timer description T3240 below abort the RR connection

*Refer timer description T3241 below abort the RR connection

- Time Out

- Power Off

- Time Out

- Power Off

CAUSE FOR START NORMAL STOP AT THE EXPIRY

TMSI-REALL-COM received Optionally Release RR connection

LOC UPD ACC sent with”Follow on Proceed” CM SERVICE REQUEST

AUTHENT-REQUEST sent Optionally Release RR connection

AUTHENT-FAILURE receivedIDENTITY REQUEST sent Optionally Release RR connection

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]).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.

CAUSE OF START NORMAL STOP ON THE

ATTACH REQ sent ATTACH ACCEPT received Retransmission of ATTACH REQ

ATTACH REJECT received

see timer description T3240 below

*Refer timer description T3241 below

eCall only MS enters MM IDLE state after an emergency call

Perform eCall Inactivity procedure in subclause 4.4.7

- Removal of eCall only restriction

eCall only MS enters MM IDLE state after a test/reconfiguration call

Perform eCall Inactivity procedure in subclause 4.4.7

- Removal of eCall only restriction

TMSI-REAL-CMD or LOC UPD ACC with new TMSI sent

Release RR Connection or use for mobile station terminating call

AUTHENT-RESPONSE received

IDENTITY RESPONSE received

- 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.

1st, 2nd, 3rd, 4th EXPIRY Note 3

Change of the routing area

Low layer failureSecurity mode setting Delete the stored RAND and RES(Iu mode only)

SERVICE REJECTreceived(Iu mode only)

Enter GMM-DEREG orGMM-NULL

DETACH REQ sent DETACH ACCEPT received

ROUTING AREA UPDATE REQUEST sent

message

ATTACH REJ with other cause values as described in chapter ‘GPRS Attach’

Restart of the Attach or the RAU procedure with updating of the relevant attempt counter

ROUTING AREA UPDATE REJ with other cause values as described in chapter ‘Routing Area Update’

RAND and RES stored as a result of a UMTS authentication challenge

SERVICE ACCEPT received. (Iu mode only)

ROUTING AREA UPDATE ACCEPT received

AUTHENTICATION AND CIPHERING REJECT received

AUTHENTICATION_AND_CIPHERING FAILURE sent

AUTHENTICATION & CIPHERING FAILURE (cause=’MAC failure’ or ‘GSM authentication unacceptable’) sent

AUTHENTICATION & CIPHERING REQUEST received

On first expiry, the MS should consider the network as false (see 4.7.7.6.1)

AUTHENTICATION & CIPHERING FAILURE (cause=synch failure) sent

AUTHENTICATION & CIPHERING REQUEST received

On first expiry, the MS should consider the network as false (see 4.7.7.6.1)

Retransmission of the DETACH REQ

ROUTING AREA UPDATE ACC received

Retransmission of the ROUTING AREA UPDATE REQUEST

ROUTING AREA UPDATE REJ received

ATTACH REJ, DETACH REQ, ROUTING AREA UPDATE REJ or SERVICE REJ with any of the causes #11, #12, #13, #15, or #25.

PS signalling connection released

Release the PS signalling connection and proceed as described in subclause 4.7.1.9

ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT is received with “no follow-on proceed“ indication.

CAUSE OF START NORMAL STOP ON

EXPIRYAt successful attach On every expiry, initiation of the

GPRS attach procedure

orRAU procedure

In A/Gb mode, when READY state is left.

In Iu mode, when PMM-CONNECTED mode is left.

Transmission of a PTP PDU Forced to Standby No cell-updates are performed

SERVICE REQ sent Abort the procedure

SERVICE ACCEPT received, or

SERVICE REJECT received

Reception of a SERVICE ACCEPT message.


DETACH REQ sent DETACH ACCEPT received

ATTACH ACCEPT ATTACH COMPLETE receivedsent with P-TMSI and/or TMSI

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

At successful routing area updating

At routing area updating failure and the attempt counter is greater than or equal to 5.

When entering state GMM-DEREG

Initiation of the Periodic RAU procedure

Security mode control procedure is completed,

Completion of the Security Mode Control procedure after sending a SERVICE REQUEST with service type “data”.

When entering PMM-IDLE mode.

SERVICE REQ with service type “data” may be invoked again, if required.

When the radio access bearer is released for any active PDP context.

When entering state GMM-DEREG

T3312 expires while the MS is in GMM-REGISTERED.NO-CELL-AVAILABLE and ISR is activated.

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

Deactivation of ISR by setting TIN to “GUTI”

NOTE 1: The 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: In Iu mode, the default value of this timer is used if the network provides a value for this timer in a non-integrity protected Iu mode GMM message.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.

1st, 2nd, 3rd, 4th EXPIRY Note 3Retransmission of DETACH REQUEST

Retransmission of the same message type, i.e. ATTACH ACCEPT, RAU ACCEPT or REALLOC COMMAND

RAU ACCEPT sent with P-TMSI and/or TMSI RAU COMPLETE received

P-TMSI REALLOC COMMAND

sentAUTH AND CIPH REQUEST sent

IDENTITY REQUEST sent

CAUSE OF START NORMAL STOP ONEXPIRY

Paging procedure initiated Paging procedure completed Network dependentReceipt of a PTP PDU Forced to Standby

PTP PDU received

PTP PDU received


ACTIVATE Retransmission of ACTIVATE PDP

ACTIVATE

MODIFY PDP CONTEXT REQUEST sent

Retransmission of the same message type, i.e. ATTACH ACCEPT, RAU ACCEPT or REALLOC COMMAND

P-TMSI REALLOC COMPLETE received

AUTH AND CIPH RESPONSE received

Retransmission of AUTH AND CIPH REQUEST

AUTHENT-AND CIPHER-FAILURE received

IDENTITY RESPONSE received

Retransmission of IDENTITY REQUEST

The network shall page the MS if a PTP PDU has to be sent to the MS

In A/Gb mode, change from READY to STANDBY state

Network dependent but typically paging is halted on 1st expiry

In Iu mode, change from PMM-CONNECTED mode to PMM-IDLE mode.

The Mobile Reachable timer expires while the network is in PMM-IDLE mode or STANDBY state and ISR is activated.

Implicitly detach the MS on 1st expiry

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.

1st, 2nd, 3rd, 4th EXPIRYACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST sent

PDP CONTEXT ACCEPT, ACTIVATE

CONTEXT REQ, ACTIVATE SECONDARY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST

SECONDARY PDP CONTEXT ACCEPT or ACTIVATE MBMS CONTEXT ACCEPT received

PDP CONTEXT REJECT, ACTIVATE

SECONDARY PDP CONTEXT REJECT or ACTIVATE MBMS CONTEXT REJECT received

MODIFY PDP CONTEXT ACCEPT received

Retransmission of MODIFY PDP CONTEXT REQUEST

DEACTIVATE PDP CONTEXT REQUEST sent Retransmission of DEACTIVATE

received PDP CONTEXT REQUEST


REQUEST PDP CONTEXT ACTIVATION or

MODIFY PDP CONTEXT REQUEST sent

DEACTIVATE PDP CONTEXT REQUEST sent

CAUSE OF START NORMAL STOP AT FIRST EXPIRY

CM SER RQ sent Clear the call

DISC sent REL or DISC received REL sent.REL sent REL COMP or REL received Retrans. RELEASE restart T308CALL PROC received Send DISC

CONN sent Send DISC

MOD sent Clear the call

MOD received MOD COMP or MOD REJ sent

START_CC sent CC-EST. received Clear the callCC-EST CONF.sent RECALL received Clear the callSTART DTMF sent

STOP DTMF sent STOP DTMF ACK received

CAUSE FOR START NORMAL STOP AT FIRST EXPIRY

DEACTIVATE PDP CONTEXT ACC


1st, 2nd, 3rd, 4th EXPIRYACTIVATE PDP CONTEXT REQUEST or ACTIVATE SECONDARY PDP CONTEXT REQUEST or

Retransmission of REQUEST PDP CONTEXT ACTIVATION or REQUEST SECONDARY PDP CONTEXT ACTIVATION or

REQUEST SECONDARY PDP CONTEXT ACTIVATION or REQUEST MBMS CONTEXT ACTIVATION sent

ACTIVATE MBMS CONTEXT REQUEST received

REQUEST MBMS CONTEXT ACTIVATION

MODIFY PDP CONTEXT ACC received

Retransmission of MODIFY PDP CONTEXT REQ

DEACTIVATE PDP CONTEXT ACC received

Retransmission of DEACTIVATE PDP CONTEXT REQ


CALL PROC, or REL COMP received

ALERT,CONN, DISC or PROG rec.

CONNect ACKnowledge received

MOD COMP or MOD REJ received

MOD REJ with old bearer capability

START DTMF ACK or START DTMF REJECT received

The MS considers the DTMF Procedure (for the digit) to be terminated

The MS considers the DTMF procedure (for the current digit) to be terminated

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.

CAUSE FOR START NORMAL STOP AT FIRST EXPIRY

ALERT received CONN received Clear the call

SETUP sent Clear the call

REL or DISC received Network sends RELEASE

REL or DISC received Stop the tone/ announc. Send REL

REL sent REL COMP or REL received Retrans. RELEASE restart T308CALL CONF received Clear the call

CON sent CON ACK received Clear the callMOD sent Clear the call

CM-SERV PROMPT sent START CC received Clear the callSTART CC received Clear the call

RECALL sent SETUP received Clear the call

DISC with CCBS possible REL or DISC received stop any tone/ announc. Send REL

CALL CONF or REL COMP received

DISC without progress indic. #8 sent or CCBS Possible

DISC with progress indic. #8 sent but no CCBS possible

ALERT, CONN or DISC received

MOD COMP or MOD REJ received

CC-EST.CONF or REL COMP received

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 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.

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]).

AT THE SECOND EXPIRY

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 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 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.

AT SECOND EXPIRY

Timer is not restarted

Timer is not restartedCall ref. releaseTimer is not restarted




Timer is not restartedTimer is not restartedTimer is not restarted


AT SECOND EXPIRY

AT SECOND EXPIRY





Release call referenceTimer is not restarted

Timer is not restartedTimer is not restarted

Timer is not restartedTimer is not restarted



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.

timers mobility gsm

Documents

umts authentication

lower layer

security mode

cipher mode

notification

recall timer

call proceeding

service accept