Guide To TD LTE Handover Problem Analysis

Guide to TD-LTE Handover
Problem Analysis
Contents
 Handover Procedure Description

 Concept of Handover Optimization
 Summary of Handover-Related Parameters
 Handover Optimization FAQs and Cases
内部资料妥善保管▲
Handover Procedure Description

Measurement Control is usually brought in the “RRC Connection
Reconfiguration”message for the random access procedure or last handover process.
Measurement Report:The UE reports the cells which RSRP reach the handover
threshold according the measurement control information of the current cell.
UE Source eNB
HO Request
1. RRCConnection
After receiving a Measurement Report, Source eNodeB applies to Target eNodeB for Reconfiguration
resources and configuration information . (MeasurementControl)
HO Request Ack Packet data Packet data
Target eNodeB feeds back the information received by the UE and other configuration
information to Source eNodeB. UL allocation（PDCCH）
RRC Connection Reconfiguration
Source eNodeB transfers the information received by Target eNodeB and configuration 2. Measurement Report
information to the UE and informs the UE that Target eNodeB is ready for UE access. The
RRC Connection Reconfiguration message contains Measurement Control.
SN Status Transfer
Source eNodeB transfers the cache of UE services to Target eNodeB.
Random Access Preamble 3. HO Request
After receiving an RRC Connection Reconfiguration (handover command) in Step 5, the
UE gets connected to the eNodeB by using the information in the reconfiguration
message.
Random Access Response
Target eNodeB sends ”RRC connection reconfiguration complete” to responds the UE 4. HO Request Ack
access. When the UE receives this command, the access process is complete. 5. RRC Connection Reconfiguration
Afterwards, the UE sends “RRC Connection Reconfiguration Complete” on the RRC layer (HO Command)
(Step 9).
RRC Connect Reconfiguration complete （ HO Confirm ）
Deliver buffered
The UE reports an RRC Connection Reconfiguration Complete. The handover is packets to T_eNB
complete.
Release Resource
6. SN Status Transfe
After the UE successfully accesses to Target eNodeB, Target eNodeB informs Source
Bu
eNodeB to delete the context information of UE. fr
7. Random Access Preamble
8. Random Access Response

Handover categories
 Intra-site handover
 X2 interface handover
 S1 interface handover

Handover Categories—Intra-site Handover
UE eNB
Intra-site handover
procedure need not to apply Measurement Report
to the core network for RRC Connection Reconfiguration

changing the data (HO Command)
transmission route.
RRC Connection Reconfiguration
Complete(HO Confirm)
MSG1
(Random Access Preamble)
RAR
(Random Access Response)

Handover Categories—X2 Interface Handover
Neighboring cells attributable to different eNBs, UE Source eNB Target eNB EPC
and eNBs has been established X2 port link.

Measurement Report
As shown in the figure on the right:
 After receiving a Measurement Report, X2AP HandoverRequest
Source eNodeB sends a X2AP Handover

X2AP
Request to Target eNodeB through X2 HandoverRequestAcknowledge
interface (Step 3) . Target eNodeB feeds back

RRCConnectionReconfiguration
by returning a X2AP Handover Request (HO Command)
X2AP SNStatusTransfer
Acknowledge. After receiving the feedback
(Step 4), Source eNodeB sends a RRC RRCConnectionReconfigurationComplete
(HO Confirm)
Connection Reconfiguration to the UE and
sends a SNStatus Transfer containing package MSG1
cache and package cache number information
to Target eNodeB. RAR
(Random Access Response)
 After the UE accesses the target eNodeB,
S1AP PathSwitchRequest
Target eNodeB sends a Path Switch Request
to the core network to inform the network to S1AP
PathSwitchRequestAcknowledge
transfer the UE service to Target eNodeB. The X2AP UEContextRelease
priority of X2 interface handover is higher than
that of X2 interface handover.

Handover Categories—S1 Interface Handover
UE Source eNB EPC Target eNB
Neighboring cells attributable to
the different eNBs, but did not Measurement Report
establish the X2 port link. S1AP HandoverRequest

