WCDMA KPI

Troubleshooting
- Retainability
 RETAINABILITY CALCULATION COUNTERS

DCR VOICE (%) :

=100*(sum(pmNoSystemRabReleaseSpeech)/sum(pmNoSystemRabReleaseSpeech)+
sum(pmNoNormalRabReleaseSpeech))
DCR VIDEO (%) :
=100*(sum(pmNoSystemRabReleaseCs64)/sum(pmNoNormalRabReleaseCs64)+
sum(pmNoSystemRabReleaseCs64))

DCR PS/R’99 (%) :

=100*(sum(pmNoSystemRabReleasePacket-pmNoSystemRabReleasePacketUra-
pmNoSystemRbReleaseHs)/sum(pmNoNormalRabReleasePacket+pmNoSystemRabReleasePacket-
pmNoNormalRabReleasePacketUra-pmNoSystemRabReleasePacketUra+pmChSwitchSuccFachUra-
pmNoSystemRbReleaseHs-pmNoNormalRbReleaseHs+ pmNoSuccRbReconfPsIntDch+
pmUpSwitchFachHsSuccess))
DCR HSDPA (%) :
=100*(sum(pmNoSystemRbReleaseHs)+sum(pmNoSystemRabReleasePsStreamHs)/
sum(pmNoSystemRbReleaseHs)+sum(pmNoSystemRabReleasePsStreamHs)+
sum(pmNoNormalRabReleasePsStreamHs)+sum(pmNoNormalRbReleaseHs)+
sum(pmNoSuccRbReconfPsIntDch)+sum(pmPsIntHsToFachSucc))
DCR EUL (%) :
=100*(sum(pmNoSystemRbReleaseEul)/(sum(pmNoSystemRbReleaseEul)
+sum(pmNoNormalRbReleaseEul)+sum(pmNoSuccRbReconfOrigPsIntEul)+sum(pmPsIntHsToFachSucc))
FLOW CHART - VOICE CALLS
 Retainability Analysis
 Retainability counters :
 pmNoNormalRabReleaseSpeech: Number of normal releases of any CS
Conversational Speech RAB (Speech)
 pmNoSystemRabReleaseSpeech: Number of system-initiated releases of CS
Conversational Speech RABs (Speech drops)
 pmNoNormalRabReleaseCs64: Number of normal RAB releases for the CS
Conversational 64 kbps (Video call)
 pmNoSystemRabReleaseCs64: Number of system-initiated releases of CS
Conversational 64 kbps (Video call drop)
 pmNoNormalRabReleasePacket: Number of normal releases of PS Interactive RABs
(PS)
 pmNoSystemRabReleasePacket: Number of system-initiated releases of PS Interactive
RABs (PS drops)
 pmNoNormalRbReleaseHs: Number of normal RAB releases for the PS Interactive
RAB mapped on HS-DSCH (HS)
 pmNoSystemRbReleaseHs: Number of system-initiated releases of PS Interactive
RABs mapped on HS-DSCH (HS drop)
 pmNoNormalRbReleaseEul: Number of normal RAB releases for the PS Interactive
RAB mapped on E-DCH/HS-DSCH
 pmNoSystemRbReleaseEul: Number of system-initiated releases of PS Interactive
RABs mapped on E-DCH/HS-DSCH
 POSSIBLE Drop reasons & RELATED counters

Drop Reasons Counters to be monitored

Drops due to Neighbors
Drops due to Soft handover
Failures
Drops due to Uplink Sync
Drops due to Congestion
pmNoAttOutIratHoSpeech-pmNoSuccessOutIratHoSpeech-
IRAT Drops
pmNoSystemRabReleaseSpeech-pmNoSysRelSpeechUlSynch-
Other Reasons Drops
Overshooting
RTWP
Cell Availability
Alarms/Transmission/
HW Issues
pmNoSysRelSpeechNeighbor
pmNoSysRelSpeechSoHo
pmNoSysRelSpeechUlSynch
pmNoOfTermSpeechCong
pmNoFailOutIratHoSpeechReturnOldChPhyChFail-
pmNoFailOutIratHoSpeechReturnOldChNotPhyChFail-
pmNoFailOutIratHoSpeechUeRejection
pmNoSysRelSpeechSoHo-pmNoSysRelSpeechNeighbor-
pmNoOfTermSpeechCong-IRAT Drops
pmPropogationDelay
pmSumUlRssi, pmSamplesUlRssi
pmCellDowntimeAuto, pmCellDowntimeMan
CM & FM Dumps
 Missing nbr Trouble shooting
 Missing Neighbor Drop :

 Check neighbor cell availability.

 Add suggested Neighbors cell with WNCS/GPEH/Drive Test data.

 Analyze existing neighbors with 3G-3G cell relation report.

 Analyze cell coverage by RF Planning tool /Drive Test data Plots.

 Check Propagation Delay to detect & down tilt the overshooting cells.
 Missing nbr Trouble shooting (ConD)
 Typical WNCS Report

Huge Number of Attempts can observed and also

having good RSCP and EcNo. So need to add these
missing neighbours.

Releaseconnoffset=120=12dB
 sho Trouble
 Soft Handover Drop :
shooting
 Check Target RBS HW Alarms like &
DUW Faulty
DUWFaultyAlarm

Sync Alarms
“Synch Reference Path HW Fault Synchronization=1 (clock_synchronisation_problem)”

 Power, Code & CE Congestion in the Target cell to be checked

 Check Transport Alarms like

“NBAP Dedicated Signaling Bearer down - NBAP Common Signaling Bearer down”

 Check Target Cell Availability

 Verify for Primary Scrambling Code Clash

 Selection Priority of the Target Cell in the source NBR list

- Details provided in the Slide No - 13.
SHO Trouble shooting
sho Trouble shooting
 Handover counters :

 pmNoTimesRlAddToActSet: Number of times that a radio link was added to the active set of
a UE or replaced in the active set of a UE
 pmNoTimesCellFailAddToActSet: Number of times that a cell could not be added to the
active set of a UE
 pmNoRlDeniedAdm: Number of radio link setup or addition requests denied by admission
control
 NBR Priority
 Selection Priority – Planning : Example
 ulsync Trouble shooting
 Uplink Sync Drop :

 Investigating the UE TxPwr by WMRR.

 Analyze cell coverage by Propagation delay counter.

 Check UL-RSSI issues.

 Parameter tuning like rlFailureT & nOutSyncInd as mentioned in the Slide No: 15.
 ulsync parameter recommendation
(contd)

PARAMETERS FOR TUNING

 To Reduce Drops due to UlSynch, can tune the parameters " rlFailureT " and
“nOutSyncInd "
 For eg: A Cell is tuned with rlFailureT ( from 10 to 50) and nOutSyncInd (from 10 to 50)
has shown a 20% improvement in Speech Drop Rate

• - Ref – Retainability & Accessibility Improvements - 144/100 56-HSD 101 02 Rev B 2012-12-05
Irat Retainability Analysis
 IRAT Drop :

 Neighbor list optimization.

 GSM coverage area verification for IRAT neighbors.

 Consistency check for external GSM cell (BSIC, BCCH, LAC, CI…)

 Selection Priority the neighbor list based on distance and attempt.

 Check parameter setting : hoType, qRxLevMin, usedFreqThresh2dEcno,

usedFreqThresh2dRscp
Retainability Analysis (ConTD)
 IRAT counters :
 pmNoDirRetryAtt: Number of attempted outgoing inter RAT handover to GSM due to capacity
reasons
 pmNoDirRetrySuccess: Number of successful outgoing inter RAT handover to GSM due to
capacity reasons
 pmNoAttOutIratHoSpeech: No. of attempted outgoing IRAT HO for speech
 pmNoSuccessOutIratHoSpeech: No. of successful outgoing IRAT HO for speech
 pmNoFailOutIratHoSpeechGsmFailure: No. of failed outgoing IRATs due to GSM allocation
failure
 pmNoFailOutIratHoSpeechReturnOldChPhyChFail: No. of failed outgoing IRATs due to
physical channel failure, where UE returns to present active set
 pmNoFailOutIratHoSpeechReturnOldChNotPhyChFail: No. of failed outgoing IRAT HOs
due to reasons other than physical channel failure, where UE returns to present active set.
 pmNoFailOutIratHoSpeechUeRejection: No. of failed due to rejection by UE
 pmNoOutIratCcAtt: Number of PS IRAT cell change attempts for a UE on dedicated
channels.
 pmNoOutIratCcSuccess: Number of successful PS IRAT cell change attempts for a UE on
dedicated channels.
Irat Retainability Analysis(CONTD)
PARAMETERS FOR TUNING – (UsedFreqThresh2dRscp)
 GPEH analysis shown IRAT Drops were happening in Weaker Coverage Area.
 In site VIEUX_LILLE_NORD_TEMP_U11 having high number of drop. After the
implementation of the CR_81 on 31st on Oct the drop rate is reduced.

CR Implemented

Parameter (usedFreqThresh2dRscp )value change (-112

to -109)
 Speech congestion drop analysis
 Congestion Drop :
 Investigate the ASU failure due to lack of DL Power, Codes & CE.

 Perform analysis of coverage area and reduce overshooting.

 Check available CE on RBS (UL/DL).

 Check CE usage and HW allocation.

 Check if Multi-RAB Drop is Seen – If so check the PCI/PVI settings in the SGSN

 Check for the No. of Simultaneous Users License in the RNC

 Other drops analysis
 Other Drop :
 L1, L2 & L3 Timer Expiry (RLC Unrecoverable Errors)

 Poor EcNo or Pilot pollution.

 Transport Issue.

 RBS / RNC HW issue.

 UE Model / SW Specific Issues.

- Moniq/GPEH Translator can be used for further Investigation

 OTHER
 Typical GPEH Report
drop analysis (ConD)
 Case study 1 – Individual offset Tuning
Individual Offset (WCDMA)
– Used in UE function event reporting. This offset is added to the measured quantity before the UE evaluates if an event has
occurred.

Individual Offset was changed from 0dB (default) to 5dB (Target cell) in order to help the SHO to trigger early (active set update)
and overcome abrupt drop. Speech Traffic had also increased in this sector what helped to have more attempt samples.

Changing the
“individualOffset” from
“0dB” to “+5dB”at target cell
SHO attempts will be
increased from all
neighbouring cells towards
the target cell, we are
increasing the SHO boundary
of the target cell.

KPIs to be monitored:
• SHO
• CE Utilization
• Traffic and Admission
rejections
 Case study 2 – minpwrmax Tuning

minPwrMax defines the minimum relative

power for maximum downlink power mapping
for resource estimation. (Maximum
transmission power per
RL)
It is a cell parameter that defines the
maximum power per Radio Link relative to the
Primary Common Pilot Channel (CPICH) power
where Radio Link bit rates are equal to or
below minimumRate [15.9 kbps].
Current Settings
minPwrMax for Speech = 0
Proposal:
minPwrMax = 30

Note:
• After increasing MinPwrMax some cells showed blocks due to lack of downlink power. Improved by increasing
Power Admission parameter values.
• No major impact in CSSR KPI at cell level .
Case study 2 – minpwrmax Tuning
 Case study 3 – HSDSCHINACTIVITYTIMER Tuning
While the UE is on the High Speed Downlink Shared Channel (HS-DSCH), throughput is monitored on the uplink and
downlink. If the throughput on both the uplink and downlink is 0 kb/s for the configurable parameter hsdschInactivityTimer
seconds, the UTRAN sends an Iu Release Request to the Core Network and the UE is sent to Idle Mode. Any active PDP
Context is maintained.

Note:
After we change the
hsdschInactivityTimer from 30s to 10s on
Nov 17th, the PS drop call rate(whole RNC
level) decreased greatly from about 5% to
2 %.
After hsdschInactivityTimer
change from 30 to 10s
 Case study 4 – minPwrRl Tuning
Minimum power per radio link.
Dependencies: minPwrRl <= minPwrMax
Disturbances: Changing this attribute may affect ongoing traffic.
Whenever its value is set, the cell is disabled automatically and then re-enabled.
Change takes effect: Object disabled/enabled
Unit: 0.1 dB
Range: -350 to 150, Default=-150
 Supervision of UE in Cell FACH/URA_PCH state

In Cell_FACH state, the supervision is provided by monitoring periodic Cell Update messages sent by the UE. In URA_PCH state periodic URA
Update messages are sent instead. The timer cchWaitCuT is started in the RNC whenever the UE enters the Cell_FACH or URA_PCH state.

A. If the UE does not receive a Cell Update Confirm it will repeat the Cell Update message a number of times before it moves to idle mode.

B. If the UE detects “Out of service area” it waits for a period of time before it moves to idle mode.

C. Upon expiry of the timer cchWaitCuT the overall release of the connection shall be triggered and as a result the UE context is released in
WCDMA RAN. The time set on the timer cchWaitCuT is longer then the time set on timer t305 – that indicates how often the UE has to send
a Cell Update message when in state CELL_FACH and how often to send URA Update message when in state URA_PCH.

cchWaitCuT=9=45min
T305=3=30min
 Supervision of UE in Cell DCH state

he Radio Connection Supervision functionality is provided by means of two different algorithms; the Radio Link Set Supervision algorithm
(in the RBS) and the Radio Connection Supervision Evaluation algorithm (in the SRNC).

Radio Connection Supervision (RCS) Evaluation : The Radio Connection Supervision Evaluation algorithm keeps track of the synchronization
status of the whole radio connection by assigning a tag to every RLS.

Radio Link Set (RLS) Supervision : The RLS Supervision function supervises the synchronization status of the RLS provided by the RBS to the
radio connection, and reports any changes to the SRNC. When nOutSyncInd number of consecutive frames are out-of-sync a timer rlFailureT
is started and at expiry the RLS is considered out-of-sync and Radio Link Failure is reported to the SRNC. When the RLS is out-of-sync and a
number of frames are in-sync, the RLS is considered in-sync and Radio Link Restore is reported to the SRNC
 RLS Supervision in UL

The RLS is considered unsynchronized whenever too many (=nOutSyncInd) consecutive frames are
indicated as out-of-sync. When an RLS is considered unsynchronized the timer rlFailureT starts and
the UE enters state “Wait”. If the RLS re-establishes synchronization before the timer rlFailureT
expires, then the timer is stopped and the UE re-enters state “In-sync”. If not, upon expiry, the
RLS Supervision algorithm sends a RL failure indication to the SRNC and the UE enters state “Out-of-
sync”. Whenever the UE gets back into “In-sync” from “Out-of-sync” a RL restore indication is sent
to the SRNC.

nOutSyncInd=10
rlFailureT=10=1s
 RCS Evaluation in SRNC

This algorithm keeps track of the synchronization status of the radio connection by assigning a tag
to every RLS. Upon creation of a new RLS the tag is set to "Fail". The tag is shifted to "OK" upon
reception of a RL restore indication and then to "Fail" upon reception of a RL failure indication. If all
RLSs are tagged as "Fail" and the timer dchRcLostT has expired, then the radio connection shall be
considered lost and the overall release of the connection is triggered
hsdschRcLosT timer starts for HSDPA calls.

dchRcLostT=90=9s
hsDschRcLostT=90=9s
 L1 Timer (UE side)

N313(100) : number of consecutive “out of sync” after that Ue starts t313 “Out of sync” generation is
Ue dependant, generally when the Ue measures a SIR < target SIR.
(the SIR is measured according to a sliding window of 160 ms)
According to specification Ues switches off the transmitter when is “out of Sync”.
T313 (3s): After n313 consecutive “out of service”, the UE starts T313 and doesn’t stop it doesn’t
Measure an “in Sync” that is SiR> SIR Target
N315: number of consecutive “in Sync” for the Ue to stop T313 and the Radio Link Failure Procedure
Total time RNC = nOutSyncInd * 10 ms + rlFailureT + dchRcLostT
Total time UE = N313 * 10 ms + T313
After this timer expiry the call is dropped
 L1 Timer (proposed value)
• Actual TELECOM Settings:
N313=100
T313=3
DL Radio Link Failure = 3 (sec) + 100*10 (ms) = 4 seconds.
This means that after 4 seconds Ue exits the DCH state to Idle; there is no possibility to recover the
call for the RNC.
• For Radio Link Failure in uplink Telecom has the DchRcsLost=100 (10sec) and RLfailureT=1 (sec)
That means UL Radio link Failure= DchRcsLost+ RLfailureT= 11 seconds.
So uplink and downlink Radio Link Failure timers are unbalanced
It is recommended to align them
Proposed values
DchRcsLostT = 60 (6 sec)
T313 = 6 sec
So UL and DL need to be balanced: suggestion to 7 seconds total supervision
 Case study 4 – t313
T313 - To give UE to have more possibilities in order to become in sync for downlink by increasing t313 timer.

T313 – 3secs

T313 – 7secs