Configuring hsdpa and eul

Configuring HSDPA and EUL

USER GUIDE

5/1553-LZA 701 6003 Uen Y

Copyright

© Ericsson AB 2011–2015. All rights reserved. No part of this document may bereproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing. Ericsson shallhave no liability for any error or damage of any kind resulting from the useof this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.These are shown in the document Trademark Information.

5/1553-LZA 701 6003 Uen Y | 2015-05-12

Contents

Contents

1 Introduction 1

1.1 Prerequisites 1

2 Procedure 3

2.1 Planning the Configuration and Identifying RequiredHardware 3

2.2 Installing or Replacing Hardware 3

2.3 Configuring Software 3

2.4 Performing Concluding Routines 12

3 Capacity Configuration 14

3.1 Processing Resource Configuration 14

3.2 HSDPA Processing Resource Allocation 15

3.3 Number of HSDPA Codes 20

3.4 Dynamic HSDPA Code Allocation 20

3.5 Number of HSDPA Users 21

3.6 HSDPA CE Consumption 21

3.7 Number of EUL Users 22

3.8 EUL FACH HW Resources 23

3.9 Typical Configurations 23

4 HSDPA Features 29

4.1 64 QAM and MIMO Combination 29

4.2 HSDPA Incremental Redundancy 29

4.3 Enhanced Layer 2 29

4.4 Enhanced UE DRX 29

4.5 High Speed Downlink for FACH 30

4.6 HSDPA Flexible Scheduler 30

4.7 HSDPA 16 QAM 30

4.8 HSDPA 64 QAM 30

4.9 HSDPA Multi Carrier 31

4.10 HSDPA Multi Carrier Inactivity Control 31

4.11 HSDPA Multi Carrier with MIMO 32

4.12 HSDPA RBR QoS Profiling 32

5/1553-LZA 701 6003 Uen Y | 2015-05-12


4.13 Improved HSDPA Link Adaptation 32

4.14 Increased Number of HSDPA Codes for Single-CarrierUsers 32

4.15 MIMO 33

4.16 Minimum Bit Rate HSDPA 33

4.17 F-DPCH and SRB on HSDPA 33

4.18 Enhanced Downlink Reception, CPC 33

4.19 AQM based Congestion Control for HSDPA 34

4.20 Channel Element Capacity for HSDPA Smartphones 34

4.21 Increased HSDPA Code Capacity on DUW 34

4.22 HSDPA MC Inter DU Joint Scheduling 35

4.23 HSDPA Dynamic Power Sharing 35

4.24 HSDPA Multi-Carrier 3 Carriers 35

4.25 Dual-Band HSDPA Multi-Carrier 3 Carriers 35

5 EUL Features 36

5.1 Downlink Power Control for Enhanced Uplink 36

5.2 EUL 2ms TTI 36

5.3 EUL in Two Baseband Pools 36

5.4 EUL TD Scheduling 36

5.5 Per HARQ Process Grant 36

5.6 Enhanced Uplink Transmission, CPC 37

5.7 Advanced Receivers, GRAKE in RBS 38

5.8 Channel Element Capacity for EUL Smartphones 38

5.9 Enhanced Uplink Ladder E 38

5.10 UL Efficiency - DCH/EUL Load Balancing 38

5.11 Interference Suppression 38

5.12 Improved Layer 2 39

5.13 EUL on Cell FACH 39

5.14 CE Extension for EUL 39

5.15 Interference Suppression for EUL 10 ms 40

5.16 EUL Multi-Carrier 40

6 Traffic Disturbances during ConfigurationModifications 41

5/1553-LZA 701 6003 Uen Y | 2015-05-12

Introduction

1 Introduction

This document describes how to equip and configure an RBS for High-SpeedDownlink Packet Access (HSDPA) and Enhanced Uplink (EUL) for DU-basedRBS.

The document covers the following procedures:

• Adding or replacing hardware units to enable required HSDPA and EULservice

• Configuring HSDPA and EUL and related functions in the RBS software

This document does not cover how to setup the Radio Access Network (RAN)to provide HSDPA and EUL services to end users.

1.1 Prerequisites

This section contains information on the documents, tools, and conditions thatapply to the procedure.

1.1.1 Target Group

This document is intended for network engineers and field technicians, whomust have the necessary training and skills to perform the tasks.

1.1.2 Documents

Before starting the procedure, ensure that the following documents have beenread and understood:

• Personal Health and Safety Information

• System Safety Information

• Element Manager

Before starting the procedure, ensure that the following documents areavailable:

• Compatibilities for Hardware and Software

• Element Manager Wizards

• File Descriptions for Site Configuration

• Installing an Element Management Application

15/1553-LZA 701 6003 Uen Y | 2015-05-12


• Software Management

• DU-based RBS: Digital Unit Description

• DU-based RBS: Replacing Digital Units

1.1.3 Tools

The following tools can be required when performing this procedure:

• A client configured to run RBS Element Manager (EM) in accordance withInstalling an Element Management Application

• A client cable package, for example NTM 50346/100, including an Ethernetcrossover cable and a serial cable

• DU-based RBS: The required tools listed in Replacing Digital Units if digitalunits must be installed or removed

1.1.4 Conditions

Before starting the procedure, ensure that the following conditions apply:

• The IP address and the password of the RBS are available.

• All required configuration parameters are available.

• An XML configuration file for the O&M Access Wizard is available (ifapplicable).

• The required licenses are installed in the RBS.

2 5/1553-LZA 701 6003 Uen Y | 2015-05-12

Procedure

2 Procedure

This section contains instructions on how to equip the RBS with the requiredhardware and how to configure the RBS software to obtain the required HSDPAand EUL functionality.

The procedure consists of the following activities:

• Planning the configuration and identifying the correct hardware for therequired HSDPA and EUL functionality, see Section 2.1 on page 3.

• Installing or replacing hardware, see Section 2.2 on page 3.

Skip this procedure if the RBS is already equipped with the correcthardware.

• Configuring the RBS software, see Section 2.3 on page 3.

• Performing concluding routines, seeSection 2.4 on page 12.

2.1 Planning the Configuration and Identifying RequiredHardware

This section contains instructions on planning the configuration and identifyingrequired hardware.

Use the information in Section 3 on page 14 and the unit descriptions, listedin Section 1.1.2 on page 1, to plan the configuration and identify the requiredhardware for the desired functionality.

2.2 Installing or Replacing Hardware

This section contains information on how to install or replace hardware toenable required HSDPA and EUL service.

Follow the instructions in Replacing Digital Units to install or replace digital units.

2.3 Configuring Software

Configuring HSDPA and EUL can be performed from the OSS-RC. This sectiondescribes how to manually configure HSDPA and EUL in the RBS software.

More information on licenses and possible licensed levels can be found inWCDMA RAN Licenses and Hardware Activation Codes document.

35/1553-LZA 701 6003 Uen Y | 2015-05-12


To manually configure the RBS software for HSDPA and EUL, do the following:

1. Connect the client to the RBS according to Hardware MaintenanceInstructions.

2. Start the RBS EM according to Installing an Element ManagementApplication.

2.3.1 Configuring HSDPA and EUL Processing Resources

This section contains instructions on how to configure HSDPA and EULprocessing resources on High-Speed (HS) capable on DUWs(DU-based RBS).

Information on determining required number of processing resources can befound in Section 3 on page 14.

More specific information on HSDPA and EUL processing resourceconfiguration can be found in Section 3.1 on page 14.

Configuring HSDPA and EUL resources (this section) and allocating them tocells as described in Section 2.3.2 on page 5 can also be performed using theSite Equipment Configuration wizard, refer to Element Manager Wizards.

Note: When the Increased Cell Carrier Support for DUW feature isenabled, and two Baseband Pools (BBPs) are used in DUW 30,the allocation of HSDPA processing resources is based on theBBP. The DownlinkBaseBandPool::numHsCodeResourcesattribute specifies the number of HSDPA processing resource.The number of EUL processing resource is indicated by theTxDeviceGroup::staticNumEulResources attribute.

DUW 11, DUW 31, and DUW 41 have a fixed number ofHSDPA and EUL processing resources as indicated by theattributes TxDeviceGroup::staticNumHsCodeResources andTxDeviceGroup::staticNumEulResources. The numbers aredependent on the DUW variant. There is no need to manually configureHSDPA and EUL Processing Resources for DUW 11, DUW 31, andDUW 41, which means that the HS and EUL configuration can begreatly simplified for DUW 11, DUW 31, and DUW 41 compared toDUW 10, DUW 20, and DUW 30.

To configure the processing resources do the following:

1. In the RBS EM, lock the TX part of the DUW to be configured following theinstructions in Lock Board.

2. In the RBS EM, modify the attribute values in Table 1 for the DUW to beconfigured.

4 5/1553-LZA 701 6003 Uen Y | 2015-05-12

Procedure

Table 1 Attributes for Configuring HSDPA and EUL Processing Resources

Feature MO Attribute Possible Values RequiredLicense

TxDeviceGroup

numHsCodeResources

(1)(2)DUW: 0 to 4depending ontype (3)

NoneNumber of HSDPA processingresources to beconfigured onthis DUW, seeSection 3.1.1 onpage 14

DownlinkBaseBandPool

numHsCodeResources

(4)1 to 2 Increased Cell

Carrier Supportfor DUW

Number ofEUL processingresources to beconfigured onthis DUW, seeSection 3.1.2 onpage 15

TxDeviceGroup

numEulResources

(1)(2)To use thisDUW for EULprocessing, theattribute needsto be set to 1. Otherwise, itmust be set to 0.

