RAN 10 HSDPA Deployment Guide-20080821-A-2.0

HSDPA Deployment Guide Internal

Document

BOM Code

Product

Name WCDMA NodeB&RNC

Intended

Audience INTERNALProduct

Version

Prepared by UMTS Maintenance

Department

Document

Version

HSDPA Deployment Guide (RAN 10)

Prepared by HSPA team, UMTS

Maintenance DepartmentDate

Reviewed by Date

Reviewed by Date

Approved by Date

2023-04-11 Huawei Confidential Page 1 of 49


Huawei Technologies Co., Ltd.

All rights reserved



Table of Contents

Chapter 1 Overview........................................................................................................................ 8

1.1 Introduction to HSDPA........................................................................................................8

1.2 Availability........................................................................................................................... 9

1.2.1 Network Elements Involved......................................................................................9

1.2.2 Version Matching....................................................................................................10

1.2.3 Other Support.........................................................................................................11

1.3 Implementation..................................................................................................................11

1.3.1 HSDPA Code Allocation Policies............................................................................11

1.3.2 Flow Control...........................................................................................................11

1.3.3 Scheduling..............................................................................................................15

1.3.4 Power Control on HSDPA Channels.......................................................................16

1.3.5 RRM Policies of HSDPA.........................................................................................18

1.3.6 Signaling over HS-DSCH........................................................................................18

Chapter 2 Basic Principles..........................................................................................................19

2.1 Overview of Basic HSDPA Principles................................................................................19

2.2 HSDPA Structure..............................................................................................................19

2.2.1 F-DPCH..................................................................................................................19

2.3 Mobility Management........................................................................................................21

2.3.1 HSDPA over Iur......................................................................................................21

Chapter 3 Upgrade Guide............................................................................................................23

3.1 RNC Upgrade....................................................................................................................23

3.1.1 Upgrade Requirements...........................................................................................23

3.1.2 Upgrade Procedure................................................................................................23

3.2 NodeB Upgrade................................................................................................................24

3.2.1 Upgrade Procedure................................................................................................24

Chapter 4 Data Configuration Policies.......................................................................................25

4.1 Building an HSDPA Network.............................................................................................25

4.1.1 Configuring the GGSN (Huawei).............................................................................25

4.1.2 Configuring the SGSN (Huawei).............................................................................25

4.1.3 Configuring the HLR Subscription (Huawei)...........................................................25

4.2 Checking Transmission Configuration on Iub and Iu Interfaces........................................25

4.2.1 Checking Transmission Configuration on Iub interface...........................................25

4.2.2 Checking the Bandwidth on Iu-PS Interface...........................................................26

4.2.3 Configuring the NodeB...........................................................................................26

4.2.4 Configuring the RNC...............................................................................................26

4.3 Service and Bearer Configuration.....................................................................................26



4.3.1 Configuring the subscription of HSDPA UE............................................................26

4.3.2 Configuring the HSDPA code allocation.................................................................26

4.3.3 Configuring the HSDPA Cell Power........................................................................27

4.3.4 Configuring HSDPA Scheduling and Flow Control.................................................27

4.3.5 Configuring HSDPA Power Control........................................................................28

4.3.6 Configuring the QoS Mechanism for HSDPA.........................................................28

4.3.7 Configuring the HSDPA License.............................................................................29

4.3.8 Configuring SRB on HS-DSCH...............................................................................29

4.3.9 Configuring the HSPA over Iur................................................................................29

4.4 Configuring Radio Resource Management.......................................................................30

4.4.1 Configuring HSDPA Measurement Control.............................................................30

4.4.2 Configuring HSDPA Admission Control..................................................................30

4.4.3 Configuring HSDPA Load Control...........................................................................31

4.5 Typical HSDPA Configuration in Competition Scenario (14.4 Mbit/s)...............................31

Chapter 5 Networking Strategy...................................................................................................33

5.1 Overview........................................................................................................................... 33

5.2 Allocation Strategy in Dual-Carrier Service.......................................................................33

5.2.1 Load Balancing Based Solution..............................................................................34

Chapter 6 Troubleshooting..........................................................................................................41

6.1 Services Cannot Be Connected to HSDPA Channels.......................................................41

6.2 Download Rate is 0 after HSDPA is Enabled....................................................................41

6.3 HDSPA Service Download Rate is Low............................................................................41

6.4 Rate of 7.2 Mbit/s High-Rate Service is Low.....................................................................42

6.5 HSDPA Service Rate Remains at 2 Mbit/s........................................................................42

Chapter 7 Appendix...................................................................................................................... 44

7.1 RNC-related MML commands...........................................................................................44

7.2 NodeB Related MML Commands......................................................................................45



List of Figures

Figure 1-1 Flow control bits in an HS-DSCH data frame........................................................12

Figure 1-2 Power offset of HS-DPCCH..................................................................................17

Figure 2-1 F-DPCCH frame structure.....................................................................................20

Figure 2-2 Multiplexing multiple F-DPCHs.............................................................................20

Figure 2-3 Static relocation....................................................................................................22

Figure 5-1 Dual-carrier application.........................................................................................33

Figure 5-2 Mobility management............................................................................................35

Figure 5-3 DRD policy in dual-carrier.....................................................................................37

Figure 5-4 DRD policy in dual-carrier.....................................................................................37



List of Tables

Table 1-1 Abbreviations............................................................................................................6

Table 1-1 Requirements for hardware......................................................................................9

Table 1-2 Categories of HSDPA-enabled UEs..........................................................................9

Table 1-3 Version matching table...........................................................................................10

Table 1-4 Performance of four types of MAC-hs scheduling algorithm...................................16

Table 3-1 Recommended RNC versions for commercial use.................................................23

Table 5-1 Configuration comparison between F1 carrier and F2 carrier.................................34

Table 5-2 Reference settings for user access policies in F1 and F2 carriers..........................38

Table 5-3 Reference settings for LDR policies in F1 and F2 carriers......................................39

Table 7-1 RNC-Related MML Commands..............................................................................44

Table 7-2 MML commands related to the NodeB....................................................................45



HSDPA Deployment GuideKey words

HSDPA, HARQ, MAC-HS scheduling

Abstract

This document supplements and amends the HSDPA Deployment Guide V18 based

on the RAN 10 features. This document describes the deployment preparations, basic

principles, upgrade precautions, data configuration policies, networking strategy, and

FAQs of the HSDPA and works as a guide for field deployment. The man-machine

language (MML) commands in this document are based on the RNC

BSC6800V100R010C01B051/BSC6810V200R010C01B051 and BBU3806-

BBU3806C V100R010C01B050.

The descriptions in this document are used for references only, but not as basis of

any reply to the customers or public.

List of abbreviations

Table 1-1 Abbreviations

Abbreviation Full Spelling

ACK Acknowledgement

AG Absolute Grant

BE Best Effect

CN Core Network

DCCH Dedicated Control Channel

DCH Dedicated Channel

DPCH Dedicated Physical Channel

DTCH Dedicated Traffic Channel

FP Frame Protocol

HARQ Hybrid Automatic Repeat Request

HSDPA High Speed Downlink Packet Access

HSUPA High Speed Uplink Packet Access

IR Increment Redundancy



Abbreviation Full Spelling

MAC-d Medium Access Control - dedicated

NACK Negative Acknowledgement

NE Network Element

PDU Protocol Data Unit

QoS Quality of Service

RG Relative Grant

RLC Radio Link Control

RLS Radio Link Set

RNC Radio Network Controller

RoT Raise of Thermal

RSN Retransmission Sequence Number

RV Redundancy Version

RTT Round Trip Time

SF Spreading Factor

SG Serving Grant

SRNC Serving RNC

TNL Transport Network Layer

TSN Transmission Sequence Number

TTI Transmission Time Interval

UE User Equipment

UTRAN UMTS Radio Access Network

WCDMA Wideband Code Division Multiple Access



Chapter 1 Overview

1.1 Introduction to HSDPA

The high speed downlink packet access (HSDPA) is introduced to the WCDMA R5 as

an enhancement of the standard WCDMA, that is, the Release 1999 (R99). The use

of the HSDPA technology helps provide a high data rate and a low delay at the radio

downlink. It largely shortens the data download time of a user equipment (UE) by

providing the high-rate download service, fast access, and short delay, and improves

Web page browsing and online interaction. Therefore, the HSDPA improves the

service experience of the users.

The HSDPA is an important feature of the WCDMA R5 used to increase the downlink

capacity that troubles the WCDMA R99. As the downlink high-speed data solution for

the WCDMA, the HSDPA supports a maximum theoretical rate of 14.4 Mbit/s at the

physical layer.

The HSDPA benefits mobile operators and end users in the following aspects:

Increasing the downlink capacity of the network and reducing the cost of

transmitting data streams

The HSDPA provides a higher data transmission rate than the standard WCDMA by

