You are on page 1of 119

1/119 Document Type Document Title

Author Date, Version
Unit/Dept. For internal use only

Nokia Siemens Networks

Data/MBB Performance Optimisation Guide

For Internal Use Only

NPO/NSO Capability Management Date: 13.4.2011
Data Performance Optimisation Guide for Version 2.2
RU10/RU20

Copyright © Nokia Siemens Networks. This material, including
documentation and any related computer programs, is protected by
copyright controlled by Nokia Siemens Networks. All rights are reserved.
Copying, including reproducing, storing, adapting or translating, any or all
of this material requires the prior written consent of Nokia Siemens
Networks. This material also contains confidential information which may
not be disclosed to others without the prior written consent of Nokia
Siemens Networks

Copyright © Nokia Siemens Networks 2008 Company confidential Page 2 (119)

NPO/NSO Capability Management Date: 13.4.2011
Data Performance Optimisation Guide for Version 2.2
RU10/RU20

Revision History

Date Rev. Summary of Change

25.9.2008 v.0.1 Document created
23.12.2008 v.0.6 First draft for review
19.1.2009 v.0.7 Initial reviewed version for RAS06
28.7.2009 v.1.0 First version for RAS06/RU10
31.12.2009 v. 1.1 Updated for RU10
15.10.2010 V.2.0 Updated for RU20
17.11.2010 v.2.1 Small updates; DC HSDPA etc.
13.4.2011 v.2.2 Small corrections & addings

Jarkko Itkonen, Kirsi
Editor/s:
Teräväinen, Pekka Ranta
Date: 13.4.2010
Version: v.2.2

Copyright © Nokia Siemens Networks 2008 Company confidential Page 3 (119)

............................1...........8 2 PS Data connection signalling.74 6...................................................................................................................................1..........1..........................................................1 Accessibility..................................................1........ 17 2.......................................... 15 2................................................................................. 94 6...................... Code and CE (HSUPA) sharing................................................2 Definition of PS RAB QoS in connection setup.............................................1 HSDPA accessibility......................... 26 3..........2.....................14 2............2 HSDPA throughput Monitoring and troubleshooting.....................................83 6......4 DC HSDPA throughput and Performance......................... 14 2..2.............................3 MIMO throughput performance & monitoring...........7 Packet data connection mobility..4................................................................................................................2011 Data Performance Optimisation Guide for Version 2..............2........................................................................................78 6...........2 HSUPA throughput monitoring and troubleshooting....................................... 101 Copyright © Nokia Siemens Networks 2008 Company confidential Page 4 (119) ....................... 97 7 HSPA & R99 bearer interworking..............................101 7........................................................1 HSDPA peak performance and configurations.............................................................2 Retainability................51 6.................51 6...................................................................................27 5 NRT PS RAB performance...........4............................................................................................1 HSUPA Peak performance and configuration...........78 6....1 Specification............................................................................ 33 6 HSPA bearer performance.........................1 Accessibility..............................................................3 PDP context setup...........................5 Direct Resource Allocation for HSPA...........4....................................................................2........................................................2 SRB on HSPA........................20 2..........................................56 6.. NPO/NSO Capability Management Date: 13...............................................................................................1.........................................................................4.......... 31 5...............................................1 RRC Setup.......................4............................1.................. 13 2...........................................................................................2 Service Request....23 3 PS RAB QoS parameters.............2.4................3 Fast Dormancy..............................4.3 Round Trip Time (RTT).....................................................26 4 UE Categories and Monitoring.........9 2...................100 7................................2.......2 RU10/RU20 Table of contents 1 Introduction............4 Data flow setup.....4....................................31 5.............................................................51 6.............................................1.....................................................................1 DL power sharing............1 Power........................................... 38 6............................................2............2....... 46 6..........................................................................................................................................38 6............6 RRC state transitions.................. 12 2.........................3 Mobility.............2 HSPA Throughput and RTT (incl................................................................................44 6.......2.....26 3...............4 Packet data connection setup.............19 2..........................2 HSUPA throughput optimisation............ 38 6...................................................................................................................... 9 2..........................2 HSDPA UL Return Channel......................2...1 HSDPA throughput Optimisation.............................................................................. 14 2..............................71 6.................................................1 GPRS Attach............4 Retainability................................................3 HSUPA Accessibility..........................................................................................1.............................................................................................................................................................................................. MIMO and DC).............................................................................................................................93 6.2..

................1.................................105 7.........................................116 References.........................2011 Data Performance Optimisation Guide for Version 2........................................................................................ NPO/NSO Capability Management Date: 13..........4....2 RU10/RU20 7...........................................111 7...2 Channelisation code tree sharing.......2 Effect of HSPA on R99 performance.3 WBTS resource sharing..............................................1..............................................118 Copyright © Nokia Siemens Networks 2008 Company confidential Page 5 (119) ..................

......................... Serving cell change triggered by Event 1B on the serving HSDSCH cell (no NBAP signalling presented)......17 Figure 7..... are shown with black lines............................46 Figure 32.............................................. Comparison of DC-HSDPA............................................60 Figure 45 Example of throughput measurements included to M1027.....................................................57 Figure 43....................4................ Serving HS-DSCH cell change triggered by periodical EcNo measurements............24 Figure 14............................................................................................41 Figure 26.....37 Figure 24 – HSDPA Accessibility Failure Analysis.......54 Figure 38............................................... Inter-RNC serving HS-DSCH cell change with hard handover (no NBAP signalling presented).........................58 Figure 44................................29 Figure 17 HSDPA UE category distribution within last 100 weeks............................................................... PDP context setup procedure......52 Figure 37...... Example of HSUPA performance (RU10/RU20)...........................................................................39 Figure 25...33 Figure 20.... Example of HSUPA setup failure causes (RAS06/RU10)...........................48 Figure 34...........29 Figure 18....... 36 Figure 22 Example of PS NRT RAB Active fail change due to BTS (RU10/RU20)..........62 Copyright © Nokia Siemens Networks 2008 Company confidential Page 6 (119) .................................................................................................................... HSDPA+HSUPA................... 55 Figure 41........................................................................................................... Example HSDPA accessibility failure causes (RU10/RU20)........................................... 21 Figure 11........ HSDPA throughput measurement from BTS and drive test log..... F-DPCH is then allocated immediately after receiving the RRC connection setup complete message...................................................... Effect of PrxLoadMarginMaxDCH on HSDPA return channel accessibility.............................................................. Example HSDPA performance (RU10/RU20) PIs.................................................................................... HSDPA 64QAM result showing TBS and retransmission rate................. New transitions supported by RU10............................................ Capacity request and resource allocation signalling for packet data call........................... RU10 Introduce possibility to use URA_PCH state and fast call setup directly from URA_PCH/CELL_PCH to Cell_DCH.................... GPRS Attach procedure......................... RRC connection setup signalling..... HSDPA accessibility failure analysis with optimisation steps.........43 Figure 29....................................................................................................................................................................... RRC states and transitions............... Relation between UL CE usage and HS-DSCH setup failures (RAS06)...................................49 Figure 35............................................................ Transition from CELL_DCH to CELL_FACH with Radio Bearer Reconfiguration procedure.................................................. ( 5 x 100M file downloads).................................... 64QAM throughput measured in the lab and in the field...................................................... Vepro is measured in the lab and Ahvenatie case is measured in the field.....................................44 Figure 30......................... DL application throughput.............54 Figure 40. Transfer of the UE to CELL_DCH and reactivation of the data connection (cause UL data transmission).......45 Figure 31............ 47 Figure 33.......2 RU10/RU20 List of Figures Figure 1......................................55 Figure 42.................................................... 13 Figure 3.............................. 15 Figure 5.....................................41 Figure 27..................................... .................. Buffers with data Example (RNC_726b_number of HSDPA users per cell).... drive test Comparison of 16QAM and 64QAM ...................................................... NPO/NSO Capability Management Date: 13................................ 25 Figure 15............. 22 Figure 12.......... when FDPCHSetup (1) RRC Connection Setup message moves the UE into Cell_FACH....21 Figure 10............................ NRT PS RAB retainability analysis.. Example of HSDPA link adaption parameters................ Comparison of Normal NRT RAB Setup and Direct Resource allocation for HSPA........................54 Figure 39......... HSDPA accessibility with optimisation.................................................. General flow chart to analyse HSDPA throughput [8].............. 15 Figure 6.......... HSUPA UE category distribution within last 100 weeks........ HSUPA Accessibility failure analysis............................... 25 Figure 16 HSDPA and HSUPA UE utilisation within last 100 weeks....................................... Max Achieved HSDPA application level throughputs for different category UEs........................................................... Service Request procedure............................................................................ RSCP vs..................................... (5x100M file downloads)................................................................... 20 Figure 9.......................... Throughput per allocated HS-DSCH [8]...30 Figure 19 PS RAB setup failure rate statistics (RU10/RU20).......................................................................33 Figure 21.........................................19 Figure 8............................................... Fast call setup with direct transition from URA_PCH/CELL_PCH to CELL_DCH..........23 Figure 13..............................................................9 Figure 2.....Test is done in NSN test network under isolated cell without any other traffic to ensure that conditions remains unchanged between testing.....................43 Figure 28....................................................36 Figure 23 Example of PS setup failure rates (RU10/RU20)........................................ Transition from CELL_FACH to CELL_PCH (URA_PCH) with Radio Bearer Reconfiguration procedure.......60 Figure 46........ PS RAB Access failure rate statistics (RU10/RU20)........................50 Figure 36............................................................... 14 Figure 4..................... MIMO and 64QAM DL application level throughputs in the field (RSCP around -60 dBm in measurement location)........................................................................ Activation of TBO and 16 kbps return channel (RAS06)..........................................................2011 Data Performance Optimisation Guide for Version 2..................................... F-DCPCH signalling example........... Relation between CE usage and HSUPA setup and selection failures.....

..............86 Figure 77...........66 Figure 53. HS-SCCH usage for both DC HSDPA and 64 QAM UE............. Example of Active HSUPA TTI throughput (both 2ms and 10ms) and Average number of HSUPA 10ms & 2ms TTI users............................................................................................................................................................................ 62 Figure 48...............81 Figure 70........................................................................................................................... Above chart show modulation for main stream and RSCP along the drive route............................................80 Figure 68........................ example from NSN test network..............................................................................80 Figure 69...... Average HSDPA power vs.................................................................................. Example of HSUPA link adaption parameters........ New usage of 16QAM codes transmission in RU10 due the unevenly distributed codes between the users.................................................90 Figure 82................................................... 91 Figure 85.................................. 82 Figure 73............................................................................ HSUPA throughput PIS and drive test tool measurement...63 Figure 50........................... Number of codes and used modulation when RSCP drops – HSDPA 5 code feature. 70 Figure 58................... Uplink Load with different number of HSUPA UEs.. HSUPA Cell UL application level throughput with different number of HSUPA UEs and with different PrxTargetMaxBTS values (changed in case of 3 HSUPA UE).......................100 Figure 93....... Example of CQI report cycle.............................................91 Figure 84............................... The relation of Average reported CQI vs.......................................... DL power sharing between HSDPA and NRT PS traffic.................................83 Figure 74......................74 Figure 63........ Chart below show modulation for secondary stream and also DL application throughput along the route...................................................... RU20 RTT values in NSN test network................... Average CQI vs........................ HSUPA throughput... Function of Iub congestion Control.................... 89 Figure 81.................................. UE tx Power limitation vs.................... 87 Figure 79.................................. HSUPA performance with R99 load.................................. 98 Figure 91 Example of HSDPA release failure (RU10/RU20).................63 Figure 49 – Air Interface bitrate estimation using reported CQI............................................. HSUPA throughput (yellow) and Noise rise with different PrxMaxTargetBTS values................................................65 Figure 52.............................................. 90 Figure 83................... The relation of Average reported CQI and HSDPA User throughput in live network........... Example of DC HSDPA throughput in lab................................................... UL application level throughput of 1 HSUPA UE when there is different number of UEs in the cell..........102 Figure 96........... throughput in case there is simultaneously DC HSDPA and 64QAM users.... Uplink PrxTotal with different number of HSUPA UEs..............93 Figure 87............................................. MIMO “peak” performance................. HSPA retainability failure analysis.... Number of codes and used modulation when RSCP drops – HSDPA 10 Code feature. HSUPA congestion control decrease the HSUPA bit rate by decreasing the Serving grant with too high spreading code configuration.... Example of RNC_1879b HSDPA end used throughput formula vs........................................................................................... HSUPA throughput with HSUPA 2 Mbps feature.......85 Figure 76..............76 Figure 65................................................ 73 Figure 61..........65 Figure 51........................................................................................74 Figure 62....................................... HSUPA throughput KPI comparison...... HSUPA selections and throughput.......... average active cell throughput RNC_722b.82 Figure 72.68 Figure 56............................................... Uplink throughput with 1 x E1 for HSPA and different Parameter values............ 71 Figure 59 ..................................................................................... MIMO drive test under NSN test network............................................. RNC_2093a Average reserved SF16 codes for HSDPA and RNC_722b Active HSDPA throughput....... HSDPA cell throughput in live network (RU10)...............................96 Figure 89.................................... 103 Figure 97................... 72 Figure 60............................................. HSUPA congestion control and HW overload CC Frame loss counter...............................................................................92 Figure 86................................................2 RU10/RU20 Figure 47..................................75 Figure 64..........................104 Copyright © Nokia Siemens Networks 2008 Company confidential Page 7 (119) ...................................67 Figure 55......4........ HSDPA SCC performance compared to HSDPA retainability............................................ (100M file uploaded).............. Example of MIMO CQI counters distribution........................................... Example of SCC Performance (RU10/RU20).......... TBS with different CPICH Tx Powers from drive test logs......... Example of TTI counters for scheduled DC HSDPA user for Primary and Secondary cells..............................8 Mbps was activated.............................................................87 Figure 78.............. Function of Iub congestion control for throughput with different symbol rate.................................... 101 Figure 95..........................97 Figure 90.......... Example is from NSN test networks......66 Figure 54.................................................................................99 Figure 92 Example of E-DCH release reasons (RU10/RU20)..................................... NPO/NSO Capability Management Date: 13.........................................................94 Figure 88.............77 Figure 66....................................81 Figure 71............................88 Figure 80.........................83 Figure 75................ HSUPA throughput when 2ms TTI and 5.101 Figure 94....... 68 Figure 57........ DL power sharing analysis................ CQI comparison between RAS06 and RU10......... Example of differences between the Compensated CQI and Reported CQI........................................................ Effect of DCH power on HSDPA throughput.... BTS CE HSUPA Usage and HSUPA Maximum Mac-d Throughput (RAS06)................... HSDPA Utilisation...................................................................................................79 Figure 67........... PrxMaxTargetBTS =6 dB (default)............2011 Data Performance Optimisation Guide for Version 2............... HS-PDSCH code reservation............................................... BTS resource status counters.........

.................................................................................................................................. Code downgrade due to NRT with DPCHOverHSPDSCHThreshold=0.........................................2 RU10/RU20 Figure 98.... WBTS CE reservation of DCH bearers................ 112 Table 31 UL/DL CE reservation example for HSUPA when Flexi Rel2 SM is used with 10ms TTI....... PIs related to channelisation code sharing between HSPA and R99 traffic.............. MIMO parameter and secondary cell info can be added to Radio Bearer reconfiguration message....................... Code tree blocking.............................. UMTS QoS attributes.................................................................................................2011 Data Performance Optimisation Guide for Version 2.............................................................. 18 Table 8........... RNC parameters related to CELL_DCH state selection and release............................................. HSUPA traffic and throughput KPIs and counters........................... 17 Table 7..................113 Copyright © Nokia Siemens Networks 2008 Company confidential Page 8 (119) .. Less CE also needed for HSDPA users in Uplink (return channel) if 384 kbps is used. Setup fails with DPCHOverHSPDSCHThreshold=0..... Reports and PIs related NRT PS RAB retainability................................................................ DC HSDPA functionality and throughput with different carrier spacing... 10 Table 2...........52 Table 17...........4.111 Figure 105................................ PIs related power sharing between HSPA and R99 traffic.........................................................35 Table 13................................................................................................... Average UL and DL load as a function of HSDPA power..................................... (RU20) .................................27 Table 11................................ 26 Table 10............................................................................................. NPO/NSO Capability Management Date: 13....... Maximum user bit rates with different RAS features (RU20)............................... Example of HSDPA code allocation and spreading code occupancy [8].............................102 Table 29............................................. Currently there is no UE in the market which supports 5........................................................................................ HSUPA bitrates with different MaxTotalUplinkSymbolRate settings.............................................................................................. 95 Table 27..................10 Table 3.................. 109 Figure 103........................................75 Table 22...........................................39 Table 14............................................................................................... 11 Table 5.............................................................69 Table 21...................................... HSPA mobility counters and KPIs................................................................32 Table 12............................................116 Figure 108.......................................... Example of HSDPA & NRT code allocation duration with different UEs........................................................... 64QAM.............. Example of WBTS resource sharing with HSDPA (RAS06).. 98 Table 28.......................79 Table 25........................ Reports and PIs related NRT PS RAB accessibility...58 Table 18..................... Packet data connection related information elements in Activate PDP Context Request message .......... Effect of increased HSDPA traffic on CS RAB and HSPA bearer performance... with code downgrade due to congestion...... Maximum throughput that can be sent by shared HSDPA scheduler for BB efficiency in one TTI......................... Example of WBTS resource sharing with HSUPA (RAS06)...47 Table 16..................................................78 Table 24....................... 26 Table 9 QoS negotiation at PDP context setup...............................................76 Table 23........................................................ Reports and PIs related HSDPA accessibility............................. HSDPA Code downgrade due to AMR with HSPDSCHMarginSF128=0.................................42 Table 15..................... 15 Table 6. Feature related information elements in RRC Connection Setup Request message.......................................................... HSDPA traffic and throughput KPIs and counters........ 112 Table 32...84 Table 26...............107 Figure 101.................................... HSUPA congestion control parameters......................................................105 Table 30....................................... Packet data connection related information elements in RRC Connection Setup Request message.................................................................................... HSDPA performance comparison with different CPICH Tx Power values................................................................. Packet data connection related information elements in RRC Connection Setup Complete message......................................................... HSPA retainability counters and KPIs (Report: Service/Session Retainability Analysis RSRAN079)..104 Figure 99...... PIs related power sharing between HSPA and R99 traffic.....111 Figure 106.10 Table 4...................................................................... 64 Table 19................... In RU10........................................................................................................ QoS values for different traffic classes................................................................... Packet data connection related information elements in Radio Bearer Reconfiguration message ........ (This table does not include MIMO or DC HSDPA users)............................................................................................................. Packet data connection related information elements in RRC connection setup message...................... Mobile Power Offset Calculation (MPO) for different Cell power setting – PtxMaxHSDPA is set to same value as PtxCellMax...........................................................................106 Figure 100.............................2 MHz carrier spacing.........115 Figure 107.............................. Code tree occupancy............64 Table 20.............117 List of Tables Table 1....110 Figure 104....... Reports and PIs related HSUPA accessibility...........108 Figure 102............................................................. Example of RNC_722d Average Active HSDPA throughput.............. less CE needed with high bitrate (384 kbps) with Flexi Rel2 HW system module.........................................................

which will be updated with RU10 features later. The performance KPIs shown in the document is structured based on the latest RU20 reporting suite reports. there are several updated KPIs due the introducing of Streaming class. In RU10. Using reporting suite Content browser functionality. This guide can be used for MBB projects also. the user can also create own report based on counters. NPO/NSO Capability Management Date: 13. Then there is chapter for NRT PS RAB performance covering traditional service level KPIs related to NRT PS RAB. It is recommended to look at separate capacity management guide for detailed capacity analysis [8]. throughout. In the beginning there is chapter for PS signalling showing different packet call setup cases and mobility both in RNC level and at UE side. Then there is a chapter for PS RAB QoS introduction. NRT feature optimization is not described here but in Packet Scheduler Optimization document [7]. The last chapter is covering the HSPA and Rel99 interworking related mainly to WBTS resource sharing. Some performance related signalling charts are included here also basic QoS information. The structure of the document is following the data call flow. Copyright © Nokia Siemens Networks 2008 Company confidential Page 9 (119) .2 RU10/RU20 1 Introduction The purpose of this guideline is to give guidance for packet data performance optimisation tasks. The main focus is in HSPA (HSDPA and HSUPA) performance but also interworking with Rel99 NRT services is covered. mobility and retainability related to HSDPA and HSUPA. Reporting suite KPI creator tool make it possible to create own KPIs also. From KPI guarantee document [13] main KPI definitions with target values are explained. KPIs or existing reports so it is not necessary to follow reporting suite report content. There is also not info about different HSPA layers which is covered in HSPA layering guide [5].2011 Data Performance Optimisation Guide for Version 2. Basic HSPA functionality and parameters is not described here but in HSPA planning guide [2]. After that there is chapter for HSPA bearer performance optimization covering accessibility. also for HSPA.4.

Cause value ‘Registration’ is used to initiate GPRS Attach signalling and Measurement quantity about the quality of the pilot signal. Establishment cause depends also on UE implementation.2 RU10/RU20 2 PS Data connection signalling Packet data connection related signalling information is exchanged in different phases of the packet call. This section describes the main signalling information. RRC connection is required for any signalling from UE to the network and the setup information contains also information related to packet data connection. Node B UE RNC RRC: RRC Connection Request (RACH) NBAP: Radio Link Setup Request NBAP: Radio Link Setup Response ALCAP: Establish Request ALCAP: Establish Confirm FP: Downlink Sync FP: Uplink Sync RRC: RRC Connection Setup (FACH) L1 Synchronisation NBAP: Synchronisation Indication RRC: RRC Connection Setup Complete (DCH) Figure 1. NPO/NSO Capability Management Date: 13. The fist message from UE is the RRC Connection Setup Request which mainly indicates the RNC that the UE wants to establish signalling connection with the RAN. A) Rel-5 UE B) Rel-6 UE C) Rel-8 UE RRC Request RRC Request RRC Request File 1.1 RRC Setup RRC connection setup procedure is performed when UE moves from Idle mode to RRC Connected mode. This message contains these information elements that can be related to packet data connection establishment. Examples of RRC Connection Setup Request messages IE: Establishment cause which gives RNC an indication of the service that the UE is requesting. IE Access stratum release indicator indicates the RNC on the release of the specification the UE Copyright © Nokia Siemens Networks 2008 Company confidential Page 10 (119) . The RRC connection setup signalling is presented in Figure 1.2011 Data Performance Optimisation Guide for Version 2.4. RRC connection setup signalling. 2.

UE signal its supports for different features in RRC Connection request message.2011 Data Performance Optimisation Guide for Version 2. NSN support only Rel7 version of F-DPCH (Enhanced F-DPCH). Table 2. This message mainly contains the configuration of the signalling radio bearers that will be used for the signalling.2 RU10/RU20 supports. Release 6 UEs are capable of sending also the IE UE capability indication to indicate the HSDPA and/or HSUPA capability of the UE. It also contains information defining the next RRC state and a request for UE capability. Parameter SRBMapRRCSetupEC defines the establishment causes which prefer SRB mapping to the common channels in the RRC connection setup. Feature related information elements in RRC Connection Setup Request message Information element ValueDescription Release The IE shall be present and set to TRUE in Support for F-DCPCH OP TRUE this version of specification Rel-6 The IE shall be present and set to TRUE in Support for Enhanced F-DPCH OP TRUE this version of specification Rel-7 The absence of this IE indicates that the MAC-ehs support OP TRUE UE does not support MAC-ehs Rel-7 EPCCH Discontinuous The absence of this IE indicates that the Transmission support OP TRUE UE does not support DPCCH DTX Rel-7 The absence of this IE indicates that the Multi Cell Support OP TRUE UE does not support Multi-Cell Rel-8 The RRC Connection Setup is received from RNC as reply to the request message. Packet data connection related information elements in RRC Connection Setup Request message Information element Value Description Establishment cause Registration For GPRS Attach Originating High For PDP Context Setup Priority Signalling Measurement Quantity Ec/No = -24 + IE / 2 EcNo used for initial UL and DL power calculation Access stratum release indicator (Absence = R99). Packet data connection related information elements in RRC connection setup message Information element Value Description RRC state indicator Cell-DCH Signalling continues typically in DCH channel type in NSN Copyright © Nokia Siemens Networks 2008 Company confidential Page 11 (119) . Common Channel Setup allows also connections to be established in CELL_FACH rather than CELL_DCH.e. With F- DPCH feature (RU20) different options can be selected with parameter FDPCHSetup. Fractional DPCH is RU20 new feature which can map SRB on HSPA. Rel. Table 3. NPO/NSO Capability Management Date: 13. HSDSCH+EDCH Optionally. RU10 optional feature. Table 1. Release of the RRC 4 / Rel-5 / Rel-6 / functionality supported by UE Rel7 / Rel8 UE capability indication Absence = No HSPA. Mac-ehs allows the support of flexible RLC PDU sizes. i. IE available only from R6 UEs HS-DSCH. using RRC Idle to CELL_FACH transition. RRC connection establishment is normally performed directly to the Cell_DCH state or optionally on common channels (Cell_FACH).4.

24 (used when Rel-8 category extension2 DC_HSDPA is enabled) E-DCH physical layer 1-16 Rel-6 Category UE power class 1-4 Note 8: All UEs supporting HS_DSCH should signal a category between 1 and 15 for this IE even if the UE physical capability category is above 15. Note 9: This is IE corresponds to the HS_DSCH category supported by the UE when MAC-ehs is configured.2 RU10/RU20 RAN Capability update requirement True Set ‘true’ for FDD UARFCN uplink Channel number UL IE is provided if the frequency is changed (can be done due to DRRC procedure) UARFCN downlink Channel number DL IE is provided if the frequency is changed (can be done due to DRRC procedure) If RU20 feature fast L1 synchronisation feature is enabled.. This IE corresponds to the HS_DSCH category supported by UE when MAC-ehs (Flexible RLC) is not configured.4. Packet data connection related information elements in RRC Connection Setup Complete message Information element Value Description HS-DSCH physical layer 1-64 (16-64 are spares) Rel-5 and later Category Note 8 HS-DSCH physical layer OP 1-64 (used when DC-HSDPA is Rel-8 category extension disabled) Note 9 HS_DSCH physical layer OP 21. Table 4. Radio Bearer Reconfiguration.2011 Data Performance Optimisation Guide for Version 2. There is range of information related to UE data connection capability.g. e. Example of RRC Connection Setup Complete message from Rel-5. HSDPA an HSUPA physical layer category and UE power class. This IE can be included RRC Connection Setup. Radio Bearer Setup or Cell Update Confirm messages The RRC Connection Setup Complete message contains mainly the UE radio access capability information. the RNC sets the ‘Post Verification Period’ information element to TRUE when signaling to a release 6 or newer UE. Rel-6 and Rel-8 UEs. The UE signals also whether or not it benefits from network based battery power consumption optimization within the RRC Connection Setup Complete message (This is related to CPC feature) A) Rel-5 UE B) Rel-6 UE C) Rel-8 UE Message Message Message File 2. NPO/NSO Capability Management Date: 13. Copyright © Nokia Siemens Networks 2008 Company confidential Page 12 (119) .

