DC-HSDPA Feature Acceptance Guide

Product Name Confidentiality

Wireless Product Service Department

Product Version Total 35 pages

RAN12.0 DC-HSDPA Feature Acceptance Guide

Huawei Technologies Co., Ltd.

All rights reserved

DC-HSDPA Feature Acceptance Guide Confidentiality: INTERNAL

2014-07-21 Huawei Technologies Proprietary Page I

Contents

1 Overview ......................................................................................................................................... 1

2 General Procedure for the DC-HSDPA Deployment ............................................................ 3

2.1 General Procedure for Deploying the DC-HSDPA Feature .............................................. 3

2.2 Procedure for the DC-HSDPA Feature Acceptance Test .................................................... 4

3 Preparations for the DC-HSDPA Deployment ....................................................................... 6

3.1 License .......................................................................................................................................... 6

3.2 Preparations for the Environment .......................................................................................... 7

3.2.1 RNC ........................................................................................................................................................ 7

3.2.2 NodeB ..................................................................................................................................................... 7

3.2.3 UE ........................................................................................................................................................... 8

3.2.4 HLR ........................................................................................................................................................ 8

3.3 Networking Mode ...................................................................................................................... 9

3.4 Software Version ........................................................................................................................ 9

3.5 Planning for the Transmission Network ............................................................................... 9

4 Data Configuration ..................................................................................................................... 10

4.1 Optimization for the DC Throughput Rate ........................................................................ 10

4.1.1 RNC ...................................................................................................................................................... 10

4.1.2 NodeB ................................................................................................................................................... 12

4.2 Examples of DC Field Verification ....................................................................................... 13

4.2.1 Field Verification Results ...................................................................................................................... 13

4.2.2 Commissioning Process ........................................................................................................................ 13

5 Acceptance Standards ................................................................................................................. 17

5.1 Downlink Peak Rate ................................................................................................................ 17

5.2 Handover ................................................................................................................................... 17

6 Test Tools ...................................................................................................................................... 18

6.1 Packet Sending ......................................................................................................................... 18

6.1.1 Packet Sending on the RNC .................................................................................................................. 18

6.1.2 Packet Sending Using Iperf ................................................................................................................... 19


2014-07-21 Huawei Technologies Proprietary Page II

6.2 Common Trace .......................................................................................................................... 20

6.2.1 Single-User Trace on the RNC .............................................................................................................. 20

6.2.2 Single-User Trace on the NodeB ........................................................................................................... 21

6.3 QXDM ........................................................................................................................................ 24

7 Guide to Test Cases ....................................................................................................................... 25

7.1 Operation Guide to the Test Case: DC Throughput Performance ................................. 26

7.1.1 Scripts for the Test Case: Single User Throughput of DC in Good Radio Condition ........................... 26

7.1.2 Preparations for the Test ........................................................................................................................ 28

7.1.3 Test Execution ....................................................................................................................................... 28

8 Points for Attention in the Data Configuration .................................................................... 31

8.1 Configuration at the RNC ...................................................................................................... 31

8.2 Configuration at the NodeB ................................................................................................... 31

9 FAQs .............................................................................................................................................. 32

9.1 Optimization of the Presentation and Competition Test ................................................. 32

9.2 Decrease of the Throughput Rate When the Tcells of the Two Cells Configured on a Single RRU ...................................................................................................................................... 33

9.3 Service Release due to UE Failure When the UE Sends the RLC ACK But the RNC Receives the TRB ACK.................................................................................................................. 33

9.4 Dumeter Display ...................................................................................................................... 34

9.5 High Block Error Rate for the 41440 Data Block ................................................................ 34

9.6 Rate for Packet Sending Lower Than 28 Mbit/s at the RNC ........................................... 34

9.7 Using a Terminal Supporting 64QAM During the Test ................................................... 34


2014-07-21 Huawei Technologies Proprietary Page III

Figures

Figure 2-1 General procedure for the DC-HSDPA deployment ............................................................................ 4

Figure 3-1 RNC license ......................................................................................................................................... 7

Figure 3-2 NodeB license ...................................................................................................................................... 7


2014-07-21 Huawei Technologies Proprietary Page IV

Tables

Table 2-1 Procedure for the DC-HSDPA feature test ......................................................................................... 5

Table 3-1 Control items of DC license .................................................................................................................. 6

Table 3-2 Categories of HSPA+ terminals (the categories in red support HSPA+ Phase2) ................................... 8


2014-07-21 Huawei Technologies Proprietary Page 1

1 Overview The WCDMA protocol of the R8 version introduces features such as DC and 64QAM+MIMO.

The R8 version enhances the HSPA+ Phase1 of the R7 version. The HSPA+ Phase2

technology can increase the data rate in the radio downlink, improve the single-user

throughput rate, and increase the cell capacity. In this sense, the advantage of HSPA+ is to

improve the service experience of end users.

HSPA+ Phase2 is the most important feature provided by Huawei RAN12.0, and one of its

most important contents is as follows:

DC-HSDPA: provides the peak download rate of 42 Mbit/s in the downlink direction. The

basic idea for Dual Cell-HSDPA (DC-HSDPA) is to improve the throughput rate for users by

