Professional Documents
Culture Documents
Problem Analysis
www.huawei.com
Foreword
Objectives
Contents
1. Call Drop Definition and Classification
2. General Troubleshooting Idea of Call Drop Problems
3. Call Drop Troubleshooting Checklists
4. Call Drop Cases
Page4
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
A call drop indicates that a call ends unexpectedly. During a call drop, the
service of the subscriber is interrupted because the BSC or MS releases the
business channel.
Statistics of call drops by counters: Upon receiving the Connection Failure and
Error Indication messages from the BTS, the BSC sends the Clear Request
message to the MSC to apply for disconnection. In this case, the number of call
BTS
BSC
MSC
Error Indication
Connection Failure
Measurement
point
Clear Request
Page5
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Typically, most call drops in a network occur over radio interface (CM33C call drops).
These call drops are classified into call drops that occur in the stable state and call drops
that occur during handover and should be given special attention.
Other types of call drops seldom occur in the network, among which, pay attention to
CM334 and CM333. The loopback function is seldom used in the network, therefore,
loopback call drops seldom occur.
CM33:
Call Drops on Traffic
Channel
CM33C:
Radio
Interface
CM330:
Stable State
CM332: No
MR from MS
for a Long
Time
CM333:Abis
Terrestrial
Link Failure
CM334:
Equipment
Failure
CM335:
Forced
Handove
r
CM331:
Handover State
Page6
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
CM397
CM385
CM330:
Stable State
CM3300:
(Error
Indication)
CM3301:
(Connection
Failure)
CM331:
Handover State
CM3302:
(Release
Indication)
H3027Ca:
(Internal
Intra-Cell
Handovers)
H3028Ca:
(Internal
Intra-Cell
Handovers)
H3127Ca:
(Outgoing
Internal
Inter-Cell
Handovers)
H3128Ca:
(Outgoing
Internal
Inter-Cell
Handovers)
H3327Ca:
(Outgoing
External
Inter-Cell
Handovers)
H3328Ca:
(Outgoing
External
Inter-Cell
Handovers)
M3100A:Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (T200 Expired)
M3100B:Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (Unsolicited DM Response)
CM3300:Call Drops on Traffic
M3100C:Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (Sequence Error)
Channel in Stable State (Error
M3200A:Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (T200 Expired)
Indication)
M3200B:Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (Unsolicited DM Response)
M3200C:Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (Sequence Error)
M3101A:Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Radio Link Failure)
M3101B:Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (HO Access Failure)
M3101C:Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (OM Intervention)
CM3301:Call Drops on Traffic M3101D:Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Radio Resource Unavailable)
M3101E:Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Other Causes)
Channel in Stable State
M3201A:Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Radio Link Failure)
(Connection Failure)
M3201B:Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (HO Access Failure)
M3201C:Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (OM Intervention)
M3201D:Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Radio Resource Unavailable)
M3201E:Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Other Causes)
CM3302:Call Drops on Traffic Channel M3102:Call Drops due to REL IND Received on TCHF (Traffic Channel)
in Stable State (Release Indication) M3202:Call Drops due to REL IND Received on TCHH (Traffic Channel)
Page7
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Page11
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Exercises
2.
Page12
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Contents
1. Call Drop Definition and Classification
2. General Troubleshooting Idea of Call Drop Problems
3. Call Drop Troubleshooting Checklists
4. Call Drop Cases
Page13
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Refer to
No
Yes
End
Page14
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Rule 1: DCR
Page15
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
After calculating the DCR of each cells, rank them in the descending order of
DCR(excluding handovers) to get the TOP cells.
Calculate the proportion of different type of DCR of each TOP cell and
determine which type of call drops percentage is the highest one in each cell.
Focus on the specific type of call drop in each cell and analyze accordingly.
For example:
Page16
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Traffic
Statistics
Signaling
Trace
Drive
Test
Page17
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
The problem of DT call drop is basically consistent with that of traffic call drop. The only
difference is that DT data cannot be classified according to the call drop reason.
According to the DT data or the log, analyze what causes call drops and count the DCR of
each cells. Then, filter the TOP cells/TOP area according to the DCR of each cells with the
help of the geographical display function of the MAPInfo.
DT call drops
Neighboring cell
relationship
Due to missing
configuration of
neighboring cell
relationship, handovers
cannot be triggered in
time. Due to redundant
neighboring cell
relationship, wrong
handovers occur. This,
then, causes call drops.
Handover
parameters
Due to improper
configuration of
handover
parameters,
handovers cannot
be triggered in
time or wrong
handovers occur.
This, then, causes
call drops.
Interference
problems
Due to cofrequency/adjacentfrequency
interference, internetwork interference,
or intermodulation
interference of
equipment, call
drops due to bad
quality occur.
Cross
coverage
Due to the
geographical
location and
terrain of the
site, cross
coverage is
caused and
then call
drops occur.
Page21
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Terminal
problems
As some terminals
do not decode the
level and BSIC of
neighboring cells
in time, handovers
cannot be
triggered in time.
This, then, causes
call drops.
The information such as receiving level, quality, CIR, usually used to analyze
call drop , are easily to be got by reviewing the history log files via software
TEMS, Probe
Compare with the signaling and traffic statistics, more information about
downlink such as the neighbor cells in BA2 is easily to be got to analyze the
neighbor cells missing, interference, handover etc.
Page22
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Contents
1. Call Drop Definition and Classification
2. General Troubleshooting Idea of Call Drop Problems
3. Call Drop Troubleshooting Checklists
4. Call Drop Cases
Page23
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
entire
network
TOP cell
entire network /some cell
BSC parameters
Proportions of CM33C is
high
Yes
No
Proportions of
CM334 and CM333
is high
No
Yes
network planning
frequency
neighboring cells
parameters
software version problems
interference
alarm information
coverage
In a normal network, most call drops over Um interface usually exist in only few cells .This type of call drops may be caused by
improper parameter settings, cross coverage, improper neighboring cells relationship, interference, and poor coverage.
Call drops over none radio interface seldom occur. When such call drops occur, just analyze the TOPN cell.
Page24
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
The reasons for call drops over Um interface in a large proportion in the entire network
Checking
core network
para.
Checking cell
network para.
Checking
freq.
planning
Checking
special
scenario
For call drops over none Um interface, pay attention to CM333 and CM334.
For CM333, determine whether they are caused by links problem on the Abis interface
according to the proportion and number of call drops.
For CM334, determine whether they are caused by equipment failure according to the
proportion and number of call drops.
The following factors may cause increase of call drops due to equipment failure:
Mutual aid of TRXs, dynamic modification of cell attributes, dynamic modification of frequencies
on TRXs, dynamic modification of frequency hopping data of TRXs, dynamic deletion of cells,
dynamic deletion of TRXs, blocking of cells, blocking of TRXs, blocking of channels
Alarm Name
LAPD Link Fault
Transmission LAPD Link Interrupt Alarm
E1/T1 Local Alarm
E1/T1 Remote Alarm Indication Signal
E1/T1 Loss of Signal(LOS)
E1/T1 Loss of Frame Alignment(LOF)
TRX communication alarm
TRX VSWR alarm
DRU Hardware alarm
Page26
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Find what are TOP cells and determine whether a TOP area exists
Engineering
Check
Parameter
Check
Interference
Check
Coverage
Check
Neighboring
Cell Check
Hardware
Transmission
TRX Usability<100%
TCH Usability<100%
Traffic Volume=0
Incoming HO Requests or
counters in the
function subset
should be equal to
(BTC Side)
transmission
problem
Outgoing HO Requests=0
Generally, the
Channel Requests=0
Page28
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Principle
By analyzing the difference between the main and diversity levels, sort
out the TRXs with comparatively great difference between main and
diversity levels.
Page30
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Version
Source
Counters ID
Calculation
BSC6000
All versions
Traffic measurement
data of the entire
network from the
M2000
BSC6900
Versions
before
BSC6900V900
R011SPC720
Traffic measurement
data of the entire
network from the
M2000
BSC6900V900
R011SPC720
and later
versions
Traffic measurement
data of the entire
network from the
M2000
Page31
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Basic Steps
Step 1 Analyze the data by running the macro in the tool after collecting busy hour traffic
measurement data in the last one or two days.
Step 2 The analysis results indicate the difference between the main and diversity levels of
each TRX based on BSC cells, and mark TRXs with a greater difference by using different
colors, as shown in the following figure.
Step 3 To analyze a specific fault point, refer to data configuration and summarized rules.
Ais of
Dif
15.7205
10.3244
Page32
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Typical case:
Connector loosed
Cell
Cell Label=B
TRX
Main level
Diversity level
Abs of Dif
TRX Index=502
-84.1285807
-95.4815181
11.35293745
11.35293745
11.35293745
TRX Index=503
-82.7684919
-84.9996951
2.231203188
2.231203188
TRX Index=509
TRX Index=510
-83.795518
-83.311275
-84.4110702
-84.7116505
0.615552168
1.400375472
0.615552168
1.400375472
Page33
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Typical case
There are the two modules in one cell, for all TRXs of one module, the main antenna
level is more than 12 dB higher than the diversity antenna level. For the other module,
the levels of the main and diversity antennas are normal.
Connector loosed
restores to normal.
Cell
TRX
Main level
Diversity level
Abs of Dif
Cell Label=A
TRX Index=195
TRX Index=196
TRX Index=215
-73.1199495
-75.3536322
-75.9703878
-75.844143
-76.2385249
-109.387862
2.724193511
0.884892689
33.41747396
2.724193511
0.884892689
33.41747396
33.41747396
TRX Index=216
-75.1245195
-107.852813
32.72829337
32.72829337
32.72829337
Page34
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Parameter check
For details, see page before(Troubleshooting for Call Drops over Um Interface in the Entire Network).
Interference checking
Coverage checking
Analyze the traffic statistics and find whether problems such as high proportion of great TAs, imbalance
between uplink and downlink, and high proportion of low levels exist.
According to the DT result, determine whether poor coverage areas exists or not.
Page35
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
H370c:Outgoing Inter-Cell
Handover Requests
H380:Incoming Inter-Cell
Handover Requests
H375B: Outgoing Inter-Cell
Handover Fail Reconn Fail
Practice
Page37
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Contents
1. Call Drop Definition and Classification
2. General Troubleshooting Idea of Call Drop Problems
3. Call Drop Troubleshooting Checklists
4. Call Drop Cases
Page38
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Fault description
Page39
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Problem Analysis
quality.
Page40
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Conclusion
After network
swapping, network
Check network
Traffic statistics: The proportion of call drops due to high expansion, network
coverage (power
levels and poor quality is high.
deployment, or
matching and newly
DT data: The downlink interference is strong.
UMTS900 refarming,
deployed sites)
the call drop rates
Analyze changes in
differ greatly between
Traffic statistics: The receive quality and call drop rate
traffic and KPIs in
GSM900 and
differ greatly between GSM900 and DCS1800. In
special scenarios
DCS1800 due to
addition, the proportion of call drops due to high levels
(networks supporting
inappropriate
and poor quality is high for cells working on GSM900.
GSM900 and DCS1800
parameter settings.
DT data: The downlink interference is strong in cells
and configured with coworking on GSM900.
BCCH)
Page41
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Transfer some
traffic from
GSM900 to
DCS1800 by
adjusting the
settings of
parameters such
as Inter-layer HO
Hysteresis.
Page42
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Evaluation
Fault description
The call drop rate in a cell is high because calls are likely to drop after
being handed over to the cell from cells served by another BSC. This
problem is caused by inappropriate settings of inter-BSC handover
parameters.
Problem Analysis
Required
Action
Conclusion
Solution Evaluation
Check all
parameters
Traffic statistics: Most call drops are caused low levels over
the Um interface.
Analyze
neighboring
relationships
(for newly
deployed sites
and areas
where Huawei
devices are
interconnected
to devices from
other vendors)
On the current
network, if the level
of a neighboring cell
under another BSC
is greater than 82
dBm, this
neighboring cell has
a higher priority
than the
neighboring cells
served by the same
BSC as the serving
cell. As a result,
calls in the serving
cell are first handed
over to the
neighboring cell
served by another
BSC. This handover
mechanism is
inappropriate.
Adjust the
setting of
Inter-layer
HO
Threshold
for the
neighborin
g cells
served by
another
BSC.
Page44
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Fault description
The call drop rate in a cell is high and the proportion of call drops due
to low levels is high. This problem is caused by cross coverage. If
cross coverage occurs, calls are not handed over in time and
therefore drop when MSs move to street corners.
Problem Analysis
Acceptable
Acceptable
Analyze neighboring
relationships (for newly
deployed sites and areas
where Huawei devices are
interconnected to devices
from other vendors)
Adjust the
antenna tile
The call drop
and azimuth
rate becomes
of cell A to
normal.
control the
coverage.
Page46
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Fault description
The call drop rate in a cell is high and the proportion of call drops
due to low levels is high. This problem is caused by missing
neighboring cells.
Problem Analysis
Page47
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Acceptable
Acceptable
Analyze neighboring
relationships (for newly
deployed sites and areas
where Huawei devices are
interconnected to devices
from other vendors)
Add a
neighboring
relationship
between cell
A and cell B.
Page48
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Fault description
After network swapping at site A, the call drop rates are high in the cells
covering two tunnels. After the network swapping, the network coverage
decreases because some combiners are added to BTSs. As a result, the call
drop rates increase. After the power is adjusted, the call drop rates become
normal.
Problem Analysis
According to the analysis of traffic statistics, most call drops are caused
low levels over the Um interface.
Page49
Solution
Evaluation
Increase the
power of the
BTSs to which
combiners are
added.
The network
coverage and call
drop rates
become normal.
Acceptable
Analyze neighboring
relationships (for newly
deployed sites and areas
Acceptable
where Huawei devices are
interconnected to devices
from other vendors)
Check RF tunnels for main
Some combiners are added to
and diversity faults, cross
BTSs, but the power of the BTSs is
connections, and
not increased.
After the network swapping,
interference
some combiners are added
Traffic statistics: Most call drops
to BTSs but the power of the
are caused low levels over the Um BTSs is not increased. As a
Check network coverage
interface.
result, the network coverage
(power matching and
becomes weak.
DT data: The network coverage
newly deployed sites)
becomes weak after the network
swapping.
Page50
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Fault description
Page51
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Analysis
Drive test
Page52
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Troubleshooting
Block TRX in turn and the congestion rate is always quite high no
matter which TRX is blocked.
Page53
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Troubleshooting
A suspect signal with 904.14 MHz center frequency, 300 kHz bandwidth is
found. It is similar to an analog signal and it exists continuously.
At the distributor output port of cell 1,2 and 3, the signal strength is 60 dBm,
40 dBm and 27 dBm respectively. It accords with the interference margin.
Fault description
Page55
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Analysis
The test mobile phone shows that before the call drop the serving
cell is BTS-B. But this building should be covered by BTS-A.
Page56
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Analysis
When the MS uses the signal of cell 2 of BTS-B in this area, the signal of
cell 3 of BTS-A is strong. But cell 2 of BTS-B and cell 3 of BTS-A are not
adjacent, therefore, handover cannot happen.
The signal in cell 2 of BTS-B is the result of multiple reflections. When the
Troubleshooting
Modify the data in BA1 table, BA2 table and add adjacent cell
relationship, set cell 3 of BTS-A as an adjacent cell of cell 2 of
BTS-B.
The test results show that the call drop problem is solved.
Page58
Define
new
adjacent
cells
for
the
isolated
cell.
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Fault description
Page59
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Analysis
The tunnel is near the BTS. When the MS enters the tunnel, the
power of the target cell is -80dBm. But the signal of source cell
goes down quickly to less than -100dBm. Before the MS enters the
tunnel, the downlink power of the two cells is good and no
handover is triggered. When the MS enters the tunnel, the level of
the source cell goes down rapidly. The call drop occurs before any
handover is triggered.
Page60
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Troubleshooting
Value after
change
PBGT HO threshold
72
68
70
60
10
15
Parameter name
Page61
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Page62
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Fault description
Analysis
Check the traffic statistic and find out that TCH congestion
Page63
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Troubleshooting
Move this board to another slot, and the problem still exists.
Conclusion
Page65
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Summary
Page66
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Thank you
www.huawei.com