06 FO - NO2004 FDD LTE Handover Optimization 60P PDF

Handover Optimization in LTE
Objectives
Learn about the concept, classification, and steps of a
handover in LTE
Learn about the inter-eNB handover, X2-based handover,
and S1-based handover procedures
Learn about how to analyze typical handover signaling
Learn about the common factors affecting a handover
Learn about the overall handover optimization outline and
how to analyze and resolve common handover problems
Contents
Overview
Handover Procedures
Handover Optimization Outline
Handover Related Radio Parameters
Case Study Common Problems and
Solutions
Purpose
What is a handover for?

Maintain call continuity in mobility.
All handovers in LTE
Improve QoS for network services. are hard handovers.
Reduce the dropped-call rate.
Lower the congestion rate.
ZTE Corporation. All rights reserved

Classification
Handovers in LTE can be classified in the following dimensions:
Whether to change the network Intra TD-LTE Handover

system TD-LTE <-> FDD LTE Handover
Intra-eNB Handover
Whether to change the eNB
Intra-LTE Inter-eNB Handover
Handover Intra-Frequency Handover
Whether to change the frequency
Inter-Frequency Handover
Handover
Intra-MME Handover
Whether to change the MME
Inter-MME Handover
TD-LTE <-> TDS Handover
TD-LTE <-> GSM Handover
Inter-RAT Handover
TD-LTE <-> UMTS Handover
TD-LTE <-> CDMA Handover

Steps
A handover involves the following three steps:
Handover Steps
Handover Handover Handover

Measurement Preparation Execution

Handover Measurement
The UE performs cell measurements and reports the

measurement information:
When?
After an RRC connection is established (i.e. after the UE receives an
RRCConnectionReconfiguration message)
What?
RSRP, and RSRQ
How?
Event triggered, or periodically

Handover Measurement
The measurement procedure includes the following three steps:

Measurement configuration: The eNB sends an
RRCConnectionReconfigurtion message to a UE, carrying the measurement
configuration applicable for the UE in the MeasConfig IE, i.e. indicating
measurements to be performed by the UE.
Measurement execution: The UE performs measurements on the serving cell,
and determines whether to perform measurements on neighboring cells
based on the s-Measure IE in the RRCConnectionReconfigurtion message.
Measurement reporting: Triggered periodically or by events. When a
reporting criterion is met, the UE carries the measurement result in a
MeasurementReport message and sends it to the eNB.

Measurement Events
Event A1 Serving becomes better than threshold (serving > threshold):

used to stop the ongoing inter-frequency measurements and release
measurement gaps.
Event A2 Serving becomes worse than absolute threshold (serving <
threshold): used to start inter-frequency measurements and set up
measurement gaps.
Event A3 Neighbor becomes amount of offset better than PCell/ PSCell
(Neighbor > Serving + Offset): used to trigger the intra-frequency / inter-
frequency handover procedure based on network coverage.
Event A4 Neighbor becomes better than absolute threshold: used to
trigger the handover procedure based on load.
Event A5 PCell/ PSCell becomes worse than absolute threshold1 (Serving
< threshold1) AND Neighbor becomes better than another absolute
threshold2 (Neighbor>threshold2): used to trigger the intra-frequency /
inter-frequency handover procedure based on network coverage.

Event A3
Event A3 is commonly used in intra-frequency handovers. Event

A2 can be used together with Event A3, A4, or A5 (A2+A3,
A2+A4, A2+A5) in inter-frequency handovers.
Entering condition for Event A3: Mn Ofn Ocn Hys Ms Ofs Ocs Off
Leaving condition for Event A3: Mn Ofn Ocn Hys Ms Ofs Ocs Off

Event A3
Mn: measurement result of the neighboring cell, not taking into account any offsets.
Ofn: frequency specific offset of the frequency of the neighboring cell, and is sent in the
measObject IE of an RRCConnectionReconfigurtion message.
Ocn: cell specific offset of the neighboring cell, and is sent in an
RRCConnectionReconfigurtion message.
Hys: hysteresis parameter for this event, and is sent in an RRCConnectionReconfigurtion
message.
Ms: measurement result of the PCell / PSCell, not taking into account any offsets.
Ofs: frequency specific offset of the frequency of the PCell / PSCell, and is set to zero and
sent in the measObject IE of an RRCConnectionReconfigurtion message.
Ocs: cell specific offset of the PCell / PSCell, and is sent in an RRCConnectionReconfigurtion
message.
Off: offset parameter for this event, and requires to be configured by upper layers. It adjusts
how difficult it is to perform a handover, and is sent in an RRCConnectionReconfigurtion
message. It can be set to a positive value to make it more difficult to trigger a handover by
this event and thus to delay handover execution, or a negative value to make it easier to
trigger a handover by this event and thus to advance handover execution.

