UMTS KPI OPTIMIZATION

JAN 2014

UMTS OPTIMIZATION GUIDELINES

HUAWEI SPECIFIC

ARUN SINGH arunsingh.ec@gmail.com

UMTS KPI OPTIMIZATION

JAN 2014

3G is basically used for data and Voice services. There are 4 service classes are there in UMTS. On
the basis of these service classes different KPIs are categorized.

Major KPIs which are needed to monitor on daily basis are:

KPIsAccessibility
CSV Access (RRC, RAB)
CSD Access
HS+PS Access (RRC, RAB)

Retainability
CSV Drop
CSD Drop
HS+PS Drop (HSDPA, PS)

Mobility
SHO Success Rate
IRAT Handover (CS, PS)
SHO Overhead

Integrity
Throughput
BLER
CQI (>15 & >21)

Access KPIs are critical KPIs as it is required to allow maximum users to access the network.
In the coming pages KPIs, reasons for poor KPIs and their daily basis possible solutions are described.

ARUN SINGH arunsingh.ec@gmail.com

UMTS KPI OPTIMIZATION

JAN 2014

AccessibilityFor accessibility there are 2 major counters which are needed to monitor
RRC setup success rate
RAB setup success rate
For the failure of above 2 KPIs major reasons are:
1. Resource Congestion
2. License(Node B, RNC) discrepancy
3. IUB, IUCS-PS issues (Bandwidth, losses)
4. Hardware issues (WBBP Card, Temp, and Alarms etc.)
5. Weak Coverage
6. Other RF Issues
For UL and DL there are different types of algorithm on cell level basis, which can be used separately
Uplink CAC algorithm switch:

(MOD UCELLALGOSWITCH)

ALGORITHM_OFF: Uplink power admission control algorithm disabled.

ALGORITHM_FIRST: Power-based increment prediction algorithm for uplink admission control.
ALGORITHM_SECOND: ENU-based admission algorithm for uplink admission control.
ALGORITHM_THIRD: Power-based non-increment prediction algorithm for uplink admission control.
ALGORITHM_FOURTH: Service load-based algorithm for uplink admission control.
We are using ALGORITHM_SECOND in Uplink case (Huawei).

Downlink CAC algorithm switch:

(MOD UCELLALGOSWITCH)

ALGORITHM_OFF: Downlink admission control algorithm disabled.

ALGORITHM_FIRST: Power-based increment prediction algorithm for downlink admission control.
ALGORITHM_SECOND: ENU-based admission algorithm for downlink admission control.
ALGORITHM_THIRD: Power-based non-increment prediction algorithm for downlink admission control.
We are using ALGORITHM_FIRST in Downlink case (Huawei).

ARUN SINGH arunsingh.ec@gmail.com

UMTS KPI OPTIMIZATION

JAN 2014

Resource Congestion:
There are 4 major resources due to which congestion could be occur
IUB Congestion (UL-DL): IUB congestion can occur if carrying high traffic beyond the allotted
bandwidth or having losses on IUB interface due to hardware issues.
Solution: a) For IUB congestion removal bandwidth augmentation required, and for IUB losses need
to IUB interface path and connection from both ends.
b) If a site has only IUB admission bandwidth limitation, and the physical bandwidth utilization is not
high then decreasing the active factor of PS R99 and HSPA could allow more user to access the
network.{ Bandwidth (IuB CAC) = GBR*active-factor}.
(ADD TRMFACTOR: FTI=11, PSINTERDL=50, PSINTERUL=50, PSBKGDL=50, PSBKGUL=50, HDINTERDL=50,
HDBKGDL=50, HUINTERUL=50, HUBKGUL=50; // define new PS interactive and background services active
factor index ADD ADJMAP: ANI=xxx, ITFT=IUB, FTI=11; // adjacent node uses the new index- Active Factor
adjustment from 100% to 50 %)

