Timer Description in LTE

Radio & NAS Signaling Failure Info Radio Problem Cause

Ericsson Internal | 2011-04-22 | Page 2

Problem cause contribution in good rf

Ericsson Internal | 2011-04-22 | Page 3

331 Ericsson Internal | 2011-04-22 | Page 4 .Timers description TS 36.

T-301 › Timer is 1s – unable to successfully RACH when trying to send RRC Connection Re-Establishment Ericsson Internal | 2011-04-22 | Page 5 .

UE RACH to attempt access Ericsson Internal | 2011-04-22 | Page 6 .T301 expiry example › T301 started when UE sends RRC Connection Re-Establishment Request – As shown above.

T301 expiry is pegged.T301 expiry example › 1sec after initiation. as no response to RACH – Low RSRP in this area › 10 sec later new RRC Connection Request issued Ericsson Internal | 2011-04-22 | Page 7 .

Timers description TS 36.331 Ericsson Internal | 2011-04-22 | Page 8 .

T-300 › Timer is 1s – unable to successfully RACH when trying to send RRC Connection Request Ericsson Internal | 2011-04-22 | Page 9 .

next access is RRC Connection Request.T300 expiry example › Continuing previous example of t301 expiry. other wise T300 expiry Ericsson Internal | 2011-04-22 | Page 10 . which also requires response within 1sec.

after no response – In general these issues are found in poor RF – but occurrence in Good DL RF is likely to indicate issues such as site problem. T300 expiry example › Here we see T300 expiry. or UL interference Ericsson Internal | 2011-04-22 | Page 11 .

331 Ericsson Internal | 2011-04-22 | Page 12 .Timers description TS 36.

Technical Session – Intra-LTE Handover Ericsson Internal | 2011-04-22 | Page 13 .T-304 Indicates Handover Failure › Timer is 1s – unable to RACH to Target Cell at Handover › Example on following slides – please also see: –Ref: Pre-L Optim.

T304 expiry example › This example shows that UE issues MR as PCI 348 has met Event A3 criteria – RRC Connection Reconfiguration message is received after the MR – indicated that HO to PCI 348 should take place Ericsson Internal | 2011-04-22 | Page 14 .

T304 expiry example › When UE attempts to send RRC Connection Reconfiguration Complete to target cell. then moves to Idle. we see repeated RACH at Max Power – The UE does not receive response. and initiates the RRC Connection Re-establishment procedure – Cause code in RRC Connection Re-establishment Request is handoverFailure Ericsson Internal | 2011-04-22 | Page 15 .

Timers description TS 36.331 Ericsson Internal | 2011-04-22 | Page 16 .

assuming N311=1. in RRC-CONNECTED mode. › Uplink synchronization is achieved using the random access procedure. timer T310 is stopped. › Qout and Qin are defined relative to the block error rate of a hypothetical PDCCH transmission.133. Ericsson Internal | 2011-04-22 | Page 17 . see the document Random Access for further information. See 3GPP TS 36. › At the expiry of the timer T310. assuming N310=1.133. the UE achieves the downlink synchronization during the cell search procedure. › Radio link quality evaluation is performed by the RBS for the uplink physical layer radio link synchronization evaluation. See 3GPP TS 36. Qin is defined as the level at which the downlink radio link can be received with significant reliability. The UE. The UE bases its evaluation on the cell-specific reference signal relative to thresholds Qout and Qin. › If the UE is in DRX mode.RL Synchronization › T310 / T311 are related to Radio Link (RL) Synchronization – Below is and extract from LTE RAN CPI.133. evaluates in the downlink the quality of the radio link of the serving cell.133.2 Radio Link Synchronization › As described previously. › If the radio link quality is below the threshold Qout over the period of 200ms. If the radio link quality is above the threshold Qin over the period of 100ms. › Qout is defined as the level at which the downlink radio link cannot be reliably received. see 3GPP TS 36. The quality of the radio link is evaluated in every radio frame if the UE is not in Discontinuous Reception (DRX) mode. and the thresholds are defined in 3GPP TS 36. the UE switches off uplink transmission.2. which describes the circumstances where these RL Synchronization mechanisms are utilized › 3. timer T310 is started. then DRX cycle length dependent evaluation period is used instead.

