334304193.

xlsx

Problem
Description
Problem Scope
Remarks

Required
Actions
Action 1: Determine the
change trend of
handover failures and
problem scopes and
analyze the causes
recorded in traffic
statistics, and related
KPIs.

Action 2: Check
operation logs, device
faults, alarms, and
external events.

Action 3: Check
parameters.

Prerequisite
None
This action is very important
because it determines the follow-up
troubleshooting direction.
.

None
Pay attention to this action in the
event of sudden deterioration of
KPIs.

None

Action 4: Check for

version differences and None
known issues.

Action 5: Check
network planning and
optimization.

Action 6: Check
interference and RF
channels.

For top cell problems, perform this

action.
For network-wide problems, perform
this action if KPIs do not meet
requirements in newly deployment
and network swapping scenarios.
For top cell problems, perform this
action. Check for interference based
on the analysis results provided by
action 1.

For top cell problems, check top

Action 7: Identify top
users.
UE types and top users. For network-wide problems, check
top UE types.
Perform this action based on the
analysis results provided by action
Action 8: Troubleshoot 1.
EPC faults.
Perform this action for network-wide
problems or top cell problems in the
event of inter-EPC handovers.
Action 9: Check
transmission.

10/22/2016

Perform this action based on the

analysis results provided by action
1.

112

334304193.xlsx

Action 10: Handle

complaints and
replicate problems.

Perform this action for complaints.

For other problems, perform this
action when problems need to be
replicated.

Checklist of Drive test handover issue

Problem
Description

Required Actions

The eNodeB does not

send measurement
control messages to the
UE.

Confirm whether handover-related switches are turned on.

The UE does not report

some types of MR.

Confirm whether the UE supports related types of handover. In the event of inter-frequency handov
the UE supports inter-frequency handovers and whether can operate at this inter-frequency band.

The eNodeB cannot

initiate handover
requests.

Check for missing configurations of neighboring cells.

If the ANR algorithm is activated, check whether the UE supports the ANR function.

Inter-eNodeB handovers Check whether X2 interface configurations are correct and whether X2 interface status is normal.
cannot be performed on
X2 interfaces but only on
S1 interfaces.

The peer eNodeB or

MME returns handover
preparation failures.

Check whether the neighbor relationship on the local eNodeB is correct. Check the parameter setti
eNodeB and EPC.

Check whether both the source and target eNodeBs add the peer cell to the external PLMN list. ADD
In the event of MOCN,
subscribers of secondary EUTRANEXTERNALCELLPLMN
operators cannot be
handed over.

The Path Switch process Check the Path Switch update process.
fails after X2-based
handovers.
Inter-eNodeB X2-based
handovers crossing
UGWs under an MME
fail.

Check whether the target eNodB is configured with the IP paths pointing to the two UGWs.

Inter-eNodeB X2-based
handovers crossing
UGWs under an MME
pool fail.

Check whether the source and target eNodeB are configured with S1 links connecting to the two MME

10/22/2016

212

334304193.xlsx

Probe data shows that

there are many
LTERandomAccess when
the UE are handed over
he target cell or whether the actual PCI of target cells conflicts with the PCI of neighboring cells configured in the neighbor relationshi
to the target cell. Random
accesses fail.

10/22/2016

312

334304193.xlsx

Analysis Purpose

1. Confirm whether the time when KPIs deteriorate matches the time when upgrades or other
operations are performed. If KPIs deteriorate gradually, confirm whether the change trend of
deterioration is related to the service increase.
2. Determine whether the problem is a top cell problem or network-wide problem. If it is a top
cell problem, determine whether it is a top paired cell problem.
3. Categorize handover failures by analyzing traffic statistics.
4. In MOCN scenarios, determine whether the problem occurs for all operators or only for a
specific operator. If it is an operator-specific problem, perform subsequent analysis and handling
according to Required Actions for Operator-specific Call Drop Analysis in MOCN Scenarios.
1. Check operation logs to identify parameter modification and operations that may cause
problems. Then, find out why parameters are modified and take measures to restore modified
parameters.
2. Check whether there are device faults or alarms that may result in handover problems.
3. Check whether there are major holidays when problems occur, and whether EPC upgrades,
network cutover, and networking changes are performed.

DONE

NO

NO

After parameter check, analyze key parameters related to handovers first. If you do not find
possible causes, analyze all parameters.

NO

1. Check whether there are known issues in the current version.

2. For top site problems, check whether there are version differences.

NO

1. Analyze whether handovers fail because of missing configurations of neighboring cells or

incorrect configurations of neighboring cells.
2. Analyze whether handovers fail because of weak coverage and absent of dominant cells.
3. Analyze whether handovers fail because of congestion in target cells.

NO

1. Check whether RF channels are normal.

2. Check whether uplink interference exists.

NO

1. Determine whether problems are caused by one user.

2. Determine whether problems are caused by one type of UEs.
3. Determine whether the cause of problems is UE capability (for example, the UE does not
support inter-frequency handovers).

NO

1. Check whether handovers fail because of EPC faults.

2. Check whether handovers fail because of operations on the EPC (for example upgrades and
configuration modification).

NO

Check whether handovers fail because of transmission faults.

NO

10/22/2016

412

334304193.xlsx

1. Provide the general principles for analyzing complaints.

2. Replicate problems to collect logs.

NO

e test handover issue

Required Actions

DONE

over-related switches are turned on.

NO

UE supports related types of handover. In the event of inter-frequency handovers, check whether
r-frequency handovers and whether can operate at this inter-frequency band.

nfigurations of neighboring cells.

is activated, check whether the UE supports the ANR function.

NO
NO

erface configurations are correct and whether X2 interface status is normal.

NO

ighbor relationship on the local eNodeB is correct. Check the parameter settings on the peer

NO

he source and target eNodeBs add the peer cell to the external PLMN list. ADD
MN

NO

h update process.

NO

rget eNodB is configured with the IP paths pointing to the two UGWs.

NO

urce and target eNodeB are configured with S1 links connecting to the two MMEs in the MME pool.

NO

10/22/2016

512

334304193.xlsx

nflicts with the PCI of neighboring cells configured in the neighbor relationships on the source eNodeB (see
NOAction 5 Checking Networ

10/22/2016

612

334304193.xlsx

Analysis Results

10/22/2016

712

334304193.xlsx

Analysis Results

10/22/2016

812

334304193.xlsx

10/22/2016

912

334304193.xlsx

TOP Site
Issue

Whole
Network Issue

Feedback the time and purpose of parameter modification on network. Is there any special demands for this modification?
Submit drive test log to R&D if the log exits, and submit the UU&X2&S1 signalling trace. The correspondation of eNB time
drive test log time is also required.

10/22/2016

1012

334304193.xlsx

Checklist of Deliverables
Latest configuration files of the top sites
Software version of TOP site.
The type and software version of UE
Engineering parameters of the top sites
One-week traffic statistics of the top sites
Signalling tracing on standard interfaces of the top site (source and target eNodeBs) during busy hours (2 to 3
hours).
Brd logs of main control boards and baseband boards of the top sites.
One-week traffic statistics of entire network
Software version of typical sites, UE information
Latest configuration files of typical sites
Brd logs of typical sites

edback the time and purpose of parameter modification on network. Is there any special demands for this modification?

bmit drive test log to R&D if the log exits, and submit the UU&X2&S1 signalling trace. The correspondation of eNB time and
ve test log time is also required.

10/22/2016

1112

334304193.xlsx

Submit?
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO

10/22/2016

1212