Wcdma kpi OPTIMIZATION

Presented by
Ahmed Aziz
agenda

 DAY 1 WCDMA KPI OPTIMIZATION

– ACCESSIBILITY CS/PS
– RETAINABILITY CS/PS
– MOBILITY
– INTEGRITY
WHY WE MEASURE NW
PERFORMANCE

› To check the cellular network is performing well.

› A set of certain threshold is defined for measuring performance.

› To check the area where improvement required for improving NW/User

perception.

› Future requirement
3g kpi principle --- s.m.a.r.t.
WCDMA RAN Optimization

WCDMA RAN Optimization process can be understood from

following workflow.

Performance Performance Recommendation Verification

Measurement Analysis & Implementation changes
accessibility
Introduction

 Accessibility is defined as the ability of a user to access the

MOC/MTC
UMTS network successfully to utilize the available services.

 The metrics within Ericsson RNC and OSS provide counters

and KPI’s that describe the behaviors and experience of the RRC Setup
subscribers while accessing the UMTS network.

 problems in Accessibility are occurring either due to problems NAS

in RRC (Radio Resource Control) connection, nas SIGNALING
or due to problems with establishment of RAB (Radio Access
Bearer). RAB Setup

Accessibility = RRC × NAS × RAB

.
accessibility

accessibility divided into:

1. admission Control

2. Congestion Control

Both these services provide the efficient use of available resources. And ensure the services to costumer.

Key Performance Indicators:

RRC connection setup

Successful RAB establishment
Paging success
ADMISSION CONTROL
 Hardware;VSWR; CS/PS Accessibility
Antenna alarms,
(RRC)

Admin Control License Node Blocking Transport Blocking

1.Check Parameter 1. RBS specific 1. Check for node 1. Check for congestion
settings for: parameters configuration on user plane (AAL2)/
error/mismatch, control plane (UniSaal
a). Feeder length/TMA 2. Verify /correct
node limitations or /SCTP) for Iub resources.
individual licensed
b). OCNS transport network
capacity levels for 2. Expand TN bandwidth
c). Adm Control layer service
the node. (via
unavailability. 3. Check IuCs / IuPs
d). Check available AMOS or SMO)
succ rate, affects all cells
resources (Downlink Tx 3.Check Channel in RNC
power, Channelization elements usage
codes). trends
RRC Succ rate could be low due to RF related issues also.
(Poor RF in RACH, FACH) Investigate the RF using WMRR
and trial maxfach1power and constantValueCprach
RRC Degradation
 CS/PS Accessibility
Hardware/Antenna
alarms, VSWR
(RAB)

Congestion Node Blocking Transport Blocking

1. Check for node 1. Check for congestion on user plane

configuration error, node (AAL2)/ control plane (UniSaal/SCTP)
limitations or transport for Iub resources.
network layer service 2. Expand TN bandwidth (add
unavailability. T1s,define more Vc)
3. Check T1 Errors
4. Check Locked T1s
5. Check Iub/TD (Vc/Vp) Mismatches
6. Share Traffic with Nbrs(qoffset2sn)
7.Reduce CPICH or Tilt or qRxlevmin
to take less traffic
8.Increase Directed Retry to Offload to
GSM
RAB Degradation
RAB Degradation
 CS/PS Accessibility
(RAB)

Congestion

DL Power Code ASE Hardware Resource Connection Limit

1.Check if Maximum
1.Check dlCodeAdm 1.Verify settings for 1. Check Locked TX/RAX 1. Verify Admission
Transmission Power is
values, if adjustment dlASEAdm,UlAseAdm; Boards; settings/Usage trends for
aligned with
MaxDlCapability; is still possible, 2.Check for R99 traffic different SF RAB.
2. Check hanging CE
2.Reduce 384k Users load on the cell. (restart)
2. Check Maximum
Transmission Power and on DL (sf8Adm), 3. Trial higher value for 3.Check HS/EUL resource 2. Fine tune parameter
CPICH ratio; 3.Reduce HS- releaseAseDlNg and settings to maintain
allocation (AMOS, UTRAN
PDSCH Codes, releaseAseDl; report) balance between
3. Reduce PwrOffset &
Increase PwrAdm; 4. Optimize radio Accessibility & throughput.
4.Reduce HS-SCCH 4. ul/dlHwAdm parameter in
network to reduce
4. Explore IFLS with other Codes Iublink;
interference/pilot
Carrier; 5. Trial FIRS 16/16
pollution.
5. Enable or Increase 6. Trial Channel Type
Directed Retry to GSM; DCH to FACH
6. Reduce 7. Reduce
sf16Adm/sf8Adm eulServing/NonServingAdm;
7.Consider changing to 8. Add,Replace RAX/TX
60W RU; Boards
8. Add another Carrier
 CS/PS Accessibility
