hsupa deployment guidelines

HSUPA Deployment Guide INTERNAL

2009-06-02 Huawei Confidential of 14

BOM Code Product

Name WCDMA NodeB&RNC

Intended Audience INTERNAL Product

Version

Prepared by

UMTS Maintenance Department

Manual Version

RAN11 HSUPA Deployment Guide

Prepared by

RNC Team of UMTS Maintenance Department

Date 2009-04-20

Reviewed by Date

Reviewed by Date

Approved by Date

Huawei Technologies Co., Ltd.



RAN11 HSUPA Deployment Guide Keywords: HSUPA, deployment, HARQ, MAC-e scheduling Abstract: This document describes the preparations for deployment, basic principles,

upgrade precautions, and preliminary data configuration policy of High Speed

Uplink Packet Access (HSUPA). This document can be used as a guide for the

deployment of RAN11 HSUPA. The information in this document is for

deployment reference only and cannot be used as a basis for answering customer

queries. As the networking policy is introduced as a professional service, the

original contents related to the networking policy are deleted. In addition, the

original FAQs are integrated into the Guide to HSPA Data Transmission

Problem Location.

Acronyms and abbreviations:

Table 1 Acronyms and abbreviations

Acronym and Abbreviation Expansion

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

E-AGCH E-DCH Absolute Grant Channel

E-DPCCH E-DCH Dedicated Physical Control Channel

E-DPDCH E-DCH Dedicated Physical Data Channel

E-HICH E-DCH HARQ Acknowledgement Indicator Channel

E-RGCH E-DCH Relative Grant Channel

E-RNTI E-DCH Radio Network Temporary Identifier

E-TFC E-DCH Transport Format Combination



FP Frame Protocol

HARQ Hybrid Automatic Repeat Request

HSDPA High Speed Downlink Packet Access

HSUPA High Speed Uplink Packet Access

IR Increment Redundancy

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 HSUPA

With the introduction of High Speed Downlink Packet Access (HSDPA) in 3GPP R5, the downlink capacity of the system is improved and the maximum rate per user is greatly increased. The improvement in downlink performance is very important for the radio communication system. With the application of multimedia communication and PS data transmission (email, multimedia file transmission, interactive gaming, and so on), a higher uplink data rate is required.

Thus, High Speed Uplink Packet Access (HSUPA) is introduced in 3GPP R6. HSUPA enhances the throughput of a cell and provides a higher data rate. This can improve the uplink capacity usage of the Uu interface and the experience of end users.

Technically, HSUPA introduces high-speed uplink E-DCHs and other related channels, and the HSUPA entity MAC-e is placed in a NodeB to increase the response speed. In addition, multiple key technologies (such as HARQ, NodeB-based fast scheduling, shorter TTI, and uplink multi-code transmission) are used to implement a maximum theoretical rate of 5.76 Mbit/s at the physical layer of uplink PS services. In PHASE1 (RAN6.0), the maximum uplink rate at the physical layer per user is 1.44 Mbit/s. In PHASE2 (RAN10.0 and later versions), the maximum uplink rate at the physical layer per user is 5.76 Mbit/s.

1.2 Availability

1.2.1 Network Elements Involved

The HSUPA feature involves the NodeB, RNC, and CN. √ indicates the network elements (NEs) involved in the HSUPA feature.

Table 2 NEs involved in the HSUPA feature

UE NodeB RNC MSC Server MGW SGSN GGSN HLR

√ √ √ – – – – –



Note: –: not involved √: involved

1.2.2 Supporting Versions

In RAN11, only some algorithms and commands related to HSUPA are modified and optimized, and little change is made to the contents related to the deployment. Table 3 lists the versions involved in RAN11.

Table 3 Versions involved in HSUPA RAN11

Product Version

BSC6800 V100R011 and later releases RNC

BSC6810 V200R011 and later releases

DBS3800 V100R011 and later releases

BTS3812A V100R011 and later releases

BTS3812E V100R011 and later releases NodeB

DBS3900 V200R011 and later releases

1.2.3 Other Requirements

None.

1.3 Implementation

After HSUPA is introduced, the protocol structure of the UTRAN changes, as shown in Figure 1-1.



Figure 1-1 Protocol structure of the UTRAN after HSUPA is introduced

On the NodeB side, the MAC-e entity is introduced to process HARQ retransmission, scheduling, and MAC-es demultiplexing/reordering.

