CDR analysis and troubleshooting

1. Analyzing RNC CDR

The RNC CDR involves the number of RAB of each service triggered by RNC, including two aspects:

 After a service is established successfully, the RNC sends CN the RAB RELEASE REQUEST message.
 After a service is established successfully, the RNC sends CN the IU RELEASE REQUEST message, and
then receives the IU RELEASE COMMAND message sent by CN.

AMR CDR = VS {100} ∗ ([VS. RAB. AbnormRel. AMR]

+ [VS. RAB. AbnormRel. AMRWB])/([VS. RAB. NormRel. AMR]
+ [VS. RAB. AbnormRel. AMR] + [VS. RAB. AbnormRel. AMRWB]
+ [VS. RAB. NormRel. AMRWB])

To analyze PS call drop of various services, you can analyze the following indexes:

PS R99 CDR = {100} ∗ [VS. RAB. AbnormRel. PSR99]/([VS. RAB. AbnormRel. PSR99]
+ [VS. RAB. NormRel. PSR99])

PS HSDPA CDR = (([VS. HSDPA. RAB. AbnormRel]

+ [VS. HSDPA. RAB. AbnormRel. RF])/([VS. HSDPA. RAB. NormRel]
+ [VS. HSDPA. RAB. NormRel. UsrInact] + [VS. HSDPA. H2D. Succ]
+ [VS. HSDPA. H2F. Succ] + [VS. HSDPA. HHO. H2D. SuccOutIntraFreq]
+ [VS. HSDPA. HHO. H2D. SuccOutInterFreq] + [VS. HSDPA. RAB. AbnormRel]
+ [VS. HSDPA. RAB. AbnormRel. RF]))

PS HSUPA CDR = {100} ∗ [VS. HSUPA. RAB. AbnormRel]/([VS. HSUPA. RAB. NormRel]
+ [VS. HSUPA. RAB. AbnormRel] + [VS. HSUPA. HHO. E2D. SuccOutIntraFreq]
+ [VS. HSUPA. HHO. E2D. SuccOutInterFreq] + [VS. HSUPA. E2F. Succ]
+ [VS. HSUPA. E2D. Succ])

Based on analysis of previous indexes, you can obtain the performance of various services and rates in the
network, as well as SHO/HHO call drop. More important, you can obtain the cells with bad indexes and
periods.

2. Common Reasons for Call Drop

2.1 NeighborCellMissing
Generally, the call drop is caused by neighbor cell missing during the early phase of optimization. For the
intra-frequency neighbor cells, you can use the following methods to determine whether the call drop is
caused by intra-frequency neighbor cell missing.

Method 1:
Check the EcIo information about cells in the active set recorded by the UE and the Best Server EcIo
information recorded by the Scanner. If the EcIo recorded by the UE is poor and the Best Server EcIo
recorded by the Scanner is good, check whether the Best Server scrambling code recorded by the Scanner
is included in the intra-frequency measurement control. If the scrambling code is not included, you can
infer that the call drop is caused by the neighbor cell missing.

Method 2:
If the UE reconnects to the network immediately after the call drop and the cell scrambling code used
during the reconnection of the UE is inconsistent with that used during the call drop, the call drop may be
caused by the neighbor cell missing. You can confirm the cause through the measurement control. The

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
neighbor cell missing, including the inter-frequency neighbor cell missing and the inter-RAT neighbor cell
missing can result in call drop.

Method 3:
Enable the measurement analysis detection set (RNC detection set) to report 1A event. Then you can use
counters of UCELL-NCELL in order to get neighboring cells making the highest number of SHO addition
and that are not configured as neighbors in order to make neighboring addition.

2.2 CoverageProblem
Generally, poor coverage implies that both the RSCP and EcIo are poor. You can confirm the coverage
problem by checking the transmit power of uplink/downlink special channels through the following
methods:

If the uplink transmit power reaches the maximum value before the call drop and the uplink BLER is poor
or the single user tracing recorded by the RNC suggests that Node B reports RL failure, you may infer that
the call drop is caused by poor uplink coverage. If the downlink transmit power reaches the maximum
value before the call drop and the downlink BLER is poor, you may infer that the call drop is caused by
poor downlink coverage.

You can also confirm the coverage problem through the following simple and direct method:

Check the data collected by the Scanner. If both the RSCP and EcNo of the best cell are poor, you can
determine that the poor coverage results in the call drop.

2.3 HandoverProblem
There are two reasons for the call drop caused by the soft handover/inter-frequency, that is, it is too late
to perform the handover or ping-pong handover. In terms of the signaling process, for the CS service, the
UE does not receive the active set update command; for the PS service, the TRB is reset before the
handover of the UE.

In terms of signal, there are two scenarios in which it is too late for the handover:

Corner:
The EcIo of the source cell has a sudden sharp drop, and the EcNo of the target cell has an unexpected
dramatic increase.

Pinpoint:
The EcIo of the source cell increases after a period of time in rapid fall. The EcIo of the target cell has a
sudden increase in a short time period.

