LTE RRC Connection Drop

Case 1

1. Normal Detach request pegged as RRC Drop.

2. RF conditions were OK, RSRP =-98.9dBm , RSRQ =-8.0 dB and normal UE Tx power further suggests there was no problem with RF.
3. Detach request might have been sent manually and hence there was no actual drop at this point.

Case 2

1. RRC Drop occurred on site IAL01222_2C_1 PCI 336 with EDT 2 serving from 3.5 miles.
2. RF conditions were degraded , RSRP =-119 dBm , RSRQ=-11.94 dB , multiple measurement reports were sent however there was no response.
3. UE power maxed out , it lost UL sync resulting in RRC Drop

Case 3

1. RRC Drop occurred on site IAL01222_2B_1 PCI 338 with EDT 2 serving from 2.3 miles.
2. RF conditions were degraded , RSRP =-120 dBm , RSRQ=-12.69 dB , multiple measurement reports were sent however there was no response.
3. UE kept dragging and UE power maxed out , it lost UL sync resulting in RRC Drop

Case 4

RACH failed

HO command
1. HO initiated from site IAL02024_9A_1 PCI 273 to site IAL02024_9C_1 PCI 275.
2. UE radiating with maximum power suggests some UL path issue even when DL RF conditions were fine.
3. RACH failure occurred and UE couldnt access Target cell IAL02024_9C_1 PCI 275 resulting in HO failure and therefore RRC got dropped.

Case 5

1. RRC drop pegged when UE was latched on site WIL03323_8B_1 PCI 164.
2. Good RF conditions, RSRP=-88 dBm , RSRQ =-7dB & normal UE Tx power suggests that Drop didnt occur due to RF conditions.
3. Drop might have occurred due to temporary UE issue or It might be a normal detach from network however can not be confirmed as L3
messages were missing for around 500ms right at the drop

Case 6

1. HO initiated from site WIL06247_7C_1 PCI 444 with EDT 3 to site WIL06288_7A_1 PCI 110 with EDT 5 serving from 12.34 miles away.
2. Due to poor RF conditions , RACH failed and UE couldnt access site WIL06288_7A_1 PCI 110 , UE power maxed out , it lost UL Sync resulting
in RRC Drop.

Case 7

1. RRC Call drop has occurred due to handover failure between site NEL02161_2C_1 PCI 208 and NEL02147_2B_1 PCI 325 overshooting from 30
miles.
2. Due to poor RF conditions and large distance , UE Tx power maxed out , it lost sync resulting in handover failure and RRC Drop.
3. Need to reduce cell radius of site NEL02147_2B_1 PCI 325

Case 8

1.
2.
3.
4.

RRC Call Drop has occurred due HO failure,

UE latched on cell WIL03353_7A_1 PCI 342 with poor RF conditions RSRP = -120.9 dBm, RSRQ = -16.63dB at a distance from 9.14 miles away .
UE initiated intra frequency HO towards target overshooter cell WIL05847_7C_1 PCI 329 however UE suddenly looses UL sync ,
UE tried to RRC connection re-establishment which resulting HO failure and RRC got dropped.

Case 9

1.
2.

At poor RF conditions, HO was initiated from site NEL01085_7A_1 PCI 204 to site NEL01005_7B_1 PCI 163 serving from 0.5
miles.
UE suddenly looses sync due to poor RF quality , RSRQ<-15dB and tries to re-establish connection back on site
NEL01085_7A_1 PCI 204 however gets rejected and RRC got dropped.

Case 10

1. UE latched on site IAL02004_9C_1PCI 138 EARFCN 1075 serving from 1.6 miles with EDT 6.
2. Multiple measurement reports were sent for site IAL02013_7A_1 PCI 165 EARFCN 5815 however no IFHO HO command initiated from serving site
IAL02004_9C_1.

Case 11

1. RRC Connection was re-established successfully by UE on site OHL05909_B PCI 224 from 2.5 miles which was wrongly pegged as RRC Drop .
2. UE remained in RRC_Connected state confirms there was no RRC drop..

IRAT HO Analysis

Case 1

UE was redirected to UMTS UARFCN 1087 when RSRP of site WIL05863_7B_1 PCI 164 degraded below -110dBm at distance of 2.41 miles away from
LTE site.

Case 2

At poor LTE coverage , UE was redirected to UMTS ARFCN 4382.

After redirection , UE latched onto UMTS site and hence IRAT was successful.