increasing the spectrum bandwidth. The DC-HSDPA technology allows a UE to receive the

HSDPA data sent by two downlink cells with different frequencies but with the same coverage.

The network side can dynamically choose to dispatch the HSDPA transmission for users

between two carriers. In the optimal case, a cell with two carriers adopts the HSDPA

transmission for users so that the peak rate on the MAC layer for users can reach 42 Mbit/s.

The following sections describe the advantages of HSPA+ from the perspectives of mobile

operators and end users:

Improving the service performance for end users

For common users, HSPA+ means high data transmission rate, short service response

time, and reliable service performance. All these advantages improve the perception of

end users and enhance the user experience.

Implementing HSPA+ by upgrading the existing WCDMA network

Mobile operators care for the expenditure for constructing the HSPA+ network. The

expenditure depends on the price of the devices provided by device suppliers and the

business policy of a single operator. As an enhanced technology for the high-speed data

service of WCDMA R7, HSPA+ ensures the forward compatibility of the system. That is,

HSPA+ is fully compatible with the previous HSDPA and WCDMA R99. To introduce

HSPA+ in the existing WCDMA R99 and HSDPA networks, the operator can upgrade

the existing WCDMA BTS to a certain degree without greatly affecting the structure of

the existing system. In this way, the time for network construction is reduced and the

previous investment of the operator is protected.

As indicated by 3GPP R8 specifications, the two cells that form a DC group must meet the

following conditions:

Two cells must be under the same NodeB and have two adjacent carrier frequencies.

The two cells must use the same antenna.



The two cells must be synchronous, indicated by the same TCell.

This document describes the deployment and acceptance processes and methods for the DC-HSDPA

feature.



2 General Procedure for the DC-HSDPA Deployment

2.1 General Procedure for Deploying the DC-HSDPA Feature

The following flowchart describes the general procedure for deploying the DC-HSDPA feature:



Figure 2-1 General procedure for the DC-HSDPA deployment

End

Whether the

verification is

passed

Start

Upgrade the

software

Send the

configuration data

Verify the network

planning and drive

test performance

Observe the KPIs

for the new

feature to be

enabled

Whether

preparations for

upgrade are

complete

YES

NO

Upgrade the

software according

to the upgrade

guide

YES

Problem

solving

process

NO

Apply for the

license

Prepare the

hardware

Plan the

transmission

network

Plan the

configuration

Prepare the

hardware goods

Apply for the transmission

bandwidth

Design and plan the

transmission bandwidth

Adjust the network structure

Prepare the configuration

scripts

Install the hardware

Send the

configuration scripts

General procedure for the DC-HSDPA deployment

Preparations for upgrade Upgrade and feature enabling

Feature verification

2.2 Procedure for the DC-HSDPA Feature Acceptance Test

The following flowchart shows the general procedure for testing the DC-HSDPA feature

during acceptance:



Table 2-1 Procedure for the DC-HSDPA feature test

The acceptance test can be performed immediately after a feature is deployed. Before the

operation, perform the following steps to obtain the test cases: Visit the website at

http://support.huawei.com/support/.

Step 2 Choose Documentation > Select by Product > Wireless.

Step 3 On the displayed window, click WCDMA-RAN, WCDMA-RAN Public, then Technical Guides.

Step 4 Click Acceptance Manual and select the Acceptance Test Case Description for the corresponding version.

After obtaining the test cases, you may need to omit some tests based on the site requirements

and customer requirements. Build the test environment by referring to the upgrade guide.

Then, perform the acceptance test following the procedures listed in the test cases. Save the

result of each operation. After the test case is completed, restore the environment before the

test to prepare for the next test case.



3 Preparations for the DC-HSDPA Deployment

3.1 License

To implement the HSPA+ Phase2 DC feature, support from license is required. Table 3-1

describes the licenses on the RAN side.

Table 3-1 Control items of DC license

Feature ID Feature Name Description Name of License Item

WRFD-010689 HSPA+ Downlink

42 Mbit/s per

User

Control on the RNC side LQW1EHSPA03

WRFD-010696 the number of

cells with DL DC

function enabled

Control on the NodeB side.

This license item is activated

according to the number of

cells. The number of activated

cells must be the same as the

actually configured one.

LQW9DDC01

RNC License: LST LICENSE, enabled in case of 42 Mbit/s per user.



Figure 3-1 RNC license

NodeB License: DSP LICENSE, unlimited.

Figure 3-2 NodeB license

3.2 Preparations for the Environment

To implement the HSPA+ Phase2 DC feature, the UE, Node B, RNC, and CN must be jointly

used.

3.2.1 RNC

In addition to the general boards, the RNC needs to use the following boards (the board in

bold is mandatory):

PARC platform: DPUe (supports 42 Mbit/s per user), SPUb, GOUc, and FG2c.

3.2.2 NodeB

To support DC-HSDPA, the BTS3900/BTS3900A/DBS3900 must be configured with one

baseband board (such as WBBPb3, WBBPb4, WBBPd1, or WBBPd2) that supports six cells,

or configured with two baseband boards (such as WBBPb1 or WBBPb2), each of which

supports three cells.