The ping-pong handover involves the following cases:

1. The primary cell changes rapidly: Two or more cells take turns to be the primary cell. The
primary cell has better RSCP and EcIo and exists in a short period of time.
2. There are multiple secondary cells: The RSCP is normal, and there is slight difference between
RSCPs of cells. The EcIo in each cell is poor.
2.4 InterferenceProblem
For the downlink, if the CPICH RSCP is greater than -85 dB and the EcIo is smaller than -13 dB, the call
drop tends to occur. This may be caused by downlink interference.

For the uplink, if the RTWP is 10 dB greater than the normal value (-104 to -105), there may be a call
drop. This is caused by pilot pollution.

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
 2.5 Interaction ProcessProblem
Processes, such as AMR control, enabling or disabling the DCCC, compression mode, and UE state
transition may fail due to reasons relating to the signal, UE capability, or the interaction between the
equipment in the RAN and UE, which finally results in call drop.

There is no common method to solve these problems. The method varies depending on the specific
process or UE.

2.6 OtherAbnormalProblems
If the preceding causes are excluded, the call drop may be caused by equipment problems. You need to
perform further cause analysis by checking logs and alarms of the equipment.

For example:

The synchronization failure causes repeated addition or deletion of links.

The UE does not report the la measurement report, which results in the call drop.

3. Analyzing Causes to Call Drop cell and RNC

In traffic statistics analysis, you must analyze the major causes to call drop.

Table 1 : Call drop counters.

Failure cause Analysis

OM interference
Causes due to RAB preemption
Causes due to UTRAN
Uplink RLC reset
Downlink RLC reset
Uplink synchronization failure
Downlink synchronization failure (including missing neighbor cell and over mall handover area) is bad, so the UE powers off
No response of UU port
Other RF causes
Abnormal AAL2 link
Abnormal GTPU
Other causes
The O&M tasks cause call drop.
High-priority preemption causes release of CS links. This kind of call drop occurs when
the load and resources are limited. Performing expansion depends on the times of
occurrence.
The causes due to UTRAN in the cell lead to abnormal release of link. This corresponds to
abnormal process, so you must further analyze it based on CHR.
Uplink RLC reset causes release of links, because the coverage quality (including missing
neighbor cell and over mall handover area) is bad.
Downlink SRB reset causes release of links, because the coverage quality (including
missing neighbor cell and over mall handover area) is bad.
Uplink synchronization failure causes abnormal release of links. The coverage quality
(including missing neighbor cell and over mall handover area) is bad, so the UE powers off
the transmitter abnormally or uplink demodulation is asynchronous.
Downlink synchronization failure causes abnormal release of links. The coverage quality
the transmitter abnormally or uplink demodulation is asynchronous.
The UE air interface fails to respond the command transmitted by system, because the
coverage is bad.
It is due to RF causes and the coverage quality is bad.
The RNC detects that AAL2 Path at CS lu interface is abnormal, so the system originates
an abnormal release. The problem might be due to abnormal transport equipment.
Immediate normal release during RB establishment is counted by statistics as abnormal
release as the cause.
The RNC detects the GTPU at PS lu interface is abnormal, so the system originates an
abnormal release. The problem is due to equipment failure.
You need to analyze the abnormal call drop based on RNC logs.

For conviniance, these counters are split as follow by service:

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
 CS Service
Table 2: CS Call drop counters.

CSRABAbnorma VS.RAB.Loss.CS.Abnorm+VS. VS.RAB.Loss.CS.Abnorm: Numbers of abnormally released

lRelease (cell) RAB.Loss.CS.RF RABs except RF causes in a cell
VS.RAB.Loss.CS.RF: Number of Released RABs Triggered by
RNC due to RF Reason
CSRABRelease VS.RAB.Loss.CS.RF+VS.RAB. VS.RAB.Loss.CS.Norm: Numbers of Released RABs Triggered
(cell) Loss.CS.Abnorm+VS.RAB.Loss by RNC due to CS Normal Cause in a cell
.CS.Norm
AMR service
Table 3: AMR Call drop counters.
AMRRABAbnrom Number of released CS AMR service RABs triggered by RNC in a
alRelease (cell) VS.RAB.Loss.CS.AMR cell
VS.RAB.Loss.CS.AMR + VS.RAB.Loss.CS.Norm.AMR: Numbers of Released RABs
AMRRABRelease VS.RAB.Loss.CS.Norm.AMR Triggered by RNC due to CS Normal Cause in a cell(AMR)
VP service
Table 4: VP Call drop counters.

VPRABAbnormal VS.RAB.Loss.CS.Conv64K Number of released CS 64 k service RABs triggered by RNC in a

Release (cell) cell

VPRABRelease VS.Norm.Rel.CS.Conv.RB.64+ Numbers of VP Service RABs released

(cell) VS.RAB.Loss.CS.Conv64K
PS services
Table 5: PS Call drop counters.

PSRABAbnormal VS.RAB.Loss.PS.RF+VS.RAB VS.RAB.Loss.PS.RF: Numbers of abnormally released