S1AP HandoverRequest
The procedure of S1 interface S1AP

HandoverRequestAcknowledge
handover is almost the same as S1AP

HandoverRequestAcknowledge
the procedure of X2 interface

RrcConnectionReconfiguration
(HO Command)
S1AP_EnbStatusTransferMsg
handover, except the interaction
RrcConnectionReconfigurationComplete
signaling is transferred between (HO Confirm)
eNodeBs through the S1 MSG1

interface of the core network RAR
which has a longer delay than (Random Access Response)
that of X2 interface. S1AP MMEStatusTransfer
S1AP HandoverNotify
S1AP
UEContextReleaseCommand
S1AP
UEContextReleaseComplete

UE Measurement Mechanism
 When the terminal

measurement results satisfy
the formula conditions and Measured amount
the state continued for a

period of time,UE reports a Neighbor cell
Serving cell
Measurement Report
The report meets
 Mn+Ofn+Ocn- the conditions
Hys>Ms+Ofs+Ocs+Off
 the length of time:Time to
Trigger Time

Foreground Signaling Resolution

Foreground Signaling Resolution—Measurement Control
 Measurement control
information is contained in
reconfiguration messages
that are generally sent for
initial access and handover
commands.
 Measurement control
information includes
neighboring cell list, event
judgment threshold, delay
and reporting interval.

Foreground Signaling Resolution—Measurement Control
 Measurement Report
reports to all cells that meet
event trigger conditions.

Foreground Signaling Resolution—Handover Command
Handover Procedure Description Foreground

Signaling Resolution-- MSG1
 UE accesses the target

eNodeB by using the access
configuration carried in
handover commands sent by
the source eNodeB.

Foreground Signaling Resolution--eNodeB Returning an
RAR Message

Foreground Signaling Resolution—UE Feeding Back a
Reconfiguration Complete Message
 The reconfiguration complete

message is already
packetized when UE
receives a handover
command. Random access to
the target eNodeB can be
deemed as access initiated
by the reconfiguration
complete message contained
in MSG3.
Contents

Concept of Handover Optimization

Measurement report
To analyze abnormal processes, first

check eNodeB, transmission and UE No
Check whether
the handover command is
received.
statuses. If there are problems, solve Procedure 1

Yes
them before analysis. The analysis of

abnormal handover process include:
Check whether
No the MSG1 is successfully
sent.
Procedure 2
 Check whether the UE receives a handover Yes
command after sending a measurement report No

Check whether the
RAR is received.
(procedure 1).
Procedure 3
Yes
 Check whether the UE sends a MSG1 to the
target eNodeB after receiving a reconfiguration The delivery of reconfiguration
is complete.
(MSG3)
command (procedure 2).
 Check whether the UE receives a MSG2 after
sending the MSG1 (procedure 3). End
Procedure 1 Procedure 1
Check whether
the serving cell has
received the measurement
No report.
Yes
Check whether
there is any cell not being
No configured as a
neighbor.
Check whether
Check the test points are
whether the cell properly covered.
state, admission
Resolve the cell exceptions and parameters, and Yes
transmission problems and Yes transmission are proper
replace the UE for another test. and whether the UE Yes
works properly.
Check whether there is

interference with the cell Optimize the neighbor cells.
uplink.
No
No Yes
Check the optimization

Check and resolve the
coverage and handover
interference.
parameters.
Report the fault

symptoms and check Check whether
whether the UE or No the problem is resolved
equipment has any after the optimization.
potential fault.
Yes
End
Procedure 2
Procedure 2
Check whether
the test points are properly
covered.
Yes
Check whether
there is interference with
No the cell uplink.
Yes
Check and resolve the

interference.
1. Check whether the
eNodeB and UE work
properly.
2. Check the optimization
coverage and handover Report the fault
parameters. Check whether symptoms and check
the problem is resolved No whether the UE or
after the optimization. equipment has any
potential fault.
Yes
End
Procedure 3
Procedure 3
Check whether the

eNodeB and the UE are
abnormal.
No
If the fault lies with the