Enhanced UplinkIntroductionPackage

(1) For DUW 11, DUW 31, and DUW 41, this attribute is not valid and has a fixed configuration, which is hiddenfrom the settings in the RBS EM.(2) When the Increased Cell Carrier Support for DUW feature is used, this attribute has no significance for DUW 30used as a primary DUW (or a single DUW).(3) To ensure the HSDPA MC Inter DU Joint Scheduling feature works normally, this attribute must be set properlydepending on the configurations. For the detailed information, see Section 3.2.4 on page 17.(4) Applicable only to DUW 30 used as a primary DUW (or a single DUW), when the Increased Cell Carrier Support forDUW feature is enabled.

The TX part of the DUW restarts.

3. In the RBS EM, unlock the TX part of the DUW, according to Unlock Board.

4. If more DUWs are to be configured, repeat Step 1 to Step 3.

Note: Always wait 2.5 minutes after a modification of a TxDeviceGroupattribute before making new modifications to the sameTxDeviceGroup or another TxDeviceGroup in the same BBpool.

2.3.2 Allocating Processing Resources

This section contains instructions on allocating HSDPA processing resourcesto specific cells.

Information about HSDPA processing resource allocation and its associatedattributes can be found in Section 3.2 on page 15.

To allocate processing resources, do the following:

1. In the RBS EM, modify the applicable attribute values listed in Table 2.

55/1553-LZA 701 6003 Uen Y | 2015-05-12


Table 2 Attributes for Allocating Processing Resources


Processingresource allocation steered orautomatic, seeSection 3.2 onpage 15

NodeBFunction

steeredHsAllocation

(1) (2) (3)True

False

None

Processingresource IDof the HSDPAprocessingresource to beallocated tothis cell, only ifsteered resourceallocation isused, seeSection 3.2 onpage 15

RbsLocalCell

for each cell

hsCodeResourceId

(1) (2)(3)DU-based RBS:0 to 4

0 disablesHSDPA and EULin the cell.

None

(1) For DUW 11, DUW 31, and DUW 41, this attribute has no significance since the function steered HS allocation isnot implemented. The attribute is hidden from the settings in the RBS EM.(2) This attribute has no significance when the HSDPA Multi Carrier Inter DU Joint Scheduling feature.(3) This attribute is not recommended to be used for the primary DUW (or single DUW) where the Increased Cell CarrierSupport for DUW feature is used. If the Increased Cell Carrier Support for DUW feature and the HSDPA MC Inter DUJoint Scheduling feature are used together on a primary DUW ( or a single DUW), this attribute is not significance.

2.3.3 Configuring Number of Codes and Users

This section contains instructions on configuring the number of HSDPA codes,HSDPA users, and EUL users.

Detailed information on the number of codes and users can be found in Section3 on page 14.

To configure the number of codes and users, do the following:


6 5/1553-LZA 701 6003 Uen Y | 2015-05-12

Procedure

Table 3 Attributes for Configuring Number of Codes and Users


HSDPA Codesper cell, seeSection 3.3 onpage 20

RbsLocalCell

for each cell

maxNumHsPdschCodes

5 to 15 More than 5codes for eachcell requires:

HSDPA Codesper cell

Dynamic HSDPACode Allocation,see Section 3.4on page 20

RbsLocalCell

for each cell

featureStateHsdpaDynamicCodeAllocation

ACTIVATED

DEACTIVATED

HSDPA DynamicCode Allocation

IncreasedNumber ofHSDPA Codesfor Single-CarrierUsers, seeSection 3.3 onpage 20

NodeBFunction

featureStateIncrNumHsCodes

ACTIVATED

DEACTIVATED

IncreasedNumber ofHSDPA Codesfor Single-CarrierUsers

HSDPA Usersper cell, seeSection 3.5 onpage 21

RbsLocalCell

for each cell

maxNumHsdpaUsers

1 to 128 More than 16users for eachcell requires:

HSDPA Usersper cell

Maximumamount of CEsthat can bereserved forA-DCH in the BBpool, see Section3.6 on page 21

DownlinkBasebandPool

for each BB pool

maxNumADchReservation

0 to 512 None

EUL Users percell, see Section3.7 on page 22

RbsLocalCell

for each cell

maxNumEulUsers

1 to 96 More than 4users for eachcell requires:

EUL Users percell

IncreasedHSDPA CodeCapacityon DUW,seeSection 3.3on page 20 andSection 4.21 onpage 34

NodeBFunction

featureStateIncreasedHsCodeCap

ACTIVATED

DEACTIVATED

IncreasedHSDPA CodeCapacity onDUW

75/1553-LZA 701 6003 Uen Y | 2015-05-12


2.3.4 Configuring HSDPA and EUL Features

This section contains instructions on configuring HSDPA and EUL features.

Detailed information on HSDPA and EUL features can be found in Section 4 onpage 29 and Section 5 on page 36.

To configure HSDPA and EUL features, do the following:


Table 4 Attributes for Configuring HSDPA and EUL Features

Feature MO Class Attribute Possible Values RequiredLicense

64QAM andMIMO Combination, see Section4.1 on page 29

RbsLocalCell featureState64QamMimo

ACTIVATED

DEACTIVATED

64QAM andMIMO Combination

HSDPAIncrementalRedundancy,see Section 4.2on page 29

RbsLocalCell

for each cell

featureStateHsdpaIncrementalRedundancy

ACTIVATED

DEACTIVATED

HSDPA Incremental Redundancy

Enhanced Layer2, see Section4.3 on page 29

RbsLocalCell

for each cell

featureStateEnhancedLayer2

ACTIVATED

DEACTIVATED

Enhanced Layer2

Enhanced UEDRX, seeSection 4.4 onpage 29

RbsLocalCell featureStateEnhUeDrx

ACTIVATED

DEACTIVATED

Enhanced UEDRX

High SpeedDownlink forFACH

High SpeedDownlink forFACH, seeSection 4.5 onpage 30

RbsLocalCell featureStateHsFach

ACTIVATED

DEACTIVATED

High SpeedDownlink forFACH

Enhanced Layer2

HSDPA FlexibleScheduler, seeSection 4.6 onpage 30

NodeBFunction

featureStateHsdpaFlexibleScheduler

ACTIVATED

DEACTIVATED

HSDPA FlexibleScheduler

8 5/1553-LZA 701 6003 Uen Y | 2015-05-12

Procedure



Schedulingalgorithm(HSDPA FlexibleScheduler), seeSection 4.6 onpage 30

RbsLocalCell

for each cell

queueSelectAlgorithm

ROUND_ROBIN

PROPORTIONAL_FAIR_MEDIUM

EQUAL_RATE

MAXIMUM_CQI

PROPORTIONAL_FAIR_HIGH

PROPORTIONAL_FAIR_LOW

EQUAL_RATE

MAXIMUM_CQI

PROPORTIONAL_FAIR_HIGH

PROPORTIONAL_FAIR_LOWrequires:

HSDPA FlexibleScheduler

HSDPA 16 QAM,see Section 4.7on page 30

NodeBFunction

featureState16Qam

ACTIVATED

DEACTIVATED

HSDPA 16 QAM

HSDPA 64 QAM,see Section 4.8on page 30

NodeBFunction

featureState64Qam

ACTIVATED

DEACTIVATED

HSDPA 64 QAM

HSDPA MultiCarrier, seeSection 4.9 onpage 31

RbsLocalCell

for each cell

featureStateHsdpaMc

ACTIVATED

DEACTIVATED

HSDPA MultiCarrier

HSDPA MultiCarrier InactivityControl, seeSection 4.10 onpage 31

RbsLocalCell

for each cell

featureStateHsdpaMcInactCtrl

ACTIVATED

DEACTIVATED

HSDPA MultiCarrier InactivityControl

HSDPA MultiCarrier withMIMO, seeSection 4.11 onpage 32

RbsLocalCell featureStateHsdpaMcMimo

ACTIVATED

DEACTIVATED

HSDPA MultiCarrier withMIMO

HSDPA RBRQoS Profiling,see Section 4.12on page 32

NodeBFunction

featureStateHsdpaRbrQosProfiling

ACTIVATED

DEACTIVATED

HSDPA RBRQoS Profiling

ImprovedHSDPA LinkAdaptation, seeSection 4.13 onpage 32

NodeBFunction

featureStateHsdpaImprovedLinkAdaptation

ACTIVATED

DEACTIVATED

ImprovedHSDPA LinkAdaptation

95/1553-LZA 701 6003 Uen Y | 2015-05-12




Multiple InputMultiple Output(MIMO), seeSection 4.15 onpage 33

RbsLocalCell featureStateMimo

ACTIVATED

DEACTIVATED

Multiple InputMultiple Output

Minimum BitRate HSDPA,see Section 4.16on page 33

NodeBFunction

featureStateHsdpaMinBitRate

ACTIVATED

DEACTIVATED

Minimum BitRate HSDPA

F-DPCH andSRB on HSDPA,see Section 4.17on page 33

RbsLocalCell

for each cell

featureStateFDpchSrbOnHsdpa

ACTIVATED

DEACTIVATED

F-DPCH andSRB on HSDPA

HSDPA MCInter DU JointScheduling, seeSection 4.22 onpage 35

NodeBFunction

featureStateHsdpaMcInterDuJointSched

ACTIVATED

DEACTIVATED

HSDPA MCInter DU JointScheduling

HSDPA DynamicPower Sharing,see Section 4.23on page 35

RbsLocalCell featureStateHsdpaPowerSharing

