Huawei LTE Handover Events PDF
Huawei LTE Handover Events PDF
Huawei LTE Handover Events PDF
UL allocation Legend
2.Measurement Reports L3 signalling
(RRC_MEAS_RPRT)
L1/L2 signalling
3.HO decision
Preparation
4.Handover Request
User Data
Handover
(HANDOVER_REQUEST)
5.Admission Control
6.Handover Request Ack
DL allocation (HANDOVER_REQUEST_ACKNOWLEDGE)
7.RRC Conn. Reconf. incl.
mobilityControlinformation
(RRC_CONN_RECFG(HO_CMD))
Execution
Handover
Data Forwarding
packet data
packet data
12.Path Switch Request
(S1AP_PATH_SWITCH_REQ) 13.User Plane update
request
Completion
Handover
End Marker
14.Switch DL path
packet data
18.Release Resources
Measurement Control
(RRC_CONN_RECFG)
Measurement Control CMP
(RRC_CONN_RECFG_CMP)
Once the event for report is trigged, UE periodic repeat this report until eNodeB reply the
instruction or the UE report times approach the maximum report times which is included in
measurement control message
After eNodeB receive measurement report, it select the suitable target and send handover
request message to the target cell via S1 or X2 interface. The following IEs could be
included:
eCGI of target cell
GUMMEI
UE context information
UE history information
Measurement point:
L.HHO.Prep.FailOut.MME: During handover preparation in a handover over the S1
or X2 interface, the L.HHO.Prep.FailOut.MME counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE COMMAND message
from the MME.
L.HHO.Prep.FailOut.NoReply: After the handover preparation in a handover over
the S1 or X2 interface is complete, if the source eNodeB does not receive any
messages from the target and does not cancel the handover, the
L.HHO.Prep.FailOut.NoReply counter is incremented by 1 each time the source
eNodeB does not receive a HANDOVER REQUEST ACKNOWLEDEG message or a
HANDOVER PREPARATION FAILURE message from the target eNodeB.
L.HHO.Prep.FailOut.PrepFailure: During handover preparation in a handover over
the X2 interface, the L.HHO.Prep.FailOut.PrepFailure counter is incremented by 1
each time the source eNodeB receives a HANDOVER PREPARATION FAILURE
message from the target eNodeB.
L.HHO.Prep.FailOut.HOCancel: During a handover over the S1 or X2 interface,the
L.HHO.Prep.FailOut.HOCancel counter is incremented by 1 each time the source
eNodeB decides to cancel the handover and sends a HANDOVER CANCEL message
to the MME or target eNodeB.
Early handover occurs if the target cell is not good or stable, consists of following scenarios:
Scenario 1: After receiving a handover command, a UE experiences a radio link
failure (RLF) during the handover to the target cell. Then, the UE is handed over
back to the source cell during RRC connection reestablishment.
Scenario 2: A UE camps on the target cell for a short period and the RLF happen. If
UE can reestablish the RRC connection to source cell, it is consider as a early
handover
Scenario 2: UE doesnt send measurement report, RLF happens in source cell, and RRC
establishment setup to target cell also fails.
If we dont enable the basic coverage based intra/inter frequency handover swith, then
eNdoeB doesnt send any measurement control message.
From above figure, we can see that Due to poor DL channel quality, SINR of PDCCH is very
low, leading the demodulation of UL grant failure. Therefore, the measurement report
cant be sent.
RSRP, RSRQ, IBLER and DL/UL grant statistic can be used to evaluate channel quality
Solution:
To increase the possibility of UL scheduling, we can enable the pre- allocation
scheduling, so that UE can get UL grant in advanced to send measurement report
If the poor quality is caused by coverage, then make some RF adjustment for
coverage
If the poor quality is caused by edge interference, we can enable ICIC feature to
mitigate the interference
Scenario: after eNodeB receive measurement report, if all reported cell is not in NRT
(neighbor relation table) and ANR is not enable or the cell in NRT is set forbidden handover,
then eNodeB doesnt send any handover request to target .
Solution:
Enable ANR to automatic configure NCL and NRT
Configure NRT by manual
How to check neighbor configuration
Should be Permit
HO
Scenario 2 : Due to the poor transmission quality, leading very long handover prepare time,
Solution: Contact transmission engineer to check the problem
Possible cause :
Poor DL coverage
Improper parameters handover parameters setting
Solution:
RF adjustment
This scenario is considered as delayed handover, we can use MRO algorithm to
optimize it
Possible cause
Poor coverage of target cell
PRACH power control setting problem
Handover parameters setting problem
Solutions:
Perform RF adjustment of target cell
Increase initial power or power step for PRACH
This problem is considered as early handover, we can enable MRO algorithm to
optimize the relevant parameters