Release (cell) .Loss.PS.Abnorm RABs except RF causes in a cell
VS.RAB.Loss.PS.Abnorm: Number of released RABs
triggered by RNC due to RF reason
PSRABRelease VS.RAB.Loss.PS.RF+ VS.RAB.Loss.PS.Norm: Numbers of released RABs
(cell) VS.RAB.Loss.PS.Abnorm+VS. triggered by RNC due to PS normal causes in a cell
RAB.Loss.PS.Norm
HSDPA services
Table 6: HSDPA Call drop counters.

HSDPA_RBAbnor VS.HSDPA.RAB.Loss.Abnor VS.HSDPA.RAB.Loss.Abnorm.NonRF: Number of

malRelease m.NonRF + released PS service RABs carried by HSDPA triggered by
VS.HSDPA.RAB.Loss.RF RNC in a cell. The cause is not RF.
VS.HSDPA.RAB.Loss.RF: Number of released PS service
RABs carried by HSDPA triggered by RNC in a cell. The
cause is RF.
HSDPA_RBNorma VS.HSDPA.RAB.Loss.Norm + VS.HSDPA.RAB.Loss.Norm: Number of released PS
lRelease service RABs carried by HSDPA triggered. The cause is
VS.HSDPA.RAB.Loss.InActiv normal.
ity +
VS.HSDPA.RAB.Loss.InActivity: Number of released PS
VS.HSDPA.ChR.HSDSCHtoD
service RABs carried by HSDPA triggered. The cause is
CH +
User Inactivity.

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
 VS.HSDPA.ChR.HSDSCHtoF VS.HSDPA.ChR.HSDSCHtoDCH: Number of successful
ACH + channel handovers from the HS-DSCH to the DCH in the
VS.HSDPA.HHO.H2D.SuccO same cell
utIntraFreq +
VS.HSDPA.HHO.H2D.SuccO VS.HSDPA.ChR.HSDSCHtoFACH: Number of
utInterFreq successful channel handovers from the HS-DSCH to the
FACH in the same cell
VS.HSDPA.HHO.H2D.SuccOutIntraFreq: Number of
successful intra-frequency hard handovers from the HS-
DSCH to the DCH between two cells
VS.HSDPA.HHO.H2D.SuccOutInterFreq: Number of
successful inter-frequency hard handovers from the HS-
DSCH to the DCH between two cells
HSUPA services
Table 7: HSUPA Call drop counters.

HSUPA_RBAbnormalRelease VS.HSUPA.RAB.Loss.Abnorm VS.HSUPA.RAB.Loss.Abnorm: Number of

go back
HSUPA_RBNormalRelease VS.HSUPA.RAB.Loss.Norm+VS.HSUP
A.ChR.IntraCell.EDCHtoDCH.Succ+VS.
HSUPA.ChR.IntraFreq.EDCHtoDCH.Su
cc+VS.HSUPA.ChR.InterFreq.EDCHtoD
CH.Succ+VS.HSUPA.ChR.EDCHtoFAC
H.Succ
abnormal released PS service RABs carried
by HSUPA triggered by RNC in a cell
VS.HSUPA.RAB.Loss.Norm: Number of
released PS service RABs carried by
HSUPA triggered. The cause is normal.
VS.HSUPA.ChR.IntraCell.EDCHtoDCH.Su
cc: Number of successful attempts to switch
the channel type from EDCH to DCH in the
same cell of the RNC
VS.HSUPA.ChR.IntraFreq.EDCHtoDCH.Su
cc: Number of successful attempts to switch
the channel type from EDCH to DCH due to
intra-frequency hard handover between two
cells.
VS.HSUPA.ChR.InterFreq.EDCHtoDCH.Su
cc: Number of successful attempts to switch
the channel type from EDCH to DCH due to
inter-frequency hard handover between two
cells.
VS.HSUPA.ChR.EDCHtoFACH.Succ:
Number of successful attempts to switch the
channel type from EDCH to FACH in the
same cell of the RNC

3.1 Check Cells

If the previous KPIs of the cell are normal, check the alarms. By this, you can exclude the causes due to
abnormal cells.

3.2 Further DT for Relocating Problems

Analyzing traffic statistics indexes helps to expose potential problems. To locate and analyze problems,
you need to use DT and CHR. For problematic cells, the cell-oriented DT is performed to trace the signaling
flow at UE side and of RNC.

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
4. General Optimization Flow
Analyze call drop rate indexes of the RNC: Check whether the call drop rate index is normal based on the
overall call drop rate index of the RNC.

Analyze call drop rate indexes of the cells such as AMR call drop rate, VP call drop rate, PS call drop rate,
hard handover call drop rate, inter-RAT handover call drop rate and sort all of these cells according to the
indexes. Analyze causes of call drops occurring in the cells with worse or worst indexes.

Check whether the cell is normal: Check alarms relating to cells and exclude causes of abnormal cells.