ACTIVATED

DEACTIVATED

HSDPA DynamicPower Sharing

HSDPA Multi-Carrier 3 Carriers,see Section 4.24on page 35

RbsLocalCell featureStateHsdpa3Mc

ACTIVATED

DEACTIVATED

HSDPA Multi-Carrier 3 Carriers

Dual-BandHSDPA Multi-Carrier 3 Carriers,see Section 4.25on page 35

RbsLocalCell featureStateHsdpaDb3Mc

ACTIVATED

DEACTIVATED

Dual-BandHSDPA Multi-Carrier 3 Carriers

Downlink PowerControl forEnhancedUplink, seeSection 5.1 onpage 36

NodeBFunction

featureStateDlPowerControlEul

ACTIVATED

DEACTIVATED

Downlink PowerControl forEnhanced Uplink

EUL 2ms TTI,see Section 5.2on page 36

NodeBFunction

featureStateEul2msTTI

ACTIVATED

DEACTIVATED

EUL 2ms TTI

10 5/1553-LZA 701 6003 Uen Y | 2015-05-12

Procedure



EUL in 2Baseband Pools,see Section 5.3on page 36

NodeBFunction

featureStateEulForLargeRbsConfig

ACTIVATED

DEACTIVATED

EUL ForLarge RBSConfigurations

EUL TDScheduling, seeSection 5.4 onpage 36

RbsLocalCell featureStateEulTdScheduling

ACTIVATED

DEACTIVATED

EUL TDScheduling

NodeBFunction

featureStatePerHarqProcessGrant

ACTIVATED

DEACTIVATED

Per HARQProcess Grant,see Section 5.5on page 36 NodeBFunctio

neul2msFirstSchedStep

20,160

Per HARQProcess Grant

RbsLocalCell featureStateCpc

ACTIVATED

DEACTIVATED

Enhanced UplinkTransmission,ContinuousPacket Connectivity (CPC),see Section5.6 on page37, EnhancedDownlinkReception, CPC,see Section 4.18on page 33

RbsLocalCell cpcCapability

CPC_CAPABLE

CPC_NON_CAPABLE

CPC

AdvancedReceivers,GRAKE in RBS,see Section 5.7on page 38

NodeBFunction

featureStateGrake

ACTIVATED

DEACTIVATED

AdvancedReceivers,GRAKE in RBS

ChannelElementCapacity for EULSmartphones,see Section 5.8on page 38

NodeBFunction

featureStateCeCapEul

ACTIVATED

DEACTIVATED

-

InterferenceSuppression,see Section 5.11on page 38

NodeBFunction

featureStateInterferenceSuppression

ACTIVATED

DEACTIVATED

InterferenceSuppression

Improved Layer2, see Section5.12 on page 39

RbsLocalCell featureStateImprovedLayer2

ACTIVATED

DEACTIVATED

Improved Layer2

115/1553-LZA 701 6003 Uen Y | 2015-05-12




EUL on CellFACH, seeSection 5.13 onpage 39

RbsLocalCell featureStateEulFach

ACTIVATED

DEACTIVATED

EUL on CellFACH

CE Extension forEUL, see Section5.14 on page 39

NodeBFunction

featureStateCeExtForEul

ACTIVATED

DEACTIVATED

CE Extension forEUL

InterferenceSuppressionfor EUL 10ms(Section 5.15on page 40)

NodeBFunction

featureStateIntSuppEul10ms

ACTIVATED

DEACTIVATED

InterferenceSuppression forEUL 10 ms

Supported as ofrelease W13.0

EUL Multi-Carrier, see Section5.16 on page 40

RbsLocalCell featureStateEulMc

ACTIVATED

DEACTIVATED

EUL Multi-Carrier

2.4 Performing Concluding Routines

This section describes actions to be performed before leaving the site.

2.4.1 Verifying the New Configuration

To verify that the new configuration is successfully implemented, do thefollowing:

1. Connect the client to the RBS.

2. Start the RBS EM.

3. In the RBS EM, check that the operationalState attribute value isENABLED for recently installed units.

4. Open the alarm list in the RBS EM and check for alarms. If alarms arepresent, follow the relevant Alarm Operating Instructions.

5. Create a new CV and set it to Startable, refer to Software Management.

2.4.2 Securing and Leaving the Site

Before leaving the site, do the following:

1. Exit the RBS EM, disconnect the client and collect all tools.

12 5/1553-LZA 701 6003 Uen Y | 2015-05-12

Procedure

2. Disconnect the Electrostatic Discharge (ESD) wrist strap from the earthgrounding point.

3. Update the Site Installation Documentation with the changes performedon the RBS configuration.

4. Close and lock the RBS cabinet door.

5. Complete the work order.

6. Secure the site.

After leaving the site, follow the procedures for the return and disposal ofreplacement parts.

135/1553-LZA 701 6003 Uen Y | 2015-05-12


3 Capacity Configuration

This section contains information on how capacity configuration works,attributes related to capacity configuration and licenses required for capacityconfiguration.

3.1 Processing Resource Configuration

This section describes the configuration of HSDPA and EUL processingresources on DUWs.

For RBSs with two DUWs, the processing resources must be configuredseparately for each DUW. More information on how the boards are divided intoBBPs, refer to RBS Configurations.

The Increased Cell Carrier Support for DUW feature enables up to 12 cellcarriers on one DUW, by dividing the BB hardware into two logical BBPs. Whenthis feature is enabled, the processing resources are divided equally betweentwo BBPs on the DUW automatically. For DUW 30 used as a primary DUW (ora single DUW), the HSDPA processing resources are configured for each BBP.

3.1.1 HSDPA Processing Resources

A DUW can be configured with a different number of HSDPA processingresources depending on the variant. Details for each variant can be foundin the DU description documents, listed in Section 1.1.2 on page 1. Thenumber of resources to be configured for each DUW is controlled by theTxDeviceGroup::numHsCodeResources attribute. Each configuredprocessing resource decreases the total Channel Element (CE) capacityavailable for R99, see Section 3.6 on page 21.

For DUW 30 used as a primary DUW (or a single DUW), whenthe Increased Cell Carrier Support for DUW feature is enabled, theHSDPA processing resource is allocated based on the BB pool. TheDownlinkBaseBandPool::numHsCodeResources attribute specifies thenumber of HSDPA processing resource. For detailed information, refer toWCDMA RAN Increased Cell Carrier Support for DUW document.

For DUW 11, DUW 31, and DUW 41, the number of HSDPA processingresources is fixed and depends on the DUW variant. The attributeTxDeviceGroup::staticNumHsCodeResources indicates this numberof resources, with the value 1, 6 and 6 for DUW 11, DUW 31, and DUW 41respectively. For details of DUW 11, DUW 31, and DUW 41, refer to DigitalUnit Description.

14 5/1553-LZA 701 6003 Uen Y | 2015-05-12

Capacity Configuration

3.1.2 EUL Processing Resources

One DUW in an RBS can be configured with an EUL processing resource. Thisis controlled by the TxDeviceGroup::numEulResources attribute.

There must be at least one HSDPA processing resource configured in thesame BB pool where the EUL resource is configured.

The use of EUL requires the Enhanced Uplink Introduction Package license.

The use of two DUWs requires the EUL For Large RBS Configurations license.

For DUW 11, DUW 31, and DUW 41, the number of EUL processingresources is fixed and depends on the DUW variant. The attributeTxDeviceGroup::staticNumEulResources indicates this number ofresources, with the value 1, 1 and 1 for DUW 11, DUW 31, and DUW 41respectively. For details of DUW 11, DUW 31, and DUW 41, refer to DigitalUnit Description.

For DUW 30, DUW 31, and DUW 41 used as a primary DUW (or a single DUW),and when the Increased Cell Carrier Support for DUW feature is enabled, theTxDeviceGroup::numEulResources attribute is ignored. Instead, theTxDeviceGroup::staticNumEulResources attribute with the value 2, isused to reflect the number of EUL processing resources configured for theDUWs. Each BBP is automatically granted one EUL processing resource. Fordetailed information, refer to WCDMA RAN Increased Cell Carrier Support forDUW document.

3.2 HSDPA Processing Resource Allocation

Allocating HSDPA processing resources to specific cells can be done in twoways: steered allocation and automatic allocation.

Note: For DUW 11, DUW 31, and DUW 41, automatic allocation is alwaysused and enabled by default, see Section 3.2.2 on page 16. Thefunction steered HS allocation is not implemented since it is not neededfor DUW 11, DUW 31, and DUW 41.

When the feature HSDPA MC Inter DU Joint Scheduling is activated,automatic allocation is always used.

When the Increased Cell Carrier Support for DUW feature is enabled,steered allocation is not recommended. For the primary DUW (or asingle DUW) where the Increased Cell Carrier Support for DUW featureis used together with the HSDPA MC Inter DU Joint Scheduling feature,automatic allocation is always used.

Using steered allocation is recommended for configurations where the numberof HSDPA codes differ between the configured cells.

155/1553-LZA 701 6003 Uen Y | 2015-05-12


3.2.1 Steered Allocation

Steered allocation enables the allocation of specific HSDPA processingresources to one or several specific cells in the same DUW. HSDPA processingresources on a DUW can be shared by up to six cells.

In DU-based RBS if there are two HSDPA processing resources configured ona DUW and there are six cells connected to this DUW, the allocation can beconfigured as demonstrated in example in Table 5.

Table 5 Steered Configuration Example for DU-based RBS

DUW Processing Resource Cell

1 1, 2, 3, 41