(RAB)

Hardware Fault

UL RSSI Errors/Crashes T1 Errors Alarms

1.Incorrect Attenuation/Losses 1. Restart Board

2. TMA UL Gain Parameter 2. Cold Restart Node Escalate Escalate
Check 3.Verify SW on Node
3. Verify RFDS (Utran Report/OSS SMO)
4. External 4.Swap Cards/Boards
Interference(UL RSSI problem
5. Replace Cards/Boards
even during off-peak hours)
5. UL line physical problems
(UL RSSI issue worst during
peak hours)
Accessibility/Block Reasons

› Common Failure Reasons

– Lack of DL Power
– Lack of DL Code
– Lack of UL/DL Hardware Resource
– Exceed Connection Limits (for PS) Mtilt & Etilt
– Iub Congestions
– UL RSSI
– HW or T1 Faults
– Neighbor site/cell down

› Admission Control - Set of rules that determines whether a UE is granted

access on making a connection request. Admission control is also used when
adding a RAB , or a new RL via SHO or upswitch of services.
Congestion control
Congestion situations are detected in the RNC by means of
event based measurements of the Downlink Transmitted
Carrier Power and the Uplink Received Total Wideband Power
ordered from the RBS.
Two types from congestion control:
1- Downlink cell congestion detection
2- Uplink cell congestion detection
Downlink cell congestion
detection

PwrHyst 300
Uplink cell congestion detection
 Congestion – dl power
› Align maximumTransmissionPower with maxDlPowerCapability

› Increase pwrAdm (but make sure that pwrAdm + pwrOffset is less than 100%)
– Con: Less power available for SHO

› Reduce sf16Adm/sf8Adm

› Traffic balance between multicarrier using qOffset1sn/qOffset2sn) in idle mode.

› Overshooter (propagationDelay/WNCS)? => Down-tilt

– Con: Reduced coverage

› Enable or Increase Directed Retry to GSM

› Consider changing to increasing the power license

› Add another carrier

 Congestion – dl codes
› Increase dlCodeAdm

› Reduce 384k Users on DL (sf8Adm)(default 8).

› Reduce number of reserved (SF16) HS codes (numHsPdschCodes)

› Reduce HS-SCCH Codes

› Check if the site is over-propagating

› Traffic balance between multicarrier using qOffset1sn/qOffset2sn) in idle mode.

› Add another carrier

 Congestion Hw limit
› Increase ulHwAdm/dlHwAdm(default 100) range 0-100

› Check hanging CE (restart)

› Check if the site is over-propagating

› Increase CE licensing

› Add DUW

› Traffic balance between multicarrier using qOffset1sn/qOffset2sn) in idle

mode.

› Add another carrier

Accessibility
Failures After Adm
› Counter: pmNoFailedAfterAdm
The RRC and RAB fails after being admitted by the Admission Control.
› Possible Causes:
– 1.Iub Congestion:

– You can find out the RBS Link ID in OSS CEX/AMOS. Iub blockings can be caused by T1/IMA link
faults, mis-configurations or lack of Iub resource. Escalate to UTRAN or ML if you see lots of Iub
blockings in these counters for further investigation. In the interim, suggest Coverage limiting (reduce
CPICH, increase qrxlevmin) of traffic offloading (qoffset,) recommendations.

– 2. CE usage:
› Check the CE usage and suggest CE usage reduction either by traffic offloading or RAXB/TXB
harvesting (exchanging from low traffic sites)
– 3. UL RSSI:
Check the Quality Report for UL RTWP level.
– 4. HW or iub link issues:
Check alarms and link error seconds/unavailability.
– 5. Poor Radio:
Check WMRR for signal level and quality distributions. Use GPEH or drive test to check pilot
pollutions.
Offload traffic to another Cell/Site (which has coverage overlap) with no problems in FailedAfterAdm