Measurement Execution
A UE can perform measurements in either RRC_IDLE or

RRC_CONNECTED.
Measurement in RRC_IDLE: for cell reselection
Measurement in RRC_CONNECTED: for handover
A UE can perform the following types of measurements:

Intra-frequency measurements: measurements at the downlink carrier
frequency(ies) of the serving cell(s), including RSRP and RSRQ.
Inter-frequency measurements: measurements at frequencies that differ from
any of the downlink carrier frequency(ies) of the serving cell(s), including
RSRP and RSRQ.
Inter-RAT measurements: includes PCCPCH RSCP, CPICH RSCP, CPICH Ec/No,
GSM Carrier RSSI, BSIC Identification, and BSIC Reconfirmation.
UE measurements includes RSRP and RSRQ.

Measurement Reporting
When a reporting criterion is met, the UE sends a Measurement Report

message to E-UTRAN, carrying the measurement ID, measurement
result (values of the RSRP and RSRQ) of the serving cell, and
measurement result of neighboring cells.
Reporting trigger type: periodically or by events.
Periodically triggered: Measurement reports are sent periodically according to the pre-
configured report interval and the total number of measurement reports applicable.
reportStrongestCells: reports the strongest cell(s)
reportCGI: reports the global cell identity of a neighboring cell
Event triggered: The UE sends a measurement report when the entry condition of an
event is met.

Handover Preparation
Involves HO decision made by the source eNB and resources

allocation made by the target eNB.
The source eNB makes an HO decision based on the received
measurement report and Radio Resource Management (RRM)
information. If it determines the necessity to initiate the
handover, it chooses a qualified target cell and sends a
HANDOVER REQUIRED message.
The target eNB performs admission control for this handover and
allocates the required radio and bearer resources.

Handover Execution
The RRCConnectionReconfiguration message is used to modify an RRC

connection, including measurement configuration (measConfig), mobility control
(mobilityControlInfo), radio resource configuration (including RBs, MAC main
configuration, and physical channel configuration), and associated dedicated NAS
information and security configuration.
A Handover Command message is an RRCConnectionReconfiguration message
that carries the mobilityControlInfo IE).

Contents
Overview
Handover Procedures
Solutions
UE eNB
Intra-eNB Handover
An intra-eNB handover means a UE is handed Measurement Report
over from one cell to another cell of the same
eNB. It has a different procedure from the inter-
eNB handover procedure in that the handover RRC Connection Reconfiguration
preparation messages between the source and (HO Command)
target cells are transmitted within the eNB rather
than through the S1 or X2 interface.
Upon receiving a Measurement Report
RRC Connection Reconfiguration
message from the UE, the eNB determines the
Complete(HO Confirm)
necessity to initiate an intra-eNB handover. The
source cell exchanges handover messages with MSG1
a target cell within the eNB. After allocating (Random Access Preamble)
resources, the target cell notifies the source cell
of the resource information. The source cell RAR
sends an RRC Connection Reconfiguration (Random Access Response)
message to the UE over the Uu interface,
indicating the UE to perform the handover.
The eNB does not notify the CN about the intra-
eNB handover, and no S1 or X2 connection is
required during the handover. The eNB does not need to request to
switch the user data transfer path from
the CN in an intra-eNB handover.

X2-Based Handover
Before the handover

UE eNB1 eNB2 MME
1 Measurement Report
Determine to perform an
S1 S1 X2-based handover
2 Handover Request
X2 Perform admission control and

eNodeB2 allocate dedicated resources
eNodeB1 3 Handover Request ACK
4 RRC Connection Reconfiguration
Uu
5 SN Status Transfer
Detach from S-eNB
6 RA Preamble
After the handover
7 RA Response
MME
8 RRC Connection Reconfiguration Complete
S1 S1
9 Path Switch Rrquest
X2 10 Path Switch Rrquest ACK