2 5, 6

Steered allocation is enabled by setting the NodeBFunction::steeredHsAllocation attribute value to True. In the steered allocation mode, cell carriersin one combined cell must use the same HSDPA code resource, that is, thevalue of hsCodeResourceId attribute must be the same.

For a DU-based RBS, the processing resources are assigned ID numbersfrom 1 to value of the TxDeviceGroup::numHsCodeResources attributefor that DUW.

The RbsLocalCell::hsCodeResourceId attribute value is set to the IDnumber of the HSDPA processing resource to be used for that cell, or to 0 todisable HSDPA and EUL in the cell.

3.2.2 Automatic Allocation

Automatic allocation allows the RBS to automatically distribute the availableHSDPA processing resources over all cells in the same BB pool or DUW, tomaximize load sharing.

Automatic allocation is enabled by setting the NodeBFunction::steeredHsAllocation attribute value to False.

3.2.3 Automatic Allocation for Multi Carrier

If the Multi Carrier feature is activated in any of the cells in the RBS, the processof automatic allocation is modified. In this case automatic allocation by theRBS places the configured HSDPA cells configured in the same sector onthe same HSDPA processing resource. If automatic configuration for the MultiCarrier cannot be resolved, the RBS distributes the cells over the availableHSDPA processing resources to maximize load sharing.

16 5/1553-LZA 701 6003 Uen Y | 2015-05-12


Note: The configured HSDPA cells can be combined cells residing in multiplesector or cells belonging to one sector. For the concept of combinedcell, refer to WCDMA RAN Combined Cell document. For the combinedcell, on condition that one of its sectors is the same as the sector ofother cells, the automatic allocation assigns these cells to the sameHSDPA processing resource.

It is recommended that the number of sectors is the same as the number ofHSDPA processing resources when automatic allocation is used for the MultiCarrier feature.

There is a possibility that Multi Carrier configuration cannot be used and allsectors cannot obtain Multi Carrier configuration if there are not enough HSDPAprocessing resources. In these cases it is recommended to unlock the HsDschManaged Objects (MOs) in the Radio Network Controller (RNC) related tothe sectors with multiple carriers first and then the HsDsch MOs in the RNCrelated to the sectors with a single carrier. This action ensures the allocationof resources to sectors with multiple carriers first.

Changing the featureStateHsdpaMc attribute does not trigger Multi Carrierreconfiguration. The operator must lock and unlock the HsDsch MO in theRNC to start the reconfiguration. It is possible to observe the outcome of thereconfiguration in the hsdpaMcCapability read-only attribute in the RBS. Noalarms are generated if Multi Carrier configuration fails.

3.2.4 Automatic Allocation for HSDPA Multi Carrier Inter DU JointScheduling

If the HSDPA Multi Carrier Inter DU Joint Scheduling feature is activated in theRBS, the automatic allocation performed by the RBS places the configuredHSDPA cells according to Table 6, Table 7 and Table 8. For the configurationsin the tables, cells that belong to the same sector, sectorGroup, or both arespread across different HS processing resources. This means that if a MC useris scheduled on both the serving cell and the secondary serving cell and thetwo cells are handled by different HS processing resources, the L1 user datacoding for both the serving cell and the secondary serving cell is performed onthe HS processing resource on which the serving cell is allocated. Thereforecode resources must also be reserved for cells belonging to the same sector,sectorGroup, or both but handled by another HS processing resource. TheL1 resources for the secondary serving cell will in these cases be denotedwith ‘s’ in the tables and in the following figure showing a 3x2 configurationon 2xDUWv1.

175/1553-LZA 701 6003 Uen Y | 2015-05-12


s1, f1 (f2 s)

s2, f1 (f2 s)

s3, f1 (f2 s)

s1, (f1 s) f2

s2, (f1 s) f2

s3, (f1 s) f2

U0001027A

Figure 1 Example of HSDPA Processing Resource allocation with HSDPAMC Inter DU Joint Scheduling

InTable 6, Table 7 and Table 8 , L1 resources for secondary serving cells aredenoted with an ‘s’ while cells handled by the same HS processing resourcesas where the L1 coding are performed are denoted ‘p’. The maximum numberof possible HS codes in each used HS processing resource(when 15 codesare used per cell) is also listed in the tables. Note that NodeBFunction andRbsLocalCell only reflects cells that is handled by the specific HS processingresource (denoted ‘p’ in the tables).

Table 6 Resource allocation per DUW for 2×DUW configurations (part 1)

#HS resourcesper DUW

3x2 or 3x1 + 3x1Dual Band withor without 4-RXdiversity

3x4 or 3x3 + 3x1Dual Band or 3x2 +3x2 Dual Band

2x4 or 2x3 + 2x1Dual Band or 2x2 +2x2 Dual Band

3x3 or 3x2 + 3x1Dual Band(1stDUW)

3x3 or 3x2 + 3x1Dual Band(2ndDUW)

Cells Cells Cells Cells Cells

6 S1 1p+1sS2 1p+1sS3 1p+1s---

S1 1p+3sS1 1p+3sS2 1p+3sS2 1p+3sS3 1p+3sS3 1p+3s

S1 1p+3sS1 1p+3sS2 1p+3sS2 1p+3s--


S1 1p+2sS2 1p+2sS3 1p+2s---

4 S1 1p+1sS2 1p+1sS3 1p+1s-

S1 2p+2sS2 2p+2sS3 2p+2s-

S1 1p+3sS1 1p+3sS2 1p+3sS2 1p+3s

S1 2p+1sS2 2p+1sS3 2p+1s-

S1 1p+2sS2 1p+2sS3 1p+2s-

3 S1 1p+1sS2 1p+1sS3 1p+1s

S1 2p+2sS2 2p+2sS3 2p+2s

S1 2p+2sS2 2p+2s-

S1 2p+1sS2 2p+1sS3 2p+1s

S1 1p+2sS2 1p+2sS3 1p+2s

2 S1,S2(1p+1s)S3 1p+1s

- S1 2p+2sS2 2p+2s

S1,S2(2p+1s)S3(2p+1s)

S1,S2(1p+2s)S3(1p+2s)

1 S1,S2,S3(1p+1s) - - - -

Table 7 Resource allocation per DUW for 2xDUW configurations (part 2)


4x2 or 4x1 + 4x1 DualBand



Cells Cells Cells

18 5/1553-LZA 701 6003 Uen Y | 2015-05-12


Table 7 Resource allocation per DUW for 2xDUW configurations (part 2)

6 S1 1p+1sS2 1p+1sS3 1p+1sS4 1p+1s--

S1 1p+1sS2 1p+1sS3 1p+1sS4 1p+1sS5 1p+1s-


4 S1 1p+1sS2 1p+1sS3 1p+1sS4 1p+1s

S1,S2(1p+1s)S3 1p+1sS4 1p+1sS5 1p+1s

S1,S2(1p+1s)S3,S4(1p+1s)S5 1p+1sS6 1p+1s

3 S1,S2(1p+1s)S3 1p+1sS4 1p+1s

S1,S2(1p+1s)S3,S4(1p+1s)S5 1p+1s

S1,S2(1p+1s)S3,S4(1p+1s)S5,S6(1p+1s)

2 S1,S2(1p+1s)S3,S4(1p+1s)

S1,S2,S3(1p+1s)S4,S5(1p+1s)

S1,S2,S3(1p+1s)S4,S5,S6(1p+1s)

1 - - -

Table 8 Resource allocation per DUW for 1xDUW configurations


1x4 or 1x3 + 1x1 DualBand or 1x2 + 1x2Dual Band



Cells Cells Cells

6 S1 1p+3sS1 1p+3sS1 1p+3sS1 1p+3s--

S1 1p+2sS1 1p+2sS1 1p+2s---

S1(1p+2s)S1(1p+2s)S1(1p+2s)S2(1p+2s)S2(1p+2s)S2(1p+2s)

4 S1 1p+3sS1 1p+3sS1 1p+3sS1 1p+3s

S1 1p+2sS1 1p+2sS1 1p+2s-

S1(2p+1s)S1(1p+2s)S2(2p+1s)S2(1p+2s)

3 S1 2p+2sS1 1p+3sS1 1p+3s

S1 1p+2sS1 1p+2sS1 1p+2s

S1,S2(1p+2s)S1,S2(1p+2s)S1,S2(1p+2s)

2 S1 2p+2sS1 2p+2s

S1 2p+2sS1 1p+2s

S1 3pS2 3p

1 S1 4p S1 3p S1,S3(3p)

195/1553-LZA 701 6003 Uen Y | 2015-05-12


3.3 Number of HSDPA Codes

A maximum of 15 HSDPA codes can be used in each cell. This number isalso dependent on processing resource configurations and installed licensesas indicated in this section.

To configure more than 20 HSDPA codes shared by two cells for single-carrierusers, the Increased Number of HSDPA Codes for Single-Carrier Users licenseis required.

To configure more than 15 HSDPA codes shared by two cells for single-carrierMIMO dual stream users, the Increased Number of HSDPA Codes forSingle-Carrier Users license is required.

For DU-based RBSs, each HSDPA processing resource supports up to 30codes to be shared by up to six cells.

To increase the number of HS codes for each HSDPA processing resource forDU-based RBSs, the Increased HSDPA Code Capacity on DUW license isrequired.

It changes the maximum number of HS codes as follows:

• from 30 to 60 codes for DUW 10, DUW 20, DUW 30 and DUW 31, DUW 41

• from 30 to 90 codes for DUW 11