› Before spending too much time on a cell, check the cell availability of the neighbors. A major neighbor
down or has T1 issue would impact the nearby sites. Also check RRC Reject due to MP Load.
BaSIC Accessibility parameter
check
Parameter Name Default Value Value Range Resolution Unit
aseDlAdm 240 0...500 1 ASE
aseUlAdm 160 0…500 1 ASE
dlCodeAdm 80 0…100 1 %
pwrAdm 75 0…100 1 %
pwrAdmOffset 10 0…100 1 %
sf8Adm 8 0…8 1 # no of radio links
sf16Adm 16 0…16 1 # no of radio links
sf32Adm 32 0….32 1 # no of radio links
ulHwAdm 100 0…100 1 %
dlHwAdm 100 0…100 1 %
primaryCpichPower 8-10% of maxTxPower  NA  1  dB
qQualMin -18   -24…0 1  dB 
qRxLevMin  -115 -25…-119  1   dBm
maxFach1Power  18 -350 ….150  0.1 dB
eulServingCellUsersAdm 64 0…96 1 Licensed dependent
hsdpaUsersAdm 64 0…128 1 Licensed dependent
Feature related to Accessibility
License FEATURE NAME FROM TO

FAJ 121 1334 Improved CE Ladder for E-DCH OFF ON

FAJ 121 406 Directed Retry to GSM OFF ON

FAJ 121 1356 Load based Handover OFF ON

FAJ 121 799 Service based Handover OFF ON

FAJ 121 1581 RNC RRC Load Control OFF ON

FAJ 121 977 Flexible Initial rate selection OFF ON

FAJ 121 435 Inter-Frequency Load Sharing OFF ON

FAJ 121 1593 Admission Block Redirection OFF ON

FAJ 121 1350 Improved RACH Coverage OFF ON

FAJ 121 2712 Service Differentiated RRC Admission OFF ON

 RETAINABILITY
Retainability is defined as the ability of a user to retain its requested service once
connected for the desired duration.

SOME OF THE main FACTORS WHICH affect retainability include:

Handover performance (soft/softer/HARD) and missing neighbor cell

INCORRECT PARAMETER SETTINGS (POWER, ADMISSION, RELASE ETC.)

CONGESTION

RADIO ENVIRONMENT (POOR COVERAGE, PILOT POLLUTION, FAST

EC/NO DROP ETC.)

NODE HARDWARE FAILURES

TRANSMISSION E1/T1 FAILURES/CONGESTION

 RETAINABILITY

Drops reasons based on counters:

Missing Neighbors DROPS

SOFT HANDOVER FAILURES DROPS

CONGESTION DROPS

IRAT DROPS

UL SYNC DROPS

OTHER REASONS DROPS

 CS/PS
Retainability

Missing Neighbor Soft Handover Uplink Sync IRAT Congestion Others

1. Investigating UE 1. Identify the failing 1. Check down 1. Transport Issue

1. Check neighbor cell 1.Check HW Alarms TxPwr by using Drive phase. switch counter for
availability 2. RBS / RNC HW
2.Check T1 Errors test data or WMRR 2. Audit the External congestion reason.
2. Add suggested Nbrs issue
3.Check Cell 2. Check parameter for GSMCell MO with latest 2. Investigate the
with WNCS/GPEH/Drive 3. RF issues outside
Availability UE TxPwr & maxSir 2G dump(BCC,NCC, RRC Access failure
Test data of available counters
4.Determine if the 3. Analyze cell BSIC,etc) due to lack of DL
3. Analyze existing power & codes 4. UE issues
issue affects only coverage by RF 3. GSM coverage area
neighbors with 3G-3G
one cell or a RBS or Planning tool or Drive verification for IRAT 3. Perform analysis
cell relation report
cluster test data neighbors of coverage area
4. Analyze cell coverage and reduce
4. Use GPEH to 4. Re-prioritization the
by RF Planning tool 5.Verify for SC
/Drive Test data/PRACH Clashes   determine the number
of Event 6a or number
neighbor list based on
overshooting
4. Verify CE usage
Plots usage
of Event 2d and HW allocation
5. Down tilts or other and dimensioning
physical optimization  5. Check Cells due to
RSSI Issues
Retainability
Drops due to Missing Neighbors

