ZWF26-02-004 Dc-Hsdpa

Feature Deployment and Testing Guide
DC-HSDPA
Feature ID: ZWF26-02-004
Version: V3.11.10
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2012-08-09 First edition
Serial Number: SJ-20120802112720-242
Publishing Date: 2012-08-09 (R1.0)
SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Contents
Chapter 1 Functional Description ............................................................. 1-1
Chapter 2 Deployment in Commercial Network and User Benefit......... 2-1
Chapter 3 Preparations .............................................................................. 3-1
Chapter 4 Data Configuration.................................................................... 4-1
Chapter 5 Testing ....................................................................................... 5-1
5.1 Test Purpose...................................................................................................... 5-1
5.2 Steps for Test..................................................................................................... 5-1
5.3 Expected Results ............................................................................................... 5-5
Chapter 6 Counter List............................................................................... 6-1

II

Chapter 1
Functional Description
DC-HSDPA Technique Principle
When users are on the edge of a cell or moving across cells, or on the poor radio
environment, MIMO and 64QAM can not get considerable gain and user experience can
not be improved effectively. DC-HSDPA introduced in 3GPP R8 can deal with this case.
DC-HSDPA uses two adjacent carriers to provide HSDPA for a user at the same time,
increases frequency resource, and then improves user throughput. For UE supported
DC-HSDPA, There are two HSDPA serving cell in downlink: the Primary serving cell and
the Secondary serving cell, but in uplink, there is still one cell. For DC-HSDPA UE, uplink
channels served for HSDPA exist in Primary serving cell, but do not exist in the Secondary
serving cell. The Primary serving cell has the same capability with single carrier HSDPA
serving cell. In the secondary serving cell, for DC-HSDPA activated UE, only downlink
channels served for HSDPA transmission exist, i.e, CPICH, HS-PDSCH and HS-SCCH.
For a secondary serving HS-DSCH cell, the timing reference is the same as the timing
reference for the serving HS-DSCH cell.
DC-HSDPA can be combined with CPC. If the secondary serving cell is activated, the
HS-SCCH orders used for activate/de-activate downlink DRX can be transmitted in either
primary serving cell or the secondary serving cell. The DRX state of primary serving cell
is same to that of the secondary serving cell.HS-SCCH-less operation is supported on
primary serving cell only, but the HS-SCCH orders for activate/de-activate HS-SCCH less
can be transmitted on both primary serving cell and the secondary serving cell.
1-1

Feature Deployment and Testing Guide Feature ID: ZWF26-02-004
Figure 1-1 MAC-ehs Entity Architecture in UTRAN
In UTRAN, when data of a user is transmitted on two carriers simultaneously, MAC-ehs

will divide data into different carriers (shown as in figure 1-1). Each carrier implements
coding, mapping, modulation and transmitting independently. In UE side, each carrier
decodes independently and combines data by MAC-ehs. Accordingly, two carriers joint
scheduling is used. For DC-HSDPA activated users, two carriers resource have to be
taken into account jointly when MAC-ehs is used for resource scheduling. As a result,
two carriers for DC-HSDPA must be located in the same NodeB. Since data allocation
operation is implemented in MAC-ehs, therefore the deployment of downlink Enhanced
Layer 2 function is the base of DC-HSDPA.
DC-HSDPA is suitable for operators occupied enough frequency resource to deploy
network. Compared to two single carriers, DC-HSDPA can improve user average
throughput and sector average throughput, and more gain can be achieved in case of
1-2

Chapter 1 Functional Description
less users, as users increase, the gain decreases. The gain is from joint scheduling of
dual carriers.
After DC-HSDPA is introduced, mobility management also need to change. These two key
technologies are performed in RNC and NodeB.
DC-HSDPA Peak Rate

The HS-PDSCH is a physical downlink channel. It is introduced to carry the actual
subscriber data transmission. The spreading factor of HS-PDSCH is fixed to 16, the
modulation mode can be QPSK, 16QAM or 64QAM, and 1/3 Turbo codes are used for
channel coding. Figure 1-2 shows the channel structure.
1-3