…) for an immediate u-plane setup available. the NRT-RB shall be mapped to DCH-0/0 as in the “classic” NRT-RAB setup scenario and the RAB Assignment Request is acknowledged to the SGSN. following two configurations are possible:  HSDPA & HSUPA 10 ms TTI  HSDPA & HSUPA 2 ms TTI (Require that HSUPA 2ms TTI is enabled) If allocation of HS-DSCH in downlink for SRB is not possible. transport. BTS.e. Requirement for F-DPCH allocation is that SRB can be mapped to HSPA in both Uplink and Downlink. LAU.) are still fully executed in Cell_FACH if so parameterized.2011 Data Performance Optimisation Guide for Version 2. With F-DPCH. If the established service doesn’t allow the usage of F-DPCH the SRBs on HSPA need to be mapped to DCH/DCH and UE/BTS must be reconfigured accordingly. the MAC-d flow for NRT-RAB is allocated during the RB setup without DCH-0/0 allocation and waiting for UL/DL capacity request first. the Direct Resource Allocation for HSPA (DRA) is used as a default. packet scheduler is able to allocate only E. F-DPCH is then allocated a the same time as user plane resources When SRB are already on HSPA during the “initial” NRT-RAB setup phase.DCH/DCH for SRB with 2ms TTI. Rel99 DCH shall be allocated for SRBs if the establishment cause received from the UE is defined to use DCH for SRBs by FDPCHSetupEC parameter. there are 2 features which map SRB to HSPA/HSUPA. NPO/NSO Capability Management Date: 13. Channel type selection algorithm for SRBs proceeds together with downlink and uplink channel type selection algorithm for HSDPA and HSUPA when there is setup RB simultaneous with SRBs on HSPA. After this the (next) UL/DL capacity request triggers the next resource allocation attempt F-DPCH -related decision making and signaling concerns only those call-types for which Cell_DCH is the preferred RRC state. DMCU. This parameter have 3 different options  (0) RRC Connection Setup message configures F-DPCH and UE is moved into CELL_DCH with an HSDPA SRB  (1) RRC Connection Setup message moves the UE into Cell_FACH.4. RAU. and thus the F-DPCH=>DPCH reconfiguration will be executed in RB Setup/RL Reconfiguration procedures when setting up the AMR-RAB Copyright © Nokia Siemens Networks 2008 Company confidential Page 13 (119) . i. Otherwise it shall follow the allocation of F-DPCH controlled by the FDPCHSetup parameter. One such service would be AMR on DCH when CS voice over HSPA isn’t allowed (or any service requiring DCH). If there aren’t the required resources (radio. HSUPA 2ms TTI feature require that SRB is mapped to HSUPA in Uplink.2 SRB on HSPA In RU20. that is SRB on HSPA is not possible. All NAS signaling transactions (registrations.2 RU10/RU20 2. SMS etc. F-DPCH is then allocated immediately after receiving the RRC connection setup complete message  (2) RRC Connection setup message moves the UE into CELL_DCH and allocates a DCH connection for the standalone SRB.

After completing data transfer. NPO/NSO Capability Management Date: 13.2011 Data Performance Optimisation Guide for Version 2. DL F-DPCH info for each RL] NBAP: RRC: Radio bearer Reconfiguration Indication complete UE in CELL_DCH state NAS Signalling Connection. In Rel8 specification is modified so that RNC can keep the UE in RRC connected mode after receiving Signaling connection release indicator with new cause value ‘UE Requested PS Data Session End’. UE send signaling connection release indicator. F-DCPCH signalling example. DRA is used and all resources immediately NBAP: RL reconfiguration available NBAP: RL prepare Reconfiguration ready NBAP:RL Reconfiguration DRA RRC: Commit Radio Bearer Setup RRC: Radio Bearer Setup Complete RANAP: RAB Assignment Response Figure 2.4. when FDPCHSetup (1) RRC Connection Setup message moves the UE into Cell_FACH. by forcing them to RRC idle mode. Setup Complete from the UE RRC Connection Setup (FACH) UE in CELL_FACH State RRC: Initial UE message RRC Connection Setup RANAP: Initial DIRECT transfer [Enhanced F-DPCH Complete support=TRUE] UE support REL7 F-DPCH NBAP: RL Setup Request [F-DPCH information] NBAP: RL Setup Response [F-DPCH capacity information] AAL2 Setup F-DPCH RRC: Radio Bearer Reconfiguration setup [RRC State Indicator: CELL_DCH. which RNC has to obey and release the UE to RRC idle mode.3 Fast Dormancy Fast dormancy is functionality that UE vendors have introduced to save UE battery life. Copyright © Nokia Siemens Networks 2008 Company confidential Page 14 (119) . F-DPCH is then allocated immediately after receiving the RRC connection setup complete message 2. DL F-DPCH Info common RL forRestore all RL.2 RU10/RU20 UE BTS RNC RRC Connection Request CN (RACH) [Support for F-DPCH=TRUE] RNC establishes RRC connection on RACH/FACH and waits for RRC Conn. UE – CN Signalling Continued RANAP: Security mode RRC: Security mode command Command RRC: Security mode Complete RANAP: Security mode complete RANAP: RAB Assignment Request F-DPCH can be used with established service. This can increase network signaling load as “polls” and “keep alives” can cause UE to continuously setup and release RRC connection.

Parameter control is coming with RU30 (FD is originally planned to be RU30 feature). In RU20. The PS core may optionally request the UE to provide its identity. With the GPRS attach the UE establishes a GPRS mobility management context with SGSN.4. It is also used to start integrity protection for all signalling radio bearers. Figure 3.4.q. IMEI. If RNC receives signaling Connection Release Indication message without a cause value then the existing legacy functionality is applied and the UE is moved to RRC Idle mode. This could be the case with MT packet call. By default the value of T323 is 0s. but it is not supported by NSN.2 RU10/RU20 Fast Dormancy feature is included to RU20 MP1 without parameter control. the fast dormancy is activated by default (RU30 this can be handled with parameter) which results T323 being broadcasted within SIB1.2 Service Request The Service Request procedure is initiated prior to PDP context setup to form a secure connection between the SGSN and the UE for user data. NPO/NSO Capability Management Date: 13. 2. This is required if no other signalling with SGSN has preceded the PDP context setup.2011 Data Performance Optimisation Guide for Version 2. Fast dormancy functionality overrides inactivity timers and RNC instructs UE to make state change to CELL_PCH/URA_PCH. This is done using the Identity Request message. Copyright © Nokia Siemens Networks 2008 Company confidential Page 15 (119) . After receiving a Signaling Connection Release Indication message with cause value ‘UE Requested PS Data Session End’. e. 2. GPRS Attach procedure The purpose of the Security Mode procedure is to trigger the start or ciphering for the radio bearers of one core network domain and for all signalling bearers. it is in a position to send a message to the core network (PS core in this case). Cell_PCH need to be enabled.4 Packet data connection setup 2.4.1 GPRS Attach After the RRC connection setup procedure the UE has established a dedicated communication link with UTRAN. T323 within SIB1 allow a UE to detect that the network supports fast dormancy.

Access point name can be used to request a connection to operator specific services like WAP or to internet if this is allowed by the operator. Access Point Name Access points are defined in the GGSN configuration and UE request a connection to/via specific access point Requested service type and quality is defined in the Requested QoS information. The Activate PDP Context Request message includes information related to the requested service type and quality.4. Service Request procedure. PDP Context Setup procedure includes Radio Access Bearer (RAB) setup and Radio Bearer setup procedures. Requested IP address By default IP address is allocated automatically. This is done to DCH 0/0 if Directed Resource Allocation for HSPA is not enabled.4. NPO/NSO Capability Management Date: 13.3 PDP context setup PDP context forms the user data connection between the UE and internet or private network. An IP address is allocated to the UE in the procedure. Section 3 describes more in detail the QoS definition parameters and procedure.2 RU10/RU20 Figure 4. If DRA for HSPA is enabled. PDP context setup procedure. Packet data connection related information elements in Activate PDP Context Request message Information element Value Description Requested QoS See Section 3. The PDP context setup Copyright © Nokia Siemens Networks 2008 Company confidential Page 16 (119) .2011 Data Performance Optimisation Guide for Version 2. Figure 5. 2. Table 5. connection end point (Access point name) and requested IP address. then HSPA UEs can establish connection directly without allocating DCH 0/0.

which contains mainly the negotiated QoS and IP/PDP address allocated for the UE. Thus there is no need for resource reservations in this phase. The AC algorithm defines the maximum bit rate of the radio bearer. Message File 5. HSPA is allocated already during RAB establishment which replaces the allocation of a 0/0 kbps DCH. In NSN RAN. Example of Radio Bearer Setup message.4. Measurement control initiates the traffic volume measurements and defines the reporting thresholds for traffic volume measurements which are used for the UL capacity requests. NPO/NSO Capability Management Date: 13. When SRB are already on HSPA during the “initial” NRT-RAB setup phase (F-DPCH). Once the RAB has been established the RNC sends a measurement control messages to the UE in order to initiate the traffic volume measurements (UE internal) together with intra and inter frequency measurements. no transport and CE resources are reserved. the Direct Resource Allocation for HSPA (DRA) is used as a default. The reception of the RAB Assignment Request message triggers the admission control (AC) procedure in RNC and the following radio bearer setup procedure.e. i. TrCH). Example of Measurement Control message. Message File 4. but no bit rate allocations.2011 Data Performance Optimisation Guide for Version 2. Examples of Activate PDP Context Request and Activate PDP Context Accept messages. There is also no radio link setup with Node B at this phase. The Radio Bearer Setup message sent from RNC to UE contains the next state (in NSN RAN cell-DCH) some Radio Bearer information (RLC. Copyright © Nokia Siemens Networks 2008 Company confidential Page 17 (119) . Prior to RU20 the initial bit rate allocated in the RAB setup procedure of the NRT RAB is always zero (RAB 0/0). A) Activate PDP Context Request B) Activate PDP Context Accept Message Message File 3. target BLER and other bearer parameters. this message is sent over the Iu-PS interface and it contains the QoS of the RAB. With RU20 feature. The Activate PDP Context Request message triggers the SGSN to start the RAB setup procedure. Direct Resource allocation for HSPA (DRA for HSPA).2 RU10/RU20 procedure is completed with the Activate PDP Context Accept message. This is initiated when SGSN sends the RAB Assignment Request message to the RNC.

2 RU10/RU20 2. HS. E-DCH Selected UL the channel type Type Downlink transport channel DCH. Example of Measurement Report message. Selected DL the channel type Type DSCH. The data flow setup involves packet scheduling. HSDPA+HSUPA UE sends the Measurement Report message for Event 4A indicating that there is some data in the buffers. NPO/NSO Capability Management Date: 13. RACH. Table 6. Packet data connection related information elements in Radio Bearer Reconfiguration message Information element Value Description RRC state indicator cell-DCH. The selected radio bearer configuration is sent in the Radio Bearer Reconfiguration message to the UE and with the following Radio Link Reconfiguration Prepare message to the Node B. HSDPA. cell-FACH The initial bit rate allocation is typically done to DCH channel at packet call setup Uplink transport channel DCH. channel type selection and resource reservation for the selected connection type. Typically UE initiates the connection to the server and the capacity request comes from the UE. FACH. Figure 6.4 Data flow setup The data flow over the air interface is setup after a capacity request from either UE or internally RNC.4. where the RNC makes a selection between HSPA. DCH or common channel usage. Capacity request and resource allocation signalling for packet data call. Scheduling includes also allocation of bit rates for DCH bearers (allowed transport format set) based on RNC parameters and load conditions. DCH + HSDSCH Copyright © Nokia Siemens Networks 2008 Company confidential Page 18 (119) . which schedules the capacity request.4. Message File 6.2011 Data Performance Optimisation Guide for Version 2. This measurement report is handled as capacity request by the packet scheduler in the RNC. The scheduling operation starts with channel type selection procedure.

656 used for higher HSDPA data rates. Value is defined by BTS and signalled to RNC and to UE in this IE. Information element ValueDescription Release This allows UE the determine which TBS table to use. Maximum channelisation codes sf4.. 2sf2and2sf4 Maximum Channelisation code configuration for HSUPA. 38 Initial grant value for HSUPA. From RU20 onwards. Flexible RLC used for higher HSDPA rata rates. NPO/NSO Capability Management Date: 13. Table 7. UARFCN uplink Channel number UL IE is provided if the frequency is changed (not done in packet call setup) UARFCN downlink Channel number DL IE is provided if the frequency is changed (not done in packet call setup) A) Rel-5 UE B) Rel-6 UE C) Rel-7 MIMO UE C) Rel-8 DC-HSDPA UE Message Message Message Message File 7. 2sf4. 64QAM. MIMO parameter and secondary cell info can be added to Radio Bearer reconfiguration message.13 dB Measurement power offset Г indicating the current available HSDPA power relative to pilot. Absence of this IE means that the HS-SCCH Downlink 64QAM Configured OP TRUE does not use the 64QAM format Rel-7 Absence of this IE means that the HS-SCCH MIMO Parameters OP TRUE does not support MIMO Rel-7 DL optional parameters relevant to reception of secondary dl-SecondaryCellInfoFDD IE OP TRUE serving HS-DSCH cell Rel-8 The UE acknowledges the Radio Bearer Reconfiguration message with a Radio Bearer Reconfiguration Complete message. Example of Radio Bearer Reconfiguration message.4. Spreading factor (UL) 4-128 Minimum spreading factor of the UL DCH channel. Copyright © Nokia Siemens Networks 2008 Company confidential Page 19 (119) . Serving Grant value 0-37.2011 Data Performance Optimisation Guide for Version 2. UE utilises the value in CQI reporting. and which HS-SCCH format to use. 38 means no grant.2 RU10/RU20 MAC-d PDU size Fixed (336 or 656) or 336 used as default in NSN Flexible RAN. Measurement Power Offset -6.

NPO/NSO Capability Management Date: 13.5 Direct Resource Allocation for HSPA Direct resource allocation for HSPA allocates HSPA during RAB setup establishment which replaces the allocation of a 0/0 kbps. Figure 7. Direct resource allocation for HSPA can be applied only for CELL_DCH or CELL_FACH or for both. initial UL rate B) Rel-6 UE. If the UE is allocated a lower than maximum bit rate. Direct resource allocation is applicable to full HSPA connections using PS NRT Interactive or Background traffic classes. Example of Measurement Control message used to modify/release the Ul traffic volume measurement. TRS or DSP congestion. A) Rel-5 UE. then the RNC modifies the Event 4A reporting threshold according to the allocated bit rate (Flexible Upgrade feature provides possibility to define bit rate specific thresholds). depending on settings of parameter RABDRAEnabled. In case HSPA allocation is not possible due to BTS.2 RU10/RU20 RNC orders the UE with the Measurement Control message to stop the traffic volume measurements. no further attempt shall be made and DCH 0/0 shall be allocated and TVM started as per existing principles.4.4. 2. HSPA allocated Message Message File 8.2011 Data Performance Optimisation Guide for Version 2. Comparison of Normal NRT RAB Setup and Direct Resource allocation for HSPA Copyright © Nokia Siemens Networks 2008 Company confidential Page 20 (119) . as there is no use for the UEs to request higher bit rate. if the UE has been allocated the maximum available bit rate of HSPA channel type. then direct resource allocation for HSPA shall not be applied but RB is mapped to DCH 0/0 kbps and traffic volume measurements are started according to existing principles. If RABDRAEnabled is disabled.

Reconfiguration After RT call with inactive PS RABs Frequent cell updates Phys. New transitions supported by RU10.6 RRC state transitions The RNC can order the UE to change the RRC state during the packet call. NPO/NSO Capability Management Date: 13. Phys. Copyright © Nokia Siemens Networks 2008 Company confidential Page 21 (119) . Figure 9. This transition included the release of the BTS and Iub resources reserved for the connection. are shown with black lines. The Physical Layer Reconfiguration procedure is used to transfer the UE to/from the CELL_PCH and URA_PCH (RU10 feature) states. RAB and PDP context remain active towards Iu-interface. Reconfiguration CELL_DCH H Cell Update. The transition of the UE from CELL_DCH to CELL_FACH is performed with the Radio Bearer Reconfiguration message (see Figure 9 and File 9 A). In this procedure the physical layer and transport channel resources are released but RB (could be with SRB only).4. Reconfiguration After RT call with inactive UL/DL activation timer PS RABs & high mobility in CELL_FAC CELL_DCH Phys. RRC states and transitions.4. paging RB. This is typically performed due to packet connection inactivity or start of data transmission (see Figure 8). Reconfiguration IDLE Mode Inactivity Timer. Overload Figure 8. When the UE is transferred from CELL_DCH to CELL_FACH state.2 RU10/RU20 2. Transition from CELL_DCH to CELL_FACH with Radio Bearer Reconfiguration procedure. RACH load RB. the radio bearer is reconfigured to use common channels (RACH/FACH) with Radio Bearer Reconfiguration procedure. UL data.2011 Data Performance Optimisation Guide for Version 2. Reconfiguration RRC Setup / Release Traffic Volume. Paging URA_PCH CELL_PCH Fast call setup from URA_PCH Phys. UL data. The common channel resources are used in CELL_FACH for the data and signalling. Reconfiguration Fast call setup from UTRA RRC Connected Mode CELL_PCH URA Update. RU10 Introduce possibility to use URA_PCH state and fast call setup directly from URA_PCH/CELL_PCH to Cell_DCH. It is initiated by the RNC in basis of data transmission inactivity both in UL and DL or low measured throughput.

If the number of complete active set changes during the time period FastUEPeriod is equal or exceeds the threshold FastUEThreshold. Low moving UEs go to CELL_PCH state. In CELL_PCH state the UE is receiving the paging messages. following handling is used: When RRC entity has tried to switch the UE to URA_PCH state and the UE has responded by sending RRC: PHYSICAL CHANNEL CONFIGURATION FAILURE message (cause: unsupported configuration). There will be second trying to the CELL_PCH state and the ‘non-URA UE’ flag is set. When URA_PCH is enabled. Figure 10. UE location is known in cell level and handover process (HA3) can calculate the velocity of the UE by active set changes needed for the UE. The re-activation of the data connection can be initiated by the UE by using the Cell Update message (cause UL data transmission. Copyright © Nokia Siemens Networks 2008 Company confidential Page 22 (119) . NPO/NSO Capability Management Date: 13. Transition from CELL_FACH to CELL_PCH (URA_PCH) with Radio Bearer Reconfiguration procedure. Transition to URA_PCH is performed with the same signalling procedure. This is used for deciding Cell_PCH or URA_PCH state transitions after inactivity is detected. The RNC either keeps the UE in CELL_FACH or moves it to CELL_DCH with the Radio Bearer Reconfiguration procedure.2011 Data Performance Optimisation Guide for Version 2. If MaxCellReselections is set to 0. URA_PCH is not possible In case of the UE is not supporting URA_PCH state.2 RU10/RU20 The transition of the UE from CELL_FACH to CELL_PCH is performed with the Physical Channel Reconfiguration message (see Figure 10 and File 9 B) is initiated by the RNC in basis of data transmission inactivity both in UL and DL. the RNC (HA3) shall inform RRC signalling entity (MCC via CCM) about UE which is moving fast. to reduce the unnecessary signalling (cell updates) the UE is moved to the URA_PCH state if UE has been moving fast (in CELL_DCH state) or when too frequent execution of cell reselection procedure is observed (in CELL_FACH state). In CELL_DCH state. see Figure 11 and File 10A) or by the RNC by paging the UE.4. In CELL_FACH state. A) RB reconfiguration B) Physical channel reconfiguration from CELL_DCH to CELL_FACH from CELL_FACH to CELL_PCH Message Message File 9. Example of Radio Bearer reconfiguration and Physical channel reconfiguration messages used in the RRC state transitions. transition to URA_PCH is performed for high mobility UEs if amount of cell reselections/updates exceed predefined threshold set by parameter MaxCellReselections within time defined with parameter CellReselectionObservingTime.

2011 Data Performance Optimisation Guide for Version 2. Transfer of the UE to CELL_DCH and reactivation of the data connection (cause UL data transmission). NPO/NSO Capability Management Date: 13. In RAS06.4. or by DL data transmission when there is so much DL data send towards UE that on RNC point of view it shall be transferred to Cell DCH state (TrafVolThrDLLowGTP exceed). Copyright © Nokia Siemens Networks 2008 Company confidential Page 23 (119) . A) Cell update B) Radio bearer reconfiguration from CELL_FACH to CELL_DCH(HSDPA) Message Message File 10 _ Example of Measurement Control message used to modify/release the UL traffic volume measurement. the Service establishment is always executed in Cell_FACH state and if the UE is in Cell_PCH state when the establishment procedure is triggered. it is possible to enable direct transition from Cell/URA_PCH states to CELL_DCH state using Cell update –procedure.2 RU10/RU20 Figure 11. In RU10. Direct transfer can be triggered by UL data transmission when UE has set TVM-indicator as TRUE in Cell Update message indicating that the RLC buffer level exceed the lower TVM threshold and RACH/FACH cannot be used for transferring the buffered amount of data. the UE is first transferred to the Cell_FACH state.

2011 Data Performance Optimisation Guide for Version 2. The decision for the SCC is done based on these periodical measurements. Copyright © Nokia Siemens Networks 2008 Company confidential Page 24 (119) .4. The Serving HS-DSCH cell change can be triggered by multiple different triggers  UE based measurements: Periodical EcNo measurements. but this is available only when HSUPA is not active and serving cell change is not activated. RAS06 RNC supports also a HSDPA cell-reselection procedure. An example of signalling for Serving HS-DSCH cell change with SHO is presented in Figure 13.2 RU10/RU20 Figure 12. Also the periodical EcNo measurements are activated for all active set cells.7 Packet data connection mobility The procedure used for mobility depends on channel type in use. Event1B or Event1C to remove current Serving HS-DSCH cell  BTS SIRerror measurements on Serving HS-DSCH cell  Loss of UL synchronisation indication from BTS The Serving HS-DSCH cell change procedure can be forbidden in some cases like when inter- RNC SHO is not supported or the Serving HS-DSCH cell change is not enabled. 2. In CELL_DCH with HSPA channels the mobility is in most cases performed with the soft handover procedure combined with Serving HS-DSCH cell change. Fast call setup with direct transition from URA_PCH/CELL_PCH to CELL_DCH. as RAS06 RNC uses different values for single link and SHO connections. which is required as HSDPA does not support soft handovers. The start of SHO triggers also the Physical Channel Reconfiguration procedure (see File 11A) that is used to change the power offset of CQI. This example starts with Active set update to add the Cell2 to the active set. QCK and NACK bits in the HS-DPCCH.4. In these cases the change of cell is performed via CELL_FACH. NPO/NSO Capability Management Date: 13. Normal DCH channels utilise the soft handover procedure and in CELL_FACH/CELL_PCH states a cell-reselection procedure is used together with Cell Updates.

Serving HS-DSCH cell change triggered by periodical EcNo measurements.2011 Data Performance Optimisation Guide for Version 2. A) Physical channel B) Physical channel C) Measurement control D) Radio bearer reconfiguration to reconfiguration to message used to activate reconfiguration to SHO configuration single link the periodical EcNo change serving HS- configuration measurements DSCH cell Message Message Message Message File 11. NPO/NSO Capability Management Date: 13.2 RU10/RU20 Figure 13. then the Physical Channel Reconfiguration is used to change to CQI. The Radio Bearer Reconfiguration message is used to inform the UE about the change of the serving HS-DSCH cell (see File 11C). Example of messages used for Serving Cell Change procedure. In this case the Radio Bearer Reconfiguration message is used first to change the serving HS-DSCH cell and then the Active Set Update to remove the previous serving HS-DSCH cell from the active set. NACK and ACK offsets to the single link values. If there is only one cell in active set after the update. The SCC can be triggered also by an Event 1B to remove the current serving HS-DSCH cell from the active set (see Figure 14). Copyright © Nokia Siemens Networks 2008 Company confidential Page 25 (119) .4. This information is indicated in the IE: Serving HS-DSCH Indicator for RL.

or inter-BTS inter-RNC cells. The serving HS-DSCH cell change can be performed with hard handover when the SHO is not possible. Serving cell change triggered by Event 1B on the serving HSDSCH cell (no NBAP signalling presented). coverage. e. inter-BTS intra-RNC. For HS-DSCH ISHO.2 RU10/RU20 Figure 14. Copyright © Nokia Siemens Networks 2008 Company confidential Page 26 (119) . intermediate channel switching from HS-DSCH to DCH (and later back to HS-DSCH) is required before the compressed mode can be started. then LAU & RAU and finally immediate assignment to start data flow in EGPRS. Without this feature. in inter-RNC mobility if inter-RNC SHO is not supported. HSPA capability and immediate IMSI based handover reasons and is available for all supported HSPA services and service combinations. the associated DCH must enter compressed mode so that IFHO measurements can be performed. HSDPA IFHO is supported from RU10 onwards. Target cells for an HSPA inter-frequency handover can be intra-BTS.2011 Data Performance Optimisation Guide for Version 2. Inter-RNC serving HS-DSCH cell change with hard handover (no NBAP signalling presented). Figure 15.4. Figure 15 presents the signalling of an inter-RNC mobility with HSPA. then compressed mode with physical_channel_reconfiguration. HSDPA IFHO can be triggered due to quality. The inter-RNC cell change triggers also the UE Capability Enquiry and UTRAN Mobility Information procedures. first there will be radio_bearer_reconfiguration to DCH. Before an HSDPA IFHO can be started. cell change order (CCO) to GPRS. NPO/NSO Capability Management Date: 13.g. Existing HS-DSCH/E-DCH configuration are reconfigured to HS-DSCH/DCH configuration independent of the need for compressed mode to perform the measurements.

NPO/NSO Capability Management Date: 13. aspects such as the UE capabilities.2 RU10/RU20 3 PS RAB QoS parameters 3.4.1 Specification A set of UMTS bearer attributes have been defined to specify the UMTS service. This PDP Context Request contains the requested QoS.2011 Data Performance Optimisation Guide for Version 2. Copyright © Nokia Siemens Networks 2008 Company confidential Page 27 (119) . This initiates the QoS negotiation procedure. UMTS QoS attributes 3. They are listed on the table below. subscription profiles and network specific QoS profiles have to be taken under consideration. Table 8.2 Definition of PS RAB QoS in connection setup UE initiates the PS RAB setup by sending a PDP context request to the SGSN (1). modified or released. Table 9 QoS negotiation at PDP context setup. When a UMTS bearer is established.

