Confidential▲

FDD LTE Call Drop Troubleshooting Guide

CDMA & FDD LTE Product Support Dept.

 Confidential▲

Table of Contents

 Call Establishment and Call Drop

 Cause Analysis
 Troubleshooting Procedure
 Case Study
 Confidential▲

Call Establishment and Call Drop

 NAS and AS
 NAS: Non-Access Stratum
 AS: Access Stratum

2. Idle/ EPC
1. Power-off Attached 3. Activated
Registered Connected

Evolved Mobility Deregistered Registered

Management (EMM)
Evolved Connection
Idle Connected
Management (ECM)
Radio Resource Control
(RRC) Idle Connected Idle Connected
 Confidential▲

Call Establishment and Call Drop

 Connection Release

UE EUTRAN

RRCConnectionRelease

 Call Drop – Definition

 A call will be dropped when an UE exits the RRC_CONNECTED state.

 Confidential▲

Call Establishment and Call Drop

 Call Drop – Common Causes

 1. Connection Reestablishment Reject (Signaling)

(1). The UE sends the rrcConnectionReestablishmentRequest; Cause = otherFailure
message through the UL-CCCH.

(2). The eNodeB returns the rrcConnectionReestablishmentReject message through the
DL-CCCH.

(3). When experiencing a call drop problem, the UE starts to receive the broadcast messa
ge that contains SIB1 through the BCCH-SCH until the UE originates the next call.
 Confidential▲

Call Establishment and Call Drop

 Call Drop – Common Causes

 2. Poor Signal over the Air Interface (Signaling)

Incomplete signaling: Without receiving the Connection Release message, the UE is tran
sitioned from the RRC-CONNECTED state to the RRC-IDLE state.

A typical symptom of this call drop problem: The UE sends the RRCConnectionReestabli
shmentRequest message but does not received the RRCConnectionReestablishment
message, and even the UE does not send the RRCConnectionReestablishmentComplet
e message.
 Confidential▲

Call Establishment and Call Drop

 Call Drop – Common Causes

 3. Other Causes

Narrowly speaking, a call drop problem occurs only when the UE sends the rrc
ConnectionReestablishmentRequest message, that is to say, the RRC conne
ction is broken.


If the RRC connection is reestablished due to a handover or any other problem,
the RRC reestablishment is usually successful. In a real project, you need to p
ay special attention to such problem. Whenever necessary, you must reach an
agreement with the customer on whether regarding such a problem as a call dr
op problem.
 Confidential▲

Table of Contents

 Call Establishment and Call Drop

 Cause Analysis
 Troubleshooting Procedure
 Case Study
 Confidential▲

Cause Analysis 1 – Poor Coverage

 Problem Symptoms
Poor
Coverage

20

10
Serving Ce
0 ll CINR

-10 Drop

-70

-90
Serving
C ell RSR
-110 P

-130
 Confidential▲

Cause Analysis 1 – Poor Coverage

 Cause Analysis: Analyzing the Drive Test Data
 Step 1. Collect the drive test data.
 Step 2. Analyze the drive test data using ZXPOS CNA or TEMS Dis
covery.
 Step 3. Check whether there is any of the following symptoms thro
ugh the geographical chart or Table View when a call drop problem
occurs:

Low RSRP (serving cell): RSRP < -105dBm

Low CINR (serving cell): CINR < 0dB

Poor signal strength (neighboring cell): Signal strength > -105d
Bm
 Confidential▲

Cause Analysis 1 – Poor Coverage

 Optimization Solutions
 1. Determine which sectors are serving current poor coverage area
s.
 2. Determine the most suitable sectors based on the network topol
ogy and radio environment, and strengthen the coverage of this ar
ea.

Troubleshoot the hardware faults from the baseband, RF, and antenna system,
VSWR alarms.

Increase the RS power of the serving cell.

Increase the power of the serving sector.

Adjust the antenna tilt of the serving sector.

Adjust the antenna azimuth of the serving sector.

Add some sites plus adjusting the antenna tilt and azimuth of the surrounding b
ase stations.
 3. Implement the Coverage & Capacity Optimization (SON-CCO) f
unction (pending).
 Confidential▲

