CS Domain Call Drop Analysis

ZTE University
Contents

Definition of Call Drop

Analysis of Call Drop
Case Study
Definition of Call Drop in Drive Test
The definition of drive test call drop is closely related to the test tool. The definition
algorithm of single-service call drop in CNT/CNA is as follows:
Call drop rate = number of call drop times/number of call setup success times
When Alerting message is received, the number of call setup success times increase
by one.
Alerting message is received, but Connect ACK message is not received while the
SYSTEM INFORMATION message is received, it can consider a call drop.
Connect ACK message is received, if the SYSTEM INFORMATION message is
received but the radioBearerReconfigurationComplete,
physicalChannelReconfigurationComplete, transportChannelReconfigurationComplete,
and rrcConnectionRelease, and rrcConnectionRelease_CCCH messages are not
received in the subsequent five seconds, it can consider a call drop.
Connect ACK message is received, if the Disconnect message is not received but
the rrcConnectionRelease and rrcConnectionRelease_CCCH messages are received, it
can consider a call drop.
In the actual application, the call drop location is specified in the L3 message by the
CNT/CNA tool.
Definitions of Call Drop in OMC
Call drop defined by the network management statistics is as follows:
z Radio call drop rate = (Number of released RABs of the call drop in the CS
domain requested by the RNC + number of RABs corresponding to the released
Iu connection in the CS domain requested by the RNC + number of released
RABs of the network disconnection in the PS domain requested by the RNC +
number of RABs corresponding to the released Iu connection in the PS domain
requested by the RNC)/(number of all released RABs in the CS domain + number
of all release RABs in the PS domain) 100%
In general, the call drop is classified into control plane and user plane
call drop. From the signaling process point of view, Control Plane
call drop occurs when the RNC initiates the Iu release request.
However, User Plane call drop occurs when the RNC initiates the
RAB release request.
Counter of Call Drop Reasons
Release Type Counter Reason
C301230315 Repeated Integrity Checking Failure
C301230316 Release due to UE generated signaling connection release
C301230317 Radio connection to the UE lost
C301230318 Repositioning complete timer expiration
Iu release C301230319 Radio interface process failure
C301230320 OM intervention
C301230321 Release due to overload control
C301230322 Uncertainty failure
C301230323 UTRAN initiation
C301230361 RAB pre-emption
C301230362 Release due to UTRAN
RAB release C301230363 IuUP failure
C301230364 Release due to overload control
C301230365 Uncertainty failure
Contents

Definition of Call Drop

Analysis of Call Drop
Case Study
Call Drop Caused by Poor Coverage

According to the network coverage definition, a sampling point is regarded as a

valid coverage point when the RSCP and Ec/Io reach specified thresholds. Poor
coverage refers to the RSCP is insufficient. At the network boundary, the RSCP
may be insufficient but Ec/Io may be good because there are few cells. In this
case, the network coverage is also regarded poor.

Service Type RSCP Requirement (dBm) Ec/Io Requirement (dB)

AMR12.2K -105 -13
CS64K -100 -11
PS384K -95 -10
HSDPA -90 -8
Call Drop Caused by Poor Coverage
The decision about the uplink or downlink coverage quality is based on the dedicated
channel power before call drop. The method is as follows:
If the uplink transmit power reaches the maximum before call drop, and the uplink
BLER is poor or the RL failure is reported by the NodeB according to the RNC
recorded single-user tracking, you can infer that the call drop is caused by poor uplink
coverage. If the downlink transmit power reaches the maximum before call drop and
the downlink BLER is poor, you can infer that the call drop is caused by poor
downlink coverage. When the uplink and downlink are well balanced and no uplink
and downlink interference exists, both uplink and downlink transmit power are
restricted. In this case, you need not check which link is first restricted. If the uplink
and downlink are severely unbalanced, you can infer that the restriction direction is
faulty.
The most effective method of determining the coverage fault is to check the data
collected by the scanner. If the RSCP and Ec/Io of the cell with the best coverage are
poor, you can infer that the coverage is poor.
Call Drop caused by Miss Configure Neighboring Cell