eNodeB2 11 UE Context Release
eNodeB1
Uu Uu Delete the UE
instance

S1-Based Handover
Before the handover UE eNB1 eNB2 MME

MME
1 Measurement Report
2 Handover Required
S1 S1 Determine to perform 3 Handover Request
an S1-based handover
X2 Allocate dedicated
eNodeB2 resources
eNodeB1 4 Handover Request ACK
5 Handover Command
Uu
6 RRC Connection Reconfiguration
7.eNB Status Transfer
8.MME Status Transfer
After the handover Detach from S-eNB
MME
9 RA Preamble
10 RA Response
11 RRC Connection Reconfiguration Complete

S1 S1
12 Handover Notify
X2
13 UE Context Release Cmd
eNodeB2
eNodeB1
14 UE Context Release Complete
Uu Delete the UE
instance

Drive Test Signaling Analysis

RRC Connection Reconfiguration Drive Test
Signaling Analysis
Measurement control information is sent to a UE in an
RRCConnectionReconfiguration message during the UE's initial access
or in a Handover Command message (the
RRCConnectionReconfiguration message including mobility control
information).

Measurement Report Drive Test Signaling
Analysis
The UE sends a measurement report to the eNB, carrying the
information of all cells that meet the event description.

Handover Command Drive Test Signaling
Analysis
The Handover Command message here is an
RRCConnectionReconfiguration message including the
mobilityControlInfo IE that contains the PCI of the target cell and
all configuration information required for the handover.

MSG1 Drive Test Signaling Analysis
The UE accesses the target cell using the configuration

information included in the Handover Command message sent
by the source cell.

MSG2 Drive Test Signaling Analysis
Because the handovers specified in this release are non-

contention based random access, the UE can be considered as
having been successfully handed over to the target cell.

RRC Connection Reconfiguration Complete
Drive Test Signaling Analysis
In actual implementation, the UE completes the reassembly of the RRC
Connection Reconfiguration Complete message right after receiving the
Handover Command message from the source eNB. The purpose that it sends
the message to the target eNB is to initiate the random access procedure on the
target eNB side. This message is encapsulated and sent in the MSG3 message.

Contents
Overview
Handover Procedures
Solutions
Measurement

Report
Receive a
For any handover procedure exception, No Handover
Command?
check whether the UE, eNBs, or
Flow
11
transmission facilities operate improperly, Yes
troubleshoot them, and then make

Send an MSG1
relevant analysis. No message
successfully?
Exceptions for a handover procedure may 22

Flow
Yes
occur in the following phases: Receive an
RAR
Whether the UE receives a Handover Command No
message?
message after sending a Measurement Report to
the source eNB (Flow 1); 3
Flow 3
Yes
Whether the UE successfully sends an MSG1
Send an RRC
message to the target eNB after receiving an RRC Connection
Reconfiguration
Connection Reconfiguration message (Flow 2); Complete message (in
an MSG3 message)
Whether the UE successfully receives an MSG2

message after sending the MSG1 message (Flow 3).
End

Handover Optimization Outline Flow 1
Flow 1
1
The serving cell

receives the
No measurement
report?
Yes
The neighbor
No relation is not
configured?
The test sites
are properly
The admission control
parameters and
covered?
Troubleshoot the Yes
target cell, replace transmission facilities of
the UE, and perform Yes the target cell are Yes
the test again improperly configured,
and the target cell and
the UE operator There is UL
Optimize the
improperly? interference to
neighbor cells
the cell?
No No
Yes
Optimize the radio

Check and
coverage and
eliminate the
handover
interference
parameters
Report the symptoms of the

problem, and help check The exception
No
whether there are any is resolved?
hidden UE or device faults
Yes
End

2
Flow 2
The test sites are

properly covered?
Yes
There is UL
interference with
No the cell?
Yes
Check and eliminate

the interference
1. Check whether the eNB
and UE operate properly.
2. Optimize the radio
coverage and handover
parameters. Report the symptoms
of the problem, and
The exception is
Yes help check whether
resolved?
there are any hidden
UE or device faults
Yes
End

