Reduce Code Congestion:

Check List

LST UCELLHSDPA

Code Min Number for HS-PDSCH = 5

Solution:

*Reduce Code Min Number for HS-PDSCH = 4,3,2,1…..

*2nd Carrier Add

*4th Sector Addition

*Traffic Redirection Feature On

*Decrease the BE Guarantee BE Rate (GBR)

*Dynamic Code Allocation Algorithm=On (LST ULOCELLMACHSPARA)

*Down tilt for reduce Traffic

Improve CSSR:
*Check RRC Rejection

 RRC Rejection due to code congestion

 RRC Rejection due to Down Link IUB Band Congestion
 RRC Rejection due to Down Link IUB Band Congestion
 RRC Rejection due to Radio Link Failure
 RRC Rejection due to IRAT direction Rejection
 RRC Rejection due to UL and DL CE congestion
 RRC Rejection due to UL and DL Power congestion
 RRC Rejection due to NoReply

*Alarm

*RTWP
Improve DCR:
Reason:

*Poor Coverage (DL / UL)

*Pilot Pollution / Pilot Spillover
*Missing Neighbor
*SC Collisions
*Delayed Handovers
*No resource availability (Congestion) for Hand in
*Loss of Synchronization
*Fast Fading
*Delayed IRAT Triggers
*Hardware Issues
*External Interference

Check List:

*Neighbor Relation

*Any service affected Alarm

*Pilot Pollution check Trough Drive test

RRC Fail Reason and Improvement:

Reason:

*RF Problem

*Incorrect parameter setting

*Miscellaneous causes

*Poor DL coverage. The “fake coverage” phenomenon (the user sees the 3G icon on the screen in
idle but cannot connect to any service). The cause could be overshooting cells but also excessive
values of Qqualmin like -22 dB. Solution: Adjust the antenna azimuth and down tilt, add repeaters and
RRUs, add micro cells. Any user should get a better signal than EcIo = -18 dB.

* Lack of Dominance (no clear Best server): Continuous change of best server leads to
RRC failures and RAB failures. Solution: Establish a best server everywhere. Clear dominance.

* Poor UL coverage: The UE has not enough TX power to communicate with Node-B (even when
there is low UL traffic on the cell). Solution: Adjust the antenna azimuth and down tilt, add repeaters,
reduce CPICH power.
*Strong UL interference: Due to external interference or high UL traffic (the cell shrinking
phenomenon). The UE will not be able to increase to more than 21 dBm for the preamble power and
the
RACH will fail - or synch will fail later. Solution: Up to operator’s decision (implement more tilt ,CPICH
power reduction, chase external source of interference or increase the number of Node-Bs to cope
with
traffic)

*Strong DL interference: Usually due to overshooting cell, external interference, high DL traffic
on this cell and surrounding cells. The UE will miss the AI message for RACH and will fail to establish a
call - or will fail to get synch in DL. Solution: Improve best server area (strong dominance)

* RF radiating system problems:

*Antenna’s footprint not touching the ground properly: sites with over 120 m height and tilts around 3
degrees. More than 3/4 of the
antenna pattern will not be touching the ground with a decent level of signal. Most calls are handled
on side lobes.

* RF jumpers (feeding the antennas with RRU signal) are too long (should be no more than 3 meters,
we’ve seen cases in --- with 10
meters of ½” jumpers). This definitely leads to high noise factors and call setup failures. Also UL and DL
coverage is very much
limited.

*Missing neighbor’s: Leads to call setup failures due to poor signal

General Causes of failures – Radio Parameter Problems(II)

Page 9
• Excessive values in object UCELLSELRESEL: Examples: Qqualmin<-18, IDLESINTRASEARCH ≠ 127,
IDLEQHYST2S>1, IDLEQHYST1S>3.
• Improper settings of access parameters: No discrepancies found in UCELLACCESSRESTRICT
• Inappropriate settings of preamble power ramp step and retransmission times: Current set of
parameters is NOK (PREAMBLERETRANSMAX=20, CONSTANTVALUE-20, PowerRampStep=2, Mmax=8).
• Inappropriate setting of adjacent cells for UINTRAFREQNCELL: Qoffset1sn, Qoofset2sn out of the
range (-4dB;+4dB). Wrong settings for Sintra (like 0 dB), Sinter( also like 0 dB).
• Inappropriate settings of synchronization parameters: Synch and Out-Of-Synch parameters for UL
(N_INSYNC_IND=8, N_OUTSYNC_IND=8,and T_RLFAILURE=20), DL (T312=1, N312=1, N313=D20 ,T313=3
and
N315=D20). Please remember that call re-establishment is activated for both UL and DL (great KPIs but
acceptable user
perception)
• Unsuitable power allocation rate for DL common channel: No discrepancies found (PSCHPower,
SSCHPower, BCHPower , MaxFachPower, PCHPower, AICHPowerOffset, PICHPowerOffset)
• Unsuitable initial power of uplink and downlink dedicated channel: No discrepancies found for UL
(DPCCH_Initial_Power = PCPICHPower - CPICH_RSCP + Uplink interference + DefaultConstantValue) and
DL initial SIR
target
• Unsuitable setting of uplink Initial SIR target value of dedicated channel: No discrepancies found for
DL initial SIR Target
• Inappropriate setting of adjacent cells for UINTERFREQNCELL:
• When 1900 and 850 MHz have significant azimuth difference why there is DRD just towards one 1900
cell and
not for the other 1900 cell as well?
• Why Qoffset1sn, Qoofset2sn are out of the range (-4;+4) on top of the IdleQhyst1s >2?

General Causes of failures –Miscellaneous causes(II)

Page 10
•Transmission issues (fluctuating PATH, high BER, reduced capacity, routers down in the IP
cloud).
•Alarms on cells, on Node-Bs, on RNC, on transmission
•Planning issues: traffic not properly shared between layers and NodeB, lack of a clear best
server( no dominance), paging congestion due to LAC splitting issue.
•Radio Congestion:
• CE
• DL Power
• UL Power
• R99 Codes
• Iub bandwidth
• SPU bottleneck
• WMPT board bottleneck