Timer & Constant (idle/connected)

What is it

JNB Value

Reference Operator (X)

Impact On KPI

How it works The UE starts T300 after transmission of the RRC Connection Request message and stops T300 when it receives the RRC Connection Setup message. At expiry the UE retransmits the RRC Connection Request message if it has not retransmitted N300 requests yet, otherwise the UE enters Idle Mode. The UE starts T300 after transmission of the RRC Connection Request message and stops T300 when it receives the RRC Connection Setup message. At expiry the UE retransmits the RRC Connection Request message if it has not retransmitted N300 requests yet, otherwise the UE enters Idle Mode.

Technical Guidelines for optimized values

Uu_RRC_UE_IdleTimersAn dConstants_t_300

Max time for transmission of RRC Connection Request Message to RRC Connection Setup Message

2000ms

1200ms

Call setup time

If T300 is chosen too short, the UE consumes resources unnecessarily by resending the request before a UTRAN response might be received. Also, the retransmission might occur under similar RF channel conditions as the previous (failed) transmission. If T300 is chosen too long, the call set -up delay increases unnecessarily. The recommended value of 1200ms for T300 provides a right ba lance between UTRAN processing time, time-selectivity of the RF channel, and call set-up delay. The optimal setting depends on the infrastructure implementation. It may need to be increased if the network is slow in responding and vice versa.

Uu_RRC_UE_IdleTimersAn dConstants_n_300

Max number of retransmission of RRC Connection Request Message

Call setup time

If N300 is set too low, the RRC connection might fail due to temporarily insufficient RF conditions. If N300 is set too high, UE battery power and UL capacity are wasted by persistently trying to esta blish an RRC connection in insufficient RF conditions. The value of 5 compliments T300 value of 1200ms to struck the right balance between UTRAN processing time, time-selectivity of the RF channel, and call set-up delay

Uu_RRC_UE_ConnTimersA ndConstants_t_302

Max time for UE from Cell Update to Cell Update Confirm

3000ms

1200 ms

Cell update procedure

Maximum time for UE from transmission of Cell Update to receive Cell Update Confirm before it reattempts Cell Update/ URA Update procedure as long as N302 is not exceeded.

If T302 is chosen too short, the UE may un -necessarily re-attempt the Cell Update procedure b efore waiting sufficient time to receive a response from the network. If T302 is chosen too long, the UE may wait too long for a network response, degrade userexperience and may not be able to attempt Cell Update sufficient number of times before the expiry of the T314/T315 timers. Th e T302 recommended value is chosen similar to T300 as it is expected that the UTRAN responds to a Cell Update message within this period. This value is selected in conjunction with the N302 constant value to improve the probability of a successful Cell Upd ate procedure before expiry of the T314/T315 timers. If N302 is chosen too small, few re-tries of the Cell Update/ URA Update procedure will be possible within the T314/T315 time-window before local release of the RRC. If chosen too large there may be un-necessarily large number of re-tries

Uu_RRC_UE_ConnTimersA ndConstants_n_302

Max number of retransmission of Cell Update message

Cell update procedure

Same as above

Uu_RRC_UE_ConnTimersA ndConstants_t_312

Max time for UE to receive In Sync indication from L1 for physical channel establishment

6s

1s

RRC SR, RB SR, Cell Update

The UE starts T312 after it begins to establish the dedicated channel. It stops T312 when it receives N312 in-sync indications from L1. If the T312 expires before N312 insync indications are received from L1 the criteria for physical channel establishment failure are met. In this case the UE will resend an RRC Connection Request message if N300 has not been exceeded. If N312 is chosen too small, the number of in-sync indications may not be sufficient to suggest that the link quality will stay good. If N312 is chosen too large the amount of time taken to confirm in-sync will be larger, may delay the RRC/RAB setup procedure

If T312 is chosen too short, the UE will un-necessarily re-try the RRC setup proceure leading to physical channel establishment procedure since N312 in -sync indications may not be received within this time-frame. If T312 is chosen too long the UE may take too long to declare physical channel establishment failure, delay the re-try mechanism leading to a longer physical channel establishment period. The recommended value for T312 is chosen to be 1 sec since the DCH is normally established in less than 1 second.

Uu_RRC_UE_IdleTimersAn dConstants_n_312

Number of In-Sync indications from L1 for physical channel establishment

RRC SR, RB SR, Cell Update

The recommendation of 1 is based on the optimistic assumption that quality will stay good after just 1 in-sync indication

Uu_RRC_UE_ConnTimersA ndConstants_t_313

Max time for UE to receive Out-of-Sync indications from L1 before declaring Radio Link Failure