Cause Analysis 2 – Handover Failure

 Problem Symptoms
 Before a call drop problem occurs, the UE has ever sent the measurement
report and received the RRCConnectionReconfiguration message from t
he eNodeB.
 The UE sends the rrcConnectionReestablishmentRequest; Cause = h
andoverFailure message immediately when receiving the broadcast mes
sage from the target cell.
 The UE usually sends the rrcConnectionReestablishmentRequest mess
age to the source cell after experiencing a handover failure.
 Confidential▲

Cause Analysis 2 – Handover Failure

 Cause Analysis: Analyzing the Signaling Data
 Obtain the signaling data collected from the drive test.
 Check whether there is any of the following symptoms when a call drop pro
blem occurs:

Before a call drop problem occurs, the UE has ever sent the measurementRep
ort message.

The UE can receive the rrcConnectionReconfiguration message that contain
s the MobilityControlInfo field from the eNodeB.

When handover to the target cell that is carried by the rrcConnectionReconfig
uration message, the UE can receive the systemInformationBlockType1 mes
sage through the BCCH-SCH.

When receiving the systemInformationBlockType1 message, the UE sends th
e rrcConnectionReestablishmentRequest Cause=handoverFailure messag
e.

Usually, the UE can successfully reestablish the connection within 200 ms, and
handover back to the source cell.
 Confidential▲

Cause Analysis 2 – Handover Failure

 Optimization Solutions
 Check whether the neighboring cells are properly configured by comparing the Neig
hbor Cell worksheet of the source cell to the Serving Cell worksheet of the target cel
l.
 Check whether the target cell is normally running.

No bit errors during the transmission

Normal power output

No handover failure due to the cell overload
 Check whether the software versions of both source and target cells are correct.
 Familiarize yourself with common handover failures.

A handover failure occurs because the X2 interface is improperly configured.

A handover failure occurs because traffic load is burdened in a single cell.

A handover failure occurs because the handover success rate is too low in this cell.

A handover failure occurs because a new site is deployed in the surrounding area.

A handover failure occurs because the UE is located at the edges of different MMEs.

A handover failure occurs because the UE is located at the borders of base stations in diffe
rent frequencies.
 Confidential▲

Cause Analysis 3 – Missing Neighbor

 Problem Symptoms
Missing
Neighbor

20

10
Servin
g Cell C R
0 INR N1 CIN
Drop
-10

-70

-90 Serving C
ell RSRP N1 RSRP

-110

-130
 Confidential▲

Cause Analysis 3 – Missing Neighbor

 Cause Analysis ： Analyzing the Signaling Data
 Obtain the signaling data collected from the drive test.
 Check whether there is any of the following symptoms when a call drop problem occ
urs:

Before a call drop problem occurs, the RSRP of the serving cell is continually d
ecreased.

Before a call drop problem occurs, the UE sends the measurementReport mes
sage consecutively. The purpose is to check whether the signals of neighboring
cells are strong enough. The signal of the serving cell becomes poorer and poor
er because no neighboring cell is configured, and eventually this causes a call d
rop problem.

The measurementReport message sent by the UE contains the target neighbo
ring cells that satisfy the A3 or A5 event, depending on system setup.

The system (neighboring cell) message sent by the serving cell does not contai
n the target neighboring cell of the measurementReport message sent by the
UE.

After sending the measurementReport message, the UE does not receive the
rrcConnectionReconfigurationRequest message with a handover instruction
from the eNodeB.
 Confidential▲

Cause Analysis 3 – Missing Neighbor

 Optimization Solutions

 Using the configuration tool or batch-import function in t

he OMC, add the missing neighbor cells to the serving c
ell list prior to the call drop.

 Implement the ANR function to optimize the configuratio

n of neighboring cells. (pending)
 Confidential▲

Cause Analysis 4 - Overshooting

 Problem Symptoms
Overshooting
(Pilot Pollution)

20

10

0
Serving Serving
Cell CINR Cell CINR
-10 Drop Drop N1 CINR

-70

-90
Serving Serving Servin Serving
Cell g
-110 1 RSRP Cell 2 Cell 2 Cell 1
RSRP RSRP RSRP
-130
 Confidential▲