On the RNC side, the MAC-es entity is introduced in the SRNC to ensure that packets are transmitted in an order and the soft handover is performed between NodeBs. The E-DCH supports multiple services simultaneously, and the UE can multiplex multiple DCHs with different QoS requirements to one MAC-d flow. A maximum of eight MAC-d flows can be multiplexed to the E-DCH for transmission with each TTI. As the DTCH and DCCH can be mapped to the E-DCH, the layer structure above layer 2 does not need to be changed. In this case, the definition in R99 or R5 can be used to simplify the requirements for implementation and test.

On the UE side, the MAC-es/e entity is introduced between the MAC-d entity and physical layer to implement HARQ retransmission, scheduling, MAC-e multiplexing, and E-DCH TFC selection. In addition, the C/T function is deleted from the MAC-d. In this case, the MAC-d transparently transmits logical channel flows to the MAC-es/e. The MAC-es/e can multiplex one or more logical channels to the same MAC-d flow.



Chapter 2 Upgrade Guide

2.1 RNC Upgrade

The HSUPA service shares signaling and resources on the user plane with R99 and

HSDPA services, and the hardware architecture of the RNC does not need to be

changed. The WFMRc, however, is required for the V1 platform to support a higher

throughput. Table 4 lists the requirements for the hardware and software.

Table 4 Requirements for the hardware and software of the RNC

Software Version of RNC Hardware Upgrade

Remarks

BSC6800V100R011 Yes The WFMRc is required.

BSC6810V200R011 No

For details on the upgrade, see the related upgrade guide.


None.

2.2 NodeB Upgrade

The HSUPA entity is located in the NodeB and the requirements for hardware are the

same as those in RAN10. Table 5 lists the requirements for the software version.

Table 5 Requirements for the software version of the NodeB

NodeB

Model Software Version

Hardware

Upgrade Remarks

3812E BTS3812EV100R011 Yes

3812A BTS3812AV100R011 Yes

The EBBI is

required.

The EULP is

required.

3806/3806C DBS3800V100R011 Yes The EBBC is

required.

3900 DBS3900V200R011 Yes The EBBC is

required.



For details on the upgrade, see the related upgrade guide.


None.

Chapter 3 Data Configuration

This chapter describes parameter configuration on the CN side, RNC side, and NodeB side. For more detailed parameter and algorithm settings, see the related RAN feature description. The parameter configuration on the CN side is based on Huawei SGSN, GGSN, and HLR. For non Huawei equipment, the configuration commands may be different. Therefore, you need to contact CN engineers or customers for confirmation and modification.

3.1 Parameter Configuration on the CN Side

HSUPA is transparent to the RLC layer and above, but a higher uplink rate also brings higher requirements for the CN. This chapter describes the parameters to be modified on the CN side after HSUPA is introduced.

You need to modify the subscription information based on the requirements of the telecom operator and the actual network capability. For a subscriber, you need to run the following commands to modify the maximum uplink and downlink rates and guaranteed rates. For a new user, you also need to run the following commands for modification after adding the user.

MOD GPRS: IMSI="460001104002001", PROV=TRUE, CNTXID=1, MAXBRDWL=8192, MAXGBRDWL=8192, MAXBRUWL=5760, MAXGBRUWL=5760;

After modifying the subscription information in the HLR, you need to modify QoS parameters on the GGSN and SGSN to adjust the uplink and downlink maximum bit rates.

//GGSN maintenance console

SET QOS: MBRDNLK=8192, MBRUNLK=5760;

//SGSN maintenance console (254 indicates 8640 kbit/s)

SET 3GSM: MBRDNLK=254, GBRDNLK=254, PARATYPE=QOS;

3.2 Parameter Configuration on the RNC Side

1. Add an HSUPA cell and set the number of E-AGCH codes and the number of E-RGCH/E-HICH codes.



ADD CELLHSUPA:CELLID=XXX, EAGCHCODENUM=1, ERGCHEHICHCODENUM=1, MAXTARGETULLOADFACTOR=75, NONSERVTOTOTALEDCHPWRRATIO=0;

2. Activate HSUPA of a cell.

ACT CELLHSUPA:CELLID=XXX

3. 2ms TTI switch

To use the 2ms TTI, turn on the 2ms TTI switch.

SET CORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1;

4. 5.76Mbps license

On the RNC LMT, run the DSP LICENSE command to check whether the license supports the 5.76Mbps.

5. SRB over E-DCH switch

To perform the 2ms service (5.76 Mbit/s) based on 2*SF2+2*SF4 codes, set up the SRB on HSPA.

SET FRCCHLTYPEPARA: SrbChlType=HSPA, SrbChlTypeRrcEffectFlag=FALSE;

Notes：the parameter of SrbChlTypeRrcEffectFlag means whether SRB over HSPA effect on RRC or not.The uplink throughput has no difference whether the flag is true or not from the Lab test result.Due to some UE does not supported on SRB over HSPA on RRC,we do recommend to set the flag false generally.