Check the optimization
eNodeB, remove the eNodeB
coverage, handover
problems; if the fault lies
parameters and target cell
with the UE, replace the UE
access parameters.
to proceed with the test.
Report the fault symptoms

Check whether the and check whether the UE or
problem is resolved No
after the optimization. equipment has any potential
fault.
Yes
End
Contents

Summary of Handover-Related Parameters
Parameter Name Value Range Unit Adjustment Step Length
 问题案例
Cell-specific reference signals
-60~50 dBm 0.1
power
Default Value Transfer Path Scope Source of Parameter
12 ENB->UE Cell 3GPP
Configuration path
OMCR setting interface: Serving Cell Configuration>Base Information>Cell-specific reference signals
power

Adjustment Step
Parameter Name Value Range Unit
Length
The Offset
Between PDSCH
EPRE and Cell-
-6, -4.77, -3, -1.77, 0, 1, 2,
specific RS dB
3
EPRE
(P_A_DTCH) of
center user
Source of
Default Value Transfer Path Scope
Parameter
0 ENB->UE Cell 3GPP
Configuration path
OMCR setting interface: Serving Cell Configuration>MAC ALG C >The offset Between
PDSCH EPRE and Cell-specifc RS EPRE(P_A_DTCH) of centre user
Adjustment Step
Length
Sel_Qrxlevmin -140~-44 dBm 2
-128dBm ENB->UE Cell 3GPP
Configuration path
OMCR setting interface: Serving Cell Configuration>Cell Selection and Reselection >Sel_Qrxlevmin

Adjustment Step
Length
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15,

Filter Coefficient for RSRP
17, 19
Configuration path
OMCR setting interface: Serving Cell Configuration >Parameters of Measurement Configuration > Filter
Coefficient for RSRP

Adjustment Step
Length
Event Identity A1, A2, A3,A4,A5
Events with measure
ment quantity of RSR
P: A1, A2, A3, A4
and A5
Cycles with
measurement
quantity of RSRP: -
Events with
measurement ENB->UE Cell 3GPP
quantity of RSRQ:
A1, A2, A3,A4 and
A5
Cycles with
measurement
quantity of RSRQ: -
Configuration path
OMCR setting interface: Base Station Radio Resource Management>Measurement Configuration
>IntraFreq Measurement for Handover> Event Identity

Adjustment Step
Length
Cell individual offset -24 ～ 24 dB 1
0 ENB->UE CELL 3GPP
Configuration path
OMCR setting interface ； Serving Cell Configuration>ENodeB Neighbouring Relation > Cell
individual offset

Parameter Adjustment Step
Value Range Unit
Name Length
0, 40, 64, 80, 100, 128,

160, 256, 320, 480, 512,
Time to Trigger ms
640, 1024, 1280, 2560,
5120
Source of
Default Value Transfer Path Scope
Parameter
256 ENB->UE eNb 3GPP
Configuration path
OMCR setting interface: Base Station Radio Resource Management>Measurement

Configuration >IntraFreq Measurement for Handover> Time to Trigger

Parameter
Value Range Unit Adjustment Step Length
Name
Hysteresis 0, …, 15 dB 0.5
0 ENB->UE Cell 3GPP
Configuration path
OMCR setting interface: Base Station Radio Resource Management>Measurement Configuration

>IntraFreq Measurement for Handover> Hysteresis

Amount of Reporting
1, 2, 4, 8, 16, 32, 64, Infinity
for event
1 ENB->UE Cell 3GPP
Configuration path
OMCR setting interface ： Base Station Radio Resource Management>Measurement Configuration

>IntraFreq Measurement for Handover> Amount of Reporting for event

Parameter
Value Range Unit Adjustment Step Length
Name
120, 240, 480, 640, 1024,

Reporting
2048, 5120, 10240, 60000,
Interval for ms
360000, 720000, 1800000,
Periodical
3600000
Default
Transfer Path Scope Source of Parameter
Value
Configuration path

>IntraFreq Measurement for Handover> Reporting Interval for Periodical

Maximum Cell Number

