Sie sind auf Seite 1von 21

Timers of mobility management

3GPP TS 24.008: Mobility management timers MS-side


TIMER NUM. T3210 MM STATE LOCATION UPDATING INITIATED TIME OUT VAL. 20s

T3211

MM IDLE,

15s

T3212 T3213

MM IDLE LOCATION UPDATING INITIATED

Note 1 4s

T3214

LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED LOCATION UPDATING INITIATED

20s

T3216

15s

T3218

20s

WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED

T3220 T3230

IMSI DETACH INITIATED WAIT FOR OUTGOING MM CONNECTION WAIT FOR ADDITIONAL OUTGOING MM WAIT FOR REESTABLISH WAIT FOR NETWORK COMMAND LOCATION UPDATE REJECTED

5s 15s

T3240

10s

T3241 T3242

RR CONNECTION RELEASE NOT ALLOWED All except NULL

300s 3600s

T3243

All except NULL

900s

NOTE 1:

The timeout value is broadcasted in a SYSTEM INFORMATION message.

3GPP TS 24.008: Mobility management timers network-side


TIMER NUM. T3250 T3255 T3260 AUTHENTICATION INITIATED MM STATE TMSI REALLOCATION INITIATED TIME OUT VAL. 12s Note 12s

T3270 NOTE 2:

IDENTIFICATION INITIATED The value of this timer is not specified by this recommendation.

12s

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 sub - 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. 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 SE 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. T3310 STATE GMMREG-INIT GMM-DEREG ATTEMPTING TO ATTACH or TIMER VALUE 15s

T3311

15s

GMM-REG ATTEMPTING TO UPDATE

T3316

GMMREG-INIT GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only)

30s

T3318

GMMREG-INIT GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only) GMMREG-INIT GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only) GMMDEREG-INIT GMM-ROUTING-UPDATING-INITIATED

20s

T3320

15s

T3321

15s

T3330

15s

T3340

GMM-

10s

REG-INIT (Iu mode only) GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only) GMM-ATTEMPTING-TO-UPDATE-MM GMM-REG-NORMAL-SERVICE

3GPP TS 24.008: GPRS Mobility management timers MS side


TIMER NUM. T3302 STATE GMM-DEREG TIMER VALUE Default 12 min

or

Note 1

GMM-REG T3312 GMM-REG

Note 5 Default 54 min Note1 Default 44 sec Note 2

T3314 READY (A/Gb mode only) T3317

All except GMM-DEREG

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

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 sig NOTE 3: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure NOTE4:ThepurposeofthistimeristopreventtheMSfromrepeatingtheSERVICEREQUESTmessagewithservicetypedatatooearlyinc 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 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 A

3GPP TS 24.008: GPRS Mobility management timers network side


TIMER NUM. T3322 T3350 STATE GMMDEREG-INIT GMM-COMMON-PROC-INIT TIMER VALUE 6s 6s

T3360

GMM- COMMON-PROC-INIT

6s

T3370

GMM-COMMON-PROC-INIT

6s

3GPP TS 24.008: GPRS Mobility management timers network side


TIMER NUM. STATE TIMER VALUE

T3313 T3314 READY (A/Gb mode only) Mobile Reachable

GMM_REG All except GMM-DEREG

Note 1 Default 44 sec Note 2

All except GMM-DEREG

Default 4 min greater than T3312

Implicit Detach timer

All except GMM-DEREG

Default 4 min greater than T3323

NOTE 1: NOTE 2: NOTE 3:

The value of this timer is network dependent. 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 sig Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure

Timers of GPRS session management


3GPP TS 24.008: GPRS session management timers MS side
TIMER NUM. T3380 STATE PDPACTIVE-PEND or MBMS ACTIVE-PENDING TIMER VALUE 30s

T3381 T3390

PDP-MODIFY-PENDING PDPINACT-PEND

8s 8s

NOTE:

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

3GPP TS 24.008: GPRS session management timers network side


TIMER NUM. T3385 STATE PDPTIMER VALUE 8s

ACT-PEND or MBMS ACTIVE-PENDING

T3386 T3395

PDPMOD-PEND PDPINACT-PEND or MBMS INACTIVE-PENDING