The maximum number of HSDPA codes that can be allocated to each cell isdetermined by the RbsLocalCell::maxNumHsPdschCodes attribute.

To configure more than five HSDPA codes in a cell, the HSDPA Codes per celllicense with the required number of codes is necessary. The number of HSDPAcodes allocated to a specific cell is fixed. This means that a cell requiringmore codes than allocated cannot use currently unused codes allocated toother cells. To allow code sharing between cells, the HSDPA Dynamic CodeAllocation feature, described in Section 3.4 on page 20, can be used.

For configurations used when the feature HSDPA MC Inter DU Joint Schedulingis active, the number of required codes per configuration can be found inSection 3.2.4 on page 17.

3.4 Dynamic HSDPA Code Allocation

Dynamic HSDPA Code Allocation allows a cell to use HSDPA codes currentlynot used in other cells that share the same HSDPA processing resource.However, a cell can still not use more than a total of 15 codes at a time.

For DU-based RBSs, 30 codes can be shared between the two cells in asimilar way. For more examples, see the typical configurations in Section 3.9on page 23 using Dynamic HSDPA Code Allocation. The number of additional

20 5/1553-LZA 701 6003 Uen Y | 2015-05-12


HSDPA codes that can be used in this way also depends on the number ofchannelization codes used by other channels in the cell.

However, when the feature HSDPA MC Inter DU Joint Scheduling is activated,the number of required codes will increase according to Section 3.2.4 on page17. The dynamic HSDPA Code Allocation will consider codes for both servingcells and secondary serving cells when the feature HSDPA Inter DU JointScheduling is activated.

The RbsLocalCell::featureStateHsdpaDynamicCodeAllocationattribute controls if the feature is enabled. The HSDPA Dynamic CodeAllocation license is required.

Activating the feature Increased HSDPA Code Capacity on DUW for DU-basedRBS, the number of codes for each HSDPA processing resource can beincreased as follows:



The cases when it is possible to share codes between cells on an HSDPAprocessing resource are diminished. With more codes available for eachHSDPA processing resource, code sharing is only needed when more than fourcells are configured on an HSDPA processing resource.

3.5 Number of HSDPA Users

For DU-based RBSs, each resource supports up to 128 users. For RBS 6501,only 64 users are supported for each resource.

The maximum number of HSDPA users that a cell is allowed to serve isdetermined by the value of the RbsLocalCell::maxNumHsdpaUsersattribute.

To configure more than 16 HSDPA users in a cell, the HSDPA Users per celllicense with the required number of users is necessary.

3.6 HSDPA CE Consumption

The amount of CE reserved for HSDPA users is taken from the R99 DedicatedChannel (DCH) resources. This section describes how to determine the amountof CE reserved by default and how to limit this amount.

For RBSs with two BB pools the board slot positions determine how CEs areallocated for each BB pool.

215/1553-LZA 701 6003 Uen Y | 2015-05-12


3.6.1 CE Consumption in DU-based RBSs

By default, the amount of CE that is reserved for HSDPA in a DUW equals thelowest of the following:

• 0.5 × 1.3 × sum of the values of the RbsLocalCell::maxNumHsdpaUsersattributes for all cells.

• 0.5 × 1.3 × number of configured HSDPA processing resources × themaximum HSDPA users supported by each HSDPA processing resource

Note: When calculating the amount of HSDPA processing resourcethat is served for HSDPA in a DUW for a combined cell, the0.5 factor in the equations above is changed to 1. The value ofRbsLocalCell::maxNumHsdpaUsers attribute needs to be set to alower value, to ensure that the capacity is enough for R99. For moreinformation, refer to WCDMA RAN Combined Cell document.

If the value of the RbsLocalCell::maxNumHsdpaUsers attribute isset higher than the HSDPA Users per cell license currently allows,the licensed value is used.

The 1.3 factor is applied to provide a capacity margin for soft handovers.

A DUW can be configured as described in the following example:

• Three cells are configured with RbsLocalCell::maxNumHsdpaUsersall set to 16.

• One HSDPA processing resource is used.

• The licensed value of HSDPA Users per cell is 32.

The reserved amount is by default the lowest of 0.5 ×1.3 × (16 + 16 + 16) = 32and 0.5 ×1.3 × 1 × 128 = 83, that is 32 CEs.

3.6.2 CE Consumption Limitation

To free resources for R99 DCH traffic and limit the number of CEs reserved forHSDPA in a DUW, the DownlinkBaseBandPool::maxNumADchReservation attribute can be used. The value of this attribute is the maximum amount ofCEs that can be reserved for A-DCH in the DUW. Reducing the attribute belowthe default reservation level frees resources for R99 DCH traffic.

3.7 Number of EUL Users

The maximum number of EUL users for each cell is 96. EUL can be configuredin two DUWs if the EUL in 2 BB pools feature is activated. The maximum totalnumber of EUL users for each BB pool is 256.

22 5/1553-LZA 701 6003 Uen Y | 2015-05-12


The maximum number of EUL users in a cell is determined by the value of theRbsLocalCell::maxNumEulUsers attribute. To configure more than fourEUL users in a cell, the EUL Users per cell license with the required numberof users is necessary.

When the EUL Multi-Carrier feature is activated, the secondary UL carrier istreated as one user.

3.8 EUL FACH HW Resources

The maximum number of HW resources for EUL FACH for each cell isdetermined by MOM parameter eulFachNumOfDecoders. The parameterdimensions the number of UEs that can transmit data on EUL FACHsimultaneously in a cell.

3.9 Typical Configurations

This section contains some typical configurations.

3.9.1 DU-based RBSs

The examples in Table 9, Table 10 and Table 11 show configurations forDUW 10, DUW 20, and DUW 30. For DUW 11, DUW 31, and DUW 41, thecalculations are done in exactly the same way, although the capacity figures aredifferent and the number of processing resources is fixed. For DUW 11, DUW31, DUW 41, and the internal DU in RBS 6501, the number of CE available forR99 is 65, 643, 643, and 54 CE respectively, see Table 12 and Table 11. Fordetails of DUW 11, DUW 31, and DUW 41, refer to Digital Unit Description.

235/1553-LZA 701 6003 Uen Y | 2015-05-12


Table 9 Configuration 1

HSDPA Codes Cell 1-3: 1 code/cell + 27 codes dynamicallyshared. The number of available codes percell varies between 1 and 15.

Cell 4-6: 1 code/cell + 27 codes dynamicallyshared. The number of available codes percell varies between 1 and 15.

HSDPA Users 32 users/cell

EUL Users 16 users/cell

Processing Resources HSDPA: 2 (One allocated to cells 1-3, oneallocated to cells 4-6). Both resources areconfigured on the same DUW.

EUL: 1

CE Available for R99 DUW 20: 131 CE

DUW 30: 515 CE

Required Licenses HSDPA Dynamic Code Allocation

HSDPA Codes per cell

HSDPA Users per cell

Enhanced Uplink Introduction Package

EUL Users per cell

Cell 1

Cell 2

Cell 3

Cell 4 Cell 5

Cell 6

32 HSDPAusers

1 HSDPAcode

1 HSDPAcode

1 HSDPAcode

1 HSDPAcode

1 HSDPAcode

131/515 CE

27HSDPAcodes

1 HSDPAcode

27HSDPAcodes

32 HSDPAusers

32 HSDPAusers

32 HSDPAusers

32 HSDPAusers

32 HSDPAusers

16 EULusers

16 EULusers

16 EULusers

16 EULusers

16 EULusers

16 EULusers

SK0000708A


HSDPA Codes 5 codes/cell



Processing Resources HSDPA: 1

EUL: 1


DUW 20: 321 CE

DUW 30: 705 CE

Required Licenses Enhanced Uplink Introduction Package

EUL Users per cell

Cell 1

Cell 2

Cell 3

Cell 4

Cell 5

Cell 6

5 HSDPAcodes

16 HSDPAusers

5 HSDPAcodes

16 HSDPAusers

5 HSDPAcodes

16 HSDPAusers

65/321/705 CE

SK0000714A

16 EULusers

16 EULusers

5 HSDPAcodes

16 HSDPAusers

16 EULusers

5 HSDPAcodes

16 HSDPAusers

16 EULusers

5 HSDPAcodes

16 HSDPAusers

16 EULusers

16 EULusers

24 5/1553-LZA 701 6003 Uen Y | 2015-05-12



HSDPA Codes 2 codes/cell + 18 codes dynamically shared.The number of available codes per cell variesbetween 2 and 15.




EUL: 1


DUW 20: 321 CE

DUW 30: 705 CE

DUW 11: 65 CE

Internal DU in RBS 6501: 54 CE(1)

Required Licenses HSDPA Dynamic Code Allocation

HSDPA Codes per cell


EUL Users per cell


Cell 1

Cell 2

Cell 3

Cell 4

Cell 5

Cell 6

2 HSDPAcodes

16 HSDPAusers

2 HSDPAcodes

16 HSDPAusers

2 HSDPAcodes

16 HSDPAusers

65/321/705 CE

SK0000715A

16 EULusers

16 EULusers

2 HSDPAcodes

16 HSDPAusers

16 EULusers

2 HSDPAcodes

16 HSDPAusers

16 EULusers

2 HSDPAcodes

16 HSDPAusers

16 EULusers

16 EULusers

18 HSDPA codes

(1) The DL capacity of the internal DU in the RBS 6501 is 96 CE.






EUL: 1


DUW 41: 643 CE

Required Licenses HSDPA Codes per cell



EUL Users per cell

Cell 1

Cell 2