1, 2, …, 8
reported
3 ENB->UE Cell 3GPP
Configuration path

>IntraFreq Measurement for Handover> Maximum Cell Number reported

Adjustment Step
Length
Power Ramping Step

[0, 6] dB 2
for PRACH
2 ENB->UE Cell 3GPP
Configuration path

0: 3, 1: 4, 2: 5, 3: 6, 4: 7, 5: 8, 6:
Max Transmit Number 10
for Prach
7: 20, 8: 50, 9: 100, 10: 200
5: 8 ENB->UE Cell 3GPP
Configuration path

Initial Power for

[-120, -90] dBm 2
Preamble of Prach
-100 ENB->UE Cell 3GPP
Configuration path
Contents

Handover Optimization FAQs and Cases
Abnormalities Caused by Missing Configuration of Neighbor Cells
 Multiple measurement reports
 No response to measurement report


Abnormalities Caused by Missing Configuration of
Neighbor Cells-- Multiple Measurement Reports
 In a drive test shown in the figures
on the right, the first three
measurement reports target
PCI=28 (the same PCI, slightly
different RSRPs). The fourth
measurement report targets
PCI=28 and 19. The measurement
value of PCI=28 is 3dB higher than
that of PCI=19.UE receives a
handover command.
 The handover command carrying
the PCI of the target cell is not 28
but 19, so PCI=28 is presumed to
be a missing configured neighbor
cell.

Neighbor Cells-- No response to measurement report
 The results of a drive

test shows the UE does
not receive a handover
command after sending
a measurement report.
The UE initiates a
reestablishment
procedure after the radio
link fails.

Neighbor Cells-- Confirmation of Missing Configured
Neighbor Cells
 You can confirm whether the

neighbor cells are configured by
checking eNodeB configurations
on the background.
 You can also check the neighbor

cell information contained in
measurement control information
sent by the source eNodeB.

Difficult Access to Target eNodeB Due to Uplink
Interferences-Problem Phenomenon
Total KPI Type Correspond Attempt Ratio
Random Access Success[%]
1 207 215 96.28 %
2 RRC Connect Success[%] 38 41 92.68 %
Initial Access Success[%]
3 0 0 0.00 %
E-RAB Connect Success[%]
4 44 44 100.00 %
5
6
Call Drop[%]
HO Success[%]
26
106
44
130
59.09 %
81.54 %
 The test of Fukuoka
network indexes shows
access failure frequently
occurs and call dropping
phenomenon appears
after handover.
Accesses sometimes
succeed and sometimes
fail. There is no rule
about the phenomenon.

Interferences--Problem Analysis
To analyze the problem, we select some cells and do tests at fixed points. We find the UE
cannot connect to the network and the status indicator on the Qualcomm UE sometimes
blinks red (abnormal) and sometimes blinks green. Our self-developed UE also cannot
connect to the network.
Qualcomm QXDM interface Self-developed UE LMT interface


Interferences-Problem Analysis
We check the call drop procedure and reestablishment procedure on Qualcomm
QCAT, the Qualcomm analysis software.
UE triggers MSG1 because DCI0 does not arrive at “rach reason=UL_DATA” and
the SR transmission attempts reach the maximum. RRC reestablishment is
triggered after the MSG1 fails to be sent to the eNodeB in eight transmission
attempts.
To verify whether it is a regular problem, we carry out DT tests near the
sites. Test areas are shown in the following figure:
In the area enclosed by
blue ellipse, the success
rate of accesses and
handovers is relatively
high.
Some sites in the area
enclosed by red ellipse are
difficult for UE to access.
RRC reestablishment fails
in the HO test. Then UE
access fails again after
RRC reestablishment is
once again rejected.

According to the above analysis, it is presumed
that the problem results from uplink data
abnormalities caused by interferences. Currently
Fukuoka site adopts GC office, namely, one BBU
with several RRUs forming a site. All sites in
Japan are omnidirectional sites. The site
distribution is shown in the figure: Call drops
concentrate in the area enclosed by red ellipse.
Currently tests are performed only in Ref area
(the area enclosed in blue ellipse) .We found call
drops have a certain relationship with BBUID.
Non-call drop areas belong to BBUID=400010
and call drop areas belong to BBUID=400011
and 400012, so we doubted there are some
problems in the correlation of BBUID=400010,
400011 and 400012.

 We checked the equipment alarms on the OMC based on