8s 8s

NOTE:

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

Timers of circuit-switched call control


3GPP TS 24.008: Call control timers MS side
TIM NUM. T303 T305 T308 T310 Note 1 T313 T323 T324 T332 T335 T336 STATE OF CALL TIM VAL

Call initiated Disconnect Request Release request Outgoing call Proceeding

30s 30s 30s 30s

Connect Request Modify Request Modify request Wait for network info CC-Est. Confirmed

30s 30s 15s 30s 30s 10s

T337

10s

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 PROG

3GPP TS 24.008: Call control timers network side


TIM NUM. T301 Note 1 T303 T305 T306 T308 T310 T313 T323 T331 T333 T334 Note 3 T338 NOTE 1: NOTE 2: STATE OF CALL DFT TIM VAL

Call received

Min180s

Call present Disconnect Indication Disconnect Indication Release request Incoming call proceeding Connect Indication Modify request CC Connec. Pending CC-Est. Present CC-Est. Confirmed

Note 2 30s 30s Note 2 Note 2 Note 2 30s Note 2 Note 2 Min 15s

Disconnect indication

Note 2

The network may already have applied an internal alerting supervision function; e.g. incorporated within call control. If such a function i 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

CAUSE FOR START

NORMAL STOP

AT THE EXPIRY

- LOC_UPD_REQ sent

- LOC_UPD_ACC - LOC_UPD_REJ - AUTH_REJ - Lower layer failure - Time out - cell change - request for MM connection establishment

Start T3211

- LOC_UPD_REJ with cause#17 netw. failure - lower layer failure or RR conn. released after RR conn. abort during loc. updating

Restart the Location update proc.

- termination of MM service or MM signalling - location updating failure

- change of LA - initiation of MM service or MM initiate periodic updating signalling - expiry new random attempt - change of BCCH parameter AUTHENT REQ received

AUTHENT FAILURE Cause=MACfailureorGSMauthentication unacceptablesent

Considerthenetworkasfalse (see 4.3.2.6.1)

AUTHENT FAILURE Cause = Synch failure sent

AUTHENT REQ received

Considerthenetworkasfalse (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 - CM SERVICE REJECT received - LOCATION UPDATING ACCEPT received - AUTHENT REJ received - AUTHENT FAIL sent - enter MM IDLE or NULL - release from RM-sublayer - Cipher mode setting - CM SERV REJ - CM SERV ACC see timer description T3240 below

Delete the stored RAND and RES

- IMSI DETACH - CM SERV REQ CM RE-EST REQ

enter Null or Idle, ATTEMPTING TO UPDATE provide release ind.

see timer description T3240 below

abort the RR connection

*Refer timer description T3241 below eCall only MS enters MM IDLE state after an emergency call

*Refer timer description T3241 below - Time Out - Power Off - Removal of eCall only restriction - Time Out - Power Off - Removal of eCall only restriction

abort the RR connection Perform eCall Inactivity procedure in subclause 4.4.7

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

Perform eCall Inactivity procedure in subclause 4.4.7

CAUSE FOR START

NORMAL STOP

AT THE EXPIRY

TMSI-REAL-CMD or LOC UPD ACC with new TMSI TMSI-REALL-COM received sent LOCUPDACCsentwithFollowonProceed CM SERVICE REQUEST AUTHENT-REQUEST sent AUTHENT-RESPONSE received AUTHENT-FAILURE received IDENTITY RESPONSE

Optionally Release RR connection Release RR Connection or use for mobile station terminating call Optionally Release RR connection

IDENTITY REQUEST sent

Optionally Release RR connection

age completing a location updating procedure in the cases specified in subclauses 4.4.4.6 and 4.4.4.8; age in the cases specified in subclause 4.4.4.7; cified in subclause 4.5.1.7; cases specified in 4.3.2.5, 4.3.5.2, 4.5.1.1, and 4.5.3.1.

essage 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 CONNECTION RELEASE NOT ALLOWED. R CONNECTION RELEASE NOT ALLOWED is left. he MM state MM IDLE.

CAUSE OF START ATTACH REQ sent

NORMAL STOP ATTACH ACCEPT received

ON THE 1st, 2nd, 3rd, 4th EXPIRY Note 3 Retransmission of ATTACH REQ

ATTACH REJECT received ATTACH REJ with other cause values as described Change of the routing area inchapterGPRSAttach ROUTING AREA UPDATE REJ with other cause valuesasdescribedinchapterRoutingArea Update Low layer failure

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

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

Security mode setting (Iu mode only) SERVICE ACCEPT received. (Iu mode only) SERVICE REJECT received (Iu mode only) ROUTING AREA UPDATE ACCEPT received AUTHENTICATION AND CIPHERING REJECT received AUTHENTICATION_AND_CIP HERING FAILURE sent Enter GMM-DEREG or GMM-NULL AUTHENTICATION & CIPHERING REQUEST received

Delete the stored RAND and RES

AUTHENTICATION & CIPHERING FAILURE (cause=MACfailureorGSMauthentication unacceptable)sent

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)