Cell 3

Cell 4

Cell 5

Cell 6

15 HSDPAcodes

32 HSDPAusers

15 HSDPAcodes

32 HSDPAusers

15 HSDPAcodes

32 HSDPAusers

643/643 CE

SK0000716B

16 EULusers

16 EUL users

15 HSDPAcodes

32 HSDPAusers

16 EUL users

15 HSDPAcodes

32 HSDPAusers

16 EUL users

15 HSDPAcodes

32 HSDPAusers

16 EULusers

16 EUL users

255/1553-LZA 701 6003 Uen Y | 2015-05-12


The examples in Table 13 and Table 15 show configurations for DUW 30, DUW31, and DUW 41 with the Increased Cell Carrier feature used. The example inTable 14 shows the configuration for DUW 30, when the Increased Cell CarrierSupport for DUW feature and HSDPA MC Inter DU Joint Scheduling featureare enabled to support the HSDPA Multicarrier (MC). When the Increased CellCarrier Support for DUW is used, the hardware in the primary DUW is dividedlogically into two BBPs with equal hardware capacity. The following examplesshow the configuration based on BBP.






EUL: 1



EUL Users per cell

Increased Cell Carrier Support for DUW

Cell 1

Cell 2

Cell 3

Cell 4

Cell 5

Cell 6

5 HSDPA codes

16 HSDPA users

5 HSDPA codes

16 HSDPA users

5 HSDPA codes

16 HSDPA users

321 CE

B0002476A

16 EUL users

16 EUL users

5 HSDPA codes

16 HSDPA users

16 EUL users

5 HSDPA codes

16 HSDPA users

16 EUL users

5 HSDPA codes

16 HSDPA users

16 EUL users

16 EUL users

26 5/1553-LZA 701 6003 Uen Y | 2015-05-12







EUL: 1



EUL Users per cell


HSDPA MC Inter DU Joint Scheduling

Cell 1

Cell 2

Cell 3

Cell 4

Cell 5

Cell 6

15 HSDPAcodes

16 HSDPA users

15 HSDPAcodes

16 HSDPA users

15 HSDPAcodes

16 HSDPA users

321 CE

B0002478A

16 EUL users

16 EUL users

15 HSDPAcodes

16 HSDPA users

16 EUL users

15 HSDPAcodes

16 HSDPA users

16 EUL users

15 HSDPAcodes

16 HSDPA users

16 EUL users

16 EUL users






EUL: 1


DUW 41: 451 CE

Required Licenses HSDPA Codes per cell



EUL Users per cell


Cell 1

Cell 2

Cell 3

Cell 4

Cell 5

Cell 6

15 HSDPAcodes

32 HSDPAusers

15 HSDPAcodes

32 HSDPAusers

15 HSDPAcodes

32 HSDPAusers

259/451 CE

B0002477A

16 EULusers

16 EUL users

15 HSDPAcodes

32 HSDPAusers

16 EUL users

15 HSDPAcodes

32 HSDPAusers

16 EUL users

15 HSDPAcodes

32 HSDPAusers

16 EULusers

16 EUL users

275/1553-LZA 701 6003 Uen Y | 2015-05-12


3.9.2 EUL Sector Configuration with Single Rx Branch

When an EUL sector is configured with a single Rx branch, the followingconfigurations are recommended:

• Set radiobuildingblock to RBB12_1A.

• Lock the antenna RxB ports (AiDevice = 2) of the radio units.

• Terminate the unused RxB port with a 50 Ohm load on-site. It preventsthe system from the effect of interfering signals which cause degradeduplink performance.

28 5/1553-LZA 701 6003 Uen Y | 2015-05-12

HSDPA Features

4 HSDPA Features

This section describes the HSDPA features.

4.1 64 QAM and MIMO Combination

The 64 Quadrature Amplitude Modulation (QAM) and MIMO Combinationfeature makes it possible to use 64 QAM and MIMO at the same time. TheRbsLocalCell::featureState64qamMimo attribute controls whether thefeature is enabled. The HSDPA 64 QAM, MIMO and 64 QAM and MIMOCombination licenses are required.

4.2 HSDPA Incremental Redundancy

The HSDPA Incremental Redundancy feature improves the radiolink performance by improving the chances of the User Equipment(UE) successfully decoding transmission on the High Speed DownlinkShared Channel (HS-DSCH). The transmitted coded bits are changedbefore a retransmission attempt. This improves performance comparedto standard method, Chase Combining, where the retransmissioncontains the same coded bits as the original transmission. TheRbsLocalCell::featureStateHsdpaIncrementalRedundancy attributecontrols whether the feature is enabled. The HSDPA Incremental Redundancylicense is required.

4.3 Enhanced Layer 2

The Enhanced Layer 2 feature provides enhancements to layer 2, the data linklayer, to support the higher bit rates associated with the MIMO, 64 QAM and MultiCarrier features. The RbsLocalCell::featureStateEnhancedLayer2attribute controls whether the feature is enabled. The Enhanced Layer 2license is required.

4.4 Enhanced UE DRX

The Enhanced UE Discontinuous Reception (DRX) feature allows the UE tosave battery power, in CELL_FACH state, by listening to the High SpeedShared Control Channel (HS-SCCH) only for a specified time, during the DRXburst. The Enhanced UE DRX must be configured together with the HighSpeed Downlink for FACH feature. The feature is also called Battery Efficiencyfor HS-FACH. The RbsLocalCell::featureStateEnhUeDrx attributecontrols whether the feature is enabled. The Enhanced UE DRX and the HighSpeed Downlink for FACH licenses are required.

295/1553-LZA 701 6003 Uen Y | 2015-05-12


4.5 High Speed Downlink for FACH

The High Speed Downlink for Forward Access Channel (HS-FACH) featuregives the possibility to use the HS-DSCH transport channel instead of theFACH transport channel. This allows the user equipment to achieve a higherbandwidth on the downlink. The RbsLocalCell::featureStateHsFachattribute controls whether the feature is enabled. The High Speed Downlink forFACH and the Enhanced Layer 2 licenses are required.

4.6 HSDPA Flexible Scheduler

The Flexible Scheduler feature includes the following functions:

• Code multiplexing, allowing the RBS to send HSDPA data to more than oneuser simultaneously

• High-Speed Shared Control Channel (HS-SCCH) power control

• Additional priority queue selections

Additional values, in addition to ROUND_ROBIN and PROPORTIONAL_FAIR_MEDIUM are allowed for the RbsLocalCell::queueSelectAlgorithmattribute.

The NodeBFunction::featureStateHsdpaFlexibleSchedulerattribute controls whether the feature is enabled. The HSDPA FlexibleScheduler license is required.

4.7 HSDPA 16 QAM

With the HSDPA 16 QAM feature, 16 QAM coding can be used in the RBSwhen supported by the UE. Depending on connection quality, the RBS can shiftforth and back between 16 QAM and Quadrature Phase Shift Keying (QPSK).The NodeBFunction::featureState16qam attribute controls whether thefeature is enabled. The HSDPA 16 QAM license is required.

4.8 HSDPA 64 QAM

With the HSDPA 64 QAM feature, 64 QAM coding can be used in theRBS when supported by the UE. Depending on connection quality, theRBS can shift forth and back between 64 QAM, 16 QAM and QPSK. TheNodeBFunction::featureState64qam attribute controls whether thefeature is enabled. The HSDPA 64 QAM, HSDPA 16 QAM, and EnhancedLayer 2 licenses are required.

30 5/1553-LZA 701 6003 Uen Y | 2015-05-12

HSDPA Features

4.9 HSDPA Multi Carrier

The Multi Carrier feature allows for transmission of the user data on HSDPAto a UE over two cell carriers within the same sector, which increases thedownlink user bit rate. The support of the Multi Carrier feature complies withthe following rules:

• For the DUW-based RBS configurations using FAJ 121 2709: HSDPA MCInter DU Joint Scheduling, the Multi Carrier feature is always supported.However, when FAJ 121 3928: Increased Cell Carrier Support for DUW isused, for the secondary DUW in a dual-DUW configuration, the support ofthe Multi Carrier feature follows the rules for the RBS configurations withoutusing the HSDPA MC Inter DU Joint Scheduling feature.

• For the DUW-based RBS configurations without using the HSDPA MCInter DU Joint Scheduling feature, the Multi Carrier feature depends onthe following DUW variants:

� The DUW 10, DUW 20, and DUW 30 variants support the steeredallocation of HSDPA processing resources to one or several specificcells in the same BBP.

• When the steered allocation is activated by setting theNodeBFunction::steeredHsAllocation attribute to True,the Multi Carrier feature is supported only on the processingresources allocated with two frequencies.

• When the steered allocation is deactivated by setting theNodeBFunction::steeredHsAllocation attribute to False,so that the automatic allocation is used, the Multi Carrier feature issupported only on the BBPs allocated with two frequencies.

� The DUW 11, DUW 31, and DUW 41 variants support only theautomatic allocation of processing resources, so the Multi Carrierfeature is supported only on the BBPs allocated with two frequencies.

Setting up a Radio Access Bearer (RAB) type that includes both the MultiCarrier and the MIMO features is supported for DUW-based RBSs.

Note: No reallocation of HS cells on HSDPA code resources is performedduring the activation of the Multi Carrier feature.

The RbsLocalCell::featureStateHsdpaMc attribute controls whether thefeature is enabled. The HSDPA Multi Carrier license is required.

4.10 HSDPA Multi Carrier Inactivity Control