Figure 1-2 HS-PDSCH Structure
M refers to the bit number represented by each modulation symbol. For QPSK, M is equal
to 2 and the bit number of the physical channel in the 2-ms TTI is 960, that is, the bit rate
is 480 Kbps. For 16QAM, M is equal to 4 and the bit number of the physical channel in the
2-ms TTI is 1,920, that is, the bit rate is 960 Kbps. For 64QAM, M is equal to 6 and the bit
number of the physical channel in the 2-ms TTI is 2880, that is, the bit rate is 1440 Kbps.
If 30 (15 code channels for each cell) code channels transmit data concurrently and the
modulation mode is 64QAM, the peak rate of the physical layer is 43.2 Mbps.
According to 3GPP protocol 25.306, the maximum number of bits of an HS-DSCH transport
block received within an HS-DSCH TTI is 42192, so the MAC layer maximum speed is:
1-4

Chapter 1 Functional Description
42192/TTI*2 = 42192/2ms*2 = 42.192mbps

Multiply by two because UE downloading from two cell at the same time.
1-5

This page intentionally left blank.
1-6

Chapter 2
Deployment in Commercial
Network and User Benefit
DC HSDPA feature uses two adjacent carriers to increase peak bit rate of HSDPA service
and meet the needs of high speed user. DC-HSDPA does not only improve bit rate of users
in cells central (Maximum up to 2 times), but also improve bit rate of user on the edge
of cells (approximately 2 times), hence users can get higher network speed experience
continuously. Combined with 64QAM, single user of DC-HSDPA peak bit rate can be up
to 43.2Mbps.
Two RNC configured parameters are used to control the access system supporting
capability of DC-HSDPA: The first is DcHsdschSptInd, and it indicates whether the RNC
supports DC-HSDPA. The second is a cell level parameter named DcHsdschSupptInd,
it indicates whether the cell supports DC-HSDPA. RNC makes decision of whether to
activate DC-HSDPA for a user according to UE capability, NodeB capability and RNC
configuration (both RNC and cell DC-HSDPA capability). Only if all these three conditions
are fulfilled, RNC configures secondary carrier information for the UE.
In primary serving carrier selection strategy, HSPA preferred carrier can be chosen as
primary carrier, if HSPA preferred carrier is in high-load, network will balance DC-HSDPA
UE to another carrier(e.g. R99, HSPA and HSPA+ sharing carrier), and take it as primary
carrier.
Mobility management need to be considered due to the introduction of DC-HSDPA.
According to 3GPP protocol, DC-HSDPA only supports mobility based on primary serving
cell, then the mobility management basic policy of DC-HSDPA UE is same to which of
single carrier user in its serving cell, but the secondary serving cell activation/de-activation
should be extra considered according to different scenario.
1. Handover of inter-cell supporting DC-HSDPA. It is handover from DC-HSDPA cell to
DC-HSDPA cell, both the primary and the secondary serving cells keep activation
before and after handover.
2. Handover from DC-HSDPA enabled cell to DC-HSDPA disabled cell. In this scenario
both the primary and the secondary serving cells are activated before handover,
when handover is executed, the secondary serving cell is no longer configured.
After handover, the secondary serving cell is deactivated. In the opposite direction
handover, the primary and secondary serving cell are activated simultaneously for
DC-HSDPA users.
3. Handover from DC-HSDPA enabled to single carrier cell. It is similar to scenario
2, when handover is executed, the secondary serving cell is not configured no
longer. After handover, only single carrier is used. The opposite direction handover,
2-1

