You are on page 1of 24

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 1 2 3 4 5 6 7 8 9 3G RAN Reports System Program System Program System Program Capactiy Capactiy Service Level ServiceLevel Traffic RSRAN070, RSRAN077 Traffic RSRAN033 , RSRAN018, RSRAN019, RSRAN023 RSRAN044, RSRAN045 RSRAN046 RSRAN033 , RSRAN018, RSRAN019, RSRAN023 RSRAN044, RSRAN045 RSRAN046 RSRAN051, RSRAN039 RSRAN051, RSRAN039 RSRAN027, RSRAN0238 RSRAN027, RSRAN038 PLMN WCEL Hourly 4 Weeks Report Name RSRAN000 RSRAN000 RSRAN000 RSRAN066, RSRAN067 RSRAN066, RSRAN068 RSRAN073, RSRAN079 RSRAN073, RSRAN079 RSRAN070, RSRAN077 Object Type PLMN PLMN PLMN PLMN PLMN PLMN PLMN PLMN Object Aggregation PLMN RNC WCEL WCEL WCEL WCEL WCEL WCEL Time Aggregation Daily Daily Daily Daily Hourly Daily Hourly Daily Measurement Period 4 Weeks 4 Weeks 4 Weeks 4 Weeks 4 Weeks 4 Weeks 4 Weeks 4 Weeks

10

Mobility & Handover

PLMN

WCEL

Daily

4 Weeks

11 12 13 14 15

Mobility & Handover HSPA HSPA Signalling Signalling

PLMN PLMN PLMN PLMN PLMN

WCEL WCEL WCEL WCEL WCEL

Hourly Daily Hourly Daily Hourly

4 Weeks 4 Weeks 4 Weeks 4 Weeks 4 Weeks

1 of 17

Nokia-Siemens Siemens Networks

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
2 of 17 Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY FileName.ppt

Low CSSR
AMR RAB setup/access Analysis

Service Level -> RSRAN073

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 500700ms ) 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
3 of 17 Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY FileName.ppt

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

Service -> RSRAN073

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

4 of 17

Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY FileName.ppt

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 90.00

300.00

250.00 80.00 max, ave occupancy & blocking (% ) 70.00 200.00 60.00 50.00 40.00 100.00 30.00 20.00 10.00 0.00 150.00

M1002C553 M1002C554 M1002C555 M1002C556 M1002C557 M1002C558 M1002C559 M1002C560

Traffic Traffic Traffic Traffic Traffic Traffic Traffic Traffic

REJ_DCH_DUE_CODES_INT_DL REJ_DCH_DUE_CODES_BGR_DL REJ_DCH_DUE_POWER_INT_DL REJ_DCH_DUE_POWER_BGR_DL REJ_DCH_REC_DUE_CODES_INT_DL REJ_DCH_REC_DUE_CODES_BGR_DL REJ_DCH_REC_DUE_PWR_INT_DL REJ_DCH_REC_DUE_PWR_BGR_DL

M1002C626 M1002C627 M1002C628 M1002C629


M1004C165

Traffic Traffic Traffic Traffic

REJ_DCH_DUE_POWER_INT_UL REJ_DCH_DUE_POWER_BGR_UL REJ_DCH_REC_DUE_PWR_INT_UL REJ_DCH_REC_DUE_PWR_BGR_UL


NRT DCH SETUP FAIL DUE TO IUR NRT DCH UL RECONFIG FAIL FOR NRT RB DUE TO IUR NRT DCH DL RECONFIG FAIL FOR NRT RB DUE TO IUR

Reconfig reject due to lack of codes


1 11 21 31 41 51 61 71 81 91 101 111 121 131 141 151 161

50.00

FAIL_NRT_DCH_SETUP_IUR FAIL_NRT_DCH_UL_RECONF _IUR FAIL_NRT_DCH_DL_RECONF _IUR

0.00

M1004C166 M1004C167

RNC_11a_Average code occupancy Rej DCH due codes

RNC_520b_M ax Occupancy Rej DCH REC due codes

RNC_949a Code blocking rate

5 of 17

Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY FileName.ppt

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

Evaluate Dominant failures: 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)
6 of 17 Nokia-Siemens Siemens Networks

Cannot differentiate Rel99 DCH , HSDPA, HSUPA setup failure

2419 NSN PMI MM/YY FileName.ppt

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 M1022C84 M1022C85 M1022C86 M1022C87 M1022C88 M1022C89 M1022C90 Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call INIT_DCH_REQ_64_UL INIT_DCH_REQ_64_DL INIT_DCH_REQ_128_UL INIT_DCH_REQ_128_DL INIT_DCH_REQ_256_UL INIT_DCH_REQ_256_DL INIT_DCH_REQ_384_UL INIT_DCH_REQ_384_DL