› Counter: pmNoSysRelSpeechNeighbr
› Suggestions:
› 1. Run WNCS and check Missing Neighbors. Check inter-site distance to
determine if they need to be added. (Prioritize missing neighbors in the order of
# of drops, # of events, distance, average RSCP/EcNo)
› Pay attention: Use SC(not cell name) to add missing neighbor.

› 2. Check PRACH Delay to assess if it is overshooting.

› 3. Check neighbor cell availability. If any of the neighbor cell is down, it can
cause missing neighbor drops.
 Retainability
Drops due to Soft Handover
Counter: pmNoSysRelSpeechSoHo
This counter is pegged when the speech call release is due to inability to add a cell
with or without relation into the active set. So it also includes the missing neighbor
drops.
› Suggestions:
› 1. Check 3G-3G Cell Relation Report on BO for both out-going and in-coming directions, to see which
relation/direction is the cause;
› 2. Check Hourly SHO stats. If occurring during busy hours, identify the cause and relieve congestion on
target cell;
› 3. If SHO fails in off-peak hours then it is not lack of resource or Admission Control. Check cell
availability/reserved, Iub configuration and UL RSSI for target cell. Check Alarms/T1/UL RSSI/HW/MP
Load for the cell and its neighbors;
› 4. Check Scrambling Code Collisions;
› 5. Check for missing neighbors in WNCS as they will also contribute to SHO Failures;
› 6. If SHO fail rate is high on many relations, the issue could be with Source cell. Check admission control
parameters such as: pwrAdm + pwrOffset, DLCodeAdm, UL/DL HWAdm to see if there is sufficient margin
available for SHO. Check SHO overhead with the admission control level.
› 7. Trial IndividualOffset to increase(faster HO) or decrease (delayed HO) SHO area with problem
neighbor.
› 8. Check CPICH Powers with the major neighbors. Keep the delta small (within 3 dB) to maintain UL
balance in SHO border.
Flowchart – drop due to Sho
High number of Drops due to SoHo
the issue could be with Source
cell.Check admission control
Identify
parameters such as: pwrAdm, Are missing missing
DLCodeAdm, UL/DL HWAdm Yes
Nbr drops Nbrs with
to see if there is sufficient also high WNCS &
resources available for SHO add
Several relations No
having moderate
SHO fail rate Check SHO
Cell maybe serving a Success rate
RF area having sudden per Nbr
interference changes. relation Check if Coverage overlap
Identify some is sufficient. Increase
relations with footprint using Tilts or
high SHO fail rate CPICH

Is relation defined Is Nbr site having HW

Yes
High ASU correctly in issues, UL RSSI,or
failures UtranRelation MO Congestion due to
(Target RNC, Transport,pwr or other
RelationID = Target resources. Fix nbr site
cellname)
No yes
Is it Inter-RNC relation?
Check Iur Definitions &
Delete and re-define
investigate other relations
over same Iur.

Reduce interference Increase IndOffset to expand HO

with tilt or CPICH area. Monitor power utilization to
avoid Acc/Throughput issue Check for SC Collisions.
changes
Retainability
Drops due to speech congestion

› Counter: pmNoOfTermSpeechCong
› This counter is Incremented by one when the speech call release is due to
congestion. The connection is terminated by RNC.

› Suggestions:
› 1. Check admission counters (LackdlCode, lackdlpwr, UL/DLHwAdm) on RAB
establishment to find out the resource bottleneck.
› 2. Check for MPLoad. (Suggest temporary traffic-offloading)
› 3. Check for Iub congestion. (Suggest temporary traffic-offloading)
› 4. Verify CE usage and HW allocation and dimensioning
› 5. Check for special events (sports/festivals/holidays/accidents) or if a site
nearby was down.
 Retainability
Drops due to UL Sync
› Counter: pmNoSysRelSpeechUlSynch
› This counter is Incremented by one when the speech call release is due to the timer dchRcLostT expires.
› Suggestions:
› 1. Resolve Missing Nbrs & SoHo issues, if any;
› 2. Check Alarms/T1/UL RSSI/HW/MP Load for the cell;
› 3. Check Propagation delay and WMRR for radio condition. If RSCP is bad, site needs to be optimized for
coverage by uptilt(coverage hole); if EcNo is bad ,down tilt to reduce pilot pollution;
› 4. Trial different cell designation (for instance, SHO to IRAT/IFHO). Lower the thresholds used to trigger
IRAT/IFHO (usedFreqThres2dEcno, usedFreqThresh2dRscp);
› 5. Check IRAT failure rates. Audit 2G (IRAT) neighbor list to see if there is missing 2G neighbors. This may
be especially true for cells on the border of the 3G coverage area;
› 6. Check for internal & External UL RSSI issues (neighbor cells);
› 7. Trial minPwrMax (increase), minPwrRL(increase) to improve RL connection, constantly check for DL
power congestion in these trials.
› 8. Limit qRxlevmin to avoid taking far away samples (calls starting at low quality and dropping
immediately).
› 9. Check CPICH Powers with the major neighbors. Keep the delta small to maintain UL balance in SHO
border. CPICH Power should be between 8-10% of maxTxPwr.
› 10. Cell maybe serving a radio environment with a relatively high number of UEs experiencing sudden
interference changes (generally caused by bridges, buildings, tunnels, steep hilly terrain, etc). As a
consequence of these changes, power utilization is higher. Trial minpwrlRL, Individualoffset but monitor
non-HS power utilization, and active set update failures.
 Retainability
Drops due to Others
› KPI Formula:
› Drop Due to Other = pmNoSystemRabReleaseSpeech –pmNoSysRelSpeechUlSynch –
pmNoSysRelSpeechSoHo - pmNoOfTermSpeechCong
› Basically all other speech drops which were not pegged in any of the speech drop counters described in
the previous slides.
› Suggestions:
› 1. Resolve missing nbrs, SoHo, UL sync issues if any before “other” drops
› 2. Check Alarms/T1/UL RSSI/HW/VSWR/MPLoad for the cell.
› 3. Check WMRR and Propagation Delay to improve radio condition and coverage range.
› 4. Assess the terrain profile and see if tilt can be adjusted.
› 5. Check Iub Congestions.
› 6. Check SHO/IRAT/IFHO failure rates. Optimize the respective (SHO/IRAT/IFHO) nbr list.
› 7. Trial HOtype and Adjust 2d thresholds (usedFreqThresh2dRscp, usedFreqThresh2dEcNo) if coverage is
weak in the area.
› 8. Check for RAX/TX board errors, may require a restart.
› 9. Check Scrambling Code Collision.
› 10. Check CPICH Power with the major neighbors. Keep the delta small to maintain UL balance in SHO
border. CPICH Power should be between 8-10% of maxTxPwr.
› 11. Restart the site if all the above has been checked and still cannot find out the problem.
› Usually drops due to others are radio related(RU/CBU/FU). A site restart or HW replacement might be
needed. Conduct drive test and record GPEH of the area for further investigation if necessary.
Solutions to control Drops due to ULsync &
Others
› Ideally, the drops due to ULsync & Others can be reduced by controlling the noise floor
in the WCDMA cell, which can be done by the means of EDT or Layer Management
( Changing HOtype or relaxing 2d thresholds). If in some cases, tilting & LM can’t be
changed, the following set of parameters can also be tried:
› 1. minpwrMax:
› Defines the maximum power per Radio Link relative to CPICH power where Radio Link bit rates are
equal to or below minimum Rate (15.9 Kbps). Increasing this parameter, provides more power for CS
users on the cell edge, at the expense of DL power.
› Connections that fall into this range are: Signaling Radio Bearers (3.7 Kbps), Standalone Signaling
Radio Bearers (14.8 Kbps), Conversational Circuit Switch Speech AMR 12.2 Kbps (15.9 Kbps).
› 2. minpwrRL:
› By changing this parameter, the minimum power given per radio link is increased, therefore the
starting point for power control ramping is higher, avoiding deep power decreases due to good RF
conditions. Hence the radio link become now less sensitive to sudden RF conditions degradation.
› 3.rlfailureT:
› Increasing the time before the radio link is considered out of sync, can lead to the signal recovering
and the call being saved from being dropped.
› 4. noutsyncInd:
› Increasing the consecutive number of error radio frames can lead to the delay in UE entering the
“Out-of-Sync” state and the delay in starting the rlfailureT timer.
BaSIC retainability parameter
check
Parameter Name Default Value Value Range Unit
hoType 2 0,1,2 none
minPwrRl -150 -350..150 dB
individualOffset 0 -100..100 dB
minPwrMax -15 -350..150 dB
nOutSyncInd 10 0….500 Frame
rlFailureT 10 0..255 sec
reportingRange1a  4 0..29 dB
reportingRange1b  8 0..29 dB
timeToTrigger1a 10 0…15 ms
timeToTrigger1b 12 0…15 ms
usedFreqThresh2dEcno -12 -24..0 dBm
usedFreqThresh2dRscp -100 -115..-25 dBm
loadSharingGsmFraction 100 0..100 %
loadSharingGsmThreshold 95 0..100 %
hsdschInactivityTimer -1 -1..-1, 1..255 s
inactivityTimer -1 -1..-1 1..1440 s
inactivityTimerPch -1 -1..240 s
downswitchTimer -1 -1..-1 0..1000 s
Case study- SHO Parameter trial
1.- DESCRIPTION
The feature enables tuning of intra-frequency mobility behaviour in high mobility areas, such as
highways, in order to reduce the number of dropped calls in these areas. It is achieved by
speeding up Radio Link additions to the Active Set and slowing down RL removals from the AS.
The feature can also be used in low mobility areas to limit the number of event 1a or event 1b
occurrences
.

2.- EXPECTED BENEFITS:

Drop rate
3.- KPI TO EVALUATE:
CS/PS Drop Rate, SHO Overhead, MP Load. Soft
handover Success Rate.
4.- DETAILS:
To change the parameter timeToTrigger1a 240-200ms
timeToTrigger1b 6401280ms (RNC)
Feature related to retain ability

 Call Re-Establishment
 Inactivity Timers on Cell Level
 Soft Handover Parameters on Cell Level
MOBILITY
 Handover in WCDMA
 Mobility/Handover is defined as the ability of a user to move between
neighboring UMTS and GSM Cells and retain its requested service (CS or PS)
once connected.

 Soft/Softer Handover
 Inter-Frequency Handover
 Inter-Radio Access Technology (Inter-RAT) Handover
 mobility
Soft Handover
In Soft Handover, the UE connection consists of at least two radio links established with cells
belonging to different Node-B.
In Softer handover, the UE connection consists of at least two radio links established with cells
belonging to the same Node-B.

Soft Handover is controlled through the events 1a, 1b, 1c & 1d:
 1a: A new candidate for the active set enters reporting range
 1b: A cell in the active set leaves the reporting range
 1c: A cell not in active set becomes stronger than a cell in the active set
 1d: Any cell becomes better than the best cell in the active set

Majority of the SOFT/SOFTER Handover failures include:

 Failures due to interference, poor areas of dominance
 Primary Scrambling Code collision
 Missing neighbors
 Neighboring sites Hardware issues
 mobility
I RAT Handover

IRAT handover process includes the following two sub-processes:

• Relocation preparation
• Handover implementation

Relocation preparation Failures are mainly due to following reasons:

• The 2G resources are not enough.
• The CN parameters are not configured reasonably.
• The configurations of GSM neighboring cells are not consistent with actual
parameters.

Handover implementation failures are mainly due to following reasons:

• Incorrect parameter configuration of neighboring 2G cells
• There exists side-channel interference in 2G cells
• Improper setting of neighboring threshold
 mobility
INTER FREQUENCY Handover

Inter-Frequency Handover allows continuation on dedicated channels when the UE is moving out
of coverage of one WCDMA RAN frequency to an area where coverage on another WCDMA
RAN frequency exists. IFHO can also be triggered when performing cell selection for a packet
connection.

IF Hanover has following events :

Event 2a: Change of best frequency
Event 2b: The estimated quality of the currently used frequency is below a certain threshold and
the estimated quality of a non-used frequency is above a certain threshold.
Event 2c:The estimated quality of a non-used frequency is above a certain threshold
Event 2d: The estimated quality of the currently used frequency is below a certain threshold (It is
based upon Ec/No measurements and RSCP measurement) i.e. start of compression mode
Event 2e:The estimated quality of a non-used frequency is below a certain threshold
Event 2f: The estimated quality of the currently used frequency is above a certain threshold. i.e.
stop of compression mode
Handover failures are mainly due to following reasons:
• Incorrect parameter configuration of neighboring 3G cells
• Hardware issue on neighboring cells.
• Improper setting of neighboring threshold
 3G-3G failures
Troubleshooting

Possible Reasons for 3G-3G HO Failures

●
Interference
●
Pilot Pollution
●
Overshooting of nearby cells
●
Low coverage area
●
External Interference
●
PSC Collision
●
Two or more nearby Cells having same PSC
●
Missing Neighbour Definition
●
Improper cell relations resulting into failed HO
●
Neighbouring Site E1/Hardware Issue
●
Attempts to nearby site failing due to E1/Hardware issue
●
Improper Definitions
●
Improper External Definitions in RNC/MSS
●
Congestion on neighboring site
●
Limited resource neighboring site will lead to failures
●
On Utran Cell Locked, Channels Unlocked
●
Attempts to the cell will take place based on unlocked cell, but will not succeed as cell is locked
Mobility
SHO & Soho

› 1. Incoming SHO SR ( = pmNoTimesRlAddToActSet /

(pmNoTimesRlAddToActSet + pmNoTimesCellFailAddToActSet) )
› * Congestion (power, code, CE, etc);
› * Overshooting

› 2. Outgoing SHO SR ( =pmRlAddSuccessBestCellSpeech /

pmRlAddAttemptsBestCellSpeech )
› * With one specific cell or some cells;
› * Dig into the root cause
› (Wrong RNC info, overshooting, etc).
 CS-IRAT failures
Possible Causes & Counters

CS IRAT HO Failure

Preparation Failure Execution Failure

not
not due
due to
to Physical Failure
Physical Failure due
due to
to UE
UE
Preparation failures - Physical Channel Failure
Physical Channel
--
Failure Channel
Channel Failure
Failure --
pmNoFailOutIratHoSpee
rejection
rejection --
pmNoFailOutIratHoSpee pmNoFailOutIratHoSpee
pmNoFailOutIratHo
pmNoFailOutIratHoSpeechGsmFail pmNoFailOutIratHoSpee
chReturnOldChPhyChFai
chReturnOldChPhyChFai
chReturnOldChNotPhyCh
chReturnOldChNotPhyCh
Fail
pmNoFailOutIratHo
SpeechUeRejection
SpeechUeRejection
Fail
 IRAT
Check Checklist

Definition
External Cell Definition – Cell defined in RNC/BSC
●

Outer Definition – Cell defined in MSS/MSC

●

SGSN Definitions – LAC/RAC Def

●

Check RNC/MSS Definitions – Correct RNC/MSS(for new

●

nodes)

Hardware
●
Blocking
●
Hardware Failure

Check
●
Poor GSM BCCH Channel quality
●
E1 Issues
BaSIC mobility parameter
check
PARAMETER NAME Object Default Recommended Value Range
fddGsmHOSupp RNC TRUE TRUE 0,1
hoType Utrancell GSM_PREFERRED GSM_PREFERRED 0,1,2,
usedFreqThresh2dEcno Utrancell -12 -15 -24..0
usedFreqThresh2dRscp Utrancell -100 -105 -115..-25
gsmThresh3a RNC -95 -92 -115..0
COEXUMTS BSC 1 (ON) 1 (ON) 0,1
gsmAmountPropRepeat RNC 4 1 0..25
gsmPropRepeatInterval RNC 5 15 0..25
tmStopGsmMeas RNC 20 20 1..60
ifhoAmountPropRepeat RNC 4 4 0..25
ifhoPropRepeatInterval RNC 5 5 0..25
fddIfhoSupp RNC 1 1 0,1
serviceOffset2dEcno RNC 0 0 -20..20
utranRelThresh3aEcno RNC -1 0 -10..10
timeToTrigger3a RNC 6 6 0..15
 integrity
Introduction

 Service Integrity represents the quality experienced by the user during A call or session.

 HSDPA & EUL throughput ARE used as MAIN Indicators FOR SERVICE INTEGRITY.

 THROUGHPUT PERFORMANCE OF A NETWORK DEPENDS ON THE SPEEDS IN

EITHER DOWNLINK AND/OR UPLINK, EXPERIENCED BY THE END USER

 LOW THROUGHPUT IS ONE OF THE MOST COMMON ISSUES OBSERVED IN THE

NETWORK
 troubleshooting flow chart

Low Throughput

Incorrect Higher Order

Lack of Poor Radio Alarms &
Congestion Parameter Modulation
Resources Conditions License
Outages
Settings

High Iub Poor

Over Pilot Transmission
Power Code CE Limiting Coverage/
shooting Pollution
Low CQI
Errors
Ratio Quality
BaSIC intigrity parameter check
MO
Parameter MO Parameter
max Hsrate

codeThresholdPdu656
NumHspdschcodes

16 QAM hsMeasurementPowerOffset
64 QAM

HSDPA Dyanmic Code Allocation

Hsdsch numHsPdschCodes

HSDPA flexischedular numHsScchCodes

Eul2msTti
Site Configuration
eulMaxTargetRtwp
CQI

Hspower margin
numEagchCodes

queueSelectAlgorithm
Eul
numEhichErgchCodes
eulmaxshorate

maxTransmissionPower
eulMaxOwnUuLoad
UtranCell
eulMaxRotCoverage eulServingCellUsersAdm
Case study- cqi Improvement-
hsMeasurementPowerOffset
1.- DESCRIPTION
Offset relative to the P-CPICH that the UE shall use when calculating the assumed HS-PDSCH power in the
CQI estimation
– Range: (0.. 200)
– Default: 0 [0 dB] / 0.1 dB
– Recommended: 80 [8 dB]

.The new recommended value is intended to shift the distribution of reported CQI away from the lower
edge, since CQI=0 will result in no scheduling and reduced throughput. Tuning of the parameter might
still be needed (considering the observed CQI distribution), but the recommended value is a better
starting point for this tuning than the current default value.
• The channel quality indicator is used by the UE to signal to the RBS it’s current radio conditions. In
fact it sends the RBS a number relating to the biggest transport block that the UE thinks it can
successfully decode under the current conditions.
• The UE reports a number between 1 and 30 and this indicates a maximum transport block size
depending on the UE category
2.- EXPECTED BENEFITS:
User and reported CQI.
3.- DETAILS:
–Changing “hsMeasurementPowerOffset” from less than 80 to default value 80.
CQI Adjustment

RBS throughput?
High number of NACKs
XXXXXX
X = 10%
High CQI √
reporting
UE High retransmission rate cqiAdjustmentOn = TRUE
=> low throughput

High number of ACKs

√√√√√√ Since the accuracy of the CQI reporting depends
on the UE vendor and model, it is recommended
Low CQI to enable the CQI adjustment feature so that
both cell and user throughput are maximized.
reporting This is particularly important when proportional
UE Low utilization fair or Max CQI is selected as scheduling
=> low throughput algorithm.
Case STUDY - ECiO IMPROVEMENT
BY HSPOWERMARGIN
1.- DESCRIPTION
In determining how much power can be allocated to HS-PDSCH, the total transmit power
(including all common channels, dedicated channels, HS-SCCH, HS-PDSCH and the
Enhanced Uplink downlink control channels) is limited to the maximum downlink
transmission power for the cell signaled from the RNC, minus the hsPowerMargin back off.
P HS = P max - P non-HS - hsPowerMargin [dB],

2.- KPI TO EVALUATE:

HS Throughput.
3.- EXPECTED BENEFITS:
EcIo.
4.- DETAILS:
–Changing hsPowerMargin 02
Case STUDY –Eul thput improvment
1.- DESCRIPTION
• The maximum total interference tolerated is set by the parameter eulMaxRotCoverage. A
high value of this parameter limits the cell coverage but increases EUL capacity. A low value
increases coverage at the expense of cell capacity. The purpose of this estimate is to
dynamically allow as much EUL throughput as possible without compromising the planned
cell coverage.

2.- KPI TO EVALUATE:

Eul Througput,RSSI
3.- EXPECTED BENEFITS:
Eul Throughput .
4.- DETAILS:
– Changing eulMaxRotCoverage 100 to 300
› WCDMA Resources
› Code tree consumption
› The code tree consumption is measured in percentage of the
› total tree size by excluding the fixed codes allocated for
› HSDPA (i.e. the higher the number of codes allocated for
› HSDPA the smaller will be the available tree and higher the
› relative consumption)
› The admission limit is set by dlCodeAdm (as a percentage)
Admission Control: Counter flow Chart- RRC