Scribd Download - Com - Umts Performance Trouble Shooting and Optimization Guideline

UMTS RAN Performance
Trouble Shooting Guidelines

Ericsson UMTS Retainability
Performance Engineering
UMTS RAN Performance Trouble Shooting Guidelines Ericsson UMTS Retainability
Introduction
Purpose & Scope
The intent of this document is to provide UMTS Trouble Shooting and
Optimization from KPI and Counter perspectives for Ericsson (E///) Retainability
and provide detailed analysis strategies for identifying reason for the KPI trends
and offering guidelines for improving performance by Key Optimization
techniques.
The KPI/Counters described here are applicable to the Ericsson UTRAN.
This document is not all inclusive and is only intended to provide a quick cook
book to understand available E/// for trouble shooting and optimization best
practices Guideline Document. For any information not covered here, the
Ericsson product documentation (CPI/ALEX Libraries) should be referenced.
1.1. Definitions for this Document
Term or
Definition
Acronym
3GPP Third Generation Partnership Project
AS Active Set
BSIC Base Station Identity Code
BTS Base Transceiver Station
CN Core Network
CPICH Common Pilot Channel
DCH Dedicated Channel
DL Downlink
DPCCH Dedicated Physical Control Channel
DPCH Dedicated Physical Channel
DRNC Drift Radio Network Controller
FACH Forward Access Channel
FIFO First In First Out
GERAN GSM EDGE RAN

Term or
Definition
Acronym
Global System for Mobile
GSM Communications
HCS Hierarchical Cell Structure
HSDPA High Speed Data Packet Access
IAF Intra Frequency
IE Information Element
IEF Inter Frequency
IFHO Inter Frequency Handover
Inter-RAT Inter Radio Access Technology
IRAT Inter Radio Access Technology
Iur Interface between two RNCs
KPI Key Parameter Indicator
LA Location Area
LAI Location Area Indicator
MO Managed Object
NBAP Node B Application Part

Logical node responsible for radio
transmission and reception in one or
Node B several cells
OCNS Orthogonal Channel Noise Simulator
PLMN Public Land Mobile Network
RA Routing Area
RAB Radio Access Bearer
RAI Routing Area Indicator
RAN Radio Access Network
RAT Radio Access Technology
RB Radio Bearer
Term or
Definition
Acronym
Radio Base Station another name
RBS for the Node B
RF Radio Frequency
RL Radio Link
RNC Radio Network Controller
RRC Radio Resource Control
RSCP Received Signal Code Power
RSSI Received Signal Strength Indicator
SIB System Information Block
SIR Signal to Interference Ratio
TRX Transceiver
TX Transmit
UE User Equipment
UL Uplink
Universal Mobile Telecommunication
UMTS Services
UMTS Terrestrial Radio Access
UTRAN Network
Wideband Code Division Multiple
WCDMA Access
Retainability
Retainability is defined as the ability of a user to retain its requested service once
connected for the desired duration. The metrics within the Ericsson RNC and OSS
provide counters and KPIs that describe the behaviors and experience of the
subscribers on the UMTS network.
This is divided up into a number of areas, CS and PS, as well as being divided on an
RRC and RAB basis.
The main items which affect retainability on the UMTS network include:
Handover performance (soft/softer/Iur/IRAT) and missing neighbour cell
UL/DL imbalance
Incorrect parameter settings (power, admission, release)
Congestion
Radio environment impact (corner effect, fast Ec/No drop, Pilot pollution
etc)
Node Hardware failure
T1 Congestion
The services which have counters for retainability are:
CS Voice
CS Data
Video
PS Streaming
PS Interactive
HSDPA
EUL (HSUPA)
In the following sections, CS Voice, PS Interactive and HSDPA will be discussed in
detail.
Troubleshooting Flowchart
The following flowchart may be useful for troubleshooting the voice drop issues
based on the problem areas
Flow chart in PowerPoint

Ericsson
Retainability flowchart.ppt
CS Voice RAB Retainability

The metrics for CS Voice RAB Retainability are the most extensive of the UMTS
Services in the Ericsson OSS. These metrics can be run on an RNC/Market level or
on a cell level.
The main report for identifying and troubleshooting retainability .This contains the
Drop Rate and Drop Reason counters that will be discussed. For drops during the
IRAT procedure, the 3G-2G Relation report can also be used to identify the IRAT
Drops.
The KPI for Voice is the Voice RAB Drop Rate %. This is made up of the following
counters:
Counter Description Condition MO Class

pmNoSystemRabReleaseSp Number of This counter is only increased UtranCell
eech successful due to a RANAP Iu Release
system RAB Command or RAB Assignment
releases Request message with release
(Speech) cause = anything except
referred to Normal Release, Successful
the Best Cell Relocation, Resource
in the Active Optimisation Relocation, User
Set. Inactivity or release-due-to-
UE-generated- signaling-
connection-release. This
counter is incremented for the
best cell in the Active Set in the
SRNC.
pmNoNormalRabReleaseSpe Number of This counter is only increased UtranCell
ech successful due to a RANAP Iu Release
normal RAB Command or RAB Assignment
releases Request message with release
(Speech) cause = Normal Release,
referred to Successful Relocation,
the Resource Optimisation
Best Cell in Relocation, User Inactivity or
the Active release-due-to-UE-generated
Set. signaling- connection-release.
This counter is incremented for
the best cell in the Active Set in
the SRNC.
The KPI is defined in T-PIM shows the percentage of system/abnormal RAB releases
over the total number of RABs. It is defined as follows:
pmNoNormalRabReleaseSpeech
VoiceRABDr opRate (%) 100 * [1 ]
pmNoSystemRabReleaseSpeech pmNoNormalRabReleaseSpeech
In the Ericsson RNC, there are also counters that breakdown some of the RF Drop
Reasons (Other than IRAT) to aid the troubleshooting of issues. The counters for
Voice Drop reasons are:

pmNoSysRelSpeechSoHo Number of Network initiated call release of UtranCell
system speech calls due to inability to
disconnects include a non-valid or valid cell
of a speech in the active set. The counter
call for the shall be incremented for the
best cell in best cell in the active set prior
the active set to the call release.
due to Soft Note: This counter is only
Handover incremented in the SRNC.
action.
pmNoSysRelSpeechNeighbr Number of Network initiated call release of UtranCell
system speech calls due to inability to
disconnects include a non-valid cell in the
of a speech active set. The counter shall be
call for the incremented for the best cell in
best cell in the active set prior to the call
the active set release.
due to
unknown
measured
cell (missing
neighbor
relation).
pmNoSysRelSpeechUlSynch Number of Incremented if the timer UtranCell
system dchRcLostT expires and the
disconnects RAB type is a CS
of a speech Conversational Speech 12.2
call for the Kbps RAB. Note that the
best cell in counter is applicable for CS
the active set Speech RAB and for Multi- RAB,
due to lost that is, the counter will be
UL synch. stepped if the released RAB is a
multi-RAB including a CS
Conversational speech RAB
Note: This counter is only
incremented in the SRNC.
pmNoOfTermSpeechCong Number of The counter is increased when UtranCell
speech Radio a UE using the speech service
Connections is released due to cell
served by congestion. The counter is
this RNC increased in CRNC for non-
terminated drifting UEs for the one cell
due to with congestion.
congestion
The counters for Soft Handover and Neighbours can be used to determine the drops
caused by Radio Link Addition failure (SHO Failure). This is typically due to site
issues or T1 issues causing a failure to add a Radio Link on this SHO leg.
These counters can be used in conjunction with the IRAT Drop calculation to
determine the breakdown of drops on the RNC/Market or Region level. The IRAT
Drops are given by the following formula:
IRAT Drops (c) = pmNoAttOutIratHoSpeech -pmNoSuccessOutIratHoSpeech-

pmNoFailOutIratHoSpeechReturnOldChPhyChFail
-pmNoFailOutIratHoSpeechReturnOldChNotPhyChFail-
NoFailOutIratHoSpeechUeRejection
The raw counter descriptions for these are below.

pmNoAttOutIratHoSpeech Number of The counter is GsmRelati
attempted outgoing increased when on
(to GSM) inter-RAT RNC sends
handover for "HANDOVER FROM
Conversational UTRAN COMMAND".
speech RAB. The This counter will
counter is stepped only be
for the best cell in incremented in the
the active set but SRNC.
only if that cell has
a cell relation
towards the target
cell. If the best cell
in the active set has
no cell relation
towards the target
cell, the counter is
not stepped.
pmNoSuccessOutIratHoSpeech Number of The trigger is when
GsmRelati
successful outgoing IU RELEASE
on
(to GSM) inter-RAT COMMAND is
handover for received with cause
Conversational Normal release or
speech RAB. The Successful
counter is stepped relocation and
for the best cell in based on the CS
the active set but RAB state. This
only if that cell has counter will only be
a cell relation incremented in the
towards the target SRNC.
no cell relation
towards the target
not stepped.
pmNoFailOutIratHoSpeechReturn Number of failed The trigger is the
GsmRelati
OldChPhyChFail outgoing (to GSM) reception of
on
inter-RAT handover "HANDOVER FROM
due to UTRAN FAILURE"
physical channel with Inter-RAT
failure, where the handover failure
UE returns to the cause=Physical
present Active Channel Failure and
Set for based on the CS
Conversational RAB state. This
speech RAB. The counter will only be
counter is stepped incremented in the
for the best cell in SRNC.

the active set but
only if that cell has
a cell relation
towards the target
no cell relation
towards the target
not stepped
pmNoFailOutIratHoSpeechReturn Number of failed The trigger is when GsmRelati
OldChNotPhyChFail outgoing (to GSM) "HANDOVER FROM on
inter-RAT handover UTRAN FAILURE" is
due to received with inter-
reasons other than RAT handover
physical channel failure cause=any
failure, where the other cause apart
UE returns to the from Physical
present Active Set channel failure or
for Conversational configuration
speech RAB. The unacceptable, and
counter based on the CS
is stepped for the RAB state. This
best cell in the counter will only be
active set but only if incremented in
that cell has a the SRNC.
cell relation towards
the target cell. If the
best cell in the
active set has
no cell relation
towards the target
not stepped
pmNoFailOutIratHoSpeechUeReje Number of failed The trigger is when GsmRelati
ction outgoing (to GSM) "HANDOVER FROM on
inter-RAT handover, UTRAN FAILURE" is
rejected by received with inter-
UE, for RAT handover
Conversational failure
speech RAB. The cause=configuratio
counter is stepped n
for the unacceptable, and
best cell in the based on the CS
active set but only if RAB state. This
that cell has a cell counter will only
relation towards be incremented in
the target cell. If the the SRNC
best cell in the
active set has no
cell relation
towards the target

not stepped
Drop Breakdown
These metrics can be used to determine the breakdown of drops on an RNC, Market
or Region level and can be shown as follows.
The Other Drops shown in the chart represent the drop causes which cannot be
tagged with a specific reason for the drop. This represents:
Other Drops = Total Voice Drops Voice Drops with a defined Reason
This chart provides an overview of the areas to concentrate the performance

analysis for the network.
MOU Per Drop

The other metric which is important to monitor is the MOU Per Drop (MPD). This
gives a measure of the Customer Experience on the network.
This is given by:
MOU Per Drop = Minutes of Use [Derived from Erlangs] / Total Number of Voice
Dropped Calls
As expected, as the drop rate decreases, the MPD will increase.
Iur Drops
When more than one RNC is used to serve a particular area, drops may occur when
the user travels between the area served by one RNC to the area served by the 2 nd
RNC over the Iur boundary. These can be seen in the retainability Iur report which
can be broken down by Iur Link MO. This metric uses the same counter names as
the Drop Rate metric but on an Iur MO.
As can be seen from the graph above, the Iur Drop Rate is higher than the overall
RNC Drop Rate and the number of samples is much lower.
Other Metrics/Counters
Other counters which are included in the report which may be useful in
troubleshooting on an RNC level are:

pmNoReleaseDchRcLostT Number of overall When the RBS Rcs
release triggered by detects loss of UL
dchRcLostT expiry synchronization for
an RL Set in a Radio
Connection it will
send the Radio Link
failure
Indication message
to the RNC. If all
RLs have failed the
timer
dchRcsLost is
started. When the
timer expires the
Radio Connection
is considered lost
and the counter is
increased.
The counter is
never incremented
in relation to a
successful or a
failed

Cell_DCH to IDLE
Transition. However,
this does not apply
to cases when RCS
failure is the actual
trigger of CELL_DCH
to idle transition
pmNORlcErrors Number of RLC An RLC Rcs
unrecoverable error unrecoverable error
(UTRAN) for UEs on in RNC L2 initiates
FACH or the IU Release
DCH procedure. The
counter is
increased.
NOTE: The counter
is not stepped for
L2 errors in the UE.
The UE
shall send Cell
Update with RLC
Error in that case.
These counters are active in the Radio Connection Supervision (RCS) Subsystem.
Drops Due to Missing Neighbours (Invalid Neighbours)

When analysis is completed for Missing Neighbours for a cell, both the WNCS/GPEH
Missing Neighbour tool and Drive Test Coverage analysis should be used. Existing
neighbours should also be optimized using the RL Addition counters in the 3G-3G
Report. The following steps are a suggestion for troubleshooting (Effect on the
surrounding sites must also be taken into account):
1. Ensure that during the period the missing neighbours were pegged that
surrounding sites were not off air creating a coverage hole and false missing
relations.
2. Addition of suggested neighbours by WNCS/GPEH (Including deletion of
unused neighbours if required) if deemed valid
3. Analysis of existing neighbours on cell
4. Analysis of coverage area of cell (Problem Cell and Proposed Neighbour) and
Target Cells using the Planning Tool, existing drive tests or by performing new
drive tests
5. Perform Downtilts and other physical optimization as required
After these steps are performed, monitoring should continue on a cluster of cells
around the affected cell to determine the performance improvement.
Drops Due to RL Addition Failures (Valid Neighbours)

When a large number of Radio Link Addition failures are detected on a cell/RBS, this
may highlight a problem with the transport network (T1s, IMA Groups) or Hardware
issues.
This metric is developed from two of the available metrics in the Retainability
Report:
Voice Drops due to Missing Neighbor
Voice Drops due to inability to add Neigh to AS
RL Addition Failure Drops = Inability to Add to AS Missing Neighbour
Drops
The following steps are a suggestion for troubleshooting:
1. Check for alarms on the site for Hardware Issues
2. Check the T1 Errors on the site
3. Check the Cell Availability (Auto Downtime) on the cells. This may cause
these issues if the PICH radiates while the cell is locked down
4. Determine if the issue affects only one cell or a RBS or a cluster of Sites
This issue should be dealt with in the normal T-Mobile process for T1s and hardware
issues. After these steps are performed, monitoring should continue on a cluster of
cells around the affected cell to determine the performance improvement.
Drops Due to UL Sync

UL Synchronization drops are difficult drops to define the exact reason for the drop.
The algorithms that cause the counter to be incremented are:
1. Supervision of radio link synchronization status
2. Supervision of RLC protocol (Layer 2 failures)
3. Supervision of connections on common channels
This can be a symptom of lack out of UL or DL coverage or high UL Interference. The
following steps are a suggestion for troubleshooting:
1. Using Drive Tests (Existing or New)and W-MRR, investigate the UE Tx Power
for high values
2. Check the parameters for the Max UE Tx Power and maxSir values
3. Analysis of coverage area of cell (Problem Cell and Proposed Neighbour) and
Target Cells using the Planning Tool, existing drive tests or by performing new
drive tests
4. Use of GPEH event (INTERNAL_MEASUREMENT_HANDLING_ EVALUATION) to
determine the number of Event 6a occurrences to determine UE Reports on
Max Tx Power or number of Event 2d occurrences to determine reported EcNo
in a cell
Drops Due to IRAT

This cause is determined by calculation using a number of counters from the
Mobility report. Issues with IRAT Drops may show an issue with the defined
neighbours for the cell. These include:
Incorrect Prioritization
Neighbour List too long (Too long in compressed mode searching for
neighbours)
The following steps are a suggestion for troubleshooting:
1. Neighbour List cleaning/deletion based on Relation Usage counters to reduce
the search time/time in compressed mode
2. Coverage area verification for IRAT Neighbours
3. Re-prioritization of Neighbour Relations based on usage
Drops Due to Congestion

This cause is related to a lack of Hardware or Software licenses on the RBS Base
Band or to interference. It uses Power and UL RTWP measurements to resolve the
overload in the Uplink and Downlink. The following steps are a suggestion for
troubleshooting:
1. Check the downswitch counters for congestion reasons determine whether
the issue is in the UL or DL
2. Investigate the RRC Accessibility Failures due to Lack of DL Power and Lack of
Channelization Codes
3. Perform analysis of the coverage area and reduce overshooting
4. Verify the CE Usage and HW Allocation and dimensioning with the BSS Team
Miscellaneous Drops
These drops are the remaining drops that cannot be accounted for in the drop
reasons outlined above. There are a number of reasons for these and the drops with
defined reasons above should be actioned first. Some of the causes for the drops
include:
1. Transport Issues (T1s etc)
2. Hardware Issues
3. RF Issues outside of the previously mentioned counters
4. UE Issues
Some of the corrections for the previous issues will aid the remedy of these
Miscellaneous/Other drops. For further investigation of the drop causes, GPEH, CTR and
the Tektronix K-18 tools should be used to determine the reason behind the drop.
CS Voice RRC Retainability

The metric for CS Voice RRC Retainability is only made up of 2 counters. This
metrics can be run on an RNC/Market level or on a cell level. The counters are
below:

pmTotNoRrcConnectReqCsS Total number The counter is increased when UtranCell
ucc of Successful an RRC Connection Setup
Conversation Complete message is received
al Call following an attempt to setup
(originating an originating or terminating
and conversational call.
terminating)
and
Emergency
Call RRC
Connection
attempt.
pmNoSpeechDchDiscAbnor Number of The counter is only increased UtranCell
m abnormal for the speech RAB, that is the
disconnect of conversational/speech 12.2
a speech call Kbps RAB". The counter is only
for the Best increased when the RRC
Cell in the Connection is released with the
Active Set.. RRC Connection Release
command with "release cause"
= anything but normal event
or user inactivity or Directed
Signalling Connection Re-
establishment. In case of
multi-RAB or multi signaling
connection, the RRC
Connection will remain after
that the signaling connection or
RAB to one CN have been
released and therefore the
counter is not be increased.
The counter is only increased
the first time the RRC
Connection Release is sent to
the UE. (The RNC may transmit
several RRC messages to
increase the probability of
proper reception of the
message by the UE).
pmNoSpeechDchDiscAbnorm
VoiceRRCDr opRate(%) 100 * [ ]
pmTotNoRrc ConnectReqCsSucc
These metrics can be investigated in the same way as the RAB Drops.
PS Interactive RAB Retainability

The KPI for PS Interactive is the PS Interactive RAB Drop Rate %. These metrics can
be run on an RNC/Market level or on a cell level. This includes the HSDPA RABs as
well as PS R99 RABs.
The main report for identifying and troubleshooting retainability issues in T-PIM is
the Retainability Report. This contains the Drop Rate and Drop Count.
This is made up of the following counters:

pmNoNormalRabReleasePac Number of This counter is only increased UtranCell
ket successful due to a RANAP Iu Release
normal RAB Command
releases (PS or RAB Assignment Request
Data) for the message with release cause
best cell =
in the active Normal Release, Successful
set. When Relocation, Resource
releasing a Optimisation
HS RAB, this Relocation, User Inactivity or
counter is release-due-to-UE-generated-
stepped signalling-connection-release.
for the It is for the Best Cell in the
Serving HS- Active Set
DCH cell and when releasing a HS RAB,
this counter is stepped for the
Serving
HS-DCH cell.
pmNoSystemRabReleasePac Number of This counter is only increased UtranCell
ket successful due to a RANAPIu Release
system RAB Command or RAB Assignment
releases (PS Request message with
Data) for the release cause = anything
best cell except Normal Release,
in the active Successful
set. When Relocation, Resource
releasing a Optimisation Relocation, User
HS RAB, this Inactivity or
counter is release-due-to-UE-generated-
stepped signalling-connection-release.
for the This
Serving HS- counter is incremented for the
DCH cell best cell in the Active Set in the
SRNC
and when releasing a HS RAB,
this counter is stepped for the
Serving
HS-DCH cell
pmNoSystemRabReleasePacket
PSInterRABDropRate (%) 100 * [ ]
pmNoSystemRabReleasePacket pmNoNormalRabReleasePacket
There are no IRAT Drop Counters for PS Interactive so a useful metric is the PS
Interactive IRAT Failure Rate (%).
pmNoOutIratCcSuccess
PSInterRAB _ IRAT _ Failure (%) 100 * [1 ]
pmNoOutIratCcAtt
The raw counter descriptions for these are below.

pmNoOutIratCcReturnOldCh Total number of the Inter-RATCC from GsmRelati
PS Inter-RATCC UTRAN to GPRS, UE on
attempts for UE on on DCH. The
DCH where counter is
the UE returns to old increased when the
channel. Cell Change Order
The counter is From UTRAN Failure
stepped for the best (RRC) message is
cell in the active received from the
set, but only if UE
that cell has a cell
relation towards the
target cell. If the
best cell in
the active set has
no cell relation
towards the target
cell, the counter
is not stepped.
pmNoOutIratCcAtt Total number of the Inter-RATCC from GsmRelati
PS Inter-RATCC UTRAN to GPRS, UE on
attempts on DCH. on DCH. The
The counter is Handover
stepped for the best evaluation function
cell in the active triggers this
set, but only if function to indicate
that cell has a cell that we need to
relation towards the make handover to a
target cell. If the GSM cell. (A
best cell in Measurement
the active set has Report message
no cell relation (RRC) for event 3a
towards the target has been received
cell, the counter from the UE). The
is not stepped. counter is
increased when the
Cell Change Order
From UTRAN (RRC)
message has been
sent to the UE.
pmNoOutIratCcSuccess Number of Inter-RAT CC from GsmRelati
successful PS Inter UTRAN to GPRS, UE on
RAT cell change on DCH. The
attempts for UE Handover
on dedicated Evaluation function
channel. The triggers this
counter is triggered function to
by CN Iu Release indicated that we
Command following need to
the sending of the make a handover to
CELL CHANGE a GSM cell (A

ORDER Measurement
FROM UTRAN Report message
message. (RRC) for event 3a
The counter is has been received
stepped for the best from the UE). The
cell in the active Cell Change
set, but only if Order from UTRAN
that cell has a cell (RRC) message is
relation towards the sent to the UE and
target cell. If the the counter
best cell in is increased when a
the active set has Iu Release
no cell relation Command is
towards the target received from the
cell, the counter PS
is not stepped CN, with cause
Normal release or
Successful
Relocation.
The IRAT Drop Rate can be estimated from the following formula:
pmNoOutIratCcAtt - pmNoOutIratCcSuccess - pmNoOutIratCcReturnOldCh
PSInterRAB _ IRATDrop (%) 100 * ]
pmNoOutIratCcAtt
Iur Drops
As in the CS Voice example, where more than one RNC is used, drops may occur
over the Iur Boundary. These can be seen in the retainability Iur report and can be
broken down by Iur Link MO. This metric uses the same counter names as the Drop
Rate metric but on an Iur MO.
As can be seen from the graph above, the Iur Drop Rate is higher than the overall
RNC Drop Rate and the number of samples is much lower. This mirrors the
experience on CS Voice.
These plots should be used as an indication of issues that should be investigated
further on a Cell/RBS basis. Detailed troubleshooting will be included in the Cell
Analysis section.
Cell/RBS Analysis
The Drop Rate and Count metrics can be used on a Cell level also. The Worst
Offenders in an RNC/Market/Region level should be ranked by the following metrics:
PS Interactive Drop Rate
PS Interactive Count (Contribution to Total RNC/Market/Region)
These PS Interactive drops do not have broken down drop reasons similar to the
Voice examples. There are a number of possible reasons for these drops and they
should be investigated like the miscellaneous drops in CS Voice.
2. Hardware Issues
4. UE Issues
Some of the corrections for the Voice drop issues will aid the remedy of these PS
Interactive drops. For further investigation of the drop causes, GPEH, CTR and the
Tektronix K-18 tools should be used to determine the reason behind the drop.
1.2. PS Interactive RRC Retainability