Code Congestion: Code congestion is totally depends upon the code utilization. If HSDPA utilization
is high code congestion could be occur.
Solution: If code utilization is less than 30% and there is code congestion then code planning need to
check. In case utilization is high then we can take several steps for optimizationa) LDR priorities can be changed (MOD UCELLLDR, MOD UNODEBLDR)
b) Allotted Max codes (HSPDSCHMAXCODENUM) can be reduced as per requirement but may
affect throughput. (MOD UCELLHSDPA)
c) Min codes (HSPDSCHMINCODENUM) can be reduced to give access at fewer codes. (MOD
UCELLHSDPA)

d) CE Cards need to add if utilization is too high.

Power Congestion (UL-DL): Power congestion could be Uplink and downlink both. Downlink
congestion occurs due to CPICH power (incorrect planning) and high users. Uplink power congestion
could be due to Uplink resources and uplink power.
Solution: DL Power (ALGO 1) - For downlink power congestion, we can reduce CPICH power or we can
physically optimize the cells to restrict overshooting. If we are using ALGO 2 for uplink (EUN based
admission), there are several parameters which can be adjusted for optimization:
(Please try to keep the ratio of CPICH power vs. Max Transmit Power of Cell at 10% this would help to
easily maintain CPICH Ec/No of the HSDPA carrier)
a) Max allowed EUN numbers can be adjusted (Default-95, Max-200 in UL-DL) (MOD UCELLCAC)
b) Max allowed HSDPA & HSUPA users can be changed (Default HSDPA-64, Max-100, Default
HSUPA-20, Max-128) (MOD UCELLCAC)
c) if FACH power is high, it is suggested to optimize the H2F timer when BE services is in the
stable low activity state.IT will decrease cell power congestion
(SET UUESTATETRANSTIMER: BeH2FStateTransTimer=5)

D) If the load occupied by R99 in a cell is high => TCP will be limited

ARUN SINGH arunsingh.ec@gmail.com

UMTS KPI OPTIMIZATION

JAN 2014

Open the LDR algorithm based on downlink power for R99 users and:
- reduce BE service rate,
- Or switch users to inter frequency cell
It will relieve cell power congestion
(ADD UCELLLDR: DlLdrSecondAction=InterFreqLDHO, DlLdrThirdAction=BERateRed ;)

Channel Element (UL-DL): CE congestion could occur due to high utilization (Primary + Secondary
traffic). Failures due to CE congestion can occurs due to
a) Card faulty (Less utilization and still failure)
b) Card hanged due to hardware, temp
c) High Utilization and lack of CE resources
Following actions can be taken to overcome from the CE Congestion:
a) If CE utilization is too high need to upgrade CE card.
b) Call admission control threshold can be changed as per requirement (Default-80...75, Max92...85 in UL-DL)
(MOD UCELLCAC)
c) Max allowed EUN numbers can be adjusted (Default-95, Max-200 in UL-DL) (MOD UCELLCAC)
d) Load balancing (LDB) function can be implemented on particular cells.
e) LDR can be implemented (Cell Level & Node B level). (MOD UCELLLDR, NODEBLDR)
f) LDR priorities can be changed.
(Downlink Actions:
1.
2.
3.
4.

Code Adjustment
BE Rated
QoS Renegotiation
IRAT CS Load Handover

Uplink Actions:
1. BE Rated
2. QoS Renegotiation
3. IRAT CS Load Handover)

g) R99, HSUPA Initial bit rate parameter values can be reduced (D256 to D32...D16) on RNC
level, Significant improvement by R99 initial bit rate change. (SET UFRC)
h) UL-L2 Enhanced can be enabled on RNC level with this all local cells must have (MOD
LOCELL=0, UL_L2PLUS=TRUE;)-

i)
j)

(UCELLALGOSWITCH)

PS256 & PS384 RAB can be disabled. (RAB Index Need to disable)
UL BE Traffic Threshold ON HSUPA (This parameter specifies the rate threshold for decision to use EDCH to carry UL PS domain background/interactive services. When the maximum UL service rate is higher than or
equal to this threshold, the service will be carried on E-DCH. Otherwise, it will be carried on DCH) can be

changed (Def-D608 toD64)