the previous analysis. We first check the GPS status and
found the GPS at 400011 site is unlocked.
 The sites of 400011 and 400012 concentrates and the
400011 has no GPS lock, which may lead to GPS
interferences in the cells belonging to 400011 and
peripheral cells and uplink access failures. For cells
where UE handover fails, we query the uplink receive
power traced on the MTS, and find that the eNodeB
receive power is too high (normally about -96-99dbm) GPStime RxPow0(dBm) RxPow1 RxPow2 RxPow3 TxDPow0(dBm) TxDPow1 TxDPow2 TxDPow3
2011-11-11 11:02:02:740 -84.6 -81.55 -88.1 -84.13 37.17 37.02 37.78 37.21
and the receive power evaluation is about -80dbm. 2011-11-11 11:02:08:750 -84.6 -81.55 -88.1 -84.13 37.17 37.02 37.78 37.21
2011-11-11 11:02:15:450 -84.18 -81.51 -88.1 -84.13 37.13 37.16 37.78 37.21
 According to the above analysis, the problem is 2011-11-11 11:02:21:350 -84.18 -81.51 -88.1 -84.13 37.13 37.16 37.78 37.21
2011-11-11 11:02:27:340 -84.18 -81.51 -88.1 -84.13 37.13 37.16 37.78 37.21
presumed to occur because GPS out-of-lock of 2011-11-11 11:02:33:960 -84.62 -81.51 -88.1 -84.15 37.3 37.16 37.78 37.11
2011-11-11 11:02:39:950 -84.62 -81.51 -88.1 -84.15 37.3 37.16 37.78 37.11
BBUID=400011 have impacts on other cells. We check 2011-11-11 11:02:46:610 -84.62 -81.53 -80.87 -84.11 37.3 37.21 37.79 36.99
2011-11-11 11:02:52:560 -84.62 -81.53 -80.87 -84.11 37.3 37.21 37.79 36.99
on the background and find the GPS of 400010 and 2011-11-11 11:02:58:570 -84.62 -81.53 -80.87 -84.11 37.3 37.21 37.79 36.99
400012 is normal, but the GPS of 400011 is not powered 2011-11-11
2011-11-11
11:03:05:150
11:03:11:150
-84.62
-84.62
-81.53
-81.53
-80.3
-80.3
-83.41
-83.41
37.3
37.3
37.21
37.21
38.09
38.09
37
37
on by BBU. However, electrical signal are already sent 2011-11-11
2011-11-11
11:03:17:780
11:03:23:750
-84.6
-84.6
-81.53
-81.53
-80.3
-80.3
-83.69
-83.69
37.15
37.15
37.21
37.21
38.09
38.09
37.18
37.18
and have impacts on cells around. Afterwards we carry
out tests by blocking all the cells belonging to 400011
and did tests and found in some cells of 400010, UE
handover also fails. Then we query the uplink receive
power and find there are certain interferences.

Interferences--Solution and Verification
From the analysis of access methods for BBUs in Fukuoka

area connecting to each cell, it can be found that the sites in
Fukuoka area adopt GC office, that is ,a BBU manages all
cells belonging to it and every BBU shares a GPS signal
source. Although the GPS of the site(BBUID=400010) is
already powered on, sometimes GPS out-of-lock occurs and
the cells that near to the site(BBUID=400010) are affected.
Therefore, we block all the cells belonging to the BBUs of
400011 and 400012 and carry out tests, and finally find UE
handover in all the cells belonging to 400010 succeeds. The
problem is solved.
Handover Problems Caused by Complicated
Environments
Characteristics of the TI project network coverage:

 All sites are omnidirectional.
 All sites are densely distributed.
 Radio propagation environment is complex
 1) The engineering parameters cannot be adjusted because TD-