DETACH REQ sent

DETACH ACCEPT received

Retransmission of the DETACH REQ Retransmission of the ROUTING AREA UPDATE REQUEST message

ROUTING AREA UPDATE REQUEST sent

ROUTING AREA UPDATE ACC received

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

ROUTING AREA UPDATE REJ received PS signalling connection Release the PS signalling released connection and proceed as described in subclause 4.7.1.9

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

NORMAL STOP At successful attach At successful routing area updating

ON EXPIRY On every expiry, initiation of the

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

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

When entering state GMMDEREG

or RAU procedure Initiation of the Periodic RAU procedure

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

Security mode control procedure Abort the procedure is completed, SERVICE ACCEPT received, or

SERVICE REJECT received Completion of the Security Mode Control procedure When entering PMM-IDLE after sending a SERVICE REQUEST with service mode. typedata. When the radio access bearer is released for any active PDP context. When entering state GMMDEREG When entering state GMMDEREGISTERED or when entering GMM-CONNECTED mode.

SERVICE REQ with service type datamaybeinvokedagain,if required.

Reception of a SERVICE ACCEPT message.

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

Deactivation of ISR by setting TIN toGUTI

te another value in a GMM signalling procedure. he Network send another value, or if the Network sends this value, in a signalling procedure. e relevant timer. Exceptions are described in the corresponding procedure description. gtheSERVICEREQUESTmessagewithservicetypedatatooearlyincasetherequesttosetuptheradioaccessbearerisqueuedbytheradioaccessnetwork. ork provides a value for this timer in a non-integrity protected Iu mode GMM message. e 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.

CAUSE OF START DETACH REQ sent ATTACH ACCEPT sent with P-TMSI and/or TMSI RAU ACCEPT sent with P-TMSI and/or TMSI P-TMSI REALLOC COMMAND sent AUTH AND CIPH REQUEST sent

NORMAL STOP

ON THE 1st, 2nd, 3rd, 4th EXPIRY Note 3 DETACH ACCEPT received Retransmission of DETACH REQUEST ATTACH COMPLETE received Retransmission of the same message type, i.e. ATTACH RAU COMPLETE received ACCEPT, RAU ACCEPT or REALLOC COMMAND P-TMSI REALLOC COMPLETE received AUTH AND CIPH RESPONSE received AUTHENT-AND CIPHERFAILURE received IDENTITY RESPONSE received Retransmission of AUTH AND CIPH REQUEST

IDENTITY REQUEST sent

Retransmission of IDENTITY REQUEST

CAUSE OF START

NORMAL STOP

ON EXPIRY

Paging procedure initiated Receipt of a PTP PDU

Paging procedure completed Forced to Standby

Network dependent 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

PTP PDU received

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 PTP PDU received network is in PMM-IDLE mode or STANDBY state and ISR is activated.

Implicitly detach the MS on 1st expiry

he 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 M e relevant timer. Exceptions are described in the corresponding procedure description.

CAUSE OF START

NORMAL STOP

ACTIVATE PDP CONTEXT REQUEST, ACTIVATE ACTIVATE SECONDARY PDP CONTEXT REQUEST or PDP CONTEXT ACCEPT, ACTIVATE MBMS CONTEXT REQUEST sent ACTIVATE