To support DC-HSDPA, the DBS3800 must be configured with EBBC or EBBCd.

To support DC-HSDPA, the BTS3812E/BTS3812AE must be configured with EBBI or EDLP.

When EDLP is configured, EULP or EULPd must be configured together.

After a cell is set up, you need to run the DSP LOCELLRES command to check whether the downlink resource group of the cell is created on the enhanced board.



1. The V13 series BTSs (BTS3812/3806/3806A) cannot be evolved to R12, that is, do not support the

new features of R12.

3.2.3 UE

The R8 protocol adds for categories of terminals that support the HSPA+ Phase2 DC feature,

that is, categories 2124, as shown in the red parts in the following table.

Table 3-2 Categories of HSPA+ terminals (the categories in red support HSPA+ Phase2)

HS- DSCH Category

Maximum Number of HS-DSCH Codes Received

Minimum Inter-TTI Interval

Maximum Number of Bits of an HS-DSCH Transport Block Received within

an HS-DSCH TTI NOTE 1

Total Number of Soft Channel Bits

Supported Modulations without MIMO Operation or Dual Cell Operation

Supported Modulations Simultaneous with MIMO Operation and without Dual Cell Operation

Supported Modulations with Dual Cell Operation

Category 21 15 1 23370 345600 N/A N/A QPSK,

16QAM

Category 22 15 1 27952 345600

Category 23 15 1 35280 518400 QPSK,

16QAM,

64QAM Category 24 15 1 42192 518400

3.2.4 HLR

The HLR must be upgraded to meet the requirement for subscriber definition rate for

expanding HSPA+ Phase2 subscribers.



3.3 Networking Mode

3.4 Software Version

RNC: V900R012C01SPC200 or later releases

NodeB: V200R012C00SPC200 or later releases

SGSN: SGSN9810V800R009ENGC01B033 or later releases

GGSN: GGSN9811V800R005ENGC01 or later releases

HLR: HLR9820V600R003ENGC03B012 or later releases

3.5 Planning for the Transmission Network

After the DC feature is introduced, the maximum downlink peak throughput rate per user can

reach 42 Mbit/s. Therefore, the minimum bandwidth of the Iub transmission network must be

50 Mbit/s (because the Iub transmission efficiency decreases by 85% on average). In addition,

as the R99 service exists on the actual commercial network, the required Iub bandwidth is

higher than 50 Mbit/s. The bandwidth required for the actual commercial network needs to be

calculated according to the network planning and optimization. In addition, enable 100 Mbit/s

full-duplex transmissions on the ports related to the following items:

Iu interface

Iub interface

Any transmission devices



4 Data Configuration This chapter describes the data configuration of the DC-HSDPA feature, including the data

configurations on the RNC side, NodeB side, and part of the core network side. Huawei core

network equipment is used as an example in the configuration of the core network side.

For details about the configuration, see the section "HSPA+ Deployment Guide" in the RAN12 Feature Deployment Guide-20110423-A-V1.3, which can be obtained from

http://support.huawei.com/support/.

To obtain the previous document, perform the following steps:

Visit the website at http://support.huawei.com/support/.

Choose Documentation > Select by Product > Wireless.

On the displayed window, click SingleRAN, MBSC, then Technical Guides.

Click Deployment Guide and download the deployment guide for the corresponding

version.You can also obtain this document at:

http://support.huawei.com/support/DocView.do?doc_id=SE0000479356&doc_type=123-2

4.1 Optimization for the DC Throughput Rate

4.1.1 RNC

Cell Power Distribution ratio: 43/31

MOD UCELL: CellId=100, MaxTxPower=430, PCPICHPower=310;



MPO: 6.5 (MPO Constant: 5.5)

MOD UCELLHSDPA: CellId=100, HsPdschMPOConstEnum=5.5DB;

When testing the peak rate per user, you can slightly adjust the MPO constant (at a step of 0.5

dB) to improve the downlink rate to a certain degree. It is recommended that the MPO

constant range from 3 to 8. After the MPO constant is adjusted, you need to redial the number

on the terminal.

Maximum Number of PDSCH Codes (15)

When the NodeB enables dynamic codes, it is recommended that only one HS-SCCH channel

be configured on the RNC during the test for peak rate per user to reduce the used code words

number and improve the throughput rate. In a multi-user environment, it is recommended that

24 HS-SCCH channels be configured.

RNC: MOD UCELLHSDPA: CellId=100, HsScchCodeNum=1;

NodeB: SET MACHSPARA: DYNCODESW=OPEN;



4.1.2 NodeB

Power Margin=0%

SET MACHSPARA: PWRMGN=0;



4.2 Examples of DC Field Verification

4.2.1 Field Verification Results

Results of DC field verification: The average peak rate achieved by sending packets is 41.7

Mbit/s, which is nearly equal to the lab result.

The devices used for the test on site are as follows:

BSC6900V900R012C01 + DBS3900V200R12C00SPC100 WBBPd2 + LRRU 80 W,

terminal Qualcomm8220 (version 1013, Type 2 receiver).

Three sectors are configured, each of which uses two adjacent frequencies as the DC cell.

When a sector is tested, the other two sectors and the neighbor cells should be disabled