M1022C91 M1022C92 M1022C93 M1022C94 M1022C95 M1022C96 M1022C97 M1022C98

Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call

DCH_UPGR_REQ_64_UL DCH_UPGR_REQ_64_DL DCH_UPGR_REQ_128_UL DCH_UPGR_REQ_128_DL DCH_UPGR_REQ_256_UL DCH_UPGR_REQ_256_DL DCH_UPGR_REQ_384_UL DCH_UPGR_REQ_384_DL

M1022C99 M1022C100 M1022C101 M1022C102 M1022C103 M1022C104 M1022C105 M1022C106


M1022C107 M1022C108 M1022C109 M1022C110 M1022C111 M1022C112 M1022C113 M1022C114

Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call


Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call

SUCC_INIT_ALLO_64_UL SUCC_INIT_ALLO_64_DL SUCC_INIT_ALLO_128_UL SUCC_INIT_ALLO_128_DL SUCC_INIT_ALLO_256_UL SUCC_INIT_ALLO_256_DL SUCC_INIT_ALLO_384_UL SUCC_INIT_ALLO_384_DL


SUCC_INIT_ALLO_REQ_64_UL SUCC_INIT_ALLO_REQ_64_DL SUCC_INIT_ALLO_REQ_128_UL SUCC_INIT_ALLO_REQ_128_DL SUCC_INIT_ALLO_REQ_256_UL SUCC_INIT_ALLO_REQ_256_DL SUCC_INIT_ALLO_REQ_384_UL SUCC_INIT_ALLO_REQ_384_DL

M1022C115 M1022C116 M1022C117 M1022C118 M1022C119 M1022C120 M1022C121 M1022C122

Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call

SUCC_UPG_NRT_DCH_64_UL SUCC_UPG_NRT_DCH_64_DL SUCC_UPG_NRT_DCH_128_UL SUCC_UPG_NRT_DCH_128_DL SUCC_UPG_NRT_DCH_256_UL SUCC_UPG_NRT_DCH_256_DL SUCC_UPG_NRT_DCH_384_UL SUCC_UPG_NRT_DCH_384_DL

M1022C123 M1022C124 M1022C125 M1022C126 M1022C127 M1022C128 M1022C129 M1022C130

Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call Packet_call

SUCC_UPG_NRT_DCH_REQ_64_UL SUCC_UPG_NRT_DCH_REQ_64_DL SUCC_UPG_NRT_DCH_REQ_128_UL SUCC_UPG_NRT_DCH_REQ_128_DL SUCC_UPG_NRT_DCH_REQ_256_UL SUCC_UPG_NRT_DCH_REQ_256_DL SUCC_UPG_NRT_DCH_REQ_384_UL SUCC_UPG_NRT_DCH_REQ_384_DL

7 of 17

Nokia-Siemens Siemens Networks

2419 NSN PMI MM/YY FileName.ppt

Low Packet/session success rate (SSSR)


M1022 Rel99 Packet session setup failures Analysis
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
M1022C143 FAIL_REC_INTERA_DCH_UL_OTH DCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR INTERACTIVE DCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR BACKGROUND DCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS FOR INTERACTIVE DCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS FOR BACKGROUND

M1022C144

FAIL_REC_BGR_DCH_UL_OTH

M1022C145 M1022C13 5 M1022C13 6 M1022C13 7 M1022C13 8 M1022C13 9 M1022C14 0 M1022C14 1 M1022C14 2 M1022C13 1 M1022C13 2 M1022C13 3 FAIL_REC_INTERA_DCH_UL_BTS FAIL_REC_BGR_DCH_UL_BTS FAIL_REC_INTERA_DCH_DL_BTS FAIL_REC_BGR_DCH_DL_BTS FAIL_REC_INTERA_DCH_UL_A C FAIL_REC_BGR_DCH_UL_AC FAIL_REC_INTERA_DCH_DL_A C FAIL_REC_BGR_DCH_DL_AC DCH UPLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE DCH UPLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND DCH UPLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE DCH UPLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR INTERACTIVE DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR BACKGROUND DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR INTERACTIVE DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR BACKGROUND
2 000.00 1 800.00 1 600.00 1 400.00 1 200.00 1 000.00 800.00

FAIL_REC_INTERA_DCH_DL_OTH

M1022C146

FAIL_REC_BGR_DCH_DL_OTH

In DL, Failures mainly from AC (Interactive and Background)


FAIL_REC_BGR_DCH_DL_TRAN S FAIL_REC_INTERA_DCH_DL_TR ANS FAIL_REC_INTERA_DCH_DL_BT S FAIL_REC_BGR_DCH_DL_BTS FAIL_REC_INTERA_DCH_DL_AC FAIL_REC_BGR_DCH_DL_AC

