3g radio network planning guideline delta ru20 pdf

1/2 Document Type Author Unit/Dept.

Document Title Date, Version For internal use only

Nokia Siemens Networks

3G Radio Network Planning Guideline Delta for RU20

NPO/NSO Capability Management Date: 30.07.2010 3G Radio Network Planning Guideline Delta for RU20

Version 1.1

REVISION HISTORY

Date Rev. Summary of Change

7.12.2009 v.1.0 Document created 30.07.2010 v.1.1 Fast Dormancy and Direct Resource

Allocation featured added. F-DPCH dependency for DC-HSDPA removed

Editors: Jarkko Itkonen, Chris Johnson, Dalius Kaskelevicius Date: 7.12.2009 Version: v.1.1

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 (64)


Version 1.1

Table of contents

1 Introduction ................................................................................................ 7 1.1 Summary of RU20 Features .................................................................................................... 7

2 General RRM and DCH features ............................................................... 9 2.1 24kbps Paging Channel........................................................................................................... 9 2.1.1 24 kbps Paging Channel Parameters ................................................................................... 9 2.2 LTE Interworking ..................................................................................................................... 9 2.2.1 LTE Inter-working Parameters .............................................................................................. 9 2.3 Fast L1 synchronisation ......................................................................................................... 11 2.3.1 Fast Layer 1 Synchronisation Parameters .......................................................................... 12 2.4 Power Saving Mode for BTS ................................................................................................. 13 2.4.1 Power Saving Mode for BTS Parameters ........................................................................... 13 2.5 Common Channel Setup ....................................................................................................... 16 2.5.1 Common Channel Setup Parameters ................................................................................. 16 2.6 Fast Dormancy ...................................................................................................................... 18 2.6.1 Fast Dormancy Parameters ................................................................................................ 19 2.7 Changes to other features ..................................................................................................... 20

3 HSDPA features ...................................................................................... 22 3.1 HSDPA bit rates .................................................................................................................... 22 3.2 CS Voice over HSPA ............................................................................................................. 22 3.2.1 CS Voice over HSPA Parameters ....................................................................................... 23 3.3 MIMO .................................................................................................................................... 27 3.3.1 MIMO Parameters .............................................................................................................. 28 3.4 HSDPA 64 QAM .................................................................................................................... 29 3.4.1 HSDPA 64QAM Parameters ............................................................................................... 30 3.5 DC-HSDPA 42Mbps .............................................................................................................. 31 3.5.1 DC-HSPA Parameters ........................................................................................................ 32 3.6 Flexible RLC (DL) .................................................................................................................. 33 3.6.1 Downlink Flexible RLC Parameters .................................................................................... 34

4 HSUPA features ...................................................................................... 36 4.1 HSUPA bit rates .................................................................................................................... 36 4.2 HSUPA 5.8 Mbps .................................................................................................................. 36 4.2.1 HSUPA 5.8 Mbps Parameters ............................................................................................ 37 4.3 HSUPA 2ms TTI .................................................................................................................... 38 4.3.1 HSUPA 2 ms TTI Parameters ............................................................................................. 38

5 HSPA features ......................................................................................... 40 5.1 Fractional DPCH ................................................................................................................... 40 5.1.1 Fractional DPCH Parameters ............................................................................................. 40 5.2 Continuous Packet Connectivity ............................................................................................ 43 5.3 Continuous Packet Connectivity Parameters ......................................................................... 44 5.4 HSPA 72 Users per Cell ........................................................................................................ 48 5.4.1 HSPA 72 Users Per Cell Parameters .................................................................................. 48 5.5 Direct Resource Allocation for HSPA ..................................................................................... 49 5.5.1 Direct Resource Allocation for HSPA Parameters ............................................................... 50



Version 1.1

6 Air interface performance ......................................................................... 51 6.1 Performance and features ..................................................................................................... 51 6.1.1 CS Voice over HSPA .......................................................................................................... 52 6.1.2 HSDPA 64 QAM ................................................................................................................. 53 6.1.3 DC-HSDPA 42Mbps ........................................................................................................... 54 6.1.4 HSUPA 5.8 Mbps ............................................................................................................... 56

7 RU20 BTS Features ................................................................................. 57 7.1 Enhanced UltraSite Base Band (EUBB) ................................................................................ 57 7.2 Multiradio BTS Concept ......................................................................................................... 58 7.3 RF Sharing WCDMA GSM ................................................................................................. 58 7.4 Flexi RF Modules................................................................................................................... 58 7.5 Multiradio Combiner 850MHz ................................................................................................ 60 7.6 Multiradio Combiner 900MHz ................................................................................................ 60 7.7 Smart Diplexer ....................................................................................................................... 61 7.8 RRH Chaining ....................................................................................................................... 62 7.9 Flexi WCDMA Software Download Capability for Antenna Line Devices ............................... 63

References ................................................................................................... 64



Version 1.1

List of Figures

Figure 1 L1 sync time without and with Fast L1 Synchronisation .................................................................. 12 Figure 2 CS voice over HSPA compared to CS voice over DCH ..................................................................... 22 Figure 3 MIMO architecture .............................................................................................................................. 27 Figure 4 Signal constellations with different modulation types ......................................................................... 30 Figure 5 Comparison of DC-HSDPA and single cell configuration ................................................................... 31 Figure 6 HSUPA Code usage for HSUPA 5.8 Mbps bit rate ............................................................................ 37 Figure 7 HSPA connection channel usage with fractional DPCH..................................................................... 40 Figure 8 DPCCH gating .................................................................................................................................... 44 Figure 9 Concept of Direct Resource Allocation for HSPA ............................................................................... 50 Figure 10 Features impact to coverage ............................................................................................................ 51 Figure 11 Features impact to capacity and baseband dimensioning ............................................................... 52 Figure 12 Noise rise with number UEs for UL .................................................................................................. 53 Figure 13 16-QAM vs. 64-QAM SINR requirements ........................................................................................ 54 Figure 14 DL throughput distribution over macro cell layout with DC-HSDPA compared to sum of two separate WCDMA cells ..................................................................................................................................... 55 Figure 15 Gain of DC-HSDPA on cell throughput ............................................................................................ 55 Figure 16 HSUPA link level performance ......................................................................................................... 56 Figure 17 Multiradio BTS concept .................................................................................................................... 58 Figure 18 Multiradio combiner .......................................................................................................................... 60 Figure 19 Active multiradio combiner ............................................................................................................... 61 Figure 20 Smart diplexer................................................................................................................................... 62 Figure 21 RRH chaining .................................................................................................................................... 63

List of Tables

Table 1 - RNC Features ............................................................................................................................................................................ 7 Table 2 - RNC Features ...................................................................................................................................... 8 Table 3 Feature inter-dependency ................................................................................................................... 8 Table 4 - Feature requirements 24kbps Paging Channel ................................................................................ 9 Table 5 Parameters associated with the 24 kbps Paging Channel feature ..................................................... 9 Table 6 Parameters associated with the LTE Inter-working feature .............................................................. 10 Table 7 - Feature requirements Fast L1 Synchronisation ............................................................................. 12 Table 8 Parameters associated with the Fast Layer 1 Synchronisation feature ........................................... 12 Table 9 - Feature requirements Power Saving Mode for BTS ....................................................................... 13 Table 10 Parameters associated with the Power Saving Mode for BTS feature........................................... 14 Table 11 - Feature requirements Common Channel Setup ........................................................................... 16 Table 12 Parameters associated with the Common Channel Setup feature ................................................. 17 Table 13 Parameters associated with the Fast Dormancy feature ................................................................ 19 Table 14 Parameters associated with the Common Channel Setup feature ................................................. 21 Table 15 - Maximum HSDPA bit rates with different features .......................................................................... 22 Table 16 - Feature requirements CS Voice over HSPA ................................................................................ 23 Table 17 Parameters associated with the CS Voice over HSPA feature ...................................................... 25 Table 18 - Feature requirements MIMO ........................................................................................................ 28 Table 19 Parameters associated with the MIMO feature .............................................................................. 29 Table 20 - Feature requirements HSDPA 64 QAM ....................................................................................... 30 Table 21 Parameters associated with the HSDPA 64QAM feature .............................................................. 30 Table 22 - Feature requirements DC-HSDPA ............................................................................................... 32 Table 23 Parameters associated with the Dual Cell HSDPA feature ............................................................ 32 Table 24 - Feature requirements Flexible RLC /DL) ...................................................................................... 34 Table 25 Parameters associated with the Downlink Flexible RLC feature .................................................... 34 Table 26 - HSUPA UE Categories with maximum supported bit rates ............................................................. 36 Table 27 - HSUPA bit rates with different RAN features .................................................................................. 36 Table 28 - Feature requirements HSUPA 5.8 Mbps ...................................................................................... 37 Table 29 Parameters associated with the HSUPA 5.8 Mbps and HSUPA 2 ms TTI features ...................... 37



Version 1.1