quickly regulating the modulation and coding schemes at the downlink according to

the actual radio environment of a UE. The theoretical chip rate of the HSDPA can

reach 14.4 Mbit/s. The theoretical rate of a single UE at the IP layer can reach 12

Mbit/s or higher.

For a mobile operator, the use of HSDPA can reduce the unit cost for transmitting

every mega bytes of data streams, increase the average capacity of the system, and

improve the downlink data service performance of a UE. For example, a three-minute

mobile video clip consists of 3 mega bytes. A short message consists of 160 bytes.

When these bandwidth-dense services spread, the existing R99 network lacks

capacity.

Improving the service performance for end users

The HSDPA offers a high data transmission rate, short service response time, and

reliable service performance for a UE. Therefore, it improves the service experience

of the UE.

Supporting easy deployment

A mobile operator concerns about the expenses for building an HSDPA network. This

depends on the device prices and service strategies of the operator. As a high-rate



data service enhancement technology in the WCDMA R5, the HSDPA is compatible

with the WCDMA R99. The operator can upgrade NodeBs in the existing WCDMA

R99 network to introduce the HSDPA with little impact on the existing architecture.

This helps shorten the network construction period and protect the investments of the

operator.

1.2 Availability

1.2.1 Network Elements Involved

The HSDPA has some requirements on the UE, NodeB, radio network controller

(RNC), and core network (CN). The following figure shows the requirements of the

HSDPA for these network elements (NEs). The √ means that the HSDPA has

requirements for the NE.

Table 1-2 Requirements for hardware

IP

RequirementUE NodeB RNC CN

Data

configuration

requirement

None √ √No special

requirements

Hardware

requirement√ √

No special

requirements

No special

requirements

1) UE

The UEs that support the HSDPA are classified into 12 categories according to the

capability. The maximum downlink rate varies from 0.9 Mbit/s to 14.4 Mbit/s. The

following table lists the capability of these UE categories.

Table 1-1 Categories of HSDPA-enabled UEs

Category

Maximum

Number of

HS-DSCH

Codes

Minimum TTIMaximum

Data Blocks

Maximum

Rate (Mbit/s)

1 5 3 7298 1.2

2 5 3 7298 1.2

3 5 2 7298 1.8



Category

Maximum

Number of

HS-DSCH

Codes

Minimum TTIMaximum

Data Blocks

Maximum

Rate (Mbit/s)

4 5 2 7298 1.8

5 5 1 7298 3.6

6 5 1 7298 3.6

7 10 1 14411 7.2

8 10 1 14411 7.2

9 15 1 20251 10.2

10 15 1 27952 14.4

11 5 2 3630 0.9

12 5 1 3630 1.8

2) NodeB

The DBS3800 uses the HBBU. Therefore, such NodeB supports the HSDPA.

HBBI or EBBI are recommended for the BTS3812E. If these boards are

unavailable, such NodeB must be configured with at least one HDLP and one

HULP.

DBS3900 and BTS3900 support the HSDPA.

1.2.2 Version Matching

Table 1-1 Version matching table

No.Compatible

ProductVersion Remarks

1 RNCBSC6810 V200R010C01B051/BSC6810

V100R010C01B051



2 M2000

Common

iManagerM2000V200R006

C01B060+SP02 and later

versions

iManagerM2000V200R008

C01B051 and later

versions

Mediation

iManagerM2000(RNC_MA

TCH_CHS)V200R006C01

B216

3 NodeBAll V100R008 NodeB versions

Not

support

RAN 10

new

features

All V100R010 NodeB versions

All V200R010 NodeB versions

4 CME WRAN CME V100R005C01B060

1.2.3 Other Support

1.3 Implementation

1.3.1 HSDPA Code Allocation Policies

The HSDPA throughput of a cell depends on the number of HS-PDSCH codes in the

cell. The maximum number of codes supported by a UE depends on the HSDPA

category of the UE. The policies for allocating HS-PDSCH codes are as follows:

Static code allocation

Dynamic code allocation controlled by the RNC

Dynamic code allocation controlled by the NodeB

An HS-SCCH carries the information about the downlink HS-PDSCH allocated for

each UE. The information carried in the HS-SCCH includes the information required

by the UE to demodulate the HS-PDSCH, including the UE ID, HS-PDSCH code

allocation information, code demodulation information, and transmission block size.



Each HS-SCCH contains 128 spreading factors (SFs). Within the transmission time

interval (TTI) of 2 ms, the information carried in each HS-SCCH is intended for only

one UE. To schedule multiple UEs within 2 ms, multiple HS-SCCHs are required.

1.3.2 Flow Control

The HSDPA flow control makes full use of the bandwidth on the Iub interface by

restricting the sending Medium Access Control – dedicated (MAC-d) flow on the Iub

interface, and works with HSDPA scheduling to make full use of the resources on the

Uu interface.

I. Allocating the bandwidth for UE queues

II. Avoiding congestion on the Iub interface

3) On the NodeB, use adaptive flow control and traffic shaping to avoid congestion

on the Iub interface.

4) On the RNC, use VP shaping and backpressure to avoid congestion on the Iub

interface.

Bandwidth allocation for UE queues

A NodeB allocates the bandwidth on the Iub interface for each MAC-hs queue

according to the buffering status of the queue and the rate on the Uu interface.

If the queue lacks data, the bandwidth allocated by the NodeB is higher than the

rate on the Uu interface. If the queue contains sufficient data, the bandwidth allocated by the NodeB is

close to the rate on the Uu interface.

If the queue contains excessive data, the bandwidth allocated by the NodeB is

lower than the rate on the Uu interface.

Traffic shaping on Iub interface

When the Iub bandwidth is limited, allocate the bandwidth according to the UE

priority. The rate for a UE is proportional to the scheduling priority index (SPI) weight.

During bandwidth allocation, guaranteed bit rate (GBR) UEs are preferred. Then, the

remaining bandwidth is allocated according to the UE priority, that is, SPI weight.

When there is a severe lack of bandwidth, and the bandwidth cannot meet

requirements of all the GBR UEs, the GBR UEs with high priority are preferred. If the

Iub bandwidth is not lacking, after traffic shaping, queues that desire bandwidth the

most are preferred in bandwidth allocation.

Adaptive flow control on Iub interface

A NodeB determines the congestion on the Iub interface by checking the frame loss

rate and delay, and thus adjusts the bandwidth allocated over the Iub interface.



Figure 1-1 Flow control bits in an HS-DSCH data frame

The Frame Seq Nr field is used to check the frame loss rate on the Iub interface.

The DRT field is used to check the delay on the Iub interface.

If the frame loss rate in the HS-DSCH is beyond the threshold, or the jitter of the

HS-DSCH frames within a period of time exceeds the delay threshold, the

bandwidth for the HSDPA service on the Iub interface is reduced.

If the frame loss rate in the HS-DSCH is lower than the threshold, or the jitter of

the HS-DSCH frames within a period of time is lower than the delay threshold,

the bandwidth for the HSDPA service on the Iub interface is increased.

Compared with a NodeB of V18, the following improvements are made to a NodeB of

RAN 10:

Flow control can be disabled for voice over IP (VoIP) services, thus ensuring the

bandwidth for real-time services.

Differentiated flow control in traffic shaping is modified. When the bandwidth is

lacking, GBR queues are preferred and SPI queues are allocated with Iub resources

according to the SPI weights.

The BW_SHAPING_ONOFF_TOGGLE policy is added. The NodeB can automatically

toggle between no flow control and adaptive flow control. If no congestion occurs to

the NodeB transmission modules during the measurement period, the NodeB

performs no flow control. Otherwise, the NodeB performs adaptive flow control.

VP shaping and backpressure



1) Flow control and backpressure based on RLC retransmission rate

In cases when virtual path (VP) backpressure is not supported, the radio network

controller (RNC) provides the layer 2 flow control based on the radio link control

(RLC) retransmission rate. Congestion detection is based on the retransmission rate.

This means that congestion happens and packets are discarded. In addition, the

round trip delay (RTD) is long. Therefore, congestion detection and flow control take a

long time and result in poor performance.

2) Backpressure of V17/V18 OSEc

This backpressure policy is based on the priority queues, including CBR/RT,

VBR/NRT, and VBR/UBR. When congestion occurs in a certain queue, the rate of the

best effect (BE) UEs in this queue falls. When no congestion occurs to the queue, the

rate of the BE UEs in the queue increases.

3) Backpressure on PVC in RNC of V29

The backpressure mechanism in the RNC of V29 is based on the permanent virtual

channel (PVC). A PVC is configured with a queue. Two PVCs of a same type have

different queues. After receiving the PVC backpressure signal, the destination

signaling point (DSP) reduces the rate for the UEs in this PVC.

4) VP backpressure on virtual port in RNC of V210 and V110