Flow
33
The UE or eNB is
faulty?
No
If the eNB is faulty,
Optimize the radio coverage
troubleshoot it; if the
and handover parameters,
UE is faulty, replace
and check the access
it, and perform the
parameters of the target cell
test again
Report the symptoms

of the problem, and
The exception is
No help check whether
resolved?
there are any hidden
UE or device faults
Yes
End

Common Factors Affecting a Handover
Handover parameters that affect MR reporting, for example,

handovertype, a3-offset, and hysteresis
Accuracy of neighboring cell configuration that affects handover
decision making
Network load that determines the sufficiency of available
network resources for handover preparation
Network topology and coverage that determines whether a
handover can be executed properly and successfully
During handover optimization, when neighboring cells operate properly and

network resources are sufficient, the handover parameters and radio
coverage of these cells are overlapped, and three handover problems may
occur: Too Early Handover, Too Late Handover, and Ping-Pong Handover.

Too Early Handover
A Too Early Handover is the one initiated by the source eNB

when the signal of the neighboring cell is not strong or stable
enough for the handover. It includes the following situations:
After receiving a Handover Command message from the source cell, the UE
fails to be handed over to a target cell due to poor signal conditions of the
target cell, and it attempts to re-establish a radio link connection in the
source cell. In this situation, a handover failure occurs because the UE fails to
perform random access or send a MSG3 message to the target cell. The UE
then initiates an RRC connection re-establishment attempt in the source cell.
A DL out-of-sync occurs shortly after a successful handover of the UE from
the source cell to a target cell. The UE then attempts to re-establish a radio
link connection in the source cell.
A handover to a cell other than the target cell occurs shortly (within 5 s) after
a successful handover of the UE from the source cell to a target cell.

Too Late Handover
The Too Late Handover problem occurs frequently in field tests.

It includes the following situations:
Due to poor signal conditions of the source cell (i.e. the value of SINR is lower
than -3 that causes the probability of failure in sending a Handover
Command message), the UE fails to receive a Handover Command message,
or the random access procedure fails after the UE receives a Handover
Command message. The UE then attempts to re-establish a radio link
connection to a target cell, which can complete successfully because the
context of the UE has be established in the target cell.
A DL out-of-sync occurs due to deterioration of the signal quality of the
source cell before the UE sends a Measurement Report message. The UE
then attempts to re-establish a radio link connection to a target cell, which
will be rejected because the context of the UE has not be established in the
target cell.

Ping-Pong Handover
The UE is handed over from the source cell A to the target cell B,
and within a predefined limited time it is handed over back to A.
The event occurs more than once, which can be easily observed
by analyzing the handover signaling procedure, i.e. check
whether the duration between two handovers in and out of the
same cell is too short, generally within 1 s.

Contents
Overview
Handover Procedures
Solutions
A3
A3 Offset
A3-Offset
Entering condition for Event A3: Mn Ofn Ocn Hys Ms Ofs Ocs Off
Leaving condition for Event A3: Mn Ofn Ocn Hys Ms Ofs Ocs Off
The Off component refers to a3-Offset.
The default value is 3 dB.
In practical use, this parameter is suggested to be set to 2, 3, or 4 dB. A
greater or smaller value is not recommended, to prevent too early handover
or too many handovers.
This parameter is applicable to all neighboring cells of a cell.

A3
Time to Trigger
TimeToTrigger (TTT)
TTT is the time period after which a UE initiates the measurement reporting
procedure when a neighboring cell has a stronger signal than the serving cell,
to avoid ping-pong handovers.
Type: Enumerated
Range: 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024, 1280, 2560,
and 5120)
The default value is 320 ms.
You can set TTT to a greater value to delay the timings of measurement
reporting and reduce the number of handovers.
In most cases, it is recommended to set TTT to 256, 320, 480, 512, or 640 ms
to avoid too many or untimely handovers.

A3
Hysteresis
Hysteresis
This parameter is used to adjust the thresholds for a UE to enter and leave
Event A3 and determine how long the UE stays in this event.
The default value is 0.

If ReportOnLeave is not enabled, it is recommended to set this parameter to
0.