Table 30 - Feature requirements HSUPA 2 ms TTI ...................................................................................... 38 Table 31 Parameters associated with the HSUPA 5.8 Mbps and HSUPA 2 ms TTI features ...................... 39 Table 32 Feature requirements Fractional DPCH ......................................................................................... 40 Table 33 Parameters associated with the Fractional DPCH feature ............................................................. 42 Table 34 - Feature requirements Continuous Packet Connectivity ............................................................... 44 Table 35 Parameters associated with enabling the Continuous Packet Connectivity feature ...................... 45 Table 36 CPC parameters associated with the CS Voice over HSPA service (2ms HSUPA TTI) ................ 45 Table 37 CPC parameters associated with other specific connection types ................................................. 47 Table 38 Extended inactivity timers for UE battery power optimisation ........................................................ 47 Table 39 Other parameters associated with the CPC feature ....................................................................... 47 Table 40 - Feature requirements HSPA 72 Users per Cell ........................................................................... 48 Table 41 Parameters associated with the HSPA 72 Users Per Cell feature ................................................. 49 Table 42 Parameters associated with the HSPA 72 Users Per Cell feature ................................................. 50 Table 43 - RNC Features .................................................................................................................................. 51 Table 44 - AMR modes and bit rates on HSPA ................................................................................................ 52 Table 45 - New BTS features ........................................................................................................................... 57 Table 46 - New Flexi Radio Modules ................................................................................................................ 59



Version 1.1

1 Introduction The purpose of this guide is to describe the features and parameters of RU20 WCDMA networks. This document focuses on the key differences introduced by RU20 and their impact on planning and performance. Prior knowledge of NSN HSPA RAN products and solutions is therefore expected from the reader.

More detail on 3G radio dimensioning can be found in [1].

More detail on RAS6 / RU10 radio planning can be found in and [2].

RU20 delta training material can be found in [3].

1.1 Summary of RU20 Features Table 1 lists the new features in RU20 (RN5.0) and RU20 On Top (RN5.0 EP1) releases with the feature number and license type.

RNC Features Feature Number

RU20 License

Mobility management LTE Interworking RAN2067 On top, RNC ON/OFF Voice CS Voice over HSPA RAN1689 On top, RNC ON/OFF Radio access bearer combinations 24kbps Paging Channel RAN1202 RNC ON/OFF HSDPA MIMO RAN1642 On top, BTS ON/OFF HSDPA 64 QAM RAN1643 RNC ON/OFF DC-HSDPA 42Mbps RAN1906 On top, RNC capacity User experience HSUPA 5.8 Mbps RAN981 RNC ON/OFF HSUPA 2ms TTI RAN1470 RNC ON/OFF Fractional DPCH RAN1201 RNC ON/OFF Fast L1 synchronisation RAN1322 Basic Continuous Packet Connectivity RAN1644 RNC ON/OFF Capacity and efficiency Flexible RLC(DL) RAN1638 Basic Power Saving Mode for BTS RAN955 RNC ON/OFF HSPA 72 Users per Cell RAN1686 RNC ON/OFF Common Channel Setup RAN1797 RU10 on top, Basic Fast Dormancy RAN2136 RU10 on top, Basic Direct Resource Allocation for HSPA RAN1762 RU10 on top, Basic

Table 1 - RNC Features

Table 2 shows the features with the related 3GPP releases. Release 9 features are not included in RU20



Version 1.1

3GPP Features

Release 7 Continuous packet connectivity HSDPA 64-QAM MIMO (16-QAM) Flexible RLC (DL) CS Voice over HSPA Flat architecture (iHSPA)

Release 8 Flexible RLC (UL) MIMO & HSDPA 64-QAM DC-HSDPA (64-QAM) Fast Dormancy

Release 9 MIMO & DC-HSDPA (64-QAM) DC-HSDPA Multi-band, (> 2 carriers?)

Table 2 - RNC Features

Table 3 lists the main inter-dependencies between the new and existing RNC features together with the HW requirement and UE release.

Table 3 Feature inter-dependency

The Fast Dormancy Feature requires release 8 or newer UE. The Direct Resource Allocation for HSPA feature requires HSDPA and HSDPA Dynamic Resource Allocation to be enabled.



Version 1.1

2 General RRM and DCH features 2.1 24kbps Paging Channel In RU10 and earlier the paging channel supports 8 kbps rate, in transport channel level TBS of 80 bits and TTI 10 ms. This provides a paging capacity of one paging per 10 ms TTI. Some network with high paging load can benefit from higher paging capacity, which is provided in RU20 with 24 kbps Paging Channel feature. This feature enables the use of dedicated S-CCPCH with SF128 and transport channel with 240 bits and 10 ms TTI for paging.

Requirements

UE requirements None Network Hardware Requirements None Feature Requirements None License RNC ON/OFF license

Table 4 - Feature requirements 24kbps Paging Channel

2.1.1 24 kbps Paging Channel Parameters The RNC databuild parameters associated with the 24 kbps Paging Channel feature are presented in Table 5.

Parameter New Scope Range Default Recommended

PCH24kbpsEnabled WCEL 0 (Disabled), 1 (Enabled) 0 (Disabled) 1 (Enabled)

PtxSCCPCH2SF128 WCEL 35..15 dB, step 0.1 dB -2 dB -2 dB

Table 5 Parameters associated with the 24 kbps Paging Channel feature

The PCH24kbpsEnabled parameter switches the 24 kbps paging channel on and off, whereas the PtxSCCPCH2SF128 parameter specifies the transmit power of the relevant S-CCPCH relative to the transmit power of the CPICH. Increasing this transmit power will help to improve the coverage of the 24 kbps paging channel. However, it will also reduce the remaining transmit power available for traffic. The S-CCPCH transferring the FACH supports bit rates of up to 36 kbps so it makes sense that the S-CCPCH transferring the 24 kbps PCH uses a similar transmit power.

2.2 LTE Interworking LTE Interworking feature enables the cell reselection from 3G to LTE. LTE adjacencies are defined in new ADJL objects and corresponding re-selection parameters on HOPL objects. Operators can set the preference of LTE capable UE either to camp on 3G or LTE by setting of the RAT priority.

2.2.1 LTE Inter-working Parameters The RNC databuild parameters associated with the LTE Inter-working feature are presented in Table 6.


SIB19Priority RNC 1 to 4, step 1 3 3

EUTRAdetection RNC 0 (false), 1 (true) 0 (false) 1 (true)



Version 1.1

LTECellReselecPSISHO WCEL 0 (Disabled), 1 (Enabled) 0 (Disabled) 1 (Enabled)

AbsPrioCellReselec WCEL 0 to 7, step 1 0 0

Sprioritysearch1 WCEL 0 to 62, step 2 dB 0 dB 0 dB

Sprioritysearch2 WCEL 0 to 7, step 1 dB 0 dB 0 dB

Threshservlow WCEL 0 to 62, step 2 dB 0 dB 0 dB

LoadBasedCPICHEcNoSRB HSPA

WCEL -25 to 0, step 1 dB -25 dB -25 dB

LoadBasedCPICHEcNoThre EDCH2MS

WCEL -25 to 0, step 1 dB -0 dB -0 dB

ADJLId ADJL 0 to 8, step 1 N/A N/A

AdjLEARFCN ADJL 0 to 65535 N/A N/A

AdjLMeasBw ADJL 6, 15, 25, 50, 75, 100 6 6

HopLIdentifier ADJL 1 to 10, step 1 N/A N/A

HOPLId HOPL 1 to 10, step 1 N/A N/A

AdjLAbsPrioCellReselec HOPL 0 to 7, step 1 1 1

AdjLQrxlevminEUTRA HOPL -140 to -44, step 2 dBm -140 dBm -140 dBm

AdjLThreshigh HOPL 0 to 62, step 2 dB 0 dB 0 dB

AdjLThreslow HOPL 0 to 62, step 2 dB 0 dB 0 dB

Table 6 Parameters associated with the LTE Inter-working feature

The LTECellReselecPSISHO parameter enables/disables cell re-selection from UMTS to LTE. This parameter has WCEL scope so cell re-selection can be enabled/disabled on a per cell basis. When enabled, the UMTS network broadcasts the relevant content within SIB19. The LTECellReselecPSISHO parameter also enables/disables incoming inter-system handover from LTE to UMTS. The SIB19Priority parameter determines how often SIB19 is broadcast relative to the other SIB. The size of the SIB also has an impact upon how often SIB are broadcast.

The EUTRAdetection parameter is used to instruct UE whether or not they are allowed to detect the presence of LTE coverage for the purposes of end-user display information, e.g. the UE could display an LTE symbol on its screen when within LTE coverage. This flag is broadcast within SIB19.

LTE does not require the definition of individual neighbour cells. The ADJL parameter object is used to specify LTE RF carriers (using the AdjLEARFCN parameter). These RF carriers are broadcast within SIB19 and provide direction for UE completing inter-RAT cell re-selection towards LTE. A maximum of 8 RF carriers can be specified. This corresponds to the maximum allowed by 3GPP within the release 8 version of TS 25.331. A measurement bandwidth is specified for each LTE RF carrier using the AdjLMeasBw parameter. The 6 possible values for the measurement bandwidth (6, 15, 25, 50, 75, 100 resource blocks) correspond to the 6 possible LTE channel bandwidths (1.4, 3, 5, 10, 15, 20 MHz). Thus, the AdjLMeasBw parameter should be configured to match the appropriate LTE channel bandwidth.

Each ADJL points toward a HOPL object which includes priority and minimum signal strength requirement parameters. The AdjLAbsPrioCellReselec parameter allows LTE RF carriers to be prioritised. If all ADJL point towards the same HOPL then all LTE RF carriers will have the same



Version 1.1

priority. 0 represents the lowest priority and 7 represents the highest priority. The WCEL AbsPrioCellReselec parameter defines the absolute priority for the serving UMTS cell. This is compared with the priority of neighbouring LTE cells during cell re-selection. Neighbouring cells with higher priority are always measured by the UE. Neighbouring cells with lower priority are measured when either the CPICH RSCP or CPICH Ec/Io becomes relatively weak. The Sprioritysearch1 parameter defines a CPICH RSCP threshold relative to Qrxlevmin, whereas the Sprioritysearch2 parameter defines a CPICH Ec/Io threshold relative to Qqualmin. The UE must complete neighbour cell measurements if the measured CPICH RSCP Qrxlevmin falls below Sprioritysearch1, or if the measured CPICH Ec/Io Qqualmin falls below Sprioritysearch2. The UE may also chose to complete measurements prior to the CPICH falling below these thresholds.