The metric for PS Interactive RRC Retainability is only made up of 3 counters. This
metrics can be run on an RNC/Market level or on a cell level. The counters are
below:

pmNoPacketDchDiscAbnorm Number of The counter is only increased UtranCell
abnormal when the RRC Connection is
disconnects released
of a packet with the RRC Connection
call over DCH Release command with
and "release cause"
E-DCH for the = anything but normal event
Best cell in or user inactivity or Directed
the Active Signalling
set Connection Re-establishment.
In case of multi-RAB or multi
signaling
connection, the RRC
Connection remains after that
the signaling
connection/RAB to one CN have
been released and therefore
the
counter shall not be increased.
The counter is only increased
the first
time the RRC Connection
Release is sent to the UE. (The
RNC
may transmit several RRC
messages to increase the
probability of
proper reception of the
message by the UE).
pmNoCellFachDisconnectAb Number of This counter is only increased UtranCell
norm abnormal when the packet FACH RRC
disconnectio Connection
ns from is released with an RRC
common Connection Release message
channels with
(that is, release cause = anything
CELL_FACH except normal event or user
state). inactivity
or Directed Signalling
Connection Re-establishment.
The counter is
only increased the first time
the RRC Connection Release is
sent
to the UE. (The RNC may

transmit several RRC messages
to increase
the probability of proper
reception of the message by
the UE).
pmTotNoRrcConnectReqPsS Total number The counter is increased when UtranCell
ucc of Successful an RRC Connection Setup
Originating Complete
Interactive message is received following
Call, an attempt to setup Originating
Terminating Interactive Call, Terminating
Interactive Interactive Call, Originating
Call, Background
Originating Call, Terminating Background
Background Call or Originating Subscribed
Call, Traffic
Terminating Call.
Background
Call, or
Originating
Subscribed
Traffic Call
RRC
connection
setups.
pmNoPacketDchDiscAbnorm pmNoCellFachDisconnectAbnorm
PSInterRRCDropRate (%) 100 * [ ]
pmTotNo RrcConnectReqPsSucc
These metrics can be investigated in the same way as the PS Interactive RAB Drops.
HSDPA Data RAB Retainability