GGSN can not allocate higher QoS than requested by SGSN.4. If a Service based QoS control feature is used in Nokia GGSN (Rel.  M1001C405_ACCESS_STRATUM_REL_IND_99 Copyright © Nokia Siemens Networks 2008 Company confidential Page 28 (119) . UE release indicator is possible to detect. the GGSN may restrict the negotiated QoS further. but based on that it is possible to detect only mandatory features. other methods like ICSU logging should be used Access Stratum Release indicator counters can be used monitor number of RRC connection establishment by UEs which access stratum release indicator release x. Nokia SGSN downgrades the QoS if necessary and sends the negotiated QoS to the GGSN.2 RU10/RU20 SGSN compares the requested QoS to the QoS profile in HLR (See ). With Counters is possible to detect UE Release Indicator and HSPA category.107. QoS values for different traffic classes. If more detail understanding is required. modulation and bit rates supported. QoS attributes are configurable. Features that are optional are not often detected with the counters. QoS profiles for different PDP contexts of one subscriber can all be different. The GGSN session management and admission control function selects the treatment class (TREC) based on used access point and service (service detection and switching). NPO/NSO Capability Management Date: 13. The QoS profile is defined for each subscriber per Access Point (AP) in the Home Location Register (HLR) and each PDP context has to negotiate its own QoS profile. The limitations for the traffic classes are according to the following . The selected TREC is mapped to the 3GPP QoS attributes in the GGSN for the QoS negotiation with the SGSN. Table 10. 5). (2) The negotiated QoS is limited by the appropriate values defined for each traffic class in the 3GPP specification TS23. (3) 4 UE Categories and Monitoring New features and bitrates may not be supported by the oldest UEs models.. UE HSPA category tells number of codes.2011 Data Performance Optimisation Guide for Version 2. In Nokia R99 HLR.

2 Mbps  UE_SUPP_HSDSCH_CLASS_9_10 (M1001C550) 15 codes. 1. (Also UE support for GSM. 17-21 Mbps  UE_SUPP_HSDSCH_CLASS_15_16 (M1001C673) MIMO.  RNC_655c_HSDPA UE utilisation  RNC_1049c_HSUPA UE utilisation Additionally number of MIMO and DC HSDPA capable EUs can be monitored. Copyright © Nokia Siemens Networks 2008 Company confidential Page 29 (119) . 15 code.8-14. NPO/NSO Capability Management Date: 13.2 RU10/RU20  M1001C404_ACCESS_STRATUM_REL_IND_4  M1001C552_ACCESS_STRATUM_REL_IND_5  M1001C616_ACCESS_STRATUM_REL_IND_6  M1001C675_ACCESS_STRATUM_REL_IND_7  M1001C699_ACCESS_STRATUM_REL_IND_8 Additionally UE support for features like Continuous Packet connectivity or CS Voice over HSPA can be detected. Figure 16 below show HSDPA and HSUPA UE utilisation within last 100 weeks. There are counters to check the UE type distribution based HSDPA category  UE_SUPP_HSDSCH_CLASS_1_6 (M1001C548) 5 codes. the HSDPA utilisation is around 86% and HSUPA UE utilisation around 30% in this example network. AGPS)  M1001C677_UE_SUPP_CPC  M1001C671_UE_SUPP_CS_VOICE_OVER_HSPA_ User throughput depends from the UE type which is used in the network. GANHO.  RNC_2110a count Amount of MIMO capable UEs and  RNC_2111a counts amount of DC HSDPA capable UEs. 28 Mbps  UE_SUPP_HSDSCH_CLASS_17_18 (M1001C674) MIMO. In RU20 maximum 64QAM user throughput can be achieved with Cat14 and Cat18 HSDPA UEs. IPHC. 15 code. In RU20 timeframe. 5 code. MIMO maximum throughput can be achieved with Cat 18 UE. 42 Mbps HSPA UE utilisation KPIs can be used to monitor how big percentage of HSPA capable UE’s got RRC-Connection from all RRC-Connections.6 Mbps  UE_SUPP_HSDSCH_CLASS_7_8 (M1001C549) 10 codes.4. 15 code. 28 Mbps  UE_SUPP_HSDSCH_CLASS_23_24 (M1001C698) DC HSDPA with 64QAM.8Mbps  UE_SUPP_HSDSCH_CLASS_13_14 (M1001C672) 64QAM. and 10. 28 Mbps  UE_SUPP_HSDSCH_CLASS_19_20 (M1001C696) MIMO with 64QAM  UE_SUPP_HSDSCH_CLASS_21_22 (M1001C697) DC HSDPA with 16QAM.4Mbps  UE_SUPP_HSDSCH_CLASS_11_12 (M1001C551) QPSK only. 3. Category 24 is required to support maximum DC HSDPA throughput with 64QAM in RU20 on top. 7. Modified version of these KPIs can be used monitor MIMO and DC_HSDPA capable UE utilisation similar way as for HSPA UE utilisation.2011 Data Performance Optimisation Guide for Version 2.

NPO/NSO Capability Management Date: 13.2 RU10/RU20 Figure 16 HSDPA and HSUPA UE utilisation within last 100 weeks. Figure 17 HSDPA UE category distribution within last 100 weeks.2011 Data Performance Optimisation Guide for Version 2.4. see below one example. There are similar counters for HSUPA UE categories as well. Currently most of the HSUPA UEs are category 5 UEs  UE_SUPP_EDCH_CATEGORY_1 (M1001C610)  UE_SUPP_EDCH_CATEGORY_2 (M1001C611)  UE_SUPP_EDCH_CATEGORY_3 (M1001C612)  UE_SUPP_EDCH_CATEGORY_4 (M1001C613)  UE_SUPP_EDCH_CATEGORY_5 (M1001C614) 2 Mbps and 10ms TTI only Copyright © Nokia Siemens Networks 2008 Company confidential Page 30 (119) .6 Mbps throughput. Majority of the HSDPA UEs are still category 1-6 five code UEs having max 3.

Less than 30% of the UEs are category 6 UEs supporting higher uplink bitrates with 2ms TTI.2 RU10/RU20  UE_SUPP_EDCH_CATEGORY_6 (M1001C615) 5. Figure 18.8 Mbps. Copyright © Nokia Siemens Networks 2008 Company confidential Page 31 (119) . NPO/NSO Capability Management Date: 13. the majority of the UEs are Category 5 UEs by supporting 2Mbps throughput and 10 ms TTI. both 2ms and 10ms TTI  UE_SUPP_EDCH_CATEGORY_7 (M1001C676) 16QAM.2011 Data Performance Optimisation Guide for Version 2.4. HSUPA UE category distribution within last 100 weeks. both 2ms and 10ms TTI For HSUPA.