In VP backpressure by virtual port, when congestion occurs on a PVC in a port, the

port is regarded as congested. The port is not regarded as congested only when no

congestion occurs to any of the PVCs. In port congestion or congestion release, the

DSP reduces or raises the rates of all the users in the port. The L2 flow control

algorithm is used to ensure the fairness between R99 and HSDPA and the GBR.

Recommended flow control modes

The NodeB can work with the RNC to enable multiple flow control modes for different

application scenarios. The recommended matching between flow control algorithms

of the NodeB of V17, V18, V29, V110, or V210 and backpressure algorithms of the

RNC is as follows:

1) For a commercial network

If the Iub interface board in an RNC supports backpressure, enable RNC

backpressure. If the interface board does not support backpressure, enable VP

shaping in a NodeB of V29, V110, or V210 to perform flow control based on the

requirements of an operator.

Enable backpressure on the OSEc in the RNC of V17 or V18 by running SET

PORTFLOWCTRLSWITCH.

By default, backpressure is enabled on the AEU, AOU, or UOI interface board in

the RNC of V29. If the interface boards do not support backpressure, run ADD

VP to enable VP shaping.



Enable backpressure on the OSE or PIE interface board in the RNC of V110 by

running SET PORTFLOWCTRLSWITCH. If the interface boards do not support

backpressure, run ADD VP to enable VP shaping for flow control.

Enable backpressure on the AEU, AOU, UOI_ATM, UOI_IP, or GOU/FG2

interface board in the RNC of V210 by running SET PORTFLOWCTRLSWITCH.

For the interface boards that do not support backpressure, run ADD VP to

enable VP shaping if flow control is required.

For a NodeB of the version earlier than R10, enable the adaptive flow control by

running SET HSDPAFLOWCTRLPARA. Set the SWITCH parameter to the

default value, that is, AUTO_ADJUST_FLOW_CTRL.

For a NodeB of R10, the BW_SHAPING_ONOFF_TOGGLE policy is

recommended. Run the following command: SET

HSDPAFLOWCTRLPARA:SWITCH=BW_SHAPING_ONOFF_TOGGLE

2) For a competitive test

If the Iub interface board in the RNC supports backpressure, enable RNC

backpressure. It is recommended that you do not configure the VP.

If the Iub interface board in the RNC supports backpressure, and the networking

mode of the NodeB is direct connection, enable backpressure in the RNC.

Perform the following flow control policy for the NodeB: flow control based on the

RNC backpressure, that is, no flow control. Run SET HSDPAFLOWCTRLPARA.

Set SWITCH to NO_FLOW_CTRL.

If the Iub interface board in the RNC supports backpressure, and the networking

mode of the NodeB is cascading, enable backpressure in the RNC. Perform the

following flow control policy for the NodeB: enable adaptive flow control in a

NodeB of the version earlier than R10. In a NodeB of R10, use the

BW_SHAPING_ONOFF_TOGGLE policy.

If the Iub interface board in the RNC does not support backpressure, perform the

following flow control policy for the NodeB: enable adaptive flow control in a

NodeB of the version earlier than R10. In a NodeB of R10, use the

BW_SHAPING_ONOFF_TOGGLE policy.

1.3.3 Scheduling

The object of the scheduling algorithm is all the UEs that need to share the HSDPA

channels. The scheduling algorithm is used to balance the resources and UEs.

The factors to be considered are as follows:

Consider the fairness. Make sure that every UE has the chance to transmit data.

Consider the channel conditions. A channel with a high carrier-to-interference

rate (C/I) is more likely to be chosen.

Consider the UE priority. A UE with high priority is more likely to be chosen.



Common scheduling algorithms

RR scheduling

This algorithm schedules all the UEs in turn and provides the best fairness. However,

this algorithm may increase the number of UEs that cannot reach the GBR and lead

to a low throughput in the cell.

Max C/I

This algorithm prefers UEs with good channel quality and brings the cell throughput to

the peak. However, UEs with poor channel environment are not served, and the

fairness is poor.

PF

The proportional fair (PF) scheduling algorithm allocates resources to UEs with high

SPI weights. The higher the SPI weight and the better the reported CQI, the higher

the proportion of allocated resources.

EPF

The enhanced proportional fair (EPF) scheduling algorithm incorporates GBR

features and guarantees the QoS of GBR services. This algorithm provides partially

fair scheduling opportunities for GBR UEs when considering the UE priority. In the

case of surplus power and code resources, this algorithm provides partially fair

scheduling opportunities for all the UEs.

Table 1-1 Performance of four types of MAC-hs scheduling algorithm

Algorithm Strength Weakness

Max C/I

Increases the cell throughput to

a high level. When the UE GBR

is the same, this algorithm

helps a large number of UEs

reach the GBR.

Some UEs with poor channel

quality cannot be allocated with

resources. The fairness is poor.

PF

Improves the fairness among

UEs. Users with poor channel

quality can be allocated with

resources.

The number of UEs that reach

the GBR falls

RR

scheduling

Users can fairly share the

scheduling opportunities.

The number of UEs that cannot

reach the GBR may increase.



EPF

scheduling

Ensures the GBR requirements

for streaming services and BE

services. You can configure the

GBR for BE services through

the LMT of the RNC and

NodeB. If the rate of BE

services reaches the GBR,

requirements of the BE UEs

can be satisfied.

The cell throughput is lower than

that in the max C/I algorithm.

It is recommended that you use the EPF scheduling algorithm to ensure the GBR.

The quality of service (QoS) for VoIP services is introduced to the NodeB of RAN 10.

Therefore, the VoIP delay-sensitive queue is added. This queue has a higher SPI.

The scheduling priority of the delay-sensitive data is higher than that of the traffic-

sensitive data.

1.3.4 Power Control on HSDPA Channels

The HSDPA introduces three types of physical channels to the R5, that is, UL HS-

DPCCH, DL HS-PDSCH, and DL HS-SCCH. Power control on HSDPA channels

refers to power control on these three types of channels. Dynamic power control is

recommended.

Power control on HS-DPCCH

No separate power control is available for the HS-DPCCH. There is a power offset

between the HS-DPCCH and the associated UL DPCCH.

Figure 1-2 Power offset of HS-DPCCH

The output power of the HS-DPCCH is obtained through the following formula:



PHS-DPCCH = PUL DPCCH x 10ΔHS-DPCCH/10

PHS-DPCCH is the output power relative to the UL DPCCH.

For the first timeslot of a TTI, when the UE responds with the ACK message,

ΔHS-DPCCH is equal to ΔACK; when the UE responds with the NACK message,

ΔHS-DPCCH is equal to ΔNACK.

For the second and third timeslots of a TTI, ΔHS-DPCCH is equal to ΔCQI.

The SRNC configures the information about the power offset of the uplink HS-

DPCCH, including PO-ACK (ΔACK), PO-NACK (ΔNACK), and PO-CQI (ΔCQI). PO-

ACK or PO-NACK is used when ACK or NACK is transmitted over the HS-DPCCH.

PO-CQI is used on the timeslot of the CQI.

The UE calculates the power of the HS-DPCCH to the DPCCH according to the PO-

ACK, PO-NACK, and PO-CQI. The value of ΔHS-DPCCH is PO-ACK, PO-NACK, or

PO-CQI in the preceding cases.

Power control on HS-HS-PDSCH and HS-SCCH

The power on downlink HSDPA channels, that is, HS-HS-PDSCH and HS-SCCH, is

controlled by the NodeB-based scheduling algorithm and power algorithm of the HS-

SCCH.

The power algorithms of the HS-SCCH are classified into two types, that is, fixed

power control and power control based on CQI, ACK, NACK, or DTX.

1.3.5 RRM Policies of HSDPA

The HSDPA admission control includes power admission control on streaming and

BE services, and admission control on bandwidth on the Iub interface.

To support the load balancing for inter-frequency networking through the HSDPA, the

potential PUC algorithm and the load balancing algorithm for the downlink DCH and

HSDPA in access state are introduced to the NodeB of RAN 10.

HSDPA load control policies

LDR algorithm: When the cell resources exceed the basic congestion threshold, the

cell enters into the basic congestion state. In this case, the cell triggers the LDR

algorithm to remove the congestion.

OLC algorithm: When the uplink or downlink power in an R99 cell exceeds the uplink

or downlink triggering threshold for OLC, the cell enters into the overload congestion

state. To ensure that the system is stable, fast OLC actions are required to quickly

eliminate the overload congestion in the cell. When the uplink or downlink power in an



R99 cell is lower than the uplink or downlink released congestion for OLC, the cell

enters into the basic congestion state.

PUC algorithm: This algorithm updates the cell reselection parameters of two carriers

according to the load of the two carriers, to control the camping behavior of idle UEs

in hot-spot areas.

Load balancing algorithm for downlink DCH and HSDPA in access state: This