Analyze call drop causes: If the call drop is not caused by AAL2 abnormality of the Iu interface or the GTPU
abnormality, check whether the reset of signaling RLC or service RLC is the call drop cause. Analyze
related handover indexes (incoming handover success rate and outgoing handover success rate) related
to the cell to check whether the call drop is caused by the handover failure. Analyze the measurement
relating to the overall bandwidth receiving power to check whether related uplink interference indexes
are high during the period of the high call drop rate. Then, you can determine whether the call drop is
caused by uplink interference.

Carry out the drive test to make call drop problems reoccur: If the call drop problem persists after the
analysis of measurement data, carry out drive tests in the cell to trace the signaling process on the UE side
and the RNC. For detailed analysis method, see the drive test analysis procedure.

Figure 1: General OSS call drop analysis procedure.

5. Optimization Flow for Tracing Data
Single subscriber tracing involves recording the following information:

 Signaling message (lu, lur, lub, and Uu) of single subscriber

 Performance tracing of CPICH RSCP and Ec/Io

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
  UE transmit power
 Uplink SIR, SIRTarget
 Uplink BLER
 Downlink code transmit power
 Uplink and downlink traffic and throughput (for data services)

Figure 2: Procedure of call drop analysis with tracing.

Analysis traced data includes analyzing single subscriber tracing message and performance monitoring.
Based on the combination of single subscriber message and data at UE side recorded by data collection
tools, you can locate basic call drop problems. For more complex problems, you need to use CHR and
performance monitoring.

By single subscriber tracing data, you need to locate and analyze problems concerning commercial UEs or
key subscribers which are not recorded at UE side.

1. Obtain single user tracing messages: Trace the single user on the RNC or M2000 before recording
related single user tracing messages. Generally, the messages recorded during the IMSI-based
tracing are sufficient for the analysis of the call drop problems.
2. Obtain information about the call drop location: Single user tracing messages suggest that the
cause of a call drop on the user plane is that the RNC actively sends the
RANAP_RAB_RELEASE_REQ message to release the RAB and the cause of a call drop on the
signaling plane is that the RNC actively sends the RANAP_IU_RELEASE_REQ message to release
the Iu interface. By checking the two messages, you can obtain the call drop time and signaling
messages before the call drop and perform further analysis.

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
 3. Analyze the call drop on the signaling plane: If a call drop occurs on the signaling plane, the UE or
the RNC cannot receive the confirmation message, which leads to the SRB reset and connection
release. The SRN reset can be caused by uplink messages such as the measurement control
message, active set update message, physical channel reconfiguration message, transmission
channel reconfiguration message, RB reconfiguration message, and command for the handover
from 3G networks to 2G networks. You need to check messages traced on the UE side to
determine whether the UE receives these commands. The SRN reset can also be caused by
downlink messages such as the measure report, active set update completion message, physical
channel reconfiguration completion message, transmission channel reconfiguration completion
message, and RB reconfiguration completion message. You need to check messages traced on the
RNC side to determine whether these tracing messages are received.
4. Analyze the call drop on the user plane: If the call drop occurs on the user plane, the TRB resets.
The TRB resetting occurs during a PS call rather than a Voice or VP call. If there is only one link in
the active set, the RL failure may cause the RNC to initiate the Iu release procedure. The lost
synchronization of the uplink causes the RL failure. The lost synchronization of the downlink
causes the UE to shut down the transmitter, which results in lost synchronization of the uplink. To
check whether the lost synchronization of the uplink or lost synchronization of the downlink
causes the release process, you need to analyze the transmit power of the UE and the monitored
code transmit power of the downlink before the call drop. Poor downlink coverage, strong
downlink interference, or uplink interference may lead to TRB reset. If the number of
retransmission times of data services is set improperly, the TRB reset occurs before the SRB reset
when it is too late for handover. You must take this case into account.
5. Analyze abnormal call drops: The abnormal call drop is caused by abnormalities occurs on the
equipment or the UE (for example, the transmission is interrupted, the base station equipment is
abnormal, and the UE crashes abruptly) rather than the coverage problem, interference problem,
or causes of the call drop occurs on the user plane or the signaling plane. If the call drop is caused
by the abrupt transmission interruption, you can analyze the CDL or alarms to locate the cause of
the call drop; if the call drop is caused by the abnormalities of the base station equipment, you can
check the status of the base station; if the call drop is caused by abnormalities of the UE, you can
analyze the data recorded by the UE.
6. Carry out drive tests to make the call drop problem reoccur: If the existing data is not sufficient to
locate the call drop problem, trace more detailed data. The best way is to carry out drive tests on
the call drop location and perform further analysis.

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
 Figure 3: Details on call drop analysis procedure with signalling trace.
6. Obtaining Information about Call Drop Point
According to single subscriber tracing messages, the call drop is defined as:

 The RNC originates RAB release (the message is RANAP_RAB_RELEASE_REQ)

 The RNC originates IU release (the message is RANAP_IU_RELEASE_REQ)

The former corresponds to call drop caused by TRB reset. The latter corresponds to call drop caused by
SRB reset. By searching for the previous two messages, you can obtain the call drop time and the signaling
message before call drop for further analysis.