Neighbor-cell optimization is a key measure in wireless network optimization. Call

drop occurs if a neighboring cell to be configured is not configured (regarded as an
unconfigured cell). In such a case, the interference level in the network rises and the
system capacity is affected. Neighbor-cell optimization is the major part of
engineering optimization.
The unconfigured neighboring cells can be spotted by the following methods:
1. During the drive test, the UE obtains the neighbor list from the base station, and
the scanner scans the 512 main scrambling codes (SCs) and records the Ec/Io. If a
certain main SC is not in the neighbor list and its strength exceeds the specified
threshold for several seconds, you can infer that the cell corresponding to the main
SC is an unconfigured cell.
2. If call drop occurs, the SC of the UE residing cell is inconsistent with the SC
before call drop. It may be caused by unconfigured cells. You can determine whether
this problem is caused by unconfigured cells by checking the neighbor list in the
measurement control message before call drop.
3. Some UE may report the Detected Set message. If the detected set information
before call drop includes relevant SC information, you can infer that unconfigured
cells exist.
The method for inter-frequency and inter-system neighboring cells is similar.
Call Drop caused by Handover
Reason:
Handover problems occur when the size of the handover region is improper or signal
strength in the handover region changes. If the handover region is small or the signal
strength declines drastically, the handover process may be incomplete. Therefore, the
handover fails. If the handover region is excessively large, the system resource is
wasted. In addition, if the signal strength of signals in the handover region changes
frequently, the handover occurs frequently and the ping-pong effect occurs. As a result,
the system resource is wasted and the call drop rate rises.
Call Drop caused by Handover
Description of signaling failure:
z The handover process is incomplete. In general, the UE reports 1a and 1c
measurement reports before call drop, and the RNC receives the measurement
reports and sends the Active Set Update message. However, because the downlink
quality deteriorates quickly, the UE cannot receive the Active Set Update
message and call drop occurs.
z Ping-pong handover. The call drop caused by ping-pong handover occurs in this
manner: A cell requests entering the active set immediately after it is deleted from
the active set, and the UE cannot receive the Active Set Update message sent by
the RNC.
Call Drop caused by Handover
Analysis:
For handover call drop, it is vital to control the size and location of the handover
region. In addition, the signal strength of signals involved in the handover should be
guaranteed. The location and size of the handover region should be considered during
network planning. The size of the handover region should adjusted according to the
actual conditions in terms of average time required by the handover and the drive
speed. The handover region should not be chosen at corners because the corner causes
additional transmission loss and drastic signal attenuation, and the size of the handover
region is reduced. The corner signal attenuation should be dealt with enough signal
strength remainder at corners. The handover region should not be chosen at crossroads,
areas with high traffic volume, and VIP service areas.
For inter-frequency handover and handover between systems, the inter-frequency or
inter-system measurements should be started before the handover through the
compression mode (2D event). If the compression mode is started too late, the UE may
not measure the signals of the target cell in time. As a result, call drop occurs. Call
drop may occur when the UE completes the measurement, but the UE cannot receive
the inter-frequency or inter-system handover request. Call drop may occur on the air
interface if the size of the inter-frequency message is excessively large and the
downlink signaling congestion is caused.
Call Drop caused by Interference
Uplink and downlink interference should be distinguished.
The downlink interference is mainly caused by the pilot pollution region or
unconfigured neighboring cells. The unconfigured neighboring cell problem is
discussed in the previous part. Pilot pollution region exists in this manner: The signals
in a cell are adequate, the RSCP is good but Ec/Io is poor. Then, the UE frequently
performs the selection or handover, and there is incoming and outgoing call difficulty.
A pilot pollution region is formed in the following conditions:
Cross-cell coverage of high base stations
Base stations in ring layout
Signal distortion caused by street effect or strong reflection
The typical feature of the downlink interference call drop is that the RNC sends the
Active Set Update message to the UE but the UE cannot receive it. As a result, RL
Failure call drop occurs.
You can check whether uplink interference exists according to the cell Average RTWP
and Max RTWP of the OMC-R. The normal Average RTWP of an idle cell and of
50% uplink load is around -105 dBm and -102 dBm respectively. If the Average
RTWP in the idle state exceeds -100 dBm and the Max RTWP is around -90 dBm, you
can infer that uplink interference exists.
Call Drop caused by Interference
Call Drop caused by Interference
Call drop can also occur when the RSCP and Ec/Io of downlink signals are good, but
the uplink transmit power keeps rising and reaches the maximum.
In this case, the signal of the UE cannot be received by the uplink. The value of UL
interference in the SIB7 is -93 dBm. It indicates that the uplink RTWP is high. Then,
you can infer that the call drop is caused by uplink interference. At the same time, you
can verify the interference using the RTWP statistics of the OMC.
Call Drop caused by improper SC Reuse Distance