algorithm allows two carriers to balance HSDPA UEs in access state.

1.3.6 Signaling over HS-DSCH

The downlink signaling data is transmitted over the HS-DSCH to save the channel

code resources in the cell. The delay is lower than that when the downlink signaling

data is transmitted over the DCH.

Implementation scheme: Use the F-DPCH to send TPC commands for power control

at the downlink. Transmit the downlink signaling data over the HS-PDSCH. Four

signaling radio bearers (SRBs) can be mapped to one MAC-d flow. When the cell and

UE support the –DPCH, and the downlink signaling bearer policy is to use the HS-

DSCH, transmit t0he downlink signaling data over the HS-DSCH. Otherwise, transmit

the downlink signaling data over the DCH. If the downlink signaling data is not

transmitted over the HS-DSCH due to admission reasons, the RNC tries to transmit

the signaling over the HS-DSCH through the periodical reattempt function of SRB

over HSPA.



Chapter 2 Basic Principles

2.1 Overview of Basic HSDPA Principles

In the R99 specifications, downlink data is sent through the DCH. In the R5, the

HSDPA is used to transmit the downlink data. The downlink signaling, however, needs

to be transmitted through the DCH. CS services also need to be transmitted through

the DCH. In the case of concurrent CS services and PS services, the HSDPA channel

is required to transmit PS services, and DCH is required to transmit CS services and

signaling. At the uplink, the DCH is used to transmit signaling and services, including

PS and CS services. In the R6, the SRB over HSPA is introduced. This feature allows

the HSPA channel to transmit signaling. As the IP QoS mechanism develops, the CS

services can be transmitted on the PS domain, that is, VoIP.

In the R5, one type of transmission channel, that is, HS-DSCH, and three types of

physical channels, that is, HS-SCCH, HS-PDSCH, and HS-DPCCH, are added. In the

R6, to enable the SRB over HSPA, the Fractional-Dedicated Physical Control

Channel (F-DPCH) is added.

2.2 HSDPA Structure

The HSDPA depends on the new channels. In the R5, the HS-PDSCH is used to

transmit the downlink UE data, the HS-SCCH is used to transmit the downlink control

information, and the HS-DPCCH is used to transmit the uplink control information. In

the R6, to transmit the signaling data over the HSPA channels, that is, transmit

downlink signaling over the HS-PDSCH and uplink signaling over the E-DPDCH, the

F-DPCH is used for uplink power control.

The following section describes the F-DPCH in the RAN 10.

2.2.1 F-DPCH

In the R5, the downlink associated DPCH transmits the signaling data and TPC

commands. Each UE is allocated with one downlink DPCH. In this case, the channel

code resources in a cell may be used up before the power resources and thus

become the bottleneck of the cell capacity. In the R6, to enable the SRB over HSPA,

the F-DPCH is added.

The F-DPCH is a special downlink physical control channel as shown in Figure 4.

Every 10-ms frame contains 15 slots. Each slot contains 2560 chips used to transmit

the TPC commands. Compared with the dedicated downlink physical channel in the



R99, the F-DPCH preserves only the TPC field for power control. The F-DPCH is

used for uplink power control. When UEs in RRC_DCH status use HSDPA channels

for downlink transmission, an F-DPCH used to send TPC commands for power

control must be established. Downlink DPCHs conflict with the F-DPCH. When a

DPCH is used for downlink transmission, the downlink DPCCH is used to perform

uplink power control. In this case, you do not need to establish an F-DPCH.

Therefore, the F-DPCH can be regarded as a special downlink DPCCH.

Figure 1-3 F-DPCCH frame structure

A NodeB of RAN 10 allows 10 F-DPCHs to share a channel code with 256 spreading

factors, thus saving the channel code resources and power resources in the cell and

improving the system capacity. A UE uses a 2-bit symbol in a slot to transmit TPC

commands. The Pilot field and TFCI are omitted. An F-DPCH can be regarded as an

associated channel in SRB over HSDPA.

TPC

TPC

TPC

TPC

TPC

TPC

TPC

TPC

TPC

TPC

TPC

TPC

TPC

UE1

UE2

UE3

UE4

UE5

UE6

UE7

UE8

UE9

UE10

P-CCPCH f rameoff set 256chi p（）

0

1

2

3

4

5

6

7

8

9

Figure 1-4 Multiplexing multiple F-DPCHs



2.3 Mobility Management

2.3.1 HSDPA over Iur

The RAN 10 supports the HSDPA over Iur, including the following aspects:

Establishing HSDPA over Iur radio links

Re-configuring HSDPA over Iur radio links

Increasing HSDPA over Iur radio links

Increasing HSDPA over Iur radio links and changing associated service links

Relocating HSDPA over Iur service links to DRNC

Changing HSDPA over Iur service links inside DRNC

Supporting static relocation of HSDPA services

Supporting preemption of HSDPA UEs by DRNC

Updating RL parameters for HSDPA over Iur

Supporting SRB over HSDPA over Iur

HSPA handover over Iur

During HSPA handover over Iur in a DRNC, check the HSPA attributes of the DRNC

and those of the Iur interface separately.

Whether a DRNC can join the HSPA service depends on the following conditions:

The DRNC supports the HSDPA service.

The Iur interface supports handover.

The Iur interface in the DRNC supports transmission of HSDPA service. This is

controlled through a switch on the SRNC side.

Static relocation of HSPA over Iur

When the Iur interface is enabled, the UE can connect to the CN through the SRNC

by using the radio resources of the DRNC. The Iur interface can transmit the DCH

data and HS-DSCH data.



Figure 1-5 Static relocation



Chapter 3 Upgrade Guide

3.1 RNC Upgrade

3.1.1 Upgrade Requirements

The following table lists the recommended RNC versions for commercial use of 3.6

Mbit/s and 7.2 Mbit/s HSDPA and presentation of 14.4 Mbit/s HSDPA

Table 1-1 Recommended RNC versions for commercial use

Recommended RNC VersionSupport HSDPA

7.2 Mbit/s

Support HSDPA 10.1

Mbit/s and 14.4 Mbit/s

BSC6800V100R008C01B071 Yes No



BSC6810V200R010C01B051 Yes Yes

BSC6810V100R010C01B051 Yes Yes

To support the HSDPA, upgrade the RNC to the related version. Unless otherwise

specified, the upgrade procedure in the following section applies to the RNCs of V18,

V29, V110, and V210.

3.1.2 Upgrade Procedure

3) Checking the RNC version

Check the RNC version and the target version before upgrade. You can view the

upgrade guide of the target version to check whether there are rules for upgrading the

existing RNC version to the target version. If there are such rules, you can upgrade

the RNC by using RNC upgrade tools.

4) Upgrading the RNC by using upgrade tools (recommended)

To upgrade the RNC by using upgrade tools, perform the steps according to the

upgrade guide for related version. This document does not specify the upgrade steps.

5) Upgrading the RNC when upgrade tools are unavailable

Verify that the services are normal in the existing RNC.



Export configuration scripts.

Adapt the configuration scripts to the HSDPA feature.

Clear the data on the BAM. Run the configuration scripts. Run the FMT DATA

command to load and reset the RNC from the BAM and verify services.

3.2 NodeB Upgrade

3.2.1 Upgrade Procedure

6) HBBI or EBBI are recommended for the BTS3812E. If these boards are

unavailable, the BTS3812E must be configured with at least one HDLP and one

HULP.

An HBBI can process 128 CEs at the uplink and 256 at the downlink. The uplink

resources of HBBI and HULP can form an uplink resource pool. The downlink

resources of HBBI and HDLP can form a downlink resource pool. An HBBI can

process three cells at the uplink and three at the downlink. The HBBI supports the

HSDPA technology and 14.4 Mbit/s of traffic for each cell.

An EBBI can process 384 CEs at the uplink and 384 at the downlink. The uplink

resources of EBBI and HULP or EULP can form an uplink resource pool. The

downlink resources of HBBI and HDLP or EULP can form a downlink resource pool.

An EBBI can process six cells at the uplink and six at the downlink. The EBBI

supports the HSDPA technology and 30 Mbit/s of traffic for each cell.The EBBI also

supports the HSUPA technology and 15 Mbit/s of traffic for each cell in this case.

To support RAN 10 features, upgrade to a V100R010 or V200R010 NodeB.

7) Upgrading the software

This document provides the suggestions for the upgrade from the R99 to the HSDPA

version. The upgrade procedure varies from one version to another. Refer to the

related upgrade guide.

Upgrade the R99 to the specified HSDPA version. For a commercial office, download

the target version through the OMCH by using the M2000 to the standby workspace

in the NodeB. Then, activate the version at the proper time. Reset the NodeB to

complete upgrade.

Use the CME to prepare the configuration script of an HSDPA version. Download the

script through the OMCH by using the M2000 to the NodeB. Reset the NodeB to