ON THE 1st, 2nd, 3rd, 4th EXPIRY Retransmission of ACTIVATE PDP CONTEXT REQ, ACTIVATE SECONDARY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST

SECONDARY PDP CONTEXT ACCEPT or ACTIVATE MBMS CONTEXT ACCEPT received ACTIVATE PDP CONTEXT REJECT, ACTIVATE SECONDARY PDP CONTEXT REJECT or ACTIVATE MBMS CONTEXT REJECT received MODIFY PDP CONTEXT ACCEPT received DEACTIVATE PDP CONTEXT ACC received

MODIFY PDP CONTEXT REQUEST sent DEACTIVATE PDP CONTEXT REQUEST sent

Retransmission of MODIFY PDP CONTEXT REQUEST Retransmission of DEACTIVATE PDP CONTEXT REQUEST

relevant timer. Exceptions are described in the corresponding procedure description.

CAUSE OF START REQUEST PDP CONTEXT ACTIVATION or

NORMAL STOP ACTIVATE PDP CONTEXT REQUEST or ACTIVATE SECONDARY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST received MODIFY PDP CONTEXT ACC received DEACTIVATE PDP CONTEXT ACC received

REQUEST SECONDARY PDP CONTEXT ACTIVATION or REQUEST MBMS CONTEXT ACTIVATION sent MODIFY PDP CONTEXT REQUEST sent DEACTIVATE PDP CONTEXT REQUEST sent

ON THE 1st, 2nd, 3rd, 4th EXPIRY Retransmission of REQUEST PDP CONTEXT ACTIVATION or REQUEST SECONDARY PDP CONTEXT ACTIVATION or REQUEST MBMS CONTEXT ACTIVATION Retransmission of MODIFY PDP CONTEXT REQ Retransmission of DEACTIVATE PDP CONTEXT REQ

relevant timer. Exceptions are described in the corresponding procedure description.

CAUSE OF START

NORMAL STOP

AT FIRST EXPIRY

CM SER RQ sent DISC sent REL sent CALL PROC received

CALL PROC, or REL COMP received REL or DISC received REL COMP or REL received ALERT,CONN, DISC or PROG rec. CONNect ACKnowledge received MOD COMP or MOD REJ received MOD COMP or MOD REJ sent CC-EST. received RECALL received START DTMF ACK or START DTMF REJECT received

Clear the call REL sent. Retrans. RELEASE restart T308 Send DISC

CONN sent MOD sent MOD received START_CC sent CC-EST CONF.sent START DTMF sent

Send DISC Clear the call MOD REJ with old bearer capability Clear the call Clear the call

STOP DTMF sent

STOP DTMF ACK 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

een 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 DISC without progress indic. #8 sent or CCBS Possible DISC with progress indic. #8 sent but no CCBS possible REL sent CALL CONF received CON sent MOD sent CM-SERV PROMPT sent START CC received RECALL sent

CALL CONF or REL COMP received REL or DISC received REL or DISC received REL COMP or REL received ALERT, CONN or DISC received CON ACK received MOD COMP or MOD REJ received START CC received CC-EST.CONF or REL COMP received SETUP received

Clear the call Network sends RELEASE Stop the tone/ announc. Send REL Retrans. RELEASE restart T308 Clear the call Clear the call Clear the call Clear the call Clear the call Clear the call

DISC with CCBS possible

REL or DISC received

stop any tone/ announc. Send REL

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

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

AT THE SECOND EXPIRY

ned in 3GPP TS 24.008, 3GPP TS 24.010 [21] or 3GPP TS 24.011 [22]).

isqueuedbytheradioaccessnetwork. is identical to the value of timer T3312.

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 restarted Call ref. release Timer is not restarted

Timer is not restarted Timer is not restarted Timer is not restarted Timer is not restarted Timer is not restarted Timer is not restarted

Timer is not restarted

AT SECOND EXPIRY

Timer is not restarted

Timer is not restarted Timer is not restarted Timer is not restarted Release call reference Timer is not restarted Timer is not restarted Timer is not restarted Timer is not restarted Timer is not restarted Timer is not restarted

Timer is not restarted

4 can take two different values. 3GPP TS 23.093 [88a] defines the range of these values.

Das könnte Ihnen auch gefallen