LTE eNodeBs are co-sited with existing PHS sites and using omni-
directional antennas.
 2) The eNodeBs are densely deployed to ensure indoor
coverage.The urban environments environment is complicated,
resulting in preferable RSRP but poor SINRs.The pilot pollution is
particularly serious nearby the intersections.
The focus of our work is to optimize the failure of these business
areas.

Environments — Overall Problem Handling Concept
 Avoid UE handovers at intersections: If a UE must be redirected to

another cell at an intersection, advance or postpone the handover
through adjustment or, if necessary, set the one-way neighbor
relationship. This approach is only used for routes where the KPI
problems cannot be resolved. Radio parameters must be adjusted
flexibly based on the alleviation of effects affecting other proper
cells during the handover optimization.
 Reduce UE handovers brought about by the cross coverage by
means of coverage adjustment. If the adjustment fails, try to avoid
the UE from being redirected. If the problem still persists, add
neighbor cells and adjust the handover parameters.

Environments — Case 1
Normally, the UE moves along the blue line
and hands over from one cell with PCI=336
to another with PCI=83. However, when the
UE moved to the place marked by a red X,
the RSRP of the cell with PCI=4 increased
suddenly and when the UE handed over to
the cell with PCI=4, the RSRP of the cell
with PCI=4 dropped unexpectedly.
Consequently, the call was dropped
because the UE did not receive any
handover command.
To prevent the UE from redirection to cells
with PCI=336 and PCI=83 at the
intersection, we strengthened the RS power
of the cell with PCI=83 to keep the
handover point between cells with PCI=336
and PCI=83 away from the intersection.

Normally, the UE moves along the blue
line and hands over from one cell with
PCI=45 to another with PCI=61.
However, as the intersection was
covered by the cell with PCI=34, the
RSRP of the cell with PCI=34 decreased
unexpectedly when the UE passed
through this intersection. Consequently,
the call was dropped because the UE did
not receive any handover command after
sending a measurement report.
We increased the CIOs of cells with

PCI=34 and PCI=61 with 3 dB, moved the
handover point towards the west, and
redirected the UE to the cell with PCI=61
in advance. As a result, the call drop
caused by rapid signal deterioration in the
cell with PCI=34 was avoided.
Handover Optimization FAQs and Cases 内部资料妥善保管▲

Normally, the UE moves along the blue line and hands over
from one cell with PCI=45 to another with PCI=8. However, the
UE handed over to the cell with PCI=4 at the intersection
marked by a red X, and then the call was dropped when the UE
was switched back to the cell with PCI=45.
 To prevent the UE from redirection to the cell with PCI=4,
we have successively attempted to lower the RS power
of the cell with PCI=4 and adjust the CIOs of cells with
PCI=45 and PCI=4. Nevertheless, the call drop persisted
while the RSRP of the cell with PCI=4 was 17 dB
stronger than that of the cell with PCI=45. We analyzed
the RSRP distribution of cells nearby the intersection,
only to find out that the northbound road was covered by
the cell with PCI=4 and the RSRP of the cell with PCI=7
approximated to that of the cell with PCI=4 near the
intersection.
 A redirection to the cell with PCI=4 can be avoided on
this test route by deleting the one-way neighbor
relationship (from the cell with PCI=45 to the cell with
PCI=4). In this case, the UE moving towards the cell with
the PCI=4 from the intersection can be redirected to the
cell with PCI=7 first, and then to the cell with PCI=4.

Lessons Learnt on Dealing with Call Drops Caused by
UE Out-of-Sync Behaviors — Problem Symptoms
During a test, the re-

establishment of an RRC
connection was denied
when the UE moved to the
location marked with a
blue rectangle.

Lessons Learnt on Dealing with Call Drops Caused by
UE Out-of-Sync Behaviors — Problem Symptoms
According to the check results of
the Layer 3 signaling, the
measurement report was sent twice
before the re-establishment without
receiving any handover command,
which eventually led to the UE out-
of-sync and re-establishment
rejection.
According to the diagnosis