SCs may be reused in site concentrated areas. If the reuse distance is inadequate or the
neighbor relation is configured to a cell (in which SCs are reused) with little handover
possibility, call drop may occur because an improper neighbor list is generated.
When analyzing such call drop, check CellID in the call drop signaling besides SCs
because the neighbor relation is identified by CellID.
Call Drop caused by others
Excluding the preceding reasons, call drop may be caused by equipment faults. In this
case, you should check the alarm information and system logs. For example: The
NodeB is faulty and the synchronization fails, and then the link is repeatedly added
and deleted. The RF module is faulty, and then call drop occurs because the downlink
signal is poor. Call drop occurs because the UE does not report 1a measurement report.
Note that the transmission condition in some overseas countries is poor and the
transmission is not stable. Thus, the call drop caused by transmission problems has
profound impact.
Common Analysis Methods for Call Drop
The common analysis methods are multi-dimension analysis, trend
analysis, accident analysis, comparison analysis, ranking analysis,
and cause-and-effect analysis.
Multi-Dimension Analysis
"Dimension" refers to the perspective and emphasis of handling a
problem. Multi-dimension analysis is carried out from different
perspectives.
For the call drop problem, not only the call drop itself, but also
related factors such as access, handover, traffic statistics, time, RTWP
are to be analyzed. For example, the background statistics report
related to the call drop mainly indicates the following indicators in
parallel:
Trend Analysis
Accident Analysis
If the call drop rate during a certain period is
particularly high, you should check the
problem of this period by the following
method:
Check the equipment alarm and system log
of this period to find out hardware problems;
Check the transmission of this period;
Check whether the upgrade or cell blocking
is performed during this period;
Check whether there is an occasion with
abrupt high traffic requirements such as a
concert, game, or exhibition.
Comparison Analysis and Ranking Analysis
Comparison analysis
Comparison analysis is carried out through comparing various data sets from the same
perspective and finds out the differences. Furthermore, the reasons of the differences
can be found out. Comparison analysis is commonly used in the analysis of signaling
process.
Ranking analysis
Ranking analysis is carried out through classifying data into top N and bottom N data
from a large amount of data. The top N and bottom N data are further analyzed. For
example, ranking analysis is used to locate the worst cell.
Cause-and-Effect Analysis
For a certain effect, the cause-and-effect analysis is performed to locate the causes that
may result in the effect and to determine the influence of the causes. For example, the
call congestion of a cell may be caused by insufficient capacity of the hardware, of the
downlink, or of the uplink.
Note that each analysis method has its pertinence and restrictions. You may use a
combination of the methods discussed accordingly to locate complicated problems
such as equipment failure, parameter configuration (engineering parameters and radio
parameters), and network resource usage.
Contents

Dentition of Call Drop

Analysis of Call Drop
Call Drop Case Study
 Neighboring Cell Optimization

Case 1 - Miss Configure Neighboring Cell