Once measurements have started, the cell re-selection decision is dependent upon the absolute priorities allocated to each network layer. The AdjLThreshigh parameter defines an RSRP margin required for cell re-selection to a higher priority network layer. The RSRP margin is specified in terms of Srxlev = Measured RSRP Qrxlevmin Pcompensation, where Pcompensation = Max(UE_TXPWR_MAX_RACH P_MAX, 0). Ignoring the impact of Pcompensation, AdjLThreshigh represents the number of dB that the RSRP must exceed Qrxlevmin before cell re-selection is allowed. In the case of LTE neighbours with equal or lower priority, the measured CPICH RSCP Qrxlevmin of the current serving cell must become less than the value Threshservlow, or the measured CPICH Ec/Io Qqualmin of the current serving cell must become less than 0, prior to cell re-selection. In addition, the AdjLThreslow parameter defines an RSRP margin for cell re-selection to a network layer with equal or lower priority. Ignoring the impact of Pcompensation, AdjLThreslow represents the number of dB that the RSRP must exceed Qrxlevmin before cell re-selection is allowed. The use of these thresholds is described in greater detail within the release 8 version of 3GPP TS 25.304. The AdjLQrxlevminEUTRA parameter defines the minimum Received Signal Reference Power (RSRP) requirement for an LTE cell to be acceptable for cell re-selection. RSRP represent the average power of a single LTE resource element occupied by the reference signal. The default value for the AdjLQrxlevminEUTRA parameter is set to its minimum. This minimum is consistent with the minimum specified by 3GPP and means that it will be relatively easy for the UE to identify an LTE with sufficient signal strength.

The LoadBasedCPICHEcNoSRBHSPA parameter is applicable to incoming handovers from LTE. It defines the coverage area for the SRB on HSPA. If the CPICH Ec/Io is greater than the value of this parameter then the SRB is allocated HSPA. Otherwise it is allocated a DCH. Likewise, the LoadBasedCPICHEcNoThreEDCH2MS parameter is also applicable to incoming handovers from LTE. This parameter defines the coverage area for the HSUPA 2 ms TTI. If the CPICH Ec/Io is greater than the value of this parameter then HSUPA is allocated the 2 ms TTI. Otherwise, HSUPA is allocated the 10 ms TTI.

2.3 Fast L1 synchronisation With the Fast L1 Synchronisation feature the initial DCH channel establishment is shortened by 40 ms. This is done by the network by instructing the UE to use so called post-verification instead of pre-verification for the L1 synchronisation before starting UL transmission.

Requirements

UE requirements Cat-6 or later Network Hardware Requirements None Feature Requirements None License None



Version 1.1

Table 7 - Feature requirements Fast L1 Synchronisation

Figure 1 present the different on the L1 synchronisation procedure without and with the Fast L1 Synchronisation feature.

Node B starts transmitting

UE starts receiving

1st in-sync primitive

40 ms window

4th in-sync primitive

UE starts transmitting

10 ms radio frames

Delay while UE receives RRC Connection Setup message on the FACH

Node B starts transmitting

Post verification check

40 ms window

UE starts transmitting

UE starts receiving

UE stops transmitting if verification check fails

10 ms radio frames

> 90 ms

> 20 ms

Figure 1 L1 sync time without and with Fast L1 Synchronisation

2.3.1 Fast Layer 1 Synchronisation Parameters The RNC databuild parameters associated with the Fast Layer 1 Synchronisation feature are presented in Table 8.


PostVerifPeriodDLSynch RNC 0 (Post-verification period not used), 1 (Post-verification period used)

1 1

PCPreamble RNC 0 to 7 frame, step 1 frame 0 frames 0 frames

SRBDelay RNC 0 to 7 frame, step 1 frame 7 frames 7 frames

Table 8 Parameters associated with the Fast Layer 1 Synchronisation feature

The PostVerifPeriodDLSynch parameter defines whether or not post-verification is used during downlink chip and frame synchronisation for release 6 and newer UE. The default value enables the feature so changes to this parameter are not necessary unless there is a requirement to disable the feature.



Version 1.1

The previously hidden parameters for the Power Control Preamble and SRB Delay become configurable with this feature. These are configured using the PCPreamble and SRBDelay parameters. The Power Control Preamble defines the number of radio frames during which the upink DPCCH is transmitted without the DPDCH/E-DPCCH/E-DPDCH. This is applied when the UE establishes its first radio link (from RRC Idle mode or from CELL_FACH). The SRB delay defines the number of radio frames after the Power Control Preamble during which SRB data cannot be transferred.

2.4 Power Saving Mode for BTS With the Power Saving Mode for BTS feature a cell (or multiple cells) can be shut down during low load periods. A cell is activated on need basis if the traffic load of other active cells is increased. When one power amplifier is shared among multiple cells, the cell shutdown needs to be done simultaneously for all those cells. Otherwise this feature does not bring benefits and cannot be used. RNC monitors the load in downlink and uplink directions and triggers the cell shutdown once all the following operator adjustable conditions have been met in a cell:

time of day no emergency calls or Wireless Priority Service calls in cell traffic load in the cell going below the defined threshold duration of low traffic remaining cells not in high load

The feature requires only RNC ON/OFF license.

Requirements

UE requirements None Network Hardware Requirements None Feature Requirements None License RNC ON/OFF license

Table 9 - Feature requirements Power Saving Mode for BTS

2.4.1 Power Saving Mode for BTS Parameters The RNC databuild parameters associated with the Power Saving Mode for BTS feature are presented in Table 10.


PWSMDuration RNC 1 to 30 minutes, step 1 minutes 5 minutes 5 minutes

PWSMExceededTrafficDur RNC 10 to 300 secs, step 10 secs 20 secs 20 secs

PWSMDriftAllowed RNC 0 (no), 1 (yes) 0 (no) 0 (no)

PWSMInUse WBTS 0 (off), 1 (on) 0 (off) 1 (on)

PWSMShutdownBeginHour WBTS 0 to 23 hours, step 1 hours 22 hours 22 hours

PWSMShutdownBeginMin WBTS 0 to 59 minutes, step 1 minutes 0 minutes 0 minutes

PWSMShutdownEndHour WBTS 0 to 23 hours, step 1 hours 6 hours 6 hours

PWSMShutdownEndMin WBTS 0 to 59 minutes, step 1 minutes 0 minutes 0 minutes

PWSMWeekday WBTS 0 (None), 1 (Saturday), 0 (None) 0 (None)



Version 1.1

2 (Sunday), 3 (Saturday and Sunday)

PWSMRemCellSDBeginHour WBTS 0 to 23 hours, step 1 hours 22 hours 22 hours

PWSMRemCellSDBeginMin WBTS 0 to 59 minutes, step 1 minutes 0 minutes 0 minutes

PWSMRemCellSDEndHour WBTS 0 to 23 hours, step 1 hours 6 hours 6 hours

PWSMRemCellSDEndMin WBTS 0 to 59 minutes, step 1 minutes 0 minutes 0 minutes

PWSMCellGroup WCEL 0 to 6, step 1 0 N/A

PWSMShutdownOrder WCEL 0 to 3, step 1 0 N/A

PWSMShutdownRemCell WCEL 0 (NO), 1 (YES) 0 N/A

PowerSaveHSPAType WCEL 0 (NoHSPA05ReConf), 1 (HSPA0), 2 (HSPA5)

0 N/A

PWSMAVPwrNRTHSDPA WCEL 0 to 50 dBm, step 1 dBm 31 31

PWSMAVLimitNRTHSDPA WCEL 0 to 300, step 1 10 10

PWSMAVPwrRTHSDPA WCEL 0 to 50 dBm, step 1 dBm 37 dBm 37 dBm

PWSMAVLimitRTHSDPA WCEL 0 to 300, step 1 0 0

PWSMAVLimitRTDCH WCEL 0 to 50 dBm, step 1 dBm 37 dBm 37 dBm

PWSMEXPwrLimit WCEL 0 to 50 dBm, step 1 dBm 37 dBm 37 dBm

PWSMEXUsrLimit WCEL 0 to 300, step 1 5 5

PWSMSDPwrNRTHSDPA WCEL 0 to 50 dBm, step 1 dBm 34 dBm 34 dBm

PWSMSDLimitNRTHSDPA WCEL 0 to 300, step 1 5 5

PWSMSDPwrRTHSDPA WCEL 0 to 50 dBm, step 1 dBm 34 dBm 34 dBm

PWSMSDLimitRTHSDPA WCEL 0 to 300, step 1 5 5

PWSMSDLimitNRTDCH WCEL 0 to 128, step 1 10 10

PWSMSDPwrRTDCH WCEL 0 to 50 dBm, step 1 dBm 34 dBm 34 dBm

PWSMSDLimitRTDCH WCEL 0 to 128, step 1 10 10

Table 10 Parameters associated with the Power Saving Mode for BTS feature

