Download - Performance Optimization 3G LUCKNOW
Performance Optimization_3G-Generic Steps & Procedure
0 of 17 © Nokia-Siemens Siemens Networks
~Saptarshi LaskarNPO-RF Planning & Optimization
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 Aggr egation 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
1 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
7 ServiceLevel RSRAN073, RSRAN079 PLMN WCEL Hourly 4 Weeks
8 TrafficRSRAN070, RSRAN077
PLMN WCEL Daily 4 Weeks
9 TrafficRSRAN070, RSRAN077
PLMN WCEL Hourly 4 Weeks
10 Mobility & Handover
RSRAN033 , RSRAN018, RSRAN019, RSRAN023 RSRAN044, RSRAN045
RSRAN046 PLMN WCEL Daily 4 Weeks
11 Mobility & Handover
RSRAN033 , RSRAN018, RSRAN019, RSRAN023 RSRAN044, RSRAN045
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
Perform data analysis and assessment1. 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)
2 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
� 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
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 -> RSRAN0733. 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
Service Level -> RSRAN073
3 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
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
Low CSSRRel99 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)
Service -> RSRAN073
4 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
M1001 M1022
Low CSSRRel99 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
M1002C553 Traffic REJ_DCH_DUE_CODES_INT_DLM1002C554 Traffic REJ_DCH_DUE_CODES_BGR_DLM1002C555 Traffic REJ_DCH_DUE_POWER_INT_DLM1002C556 Traffic REJ_DCH_DUE_POWER_BGR_DL80.00
90.00
100.00
250.00
300.00
5 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
M1002C556 Traffic REJ_DCH_DUE_POWER_BGR_DLM1002C557 Traffic REJ_DCH_REC_DUE_CODES_INT_DLM1002C558 Traffic REJ_DCH_REC_DUE_CODES_BGR_DLM1002C559 Traffic REJ_DCH_REC_DUE_PWR_INT_DLM1002C560 Traffic REJ_DCH_REC_DUE_PWR_BGR_DL
M1002C626 Traffic REJ_DCH_DUE_POWER_INT_ULM1002C627 Traffic REJ_DCH_DUE_POWER_BGR_ULM1002C628 Traffic REJ_DCH_REC_DUE_PWR_INT_ULM1002C629 Traffic REJ_DCH_REC_DUE_PWR_BGR_UL
0.00
10.00
20.00
30.00
40.00
50.00
60.00
70.00
80.00
1 11 21 31 41 51 61 71 81 91 101 111 121 131 141 151 161
max
, av
e oc
cup
ancy
& b
lock
ing
(%)
0.00
50.00
100.00
150.00
200.00
RNC_11a_Average code occupancy RNC_520b_Max Occupancy RNC_949a Code blocking rate
Rej DCH due codes Rej DCH REC due codes
Reconfig reject due to lack of codes
M1004C165 FAIL_NRT_DCH_SETUP_IURNRT DCH SETUP FAIL DUE TO IUR
M1004C166FAIL_NRT_DCH_UL_RECONF_IUR
NRT DCH UL RECONFIG FAIL FOR NRT RB DUE TO IUR
M1004C167FAIL_NRT_DCH_DL_RECONF_IUR
NRT DCH DL RECONFIG FAIL FOR NRT RB DUE TO IUR
Low Packet/session success rate (SSSR)Service -> RSRAN073
Rel99 Packet session setup failures Analysis (M1022)
Evaluate Dominant failures:
AC failure : lack of DL power or high UL interference, UL
Cannot differentiate Rel99 DCH , HSDPA, HSUPA
setup failure
∑∑⋅
_DCH_BGRPS_ATT_DCH M1022C8 +_DCH_INTPS_ATT_DCH M1022C7
D_ALLO_BGRD_D_REQ_D_ M1022C32 +D_ALLO_INTD_D_REQ_D_ M1022C31100� Check KPI RNC_943a for low Rel99 packet SSSR
6 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
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)
Low Packet/session success rate (SSSR)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_ULM1022C84 Packet_call INIT_DCH_REQ_64_DLM1022C85 Packet_call INIT_DCH_REQ_128_ULM1022C86 Packet_call INIT_DCH_REQ_128_DLM1022C87 Packet_call INIT_DCH_REQ_256_ULM1022C88 Packet_call INIT_DCH_REQ_256_DLM1022C89 Packet_call INIT_DCH_REQ_384_UL
M1022C91 Packet_call DCH_UPGR_REQ_64_ULM1022C92 Packet_call DCH_UPGR_REQ_64_DLM1022C93 Packet_call DCH_UPGR_REQ_128_ULM1022C94 Packet_call DCH_UPGR_REQ_128_DLM1022C95 Packet_call DCH_UPGR_REQ_256_ULM1022C96 Packet_call DCH_UPGR_REQ_256_DLM1022C97 Packet_call DCH_UPGR_REQ_384_UL
7 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
M1022C89 Packet_call INIT_DCH_REQ_384_ULM1022C90 Packet_call INIT_DCH_REQ_384_DL
M1022C97 Packet_call DCH_UPGR_REQ_384_ULM1022C98 Packet_call DCH_UPGR_REQ_384_DL
M1022C99 Packet_call SUCC_INIT_ALLO_64_ULM1022C100 Packet_call SUCC_INIT_ALLO_64_DLM1022C101 Packet_call SUCC_INIT_ALLO_128_ULM1022C102 Packet_call SUCC_INIT_ALLO_128_DLM1022C103 Packet_call SUCC_INIT_ALLO_256_ULM1022C104 Packet_call SUCC_INIT_ALLO_256_DLM1022C105 Packet_call SUCC_INIT_ALLO_384_ULM1022C106 Packet_call SUCC_INIT_ALLO_384_DL
M1022C107 Packet_call SUCC_INIT_ALLO_REQ_64_ULM1022C108 Packet_call SUCC_INIT_ALLO_REQ_64_DLM1022C109 Packet_call SUCC_INIT_ALLO_REQ_128_ULM1022C110 Packet_call SUCC_INIT_ALLO_REQ_128_DLM1022C111 Packet_call SUCC_INIT_ALLO_REQ_256_ULM1022C112 Packet_call SUCC_INIT_ALLO_REQ_256_DLM1022C113 Packet_call SUCC_INIT_ALLO_REQ_384_ULM1022C114 Packet_call SUCC_INIT_ALLO_REQ_384_DL
M1022C115 Packet_call SUCC_UPG_NRT_DCH_64_ULM1022C116 Packet_call SUCC_UPG_NRT_DCH_64_DLM1022C117 Packet_call SUCC_UPG_NRT_DCH_128_ULM1022C118 Packet_call SUCC_UPG_NRT_DCH_128_DLM1022C119 Packet_call SUCC_UPG_NRT_DCH_256_ULM1022C120 Packet_call SUCC_UPG_NRT_DCH_256_DLM1022C121 Packet_call SUCC_UPG_NRT_DCH_384_ULM1022C122 Packet_call SUCC_UPG_NRT_DCH_384_DL
M1022C123 Packet_call SUCC_UPG_NRT_DCH_REQ_64_ULM1022C124 Packet_call SUCC_UPG_NRT_DCH_REQ_64_DLM1022C125 Packet_call SUCC_UPG_NRT_DCH_REQ_128_ULM1022C126 Packet_call SUCC_UPG_NRT_DCH_REQ_128_DLM1022C127 Packet_call SUCC_UPG_NRT_DCH_REQ_256_ULM1022C128 Packet_call SUCC_UPG_NRT_DCH_REQ_256_DLM1022C129 Packet_call SUCC_UPG_NRT_DCH_REQ_384_ULM1022C130 Packet_call SUCC_UPG_NRT_DCH_REQ_384_DL
Low Packet/session success rate (SSSR)
� Counters available also to identify the Rel99 NRT DCH Reconfiguration failure during initial request (DCH0/0 to DCH x/x kbps or cell Fach to DCH) and bit rate upgrade request� Also HSDPA uplink allocations update these counters
M1022C135 FAIL_REC_INTERA_DCH_UL_BTS
DCH UPLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE
M1022C136 FAIL_REC_BGR_DCH_UL_BTS
DCH UPLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND
M1022C137 FAIL_REC_INTERA_DCH_DL_BTS
DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE
M1022C13 DCH DOWNLINK RECONFIG FAIL
M1022 Rel99 Packet session setup failures Analysis
M1022C143 FAIL_REC_INTERA_DCH_UL_OTHDCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR INTERACTIVE
M1022C144 FAIL_REC_BGR_DCH_UL_OTHDCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR BACKGROUND
M1022C145 FAIL_REC_INTERA_DCH_DL_OTHDCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS FOR INTERACTIVE
M1022C146 FAIL_REC_BGR_DCH_DL_OTHDCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS FOR BACKGROUND
In DL, Failures mainly from
8 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
M1022C139
FAIL_REC_INTERA_DCH_UL_AC
DCH UPLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE
M1022C140 FAIL_REC_BGR_DCH_UL_AC
DCH UPLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND
M1022C141
FAIL_REC_INTERA_DCH_DL_AC
DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE
M1022C142 FAIL_REC_BGR_DCH_DL_AC
DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND
M1022C138 FAIL_REC_BGR_DCH_DL_BTS
DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND
M1022C131
FAIL_REC_INTERA_DCH_UL_TRANS
DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR INTERACTIVE
M1022C132 FAIL_REC_BGR_DCH_UL_TRANS
DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR BACKGROUND
M1022C133
FAIL_REC_INTERA_DCH_DL_TRANS
DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR INTERACTIVE
M1022C134 FAIL_REC_BGR_DCH_DL_TRANS
DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR BACKGROUND
0.00
200.00
400.00
600.00
800.00
1 000.00
1 200.00
1 400.00
1 600.00
1 800.00
2 000.00
1 10 19 28 37 46 55 64 73 82 91 100 109 118
FAIL_REC_BGR_DCH_DL_TRANS
FAIL_REC_INTERA_DCH_DL_TRANS
FAIL_REC_INTERA_DCH_DL_BTS
FAIL_REC_BGR_DCH_DL_BTS
FAIL_REC_INTERA_DCH_DL_AC
FAIL_REC_BGR_DCH_DL_AC
FAIL_REC_INTERA_DCH_DL_OTH
FAIL_REC_BGR_DCH_DL_OTH
In DL, Failures mainly from AC (Interactive and Background)
Low HSDPA Accessibility
HSDPA Accessibility failure cause analysis can be done with traffic measurements (RNC_605b) and Packet call measurements (RNC_914b)
System Program – RNC_605aService Level –RNC_914a
Low HSDPA accessibility (RNC_605b)
Check Number of simultaneous HSDPA users in BTS or cell level depending on the scheduler type
No Action Needed
Too many HSDPA users reached
No
Yes
Yes
No
Based on Traffic measurement
analysis (M1002)
9 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
Check BH Channel Element resource Usage (Lack of CE for UL return Channel)
Check BH UL Power Congestion(Lack of Radio resources for UL return Ch.)
Check BH AAL2 Iub congestion(Lack of Iub resources for UL return Ch.)
Check RB reconfiguration failure rate(Terminal Problem)
Check RNC Unit load (DMPG), max number of users/RNC, DSP failures and faulty alarms
HSDPA Setup Fail due BTS
Rejection of UL Return Channel Rejections
HSDPA Setup Fail Iub (Both UL & DL)
HSDPA Setup Fail UE
HSDPA Setup Fail RNC Internal
Yes
Yes
Yes
Yes
Yes
No
No
No
No
Low HSDPA Accessibility
PS Setup Failure due AC
Low HSPA Setup Performance (RNC_914b)
Yes
No
Air Interface
PS Setup Failure due BTS
Yes
No
BTS
Problem InRSRAN073
HSDPA Accessibility failure analysis based on Packet Call Measurement (M1022)
If not DMCU faulty, check DSP resource
10 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
PS Setup Failure due Iub
Yes
No
Iub
PS Setup Failure due to, DMCU
YesRNC
PS Setup failure due to
Others
No
YesHigh Traffic Event
Yes
PS Setup failure due to
UE
No action needed
Terminal Issue?
Others failure could be max HSPA users been reached or “radio link failure” during setup
check DSP resource usage and availability with RU M609 DSP Service Stats and M615 DSP Resource.
Low HSDPA Accessibility�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)
100* sum(HS_E_REQ_HS_E_ALLO_INT + HS_E_REQ_HS_E_ALLO_BGR +
RNC_605b: (NetAct names)100* sum(ALLO_HS_DSCH_FLOW_INT+ALLO_HS_DSCH_FLOW_BGR) / sum(ALLO_HS_DSCH_FLOW_INT +
11 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
HS_E_REQ_HS_E_ALLO_BGR + HS_E_REQ_HS_D_ALLO_INT + HS_E_REQ_HS_D_ALLO_BGR + HS_D_REQ_HS_D_ALLO_INT + HS_D_REQ_HS_D_ALLO_BGR) / sum(PS_ATT_HSDSCH_EDCH_INT + PS_ATT_HSDSCH_EDCH_BGR + PS_ATT_HSDSCH_DCH_INT + PS_ATT_HSDSCH_DCH_BGR -HS_D_REQ_D_D_ALLO_BGR_CELL -HS_D_REQ_D_D_ALLO_INT_CELL -HS_E_REQ_D_D_ALLO_BGR_CELL -HS_E_REQ_D_D_ALLO_INT_CELL )
OW_BGR) / sum(ALLO_HS_DSCH_FLOW_INT + ALLO_HS_DSCH_FLOW_BGR + REJ_HS_DSCH_RET_INT + REJ_HS_DSCH_RET_BGR+ SETUP_FAIL_RNC_HS_DSCH_INT + SETUP_FAIL_BTS_HS_DSCH_INT + SETUP_FAIL_IUB_HS_TOTAL_INT + SETUP_FAIL_RNC_HS_DSCH_BGR + SETUP_FAIL_BTS_HS_DSCH_BGR + SETUP_FAIL_IUB_HS_TOTAL_BGR + SETUP_FAIL_UE_HS_DSCH_INT + SETUP_FAIL_UE_HS_DSCH_BGR + DCH_SEL_MAX_HSDPA_USERS_INT + DCH_SEL_MAX_HSDPA_USERS_BGR)
The number of DCH/DCH allocations after an HS-DCSH/E-DCH request for the background traffic class due to the cell not supporting HSUPA and HSDPA
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)
� RU10 new counters on max & average HSPA users
Low HSDPA Accessibility Service level -> RSRAN073
M1000C282 Cell_Resource MAX_HSDPA_USERS_IN_CELLM1000C283 Cell_Resource MAX_HSUPA_USERS_IN_CELLM1000C284 Cell_Resource SUM_HSDPA_USERS_IN_CELLM1000C285 Cell_Resource DENOM_HSDPA_USERS_PER_CELL
12 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
3. If high HSDPA Access Failure_UL DCH
� 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
4. If high HSDPA Access Failure_UE
� Check RB reconfiguration failure rate
� ICSU log for UE types troubleshooting ?
� Counters to measure HSDPA setup success in RB reconfiguration phase
M1000C286 Cell_Resource SUM_HSUPA_USERS_IN_CELLM1000C287 Cell_Resource DENOM_HSUPA_USERS_PER_CELL
M1006C149 RRC ATT_RB_SETUP_HSDPAM1006C150 RRC SUCC_RB_SETUP_HSDPAM1006C192 RRC FAIL_RB_SETUP_HSDPA_NOREPLYM1006C193 RRC FAIL_RB_SETUP_HSDPA_UE
Low HSDPA Accessibility5. 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
600
800
1000
1200
15
20
25
30
SETUP_FAIL_BTS_HS_DSCH_BGR (Traffic)
M1005C241 L3Iub ATT_MACD_SETUP_FOR_HSDPAM1005C242 L3Iub SUCC_MACD_SETUP_FOR_HSDPAM1005C247 L3Iub FAIL_MACD_SETUP_HSDPA_NORESPM1005C248 L3Iub FAIL_MACD_SETUP_HSDPA_RNLM1005C249 L3Iub FAIL_MACD_SETUP_HSDPA_TRM1005C250 L3Iub FAIL_MACD_SETUP_HSDPA_PROTM1005C251 L3Iub FAIL_MACD_SETUP_HSDPA_MISC
13 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
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
0
200
400
600
1 14 27 40 53 66 79 92 105 118 131 144 157 170 183 196 209 222 235 248 261 274 2870
5
10
15AVE_AVAIL_PERC_POOL_CAPA_UL (Cellres)
Low HSDPA Cell/User Throughput
� HSDPA throughput limiting factors:
System Program -> RSRAN000 HSPA -> RSRAN051HSPA -> RSRAN039
HSDPA Throughput AnalysisAir interface support from CQI distribution
HSDPA Throughput Available from Iub
BTS Power Availability
HSDPA UL Return channel limitation (Iub)
HSDPA UL Return channel limitation (UL
Interference)
Problem in
Air Interface
Iub
BTS
14 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
BTS Power Availability for HSDPA
Cell Channelisation code Availability for
HSDPA
RNC limiting factors: DSP, #simultaneous HSDPA users and
throughput
Iu-PS capacity available or HSDPA
HSDPA UL Return channel limitation (CE)
RNC
Iu-PS
BTS scheduler limitation
(#simultaneous users per scheduler)
Low HSDPA Cell/User Throughput
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)
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
System Program -> RSRAN000 HSPA -> RSRAN051HSPA -> RSRAN039Traffic - RSRAN077
M5002C21 Cell_Throughput_WBTS HS_TOTAL_DATA
15 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
simultaneous HSDPA users (RNC_726a) or two new KPIs based on users in buffer where v2.1 is for user throughput <1.5Mbps
( )
ELLSS_3_0_IN_CHSDPA_USERELLSS_2_1_IN_CHSDPA_USERELLSS_1_2_IN_CHSDPA_USER
ELLSS_0_3_IN_CHSDPA_USERELLSS_2_0_IN_CHSDPA_USERELLSS_1_1_IN_CHSDPA_USER
ELLSS_0_2_IN_CHSDPA_USERELLSS_1_0_IN_CHSDPA_USERELLSS_0_1_IN_CHSDPA_USERELLS)S_3_0_IN_CHSDPA_USERELLSS_0_3_IN_CHSDPA_USER
ELLSS_2_1_IN_CHSDPA_USERCELLSRS_1_2_IN_(HSDPA_USE3
ELLS)S_2_0_IN_CHSDPA_USERELLSS_1_1_IN_CHSDPA_USERCELLSRS_0_2_IN_(HSDPA_USE2
ELLS)S_1_0_IN_CHSDPA_USERCELLSRS_0_1_IN_(HSDPA_USE
_PER_TTI_WITH_DATAHSDPA_BUFF
500TSHS_MACD_BIDISCARDED_-SS_MACD_BITRECEIVED_H
v3.0experienceuser End
++++++++
+++⋅+
++⋅++
⋅
⋅=
( )2_PER_TTI_WITH_DATAHSDPA_BUFF
500TSHS_MACD_BIDISCARDED_-SS_MACD_BITRECEIVED_H
v2.1experienceuser End
⋅⋅=
Low HSDPA Cell/User Throughput
Below is comparison of all the throughput per user formulas as well as RNC_722b
Average HSDPA
16 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
Average HSDPA Throughput per User has increased a lot
based on users in data buffer
Low HSDPA cell/user Throughput
3. Check RNC_706a Ave Reported CQI and CQI distribution (M5000C8-M5000C39) or Ecnodistribution 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)
System Program -> RSRAN000 HSPA -> RSRAN051HSPA -> RSRAN039
17 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
� 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_01M5000C269 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_02M5000C270 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_03M5000C271 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_04M5000C272 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_05M5000C273 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_06M5000C274 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_07M5000C275 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_08M5000C276 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_09M5000C277 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_10
18 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
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
M5000C277 HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_10
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
� 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)
System Program -> RSRAN000Service Level -> RSRAN073
19 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
� 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
�For static resource allocation the power could limitM1002C521 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
System Program -> RSRAN000Service Level -> RSRAN073
20 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
M1002C519 EDCH_ALLO_CANC_NA_AS_INT
M1002C520 EDCH_ALLO_CANC_NA_AS_BGR
M1002C601EDCH_ALLO_CANC_NA_AS_STR
Low HSUPA Throughput
� Check Mininum, Maximum & Average HSUPA throughput from WBTS counter measurement (M5000C153)
� Check average or data volume HSUPA throughput from Cell Throughput measurement with RNC_952csum(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
Traffic -> RSRAN070/077HSPA -> RSRAN051HSPA -> RSRAN039System Program -> RSRAN000
Counter ID Measurement Counter nameM5002C41 Cell_Throughput_WBTS UE_HSUPA_TP03M5002C42 Cell_Throughput_WBTS UE_HSUPA_TP04M5002C43 Cell_Throughput_WBTS UE_HSUPA_TP05M5002C44 Cell_Throughput_WBTS UE_HSUPA_TP06
21 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
� Check HSUPA user throughput by dividing above with KPI RNC_1037a -Average number of simultaneous HSUPA users, during HSUPA usage
M5002C44 Cell_Throughput_WBTS UE_HSUPA_TP06M5002C45 Cell_Throughput_WBTS UE_HSUPA_TP07M5002C38 Cell_Throughput_WBTS UE_HSUPA_TP00M5002C39 Cell_Throughput_WBTS UE_HSUPA_TP01M5002C40 Cell_Throughput_WBTS UE_HSUPA_TP02M5002C46 Cell_Throughput_WBTS UE_HSUPA_TP08M5002C47 Cell_Throughput_WBTS UE_HSUPA_TP09M5002C48 Cell_Throughput_WBTS UE_HSUPA_TP10M5002C49 Cell_Throughput_WBTS UE_HSUPA_TP11M5002C2 Cell_Throughput_WBTS EDCH_DATA_SCELL_ULM5002C3 Cell_Throughput_WBTS EDCH_DATA_NSC_S_EDCH_ULM5002C4 Cell_Throughput_WBTS EDCH_DATA_NSC_NS_EDCH_UL
Note: HSUPA cell throughput measurement is less accurate than HSDPA cell throughput due to counters updating across total measurement period and not in active data transfer period
Low HSUPA Throughput
�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
Traffic -> RSRAN070/077HSPA -> RSRAN051HSPA -> RSRAN039System Program -> RSRAN000
M5000C245 FRACT_LOAD_DISTR_CLASS_00 - Ptotal>=Pnoise : (L = 0).
M5000C246 FRACT_LOAD_DISTR_CLASS_01
22 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
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)
M5000C248 FRACT_LOAD_DISTR_CLASS_03 - Ptotal>=Pnoise : (0.1 < L <= 0.15)
M5000C249 FRACT_LOAD_DISTR_CLASS_04 - Ptotal>=Pnoise : (0.15 < L <= 0.2)
M5000C250 FRACT_LOAD_DISTR_CLASS_05 - Ptotal>=Pnoise : (0.2 < L <= 0.25)
M5000C251 FRACT_LOAD_DISTR_CLASS_06 - Ptotal>=Pnoise : (0.25 < L <= 0.3)
M5000C252 FRACT_LOAD_DISTR_CLASS_07 - Ptotal>=Pnoise : (0.3 < L <= 0.35)
M5000C253 FRACT_LOAD_DISTR_CLASS_08 - Ptotal>=Pnoise : (0.35 < L <= 0.4)
M5000C254 FRACT_LOAD_DISTR_CLASS_09 - Ptotal>=Pnoise : (0.4 < L <= 0.45)
M5000C255 FRACT_LOAD_DISTR_CLASS_10 - Ptotal>=Pnoise : (0.45 < L <= 0.5)
M5000C256 FRACT_LOAD_DISTR_CLASS_11 - Ptotal>=Pnoise : (0.5 < L <= 0.55)
M5000C257 FRACT_LOAD_DISTR_CLASS_12 - Ptotal>=Pnoise : (0.55 < L <= 0.6)
M5000C258 FRACT_LOAD_DISTR_CLASS_13 - Ptotal>=Pnoise : (0.6 < L <= 0.65)
M5000C259 FRACT_LOAD_DISTR_CLASS_14 - Ptotal>=Pnoise : (0.65 < L <= 0.7)
M5000C260 FRACT_LOAD_DISTR_CLASS_15 - Ptotal>=Pnoise : (0.7 < L <= 0.75)
M5000C261 FRACT_LOAD_DISTR_CLASS_16 - Ptotal>=Pnoise : (0.75 < L <= 0.8)
M5000C262 FRACT_LOAD_DISTR_CLASS_17 - Ptotal>=Pnoise : (0.8 < L <= 0.85)
M5000C263 FRACT_LOAD_DISTR_CLASS_18 - Ptotal>=Pnoise : (0.85 < L <= 0.9)
M5000C264 FRACT_LOAD_DISTR_CLASS_19 - Ptotal>=Pnoise : (0.9 < L <= 0.95)
M5000C265 FRACT_LOAD_DISTR_CLASS_20 - Ptotal>=Pnoise : (0.95 < L <= 1)
Low HSUPA Throughput
�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 delayor frame loss)
Traffic -> RSRAN070/077HSPA -> RSRAN051HSPA -> RSRAN039System Program -> RSRAN000
23 of 17 © Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY – FileName.ppt
� 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