Reason
Call drop caused by miss configure neighboring cell
Description
As is shown in next slide, UE moves from south to north along the
red arrow. The serving cell with SC 74 is in the south, whose
quality is extremely poor in the red circle (Ec/Io = -20.72 dB). The
Ec/Io of cell with SC 9 is -8.75 dB and good. However, the cell
with SC 9 is always in the detected set and can not add into active
set. As a result, soft handover is not successful and call drop occurs.
 Neighboring Cell Optimization

Case 1 - Miss Configure Neighboring Cell

74
 Neighboring Cell Optimization

Case 1 - Miss Configure Neighboring Cell

Main parameters
UTRAN neighbor cell list
Process of analysis
The cell with SC 9 is in the detected set and cannot be added to the
active set when the quality of the serving cell with SC 74 is extremely
poor. This is typical miss configure neighboring cell.
Optimization Solution
Modify the neighbor cell relation. Add the cell with SC 9 to the
neighbor cell list of the cell with SC 74.
Result
In the following two slides, at the beginning the cell with SC 9 is in
monitor set, and then becomes cell in the active set. Soft handover is
successful and no call drop again.
 Neighboring Cell Optimization

Case 1 - Miss Configure Neighboring Cell

 Neighboring Cell Optimization

Case 1 - Miss Configure Neighboring Cell

Case 2 Improper Neighbor Cell Relation
Reason
High call drop rate caused by improper neighbor cell relation.
Description
The call drop rate of the cell TRI135W-1 is always around 3%, and
no hardware alarm is reported. The cell coverage has no problem.
Main parameters
UTRAN neighbor cell list
Case 2 Improper Neighbor Cell Relation

Process of analysis
With ZTEs neighbor cell optimization software, NCOS, handover
and detected set data of each MINOS system can be collected. The
software is dedicated to analyzing the handovers between the cells in
details and to determine which neighboring cell should be added or
deleted, and how to set measurement priority of neighboring cells.
With the GIS map, the NCOS shows the neighbor relation directly.
Case 2 Improper Neighbor Cell Relation
index RNCID CID Cell Name SC Handover Times
1 1 10263 TRI026W-3 248 66689
2 1 11352 TRI135W-2 59 37017
3 1 10253 TRI025W-3 208 28371
22 1 11932 TRI193W-2 281 23
23 1 10212 TRI021W-2 156 23
24 1 10211 TRI021W-1 148 20
25 1 11001 TRI100W-1 196 9693
26 1 10203 TRI020W-3 144 1893
27 1 14351 TRI435W-1 53 1104
28 1 10981 TRI098W-1 414 943
29 1 11133 TRI113W-3 49 686
30 1 12003 TRI200W-3 409 292
31 1 10741 TRI074W-1 390 218
32 1 10191 TRI019W-1 147 106
33 10 10951 TRI095W-1 81 68
34 1 14183 TRI418W-3 120 53

The cells in white background are current neighbor cell of cell TRI135W-1,
while the cells in yellow are not.
Case 2 Improper Neighbor Cell Relation

Optimization Solution
Handover occurs 9693 times between cell TRI135W-1 and
TRI100W-1 with SC 196 and 1893 times between cell TRI135W-1
and TRI020W-3. These cells with most handover times should be
added as the neighbor cells of TRI135W-1.
However, handover occurs less than 80 times in current neighbor
cells such as TRI021W-2 and TRI021W-1 during busy hours of the
week. The current neighbor cells with too few handover times should
be deleted.