The PWSMInUse parameter enables/disables the Power Saving Mode for BTS feature on a per Node B basis. The default value is OFF so the feature is disabled unless the parameter is changed. When using this feature, the cells belonging to the Node B need to be organised into PWSM cell groups. The cell group to which a cell belongs is defined by the WCEL PWSMCellGroup parameter. The default value of 0 means that the cell does not belong to a cell group so this parameter requires configuration prior to enabling the feature. The normal strategy is to define one cell group per sector, i.e. cells belonging to the same sector belong to the same PWSM cell group. The PWSMShutdownOrder parameter defines the order in which the cells belonging to a specific cell group are shutdown. Every cell group must have at least one cell which is configured with a shutdown order value of 0. This value indicates that the cell is a remaining cell and is not targeted for low traffic shutdown. The value of 1 means that the cell is the first cell within the group to be targeted for shutdown, while the value of 2 means that the cell is the second cell within the group to be targeted for shutdown.



Version 1.1

The WCEL PWSMShutdownRemCell parameter defines whether or not a remaining cell can be shutdown. Remaining cells can be shutdown on the days defined by the PWSMWeekday parameter. Otherwise, they can be shutdown during the time window defined by the PWSMRemCellSDBeginHour, PWSMRemCellSDBeginMin, PWSMRemCellSDEndHour and PWSMRemCellSDEndMin parameters. Remaining cells can only be shutdown when all non-remaining cells within a cell group have already been shutdown. The shutdown of remaining cells does not depend upon traffic levels (with the exception of emergency calls - which prevent remaining cells from being shutdown).

In general, the feature is aimed for use during periods of low network activity, i.e. during the night. Once the feature has been enabled, the PWSMShutdownBeginHour, PWSMShutdownBeginMinute, PWSMShutdownEndHour and PWSMShutdownEndMinute parameters define the time window during which the feature is able to shutdown a cell.

There is a relatively large group of parameters associated with triggering cell shutdown due to low traffic. The PWSMSDLimitRTDCH and PWSMSDPwrRTDCH parameters define triggering thresholds for Real Time DCH connections, whereas the PWSMSDLimitNRTDCH parameter defines a triggering threshold for Non-Real Time DCH. The PWSMSDPwrRTHSDPA and PWSMSDLimitRTHSDPA parameters define triggering thresholds for Real Time HSPA connections, whereas the PWSMSDPwrNRTHSDPA and PWSMSDLimitNRTHSDPA parameters define triggering thresholds for Non-Real Time HSPA connections. A cell shutdown due to low traffic is attempted if all of the above triggering mechanisms are satisfied for a period of time defined by the PWSMDuration parameter.

Shutting down a non-remaining cell also involves an admission control check on the target cell to help ensure that there is sufficient capacity to support the traffic from the cell to be shutdown. This admission control check is based upon the PWSMEXPwrLimit and PWSMEXUsrLimit parameters. The PWSMEXUsrLimit parameter is only applicable if HSDPA is enabled at the target cell.

The PWSMDriftAllowed parameter with scope RNC, defines whether or not a cell can be shutdown due to low traffic when the controlling RNC is a drift RNC for one or more UE. The default value of this parameter is NO, meaning that cells cannot be shutdown when they have connected UE for which the controlling RNC is a drift RNC.

Non-Remaining cells can be re-activated after cell shutdown if levels of traffic start to increase. The PWSMAVLimitRTDCH parameter defines a threshold for Real Time DCH connections, whereas there is no re-activation triggering threshold based upon Non-Real Time DCH connections. The PWSMAVPwrRTHSDPA and PWSMAVLimitRTHSDPA parameters define thresholds for Real Time HSPA connections, whereas the PWSMAVPwrNRTHSDPA and PWSMAVLimitNRTHSDPA parameters define thresholds for Non-Real Time HSPA connections. A cell re-activation due to increasing traffic is attempted if all of the above triggering mechanisms are satisfied for a period of time defined by the PWSMExceededTrafficDur parameter.

The PowerSaveHSPAType parameter defines the HSPA configuration of a cell and whether or not that configuration can change, or trigger changes when cells are shutdown. Configuring a value of 1 (HSPA0) means that the cell does not normally support HSPA. However, if a cell which is configured with a value of 2 (HSPA5) is shutdown, then this triggers the enabling of HSPA within the HSPA0 cell. If a cell is configured as HSPA0 then there must be at least one cell within the same cell group which is configured as HSPA5. If an HSPA5 cell is re-activated then HSPA can be re-disabled at the HSPA0 cell. The PowerSaveHSPAType parameter can also be configured with a value of 0 (NoHSPA05ReConf) which means that the cell does not trigger HSPA to be enabled in another cell when shutdown, and likewise, does not have HSPA enabled if another cell is shutdown.



Version 1.1

2.5 Common Channel Setup Common Channel Setup feature is introduced in RU10 On Top release CD2. This feature enables the use of RACH and FACH common channels for RRC connection setups instead of dedicated channel. Signalling link for the RRC connection setup can be selected between RACH/FACH common channels, DCH 13.6 kbps or DCH 3.4 kbps according to operator's defined preferences. Operator defines the preferred signalling link type depending on the UE establishment cause, UE measurement results (CPICH EC/N0) and common channel load.

Requirements

UE requirements none Network Hardware Requirements None Feature Requirements None License None

Table 11 - Feature requirements Common Channel Setup

2.5.1 Common Channel Setup Parameters The Common Channel Setup feature is available as part of RU10. However, the RU10 version of the feature does not include any configurable parameters within the RNC databuild (parameters are configured within the PRFILE). The RNC databuild parameters associated with the RU20 version of the Common Channel Setup feature are presented in Table 12.


