RAN12 0 DC HSDPA Feature Acceptance Guide 20100802 V1 0 A

Product name
Confidentiality level
Wireless Product Service Department
Product version
Total 44 pages
RAN12.0 DC-HSDPA Feature Acceptance Guide

(For internal use only)
Prepared
by
Date
Gao Peng (employee

ID: 00133535)
Reviewed
by
Date
Reviewed
by
Date
Granted by
Date
Huawei Technologies Co., Ltd.

All rights reserved
2010-08-02
Confidentiality Level: Internal
Revision Record
Date
Version
Description
Author
2010-08-02
V1.0
Draft completed
Gao Peng (employee

ID: 00133535
2016-11-13
Huawei Technologies Proprietary
Page 2 of 44
Contents
1 Overview...................................................................................... 7
2 General Process of the DC-HSDPA Deployment...............................9
3 Preparations for the DC-HSDPA Deployment.................................10
3.1 License.............................................................................................................................................................10
3.2 Preparations for the Environment....................................................................................................................11
3.2.1 RNC........................................................................................................................................................11
3.2.2 NodeB.....................................................................................................................................................11
3.2.3 UE...........................................................................................................................................................11
3.2.4 CN...........................................................................................................................................................13
3.2.5 HLR........................................................................................................................................................13
3.3 Networking Mode............................................................................................................................................14
3.4 Software Version..............................................................................................................................................14
3.5 Planning for the Transmission Network..........................................................................................................14
4 Data Configuration......................................................................15
4.1 Configuration for the CN.................................................................................................................................15
4.1.1 Configuration for the GGSN (HUAWEI)...............................................................................................15
4.1.2 Configuration for the SGSN (HUAWEI)...............................................................................................15
4.1.3 Configuration for Subscriber Definition.................................................................................................16
4.2 Configuration for the RAN..............................................................................................................................16
4.2.1 Configuration for the Transport Layer....................................................................................................16
4.2.2 Configuration for the Radio Layer.........................................................................................................17
4.3 Optimization for the DC Throughput Rate......................................................................................................21
4.3.1 RNC........................................................................................................................................................21
4.3.2 NodeB.....................................................................................................................................................23
4.4 Examples of DC Field Verification..................................................................................................................24
4.4.1 Field Verification Results.......................................................................................................................24
4.4.2 Commissioning Process..........................................................................................................................24
5 Acceptance Standards.................................................................28
5.1 Downlink Peak Rate........................................................................................................................................28
5.2 Handover..........................................................................................................................................................28
2016-11-13
Page 3 of 44
6 Test Tools...................................................................................29
6.1 Packet Sending.................................................................................................................................................29
6.1.1 Packet Sending on the RNC...................................................................................................................29
6.1.2 TestPing..................................................................................................................................................30
6.2 Common Trace.................................................................................................................................................30
6.2.1 Single-User Trace on the RNC...............................................................................................................30
6.2.2 Single-User Trace on the NODEB..........................................................................................................31
6.3 QXDM.............................................................................................................................................................34
7 Guide to Test Cases.....................................................................35

7.1 Operation Guide to the Test Case: DC Throughput Performance...................................................................35
7.1.1 Scripts for the Test Case: DC-HSDPA Service Throughput in the Center of Cell.................................35
7.1.2 Preparations for the Test.........................................................................................................................37
7.1.3 Test Execution........................................................................................................................................38
8 FAQs........................................................................................... 40
8.1 Decrease of the Throughput Rate When the Tcells of the Two Cells Configured on a Single RRU Are the
Same.......................................................................................................................................................................40
8.2 Service Release due to UE Failure When the UE Sends the RLC ACK But the RNC Receives the TRB ACK
...............................................................................................................................................................................40
8.3 Dumeter Display..............................................................................................................................................41
8.4 High Block Error Rate for the 41440 Data Block............................................................................................41
8.5 Using a Terminal Supporting 64QAM During the Test...................................................................................41
2016-11-13
Page 4 of 44
Figures
Figure 2-1 General process of the DC-HSDPA deployment...................................................................................9
Figure 3-1 RNC license.........................................................................................................................................10
Figure 3-2 NodeB license......................................................................................................................................11
2016-11-13
Page 5 of 44
Tables
Table 3-1 Control items of DC license..................................................................................................................10
Table 3-2 Categories of HSPA+ terminals (the categories in red support HSPA+ Phase2)..................................12
2016-11-13
Page 6 of 44
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, including the
following contents:
64QAM + MIMO: provides the peak download rate of 42 Mbit/s in the downlink direction,
and increases the downlink capacity through higher order modulation and by transmitting two
streams through two antennas in the downlink direction.
DC-HSDPA: provides the peak download rate of 42 Mbit/s in the downlink direction. The
basic idea for 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.
UL Enhanced Layer 2: supports the flexible RLC PDU in the uplink direction. When the air
interface is of high quality, the air interface can send large PDUs to increase the speed. When
the power of the air interface is restricted, the air interface can segment MAC SDUs to reduce
the residual BLER of the HARQ.
UL 16QAM: adopts a high-level modulation mode to improve the uplink peak rate.
Theoretically, the uplink peak rate can reach 11.5 Mbit/s.
The following sections describe the advantages of HSPA+ from the perspectives of mobile
operators and end users.
Increasing the downlink capacity of the network and providing a high spectral efficiency
in case of high signal-to-noise ratio
The HSPA+ 64QAM technology can provide higher data traffic than HSDPA by quickly
adjusting the downlink modulation and encoding modes and using a higher order
modulation mode when users are subject to a good radio environment. Theoretically, the
maximum downlink peak rate provided by the HSPA+ 64QAM technology can reach
21.096 Mbit/s (TB_Size / TTI = 42192 / 2 ms).
2016-11-13
Page 7 of 44
The HSPA+ MIMO technology utilizes the special dimension resources and adopts the
multi-antenna technology at the transmitting end and receiving end at the same time.
Therefore, the HSPA+ MIMO technology can multiply the transmission capacity of the
radio communication system in a high signal-to-noise ratio environment without
increasing the transmit power and bandwidth. The increase of capacity is proportional to
the number of antennas. Theoretically, the maximum downlink peak rate provided by the
HSPA+ MIMO technology can reach 27.952 Mbit/s (TB_Size / TTI = 27952 / 2 ms x 2
(two streams)).
The 64QAM+MIMO technology of HSPA+ Phase2 uses the combination of MIMO and
64QAM for a single user to provide the single-user peak throughput rate. Theoretically,
the maximum downlink peak rate can reach 42 Mbit/s.
For the mobile operator, the HSPA+ technology can reduce the transmission cost for data
stream per M bytes, increase the average capacity of the system, improve the downlink
data service performance for a single user, and improve the throughput rate of cells.
Improving the service performance for end users

For ordinary 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.
This document describes the deployment and acceptance processes and methods for the DC-HSDPA
feature.
2016-11-13
Page 8 of 44
General Process of the DCHSDPA Deployment
Figure 1.1 General process of the DC-HSDPA deployment
2016-11-13
Page 9 of 44
2016-11-13
Page 10 of 44
Preparations for the DC-HSDPA

Deployment
3.1 License
To implement the HSPA+ Phase2 DC feature, support from license is required. Figure 1.1
describes the licenses on the RAN side.
Figure 1.1 Control items of DC license
Feature ID
Feature Name
Description
Name of
License Item
WRFD-010689
HSPA+ Downlink
42Mbps 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.
2016-11-13
Page 11 of 44
Figure 1.2 RNC license
NodeB License: DSP LICENSE, unlimited.

Figure 1.3 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.
2016-11-13
Page 12 of 44
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.
Figure 1.1 Categories of HSPA+ terminals (the categories in red support HSPA+ Phase2)
HSDSCH
Categor
y
Maximu
m
Number
of HSDSCH
Codes
Receive
d
Minim
um
InterTTI
Interv
al
Maximu
m
Number
of Bits
of an
HSDSCH
Transpo
rt Block
Receive
d within
Total
Numb
er of
Soft
Chann
el Bits
Support
ed
Modulati
ons
without
MIMO
Operatio
n or
Dual
Cell
Operatio
n
Support
ed
Modulati
ons
Simultan
eous
with
MIMO
Operatio
n and
without
Dual Cell
Operatio
n
Support
ed
Modulati
ons with
Dual Cell
Operatio
n
QPSK,
16QAM
Not
applicable
(MIMO not
supported)
Not
applicable
(dual cell
operation
not
supported)
an HSDSCH
TTI
NOTE 1
Category 1
7298
19200
Category 2
7298
28800
Category 3
7298
28800
Category 4
7298
38400
Category 5
7298
57600
Category 6
7298
67200
Category 7
10
14411
115200
Category 8
10
14411
134400
Category 9
15
20251
172800
Category 10
15
27952
172800
Category 11
3630
14400
Category 12
3630
28800
Category 13
15
35280
259200
2016-11-13
QPSK
QPSK,
Page 13 of 44
HSDSCH
Categor
y
Maximu
m
Number
of HSDSCH
Codes
Receive
d
Minim
um
InterTTI
Interv
al
Maximu
m
Number
of Bits
of an
HSDSCH
Transpo
rt Block
Receive
d within
Total
Numb
er of
Soft
Chann
el Bits
Support
ed
Modulati
ons
without
MIMO
Operatio
n or
Dual
Cell
Operatio
n
16QAM,
64QAM
an HSDSCH
TTI
NOTE 1
Support
ed
Modulati
ons
Simultan
eous
with
MIMO
Operatio
n and
without
Dual Cell
Operatio
n
Category 14
15
42192
259200
Category 15
15
23370
345600
Category 16
15
27952
345600
Category 17
NOTE 2
15
35280
259200
QPSK,
16QAM,
64QAM
23370
345600
QPSK,
16QAM
42192
259200
QPSK,
16QAM,
64QAM
27952
345600
QPSK,
16QAM
Category 18
NOTE 3
15
Category 19
15
35280
518400
Category 20
15
42192
518400
Category 21
15
23370
345600
Category 22
15
27952
345600
Category 23
15
35280
518400
Category 24
15
42192
518400
2016-11-13
Support
ed
Modulati
ons with
Dual Cell
Operatio
n
QPSK, 16QAM
QPSK, 16QAM, 64QAM
QPSK,
16QAM
QPSK,
16QAM,
64QAM
Page 14 of 44
3.2.4 CN
The CN must be upgraded to support the R8 protocol version.
3.2.5 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
2016-11-13
Page 15 of 44
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.
2016-11-13
Page 16 of 44
Data Configuration
4.1 Configuration for the CN

The CN and HLR must support the maximum downlink peak rate (42 Mbit/s). If Huawei CN
is used, the reference configuration is as follows (the detailed reply from the CN side should
be followed).
4.1.1 Configuration for the GGSN (HUAWEI)

1.
HSPA+ provides users with a higher throughput than HSDPA. This means that UMTS
bears a higher rate. Therefore, certain settings for capacity must be performed on the
GGSN.
Run the following command to set the maximum rate to 8640 Kbit/s.
SET QOS: MBRDNLK=8640, GBRDNLK=8640;
On the GGSN, run the LST QoS and SET QoS commands to check whether the set
uplink data rate reaches the required value. If not, modify and set the values of uplink
and downlink data rates.
Note: The set QoS is the default QoS in the system and generally does not take effect.
The default QoS takes effect only when the QoS sent by the SGSN contains an invalid
value.
2.
On the GGSN, run the LST APNQoS command to check whether the uplink data rate
for a specified APN is set. If not, do not set the uplink data rate for the specified APN. If
yes, check whether the set uplink data rate reaches the required value. If the set uplink
data rate does not reach the required value, modify and set the values of uplink and
downlink data rates.
4.1.2 Configuration for the SGSN (HUAWEI)

Run the following command to set the maximum rate to 8640 Kbit/s (254 represents 8640
Kbit/s).
SET 3GSM: PARATYPE=QOS, MBRUPLK=254, GBRUPLK=254, MBRDNLK=254,
GBRDNLK=254, MBRDNLKEX=250, GBRDNLKEX=250, MBRUPLKEX=250, GBRUPLKEX=250;
SET PROCR: RNCQOSVERSION=R8, GGSNQOSVERSION=R8, SGSNQOSVERSION=R8;
Set the RNC version to R8. Note that the following command should correspond to the
actually used RNC index.
2016-11-13
Page 17 of 44
MOD RNC: IMS=YES, RNCVER=R8, R8QOS=YES;
Change the QoS attribute of the specified GGSN to R8Qos version.

MOD GGSNCHARACT: IPT=IPV4, QOSVER=R8Qos;
On the SGSN, run the LST COMPATIBILITY and SET COMPATIBILITY commands.
Set RABQoS (parameter negotiation) to Yes.
SET COMPATIBILITY: RABQOS=YES;
4.1.3 Configuration for Subscriber Definition

Based on the rate requirement of the operator, set the extended rate to 42 Mbit/s (DL) to
support the HSPA+ DC feature.
4.2 Configuration for the RAN

4.2.1 Configuration for the Transport Layer
RNC
Among the IP types of ADD TRMMAP, the transmission priorities (such as AF42 and AF11)
of the following services (such as signaling and session) must contain the IPPATH that
corresponds to the PATHT index type.
HDSRBPRIPATH=AF42
//HSDPA Signaling primary path
HDSRBSECPATH=NULL
//HSDPA Signaling secondary path
HDCONVPRIPATH=AF42
//HSDPA conversational primary path
HDCONVSECPATH=NULL
//HSDPA conversational secondary path
HDSTRMPRIPATH=AF11
//HSDPA streaming primary path
HDSTRMSECPATH=NULL
//HSDPA streaming secondary path
HDINTHGHPRIPATH=AF11
//HSDPA high PRI interactive primary
path
HDINTHGHSECPATH=NULL
//HSDPA high PRI interactive secondary
path
HDINTMIDPRIPATH=AF11
//HSDPA middle PRI interactive primary
path
HDINTMIDSECPATH=NULL
//HSDPA middle PRI interactive secondary
path
HDINTLOWPRIPATH=AF11
//HSDPA low PRI interactive primary path
HDINTLOWSECPATH=NULL
//HSDPA low PRI interactive secondary
path
2016-11-13
HDBKGPRIPATH=AF11
//HSDPA background primary path
HDBKGSECPATH=NULL
//HSDPA background secondary path
Page 18 of 44
Add the IPPATH. If the peak rate must be reached, the configured bandwidth must exceed 42
Mbit/s (including the configured bandwidth for the intermediate switch).
ADD IPPATH: ANI=0, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=AF11,
IPADDR="1.1.1.2", PEERIPADDR="1.1.1.1", PEERMASK="255.255.255.255",
TXBW=45000, RXBW=45000, CARRYFLAG=NULL, VLANFlAG=DISABLE,
PATHCHK=DISABLED;
Set the mapping between the PHB and the DSCP.

SET PHBMAP: SRN=0, SN=14, PHB=AF11, DSCP=40;
NodeB
The NodeB must be configured with the related Iub PATH. Since the R11 version, the NodeB
is not configured with the PATH type. The IP address of the NodeB matches the related PATH
according to the DSCP value sent by the RNC during service setup.
ADD IPPATH: PATHID=0, SRN=0, SN=0, SBT=BASE_BOARD, PT=ETH,
JNRSCGRP=DISABLE, NODEBIP="1.1.1.1", RNCIP="1.1.1.2", DSCP=40,
RXBW=50000, TXBW=50000, TXCBS=15000, TXEBS=15000, FPMUXSWITCH=DISABLE;
For the bandwidth configured for the IPRAN, see the related bandwidth configuration in the
IPRAN deployment guide. As the physical bandwidth for IP transmission exceeds the rate of
the air interface, the recommended IP bandwidth is 50 Mbit/s. In addition, in case of IPRAN
networking mode, check whether the port modes at both ends are the same (100 M full
duplex).
4.2.2 Configuration for the Radio Layer

RNC
Enable the switch of the 64QAM algorithm.

SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1;
Enable the switch of the DC HSDPA algorithm.

SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSDPA_DC_SWITCH-1;
Set the preferred technology to DC HSDPA.

SET UFRC: MIMO64QAMorDCHSDPASwitch=DC_HSDPA;
Use HSDPA if the stream service is required.

SET UCORRMALGOSWITCH: MapSwitch=MAP_PS_STREAM_ON_HSDPA_SWITCH-1;
Set the threshold of HSDPA.

SET UFRCCHLTYPEPARA: DlStrThsOnHsdpa=D64, DlBeTraffThsOnHsdpa=D64;
Activate the HSDPA function of the cell.

ADD UCELLHSDPA: CellId=1, AllocCodeMode=Automatic,
CodeAdjForHsdpaSwitch=ON;
ACT UCELLHSDPA: CellId=1;
2016-11-13
Enable the switches of the downlink L2 enhancement and DC-HSDPA function of the
cell.
Page 19 of 44
MOD UCELLALGOSWITCH: CellId=1, HspaPlusSwitch=DL_L2ENHANCED1&DC_HSDPA-1;
Activate the license for the downlink peak rate (42 Mbit/s).
ACT LICENSE: ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=HSPA_DOWN42_PER_USER1;
Check whether the current DC status is OK.

DSP UCELLCHK: CHECKSCOPE=CELLID, CellId=1;
DC-HSDPA function of cell indicates whether the logical cell provides the DC function,
depending on the status of the local cell.
DC-HSDPA function of local cell indicates whether the local cell provides the DC function.
Local Cell ID of DC Assisted Cell indicates the ID of another cell in the DC carrier group that
corresponds to the local cell.
1. For the following parameters, check whether they are the recommended baseline parameters. If yes,
they do not need to be modified.
2. The following parameters are optional but related to the policies such as networking mode. Therefore,
you need to negotiate with network planning engineers for the operations.
Allocate and configure the code words for the DC cell.

If the NodeB uses dynamic codes, perform static configuration. That is, statically
allocate five HSDSCH codes and four HSSCCH codes.
ADD UCELLHSDPA: CellId=1, AllocCodeMode=Manual, HsPdschCodeNum=5,
HsScchCodeNum=4;
If the NodeB uses static codes, perform dynamic configuration. That is, allocate 515
HSDSCH codes and four HSSCCH codes.
ADD UCELLHSDPA: CellId=1, AllocCodeMode=Automatic,
HsPdschMaxCodeNum=10, HsPdschMinCodeNum=5, HsScchCodeNum=4;
Configure the power for the DC cell (dynamic power allocation is adopted).
MOD UCELLHSDPA: CellId=1, HspaPower=0;
2016-11-13
Configure the QoS assurance for DC. It is recommended that the baseline parameters be
used. The detailed values of the parameters are determined according to the requirements
of the operator.
Page 20 of 44
For the mapping from the ARP to the SPI, run the following command to configure the
user level corresponding to each ARP.
ADD UOPERUSERPRIORITY: 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,
CnOpIndex=0;
Configure the mapping from the service type and level of users to the SPI.
ADD UOPERSCHEDULEPRIOMAP: CnOpIndex=0, TrafficClass=INTERACTIVE,
UserPriority=SILVER, THPClass=High, SPI=5;
Run the SET UUSERGBR command to configure the GBR of the BE service.
ADD UOPERUSERGBR: CnOpIndex=0, TrafficClass=INTERACTIVE,
THPClass=High, BearType=HSPA, UserPriority=SILVER, UlGBR=D64,
DlGBR=D64;
Configure the DC measurement control.

Configure the GBP and PBR measurements for the cell.
MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=HSDPA_GBP_MEAS1&HSDPA_PBR_MEAS-1;
Set the basic measurement period to 200 ms.

SET ULDM: ChoiceRprtUnitForDlBasicMeas=TEN_MSEC,
TenMsecForDlBasicMeas=20;
Set the period of the HSPA GBP measurement and HSPA PBR measurement to 1s.
SET ULDM: ChoiceRprtUnitForHsdpaPwrMeas=TEN_MSEC,
TenMsecForHsdpaPwrMeas=100;
SET ULDM: ChoiceRprtUnitForHsdpaRateMeas=TEN_MSEC,
TenMsecForHsdpaPrvidRateMeas=100;
Configure the DC admission control.

The admission control switch for HSPA+ is the same as that for HSDPA. Run the
following command to enable the switch.
MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=HSDPA_UU_ADCTRL-1;
Enable the CE resource admission control for the cell.

SET UCACALGOSWITCH: CacSwitch=NODEB_CREDIT_CAC_SWITCH-1;
MOD UCELLALGOSWITCH: CellId=1, NBMCacAlgoSwitch=CRD_ADCTRL-1;
Configure the DC DRD.

Enable the DRD control switch for HSPA+ and the blind handover switch for the cells
with different frequencies but with the same coverage.
SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH1&DR_RAB_SING_DRD_SWITCH-1&DR_RAB_COMB_DRD_SWITCH-1;
ADD UINTERFREQNCELL: RNCId=1, CellId=1, NCellRncId=1, NCellId=2,
CIOOffset=0, SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0,
BlindHoFlag=TRUE, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;
2016-11-13
Page 21 of 44
Configure the DC load control.

Enable the switch for the HSPA state transition algorithm.
SET UCORRMALGOSWITCH: DraSwitch = DRA_PS_BE_STATE_TRANS_SWITCH-1&
DRA_PS_NON_BE_STATE_TRANS_SWITCH-1& DRA_HSDPA_STATE_TRANS_SWITCH-1&
DRA_HSUPA_STATE_TRANS_SWITCH-1;
Enable the switches for the load reshuffling, code resource reshuffling, and CE resource
reshuffling algorithms.
MOD UCELLALGOSWITCH: CellId=0, NBMLdcAlgoSwitch=UL_UU_LDR1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR-1;
NodeB
Set up two cells with adjacent frequencies but the same coverage. Pay attention to the
following points:
The UL/DL frequencies are adjacent ones with an interval of 25 MHz.
The two cells belong to the same site and sector, ensuring the same coverage.
The resources are loaded from the E board.
ADD LOCELL: LOCELL=1;

ADD LOCELL: LOCELL=2;
Configure the DC cell group. That is, set local cell 1 and local cell 2 to form a DC cell group.
ADD DUALCELLGRP: FIRSTLOCELL=1, SECONDLOCELL=2;
Constraints
The two cells that form a DC cell group must meet the following conditions:
2016-11-13
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.
Page 22 of 44
1. For the following parameters, check whether they are the recommended baseline parameters. If yes,
they do not need to be modified.
2. The following parameters are optional but related to the policies such as networking mode. Therefore,
you need to negotiate with network planning engineers for the operations.
Configure the HSDPA dynamic codes for the DC cell.

It is recommended that the dynamic codes of the NodeB be enabled.
SET MACHSPARA: LOCELL=1, DYNCODESW=OPEN;
SET MACHSPARA: LOCELL=2, DYNCODESW=OPEN;
Configure the DC scheduling algorithm.

The default scheduling algorithm (that is, the EPF scheduling algorithm) is
recommended.
SET MACHSPARA: LOCELL=1, SM=EPF;
SET MACHSPARA: LOCELL=2, SM=EPF;
Configure the DC flow control algorithm.

Currently, the default parameters for flow control are recommended. The flow control
policy is automatically set to DYNAMIC_BW_SHAPING or NO_BW_SHAPING
through the congestion detection mechanism of the NodeB.
SET HSDPAFLOWCTRLPARA: SWITCH=BW_SHAPING_ONOFF_TOGGLE;
Configure the DC power control.

For the power control configuration for the HS-SCCH channel, the default
parameters are recommended. Configure the HS-SCCH power control as CQI-based
adjustment. The offset relative to the initial power of PCPICH is 0 dB and the frame
error rate is 1%.
SET MACHSPARA: HSSCCHPWRCMINDCH=CQI, HSSCCHFERTRGTINDCH=10;
For the setting of the cell power margin, the default parameter (that is, 5%) is
recommended.
SET MACHSPARA: PWRMGN=5;
4.3 Optimization for the DC Throughput Rate

4.3.1 RNC
Cell Power Distribution ratio: 43/31
MOD UCELL: CellId=100, MaxTxPower=430, PCPICHPower=310;
2016-11-13
Page 23 of 44
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;
2016-11-13
Page 24 of 44
NODEB: SET MACHSPARA: DYNCODESW=OPEN;
4.3.2 NodeB
Power Margin=0%
SET MACHSPARA: PWRMGN=0;
2016-11-13
Page 25 of 44
4.4 Examples of DC Field Verification

4.4.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.
2016-11-13
Page 26 of 44
4.4.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.3.
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.
2016-11-13
List of Items to Be
Checked Before Field
Test
Mandator
y/Option
al
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
Page 27 of 44
List of Items to Be
Checked Before Field
Test
Mandator
y/Option
al
Owner
Remarks
External data network adapter

(1 PCS)
Mandatory
Test personnel
Postpaid SIM card (1 PCS)
Mandatory
Test personnel
Prevent network
access failure due
to arrears
Test data card (used for basic

service verification: DPA cat8
data card)
Mandatory
Test personnel
Responsibility of
test personnel
LMT version matching the

NODEB
Mandatory
Test personnel
Key for the site
Optional
License for field test in Spain
Mandatory
Field test vehicle with vehicle

mounted power supply (1
PCS)
Mandatory
Electric torch
Optional
Screwdriver and insulating

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.
2016-11-13
Page 28 of 44
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.
2016-11-13
Page 29 of 44
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.
2016-11-13
Page 30 of 44
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:
2016-11-13
Page 31 of 44
6.1.2 TestPing
On the FTP server, perform the settings for TestPing to meet the requirement for the
throughput rate of 42 Mbit/s, as shown in the following figure. The calculation formula is as
follows:
1400 x 8 / (5 / 30) = 67.2 Mbit/s
Data configuration is not mandatory but the data amount must be sufficient. You need to
understand the parameter calculation methods.
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
2016-11-13
Page 32 of 44
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.
2016-11-13
Page 33 of 44
Uplink Service
To locate the uplink service, see the reference settings in the following figures.
2016-11-13
Page 34 of 44
2016-11-13
Page 35 of 44
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.
The QXDM software is used in the same way as the earlier version. Currently, however,
certain observation points are displayed improperly.
2016-11-13
Page 36 of 44
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: DC-HSDPA Service
Throughput in the Center of Cell
Global ID
DC-HSDPA A1-0601
Priority
High1
Objective
Theoretically, DC-HSDPA with downlink 64QAM modulation method can provide a peak
rate of 42 Mbit/s for a single UE. It enables the UEs with good channel conditions to
download data at higher rates, improves user experience, and increases the competitiveness
of the telecom operator.
The case verifies the Cat 24 UE's downlink throughput of a DC-HSDPA with 64QAM
Service.
Network diagram
Standard networking of acceptance, for details of standard networking, refer to Appendix 1.
(NE: RNC1, NodeB1, CELL_A11, CELL_A12 and they are DC cell group)
2016-11-13
Page 37 of 44
Prerequisites
WCDMA system is in normal operation.
DC-HSDPA CAT24 UE is subscribed to the interactive service at 5,760 kbit/s (UL) and
43,200 kbit/s (DL) on the HLR.
CELL_A11 and CELL_A12 support HSUPA, 64QAM and DC-HSDPA function.
UE is in idle mode and camps on the CELL_A11.
Set the allocation mode of HS-PDSCH code to automatic on RNC1 as follows:
MOD UCELLHSDPA: CellId=<CELL_A11>, AllocCodeMode=Automatic,
HsPdschMaxCodeNum=15;
Set the allocation mode of HS-PDSCH code to automatic on NodeB1 as follows:
SET MACHSPARA: DYNCODESW=OPEN;
The [DL Throughput Bandwidth] of connection performance monitoring is created in
the BSC6900 Local Maintenance Terminal of RNC1.
The corresponding Uu, Iub, Iu tracing are created in the BSC6900 Local Maintenance
Terminal of RNC1.
Procedure
Expected result
UE initiates PS Dial-up.
The DC-HSDPA Service with 64QAM setup

successfully.
Through the Uu tracing in RNC1, it can be
observed that RNC1 sends the RRC_RB_SETUP
message to UE.
Through the "rab-InformationSetupList" IE in
RRC_RB_SETUP message, it can be observed
that "ul-TrCH-Type" is "e-dch" and "dlTransportChannel-Type" is "hsdsch".
Through the "dl-HSPDSCH-Information" IE in
that "dl-64QAM-Configured: true".
It can be observed that dlSecondaryCellInfoFDD IE is included in the
RRC_RB_SETUP message.
Through the "dl-SecondaryCellInfoFDD " IE in
that "dl-64QAM-Configured: true".
2016-11-13
UE starts download.
The download data transmission is normal.
UE releases the service.
The service is released successfully.
Page 38 of 44
Remarks
Check RNC license "HSPA + Downlink 42 Mbps Per User" is "ON" on RNC1
through the MML command: DSP LICENSE.
Local Cell Number Support DL 64QAM and DC-HSDPA on NodeB through the MML
command: DSP LICENSE.
Logical Cell support DL 64QAM and DC-HSDPA through the MML command: DSP
UCELLCHK.
Before the verification, backup the configuration.
Related protocol specifications are as follows:
3GPP TS 25.211: Physical channels and mapping of transport channels onto physical
channels (FDD)
3GPP TS 25.306: UE Radio Access capabilities
3GPP TS 25.321: Medium Access Control (MAC) protocol specification
3GPP TS 25.331: Radio Resource Control (RRC) Protocol Specification
Related Huawei feature specifications are as follows:
WRFD-010696 DC-HSDPA
WRFD-010683 Downlink 64QAM
Radio Bearers Parameter Description
Operation Guide
Check the HSDPA and HSUPA function of the two cells is active through the MML
command: DSP UCELL.
Check the 64QAM function, downlink L2 Enhanced function and DC-HSDPA
function are active through the MML command: LST UCORRMALGOSWITCH.
Check the 64QAM function, downlink L2 Enhanced function and DC-HSDPA
function of the two cells are active through the MML command: LST
UCELLALGOSWITCH.
Check the code resource of cell is enough through the MML command: LST
UCELLHSDPA.
Check UE supports DC-HSDPA function through the "hsdsch-physical-layercategory-ext2" IE in the RRC_RRC_CONNECT_SETUP_CMP message.
Check "DL BE traffic threshold on HSDPA" is default value on RNC1 through the
MML command: LST UFRCCHLTYPEPARA.
In lab tests, the average downlink bit rate of DC-HSDPA CAT24 service normally can
reach about 37.0 Mbit/s.
After the verification, restore the configuration.
7.1.2 Preparations for the Test

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.
2016-11-13
Page 39 of 44
The test terminal must support Cat24. The subscriber definition rates of the SIM card are
5760 Kbit/s (uplink) and 43200 Kbit/s (downlink).
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.

On the RNC, run the following command: MOD UCELLHSDPA:
CellId=<CELL_A11>, AllocCodeMode=Automatic, HsPdschMaxCodeNum=15;
On the NodeB, run the following command: SET MACHSPARA:
DYNCODESW=OPEN;
2.
Enable the trace on the Uu interface (as shown in the following figure).
Step 1 Log in to the WebLMT. 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 WebLMT. 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.
2016-11-13
Page 40 of 44
Step 3 In the Parameter Setting message box, select DL Throughout Bandwidth.

Step 4 Fill in the IMSI.
Step 5 Click Submit to start the monitoring process.
4.
Use the terminal to initiate the PS service. It is recommended that the terminal be
connected to a stable FTP service 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 dl64QAM-Configured: true are displayed, it indicates that DC is successfully set up.
1.
Save the monitoring result file and message trace result.
2.
Restore the test environment.
The operation procedure for the test case (DC-HSDPA Service Throughput in the Center of
Cell) is complete.
2016-11-13
Page 41 of 44
FAQs
8.1 Decrease of the Throughput Rate When the

Tcells of the Two Cells Configured on a Single
RRU Are the Same
This problem is inherent for the RRU. Theoretically, the RF module should ensure highlinearity 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.
8.2 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
2016-11-13
Page 42 of 44
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).
8.3 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.
8.4 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.
2016-11-13
Page 43 of 44
8.5 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.
2016-11-13
Page 44 of 44