The KPI for HSDPA is HSDPA RAB Drop Rate %. These metrics can be run on an
RNC/Market level or on a cell level.
This is made up of the following counters:

pmNoSystemRbReleaseHs Number of The counter is stepped for the UtranCell
successful Serving HS-DSCH cell at
system RAB/RB combination transition
releases of from PS Interactive 64/HS (or
packet RABs 384/HS or EUL/HS) - HS-DSCH
mapped on to SRB-DCH or to Idle mode
HS-DSCH in due to the same reasons as for
the Serving stepping the existing counter
HS-DSCH cell pmNoSystemRabReleasePacket
pmNoNormalRbReleaseH Number of The counter is stepped for the UtranCell
successful Serving HS-DSCH cell at
normal RAB/RB combination transition
releases of from PS Interactive 64/HS (or

packet RABs 384/HS or EUL/HS) - HS-DSCH
mapped on to SRB-DCH or to Idle mode
HS-DSCH in due to the same reasons as for
the Serving stepping the existing counter
HS-DSCH pmNoNormalRabReleasePacket
cell.
pmNoSystemRbReleaseH
HSDPA _ RABDropRat e(%) 100 * [ ]
pmNoSystemRbReleaseH pmNoNormalRbReleaseH
HSDPA MB Per Drop