Cause Analysis 4 - Overshooting

 Cause Analysis: Analyzing the Signaling Data
 Obtain the signaling data collected from the drive test.
 Check whether there is any of the following symptoms when a call dro
p problem occurs:

The signals in a coverage area where a call drop problem occurs, s
erving cell, or searchable neighboring cell contains some overshoo
ting signals (overshooting 3 or more layers).

Determine whether the coverage area where a call drop problem o
ccurs is in nature a pilot polluted area, which is served by more tha
n three cells (RSRP > -110 dBm, CINR < 0 dB).

Determine whether any neighboring cell is unconfigured. Check wh
ether the neighboring cell list of the coverage area contains any ov
ershooting cell.
 Confidential▲

Cause Analysis 4 - Overshooting

 Optimization Solutions
 The general principle is: on the condition that the coverage area is
provided with stable and proper signals, try as best as possible to c
ontrol the signals of the overshooting area.

Decreasing the power of the overshooting area

Increasing the antenna downtilt of the overshooting area

By taking the border coverage of the overshooting area as well as the network t
opology into consideration, carefully adjust the antenna azimuth of the overshoo
ting area.

 Pilot Pollution Caused by Overshooting Coverage


Increase the power of the primary sector

Adjust the antenna downtilt of the primary sector

Adjust the antenna azimuth of the primary sector

Control the polluted signals from other areas

 Neighbor Cell Unconfigured: Optimizing neighbor cells

 Confidential▲

Cause Analysis 5 – Equipment Fault

 Problem Symptoms
 Equipment Faults

Handover abnormalities

A call drop problem occurs and can reoccur when a service is p
rocessed at a fixed time or place.

A call drop problem occurs and can reoccur in one or more spe
cific sectors of the eNodeB.

A call drop problem occurs and can reoccur in an inter-MME, int
er-TA, or any other special area.
 Confidential▲

Cause Analysis 5 – Equipment Fault

 Cause Analysis: Analyzing the Drive Test Data and
OMC Statistics Data
 Step 1. Collect the required data.
 Step 2. Analyze the data before and after the call drop problem occurs.
– Radio environment (GE): poor coverage, fast fading, shadowing
– Coverage of the serving cell (RSRP and SINR)
– Neighboring cell configuration and handover statistics
– Signaling flow abnormalities
 Step 3. Eliminate the causes one by one and sum up some helpful principl
es
– Whole or part of a site?
– S1 or X2 interface?
– Affected by any critical operations?
 Confidential▲

Cause Analysis 5 – Equipment Fault

 Optimization Solution
 If a call drop problem is caused by any equipment fault, you need t
o submit it to an R&D engineer.
 When necessary, you must capture the required information for furt
her analyzing the call drop problem, in coordination with the R&D e
ngineer.
 Follow up the problem troubleshooting procedure.
 Eventually, verify that the problem is properly eliminated.
 Confidential▲

Cause Analysis 6 – Interference

 Problem Symptoms (Uplink Interference)
Interference
(Uplink)

20 UE Tx Power
Drop
10 Serving Cell CINR

-10

-70 eNodeB RSSI

-90
Serving Cell RSRP
-110

-130
 Confidential▲

Cause Analysis 6 – Interference

 Problem Symptoms (Downlink Interference)
Interference
(Downlink)

20

10

0
Serving Cell and Neighbor Cell CINR Drop
-10

-70
Serving Cell & Neighbor Cell RSRP
-90

-110

-130
 Confidential▲

Cause Analysis 6 – Interference

 Cause Analysis ： Drive Test Data Analysis + OMC Dynamic Data Analysi
s
 Step 1. Collect the drive test data and dynamically observe the RSSI data i
n the OMC when a call drop problem occurs.
 Step 2. Analyze the data features when a call drop problem occurs:

Check whether the RSSI of the BTS is too high (such as -85 dBm or higher). If y
es, you can infer that uplink interference is present.

Check whether the transmit power of the UE is greater than 20 dBm within a fe
w minutes prior to the call drop occurrence. At this time, the UE is not located in
any weakly covered area. In this case, you can infer that uplink interference is p
resent.