A3
ReportOnLeave
ReportOnLeave
This parameter indicates whether or not the UE shall initiate the
measurement reporting procedure when the leaving condition for Event A3 is
met.
Leaving condition:
Mn Ofn Ocn Hys Ms Ofs Ocs Off

The default value is False (not initiate the measurement reporting procedure).

A3
cellIndividualOffset (CIO)
Cell Individual Offset

Entering condition for Event A3:
Mn Ofn Ocn Hys Ms Ofs Ocs Off

CIO is the Ocn in the above formula.
Type: Enumerated
Range: -24, -22, -20, -18, -16, -14, -12, -10, -8, -6, -5, -4, -3, -2, -1, 0, 1, 2,
3, 4, 5, 6, 8, 10, 12, 14, 16, 18, 20, 22, and 24
Unit: dB
To accelerate the handover from the serving cell to a neighboring cell (i.e.
lower the handover threshold), you can set CIO of the neighboring cell to a
greater value (1 to 3 dB). (corner and deep fading)

A3
Layer 3 filtering
Layer 3 filtering (filterCoefficent)

The measurement result reported by a UE is filtered by layer 3.
Mn: the latest received measurement result from the physical layer
Fn: the updated filtered measurement result, which is used for evaluation of
reporting criteria or for measurement reporting
a = 1/2(k/4), where k is the filterCoefficient in the system.
Type: Enumerated
Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, and 19

A3
Layer 3 filtering
Layer 3 filtering (filterCoefficent)

If k is set to 0, no layer 3 filtering is
applicable.
The default value of k is 4.
It is recommended to filterCoefficent
to a smaller value in some fast fading
scenarios, for example, when a UE
moves to a corner or passes through
a shadow area.

A3
ReportInterval and reportAmount
ReportInterval and reportAmount

Event triggering: ReportInterval is applicable if the UE performs periodic
reporting (i.e. when reportAmount exceeds 1).
Periodic reporting: ReportInterval is set to the interval between periodic
reports.
ReportInterval:
Type: Enumerated
Range: 120, 240, 480, 640, 1024, 2048, 5120, 10240, 60000, 360000, 720000,
1800000, and 3600000
Unit: ms
ReportAmount:
Type: Enumerated
Range: 1, 2, 4, 8, 16, 32, 64, and Infinity
It is recommended to set ReportInterval to 480 ms, and reportAmount to 4.

A3
T304
T304
Timer for successful completion of a handover
Type: Enumerated
Range: 50, 100, 150, 200, 500, 1000, and 2000
Unit: ms
The default value is 1,000 ms.

Contents
Overview
Handover Procedures
Solutions
Handover Exception Due to Lack of Neighbor Relation
Configurations Multiple Measurement Reports
Problem Description
and Analysis:
In a drive test, an exception as shown
in the right figure occurred. The PCI of
the target cell in the previous three
measurement reports was 28 (the same
PCI with slightly different RSRP values).
However, two cells (PCI 28 and PCI 19)
appeared in the 4th measurement
report, and the RSRP of PCI 28 was 3
dB higher than that of PCI 19. The UE
then received a Handover Command
(RRCConnectionReconfiguration) Previous Three
Measurement Reports
message (see Figure 4-4), where
4th Measurement Report
PhysCellId was set to 19 rather than 28.
This indicates that PCI 28 was not
configured on the serving cell of the
UE.

Handover Exception Due to Non-Configuration of a
Neighbor Relation No Response After the UE Sends
a Measurement Report
In a drive test, the UE did not receive
a Handover Command message after
sending a Measurement Report,
resulting in radio link failure and RRC
connection re-establishment.
Whether there are any neighbor cells
not configured can be checked in the
OMC or on the eNB. Neighbor cell
information can be retrieved in the
measurement report on the source
cell.
Solution:
Configure the neighbor relation.

Untimely Handover
Problem Description and Analysis:
Problem Description
The value of SINR around building Guoxiang in Jinhu was very low. The test
log viewed in the CXA shows that the UE entering in this area was connected
to the network still through PCI 160 for building Jinqiao, instead of being
handed over to PCI 179 for Guoxiang.