Another metric, aside from the Drop Rate and Count, which can be monitored, is the
MB Per Drop (MBPD). This gives a measure of the Customer Experience on the
network.
This is given by:
MB Per Drop = MB Downloaded / Total Number of HSDPA Dropped Calls
Cell/RBS Analysis
The Drop Rate and Count metrics can be used on a Cell level also. The Worst
Offenders in an RNC/Market/Region level should be ranked by the following metrics:
HSDPA Drop Rate
HSDPA Count (Contribution to Total RNC/Market/Region)
These HSDPA drops do not have broken down drop reasons. There are a number of
possible reasons for these drops and they should be investigated like the
miscellaneous drops in CS Voice.
2. Hardware Issues
4. UE Issues
Some of the corrections for the Voice drop issues will aid the remedy of these HSDPA
Drops. For further investigation of the drop causes, GPEH, CTR and the Tektronix K-18
tools should be used to determine the reason behind the drop.
2.Configuration Management
Configuration Management tools and methods should also be used in improving
retainability. Some of these items have been discussed already but these include:
Neighbour List Optimization
Counts (3G-3G and 3G-2G)
Removals
Additions
Selection Priority (3G-3G and 3G-2G)
Counter Based Changes to Priority levels
Antenna Changes
Tilts
Azimuths
3.Troubleshooting Tools
The following tools can be used for troubleshooting:
W-NCS
The WCDMA Neighbouring Cell Support (W-NCS) is an Ericsson OSS Tool
which provides suggestions on missing neighbour additions and
neighbour removals
More detail on this tool can be found in ALEX
GPEH
The General Performance Event Handling (GPEH) tool is a feature in the
Ericsson OSS that provides capability similar to a protocol analyzer.
This also has visibility of internal RNC events such as Missing
neighbour etc
This can be run on an RNC level
CTR/Uech
The Call Trace (CTR) tool is a feature in the Ericsson OSS that provides
capability similar to the GPEH Tool
This can be run on a Cell level for specific cell troubleshooting. These
files can be read in Actix
UETR
The User Equipment Trace (UETR) tool is a feature in the Ericsson OSS
that provides capability similar to the GPEH Tool
This is run on a particular IMSI for specific issue troubleshooting,
typically a test SIM attempting to recreate problem conditions. These
files can be read in Actix