is also similar to scenario 2, he primary and secondary serving cell are activated
simultaneously for DC-HSDPA users.
In inter-RNC handover, source RNC gets the DC-HSDPA capability of neighboring cell
in neighboring RNC through parameter IurDcHsdsSuptInd, and then make decision that
whether to configure secondary serving cell for HSDPA service. If secondary serving cell
configuration is needed, the configured secondary cell ID is parameter SndSvrCelID.
In inter-RNC handover, if DC-HSDPA function is supported, there is a limitation in 3GPP
protocol that SRNC could not get Scrambling Code and frequency information of the
Secondary serving cell in DRNC directly, which is expressed as follows:
In Radio Link Setup procedure between cell 1 and cell3 over Iur shown as Figure 1-3
(assuming that cell 2 and cell 4 can be the candidate HSDSCH secondary serving cell for
cell1 and cell 3 respectively and vice versa), according to 3GPP TS25.423, the DRNC
could not take the Scrambling Code and frequency information of cell 4 to SRNC through
Radio Link Setup Response message(Assuming the left side is SRNC), then in the
following operation, because of short of the Scrambling Code and frequency information
of cell 4, the SNC could not configure the cell4 as the secondary serving cell of cell 3
when changing the HSDSCH serving cell from SRNC to DRNC without relocation.
Figure 2-1 A Example of Neighboring Cell Configuration Inter-RNC
To deal with this case, two proposals are introduced. The first proposal is that the Primary
serving cell and the Secondary serving cell should be configured as neighboring cell
relationship for CELL_DCH state as shown in figure 1-3, cell 1 and cell 2 (i.e. the primary
serving cell and its candidate secondary serving cell ) should be configured as neighboring
cells in CELL_DCH state(So do the cell 3 and cell 4), as a result, the Scrambling
Code and frequency information of cell 4 can be taken to SRNC in Neighboring UMTS
Cell Information Information Element of RNSAP messages such as Radio Link Setup
Response/Radio Link Add Response etc, and SRNC can get all necessary information of
the candidate HSDSCH secondary serving cell (i.e. cell 4) in DRNC, and then SRNC can
2-2

Chapter 2 Deployment in Commercial Network and User Benefit
configure cell 4 as the secondary serving cell of cell3 in the HSDSCH serving cell change
procedure.
Figure 2-2 A Proposal of DC HSDPA Cell Configuration in Inter-RNC Case
The second proposal is to configure all candidate Secondary HS-DSCH serving cells in
DRNC as neighboring cells of SRNC in External UTRAN Cell. If DRNC does not take the
secondary HS-DSCH serving cell Scrambling Code and frequency information to SRNC
through RNSAP messages such as Radio Link Setup Response/Radio Link Add Response
etc, then SRNC can search configured External UTRAN Cell to achieve the Scrambling
Code and frequency information of the Secondary HS-DSCH serving cell in DRNC by its
RNC ID and Cell ID.
2-3

2-4

Chapter 3
Preparations
License
Feature License
ZWF26-02-004 DC-HSDPA WCDMA DC-HSDPA Cell Number
ZWF26-02-004 DC-HSDPA WCDMA maximum HSDPA 64QAM cell
Hardware Requirement
NE Requirement
RNC None
NodeB None
3-1

Software Requirement
NE Involved Version Requirement
UE YES UMTS FDD Number: 1

Release: R8, DPA
category: 24, UPA
category 5 or above
Node B YES V4.11.10.14 ZTE equipment
RNC YES V3.11.10.11 ZTE equipment
MSCS YES ZTE equipment
MGW YES ZTE equipment
SGSN YES ZTE equipment
GGSN NO
HLR NO
Topology
Topology is shown in Figure 3-1.
Figure 3-1 Topology
3-2

Chapter 4
Data Configuration
SGSN/GGSN - ZTE
N/A
MSC/MGW - ZTE
N/A
HLR - ZTE
UE1 subscribe interactive, downlink MBR 43mbps, uplink MBR more than 2mbps.
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_interactiv
e
SetupOrModifyItemFirst.rAB_Parameters.iE_Extensions.rAB_Parameter_ExtendedMax
BitrateList.n = 2
BitrateList.elem[0] = 43000000
BitrateList.elem[1] = 16000001
RNC
In RNC side, the test cell is 102 and 104. They are in the same RRU of NodeB 19. Both
cells (cell102 and cell104) configured with the same parameters. The following steps take
one cell (cell 102) configuration as example.
There are some special parameters setting in peak rate test, this setup cant be used in
live network.
1. The utilization rate of transmission is about 85% or less, to achieve the peak rate,
Iub and Iu-PS bandwidth should configure 60mbps or more, the recommend value is
100mbps. Please make sure the Iub bandwidth and bandwidth between RNC and
PDN server is enough before testing. In this test Iub and Iu-PS bandwidth is set to
100mbps.
a. Configure Iub bandwidth.
- Tx bandwidth (Unit: bps): 100,000,000
4-1

