Professional Documents
Culture Documents
UMTS CS Call Drop Analysis Guide BOOK
UMTS CS Call Drop Analysis Guide BOOK
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
Chapter 1.........................................................................1
Introduction ....................................................................1
Chapter 2.........................................................................3
Definition.........................................................................3
Definition of Call Drop from Drive Test Aspect ..................... 3
Definition of Call Drop at OMC Side .................................... 3
Chapter 3.........................................................................5
Introduction
Definition
Meanwhile the traffic statistics also imply reasons that the RNC
triggers the release of the RABs of different services.
The call drop rate can be calculated by the following formula:
CS _ CDR =
∑ CSRabrelTriggedByRNC *100%
∑ CSRABSetupSuccess
CSRabrelTriggedByRNC contains the number of RABs included in
RAB RELEASE REQUEST for CS services and that included in IU
RELEASE REQUEST for CS services.
PS _ CDR =
∑ PSRabrelTriggedByRNC *100%
∑ PSRABSetupSuccess
RabrelTriggedByRNC contains the number of RABs included in
RAB RELEASE REQUEST for PS services and that included in IU
RELEASE REQUEST for PS services.
It should be specified that the RNC traffic statistics calculates
the times of call drops through the signaling at the Iu interface,
and counts the number of RAB RELEASE REQUEST and the
number of IU RELEASE REQUEST initiated by the RNC. While call
drops in the drive test aspect emphasizes the information at the
air interface and non-access stratum and their cause value. It is
different from call drops at the OMC side.
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 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.
Scenario Two
FIGURE 2 S C E N A R I O T W O T H A T M A Y C A U S E T H E S A ME P S C P R O B L E M
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.
Scenario Three
FIGURE 3 S C E N A R I O T H R E E T H A T M A Y C A U S E T H E S A ME P S C P R O B L E M
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.
T ABLE 2 C O MMO N E 1 F AU L T S AN D H AN D L I N G SU G G E S T I O N S
FIGURE 4 F L O W C H A R T T O T E S T C A L L D R O P S B Y DT
For sites where alarms are reported, you should first perform
the health check for the site, which mainly covers the following
aspects:
n Alarms
n Frequently added or removed common transport channels
n UL & DL power
n Radio link restore
n Balance level between two antennas
n Statistics of service failures
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:
n UL interferences
n Insufficient cell radius or overshooting
n Reuse of the same PSC
n Abnormal UL RF channel
For these possible causes, you may check them combining other
measurement results and data analysis.
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.
NodeB LMT
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, 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.
UE Log
The sum of the value of Cell Individual Offset (CIO) and the
actually measured value is used in the evaluation of the events
of the UE. The UE would use the original measurement value of
this cell plus the CIO as the measurement result for the
intra-frequency handover judgment. CIO can help to ascertain
the cell edge.
The larger this parameter is set, the easier the soft handover will
be, and more UEs will be in soft handover state. However, more
resources are consumed. This smaller is parameter is set, the
more difficult the soft handover is.
CIO is valid only for the neighbor cell. For Event 1A, the CIO can
be set in the neighbor cell; for Event 1B, the CIO can be set in
the cell to be removed. The formula is as follows:
Formula of Event 1A triggering:
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
10⋅ LogMOld + CIOOld ≤ W ⋅10 ⋅ Log ∑Mi + (1−W) ⋅10 ⋅ LogMBest − (R1b + H1b / 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.
R1bis the reporting range of Event 1B.
H1b is the reporting hysteresis of Event 1B.
the handover, and the system can use the time slot brought by
compressed mode to perform the signal quality test on the
inter-frequency or inter-RAT neighbor cells. In the current
system, the compressed mode is started through Event 2D, and
stopped through Event 2F. The measurement value of RSCP or
Ec/Io can be selected. Currently, the default value is RSCP.
Generally, the quality and other related information of the target
cell (inter-frequency or inter-RAT) must be acquired for the
compressed mode. Meanwhile, the moving of the UE would lead
to the deteriorate of the quality of the cell, therefore, the start
threshold of the compressed mode should satisfy the condition
that the UE can finish the measurement of the target cell and
report for handover before call drops happens. For the stop
threshold, it should help to avoid the frequent start or stop of
compressed mode.
In dense urban, the continuous coverage of the 3G should be
ensured, thus avoiding unnecessary inter-RAT handovers and
increase of system load. For edges of the 3G network and
highways, the UEs should be handed over to the 2G network
before the heavy fading. Under this condition, the trigger
threshold of Event 2D should be raised so that the UE can
initiate the compressed mode as early as possible.
T ABLE 3 T I ME R A N D C O U N T E R R E L AT E D T O T H E UE
Value Default
Name Description
Range Value
T312 T312 in connected mode, (1..15)s 1s
Connected and indicates the time that
UE waits from the
synchronization indicator
from L1 when it starts to
establish the DPCCH.
N312 T312 in connected mode, (1, 2, 4, 10, 1
Connected and indicates the number of 20, 50, 100,
synchronization indicator 200, 400,
that the UE received from L1 600, 800,
before the DPCCH is 1000)
established.
T313 Indicates the waiting time of (0..15)s 3s
the UE in CELL_DCH state
after the DPCCH channel is
established.
N313 Indicates the number of (1, 2, 4, 10, 20
maximum number of out of 20, 50, 100,
sync indicators that the UE 200)
receives from L1.
T314 Start: When the criteria for (0, 2, 4, 6, 8, 4s
radio link failure are fulfilled. 12, 16, 20)s
The timer is started if radio
bearer(s) that are
associated with T314 exist
or if only RRC connection
exists only to the CS
domain.
T315 Start: When the criteria for (0,10, 30, 30s
radio link failure are fulfilled. 60, 180, 600,
The timer is started if radio 1200, 1800)s
bearer(s) that are
associated with T314 exist
or if only RRC connection
exists only to the CS
domain.
N315 Indicates the maximum (1, 2, 4, 10, 1
number of synchronization 20, 50, 100,
indicators that the UE 200, 400,
received from L1 after T313 600, 800,
is activated. 1000)
T309 Indicates the waiting time of (1..8)s 3s
the UE after sends the
inter-RAT handover
requests.