replace the script.

If the script is incorrect, log in to the LMT to check the local commissioning network

port of the NodeB. The default IP address of the port is 17.21.2.15. Download the

modified script or run MML commands to add the related HSDPA attributes.



Chapter 4 Data Configuration Policies

4.1 Building an HSDPA Network

4.1.1 Configuring the GGSN (Huawei)

The HSDPA provides a higher throughput than the R99. This means that the UMTS

supports a higher rate. In this case, you need to run SET QOS to set the capacity on

the gateway GGSN and the 14.4 Mbit/s services supported by the RAN 10.

4.1.2 Configuring the SGSN (Huawei)

To support 14.4 Mbit/s services, run SET 3GSM to upgrade the SGSN to the related

version.

4.1.3 Configuring the HLR Subscription (Huawei)

Run MOD GPRS to set the downlink rate required by an operator. The RAN 10

network supports a maximum downlink rate of 13.976 Mbit/s.

4.2 Checking Transmission Configuration on Iub and Iu Interfaces

4.2.1 Checking Transmission Configuration on Iub interface

Add the types of paths that transmit the HSDPA service on the RNC and NodeB

sides.

For example,

ADD AAL2PATH: PAT=HSPA_NRT;

ADD IPPATH: TFT=HSPA_NRT;

The bandwidth on the RNC side or NodeB side depends on the actual physical

transmission bandwidth on the Iub interface. Make sure that the bandwidth on the

RNC, that is, sustainable cell rate (SCR), is the same as that on the NodeB, that is,

receive cell rate (RCR).

Check the bandwidth of the AAL2 path on the RNC side that transmits the HSDPA

service. Run DSP AAL2PATH to check the actual available bandwidth, that is, SCR.

The HSDPA bandwidth on the NodeB side depends on the RCR. Check the RCR



configuration of the AAL2 path. For the bandwidth configuration, see the Transmission

Configuration Guide.

Configure the bandwidth of an IP RAN by referring to the IP RAN Deployment Guide.

The physical bandwidth for IP transmission is larger than the rate on the Uu interface.

Therefore, the IP bandwidth is recommended to be 15 Mbit/s. In addition, in IP RAN

networking, make sure that the port modes on both ends are the same, that is, 100

Mbit/s full-duplex.

4.2.2 Checking the Bandwidth on Iu-PS Interface

8) Run LST IPOAPVC to query for the traffic parameter index on the user plane.

9) Run LST ATMTRF to query for the rates supported by the traffic index, including

the peak cell rate (PCR) and SCR. If the supported rates are low, change them

to over 100 Mbit/s.

4.2.3 Configuring the NodeB

In versions later than V18, the HSDPA function is enabled by default.

4.2.4 Configuring the RNC

Run ACT CELLHSDPA to enable the HSDPA function in the related cell.

4.3 Service and Bearer Configuration

4.3.1 Configuring the subscription of HSDPA UE

All the UE subscription information is stored on the HLR. The preceding sections

describe the parameters related to the HSDPA attributes. An operator configures the

values of these parameters according to the subscription requirements.

4.3.2 Configuring the HSDPA code allocation

The HSDPA code allocation is based on cells. Fixed code allocation and RNC-based

dynamic code allocation are performed on the RNC side. NodeB based dynamic code

allocation is performed on the NodeB side. The policies for allocating codes on the

RNC and NodeB are as follows:

Recommended mapping between HSDPA RNC dynamic code and NodeB dynamic

code:

1. If the version of the NodeB is V17, enable the RNC dynamic code. A NodeB of V17

does not support the NodeB dynamic code.



2. If the version of the NodeB is V18, V19, or V20, and the version of the RNC is V18,

choose from the following policies:

2.1 Enable the RNC dynamic code. Disable the NodeB dynamic code. A NodeB of a

version later than V17 supports the NodeB dynamic code.

2.2 Enable the NodeB dynamic code and the RNC dynamic code.

3. If the version of the NodeB is V18, V19, or V110, and the version of the RNC is

V29, V110, or V210, enable the dynamic code on the NodeB and use the static code

for the RNC. Configure one HS-PDSCH code and two HS-SCCH codes.

To enable the RNC-based dynamic code allocation policy, set the maximum number

of HS-PDSCH codes to 10, the minimum number of HS-PDSCH codes to 5, and set

the number of HS-SCCH codes to 2, run the following command:

ADD CELLHSDPA: CellId=1, AllocCodeMode=Automatic, HsPdschMaxCodeNum=10,

HsPdschMinCodeNum=5, HsScchCodeNum=2;

To enable the RNC-based static code allocation policy, set the number of HS-PDSCH

code to 1, and set the number of HS-SCCH codes to 2, run the following command:

ADD CELLHSDPA: CellId=1, AllocCodeMode=Manual, HsPdschCodeNum=1, HsScchCodeNum=2,

CodeAdjForHsdpaSwitch=ON;

In addition, pay attention to the restriction on the license number. Run DSP LICENSE

on the LMT of the NodeB to query for the available code resources.

Run SET MACHSPARA to configure the code on the NodeB. To enable the NodeB

based dynamic code allocation policy, run the following command:

SET MACHSPARA: LOCELL=1, DYNCODESW=OPEN;

You cannot detect the dynamic code used by the NodeB on the LMT of the RNC. An

idle code with 16 SFs, however, is occupied by the HSDPA.

4.3.3 Configuring the HSDPA Cell Power

The HSDPA cell power is configured on the RNC. Run ADD CELLHSDPA to

configure the static power and dynamic power. The power is relative to the maximum

transmit power in the cell. For example, to set the overall HSDPA power to the

maximum transmit power in the cell, run the following command:

ADD CELLHSDPA: CellId=1, HspaPower=0;

If the HSDPA power is the same as the maximum transmit power of the cell, it is

regarded as dynamic power. Otherwise, it is regarded as static power.

4.3.4 Configuring HSDPA Scheduling and Flow Control



Four scheduling algorithms are supported. Run SET MACHSPARA to configure the

algorithm on the NodeB. For example, to use the EPF scheduling algorithm, run the

following command:

SET MACHSPARA: SM=EPF;

Flow control on the NodeB (BW_SHAPING_ONOFF_TOGGLE is enabled by default):

To enable the BW_SHAPING_ONOFF_TOGGLE policy, run the following command:

SET HSDPAFLOWCTRLPARA: SWITCH=BW_SHAPING_ONOFF_TOGGLE;

VP backpressure on the RNC side

For an RNC of V110, run the following command to turn on the backpressure switch

on the OSE and PIE interface boards:

SET PORTFLOWCTRLSWITCH: OSEFlowCtrlSwitch=ON, PIEFlowCtrlSwitch=ON;

For an RNC of V210, run the following command to enable flow control on the AEU,

AOU, UOI, GOU, and FG2 interface boards:

SET PORTFLOWCTRLSWITCH: AEUFlowCtrlSwitch=ON, AOUFlowCtrlSwitch=ON,

UOIATMFlowCtrlSwitch=ON, UOIIPFlowCtrlSwitch=ON, GOUFlowCtrlSwitch=ON,

FG2FlowCtrlSwitch=ON;

Add a virtual port:

ADD VP;

4.3.5 Configuring HSDPA Power Control

Run SET HSDPCCH on the LMT of the RNC to configure the power control on the

HS-DPCCH. It is recommended that you use the baseline parameter values.

Run SET MACHSPARA on the LMT of the NodeB to configure the power control on

the HS-SCCH. It is recommended that you use the CQI-based adaptive power

control. For example, to adjust the HS-SCCH power control based on the CQI and set

the frame error rate to 1%, run the following command:

SET MACHSPARA: SCCHPWRCM=CQI, SCCHFER=1;

To set the power margin of the cell to 5% of the baseline value, run the following

command:

SET MACHSPARA: PWRMGN=5;

In versions later than the VX10, as the standard for quality control on the Uu

interface, the default value of the IBLER parameter is 0%.

SET MACHSSPIPARA: CQIADJA=NO_CQI_ADJ;



4.3.6 Configuring the QoS Mechanism for HSDPA

Run SET USERPRIORITY to map the ARP priority to the SPI. The following

command sets the UE level of each ARP priority.

SET USERPRIORITY: ARP1Priority=Gold, ARP2Priority=Gold, ARP3Priority=Gold,

ARP4Priority=Gold, ARP5Priority=Gold, ARP6Priority=Silver, ARP7Priority=Silver,

ARP8Priority=Silver, ARP9Priority=Silver, ARP10Priority=Silver,

ARP11Priority=Copper, ARP12Priority=Copper, ARP13Priority=Copper,

ARP14Priority=Copper;

Run SET SCHEDULEPRIOMAP to map the UE service type and class to the SPI.

For example,

SET SCHEDULEPRIOMAP: TrafficClass=INTERACTIVE, UserPriority=SILVER, THP=10, SPI=5;