- Rx bandwidth (Unit: bps): 100,000,000
Path: View > Configuration Management > RNC Managed Element > Ground
Resource Management Information > Transport Configuration > 3G Office
Configuration > IUB Configuration > IUB Configuration xxx > TrPath > TrPath
ID xxx
b. Configure Iu-Ps bandwidth.
- Tx bandwidth (Unit: bps): 100,000,000

- Rx bandwidth (Unit: bps): 100,000,000
4-2

Chapter 4 Data Configuration
Path: View > Configuration Management > RNC Managed Element > Ground
Resource Management Information > Transport Configuration > 3G Office
Configuration > SGSN > TrPath > TrPath ID xxx
2. Parameters Setting in HSPA Configuration
-Dual-Cell HS-DSCH Support Indication: Support
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > HSPA Configuration > Dual-Cell HS-DSCH Support
Indication
3. Parameters Setting in RNC Configuration

-Type of Transport Channel for Initial RRC Connection Setup: Forced to
CELL_FACH
To make sure there is one SF = 256 code tree left for DPDCH, this code tree used to
bearer UE downlink signaling.
4-3

Resource Management > RNC Configuration > Type of Transport Channel for
Initial RRC Connection Setup
4. Parameters Setting in Cell Setup Parameters

-T_cell: 0
T_cell represents the Timing delay used for defining the start of SCH, CPICH and the
DL Scrambling Code(s) in a cell relative BFN. This parameter is not required to 0, while
the primary cell and secondary cell must configure the same value.
-Cell Downlink Enhanced Layer 2 Support Indicator: Support
-Cell 64QAM Support Indicator: Support
-Dual-Cell HS-DSCH Support Indication: Support
-P-CPICH Power (dBm): 30
4-4

Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Setup Parameters
5. Parameters setting in Cell Ability and Cell Reselection
-Number of HS-PDSCH: 15
- Maximum Number of HS-PDSCH: 15
- Minimum Number of HS-PDSCH: 15
4-5

To make sure UE can use the maximum number of HS-PDSCH. Number of

HS-PDSCH, Maximum Number of HS-PDSCH and Minimum Number of HS-PDSCH
all set to15.
Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and Cell
Reselection
6. Parameters setting in HSPA Configuration Information In A Cell
-Number of HS-SCCH: 1
- DPCH Code Hysteresis: 0
- Code Update Hysteresis A: 0
To make sure there is one SF = 256 code tree left for DPDCH, Number of HS-SCCH
set to 1, DPCH Code Hysteresis and Code Update Hysteresis A set to 0.
4-6

Resource Management > UTRAN Cell > UTRAN Cell xxx > Modify Advanced
Parameters > HSPA Configuration Information In A Cell
7. Parameters setting in HS-PDSCH Measurement Power Offset
- HS-PDSCH Measurement Power Offset (dB): 8
Increase the Measurement Power Offset have benefit to UE downlink decoding, the
recommend value for DC-HSDPA peak rate testing is 8. The measurement power
offset is configured according the UEs actual use of 64QAM, MIMO and DC-HSDPA
in the cell. The value of measurement power offset is indexed by parameter Actual
Configuration of HSDPA Evolution Function of UE in the Cell. When UE use 64QAM
and DC-HSDPA at the same time, the index is 5.
4-7

Resource Management > UTRAN Cell > UTRAN Cell xxx > Modify Advanced
Parameters > HS-PDSCH Measurement Power Offset > HS-PDSCH Measurement
Power Offset (dB) (Actual Configuration of HSDPA Evolution Function of UE in
the Cell index 5)
8. Parameters setting in Neighbouring Cell
- Add cell104 as cell102s neighbor cell.
- Add cell102 as cell104s neighbor cell.
4-8

Resource Management > UTRAN Cell > Neighbouring Cell > Create
Node B
The test take cell102 and cell104 as example.
1. parameters setting in NodeB ULocalCellRelation
ref1ULocalCell_localCellId is primary cell.
ref2ULocalCell_localCellId is secondary cell.
- Add cell102 as primary cell, cell104 as secondary cell
- Add cell104 as primary cell, cell102 as secondary cell
2. parameters setting in NodeB PhyLayerPort