to prevent interference.

4.2.2 Commissioning Process

Field Verification Preparation

Ensure that the DC cell takes effect according to the configuration recommended in the lab.

For details, see section 4.1 "Optimization for the DC Throughput Rate."

The typical parameters are as follows:

RNC side: maximum transmit power of the cell: 430; pilot: 310 (the power of the pilot is

reduced according to the actual situations in the future); MPOC: 5.5

NodeB side: Power Margin: 0

UE side: check the typical NV item of DC through the QXDM software

00010 = 14 (WCDMA only)



00850 = 0x02 (service domain)

03524 = DL freq [if you would like to hard code it instead of Freq scan]

03525 = 1 [to force DL freq to the one you provided in 3524]

03649 = 4 (RRC version: 3:R7; 4:R8)

03851 = 3 (The detailed the values of NV3851 & 3852 can refer the below definition)

03852 = 0x33(0x33:Type0+2 SCHIC; 0x34:Type2 SCHIC; 0x35:Type0 SCHIC;)

04118 = 24 (HSPA category)

04210 = 6 (HSUPA category)

04257 = 4 (RF PMIC)

04526 = 1 (USB composition) (If "0" here, No QMICM cant be used.)

Prepare other materials according to the field test checklist.

List of Items to Be Checked Before Field Test

Mandatory/Optional

Owner Remarks

Vehicle mounted storage

batteries (12 PCS, fully charged)

Mandatory Driver of the

cooperator

Responsibility of

the cooperator

Power socket (1 PCS) Mandatory Driver of the

cooperator

Responsibility of

the cooperator

Vehicle mounted power

transformer (1 PCS)

Mandatory Driver of the

cooperator

Responsibility of

the cooperator

GPS (1 PCS) Mandatory Driver of the

cooperator

Responsibility of

the cooperator

Test laptop with available

battery (1 PCS)

Mandatory Test personnel

External data network adapter

(1 PCS)


Postpaid SIM card (1 PCS) Mandatory Test personnel Prevent network

access failure due

to arrears

Test data card (used for basic

service verification: DPA

CAT 8 data card)

Mandatory Test personnel Responsibility of

test personnel

LMT version matching the

NodeB


Key for the site Optional

License for field test Mandatory



List of Items to Be Checked Before Field Test

Mandatory/Optional

Owner Remarks

Field test vehicle with vehicle

mounted power supply (1

PCS)

Mandatory

Electric torch Optional

Screwdriver and PVC

insulation tape (may be used

at the site)

Optional

Selecting the Near Test Point

Drive the car and find the test point where the reported CQI is 30 and remains stable. Fasten

the terminal at the selected test point by using the extended USB cable and adhesive tape.

Use the QXDM software to observe the pilot path. When no data is transmitted, single-path is

used and CPICH EcNo is about -2.0. In this case, the quality of the radio channel is optimal.

Currently, the latest version provided by Qualcomm is 03.12.637. This version supports CQI

reporting but the reported CQI is inaccurate. Therefore, you need to compare the reported

CQI against the flow control trace on the NodeB CDT side of the network side. You should

obtain the latest QXDM software before the test.



There may be multiple points where the reported CQI is 30. For the purpose of subsequent

optimization, it is recommended that the point with a high RSCP value (about -30) be used.

The peak value at the near test point for DC-64QAM has stringent requirements for the radio scenario.

After the service is set up, the largest block (size range: 4070442192) can be dispatched and sent only when the reported CQI ranges between 28 and 30 and remains stable, the transmission is not restricted,

and the data source for the users is sufficient.

The SNR step between CQI 28, 29, and 30 reported by the UE is 2 dB.

Verifying the Optimization Result

After the optimal test point is found, observe the data transmission. The rate should exceed 35

Mbit/s. In this case, you can use the QXDM software to observe the decoding process. The

large block (size: 42192) is sent. The bit error rate exceeds 10% so that the rate does not

increase. Perform trace on the network side and find that the used power is about 97% and the

reported CQI fluctuates, causing a high bit error rate for large blocks.

Next, you need to enhance the available power of H, reduce the interference, and keep the

CQI stable.

The CPICH Power is reduced by 0.52 dB on site. The result is optimal when the CPICH Power is reduced by 1 dB, that is, the value of CPICH Power is changed from 310 to 300. In

this case, the available power of H is enhanced and the interference caused by the pilot to H is

reduced so that the reported CQI is not lower than 30.

If the channel quality is stable, only the blocks with a fixed size can be sent. If larger blocks

are forcibly sent, high block error rate occurs inevitably. The preceding optimization actually

does not provide a high reported CQI but enhances the channel quality. Therefore, the

problem about high block error rate cannot be solved simply by sending a fixed CQI.



5 Acceptance Standards 5.1 Downlink Peak Rate

Theoretically, the downlink peak rate per user of DC-HSDPA is 42 Mbit/s. During the field

test in a good radio environment, the acceptance baseline for the downlink rate per user of

DC-HSDPA is 37 Mbit/s. As the radio environment for field test differs, the test results differ

slightly. During the test through a shielded cabinet in the lab, the downlink peak rate per user