FAIL_REC_INTERA_DCH_UL_TRAN S FAIL_REC_BGR_DCH_UL_TRANS FAIL_REC_INTERA_DCH_DL_TRAN S

600.00 400.00 200.00 0.00 1 10 19 28 37 46 55 64 73 82 91 100 109 118 FAIL_REC_INTERA_DCH_DL_OT H FAIL_REC_BGR_DCH_DL_OTH

M1022C13 4 FAIL_REC_BGR_DCH_DL_TRANS 8 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

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 accessibility (RNC_605b)
Yes Yes Check Number of simultaneous HSDPA users in BTS or cell level depending on the scheduler type No

No Action Needed

Based on Traffic measurement analysis (M1002)

Too many HSDPA users reached No HSDPA Setup Fail due BTS No Rejection of UL Return Channel Rejections No HSDPA Setup Fail Iub (Both UL & DL) No

Yes

Check BH Channel Element resource Usage (Lack of CE for UL return Channel)

Yes

Check BH UL Power Congestion (Lack of Radio resources for UL return Ch.)

Yes

Check BH AAL2 Iub congestion (Lack of Iub resources for UL return Ch.)

Yes HSDPA Setup Fail UE No HSDPA Setup Fail RNC Internal


9 of 17 Nokia-Siemens Siemens Networks

Check RB reconfiguration failure rate (Terminal Problem)

Yes

Check RNC Unit load (DMPG), max number of users/RNC, DSP failures and faulty alarms

2419 NSN PMI MM/YY FileName.ppt

Low HSDPA Accessibility


HSDPA Accessibility failure analysis based on Packet Call Measurement (M1022)

Low HSPA Setup Performance (RNC_914b)


PS Setup Failure due AC

RSRAN073
Yes

Problem In
Air Interface

No
PS Setup Failure due BTS

Yes

BTS

No
PS Setup Failure due Iub

Yes

Iub

Others failure could be max HSPA users been reached or radio link failure during setup

No
PS Setup Failure due to, DMCU

If not DMCU faulty, check DSP resource usage and availability with RU M609 DSP Service Stats and M615 DSP Resource.

Yes

RNC

No
PS Setup failure due to Others

Yes

High Traffic Event

PS Setup failure due to UE

Terminal Issue?

No action needed
10 of 17 Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY FileName.ppt

Yes

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 + HS_E_REQ_HS_D_ALLO_INT + HS_E_REQ_HS_D_ALLO_BGR + The number of HS_D_REQ_HS_D_ALLO_INT + DCH/DCH HS_D_REQ_HS_D_ALLO_BGR) / allocations after an sum(PS_ATT_HSDSCH_EDCH_INT + HS-DCSH/E-DCH request for the PS_ATT_HSDSCH_EDCH_BGR + background traffic class due to the cell PS_ATT_HSDSCH_DCH_INT + not supporting PS_ATT_HSDSCH_DCH_BGR HSUPA and HSDPA 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)

RNC_605b: (NetAct names) 100* sum(ALLO_HS_DSCH_FLOW_INT+ALLO_HS_DSCH_FL 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)

11 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

Low HSDPA Accessibility


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

Service level -> RSRAN073

2. If high HSDPA Access Failure _too many HSDPA users Check simultaneous HSDPA users (RNC_646c to RNC_654c) & (RNC_1028b to RNC_1035b) & M1000C282 Cell_Resource MAX_HSDPA_USERS_IN_CELL (RNC_1665a to RNC_1668a) M1000C283 Cell_Resource MAX_HSUPA_USERS_IN_CELL RU10 new counters on max & average HSPA users M1000C284 Cell_Resource SUM_HSDPA_USERS_IN_CELL 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 M1006C150 M1006C192 Check RB reconfiguration failure rate M1006C193 ICSU log for UE types troubleshooting ? Counters to measure HSDPA setup success in RB reconfiguration phase
12 of 17 Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY FileName.ppt

M1000C285 Cell_Resource DENOM_HSDPA_USERS_PER_CELL M1000C286 Cell_Resource SUM_HSUPA_USERS_IN_CELL M1000C287 Cell_Resource DENOM_HSUPA_USERS_PER_CELL

M1006C149 RRC RRC RRC RRC

ATT_RB_SETUP_HSDPA SUCC_RB_SETUP_HSDPA FAIL_RB_SETUP_HSDPA_NOREPLY FAIL_RB_SETUP_HSDPA_UE

Low HSDPA Accessibility


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
1200 30

1000

25

800

20

SETUP_FAIL_BTS_HS_DSCH_BGR (Traffic) 600 15 AVE_AVAIL_PERC_POOL_CAPA_UL (Cellres)

M1005C241 M1005C242 M1005C247 M1005C248 M1005C249 M1005C250 M1005C251