Untimely Handover
Analysis
The neighbor relation between PCI 160 and PCI 179 has already been configured.
Both the handover threshold A3-Offset and Hysteresis were properly configured, and
their values were set to 1.5 dB and 1.5 dB, respectively.
The problem lied in the UE's untimely handover to PCI 179. It remained camping on PCI
160, causing SINR to deteriorate with the decrease of RSRP of PCI 160.
One solution is to modify A3-Offset and Hysteresis to change the handover threshold,
but the modification also affects handovers on other cells of the same eNB. Therefore, it
is recommended to modify CIO of PCI 179.
Solution:
CIO is the Ocn in the aforementioned
formula, and is set to 0 by default. To
accelerate the handover from PCI 160
to PCI 179, set CIO to 2.

Handover Failure Due to Expiration of Timer
TS1RELOCprep
The statistics made in the OMC shows that the weekly success rate of outgoing intra-
frequency handovers over the S1 interface between eNBs was 98.64% on average. The
number of times that timer TS1RELOCprep (the maximum time for the Handover Command
in the source eNB) expired accounted for 0.43% of the total number of outgoing handovers,
much higher than the same indicator (0.05%) in other offices.
Troubleshooting of the cell where the problem was prominent shows that there were
hundreds of times that an outgoing handover preparation failed due to timer TS1RELOCprep
expiry in the cell every day, resulting in about a 2.5% lowered success rate of outgoing intra-
frequency handovers over the S1 interface between eNBs.
To exclude the impact of transmission congestion, the corresponding timer TS1RELOCprep
(currently 2,000 ms) was modified to 5,000 ms, 8,000 ms, and 500 ms. The problem still
existed, indicating that it has little to do with transmission.
Source cell signaling trace shows that the source eNB did not receive a corresponding
Handover Command message after sending a Handover Required message to the CN for the
first time.

Handover Failure Due to Expiration of Timer
TS1RELOCprep
Signaling trace in the OMC shows that the CN
did not respond to the first Handover Required
message, but responded properly to the next
Handover Required message.
The most probable cause: When the source
eNB is proceeding the TAU part of the first
handover procedure, another handover is
initiated. Because the CN does not complete
handling the first TAU, it does not respond to the
second Handover Required message.
Further analysis shows that the MME (in the CN)
mandated authentication in every TAU procedure,
leading to a long delay of the procedure (above
400 ms).
Solution:
1. Modify the authentication mode in the TAU
procedure from "mandatory" to "determined by
the system" in the MME to shorten the TAU
delay.
2. Disable GUTI reallocation in the TAU
procedure during an intra-office handover, so
that the MME does not need to wait for the
TAU Complete message from the UE.
Handover Failure Due to a Duplicated PCI
Handover exceptions occurred for days in a row in telecom site 301844_50, with a high
handover failure rate. According to the OMC, failures took place in the handover execution
part due to RRC connection re-establishment at the eNB side or other causes.
The analysis of UE handover data under the coverage of cell 301844_50 shows that the handover
procedure operated properly. The UE indicated the PCI of the target cell as 204 and signal
strength as -89 dBm in a Measurement Report message.
According to the cell ID carried in the Handover Required message and the PCI carried in the
Measurement Report, the target site was cell 301922_49, which had a normal neighbor relation
with cell 301844_50.
In the Handover Execution part, the source eNB received a Deactivate Bearer Request message
from the MME, indicating the release of the UE's EPS bearer context. The cause carried in the
message shows that the handover failed and the MME released the EPS bearers of the UE.
Handover Failure Due to a Duplicated PCI
The possible reason is duplication of PCI. After the PCI of the target cell
301922_49 was modified to 501 (reserved), signaling analysis shows that the PCI
carried in the Measurement Report message was still 204. This indicates that the
PCI of another cell other than cell 301922_49 is 204.
The PCI list shows that the PCI of cell 301898_49 is also 204.
Solution:
1. Modify the PCI of the target
cell (301922_49 in this case);
2. Plan PCIs to make them
unique for each cell.

Handover Failure Due to UL Out-Of-Sync
In a drive test, when the UE moved into the blue frame in the
following figure, it initiated an RRC connection re-establishment
request, but the request was rejected.

Layer-3 signaling analysis shows

that the UE sent two Measurement
Report messages before sending an
RRC Connection Reestablishment
Request message, but did not
receive a Handover Command
message, leading to UL out-of-sync
and re-establishment request
rejection.
The diagnosis signaling shows that
the UE had already sent a
Scheduling Request (SR) message
for scheduling before sending a
Measurement Report message, but
did not receive any feedback
information on the PDCCH, i.e. the
SR request failed.