of DC-HSDPA can reach 41.8 Mbit/s in case of packet sending on the RNC and 41.5 Mbit/s in

case of FTP.

5.2 Handover

The acceptance standards for DC handover are the same as those for the common CS or PS

handover. That is, no call drop occurs during the handover process. As the DC feature uses the

dual-carrier technology, when observing signaling messages during the handover process, you

do not need to observe the handover of the UE in two cells at the same time but only need to

observe the handover of the UE in the master cell.



6 Test Tools 6.1 Packet Sending

6.1.1 Packet Sending on the RNC

You can control the packet rate by setting the packet length and packet sending interval. For

example: 1000 x 8 / 0.3 = 26.7 Mbit/s.

Data configuration is not mandatory but the data amount must be sufficient.

It is recommended that the packet length should not exceed 1500 bytes (the recommended

packet length is about 1450 bytes). Otherwise, the throughput rate is reduced.

Switch:



6.1.2 Packet Sending Using Iperf

When sending packets using an Iperf, specify the server and client in the following method:

If packets are transmitted on the downlink, set the Iperf server to the FTP server, and the Iperf

client to the UE.

If packets are transmitted on the uplink, set the Iperf server to the UE, and the Iperf client to

the FTP server.

Before testing, save the Iperf.exe file in the directory where the MS-DOS is stored, for

example, C:\Documents and Settings\Administrator, as shown in the following figure:



Then, run the following commands in the MS-DOS prompt window:

On the Iperf server: >iperf -f k -i 2 -u -c "IP address of UE" -t 1200 -b 60M

On the Iperf client: >iperf -s -f k -i 2 u

The following attachment is an example Iperf.ext file:

6.2 Common Trace

6.2.1 Single-User Trace on the RNC

Single-user trace on the RNC is usually used to identify the problem that the throughput rate

is too low. During the problem identification, Trace Mode is set to Full Mode and Report

Interval is set to 91 (special setting on the RNC. The value range of this parameter is 1 to 100,

in which 91 indicates a long period). The following figures show the detailed settings.



6.2.2 Single-User Trace on the NodeB

Downlink Service

Generally, you only need to trace the HSDPA enhancement messages and flow control

messages. When necessary, contact R&D engineers to check whether to add other trace items.

The following figures show other reference options.



Uplink Service

To locate the uplink service, see the reference settings in the following figures.



6.3 QXDM

The QXDM software provided by Qualcomm is installed in the same way as the earlier

version. Currently, you can apply for the license through the internet as follows:

Access the internet and click the QXDM icon. In the displayed license activation dialog box,

fill in and confirm the related information:

User Name: Huawei

Password: keyboard

Admin Key: 1024

The QXDM software is used in the same way as the earlier version. Currently, however,

certain observation points are displayed improperly.



7 Guide to Test Cases This chapter is designed for test personnel to run and observe DC-HSDPA acceptance test

cases. This chapter does not cover all the acceptance test cases and is only used as a guide.



7.1 Operation Guide to the Test Case: DC Throughput Performance

7.1.1 Scripts for the Test Case: Single User Throughput of DC in Good Radio Condition

Global ID

FA265-0101

Priority

Middle

Objective

Evaluate the throughput performance differentiation between DC and SC single user in good position.

Network diagram

Standard networking of acceptance:

NE: RNC1, NodeB1, CELL XXXX0, CELL XXXX1 and they are DC group.

Local cell is 0 and 1.

Prerequisites

1. WCDMA system is operational.

2. One DC-64QAM category24 UE is subscribed correctly in HLR: Set traffic class to

Interactive/background, max bit rate to UL 5740 kbit/s/DL 42100 kbit/ss and camps on the DC cell.

3. One SC-64QAM category14 UE is subscribed correctly in HLR: Set traffic class to

Interactive/background, max bit rate to UL 5740 kbit/s/DL 21600 kbit/s and camps on the DC cell.

4. RNC license switch HSPA + Downlink 42 Mbps per User=ON.

5. RNC license switch HSPA + Downlink 21 Mbps per User=ON.

6. DC Cells support DL L2 Enhance, 64QAM, DC-HSDPA in RNC:

SET UCORRMALGOSWITCH:

CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1&CFG_HSDPA_DC_SWITCH-1;

MOD UCELLALGOSWITCH: CellId=XXXX0,

HspaPlusSwitch=64QAM-1&DL_L2ENHANCED-1&DC_HSDPA-1;

MOD UCELLALGOSWITCH: CellId=XXXX1,

HspaPlusSwitch=64QAM-1&DL_L2ENHANCED-1&DC_HSDPA-1;

7. Set DL BE traffic threshold on HSDPA to 256 kbit/s in RNC:

SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D256;

8. Set UL BE traffic threshold on HSUPA to 608 kbit/s in RNC:

SET UFRCCHLTYPEPARA: UlBeTraffThsOnHsupa=D608;

9. Modify the code resource of test cell: On the RNC LMT, configure 14 HS-PDSCH codes and 4

HS-SCCH codes:

DEA UCELLHSDPA: CELLID= XXXX0;

MOD UCELLHSDPA: CELLID= XXXX0, AllocCodeMode=Automatic,

HsPdschMaxCodeNum=14, HsPdschMinCodeNum=5, HsScchCodeNum=4;