7. Analyzing Call Drop due to SRB Reset

 Security mode process
 Authentication and encryption process
 Measurement control
 Active set update
 Physical channel reconfiguration
 Transport channel reconfiguration
 RB reset
 Handover command from 3G to 2G (HANDOVER FROM UTRAN COMMAND)

Confirm that the UE receives these messages by tracing messages at UE side. SRB reset occurs probably if
the UE fails to receive the following messages in uplink:

 Measurement report
 Active set update complete
 Physical channel reconfiguration complete
 Transport channel reconfiguration complete
 RB reconfiguration complete

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
8. Analyzing Call Drop due to TRB Reset
TRB reset usually occurs in PS services. It seldom occurs in voice and VP services. Confirm TRB reset by
the UE transmit power upon call drop and downlink Transmit Code Power. When only one link exists in
active set, uplink asynchronization causes RL failure which consequently causes lu release originated by
RNC. Downlink asynchronization causes UE to power off transmitter, which consequently causes uplink
asynchronization. To judge whether uplink asynchronization or downlink asynchronization causes
release, you must analyze the UE transmit power before call drop and downlink code transmit power
monitored in real-time state. Weak downlink coverage, strong downlink interference or uplink
interference causes TRB reset. If the retransmission times of data services are improperly configured, TRB
reset occurs before SRB reset upon delayed handover. Pay attention to this.

9. AnalyzingAbnormal Call Drop

Abnormal call drop can neither be located from coverage and interference nor be explained by TRB reset
or SRB reset. It is caused by abnormal equipment or UE. For example, it might be caused by the following
factors:

 Abrupt transmission failure

 Abnormal NodeB equipment
 Abrupt breakdown of UE

Analyze abnormal transmission by analyzing CHR or checking alarms. Confirm that the NodeB equipment
is abnormal by querying NodeB state. Locate abnormal UE problems by analyzing data recorded by UE.

10. Performing CQT to RecheckProblems

When the data is inadequate for locating call drop problems, you must start more detailed data tracing.
The best method is to perform CQT at call drop points to recheck problems for further analysis.

11. Usual Parameters used for CDR adjustment

11.1Cellindividual offset (CIO):
The sum of the CIO and the actual measured value is used to determine whether the intra-frequency
handover is to be performed in the event evaluation process of the UE. In addition, the sum can serve as
the mobile cell boundary. If the value is larger, the soft handover is easier and more UEs are in the soft
handover state. In this case, the forward resources are occupied. If the value is smaller, the soft handover
is more difficult and the quality of received signals may be affected. For the pinpoint or corner effect, the
better method is to configure the CIO as about 5 dB.

11.2Time to trigger the delay related to the soft handover:

The delay triggering time refers to the time to trigger 1A, 1B, 1C, or 1D event. The triggering time may
affect the promptness of the handover. Generally, the default triggering time can meet requirements of
most scenarios. Set handover-related parameters according to the environment and adjust the
configuration of related parameter for each cell. You can limit the impact of the parameter modifications
to certain cells, which reduces the impact on the system.

11.3FilterCoef:
The layer 3 filter tries to filter out the random impingement samples to enable the filtered measured
values to reflect the main change trend of actual measured values. The measured values input in the layer
3 filter are filtered by the layer 1 filter. Therefore, the impacts of fast fading are removed, and the layer 3
filter performs the smooth filtering on shadow fading and few fast fading burrs to provide higher quality
measurement data. The filter with greater filtering coefficient has stronger ability to smooth burrs but
weaker ability to trace signals. Typical values are set as follows:

 If signals in the handover area change slowly, the intra-frequency filtering coefficient is set to 7.

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
  If signals in the handover area change at a moderate speed, the intra-frequency filtering
coefficient is set to 6.
 If signals in the handover area change rapidly, the intra-frequency filtering coefficient is set to 3.
11.4Threshold for enabling or disabling the compression mode:
The compression mode is enabled before the inter-frequency or inter-RBT handover. You can use the
compression mode to check the quality of inter-frequency or inter-RBT cells. The compression mode is
enabled only when the RSCP or EcIo of the CPICH meet requirements. In actual applications, the common
triggering condition is that the RSCP must meet requirements. Generally, the compression mode requires
measuring the quality of the target cell (inter-frequency or inter-RAT cell) to obtain related information.
Movements of the UE deteriorate the quality of the current cell. Therefore, the requirement for setting the
threshold for enabling the compression mode is to measure that the target cell completes the handover
before the quality deterioration of the current cell leads to the call drop; the requirement for setting the
threshold for disabling the compression mode is to avoid the compression mode being enabled or
disabled frequently.

11.5RLMaxDLPwr (Maximum Downlink Transmit Power of Radio Links):