Run SET USERGBR to configure the GBR for BE services. For example,

SET USERGBR: GoldUlGBR=D128, GoldDlGBR=D128, SilverUlGBR=D64, SilverDlGBR=D64,

CopperUlGBR=D32, CopperDlGBR=D32;

In the preceding example, the GBR parameters use the baseline values. The values

can be changed according to the operator requirements.

4.3.7 Configuring the HSDPA License

You need to apply license for 14.4 Mbit/s, 7.2 Mbit/s, and 3.6 Mbit/s services for an

RNC. The RAN 10 supports the peak rate of a single HSDPA UE of 13.976 Mbit/s.

Run the following command to enable the HSDPA 13.976 Mbit/s function:

ACT LICENSE: ISPRIMARYPLMN=YES, FUNCTIONSWITCH3= HSDPA_13_976MBPS-1;

4.3.8 Configuring SRB on HS-DSCH

To set the channel type preferred by SRB, run the following command:

SET FRCCHLTYPEPARA: SrbChlType=HSDPA;

To configure the power control parameters of the F-DPCH, run the following

commands:

SET FDPCHPARA; SET FDPCHRLPWR;

To add typical parameters for SRB on HSDSCH, run the following command:

ADD TYPSRBHSPA: TrchType=TRCH_HSDSCH;

To set the length of the periodical retry timer of SRB over HSPA, run the following

command:

SET COIFTIMER: SrbOverHspaRetryTimerLength=10;



To set the length of the SRB D2H protective timer, run the following command:

SET HOCOMM: SrbD2HHoTimerLength=5;

Run SET DEFAULTTRMMAP or ADD TRMMAP to set the SRB on an HSDPA path.

Run SET DEFAULTFACTORTABLE or ADD FACTORTABLE to set the SFs for SRB

over HSDPA.

4.3.9 Configuring the HSPA over Iur

Enable the HSDPA or HSUPA function in the adjacent RNC and the HSDPA function

on the Iur interface.

MOD NRNCCELL: NRncId=1, CellId=1, CellCapContainerFdd=HSDSCH_SUPPORT-

1&FDPCH_SUPPORT-1;

MOD NRNC: NRncId=1, IurHsdpaSuppInd=ON;

Note:

Query for the preceding parameters. If the values of the parameters are the baseline

values, you do not need to change the values.

4.4 Configuring Radio Resource Management

4.4.1 Configuring HSDPA Measurement Control

During deployment, use the baseline values of the following parameters. You do not

need to change the values of these parameters.

Configuration related to HSDPA measurement includes configuration of the

measurement switch and measurement period. Run MOD CELLALGOSWITCH to

configure the measurement switch. To measure the GBP and PBR in the cell, run the

following command:

MODCELLALGOSWITCH:NBMCacAlgoSwitch=HSDPA_GBP_MEAS-

1&HSDPA_PBR_MEAS-1;

Run SET LDM to configure the measurement period. To set the basic downlink

measurement period to 200 ms, run the following command:

SET LDM: ChoiceRprtUnitForDlBasicMeas=TEN_MSEC, TenMsecForDlBasicMeas=20;

To set the HSDPA GBP measurement period and HSDPA PBR measurement period

to 1 second, run the following command:



SET LDM: ChoiceRprtUnitForHsdpaPwrMeas=TEN_MSEC, TenMsecForHsdpaPwrMeas=100;

SET LDM: ChoiceRprtUnitForHsdpaRateMeas=TEN_MSEC, TenMsecForHsdpaPrvidRateMeas=100;

4.4.2 Configuring HSDPA Admission Control



Run the following command to turn on the HSDPA admission control switch:

ADD CELLALGOSWITCH: NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1;

Run the following command to turn on the admission switch for Iub bandwidth

congestion:

V110: SET CACALGOSWITCH: CacSwitch=IUB_CONG_CAC_SWITCH-1&NODEB_CREDIT_CAC_SWITCH-1;

V110: ADD CELLALGOSWITCH: NBMCacAlgoSwitch=IUBBAND_ADCTRL-1;

Run the following commands to configure admission control on the CE resources:

SET CACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-1;

ADD CELLALGOSWITCH: NBMCacAlgoSwitch=CRD_ADCTRL-1;

4.4.3 Configuring HSDPA Load Control



When congestion occurs to a cell, the system can take multiple actions to relieve the

congestion. However, few actions are related to the HSDPA service. The following

commands are related to the HSDPA service.

Run SET CORRMALGOSWITCH to turn on the HSDPA state transition switch, and

intra-frequency D2H and inter-frequency D2H algorithm. For example,

SET CORRMALGOSWITCH: HspaSwitch=HSDPA_STATE_TRANS_SWITCH-1,

DrdSwitch=INTER_HO_D2H_DRD_SWITCH-1&INTRA_HO_D2H_DRD_SWITCH-1;

Run ADD CELLALGOSWITCH to turn on the switch of the load reshuffling, code

resource reshuffling, or CE resource reshuffling algorithm. For example,

ADD CELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch=ULLDR-1&DLLDR-1&CELL_CODE_LDR-

1&CELL_CREDIT_LDR-1;

Run ADD CELLLDR to set the parameters of the load reshuffling algorithm in a cell.

You can also set the service types in the cell through traffic division.

ADD CELLINETSTRATEGY: R99CSSepInd=TRUE, R99PSSepInd=TRUE;



In dual-carrier networking mode, the following commands are involved. For the

configuration, see Chapter 5.

Enable the PUC algorithm to balance the number of UEs in idle state. Run the

following command:

ADD CELLPUC;

Enable the directed retry decision (DRD) algorithm to balance the load among UEs in

access state. Run the following command:

SET CORRMALGOSWITCH: DrdSwitch=DRD_SWITCH-1&HSDPA_DRD_SWITCH-1&HSUPA_DRD_SWITCH-1;

SET DRD: ServiceDiffDrdSwitch=OFF, LdbDrdSwitchDCH=ON, LdbDrdSwitchHSDPA=ON,

LdbDRDchoice=UserNumber;

Run the following command to configure the mobility management:

ADD INTERFREQNCELL:BlindHoFlag=TRUE, BlindHOPrio=0;

4.5 Typical HSDPA Configuration in Competition Scenario (14.4 Mbit/s)

10) Set the size of the MAC-PDU to 1296 to improve the MAC-HS transmission

efficiency. Run the following command to select the related service index: LST

TYPRAB: QueryType=QUERY_BY_RABINDEX; Find out the required index

number of downlink subscription. Then, change the MAC-PDU size.MOD TYPRABHSPA: RabIndex=##, TrchType=TRCH_HSDSCH, HsdschMacdPduSize=1296;

11) Disable CQI offset handling on the NodeB.

SET MACHSSPIPARA: CQIADJA=NO_CQI_ADJ;

12) Ensure that the transmission resources are sufficient.

13) In the direct connection environment, enable VP backpressure in the RNC. Then,

change the flow control mode of the NodeB to simple flow control or no flow

control.

14) Activate the license for a single 13.976 Mbit/s UE in the RNC.

15) Enable the NodeB dynamic node. Configure one static code for the HS-PDSCH

in the RNC. Configure two codes for the HS-SCCH.

16) Check the license of the NodeB. The license for 16QAM and 15 HS-PDSCH

codes is required.

Dsp licence;

SET MACHSPARA: 16QAMSW=OPEN;

17) Configure the dynamic power for the HSDPA.

18) Check that the maximum rate of the SGSN, GGSN, and HLR reaches 14.4

Mbit/s.





Chapter 5 Networking Strategy

5.1 Overview

As the HSDPA technology grows rapidly, it is an inevitable trend to introduce the

HSDPA to commercial networks. Therefore, the dual-carrier technology is introduced.

It becomes a key concern to process the R99 and HSDPA services in the dual-carrier

environment.

Considering the actual operation scenarios and industrial strategies, a clear

prerequisite for introducing the HSDPA is that the HSDPA service does not impact the

existing R99 service. That is, the R99 service is preferred in resource allocation over

the HSDPA service in the following aspects:

19) The R99 and HSDPA services can dynamically share power resources.

However, the R99 is always preferred.

20) The R99 and HSDPA services can dynamically share code resources. However,

the R99 is always preferred.

21) The R99 and HSDPA services fully share transmission resources. However, the

R99 is preferred.

To ensure that the HSDPA service does not fail, configure a GBR for the HSDPA

service to guarantee the minimum power, code, and transmission resources.

For the dual-carrier service that incorporates the HSDPA, an operator needs to

research the existing R99 features. The operator needs to put more efforts in

allocating code, power, and transmission resources between the HSDPA and the

R99, thus reaching the highest efficiency.

5.2 Allocation Strategy in Dual-Carrier Service

The F1 carrier provides continuous R99+HSDPA coverage. In hot-spot areas, an