DEA UCELLHSDPA: CELLID= XXXX1;



MOD UCELLHSDPA: CELLID= XXXX1, AllocCodeMode=Automatic,


10. Set Cell Max Power=43dBm, PCPICH Power=33dBm in RNC.

11. NodeB license Number of local cells supporting DL 64QAM is bigger than 2;

12. NodeB license Number of local cells supporting DL DC-HSDPA is bigger than 2;

13. DC local cells are in the same sector, and in DUALCELLGROUP of NodeB:

ADD DUALCELLGRP: FIRSTLOCELL=0, SECONDLOCELL=1;

14. Act the DC cells in RNC:

ACT UCELLHSDPA: CELLID= XXXX0;

ACT UCELLHSDPA: CELLID= XXXX1;

15. Trace the IU/IUB/UU interface and Throughput Bandwidth in RNC LMT.

Procedure Expected result

UE must be located at good radio condition

(CQI>29, PCPICH RSCP>-70dBm). The CQI of the UE is around 30.

Category24 UE dials up and sets up a PS service.

UE do FTP downloading from FTP server.

PS service is set up successfully, and the service

is carried on the E-DCH and the HS-DSCH.

The bandwidth of downlink throughput is 42.1

Mbit/s in RNC LMT.

Use Dumeter to record the throughput for 3

minutes.

Dumeter can record the throughput normally.

Dumeter stops recording throughput and then

Category24 UE stops the PS service.

Max throughput, Min throughput and AVE

throughput can be read in Dumeter.

Category14 UE dials up and sets up a PS service.

UE do FTP downloading from FTP server.

PS service is set up successfully, and the service

is carried on the E-DCH and the HS-DSCH.

The bandwidth of downlink throughput is 21

Mbit/s in RNC LMT.

Use Dumeter to record the throughput for 3

minutes.

Dumeter can record the throughput normally.

Dumeter stops recording throughput and then

Category24 UE stops the PS service.

Max throughput, Min throughput and AVE

throughput can be read in Dumeter.

Repeat 2~7 for 3 times. Get the throughput of each test.

Remark

None

Caution

None

Additional Remark

None



7.1.2 Preparations for the Test

Objective: This test case aims to demonstrate the downlink peak rate per user (42 Mbit/s) in a

cell when the DC feature is enabled.

Minimum networking requirements: RNC x 1; NodeB x 1; two cells with adjacent frequencies

support HSUPA, downlink 64QAM, and DC-HSDPA; the local cell on the NodeB must

support downlink 64QAM and DC-HSDPA.

Two UEs are required for the test:

A UE CAT 24 whose subscribed rate is 5740 kbit/s on the uplink and 43,200 kbit/s on the

downlink

A UE CAT 14 whose subscribed rate is 5740 kbit/s on the uplink and 21,600 kbit/s on the

downlinkCheck in the RNC license whether the transmission rates of 21 Mbit/s and 42

Mbit/s are supported on the downlink.

Check in the NodeB license whether there are more than two local cells supporting the

Downlink 64QAM and DC-HSDPA features under the NodeB.

In this test case, as certain settings on the RNC and NodeB sides need to be modified, you

need to record the current parameter status before setting the parameters for the test case. In

this way, environment restoration after the test can be performed easily.

For the parameters used for modifying the RNC and NodeB code allocation in this test case,

you need to run the LST command to check the current configurations before modification.

On the RNC, run the LST UCELLHSDPA command to check the settings for code allocation.

On the NodeB, run the LST MACHSPARA command to check the switch status of dynamic

code allocation.

7.1.3 Test Execution

1. Set the parameters.

To turn on the algorithm switches for the Downlink 64QAM and DC-HSDPA features in the

RNC, run the following command on the RNC:

SET UCORRMALGOSWITCH:

CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1&CFG_HSDPA_DC_SWITCH-1;

To turn on the algorithm switches for the Downlink 64QAM, enhanced L2, and DC-HSDPA

features in all cells, run the following command on the RNC:

MOD UCELLALGOSWITCH: CellId=XXXX,

HspaPlusSwitch=64QAM-1&DL_L2ENHANCED-1&DC_HSDPA-1;Note that the command

must be executed for the two cells in a DC group.

To set the uplink and downlink thresholds for best effort (BE) services, run the following

command on the RNC:

SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D256; SET UFRCCHLTYPEPARA:

UlBeTraffThsOnHsupa=D608;

To set a maximum number of 14 High-Speed Physical Downlink Shared Channels

(HS-PDSCHs) and 4 High Speed Shared Control Channel (HS-SCCHs) for each cell, run the

following command:

DEA UCELLHSDPA: CELLID= XXXX;

MOD UCELLHSDPA: CELLID= XXXX, AllocCodeMode=Automatic,




To bind two local cells as a DC group, run the following command on the NodeB:

ADD DUALCELLGRP: FIRSTLOCELL=0, SECONDLOCELL=1;

To activate the two cells in a DC group and set parameter, run the following command on the

RNC:

ACT UCELLHSDPA: CELLID= XXXX;

2. Enable the trace on the Uu interface (as shown in the following figure).