Result
After the neighbor relation is adjusted, the CS call drop rate of
TRI135W-1 decreases from 3 to 1.3%.
Case 3 - SC Reuse Optimization
Reason:
Call drop because of inadequate SC reuse distance
Description:
When the UE moves from the China Unicom building to Huaqiangbei
Commercial District along the Shennan Road, it firstly connects to
sectors 1 and 2 (SCs 246 and 247) of the outdoor site of the China
Unicom building. Occasionally, SC 124 reports 1a measurement
report, but it is not added by the RNC because it is not in the
detection set.
Then, SC 350, the fourth sector of the outdoor site of the China
Unicom building, is added and immediately replaced by SC 124.
After check, the cell with SC 124 (sector 2 of the Xiangmihu East
Hotel) is a neighboring cell of the cell with SC 350.
Later, the signal of SC 246 and SC 247 becomes weak. Only SC 124
is used after SC 123 is added several times. Then, 1a measurement is
reported to add SC 125 but no Active Set Update message sent by the
RNC is received. At last, call drop occurs.
Case 3 - SC Reuse Optimization
cellSynchronisationInfo cellSynchronisationInfo
{ {
modeSpecificInfo fdd : modeSpecificInfo fdd :
{ {
countC-SFN-Frame-difference countC-SFN-Frame-difference
{ {
countC-SFN-High 0, countC-SFN-High 0,
off 212 off 212
}, },
tm 37446 tm 37958
} }
}, },
modeSpecificInfo fdd : modeSpecificInfo fdd :
{ {
primaryCPICH-Info primaryCPICH-Info
{
{
primaryScramblingCode 124
primaryScramblingCode 123
},
},
cpich-Ec-N0 22,
cpich-Ec-N0 6,
cpich-RSCP 21
cpich-RSCP 13
Case 3 - SC Reuse Optimization
This problem occurs because the setup SC 124 and reported SC 125
are not from the same site. The drive test route starts from the
Nanguang Building in the Futian District and passes the Huaqiangbei
Commercial District. SC 125 is first regarded as the signal from the
Nanguang Building. However, according to the neighboring relation
in the background configuration and the drive test route, the signal is
from Xiangmihu East Hotel. According to the UE log, the cell ID in
the Active Set Update message is 18321, which indicates sector 2 of
the Xiangmihu East Hotel). The two sites use the same SC and the
distance between them is about 4.3 km. Between them, a lot of sites
are not started.
Case 3 - SC Reuse Optimization
According to the UE measurement at the location 2.6 km from the Xiangmihu East
Hotel, the frame offset and code offset are 108 and 21891 respectively. For
comparison, the frame offset and code offset of SC 251 reported by the UE at the
same time are 42 and 26102 respectively. This SC 124 is added to the active set.
According to the RNC signaling, this SC 124 is sector 2 of the Xiangmihu East
Hotel. After a period, the signal of SC 124 appears again at the location 900 m
away from the Nanguang building, marked by the red circle in the figure.
According to the UE measurement report, the frame offset and code offset are 129
and 33071 respectively. The frame offset and code offset of SC 125 are 129 and
32560 respectively. For comparison, the frame offset and code offset of SC 251
reported by the UE at the same time are 42 and 26066 respectively. Then, SC 125
is added to the active set. According to the RNC signaling, this SC 125 is sector 3
of the Nanguang building, 700 m from the preceding location.
According to the two groups of data, SC 124 in the first group is not SC in the
second group because the frame offset and code offset differ greatly. The jitter is
not intensified according to the frame offset and code offset of SC 251 used as
comparison. Because SC 124 is always in the active set during the UE call process,
SC 125 of the other site is not requested to be added when SC 124 is used.
Note that SC 125 cannot be added if the UE connects to the first SC 124 because
the distance between the sites with the same SC is close.
Case 3 - SC Reuse Optimization
Solution:
The SCs of the Xiangmihu East Hotel are adjusted so that the SCs
are different from that of the nearby site.
Result:
No call drop occurs due to the SC reuse fault of this site in later tests.
Case 4 - Soft Handover Parameter Optimization

Reason
Low handover success rate because of improper soft handover
parameter configuration
Description
The success rate of the handover from sector 1 (SC 436) of the
Shuqian Lu site to sector 2 (SC 434) of the Meihuacun hotel is low.
This area is within the Shuqian Lu section.
Main parameters
Soft handover 1a/1b event handover threshold, time to trigger
Case 4 - Soft Handover Parameter Optimization

The signal quality of the Shuqian Lu section is poor and fluctuating,

because there are over-bridge. Because the comparative threshold
decision algorithm is used, a cell with poor signal quality may be
added to the active set if the1a threshold is excessively high. If the
RNC sends the Active Set Update Command message to instruct the
UE to enter this cell, the soft handover may fail because the radio link
cannot be set up due to poor and fluctuating signal quality of this cell.
Case 4 - Soft Handover Parameter Optimization

Adjust the 1a/1b event handover threshold and trigger time in cell
436.
Lower 1a event handover threshold and shorten the trigger time to
ensure that the cells with good signal quality can firstly enter the
active set. Raise the 1b event handover threshold and extend the
trigger time so that the cells are not deleted too early due to sudden
signal deterioration.
Case 4 - Soft Handover Parameter Optimization

Result
After the parameter optimization, cell 434 of the Meihuacun site can
be added to the active set quickly and is not deleted too early.
According to the drive test result from more than 100 times of
handover tests, the success rate of the handover between the Shuqian
Lu site and the Meihuacun hotel site increases greatly.
Suggestion for similar problems:
The handover failure discussed in this example may occur when the
cell signal is within the handover region and the signal deteriorates
quickly because of obstructions. If the coverage of this cell cannot be
improved, it can adjust handover parameters. It should ensure that the
target cell can be added to the active set quickly and deleted from the
active set slowly.
Case 5 - Data Configuration Optimization in 2G/3G
Operations
Reason:
Call drop because of incorrect data configuration
Description:
When the 2G/3G handover tests are performed at the boundary of the
3G network, the handover from the 3G network to the 2G network
succeeds in the west to east direction, but the handover fails in the
east to west direction.
Main parameters:
BSC ID, LAC, NCC, and BCCH of the 2G neighboring cell
Data Configuration Optimization in 2G/3G Operations
Process of Analysis
Because the handover from 3G to 2G network fails, you should firstly check
whether neighbor cells are configured in 2G. If all neighboring cells are
configured, go to the next step.
Record whether the 2G UE starts the compression mode when the signal
quality of 3G is lower than the threshold, and record the CI of the 2G cell
where the compression mode is started. The signaling is below:

However, after the UE starts the compression mode, the relocation fails. The
signaling is below:

And the cause of the relocation failure is as follows:

According to previous signaling analysis, it can find that the UE does not
recognize the BSC of the 2G cell during the 3G-to-2G handover. In this case,
the failure may be caused by unconfigured BSC ID or LAC.
Data Configuration Optimization in 2G/3G Operations

Solution:
Check the BSC and LAC of the target 2G cell on the CN. It is found
that the LAC is not configured. Then, reconfigure the LACs of all 2G
neighboring cells on the CN.
Result:
After the data is configured again, all 3G-to-2G handovers succeed.
Suggestion for similar problems:
In the 3G-to-2G handover, the BSC ID, LAC, NCC, and BCCH of
2G neighboring cells must be configured in the 2G neighboring cell
database of the OMCR and in the CN.
Case 6 - Soft Handover Event Detection and
Reporting Time To Trigger
Time To Trigger (TTT) refers to the interval between the detection and reporting of
events (1A, 1B, 1C, and 1D). The setting of TTT has an impact on the promptness of
handovers.
When adjusting handover parameters, pay attention to two factors: 1. The signals from
different cells must be definitely overlapped. Then, you can adjust related radio
parameters so that the time for the UE crossing the handover region is longer than the
whole handover delay. Thus, the service continuity is guaranteed. 2. The size of the
handover region determined by both the signal and the radio parameters cannot too
large. If the size of the handover region is too large, the overhead used by the handover
is high and the resource usage decreases.
For areas with sheer signal changes such street corners, you should shorten 1a trigger
time, extend 1b trigger time, and adjust the CIO of neighboring cells so that 1a occurs
earlier and 1b occurs later. Thus, the handover can be performed successfully.
For scenarios such as express highways, call drop may occur because the UE cannot
enter the new cell due to fast drive speed and large cell spacing. The parameter
adjustment should be performed referring to the adjustment of street corners, that is,
helping the cell with good signal quality enters the active set quick to ensure the
service continuity.
Currently, the parameter adjustment is performed by adding a measurement number
and using it in the target cell.
Neighboring Cell Offset CIO
The sum of the CIO and the actual measurement value is used for the
event assessment of the UE. The sum is used by the UE in the intra-
frequency handover decision, which changes the cell boundary in the
handover algorithm.
A higher value of this parameter results in easier soft handovers,
more UEs in the soft handover state, and more used resources. A
lower value, however, results in more difficult handovers.
The CIO has an impact on the non-best cell. In detail, the CIO is
effective for 1a events in neighboring cells and effective for 1b events
in cells to be deleted.
Compression Mode Enabling/Disabling Threshold
The compression mode is used in inter-frequency and inter-system handovers. The
compression mode is enabled before the handover. The system uses the time interval
generated by the compression to measure the signal quality of the target cell of inter-
frequency or inter-system handovers. Currently, the compression mode is enabled by
the 2D event and disabled by the 2F event. The measurement can be RSCP or Ec/Io.
By default, the RSCP is currently used. The method of using the Ec/Io for enabling or
disabling the compression mode applies to the population concentrated urban areas or
the areas with weak coverage (similar RSCP and average main pilot).
Generally, enabling the compression mode involves the signal quality measurement of
the target cell (inter-frequency or inter-system) and signal quality deterioration
because of the UE movement. The compression mode can be started when the
handover process is complete, that is, the signal of the target cell is successfully
measured and reported before the signal quality of the current cell deteriorates to a
level close to the call drop condition. In addition, the compression mode should not be
enabled and disabled frequently.
In population concentrated urban areas, the continuous coverage of the 3G network
should be guaranteed. In this way, unnecessary system load will not be generated from
inter-system handovers. In scenarios such as 3G network boundary and express
highways, the 2D trigger threshold should be raised so that compression mode is
started quickly before 3G signals deteriorate and fades away.
Maximum Downlink Transmit Power of Radio Link

If call drop occurs frequently in a cell due to coverage problem,

increase the maximum downlink transmit power of services.
However, a user in the edge area may consume great transmit power,
which affects other users and reduces the downlink capacity of the
system. If users fail to access a cell due to heavy traffic, consider
changing the value of this parameter to a smaller value. However, be
cautious to perform this operation, which is risky, because this
parameter takes effect in the entire network.
Inter-frequency and Inter-RAT Threshold
When the measured value of inter-frequency and inter-RAT
neighboring cell signal exceeds the specified threshold, handover is
triggered. Considering the enable/disable threshold in compression
mode, configure this parameter. If you set this parameter to a small
value, handover is triggered ahead of time. If you set this parameter
to a great value, handover is delayed.
Timer and Counter Related to Call Drop
Name Description Value Range Default Value
T312 T312 of connection mode, that is, the time when the UE waits (1..15)s 1s
Connected for L1 synchronization indicator when the special physical
channel is set up
N312 N312 of connection mode, that is, the number of synchronization (1, 2, 4, 10, 20, 50, 1
Connected indicators that the UE should receive continuously from L1 100, 200, 400, 600,
before the special channel is set up successfully 800, 1000)
T313 Waiting time after the DPCCH channel set up in CELL_DCH (0..15)s 3s
mode loses synchronization
N313 Maximum number of lost synchronization indicators that the UE (1, 2, 4, 10, 20, 50, 20
receives continuously from the L1 100, 200)
T314 Time of cell update, existing in T314-related radio bearer when (0, 2, 4, 6, 8, 12, 16, 4s
wireless connection fails 20)s
T315 Time of cell update, existing in T315-related radio bearer when (0,10, 30, 60, 180, 600, 30s
wireless connection fails 1200, 1800)s

N315 Maximum number of synchronization indicators that the UE (1, 2, 4, 10, 20, 50, 1
receives continuously from L1 in T313 activated state 100, 200, 400, 600,
800, 1000)
T309 Waiting time after initiating requests to access other RATs, such (1..8)s 3s
as GSM