The HSDPA Multi Carrier Inactivity Control feature makes it possibleto deactivate and reactivate the secondary serving cell carrier tolimit battery consumption for UE in the Multi-carrier mode. TheRbsLocalCell::featureStateHsdpaMcInactCtrl attribute controls

315/1553-LZA 701 6003 Uen Y | 2015-05-12


whether the feature is enabled. The HSDPA Multi Carrier Inactivity Controllicense is required.

4.11 HSDPA Multi Carrier with MIMO

The HSDPA Multi Carrier with MIMO feature enables the transmission ofHSDPA user data to the same UE over two cell carriers using MIMO. Therefore,this feature helps to increase the user throughput for the downlink. TheRbsLocalCell::featureStateHsdpaMcMimo attribute controls whetherthe feature is enabled. The HSDPA Multi Carrier, the MIMO and the HSDPAMulti Carrier with MIMO licenses are required.

4.12 HSDPA RBR QoS Profiling

The HSDPA Relative Bit Rate (RBR) Quality of Service (Qos) feature makesit possible to define gold, silver and bronze users for relative bit rates withan OSS functionality. This makes it easier to configure RBS nodes. TheNodeBFunction::featureStateHsdpaRbrQosProfiling attributecontrols whether the feature is enabled. The HSDPA RBR QoS Profilinglicense is required.

4.13 Improved HSDPA Link Adaptation

The Improved HSDPA Link Adaptation feature increases the maximum bitrate for HSDPA users with 5–10% in good radio conditions. It is possibleby using abundant power available in a cell to lower the Hybrid AutomaticRepetition Request (HARQ) block error rate for HSDPA users. TheNodeBFunction::featureStateHsdpaImprovedLinkAdaptationattribute controls whether the feature is enabled. The Improved HSDPA LinkAdaptation license is required.

4.14 Increased Number of HSDPA Codes for Single-CarrierUsers

The Increased Number of HSDPA Codes for Single-Carrier Users featureincreases the number of HSDPA codes available within one HSDPAprocessing resource on a TX6HS-0x to increase the HSDPA bit rate. Fordual stream MIMO users the feature allows 18 HSDPA codes to be sharedover two cells in a HSDPA processing resource. For all other types ofsingle-carrier users (including single stream MIMO users) 26 HSDPA codescan be shared over two cells in an HSDPA processing resource. TheNodeBFunction::featureStateIncrNumHsCodes attribute controlswhether the feature is enabled. The Increased Number of HSDPA Codes forSingle-Carrier Users license is required.

32 5/1553-LZA 701 6003 Uen Y | 2015-05-12

HSDPA Features

4.15 MIMO

The MIMO feature enables simultaneous use of two transmitting antennas onthe RBS and two receiving antennas on the UE. With two parallel data streamstransmitted to one UE, the peak bit rate for HSDPA is theoretically doubled.The RbsLocalCell::featureStateMimo attribute controls whether thefeature is enabled. The Enhanced Layer 2 and Multiple Input Multiple Outputlicenses are required.

4.16 Minimum Bit Rate HSDPA

The Minimum Bit Rate HSDPA feature provides certain users with a guaranteeto receive at least a minimum bit rate for their packet data. The minimum bitrate in the HSDPA scheduler is maintained by an additional scheduling priorityfactor when the measured rate drops below the targeted minimum rate. TheNodeBFunction::featureStateHsdpaMinBitRate attribute controlswhether the feature is enabled. The Minimum Bit Rate HSDPA license isrequired.

4.17 F-DPCH and SRB on HSDPA

The Fractional Dedicated Physical Channel (F-DPCH) and the SignalingRadio Bearer (SRB) on HSDPA features allows the efficient use of downlink(DL) channelization codes and DL power. The F-DPCH feature meansthat F-DPCH is used instead of Associated Dedicated Channel (A-DCH).The SRB on HSDPA feature allows quicker downlink signalling, so thesynchronized reconfigurations between different DCH states are done faster.The RbsLocalCell::featureStateFDpchSrbOnHsdpa attribute controlswhether the features are enabled. The F-DPCH and SRB on HSDPA license isrequired.

4.18 Enhanced Downlink Reception, CPC

The Enhanced Downlink Reception, CPC feature allows the UE to switch offits receiver after a certain period of HSDPA inactivity. This reduces the powerconsumption for the UE.

Note: A CPC user consumes at least two CE, so it overwrites the EnhancedUplink Ladder E feature.

The observability of the CPC state of the cell is ensured by the cpcCapabilityparameter. A local cell is CPC capable if the following conditions are fulfilled:

• The local cell is HSDPA capable

• The local cell is E-DCH capable

• The local cell is F-DPCH capable

335/1553-LZA 701 6003 Uen Y | 2015-05-12


• The CPC feature is activated

• A valid license key is installed for CPC

• At least one DUW is CPC capable

Inter-Frequency Handover within the same RBS is rejected for a CPC user.More information about CPC can be found in the WCDMA RAN CPC document.The RbsLocalCell::featureStateCpc attribute controls whether thefeature is enabled. The CPC license is required for each RBS.

4.19 AQM based Congestion Control for HSDPA

AQM based Congestion Control for HSDPA feature is new congestioncontrol for RBS Priority Queue (PQ) and WRAN Transport Network andprovides improved performance for short transfers at high rates. The featureenables LTE and WCDMA PS Interactive and Background traffic in thesame TN QoS Class. More information about this feature can be found inthe WCDMA RAN AQM Based Congestion Control for HSDPA document.The NodeBFunction::featureStateHsAqmCongCtrl attribute controlswhether the feature is enabled. A restart is required for this feature to beactivated, refer to Restart Node. The AQM based Congestion Control forHSDPA license is required for each RBS.

4.20 Channel Element Capacity for HSDPA Smartphones

The CE Capacity for HSDPA Smartphones feature provides a more efficientuplink CE ladder for the DCH, called ladder F. The uplink CE ladder improvesthe total uplink hardware capacity for the RBS by lowering the UL hardwareresource consumption for DCH. The feature is only available for DU-basedRBS. A restart of the RBS is required after the license key is installed, refer toRestart Node. The CE Capacity for HSDPA Smartphones license is required.

4.21 Increased HSDPA Code Capacity on DUW

The Increased HSDPA Code Capacity on DUW feature changes the maximumnumber of HS codes for each HSDPA processing resource as follows:



The feature increases the cell throughput for each HSDPA processingresource and removes the code limitation in many configurations. With morecodes available for each HSDPA processing resource, the throughput isimproved. The NodeBFunction::featureStateIncreasedHsCodeCapattribute controls whether the feature is enabled. The Increased HSDPA CodeCapacity on DUW license is required.

34 5/1553-LZA 701 6003 Uen Y | 2015-05-12

HSDPA Features

4.22 HSDPA MC Inter DU Joint Scheduling

The HSDPA MC Inter DU Joint Scheduling feature makes it possibleto run multi carriers between any of the carriers in an RBS. TheNodeBFunction::featureStateHsdpaMcinterDuJointSchedulingattribute controls whether the feature is enabled. The HSDPA MC Inter DUJoint Scheduling license is required.

4.23 HSDPA Dynamic Power Sharing

The HSDPA Dynamic Power Sharing feature is a licensed feature.This feature enables sharing the HS-DSCH transmission powerby the cells in the same frequency band within a sector. TheRbsLocalCell::featureStateHsdpaPowerSharing attribute controlswhether the feature is enabled.

4.24 HSDPA Multi-Carrier 3 Carriers

The HSDPA Multi-Carrier 3 Carriers feature is an optional feature thatcorresponds to 4C-HSDPA in the 3GPP Rel-10 standard. The featureintroduces support for HSDPA multicarrier, with or without 64 QAM, using threeadjacent carriers. The RbsLocalCell::featureStateHsdpa3Mc attributecontrols whether the feature is enabled.

4.25 Dual-Band HSDPA Multi-Carrier 3 Carriers

The Dual-Band HSDPA Multi-Carrier 3 Carriers feature is an optional featurethat corresponds to 4C-HSDPA in the 3GPP Rel-10 standard. The featureintroduces support for Dual-Band HSDPA multicarrier on three carriers, withor without 64 QAM, using carriers in two separate frequency bands. TheRbsLocalCell::featureStateHsdpaDb3Mc attribute controls whetherthe feature is enabled.

355/1553-LZA 701 6003 Uen Y | 2015-05-12


5 EUL Features

This section describes the EUL features.

5.1 Downlink Power Control for Enhanced Uplink

The Downlink Power Control for Enhanced Uplink feature gives transmissionpower control of the Enhanced Acknowledgement Channel (E-HICH), reducingHS capacity costs. The NodeBFunction::featureStateDlPowerControlEul attribute controls whether the feature is enabled. The Downlink PowerControl for Enhanced Uplink license is required.

5.2 EUL 2ms TTI

The EUL 2ms Transmission Time Interval (TTI) feature provides higher uplink bitrates and lower latency. The NodeBFunction::featureStateEul2msTtiattribute controls whether the feature is enabled. The EUL 2ms TTI license isrequired.

5.3 EUL in Two Baseband Pools

The EUL in Two Baseband Pools feature makes it possible to enable EUL intwo BB pools in DU-based RBSs. The NodeBFunction::featureStateEulForLargeRbsConfig attribute controls whether the feature is enabled.The Enhanced Uplink Introduction Package and the EUL For Large RBSConfigurations licenses are required.

5.4 EUL TD Scheduling