Step 1 Log in to the LMT. Then click Trace to open the trace page.

Step 2 On the navigation tree, choose UMTS Services > Uu Interface Trace to open the trace window.

Step 3 Fill in the RNC ID and cell ID in the Cell Config field and then click Submit to start the trace process.

3. Enable the connection performance monitoring (as shown in the following figure).

Step 1 Log in to the LMT. Then click Monitor to open the monitoring page.

Step 2 On the navigation tree, choose UMTS Monitoring > Connection Performance Monitoring to open the monitoring configuration window.

Step 3 In the Parameter Setting message box, select DL Throughput Bandwidth.

Step 4 Fill in the IMSI.

Step 5 Click Submit to start the monitoring process.



4. Use the QXDM to detect a site with relatively good radio signal (CQI>29, PCPICH RSCP>-70dBm). At this site, use the UE CAT 24 to initiate PS services. It is

recommended that the terminal be connected to a stable FTP server without speed

restriction. Check the signaling trace and performance monitoring windows.

In case of stable FTP downloading, you can find the downlink rate (the downlink rate

should be about 37 Mbit/s) in the performance monitoring window.

In the signaling trace window, you can find the RRC_RB_SETUP message sent by the

RNC to the UE. Double-click this message. The contents of the message are displayed.

In the rab-InformationSetupList signaling message, ul-TrCH-Type should be e-dch and

dl-TransportChannel-Type should be hsdsch. In the dl-HSPDSCH-Information

signaling message, you can find dl-64QAM-Configured: true, which indicates that

64QAM is successfully set up. In the dl-SecondaryCellInfoFDD signaling message, you

can find dl-64QAM-Configured: true, which indicates that 64QAM for the cell of the

second frequency is successfully set up. If both dl-64QAM-Configured: true and

dl-64QAM-Configured: true are displayed, it indicates that DC is successfully set up.

In the performance monitoring window, you can find that the allocated bandwidth is 42.1

Mbit/s.

5. On the Dumeter, observe the performance KPIs for more than 3 minutes, save the obtained results, and terminate PS services on the UE CAT 24.

6. Use UE CAT 14 to initiate PS services using dialup access. In the performance monitoring window, you can find that the allocated bandwidth is 21 Mbit/s. In the trace

of the RRC_RB_SETUP signaling message, you can find ul-TrCH-Type: e-dch in the

"rab-InformationSetupList" information element (IE).

7. On the Dumeter, observe the performance KPIs for more than 3 minutes, save the obtained results, and terminate PS services on the UE CAT 14.

8. Save the monitoring result file and message trace result.

9. Restore the test environment.

The operation procedure for the test case (DC-HSDPA Service Throughput in the Center of

Cell) is complete.



8 Points for Attention in the Data Configuration

8.1 Configuration at the RNC When configuring the algorithm switches, note that some parameters are global whereas

others are local (They are valid only in a local cell.). Global parameters need to be configured

only once, whereas local parameters must be set once for each cell. The algorithm switch for

the 64QAM is a global parameter and needs to be set only once, as shown in section 7.1.3

"Test Execution." The algorithm switches for the Downlink 64QAM, enhanced L2, and

DC-HSDPA features are local parameters and must be set once for each cell.

When modifying or adding DC groups, pay attention to the following policies:

For newly added cells, set their parameters to the same values as existing cells.

For the two cells in a DC group, modify their parameters at a time to keep their

parameter settings identical. If any of the previous policies is violated, the DC-HSDPA

feature cannot be successfully activated.

The two cells that form a DC group must meet the following conditions:

Two cells belong to the same operator, the same frequency band, and the same sector.

Two cells have the same TCELL and adjacent frequencies (the interval is not more than

5 MHz).

Two carriers of the same sector share one transmit channel, that is, share one RRU.

When both RRUs support DC-HSDPA, the cascading mode should be used between the

two RRUs.

8.2 Configuration at the NodeB

At the NodeB, configure newly added cells based on parameter settings for existing cells.

If two local cells are mistakenly configured as a DC group, perform the following steps:

Step 1 Deactivate the two cells at the RNC.

Step 2 Delete the DC group at the NodeB.

Step 3 Set up the correct DC group.



9 FAQs 9.1 Optimization of the Presentation and Competition Test

1. Optimize the FTP server.

If a Microsoft IIS FTP server is used, go to the directory for the FTP server

HKLM\System\CurrentControlSet\Services\AFD\Parameters. Then, set the

TransmitIoLength registry key of the DWORD type to 262144. With this setting, the send

window of the server can transmit a maximum of 256,000 frames at a time. If no

TransmitIoLength is displayed in the registration, add one and set it to 262144.

If a Serv-U FTP server is used, open the daemon.ini file in the Serv-U installation directory

and set sendbuff to a value larger than 99999. To modify the sendbuff settings, perform the following steps:

Delete the settings for sendbuf.

Stop the Serv-U services.

In the daemon.ini file, set sendbuf to a desired value.

Save the setting and exit.

Start the Serv-U services again.

Check the sendbuff settings and use Ethereal to capture packets. If packets are captured, the desired

value takes effect.

If the settings fail, restart the server.

2. Optimize the TCP window on the UE side.