3s

5s

CS PS CDR

Uu_RRC_UE_ConnTimersA ndConstants_n_313

Max number of Out-of-Sync indications from L1 to trigger T313

50

50

CS PS CDR

The UE starts T313 after it detects N313 consecutive out of sync indications from L1. The UE stops T313 when it detects N315 in sync indications from L1. If the T313 expires before N315 in-sync indications are received from L1 the criteria for declaring radio link failure are met. In this case the UE will clear its physical channel information, initiate the cell search procedure and if successful and will respond with a Cell Update with cause radio link failure if configured. The UE starts T313 after it detects N313 consecutive out of sync indications from L1. The UE stops T313 when it detects N315 in sync indications from L1. If the T313 expires before N315 in-sync indications are received from L1 the criteria for declaring radio link failure are met. In this case the UE will clear its physical channel information, initiate the cell search procedure and if successful and will respond with a Cell Update with cause radio link failure if configured.

If T313 is chosen too short, N315 in-sync indications may not be received within this time -frame resulting in the UE declaring radio link failure prematurely. In this case if the network does not su pport the Cell Update procedure, the user may experience a call drop earlier. I f T313 is chosen too long the UE may take too long to declare radio link failure, delay call recovery mechanisms (such as Cell Update) negatively impacting user CS/PS experience.This timer is common for the PS and CS domains. From CS call point of view higher value is not recommended, as the user may prematurely disconnect the call. From PS point of view higher value is recommended only if Cell Update proc edure is not supported by the network.

If N313 is chosen too small, the low number of out of sync indications may unnecessarily trigger T313 in cases of small fluctuations in link quality leading possibly to early declaration of radio link failure. If N313 is chosen too large the radio link may deteriorate significantly leading to a call drop before T313 is triggered. This would be followed by either N315 in sync indications being received from L1 or T313 expiry spurring call recovery mechanisms to kick -in. The recommendation of 50 is high enough to tolerate temporary degradations in RF (causing un -necessary T313 triggering). Higher value is not needed as T313 will be started afterwards, and still give chance to recover the radio link (to receive an "in sync").

Uu_RRC_UE_ConnTimersA ndConstants_n_315

Number of consecutinve InSync indications to stop T313

CS PS CDR

Same as above

If N315 is chosen too small, the low number of in- sync indications may unnecessarily prevent expiry of the T313 in cases of only short improvements in link quality delaying declaration of radio link failure. The user experience may be deteriorated since the UE may remain in poor radio cond itions on average for a longer period without being able to search for a new cell and initiating call receovery in better conditions. If N315 is chosen too large the radio link may improve significantly though T313 may expire leading to declaration of radio link failure before N315 is reached. The call recovery mechanism and slight delay associated with the same may be unnecessarily perceived by the user. The recommendation of 1 is based on the optimistic assumption that qual ity will stay good after just 1 in-sync indication

Uu_RRC_UE_ConnTimersA ndConstants_t_314

Max time for UE (CS) to complete Cell Update procedure after Radio Link Failure

8s

12s

CS CDR

The UE starts T314 when the criteria for radio link failure are fulfilled. The timer is stopped when the Cell Update procedure has been completed. If the timer expires, the UE locally releases the RAB (unless T302 is running i.e waiting for response from UTRAN). The UE starts T315 when the criteria for radio link failure for PS call are fulfilled. The timer is stopped when the Cell Update procedure has been completed. If the timer expires, the UE locally releases the RAB (unless T302 is running i.e waiting for response from UTRAN).

If T314 is chosen too short, the UE lacks sufficient time to re-read SIBs and perform a Cell Update procedure. If T314 is chosen too long, the network will un -necessarily keep the RRC resources assigned for a long time while the end user may have released the call.T314 should be set greater than T302*N302. In case of the expiry of T314, the corresponding service RBs will be removed. For a CS call a high value has limited value, as it unlikely that that a user will wait so long in case of voice outage and network may unnecessarily reserve RRC connection resourc es for an extended period of time.

Uu_RRC_UE_ConnTimersA ndConstants_t_315

Max time for UE (PS) to complete Cell Update procedure after Radio Link Failure

30s

180s

PS CDR

If T315 is chosen too short, the UE lacks sufficient time to re-read SIBs and perform a Cell Update procedure. If T315 is chosen too long, the PS user may release the data call (given lack of data transfer) before the UE releases the RAB resources. The recommended value of 180 sec has been chosen given that most networks support the Cell Update procedure for PS domain and hence allowing for a longer period to receover the call without requesting for user -intervention is considered beneficial especially in case of PS service.