inter-frequency F2 carrier is added. The F2 carrier supports R99 and HSPA services.

A UE can camp in both carriers. In this scenario, BE services are transmitted over the

HSPA. R99 services mainly include CS services.

Figure 1-1 Dual-carrier application



5.2.1 Load Balancing Based Solution

This solution does not consider the interference between an R99 UE and an HSPA

UE. It shares the load between two carriers through the PUC algorithm in idle state,

the load balancing based DRD algorithm in access state, and the LDR algorithm in

connection state.

I. Network strategy

F1 carrier configuration

The carrier service priority uses the baseline configuration. No priority is used for

service bearer.

Use the static allocation mode to allocate HSDPA codes in the RNC. Set the number

of HS-PDSCH codes to 5, and the number of HS-SCCH codes to 4. Use the fully

share mode for the HSDPA power in the cell. Turn on the NodeB dynamic code switch

in the NodeB.

The HSUPA cell uses the baseline configuration.

F2 carrier configuration

The carrier service priority uses the baseline configuration. No priority is used for

service bearer.

Use the static allocation mode to allocate HSDPA codes in the RNC. Set the number

of HS-PDSCH codes to 5, and the number of HS-SCCH codes to 4. Use the fully

share mode for the HSDPA power in the cell. Turn on the NodeB dynamic code switch

in the NodeB.

The HSUPA cell uses the baseline configuration.

Table 1-1 Configuration comparison between F1 carrier and F2 carrier

Networking Strategy F1 Carrier F2 Carrier

Carrier camping policy NOT_Barred NOT_Barred

Priority of R99 real-time services 1 1

Priority of R99 non-real-time services 1 1

Priority of HSPA service 1 1

HSDPA code allocation mode Manual Manual

Number of HS-PDSCH codes 5 5

Number of HS-SCCH codes 4 4



Networking Strategy F1 Carrier F2 Carrier

Offset of overall HSPA power to maximum

cell transmit power (0.1dB)0 0

HSDPA-based code tree reshuffling switch ON ON

NodeB dynamic code switch ON ON

Number of E-AGCH codes 1 1

Number of E-RGCH/E-HICH codes 1 1

Maximum target value of uplink load factor 75 75

Ratio of the power received by non-serving

E-DCH to the total power received by the E-

DCH (%)

0 0

Mobility management configuration

Adjacent cells in a carrier are intra-frequency neighbor cells.

Configure the cells in F1 and F2 carriers as inter-frequency blind handover cells

(BlindHOFlag=TRUE).

Configure F2 cells at the edge of the F2 carrier and adjacent non-hot spot F1 cells as

unidirectional inter-frequency neighbor cells.

When a UE in the F2 carrier roams from a hot-spot area, perform inter-frequency

handover from an F2 cell to a non-hot spot F1 cell.

Figure 1-2 Mobility management

When a UE gets to a hot-spot area, perform intra-frequency handover in F1 cells.

Configure cells in both carriers as inter-system 2G neighbor cells.



Note:

Such configuration ensures the continuity of R99 and HSPA services when a UE

moves into or out of a hot-spot area. Make sure that the edges of the hot-spot areas

are continuously covered.

II. Load control policies for UEs in idle state in hot-spot areas

Enable the PUC algorithm in hot-spot areas. After a UE enters into a hot-spot area

covered by two carriers, the UE can camp in any carrier. The system updates the cell

reselection parameters of the two carriers through the PUC algorithm according to the

load status of the carriers, and controls the camping behavior of a UE in idle state in

the hot-spot area.

Note:

The load balancing algorithm in access state can balance the number of accessed

UEs among two carriers. The DRD success rate, however, cannot be guaranteed.

The load balancing algorithm in idle state can reduce the attempts of inter-frequency

directed retry by UEs and ensure the access success rate.

III. Load control policies for UEs in access state in hot-spot areas

The load balancing of the downlink DCH and HSDPA in access state are mainly

involved.

Set the admission algorithm for all the cells to power admission. Turn on the DRD

switch for downlink load balancing in F1 and F2 cells. Turn off the DRD switch for the

service hierarchy. Set the DRD load balancing offset of DCH and HSDPA to 5%. Set

the DRD load space threshold for DCH load balancing to 35%. Set the DRD load

space threshold for HSDPA load balancing to 100%. Set the maximum number of

equivalent R99 users at the downlink to 80 and the maximum number of HSDPA

users to 64.

Such configuration can balance the number of HSDPA users in access state among

the two carriers. In addition, the number of DCH equivalent users is balanced when

the DRD load space conditions for DCH load balancing are met.

For the downlink HSDPA service, the DRD load space threshold for HSDPA load

balancing is 100%. Therefore, the DRD algorithm is valid since the time when the first

HSDPA user is connected to the system. To reduce the directed retry attempts

between the two carriers, the DRD load balancing offset for HSDPA users is set to



5%. In this case, only when the variance of HSDPA users between the two carriers is

greater than 3, that is, 64 x 5%, HSDPA users are allocated to a cell with a small

number of users through the DRD. Thus, HSDPA users in F1 and F2 cells are

balanced.

When the variance of HSDPA users between the two carriers does not exceed 3, no

DRD is performed for the connected HSDPA users. When the variance is greater than

3 due to reasons such as user movement and release of original connected users,

the system allocates new HSDPA users to the carrier with a smaller number of

HSDPA users through the DRD.

Figure 1-3 DRD policy in dual-carrier

For the DCH service, when the load in F1 and F2 cells is not heavy, the load

balancing policy for DCH users in cells is not valid. In this case, the establishment of

an R99 user in the two carriers depends on the camping behavior of users in idle

state. When the number of R99 equivalent users in a carrier exceeds 52, that is, 80 x

65%, the balancing mechanism for R99 users is valid. After that, if the variance of

R99 equivalent users between the two carriers exceeds 4, that is, 80 x 5%, R99 users

connected to the carrier with a larger number of R99 equivalent users are allocated to

the other carrier through the DRD. Thus, R99 users in both carriers are balanced.

See the following figure.



Figure 1-4 DRD policy in dual-carrier

When the DRD load space thresholds in F1 and F2 cells are not reached, no

balancing on R99 equivalent users is performed. Only when the DRD load space

threshold for DCH load balancing in a cell is reached, and the variance of R99

equivalent users in F1 and F2 cells exceeds the DRD offset for DCH load sharing,

balancing on R99 equivalent users is performed.

Table 1-1 Reference settings for user access policies in F1 and F2 carriers

Access Policy F1 Carrier F2 Carrier

Admission algorithm Power prediction Power prediction

DRD algorithm for service hierarchy OFF OFF

DRD algorithm for load balancing ON ON

Object of DRD load balancing UserNum. UserNum.

DRD offset for DCH service load

balancing5% 5%

DRD offset for HSDPA service load

balancing5% 5%

DRD load space threshold for DCH

service load balancing35% 35%

DRD load space threshold for HSDPA

service load balancing100% 100%

Maximum number of downlink

equivalent users in cell80 80



Maximum number of HSDPA users in

cell64 64

Note:

The RAN 10 does not perform load balancing on HSUPA users in access state.

However, uplink and downlink HSPA users are carried over the HSPA channels.

Therefore, when the HSDPA users are balanced, the HSUPA users can be balanced

to some extent.

Note:

The traffic structure varies from one network to another. In a network, the user

number may be balanced, but the load is not. In this solution, the user number

balancing is involved. This is because the power resources can be balanced through

the LDR algorithm.

IV. Load control policies for UEs in connection state in hot-spot areas

Turn on the DCCC switches for uplink and downlink R99 BE services and HSUPA

service.

SET CORRMALGOSWITCH: ChSwitch=DCCC_SWITCH-1,

HspaSwitch=HSUPA_DCCC_SWITCH-1;

Enable the LDR algorithm based on CE resources and power resources at the uplink,

and LDR algorithm based on power resources and code resources at the downlink in

both carriers.

SET LDCALGOPARA: LdcSwitch=NODEB_CREDIT_LDR_SWITCH-1;

ADD CELLALGOSWITCH: CellId=1, NBMLdcAlgoSwitch=UL_UU_LDR-

1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR-1;

Note:

The users in access state in the two carriers are balanced. Therefore, both carriers

have R99 and HSPA users. In such a traffic model, the first restricted resources at the

uplink of a cell are CE or power resources, and those at the downlink are power or

code resources.



Configure the LDR actions at the uplink in the cells of the two carriers in sequence as

follows: BE traffic rate reduction, inter-frequency load handover, and CS inter-system

load handover. Configure the LDR actions at the downlink in sequence as follows:

code reshuffling, BE traffic rate reduction, inter-frequency load handover, and CS

inter-system load handover.

To set the LDR actions, make sure that the HSPA users are preferred during action

execution when the CN priority is the same.