The high transmit power of special links is favorable for solving call drop problems caused by the poor
coverage but causing the interference problem. In this case, the single user consumes high power at the
edge of the cell, which impacts on other users and reduces the downlink capacity of the system. Generally,
the downlink transmit power is determined by the link budget with a variation of 1-2dB. If the drive test is
carried out for once, it is difficult to measure the impact of the high power on the call drop. The
measurement, however, reveals the impacts. If the poor coverage causes a higher call drop rate in certain
cells, you can raise the maximum transmit power of special links. If the overload results in a higher access
failure rate, you can consider to reduce the maximum transmit power.

11.6Number of signaling/service retransmission times:

If the number of retransmission times of the signaling over links with higher block error rate reaches the
maximum value, the signaling is reset, which causes the call drop. If the number of retransmission times of
the service transmitted in AM mode reaches the maximum value, the signaling is reset. If the number of
the reset times reaches the configured maximum value, the system releases the service, which causes the
call drop. The default configuration only ensures that the unexpected error blocks do not cause a call drop.
In certain scenarios with poorer coverage, however, the signaling reset results in the call drop and causes
the resources occupied by the service to be released. In certain scenarios with more burst interference or
remarkable pinpoint effect, the block error rate may reach 100%. If the call drop rate is required to be not
too high in such scenarios, you can appropriately increase the number of retransmission times to weaken
the impact of the burst interference. This parameter is configured on the RNC.

11.7RSCP (Inter-RAT Hard Handover Threshold) :

After the inter-frequency measurement is started, the UE starts measuring the inter-frequency cells. If the
signal quality of the inter-frequency cells is higher than the threshold, the RNC initiates the inter-
frequency handover. You can configure the parameter based on the threshold for enabling or disabling the
compression mode. If the parameter value is smaller, the handover is triggered earlier. If the parameter
value is greater, the triggering of the hard handover is delayed. In this way, you can control the handover
area or reduce the call drop rate.

11.8GsmRSSICSThd and GsmRSSIPSThd:

GsmRSSICSThd and GsmRSSIPSThd specify the inter-system handover thresholds of the CS service and the
PS service respectively. The method for setting the two parameters is the same as that for setting the
inter-frequency hard handover threshold.

12. Multi-RAB CDR optimization

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
The Multi-RAB services increased as smart phone penetration is increasing.

The general causes of drop rate of Multi-RAB are higher than single CS RAB are:

 Higher RF signal quality requirement comparing with CS Single RAB

 More complicated signaling procedure comparing with Single RAB

To improve the CS call drop three different techniques are possible:

 Reduce the PS RF signal quality requirement for multi-RAB

 Reduce the loss probability due to complicated signaling process.
 Optimize the signaling procedures
12.1Bear UL PS service on DCH instead of HSUPA:
Benefit:
The UL RF signal requirement of DCH is much less than HSUPA.

The signaling procedure is simplified because there is no HSUPA related procedures including HSUPA
DCCC, HSUPA 2ms to 10 ms TTI reconfiguration, H2D handover, etc.

Possible Negative Impact:

Reduce UL throughput in case of CS+ PS Multi-RAB.

Impact Analysis:
HSUPA can be used after CS release.

The subscriber is not sensitive to throughput when at a CS call session.

12.2Reduce PS service Bit Rate for Multi-RAB

Benefit:
Reduce the RF signal requirement of DCH.

The signaling procedure is simplified because of DCCC reductions.

Possible Negative Impact:

Reduce throughput in case of CS+ PS Multi-RAB.

Impact Analysis: The subscriber is not sensitive to throughput when at a CS call session.

12.3Activate the Cell Update Based on UE SRB Reset

Background:
The UEs with this functionality of cell update based on UE SRB Reset in this industry have been increasing
recently.

Figure 4: Cell update procedure

Benefit:

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
Reduce the call drop rate to UEs with this function.

Negative Impact:
Slightly more resource consumption.

12.4Reduce the drop probability by timer optimization

12.4.1 Optimize Active set update timer and HSDPA Cell Change timer
Benefit:
Reduce the call drops for the case:

RNC sends the ASU (1A/1B/1C) or Serving Cell change(HSDPA), if the network cannot receive “ASU
complete”, the call will be released.

Negative Impact:
Slightly more resource consumption.

12.4.2 Optimize RB Reconfiguration timer

Benefit:
Reduce the call drops for the case:

Network sends the RB reconfiguration, if the network cannot receive the “complete” signalling, the call
will be released.

Negative Impact:
Slightly some resource consumption.

12.4.3 OptimizeCell-Update responsetimer:

Benefit:
Reduce the call drops for the case:

RNC sends the “Cell Update confirm”, if the network cannot receive the “complete” in time, the call will be
released.

Negative Impact:
Slightly more resource consumption. Subscriber may feel some disconnection/silence in this period.

Impact Analysis:
Compared with the timer in UE (8 seconds), UE will re-connect to the network rather than network
waiting for even longer time. The actual subscriber perception is impacted.

12.4.4 Optimize RB REL timer:

Benefit:
Reduce the call drops for the case: Network sends the RB Release(for PS service), if the network cannot
receive the “complete” in time, the call will be released. .

Negative Impact:
Slightly more resource consumption.

