1、RR 定时器（MS 侧）：Timer Start Stop At expiryT300 Transmission of RRC CONNECTION REQUESTReception of RRC CONNECTION SETUPRetransmit RRC CONNECTION REQUEST if V300 = N300, else go to Idle modeT302 Transmission of CELL UPDATE/URA UPDATEReception of CELL UPDATE CONFIRM/URA UPDATE CONFIRM Retransmit CELL UPDA
2、TE/URA UPDATE if V302 = N302, else, go to Idle modeT304 Transmission of UE CAPABILITY INFORMATIONReception of UE CAPABILITY INFORMATION CONFIRMRetransmit UE CAPABILITY INFORMATION if V304 = N304, else initiate a cell update procedureT305 Entering CELL_FACH or URA_PCH or CELL_PCH state. Reception of
3、CELL UDPATE CONFIRM/URA UPDATE CONFIRM. Entering another state. Transmit CELL UPDATE if T307 is not activated and the UE detects “in service area“. Otherwise, if T307 is not active, start T307.T307 When the timer T305 has expired and the UE detects “out of service area“.When the UE detects “in servi
4、ce area“.Transit to idle modeT308 Transmission of RRC CONNECTION RELEASE COMPLETENot stopped Transmit RRC CONNECTION RELEASE COMPLETE if V308 =N308, else go to idle mode. T309 Upon reception of CELL CHANGE ORDER FROM UTRAN messageSuccessful response to a connection establishment request in the new c
5、ell. Resume the connection to UTRANT310 Transmission of PUSCH CAPACITY REQUESTReception of PHYSICAL SHARED CHANNEL ALLOCATIONTransmit PUSCH CAPACITY REQUEST if V310 = N310, else procedure stops.T311 Reception of PHYSICAL SHARED CHANNEL ALLOCATION message with the CHOICE “PUSCH allocation“ set to “PU
6、SCH allocation pending“.Reception of PHYSICAL SHARED CHANNEL ALLOCATION message with CHOICE “PUSCH allocation“ set to “PUSCH allocation assignment“.UE may initiate a PUSCH capacity request procedure.T312 When the UE starts to establish dedicated CHWhen the UE detects N312 “in sync“ indication from L
7、1. The criteria for physical channel establishment failure is fulfilledTimer Start Stop At expiryT313 When the UE detects consecutive N313 “out of sync“ indication from L1.When the UE detects consecutive N315 “in sync“ indication from L1.The criteria for Radio Link failure is fulfilledT314 When the
8、criteria for radio link failure are fulfilled.The timer is started if radio bearer(s) that are associated with T314 exist of if only RRC connection exists.When the Cell Update procedure has been completed.See subclause 8.3.1.13T315 When the criteria for radio link failure are fulfilled.The timer is
9、started only if radio bearer(s) that are associated with T315 exist.When the Cell Update procedure has been completed.See subclause 8.3.1.14T316 When the UE detects “out of service area“ in URA_PCH or CELL_PCH stateWhen the UE detects “in service area“.Initiate cell update procedure if in service ar
10、ea is detected. Otherwise start timer T317, transit to CELL_FACH state and initiate cell update procedure when the UE detects “in service area“.T317 When the T316 expires or when in CELL_FACH state, the UE detects “out of service area“.When the UE detects “in service area“.Transit to idle modeMM 定时器
11、（ MS 侧）：TIMERNUM.MMSTATTIMEOUTVAL.CAUSE FOR START NORMAL STOP AT THE EXPIRYT3210 3 20s - LOC_UPD_REQ sent- LOC_UPD_ACC- LOC_UPD_REJ- AUTH_REJ- Lower layer failureStart T3211T3211 1215s - LOC_UPD_REJ with cause#17 netw. failure- lower layer failure or RR conn. released after RR conn. abort during loc
12、. updating- Time out- cell change- request for MM connection establishment- change of LARestart the Location update proc.T3212 1,2Note 1 - termination of MM service or MM signalling- initiation of MM service or MM signallinginitiate periodic updatingT3213 12114s - location updating failure- expiry-
13、change of BCCH parameternew random attemptT3214 35720s AUTHENT FAILURECause = MAC failure or GSM authentication unacceptable sentAUTHENT REQ receivedConsider the network as false (see 4.3.2.6.1)T3216 35715s AUTHENT FAILURECause = Synch failure sentAUTHENT REQ received Consider the network as false (
14、see 4.3.2.6.1)T3218 35720s 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- AUTHENT REJ received- AUTHENT FAIL s
15、ent- enter MM IDLE or NULLDelete the stored RAND and REST3220 7 5s - IMSI DETACH - release from RM-sublayerenter Null or Idle, ATTEMPTING TO UPDATET3230 5 15s - CM SERV REQCM REEST REQ- Cipher mode setting- CM SERV REJ- CM SERV ACCprovide release ind.T3240 91010s see subclause 11.2.1 see subclause 1
16、1.2.1 abort the RR connectionT3241 25 300s see subclause 11.2.1 see subclause 11.2.1 abort the RR connectionGMM 定时器（MS 侧）：TIMER NUM.TIMER VALUESTATE CAUSE OF START NORMAL STOP ON THE1st, 2nd, 3rd, 4th EXPIRY Note 3T3310 15s GMM-REG-INITATTACH REQ sent ATTACH ACCEPT receivedATTACH REJECT receivedRetr
17、ansmission of ATTACH REQT3311 15s GMM-DEREG ATTEMPTING TO ATTACH orGMM-REG ATTEMPTING TO UPDATEATTACH REJ with other cause values as described in chapter GPRS Attach ROUTING AREA UPDATE REJ with other cause values as described in chapter Routing Area Update Low layer failureChange of the routing are
18、aRestart of the Attach or the RAU procedure with updating of the relevant attempt counterT3316 30s GMM-REG-INITGMM-REGGMM-DEREG-INITGMM-RA-UPDATING-INTGMM-SERV-REQ-INIT(Iu mode only)RAND and RES stored as a result of a UMTS authentication challengeSecurity mode setting(Iu mode only)SERVICE ACCEPT re
19、ceived. (Iu mode only)SERVICE REJECTreceived(Iu mode only)ROUTING AREA UPDATE ACCEPT receivedAUTHENTICATION AND CIPHERING REJECT receivedAUTHENTICATION_AND_CIPHERING FAILURE sentEnter GMM-DEREG or GMM-NULLDelete the stored RAND and REST3318 20s GMM-REG-INITGMM-REGGMM-DEREG-INITGMM-RA-UPDATING-INTGMM
20、-SERV-REQ-INIT (UMTS only)AUTHENTICATION & CIPHERING FAILURE (cause=MAC failure or GSM authentication unacceptable) sentAUTHENTICATION & CIPHERING REQUEST receivedOn first expiry, the MS should consider the network as false (see 4.7.7.6.1)T3320 15s GMM-REG-INITGMM-REGGMM-DEREG-INITGMM-RA-UPDATING-IN
21、TGMM-SERV-REQ-INIT (UMTS only)AUTHENTICATION & CIPHERING FAILURE (cause=synch failure) sentAUTHENTICATION & CIPHERING REQUEST receivedOn first expiry, the MS should consider the network as false (see 4.7.7.6.1)T3321 15s GMM-DEREG-INITDETACH REQ sent DETACH ACCEPT receivedRetransmission of the DETACH
22、 REQT3330 15s GMM-ROUTING-UPDATING-INITIATEDROUTING AREA UPDATE REQUEST sentROUTING AREA UPDATE ACC receivedROUTING AREA UPDATE REJ receivedRetransmission of the ROUTING AREA UPDATE REQUESTmessageTIMER NUM.TIMER VALUESTATE CAUSE OF START NORMAL STOP ON EXPIRYT3302 Default 12 minNote 1 GMM-DEREGorGMM
23、-REGAt attach failure and the attempt counter is greater than or equalto 5.At routing area updating failure and the attempt counter is greater than or equal to 5.At successful attachAt successful routing area updatingOn every expiry, initiation of theGPRS attach procedureorRAU procedureT3312 Default
24、 54 minNote1GMM-REG In GSM, when READY state is left.In UMTS, when PMM-CONNECTED mode is left.When entering state GMM-DEREG Initiation of the Periodic RAU procedureT3314READY(GSM only)Default 44 secNote 2All except GMM-DEREGTransmission of a PTP PDU Forced to Standby No cell-updates are performedT33
25、17(UMTS only)10s GMM-SERVICE-REQUEST-INITIATEDSERVICE REQ sent Security mode control procedure is completed,SERVICE ACCEPT received, orSERVICE REJECT receivedAbort the procedureSM 定时器（MS）：TIMER NUM.TIMER VALUESTATE CAUSE OF START NORMAL STOP ON THE1st, 2nd, 3rd, 4th EXPIRYT3380 30s PDP-ACTIVE-PENDAC
26、TIVATE PDP CONTEXT REQUEST or ACTIVATE SECONDARY PDP CONTEXT REQUEST sentACTIVATE PDP CONTEXT ACCEPT or ACTIVATE SECONDARY PDP CONTEXT ACCEPT receivedACTIVATEPDP CONTEXT REJECT or ACTIVATESECONDARY PDP CONTEXT REJECT receivedRetransmission of ACTIVATE PDPCONTEXT REQ or ACTIVATE SECONDARY PDP CONTEXT
27、 REQUESTT3381 8s PDP-MODIFY-PENDINGMODIFY PDP CONTEXT REQUEST sentMODIFY PDP CONTEXT ACCEPT receivedRetransmission of MODIFY PDP CONTEXT REQUESTT3390 8s PDP-INACT-PENDDEACTIVATE PDP CONTEXT REQUEST sentDEACTIVATE PDP CONTEXT ACCreceivedRetransmission of DEACTIVATEPDP CONTEXT REQUESTCC 定时器（MS）：TIMNUM
28、.TIM VALSTATE OF CALLCAUSE OF STARTNORMAL STOPAT FIRST EXPIRYAT SECOND EXPIRYT303 30s Call initiated CM SER RQ sentCALL PROC, or REL COMP receivedClear the call Timer is not restartedT305 30s Disconnect RequestDISC sent REL or DISC receivedREL sent. Timer is not restartedT308 30s Release requestREL
29、sent REL COMP or REL receivedRetrans. RELEASE restart T308Call ref. releaseT310Note 130s Outgoing call ProceedingCALL PROC receivedALERT,CONN, DISC or PROG rec.Send DISC Timer is not restartedT313 30s Connect RequestCONN sent CONNect ACKnowledge receivedSend DISC Timer is not restartedT323 30s Modif
30、y RequestMOD sent MOD COMP or MOD REJ receivedClear the call Timer is not restartedT332 30s Wait for network infoSTART_CC sentCC-EST. receivedClear the call Timer is not restartedT335 30s CC-Est. ConfirmedCC-EST CONF.sentRECALL receivedClear the call Timer is not restartedT336 10s START DTMF sentSTART DTMF ACK or START DTMF REJECT receivedTimer is not restartedThe MS considers the DTMF Procedure (for the digit) to be terminatedT337 10s STOP DTMF sentSTOP DTMF ACK receivedThe MS considers the DTMF procedure (for the current digit) to be terminatedTimer is not restarted