SET USERPRIORITY: PriorityReference=ARP, CarrierTypePriorInd=DCH;

To avoid frequent changes in inter-frequency load handover, set the threshold of load

space for uplink and downlink inter-frequency load handover in the cell to 20%. Set

the upper limit of uplink and downlink inter-frequency load handover bandwidth to 200

Kbit/s to avoid overlarge fluctuations to the load in the destination cell after inter-

frequency load handover.

Enable inter-frequency load handover triggered by code resource congestion.

Table 1-2 Reference settings for LDR policies in F1 and F2 carriers

LDR SettingsF1/F2 Carrier

Uplink Downlink

Triggered by power resource ON ON

Triggered by code resource - ON

Triggered by CE resource ON OFF

LDR action 1BE traffic rate

reductionCode reshuffling

LDR action 2Inter-frequency

load handover

Inter-frequency

load handover

LDR action 3CS inter-system

load handover

BE traffic rate

reduction

LDR action 4 -CS inter-system

load handover

Cell load space threshold for inter-

frequency load handover20% 20%

Maximum bandwidth for inter-frequency

load handover user200000 200000



LDR SettingsF1/F2 Carrier

Uplink Downlink

Number of users with BE traffic rate

reduction1 1

Number of users in CS inter-system load

handover3 3

Inter-frequency load handover on code

resource congestion- ON

Threshold for variance of occupied code

resources in inter-frequency load

handover

- 13%

Threshold of SFs reserved for uplink LDR

creditSF8 -

Load control switch for gold users OFF

Reference comprehensive priority ARP

Reference bearer priority DCH

Note:

In the R99+HSPA dual-carrier scenario, BE services are transmitted over the HSPA.

R99 services mainly include CS services. Therefore, the most efficient action to

release the uplink LDR status is to reduce the HSUPA BE traffic service. The most

efficient action to release the downlink LDR status is to perform inter-frequency load

handover of R99 CS services.

Chapter 6 Troubleshooting

When a problem occurs after the HSDPA is enabled, follow the steps listed in the

HSDPA Check List to perform self check. If the problem persists, locate the problem

by referring to the UMTS Maintenance Department HSDPA Throughput



Troubleshooting Guide – Primary. If the problem persists, collect the logs according to

the HSDPA Information Collection Guide and submit them to the HQ for analysis.

6.1 Services Cannot Be Connected to HSDPA Channels

22) Check the HSDPA category of the UE.

23) Check that the subscription rate of the SIM card is correct.

24) Check that the initial rate reaches the access threshold for HSDPA channels.

25) Run DSP CELL on the RNC to check that the HSDPA of the related cell is

available.

6.2 Download Rate is 0 after HSDPA is Enabled

Run DSP AAL2PATH or DSP IPPATH to check that the transmission on the Iub

interface is normal. If the Iub interface uses the IP transmission mode, ping the peer

IP address on the LMT.

6.3 HDSPA Service Download Rate is Low

26) Check that the UE supports downloading at high rate.

27) Check the transmission configuration for lack of bandwidth.

28) Check that the traffic indexes used by the paths of the RNC and NodeB are

correct.

29) Check that the path configuration on the RNC is the same as that on the NodeB.

If the RCR on the NodeB is larger than the sending bandwidth on the RNC,

packets are discarded due to the low rate.

Recommended configuration: NodeB’s RCR=RNC’ s SCR, RNC’ s SCR=PCR-1

30) Check that the TRM mapping is correct.

Run LST TRMMAP to check that the service mapping is normal.

For example, during interactive HSDPA services, set TRFTYPE to HSDPA_NRT.

If the transmission rate is significantly improved after the NodeB uses simple flow

control, the problem may caused by transmission issues on the Iub interface, such as

packet loss and jitter.

6.4 Rate of 7.2 Mbit/s High-Rate Service is Low

During a test in a certain office, the download rate of the 7.2 Mbit/s HSDPA was low.

Check whether the download service requires a single thread or multiple threads. For

a single-thread service, the possible causes are as follows:

Subscription rate

Size of TCP receiving window on the PC side (modifiable through a DRTCP tool)



Rate restriction at server

Packet loss rate at TCP layer

Sequential or non-sequential (the non-sequential mode is favorable for the

uplink)

Rate restriction on Iu interface (check that the bandwidth at the user plane on the

Iu interface is sufficient)

Packet loss rate on Iub interface

Rate restriction on Iub interface (check that the bandwidth is sufficient)

Block error rate on Uu interface (the radio environment quality)

Gain due to the RTT delay of the uplink 384 Kbit/s lower than that of the initial 64

Kbit/s rate

CQI

The possible causes for multi-thread services are as follows:

Iub interface configuration issues (see the preceding configuration reference)

Note:

For an IP networking environment, troubleshoot all the ports. Make sure that all the

ports, including those on the CN and switches, work in full-duplex mode.

Rate restriction on the Iu interface

Poor radio environment quality (check Ec/N0 through the LMT or other tools)

Lack of data sources due to packet loss in the CN data source

The most possible cause is the low rate at the application layer due to incorrect

configuration and terminal drive of the laptop.

The recommended configuration of a laptop is as follows: 1 Gb memory, high-

performance CPU, and E270 terminal with the latest drive release. In such

configuration, packet loss does not occur to the CN. The common problem is that the

rate is limited to 4 Mbit/s. The application layer performance is important, especially

for high-rate applications.

6.5 HSDPA Service Rate Remains at 2 Mbit/s

The test on a certain office showed that the rate of the HSDPA service remained at 2

Mbit/s. The CQI on the Uu interface was good. The data sources were sufficient.

However, few resources were allocated. It means that the NodeB received little data.

This was similar to the rate restriction in the previous RNC. This problem was caused

by the transmission configuration on the Iub interface. The object of flow control on

the HSDPA bandwidth was the RCR of the NodeB. The RCR was 2 Mbit/s. As a

result, the rate of the HSDPA service was 2 Mbit/s.



Chapter 7 Appendix

7.1 RNC-related MML commands

Table 1-1 RNC-Related MML Commands

MML Command Function

ADD NODEB To set the protocol version of a NodeB

ADD CELLHSDPA To set the basic HSDPA resources of a cell

ACT CELLHSDPA To enable the HSDPA function of a cell

DEA CELLHSDPA To disable the HSDPA function of a cell

ADD CELLCACTo set the parameters of the HSDPA admission control

algorithm

SET

CORRMALGOSWITCHTo set the HSDPA algorithm switch

SET FRCTo set the parameters of the basic HSDPA configuration

algorithm

SET

SCHEDULEPRIOMAPTo set the service scheduling priority

ADD TYPRABBASIC/

MOD TYPRABTo add or change a typical service index

ADD

TYPRABRLC/MOD

TYPRABRLC

To add or change RLC parameters of a typical RAB.

ADD

TYPRABOLPC/MOD

TYPRABOLPC

To add or change the OLPC parameter configuration of

the typical RAB.

ADD

TYPRABHSPA /MOD

TYPRABHSPA

To add or modify the HSPA information about a typical

RAB.




LST TYPRAB To list the information about the typical RAB parameters.

SET HSDPCCH

To set the RNC-oriented HS-DPCCH power offset. The

RNC changes the HS-DPCCH power offset based on the

actual initial SIR target of the UL DPCCH. This ensures

that the power requirement on the HS-DPCCH changes

little when the initial SIR target of the UL DPCCH differs.

ADD

CELLHSDPCCH/MOD

CELLHSDPCCH

To add a set of HS-DPCCH power offset values

corresponding to the initial SIR target that is specified

based on the UL DPCCH. The RNC changes the HS-

DPCCH power offset based on the actual initial SIR

target of the UL DPCCH. This ensures that the power

requirement on the HS-DPCCH changes little when the

initial SIR target of the UL DPCCH differs.

SET HOCOMM To set the parameters related to the HSDPA handover.

ADD AAL2PATH

To set the AAL path to bear the user plane channel

during ATM transmission and set the path type to HSPA

for the HSDPA service.

ADD IPPATH To add an IP path of the HSPA type

ADD IPOAPVC To set the IPoA PVC required for IP transmission.

ADD ATMTRF

To set the ATM traffic records. These records are public

resources and can be used by IPoA PVC, AAL2 path,

SAAL, and CMB PVC.

7.2 NodeB Related MML Commands

Table 1-2 MML commands related to the NodeB


ADD AAL2PATH To set the AAL2 path related to the HSDPA service

ADD IPPATH To set the IP path related to the HSDPA service

SET MACHSPARATo set the related algorithms and functions of the

HSDPA



SET

HSDPAFLOWCTRLPARATo set the flow control switch of the HSDPA

SET MACHSSPIPARATo change the values of scheduling parameters of the

Mac-hs SPI


Documents

RAN 10 HSDPA Deployment Guide-20080821-A-2.0