To optimize the TCP window on the UE side, run the following attachment on the test PC.



9.2 Decrease of the Throughput Rate When the Tcells of the Two Cells Configured on a Single RRU

This problem is inherent for the RRU. Theoretically, the RF module should ensure

high-linearity signal input and low-distortion signal output. If the peak-to-average ratio (PAR)

of the input signals is too high, the EVM of the output signals of the RRU and even the

service performance are worsened. When the two cells are configured with the same

scrambling code and the same Tcell, baseband signals are nearly overlapped in phase. The

peak value and bottom value increase accordingly. (When the two cells are configured with

different Tcells, it means that the two cells are not configured in the same phase to stagger the

delay of carriers. When the two cells are configured with different scrambling codes, it means

that the feature difference between baseband signals is maximized.)

To implement the DC feature, two cells with different frequencies but with the same coverage

must be synchronized strictly. Therefore, the two cells must have the same TCELL. In this

case, the PAR is inevitably too high. The current method to dodge this problem is to disable

the static voltage regulation. This method, however, results in low RF efficiency and therefore

is not suitable for large-scale commercial use. The detailed solution needs to be further

discussed.

9.3 Service Release due to UE Failure When the UE Sends the RLC ACK But the RNC Receives the TRB ACK

Qualcomm and Huawei RNC engineers confirm that the RLC ACK sent by the UE and the

TRB ACK seen on the RNC are the same message, that is, the RLC RST PDU described in

the RLC protocol. In this scenario, the reason for sending the PDU is as follows:

The UE sends the uplink data and waits for the ACK from the RNC. If the UE fails to receive

the ACK from the RNC, the UE sends the RLC RST PDU and waits for the RLC RST PDU

ACK from the network side. If the UE receives the RLC RST PDU ACK from the network

side, the UE continues to send the next uplink PDU. If the UE fails to receive the RLC RST

PDU ACK from the network side, the UE continues to send the RLC RST PDU until TRB

resetting occurs (when the maximum number of times for RLC resetting configured on the

network side is reached). Currently, the maximum number of times for RLC resetting

configured on the network side is 32, which can be found in the RB SETUP message.

The problem is that after the UE sends the PDU, the RNC does not find the PDU, and

therefore does not return the ACK. The possible reasons for the problem are as follows:

The uplink packet is lost on the air interface, NodeB, or UE.

The UE improperly sends the uplink packet.

Analyze the problem by comparing the packets on the UE, NodeB, and RNC. But strangely,

the scenario of the service is sending Testping packets on the FTP side. In this scenario, the

UE should not send any uplink packet.

The problem may be related to the insertion of an internet network cable during the test

performed by Qualcomm engineers (data is still transmitted in the uplink direction when

certain software on the laptop sends certain unrelated packets). Remove the internet network

cable and the problem is solved.



In addition, if the IP route of the network can be added automatically, you can dodge the

problem by using other methods. For example, delete the uplink route from the laptop. That is,

after dial-up, run the route print command in MS-DOS mode to query the current route

information and then delete the route that is set up after dial-up.

The UE releases the service in case of UE failure (that is, the UE is unstable and crashed).

9.4 Dumeter Display

During normal packet sending, the throughput rate is continuous but the Dumeter display

usually contains intermittent blank and the throughput rate decreases. Troubleshooting shows

that the problem is related to the APN software provided by HUAWEI. Dodging method:

uninstall the APN software and restart the PC.

9.5 High Block Error Rate for the 41440 Data Block

The normal result is that the HS-PDSCH SNR required by the 41440 data block is 1 dB

smaller than that required by the 42192 data block. During the test, however, the SNR

required by the Qualcomm terminal to receive the 41440 data block is larger than that

required for receiving the 42192 data block.

Qualcomm engineers confirm that their SNR curve does not rise smoothly and 41440

indicates an inflection point. Therefore, in this scenario, dispatching the 42192 data block

instead of the 41440 data block achieves a better result.

This problem is related to the terminal.

You can dodge this problem by modifying the MPO value, that is, reducing or increasing the

MPO value. Note that you need to redial the number after each time the MPO value is

modified.

9.6 Rate for Packet Sending Lower Than 28 Mbit/s at the RNC

Description: Packet sending is commonly used to verify the peak throughput at the RNC. If

DPUb boards are used in the RNC, the rate for packet sending cannot exceed 28 Mbit/s.

Solution: Verify the peak throughput by sending packets from the FTP server to the RNC. To

verify whether the peak throughput of 42 Mbit/s can be realized, replace the DPUb board with

the DPUe board.

9.7 Using a Terminal Supporting 64QAM During the Test

As the DC feature is fully based on the 64QAM technology, a terminal supporting 64QAM

should be used during the on-site acceptance test. When identifying a problem, you can run the 64QAM service separately. If the 64QAM service can run properly and the indexes meet



the standards, it indicates that the DC service is improperly configured. If the 64QAM service

fails to meet the standards, the problem is unrelated to DC. In this case, you need to solve the

problem about 64QAM before performing acceptance test for DC.

DC-HSDPA Feature Acceptance Guide

Documents

Transcript of DC-HSDPA Feature Acceptance Guide