Download as xlsx, pdf, or txt
Download as xlsx, pdf, or txt
You are on page 1of 1

Handover Execution Failure

Consider a scenario, where UE tries to perform a handover and fails. In this case, the UE will wait for a specific time as per T304 and once T304 expires,
initiate a RRC ReEstablishment with the cause value of Handover failure. Now, if this RRC ReEstablishment also fails and the UE is unable to get a conne
the source eNB will release the context after expiry of the internal timer. This is the X2 Reloc Overall Timer and the cause of this release will be X2 Reloc
Overall Expiry. Such a case is pegged under call drop due to Handover failure.

Optimization
The most common issue for this kind of failure is when the target cell is very far away such that when the UE initiates handover on the target cell, it is at a
distance beyond the cell radius. So, the target cell fails to decode the dedicated RACH properly for this UE and it results in a handover failure. So, in this c
either increase the cell radius of the target cell or downtilt it so that it does not overshoot beyond its planned radius. This can also happen in areas where
are large water bodies as signals easily tend to get reflected over water. In such cases, either forbid handovers to such cells or add offsets for those cells
make handovers difficult.

You might also like