Scribd Download - Com - Umts Performance Trouble Shooting and Optimization Guideline

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Scribd Download - Com - Umts Performance Trouble Shooting and Optimization Guideline

Uploaded by

Copyright:

Available Formats

UMTS RAN Performance

Trouble Shooting Guidelines

1.1. Definitions for this Document

3GPP Third Generation Partnership Project

BSIC Base Station Identity Code

BTS Base Transceiver Station

CPICH Common Pilot Channel

DCH Dedicated Channel

DPCCH Dedicated Physical Control Channel

DPCH Dedicated Physical Channel

DRNC Drift Radio Network Controller

FACH Forward Access Channel

FIFO First In First Out

GERAN GSM EDGE RAN

HCS Hierarchical Cell Structure

HSDPA High Speed Data Packet Access

IAF Intra Frequency

IEF Inter Frequency

IFHO Inter Frequency Handover

Inter-RAT Inter Radio Access Technology

IRAT Inter Radio Access Technology

Iur Interface between two RNCs

KPI Key Parameter Indicator

LAI Location Area Indicator

NBAP Node B Application Part

OCNS Orthogonal Channel Noise Simulator

PLMN Public Land Mobile Network

RAB Radio Access Bearer

RAI Routing Area Indicator

RAN Radio Access Network

RAT Radio Access Technology

RNC Radio Network Controller

RRC Radio Resource Control

RSCP Received Signal Code Power

RSSI Received Signal Strength Indicator

SIB System Information Block

SIR Signal to Interference Ratio

Flow chart in PowerPoint

CS Voice RAB Retainability

Counter Description Condition MO Class

Counter Description Condition MO Class

IRAT Drops (c) = pmNoAttOutIratHoSpeech -pmNoSuccessOutIratHoSpeech-

The raw counter descriptions for these are below.

Counter Description Condition MO Class

Counter Description Condition MO Class

Counter Description Condition MO Class

This chart provides an overview of the areas to concentrate the performance

MOU Per Drop

As expected, as the drop rate decreases, the MPD will increase.

Counter Description Condition MO Class

Counter Description Condition MO Class

Drops Due to Missing Neighbours (Invalid Neighbours)

Drops Due to RL Addition Failures (Valid Neighbours)

Drops Due to UL Sync

Drops Due to IRAT

Drops Due to Congestion

CS Voice RRC Retainability

Counter Description Condition MO Class

PS Interactive RAB Retainability

Counter Description Condition MO Class

The raw counter descriptions for these are below.

Counter Description Condition MO Class

Counter Description Condition MO Class