RAN12 0 DC HSDPA Feature Acceptance Guide 20100802 V1 0 A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RAN12 0 DC HSDPA Feature Acceptance Guide 20100802 V1 0 A

Uploaded by

Copyright:

Available Formats

Product name

RAN12.0 DC-HSDPA Feature Acceptance Guide

Gao Peng (employee

Huawei Technologies Co., Ltd.

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

Gao Peng (employee

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

7 Guide to Test Cases.....................................................................35

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

The WCDMA protocol of the R8 version introduces features such as DC and

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

Improving the service performance for end users

Implementing HSPA+ by upgrading the existing WCDMA network

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

General Process of the DCHSDPA Deployment

Figure 1.1 General process of the DC-HSDPA deployment

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Huawei Technologies Proprietary

Confidentiality Level: Internal

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

Preparations for the DC-HSDPA

Control on the RNC side

Control on the NODEB side.

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

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

Figure 1.2 RNC license

NodeB License: DSP LICENSE, unlimited.

3.2 Preparations for the Environment

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

QPSK, 16QAM, 64QAM

Huawei Technologies Proprietary

RAN12.0 DC-HSDPA Feature Acceptance Guide

Confidentiality Level: Internal

3.3 Networking Mode

3.4 Software Version

Huawei Technologies Proprietary