RRCSetupCCHEnabledR99 RNC 0 (Disabled), 1 ((Enabled) 0 (Disabled) 0 (Disabled)

SRBMapRRCSetupEC WCEL Bit 0: Orig. conv. call Bit 1: Orig. stream call Bit 2: Orig. interactive call Bit 3: Orig. background call Bit 4: Orig. sub. traffic call Bit 5: Term. conv. call Bit 6: Term.stream call Bit 7: Term.interactive call Bit 8: Term.background call Bit 9: Emerg.call, Bit 10: Inter-RAT cell re-sel. Bit 11: Inter-RAT CCO Bit 12: Registration Bit 13: Detach Bit 14: Orig. high priority sig. Bit 15: Orig. low priority sig. Bit 16: Call re-establishment Bit 17: Term. high pri. sig. Bit 18: Term. low pri. sig. Bit 19: Term. cause unknown Bit 20: MBMS reception Bit 21: MBMS ptp RB req.

0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 1 1 0 0 0

0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 1 1 0 0 0

SRBBitRateRRCSetupEC WCEL Bit 0: Orig. conv. call Bit 1: Orig. stream call Bit 2: Orig. interactive call Bit 3: Orig. background call Bit 4: Orig. sub. traffic call

1 1 1 1 1

1 1 1 1 1



Version 1.1

Bit 5: Term. conv. call Bit 6: Term.stream call Bit 7: Term.interactive call Bit 8: Term.background call Bit 9: Emerg.call, Bit 10: Inter-RAT cell re-sel. Bit 11: Inter-RAT CCO Bit 12: Registration Bit 13: Detach Bit 14: Orig. high priority sig. Bit 15: Orig. low priority sig. Bit 16: Call re-establishment Bit 17: Term. high pri. sig. Bit 18: Term. low pri. sig. Bit 19: Term. cause unknown Bit 20: MBMS reception Bit 21: MBMS ptp RB req.

1 1 1 1 1 1 1 0 0 0 0 1 0 0 0 0 0

1 1 1 1 1 1 1 0 0 0 0 1 0 0 0 0 0

CPICHEcNoSRBMapRRC WCEL -24 to 0 dB, step 0.5 dB -8 dB -8 dB

CCHSetupEnabled WCEL 0 (Disabled), 1 (Enabled) 0 (Disabled) 1 (Enabled)

RachLoadThresholdCCH - WCEL 0 to 100, step 1 % 75 % 75 % FachLoadThresholdCCH - WCEL 0 to 100, step 1 % 75 % 75 % PtxThresholdCCH - WCEL -5 to 0, step 0.1 dB -1 dB -1 dB RACHCapacity - WCEL 1 to 4, step 1 2 4

Table 12 Parameters associated with the Common Channel Setup feature

The CCHSetupEnabled parameter is used to enable and disable the feature on a per cell basis. The parameter in online so can be changed without object locking.

The RRCSetupCCHEnabledR99 parameter is used to determine whether or not release 99 UE are permitted to establish connections in CELL_FACH rather than CELL_DCH. By default, this parameter is set to disabled, so release 99 UE are always directed from RRC Idle mode to CELL_DCH. This parameter is included in case older UE do not support the transition from RRC Idle mode to CELL_FACH.

The SRBMapRRCSetupEC parameter specifies the set of RRC Connection Request cause values which trigger the RRC Idle mode to CELL_FACH transition, rather than the RRC Idle mode to CELL_DCH transition. A value of 1 indicates that the transition to CELL_FACH is used. Bit 9 for emergency calls does not have any impact because emergency calls are always directed to CELL_DCH. By default, the registration, detach, originating high priority signaling, originating low priority signaling, terminating high priority signaling and terminating low priority signaling cause values are selected as those which trigger the transition to CELL_FACH. This selection of cause values means that signaling procedures can be completed entirely in CELL_FACH without requiring a transition to CELL_DCH, i.e. the sequence would be RRC Idle mode -> CELL_FACH -> RRC Idle mode. Some UE use the high priority signaling cause value for PS data connections. These connections may or may not make a subsequent transition to CELL_DCH. If the data transfer is small, e.g. a keep-alive, then the UE is likely to remain in CELL_FACH before returning to RRC Idle mode or moving into CELL_PCH. If the data transfer is larger then the UE is likely to trigger an upgrade from CELL_FACH to CELL_DCH. The benefit of completing signaling procedures in CELL_FACH is a reduction of the CNBAP signaling at the Node B, i.e. the radio link setup procedure is not required. This is important because Node B are limited in terms of the rate at which radio link setup procedures which can be processed. Completing signaling on the common channels also helps to reduce RNC ICSU load. The drawback of establishing connections



Version 1.1

in CELL_FACH is an increased common channel load, i.e. the utilization of the RACH and FACH increases.

The CPICHEcNoSRBMapRRC parameter defines the minimum CPICH Ec/Io required for connection establishment in CELL_FACH. Connections are established in CELL_DCH if the CPICH Ec/Io reported within the RRC Connection Request message is less than the value of this parameter. This parameter can effectively be disabled by configuring it with its smallest value. However, the objective is to ensure that UE are only allowed to establish connections in CELL_FACH when the coverage conditions are relatively good.

The SRBBitRateRRCSetupEC parameter specifies the set of RRC Connection Request cause values which use the 13.6 kbps standalone SRB when connections are established in CELL_DCH rather than CELL_FACH, i.e. this parameter does not impact connections which are directed from RRC Idle mode to CELL_FACH. A value of 1 indicates that the 13.6 kbps standalone SRB is allocated in CELL_DCH. The default value of this parameter allows a relatively large set of establishment causes to use the 13.6 kbps standalone SRB. This provides the benefit of decreased connection establishment time at the cost of a greater Iub bandwidth reservation. Note that the previously used StandAloneDCCHBitRate parameter is deleted in RU20.

The RachLoadThresholdCCH parameter defines a threshold for the RACH load. Connections are established in CELL_DCH if the RACH load exceeds the value of this threshold. The RACH load is quantified as the average number of acknowledged PRACH preambles over 2 radio frames, relative to the value of the RACHCapacity parameter multiplied by 2. The factor of 2 is included because the RACHCapacity parameter defines the number of messages which can be decoded per 10 ms radio frame. The default value for this parameter is 75 %, corresponding to 3 out of 4 (or 6 out of 8) RACH messages per 20 ms.

The RACHCapacity parameter specifies the maximum number of RACH messages which are decoded during a 10 ms radio frame. This parameter requires object locking for modification. The default value is 2 messages but it is recommended to increase this to 4 messages when the common channel setup feature is enabled. Using a larger value increases the capacity of the RACH to handle the increased load generated by establishing connections in CELL_FACH.

The FachLoadThresholdCCH parameter defines a threshold for the FACH load. Connections are established in CELL_DCH if the FACH load exceeds the value of this threshold. The FACH load is quantified as the S-CCPCH throughput measured at the bottom of the physical layer relative to the maximum capability of the S-CCPCH. The default value for this parameter is 75 %, corresponding to a S-CCPCH activity factor of 75 %.

The PtxThresholdCCH parameter defines a threshold relative to PtxTarget for the total downlink transmit power. Connections are established in CELL_DCH if the total downlink transmit power exceeds the value of this threshold. The default value is -1 dB corresponding to a threshold of 41 dBm when PtxTarget is configured with a value of 42 dBm. Connections are established in CELL_DCH rather than CELL_FACH when the total downlink transmit power is high because DPCH connections are more efficient on the air-interface as a result of using inner loop power control.

2.6 Fast Dormancy Fast Dormancy feature is introduced in RU20 On Top. The Fast Dormancy feature modifies the system behaviour associated with the original Fast Dormancy introduced by UE vendors. UE vendors originally introduced Fast Dormancy as a means to increase UE battery life. The original Fast Dormancy procedure allows UE to release themselves to RRC Idle mode by sending a Signalling Connection Release Indication (SCRI) after completing their data transfer. The RNC is



Version 1.1

forced to release the UE to RRC Idle mode (to comply with the 3GPP specifications). UE power consumption is minimised in RRC Idle mode so battery life is prolonged. However, the transition to Idle mode defeats the purpose of having CELL_PCH and URA_PCH. UE power consumption in these RRC states is only slightly greater than that in RRC Idle mode (potentially shorter DRX cycle and Cell or URA updates required). A major drawback of the original Fast Dormancy introduced by UE vendors is that the signalling load can increase significantly. Smart phones can send frequent polls or keep-alives causing UE to ping-pong between RRC Idle mode and RRC Connected mode (typically every 60 to 90 seconds). The Common Channel Setup feature helps to some extent by avoiding the use of CELL_DCH.

The issues associated with the UE vendor version of Fast Dormancy were raised within 3GPP. 3GPP agreed to modify the specifications from release 8 such that the RNC can keep the UE in RRC Connected mode after receiving a SCRI. A cause value was introduced which could be included within the SCRI message. This cause value of UE Requested PS Data Session End informs the RNC that the UE can be moved out of CELL_DCH because the data transfer has finished. Instead of being released to RRC Idle mode, the RNC moves the UE into CELL_PCH or URA_PCH. UE battery life remains prolonged because power consumption in CELL_PCH and URA_PCH is low. Also, the signalling load is reduced because UE remain in RRC Connected mode. Polls and keep alives can be sent in CELL_FACH without making the transition to CELL_DCH.

An SCRI message with cause UE Requested PS Data Session End allows the RNC to overide the normal inactivity timers. The RNC instructs the UE to make the state change to CELL_PCH or URA_PCH. If the RNC receives an SCRI without a cause value then the existing legacy functionality is applied and the UE is moved to RRC Idle mode.

2.6.1 Fast Dormancy Parameters The RNC databuild parameters associated with the Fast Dormancy feature are presented in Table 13


FastDormancyEnabled RNC 0 (Disabled), 1 ((Enabled) 0 (Disabled) 1 (Enabled)

T323 (hard coded) RNC 0, 5, 10, 20, 30, 60, 90, 120 secs

0 secs 0 secs

FastDormOverCpcPri RNC 0 (Fast Dormancy has higher priority), 1 (CPC has higher priority)

0 (Fast Dormancy has higher priority),

0 (Fast Dormancy has higher priority),

Table 13 Parameters associated with the Fast Dormancy feature

The FastDormancyEnabled parameter is used to enable and disable the feature on a per RNC basis. The parameter in online so can be changed without object locking. Enabling the feature also requires the existing MSActivitySupervision parameter to be configured with a value > 0 to enable the PCH states. Enabling the feature results in T323 being broadcast within SIB1. The inclusion of T323 within SIB1 allows the UE to detect that the network supports Fast Dormancy.

The T323 parameter is hard coded with a value of 0 seconds. This parameter does not belong to the normal RNC databuild and is not configurable. The T323 timer is used as a guard timer to avoid too frequent transmissions of the Signalling Connection Release Indicator (SCRI) message. It is started when the UE sends a SCRI which includes the Cause information element. UE are not permitted to send a subsequent SCRI which includes the Cause information element until T323 expires.



Version 1.1

The FastDormOverCpcPri parameter allows priority to be given to either the Fast Dormancy feature or the Continuous Packet Connectivity (CPC) feature. Fast Dormancy acts to move UE into PCH states, whereas CPC acts to hold UE in CELL_DCH. If FastDormOverCpcPri is set to 0 and the UE is requesting Fast Dormancy then the UE is moved into CELL_PCH or URA_PCH. Otherwise, if FastDormOverCpcPri is set to 1 and the UE is requesting Fast Dormancy then the UE state is not changed.

2.7 Changes to other features RU20 introduces possibility to restrict the bitrate of the HSDPA UL DCH return channel. The new WCEL-parameter HSDPAMaxBitrateUL defines the maximum bitrate for HSDPA UL DCH return channel. Restriction will be effective to the PS NRT RAB. Existing WCEL-parameter MaxBitRateULPSNRT shall not affect the HSDPA UL DCH return channel anymore but it is applicable to the UL DCH channel only when DL DCH is allocated.

In case of multiple PS RABs, the total bit rate of the radio link shall be balanced between radio bearers in order to guarantee DCH bit rate to all established NRT PS RABs. Balancing shall be targeted at NRT PS RAB(s), not RT PS RAB. DCH bit rate balancing shall be controlled by the new RNW-parameter DCHBitRateBalancing (RNC object class). Bit rate of the existing DCH shall not be downgraded lower than the initial bit rate. DCH bit rate balancing shall be applied to the HSDPA UL DCH return channel.

HSUPA user (PS RBs on HSPA + SRBs on DCH) can be selected as target for RT-over-(N)RT or pre-emption actions in case of BTS congestion for R99 user (existing functionality). In these cases the cell specific admission control can select a HSPA user as target for RT-over-(N)RT or pre-emption actions, if the license 1754 HSUPA Pre-emption exists and the state is On. PRFILE parameter RN40_MAINT_007 (007:276) is not used anymore for this purpose, but it is replaced with this new license.

RNC20 introduces a possibility transfer A-GPS in system information block SIB15 (new). This will enable the A-GPS capable UEs to receive this data without dedicated signalling.

In RU10 the HSDPA capable UEs can be directed from the HSDPA capable cell to another HSDPA capable cell for load balancing reasons if HSDPALayeringCommonChEnabled is enabled in the source cell, the UE is requesting interactive or background service, the HSDPA capable cell is in the same sector and the HSDPA load of the target cell is suitable. In RU20 the requested services are separately enabled with ServBtwnHSDPALayers parameter.

RU20 introduces multiple improvements which enhance the signalling performance. The first improvements were already included in the Common Channel Setup feature in RU10 CD2 and RU20 adds other improvements. In RU20 the SRB4 not used anymore, which simplifies the messaging. Reduced Radio Bearer mapping (same info utilised for multiple bearers etc.) information decreases the message sizes. The impacted procedures in L3 are:

RRC Connection setup Non-Real-Time PS RAB setup State Transition Cell_FACH->Cell_DCH Any Radio Bearer and Transport Channel reconfigurations

These changes together with the Common Channel Setup feature will shorten message delays and improve success rate, reduce resource usage in Iub, RNC ICSU and BTS.



Version 1.1

Parameter New Scope Range Default Recommen

ded

HSDPAMaxBitrateUL WCEL 1 (16 kbps), 3 (64 kbps), 4 (128 kbps), 6 (384 kbps)

6 (384 kbps) 6 (384 kbps)

HSDPACapUEInServiceHO

InacUserNbrXXXOverNRT RNC

SIB15_priority RNC 1..4, step 1 4 4 (lowest)

BroadcastSIB15 WBTS 0 (Disabled), 1 (Enabled) 0 (Disabled)

BroadcastSIB15_2 WBTS 0 (Disabled), 1 (Enabled) 0 (Disabled)

BroadcastSIB15_3 WBTS 0 (Disabled), 1 (Enabled) 0 (Disabled)

ServBtwnHSDPALayers RNC Bit 0: Background Call , Bit 1: Interactive Call , Bit 2: PS

Streaming Call , Bit 3: CS voice Call

3 (BG and I/A)

3 (BG and I/A)

Table 14 Parameters associated with the Common Channel Setup feature



Version 1.1

3 HSDPA features 3.1 HSDPA bit rates The maximum HSDPA bit rates supported by the RAN depend on the RAN configuration and active features. Table 15 lists the maximum user bit rates with different features. The DC-HSDPA bit rate is double of 64-QAM user bit rate and the transport block size is the total of two transport blocks. The MIMO bit rate is similarly double of 14.4 Mbps per user bit rate. The 64-QAM, DC-HSDPA and MIMO features require usage of Flexible RLC, thus the number of TB for these features is not integer value (see more in ??).

Features 16-QAM + 10/15 +10 Mbps/ +14.4 Mbps/ HSDPA DC-HSDPA MIMOcode user user 64-QAM (2 flows) (2 flows)

Min. UE Category Cat-6 Cat-8 Cat-9 Cat-10 Cat-14 Cat-24 Cat-16Modulation 16-QAM 16-QAM 16-QAM 16-QAM 64-QAM 64-QAM 16-QAMNumber of HS-PDSCH codes 5 10 15 15 15 30 30Air interface bit rate (Mbps) 4.8 9.6 14.4 14.4 21.6 43.2 28.8Max. transport block size (bits) 7168 13904 19891 27952 42192 84384 55904Max. transport channel (HS-DSCH) bit rate (Mbps)

3.58 6.95 9.95 14.0 21.1 42.2 28.0

RLC PDU (bits) 336 656 656 656 11216 22432 1312RLC blocks/TTI 21 21 30 42 3.76 7.51 84RLC bit rate (Mbps) 3.53 6.89 9.84 13.8 21.1 42.1 27.6RLC payload (Mbps) 3.36 6.72 9.60 13.4 21.0 42.1 26.9RLC payload (Mbps) - 10% HARQ retrans.

3.02 6.05 8.64 12.1 18.9 37.9 24.2

TCP/IP payload (Mbps) 2.94 5.89 8.41 11.8 18.4 36.8 23.5

Table 15 - Maximum HSDPA bit rates with different features

3.2 CS Voice over HSPA With the CS Voice over HSPA feature the transport channels of the AMR RAB are mapped to the HSPA bearer type (HSDPA in DL and HSUPA in UL). There are no changes on the RAB level, but the L2 RLC and transport channel is different from AMR over DCH channel type (see Figure 2). This feature supports both NB-AMR and WB-AMR together with various CS+ PS multirab combinations over HSPA channel type.

Figure 2 CS voice over HSPA compared to CS voice over DCH



Version 1.1

Table 16 lists the required features and HW. The QoS aware HSPA scheduling feature is required in order to prioritise the CS Voice traffic over the PS traffic in the HSPA schedulers.

Requirements

UE requirements 3GPP Rel-7 (late release) or Rel-8 Network Hardware Requirements Flexi Rel. 2 HW Ultrasite with EUBB RNC with CDSP-DH cards HSPA Peak Rate Upgrade in RNC196 and RNC450 Feature Requirements HSUPA basic HSDPA Dynamic Resource Allocation HSDPA with Simultaneous AMR Voice Call HSUPA with Simultaneous AMR Voice Call Fractional DPCH QoS aware HSPA scheduling Flexible RLC Continuous Packet Connectivity License RNC ON/OFF license

Table 16 - Feature requirements CS Voice over HSPA

3.2.1 CS Voice over HSPA Parameters The RNC databuild parameters associated with the CS Voice over HSPA feature are presented in Table 17.


HSPAQoSEnabled - WCEL 0 (QoS prioritization is not used for HS transport),

1 (QoS prioritization is used for HS NRT channels),

2 (HSPA streaming is in use), 3 (HSPA CS voice is in use), 4 (HSPA streaming and CS

voice are in use)

0 3

PriForConvOnHSPA RNC 0 to 14, step 1 14 14

MaxNbrOfHSSCCHCodes - WCEL 1 to 4, step 1 1 1 UsersPerHSSCCHCode WCEL 1 to 40, step 1 30 30

PtxTargetTotMin WCEL -10 to 50 dBm, step 0.1 dBm 40 dBm 40 dBm

PtxTargetTotMax WCEL -10 to 50 dBm, step 0.1 dBm 41 dBm 41 dBm

RRMULDCHActivityFactorCSAMR

- WBTS 0 to 100 %, step 1 % 50 % 50 %

PrxTargetMax WCEL 0 to 30 dB, step 0.1 dB 4 dB 4 dB

VoiceOverrideSTHSUPA WCEL 0 (Override not allowed), 1 (Override allowed)

1 1

MaxSetOfEDPDCHCSAMR2 RNC 0 (SF8), 1 (SF4) 0 0

MaxSetOfEDPDCHCSAMR10 RNC 0 (SF32), 1 (SF16) 0 0



Version 1.1

MaxEHARQReTxCSAMR2 RNC 0 to 5, step 1 2 2

MaxEHARQReTxCSAMR10 RNC 0 to 3, step 1 1 1

EDCHMuxVoiceTTI10 RNC Bit 0: Signaling link Bit 1: PS streaming

Bit 2: PS interactive THP 1 Bit 3: PS interactive THP 2 Bit 4: PS interactive THP 3

Bit 5: PS Background

63 63

EDCHMuxVoiceTTI2 RNC Bit 0: Signaling link Bit 1: PS streaming

Bit 2: PS interactive THP 1 Bit 3: PS interactive THP 2 Bit 4: PS interactive THP 3

Bit 5: PS Background

63 63

PowerOffsetEHARQVoice RNC 0 to 6 dB, step 1 dB 0 dB 0 dB

EbNoEDCHCSAMR WRAB -11 to 20 dB, step 0.1 dB 4 dB 4 dB

DiscardTimerHSCSVoice RNC 0 (Discard Timer not used), 1 (20 ms), 2 (40 ms), 3 (60 ms), 4 (80 ms), 5 (100 ms), 6 (120 ms), 7 (140 ms), 8 (160 ms), 9 (180 ms), 10 (200 ms)

2 2

T1HSCSVoice RNC 0 (10 ms), 1 (20 ms), 2 (30 ms), 3 (40 ms), 4 (50 ms), 5 (60 ms), 6 (70 ms), 7 (80 ms), 8 (90 ms), 9 (100 ms), 10 (120 ms), 11 (140 ms), 12 (160 ms), 13 (180 ms), 14 (200 ms)

1 1

MaxCSDelayUE RNC 20 to 200 ms, step 10 ms 60 ms 60 ms

MaxCSDelayRNCETTI2 RNC 20 to 200 ms, step 10 ms 80 ms 80 ms

MaxCSDelayRNCETTI10 RNC 20 to 200 ms, step 10 ms 50 ms 50 ms

HSPAForPriEnabled RNC 0 (HSPA support disabled), 1 (HSPA support enabled)

1 1

DRRCForHSDPALayerServices

- RNC Bit 0: Conversational Call , Bit 1: Streaming Call , Bit 2: Interactive Call , Bit 3: Background Call , Bit 4: Subscribed traffic Call , Bit 5: Emergency Call , Bit 6: Inter-RAT cell re-selection , Bit 7: Inter-RAT cell change order , Bit 8: Registration , Bit 9: High Priority Signalling , Bit 10: Low Priority Signalling , Bit 11: Call re-establishment , Bit 12: Terminating cause unknown , Bit 13: MBMS reception , Bit 14: MBMS ptp RB request , Bit 15: Other , Bit 16: Conv Call with F-DPCH

204 204

ServBtwnHSDPALayers RNC Bit 0: Background Call Bit 1: Interactive Call

Bit 2: PS Streaming Call Bit 3: CS voice Call

3 3

HSCAHORabCombSupport - RNC Bit 0: PS I/B RAB (always 1), 1 1



Version 1.1

Bit 1: PS Streaming , Bit 2: 2/3 NRT PS RAB , Bit 3: PS Streaming+1/2/3 NRT PS RAB's , Bit 4: CS AMR + 1 PS I/B RAB , Bit 5: CS AMR + 2/3 PS I/B RAB's , Bit 6: CS AMR + PS Streaming , Bit 7: CS AMR + PS Streaming+1/2/3 NRT RAB's , Bit 8: CS AMR RAB

PBSHSMinAllocHigher WCEL 0 to 60 s, step 1 s 30 s 30 s

PBSHSMinAllocEqual WCEL 0 to 60 s, step 1 s 20 s 20 s

PBSHSMinAllocLower WCEL 0 to 60 s, step 1 s 15 s 15 s

Table 17 Parameters associated with the CS Voice over HSPA feature

The HSPAQoSEnabled parameter is used to enable and disable the feature on a per WCEL basis. This parameter must be configured with a value of either 3 or 4, and requires object locking for modification. The HSPAQoSEnabled parameter is an existing parameter from RU10 which has had its range extended for RU20.

The PriForConvOnHSPA parameter belongs to the QoSPriorityMapping parameter structure. Its used to define a Scheduling Priority Indicator (SPI) for the CS Voice over HSPA service. The SPI allocated to the CS Voice over HSPA service should be greater than that for PS streaming but less than that for the SRB. The SPI impacts traffic handling on the Iub as well as on the air-interface.

The RNC limits the number of conversational connections using HSDPA to the value defined by MaxNbrofHSSCCHCodes UsersPerHSSCCHCode. The value of MaxNbrofHSSCCHCodes is determined by whether or not code multiplexing is enabled. Enabling code multiplexing increases the number of supported CS Voice over HSPA connections. MaxNbrofHSSCCHCodes is an existing RAS06 parameter although its maximum value is increased from 3 to 4 in RU10. UsersPerHSSCCHCode is a new parameter for RU20 with a maximum value of 40 users per HS-SCCH.

The PtxTargetTotMin and PtxTargetTotMax parameters define the dynamic range for the load control threshold, PtxTargetTot. PtxTargetTot is used for admission decisions when there is non-controllable load on HSDPA. PtxTargetTotMin must be greater than or equal to PtxTarget i.e. if PtxTarget has been increased to 42 dBm then both PtxTargetTotMin and PtxTargetTotMax must be increased from their default values. PtxTargetTotMax should not be set greater than PtxCellMax.

The RRMULDCHActivityFactorCSAMR parameter is an existing parameter used to estimate the downlink transmit power requirement of a new CS voice connection. The parameter name implies that it is used only for the uplink (includes UL) but the parameter is also used for downlink power estimation.

The PrxTargetMax parameter defines the upper limit for the dynamic range of the load control threshold, PrxTargetAMR. The lower limit is defined by the PrxTarget parameter. This means that the value of PrxTargetMax must be increased from its default if PrxTarget has been allocated a high value. The PrxTargetAMR threshold is applicable to SRB and speech connections. This threshold is applied irrespective of whether or not the CS Voice over HSPA feature is enabled.

The VoiceOverrideSTHSUPA parameter impacts the definition of the RSSI within the uplink admission control decision for CS Voice over HSPA connections. If configured with a value of



Version 1.1

Override not allowed then RSSI = MAX(PrxTotal, PrxNonEDCHST). Otherwise, if configured with a value of Override allowed then RSSI = PrxNonEDCHST. This means that a smaller value is potentially used when override is allowed.

The MaxSetOfEDPDCHCSAMR2 and MaxSetOfEDPDCHCSAMR10 parameters define the maximum E-DPDCH configuration for the 2 and 10 ms TTI. In both cases, only a single E-DPDCH is allocated so these parameter define the spreading factor of that E-DPDCH. Smaller spreading factors are allowed for the 2 ms TTI to permit higher instantaneous throughputs, i.e. to allow the same quantity of data to be transferred in 2 ms rather than 10 ms.

The MaxEHARQReTxCSAMR2 and MaxEHARQReTxCSAMR10 parameters define the maximum number of HSUPA re-transmissions allowed for CS voice over HSPA connections. In both cases, the default value is relatively small because speech data quickly becomes obsolete, i.e. there is no point in completing too many retransmissions because the delay becomes too great.

The EDCHMuxVoiceTTI2 and EDCHMuxVoiceTTI10 parameters define whether or not other E-DCH MAC-d flow data can be multiplexed within the same MAC-e PDU as CS Voice. The default values for these parameters allow multiplexing. In general, the SRB has a higher SPI than CS Voice so is prioritised during E-TFC selection. However, the maximum SRB bit rate is limited to ensure that at least 1 CS Voice frame can always be transmitted together with the SRB.

The PowerOffsetEHARQVoice parameter allows a power offset to be applied to the HARQ process used to transfer the CS Voice. The parameter is only applicable if another E-DCH MAC-d flow is multiplexed within the same MAC-e PDU as CS Voice. Otherwise the power offset is 0 dB.

The EbNoEDCHCSAMR parameter belongs to the WRAB object. This HSUPA Eb/No requirement is used by the RNC when estimating the uplink load generated by an HSUPA connection transferring CS voice. The same parameter is applicable to both 2 ms and 10 ms TTI, and to all AMR CODEC sets.

The DiscardTimerHSCSVoice parameter is used by the Node B to ensure that data is not buffered for too long, i.e. data is discarded by the Node B if a positive HARQ acknowledgement is not received before the timer expires. Similarly, the T1HSCSVoice parameter defines the T1 timer used by the UE to determine when received data should be forwarded to the higher layers despite there being missing data with lower sequence numbers. The T1HSCSVoice parameter defines the T1 timer for CS voice over HSPA connections. The non-configurable T1 parameter with a value of 120 ms is used for other connection types.

The MaxCSDelayUE parameter defines the maximum buffering time for CS voice frames within the UE de-jittering buffer. The dejitter buffer helps to remove the impact of delay variation. The MaxCSDelayRNCETTI2 and MaxCSDelayRNCETTI2 parameters define the equivalent maximum buffering time for CS voice frames within the RNC.

The HSPAForPriEnabled parameter indicates whether or not conversational RAB capable of pre-emption can be mapped onto HSPA. The priority of the user for pre-emption is defined by the RAB pre-emption parameters. Conversational HSPA connections can trigger pre-emption, while conversational DCH and standalone SRB can trigger pre-emption of conversational HSPA users.

The existing DRRCForHSDPALayerServices parameter is updated to include a cause value of Conversational Call with F-DPCH. This parameter is applied when enhanced Directed RRC Connection Setup for HSDPA is enabled.



Version 1.1

The ServBtwnHSDPALayers parameter is introduced in RU20 and is not specific to the CS Voice over HSPA feature, i.e. it is always used when HSDPA Common Channel Layering is enabled. It specifies the connection types which should be re-directed between HSDPA layers when making the CELL_FACH to CELL_DCH transition. This parameter does not impact Directed RRC Connection Setup from RRC Idle mode.

The existing HSCAHORabCombSupport parameter is updated to include a cause value of CS AMR RAB. Allows Capability based Handover to be triggered for CS Voice over HSPA connections.

In the case of NRT-over-NRT, the RNP parameter IurPriority defines how own users and users of other RNC are prioritized. The existing PBSPolicy parameter defines the way in which the priority of the new service and existing services are used during victim selection. Victim selection also depends upon their connection allocation duration. An existing connection can only be selected as a victim if the allocation time exceeds the value of the relevant parameter: PBSHSMinAllocHigher, PBSHSMinAllocEqual, PBSHSMinAllocLower. When the potential victims are found, then a selection is done in order of QoS priority (QoSPriorityMapping) of the victims.

3.3 MIMO MIMO feature introduces the support for MIMO technology for HSDPA in DL. MIMO utilises combination of two antennas and two receive antennas (2x2 MIMO) together with BTS and MIMO pre-coding in BTS and de-coding in terminal side (see Figure 3). The pre-coding utilises channel information received from the terminal in HS-DPCCH channel.

Figure 3 MIMO architecture

BTS scheduler can transmit either same data or different data in the two parallel MIMO channels depending on the channel quality information received from the UE. There two modes are called single stream and dual stream correspondingly. With dual stream mode the BTS can transmit two different transport blocks in the parallel MIMO channels. This enables up to double data rates. This means up to 28 Mbps (see Table 15) in RU20, as the MIMO is enabled only with 16 QAM, not 64-QAM modulation. In single stream MIMO mode the same data is transmitted over the two MIMO channels and combination of transmit and receive diversity can be achieved enabling higher bit rates over radio channel.

It should be noted that MIMO utilises very distinct spatial properties of the radio channel in order to be able to separate the two different MIMO channels. These radio channel properties are highly



Version 1.1

variable and dependent on the propagation environment. Thus the maximum radio link performance can be achieved only in specific conditions. See ?? for more details on the MIMO performance.

MIMO operation has some limitations

MIMO can not be enabled simultaneously with DC-HSDPA feature and does not support 64-QAM HSDPA.

MIMO can be used only with NRT PS services, also NRT HSPA .?? MIMO is preferred over 64-QAM when both supported. Only one layer can be configured MIMO capable in the BTS.

The mobility of the UEs between the MIMO layer and the other layers is handled by combination of multiple features:

MIMO Capability Based Handover shall move MIMO UE to MIMO layer and non-MIMO UEs away from MIMO layer.

Service and load based HO, and Directed RRC connection setup (for HSDPA) do not direct any UE to MIMO layer

Directed RRC connection setup and HSPA layering for UEs in common channels features shall move non-MIMO services from the MIMO layer

Table 18 lists the required features and HW.

Requirements

UE requirements 3GPP Rel-7 (Cat-15, Cat-16, Cat-17, Cat-18) and Rel-8 (Cat-19, Cat-20) with 16-QAM only

Network Hardware Requirements Flexi Rel. 2 HW Ultrasite with EUBB Double PA units and antenna lines RNC with CDSP-DH cards HSPA Peak Rate Upgrade in RNC196 and RNC450 Feature Requirements HSUPA basic HSDPA Dynamic Resource Allocation HSDPA 14 Mbps per user Fractional DPCH Flexible RLC Continuous Packet Connectivity License RNC Capacity (Cell) license

Table 18 - Feature requirements MIMO

3.3.1 MIMO Parameters The RNC databuild parameters associated with the MIMO feature are presented in Table 19.


MIMOEnabled WCEL 0 (Disabled), 1 (Enabled) 0 1

MIMOHSDPACapaHO WCEL 0 (Disabled), 1 (Enabled) 0 0

NonMIMOPrevention WCEL 0 (Disabled), 1 (Enabled) 0 0



Version 1.1

MIMOCapaHORABSupport RNC Bit 0: PS NRT RAB,

Bit 1: 2/3 PS NRT RAB, Bit 2: PS Streaming, Bit 3: PS Stre + 1-3 PS NRT RAB, Bit 4: Other services

3 3

PtxPrimaryCPICH - WCEL -10 to 50, step 0.1 dBm 33 dBm 33 dBm MaxBitRateNRTMACDFlow - RNC 128 to 42112, step 128 kbps,

65535 (not restricted) 65535 65535

MaxIurNRTHSDSCHBitRate IUR 128 to 42112, step 128 kbps, 0 (not restricted)

0 0

Table 19 Parameters associated with the MIMO feature

The MIMOEnabled parameter enables and disables MIMO on a per cell basis. This parameter requires object locking for modification so the cell must be locked prior to enabling MIMO. The MIMOHSDPACapaHO parameter enables and disables MIMO HSDPA Capability based Handover. If this parameter is set to enabled then HSPA Capability based Handover is automatically disabled, i.e. either MIMO HSDPA Capability based Handover or HSPA Capability based Handover can be enabled. This parameter does not require object locking for modification.

The NonMIMOPrevention parameter enables and disables the functionality used to prohibit the use of non-MIMO HSDPA connections within a cell. This parameter can be set to enabled within both MIMO enabled cells and MIMO disabled cells. In the latter case, the parameter does not prohibit the use of non-MIMO connections. When the parameter is enabled within a MIMO cell then non-MIMO connections are allocated DCH rather than HS-DSCH. MIMO HSDPA Capability based Handover can then be used to move those connections onto a non-MIMO RF carrier. The NonMIMOPrevention parameter requires object locking for modification.

The MIMOCapaHORABSupport parameter is only applied if the NonMIMOPrevention parameter is enabled. In that case, the parameter defines the set of services which are targeted by MIMO HSDPA Capability based Handover, i.e. a MIMO capable UE using one of the specified services is moved onto the MIMO HSDPA RF carrier.

The PtxPrimaryCPICH parameter remains the same as for previous RAN software releases with the exception that when MIMO is enabled, it defines the transmit power of the secondary CPICH as well as the primary CPICH, i.e. it defines the CPICH transmit power from each antenna element.

The MaxBitRateNRTMacdflow parameter allows the operator to limit the maximum rate at which HSDPA data is transferred from the RNC to the Node B. In general, it is not necessary to define a limit and the default value of 65535 should be configured. The parameter has an RNC scope so any bit rate limit defined by this parameter will impact all cells parented by that RNC.

Similarly, the MaxIurNRTHSDSCHBitRate parameter allows the operator to limit the maximum rate at which HSDPA data is transferred across the Iur. In general, it is not necessary to define a limit and the default value of 0 should be configured. The parameter has an Iur scope so any bit rate limit defined only impacts connections using a specific Iur.

3.4 HSDPA 64 QAM HSDPA 64 QAM feature adds the support for 64-QAM modulation introduced in 3GPP Rel7 to HSDPA. This increases the number of transmitted bits per symbol from 4 in 16-QAM to 6 in 64-QAM, thus increasing the air-interface rate by 50% to 21 Mbps. The use of 64-QAM is supported by the UE categories 13, 14, 17 and 18. More detailed calculation of the theoretical user bit rates is presented in Section 3.1.



Version 1.1

The usage of HSDPA 64-QAM extends the range of the HSDPA link adaption to the larger transport block sizes. When channel conditions are sufficiently good, and Node B has sufficient data within its buffer, then 64QAM is selected by the link adaptation rather than 16QAM.

QPSK 16QAM 64QAM

2 bits per symbol 4 bits per symbol 6 bits per symbolpoor to moderate

channel conditionsgood

channel conditionsvery good

channel conditions

Figure 4 Signal constellations with different modulation types

The require features and HW is listed in Table 20.

Requirements

UE requirements 3GPP Rel-7; Cat-13, Cat-14, Cat-17, Cat-18 Network Hardware Requirements Flexi Rel. 2 HW Ultrasite with EUBB RNC with CDSP-DH cards HSPA Peak Rate Upgrade in RNC196 and RNC450 Feature Requirements HSUPA basic HSDPA Dynamic Resource Allocation HSDPA 16QAM HSDPA 14 Mbps per User HSDPA 15 codes QoS aware HSPA scheduling Flexible RLC License RNC ON/OFF license

Table 20 - Feature requirements HSDPA 64 QAM

3.4.1 HSDPA 64QAM Parameters The RNC databuild parameters associated with the HSDPA 64QAM feature are presented in Table 21.


HSDPA64QAMallowed WCEL 0 (Disabled), 1 (Enabled)

0 (Disabled) 1 (Enabled)

MaxBitRateNRTMacdflow - RNC 128 to 42112, step 128, 65535 (Does not Limit)

65535 (Does not Limit)

65535 (Does not Limit)

Table 21 Parameters associated with the HSDPA 64QAM feature



Version 1.1

The parameters associated with the HSDPA 64QAM feature do not offer scope for optimisation. The HSDPA64QAMallowed parameter allows the feature to be enabled/disabled on a per cell basis. The feature can be enabled using this parameter if the license exists within the RNC. It is an online parameter so does not require cell locking. The MaxBitRateNRTMacdflow parameter allows the operator to limit the maximum rate at which HSDPA data is transferred from the RNC to the Node B. In general, it is not necessary to define a limit and the default value of 65535 should be configured. The parameter has an RNC scope so any bit rate limit defined by this parameter will impact all cells parented by that RNC.

Achieving high HSDPA throughputs from the 64QAM feature relies upon having areas of good coverage. HSDPA coverage can be improved by increasing the transmit power available to HSDPA. This can be achieved by increasing the value allocated to the PtxMaxHSDPA parameter. Alternatively, HSDPA coverage can be improved by allocating an RF carrier which is dedicated to HSDPA connections, i.e. reducing the transmit power used by other connection types. In each case, the implications upon other connection types should be considered, e.g. increasing the value of PtxMaxHSDPA can generate larger rises in the downlink interference floor and thus impact the downlink coverage of speech connections.

3.5 DC-HSDPA 42Mbps The release 8 version of the specifications allows 2 adjacent channels to be combined to generate an effective HSDPA channel bandwidth of 10 MHz. This is known as Dual Cell HSDPA. RU20 implementation of Dual Cell HSDPA is based upon release 8 of 3GPP. Release 8 version of the specifications allow Dual Cell HSDPA to be combined with 64QAM but not with MIMO (Release 9 allows combination with MIMO). This version of the specification does not allow CS Voice over HSPA, Streming QoS, or non-HSUPA UEs on DC-HSDPA connections.

The combination of multiple RF carriers provides greater flexibility to the HSDPA Scheduler, i.e. the scheduler can allocated resources in the frequency domain as well as in the code and time domains. This will improve the cell and user throughputs. Figure 5 present a comparison of DC-HSDPA to single cell configuration.

Figure 5 Comparison of DC-HSDPA and single cell configuration

It should be noted that from the non DC-HSDPA UE point of view the RRM functionality remains the same.??

The require features and HW is listed in Table 22.



Version 1.1

Requirements

UE requirements 3GPP Rel-8: Cat-21 to Cat-24 Network Hardware Requirements Flexi Rel. 2 HW Ultrasite with EUBB RNC with CDSP-DH cards HSPA Peak Rate Upgrade in RNC196 and RNC450 Feature Requirements HSUPA basic HSDPA Dynamic Resource Allocation HSDPA 16QAM HSDPA 14 Mbps per User HSDPA 15 codes Flexible RLC Shared Scheduler for Baseband Efficiency License RNC capacity (cell) license

Table 22 - Feature requirements DC-HSDPA

3.5.1 DC-HSPA Parameters The RNC databuild parameters associated with the Dual Cell HSDPA feature are presented in Table 23.


DCellHSCAHORabComp RNC Bit0: PS I/B RAB (always 1) Bit1: PS Streaming Bit2: 2/3 NRT PS RAB Bit3: PS Str + 1-3 NRT PS RAB Bit4: CS AMR + 1 PS I/B RAB Bit5: CS AMR + 2/3 PS I/B RAB Bit6: CS AMR + PS Streaming Bit7: CS AMR + PS Streaming + 1-3 NRT RAB

1 1

MaxBitRateNRTMACDFlow - RNC 128 to 42112, step 128 kbps, 65535 (not restricted)

65535 65535

MaxIurNRTHSDSCHBitRate IUR 128 to 42112, step 128 kbps, 0 (not restricted)

0 0

DCellHSDPAEnabled WCEL 0 (Disabled), 1 (Enabled)

0 1

UARFCN - WCEL 0 to 16383, step 1 N/A N/A SectorID - WCEL 0 to 12, step 1 0 N/A Tcell - WCEL 0 to 9, step 1 N/A N/A MaxNumbHSDPAUsersS WCEL 1 to 511, step 1,

0 (does not limit) 0 0

Max

3g radio network planning guideline delta ru20 pdf

Documents