it can be seen that after call is setup at 03:56:05.T-310 expiry example › In this example. RSRP is already quite low Ericsson Internal | 2011-04-22 | Page 18 .

when T310 expiry occurs.T-310 expiry example › By 03:56:13. signal quality as well as coverage. and RL is lost Ericsson Internal | 2011-04-22 | Page 19 . has deteriorated.

331 Ericsson Internal | 2011-04-22 | Page 20 .Timers description TS 36.

T-311 › Timer is 3s – unable to find suitable cell in order to send RRC Connection Re-Establishment Request Ericsson Internal | 2011-04-22 | Page 21 .

UE attempts to initiate RRC Connection Re-establishment procedure. we see that after T310 expiry.T-311 expiry example RRC Re-establishment initiation No suitable cell for 3s Inactive (search again after 10s) › Continuing the example in the T310 section. but is not able to find a suitable cell › These issues usually indicate areas of poor coverage Ericsson Internal | 2011-04-22 | Page 22 .

for no response after 10 retransmission – UE Analysis often reveals these 2 causes at the same issue › Some additional information on TA on next slide.Timing Alignment (TA) › TA_Expire and MAC_RA_Problem are 2 cause-codes seen regularly – Generally also in poor RF. also occasionally in rapidly changing RF › TA_Expire – Timing advance expire reported by UE (RACH to achieve synchronization is necessary) › MAC_RA_Problem – Random Access attempt to re-sync. also with example of both cause-codes occurring › New setting of TATimer in R5DJ is targeted to improve Timer Alignment performance on LG Device Ericsson Internal | 2011-04-22 | Page 23 .

TA_expire/MAC_RA_Problem › Example of multiple TA_Expire and MAC_RA_PRO BLEM. in area where there are numerous servers. of low RSRSP › UE is able to re-sync via RACH. but ultimately loses RRC Ericsson Internal | 2011-04-22 | Page 24 .

and also normal user-initiated releases. will be noted as RRC Connection Release (other) – This should be borne in mind when performing call analysis Ericsson Internal | 2011-04-22 | Page 25 . at next access › As currently there are only 2 cause codes for normal release (other. loadbalancingTAUrequired) – therefore release due to inactivity.UE Analysis Inactivity release › Parameter tInactivityTimer (10s) › RRC connection is release after no user data exchanged for a duration of the expiry of this timer › Note that PDN connectivity is maintained. allowing faster setup from Idle mode.

no throughput › 10 seconds of inactivity › tInactivityTimer = 10s – No User Plane Traffic – Normal Release Ericsson Internal | 2011-04-22 | Page 26 .Release caused by other while in good rf condition .

NAS Signalling Failures › The following slide is an example distribution of the NAS release causes encountered on an LTE Cluster Drive Test– – These are generally consequences of underlying issue (see previous slides). then on NAS level the categorization is related to that procedure that was ongoing Ericsson Internal | 2011-04-22 | Page 27 .331). Detach.g. etc. RRC failure – These causes are incremented due to RRC Connection failure. rather if a RRC Connection failure occurred (due to a reason in previous slides for example). majority of release causes relate to RRC Connection Release Other: – Due to RRC Connection Release cause codes (TS 36. TAU accept. are not failures explicitly due to the settings of those timers. Inactivity release. during a procedure being monitored by one of these timers. but the pegging of the NAS release cause is often different depending on the procedure that was underway when the underlying issue occurred › The subsequent slides highlights the NAS timers mentioned (REF: 3GPP TS 24.. normal releases (e.. T3430 etc.301) › In general.) are also included as “other” categorization › RRC Connection release. leading to initiation of RRC Connection Re-Establishment procedure – See previous slides for more details on the causes of the RRC Connection failures › And its important to note that the events tagged as T3411.

Radio & nas signaling failure excluding Detach accept & tracking area update Ericsson Internal | 2011-04-22 | Page 28 .

301 Ericsson Internal | 2011-04-22 | Page 29 .Timers TS 24.