L3Iub L3Iub L3Iub L3Iub L3Iub L3Iub L3Iub

ATT_MACD_SETUP_FOR_HSDPA SUCC_MACD_SETUP_FOR_HSDPA FAIL_MACD_SETUP_HSDPA_NORESP FAIL_MACD_SETUP_HSDPA_RNL FAIL_MACD_SETUP_HSDPA_TR FAIL_MACD_SETUP_HSDPA_PROT FAIL_MACD_SETUP_HSDPA_MISC

400

10

200

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 (M1022C131C146) 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
13 of 17 Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY FileName.ppt

Low HSDPA Cell/User Throughput


HSDPA throughput limiting factors:
HSDPA Throughput Analysis
Air interface support from CQI distribution HSDPA UL Return channel limitation (UL Interference) HSDPA Throughput Available from Iub HSDPA UL Return channel limitation (Iub) BTS Power Availability for HSDPA Cell Channelisation code Availability for 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
14 of 17 Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY FileName.ppt

System Program -> RSRAN000 HSPA -> RSRAN051 HSPA -> RSRAN039

Problem in
Air Interface Iub BTS RNC Iu-PS

Low HSDPA Cell/User Throughput


1.

System Program -> RSRAN000 HSPA -> RSRAN051 HSPA -> RSRAN039 Traffic - RSRAN077

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
(RECEIVED_HS_MACD_BITS - DISCARDED_HS_MACD_BITS) 500

End user experience v3.0 =

(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

15 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

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

16 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

Low HSDPA cell/user Throughput


3. 4.

System Program -> RSRAN000 HSPA -> RSRAN051 HSPA -> RSRAN039

Check RNC_706a Ave Reported CQI and CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38-M1007C47) 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?

17 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

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 M5000C269 M5000C270 M5000C271 M5000C272 M5000C273 M5000C274 M5000C275 M5000C276 M5000C277 HSDPA_WBTS HSDPA_WBTS HSDPA_WBTS HSDPA_WBTS HSDPA_WBTS HSDPA_WBTS HSDPA_WBTS HSDPA_WBTS HSDPA_WBTS HSDPA_WBTS SAMPLE_HS_PDSCH_PWR_CLASS_01 SAMPLE_HS_PDSCH_PWR_CLASS_02 SAMPLE_HS_PDSCH_PWR_CLASS_03 SAMPLE_HS_PDSCH_PWR_CLASS_04 SAMPLE_HS_PDSCH_PWR_CLASS_05 SAMPLE_HS_PDSCH_PWR_CLASS_06 SAMPLE_HS_PDSCH_PWR_CLASS_07 SAMPLE_HS_PDSCH_PWR_CLASS_08 SAMPLE_HS_PDSCH_PWR_CLASS_09 SAMPLE_HS_PDSCH_PWR_CLASS_10

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

18 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

Low HSUPA Accessibility

System Program -> RSRAN000 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

19 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

Low HSUPA Accessibility


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)

System Program -> RSRAN000 Service Level -> RSRAN073

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

20 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

Low HSUPA Throughput

Traffic -> RSRAN070/077 HSPA -> RSRAN051 HSPA -> RSRAN039 System Program -> RSRAN000

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
M5002C41 M5002C42 M5002C43 M5002C44 M5002C45 M5002C38 M5002C39 M5002C40 M5002C46 M5002C47 M5002C48 M5002C49 M5002C2 M5002C3 M5002C4 Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS Cell_Throughput_WBTS

Counter name
UE_HSUPA_TP03 UE_HSUPA_TP04 UE_HSUPA_TP05 UE_HSUPA_TP06 UE_HSUPA_TP07 UE_HSUPA_TP00 UE_HSUPA_TP01 UE_HSUPA_TP02 UE_HSUPA_TP08 UE_HSUPA_TP09 UE_HSUPA_TP10 UE_HSUPA_TP11 EDCH_DATA_SCELL_UL EDCH_DATA_NSC_S_EDCH_UL 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

Check HSUPA user throughput by dividing above with KPI RNC_1037a -Average number of simultaneous HSUPA users, during HSUPA usage

21 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt

Low HSUPA Throughput

Traffic -> RSRAN070/077 HSPA -> RSRAN051 HSPA -> RSRAN039 System Program -> RSRAN000

Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38M1007C47) Check If low throughput due to high number of retransmission & failed retransmission (RNC_917a HSUPA MACes 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) 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) 22 of 17 Nokia-Siemens Siemens Networks
2419 NSN PMI MM/YY FileName.ppt

Low HSUPA Throughput

Traffic -> RSRAN070/077 HSPA -> RSRAN051 HSPA -> RSRAN039 System Program -> RSRAN000

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

23 of 17 Nokia-Siemens Siemens Networks


2419 NSN PMI MM/YY FileName.ppt