Professional Documents
Culture Documents
Version: V2.0
Date
V1.0
2009/4/23
V2.0
2009/11/25
Author
Qin Jianhan
Zhou Changjing
Reviewed by
None
Yin Jianhua, Gan Yi, Xu
Zhexian
Revision History
Draft
2nd edition
Key words:
CS, Call drop
Abstract:
This document introduces ways to evaluate, test, analyze and solve the call drop
problem.
Abbreviation:
None
Reference:
None
Table of Contents
1 Introduction ....................................................................................................................................... 1
2 Definition ............................................................................................................................................ 2
2.1
2.2
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.2
3.3
3.4
3.3.1
3.3.2
3.3.3
3.4.2
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
Figures
Figure 1
Scenario one that may cause the same PSC problem ...................................................... 7
Figure 2
Scenario two that may cause the same PSC problem ...................................................... 8
Figure 3
Scenario three that may cause the same PSC problem .................................................... 9
Figure 4
Figure 5
Figure 6
Figure 7
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
II
Internal
Tables
Table 1
Table 2
Table 3
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
III
Internal
1 Introduction
This document is compiled to guide the network optimization engineers to solve the
call drop problem, to reduce the call drop rate, and to improve the quality of the
network. It also introduces ways to evaluate, test, analyze and solve the call drop
problem. In addition, it also includes some typical cases. In the actual network
optimization activities, handover and call drop are strongly related. In most cases,
handover failure would lead to call drops. For this kind of call drops, you may refer to
the guidebook for call drops caused by handover. This document mainly focuses on call
drops which are not caused by handover failures.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
2 Definition
2.1 Definition of Call Drop from Drive Test Aspect
Air interface signaling at the UE side: Call drops refer to call releases caused by Not
Normal Clearing, Not Normal, or Unspecified when the message on the air interface
satisfying any of the following three conditions:
The call is released for Not Normal and the UE receives the RRC
Release information.
Release information.
Signaling recorded at the RNC side: Call drops refer to call releases when the RNC has
sent the Iu Release Request to the CN through the Iu interface, or when the RNC has
sent the RAB Release Request information to the CN through the user panel.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
CS _ CDR
CSRabrelTriggedByRNC *100%
CSRABSetupSuccess
PS _ CDR
PSRabrelTriggedByRNC *100%
PSRABSetupSuccess
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
RSCP [dBm]
Ec/Io [dB]
AMR12.2K
-105
-13
CS64K
-100
-11
PS384K
-95
-10
HSDPA
-90
-8
The coverage condition at the UL and DL of the network can be estimated through the
power of the dedicated channels for the UL and DL before call drops, which can be
performed through the following methods.
If the UL TX power before the call drop has reached the maximum value and the UL
BLER is bad, or it is found out through the single user tracing record at the RNC that
the NodeB has reported RL failure, then the call drop is caused by bad UL coverage. If
the DL TX power before the call drop has reached the maximum value and the DL
BLER is bad, then the call drop is caused by bad DL coverage.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
For the coverage optimization method, see the WCDMA Radio Network Optimization
Guide.
Use ZTE CNA to playback the call drop data. If the blue pillar
(representing the detected set) in the histogram of the pilot signals is the
longest, then the missed neighbor cell problem exists.
Use the automatic analysis tool of ZTE NCOS, it would study the
handover data of the network, and automatically add the missed neighbor cell.
For details, see the operation guide of NCOS.
During the drive test, the UE would acquire the neighbor cell list from
the NodeB, and the scanner would scan the 512 PSCs and record the Ec/Io. If
one of the PSCS is not included in the neighbor cell list, and its pilot strength
is stronger than the threshold, and the phenomenon lasts for a few seconds,
then the missed neighbor cell problem exists.
2.
Assign the priority of the neighbor cell when performing the initial neighbor cell
planning, then optimize the priority and number of neighbor cells periodically with
NCOS as the traffic volume increases.
3.
Check the external cells of the RNC periodically, and ensure the cells in the list are
correct.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
3.1.3 Call Drop Caused by Interference
Distinguish the UL and DL interferences.
The interferences from the UL and DL would both lead to call drop. Generally, when
the CPICH RSCP of the active set is large than -85dBm, and the comprehensive Ec/Io
is lower than -13dB, call drop occurs, then the call drop is caused by the DL
interference. Note that when the handover is not timely, the RSCP of the serving cell
may be good, but the Ec/Io is bad. However, the RSCP and Ec/Io of the monitored set
are both excellent under this condition. When the UL RTWP is 10dB higher than the
normal value, which is -107~-105, and the interference duration is 2s or 3s longer, call
drop may happen and the problem must be solved.
Two reasons may cause DL interferences, which are pilot pollution and missed
neighbor cell. The missed neighbor cell has already been discussed in the above part
and would not be repeated here. In the pilot pollution area, signals of multiple cells
exist, the RSCP of these cells is good, while Ec/Io is bad, the UE would frequently
reselect the neighbor cell or perform the handover, and the incoming and outcoming of
calls can hardly reach the UE. Generally, three factors would lead to pilot pollution in
the network.
Wave-guide effect, large reflectors, and some other effects that may
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
to failed handovers and call drops. The UL interference may be intra-RAT or inter-RAT
interferences. In most cases, the UL interferences are inter-RAT interferences.
When DL interference exists, the UL TX power is very small or the UL BLER may
converge, however, when the DL TX power of the UE reaches the maximum value, the
DL BLER does not converge. If UL interferences exist, the same problem would insist.
Thus, in actual analysis, this method can be used to distinguish whether interferences
exist.
For methods to investigate the interferences, see the UMTS Interference Investigation
Guidebook.
3.1.4 Call Failure Caused by Two Cells Using the Same PSC
3.1.4.1
Scenario One
Figure 1 Scenario one that may cause the same PSC problem
Cell A and Cell B (source cell) are configured as neighbor cell for each other, however,
the geographical distance between Cell A and Cell B is huge. Cell A and Cell C has the
same PSC, and Cell C and Cell B (source cell) is very close, however, Cell C and Cell
B are not configured as neighbor cells for each other.
Under this situation, the UE detects signals from Cell C and sends Event 1A request to
be soft handed over to Cell C. The PSC in the Event 1A request is 123. After receiving
the Event 1A request, the RNC checks from the neighbor cell list of Cell B (source cell)
for cells with PSC of 123, then it finds Cell A. Then the RNC tries to build the radio
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
link on Cell A. The RNC instructs the UE to add Cell A to its active set. Then, the
update of the active set times out for the cell measured by the UE is different from the
cell where the radio link is built.
3.1.4.2
Scenario Two
Figure 2 Scenario two that may cause the same PSC problem
In this scenario, the UE has established the radio link with two cells, Cell B and Cell C.
Cell A is the neighbor cell of Cell B, and Cell D is the neighbor cell of Cell C, and
these two cells have the same PSC. When the UE is in soft handover state, the RNC
would combine the neighbor cell lists of Cell B and Cell C, then the same PSC problem
would happen.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
3.1.4.3
Scenario Three
Figure 3 Scenario three that may cause the same PSC problem
Cell B and Cell D are not configured as neighbor cell for each other, however, these
two cells are both included in the active set owing to the third-party handover among
Cell B, Cell C, and Cell D. Cell A is the neighbor cell of Cell B, and Cell E is the
neighbor cell of Cell D, and these two cells have the same PSC. The RNC would
combine the neighbor cells of Cell B, Cell C, and Cell D in the active set, then the
same PSC problem may occur.
Reversely-connected antenna
You can check whether the diversity is reversely connected by the PSC distribution
figure of the drive test data. For the connection of the diversity, the PMS can be used to
measure the cell performance. The antenna would only generate power when UEs try
to access the network, and the measured value of the power equals to the demodulation
power. You can check the ratio of two antennas, if the power of one antenna is lower
than the other one in a long period of time, then the diversity must be reversely
connected.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
Internal
The balance level checking of two antennas in whole network can be implemented by
OMCB measurement. However, you need to manually process the acquired data.
2.
An excessive VSWR
You can check the VSWR of the current site at the RNC SDR. If the VSWR is large
than or equals to 1.4, then it must be adjusted.
3.
In the network of some cities, multi-band antennas exist. The operator usually refuses
to adjust the parameters of the multi-band antenna for fearing of affecting the
subscribers of the existing 2G network. Then pilot pollution or overshooting may occur.
To solve this problem, you should try to persuade the operator to change the antenna,
so that 2G and 3G networks can have separate antennas. If these antennas cannot be
changed, then the specific environment must be carefully studied before taking any
actions. You can optimize the neighbor cells to avoid call drops.
4.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
10
Internal
In most cities, call drops caused by signal leakage from indoor distribution system exist.
You should persuade the operator to reconstruct the indoor distribution system. Or, the
indoor distribution system can be merged to the whole network, which can be done by
optimizing of the coverage of the ambient outdoor cells and addition of neighbor cells.
5.
As the bottom level of transmission medium, E1 would report the loss of E1 electrical
signals and reception failures at the remote end. Meanwhile, several E1s would be
bound together as a group, and then E1 would report the fault of IMA group in
non-operating mode.
The following table lists several E1 faults that must be handled and the related
handling suggestions.
Table 2 Common E1 faults and handling suggestions
Fault
Lost of E1
electrical signals
Causes
Solutions
is slack.
whether
the
joint
E1
cable
satisfies
the
failure of the E1
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
11
Internal
the local end, and the local end reports the
alarm after detecting the alarm.
LOS Alarm.
The remote
E1 frame out of
sync
of
(dual-frame/multi-frame).
alarm is reported.
the
same
modes
non-operating
mode
Currently, some sites are configured with IP transmission. Therefore, the alarm of
"Lack Ethernet electrical signals" also should be handled on site.
If the 2G cells are congested, or interfered, then the success rate of 3G -> 2G
handovers is low. During the neighbor cell optimization, this kind of neighbor cells
must be removed from the list.
2.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
12
Internal
To improve 3G->2G handover success rate, the parameters must be detailed planned
based on different scenarios.
3.
Compatibility of UEs
The 2G->3G handovers of some cells are slow. This is because some smuggled 3G
handsets have some difficulties in supporting the 2G network.
4.
To support 2G/3G handovers, the 2G/3G cells must be configured as the neighbor cells
for each other firstly. If the cell information is updated timely, then the handover would
fail and cell reselection cannot be performed. Therefore, the data of 2G/3G network
should be synchronized timely.
For example, an
abnormal NodeB would lead to the synchronization failures, which would lead to
frequent removal and addition of radio links, and then call drops may happen; call
drops caused by poor DL signals may be because of abnormal RF module, and call
drops caused by that the UE fails to report the measurement report Event 1A.
It should be noted that in many foreign countries, the TX environment is bad and
unstable. Therefore, influences of call drops caused by TX problem are huge.
3.2
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
13
Internal
1.
The call drop data refers to the CNT test data and RNC signaling tracing data.
2.
Use CNA to analyze the call drops to acquire the location where call drops happen.
Then acquire the following data: pilot data collected before and after call drops, active
set and monitoring set information collected by the cell phone, and signaling flow.
3.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
14
Internal
The stability of the primary serving cell refers to its changes. If the primary serving cell
is stable, then analyze RSCP and Ec/Io. If the primary serving cell changes frequently,
then the handover parameters should be changed to avoid the ping-ping effect.
4.
Check the RSCP and Ec/Io of the optimal cell, and then
When the RSCP is normal, while the Ec/Io is bad, pilot pollution or DL
interference exists.
When RSCP and Ec/Io are both normal, if cells in the active set of the
UE are not the optimal cells (which can be checked through playback of data),
then the call drops may be caused by missed neighbor cell or untimely
handovers; if cells in the active set of the UE are the optimal cells, then call
drops may be caused by UL interferences or abnormal call drops.
5.
Since you cannot collect all necessary information by one DT, then multiple DTs shall
be performed to collect sufficient data. In addition, multiple DTs can also help to
ascertain whether the call drop is random or always happens at the same spot.
Generally, if call drops always happen at the same spot, this problem must be solved,
or if call drops happen randomly, multiple DTs must be performed to find inner
reasons.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
15
Internal
based on the alarms. If no obvious abnormal cells exist, the statistics can be classified
based on the carrier in each sector, then cells with poor KPIs can be screened out.
Further analyze the traffic statistics of these cells, such as analyzing more related KPIs,
such as analyzing data at a shorter interval, or analyzing KPIs that are more likely to
cause call drops, such as handover. Meanwhile, you can analyze the reasons for call
drops based on system logs. During the analysis, you should consider the effect of
other KPIs when focusing on a certain KPI. It should be specified that the result of
traffic statistics is meaningful only when the traffic volume reaches a certain amount.
For example, a 50% of call drop rate does not mean that the network is bad. This value
is meaningful only when the calling number, succeed calling number, call drop times
all make statistical significances.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
16
Internal
Collecting UE log, RNC signaling, KPI data, alarms, abnormal probes, and packet
Some common skills are required to collect data of the first layer, and the network
optimization & maintenance personnel can easily master these skills. At present, most
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
17
Internal
field questions can be located through the data analysis at this layer. Collection of the
debug log of the second layer should be performed or remotely supported by the
relative R&D engineers. Data at this layer can help to solve some deep layer problems.
The following chapter focuses on the data collection tool and method for the first layer
data, and only gives a brief introduction to that of the second layer.
3.3.2.2
Alarms
UL & DL power
The RL restore rate is shown by the NodeB cell measurement recorded by PMC as
shown in the following figure, and is accumulated since the establishment of cells. If
the RL restore rate of a cell is lower than 80%, the cell is treated as abnormal, and the
possible causes are as follows:
UL interferences
Abnormal UL RF channel
For these possible causes, you may check them combining other measurement results
and data analysis.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
18
Internal
Signal Trace
This tool traces signaling of RNC, you can trace the signaling at the Iu, Iur, Iub, and Uu
interfaces, TNL signaling, and RNL signaling through this tool. The most commonly
used method to check the KPIs is to trace the RNL signaling. This tool is very useful,
and can trace the signaling on the basis of cell (trace signaling of multiple UEs) and
IMSI (trace signaling of one UE).
It should be emphasized that signaling tracing by cells can only trace the UE that
initiates the call from this cell. The UE can be traced as long as it remains in the same
RNC, even if it is handed over to other cells. However, if a UE initiates the call from
other cells and then is handed over this call, and its call drop happens in this cell, it
cannot be traced. Therefore, when you trace the signaling of a cell with high call-drop
rate, the signaling of cells in close handover relation with this cell should also be traced,
then the result would be more comprehensive.
The RNC R&D engineers also develop a RNC signaling tracing tool, WinSigAn, which
can mark the call drop spots more clearly.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
19
Internal
3.3.3.2
3.3.3.3
NodeB LMT
Besides all functions of OMCB, NodeB Local Maintenance Terminal (LMT) can also
provide detailed cell and UE information.
The NodeB LMT consists of EOMS, EFMS, DMS, and PMS.
3.3.3.4
3.3.3.5
CTS
CTS is the tool for the CN, and it can be used to perform deep signaling by IMSI.
Unlike SignalTrace, which is applicable to the signaling tracing within one RNC, CTS
can perform the signaling tracing across the RNC border, Therefore, it is applicable to
the signaling tracing of VIPs.
CTS can trace the interactive signaling among different NEs within the CN, and can
trace the signaling at the Iu and Uu interfaces, and this is called deep tracing. The
working principles of CTS is as follows: First establish an IMSI task on CTS server,
and then sent this IMSI task to the CN, which is further sent to different modules
through the arranged interfaces, then each module collects the signaling related to IMSI,
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
20
Internal
and then the collected signaling is transmitted back to the CTS server through the CN.
The above interfaces are all private interfaces, thus this tool only work on ZTE CN and
RNC.
3.3.3.6
UE Log
DT is an important means to analyze KPIs. Many problems, signaling tracing at the
network side and tracing of problems which are hard to be located, can be finally
located after combining the UE logs. The commonly used DT software is
QXDM/APEX(QCAT), CNT/CNA, and TEMS.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
21
Internal
For the adjustment of the related parameters, a whole new set of parameters must be
assigned to the target cell.
3.4.1.1
NA
10 LogM New CIONew W 10 Log M i (1 W ) 10 LogM Best ( R1a H 1a / 2),
i 1
MNew is the measurement of the to-be-evaluated cells that has entered the report range.
Mi is the mean measurement result of cells (exclude the best cell) in an active set.
NA is the current cell number (exclude the best cell) in the active set.
MBest is the measurement result of the optimal cell in the active set.
W is the weight proportion of the best cell to the rest cells in the active set.
R1a is the reporting range of Event 1A.
H1a is the reporting hysteresis of Event 1A.
Formula of Event 1B triggering:
NA
Mnew is the measurement of the to-be-evaluated cells that has entered the report range.
Mi is the mean measurement result of cells (exclude the best cell) in an active set.
NA is the current cell number (exclude the best cell) in the active set.
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
22
Internal
MBest is the measurement result of the optimal cell in the active set.
W is the weight proportion of the best cell to the rest cells in the active set.
R1bis the reporting range of Event 1B.
H1b is the reporting hysteresis of Event 1B.
3.4.1.2
3.4.1.3
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
23
Internal
3.4.1.4
Description
Value Range
Default
Value
T312
Connected
(1..15)s
1s
Connected
800, 1000)
established.
T313
(0..15)s
3s
20
100, 200)
from L1.
T314
20)s
4s
30s
Indicates
the
maximum
number
of
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
24
Internal
synchronization
T309
indicators
that
the
UE
800, 1000)
(1..8)s
3s
This document contains proprietary information of ZTE Corporation and is not to be disclosed or used
except in accordance with applicable agreements.
25