The EUL Time Domain (TD) Scheduling feature introduces time orthogonaltransmissions by assigning different HARQ processes to 2ms TTI users.This allows to increase the cell throughput for multiuser cases. TheRbsLocalCell::featureStateEulTdScheduling attribute controlswhether the feature is enabled. The EUL TD Scheduling and the EUL 2ms TTIlicenses are required.

5.5 Per HARQ Process Grant

The Per HARQ Process Grant function is a part of the EUL Single HARQProcess Scheduling feature. The Per HARQ Process Grant is an optionalfeature handled with a license key on the RBS.

36 5/1553-LZA 701 6003 Uen Y | 2015-05-12

EUL Features

Note: The Per HARQ Process Grant feature is for 2 ms EUL users only.

The eul2msFirstSchedStep RBS parameter specifies whetherthe initial ramp-up step from zero rate stops at the 20 kbps(one HARQ process) or 160 kbps (all HARQ processes). TheNodeBFunction::featureStatePerHarqProcessGrant attributecontrols whether the feature is enabled. The Per HARQ Process Grant licenseis required.

5.6 Enhanced Uplink Transmission, CPC

The Enhanced Uplink Transmission, CPC feature has the following threefunctions:

• Uplink Discontinuous Transmission (UL DTX) that allows the UE to switchoff the UL Dedicated Physical Control Channel (DPCCH) when there is notransmitted data. It reduces the power consumption for the UE

• Channel Quality Indicator (CQI) reporting reduction that makes it possibleto send the CQI reports in the HS-DPCCH channel discontinuously after acertain period of HSDPA inactivity

• Medium Access Control (MAC) DTX that allows the MAC layer to restrictthe time period where the UE can start an EUL transmission after a certainperiod of EUL inactivity

Note: A CPC user consumes at least two CE, so it overwrites the EnhancedUplink Ladder E feature.

The observability of the CPC state of the cell is ensured by the cpcCapabilityparameter. A local cell is CPC capable if the following conditions are fulfilled:

• The local cell is HSDPA capable

• The local cell is E-DCH capable

• The local cell is F-DPCH capable

• The CPC feature is activated

• A valid license key is installed for CPC

• At least one DUW is CPC capable.

Inter-Frequency Handover within the same RBS is rejected for a CPC user.More information about CPC can be found in the WCDMA RAN CPC document.The RbsLocalCell::featureStateCpc attribute controls whether thefeature is enabled. The CPC license is required for each RBS.

375/1553-LZA 701 6003 Uen Y | 2015-05-12


5.7 Advanced Receivers, GRAKE in RBS

The GRAKE (Generalized RAKE) algorithm reduces the interference betweenRAKE fingers at high rates. It is applied for higher rates for EUL 2ms TTI.The NodeBFunction::featureStateGrake attribute controls whether thefeature is enabled. The Advanced Receivers, GRAKE in RBS, EnhancedUplink Introduction Package, and EUL 2ms TTI licenses are required.

5.8 Channel Element Capacity for EUL Smartphones

The CE Capacity for EUL Smartphones feature provides a more efficientminimum CE cost for EUL 2 ms TTI users. It enables the operator to set anddecide the timing for hardware grant handling for inactive users. The featureis only available for DU-based RBS.

Note: When the feature Interference Suppression is enabled, InterferenceSuppression is allocated for EDCH radio links with one HARQ grantas far as possible.

The NodeBFunction::featureStateCeCapEul attribute controls whetherthe feature is enabled. A restart of the RBS is required after the license keyis installed, refer to Restart Node. The CE Capacity for EUL Smartphoneslicense is required.

5.9 Enhanced Uplink Ladder E

The Enhanced Uplink Ladder E feature consumes less E-DCH resources,which leads to a higher total throughput. It is compatible with all DUW variants.The Enhanced Uplink Ladder E license is required.

5.10 UL Efficiency - DCH/EUL Load Balancing

The UL efficiency - DCH/EUL load balancing feature is used for loadbalancing between DCH and EUL users. The RBS monitors the EULperformance (Unhappy User Rate) and reports it to the RNC. TheNodeBFunction::featureStateDchEulBalancing attribute controlswhether the feature is enabled. The UL efficiency - DCH/EUL load balancinglicense is required.

5.11 Interference Suppression

The Interference Suppression is an advanced receiver enhancement for DUW.It brings significant performance gains for EUL, which in turn lowers interferencelevels also for other radio bearers. Interference Suppression is supported indeployment scenarios with 1, 2, or 4 receiver antennas.

38 5/1553-LZA 701 6003 Uen Y | 2015-05-12

EUL Features

The Interference Suppression receiver replaces the existing G-Rake receiverand improves equalization, SIR estimation, and interference suppression(interference mitigation) capabilities.

The NodeBFunction::featureStateInterferenceSuppressionattribute controls whether the feature is enabled.

The Interference Suppression licenses is required.

This feature is only available for DU-based RBS.

5.12 Improved Layer 2

Improved Layer 2 (IL2) includes the following functions:

• Flexible Mode RLC (flexible sized RLC PDUs) on the uplink

• New protocols MAC-i/is (to support segmentation) and a new uplink IubFrame Protocol, type2, introduced to support IL 2 data transport in thetransport network (Iub)

Flexible RLC introduces the possibility to vary the size of the RLC SDU'scarried in the corresponding RLC PDU's (MAC-d PDU) on the uplink. Thisenables larger PDU sizes, to allow higher uplink bit rates and reduced RLCoverhead, and smaller PDU sizes, which eliminates the need for padding.MAC- i/is introduces the possibility for the UE to segment MAC-d PDUs,if these do not fit within the selected Transport Block in UE power limitedcases. A new transport block format is introduced to support segmentation.Otherwise the MAC-i/is has the same functionality as for MAC-e/es. TheRbsLocalCell::featureStateImprovedLayer2 attribute controlswhether the feature is enabled. The Improved Layer 2 license is required.

5.13 EUL on Cell FACH

The enhanced uplink (EUL) on Cell FACH feature makes it possible forUEs in CELL_FACH supporting this feature to transmit their data on theE-DCH instead of transmitting the data on the data part of the RACH. Thefeature provides shorter uplink transfer times while being in CELL_FACHand faster transition from CELL_FACH to CELL_DCH. This improvesthe end user experience of users in CELL_FACH and up-switching toCELL_DCH from CELL_FACH. Only EUL with 10ms TTI is provided. TheRbsLocalCell::featureStateEulFach attribute controls whether thefeature is enabled. The EUL on Cell FACH license is required.

5.14 CE Extension for EUL

The CE Extension for EUL is a licensed feature and is only available forDU-based RBS. This feature extends the hardware capacity for CE by 50% of

395/1553-LZA 701 6003 Uen Y | 2015-05-12


the RBS licensed CE, and the extended hardware capacity is used only for EULdynamic CE for scheduling. The number of static CEs remains the same. Forexample, a node with 1,024 licensed CEs can use 1,536 CEs with this feature,of which 512 CEs are intended to be used only for EUL bit rates higher thanallowance value defined by the minimum CE allocation, that is, EUL dynamicCEs use. The NodeBFunction::featureStateCeExtForEul attributecontrols whether the feature is enabled. The CE Extension for EUL license isrequired.

5.15 Interference Suppression for EUL 10 ms

Interference Suppression for EUL 10 ms is an advanced receiver expansion forDUW. It brings significant performance gains also for EUL 10 ms, which in turnlowers interference levels also for other radio bearers. Interference Suppressionis supported in deployment scenarios with 1, 2, or 4 receiver antennas.

The Interference Suppression receiver replaces the existing Rake receiverand improves equalization, SIR estimation, and interference suppression(interference mitigation) capabilities.

The NodeBFunction::featureStateIntSuppEul10ms attribute controlswhether the feature is enabled.

The Interference Suppression and Interference Suppression for EUL10 mslicenses are required.

This feature is only available for DU-based RBS.

5.16 EUL Multi-Carrier

The EUL Multi-Carrier feature introduces support for UE to use EUL on twoadjacent carriers. This means that uplink E-DCH transmission from the givenUE is supported simultaneously on two adjacent carriers.

EUL Multi-Carrier is the uplink equivalent to HSDPA Multi-Carrier.

The RbsLocalCell::featureStateEulMc attribute controls whether thefeature is enabled.

The EUL Multi-Carrier license is required.

This feature is only applicable to DU-based RBSs.

40 5/1553-LZA 701 6003 Uen Y | 2015-05-12

Traffic Disturbances during Configuration Modifications

6 Traffic Disturbances during ConfigurationModifications

Table 16 lists some hardware and software modifications and their effect onongoing RBS traffic for a DU-based RBSs.

Table 16 Effects on RBS Traffic for DU-based RBSs

Modification Effect on RBS Traffic Comment

Replacing DU; one DUin RBS

High All traffic is lost duringreplacement.

Replacing DU; two DUsin RBS

Low Replace DUs one at atime.

Calls in progresshandled by this DUare lost.

Replacing DU; twoDUs in RBS with theHSDPA MC Inter DUJoint Scheduling featureenabled

High All traffic is lost duringreplacement.

Adding DU None

Modifying HSDPAcapacity in DU; one DUin RBS

High All traffic is lost duringrestart.

Modifying HSDPAcapacity in DU; two DUsin RBS

Low Configure DUs one at atime.

Calls in progresshandled by this DUare lost.

Modifying HSDPAcapacity in DU; twoDUs in RBS with theHSDPA MC Inter DUJoint Scheduling featureenabled

High All traffic is lost duringrestart.

415/1553-LZA 701 6003 Uen Y | 2015-05-12

Technology

Configuring hsdpa and eul