[SET UFRCCHLTYPEPARA- UlBeTraffThsOnHsupa)
k) Dynamic CE disabled from Node B end, significant improvement.
l) CQIFBCK Value changed from D2 to D8, significant improvement.
(ADD UCELLHSDPCCH: CellId=*****, CQIPO=PO_24/15, CQIPOFORSHO=PO_24/15, CQIREF=1, CQIREFFORSHO=1,
CQIFBCK=D8, CQIFBCKFORSHO=D8;)

ARUN SINGH arunsingh.ec@gmail.com

UMTS KPI OPTIMIZATION

JAN 2014

m) Change the DCCC data rate degree, from (MBR-PS128-PS64) to (MBR-PS64-PS32), make user
with low data transition use PS32 and if need more data transition, increase the Data rate to
PS64 and MBR (now use PS384).
(SET DCCC: UlDcccRateThd=D32, LittleRateThd=D32, UlRateDnAdjLevel=3_Rates, lMidRateCalc=HAND_APPOINT,
UlMidRateThd=D64;)
n)

Change the GBR, from PS64 to PS32. GBR is guarantee data rate, also the minimal data rate
the LDR can reduce.
(SET USERGBR: TrafficClass=INTERACTIVE/ BACKGROUND, THPClass=High/ Medium/ Low, BearType=R99,
UserPriority=GOLD/ SILVER/ COPPER, UlGBR=D32 ;)

n)

DRT

License (Node B, RNC) discrepancy:

During Network audit in some cases we found that CE license configured in RNC, Node B is less than
the installed CE cards. In that case it will use only configured CE licenses. CE definitions should be
same as configured CEs.
Example: If we installed 256 CE card on site than default configured license value also need to
change from 192 to 256 on Node B.
IUB, IUCS-PS issues (Bandwidth, losses):
IUB: Access failure could be due to IUB congestion and IUB frame losses on UL and DL. IUB
congestion could be due to high utilization on assigned IUB in this case IUB bandwidth need to
augment. Second is IUB frame losses can be due to MEN issue, port issue on both sides.
IUCS-IUPS: It could be due to frame losses on IUCS and IUPS, IUCS-PS link fluctuation, and M3UA link
fluctuation.
Hardware issues (WBBP Card, Temp, and Alarms etc.): Congestion can be occur due to hardware
issues on Node B i.e. Alarms, CE card faulty, CPRI issue, High Temperature due to which card hangs
Weak Coverage: Due to weak coverage access failure issues can happen. Due to poor coverage,
weak EcNo not able to initiate call properly (Either RRC or RAB).
Missing NBRs (NBRs need to check)
Weak coverage (New Site Required)
Ssearchrat value can be changed for early IRAT
Physical Optimization for coverage improvement

Other RF Issues: There are several reasons for other RF issues i.e. Failures due to weak coverage,
Failures due to UE no reply, Failures due to ULsync Failures due to SRB reset (Signaling Reset- by
RNC). To overcome above failures several steps need to take:
Missing NBRs (NBRs need to check)
Weak Coverage
High RTWP (Connectors, Cables need to check)
Proper IRAT parameters definition (Idle-Dedicated)

ARUN SINGH arunsingh.ec@gmail.com

UMTS KPI OPTIMIZATION

JAN 2014

Pilot pollution need to check

Overshooting need to check
RACH failures (Max retransmission rate can be increased, CPRACH value can be adjusted).
RTWP optimization solutions for heavy-traffic cells:
1) For the indoor scenario:
a) Modify the constant value of the initial transmit power: Constantvalue=-20->
Constantvalue=-30,
b) Modify the step: PowerRampStep=2 -> PowerRampStep=1,
c) Modify the Preamble retransmit times: PreambleRetransMax=20 ->
PreambleRetransMax=40,
d) Modify the maximum number of cycles: Mmax=8->Mmax=3,
e) Modify the upper limit of random rollback: NB01max=0 -> NB01max=10.
2) For the outdoor scenario:
a) Modify the maximum cyclic times: Mmax = 8 -> Mmax = 3,
b) Modify the upper limit of random rollback: NB01max=0 -> NB01max=10

RTWP analysis.xls

ARUN SINGH arunsingh.ec@gmail.com