signaling, the UE had sent an SR
before sending the measurement
report, but no scheduling
information was returned by the
PDCCH. Namely, the SR failed.
Handover Optimization FAQs and Cases 内部资料妥善保管▲
The experience to deal with Call Drops Caused by UE

Out-of-Sync Behaviors — Symptom Analysis
When the delivery of SRs reached the upper limit,
the source cell initiated a random access
procedure.Queried the MAC RACH Trigger
signaling,the cause value of the delivery of random
access was “UL data arrival” — namely, the random
access procedure was initiated to restore the uplink
services when both SR and MR delivery failed.
During the entire random access

procedure, no RAR was received
upon each delivery of MSG1 by the
source cell.

Out-of-Sync— Symptom Analysis
When the delivery of MSG1s
reached the upper limit, the
attempt to restore uplink services
in the source UE failed and the
RRC connection was redirected
to the re-establishment
procedure because of a radio link
failure.
The cell with PCI=134 is

reconstructed and has no UE context.
However, re-establishment
required cell selection and the
selected cell had no context of
that UE. Consequently, the re-
establishment was denied and
the call was dropped.

Out-of-Sync Behaviors — Problem Resolution and
Verification
 UL data arrival often occurred in weak fields of the
source cell. This problem can be addressed by
redirecting a UE to another cell with better signal
quality beforehand.
 We checked changes in the RSRP of a trouble spot
only to find out that the signal strength of the source
cell dropped dramatically while that of the neighboring
cell increased sharply in a very short time. In this case,
we shortened the time-to-trigger of the current network
as the adjustment of cell migration produced no
obvious effect.
 We attempted to change the "time to the trigger"

parameter from 320ms to 256ms, the aim is to shorten
A3 judgment time. After the modification, this problem
was resolved on the basis of multiple tests.

Guide To TD LTE Handover Problem Analysis

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Guide To TD LTE Handover Problem Analysis

Загружено:

Авторское право:

Доступные форматы

Guide to TD-LTE Handover

 Handover Procedure Description

Handover Procedure Description

8. Random Access Response

Handover Procedure Description

to the core network for RRC Connection Reconfiguration

Handover Procedure Description

and eNBs has been established X2 port link.

Source eNodeB sends a X2AP Handover

interface (Step 3) . Target eNodeB feeds back

Handover Procedure Description

establish the X2 port link. S1AP HandoverRequest

The procedure of S1 interface S1AP

handover is almost the same as S1AP

the procedure of X2 interface

eNodeBs through the S1 MSG1

that of X2 interface. S1AP MMEStatusTransfer

Handover Procedure Description

 When the terminal

the state continued for a

Handover Procedure Description

Handover Procedure Description

Handover Procedure Description

Handover Procedure Description

Handover Procedure Description Foreground

 UE accesses the target

Handover Procedure Description

Handover Procedure Description

 The reconfiguration complete

 Handover Procedure Description

Concept of Handover Optimization

To analyze abnormal processes, first

statuses. If there are problems, solve Procedure 1

them before analysis. The analysis of

command after sending a measurement report No

Check whether there is

Check the optimization

Report the fault

Check and resolve the

Check whether the

If the fault lies with the

Report the fault symptoms

 Handover Procedure Description

Summary of Handover-Related Parameters

Parameter Name Value Range Unit Adjustment Step Length

Default Value Transfer Path Scope Source of Parameter

12 ENB->UE Cell 3GPP

Summary of Handover-Related Parameters

Summary of Handover-Related Parameters

Sel_Qrxlevmin -140~-44 dBm 2

Default Value Transfer Path Scope Source of Parameter

-128dBm ENB->UE Cell 3GPP

Summary of Handover-Related Parameters

0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15,

Default Value Transfer Path Scope Source of Parameter

13 ENB->UE Cell 3GPP

Summary of Handover-Related Parameters

Summary of Handover-Related Parameters

Cell individual offset -24 ～ 24 dB 1

Default Value Transfer Path Scope Source of Parameter

0 ENB->UE CELL 3GPP

Summary of Handover-Related Parameters

0, 40, 64, 80, 100, 128,