WCDMA Timer
November 12, 2016 | Author: anh00 | Category: N/A
Short Description
Timer for WCDMA UE...
Description
UE WCDMA/UMTS Timers This page covers timers used in 3G/WCDMA/UMTS compatible UE which include T300,T302,T304,T305,T307,T308,T309,T310,T311,T312,T313,T314,T315 and T316 timers. WCDMA/UMTS Timer T300
T302
T304
T305
T307
T308
T309
T310
T311
Function when Start/Stop/at expiry >>Starts at the transmission of RRC CONNECTION REQ >>Stops at the receipt of RRC Connection setup >> At expiry, re-transmits RRC CONNECTION REQ if V300> Starts at the transmission of Cell Update or URA Update >> Stops at the receipt of Cell Update Confirm or URA Update Confrim >> At expiry, re-transmits Cell Update/URA Update if V302> Starts at the transmission of UE Capability Info >> Stops at the receipt of UE capability Information Confirm >> At Expiry, re-transmits UE capability information if V304> Starts upon entering CELL_FACH/URA_PCH/CELL_PCH state. OR upon receipt of CELL Update Confirm/URA Update Confirm >> Stops upon entering another state >> At expiry, transmits CELL Update if T307 is not activated and UE detects "In Service Area" Otherwise If T307 is not active, initiate starting of timer T307 >>Starts when timer T305 has been expired and UE detects the " Out of Service Area" >>Stops when UE detects "In Service Area" >>At Expiry it transit to the IDLE MODE >> Starts at the transmission of RRC Connection Release Complete >> Not Stopped >> At Expiry,transmits RRC connection Release Complete IF V308>Starts upon receipt of Cell Change Order from UTRAN message >> Stops upon successful response to a CONNECTION ESTABLISHMENT REQUEST in a new CELL >> At Expiry, resumes the Connection to UTRAN network >> Starts upon transmission of PUSCH Capacity Request message >> Stops upon receipt of Physical Shared Channel Allocation >> At expiry transmits PUSCH Capacity Request if V310 > Starts upon reception of Physical Shared Channel Allocation ( When "PUSCH ALLOCATION" set to "PUSCH ALLOCATION pending")
T312
T313
T314
T315
T316
T317
>> Stops upon receipt of Physical Shared Channel Allocation ( When "PUSCH allocation" set to "PUSCH allocation assignment") >> At Expiry, UE initiate a PUSCH CAPACITY REQUEST procedure >>Starts When UE starts to establish dedicated channel mode >>Stops When UE detects N312 "in sync" indication from Layer-1(PHY) >>Timer expires when criteria for physical channel establishment failure is fulfilled >>Timer Starts when UE detects consecutive N313 "out of sync" indication from Layer-1(PHY) >> Stops when UE detects consecutive N315 "in sync" indication from Layer-1(PHY) >> Timer expires when the criteria for Radio Link failure is fulfilled >>Starts after the criteria for radio link failure have been fulfilled, and if radio bearers associated with T314 exists. >>Stops when the cell update procedure completes >>REFER 8.3.1.13 in 3GPP TS 25.331 Specification >>Starts after the criteria for radio link failure have been fulfilled, and if radio bearers associated with T315 exists. >> Stops when the cell update procedure completes >> REFER 8.3.1.14 in 3GPP TS 25.331 Specification >>Starts when UE detects "out of service area" in the URA_PCH or CELL_PCH state >>Stops when UE detects "in service area" >>At expiry,initiates cell update procedure if "in service area" is detected, OTHERWISE starts timer T317, transit to CELL_FACH state and initiate cell update procedure when the UE detects "in service area" >> Starts when timer T316 expires OR when in CELL_FACH state, UE detects "out of service area" >> Stops when UE detects "in service area" >> At Expiry, transits to IDLE MODE
V300,V302,V304,V308 abd V310 are counters used in UE. N300,N302,N304,N308,N310,N312,N313 and N315 are constants used in UE. For information refer 3GPP TS 25.331 Specification .
what is the difference between T314 and T315 in 3G? T314 & T315 are guard timers during which the UE keeps the RABs following radio link failure until they expire or the cell update procedure has been completed. During this time, the RNC can try to reestablish the UE so that the user traffic can resume. When T314 and / or T315 expire, the UE releases the associated RABs. From specs.... t302 : Starts at the transmission of CELL/URA UPDATE, and stops at the reception of CELL/URA UPDATE CONFIRM. T314 expiry Upon expiry of timer T314 the UE shall: 1> if timer T302 is running: 2> continue awaiting response message from UTRAN. 1> if timer T302 is not running and timer T315 is running: 2> set IE "T314 expired" in variable RB_TIMER_INDICATOR to TRUE; 2> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT314"; 2> indicate release of those radio access bearers to upper layers; 2> delete all information about those radio access bearers from the variable ESTABLISHED_RABS; 2> if all radio access bearers associated with a CN domain are released: 3> release the signalling connection for that CN domain; 3> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 3> indicate release (abort) of the signalling connection to upper layers. 1> if timers T302 and T315 are not running: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> and the procedure ends. T315 expiry Upon expiry of timer T315 the UE shall: 1> if timer T302 is running: 2> continue awaiting response message from UTRAN. 1> if timer T302 is not running and timer T314 is running:
2> set IE "T315 expired" in variable RB_TIMER_INDICATOR to TRUE; 2> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "use T315"; 2> indicate release of those radio access bearers to upper layers; 2> delete all information about those radio access bearers from the variable ESTABLISHED_RABS; 2> if all radio access bearers associated with a CN domain are released: 3> release the signalling connection for that CN domain; 3> remove the signalling connection for that CN domain from the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 3> indicate release (abort) of the signalling connection to upper layers. 1> if timers T302 and T314 are not running: 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; 2> clear the variable PDCP_SN_INFO; 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; 2> release all its radio resources; 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; 2> clear the variable ESTABLISHED_RABS; 2> set the variable CELL_UPDATE_STARTED to FALSE; 2> enter idle mode; 2> other actions the UE shall perform when entering idle mode from connected mode are specified in subclause 8.5.2; 2> and the procedure ends.
View more...
Comments