Vous êtes sur la page 1sur 7

Dear 3G Experts, can any one tell me what is the difference between T314 and T315 in 3G?

hari_2208 2011-02-10, 01:44 AM 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 re-establish 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. zhanglw268 T314 is used for CS radio link failure, T315 is used for PS radio link failure. idxtor 2012-02-07, 07:15 PM here is quote from the following document:[Only registered and activated users can see links] In 3G a new mechanism is available to rescue some dropped calls (both CS and PS) due to RL Failure: Call Reestablishment by Cell Update procedure. Refer to ANNEX I (file:///C:/Documents%20and%20Settings/iivanov/%D0%9C%D0%BE%D0%B8%20%D0%B4%D0%BE%D 0%BA%D1%83%D0%BC%D0%B5%D0%BD%D1%82%D1%8B/Downloads/79118694-OptimizationGuidelines-Retain-Ability-NSN-Draft1.doc#_5BANNEX_I:_Call) for further details. If timer T314 is set higher than 0, Voice calls that suffer from a RL Failure are not considered dropped till timer T314 expires and the call could not be reestablished by the Cell Update Procedure. Similarly, if timer T315 is set higher than 0, PS calls that suffer from a RL Failure are not considered dropped till timer T315 expires and the call could not be reestablished by the Cell Update Procedure. We could say that in both cases, CS and PS, those RL Failures that can be rescued are just systemperceived drops, but not user-perceived drops, as the user does not have to perform any additional manual operations like for example manual re-activation of the PDP context. In reality, during the Cell Update procedure (T314 or T315 seconds), Voice calls will be perceived as silent by the user, and PS data sessions may suffer from delays and lower throughputs, but the fact is that the call does not drop, and it is not counted by the RAB releases counters (and therefore, neither as a drop). In NSN infrastructure, T314=0 is hardcoded, and T315=30 sec (changeable), i.e., this Cell Update mechanism is only available for PS data calls (not for Voice calls). In terms of Voice Calls, this means that all RL Failures in DL will finally lead to a drop (user and system perceived, and RAB release counters and drops- increased). In terms of PS Calls, those RL Failures that are rescued will be system but not user-perceived, and the abnormal RAB release counter (=drops) will not be increased. As some other vendors may have the Cell Update mechanism de-activated for PS, the optimization team 2011-02-10, 09:22 AM

should keep in mind these considerations when comparing PS DCR (%) in different vendors: usually worst in those ones with this functionality disabled. Nevertheless, this worst behavior in the KPI usually does not match the user perception (that is typically good) thanks to additional implicit re-establishment mechanisms (Paging/Service Request). phuvuong_uk Can we set it with NodeB level? narula.pawan@gmail.com Dear 3G Experts, can any one tell me what is the difference between T314 and T315 in 3G? Dear, These are the UE Timers used during the Cell Update T314: RRC Connection Re-Establishment Timer used for CS-RAB services.UE starts this timer where there is RL failure and exists till the UE completes the cell update procedure. Once this timer expired then it releases the CS-RAB. T315: RRC Connection Re-Establishment Timer used for PS-RAB services.UE starts this timer where there is RL failure and exists till the UE completes the cell update procedure. Once this timer expired then it releases the PS-RAB. Br.. Pawan nkboy9 t314 for cs domain (or CS RAB) t315 for ps domain (ps rab) 2012-02-21, 03:03 AM 2012-02-09, 02:07 AM

2012-02-09, 06:35 AM

UE Protocol timers, counters, other parameters and default configurations



Posted by: Caterpillar on: September 8, 2010 In: RRC Leave a Comment

Timers for UE
Timer Start Stop At expiry

T300

Transmission of Reception of RRC RRC CONNECTION CONNECTION SETUP REQUEST Transmission of Reception of CELL CELL UPDATE UPDATE/URA CONFIRM/URA

T302

Retransmit RRC CONNECTION REQUEST if V300 =< N300, else go to Idle mode Retransmit CELL UPDATE/URA UPDATE if V302 =<

Timer

Start

Stop

At expiry

UPDATE T304

T305

T307

T308

T309

T310

T311

UPDATE CONFIRM N302, else, go to Idle mode Transmission of Reception of UE Retransmit UE UE CAPABILITY CAPABILITY CAPABILITY INFORMATION INFORMATION if INFORMATION CONFIRM V304 =< N304, else initiate a cell update procedure Entering Entering another state. Transmit CELL CELL_FACH or UPDATE if T307 is URA_PCH or not activated and the CELL_PCH state. UE detects in service Reception of area. Otherwise, if CELL UDPATE T307 is not active, CONFIRM/URA start T307. UPDATE CONFIRM. When the timer When the UE detects Transit to idle mode T305 has expired in service area. and the UE detects out of service area. Transmission of Not stopped Transmit RRC RRC CONNECTION CONNECTION RELEASE RELEASE COMPLETE if V308 COMPLETE <=N308, else go to idle mode. Upon reception of Successful response to Resume the CELL CHANGE a connection connection to UTRAN ORDER FROM establishment request UTRAN message in the new cell. Transmission of Reception of Transmit PUSCH PUSCH PHYSICAL SHARED CAPACITY CAPACITY CHANNEL REQUEST if V310 =< REQUEST ALLOCATION N310, else procedure stops. Reception of Reception of UE may initiate a PHYSICAL PHYSICAL SHARED PUSCH capacity SHARED CHANNEL request procedure. CHANNEL ALLOCATION ALLOCATION message with message with the CHOICE PUSCH CHOICE allocation set to PUSCH PUSCH allocation

Timer

Start

Stop

At expiry

T312

allocation set to PUSCH allocation pending. When the UE starts to establish dedicated CH

assignment.

T313

T314

When the UE detects The criteria for N312 in sync physical channel indication from L1. establishment failure is fulfilled When the UE When the UE detects The criteria for Radio detects consecutive N315 in Link failure is fulfilled consecutive N313 sync indication from out of sync L1. indication from L1. When the criteria When the Cell Update See subclause 8.3.1.13 for radio link procedure has been failure are completed. fulfilled.
The timer is started if radio bearer(s) that are associated with T314 exist of if only RRC connection exists.

T315

When the criteria When the Cell Update See subclause 8.3.1.14 for radio link procedure has been failure are completed. fulfilled.
The timer is started only if radio bearer(s) that are associated with T315 exist.

T316

When the UE When the UE detects detects out of in service area. service area in URA_PCH or CELL_PCH state

T317

When the T316 expires or when

Initiate cell update procedure if in service area is detected. Otherwise start timer T317, transit to CELL_FACH state and initiate cell update procedure when the UE detects in service area. When the UE detects Transit to idle mode in service area.

Timer

Start

Stop

At expiry

in CELL_FACH state, the UE detects out of service area.

Counters for UE
Counter Reset V300 When reaching max value When initiating Upon expiry of T300. When V300 > N300, the procedure the UE enters idle RRC connection mode. establishment When initiating Upon expiry of T302 When V302 > N302 the procedure Cell the UE enters idle update or URA mode. update When sending the Upon expiry of T304 When V304 > N304 first UE the UE initiates the CAPABILITY Cell update procedure INFORMATION message. When sending the Upon expiry of T308 When V308 > N308 first RRC the UE stops reCONNECTION transmitting the RRC RELEASE CONNECTION COMPLETE RELEASE message in a RRC COMPLETE message. connection release procedure. When sending the Upon expiry of T310 When V310 > N310 first PUSCH the UE stops reCAPACITY transmitting the REQUEST PUSCH CAPACITY message in a REQUEST message. PUSCH capacity request procedure Usage Maximum number of retransmissions of the RRC CONNECTION REQUEST message Maximum number of retransmissions of the CELL UPDATE / URA UPDATE message Maximum number of retransmissions of the UE CAPABILITY INFORMATION message Maximum number of retransmissions of the RRC Incremented

V302

V304

V308

V310

UE constants and parameters


Constant N300 N302 N304 N308

Constant N310 N312 N313 N315

Usage CONNECTION RELEASE COMPLETE message Maximum number of retransmission of the PUSCH CAPACITY REQUEST message Maximum number of in sync received from L1. Maximum number of successive out of sync received from L1. Maximum number of successive in sync received from L1 during T313 is activated.