12.4.5 Relatedparameters and MML commands

Bearer Channel Type and Access Rate Control Policy

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement

function
The switch for CS service
triggers P2D state transition
when UE processing PS BE
services
the bearer channel type and
access rate of PS BE
services is DCH0K or
DCH8K after the P2D state
transition
The switch to validate
above two policies
Limit the PS BE service rate in the combined service
function
Limit the uplink PS BE
services on the DCH in the
CS+PS combined services
Limit the upper limit of
uplink DCH rate in CS+PS
combined services
Limit the downlink PS BE
services on the DCH in the
CS+PS combined services
Limit the upper limit of
downlink DCH rate in
CS+PS combined services
Reserved parameters
Switch
RESERVED_SWITCH_0_BIT28
RESERVED_SWITCH_0_BIT14
RESERVED_SWITCH_1_BIT6
RESERVED_SWITCH_0_BIT11
RESERVED_SWITCH_0_BIT15
ULDCHBEUPPERLIMITFORAMR
DLDCHBEUPPERLIMITFORAMR
12.4.6 EffectEvaluate
KPIs and counters for monitoring the feature performance show as below,
KPIs & counters
VS.MultiRAB.CSAbnormRel.CSPS
Call drop rate of CS service in combined services
NOVATEL_IT_Algeria_Internal_Document_V032016
Table 8: Bearerchannel type parameters.
Parameters and meanings
SET
UCORRMALGOSWITCH:RESERVEDSWITCH0=RESERVED_SWITCH_0_BIT28-
1;1 means the UE first performs a P2D state transition
SET
UCORRMALGOSWITCH:RESERVEDSWITCH0=RESERVED_SWITCH_0_BIT14-
1; 1 means the bearer channel type and access rate of PS BE services is DCH0K in both
the uplink and downlink
SET
UCORRMALGOSWITCH:RESERVEDSWITCH0=RESERVED_SWITCH_0_BIT6-
1;1 means the above two policies is validated
Table 9: PS BE service rate parameters.
Parameters and meanings
SET
UCORRMALGOSWITCH:RESERVEDSWITCH0=RESERVED_SWITCH_0_BIT11-
1; 1 means the PS service must be carried by DCHs in the uplink if both CS and PS
services exist.
SET UFRC:ULDCHBEUPPERLIMITFORAMR=D8 This parameter specifies the
upper limit of uplink R99 BE service rate in combined AMR services.
SET
UCORRMALGOSWITCH:RESERVEDSWITCH0=RESERVED_SWITCH_0_BIT15-
1; 1 means the PS service must be carried by DCHs in the downlink if both CS and PS
services exist.
SET UFRC:DLDCHBEUPPERLIMITFORAMR=D8; This parameter specifies the
upper limit of downlink R99 BE service rate in combined AMR services.
Table 10: Reserved parameters for multiRAB.
Current Target
Level Meaning and impact
Value value
When the switch is turned on,the UE first performs a P2D
0 1 RNC state transition and then
establishes the CS service if the UE processing
When the RESERVED_SWITCH_0_BIT14 PS BE services
is selected,the bearer
1 1 RNC channel type and access rate of PS BE
When the RESERVED_SWITCH_1_BIT6 is selected, the Bearer
1 1 RNC Channel Type and Access Rate Control Policy can be used
When the switch is turned on, the PS service must be carried
1 1 RNC by DCHs in the uplink if both CS and PS services exist.
When the switch is turned on, the PS service must be carried
0 1 RNC by DCHs in the downlink if both CS and PS services exist.
Meaning: This parameter specifies the upper limit of uplink
D384 D8 RNC R99 BE service rate in combined AMR services. Combined
AMR services
Meaning: Thisconsist of only
parameter AMR services
specifies andlimit
the upper BE services.
of If
D384 D8 RNC downlink R99 BE service rate in combined AMR services.
Combined AMR services consist of only AMR services and BE
Table 11: MultiRAB optimization procedure impact on KPIs.
Expected Result
Decrease
Decrease
RNO_Departement
Call drop rate of pure CS services decrease
PS Call Drop Rate in CS+PS Combined Service similar or decrease
CS+PS RAB Setup Success ratio similar or increase
RAB setup success rate of AMR services similar or increase
R99 Code Utilization(%) increase
Code Utilization Rate(%) similar
VS.MultiRAB.MeanThroughput.HSDPA(kbit/s) similar
VS.MultiRAB.MeanThroughput.PSR99UL(kbit/s) Decrease
VS.MultiRAB.MeanThroughput.HSUPA(kbit/s) similar
VS.MultiRAB.MeanThroughput.PSR99DL(kbit/s) Decrease
R99 UL User(RNC Level) increase
R99 DL User(RNC Level) increase
PS R99 Call Drop Ratio with PCH similar
VS.R99PSLoad.DLThruput.RNC(kbit/s) similar
VS.R99PSLoad.ULThruput.RNC(kbit/s) similar
PS RAB Setup Success Ratio (RNC) similar
CS RAB Setup Success Ratio (RNC) similar or increase