3.3 Parameter Configuration on the NodeB Side

As most parameters on the NodeB side are associated with scheduling and power control algorithms, you are not advised to modify them.

1. License required for the 2ms TTI

On the NodeB LMT, run the DSP LICENSE command to check whether the license supports the 2ms TTI.

DSP LICENSE;

2. Uplink CE capability required for the 5.76 Mbit/s rate

On the NodeB LMT, run the DSP LICENSE command to check the number of uplink CE licenses.

DSP LICENSE;



3.Two antenna receiving required

On the NodeB LMT, run the ADD SEC command to set 2 antennas receiving model.

ADD SEC: STN=xxx, SECN=xxx, SECT=REMOTE_SECTOR, ANTM=2, DIVM=NO_TX_DIVERSITY, ANT1SRN=xxx, ANT1N=R0A, ANT2SRN=xxx, ANT2N=R0B;



Chapter 4 FAQs

The Guide to HSPA Problem Location covers all contents involved in the original

chapter and the guide to HSPA data transmission problem location is added. You can log

in to the support website for downloading.



Chapter 5 Appendix

5.1 MML Commands Related to the RNC

Table 6 MML command reference related to the RNC

MML Command Description Function

ADD NODEB Add a NodeB. Set the protocol version of the NodeB.

ADD CELLHSUPA Add HSUPA parameters for a cell.

Configure basic resources of HSUPA.

ACT CELLHSUPA Activate high speed uplink packet access (HSUPA) of a cell.

Activate HSUPA of a cell.

DEA CELLHSUPA Deactivate high speed uplink packet access (HSUPA) of a cell.

Deactivate HSUPA of a cell.

ADD CELLCAC Add admission control algorithm parameters for a cell.

Set the maximum number of users on the HSUPA channel.

SET CORRMALGOSWITCH

Set the connection-oriented algorithm switches in the RNC.

Set the HSUPA algorithm switch.

SET FRC Set the RNC-oriented FRC algorithm parameters.

Set the HSUPA FRC algorithm parameters.

SET FRCCHLTYPEPARA

Set RAB and SRB related parameters.

Set RAB and SRB related parameters.

SET SCHEDULEPRIOMAP

Set the scheduling priority mapping information.

Set the scheduling priority of a service.

ADD TYPRABBASIC/ MOD TYPRAB

Add or modify basic information of a typical RAB.

Add or modify a typical service index.

ADD TYPRABRLC/MOD TYPRABRLC

Add or modify RLC parameters of a typical RAB.

Add or modify RLC parameters of a typical RAB.

ADD TYPRABOLPC/MOD TYPRABOLPC

Add or modify OLPC parameters of a typical RAB.

Add or modify OLPC parameters of a typical RAB.

LST TYPRAB List the information of a typical RAB.

List the information of a typical RAB.

SET EDCHRATEADJUSTSET

Set a rate adjustment set of HSUPA.

Set a rate adjustment set of HSUPA.




ADD TYPRABHSPA /MOD TYPRABHSPA

Add or modify HSPA information of a typical RAB.

Add or modify HSPA information of a typical RAB.

ADD AAL2PATH Add an AAL2 path between the RNC and its adjacent node.

In ATM transmission mode, an AAL2 path is required to carry user-plane channels. For HSPA services, an HSPA path should be set.

ADD IPPATH Add an IP path. Add an HSPA IP path.

ADD IPOAPVC

Add an IPoA PVC between the local IPoA client and the peer IPoA client.

In IP transmission mode, an IPoA PVC should be set.

ADD ATMTRF Add an ATM traffic record.

ATM traffic records are public resources and can be used by the IPoA PVC, AAL2 path, and SAAL link.

5.2 MML Commands Related to the NodeB

Table 7 MML command reference related to the NodeB


ADD AAL2PATH Add an AAL2 path on the Iub interface.

Set an AAL2 path related to HSUPA services.

ADD IPPATH Add an IP path on the Iub interface.

Set an IP path related to HSUPA services.

SET MACEPARA Set MAC-e parameters.

Set HSUPA-related algorithms and functions.

SET BRDHSUPA

For a distributed NodeB, you must turn on the HSUPA switch on the HBBU or HBBUC before using the HSUPA feature.

Set whether the HBBU or HBBUC in a distributed NodeB supports the HSUPA feature.

hsupa deployment guidelines

Documents

deployment of ran11

deployment reference

huawei confidential

mace scheduling abstract

date huawei technologies

radio communication

grant srnc

ps data transmission