KPIs are taken with RAS06 RS formulas to see the impact of performance change.2011 Data Performance Optimisation Guide for Version 2. then DCH 0/0 is allocated instead. service summary) RAB Setup and Access Complete Ratio for NRT Service from User perspective can be used to monitor RAB accessibility from user point of view.1 Accessibility In normal network conditions there should not be NRT PS RAB access failures as there is no resource reservation done in the RAB setup and access phases for NRT RAB. The KPI example figures show the impact of RU10 upgrade (done 9. counters & PIs:  RNC_376a=M1001C105 RAB_STP_FAIL_PS_BACKG_AC. RNC_384a=M1001C110 RAB_STP_FAIL_PS_INTER_AC  RNC_1073a (RAB Setup FR for PS I&B calls due to AC)  There is no check of air interface resources in NRT PS RAB setup  RNC decides to reject the PS RAB request due to RNC internal failure.2009). High level RAB KPI .  M1001C257 RAB_STP_FAIL_PS_NOT_SUPP_PAR  The RAB setup attempt counters are not updated in this case  RAB assignment fails due to AC.7. NPO/NSO Capability Management Date: 13. So If NRT RAB drops it is possible that end user does not see it due to RAB re-establishment procedure. Low performing cells can be then ranked to more detail analysis RAB_STP_ACC_COMP_PS_BACKG  RAB_STP_ACC_COMP_PS_INTER RNC_156a  100 % RAB_STP_AT T_PS_BACKG  RAB_STP_AT T_PS_INTER The failure reasons for NRT PS RAB Setup and Access are limited to following. counters and PIs:  RNC_387a = M1001C112 RAB_STP_FAIL_PS_BACKG_RNC  RNC_379a = M1001C107 RAB_STP_FAIL_PS_INTER_RNC  RNC_1076a (RAB Setup FR for PS I&B calls due to RNC)  The number of RAB setup failures caused by ongoing relocation or hard handover for PS data interactive. The NRT PS RAB setup does not require any resource reservation as no radio link is setup at this phase. 5. M1001C113_RAB_STP_FAIL_PS_BACKG_ANCH  PIs: RNC_1074a (RAB Setup FR for PS I&B calls due to ANCH)  No RRC: Radio Bearer Setup Complete message received from the UE.  RNC_404a=M1001C134 RAB_ACC_FAIL_PS_BACKG_MS Copyright © Nokia Siemens Networks 2008 Company confidential Page 32 (119) .2 RU10/RU20 5 NRT PS RAB performance It is worth of mentioning here that RAN KPI does not always mean end user perception. as there is no BTS or transport resource reservation done in RAB setup phase for NRT. for example. The RAB setup procedure is started with RAB Assignment request message from CN (see Figure 5).RNC_157a (RSRAN 003. Counters and PIs  RNC_403a=M1001C132 RAB_ACC_FAIL_PS_INTER_MS. Counters  M1001C258 RAB_STP_FAIL_PS_UE_CAPA.4. Counters and PIs  M1001C108_RAB_STP_FAIL_PS_INTER_ANCH. This is due to new RU10 KPIs could not be seen from RAS06 SW level with RU10 RS.  The PS RAB setup attempt is not started due to requested parameters not supported by the UE or RNC. If direct resource allocation for HSPA fails.

RNC failures can be studied in more detail with RNC internal ICSU logging.2011 Data Performance Optimisation Guide for Version 2.2 RU10/RU20  RNC_1078a (RAB Setup Access FR for PS I&B calls due to UE) Table 11 lists the reports and PIs related to NRT PS RAB performance monitoring and failure analysis.4. The failures were increasing after DRA enabling.02 % and that the RNC failures are most typical in this example. In general the failure rate is very low. typically below 0. Copyright © Nokia Siemens Networks 2008 Company confidential Page 33 (119) . Figure 20 shows example of RAB access failure statistics. Table 11. Reports and PIs related NRT PS RAB accessibility PI ref PI name / Abbreviation PI unit Report: System Program RNSRAN000 RNC_616a RAB Attempts PS Interactive and Background # RAB Setup and Access Complete Ratio for NRT Service from User RNC_157a perspective % Report: Service/Session Access Detailed info RSRAN73 RNC_569a RAB PS Setup Attempts # RNC_1925a PS RAB Setup Completed # RNC_1026a PS RAB Setup FR due to AC % RNC_2007a PS RAB Setup FR due to ANCH % RNC_1028a PS RAB Setup FR due to RNC % RNC_1031a PS RAB Setup FR due to FROZBS % RNC_1033a PS RAB Setup Access FR due to UE % RNC_1035a PS RAB Setup Access FR due to RNC % Figure 19 presents an example of PS RAB accessibility performance before and after RU20 upgrade. AC failures disappeared already in RU10. The RAB setup failures due to transmission (RNC_1075a) are not related to RAB setup phase but to actual radio bearer resource allocation or modification. this PI or related counters M1001C106 and M1001C111 are not supported in RU10 onwards. This is natural because resource reservation is not done during PS RAB setup. NPO/NSO Capability Management Date: 13.

HSPA or CCCH). Copyright © Nokia Siemens Networks 2008 Company confidential Page 34 (119) .2011 Data Performance Optimisation Guide for Version 2.0 EP1 RU20 first cluster MP2 PP1.2 Retainability The NRT PS RAB consists of Iu bearer and radio bearer.12 Figure 19 PS RAB setup failure rate statistics (RU10/RU20) RU10 RU20 MP1 RU20EP1 WN6. The radio bearer can utilise multiple different channel types (DCH.2 RU10/RU20 RU10 RU20 MP1 RU20EP1 WN6.12 Failures decrease on 01.0 EP1 RU20 MP2 first cluster PP1. NPO/NSO Capability Management Date: 13. The retainability of a NRT PS RAB will depend on the Iu bearer and radio bearer performance.4. PS RAB Access failure rate statistics (RU10/RU20) 5.10 after enabling of DRA Figure 20.

the RNC releases RAB resources.RAB active failures in PCH state (I & B) RNC_736a  100  100 RAB active completions (I & B)  RAB active releases (I & B)  RAB active failures RAB active fails when an interface-related (Iu. RAB active failures (I & B) . RAB active is completed also when the RNC receives a RANAP: IU RELEASE COMMAND message from the CN. M1001C398_RAB_ACT_FAIL_PS_BACKG_UE  because the UE is not responding to an RRC message or the UE is responding with such failure message that the connection must be released  Caused by integrity check  PI: RNC_1089a (RAB Active FR for PS I&B due to I_CHK)  Counters: M1001C189_RAB_ACT_FAIL_PS_INTER_I_CHK. After that. NPO/NSO Capability Management Date: 13. that is. M1001C191_ RAB_ACT_FAIL_PS_BACKG_IU  Caused by drift RNC procedures  PI: RNC_1088a (RAB Active FR for PS I&B due to IUR)  Counters: M1001C190_ RAB_ACT_FAIL_PS_INTER_IUR. NRT Services. Iub. that is. M1001C194_ RAB_ACT_FAIL_PS_BACKG_IUR  Caused by UE  PI: RNC_1091a (RAB Active FR for PS I&B due to UE)  Counters: M1001C397_RAB_ACT_FAIL_PS_INTER_UE.2011 Data Performance Optimisation Guide for Version 2. RAB active phase ends before the release. M1001C193_ RAB_ACT_FAIL_PS_BACKG_BTS  release is requested due to BTS failure  Abnormal reason related to Iu-interface  PI: RNC_1085a (RAB Active FR for PS I&B due to IU)  Counters: M1001C185_RAB_ACT_FAIL_PS_INTER_IU.  Some reason not covered by the other failure counters  PI: RNC_1090a (RAB Active FR for PS I&B due to RNC) Copyright © Nokia Siemens Networks 2008 Company confidential Page 35 (119) . M1001C195_RAB_ACT_FAIL_PS_BACKG_I_CHK. from User Perspective) can be used to monitor RAB retainability. and then releases RAB resources. and the failure causes the release of the RAB connection.2 RU10/RU20 RAB active starts when the RNC sends a RANAP: RAB ASSIGNMENT RESPONSE message to the CN (see Figure 5). Low performing cells can be then ranked to more detail analysis.RNC_736a (RAB Success Ratio. M1001C192_ RAB_ACT_FAIL_PS_BACKG_RADIO  release is requested due to radio interface synchronisation failure  Caused by BTS (for example. radio link setup or reconfiguration problem)  PI: RNC_1087a (RAB Active FR for PS I&B due to BTS)  Counters: M1001C187_ RAB_ACT_FAIL_PS_INTER_BTS. Iur. RAB active phase ends after the release.4.  This counter is never updated. and then acknowledges that by sending a RANAP: RAB ASSIGNMENT RESPONSE message to the CN. High level RAB KPI . RAB active is completed when the RNC receives a RANAP: RAB ASSIGNMENT REQUEST message from the CN with the IE: RAB release. or Uu) or RNC internal failure occurs.  Caused by radio interface synchronisation  PI: RNC_1086a (RAB Active FR for PS I&B due to RADIO)  Counters: M1001C186_ RAB_ACT_FAIL_PS_INTER_RADIO.

NPO/NSO Capability Management Date: 13. M1001C196_ RAB_ACT_FAIL_PS_BACKG_RNC It should be noted that RAB retainability is not same than RB retainability.4. Table 12 lists the relevant reports and PIs for NRT PS RAB retainability monitoring and troubleshooting. RNC_736b: in RU10 this failure cause was included in failure due to RNC -> KPI comparable Copyright © Nokia Siemens Networks 2008 Company confidential Page 36 (119) .2011 Data Performance Optimisation Guide for Version 2. These new counters are included to RNC_615c. because it is possible to re-establish the RB in side RAN (by setting T315 parameter greater than 0) when having existing RAB connection to the core network. NRT Services. Table 12. from User Perspective % Report: Service/Session Detailed Retain Info RSRAN79 RNC_1978a RAB Setup Access Completions for PS # RNC_1964a RAB Active FR for PS due to IU % RNC_1959b RAB Active FR for PS due to RADIO % RNC_1960b RAB Active FR for PS due to BTS % RNC_1961b RAB Active FR for PS due to IUR % RNC_1962b RAB Active FR for PS due to RNC % RNC_1963b RAB Active FR for PS due to UE % RNC_2005a RAB Active FR for PS due to trans RU20 introduce new RAB Active failure cause due to transport (Drop) included. NRT Services.2 RU10/RU20  Counters: M1001C190_ RAB_ACT_FAIL_PS_INTER_RNC. Reports and PIs related NRT PS RAB retainability PI ref PI name / Abbreviation PI unit Report: System Program RNSRAN000 RNC_616a RAB Attempts PS Interactive and Background # RNC_615c RAB Success Ratio. from Network Perspective % RNC_736b RAB Success Ratio. In RU10 it is possible to have RAB re- establishment also for Voice and PS RT (by setting parameter T314 greater than 0).

can be caused NRT PS RAB by failed SCC due to HSDPA ret channel Yes active fail due BTS NRT PS RAB No active fail due to Yes Iu Check core network parameter settings Rejections NRT No PS RAB active fail due to Iur Yes Inter RNC mobility? NRT PS No RAB RNC Internal Problem active fail due to RNC Yes NRT PS No RAB ( active fail due to UE Yes Terminal Problem Figure 21.10 (TN148) and correction of a problem with iPhone in PP1.08. RU10 RU20 MP1 RU20EP1 WN6. it can be seen that RAB Active failure improved since PRFILE change on 27. NRT PS RAB retainability analysis Below is one example of NRT PS RAB retainability.0 EP1 RU20 MP2 first cluster PP1.2 RU10/RU20 Low NRT PS RAB No No Action retainability (cell) Needed Yes NRT PS RAB active fail due to radio Yes Check NRT PS radio bearer failures due to radio No Check BTS HW resources.2011 Data Performance Optimisation Guide for Version 2.93 .93 Figure 22 Example of PS NRT RAB Active fail change due to BTS (RU10/RU20) Copyright © Nokia Siemens Networks 2008 Company confidential Page 37 (119) . NPO/NSO Capability Management Date: 13.4.12 TN148 iPhone correction in PP1.

NPO/NSO Capability Management Date: 13.4.2011
Data Performance Optimisation Guide for Version 2.2
RU10/RU20

Below is also example of PS setup failures causes based on packet call counters. Different
failure cases are explained in the HSDPA accessibility chapter in Table 13.

RU10 RU20 MP1 RU20EP1 WN6.0 EP1 RU20 MP2
first cluster
PP1.12

Increased failures
due to BTS on a few
sites during high
traffic season

Figure 23 Example of PS setup failure rates (RU10/RU20)

Copyright © Nokia Siemens Networks 2008 Company confidential Page 38 (119)

NPO/NSO Capability Management Date: 13.4.2011
Data Performance Optimisation Guide for Version 2.2
RU10/RU20

6 HSPA bearer performance
6.1 Accessibility
HSUPA cannot be established without HSDPA; if HSUPA is supported the HSDPA UL return
channel is HSUPA instead of R99. In both cases, the High level Setup procedure is the same:
RNC starts by allocation a 0/0 kbps connection and selection between DCH and E-DCH is then
completed when RNC receives the uplink or downlink capacity request, or if Direct resource
allocation for HSPA feature (RU20) is used, then HSPA is already allocated during RAB
establishment which replace the allocation of 0/0 kbps.

6.1.1 HSDPA accessibility
High level HSDPA KPI - RNC_605a (RSRAN003, Service Summary) can be used to monitor
HSDPA accessibility from user point of view. Low performing cells can be then ranked to more
detail analysis.

RNC_605a 
ALLO _ HS _ DSCH _ FLOW _ INT  ALLO _ HS _ DSCH _ FLOW _ BGR
 ALLO _ HS _ DSCH _ FLOW _ INT  ALLO _ HS _ DSCH _ FLOW _ BGR  DCH _ SEL _ MAX _ HSDPA _USERS _ INT  100%

 DCH _ SEL _ MAX _ HSDPA _ USERS _ BGR  REJ _ HS _ DSCH _ RET _ INT  REJ _ HS _ DSCH _ RET _ BGR
 SETUP _ FAIL _ RNC _ HS _ DSCH _ INT  SETUP _ FAIL _ RNC _ HS _ DSCH _ BGR  SETUP _ FAIL _ UE _ HS _ DSCH _ INT
Equation 1. RNC_605a HSDPA accessibility for NRT traffic from user point of view
 SETUP _ FAIL _ UE _ HS _ DSCH _ BGR  SETUP _ FAIL _ BTS _ HS _ DSCH _ INT  SETUP _ FAIL _ BTS _ HS _ DSCH _ BGR 
The HS_DSCH setup and Selection can fail due the many reasons. When monitoring HSDPA
 SETUPfailure
setup HS _ DSCH _ INT itSETUP
_ FAIL _ IUB _counters is _important
FAIL _ IUB _ HS _ DSCH
to _understand
BGR root cause of the failure. Typically setup
failures indicate resource shortage, and as can be seen from flow chart below (Figure 24), these
problems are often related to HSDPA UL DCH return channel rather than HSDPA Mac-d flow
itself. But if there are not enough resources to set up HSDPA UL DCH return channel, the
HSDPA Mac-d flow setup will fail also.

Copyright © Nokia Siemens Networks 2008 Company confidential Page 39 (119)

NPO/NSO Capability Management Date: 13.4.2011
Data Performance Optimisation Guide for Version 2.2
RU10/RU20

Low HSDPA No No Action
accessibility (cell) Needed

Yes

Check Number of simultaneous HSDPA
Too many HSDPA Yes users in BTS or cell level depending on
users reached
the scheduler type
No
Check BH Channel Element resource
HSDPA Setup Fail Yes
Usage
due BTS
(Lack of CE for UL return Channel)
No
Rejection of UL Yes Check BH UL Power Congestion
Return Channel (Lack of Radio resources for UL return
Rejections Ch.)
No
HSDPA Setup Fail Yes Check BH AAL2 Iub congestion
Iub (Both UL &
(Lack of Iub resources for UL return Ch.)
DL)
No Check RB reconfiguration failure rate
Yes (Terminal Problem)
HSDPA Setup Fail
UE
No
(
Check RNC Unit load (DMPG), max
HSDPA Setup Fail Yes
number of users/RNC, DSP failures and
RNC Internal
faulty alarms

Figure 24 – HSDPA Accessibility Failure Analysis

Besides of reasons listed in Figure 24, the HSDPA accessibility problems can be also related to
Iu-PS or IP-BB capacity problems. HSDPA channel type selection can be also fail due the
downlink power if static power allocation is used instead of Dynamic resource/power allocation.
There should be also enough resources to set up HS_SCCH for DL.

Table 13 lists the relevant reports and PIs for HSDPA RB accessibility monitoring and
troubleshooting. Note: HSDPA access failure rate PIs are currently defined as % of all failures
calculating failure distribution, instead of the failure rate over the HS-DSCH selection. In RU10,
these PIs are changed to calculate failure rate over all HS-DSCH selections.

Table 13. Reports and PIs related HSDPA accessibility

PI ref PI name / Abbreviation PI unit
Report: System Program RNSRAN000
RNC_930b Packet Session Attempts (for R99 & HSPA) #
RNC_916b Packet Session Setup Success Ratio for NRT (for R99 & HSPA) %
RNC_614c HS-DSCH selections (for HSDPA only) #
RNC_605b HSDPA Resource Accessibility for NRT Traffic (user) (for HSDPA only) %
RNC_926b HSDPA attempts #
RNC_914c HSDPA Setup Success Ratio from user perspective (HSDPA & HSUPA) %
Report: Service/Session Accessibility Analysis RSRAN073 (M1022, M1002)
RNC_930b Packet Session Attempts (for R99 + HSPA) #
RNC_967b PS Call Setup FR due to AC (for R99 +HSPA) %

Copyright © Nokia Siemens Networks 2008 Company confidential Page 40 (119)

the performance could be lower as well due to statistical calculation. gives lower value than RNC_605a due to the HSDPA/HSUPA attempt counters are incremented for cells which do not have HSDPA/HSUPA enabled if the UE is HSDPA/HSUPA capable. these counters are updated only ones resulting only counter update. RNC_914a also does not include statistics from serving cell change mobility. attempt for high bitrate fails and immediate retry to lower allowed UL bitrate is done. which are typically related to HSDPA UL R99 return channel. This impact BTS and Iub Setup failure counters.2 RU10/RU20 RNC_955b PS Call Setup FR due to BTS (for R99 +HSPA) % RNC_1080b PS Setup FR for I&B due to lack of DMCU (for R99 +HSPA) % RNC_1081b PS Setup FR for I&B due to Transport (for R99 + HSPA) % RNC_1082b PS Setup FR for I&B due to UE (for R99 +HSPA) % RNC_1083b PS Setup FR for I&B due to Others (for R99 +HSPA) % RNC_614c HS-DSCH selections (for HSDPA only) # RNC_663d HSDPA Access FR due to RNC (for HSDPA only) % RNC_673d HSDPA Access FR due to BTS (for HSDPA only) % RNC_665d HSDPA Access failures due to Iub (for HSDPA only) % RNC_667d HSDPA Access FR due to UE (for HSDPA only) % RNC_661d HSDPA Access FR due to UL DCH (for HSDPA only) % RNC_671c HSDPA Access FR due to AMR+HSPA (for HSDPA only) % RNC_660d DCH Selected due to too many HSDPA users (for HSDPA only) % RNC_914a (RNC_914c in RU10) HSDPA setup success rate. NPO/NSO Capability Management Date: 13. No impact to packet call counters (M1022) Figure 25 presents an example of HSDPA accessibility PIs from live network. Also HSUPA is included into RNC_914a/b as well. Otherwise performance is more or less same than in RU10 level.4. Thus. Now in RU20. When aggregate across cells. so it is more HSPA accessibility KPI. When the UE is attempted to transfer from FACH directly to high UL bitrate.2011 Data Performance Optimisation Guide for Version 2. this KPI should aggregate across cells which have HSDPA enabled only (RNC level not recommended unless all cells HSDPA enabled) In RU20 there is less HSDPA setup failures due the changes in counter implementation. in RU10 the counter is updated for each bit rate until successful allocation for that secuency happens or entire procedure failed. HSDPA mac-hs efficiency increased on Flexi rel-2 sites due to new functionality ‘HSDPA dynamic BLER’. This impact only FACH-> HSxPA procedure. Copyright © Nokia Siemens Networks 2008 Company confidential Page 41 (119) . In DCH 0/0 -> HSxPA transition counters work similarly in RU10 and RU20.

64 users is also possible with shared scheduler for BB efficiency in case Flexi BTS Rel 2 HW (FSMC/D) is used. The network capability can be increased by introducing high Share Scheduler for BB efficiency (max 48 users/scheduler) or 48 users/cell feature. It should also be considering if traffic balancing between neighbouring sites is possible. There are two main solutions available.4. HSDPA mac-hs efficiency increased on Flexi rel2 sites Figure 25.12 Configuration error on 4 sites of DC HSDPA cluster. In RU10. Figure 26 presents an example of HSDPA access failure cause. In RU10 it is possible to limit either maximum number of Copyright © Nokia Siemens Networks 2008 Company confidential Page 42 (119) . Example HSDPA performance (RU10/RU20) PIs.0 EP1 RU20 MP2 first cluster PP1. or even second scheduler. HSDPA setup can fail due the number of simultaneous users reached.2 RU10/RU20 RU10 RU20 MP1 RU20EP1 WN6.2011 Data Performance Optimisation Guide for Version 2. which indicates HSDPA return channel allocation failure due to BTS HW resource shortage. Example HSDPA accessibility failure causes (RU10/RU20). the maximum number of HSDPA users increase to 64 with full baseband scheduler (ex-48 users per cell scheduler). In this example Iub and BTS failures are most dominating.12 Figure 26.0 EP1 RU20 MP2 first cluster PP1. increase the capability of the network or decreased the number of UEs in DCH. NPO/NSO Capability Management Date: 13. It can be seen that there are less access failures with RU20. RU10 RU20 MP1 RU20EP1 WN6.

Copyright © Nokia Siemens Networks 2008 Company confidential Page 43 (119) . RNC parameters related to CELL_DCH state selection and release. HSDPA user is a user that has one or more HS-DSCH MAC-d flows established. The traffic volume related parameters can be used to delay the transition from CELL_FACH to CELL_DCH. due the very long inactivity timer. This removed most of the failures due to number of HSDPA users. This was first optimised by increasing the scheduler capacity from 16 users/BTS to 48 users/BTS (16/cell). Table 14 presents example parameter sets targeted to decrease HSDPA utilisation.4. This change shows a clear improvement in accessibility and failure rates. Low utilisation and inactivity timer parameter for HSDPA and UL DCH return channel can be tuned to increase HSDPA accessibility in case maximum amount of HSDPA user is reach. Table 14. Figure 27 presents an example of the HSDPA accessibility (RNC_605a) and Figure 28 the corresponding failure analysis.) Typically cell have amount of HSDPA user which does not have any data in the buffers but are still counted. The MAD-d flow throughput and utilisation parameters can be used to release the HSDPA allocation faster. This can be. the result was a clear decrease in the failure rate. The second optimisation action was to change the low traffic volume threshold in order to decrease/postpone the transitions to CELL_DCH. The accessibility was increased further by activating the 48 users/cell in the RNC. NPO/NSO Capability Management Date: 13. (by default. this is done with parameters MaxNumberHSDPAUsers and MaxNumberHSDSCHMACdFlows.2 RU10/RU20 HSDPA users or HSDPA Mac-d flows in the cell.2011 Data Performance Optimisation Guide for Version 2. both parameters are set to 0 – default value does not restrict the number of HSDPA users. The results show that the main accessibility failure cause is too many HSDPA users. thus enabling higher number of users in cell level. for example.

2011 Data Performance Optimisation Guide for Version 2. HSDPA accessibility with optimisation.4. NPO/NSO Capability Management Date: 13. HSDPA accessibility failure analysis with optimisation steps. Figure 28.2 RU10/RU20 Figure 27. Copyright © Nokia Siemens Networks 2008 Company confidential Page 44 (119) .

1. the parameter MaxBitrateULPSNRT was also applicable to the HSDPA UL return channel. This Copyright © Nokia Siemens Networks 2008 Company confidential Page 45 (119) . It is recommended to remove impact of this parameter by setting it to value 0 dB (throughput based AC algorithm not in use). In RAS06. see Figure 29. In RU20 onwards there is own parameter HSDPAMaxBitrateUL which defines the maximum user bit rate allowed in the cell for HSDPA UL DCH return channel. UL AC could be based on both throughput and power based PS call algorithm depending on the parameter settings. can be used to optimise resources for HSDPA UL DCH. There have to be enough free UL CE capacity available to setup HSDPA UL return channel or HSDPA setup will fail. Effect of PrxLoadMarginMaxDCH on HSDPA return channel accessibility.2 HSDPA UL Return Channel HSDPA UL return channel rejections due AC can be monitored with RNC_662a . This HSDPA Baseband resource reservation is symmetric for uplink and downlink. not only for HSDPA UL return channel. PrxLoadMarginMaxDCH parameter defines interference margin for the maximum UL DCH load.HSDPA access Failure Rate due the UL DCH. the UL DCH data rate of 16 kbps for HSDPA return channel is supported in addition to currently supported 64. In RAS06.2 RU10/RU20 6. Existing RAS05 and RAS51 features support the dynamic use of lower DCH data rates for HSDPA UL DCH return channel. By default the value of this parameter is 384 kbps. together with PBS or TBO. Using other value than default (0 dB). Prior to RU20. This parameter is valid for all R99 PS bearers. Figure 29. resources are not reserved for HSDPA UL return channel. and cannot be used for other purpose but HSDPA only. The following existing functionalities are applied to the HSDPA UL return channel (UL DCH):  Priority based scheduling and Overload control – PBS can release or downgrade existing NRT allocation if there is other user requesting initial capacity in congested situation.4. However. 16 kbps for HSDPA return channel feature. and depends on scheduler type (shared or dedicated). 128 and 384 kbps bitrates. BTS HW type and release. for example value of 2dB (37% load) can cause HSDPA UL return channel rejections due AC to increase. NPO/NSO Capability Management Date: 13.2011 Data Performance Optimisation Guide for Version 2. HSDPA BTS CE resource reservation is always fixed.

downlink spreading code.2011 Data Performance Optimisation Guide for Version 2. Relation between UL CE usage and HS-DSCH setup failures (RAS06) Activation of TBO and HSDPA 16 kbps Return channel improves HSDPA accessibility (blue line) as can be seen from Figure 31 below. UL interference. However. More detail description of PSB and TBO can be found from [7] As can be seen from Figure 30 below. NPO/NSO Capability Management Date: 13. Congestion of following resources can trigger enhanced priority based scheduling function: DL power.4. 128).TBO of PS Algorithms feature downgrades the DCH bit rate down to 16 kbps if the high bit rate DCH is used inefficiently which help saving resources (mainly BTS CE. RT over NRT actions can be targeted to UL return channel DCH. transmission and downlink spreading code resources)  Upgrade of NRT DCH Data Rate (Normal or Flexible upgrade)  RT-over-NRT RT over NRT and pre-emption actions for any reason shall not be targeted to Mac-d flow. This is because of improved UL CE resource usage. the HS- SETUP_FAIL_BTS_HS_DSCH_BGR drops significantly Figure 30. When Maximum used CE drop below 124 (from max. there is clear correlation between UL CE usage and HS- DSCH setup failures. Copyright © Nokia Siemens Networks 2008 Company confidential Page 46 (119) . BTS HW (CE) and Iub transmission  Throughput based Optimization . the PBS downgrade existing DCHs from higher data rates to 16 kbps one by one until the maximum number of users in the BTS is achieved. causing also the release of MAC-d flow.2 RU10/RU20 means that for example in case of CE congestion.

the final EDCH active set size is not acceptable.2 RU10/RU20 Figure 31.2011 Data Performance Optimisation Guide for Version 2. The decision between DCH and E-DCH allocation for a UE is based on the service (RAB parameters). resource availability. HSUPA allocation is not possible if there is ongoing IFHO or ISHO measurements. Parameter EDCHQOSClasses defines whether certain traffic class and traffic handling priority is allowed to use for HSUPA. NPO/NSO Capability Management Date: 13.RNC_913a can be used to monitor HSUPA accessibility from user point of view. HSDPA mobility is disabled or HS-DSCH allocation is not possible. When 16 kbps is activated.1. Minimum allowed bit rate for HSDPA UL return channel is set with parameter HSDPAminAllowedBitrateUL. the throughput based optimisation and flexible upgrade features can be activated for HSDPA return channel with parameter DynUsageHSDPAReturnChannel (This require that TBO or/and FU features are also activated in the network). Limitation should be disabled with the parameter BitRateSetPSNRT. multi-RAB combination and UE capability. Activation of TBO and 16 kbps return channel (RAS06) 16 kbps Return channel DCH data rate support for HSDPA is RAS06 optional feature. the PS tries to allocate the DCH in both UL and DL. 6. High level HSUPA KPI . which can be activated by the operator with management parameter HSDPA16KBPSReturnChannel. Low performing cells can be then ranked to more detail analysis RNC_913a_HSUPA_ Accessiblity   ALLO_SUCCESS_EDCH_INT + ALLO_SUCCESS_EDCH_BGR  100% ALLO_SUCCESS_EDCH_INT + ALLO_SUCCESS_EDCH_BGR + EDCH_ALLO_CANC_NA_AS_BGR + EDCH_ALLO_CANC_NA_AS_INT  UL_DCH_SEL_MAX_HSUPA_USR_BGR + UL_DCH_SEL_MAX_HSUPA_USR_INT  UL_DCH_SEL_BTS_HW_INT + UL_DCH_SEL_BTS_HW_BGR   + SETUP_FAIL_EDCH_BTS_BGR + SETUP_FAIL_EDCH_BTS_INT  SETUP_FAIL_EDCH_OTHER_BGR + SETUP_FAIL _EDCH_OTHE R_INT + SETUP_FAIL _EDCH_TRANS_BGR  SETUP_FAIL _EDCH_TRAN S_INT + SETUP_FAIL _EDCH_UE_BGR + S ETUP_FAIL_ EDCH_UE_INT Copyright © Nokia Siemens Networks 2008 Company confidential Page 47 (119) . If the allocation of HS-DSCH in downlink is not possible.3 HSUPA Accessibility HSUPA cannot be established without HSDPA. the UL return channel is HSUPA instead of R99.4.

due the too many simultaneous users. if this procedure will not allow HSUPA channel type the HSUPA selection failure counters are triggered. Reports and PIs related HSUPA accessibility PI ref PI name / Abbreviation PI unit Copyright © Nokia Siemens Networks 2008 Company confidential Page 48 (119) . the HSUPA setup will also fail. HSUPA Accessibility failure analysis Below are main KPIs needed for HSUPA accessibility analysis. first HSUPA channel type has to be selected in channel type selection procedure.. 74/cell and 80/BTS in users reached RU20 ) No Check BH Channel element resource usage UL DCH selected Yes UL/DL due BTS HW (BTS in state that no capacity available for EDCH) No HSUPA fail due Yes Not Acceptable HSUPA is not supported in SHO branch Setup failures Active Set No HSUPA Setup Fail Yes Check BH Channel element resource usage BTS UL/DL No HSUPA Setup Fail Yes Check RB reconfiguration failure rate UE (Terminal problem) No HSUPA Setup Fail Yes Check AAL2 connections (not enough CID) or TRANS Signalling problems No Yes HSUPA Setup Fail Go for troubleshooting Other ( E.2011 Data Performance Optimisation Guide for Version 2. Also. HSUPA selection can also fail if Active set size is not acceptable. for example. if HSDPA Mac-d flow setup is failing. NPO/NSO Capability Management Date: 13.4. RNC internal failures) Figure 32. After HSUPA channel type is selected the actual HSUPA radio bearer setup will take place and is this fails the HSUPA setup failures are triggered.2 RU10/RU20 Equation 2 – RNC_913a HSUPA Accessibility from User point of view HSUPA access is done in two phases.g. HSUPA selection and setup failures reasons are similar to HSDPA. Selection failures Low HSUPA No No Action accessibility Needed Yes Yes Check Number of simultaneous HSUPA users Too many HSUPA (60/BTS in RU10. Table 15.

12 Figure 33. Figure 34 shows an example of HSUPA setup failure causes. NPO/NSO Capability Management Date: 13. Example of HSUPA performance (RU10/RU20).4. No changes compared to RU10. M1002) E-DCH Allocation FR due to NA AS (E-DCH allocation cancel due to non RNC_1103b acceptable active set) % RNC_968b UL DCH Selected due to too many HSUPA users % RNC_957c E_DCH not selected due the BTS HW % RNC_956c E-DCH Setup FR due to BTS % RNC_1105c E-DCH Setup FR due to Transport % RNC_1106c E-DCH Setup FR due to UE % RNC_1104c E-DCH Setup FR due to Other Failures % Figure 33 presents example of HSUPA performance. RU10 RU20 MP1 RU20EP1 WN6.2 RU10/RU20 Report: System Program RNSRAN000 RNC_923c E-DCH selections # RNC_913a HSUPA Resource Accessibility for NRT Traffic % RNC_928b HSUPA attempts # RNC_915c HSUPA Setup Success Ratio from user perspective % RNC_923c E-DCH selections # Report: Service/Session Accessibility Analysis RSRAN073 (M1022. but there is also some level of transport and BTS failures. Copyright © Nokia Siemens Networks 2008 Company confidential Page 49 (119) . Most failures are due to Other reason.2011 Data Performance Optimisation Guide for Version 2.0 EP1 RU20 MP2 first cluster PP1.

2 RU10/RU20 RU10 RU20 MP1 RU20EP1 WN6. there is new BTS parameter HSUPAXUsersEnabled which is used to reserve corresponding license from RNC license pool (3/12/24/60) for BTS. Limitations are also valid for Soft and softer (cell only) HO branch additions.12 Figure 34. BTS informs RNC that E-DCH users can be taken in when at least 32 channel elements (dynamic reservation) are reserved for E-DCHs (18 CE in case of Flexi Rel2 HW). Parameter NumberEDCHReservedSHOBranchAdditions (default=2) defines the number of E-DCH allocations that are reserved only for soft and softer handover branch additions in the cell and for soft handover branch additions in the BTS LCG. Each active E-DCH user requires channel element capacity. In RU10. With the exception of fixed reservation.g. Flexi Rel1 HW and Flexi Rel2 HW). Copyright © Nokia Siemens Networks 2008 Company confidential Page 50 (119) . If there is not enough CE for HSUPA. The values of these parameters are checked only in E- DCH allocation and E-DCH branch addition phases. The Value of this parameter is subtracted from both. Maximum amount of HSUPA users are limited either with parameter or license. In RAS06. In the CE allocation. Example of HSUPA setup failure causes (RAS06/RU10) DCH is selected instead of EDCH if Maximum amount of HSUPA allocations is reached either in cell or in BTS LCG. the CE allocation for HSUPA is dynamic and depending upon both the number of HSUPA connections and load generated by the DCH traffic.0 EP1 RU20 first cluster MP2 PP1. Cell specific PS use a value which is lower than these two values (parameter or license).2011 Data Performance Optimisation Guide for Version 2. DCH capacity request are able to pre-empt the set of CE allocated to HSUPA (with the exception of the minimum static allocation of 8 CE in RAS06). DHC has a higher priority than HSUPA. HSUPA resource steps and reservations are different between HW releases (e. the maximum number of E-DCH allocations in the cell and the maximum number of E-DCH allocations in BTS LCG to achieve correspondingly the maximum number of new E-DCH allocations in the cell and BTS LCG. In RAS06. the maximum value is defined with license ‘HSUPA.4. this fixed reservation of 8 CE is removed (0 CE in RU10). In RU10. RU20 72 HSPA users feature increase the number of HSUPA users to 72 per cell (80/BTS) Parameters MaxNumberofEDCHCell and MaxNumberEDCHLCG together with license define maximum number of E-DCH allocations in the cell and BTS LCG respectively. the minimum static allocation of 8 CE (for both UL and DL) is reserved as soon as HSUPA is enabled at a WBTS. Basic 3/12/24 and parameters MaxNumberofEDCHCell and MaxNumberEDCHLCG. the HSUPA setup will fail. The HSUPA baseband processing requirements are symmetric across the UL and DL directions. NPO/NSO Capability Management Date: 13.

2011 Data Performance Optimisation Guide for Version 2. NPO/NSO Capability Management Date: 13. Default value of 136 dB means approximately RSCP value of -114 dBm. the resource Manager starts to free resources used by HSUPA There seems to be also correlation between EDCH setup failures and Maximum CE usages. As HSUPA CE resource reservation is symmetric. There is defined the coverage area when the HSUPA 2ms TTI can be used.CableLoss – Meas CPICH RSCP < CPICHRSCPThreEDCH2MS (136 dB) + MAX(0. Figure 35. Relation between CE usage and HSUPA setup and selection failures The 2ms HSUPA TTI is selected if enabled with parameter HSUPA2MSTTIEnabled . then it is controlled with parameter CPICHRSCPThreEDCH2MS (RNC). UETxPowerMaxRef . both UL and DL should be monitored.4. PtxPrimaryCPICH . Copyright © Nokia Siemens Networks 2008 Company confidential Page 51 (119) . then CPICH RSCP of current cell must satisfy equation below.2 RU10/RU20 Additional free capacity of 6 CE is needed top of the HSUPA resource steps to avoid ‘ping-pong’ effect in reserving and freeing HSUPA resource steps. When there is no possible to use HSUPA 2 ms TTI then HSUPA TTI is reconfigured to 10 ms TTI. When free channel element capacity drops below 4 CE. then it is controlled with parameter CPICHECNOThreEDCH then CPICH Ec/Io of current cell must satisfy equation below Meas CPICH Ec/Io > CPICHECNOThreEDCH2MS (-6 dB) Currently there are no counters to monitor switching in between 2ms TTI and 10 ms TTI EDCH reconfiguration. UE supports 2 ms TTI and RAB combination supports SRB on HSUPA. If the selection is from Cell_FACH.P_MAX)*. If selection is from Cell_DCH.

2. Features 16-QAM + 10/15 +10 Mbps/ +14. TCP IP settings etc. like Air Interface and Iub. . MIMO and DC) Throughput cannot be guaranteed for PS NRT Interactive or Background class services including HSPA. it is important to monitor number of simultaneous HSPA users as well.6 Mbps with MIMO and ~35 Mbps with DC-HSDPA. although it can be achieved only in nominal conditions commonly not available for users. one Cat10 UE can achieve the maximum bit rate of 13.976Mbps ~14 Mbps (13. NOTE! HSPA+ features are supported with Rel2 BTS HW only 6. which refers quite well FTP application level throughput (with 10% HARQ retransmission).2.2 HSPA Throughput and RTT (incl. Table 16 below give TCP/IP payload of 18.4) Mbps RLC payload) and RU20 increase bit rate to 42 Mbps with DC-HSDPA feature. but with lower priority.1.2. Test of maximum HSDPA throughput and understanding of the required configuration is a starting point for HSDPA feature performance tests and performance optimisation. These issues are covered with chapter 6.  Problems with drive test tools (QoS profile. NPO/NSO Capability Management Date: 13. typically all drive test/field measurement results are based on application level throughput.2 Mbps for 64QAM user.1.2. RU20 target for DL application level throughput is ~ 19 Mbps with 64QAM. Most of the resources. the maximum RLC throughput is 9. are shared between the users causing performance degrading when amount of users in the cell increase.2. In RU10.) RU10 optional feature.2011 Data Performance Optimisation Guide for Version 2. This Nominal bitrate is scheduled as Guaranteed BitRate. In RAS06.1.1 HSDPA peak performance and configurations HSDPA bitrates depend upon the protocol stack layer from where they are measured. More details can be found in [14] 6.6 Mbps for single users (Cat-9 UE).4 HSDPA MIMO DC-HSDPA Mbps/ code user user 64-QAM (2 flows) (2 flows) Min. Counters and KPIs that can be used to monitor HSDPA throughput performance are listed in 6. Counter statistics can be used to detect network wide problems and bottlenecks. When monitoring HSDPA throughput with the counters. UE Category Cat-6 Cat-8 Cat-9 Cat-10 Cat-14 Cat-16 Cat-24 Modulation 16-QAM 16-QAM 16-QAM 16-QAM 64-QAM 16-QAM 64-QAM Number of HS-PDSCH codes 5 10 15 15 15 30 30 Copyright © Nokia Siemens Networks 2008 Company confidential Page 52 (119) . 23. Following has impact to user and cell throughputs:  Radio Channel Conditions  UE category and types  Activated features  Shortage on Iub User plane or DCH traffic too high  Incorrect Iub Parameter settings  HSPA parameters and HSDPA power parameter settings  Problems in core network or application server.1.4. Throughput measurements together with other counters can be used identify possible causes for low throughput.2 RU10/RU20 6. Streaming QoS for HSPA enables also the definition of Nominal Bit Rate (NBR) for Interactive and Background NRT MAC-d flows. It is crucial to understand which protocol layer throughput is referred.1 HSDPA throughput Optimisation Both Counter statistic and drive test logs can be used to detect HSDPA throughput problems.

32 11.0 42. NPO/NSO Capability Management Date: 13.54 12. all interfaces and protocol layers. Results are FTP throughputs.4 Table 16.89 9.10% 2. Copyright © Nokia Siemens Networks 2008 Company confidential Page 53 (119) .98 8.6 42.84 13.58 6.8 21.53 6.4 21. Flexible RLC feature was used with the HSDPA measurements.0 18.1 28. transport block size (bits) 7168 13904 19891 27952 42192 55904 84384 Max.1 27.8 9.95 14.2 DSCH) bit rate (Mbps) RLC PDU (bits) 336 656 656 656 11216 1312 22432 RLC blocks/TTI 21 21 30 42 3.72 9.7 23.82 8. TCP/IP payload (Mbps) 2.9 37.36 6.9 42.6 18.1 RLC payload (Mbps) . transport channel (HS.4 21.95 9.0 21.99 5. Maximum achieved DL application level throughput in RU10 is 11.4 HARQ retrans. RU20 new features increase HSDPA throughput to 18-19 Mbps with 64QAM.60 13. (NORM is Nokia Reference Mobile which is R&D UE and capable of changing it’s category).4 14.3 36.4.6 28.0 26.5 Mbps. Max Achieved HSDPA application level throughputs for different category UEs The maximum achievable throughput has to be supported by the whole end-to-end connection.8 43.2 23.76 84 7. Maximum user bit rates with different RAS features (RU20) Error: Reference source not foundFigure 36 below show lab measurement results for different category UEs for RU10 and RU20. “HSPA Radio Network Planning Guide” [1] and section “Checking HSDPA settings in network elements” in RAS06 product documentation [3]. Novatel Ovation MC996d was used for HSDPA Cat18 (MIMO) measurements and Qualcomm 8220 used for Cat24 (DC-HSDPA) measurements. Norm UE was used up to Cat8. DC-HSDPA throughput was verified with UDP.91 5. 3. 23 Mbps with MIMO and 35 Mbps with HSDPA DC feature.2 RU10/RU20 Air interface bit rate (Mbps) 4. Novatel Ovation was used for HSDPA Cat14 measurements.1 RLC payload (Mbps) 3. HSDPA parameters for high bit rate testing are listed below.2 Max.2011 Data Performance Optimisation Guide for Version 2. Figure 36.6 14. This topic is handled in multiple references like “RAN E2E system performance optimization guide” [12].51 RLC bit rate (Mbps) 3.

9 dB – this can set to “off” When troubleshooting HSDPA user throughput. 15 is possible for HSDPA only if MaxNbrOfHSSCCHCodes is 1 or 2. TBS & Retransmission – Check Transport block size (TBS) during transmission and retransmission rate. Easiest way to avoid the HLR profile to limit the throughput is set this to 0 (not limit) because if limitation is active (by default). MIMO supports only 16QMA modulation. the HSDPA DL peak rate maximum cannot be higher than the RAB maximum. NPO/NSO Capability Management Date: 13. BTS is using compensated CQI to selected Transport block side (TBS). and it is possible to have 15 codes for HSDPA even when MaxNbrOfHSSCCHCodes =3/4 and HSUPA enabled. or limitations in Iub / core networks.4. which shows TBS and retransmission rate for two different test cases HS-SCCH Usage. peak rate of NRT RB mapped to HS-DSCH and peak rate of UL return channel limited to RAB attribute maximum bit rate received from RANAP or not. • Parameter HSDPAPeakRateLimitRABMax defines the peak rate of MAC-d flow. Typical retransmission rate 10%. Copyright © Nokia Siemens Networks 2008 Company confidential Page 54 (119) . HSPA 72 users feature change HS-SSCH code allocation to dynamic.2 RU10/RU20 • Parameter MaxBitRateNRTMACDFlow defines the maximum bit rate of NRT MAC-d flow. 16QAM and 64QAM modulations for HSDPA. following should be checked: CQI – Maximum performance can be reach on with high CQI values. Maximum number of HS-SCCH codes increase from 3 to 4. in very good conditions can be less than 10%. Number of codes allocated for HSDPA – With HSUPA enabled. UE support is required in both cases. HS-DSCH SIR has to be equal to or higher than the threshold before RLC PDU size 656 bits can be selected o By default (RU10) this is .2011 Data Performance Optimisation Guide for Version 2. See example in Figure 39. Compensated CQI value of 32 is required to reach maximum 64QAM performance. Value of this parameter can be set according to activated license or directly use RU10 default special value 65535 no restriction for NRT MACD flow. Modulation – RU20 supports QPSK. High retransmission rate can decrease the throughput even when TBS is high.Monitor HS-SCCH usage (HSDPA activity/utilisation) as low usage indicate bottleneck in some part of the network like TCP limitations (client or/and server). (MaxNbrOfHSSCCHCodes is the parameter to enable code multiplexing). o RU10 default value 1 (Limitation is active) • RU20 new features require that Flexible RLC is enabled with FlexiRLC parameter • Parameter PDUSize656WithHSDSCH enables the use of PDU size 656 • The maximum bit rate of the NRT RB has to be equal to or higher than the threshold defined with parameter PDUSizeBitRateThr before the PDU size 656 bits can be selected o Use default 3584 to use PDU size 656 • Parameter PDUSizeCodeThreshold defines number of codes required to use PDU size 656 bits o Change this from default 10 to 5 to use 656 always for maximum throughput • Parameter PDUSizeSIRThr defines the HS-DSCH signal to interference ratio threshold for the usage of RLC PDU size 656 bits in DL data transfer if the RB is mapped to HS- DSCH in the DL. Reported CQI can be used to estimate what kind of bit rates are possible but CQI reported by the UE is different that compensated CQI.

4. NPO/NSO Capability Management Date: 13. ( 5 x 100M file downloads) In both cases. but as can be seen in Figure 39. Field test case is also measured in good radio conditions (RSCP -50dBm). the retransmission rate is close to 10%. 64QAM throughput measured in the lab and in the field.2011 Data Performance Optimisation Guide for Version 2. Figure 38 below show HSDPA 64QAM throughput results for both lab (Vepro) and the field (Ahvenatie). (Both get high TBS) Figure 38. in the lab retransmission rate is below 2% which have clear impact for the throughput. there is differences in retransmission rate. the retransmission rate was close to 10% while in lab it was only 2%. Example of HSDPA link adaption parameters. the same TBS was reached. Copyright © Nokia Siemens Networks 2008 Company confidential Page 55 (119) . While in the field. This explains the throughput difference between the cases.2 RU10/RU20 Figure 37. the average DL application (FTP) throughput ~19 Mbps while in the field ~17 Mbps was reached. but in case of field. In the lab.

In cell edge. Figure 40 below show RSCP vs. isolated cell with both MIMO and DC-HSDPA enabled. HSDPA 64QAM result showing TBS and retransmission rate. MIMO and 64QAM comparison measurements done in NSN test network. Vepro is measured in the lab and Ahvenatie case is measured in the field. under empty. 18. the 16QAM modulation is used in both cases.2 RU10/RU20 Figure 39.7 M) show clear gain against MIMO (Ave.4. DL application throughput. NPO/NSO Capability Management Date: 13. usage of 64QAM modulation start to increase when RSCP increase above -80 dBm. Figure 40. 15M). 27. isolated cell). the DC HSDPA (ave.2011 Data Performance Optimisation Guide for Version 2. RSCP vs. DL application throughput result from 64QAM and 16QAM drive test comparison (test done under empty. Measurement done in the field. In good RF environment. (5x100M file downloads) 64QAM is used only in good RF environments. Copyright © Nokia Siemens Networks 2008 Company confidential Page 56 (119) . Figure 41 below show result from DC-HSDPA.7M) and 64QAM (Ave. drive test Comparison of 16QAM and 64QAM - Test is done in NSN test network under isolated cell without any other traffic to ensure that conditions remains unchanged between testing.

For example. Category 22 or 24 is required to support maximum DC HSDPA throughput in RU20 on top. DMCU upgrade is needed in RNC196 and RNC450 to support new RU20 user bitrates. Comparison of DC-HSDPA. Laptop & Server Settings: Client Settings: Use Clean.g. Iub Capacity can be checked from the COCO. Old CDSP-C cards need to be replaces with CDSP-HD cards.4.nokiasiemensnetworks. In RU20 maximum 64QAM user throughput can be achieved with Cat14 and Cat18 HSDPA UEs. Copyright © Nokia Siemens Networks 2008 Company confidential Page 57 (119) . MIMO maximum throughput can be achieved with Cat 18 UE. by using Wireshark (Ethereal) that change is done. Conform e. used user plane size of 40000 cps equals to 16. use ready made tools like TCP optimiser to change values. RNC Capacity RNC HW capacity can also limit throughput. Iub Capacity: High enough Iub capacity ensures that throughput is not limited by Iub. Iub capacity calculations per feature can be found: https://sharenet-ims.2011 Data Performance Optimisation Guide for Version 2.inside. MIMO and 64QAM DL application level throughputs in the field (RSCP around -60 dBm in measurement location) UE category and type: Performance between the UE types can vary.96Mbps.com/Open/404366147 Core Networks: Flexi ISN GGSN should be used as old GGSN HW is not valid for maximum throughput.2 RU10/RU20 Figure 41. NPO/NSO Capability Management Date: 13. Never set TCP values manually by modifying registers (same parameter can be in the several places). high-spec laptop instead of NSN build laptop with TCP receive window size >=256kB (unnecessarily high values should be avoided). Currently there are no commercial available terminals supporting DC HSDPA (9/2010).

g.2 HSDPA throughput Monitoring and troubleshooting HSDPA selections (RNC_614c) together with HSDPA data volume (RNC_608b) can be used to monitor possible capacity bottlenecks. Also incorrect parameter settings (Iub/Radio). Throughput per allocated HS-DSCH [8] Low HSDPA throughput could be a reason from several issues. the HSDPA selections and data volume increase   SETUP_FAIL _UE_HS_DSC  SETUP_FAIL H_STR way. HSDPA selections_HSDPA_POW increase but ER_STR data volume remains constant.CH_STR e. Throughput can also be limited due the drive test tools (if used) E.RNC_614c HSDPA Selections (RU10)   SETUP_FAIL _IUB_HS_TOTAL_BGR  SETUP_FAIL _RNC_HS_DSCH_STR  SETUP_FAIL _IUB_HS_TOTAL_STR  Normally.2011 Data Performance Optimisation Guide for Version 2.  ALLO_HS_DSCH_FLOW_INT  ALLO_HS_DSCH_FLOW_BGR  ALLO_HS_DSCH_FLOW_STR    DCH_SEL_MAX_HSDPA_US ERS_INT  DCH_SEL_MAX_HSDPA_US ERS_BGR  DCH_SEL_MAX_HSDPA_US E   REJ_HS_DSCH_RET_INT  REJ_HS_DSCH_RET_BGR  REJ_HS_DSCH_RET_STR  SETUP_FAIL _RNC_HS_DS    SETUP_FAIL _UE_HS_DSCH_INT  SETUP_FAIL _BTS_HS_DSCH_INT  SETUP_FAIL _IUB_HS_TOTAL_INT RNC _ 614c     SETUP_FAIL _RNC_HS_DSCH_BGR  SETUP_FAIL _UE_HS_DSCH_BGR  SETUP_FAIL _BTS_HS_DSCH_BGR Equation 3 . Iub or BTS Channel Elements.1.e. activated features and used server settings can cause throughput to be lower than expected. similar If this is not the case. it indicates that possible capacity bottleneck exist somewhere. For example it could be related to return channel. NPO/NSO Capability Management Date: 13. which can be limited due to UL interface.   DL_DCH_SEL_HSDPA_POW ER_INT  DL_DCH_SEL_HSDPA_POW ER_BGR  Figure 42.2 RU10/RU20 6. as can be seen from picture below.2. _BTS_HS_DS  DL_DCH_SEL with same linearity I. not only due to radio channel conditions (lack of DL power or low CQI).g.4. Copyright © Nokia Siemens Networks 2008 Company confidential Page 58 (119) . not optimised TC IP settings in laptop/server side or low power laptop.

HSDPA traffic and throughput KPIs and counters PI ref PI name / Abbreviation PI unit Report: System Program RNSRAN000 RNC_930b Packet Session Attempts # RNC_614c HS-DSCH selections # RNC_926b HSDPA attempts # RNC_608b HSDPA received data Mbit RNC_722b Active HS-DSCH MAC-d throughput. #simultaneous HSDPA users and throughput (RNC HW?) Iu-PS capacity available or HSDPA IP Back Bone / PS CN Figure 43.4. Table 17. network perspective Kbps RNC_1879b Average HSDPA end user throughput kbps RNC_5043a HSDPA MAC-d data volume at RNC (added to RU10 system program) Mbps RNC_721c Average MAC-d flow throughput (added to RU10 system program) Kbps Report: Cell Data Volume and Throughput at RNC RSRAN077 (M1023) M1023C8 HS_DSCH_DATA_VOL Byte RNC_941a HSDPA MAC-d average throughput at RNC Kbps M1023C9 NRT_DCH_HSDPA_UL_DATA_VOL Byte RNC_1175a HSDPA UL Return Channel Throughput (DCH) Kbps Report: Allocated Traffic Amounts (R99 + HSPA) RSRAN070 (M1002. General flow chart to analyse HSDPA throughput [8] Table 17 lists the relevant reports and PIs for HSDPA RB throughput monitoring and troubleshooting. M5000) Copyright © Nokia Siemens Networks 2008 Company confidential Page 59 (119) .2 RU10/RU20 HSDPA Throughput Limiting Factor Air interface support from CQI distribution Analysis A 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.2011 Data Performance Optimisation Guide for Version 2. NPO/NSO Capability Management Date: 13.

The other PIs measure the average throughput and they show that equal values can be achieved from different measurements (Cell throughput M1023. NPO/NSO Capability Management Date: 13. Iu-PS Throughputs RSRAN064 ATM interface based average throughput for outgoing traffic (RNC side) RNC_950b (RSRAN080) Mbps RNC_732b HSDPA ATM VCC traffic load Iub downlink (RSRAN087) Cps RNC_986a PS Data in DL (RSRAN068) Mbps RNC_753a Average ATM VCC egress throughput (RSRAN087) Cps Iu-PS Throughputs RSRAN064 RNC_934a Iu-PS incoming interactive user data throughput in RNC (RSRAN064) Kbps RNC_935a Iu-PS incoming background user data throughput in RNC (RSRAN064) Kbps RNC_912a Iu-PS GTP input traffic rate in RNC (RSRAN064) Kbps Radio Connection Performance Measurement M1017 based RNC_613b Average NRT HS-DSCH DL Throughput Mbps For HSDPA. BTS M5000 and RCPM M1017). Figure 44 shows an example of HSDPA throughput measurement from multiple throughput PIs (RNC_722c. 128kbit/s Kbps RNC_689b HS-DSCH return channel allocations. 64kbit/s Kbps RNC_688c HS-DSCH return channel allocations. total Kbps RNC_1027b HS-DSCH return channel allocations. network perspective Mbps RNC_606d HSDPA MAC-d average net throughput at BTS Mbps RNC_941a HSDPA MAC-d average throughput at RNC Kbps RNC_608b HSDPA received data Mbit RNC_686d HS-DSCH return channel allocations.2 RU10/RU20 RNC_683b HSDPA MAC-d flow allocations # RNC_684c HSDPA MAC-d flow allocation duration Min RNC_721c Average MAC-d flow throughput Mbps RNC_722c Active HS-DSCH MAC-d throughput. it is possible to monitor both cell and user level throughput.4. RNC capacity RSRAN068. It mainly shows that the active throughput PI RNC_722c shows quite close the measured average throughput from drive test tool. RNC_914a and RNC_613b)) and drive test log. 16kbit/s Kbps RNC_687c HS-DSCH return channel allocations. This gives the freedom to choose the PI based on the available measurements. during HSDPA usage # RNC_2054a Average Scheduled HSDPA users per TTI # Report: HSPA Overview RSRAN092 RNC_706b Average Reported CQI # RNC_626b Active HSDPA time share % RNC_685a HS-DSCH utilization ATM Iub Throughputs RSRAN080. RNC_606d.2011 Data Performance Optimisation Guide for Version 2. M1001) RNC_645c Average number of simultaneous HSDPA users # RNC_726e Average number of simultaneous HSDPA users. For the cell throughput different PIs are available. 384kbit/s Kbps Report: Number of HSPA Users and UE capability RSRAN051 (M1000. Copyright © Nokia Siemens Networks 2008 Company confidential Page 60 (119) . Throughput measured from drive test log is application level throughput. Iub capacity RSRAN087.

Activation of M1027 measurement table generates less load than activation of existing M1017 counters. Figure 45 shows RLC active bit rate separately for interactive and background traffic classes per RAB max bit rate. the object includes TC. RNC_1455a HSDSCH Cell throughput PI is based on M5002 measurements (RU10 new) and includes both new and retransmitted MAC-hs PDUs.4. For RNC level. RAB max bit rate and RB bit rate. Figure 45 Example of throughput measurements included to M1027 Copyright © Nokia Siemens Networks 2008 Company confidential Page 61 (119) .2011 Data Performance Optimisation Guide for Version 2. but results are pre-aggregated either to RNC (M1027) or Cell (M1026) level. THP.2 RU10/RU20 Figure 44. NPO/NSO Capability Management Date: 13. HSDPA throughput measurement from BTS and drive test log. RU10 introduce new RCPM RLC measurement tables including same counters as existing RCPM RLC M1017 measurement table.

RNC_1879b Average HSDPA end user throughput Average Number of HSDPA users KPIs (RNC_726d). RNC _ 722c RNC _ 1879a  Max( RNC _ 726d * RNC _ 685b.2011 Data Performance Optimisation Guide for Version 2. Average HSDPA throughput per session can be calculated by using KPI RNC_1879a. (RECEIVED_HS_MACD_BITS .DISCARDED_HS_MACD_BITS) * 500 RNC _ 1879b  HSDPA_BUFF_WITH_DATA _PER_TTI * RNC _ 2054a) Equation 5. It can be seen that the average number of buffers with data is about 1.2 RU10/RU20 Low HSDPA throughput analysis can start by calculating rough HSDPA User Throughput.5. Average Active HSDPA throughput can be monitored with the RNC_722c which calculates the actual HSDPA throughput on cell level.1) Equation 4 – RNC_1879a Average HSDPA throughput per session RNC_1879b is new end user throughput formula included RU20 system program report. Other way of calculating is to adjust Average number of simultaneous HSDPA users by the real activity of those users i. Priorisation is done in HSDPA scheduler between buffers with data. HSDPA_BUFF_WITH_DATA_PER_TTI Number _ of _ user _ buffers  ( HS_SCCH_PWR_DIST_CLASS_0  HS_SCCH_PWR_DIST_CLASS_1  HS_SCCH_PWR_DIST_CLASS_2  HS_SCCH_PWR_DIST_CLASS_3  Equation 6. Copyright © Nokia Siemens Networks 2008 Company confidential Page 62 (119) . TTI utilization (RNC_685a). Simplest way to calculate throughput per HSDPA user is to divide RNC_722c average active HSDPA throughput with Average number of HSDPA users (Either with RNC_645c or RNC_726d). included to previous version of the KPI (RNC_1979a) also counts those users not necessary having any data in the buffer. formula sow HSDPA_BUFF_WITH_DATA_PER_TTI / # of active TTIs. NPO/NSO Capability Management Date: 13.e. where denominator includes those users having data in the buffer multiplied by Average number of users per scheduler per TTI formula. When very low amount of HSDPA users or/and low utilization. Number users with data in buffer HS_SCCH_PWR_DIST_CLASS_4  HS_SCCH_PWR_DIST_CLASS_5 ) Below is one example from number of users in the buffer compared with other KPIs.4. KPI below can be used instead to count number of users having data in the buffer (HSDPA_BUFF_WITH_DATA_PER TTI counter is counting number of user buffers with data in the buffer for each TTI). this KPI give value close to RNC_722c.

2 RU10/RU20 Figure 46. Legacy UEs are reporting CQI values from 0-30 when MIMO UEs are reporting both CQI type A (from 0-14) and type B (from 0-30). Compensated CQI Reported CQI is the value Reported by the UE. Example of RNC_1879b HSDPA end used throughput formula vs. Reported CQI values can be used to estimate what kind of bitrates are available in air interface. NPO/NSO Capability Management Date: 13. Compensated CQI report values from 1-35. but BTS decides transport block size based on compensated CQI not based on reported CQI. BTS link adaption compensates CQI for the differences between assumed HS-PDSCH transmit power and actual available HS-PDSCH transmits power by targeting 10% HARQ retransmission rate. It is not possible to capture compensated CQI Copyright © Nokia Siemens Networks 2008 Company confidential Page 63 (119) .2011 Data Performance Optimisation Guide for Version 2.4. average active cell throughput RNC_722b Reported CQI vs. and this is the CQI that can be captured from the drive test logs and CQI distribution counters (M5000). Buffers with data Example (RNC_726b_number of HSDPA users per cell) Figure 47.

2 RU10/RU20 values from the drive test logs and counter stats.2011 Data Performance Optimisation Guide for Version 2. Measurement power offset is signaled to the UE when HS-DSCH MAC-d flow is set-up or if updating is needed due to serving HS-DSCH cell change. CQI distribution counters (M5000) or Average CQI (RNC_706a) can be translated into throughput with CQI throughput mapping.4. Example of differences between the Compensated CQI and Reported CQI In RAS06. Low throughput but high CQI/EcNo typically indicates that there is some other bottleneck in the network which limits the throughput. Figure 48 show theoretical difference between compensated CQI (from LA table) and Reported CQI (from CQI mapping table) Modulation for QPSK 16-QAM 64-QAM Cat 13-18 Compensated CQI Reported CQI Figure 48. Also there are some differences between terminals related to reported CQI values. the Compensated CQI has been seen to be 2-3 dB better than reported CQI as power offset makes reported CQI looks worse than it is in practice. mapping table Figure 49 – Air Interface bitrate estimation using reported CQI Measurement power offset. By using reported CQI counters it is possible to estimate what kind of bitrates are possible in air interface. Internal tool called DSP browser can be used to collect compensated CQI values directly from the BTS if needed. The difference between reported and Compensated CQI depends on channel quality and bit rate. MPO is calculate as below G  Ptx _ allowed _ HSDPA  PCPICH Copyright © Nokia Siemens Networks 2008 Company confidential Page 64 (119) . NPO/NSO Capability Management Date: 13. CQI report from live Scale CQI value up by Estimate the throughput network per cell 2-3 dB using tp. G is the default power offset between HS-PDSCH and P-CPICH.

5 2 Table 19.2 RU10/RU20 where Ptx_allowed_HSDPA is calculated as follows   Ptx _ allowed _ HSDPA  MAX MIN PtxMaxHSDPA. dB (calculated) 6. Mobile Power Offset Calculation (MPO) for different Cell power setting – PtxMaxHSDPA is set to same value as PtxCellMax Reported CQI is not absolute measure of channel quality as CQI compensation will tune the HSDPA bit rate according to actual channel conditions and available power.2011 Data Performance Optimisation Guide for Version 2.5 35. Copyright © Nokia Siemens Networks 2008 Company confidential Page 65 (119) .5 . TBS with different CPICH tx Powers. HSDPA performance comparison with different CPICH Tx Power values.5 Available HSDPA pwr (W) 16. Measurements done under isolated cell by repeating same route with different CPICH tx power values of 30 dBm and 33 dBm. Nemo Outdoor MPO Values are from drive test done under isolated cell. No changes for other parameters (e. PtxCellMax 43 40 40 PtxCPICH 33 30 33 CCCH total 35. However.1 2. half of the available HSDPA power is signaled to UE.  GammaFactor is RNC-internal (hidden) parameter which has an actual value of 0.4 8.5. this impact only reported CQI values and has no negative impact to final performance as BTS make decision (about TBS) based on compensated CQI (by knowing how much power there is actually available for HSDPA) Table 18 below show MPO calculation for different BTS & CPICH power combinations. throughput is slightly higher as there is more power available for HSDPA RSCP EcNo Average CQI Ave TBS size MPO CPICH 30 -80.  The PtxMaxHSDPA parameter defines the maximum allowed HSDPA tx power.5 32. Reported CQI can be improved by optimization on DL FR quality and level (RF optimization) only.8 -8. without any other traffic.4. which is matching for the value extracted from the drive test tool (Nemo Outdoor). NPO/NSO Capability Management Date: 13.2 -11.0 where:  Pmax is the cell maximum output power  Ptx_non_HSPA is the latest received PtxNonHSPA measurement.1 3.g.3 dB but average reported CQI increase only ~ 1.5 0.5 Gammafactor 0. Reported CQI can not be improved by direct parameter changes in NSN RAN. While decreasing CPICH tx power by 3 dB (from 33 dBm to 30 dBm). With CPICH 30. CQI value reported by UE is then 3 less than it should be based on actual available power.2 6.1 6.35 22358 6 CPICH 33 -77.5 23 20972.2 4.5 Ptx_Allowed HSDPA (W) 8.1 MPO from Nemo 6 6 2 Table 18.  Pmax  Ptx _ non _ HSPA  * GammaFactor .05 24.5 0. Based on formulas above. PtxCellMax was same in both cases).2 MPO. Average reported EcNo decrease ~ 2. Figure 50 below show average CQI vs.

TBS with different CPICH Tx Powers from drive test logs. In RU10. RU10 shows slightly increased CQI values as Interference to own and neighbour cells is decreased due to the less power used for HSDPA. BTS link adaptation reduces HS-PDSCH power for low data rate users and users who are in good radio conditions to value needed to reach the target BLER (10%). maximising the single user throughput (BLER could be even ~0%). impact is not very big as can be seen from Figure 51 below. RU10 Figure 51. NPO/NSO Capability Management Date: 13. Due to spectral efficient link adaption.2011 Data Performance Optimisation Guide for Version 2. In RAS06 all available power was used for HS-PDSCH transmissions. However.2 RU10/RU20 Figure 50. CQI comparison between RAS06 and RU10 Copyright © Nokia Siemens Networks 2008 Company confidential Page 66 (119) .4 after upgrade to RU10.4. Average CQI vs. average RNC level CQI increase 0.3-0.

NPO/NSO Capability Management Date: 13. The relation of Average reported CQI and HSDPA User throughput in live network.2011 Data Performance Optimisation Guide for Version 2. average CQI.2 RU10/RU20 Example blow show HSDPA cell throughput vs. HSDPA cell throughput in live network (RU10) Below is one example of Average CQI vs. the average throughput is about 2 Mbps Figure 52. It can be seen that even if there is 7. The relation of Average reported CQI vs. which show that average CQI limits also the throughput per user capability. HSDPA user Throughput (RNC_1879b). Figure 53.2 Mbps or more possible to have from the cell. Copyright © Nokia Siemens Networks 2008 Company confidential Page 67 (119) .4.

TBS is increased while continue to use QPSK with all available codes. Switching between the modulations happens as example below where channel conditions improve from being poor according to link adaption. With 5 codes.2 RU10/RU20 Modulation and code multiplexing In RU20. QPSK. NPO/NSO Capability Management Date: 13.  The Number of codes are increased while using QPSK – if all available codes are used then the coding rate is increased. i. The TBS is then futher increased while using 16QAM with all available codes. the 16QAM modulation can be maintained longer than with 10 code feature. However. Figure 55 and Figure 54 shows HSDPA behaviour with 5 code and 10 code features when FTP Download is performed. 16QAM and 64QAM modulations are supported. Figure 54. the modulation is switched from 16QAM to QPSK prior to decreasing number of codes.4.  If coding rate becomes to high then the modulation scheme is switched from 16QAM to 64QAM and then the TBS is further increased while using 64QAM with all available codes.2011 Data Performance Optimisation Guide for Version 2. With 10 codes.  If coding rates becomes too high then the modulation scheme is switched from QPSK to 16QAM (decreasing the coding rate by increasing the physical channel capacity). The Average number of codes remains high even with low RSCP value. Number of codes and used modulation when RSCP drops – HSDPA 5 code feature Copyright © Nokia Siemens Networks 2008 Company confidential Page 68 (119) . Number of codes is maximised by the link adaptation algorithm for maximum spectral efficiency.e. MIMO supports only 16QAM.

HSDPA codes are always evenly divided between the users when code multiplexing between the users in same TTI is performed.4. In RU10. Number of codes and used modulation when RSCP drops – HSDPA 10 Code feature In RAS06. NPO/NSO Capability Management Date: 13. Copyright © Nokia Siemens Networks 2008 Company confidential Page 69 (119) . This will give possibility to allocate codes unevenly between the users. as can be seen from Figure 56 RU10 Figure 56. more codes to high data rate users and less code for those users who have low amount of data in the buffer. New usage of 16QAM codes transmission in RU10 due the unevenly distributed codes between the users. the HS-PDSCH codes and power resources are shared between code multiplexed MAC-d flows based on channel conditions and amount of data in the buffer.2 RU10/RU20 Figure 55. This will increase usage of small 16QAM code users.2011 Data Performance Optimisation Guide for Version 2.

NPO/NSO Capability Management Date: 13.4.2011
Data Performance Optimisation Guide for Version 2.2
RU10/RU20

Number of HS-SCCH channels increase from 3 to 4 in RU20 with Rel2 HW. This also increase
the number of scheduled users per TTI to 9. The Spectral Efficient Link Adaptation can Increase
the number of scheduled users per TTI if their combined throughput is low enough. In case of
shared scheduler for BB efficiency, up to 9 UEs can be served in one TTI (max 4 UEs per cell)
with Flexi Rel2 HW while up to 6 UEs per TTI can be served by scheduler based on WSPC/Flexi
System module Rel1 HW.

BTS scheduling algorithm maximised always the cell throughput. If Better throughput is
achieved by scheduling only 3 users per TTI then no more users are scheduled in that TTI.
Typically throughput in code multiplexing case (several users per TTI) is anyway limited for other
reasons (low data amount in buffer, low CQI etc.) and more users per TTI can be scheduled
without decreasing the achievable throughput. When many low data rate users, the number of
scheduled users can be increased as function of total throughput. If throughput with n user is
under possible throughput with n+1, one user is added into scheduling on that TTI. Throughput
will not be reduced to get more users. For example, if there are 4 users on scheduling (Rel1
HW) but they have throughput together only 4 Mbps. Then MAC-hs takes 5 th user into
scheduling.

Max throughput that can be sent by Shared HSDPA Scheduler for BB efficiency in One TTI
WSPF / FSMC/D/E WSPF / FSMC/D/E
Scheduled users per TTI WSPC/FSMB RU20 RU20 On top
1 scheduled UE's per TTI 21.1 Mbps
2 scheduled UE's per TTI 10.8 Mbps 21.1 Mbps 42.2 Mbps
3 scheduled UE's per TTI 21.1 Mbps
4 scheduled UE's per TTI 7.2 Mbps 14.4 Mbps 21.1 Mbps
5 scheduled UE's per TTI 5.4 Mbps 14.4 Mbps 21.1 Mbps
6 scheduled UE's per TTI 3.6 Mbps 10.8 Mbps 14.4 Mbps
7 scheduled UE's per TTI n/a 7.2 Mbps 14.4 Mbps
8 scheduled UE's per TTI n/a 5.4 Mbps 10.8 Mbps
9 scheduled UE's per TTI n/a 3.6 Mbps 7.2 Mbps
Table 20. Maximum throughput that can be sent by shared HSDPA scheduler for BB efficiency in
one TTI. (This table does not include MIMO or DC HSDPA users)

BTS scheduling efficiency can be monitored HSDPA_users_x_y_cells counters (= x users in
RNC_2054a((HSDPA_UStarget cell, _CELLS
ERS_0_1_IN y users HSDPA_USER
in other cell), which
S_1_0_IN_C  collection measurement data of simultaneous code
ELLS)are
multiplexed HSDPA users in TTI level. Average Number
2* (HSDPA_USE RS_0_2_IN_CELLS HSDPA_USER S_1_1_IN_CELLS HSDPA_USER S_2_0_IN_C of users per TTI can be monitored using
ELLS)
RNC_2054a below; all cells under same HSDPA Scheduler should show same value for this
3 *(HSDPA_US ERS_0_3_IN_CELLS HSDPA_USER S_1_2_IN_CELLS HSDPA_USER S_2_1_IN_CELLS HSDPA_USER S_3_0_IN_CELLS) 
KPI. This formula is also included to denominator when calculating HSDPA user throughput
4* (HSDPA_USE RS_0_4_IN_ CELLS HSDPA_USER S_1_3_IN_CELLS HSDPA_USER S_2_2_IN_CELLS HSDPA_USER S_3_1_IN_CELLS HSDPA_USER S_4_0_IN_CELL
(RNC_1879b)
5* (HSDPA_USE RS_0_5_IN_CELLS HSDPA_USER S_1_4_IN_CELLS HSDPA_USER S_2_3_IN_CELLS HSDPA_USER S_3_2_IN_CELLS HSDPA_USER S_4_1_IN_CELL
6* (HSDPA_USE RS_0_6_IN_CELLS HSDPA_USER S_1_5_IN_CELLS HSDPA_USER S_2_4_IN_CELLS HSDPA_USER S_3_3_IN_CELLS HSDPA_USER S_4_2_IN_CELL
7* (HSDPA_USE RS_0_7_IN_CELLS HSDPA_USER S_1_6_IN_CELLS HSDPA_USER S_2_5_IN_CELLS HSDPA_USER S_3_4_IN_CELLS HSDPA_USER S_4_3_IN_CELL
8* (HSDPA_USE RS_0_8_IN_CELLS HSDPA_USER S_1_7_IN_CELLS HSDPA_USER S_2_6_IN_CELLS HSDPA_USER S_3_5_IN_CELLS HSDPA_USER S_4_4_IN_CELLS
9*( HSDPA_USER S_1_8_IN_CELLS HSDPA_USER S_2_7_IN_CELLS HSDPA_USER S_3_6_IN_CELLS HSDPA_USER S_4_5_IN_CELLS )
HSDPA_USER S_0_1_IN_CELLS + HSDPA_USER S_1_0_IN_CELLS + HSDPA_USER S_0_2_IN_CELLS + HSDPA_USER S_1_1_IN_CELLS+
HSDPA_USER S_2_0_IN_CELLS + HSDPA_USER S_0_3_IN_CELLS+ HSDPA_USER S_1_2_IN_CELLS + HSDPA_USER S_2_1_IN_CELLS +
HSDPA_USER S_3_0_IN_CELLS + HSDPA_USER S_0_4_IN_CELLS+ HSDPA_USER S_1_3_IN_CELLS + HSDPA_USER S_2_2_IN_CELLS+
HSDPA_USER S_3_1_IN_CELLS + HSDPA_USER S_4_0_IN_CELLS + HSDPA_USER S_0_5_IN_CELLS + HSDPA_USER S_1_4_IN_CELLS +
HSDPA_USER S_2_3_IN_CELLS + HSDPA_USER S_3_2_IN_CELLS + HSDPA_USER S_4_1_IN_CELLS+ HSDPA_USER S_0_6_IN_CELLS +
HSDPA_USER S_1_5_IN_CELLS + HSDPA_USER S_2_4_IN_CELLS + HSDPA_USER S_3_3_IN_CELLS + HSDPA_USER S_4_2_IN_CELLS+
HSDPA_USER S_0_7_IN_CELLS+ HSDPA_USER S_1_6_IN_CELLS+ HSDPA_USER S_2_5_IN_CELLS + HSDPA_USER S_3_4_IN_CELLS+
HSDPA_USER S_4_3_IN_CELLS+ HSDPA_USER S_0_8_IN_CELLS+ HSDPA_USER S_1_7_IN_CELLS + HSDPA_USER S_2_6_IN_CELLS+
HSDPA_USER
CopyrightS_3_5_IN_C ELLS +Networks
© Nokia Siemens HSDPA_USER
2008 S_4_4_IN_CELLS+ HSDPA_USER
Company confidential S_1_8_IN_CELLS+ HSDPA_USER S_2_7_IN_C
Page 70ELLS
(119)+
HSDPA_USER S_3_6_IN_CELLS + hHSDPA_USE RS_4_5_IN_CELLS

NPO/NSO Capability Management Date: 13.4.2011
Data Performance Optimisation Guide for Version 2.2
RU10/RU20

Equation 7. RNC_2054a Average Number of scheduled users per TTI per scheduler

RNC_2093a can be used to monitor Average number of SF16 codes reserved for HSDPA. This
KPI is based on duration of HSDPA x code counters. Picture below show 100 weeks history data
of two KPIs, RNC_2093a and RNC_722b collected from one RNC. HSDPA x code counters
(M1000C248-C258) show duration of x code reservation, as soon as there is one HSDPA Mac-d
flow allocated to cell, all available codes are reserved for HSDPA regardless of HSDPA UE
category. Original transmitted_x_code counters for QPSK/16QAM can be used to monitor
number of codes allocated for UE (see Figure 56).

Figure 57. RNC_2093a Average reserved SF16 codes for HSDPA and RNC_722b Active HSDPA
throughput.

Copyright © Nokia Siemens Networks 2008 Company confidential Page 71 (119)

NPO/NSO Capability Management Date: 13.4.2011
Data Performance Optimisation Guide for Version 2.2
RU10/RU20

6.2.1.3 MIMO throughput performance & monitoring

In RU20, MIMO is supported with 16QAM modulation. 64QAM modulation is not supported with
MIMO. Maximum MIMO dual stream bit rate per transport block 2*13.98 = 27.95 Mbps,
providing around 24Mbps downlink application level throughput with dual stream transmission.

Figure 58 below show MIMO measurement results done in very good network environment.
Above picture show downlink application level throughput (FTP) for MIMO (3 x 100M file
downloaded) and TBS separately for both streams. Below picture show MIMO usage and CQI
and CQI2. During testing average downlink application level throughput of 23.4 Mbps was
measured.

MIMO TBS
and TBS1

MIMO CQI
and CQI2 MIMO Usage

Figure 58. MIMO “peak” performance.

Example below show MIMO drive test results done in NSN test network. Modulation is plotted
separately for both streams. Above chart show also RSCP along route and below chart the DL
application level throughput is included.

Copyright © Nokia Siemens Networks 2008 Company confidential Page 72 (119)

20. Dual stream is selected if  UE preference is dual stream (indicated by CQI)  Buffer status > TBS1+TBS2 – mimoDualStreamOffset bits (hard coded to BTS) MIMO is reporting both CQI type A (0-14) and type B (0-30). 4/5. MIMO is reporting CQI and CQI 2 (from 0-14). MIMO drive test under NSN test network.40. Above chart show modulation for main stream and RSCP along the drive route. 7/8.  CQI feedback cycle (range: 0. where CQI feedback cycle = 8 ms CQI repetition factor = 2 and N CQI type A / M = 9/10 Copyright © Nokia Siemens Networks 2008 Company confidential Page 73 (119) . NPO/NSO Capability Management Date: 13. which by default is 9/10 indicating that every 10 CQI report is type B.32.8. 1/1) When analyzing MIMO CQI from drive test results.2011 Data Performance Optimisation Guide for Version 2. 9/10. both CQI type A and CQI type B can be seen.10.16. 6/7.2.80 ms)  CQI repetition factor (range: 1. where N_cqi_typeA/M_cqi ratio is new for MIMO. For Type A. MIMO usage in Nemo is indicating how often dual stream transmission is used. These parameters are listed below. 2/3.4)  N_cqi_typeA/M_cqi ratio (range: 1/2. Type B is send periodically for single stream ‘fall back’ in case the BTS decides to use single stream while the UE is reporting the dual stream.3. As MIMO CQI differs from CQIs reported by legacy HSDPA UEs.64. 3/4.4. Chart below show modulation for secondary stream and also DL application throughput along the route.2. there is own counters to monitor MIMO CQI values (M5000C339 – C357). 8/9. CQIs are send based on A/M ratio.2 RU10/RU20 Figure 59 . Figure 60 below shows example from CQI report cycle.4. 5/6. RNC informs UE of parameters which defines CQI report sending pattern.

 RNC_2049a Active MIMO users MIMO CQI can be monitored with MIMO CQI counters.  RNC_2095a_MIMO Usage ratio  RNC_2096a retransmission ratio for MAC-ehs PDUs using MIMO dual stream Number of scheduled TTIs separately for dual stream and single stream users  M5000C336 TTIs Scheduled for MIMO users with Dual stream  M5000C335 TTIs Scheduled for MIMO users with Single Stream Users having MIMO dual stream mode active can be monitored with Average Active MIMO users PI. NPO/NSO Capability Management Date: 13.2 RU10/RU20 New CQI sent every 4 TTI = 8 ms Type A CQI Type B CQI Complete cycle of 10 × 4 = 40 TTI = 80 ms Figure 60.2011 Data Performance Optimisation Guide for Version 2.4. MIMO CQI counters include classes from 0 to 18 as can be seen below. The number of original MAC-ehs PDUs transmitted with MIMO dual stream compared to the total number of original MAC-hs PDUs being transmitted can be monitored with MIMO usage ratio.  Class 11: The counter is updated by 1 because of the following class criteria: class11: sum(CQI1+CQI2)= (17 or 18) and (Diff<5)  Class 17: The Counter is updated by 1 because of the following class criteria: class17: sum(CQI1+CQI2)= 25 or 26 Copyright © Nokia Siemens Networks 2008 Company confidential Page 74 (119) . For example. Counters and KPIs to Monitor MIMO performance. Below example of MIMO parameters included to Radio bearer reconfiguration message. Example of CQI report cycle.  MIMO CQI – M5000C339 – 357.

carrier spacing tp (Mbps) DC Call 10713 10687 5.2011 Data Performance Optimisation Guide for Version 2. Maximum double peak rate for single user is 42 Mbps.6 33 OK 10713 10691 4.8 33 OK 10713 10690 4. providing DL application level throughput of 36 Mbps with 10% retransmission rate.8 MHz to 5. Figure 62 show DC HSDPA throughput example from the lab.4 35 OK 10713 10692 4. Table 21 below show measurement result done by BTS product line.2.2 .2 RU10/RU20 Figure 61. NPO/NSO Capability Management Date: 13. 1st ch. currently there is not DC HSDPA UE which support carrier spacing over 5 MHZ so functionality of 5. Figure 62.2 MHz for DC HSDPA.2MHz carrier spacing it is verified by product line. NOK 10713 10689 4.4. Example of DC HSDPA throughput in lab NSN BTS support carrier spacing from 3. UE support for different carrier spacing should be checked.1. 2nd ch. Example of MIMO CQI counters distribution 6.4 DC HSDPA throughput and Performance Dual Cell HSDPA feature allow 2 adjacent channels to be combined to generate an effective HSDPA channel bandwidth of 10 MHz.2 33 OK Copyright © Nokia Siemens Networks 2008 Company confidential Page 75 (119) .

After DC HSDPA UE penetration increase. in one of the cell or in both of the cells. the uplink capacity may be limiting factor in primary cell if fixed configuration is used. Flexible configuration require that HSUPA is enabled for both of the carriers and allows both cells to simultaneously act as primary serving cell for some DC HSDPA capable UE and secondary serving HSDPA cell for some DC HSDPA capable UE. Proportional fair scheduler decides the scheduled user on cell separately per TTI and DC HSDPA user is included in scheduling in both cells.8 25 OK Table 21. Violet line show combined throughput of both UEs DC HSDPA UE 64QAM UE Figure 63. Single cell and dual cell users are scheduled in fair manner simultaneously in both cells. When 64QAM UE start downloading (yellow). DC HSDPA UE is doing continuous download (blue line) while 64 QAM is downloading 100 Mbps files (Pink line). Figure 63 below show DL application throughput when there is simultaneously DC HSDPA and 64QAM UEs. which then act as primary serving HSDPA cell for DC-HSDPA capable UE. Currently there is no UE in the market which supports 5. DC HSDPA is scheduled 100% in other cell but only 10% in the cell where there is active 64 QAM UE. In fixed configuration.4. the DC HSDPA usage decrease in the cell where 64 QAM UE is active. but uplink return channel is always served with primary cell.2 RU10/RU20 10713 10693 4 30 OK 10713 10694 3. Based on cell specific scheduling decision per TTI. DC HSDPA configuration can be fixed or flexible. it is possible to start with fixed configuration and expands to flexible configuration when number of DC HSDPA capable UEs increase if enabling HSUPA in all cells is an issue (require license). However. the DC user can be scheduled in none of the cells. the HSUPA is enabled only in one of the carriers. Copyright © Nokia Siemens Networks 2008 Company confidential Page 76 (119) . throughput in case there is simultaneously DC HSDPA and 64QAM users.2011 Data Performance Optimisation Guide for Version 2. NPO/NSO Capability Management Date: 13. Figure 64 show HS-SCCH usage in case there is both DC HSDPA and 64 QAM UE simultaneously active. Functionality and performance of Dual Cell HSDPA with different frequency carrier spacing. This is the case in downlink.2 MHz carrier spacing.

2011 Data Performance Optimisation Guide for Version 2. a UE which is scheduled high throughput in cell 1 (possible because it is the only active UE) will have a reduced scheduling. reprsents the total average throughput allocated for the UE. This average TBS is based upon the previously allocated TBS in both cells belonging to the DC HSDPA cell pair i. There is some DC HSDPA specific counters & KPIs which can be used to monitor DC HSDPA performance. new PM counters need to be included in some throughput and data volume KPIs. HS-SCCH usage for both DC HSDPA and 64 QAM UE A scheduler metric is calculated for each RF carrier and instantaneous Transport block Size (TBS) is generated separately for each cell by link adaptation. network perspective  RNC_1879c Average HSDPA end user throughput  RNC_606e HSDPA MAC-d average net throughput at BTS  RNC_739d HSDPA MAC-d data volume at BTS  RECEIVED_HS_MACD_BITS . Thus. These KPIs are:  RNC_608c HSDPA received data  RNC_721d Average MAC-d flow throughput  RNC_722d Active HS-DSCH MAC-d throughput.2 RU10/RU20 DC HSDPA UE – primary cell 64QAM UE DC HSDPA UE – secondary cell Figure 64.DISCARDED_HS_MACD_BITS   (MC_HSDPA_ORIG_DATA_PRI  MC_HSDPA_ORIG_DATA_SEC)*8 All KPIs above should include new DC HSDPA counters which monitor total amount of Multi- Carrier HSDPA original data send on MAC-ehs PDUs in the primary and secondary cell.  HS_SCCH_PWR_DIST_CLASS_0  HS_SCCH_PWR_DIST_CLASS_1     HS_SCCH_PWR_DIST_CLASS_2  HS_SCCH_PWR_DIST_CLASS_3  Table 22.  M5002C128MC_HSDPA_ORIG_DATA_SEC (kB)    M5002C129MC_HSDPA_ORIG_DATA_PRI (kB) RNC _ 722d  For example new version of RNC_722d includes counters M5002C128 and 129. After enabling DC HSDPA feature in the network.e. Example of RNC_722d Average Active HSDPA throughput   HS_SCCH_PWR_DIST_CLASS_4  HS_SCCH_PWR_DIST_CLASS_5)   Copyright © Nokia Siemens Networks 2008 500 Company confidential Page 77 (119) .4. NPO/NSO Capability Management Date: 13.

2 RU10/RU20 There also two new counters to monitor total amount of positively acknowledged Multi-carrier HSDPA data send on MAC-ehs PDU in primary and secondary cell. per Cell (%)  RNC_2105a Average number of DC HSDPA capable users.4. per Cell (%)  RNC_2101a DC HSDPA Usage Ratio. number of TTIs for scheduled DC HSDPA users for Primary and Secondary carrier when either one or two carrier is used can be monitored: Figure 65. per Cell  RNC_2106a Average number of DC HSDPA capable users. per WBTS  RNC_2107a Average number of Active DC HSDPA capable UE using 2C. Also DC HSDPA Usage ratio can be monitored (based on active DCHSDPA UE/capable DCHSDPA UEs)  RNC_2100a DC HSDPA Usage Ratio. per BTS (%)  RNC_2102a DC HSDPA two carriers Usage Ratio. Cell  RNC_2108a Average number of Active DC HSDPA capable UE using 2C. Example of TTI counters for scheduled DC HSDPA user for Primary and Secondary cells Copyright © Nokia Siemens Networks 2008 Company confidential Page 78 (119) .  RNC_5114a Multi Carrier PDU drop ratio in the radio interface (%)  RNC_5115a Multi Carrier PDU drop ratio on BTS level (%) Average number of DC HSDPA capable and Active UEs can be monitored separately. WBTS  RNC_2109a Average number of Active DC HSDPA capable UE using 1C Using M5000C331-C334 counters.2011 Data Performance Optimisation Guide for Version 2. NPO/NSO Capability Management Date: 13. Based on these counters two new PI are introduced which can be used monitor MC PDU drop ratio.

2 HSUPA throughput optimisation HSUPA throughput problems can be detected either by using drive test tools (user level throughput problems) or with counters stats when network/BTS/cell level problems can be tracked.8 Mbps features.2. The lowest parameter value among the values of the parameter of the cells that belongs to the E- DCH active set is used when the E-DCH is allocated. NPO/NSO Capability Management Date: 13.8 Mbps is activated or to 3840 kbps (2 x SF2) if HSUPA 2.1. RU20 introduce HSUPA 2ms TTI feature which increase HSUPA maximum throughput to 5. BTS HW capacity and Iub Capacity.44 Mbps Table 23.1 HSUPA Peak performance and configuration HSUPA throughput depends on parameter settings.2.2 with some examples. these explained in chapter 6. When some condition is not fulfilled during a call. In RU20 total BTS level HSUPA throughput increase to 21 Mbps (12. Also air interface start to limit HSUPA throughput when several HSUPA users under same cell. 6.2011 Data Performance Optimisation Guide for Version 2. The test results is shown in Figure 85 (end of this chapter) UL throughput values with different setting of above parameters.0 is activated.8 Mbps. UE capability.0 Mbps means that RNC is allowed to set up the bit rate for the UE when requested by core network (in RAB QoS) and when needed conditions are met.8 Mbps but for 5.2.89 Mbps 2*SF2+2*SF4 5760 11484 bits 5.8 Mbps the 2ms TTI feature is needed.2. Different counters and KPIs can be used to monitor HSUPA throughput performance and problems in network level. HSUPA bitrates with different MaxTotalUplinkSymbolRate settings  Parameter FactorEDCHMaxBitRate should be set to 0 (Restriction not set) or checked together with the RAB UL max bit rate setting in HLR  Parameter ThresholdMaxEDPDCHSR can be used to restrict the maximum total Uplink symbol rate of E-DPDCH based on maximum uplink user bit rate of the RAB (see [1]).2.6 Mbps in RU10) (there can be up to 6 cells under one HSUPA scheduler) RU20 introduces HSUPA 2ms and HSUPA 5.2.  Parameter MaxTotalUplinkSymbolRate defines maximum total UL symbol rate of the E- DPDCH(s) of the UE in the cell and should be set to 5760 (2 x SF2 + 2 x SF4) if HSUPA 5.4. activated features. HSDPA peak performance issues and configurations are discussed with chapter 6.672 2*SF4 1920 14484 bits 1. 2ms HSUPA TTI can be enabled without 5. RNC may downgrade a UE bit rate. Supporting HSUPA 2. Copyright © Nokia Siemens Networks 2008 Company confidential Page 79 (119) . suitable UE category and that the bit rate is supported also in the neighbouring cells (no SHO needed??). The needed conditions are.2 RU10/RU20 6. MaxTotalUplinkSymbolRat TBS RLC Throughput e SF4 960 7110 0. HSUPA channel is often used simply as return channel for HSDPA while it carriers only acknowledgment type of small packets.38 Mbps 2*SF2 3840 19950 bits 1. for instance.2.

High PrxMaxTargetBTS values should only used for demonstration purposes.2011 Data Performance Optimisation Guide for Version 2. not in live network. Figure 67 below show maximum HSUPA throughput when 2ms TTI and HSUPA 5. Average uplink application level throughput was 4. RU20 maximum supported TBS is 11484 with 2ms TTI and 2xSF4 + 2xSF2 (this require that SRB can be mapped to HSUPA in uplink) High retransmission rate can decrease the throughput even with high TBS.4. This is possible to change with Feature RAN2170 “Adjustable HSUPA BLER target for PS NRT” if there is need for high bit rate demostrations Figure 66. RU20 introduce own set of parameters for HSUPA 2ms TTI RAS06 TN RU10 TN SW_127 & Parameter RAS06 default SW_104 RU10 default RU20 default DelayThresholdMax 300 ms 8 ms 8 ms 100 ms DelayThresholdMid 70 ms 4 ms 4 ms 70 ms DelayThresholdMin 40 ms 1 ms 1 ms 50 ms ProbabilityFactorMax 0.1 0.1 Table 24. Default HARQ retransmission target is 10%. Example of HSUPA link adaption parameters. NPO/NSO Capability Management Date: 13. Maximum TBS 11848 was reach during testing.7 Mbps with around 10% retransmission rate.8 0.8 0. HSUPA throughput can be limited by  UE Tx Power – UE is already using its maximum Tx power  Serving Grant – Maximum grant is used already  Data – UE buffer is empty – no new data to send PrxMaxTargetBTS – Parameter PrxTargetMaxBTS define maximum target for received total wide band power in the cell for BTS Packet scheduling. the highest HSUPA rates were achieved using parameter values listed in TN SW 127.8Mbps features are enabled. following should be checked: Modulation – RU20 supports only QPSK for HSUPA TBS & Retransmission – Check Transport block size (TBS) during transmission and retransmission rate. Measurements are done under empty cell (no other traffic) by setting parameter PrxMaxTargetBTS = 30 dB to avoid air interface limitations during peak bit rate testing. When troubleshooting HSUPA user throughput.1 DelayThresholdMax2msTTI 100 ms DelayThresholdMid2msTTI 70 ms DelayThresholdMin2msTTI 50 ms ProbabilityFactorMax2msTTI 0.2 RU10/RU20 Low HSUPA throughput can be also due the wrong HSUPA congestion control parameter settings. HSUPA congestion control parameters. In RU10. Copyright © Nokia Siemens Networks 2008 Company confidential Page 80 (119) .

Next test show HSUPA performance with DCH load with default parameters. PrxTargetPSMin/Max = 4 dB). Copyright © Nokia Siemens Networks 2008 Company confidential Page 81 (119) . High values increase also nonHSPA noise caused by DPCCH+HS-DPCCH 30 dB 30 dB 20 dB 8 dB 12 dB 6 dB 10 dB 4 dB 2 dB Figure 68. (100M file uploaded) Following show results from HSUPA throughput test done to test effect of PrxMaxTargetBTS on HSUPA 5. After starting the HSUPA. NPO/NSO Capability Management Date: 13.2 RU10/RU20 Figure 67. Parameter PrxMaxTargetBTS defines the maximum UL noise rise (NR) level used by the BTS scheduler. Result indicated that PrxMaxTargetBTS value 6 dB (default) gives 90% of the maximum throughput while PrxMaxTargetBTS value 4 dB gives 75% of the maximum throughput with low EbNo value (high power efficiency) High PrxMaxTargetBTS value (>12 dB) is required for peak rate testing but high values will cause lot of variation on uplink noise and application throughput resulting performance degradation of all users in cell. Cell was first loaded with R99 NRT data users and after that HSUPA was started. During testing. Figure 69 show that maximum R99 throughput was 1.3 Mbps with full R99 load.8 Mbps was activated.4. Cell with high R99 load get HSUPA throughput of around 0. the value of PrxMaxTargetBTS varies between 2 and 30 dB.3 Mbps. (PrxMaxTargetBTS = 6 dB.2 Mbps at 4 dB UL noise rice and HSUPA throughput was 0. HSUPA throughput when 2ms TTI and 5.2011 Data Performance Optimisation Guide for Version 2. the R99 UEs were shut down one by one.8 Mbps feature throughput. íncreased R99 load will decrease HSUPA throughput. HSUPA throughput (yellow) and Noise rise with different PrxMaxTargetBTS values HSUPA and R99 are sharing uplink resources.

HSUPA UE1 2x100M UL Figure 70. Figure 71 below present cell level UL application throughput with different number of HSUPA UEs. under NSN test network.4. and by achieving maximum throughput the parameter Maximum total uplink symbol rate have to be set 3840. HSUPA performance with R99 load. Maximum achieved UL cell level application throughput is around 3 Mbps with 2 HSUPA UEs.0Mbps with 10ms TTI Following study show HSUPA Cell and user peak throughput when 2Mbps and 10ms TTI is enabled. HSUPA 2.0 feature is activated. Figure 70 below show UL application (green line) level throughput when HSUPA 2. HSUPA NR PrxTargetPSMax Figure 69. Adding more UEs does not increase UL cell level throughput due uplink air interface limitations. Copyright © Nokia Siemens Networks 2008 Company confidential Page 82 (119) . This test is done in lab.2011 Data Performance Optimisation Guide for Version 2.2 RU10/RU20 . changing this parameter does not improve total uplink cell throughput significantly but rather make uplink unstable. PrxMaxTargetBTS =6 dB (default) HSUPA 2. NPO/NSO Capability Management Date: 13. HSUPA throughput with HSUPA 2 Mbps feature Uplink radio resources are shared between the HSUPA and R99 users. As can be seen from results below. Parameter PrxTargetMaxBTS define maximum target for received total wide band power in the cell for BTS Packet scheduling.0 Mbps is licensed feature.

In case of 3 HSUPA UE. Copyright © Nokia Siemens Networks 2008 Company confidential Page 83 (119) .2011 Data Performance Optimisation Guide for Version 2. throughput PrxTargeMaxBTS changed with 2 HSUPA UE Figure 71. NPO/NSO Capability Management Date: 13.4. Figure 73 show PrxTotal (from Online Monitor) value with different number of HSUPA Users. UL application level throughput of 1 HSUPA UE when there is different number of UEs in the cell.2 RU10/RU20 Max DL cell app. HSUPA Cell UL application level throughput with different number of HSUPA UEs and with different PrxTargetMaxBTS values (changed in case of 3 HSUPA UE) Figure 72 show uplink application level throughput of 1 HSUPA User. Figure 72. PrxtargetMaxBTS was changed from 6 (default) to 30 and both values were tested. when there is different number of users in the cell.

2. NPO/NSO Capability Management Date: 13.2 HSUPA throughput monitoring and troubleshooting RU20 introduce HSUPA 2ms TTI feature and increase the HSUPA user throughput to 5. Figure 74. Copyright © Nokia Siemens Networks 2008 Company confidential Page 84 (119) . Uplink PrxTotal with different number of HSUPA UEs With 1 HSUPA UE the uplink load is around 30%.2 RU10/RU20 Figure 73. Adding 3rd UE the load increase close to 75% (PrxTargetMaxBTS=6) and cell level throughput is not increased any more. HSUPA 2ms TTI attempts and selections cannot be monitored separately.4.8 Mbps. with 2 HSUPA UE close to 60% but not yet limited by air interface. Uplink Load with different number of HSUPA UEs 6.2.2011 Data Performance Optimisation Guide for Version 2. but there are counters/PIs to monitor number of users and TTI throughput separately for 2ms and 10 ms TTI.

HSUPA traffic and throughput KPIs and counters PI ref PI name / Abbreviation PI unit Report: System Program RNSRAN000 (M1002.2011 Data Performance Optimisation Guide for Version 2.4.2 RU10/RU20 The HSUPA performance evolution can be estimated with same method as HSDPA. M1001) Average number of simultaneous HSUPA users RNC_1036b (RNC_1036b is based on RU10 new counters) # Average number of simultaneous HSUPA users.). during RNC_1037b HSUPA usage # RNC_968b UL DCH Selected due to too many HSUPA users % Report: HSPA Overview RSRAN092 RNC_1878a Average HSUPA Mac-d throughput Mbps RNC_1883b Active HSUPA cell throughput Mbps RNC_1884b Average HSUPA throughput per session Mbps RNC_2050a Active HSUPA 2ms TTI throughput Mbps RNC_2051a Active HSUPA 10ms TTI throughput Mbps RNC_2048a HSUPA 2 ms TTI Transmission Usage Ratio % RNC_2049a HSUPA 10 ms TTI Transmission Usage Ratio % RNC_2052a Average HSUPA 2ms TTI Users # RNC_2053a Average HSUPA 10ms TTI Users # ATM VCC Traffic Load RSRAN083 (M530) RNC_752a Average ATM VCC ingress throughput Cps Copyright © Nokia Siemens Networks 2008 Company confidential Page 85 (119) . Table 25. by comparing the HSUPA selection (RNC_923b) and HSUPA data volume (RNC_931c). M1022. Table 25 lists the relevant reports and PIs for HSUPA RB throughput monitoring and troubleshooting. M5000) RNC_1117b E-DCH allocations # RNC_1118b E-DCH allocation duration Min RNC_952c HSUPA MAC-es average throughput at RNC Kbps RNC_931a HSUPA MAC-es data volume at RNC Mbit M5000C151 HSUPA_MIN_MACD_THR kbit/s M5000C152 HSUPA_MAX_MACD_THR kbit/s M5000C153 HSUPA_AVE_MACD_THR kbit/s Report: Number of HSPA Users and UE capability RSRAN051 (M1000. Service/Session Accessibility analysis RSRAN073 RNC_930b Packet Session Attempts # RNC_923c E-DCH selections (RSRAN073) # RNC_928b HSUPA attempts # RNC_1883a HSUPA active Cell throughput kbps RNC_931c HSUPA MAC-es data volume at RNC Mbit Report: Cell Data Volume and Throughput at RNC RSRAN077 (M1023) M1023C10 NRT_EDCH_UL_DATA_VOL Byte RNC_952a HSUPA MAC-es average throughput at RNC kbps Report: Allocated Traffic Amounts (R99 + HSPA) RSRAN070 (M1002. NPO/NSO Capability Management Date: 13.

RNC_1883b is HSUPA active cell throughput and naturally show highest value. M5000C153. RNC_1878a is based M5000C153 and show average HSUPA MAC-d throughput using the average over measurement period samples (updated 100ms periods). RNC_952c is data volume divided by measurement period and value of this KPI highly depends on how much HSUPA activity there is in the cell during measurement period.4. The PIs that measure the average throughput from different measurements (Cell throughput M1023 and BTS M5000) show equal values.2011 Data Performance Optimisation Guide for Version 2. HSUPA throughput PIS and drive test tool measurement. Figure 75.2 RU10/RU20 Iu-PS Throughputs RSRAN064 RNC_939a Iu-PS outgoing interactive user data throughput in RNC kbps RNC_940a Iu-PS outgoing backgroud user data throughput in RNC kbps RNC_936b Iu-PS outgoing user data throughput in RNC kbps Figure 75 shows an example of HSUPA throughput measurement from multiple throughput PIs (M5000C152. This gives the freedom to choose the PI based on the available measurements. RNC_952b) and drive test log. including inactivity time and time of allocated EDCH even if only download is done Picture below show HSUPA throughput KPI comparison. RU20 introduce new KPI RNC_1883b_HSUPA_active_cell_throughput. Copyright © Nokia Siemens Networks 2008 Company confidential Page 86 (119) . This KPI is based on existing counters and counts Average HSUPA cell throughput when at least one user is allocated for HSUPA in the cell. which is included to system program report. M5000M152 show maximum HSUPA Mac-d throughput. NPO/NSO Capability Management Date: 13.

10 ms TCP ack = 40 byte * 8 / 10ms = 32 kbps 2 ms TCP ack = 40 byte * 8 / 2ms = 160 kbps Copyright © Nokia Siemens Networks 2008 Company confidential Page 87 (119) . the RNC_2050a counts total volume of MAC-e data received with 2 ms by BTS divided by number of 2ms TTI MAC-e PDUs received by BTS.2 RU10/RU20 Figure 76. HSUPA throughput KPI comparison. example from NSN test network Active HSUPA TTI throughput can be monitored separately for 2ms and 10 ms TTIs. NPO/NSO Capability Management Date: 13. Similar also average number of HSUPA users can be monitored.2011 Data Performance Optimisation Guide for Version 2. So this is active TTI user throughput HSUPA channel is often used simply as return channel for HSDPA while it carriers only acknowledgment type of small packets.4.  RNC_2050a_Active HSUPA_2ms_TTI_Troughput  RNC_2051a_Active HSUPA_10ms_TTI_throughput  RNC_2052a_Average_HSUPA_2ms_TTI_users  RNC_2053a_Average_HSUPA_10ms_TTI_users As on example.

2011 Data Performance Optimisation Guide for Version 2.4. HSUPA throughput can be limited by BTS Channel elements. There is also differences between 10ms and 2ms resource steps as 2mst TTI HSUPA users require more processing than 10ms TTI HSUPA users. HSUPA CE allocation is done with specific sizes of resource steps. Example is from NSN test networks Figure 78.2 RU10/RU20 Figure 77. The amount of resources Copyright © Nokia Siemens Networks 2008 Company confidential Page 88 (119) . HSUPA selections and throughput. NPO/NSO Capability Management Date: 13. Example of Active HSUPA TTI throughput (both 2ms and 10ms) and Average number of HSUPA 10ms & 2ms TTI users. Number of resource steps vary between RAN release and BTS HW release.

in case of BTS CE’s.2 RU10/RU20 needed depends on the throughput (Physical layer cell level throughput) and the number of HSUPA users To be able to allocate the next HSUPA resource step. In this state.2011 Data Performance Optimisation Guide for Version 2. Figure 79 below show BTS CE HSUPA usage versus HSUPA MAX/AVE Mac-d throughput. these are the period when max used CE show very high value. BTS CE HSUPA Usage and HSUPA Maximum Mac-d Throughput (RAS06) There is own counters to monitor HSUPA CE resource status. When free channel capacity drops below 4 CE. In this state. the Resource Manager starts to free resources used by HSUPA. only first WSPC card or Flexi submodule is used in RAS06. has priority over HSUPA). More details of HSUPA resource steps can be found from BB dimensioning guideline. NPO/NSO Capability Management Date: 13. HSUPA HSUPA + R99 Figure 79. RNC sets up the E-DCH but the BTS HW shortage may cause throughput to be lower than expected. and if we compare Figure 79 and Figure 80. These counters can be used to monitor periods when HSUPA throughput is limited or HSUPA setup is not possible due the BTS HW. There is few periods HSUPA throughput is limited due the BTS HW due the increased R99 traffic which can be seen from Figure 79. the RNC does not set up the E-DCH Figure 80 present hours when HSUPA throughput is limited due the lack of BTS CE (due the increase R99 traffic which. Copyright © Nokia Siemens Networks 2008 Company confidential Page 89 (119) . If all the HSUPA users are under one cell (or there is only one cell).  M1000C270 BTS HSUPA NO HW Capacity duration is updated when BTS reports to be in state that it does not have HSUPA HW capacity available.  M1000C269 BTS HSUPA HW Limited Duration is updated when BTS is in HSUPA HW limited state. an additional free capacity of 6 CE is needed.4. The required six CEs free on top of the HSUPA resource step is to avoid a ‘ping-pong’ effect in reserving and freeing HSUPA resource step.

BTS resource status counters HSUPA throughput can be low due the Iub congestion. traffic loss or RNC HW overload. The main entities of interest are Iub in terms of transport capabilities and the RNC in terms of processing resources. NPO/NSO Capability Management Date: 13. Following counters count those messages: • M1022C71 IUB_LOSS_CC_FRAME_LOSS_IND • M1022C72 IUB_DELAY_CC_FRAME_LOSS_IND • M1022C73 HW_OVERL_CC_FRAME_LOSS_IND These problems can be detected with the KPIs. (Counters are presented in different scale. % ) Copyright © Nokia Siemens Networks 2008 Company confidential Page 90 (119) .65. Counter HW_Overload_CC_Frame loss is triggered in case when there is 3 or 4 simultaneous HSUPA UEs indicating lack of DSP/DMPG processing capacity. HSUPA congestion control feature consists of multiple detection entities separated into different parts of the system.2011 Data Performance Optimisation Guide for Version 2.4. In case of congestion with Iub or RNC: RNC sends HSUPA Congestion Control indications to the BTS based on detected received Iub FP frame delay build up or RNC HW overload.  RNC_1165a Frame protocol delay rate for E-DCH traffic  RNC 1166a Frame protocol lost rate for E-DCH traffic Figure 81 below show successfully received EDCH frames and Frame losses due the RNC HW. Following counters count those messages: • M1022C69 IUB_DELAY_CC_DELAY_IND • M1022C70 HW_OVERL_CC_DELAY_IND • RNC sends HSUPA Congestion Control indications to the BTS based on detected received Iub FP frame frame loss due to Iub delay. max frame loss 2.2 RU10/RU20 Figure 80.

 Frame Loss => 60 ms between consecutive reductions  Delay Build-up => 100 ms between consecutive reductions Once the congestion is over.interface. the E-DCH Packet Scheduler stops sending ‘DOWN’ commands to the UE and recovers gradually back to normal operation. HSUPA congestion control and HW overload CC Frame loss counter When the Node B receives a TNL congestion indication Control Frame it starts to decrease the HSUPA throughput in air. Function of Iub congestion Control In case of limited Iub capacity (e.g. Receiving the ‘No TNL Congestion’ indication. compared to ‘Delay Build-up’. 1 x E1) the full symbol rate allocation (2 x SF2) can cause throughput drops.2 RU10/RU20 Figure 81.2011 Data Performance Optimisation Guide for Version 2.  Node B waits 60 ms before re-allocating resources in case congestion reoccurs  Node B then has 200 ms to re-allocate resources to the UE from which they were removed prior to making them generally available to all UE Resources generally ‘Congestion’ available to any Indication received E-RGCH Hold Re-allocate connection from the RNC Down Period Resources Resources only available to connection ‘No Congestion’ from which they were Indication received from removed the RNC 60 ms 200 ms Figure 82. Copyright © Nokia Siemens Networks 2008 Company confidential Page 91 (119) . HSUPA congestion control decrease the HSUPA bit rate by decreasing the serving grant with too high spreading code configuration. Performance of unlimited (2 x SF2) configuration is worse than limited (2 x SF4) configuration in a site with 1 x E1 Iub. UE bit rate is decreases because the Packet Scheduler is sending a relative grant ‘DOWN’ commands. Solution to this issue is to introduce cell level symbol rate limitation MaxTotalUplinkSymbolRate parameter. NPO/NSO Capability Management Date: 13. the Congestion Indication entity send an E-DCH FP control frame of type ‘Congestion Indication’ and value ‘No TNL Congestion’ to the BTS. The E-DCH Packet Scheduler decreases the UE bit rate aggressively if received congestion indication was ‘Frame Loss’. because HSUPA congestion control fluctuates the bitrate (serving grant). This impact can be clearly seen from figure below.4.

4.5)  (= 0): Max E-DCH bit rate not sent to BTS  (> 0): E-DCH Max BitRate = FactorEDCHMaxBitRate · RAB: Max UL bit rate. Function of Iub congestion control for throughput with different symbol rate SF4 2xSF4 2xSF2 Figure 84. sent to BTS in NBAP: RL setup/reconfiguration message (IE : E-DCH Maximum Bit Rate)  Total uplink symbol rate of E-DPDCH(s) can be limited with ThresholdMaxEDPDCHSR  RAB: Max UL bit rate ≤ ThresholdMaxEDPDCHSR960kbps (def 512 kbps) OR MaxTotalUplinkSymbolRate = 960 è SF4 è 672 kbps  RAB: Max UL bit rate ≤ ThresholdMaxEDPDCHSR1920kbps (def 1024 kbps) OR MaxTotalUplinkSymbolRate = 1920 è 2 * SF4 è 1380 kbps Copyright © Nokia Siemens Networks 2008 Company confidential Page 92 (119) .2011 Data Performance Optimisation Guide for Version 2.2 RU10/RU20 SF4 2xSF4 2xSF2 Figure 83.)  E-DCH maximum bit rate limitation with RAB QoS and FactorEDCHMaxBitRate (def 1. HSUPA congestion control decrease the HSUPA bit rate by decreasing the Serving grant with too high spreading code configuration HSUPA bit rate can be limited by BTS scheduler with two mechanisms which utilise the RAB max bit rate (detail parameter description presented beginning of this chapter. NPO/NSO Capability Management Date: 13.

256 kbps  ThresholdMaxEDPDCHSR = 0 (Not set) Copyright © Nokia Siemens Networks 2008 Company confidential Page 93 (119) .2011 Data Performance Optimisation Guide for Version 2. . Uplink throughput with 1 x E1 for HSPA and different Parameter values  Test 1: Effect of FactorEDCHMaxBitRate  FactorEDCHMaxBitRate = 0 (not set).2 RU10/RU20  Otherwise (RAB: Max UL bit rate > ThresholdMaxEDPDCHSR1920kbps AND MaxTotalUplinkSymbolRate = 3840) è 2 * SF2 è 1888 kbps  Maximum set of the E-DPDCHs sent to BTS in NBAP: RL setup/reconfiguration message (IE : Maximum Set of E-DPDCHs) AND to UE in RRC: Radio bearer reconfiguration message (IE: Maximum channelisation codes) Figure 85 show result from HSUPA bit rate parameter test and impact of Iub congestion control. Q oS oS 4. 1. 3840  ThresholdMaxEDPDCHSR = 0 (Not set)  FactorEDCHMaxBitRate = 0 (Not set)  RAB Max UL bit rate 4132 kbps  Test 3: Effect of RAB QoS and ThresholdMaxEDPDCHSR  RAB Max UL bit rate 64.Q .Q . With 1 x E1.4. NPO/NSO Capability Management Date: 13.5 =3 =3 =3 =3 =9 19 38 =6 15 y= =3 =1 =1 =1 =1 te e= e= oS oS S= nl ly ct ct ct ct oS oS oS oS a t t Q o o on F a F a F a F a .0 1116 1010 1038 1000.Q R Ra Ra f. 8.0 FactorEDCHMaxBitRate=1. 4.5 .5 and 5  RAB Max UL bit rate 384 kbps  ThresholdMaxEDPDCHSR = 0 (Not set)  Test 2: Effect of MaxTotalUplinkSymbolRate  MaxTotalUplinkSymbolRate = 960. Test cases and used parameter settings are listed below.5 . the Iub congestion control is limiting throughput with high bitrate settings.0 592 584 QoS with kbit/s 600.0 84 84 84 84 60 20 40 =6 4 40 00 64 84 . 384 kbps  ThresholdMaxEDPDCHSR = 0 (Not set)  FactorEDCHMaxBitRate = 0 (Not set)  Test 5: Effect of RAB QoS  RAB Max UL bit rate 64. 1920.0 MaxTotalUplink ThresholdMaxEDP QoS only 106 FactorEDCHMaxBitRate SymbolRate DCHSR 48 0.5 .5 m de ef f.Q . 128. 640 kbps  FactorEDCHMaxBitRate = 0 (Not set)  ThresholdMaxEDPDCHSR960kbps = 512 ksps and ThresholdMaxEDPDCHSR1920kbps = 1024 ksps  Test 4: Effect of RAB QoS only  RAB Max UL bit rate 64. =1 =5 S Sy m m e= =d de Q =6 12 25 38 act t=1 act t=N Sy Sy h e = Q oS = = = F c F c T Th e oS oS oS Fa Fa Th Q Q Q Q Figure 85.5 367 375 400.0 843 861 867 852 830 800. 6.0 297 296 200. (Arrows in Figure 85 show cases where Iub congestion control is limiting HSUPA bitrate) UL throughput 1200. 1.Q .

4.3 Round Trip Time (RTT) Latency can be measured as round trip time (RTT). for a theoretical RTT estimation. we can use the following assumptions: Copyright © Nokia Siemens Networks 2008 Company confidential Page 94 (119) .2011 Data Performance Optimisation Guide for Version 2. as we only see end-to-end the total sum of all the times a packet spent in the network in UL and DL direction. It is important to understand that from a single RTT measurement we cannot see where the packets have spent which amount of time. RED= AG Yellow =E-TFCI BLUE= SG Figure 86. BTS reduce aggressively the throughput and therefore AG are used. which is defined as the time an IP packet takes to travel from the terminal through all network elements to the application server.5 HSUPA data rate can be limited by  UE Tx Power – UE is already using its maximum Tx power  Serving Grant – Maximum grant is used already  Data – UE buffer is empty – no new data to send Figure 86 below show situation when UE tx power increase and start to limit throughput. there is more Absolute Grants given to the UE.2 RU10/RU20  FactorEDCHMaxBitRate = 1. UE tx Power limitation vs.2. NPO/NSO Capability Management Date: 13. and back. HSUPA throughput 6. neither on which direction (UL/DL) nor on the individual links. However.

so that the serving cell change would be normally triggered by the Ec/No measurements and not by the event 1B. HSUPA uplink assumes a 2ms TTI.g. 20ms for HSDPA. ping from a Windows XP command line) use per default ICMP messages with a payload of 32 Byte. of 43-53ms for Release 99. and 5ms for HSUPA  RNC delay of 20ms for release 99 and 10ms for HSDPA/HSUPA  Iu plus core network delay of 3ms The ICMP packet uses 20 Byte for IP header and 8 byte for ICMP header plus the payload. making a total IP packet length of 60 Byte. RU20 RTT values in NSN test network 6. Often ping applications (e. HSDPAServCellWindow (def 2 dB) parameter determines the maximum allowed difference between the best cell CPICH Ec/No and the serving HS-DSCH cell CPICH Ec/No.3 Mobility HSPA mobility can be performed with cell reselection in CELL_FACH or serving cell change functionality. UL SIR error and event 1B/1C.2 RU10/RU20  UE delay of 10-25ms  Air interface delay. The WCDMA release 99 data rate 64/64 kbps uplink/downlink assumes a 20ms TTI while 128/384 kbps assumes a 10ms TTI. Figure 87. The most common triggering reason is supposed to be periodical Ec/No measurements. 10ms for HSDPA. The RTT depends heavily on the used Radio Bearer. NPO/NSO Capability Management Date: 13.4. The recommendation is to set DropWindow parameter value in HSDPA FMCS higher than HSDPAServCellWindow. and 10ms for HSUPA. including uplink and downlink buffering. The values were measured in NSN Test Network under empty cell with optimised E2E environment. The Figure 87 below shows typical lowest achievable RTT values for different RBs and different payload size. Serving cell change with soft handover is required for HSUPA.  BTS delay 10-15ms  Iub delay of 20-40ms for release 99. Copyright © Nokia Siemens Networks 2008 Company confidential Page 95 (119) . HS-DSCH serving cell change can be triggered by the best server Ec/No.2011 Data Performance Optimisation Guide for Version 2.

Table 26. The HSDPA serving cell change performance can be measured with RNC_733a (HSDPA Serving Cell Change Success Rate). to have smaller SHO area for HSDPA users. The SCC can be triggered mainly by CPICH EcNo. HSPA mobility counters and KPIs PI ref PI name / Abbreviation PI unit Report: System Program RSRAN000 RNC_733a HSDPA Serving Cell Change Success Rate % RNC_918b HSUPA Serving Cell Change Success Rate % Report: HSPA Serving Cell Change RSRAN033 RNC_906a HSDPA SCC attempts # RNC_733a HSDPA Serving Cell Change Success Rate % M1008C213 SCC_STARTED_CPICH_ECNO Integer number M1008C214 SCC_STARTED_UL_SIR_ERROR Integer number M1008C215 SCC_STARTED_ACTIVE_SET_UPD Integer number M1008C216 SCC_STARTED_OTHER_REASON Integer number M1008C217 SCC FAILED_DUE_TO_UE M1008C218 SCC_FAILED_DUE_TO_BTS Integer number M1008C219 SCC_FAILED_DUE_TO_TRANSM Integer number M1008C220 SCC_FAILED_DUE_TO_AC Integer number M1008C221 SCC_FAILED_DUE_TO_OTHER Integer number M1008C239 EDCH_SCC_STARTED # RNC_918b HSUPA Serving Cell Change Success Ratio % RNC_2135a HSUPA Inter-RNC SCC Success Rate % Report: Service/Session Retainability Analysis RSRAN079 (M1022) M1008C243 INTER_RNC_HHO_ATT_HSPA_SCC RNC_1163a HSUPA Inter-RNC SCC Failure Rate % Copyright © Nokia Siemens Networks 2008 Company confidential Page 96 (119) .2011 Data Performance Optimisation Guide for Version 2. Current recommendation is to use lower value for AdditionWindow (closer to 0 dB) in HSDPA FMCS than in the RT/NRT FMCS.  Failures doe to other reasons  The number of HS-DSCH serving cell change failures due to other reasons.2 RU10/RU20 AdditionWindow in HSDPA FMCS is controlling the active set size of the associated UL channels. UL SIR Error or active set update (removal of serving HS-PDSCH cell from AS). It doesn’t have direct impact on the serving cell change functionality and triggering. Low success rate can be caused by  Failures due to BTS  When the RNC receives NBAP: RADIO LINK RECONFIGURATION FAILURE during serving HS-DSCH cell change  Failures due to transmission  When a serving HS-DSCH cell change fails due to an Iub transport setup failure. Table 26 summarises the HSPA mobility related KPIs and counters. for example because the maximum number of HSDPA users were already allocated in the target cells.  Failures due to admission control  The number of HS-DSCH serving cell change failures due to admission control.4. NPO/NSO Capability Management Date: 13.

4.2011 Data Performance Optimisation Guide for Version 2.2 RU10/RU20 RNC_1164a HSUPA Inter-RNC SCC Drop Rate % HSUPA serving Cell Change are only done when HSDPA serving Cell change is needed. as seen in the picture below.0 EP1 RU20 MP2 first cluster PP1. Copyright © Nokia Siemens Networks 2008 Company confidential Page 97 (119) . NPO/NSO Capability Management Date: 13. It has been sent that in RU10 the SCC performance is better and even better in RU20. Main reasons to start SCC is the decreased CPICH EcNo and active set update (event 1b/1c). Example of SCC Performance (RU10/RU20) There seems not to be a relation with poor SCC success and HSDPA retainability. SCC success rate for HSDPA and HSUPA is not very accurate in cell level as denominator is incremented in the source cell (old serving cell) and numerator is incremented in the target cell (new serving cell). Below is typical example of HSDPA mobility performance taken from RSRAN033 report.12 Figure 88. RU10 RU20 MP1 RU20EP1 WN6.

radio link failure. 6. The PI RNC_920a (see Table 27) describes the retainability based on packet M1022 measurements.4. HSDPA SCC performance compared to HSDPA retainability.2 RU10/RU20 Figure 89. The HSPA packet call failures are mainly due to RL failures. thus does not necessary present users view of connection quality. Figure 32 presents an example of HSPA packet call retainability analysis. Copyright © Nokia Siemens Networks 2008 Company confidential Page 98 (119) . NPO/NSO Capability Management Date: 13. The PI RNC_609a can be also used for retainability measurement. RLC protocol reset or uplink RLC unrecoverable error (Cell Update sent by UE).4 Retainability The retainability of a HSPA packet call describes the probability that the packet call is not dropped when the HSPA channel type is used. This takes into account only events when the DCH connection is abnormally released.2011 Data Performance Optimisation Guide for Version 2. Inter RNC SCC performance seems to be about 2-4 % lower than Intra RNC SCC due to SRNC relocation issues. but this PI is triggered in cell where the RL fails even if there is working RL in other cell of active set and the packet call is switched to that.

Table 27. Iub. NPO/NSO Capability Management Date: 13. SCC parameter HSPA packet call Yes Check for RNC failures and use RNC logging if failures .2 RU10/RU20 RNC_920a< No No Action Needed X% Yes HSPA packet call Yes Check SCC Failure Rate – Radio. CE Radiolink failures resource congestion No Check CQI distribution and Ecno distribution for coverage issue Check HSDPA mobility parameter – Add/Drop window.other required Figure 90. HSPA retainability failure analysis Table 27 lists the relevant reports and PIs for HSDPA RB accessibility monitoring and troubleshooting.4. HSPA retainability counters and KPIs (Report: Service/Session Retainability Analysis RSRAN079) PI PI ref PI name / Abbreviation unit Report: System Program RSRAN000 RNC_930b Packet Session Attempts # RNC_922b Packet Session Success Ratio for NRT % RNC_614c HS-DSCH selections # RNC_609a HSDPA Resource Retainability for NRT Traffic % RNC_926b HSDPA attempts # RNC_920b HSDPA Success Ratio from user perspective for NRT % RNC_923c E-DCH selections # RNC_919a HSUPA resource Retainability for NRT Traffic % RNC_928b HSUPA attempts # RNC_915c HSUPA Success Ratio from user perspective for NRT % Report: Service/Session Retainability Analysis RSRAN079 (M1022) RNC_1092b Packet Session Rel from HS-EDCH # RNC_1093b Packet Session Rel from HS-DCH # RNC_1094b Packet Session Rel from DCH-DCH # RNC_1095a HS-DSCH/E-DCH Packet Call Rel due to RL Failures % RNC_1096a HS-DSCH/DCH Packet Call Rel due to RL Failures % RNC_1097a DCH/DCH Packet Call Rel due to RL Failures % Copyright © Nokia Siemens Networks 2008 Company confidential Page 99 (119) .2011 Data Performance Optimisation Guide for Version 2.

4. Copyright © Nokia Siemens Networks 2008 Company confidential Page 100 (119) .12 Direct transition DCH-PCH causing problems. RU10 RU20 MP1 RU20EP1 WN6. Figure 91 Example of HSDPA release failure (RU10/RU20) Figure 92 shows that also for HSUPA release the main cause is radio link failure.other than DCH switch % RNC_1107d E-DCH Allocation Rel # RNC_1108d E-DCH Rel due to RL Failures % RNC_1115d E-DCH Rel due to HS-DSCH serving cell change % RNC_1109d E-DCH Rel due to Other Failures % Figure 91 shows one example about HS-DSCH release failure.2011 Data Performance Optimisation Guide for Version 2.2 RU10/RU20 RNC_1098a HS-DSCH/E-DCH Packet Call Rel due to Other Failures % RNC_1099a HS-DSCH/DCH Packet Call Rel due to Other Failures % RNC_1100b DCH/DCH Packet Call Rel due to Other Failures % RNC_1101b HS-DSCH Allocation Rel # RNC_1102b HS-DSCH Release Rate due to RL Failure % RNC_677b HSDPA Radiolink failures # RNC_1185b HS-DSCH Allocation Release Rate due to Non-RL failures RNC_675b HSDPA Non . NPO/NSO Capability Management Date: 13..Radiolink failures # RNC_679c HS-DSCH release due to mobility % RNC_681b S-DSCH release due to pre-emption % RNC_724b HS-DSCH to DCH switch . OK after deactivation.0 EP1 RU20 MP2 first cluster PP1.

This resource sharing can cause some performance degradation on both R99 and HSPA users Copyright © Nokia Siemens Networks 2008 Company confidential Page 101 (119) . Figure 93 presents and example of the effect of DCH power reservation on the HSDPA cell throughput.4.0 EP1 RU20 MP2 first cluster PP1. NPO/NSO Capability Management Date: 13. they will actively share the radio and logical resources in the cell. OK after deactivation.12 Direct transition DCH-PCH causing problems.2 RU10/RU20 RU10 RU20 MP1 RU20EP1 WN6. Figure 94 presents the effect of HS-PDSCH code allocation on the code tree occupancy and number of available SF32 codes used for 64kbps connections.2011 Data Performance Optimisation Guide for Version 2. Figure 92 Example of E-DCH release reasons (RU10/RU20) 7 HSPA & R99 bearer interworking When of R99 and HSPA traffic is allocated in the same cell.

2011 Data Performance Optimisation Guide for Version 2.1 Power.1. Non-real time bearer power (PtxNRT) can be monitored separately. Copyright © Nokia Siemens Networks 2008 Company confidential Page 102 (119) . Effect of DCH power on HSDPA throughput. HS-PDSCH code reservation.2 RU10/RU20 Figure 93. it is calculated by the RNC as the sum of dedicated power measurements of NRT bearers received from BTS. Figure 94. Code and CE (HSUPA) sharing 7.1 DL power sharing The power sharing between HSDPA and DCH traffic can be monitored based on the PtxTotal and PtxNonHSDPA measurements reported by the BTS. NPO/NSO Capability Management Date: 13. 7.4.

5 W. The cell level DL power measurements are stored to number of counters and KPIs.2 RU10/RU20 Figure 95 presents an example (BTS measurements from Online-monitoring) of power sharing between HSDPA and NRT DCH traffic. Figure 95. TB size. Table 28 lists the main counters/KPIs and related measurements from BTS. Spectral efficient link adaption reduces HS-DSCH transmission power of the low data rate users and users in good radio conditions based on function of compensated CQI. number of HS-PDSCH codes and modulation. but now HSDPA only use power it needs and not necessarily all power available for HSDPA.4. PIs related power sharing between HSPA and R99 traffic PI ref PI name / Abbreviation PI unit Report: Cell Capacity RSRAN067 RNC_102b Average R99 Downlink Load dBm RNC_690a Average active non-HSDPA power ratio % RNC_691a Average non-HSDPA power ratio % M1000C236 MIN_HSPA_DL_POWER dBm M1000C237 MAX_HSPA_DL_POWER dBm M1000C238 AVE_HSPA_DL_POWER dBm M1000C232 MIN_PTX_TARGET_PS dBm M1000C233 MAX_PTX_TARGET_PS dBm M1000C234 AVE_PTX_TARGET_PS dBm RNC_101b Average Uplink R99 Load dBm RNC_177b Noise floor of the System dBm*-100. The HSDPA power is averaged over the reporting period and it depends also on the HSDPA activity (TTI activity%). Table 28. DL power sharing between HSDPA and NRT PS traffic.0 Copyright © Nokia Siemens Networks 2008 Company confidential Page 103 (119) . NPO/NSO Capability Management Date: 13.2011 Data Performance Optimisation Guide for Version 2. Basic principle of power sharing between r99 and HSDPA still works similarly as in RAS06. The dynamic resource allocation is active and all available power is allocated to HSDPA (about 4W is used by CCCHs) with maximum of 15. HSDPA transmit power is calculated as PtxTotal – PtxNonHSPA. In RU10.

Low level of available HSDPA power will have an effect on the peak data rates in the cell. HSDPA DL power availability AVG_NON_HSDP A_POWER > 50% No Yes Consider activation of 2nd carrier for HSPA HSDPA power utilization > 50% No Check other resources Figure 96. The available power can be measured based on the M1000C138_AVG_NON_HSDPA_PWR counter or Average DL Load RNC_102b KPI. Increase R99 traffic decrease the HSDPA power as they share the same resource. NPO/NSO Capability Management Date: 13.2011 Data Performance Optimisation Guide for Version 2.2 RU10/RU20 M5000C154 HSUPA_UL_PWR_MIN dBm M5000C155 HSUPA_UL_PWR_MAX dBm M5000C156 HSUPA_UL_PWR_AVG dBm Report: NRT Radio Bearer PBS and OLC RSRAN013 M1000C142 RB_DOWNGR_DUE_OLC_TFC_SUBS # M1000C154 RB_DOWNGR_DUE_OLC_RL_RECONF # M1000C166 RB_RELEASE_DUE_OLC_RL_RECONF # M1000C147 RB_DOWNGR_DUE_PBS_INTERF # M1000C152 RB_DOWNGR_DUE_PRE_EMP_INTERF # M1000C159 RB_RELEASE_DUE_PBS_INTERF # M1000C164 RB_RELEASE_DUE_PRE_EMP_INTF # The main interest is on the monitoring of available DL power for HSDPA and also how much of this power is actually used. average HSDPA power can low due the low utilisation (low HSDPA activity) as can be seen in Figure 97 below. The HSDPA power utilisation can be measured as ratio of average HSDPA power AVE_HSPA_DL_POWER and average available HSDPA power. HSDPA power counters show average or maximum during measurement period. It is feasible to monitor cells with high HSDPA activity (50-60%) but low HSDPA power.4. However. HSDPA cell throughput limitation can be detected when the power utilisation increases. DL power sharing analysis. Copyright © Nokia Siemens Networks 2008 Company confidential Page 104 (119) .

HSDPA power measurement with averaged input values. Average HSDPA power vs.2011 Data Performance Optimisation Guide for Version 2. NPO/NSO Capability Management Date: 13. With Dynamic power allocation / resource allocation it is possible to use all left over power for HSDPA. Average UL and DL load as a function of HSDPA power Copyright © Nokia Siemens Networks 2008 Company confidential Page 105 (119) .4. Figure 98. HSDPA Utilisation Below is one example of HSDPA power compared to Average DL/UL load.2 RU10/RU20 Figure 97.

Right now they seem not giving reasonable values (-112 dBm during most of the cases). NPO/NSO Capability Management Date: 13. Copyright © Nokia Siemens Networks 2008 Company confidential Page 106 (119) . This can be seen in the Figure 99. average and maximum HSUPA UL physical channel power (M5000C154-156) could be used to see how UL power is changing in due to HSUPA. PI ref PI name / Abbreviation PI unit Report: Cell Capacity RSRAN067 RNC_113a Average occupancy % RNC_520b Max occupancy % RNC_519b Min occupancy % M1000C83 NBR_SUCC_CODE_TREE_ALLO # RNC_949a(b) Spreading Code Blocking rate in DL % RNC_512b SF4 blocking rate % RNC_513b SF8 blocking rate % RNC_514b SF16 blocking rate % RNC_515b SF32 blocking rate % RNC_516b SF64 blocking rate % RNC_517b SF128 blocking rate % RNC_518b SF256 blocking rate % M1000C266 CH_CODE_DOWNG_RT # M1000C267 CH_CODE_DOWNG_NRT_DCH # Report: NRT Radio Bearer PBS and OLC RSRAN013 M1000C148 RB_DOWNGR_DUE_PBS_SPREAD # M1000C153 RB_DOWNGR_DUE_PRE_EMP_SPREAD # M1000C160 RB_RELEASE_DUE_PBS_SPREAD # M1000C165 RB_RELEASE_DUE_PRE_EMP_SPREA # Report: HSPA Code and Modulation Usage RSRAN034 M1000C248- 258 DURA_HSDPA_x_CODE (from 5-15) The HSDPA code reservation is increased when the first HSDPA connection is setup to the cell or periodically while the HSDPA is active in the cell.2 RU10/RU20 Minimum. 7.1. DCH traffic and CCCHs. When HSDPA is activated in the cell it reserves a minimum reservation of 5 codes out of 16 SF16 codes. Table 29.4. The code reservation for HSDPA and R99 traffic is controlled by following principles and monitored by the KPIs and counters. because RT calls will pre-empt or downgrade HSDPA codes if SF16 codes are fully used.2 Channelisation code tree sharing The DL Channelisation code tree is shared by the HSDPA traffic. PIs related to channelisation code sharing between HSPA and R99 traffic.2011 Data Performance Optimisation Guide for Version 2. Table 29 lists the main PIs related to channelisation code tree reservation and sharing. This parameter could be set even to zero. This parameter tells how much margin is reserved in the code tree. HSDPA code reservation can be increased until the number of free SF16 codes is less that HSPDSCHMarginSF128 parameter. if the cell is configured with higher number of codes than 5 (up to 15) and the UE support that also.

which indicated low amount of R99 traffic. Copyright © Nokia Siemens Networks 2008 Company confidential Page 107 (119) . RNC_519b (Min Occupancy) and HSDPA code usage counters M1000C248-258. In the below example the code occupancy is low when the HSDPA code allocation is at minimum (5 codes static allocation). HSDPA Code downgrade due to AMR with HSPDSCHMarginSF128=0 The total code occupancy of R99+HSDPA traffic can be monitored with RNC_113a (Average occupancy). RNC_520b (Max occupancy. According to code tree occupancy calculations. with 5 HS-PDSCH codes the reservation is minimum 38%. NPO/NSO Capability Management Date: 13. These figures correspond quite closely the presented example. M1000C75). The graph below present an example of code tree occupancy and HSDPA code usage.2 RU10/RU20 Figure 99.4.2011 Data Performance Optimisation Guide for Version 2. the allocation of 10 HS- PDSCH codes raises code occupancy to about 70% without any R99 traffic.

The default set is to use codes like 5. 10. But it is also possible to use all codes from network point of view by changing just the code usage by HS-PDSCH code set in RNC. 12.2 RU10/RU20 Figure 100. NPO/NSO Capability Management Date: 13. Cat8 UE supports 10 codes and Cat UE 6 supports 5 codes. RNC_2093a can be used to monitor average number of reserved SF16 codes for HSDPA. 8. This KPI is based on duration of HSDPA x code counters (M1000C248-C258).4. Cat9 UE supports 15 codes. The picture below shows that regardless of UE category and code capability. Codes 5-15 can be allocated as wanted from network point of view. the network allocates all available codes for HSDPA. Also if network allocates possible codes (like default values) UE can still use other number of codes depending on the situation. Copyright © Nokia Siemens Networks 2008 Company confidential Page 108 (119) . Example of HSDPA code allocation and spreading code occupancy [8].2011 Data Performance Optimisation Guide for Version 2. 14 and 15 with 15 codes feature.

It shows that when the average code occupancy increases above 50%. The overall code blocking can be monitored with RNC_949b (Spreading Code Blocking rate in DL) and per SF with Blocking rate of SF due to No codes available: PIs RNC_512b-RNC_518b.2 RU10/RU20 Figure 101. Figure 102 presents an example of code occupancy and code tree blocking rate. A code allocation failure causes typically the packet scheduler to allocate of lower bit rate (higher SF) if possible. counters M1000C76-82. The total R99 code requests are given in SF requests M1000C259-265. Example of HSDPA & NRT code allocation duration with different UEs The PS NRT allocation (upgrade or initial bit rate) can fail if there is no free code for NRT DCH.4.2011 Data Performance Optimisation Guide for Version 2. Copyright © Nokia Siemens Networks 2008 Company confidential Page 109 (119) . NPO/NSO Capability Management Date: 13. the maximum code occupancy reaches 100% and code tree blocking rate increases. M1000C89.

2011 Data Performance Optimisation Guide for Version 2.2 RU10/RU20 Figure 102. NPO/NSO Capability Management Date: 13. Figure 103 presents and example of increased code tree blocking rate and the SF(s) that cause the blocking.4. Code tree occupancy. Copyright © Nokia Siemens Networks 2008 Company confidential Page 110 (119) . Low amount of code blocking can be tolerated as it is typically due to NRT DCH allocation attempts for low SF bearers (SF8 and SF16).

However it has been tested that when the parameter DPCHOverHSPDSCHThreshold is set to zero. Copyright © Nokia Siemens Networks 2008 Company confidential Page 111 (119) . Code tree blocking. RB downgrade/release due to code congestion can be seen from the RS RSRAN013 and the counters are:  M1000C148_RB_DOWNGRADE_BY_PBS_DUE_TO_SPREADING_CODE_CONGESTION  M1000C153_RB_DOWNGRADE_BY_PRE- EMPTION_DUE_TO_SPREADING_CODE_CONGESTION  M1000C160_RB_RELEASE_BY_PBS_DUE_TO_SPREADING_CODE_CONGESTION  M1000C165_RB_RELEASE_BY_PRE- EMPTION_DUE_TO_SPREADING_CODE_CONGESTION The request for NRT can downgrade the HSDPA allocation only if the parameter DPCHOverHSPDSCHThreshold allows it. The amount of downgrades can be monitored with HSDPA CH CODE DOWNGRADE DUE TO RT M1000C266 and HSDPA CH CODE DOWNGRADE DUE TO NRT DCH M1000C267. Code downgrade happens already during RT signalling phase. In case this parameter is set to zero. it is still possible to allocate NRT calls. so more code downgrade can be seen in that case.4. An incoming RT call will always downgrade (pre-empt) the HSDPA code reservation. This is seen in the next picture. NPO/NSO Capability Management Date: 13. note the the last 2 samples are with the parameter value of 5.2 RU10/RU20 Figure 103. Also PS NRT allocation (upgrade or initial bit rate) can fail if there is code congestion. A code allocation failure causes typically the packet scheduler to allocate of lower bit rate (higher SF) if possible. The code tree congestion can cause also that the NRT RB are downgraded or released by PBS or pre-emption due to code tree congestion.2011 Data Performance Optimisation Guide for Version 2. there should not be room to downgrade HSDPA codes for NRT. with code downgrade due to congestion.

4. It will be recommended not to use zero value for this parameter unless HSDPA will be the only service for Data service. The resource reservation of R99 traffic depends on the traffic level and can be significant in shared carrier. It that case for example it can be seen that req_PS_rej_DL counter is updated as there is capacity upgrade requests from initial bitrate to maximum. Also it was found that when network is allocating all available codes for HSDPA and there is no UE capability to fully utilize those.1. Figure 105. NPO/NSO Capability Management Date: 13. Setup fails with DPCHOverHSPDSCHThreshold=0. Code downgrade due to NRT with DPCHOverHSPDSCHThreshold=0. Copyright © Nokia Siemens Networks 2008 Company confidential Page 112 (119) . Both cases means that there is no DL codes available. This can also seen as req_PS_rej_UL and PS setup fail AC. This reservation depends on the HSDPA scheduler type and number of schedulers active in the BTS. 7.3 WBTS resource sharing HSDPA has a static reservation from WBTS resources. it is not possible to use remaining codes for PS NRT when the parameter DPCHOverHSPDSCHThreshold is set to zero.2011 Data Performance Optimisation Guide for Version 2.2 RU10/RU20 Figure 104. which is updated only when there is initial capacity request from DCH 0/0 or from FACH.

4. this can not be allocated to DCH. There is also differences between BTS type and HWs.2011 Data Performance Optimisation Guide for Version 2. example table from RU20 below: Different HSUPA resource step table is used for HSUPA 2ms and 10 ms TTI features.4/13. the resources are given to the E-DCH.2 RU10/RU20 The HSDPA return channel is critical from BTS HW availability point of view especially in areas with high HSDPA traffic. The return channel can utilise NRT DCH or HSUPA channel type. WBTS CE reservation of DCH bearers. Bearer data rate CE UL/min SF CE DL/min SF SRB 3. Table 30 presents the CE reservation of DCH bearers. and when the resources are left from the DCH. The HSUPA will have a minimum resource allocation of 8 CE in RAS06 and 0 CE in RU10. NRT DCH return channel reserves BTS resources from the UL channel element pool. The maximum total number of HSUPA users and total throughput depends on the amount of available CE resources. The HSDPA return channel bit rates and CE reservations are highlighted. (RU20) Copyright © Nokia Siemens Networks 2008 Company confidential Page 113 (119) . Table 30. In RU10. The DCH has the highest priority.4 kbps 1/ SF256 1/ SF256 AMR (voice) 1) 1/ SF64 1/ SF128 WB-AMR 2) 1 / SF64 1 / SF128 CS 64 kbps 4 / SF16 4 / SF32 PS 16 kbps 1 / SF64 1 / SF128 PS 32 kbps 2 / SF32 2 / SF64 PS 64 kbps 4 / SF16 4 / SF32 PS 128 kbps 4 / SF8 4 / SF16 PS 256 kbps 8 / SF4 8 / SF8 PS 384 kbps 16 / SF4 16 / SF8 HSUPA return channel reservation the DCH and E-DCH resources share the same DSP resource pool. Less CE also needed for HSDPA users in Uplink (return channel) if 384 kbps is used. NPO/NSO Capability Management Date: 13. Table 31 UL/DL CE reservation example for HSUPA when Flexi Rel2 SM is used with 10ms TTI. less CE needed with high bitrate (384 kbps) with Flexi Rel2 HW system module.

6 7 8. the RNC sets up the E- DCH but the BTS HW shortage may cause the throughput to be lower than expected  1000C270 BTS HSUPA HW NO CAPACITY DURATION: In this state.4.2 5. This measurement supports the measurement of total available CE capacity (licensed).4 9.8 18.9 36 36 36 54 54 54 72 72 90 108 108 126 n/a n/a n/a 10-12 36 36 54 72 72 72 72 90 108 108 126 144 144 162 162 13-15 36 54 54 72 90 90 90 90 108 108 126 144 144 162 162 16-18 54 54 54 72 90 108 108 108 108 126 144 144 162 180 180 19-21 54 72 72 72 90 108 126 126 126 144 144 162 180 180 n/a 22-24 72 72 72 72 90 108 126 144 144 162 162 180 180 n/a n/a 25-27 72 72 90 90 90 108 126 144 162 162 180 180 n/a n/a n/a 28-30 72 72 90 90 90 108 126 144 162 180 180 n/a n/a n/a n/a 31-33 90 90 108 108 108 108 126 144 162 180 n/a n/a n/a n/a n/a 34-36 90 108 108 108 108 108 126 144 162 180 n/a n/a n/a n/a n/a 37-39 108 108 108 126 126 126 126 144 162 180 n/a n/a n/a n/a n/a 40-42 108 108 108 126 126 126 126 144 162 180 n/a n/a n/a n/a n/a 43-45 108 126 126 144 144 144 144 144 162 180 n/a n/a n/a n/a n/a 46-51 126 126 144 144 162 162 162 162 180 180 n/a n/a n/a n/a n/a 51-60 144 144 144 144 162 180 180 180 n/a n/a n/a n/a n/a n/a n/a 61-72 162 162 162 162 180 n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a 73-80 180 180 180 180 180 n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a The BTS HW resource status can be monitored with WBTS HW resource counters in the M5001 counter table.2 12.4 16.3 18 18 36 36 n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a 4. the RNC does not set up the E-DCH The PIs discussed above together with other BTS resource related PIs are listed in table below.2 19.8 4. PIs related power sharing between HSPA and R99 traffic PI ref PI name / Abbreviation PI unit Report: Node B Capacity RSRAN066 RNC_955b PS Call Setup FR due to BTS % RNC_924a RRC stp fail rate BTS (RU10 RS) % RNC_925a RAB stp fail rate BTS (RU10 RS) % RNC_673d HSDPA Access FR due to BTS % RNC_956a E-DCH Setup FR due to BTS % RNC_957b E-DCH Not Selected due the BTS HW % Copyright © Nokia Siemens Networks 2008 Company confidential Page 114 (119) .  1000C269 BTS HSUPA HW LIMITED DURATION: In this state. CE reservation and HSUPA specific CE reservation The total CE reservation can be monitored with maximum. A HSUPA throughput limitation due to lack of CEs is indicated by the following counters:  1000C268 BTS HSUPA NOT HW LIMITED DURATION: In this state.8 11. RNC_730a (Average Ratio of Utilised CE for DL in BTS) and RNC_731a (Average Ratio of Utilised CE for UL in BTS).6 21 HSUPA UEs per Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps Mbps LCG 1.2 RU10/RU20 Number of 1.6 18 36 36 36 54 54 72 72 n/a n/a n/a n/a n/a n/a n/a 7. minimum and average used CE counters and RNC KPIs like RNC_959a (Maximum Used CE's ratio).6 14 15. Table 32.2011 Data Performance Optimisation Guide for Version 2.4 2. The HSUPA CE reservation can be monitored with maximum and minimum used CE counters and RNC KPIs RNC_947a and RNC_948a (Average ratio of utilised CE for DL/UL for HSUPA in BTS). the BTS HW does not limit the HSUPA throughput. NPO/NSO Capability Management Date: 13.

2011 Data Performance Optimisation Guide for Version 2. NPO/NSO Capability Management Date: 13.4.2 RU10/RU20 RNC_958a RL Setup FR due the MISC % M1000C268 BTS_HSUPA_HW_NOT_LIMITED_DUR S M1000C269 BTS_HSUPA_HW_LIMITED_DUR S M1000C270 BTS_HSUPA_NO_HW_CAPA_DUR S M5001C0 MAX_AVAIL_CE Integer number M5001C1 MIN_AVAIL_CE Integer number M5001C2 AVG_AVAIL_CE Integer number RNC_830a CE situation change indication # M5001C3 MAX_USED_CE_DL Integer number M5001C4 MAX_USED_CE_UL Integer number RNC_959a Maximum Used CE's ratio % M5001C5 MIN_USED_CE_DL Integer number M5001C6 MIN_USED_CE_UL Integer number RNC_822a Average free CEs # RNC_730a Average ratio of utilized CE for DL in BTS % RNC_731a Average ratio of utilized CE for UL in BTS % M5001C9 MAX_HSUPA_CE_UL Integer number M5001C12 MAX_HSUPA_CE_DL Integer number M5001C10 MIN_HSUPA_CE_UL Integer number M5001C13 MIN_HSUPA_CE_DL Integer number RNC_947a Average ratio of utilized CE for DL for HSUPA in BTS % RNC_948a Average ratio of utilized CE for UL for HSUPA in BTS % Report: NRT Radio Bearer PBS and OLC RSRAN013 M1000C146 RB_DOWNGR_DUE_PBS_BTS # M1000C151 RB_DOWNGR_DUE_PRE_EMP_BTS # M1000C158 RB_RELEASE_DUE_PBS_BTS # M1000C163 RB_RELEASE_DUE_PRE_EMP_BTS # Copyright © Nokia Siemens Networks 2008 Company confidential Page 115 (119) .

2 RU10/RU20 Figure 106 below presents an example of BTS resource reservation with HSDPA. It also shows that the maximum UL reservation is normally higher. 8 for HSUPA and 32 for HSDPA). Figure 106. Example of WBTS resource sharing with HSDPA (RAS06) Copyright © Nokia Siemens Networks 2008 Company confidential Page 116 (119) .4. The minimum UL and DL resource reservation is 56 (16 for CCHs.2011 Data Performance Optimisation Guide for Version 2. NPO/NSO Capability Management Date: 13.

These failures are monitored with KPIs: RNC_674a (HSDPA Access FR due the BTS). The decreased Ec/No can also increase the amount of inter-system handovers or cell re-selections to GSM. as the Ec/No is typically used as the main criteria triggering the procedures. The maximum HSUPA reservation is 64. NPO/NSO Capability Management Date: 13. With high level of HSDPA return channel on DCH causes typically high UL reservation.1.3.2 Effect of HSPA on R99 performance The main concern related to effect of HSPA traffic on R99 traffic performance is typically related to additional interference caused by HSDPA in DL.4.4 Mbps throughput in Ultrasite BTS. but still remain in good level. The HSDPA accessibility and retainability are slightly dropped. In this example the AMR call Retainability is even improved despite the increased HSDPA traffic. This increased level of interference can cause call setup problems and call drops. This is easy to understand in a case when the HSDPA transmission increases the BTS transmit power from typical 8 W to maximum of 20 W in matter of milliseconds. Figure 107. More about the return channel performance in Sections and 6.2 RU10/RU20 Figure below shows an example of WBTS resource reservation with HSUPA.2011 Data Performance Optimisation Guide for Version 2. Example of WBTS resource sharing with HSUPA (RAS06) Lack of BTS resources is the most common reason for HSDPA and HSUPA accessibility failures. Figure 108 presents an example of network performance for two years from the HSDPA launch. RNC_956a (E-DCH Setup FR due the BTS). which is for example due to user with >1. 7. RNC_957a (E-DCH Not Selected due the BTS HW). Copyright © Nokia Siemens Networks 2008 Company confidential Page 117 (119) .

2 RU10/RU20 Figure 108.4. Copyright © Nokia Siemens Networks 2008 Company confidential Page 118 (119) . NPO/NSO Capability Management Date: 13. Effect of increased HSDPA traffic on CS RAB and HSPA bearer performance.2011 Data Performance Optimisation Guide for Version 2.

Paul Larsen 12/2008 [12] RAN E2E system performance optimization guide [13] KPI list and targets recommendation doc https://sharenet- ims.com/Guest/Overview/408667477 [15] RSRAN RU10 Full Report Set.4.nokiasiemensnetworks.inside.com/Open/378112337 [2] 3G Radio Network Planning Guidelines for RAS06 and RU10 https://sharenet-ims.inside.php?set=426&co=1&m=1&se=1 Copyright © Nokia Siemens Networks 2008 Company confidential Page 119 (119) .inside.com/Open/398619055 [11] LAM RAS06 Experiences.nokiasiemensnetworks.inside.nokiasiemensnetworks. 1st January 2007 [5] Multilayer planning guideline https://sharenet- ims.nokiasiemensnetworks.nokiasiemensnetworks.nokiasiemensnetworks.nokiasiemensnetworks.com/livelink/livelink/guest/Download/360111458 [7] Packet Scheduler optimisation guide https://sharenet-ims.nokiasiemensnetworks.com/Open/364909596 [8] Capacity Management Workshop –phase 2.inside. [9] Capacity Management Guide https://sharenet- ims.inside. Inacio Rui 2009 http://nop- i.inside.com/Open/363676257 [3] RAS06 Product Documentation [4] 'KPI for HSDPA Planning'.nokiasiemensnetworks.nokiasiemensnetworks.Baseband dimensioning https://sharenet- ims.inside.inside.com/Open/364616733 [14] RAN QoS Provisioning Guide https://sharenet- ims.com/Open/363972983 [10] HSDPA & HSUPA throughput and parameter testing in NTN https://sharenet- ims.com/reportmanager/htmlset.com/Open/383626385 [6] Flexi WCDMA BTS sales guide .2 RU10/RU20 References [1] HSPA Radio Network Planning Guide https://sharenet- ims. NPO/NSO Capability Management Date: 13.2011 Data Performance Optimisation Guide for Version 2. Jussi Reunanen et all.