13. Diagrams:

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
 Start

Is CS CDR
Go to
Multi-RAB True multiRAB True >= 1% False
optimizatio main
n diagram problem?

False

VS.RAB.Abnor Check AAL2 parameters in cell, VS.RAB.Abnor

Drop due to O&M. Check alarm
mRel.CS.OM AAL2 capacity and equipment mRel.CS.IuAA
history and log for analysis. Not
failures (analyse all
relevant. L2
transmission path).

1- Solve capacity problems 1- Solve capacity problems

VS.RAB.Abno (relate to UL/DL capacity (relate to UL/DL capacity VS.RAB.Abnor
management) management)
rmRel.CS.Pre mRel.CS.OLC
2- Remove preemption. 2- Easier IRAT trigger threshold
empt 3- Easier IRAT trigger threshold 3- Activate 3G to 2G relocation
4- Activate 3G to 2G relocation on load.
on load.

VS.RAB.Abno
Includes all precedent causes and
rmRel.CS.UTR
actions. Check alarms and hardware
ANgen malfunctioning.

1- Neighboring missing
2- Coverage problem (tilt change, CIO
VS.RAB.Abnor VS.RAB.Abnor change, …)
3- Problem in transmitter
mRel.CS.RF mRel.CS.RF.U 4- Solve RTWP and interference
LSync problem (Uplink demodulation
problem)
5- Change Soft HO parameters (1A,
1B, 1C trigger and/or Filter coef

1- Coverage problem (tilt change, CIO

VS.RAB.Abnor change, …)
mRel.CS.RF.U 2- Indoor coverage, …
3- Increase RLMaxDLPwr.
uNoReply 4- Easier IRAT trigger threshold.
5- Enable Call reestablishment.

VS.RAB.Abnor 1- Coverage problem (tilt change, CIO

mRel.CS.RF.S change, …), indoor coverage, …
2- Easier IRAT trigger threshold
RBReset
3- Enable Call reestablishment

End
NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
 Start

Is PS CDR
Go to True
Multi-RAB multiRAB True >= 3% False
optimizatio main
n diagram problem?

False

4- Solve capacity problems

VS.RAB.Abnor (relate to UL/DL capacity VS.RAB.Abnor
Drop due to O&M. Check alarm
mRel.PS.OM management) mRel.PS.OLC
history and log for analysis. Not 5- Easier IRAT trigger threshold
relevant. 6- Activate 3G to 2G relocation
on load.

1- Solve capacity problems 1- Check interference

VS.RAB.Abno (relate to UL/DL capacity 2- Check neighboring VS.RAB.Abnor
management) 3- Check power related
rmRel.PS.Pre mRel.PS.CCH
2- Remove preemption. parameters for CCH power
empt 3- Easier IRAT trigger threshold 4- Increase power
4- Activate 3G to 2G relocation
on load.

VS.RAB.Abno
rmRel.PS.GTP Change GTPU and/or check
ULoss transmission quality.

6- Neighboring missing
7- Coverage problem (tilt change, CIO
VS.RAB.Abnor VS.RAB.Abnor change, …)
8- Problem in transmitter
mRel.PS.RF mRel.PS.RF.U 9- Solve RTWP and interference
LSync problem (Uplink demodulation
problem)
10- Change Soft HO parameters (1A,
1B, 1C trigger and/or Filter coef

6- Coverage problem (tilt change, CIO

VS.RAB.Abnor change, …)
mRel.PS.RF.U 7- Indoor coverage, …
8- Increase RLMaxDLPwr.
uNoReply 9- Easier IRAT trigger threshold.
10- Enable Call reestablishment.

VS.RAB.Abnor 4- Coverage problem (tilt change, CIO

mRel.PS.RF.S change, …), indoor coverage, …
5- Easier IRAT trigger threshold
RBReset
6- Enable Call reestablishment

NOVATEL_IT_Algeria_Internal_Document_V032016
VS.RAB.Abnor 7- Coverage problem (tilt change, CIO RNO_Departement
mRel.PS.RF.T change, …), indoor coverage, …
8- Easier IRAT trigger threshold
RBReset 9- Enable Call reestablishment
End
 Start

VS.MultiRA
B.CSAbnor False
mRel.CSPS
important

True

1- Check if multifrequency
Main problem strategy is respected
2- Check interfreq and intrafreq
happens in Frequency relations neighboring (go to
3 (discontinuous related document)
3- Change compressed mode
coverage)
triggers to make easier HO.

1- The switch for CS service

triggers P2D state transition
when UE processing PS BE
services
2- Change bearer channel type
and access rate of PS BE
services is DCH0K or DCH8K.

1- Limit the uplink PS BE services

on the DCH in the CS+PS
combined services
2- Limit the upper limit of uplink
DCH rate in CS+PS combined
services

3- Limit the Downlink PS BE

services on the DCH in the
CS+PS combined services
4- Limit the upper limit of
Downlink DCH rate in CS+PS
combined services

End

NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement