Performance Optimization 3G PDF

Performance Optimization_3G
-Generic Steps & Procedure
~Saptarshi Laskar
NPO-RF Planning & Optimization
0 of 17 © Nokia-Siemens Siemens Networks

Measurement data collection
- Reporting Suite/EOSFLEX
Various Available Reports give details information (root causes) for bad KPI analysis (daily, hourly) as briefly mentioned
below.
Apart from the readily available reports, customized reports can be prepared from the report builder using different
counters
Item 3G RAN Reports Report Name Object Type Object Aggregation Time Aggregation Measurement Period
1 System Program RSRAN000 PLMN PLMN Daily 4 Weeks
2 System Program RSRAN000 PLMN RNC Daily 4 Weeks
3 System Program RSRAN000 PLMN WCEL Daily 4 Weeks
4 Capactiy RSRAN066, RSRAN067 PLMN WCEL Daily 4 Weeks
5 Capactiy RSRAN066, RSRAN068 PLMN WCEL Hourly 4 Weeks
6 Service Level RSRAN073, RSRAN079 PLMN WCEL Daily 4 Weeks
7 ServiceLevel RSRAN073, RSRAN079 PLMN WCEL Hourly 4 Weeks

RSRAN070, RSRAN077
8 Traffic PLMN WCEL Daily 4 Weeks
RSRAN070, RSRAN077
9 Traffic PLMN WCEL Hourly 4 Weeks
RSRAN033 , RSRAN018,
RSRAN019, RSRAN023
RSRAN044, RSRAN045
10 Mobility & Handover RSRAN046 PLMN WCEL Daily 4 Weeks
RSRAN033 , RSRAN018,
RSRAN019, RSRAN023
RSRAN044, RSRAN045
11 Mobility & Handover RSRAN046 PLMN WCEL Hourly 4 Weeks
12 HSPA RSRAN051, RSRAN039 PLMN WCEL Daily 4 Weeks
13 HSPA RSRAN051, RSRAN039 PLMN WCEL Hourly 4 Weeks
14 Signalling RSRAN027, RSRAN0238 PLMN WCEL Daily 4 Weeks
15 Signalling RSRAN027, RSRAN038 PLMN WCEL Hourly 4 Weeks

2419 NSN PMI MM/YY – FileName.ppt
Perform data analysis and assessment
1. Assess weekly average PLMN/RNC KPI performance to identify KPIs below targets
Start from bigger picture assessment (PLNM -> RNC -> Cluster -> WCEL )
Weekly average will smooth the performance and gives better accuracy of performance assessment as
daily performance varies a lot (especially in unloaded network)
2. Assess network performance at RNC/Area level to check if bad performance happens

across network or only particular RNC/Area
Compare different RNC/Regions performance
3. Apply drill down approach to assess bad performing KPIs in WCEL level
Identify the failures in call phases (refer call flow)
Categorizing failure ratio or distribution of each counters (radio, AC, transmission, BTS, RNC)
Identify main cause of underperforming KPIs
4. Prioritize analysis
Filter using high number of failures or high number failure ratio (weighting)
Identify top 50 worst cells
5. Look at failure distribution in the network topology (rural, RNC border, expressway)
6. Make solution proposal to improve KPIs
Low CSSR Service Level -> RSRAN073
AMR RAB setup/access Analysis
1. Check the problem cells and its neighbouring cells of any faulty alarms
2. Identify root cause failure distribution and main failure contributor using Services -> RSRAN073
3. RAB_STP_FAIL_XXX_AC
Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity
REQ_CS_VOICE_REJ_UL_SRNC -> Evaluate Prx cell resource
REQ_CS_VOICE_REJ_DL_SRNC -> Evaluate Ptx cell resource
NO_CODES_AVAILABLE_SF128/SF256 -> Evaluate AMR voice code congestion
Check parameter setting with UL throughput based AC and power based AC
4. RAB_STP_FAIL_XXX_BTS
Evaluate NBAP counters (radio link reconf. Add failures) and KPIs for troubleshooting BTS resources
Check BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to evaluate
lack of Channel Elements
Expand the Capacity or decrease the traffic offered to the site by virtue of SHO, power & site footprint control
5. RAB_STP_FAIL_XXX_TRANS
Evaluate Number of reconfiguration failure due the transmission
Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL
Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533
6. RAB_ACC_FAIL_XXX_UE
Evaluate Cell resource Prx and Ptx (for example high uplink interference)
Check RB reconfiguration failure ration ( If offset for activation time (RNC) setting is insufficient – recommended is 500-
700ms )
7. RAB_ACC_FAIL_XXX_RNC
Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)
Required ICSU log tracing if no RNC fault or SRNC relocation problem
Service -> RSRAN073
Low CSSR
Rel99 NRT RAB Setup Success Analysis
There is two ways to evaluate the Rel99 NRT RAB setup success performance
M1001, RNC_576e Packet Service Setup Success Ratio (CSSR) / CSSR PS NRT
M1022, RNC_943a R99 Setup Success Ratio from user perspective for NRT/ R99 stp SR Usr
Since RNC_576c (M1001) is measured NRT DCH setup upto 0/0kbps, it is always showing >99.5%. So it is not useful for
data call setup analysis
Packet calls starts with user plane capacity allocation (transfer from FACH/PCH, DCH 0/0) and ends with dedicated
resource release (transfer back to FACH/PCH, DCH 0/0, RAB release, outgoing relocation, HHO, ISHO)
M1001 M1022

Low CSSR
Rel99 NRT RAB Setup Success Analysis in RU10
The number of NRT DCH setup rejects for interactive/BG traffic class due to running out of channelization codes in
DL and power in DL/UL (This counter includes initial DCH setups, handover attempts and channel type switches
from HS-DSCH to DCH)
The number of NRT DCH reconfiguration rejects (bitrate upgrade) for interactive/BG traffic class due to running out
of channelization codes in DL and power in DL/UL
Iur resources setup fails during user plane allocation/modification of PS NRT RAB over IUR branch
100.00 300.00 M1002C553 Traffic REJ_DCH_DUE_CODES_INT_DL

M1002C554 Traffic REJ_DCH_DUE_CODES_BGR_DL
90.00
M1002C555 Traffic REJ_DCH_DUE_POWER_INT_DL
250.00
80.00 M1002C556 Traffic REJ_DCH_DUE_POWER_BGR_DL
M1002C557 Traffic REJ_DCH_REC_DUE_CODES_INT_DL
max, ave occupancy & blocking (% )
70.00
200.00
M1002C558 Traffic REJ_DCH_REC_DUE_CODES_BGR_DL
60.00
M1002C559 Traffic REJ_DCH_REC_DUE_PWR_INT_DL
M1002C560 Traffic REJ_DCH_REC_DUE_PWR_BGR_DL
50.00 150.00
M1002C626 Traffic REJ_DCH_DUE_POWER_INT_UL

40.00
M1002C627 Traffic REJ_DCH_DUE_POWER_BGR_UL
100.00
30.00 M1002C628 Traffic REJ_DCH_REC_DUE_PWR_INT_UL
M1002C629 Traffic REJ_DCH_REC_DUE_PWR_BGR_UL
20.00
Reconfig reject 50.00
NRT DCH SETUP FAIL DUE TO
10.00 due to lack of M1004C165 FAIL_NRT_DCH_SETUP_IUR IUR
0.00
codes 0.00 FAIL_NRT_DCH_UL_RECONF NRT DCH UL RECONFIG FAIL
1 11 21 31 41 51 61 71 81 91 101 111 121 131 141 151 161
M1004C166 _IUR FOR NRT RB DUE TO IUR
RNC_11a_Average code occupancy RNC_520b_Max Occupancy RNC_949a Code blocking rate FAIL_NRT_DCH_DL_RECONF NRT DCH DL RECONFIG FAIL
Rej DCH due codes Rej DCH REC due codes M1004C167 _IUR FOR NRT RB DUE TO IUR

Low Packet/session success rate (SSSR)
Service -> RSRAN073
Rel99 Packet session setup failures Analysis (M1022)
Check KPI RNC_943a for low Rel99 packet SSSR 100 ⋅

∑ M1022C31 D_D_REQ_D_ D_ALLO_INT + M1022C32 D_D_REQ_D_ D_ALLO_BGR
∑ M1022C7 PS_ATT_DCH _DCH_INT + M1022C8 PS_ATT_DCH _DCH_BGR
Cannot differentiate Rel99

Evaluate Dominant failures: DCH , HSDPA, HSUPA
setup failure
AC failure : lack of DL power or high UL interference, UL
admission control parameter setting
Other failure: This could be due to max HSPA users

limit reached or “radio link failure” during setup
BTS failure: lack of HW CE capacity
DMCU failure: DMCU/DSP faulty or lack of DSP

resources in RNC
TRANS failure: lack of Iub capacity
UE failure: UE internal problem (not capability issue)

M1022 Rel99 Packet session setup failures Analysis
Counters available to identify the Rel99 NRT DCH setup and successful setup based on initial request
bit rates or DCH upgrade bit rates
Uplink initial request and success include also HSDPA UL return channel
This is useful to identify each of the bit rate setup performance and its distribution as well as capacity
bottleneck
M1022C83 Packet_call INIT_DCH_REQ_64_UL M1022C91 Packet_call DCH_UPGR_REQ_64_UL
M1022C84 Packet_call INIT_DCH_REQ_64_DL M1022C92 Packet_call DCH_UPGR_REQ_64_DL
M1022C99 Packet_call SUCC_INIT_ALLO_64_UL M1022C115 Packet_call SUCC_UPG_NRT_DCH_64_UL
M1022C100 Packet_call SUCC_INIT_ALLO_64_DL M1022C116 Packet_call SUCC_UPG_NRT_DCH_64_DL
M1022C107 Packet_call SUCC_INIT_ALLO_REQ_64_UL M1022C123 Packet_call SUCC_UPG_NRT_DCH_REQ_64_UL
M1022C108 Packet_call SUCC_INIT_ALLO_REQ_64_DL M1022C124 Packet_call SUCC_UPG_NRT_DCH_REQ_64_DL

M1022 Rel99 Packet session setup failures Analysis
Counters available also to identify the Rel99 NRT DCH
DCH UPLINK RECONFIG FAIL DUE TO
Reconfiguration failure during initial request (DCH0/0 to DCH x/x kbps M1022C143 FAIL_REC_INTERA_DCH_UL_OTH OTHER REASONS FOR INTERACTIVE
or cell Fach to DCH) and bit rate upgrade request
Also HSDPA uplink allocations update these counters DCH UPLINK RECONFIG FAIL DUE TO
M1022C144 FAIL_REC_BGR_DCH_UL_OTH OTHER REASONS FOR BACKGROUND
DCH DOWNLINK RECONFIG FAIL DUE TO

M1022C145 FAIL_REC_INTERA_DCH_DL_OTH OTHER REASONS FOR INTERACTIVE
M1022C13 DCH UPLINK RECONFIG FAIL DUE
5 FAIL_REC_INTERA_DCH_UL_BTS TO BTS FOR INTERACTIVE
DCH DOWNLINK RECONFIG FAIL DUE TO
M1022C13 DCH UPLINK RECONFIG FAIL DUE M1022C146 FAIL_REC_BGR_DCH_DL_OTH OTHER REASONS FOR BACKGROUND
6 FAIL_REC_BGR_DCH_UL_BTS TO BTS FOR BACKGROUND
M1022C13 DCH DOWNLINK RECONFIG FAIL

7 FAIL_REC_INTERA_DCH_DL_BTS DUE TO BTS FOR INTERACTIVE
M1022C13 DCH DOWNLINK RECONFIG FAIL

8 FAIL_REC_BGR_DCH_DL_BTS DUE TO BTS FOR BACKGROUND In DL, Failures mainly from
M1022C13 FAIL_REC_INTERA_DCH_UL_A DCH UPLINK RECONFIG FAIL DUE TO
AC (Interactive and
9 C AC FOR INTERACTIVE 2 000.00 Background)
FAIL_REC_BGR_DCH_DL_TRAN
M1022C14 DCH UPLINK RECONFIG FAIL DUE TO 1 800.00
S
0 FAIL_REC_BGR_DCH_UL_AC AC FOR BACKGROUND 1 600.00 FAIL_REC_INTERA_DCH_DL_TR
ANS
M1022C14 FAIL_REC_INTERA_DCH_DL_A DCH DOWNLINK RECONFIG FAIL DUE 1 400.00 FAIL_REC_INTERA_DCH_DL_BT
1 C TO AC FOR INTERACTIVE S
1 200.00 FAIL_REC_BGR_DCH_DL_BTS
M1022C14 DCH DOWNLINK RECONFIG FAIL DUE
2 FAIL_REC_BGR_DCH_DL_AC TO AC FOR BACKGROUND 1 000.00
FAIL_REC_INTERA_DCH_DL_AC
M1022C13 FAIL_REC_INTERA_DCH_UL_TRAN DCH UPLINK RECONFIG FAIL DUE 800.00
FAIL_REC_BGR_DCH_DL_AC
1 S TO TRANSPORT FOR INTERACTIVE
600.00
M1022C13 DCH UPLINK RECONFIG FAIL DUE FAIL_REC_INTERA_DCH_DL_OT
400.00 H
2 FAIL_REC_BGR_DCH_UL_TRANS TO TRANSPORT FOR BACKGROUND
FAIL_REC_BGR_DCH_DL_OTH
200.00
DCH DOWNLINK RECONFIG FAIL
M1022C13 FAIL_REC_INTERA_DCH_DL_TRAN DUE TO TRANSPORT FOR 0.00
3 S INTERACTIVE 1 10 19 28 37 46 55 64 73 82 91 100 109 118
DCH DOWNLINK RECONFIG FAIL
M1022C13 DUE TO TRANSPORT FOR
4 FAIL_REC_BGR_DCH_DL_TRANS BACKGROUND
Low HSDPA Accessibility System Program – RNC_605a
Service Level –RNC_914a
HSDPA Accessibility failure cause analysis can be done with traffic measurements
(RNC_605b) and Packet call measurements (RNC_914b)
Low HSDPA
No Based on Traffic
accessibility No Action Needed
(RNC_605b) measurement
Yes analysis (M1002)
Check Number of simultaneous HSDPA users in BTS or
Too many HSDPA users Yes
cell level depending on the scheduler type
reached
No
HSDPA Setup Fail due Yes Check BH Channel Element resource Usage
BTS (Lack of CE for UL return Channel)
No
Rejection of UL Return Yes Check BH UL Power Congestion

Channel Rejections (Lack of Radio resources for UL return Ch.)
No
HSDPA Setup Fail Iub Yes Check BH AAL2 Iub congestion

(Both UL & DL) (Lack of Iub resources for UL return Ch.)
No
Yes Check RB reconfiguration failure rate
HSDPA Setup Fail UE (Terminal Problem)
No
HSDPA Setup Fail Yes Check RNC Unit load (DMPG), max number of
RNC Internal users/RNC, DSP failures and faulty alarms

Low HSDPA Accessibility
HSDPA Accessibility failure analysis based on Packet Call Measurement (M1022)
Low HSPA Setup RSRAN073 Problem In

Performance (RNC_914b)
PS Setup Failure Yes
Air Interface
due AC
No
PS Setup Failure Yes
BTS
due BTS
If not DMCU faulty,
No check DSP resource
PS Setup Failure Yes usage and availability
Iub with RU M609 DSP
due Iub
Others failure Service Stats and
could be max No
M615 DSP Resource.
HSPA users been PS Setup Failure due to, Yes
RNC
DMCU
reached or “radio
link failure” during No
setup PS Setup failure due to Yes
High Traffic Event
Others
PS Setup failure due to

Terminal Issue?
UE
Yes
No action needed
There are counters in packet call to identify packet call attempt to cells which are not HSPA enabled.
New KPI (RNC_914b) gives better results in terms of HSDPA accessibility when networks mixed with
HSPA and non-HSPA enabled cells. This avoids separate aggregation which required previously in
RAS06.
RNC_914b does not include statistics from serving cell change mobility. Thus, the performance could
be lower as well due to statistical calculation
RNC_914b: (NetAct names) RNC_605b: (NetAct names)

100*
100* sum(HS_E_REQ_HS_E_ALLO_INT + sum(ALLO_HS_DSCH_FLOW_INT+ALLO_HS_DSCH_FL
HS_E_REQ_HS_E_ALLO_BGR + OW_BGR) / sum(ALLO_HS_DSCH_FLOW_INT +
HS_E_REQ_HS_D_ALLO_INT + ALLO_HS_DSCH_FLOW_BGR +
HS_E_REQ_HS_D_ALLO_BGR + REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR
The number of
HS_D_REQ_HS_D_ALLO_INT + DCH/DCH
+ SETUP_FAIL_RNC_HS_DSCH_INT +
HS_D_REQ_HS_D_ALLO_BGR) / allocations after an SETUP_FAIL_BTS_HS_DSCH_INT +
sum(PS_ATT_HSDSCH_EDCH_INT + HS-DCSH/E-DCH SETUP_FAIL_IUB_HS_TOTAL_INT +
request for the
PS_ATT_HSDSCH_EDCH_BGR + background traffic SETUP_FAIL_RNC_HS_DSCH_BGR +
PS_ATT_HSDSCH_DCH_INT + class due to the cell SETUP_FAIL_BTS_HS_DSCH_BGR +
not supporting
PS_ATT_HSDSCH_DCH_BGR - HSUPA and HSDPA
SETUP_FAIL_IUB_HS_TOTAL_BGR +
HS_D_REQ_D_D_ALLO_BGR_CELL - SETUP_FAIL_UE_HS_DSCH_INT +
HS_D_REQ_D_D_ALLO_INT_CELL - SETUP_FAIL_UE_HS_DSCH_BGR +
HS_E_REQ_D_D_ALLO_BGR_CELL - DCH_SEL_MAX_HSDPA_USERS_INT +
HS_E_REQ_D_D_ALLO_INT_CELL) DCH_SEL_MAX_HSDPA_USERS_BGR)

Low HSDPA Accessibility Service level -> RSRAN073
1. Identify root cause of failure distribution and main failure contributor
2. If high HSDPA Access Failure _too many HSDPA users

Check simultaneous HSDPA users (RNC_646c to RNC_654c) & (RNC_1028b to RNC_1035b) &
(RNC_1665a to RNC_1668a) M1000C282 Cell_Resource MAX_HSDPA_USERS_IN_CELL
M1000C283 Cell_Resource MAX_HSUPA_USERS_IN_CELL
RU10 new counters on max & average HSPA users M1000C284 Cell_Resource SUM_HSDPA_USERS_IN_CELL
M1000C285 Cell_Resource DENOM_HSDPA_USERS_PER_CELL
M1000C286 Cell_Resource SUM_HSUPA_USERS_IN_CELL
3. If high HSDPA Access Failure_UL DCH M1000C287 Cell_Resource DENOM_HSUPA_USERS_PER_CELL
Rejected HS-DSCH return channel due to lack of radio power resource

Check M1002C521 or M1002C522 or M1000C144 – only when HSDPA static allocation
Check Cell resource PrxTotal, PtxTotal
Check parameter setting for uplink throughput based and interference based admission control
M1006C149 RRC ATT_RB_SETUP_HSDPA
4. If high HSDPA Access Failure_UE M1006C150 RRC SUCC_RB_SETUP_HSDPA
M1006C192 RRC FAIL_RB_SETUP_HSDPA_NOREPLY
Check RB reconfiguration failure rate
M1006C193 RRC FAIL_RB_SETUP_HSDPA_UE
ICSU log for UE types troubleshooting ?
Counters to measure HSDPA setup success in RB reconfiguration phase

5. If high HSDPA Access Failure_BTS
Lack of UL channel resources (check CE resource utilisation using M5001 counters at BH)
Too high SHO overhead – all branches must have enough CE capacity if UE is in SHO when HS-DSCH allocation is
started
RU10 brings new counters measure on the setup/success/failure for HSDPA MAC-d setup on NBAP Radio link
Reconfiguration phase
M1005C241 L3Iub ATT_MACD_SETUP_FOR_HSDPA
1200 30
M1005C242 L3Iub SUCC_MACD_SETUP_FOR_HSDPA
M1005C247 L3Iub FAIL_MACD_SETUP_HSDPA_NORESP
1000 25
M1005C248 L3Iub FAIL_MACD_SETUP_HSDPA_RNL
M1005C249 L3Iub FAIL_MACD_SETUP_HSDPA_TR
800 20
M1005C250 L3Iub FAIL_MACD_SETUP_HSDPA_PROT
SETUP_FAIL_BTS_HS_DSCH_BGR (Traffic) M1005C251 L3Iub FAIL_MACD_SETUP_HSDPA_MISC
600 15
AVE_AVAIL_PERC_POOL_CAPA_UL (Cellres)
400 10
200 5
0 0
1 14 27 40 53 66 79 92 105 118 131 144 157 170 183 196 209 222 235 248 261 274 287
6. HS-DSCH return channel setup fail due to Iub transport

Breakdown the failure distribution (64,128,384,MAC-d)
Evaluate RU10 UL rejection failure cause (M1022C131…C146)
Evaluate number of reconfiguration failure due the transmission
Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL
Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533

Low HSDPA Cell/User Throughput System Program -> RSRAN000
HSPA -> RSRAN051
HSPA -> RSRAN039
HSDPA throughput limiting factors:
HSDPA Throughput Analysis

Air interface support
from CQI distribution
HSDPA UL Return Problem in

channel limitation (UL
Interference)
Air Interface
HSDPA Throughput
Available from Iub
Iub
HSDPA UL Return
channel limitation (Iub)
BTS
BTS Power Availability
for HSDPA RNC
Cell Channelisation
code Availability for Iu-PS
HSDPA
BTS scheduler
limitation
(#simultaneous users
per scheduler)
HSDPA UL Return
channel limitation (CE)
RNC limiting factors:

DSP, #simultaneous
HSDPA users and
throughput
Iu-PS capacity
available or HSDPA

System Program -> RSRAN000
Low HSDPA Cell/User Throughput HSPA -> RSRAN051
HSPA -> RSRAN039
Traffic - RSRAN077
1. Check HSDPA active Throughput in the cell (RNC_722b/c) and Average throughput in the cell
(RNC_606c) or with cell throughput in RNC/WBTS measurements (RNC_941a)
KPI RNC_941a : sum ( HS_DSCH_DATA_VOL * 8) /sum ( 1000 * PERIOD_DURATION)* 60 (kbps)
RNC_606c: sum(RECEIVED_HS_MACD_BITS - DISCARDED_HS_MACD_BITS) /

sum(PERIOD_DURATION)*60 (kbps)
M5002C21 Cell_Throughput_WBTS HS_TOTAL_DATA
2. Calculate rough HSDPA User Throughput by dividing RNC_722b with average number of
simultaneous HSDPA users (RNC_726a) or two new KPIs based on users in buffer where v2.1 is
for user throughput <1.5Mbps
End user experience v2.1
=
(RECEIVED_HS_MACD_BITS - DISCARDED_HS_MACD_BITS )⋅ 500
HSDPA_BUFF_WITH_DATA_PER_TTI ⋅ 2
End user experience v3.0
=
(RECEIVED_HS_MACD_BITS - DISCARDED_HS_MACD_BITS)⋅ 500
(HSDPA_USE RS_0_1_IN_CELLS + HSDPA_USER S_1_0_IN_CELLS) +
2 ⋅ (HSDPA_USERS_0_2_IN_CELLS + HSDPA_USERS_1_1_IN_CELLS + HSDPA_USERS_2_0_IN_CELLS)
+ 3 ⋅ (HSDPA_USERS_1_2_IN_CELLS + HSDPA_USERS_2_1_IN_CELLS +
HSDPA_USER S_0_3_IN_CELLS + HSDPA_USERS_3_0_IN_CELLS)
HSDPA_BUFF_WITH_DATA _PER_TTI ⋅
HSDPA_USERS_0_1_IN_CELLS + HSDPA_USERS_1_0_IN_CELLS + HSDPA_USER S_0_2_IN_CELLS +
HSDPA_USERS_1_1_IN_CELLS + HSDPA_USERS_2_0_IN_CELLS + HSDPA_USER S_0_3_IN_CELLS +
HSDPA_USERS_1_2_IN_CELLS + HSDPA_USERS_2_1_IN_CELLS + HSDPA_USER S_3_0_IN_CELLS

Low HSDPA Cell/User Throughput
Below is comparison of all the throughput per user formulas as well as
RNC_722b
Average HSDPA
Throughput per User
has increased a lot
based on users in data
buffer

Low HSDPA cell/user Throughput HSPA -> RSRAN051
HSPA -> RSRAN039
3. Check RNC_706a Ave Reported CQI and CQI distribution (M5000C8-M5000C39) or Ecno
distribution for bad coverage issue (M1007C38-M1007C47)
4. High CQI / Ecno but low HSDPA user throughput
Check problem at core network or application server (FTP, HTTP) or in measurement tools & PC
settings
Check any shortage on Iub user plane and CEs shortage due to DCH traffic is too high
Check if UL return channel is limiting due to interference (PrxLoadMarginMaxDCH -> 0 dB)
Check the if there is code blocking for HSDPA (set HSPDSCHMarginSF128 from 8-> 0)
Check HSDPA power parameter setting (M1000C232-C235) & (M1000C236-C239)
Check simultaneous HSDPA users in the Node B Scheduler (increase the scheduler capacity from 16
users/BTS to 48 users/BTS (16/cell)
Check HSDPA FMCS mobility parameters (lower window add for HSDPA than for R99 to save capacity in
target cell due to smaller SHO OH)
Throughput limitation per user (throttled user) is active in Core?

Low HSDPA Cell/Users Throughput
5. HSDPA power in BTS
The counters tell the number of samples (TTI) per class when the actual used HS-PDSCH power (given as % value from the
max HS-PDSCH pwr) is within the limits defined for a class
This give hints whether low HSDPA throughput due to lack of HSDPA power (high RT/Rel99 NRT traffics in the cell)
M5000C268 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_01
6. DMPG resource sharing causes the total throughput per user is not only limited by the #
simultaneous users per cell and their activity but also the amount of simultaneous users per
DMPG (per RNC sharing the total RNC throughput) and their activity
Max HSDPA Throughput per RNC (62 x 7.2Mbps currently on RNC Throughput 450Mbps)
Sum ( #_users_with_data_in_buff_per_TTI / all_active_TTIs) x avg_#_HSDPA_users_in_RNC
HSDPA_NRTD_PEAK_CALLS

Low HSUPA Accessibility Service Level -> RSRAN073
HSUPA Accessibility KPI is measured with RNC_913a (Traffic Measurement)

If HSDPA setup is failing also HSUPA setup will fail, but it could be also that only HSUPA will fail. The
reasons are similar to HSDPA
RNC_956b E-DCH Setup FR due to BTS (RL reconfiguration failure to RNC)
RNC_1105b E-DCH Setup FR due to Transport (RL reconfiguration cancel from RNC)
RNC_1106b E-DCH Setup FR due to UE (RB reconfiguration failure from UE)
RNC_1104b E-DCH Setup FR due to Other Failures (RNC internal reason)
RNC_1103bE-DCH Allocation FR due to NA AS (due to non-acceptable E-DCH active set)
Also there could be too many HSUPA users (20/cell, 24/NodeB,In RU10:64 users/Node B)
RNC_968b UL DCH Selected due to too many HSUPA users
RNC_969b DL DCH Selected due to the HSDPA power (updated when only HSDPA static power allocation used)
HSUPA setup failed due to BTS reports HSUPA cannot be allocated
RNC_957b E-DCH Not Selected due the BTS HW (BTS sent radio resource measurement report)
M1000C268-C270 – These counters measure the BTS HW limitation during HSUPA Calls

Low HSUPA Accessibility System Program -> RSRAN000
Service Level -> RSRAN073
For static resource allocation the power could limit

M1002C521 DL_DCH_SEL_HSDPA_POWER_INT
M1002C522 DL_DCH_SEL_HSDPA_POWER_BGR
M1002C602DL_DCH_SEL_HSDPA_POWER_STR
AC: (PtxTotal>PtxTargetHSDPA or PtxNC>PtxTargetHSDPA)
EDCH cannot be allocated in case HSUPA is not supported in SHO

branch
M1002C519 EDCH_ALLO_CANC_NA_AS_INT
M1002C520 EDCH_ALLO_CANC_NA_AS_BGR
M1002C601EDCH_ALLO_CANC_NA_AS_STR

Traffic -> RSRAN070/077
Low HSUPA Throughput HSPA -> RSRAN051
HSPA -> RSRAN039
Check Mininum, Maximum & Average HSUPA throughput from WBTS counter measurement (M5000C153)
Check average or data volume HSUPA throughput from Cell Throughput measurement with RNC_952c
sum(NRT_EDCH_UL_DATA_VOL + RT_E_DCH_UL_STREA_DATA) * 8 / sum(PERIOD_DURATION)*1000000*60
Check HSUPA throughput from M5002 Cell Throughput_WBTS and its throughput distributions in classes
Counter ID Measurement Counter name

M5002C41 Cell_Throughput_WBTS UE_HSUPA_TP03
M5002C45 Cell_Throughput_WBTS UE_HSUPA_TP07 Note: HSUPA cell throughput
M5002C38 Cell_Throughput_WBTS UE_HSUPA_TP00 measurement is less accurate
M5002C39 Cell_Throughput_WBTS UE_HSUPA_TP01 than HSDPA cell throughput
M5002C40 Cell_Throughput_WBTS UE_HSUPA_TP02 due to counters updating
M5002C46 Cell_Throughput_WBTS UE_HSUPA_TP08 across total measurement
M5002C47 Cell_Throughput_WBTS UE_HSUPA_TP09 period and not in active data
M5002C48 Cell_Throughput_WBTS UE_HSUPA_TP10 transfer period
M5002C2 Cell_Throughput_WBTS EDCH_DATA_SCELL_UL
M5002C3 Cell_Throughput_WBTS EDCH_DATA_NSC_S_EDCH_UL
M5002C4 Cell_Throughput_WBTS EDCH_DATA_NSC_NS_EDCH_UL
Check HSUPA user throughput by dividing above with KPI RNC_1037a -Average number of simultaneous HSUPA
users, during HSUPA usage

HSPA -> RSRAN039
Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38-
M1007C47)
Check If low throughput due to high number of retransmission & failed retransmission (RNC_917a HSUPA MAC-
es BLER)
Check KPI RNC_1165a/RNC_1166a for low HSUPA throughput due to Iub congestion (frame delay or frame loss)
In RU10, there is new counters to check on the Rise Over Thermal in Fractional load:L = 1 - (Pnoise/Ptotal), The
fractional load is calculated in the normal scheduling operation. HSUPA throughput will be limited by high
fractional load in the cells
M5000C245 FRACT_LOAD_DISTR_CLASS_00 - Ptotal>=Pnoise : (L = 0).

M5000C246 FRACT_LOAD_DISTR_CLASS_01 - Ptotal>=Pnoise : (0 < L <= 0.05)
M5000C247 FRACT_LOAD_DISTR_CLASS_02 - Ptotal>=Pnoise : (0.05 < L <= 0.1)
M5000C265 FRACT_LOAD_DISTR_CLASS_20 - Ptotal>=Pnoise : (0.95 < L <= 1)
HSPA -> RSRAN039
Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue
(M1007C38-M1007C47)
Check If low throughput due to high number of retransmission & failed retransmission (RNC_917a
HSUPA MAC-es BLER)
Check KPI RNC_1165a/RNC_1166a for low HSUPA throughput due to Iub congestion (frame delay
or frame loss)
Check AVG_NON_HSDPA_PWR (M1000C138) & AVG_ACTIVE_NON_HSDPA_PWR to investigate

whether high DCH power (DCH traffic) causes low HSUPA throughput
Others reasons with low HSUPA throughput
Check problem at core network or application server
Check HSPA FMCS / SCC mobility related parameters & performance


Performance Optimization 3G PDF

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

Performance Optimization 3G PDF

Uploaded by

Copyright:

Available Formats

Performance Optimization_3G

-Generic Steps & Procedure

0 of 17 © Nokia-Siemens Siemens Networks

1 System Program RSRAN000 PLMN PLMN Daily 4 Weeks

2 System Program RSRAN000 PLMN RNC Daily 4 Weeks

3 System Program RSRAN000 PLMN WCEL Daily 4 Weeks

4 Capactiy RSRAN066, RSRAN067 PLMN WCEL Daily 4 Weeks

5 Capactiy RSRAN066, RSRAN068 PLMN WCEL Hourly 4 Weeks

6 Service Level RSRAN073, RSRAN079 PLMN WCEL Daily 4 Weeks

7 ServiceLevel RSRAN073, RSRAN079 PLMN WCEL Hourly 4 Weeks

12 HSPA RSRAN051, RSRAN039 PLMN WCEL Daily 4 Weeks

13 HSPA RSRAN051, RSRAN039 PLMN WCEL Hourly 4 Weeks

14 Signalling RSRAN027, RSRAN0238 PLMN WCEL Daily 4 Weeks

15 Signalling RSRAN027, RSRAN038 PLMN WCEL Hourly 4 Weeks

1 of 17 © Nokia-Siemens Siemens Networks

2. Assess network performance at RNC/Area level to check if bad performance happens

AMR RAB setup/access Analysis

4 of 17 © Nokia-Siemens Siemens Networks

100.00 300.00 M1002C553 Traffic REJ_DCH_DUE_CODES_INT_DL

M1002C626 Traffic REJ_DCH_DUE_POWER_INT_UL

5 of 17 © Nokia-Siemens Siemens Networks

Check KPI RNC_943a for low Rel99 packet SSSR 100 ⋅

Cannot differentiate Rel99

Other failure: This could be due to max HSPA users

BTS failure: lack of HW CE capacity

DMCU failure: DMCU/DSP faulty or lack of DSP

TRANS failure: lack of Iub capacity

UE failure: UE internal problem (not capability issue)

6 of 17 © Nokia-Siemens Siemens Networks

7 of 17 © Nokia-Siemens Siemens Networks

DCH DOWNLINK RECONFIG FAIL DUE TO

M1022C13 DCH DOWNLINK RECONFIG FAIL

M1022C13 DCH DOWNLINK RECONFIG FAIL

Rejection of UL Return Yes Check BH UL Power Congestion

HSDPA Setup Fail Iub Yes Check BH AAL2 Iub congestion

9 of 17 © Nokia-Siemens Siemens Networks

Low HSPA Setup RSRAN073 Problem In

PS Setup failure due to

RNC_914b: (NetAct names) RNC_605b: (NetAct names)

11 of 17 © Nokia-Siemens Siemens Networks

1. Identify root cause of failure distribution and main failure contributor

2. If high HSDPA Access Failure _too many HSDPA users

Rejected HS-DSCH return channel due to lack of radio power resource

12 of 17 © Nokia-Siemens Siemens Networks

6. HS-DSCH return channel setup fail due to Iub transport

13 of 17 © Nokia-Siemens Siemens Networks

HSDPA Throughput Analysis

HSDPA UL Return Problem in

RNC limiting factors:

14 of 17 © Nokia-Siemens Siemens Networks

RNC_606c: sum(RECEIVED_HS_MACD_BITS - DISCARDED_HS_MACD_BITS) /

M5002C21 Cell_Throughput_WBTS HS_TOTAL_DATA

15 of 17 © Nokia-Siemens Siemens Networks

16 of 17 © Nokia-Siemens Siemens Networks

17 of 17 © Nokia-Siemens Siemens Networks

Sum ( #_users_with_data_in_buff_per_TTI / all_active_TTIs) x avg_#_HSDPA_users_in_RNC

18 of 17 © Nokia-Siemens Siemens Networks

HSUPA Accessibility KPI is measured with RNC_913a (Traffic Measurement)

19 of 17 © Nokia-Siemens Siemens Networks

For static resource allocation the power could limit

AC: (PtxTotal>PtxTargetHSDPA or PtxNC>PtxTargetHSDPA)

EDCH cannot be allocated in case HSUPA is not supported in SHO

20 of 17 © Nokia-Siemens Siemens Networks