After sending the SR request for

the maximum number of times
allowed, the UE initiated random
access in the source cell. Analysis
of the MAC RACH Trigger message
shows that the cause for random
access is UL data arrival, meaning
that random access was initiated
to resume the uplink connection
after the SR request failed and the
Measurement Report message was
not successfully sent.
The UE did not receive any RAR
after sending the MSG1 messages
throughout the random access
procedure.

After sending the MSG1

message for the maximum
number of times allowed, i.e.
the UE failed to resume the
uplink connection in the
source cell, the UE initiated
the RRC connection re-
establishment procedure with
the cause being Radio link
failure.
Cell reselection is required in
this procedure. However, the
selected cell lacked the bearer
context of the UE, resulting in
re-establishment request
rejection and call dropping.

UL data arrival being the cause for random access

usually appears when the signal strength of the source
cell is weak. To solve this, the UE can be handed over
to a cell with good signal in advance when located in a
handover region.
The RSRP changes at the point of failure shows that
the signal strength of the source cell plunged in a very
short time, while the signal strength of the
neighboring cells rose sharply. As such, adjustment of
the CIO of the cell does not work well, and reduction
of the current value of the TimeToTrigger parameter is
a better option.
Solution:
Modify the TimeToTrigger parameter from currently

320 ms to 256 ms to shorten the decision time for
entering Event A3. Tests for several times after the
modification show that the problem is solved.

06 FO - NO2004 FDD LTE Handover Optimization 60P PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

06 FO - NO2004 FDD LTE Handover Optimization 60P PDF

Caricato da

Copyright:

Formati disponibili

Handover Optimization in LTE

What is a handover for?

ZTE Corporation. All rights reserved

Handovers in LTE can be classified in the following dimensions:

Whether to change the network Intra TD-LTE Handover

ZTE Corporation. All rights reserved

A handover involves the following three steps:

Handover Handover Handover

ZTE Corporation. All rights reserved

The UE performs cell measurements and reports the

ZTE Corporation. All rights reserved

The measurement procedure includes the following three steps:

ZTE Corporation. All rights reserved

Event A1 Serving becomes better than threshold (serving > threshold):

ZTE Corporation. All rights reserved

Event A3 is commonly used in intra-frequency handovers. Event

ZTE Corporation. All rights reserved

ZTE Corporation. All rights reserved

A UE can perform measurements in either RRC_IDLE or

A UE can perform the following types of measurements:

UE measurements includes RSRP and RSRQ.

ZTE Corporation. All rights reserved

When a reporting criterion is met, the UE sends a Measurement Report

ZTE Corporation. All rights reserved

Involves HO decision made by the source eNB and resources

ZTE Corporation. All rights reserved

The RRCConnectionReconfiguration message is used to modify an RRC

ZTE Corporation. All rights reserved

ZTE Corporation. All rights reserved

Before the handover

X2 Perform admission control and

X2 10 Path Switch Rrquest ACK

ZTE Corporation. All rights reserved

Before the handover UE eNB1 eNB2 MME

11 RRC Connection Reconfiguration Complete

ZTE Corporation. All rights reserved

ZTE Corporation. All rights reserved

ZTE Corporation. All rights reserved

ZTE Corporation. All rights reserved

ZTE Corporation. All rights reserved

The UE accesses the target cell using the configuration

ZTE Corporation. All rights reserved

Because the handovers specified in this release are non-

ZTE Corporation. All rights reserved

ZTE Corporation. All rights reserved

Handover Optimization Outline

troubleshoot them, and then make

Exceptions for a handover procedure may 22

Whether the UE successfully receives an MSG2

ZTE Corporation. All rights reserved

The serving cell

Optimize the radio

Report the symptoms of the

ZTE Corporation. All rights reserved

The test sites are

Check and eliminate

ZTE Corporation. All rights reserved

Report the symptoms

ZTE Corporation. All rights reserved

Handover parameters that affect MR reporting, for example,

During handover optimization, when neighboring cells operate properly and

ZTE Corporation. All rights reserved

A Too Early Handover is the one initiated by the source eNB