- operatingMode: 0
- egressPeakBitRate: 100000
egressPeakBitRate used to control uplink throughput. According to the experience
of statistics, upper application layer carried by TCP needs backward bandwidth with
1/40~1/30 of its forward bandwidth to carry acknowledge information. To guarantee
downlink data bit rate, enough uplink channel bandwidth should be provided. For
example, uplink channel with approximate 1.4mbps bandwidth is needed to sustain up
to 43.2Mbps downlink peak bit rate when DC-HSDPA used. Given to the symmetric
of uplink and downlink, this speed also set to 100mbps.
4-9

4-10

Chapter 5
Testing
Table of Contents
Test Purpose ..............................................................................................................5-1
Steps for Test .............................................................................................................5-1
Expected Results .......................................................................................................5-5
5.1 Test Purpose

The purpose of this test case is to verify the peak bit rate of DC-HSDPA
Related document:
ZTE UMTS HSPA Evolution Feature Guide.doc
5.2 Steps for Test

Before testing, please make sure both two test cells can support 64QAM, and the average
ftp downlink throughput is more than 19mbps. For more detail please refer to document
ZWF26-01-001 64QAM for HSDPA_Feature Deployment & Testing Guide.docx
1. Check the signal quality from QXDM

Path: View->New->WCDMA->WCDMA Pilot Scanner
When the UE is in idle mode, the RSCP of the two cells should be about -60dBm or
above. Ec/No (Energy in the picture bellow) should be -1~-2dB, otherwise the signal
is not good enough.
5-1

5-2

Chapter 5 Testing
2. UE activates a PS call in Cell1/Cell2.

From rrcConnectionSetupComplete message, UE HS-DSCH physical layer category
is 24, EDCH physical layer category is 6.
Note:
The HS-DSCH physical layer category is extended 2 times.
5-3

From RAB_AssignmentRequestMsg message, UE traffic class is interactive,

maxBitrate is 43mbps/16mbps.
Note:
The maximum bitrate is in rAB_Parameter_ExtendedMaxBitrateList sub message.
From radioBearerSetup message, secondary cell info is added in

dl_SecondaryCellInfoFDD sub message, and from dl_64QAM_Configured
= eRRC_newConfiguration_dl_64QAM_true sub message, 64QAM is used in
downlink.
5-4

Chapter 5 Testing
3. UE starts multi-thread FTP downloading. The file on the server is no less than
1GByte.Maintain the downloading for 3mins. Use DU meter software record the
average speed.
4. Release the PS service.
5.3 Expected Results

In step2, the DC-HSDSCH service is established successfully.
In step3, the 3mins average speed is more than 38mbps.
5-5

5-6

Chapter 6
Counter List
Counter No. Description
C310080218 Number of successful RRC connection access by

UE HSDPA categories 23 24
C310170842 Number of successful HSDPA RAB assignment

setup for PS domain, Streaming Class, UE hsdpa
category 23-24

setup for PS domain, Interactive Class, UE hsdpa
category 23-24

setup for PS domain, Background Class, UE
hsdpa category 23-24
C310090280 Number of attempted RAB assignment setup in

cell for PS domain, Streaming.

cell for PS domain, Interactive

cell for PS domain, Background

setup for PS domain, Streaming Class

setup for PS domain, Interactive Class

setup for PS domain, Background Class
C310100739 Number of successful RAB assignment setup in

cell for PS domain, Streaming

cell for PS domain, Interactive

cell for PS domain, Background
6-1

ZWF26-02-004 Dc-Hsdpa

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ZWF26-02-004 Dc-Hsdpa

Caricato da

Copyright:

Formati disponibili

Feature Deployment and Testing Guide

Revision No. Revision Date Revision Reason

R1.0 2012-08-09 First edition

Serial Number: SJ-20120802112720-242

Publishing Date: 2012-08-09 (R1.0)

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Chapter 6 Counter List............................................................................... 6-1

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Figure 1-1 MAC-ehs Entity Architecture in UTRAN

In UTRAN, when data of a user is transmitted on two carriers simultaneously, MAC-ehs

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

DC-HSDPA Peak Rate

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Figure 1-2 HS-PDSCH Structure

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

42192/TTI*2 = 42192/2ms*2 = 42.192mbps

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Figure 2-1 A Example of Neighboring Cell Configuration Inter-RNC

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Figure 2-2 A Proposal of DC HSDPA Cell Configuration in Inter-RNC Case

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120802112720-242|2012-08-09 (R1.0) ZTE Proprietary and Confidential