Check whether the RSRP is -90 dBm or better but the CINR is smaller than 0 d
B in the serving cell (even including neighbor cells) that is being tested. If yes, y
ou can infer that downlink interference is present.
 Step 3. Determine which type of interference is present, and then handle it
accordingly.
 Confidential▲

Cause Analysis 6 – Interference

 Optimization Solution
 Determine and troubleshoot uplink interference:

Specify the rough range of the interference (which cells experiencing interferenc
e and whether these cells are included in a certain cluster)

Using a spectrum scanner such as YBT250 plus Yagi antenna to pinpoint the int
erference source.

 Determine and troubleshoot downlink interference:


Confirm that downlink interference does not come from any internal system (Thi
s requires eliminating the overshooting coverage and unconfigured neighbor cel
l problems).

If downlink interference comes from an external system, you need to use a spec
trum scanner such as YBT250 plus Yagi antenna to pinpoint the interference so
urce.
 Confidential▲

Cause Analysis 7 – Traffic Congestion

 Problem Symptoms
 There are relatively too many real-time activated subscribers
in the cell.
 The cell starts to reject the UEs during the admission control
procedure.
 The transmit power of the cell is becoming almost saturated.
 The call setup success rate and the call drop rate are becom
ing worse.
 Confidential▲

Cause Analysis 7 – Traffic Congestion

 Cause Analysis: OMC Performance Statistics Analysis
 Step 1. Collect performance statistics in busy hours from the OMC,
including call setup, handover, and call release.
 Step 2. Query the number of subscribers as well as the traffic load
when a call drop problem occurs, and then check whether the cell i
s heavily loaded.
 Step 3. Query the cell setup success rate, handover success rate,
and call drop rate; and locate their potential causes.
 Step 4. When a cell starts to reject the UEs during the admission c
ontrol procedure because of resource insufficiency, you can infer th
at the call drop problem is caused by traffic congestion.
 Confidential▲

Cause Analysis 7 – Traffic Congestion

 Optimization Solutions
 Increase the system capacity.

Increase the cell power.

Compress the overhead channel power.

Increase the resource blocks (RBs).

Add some base stations.
 Change the network topology and balance the traffic loa
d.

Shrink the coverage and adjust the RF for mitigating the power
overload
 Implement the SON-CCO function (pending).
 Confidential▲

Table of Contents

 Call Establishment and Call Drop

 Cause Analysis
 Troubleshooting Procedure
 Case Study
 Confidential▲

Call Drop Troubleshooting Procedure

Call Drop Troubleshooting Procedure

1. Check eNodeB is 2. Check the hardware 4. Check UE is working

running normally components properly.
3. Check
Equimnt

eNodeB is
running the
correct version UE rank UE
Common hardware Output power Feeder The UE is The UE
problems Antenna and authentica
RSSI connector faulty? version
capability tion
Radio Environnt

1. Check coverage problem 2. geographic characteristics 3. Check interference

Frequency Downlink:
Block Corner pilot Service Isolated cell Uplink: too
new site band Good RSRP
problem problem pollution border or hop spot high RSSI
(border) Poor CINR
Configuration and

1. Check parameters 2. Top N causes.

Performance
Network

other
Missing PCI handover Affected range Related KPIs
power Occurrence sectors
Neighbor multiplexing parameters (network, cell, Other KPIs of surrounding
time under this
BTS) cells
site
Resource Utilization

1. Radio resources are 2. Hardware resources are

restrained. restrined.

Power Transmission Heavy CPU

RB shortage resource usage of a
shortage
shortge board
 Confidential▲

Table of Contents

 Call Establishment and Call Drop

 Cause Analysis
 Troubleshooting Procedure
 Case Study
 Confidential▲

Case Study 1 – Poor Coverage

 Poor Coverage

RSRP < -120 dBm

Serving Cell CINR < -2 dB
 Confidential▲

Case Study 2 – Handover Failure

 Inter-Frequency Handover Unsupported
 Confidential▲

Case Study 3 – Missing neighboring Cell

 The UE sends the measurementReport message for several times be
fore a call drop problem occurs.
 Confidential▲

Course Review

 Call Establishment and Call Drop

 Cause Analysis
 Troubleshooting Procedure
 Case Study
Confidential▲