Dual Carrier Multi Carrier Hsdpa Ran 13 Huawei PDF

WCDMA RAN
DC-HSDPA
Feature Parameter Description
Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other
trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made between
Huawei and the customer. All or partial products, services and features described in this document may
not be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all
statements, information, and recommendations in this document are provided "AS IS" without warranties,
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd
WCDMA RAN
DC-HSDPA Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview .....................................................................................................................................2-1
3 Basic Principle...........................................................................................................................3-1
3.1 Overview ....................................................................................................................................... 3-1
3.2 Cell Configuration .......................................................................................................................... 3-1
3.3 Channel Mapping .......................................................................................................................... 3-3
3.4 UE Categories ............................................................................................................................... 3-3
3.5 NodeB MAC-ehs ........................................................................................................................... 3-4
3.6 Impact on Interfaces ...................................................................................................................... 3-5
4 Technical Description ..............................................................................................................4-1

4.1 Overview ....................................................................................................................................... 4-1
4.2 Radio Bearers ............................................................................................................................... 4-1
4.3 State Transition.............................................................................................................................. 4-2
4.4 Mobility Management .................................................................................................................... 4-2
4.5 Load Control .................................................................................................................................. 4-4
4.5.1 RAB DRD ............................................................................................................................. 4-4
4.5.2 Call Admission Control ......................................................................................................... 4-5
4.5.3 Queuing and Preemption...................................................................................................... 4-6
4.5.4 Load Reshuffling and Overload Control ............................................................................... 4-7
4.6 Scheduling..................................................................................................................................... 4-7
4.7 Activating or Deactivating Secondary Cell .................................................................................... 4-7
5 Engineering Guidelines...........................................................................................................5-1
5.1 DC-HSDPA .................................................................................................................................... 5-1
5.1.1 When to Use DC-HSDPA ..................................................................................................... 5-1
5.1.2 Factors to Consider During Feature Deployment ................................................................. 5-1
5.1.3 Recommended Settings for Key Parameters ....................................................................... 5-1
5.1.4 Feature Monitoring ............................................................................................................... 5-2
5.2 Activating or Deactivating Secondary Cell .................................................................................... 5-2
6 Parameters .................................................................................................................................6-1
7 Counters ......................................................................................................................................7-1
8 Glossary ......................................................................................................................................8-1
9 Reference Documents .............................................................................................................9-1
Issue 02 (2011-06-30) Huawei Proprietary and Confidential ii

WCDMA RAN
DC-HSDPA 1 Introduction
1 Introduction
1.1 Scope
This document describes the feature Dual-Carrier High Speed Downlink Packet Access (WRFD-010696
DC-HSDPA).
Before reading this document, you are advised to read the HSDPA Feature Parameter Description.
1.2 Intended Audience

This document is intended for:
 Personnel who are familiar with WCDMA basics
 Personnel who need to understand DC-HSDPA
 Personnel who work with Huawei products
1.3 Change History

This section provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:
 Feature change: refers to the change in the DC-HSDPA feature.
 Editorial change: refers to the change in wording or the addition of the information that was not
described in the earlier version.
Document Issues
The document issues are as follows:
 02 (2011-06-30)
 01 (2011-04-30)
 Draft B (2011-03-30)
 Draft A (2010-12-30)
02 (2011-06-30)
This is the document for the second commercial release of RAN13.0.
Compared with issue 01 (2011-04-30) of RAN13.0, this issue has the following changes.
Change Type Change Description Parameter Change

Feature change None. None.
Editorial change The engineering guideline about DC-HSDPA is None.
added. For details, see 5.1 “DC-HSDPA.”
The engineering guideline about activating or None.
deactivating secondary cell moved from 4.7
“Activating or Deactivating Secondary Cell” to 5.2
“Activating or Deactivating Secondary Cell.”
Issue 02 (2011-06-30) Huawei Proprietary and Confidential 1-1

WCDMA RAN
DC-HSDPA 1 Introduction
01 (2011-04-30)
This is the document for the first commercial release of RAN13.0.
Compared with issue Draft B (2011-03-30) of RAN13.0, this issue has no change.
Draft B (2011-03-30)
This is the draft of the document for RAN13.0.
Compared with issue Draft A (2010-12-30) of RAN13.0, this issue optimizes the information about
activating or deactivating secondary cell. For details, see 4.7 “Activating or Deactivating Secondary
Cell.”
Draft A (2010-12-30)
This is the draft of the document for RAN13.0.
Compared with issue 01 (2010-03-30) of RAN12.0, this issue adds the information about activating or
deactivating secondary cell. For details, see 4.7 “Activating or Deactivating Secondary Cell.”

WCDMA RAN
DC-HSDPA 2 Overview
2 Overview
Similar to Long Term Evolution (LTE), the HSPA technology is also influenced by the multi-carrier
aggregations. The performance and throughput of HSPA can be improved by using more bandwidth
provided by multi-carriers. The throughput of end users can be double or more as compared to
single-carrier HSPA.
In 3GPP Release 8 or earlier, only a single carrier can be used for the HSDPA transmission of a UE. The
single carrier HSDPA is hereafter referred to as SC-HSDPA.
The first phase of Multi-Carrier HSPA (MC-HSPA) based on 3GPP R8 Technical Specifications (TSs)
uses two consecutive carriers in the downlink to transmit data for one subscriber, which is named Dual
Carrier HSDPA (DC-HSDPA). 3GPP Release or later specifies the use of more than two carriers for a
single subscriber without the restrictions on the use of the same frequency band.
Figure 2-1 shows the 3GPP evolution of MC-HSDPA.
Figure 2-1 3GPP evolution of MC-HSDPA
The requirements of DC-HSDPA are listed in Table 2-1.

Table 2-1 Requirements of the DC-HSDPA
Item Requirement
CN The CN needs to support the downlink peak rate of 42 Mbit/s provided by downlink DC-HSDPA
with 64QAM.
RNC The RNC needs to support downlink enhanced L2.
The RNC provides the radio bearer scheme for DC-HSDPA.
NodeB DC-HSDPA requires NodeB to support MAC-ehs. A single MAC-ehs entity supports HS-DSCH
transmission in more than one cell served by the same Node-B (FDD only).
UE The UE can monitor a maximum of six HS-SCCHs in the two cells of DC-HSDPA. In each cell,
the UE can monitor a maximum of three HS-SCCHs at the same time.
In 3GPP Release 8, HS-DSCH UE categories 21, 22, 23, and 24 are added to support
DC-HSDPA. In 3GPP Release 9 or later, more HS-DSCH UE categories support DC-HSDPA.

WCDMA RAN
DC-HSDPA 3 Basic Principle
3 Basic Principle
3.1 Overview
DC-HSDPA allows a UE to set up HSDPA connections with two inter-frequency synchronous cells that
have the same coverage. In the downlink, the UE can receive different data through HS-DSCHs from the
two cells simultaneously. In the uplink, however, the UE sends data only through its primary cell.
Figure 3-1 DC-HSDPA principle
The two cells (primary cell and secondary cell) of DC-HSDPA follow the following restrictions:
 The two cells belong to the same sector of a NodeB and are inter-frequency same-coverage cells.
 The two cells are in the same downlink resource group of a NodeB.
 The two cells operate on adjacent carriers with a frequency spacing less than or equal to 5 MHz in the
same frequency band.
 The two cells have the same timing (Tcell).
 The two cells support HSDPA and enhanced L2.
 The two cells belong to the same operator.
 The dual cell transmission only applies to HSDPA physical channels.
The uplink of DC-HSDPA UE is in only the primary cell but not in the secondary cell.
DC-HSDPA improves the throughput and QoS of end users in the whole cell area even on the cell edges.
Theoretically, DC-HSDPA with 64QAM can provide a peak rate of 42 Mbit/s in the downlink. This rate
doubles the peak rate provided by only 64QAM.
3.2 Cell Configuration

DC-HSDPA cell group consists of two cells: primary cell and secondary cell.
From the UE perspective:

WCDMA RAN
 Primary cell (also called anchor cell) carries all the types of channel for a UE. Each UE has only one
primary cell.
 Secondary cell (also called supplementary cell) carries only three types of downlink (DL) channel for a
UE. Each UE has only one secondary cell.
The three types of DL channel are as follows:
− High-speed shared control channel (HS-SCCH)
− High-speed physical downlink shared channel (HS-PDSCH)
− Primary common pilot channel (P-CPICH)
Figure 3-2 shows the physical channels involved in DC-HSDPA for a UE.
Figure 3-2 Cell configuration from the UE perspective
From the RAN perspective, both the cells can work as primary cell and secondary cell. The two cells can
be deployed equivalently with the same configuration, as shown in Figure 3-3.
Figure 3-3 Equivalent deployment of primary cell and secondary cell
In equivalent deployment of primary and secondary cells, the RNC selects the primary cell for UEs
based on the load and radio bearer scheme. Both cells can work independently for non-DC-HSDPA UEs
or legacy HSDPA UEs.
Alternatively, the primary cell is configured with all channels whereas the secondary cell is configured
with only HS-DSCH and P-CPICH. The secondary cell cannot work independently. This is called
non-equivalent deployment. Non-equivalent deployment is not supported.

WCDMA RAN
3.3 Channel Mapping

Overview
Figure 3-4 Channel mapping of DC-HSDPA
A DC-HSDPA UE receives two HS-DSCH transport channels from two cells of the same NodeB. Each
HS-DSCH is mapped to one HS-SCCH and several HS-PDSCH physical channels.
The uplink DCH or E-DCH of DC-HSDPA is carried only on the primary cell.
All dedicated physical control channels DPCCH and DPCH/F-DPCH in the uplink and downlink are
carried on the primary cell.
HS-SCCH
In 3GPP Release 8 or earlier, a UE can monitor a maximum of four HS-SCCHs at the same time,
according to 3GPP TS 25.331. In DC-HSDPA cell group, the HS-SCCHs on the primary cell are
independent of those on the secondary cell. A UE can monitor a maximum of six HS-SCCHs at the same
time. In each cell, the UE can monitor a maximum of three HS-SCCHs at the same time.
There are three types of HS-SCCH, type 1 for common use, type 2 for HS-SCCH Less Operation, and
type 3 for MIMO. DC-HSDPA uses only HS-SCCH type 1. DC-HSDPA with HS-SCCH Less Operation
uses HS-SCCH type 2.
HS-SCCH Less Operation applies only to the primary cell.
HS-DPCCH
The UE gives feedback on the CQIs and HARQ ACK/NACK about two cells on the HS-DPCCH channel
to the primary cell. The HS-DPCCH uses a new frame format that enables it to carry CQI and HARQ
ACK/NACK information of the two cells in a Transmission Time Interval (TTI).
3.4 UE Categories
In 3GPP Release 8, HS-DSCH UE categories 21, 22, 23, and 24 are added to support DC-HSDPA, as
listed in Table 3-1 (similar to that in 3GPP TS 25.306). In 3GPP Release 9 or later, more HS-DSCH UE
categories support DC-HSDPA.

WCDMA RAN
Table 3-1 FDD HS-DSCH physical layer categories 21 to 24

HS-DSCH Maximu Minimum Maximum Total Supported Supported Suppo
Category m Inter-TTI Number of Number Modulatio Modulation rted
Number Interval Bits of an of Soft n Without Simultaneo Modul
of HS-DSCH Channel MIMO us with ation
HS-DSCH Transport Bits Operation MIMO with
Codes Block or Dual Operation Dual
Received Received Cell and Cell
Within Operation Without Opera
an HS-DSCH Dual Cell tion
TTI Operation
Category 21 15 1 23370 345600 QPSK,

16QA
Category 22 15 1 27952 345600 M
Category 23 15 1 35280 518400 - - QPSK,
16QA
Category 24 15 1 42192 518400 M,64Q
AM
The requirements for the UEs of different HS-DSCH categories when DC-HSDPA is not configured are
as follows:
 The UE of HS-DSCH category 21 needs to support at least one of the HS-DSCH categories 9, 10, 13,
14, 15, 16, 17, and 18.
and 18.
18, 19, and 20.
 The UE of HS-DSCH category 24 needs to support at least one of the HS-DSCH categories 14, 18,
and 20.
The peak rate can reach 42.192 Mbit/s (= 2 x TB_Size/TTI = 2 x 42192/2) at the MAC layer, supported
by the CN.
The DC-HSDPA UEs and MIMO UEs can co-exist in the same cell, but one UE cannot use MIMO and
DC-HSDPA together.
3.5 NodeB MAC-ehs

DC-HSDPA requires the NodeB to support MAC-ehs. A single MAC-ehs entity supports HS-DSCH
transmission in more than one cell served by the same NodeB (FDD only). Queues of a DC-HSDPA UE
are common for the two cells. The scheduler in the NodeB arranges the data transmission of queues on
the two cells. DC-HSDPA transmissions can be regarded as independent transmissions over two
HS-DSCH channels. There will be a separate HARQ entity on each HS-DSCH channel, that is, one
HARQ process per TTI for single carrier transmission and two HARQ processes per TTI for dual carrier
transmission.
MAC-ehs selects Transport Format and Resource Combination (TFRC) for the MAC-ehs Protocol Data
Units (PDUs) of each cell independently based on the available resources of the cells and the CQI
reported by the UE.

WCDMA RAN
Figure 3-5 MAC-ehs architecture
In a NodeB, two MAC-ehs PDUs can be scheduled at the same time. Figure 3-6 shows an example of
traffic flow to a DC-HSDPA UE.
Figure 3-6 Example of traffic flow to a DC-HSDPA UE
3.6 Impact on Interfaces

To support DC-HSDPA, new Information Elements (IEs) are added to signaling messages.
UEs and cells can report their capacity of DC-HSDPA to the RNC through the Iub and Uu interfaces. The
RNC instructs cells to set up or reconfigure radio links with DC-HSDPA through the Iub interface. The
RNC instructs UEs to set up or reconfigure radio bearers with DC-HSDPA through the Uu interface.

WCDMA RAN
Impact on Iub
When a cell receives the AUDIT REQUEST message or when a new cell is set up or a cell capability is
changed, the NodeB reports the cell capability to the RNC in Audit Response message or Resource
State Indication message
 When a cell supports DC-HSDPA, the NodeB sets the Multi Cell Capability Info IE to Multi Cell
Capable for the cell in Audit Response and sends the message to the RNC.
 If the cell is a primary serving cell, all the possible secondary serving cells in the same sector must be
listed in the Possible Secondary Cell List IE.
When the RNC instructs a cell to set up a radio link with DC-HSDPA, the information of the secondary
serving cell is added to the Radio Link Setup procedure or Radio Link Addition procedure.
The Additional HS Cell Information RL Setup IE is added to the Radio Link Setup
Request/Response/Failure messages and Radio Link Addition Request/Response/Failure messages to
indicate the usage of DC-HSDPA and associated parameters.
Impact on Uu
In the RRC CONNECTION REQUEST message, the Multi cell support IE is added to indicate the UE
capability of supporting multiple cells.
In the RRC Connection Setup Complete and UE Capability Information message, the Physical Channel
Capability IE is extended to indicate the UE capability of DC-HSDPA.
The Downlink secondary cell info FDD IE in the following signaling messages indicates the usage of
secondary serving cell and related parameters:
 RRC CONNECTION SETUP
 ACTIVE SET UPDATE
 CELL UPDATE CONFIRM
 PHYSICAL CHANNEL RECONFIGURATION
 TRANSPORT CHANNEL RECONFIGURATION
 RADIO BEARER RECONFIGURATION
 RADIO BEARER RELEASE
 RADIO BEARER SETUP

WCDMA RAN
DC-HSDPA 4 Technical Description
4 Technical Description
4.1 Overview
This document describes only the functions that are different from those of SC-HSDPA.
These functions are as follows:
 Radio Bearers
 State transition
 Mobility management
 Load control
 Scheduling
For details about other functions, see the HSDPA Feature Parameter Description.
4.2 Radio Bearers

When the downlink transport channel HS-DSCH is selected for streaming or BE services or combined
service with streaming or BE, DC-HSDPA is applied. When there is only a CS service, PS conversational
service, IMS signaling, or SRB signaling, DC-HSDPA is not applied because of small traffic volume and
low transmission delay.
Before using DC-HSDPA for a service, you need to configure the feature on both RNC and NodeB.
 On the NodeB:
− Youneed to set up two cells to support DC-HSDPA. The two cells operate on adjacent carriers with a
frequency spacing of 5 MHz or smaller in the same frequency band. The two carriers are specified by
frequency channel numbers (DLFREQ/ ULFREQ).
− Thetwo cells are configured as a DC-HSDPA group (ADD DUALCELLGRP). The two cells are
specified by the parameters (FIRSTLOCELL, SECONDLOCELL).
 On the RNC:
− You
need to turn on the switches CfgSwitch: CFG_HSDPA_DC_SWITCH and HspaPlusSwitch:
DC_HSDPA.
− The
preferred feature should be set to DC_HSDPA in the parameter
MIMO64QAMorDcHSDPASwitch.
− The timing (Tcell) of the two cells needs to be set to the same value.
64QAM can be enabled in one or both cells in the DC-HSDPA cell group. DC-HSDPA and 64QAM can
be used at the same time.
The Continuous Packet Connectivity (CPC) function can be enabled in the DC-HSDPA cells with the
following limitations:
 CPC DTX is applicable to primary cell only because there will be no uplink control channel for the
DC-HSDPA UE on secondary cell
 CPC HS-SCCH Less Operation is applicable to primary cell only and is not applicable to secondary
cell.
 CPC DRX for a DC-HSDPA UE on two carriers is similar to that for a UE on a single cell.
HSPA+ based on 3GPP Release 8 is optional for the operators to select DC-HSDPA or MIMO. However,
in later 3GPP releases, the DC-HSDPA and MIMO should be deployed together.

WCDMA RAN
 In RAN12.0, a cell is enabled with the DC-HSDPA and MIMO functions at the same time but a UE can
use only one of the functions.
 In RAN12.0, the two cells in a DC-HSDPA cell group cannot support MIMO at the same time. Only one
of them can support MIMO.
 In RAN13.0, a cell is enabled with the DC-HSDPA and MIMO functions at the same time and both cells
in a DC-HSDPA cell group can support MIMO at the same time.
DC-HSDPA with 64QAM can reach a peak rate of 42 Mbit/s.
The Transmission Control Protocol (TCP) is widely used in data transmission. When a file is being
downloaded, the TCP acknowledgement is sent in the uplink. The higher the rate of download is, the
larger the bandwidth is required in the uplink. If the download rate reaches up to 42 Mbit/s, the uplink
rate of TCP acknowledgement is much higher than 384 kbit/s, the highest supported by the DCH.
HSUPA bearer is required to provide high bandwidth in the uplink to transmit TCP acknowledgement
without delay. The downlink rate of 42 Mbit/s per user can be supported only when HSUPA is used.
4.3 State Transition

DC-HSDPA state transition, based on the SC-HSDPA state transition strategy, considers the primary cell
during state transition.
Assume that a DC-HSDPA UE preferentially selects F2 as the primary cell. Then, the DC-HSDPA state
transition strategy is as follows:
To move from the CELL_FACH, CELL_PCH, or URA_PCH state to the CELL_DCH state:
1. If the UE is allowed to access the F2 cell, the UE moves to the CELL_DCH state in this cell.
2. If the UE is not allowed to access the F2 cell, the UE attempts to access other DC-HSDPA cells in a
DRD candidate cell set.
3. If the UE is allowed to access one of the candidate cells, the UE moves to the CELL_DCH state in
this cell.
4. If the UE is not allowed to access any of the candidate cells, the UE performs the following
operations:
− If the UL service is carried on the HSUPA channel, the UL falls back to DCH:
If the UE is allowed to access the cell, the UE moves to the CELL_DCH state.
If the UE is not allowed to access the cell, the state transition fails and the UE stays in the original
state.
− If the UL service is carried on the DCH, the state transition fails and the UE stays in the original state.
To move from the CELL_DCH state to the CELL_FACH state, the DC-HSDPA UE performs the same
state transition as an SC-HSDPA UE in the primary-carrier cell.
To move from the CELL_FACH state to the CELL_PCH state, the DC-HSDPA UE performs the same
state transition as an SC-HSDPA UE because the DC-HSDPA UE in the CELL_FACH state can use only
one frequency.
4.4 Mobility Management

The introduction of DC-HSDPA has no impact on handover measurement triggering and handover
decision processes. During a handover, however, the RNC needs to decide whether DC-HSDPA is used
after the handover if the target cell supports DC-HSDPA, or whether non-DC-HSDPA is used after the
handover if the target cell does not support DC-HSDPA.
This section describes only the mobility management of DC-HSDPA. For other information about
handover, see the Handover Feature Parameter Description.

WCDMA RAN
Measurement Control
The active set is maintained for primary carriers only. For DC-HSDPA intra-frequency handover, only the
signal quality of the primary-carrier cell and its neighboring cells needs to be measured.
For DC-HSDPA inter-frequency handover, except for the signal quality of the primary-carrier cell and its
neighboring cells, the signal quality of the secondary-carrier cell also needs to be measured like an
inter-frequency neighboring cell.
If the UE has a dual-frequency receiver, it can perform inter-frequency measurement without starting the
compressed mode if all of the following conditions are met:
 The CmpSwitch: CMP_UU_ADJACENT_FREQ_CM_SWITCH is turned on.
 The value of the IE "Adjacent frequency measurements without compressed mode" reported by the
UE is TRUE.
 For the UE that supports DC-HSDPA:
− If
the UE has a DC-HSDPA service, all the cells involved in inter-frequency measurement are at the
same frequency as the secondary carrier.
− If
the UE does not have a DC-HSDPA service, all the cells involved in inter-frequency measurement
are at the same frequency, with a 5 MHz spacing from the current cell but within the same band as
the current cell.
Handover Between DC-HSDPA Cells

When receiving a measurement report indicating that the signal quality of a DC-HSDPA cell is better than
that of the serving cell (a DC-HSDPA cell), the RNC decides whether to perform a DC-HSDPA handover
to the target cell:
 If the admission to the target cell is allowed and the radio link configuration is successful, the RNC
performs the handover.
 If the admission to the target cell is allowed but the radio link configuration is unsuccessful, the RNC
reconfigures the service on SC-HSDPA and then performs an SC-HSDPA handover.
 If the admission to the target cell is not allowed, the RNC reconfigures the service on the DCH and
performs a DCH handover:
− If the DCH handover is allowed, the RNC performs the handover.
− Otherwise, the RNC does not perform the handover.
Handover from a DC-HSDPA Cell to a Non-DC-HSDPA Cell

When receiving a measurement report indicating that the signal quality of a non-DC-HSDPA cell is better
than that of the serving cell (a DC-HSDPA cell), the RNC reconfigures the service to DCH or HSDPA and
continues to perform the handover procedure.
Handover from a Non-DC-HSDPA Cell to a DC-HSDPA Cell

When receiving a measurement report indicating that the signal quality of a DC-HSDPA cell is better than
that of the serving cell (a non-HSDPA cell), the RNC performs a handover after which the HSPA+
technologies supported by both the source cell and the target cell are used in the target cell. If such
HSPA+ technologies are ranked lower than some HSPA+ technologies supported by both the target cell
and the UE, the ChannelRetryHoTimerLen timer is started after the handover. When the timer expires,
the RNC tries to reconfigure the traffic radio bearer (TRB) and signaling radio bearer (SRB) to enable
them to support the higher-ranked HSPA+ technologies.

WCDMA RAN
4.5 Load Control

4.5.1 RAB DRD
During the RB setup or state transition from CELL_FACH to CELL_DCH, the RNC makes DRDs to
select a DC-HSDPA cell group and then select a primary-carrier cell for the UE.
For details about DRD, see Directed Retry Decision Feature Parameter Description.
DRD Procedure
The procedure is as follows:
1. The RNC selects a set of candidate cells that meet the DRD quality requirements.
For details, see the Directed Retry Decision Feature Parameter Description.
2. The RNC selects a DC-HSDPA cell group according to the HSPA+ technological satisfaction.
The RNC selects a cell with the highest priority as the target cell according to the HSPA+ technological
satisfaction. Based on this cell, the RNC searches for the corresponding DC-HSPA cell group and
takes this group as the DC-HSPA cell group, and go to step 4. If there are multiple DC-HSPA cell
groups with the same HSPA+ technological satisfaction, the RNC performs step 3.
3. The RNC selects a DC-HSDPA cell group as follows:
 If the parameter ServiceDiffDrdSwitch is on, the RNC selects a group with the highest service
priority.
For details, see section "Cell Group Selection Based on Service Priorities."
 If there are multiple DC-HSDPA cell groups with the same highest service priority, the RNC selects a
group based on DL load balancing between these groups.
4. The RNC selects a primary-carrier cell from the DC-HSDPA cell group as follows:
The RNC selects a primary-carrier according to HSPA+ technological satisfaction and cell service
priority. If all the HSPA+ technological satisfaction, cell service priority and downlink load of the two
cells are the same, the RNC performs the following steps:
a) If the ULLdbDRDSwitchDcHSDPA switch is turned on, the RNC selects a primary-carrier cell
based on UL load balancing between the two cells. For details, see section "Cell Selection Based on
UL Load."
b) If the ULLdbDRDSwitchDcHSDPA switch is turned off, the RNC selects the cell randomly.
5. If the directed retry fails, the RNC repeats the RAB DRD procedure until the procedure is performed
for all the candidate cell groups.
Cell Group Selection Based on Service Priorities

If different DC-HSDPA cell groups support the same HSPA+ technology, these groups are ranked by
service priority.
The service priority of a DC-HSDPA cell group is determined by the highest service priority of the two
cells in the group.
Table 4-1 lists the reference service priorities for different service bearers.
Table 4-1 Reference service priorities
UL and DL Service Bearers Reference Service Priority
DCH and DCH DCH service priority
DCH and HSDPA HSDPA service priority

WCDMA RAN
DCH and DC-HSDPA HSDPA service priority

HSUPA and DCH HSUPA service priority
HSUPA and HSDPA HSDPA service priority and then HSUPA service priority
Note:
HSUPA and DC-HSDPA
The HSDPA service priority is used first for the ranking. If the HSDPA service
priority is not enough for the ranking, the HSUPA service priority is used.
Cell Selection Based on UL Load

If the ULLdbDRDSwitchDcHSDPA switch is turned on, the RNC determines the primary-carrier cell
based on UL load balancing between the two cells.
If the current serving cell is not in the target DC-HSDPA cell group, the RNC selects a primary cell with
lower uplink load. Otherwise, the RNC checks whether the remaining UL load resource of the serving
cell is lower than or equal to the value of ULLdbDRDLoadRemainThdDCHSDPA:
 If the remaining UL load is above the threshold, the RNC selects the serving cell as the primary-carrier
cell because its UL load is lower.
 If the remaining UL load is below the threshold, the RNC calculates the difference between the UL load
margin of the serving cell and that of the target cell. Then,
− If
the difference is greater than the value of ULLdbDRDOffsetDcHSDPA, the RNC selects the target
cell as the primary-carrier cell because its UL load is lower.
− Otherwise, the RNC selects the serving cell as the primary-carrier cell.
4.5.2 Call Admission Control

Overview
In terms of Call Admission Control (CAC) based on the code resource, CE resource, or Iub resource,
DC-HSDPA CAC is not changed, compared with SC-HSDPA CAC.
In terms of CAC based on the DL power or equivalent number of users (ENU), DC-HSDPA CAC is
changed, that is, the resources of the DC-HSDPA cell group need to be considered.
CAC Based on the DL Power

Figure 4-1 shows the resource allocation in the two cells of a DC-HSDPA cell group. In this figure, the DL
power is taken as an example.

WCDMA RAN
Figure 4-1 DL power of a DC-HSDPA cell group
The variables in Figure 4-1 are described as follows:

 Pmax: maximum DL power of a cell
 Pnon-HSPA: DL power used for non-HSPA UEs in a cell
 GBPSC-H: DL power required by the HS-PDSCHs to provide GBRs for SC-HSDPA UEs in a cell.
 GBPDC-H: DL power required by the HS-PDSCHs to provide GBRs for the DC-HSDPA UEs in the
DC-HSDPA cell group.
For a DC-HSDPA UE, the RNC performs CAC based on the total DL power margin of the DC-HSDPA cell
group because the UE can use the DL power margin of any of the two cells after the admission.
For a non-DC-HSDPA UE, the RNC performs CAC based on the total DL power of the serving cell minus
the DL power used for the existing non-DC-HSDPA UEs in this cell. If the admission is successful, the
RNC continues to perform the CAC based on the total DL power margin of the DC-HSDPA cell group.
CAC Based on the ENU

The CAC based on the Equivalent Number of Users (ENU) is similar to CAC based on the DL power.
For a DC-HSDPA UE, the RNC performs CAC based on the total ENU of the DC-HSDPA cell group.
For a non-DC-HSDPA UE, the RNC first performs CAC based on the ENU of the serving cell. If the
admission is successful, the RNC then continues to perform the CAC based on the ENU of the
DC-HSDPA cell group.
CAC Based on the Number of HSDPA Users

The HSDPA services have to make admission decision based on the number of HSDPA users. The
DC-HSDPA costs only one HSDPA license user in the primary cell.
4.5.3 Queuing and Preemption

The UE requesting DC-HSDPA services will be queued in the selected primary cell. The queuing
principle is the same as that described in the Load Control Feature Parameter Description.

WCDMA RAN
For DC-HSDPA services, the RNC selects the primary cell in the DC-HSDPA cell group to perform
preemption.
4.5.4 Load Reshuffling and Overload Control

The power of the cell group may trigger basic congestion and overload. If the load of non-HSPA power
and GBP in the two cells is higher than or equal to the sum of the DL LDR/overload trigger threshold of
the two cells, the cell group is in basic congestion state.
If the cell group is in the basic congestion or overload state, both cells are in the basic congestion or
overload state. The operations to relieve congestion or overload are performed in each cell separately.
The operations to relieve basic congestion are performed for inter-frequency and inter-RAT handover.
The actions to relieve overload are the same as that of RAN11.0.
4.6 Scheduling
The NodeB selects the first cell from the two cells to perform the scheduling process. If the first cell
cannot transmit all the data of a UE, the NodeB selects the second cell to provide services.
After determining the cell, the NodeB needs to determine the queuing of this UE and other UEs in this
cell.
The method of DC-HSDPA scheduling is similar to that of SC-HSDPA scheduling. For details, see the
HSDPA Feature Parameter Description. This section describes only the difference between the two
scheduling methods.
The calculation of the scheduling priority of a DC-HSDPA queue needs to consider different CQIs and Uu
rates of the two carriers. In the proportional fair (PF) algorithm and enhanced proportional fair (EPF)
algorithm, R/r used for DC-HSDPA is different from that used for SC-HSDPA:
 For SC-HSDPA, R represents the throughput corresponding to the CQI reported by the UE for this
carrier, and r represents the throughput currently achieved by the UE. A greater R/r value indicates a
higher scheduling priority.
 For DC-HSDPA, R represents the throughput corresponding to the CQI reported by the UE for this
carrier, and r represents the total throughput currently achieved by the UE on the two carriers.
4.7 Activating or Deactivating Secondary Cell

This section describes the feature WRFD-010713 Traffic-Based Activation and Deactivation of the
Supplementary Carrier In Multi-carrier.
The NodeB periodically monitors the traffic volume of a UE and decides whether to activate or deactivate
the secondary cell in the DC-HSDPA/DC-MIMO cell group through HS-SCCH order.
 If data in MAC-ehs is insufficient and the throughput of MAC-ehs is low, the NodeB instructs the UE to
deactivate the secondary cell.
 If data in MAC-ehs is sufficient and the throughput of MAC-ehs is high, the NodeB instructs the UE to
activate the secondary cell.
The deactivation neither changes a DC-HSDPA cell to a non-DC-HSDPA cell nor changes the HS-DSCH
UE category. After deactivation, the NodeB regards the UE as a SC-HSDPA UE, and after activation, the
NodeB regards the UE as a DC-HSDPA UE.
The function is controlled by the SECCELLACTDEASW switch in the NodeB MML command SET
MACHSPARA.

WCDMA RAN
The activation or deactivation is applicable to the UEs configured with DC-HSDPA, DC-MIMO, or
DB-HSDPA in the downlink and to those configured with DCH or SC-HSUPA in the uplink. The function is
not applicable to DC-HSUPA because DC-HSUPA depends on DC-HSDPA.
The activation or deactivation of the UE takes effect after 12 timeslots when the UE receives the
HS-SCCH order. The activation or deactivation of the NodeB takes effect immediately after the NodeB
receives an ACK of HS-SCCH order from the UE. If the NodeB receives an DTX from the UE, the NodeB
retransmits or discards the HS-SCCH order.

WCDMA RAN
DC-HSDPA 5 Engineering Guidelines
5 Engineering Guidelines
5.1 DC-HSDPA
5.1.1 When to Use DC-HSDPA
DC-HSDPA is recommended in the following situations:
 The operator needs DC-HSDPA to provide two continuous absolute radio frequency channel numbers
(ARFCNs) within the same frequency band and has adequate spectral resources to support this.
 The traffic model on the network is close to a burst traffic model, in which case DC-HSDPA yields
increased gains in system throughput.
 The network downlink load is light, in which case DC-HSDPA increases the peak data rate for users
and noticeably improves the experience of users at cell edges.
 The network downlink load is heavy, in which case DC-HSDPA increases system throughput. The
system throughput increase is inversely related to the user number.
If the network is heavily loaded with a large number of users, DC-HSDPA can be used but only yields
subtle gains.
5.1.2 Factors to Consider During Feature Deployment

Consider the following factors when deploying HS-DSDPA:
 Proportion of DC-HSDPA users on the network: A higher proportion of DC-HSDPA users results in
better system throughput gains.
 Uplink capabilities: If dedicated channels (DCHs) are used on the uplink, the downlink peak rates for
DC-HSDPA users are restricted, resulting in decreased gains. HSUPA is recommended on the uplink
for DC-HSDPA.
 Bandwidth over the Iub interface: If the bandwidth over the Iub interface is inadequate, DC-HSDPA
cannot yield notable gains. An appropriate bandwidth is required over the Iub interface.
 Packet loss rate on the core network: If the core network has a high packet loss rate, gains yielded by
DC-HSDPA decrease during single-thread FTP sessions. An appropriate packet loss rate is required
for the core network.
5.1.3 Recommended Settings for Key Parameters

The following key parameters are involved in this feature:
 MIMO64QAMorDCHSDPASwitch
This parameter specifies priorities for MIMO+64QAM and DC-HSDPA. If the network supports both
MIMO+64QAM and DC-HSDPA, consult with the operator to determine which technique takes priority.
If the network load is heavy, set this parameter to MIMO+64QAM. Otherwise, set this parameter to
DC-HSDPA.
 CmpSwitch: CMP_UU_ADJACENT_FREQ_CM_SWITCH
When this switch is turned on and the RNC needs to start inter-frequency measurement, the RNC
considers whether to allow the UE not to use the compressed mode for ARFCNs within 5 MHz from
the current ARFCN. If the UE is allowed to do so, the RNC starts inter-frequency measurement without
requiring the UE to use the compressed mode.
For a DC-HSDPA network, it is recommended that this switch be turned off, because the UE currently
cannot report whether it is allowed not to use the compressed mode for ARFCNs within 5 MHz from
the current ARFCN.

WCDMA RAN
5.1.4 Feature Monitoring

To determine the number of DC-HSDPA radio access bearers (RABs) or DC-HSDPA users in a cell,
check the values of the following RNC counters:
 VS.HSDPA.RAB.DC.AttEstab: number of attempts to set up DC-HSDPA RABs on the primary carrier
in the DC-HSDPA cell
 VS.HSDPA.RAB.DC.SuccEstab: number of successful DC-HSDPA RAB setups on the primary
carrier in the DC-HSDPA cell
 VS.HSDPA.DC.PRIM.UE.Mean.Cell: average number of users that have chosen the current cell as
the primary-carrier cell
 VS.HSDPA.DC.SEC.UE.Mean.Cell: average number of users that have chosen the current cell as the
secondary-carrier cell
To obtain the information about the scheduling of DC-HSDPA users under a NodeB, check the values of
the following NodeB counters:
 VS.HSDPA.DCCfg.AnchorCarrierActedNum: number of times during a measurement period that
the current cell has performed scheduling for users that are configured with DC-HSDPA and have
chosen the current cell as the primary-carrier cell, regardless of whether the secondary carrier has
performed scheduling simultaneously. If the primary and secondary carriers have performed
scheduling for a user simultaneously, only one time is counted.
 VS.HSDPA.DCCfg.SupCarrierActedNum: number of times during a measurement period that the
current cell has performed scheduling for users that are configured with DC-HSDPA and have chosen
the current cell as the secondary-carrier cell, regardless of whether the primary carrier has performed
scheduling at the same time. If the primary and secondary carriers have performed scheduling for a
user simultaneously, only one time is counted.
 VS.HSDPA.DCCfg.DualCarrierActedNum: number of times during a measurement period that
scheduling has been performed by the primary and secondary carriers at the same time for users that
are configured with DC-HSDPA and have chosen the current cell as the primary-carrier cell
DC-HSDPA increases cell throughput and peak rates for individual users. To determine the average
HSDPA throughput and total downlink throughput before and after DC-HSDPA is deployed, check the
values of the following counters:
 VS.HSDPA.MeanChThroughput: an RNC counter that measures the average downlink throughput of
individual MAC-d flows for HSDPA in the cell.
The value of this counter is an average. The peak data rate per user can only be checked in drive
tests.
 VS.DataOutput.Mean: a NodeB counter that measures the average throughput at the
MAC-hs/MAC-ehs layer in the cell during a measurement period.
5.2 Activating or Deactivating Secondary Cell

This function cuts overheads on the uplink control channels, lowers UE power consumption, and
reduces the uplink load. It is recommended that this function be enabled if DC-HSDPA has been
deployed.
For burst services such as web browsing, this feature slightly decreases the DC-HSDPA throughput
during service burst transmission. As a result, the delay increases slightly. In addition, this feature
increases the usage of HS-SCCH code resources.
You can check the value of the counter VS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio to determine
the proportion of time during which supplementary carriers remained deactivated for DC-HSDPA users
and DC-HSDPA+MIMO users in a cell depending on the traffic volume.

WCDMA RAN
For a single DC-HSDPA user, this function reduces the uplink load only by a limited degree. If there are a
large number of DC-HSDPA users, this function reduces the uplink load significantly. Follow these steps
to calculate the uplink load gain for a cell:
1. With this function disabled, obtain the value of VS.MinRTWP when the cell is idle and the value of
VS.MeanRTWP when some DC-HSDPA users are camping on the cell. Then, calculate the
difference between the values of VS.MinRTWP and VS.MeanRTWP and record it as RTWPoff.
2. With this function enabled, obtain the value of VS.MinRTWP when the cell is idle and the value of
VS.MeanRTWP when some DC-HSDPA users are camping on the cell. Then, calculate the
difference between the values of VS.MinRTWP and VS.MeanRTWP and record it as RTWPon.
3. Calculate the difference between the values of RTWPoff and RTWPon to obtain the uplink load gain
yielded by this function.
The uplink load gain is easily affected by the number of DC-HSDPA users, the channel condition, and
other users, and its absolute value is small. As a result, it is not easy to notice a stable uplink load gain.

WCDMA RAN
DC-HSDPA 6 Parameters
6 Parameters
Table 6-1 Parameter description
Parameter ID NE MML Command Description
CfgSwitch BSC6900 SET Meaning: Channel configuration strategy switch
UCORRMALGOSWI group.
TCH(Optional) 1) CFG_DL_BLIND_DETECTION_SWITCH: When
the switch is on, the DL blind transport format
detection function is used for single SRB and
AMR+SRB bearers. Note that the UE is only required
to support the blind transport format stipulated in
3GPP 25.212 section 4.3.1.
2) CFG_HSDPA_64QAM_SWITCH: When the switch
is on, 64QAM can be configured for the HSDPA
service.
3) CFG_HSDPA_DC_SWITCH: When the switch is
on, DC can be configured for the HSDPA service.
4) CFG_HSDPA_MIMO_SWITCH: When the switch
is on, MIMO can be configured for the HSDPA
service.
5) CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:
When the switch is on and the switches for 64QAM
and MIMO are on, 64QAM+MIMO can be configured
for the HSDPA service
6) CFG_HSPA_DTX_DRX_SWITCH: When the
switch is on, DTX_DRX can be configured for the
HSPA service.
7) CFG_HSPA_HSSCCH_LESS_OP_SWITCH:
When the switch is on, HS-SCCH Less Operation
can be configured for the HSPA service.
8) CFG_HSUPA_16QAM_SWITCH: When the switch
is on, 16QAM can be configured for the HSUPA
service.
9) CFG_IMS_SUPPORT_SWITCH: When the switch
is on and the IMS license is activated, the RNC
supports IMS signaling.
10)
CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH
: When the switch is on, DL lossless RLC PDU size
change is supported.
11) CFG_LOSSLESS_RELOC_CFG_SWITCH:
When the switch is on and the UE supports lossless
relocation, the RNC configures lossless relocation for
PDCP parameters if the requirements of RLC mode,
discard mode, and sequential submission are met.
Then, lossless relocation is used for the UE.
12) CFG_MULTI_RAB_SWITCH: When the switch is
on, the RNC supports multi-RABs combinations such
as 2CS, 2CS+1PS, 1CS+2PS, and 2PS.

WCDMA RAN

13)
CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:
When the switch is on and the PDCP Header
compression license is activated, the PDCP header
compression algorithm for IPv6 is used at the RNC.
14) CFG_PDCP_RFC2507_HC_SWITCH: When the
switch is on and the PDCP Header compression
license is activated, the PDCP RFC2507 header
compression algorithm is used for the RNC.
15) CFG_PDCP_RFC3095_HC_SWITCH: When the
switch is on and the PDCP ROHC license is
activated, the PDCP RFC3095 header compression
algorithm is used for the RNC.
16) CFG_PTT_SWITCH: When this switch is on, the
RNC identifies the PTT user based on the QoS
attributes in the RAB assignment request message.
Then, the PTT users are subject to special
processing.
17) CFG_RAB_REL_RMV_HSPAPLUS_SWITCH:
When this switch is on and if an RAB release is
performed, the RNC decides whether to fall back a
certain HSPA(HSPA+) feature based on the
requirement of remaining traffic carried by the UE.
That is, if an HSPA+ feature is required by the
previously released RAB connection but is not
required in the initial bearer policy of the remaining
traffic, the RNC falls back the feature to save the
transmission resources. The HSPA+ features that
support the fallback are MIMO, 64QAM,
MIMO+64QAM, UL 16QAM, DC-HSDPA, and UL TTI
2ms.
18) CFG_EDPCCH_BOOSTING_SWITCH: When
the switch is on, Boosting can be configured for the
HSUPA service.
19) CFG_HSDPA_DCMIMO_SWITCH: When this
switch is turned on, DC+MIMO can be configured for
the HSDPA service.
20) CFG_FREE_USER_SWITCH: When this switch
is turned on, special handling for free access user is
enabled.
21) CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:
When this switch is turned on, the RNC determines
whether to enable the DC-HSDPA or MIMO feature
for a newly admitted user based on the cell load and
the number of HSDPA users.
GUI Value Range:
CFG_DL_BLIND_DETECTION_SWITCH,
CFG_HSDPA_64QAM_SWITCH,
CFG_HSDPA_DC_SWITCH,
CFG_HSDPA_MIMO_SWITCH,

WCDMA RAN

CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,
CFG_HSPA_DTX_DRX_SWITCH,
CFG_HSPA_HSSCCH_LESS_OP_SWITCH,
CFG_HSUPA_16QAM_SWITCH,
CFG_IMS_SUPPORT_SWITCH,
, CFG_LOSSLESS_RELOC_CFG_SWITCH,
CFG_MULTI_RAB_SWITCH,
CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH,
CFG_PDCP_RFC2507_HC_SWITCH,
CFG_PTT_SWITCH,
CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,
CFG_EDPCCH_BOOSTING_SWITCH,
CFG_HSDPA_DCMIMO_SWITCH,
CFG_FREE_USER_SWITCH,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH
Actual Value Range:
CFG_DL_BLIND_DETECTION_SWITCH,
CFG_HSDPA_64QAM_SWITCH,
CFG_HSDPA_DC_SWITCH,
CFG_HSDPA_MIMO_SWITCH,
CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,
CFG_HSPA_DTX_DRX_SWITCH,
CFG_HSPA_HSSCCH_LESS_OP_SWITCH,
CFG_HSUPA_16QAM_SWITCH,
CFG_IMS_SUPPORT_SWITCH,
, CFG_LOSSLESS_RELOC_CFG_SWITCH,
CFG_MULTI_RAB_SWITCH,
CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH,
CFG_PTT_SWITCH,
CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,
CFG_EDPCCH_BOOSTING_SWITCH,
CFG_HSDPA_DCMIMO_SWITCH,
CFG_FREE_USER_SWITCH,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH
Default Value: None
ChannelRetry BSC6900 SET Meaning: This parameter specifies the value of the
HoTimerLen UCOIFTIMER(Optio channel retry handover timer.
nal) When handover is performed and some higher HSPA
or HSPA plus technique is supported, UTRAN will
trigger the reconfiguration for the higher techniques.
Pingpang will happen when the reconfiguration is
triggered immediately when handover succeeds,
because handover procedure is frequently.
In order to avoid the pingpang, this timer will start
after handover procedure is performed, and the
reconfiguration will not be triggered until the timer

WCDMA RAN

expires.
GUI Value Range: 0~999
Actual Value Range: 0~999
Default Value: 2
CmpSwitch BSC6900 SET Meaning: Compatibility switch group.
UCORRMALGOSWI 1)
TCH(Optional) CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:
When the switch is on, the IMS signaling assigned by
the CN undergoes compatibility processing as an
ordinary PS service. When the switch is not on, no
special processing is performed.
2)
CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWI
TCH: When the Iu QoS Negotiation function is active
and the switch is on, IE RAB Asymmetry Indicator is
Symmetric bidirectional, The uplink and downlink
RNC negotiation rate is asymmetric, RNC select the
bigger rete as Iu QoS negotiation rate. When the
switch is OFF, RNC select the less rate as Iu QoS
negotiation rate.
3)
CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH:
When the switch is on, the IUUP version can be
rolled back to R99 when complete configurations are
applied during inter-RAT handover.
4)
CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWIT
CH: When the switch is on, H2D is performed before
a neighboring RNC cell whose version is earlier than
R5 is added to the active set; E2D is performed
before a neighboring RNC cell whose version is
earlier than R6 is added to the active set. If the DRNC
is of a version earlier than R5, DL services cannot be
mapped on the HS-DSCH. If the DRNC is of a
version earlier than R6, DL services cannot be
mapped on the HS-EDCH.
5) CMP_IUR_SHO_DIVCTRL_SWITCH: When the
switch is on, the diversity combination over the Iur
interface is configured on the basis of that of the local
RNC. When the switch is not on, the diversity
combination over the Iur interface is configured on
the basis of services. The flag of diversity
combination over the Iur interface can be set to
MUST (for BE services) or MAY (for other services).
6) CMP_UU_ADJACENT_FREQ_CM_SWITCH:
when the switch is on, the RNC initiates the
inter-frequency measurement without activating the
compressed mode if the following two conditions are
met: the UE supports the non-compressed
inter-frequency measurement, the inter-frequency

WCDMA RAN

neighboring cells work in a same frequency which is
within 5 MHz higher or lower than the current
frequency; when the switch is off, the RNC activates
the compressed mode before initiating the
inter-frequency measurement.
7) CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH:
When the switch is on, When SRB is set up on DCH,
and RNC decides to setup the AMR through DRD
procedure, RNC will execute blind handover to the
target cell, and then setup the AMR RBs on the target
cell.
8) CMP_UU_AMR_SID_MUST_CFG_SWITCH: For
narrowband AMR services, when the switch is on, the
SID frame is always configured; when the switch is
not on, the SID frame is configured on the basis of
CN assignment.
9) CMP_UU_FDPCH_COMPAT_SWITCH: When the
switch is OFF, if the information element that
indicates the F-DPCH capability of UE exists in the
message "RRC_CONNECT_REQ" or
"RRC_CONNECT_SETUP_CMP", the F-DPCH
capability depends on that indicator. In other case, it
means UE does not support F-DPCH. When the
switch is ON, if the information element that indicates
the F-DPCH capability of UE exists in the message
"RRC_CONNECT_REQ" or
"RRC_CONNECT_SETUP_CMP", the F-DPCH
capability depends on that indicator. If that
information element does not exist, UE supports
F-DPCH when all the conditions meets: a) the
version of UE is Release 6. b) UE supports
HS-PDSCH.
10) CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
When the switch is on, the RAB assignment request
and the subsequent RB setup procedure proceed if
the RLC AM capabilities of the UE fail to meet the
minimum RLC TX/RX window buffer requirement of
the RAB to be setup. When the switch is not on, the
RAB assignment request is rejected.
11)
CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SW
ITCH: When this switch is on, the cell individual offset
(CIO) of the best cell is always set to 0 in the
INTRA-FREQUENCY MEASUREMENT CONTROL
messages. Otherwise, the CIO information of the
best cell is not carried in the INTRA-FREQUENCY
MEASUREMENT CONTROL messages.
12)
CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWI
TCH: When the switch is on, the cell synchronization
information traced by the IOS need to be reported

WCDMA RAN

during the RRC measurement period.
13)
CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITC
H: When the switch is on, the active set update is in
the same procedure as the change of the serving cell.
When the switch is not on, the serving cell is changed
after the UE updates the active set and delivers
reconfiguration of physical channels. This switch is
applicable only to R6 or aboveUEs.
14)
CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SW
ITCH: When the switch is on, channel transition is in
the same procedure as the change of the serving cell.
When the switch is not on, the serving cell is changed
after the UE performs channel transition and delivers
reconfiguration of physical channels.
15)
CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SW
ITCH: By default, the switch is on. In this case, the
Alternative E-bit is not configured for L2.
16) CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:
When the switch is set to ON, only uplink RLC or
downlink RLC can be re-established during the state
transition from CELL_FACH to CELL_FACH (F2F for
short).
17)
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:
When the switch is set to ON, only uplink RLC or
downlink RLC can be re-established during the state
transition from CELL_DCH to CELL_FACH (D2F for
short).
18) CMP_RAB_5_CFG_ROHC_SWITCH: When the
switch is set to ON, the service with RAB ID 5 can be
configured with the Robust Header Compression
(ROHC) function. When the switch is set to OFF, the
service with RAB ID 5 cannot be configured with the
ROHC function.
configured with the ROHC function. When the switch
is set to OFF, the service with RAB ID 6 cannot be
configured with the ROHC function.

WCDMA RAN

23) CMP_HSUPA_MACD_FLOW_MUL_SWITCH:
When the switch is set to ON, MAC-d flow can be
multiplexed without any restrictions. When the switch
is set to OFF, only MAC-d flows whose scheduling
priority is lower than that of the current MAC-d flow
can be multiplexed.
24) CMP_SMLC_RSLT_MODE_TYPE_SWITCH: If
the Client Type of a positioning request is Value
Added Service or Lawful Intercept Client, the
positioning result is reported by using the Ellipsoid
Arc type. For other client types, the positioning result
is reported by using the Ellipsoid point with
uncertainty circle type.
GUI Value Range:
CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH,
TCH,
CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH,
CH, CMP_IUR_SHO_DIVCTRL_SWITCH,
CMP_UU_ADJACENT_FREQ_CM_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,
CMP_UU_AMR_SID_MUST_CFG_SWITCH,
CMP_UU_FDPCH_COMPAT_SWITCH,
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,
ITCH,
TCH,
H,
ITCH,
ITCH,
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_RAB_5_CFG_ROHC_SWITCH,
CMP_HSUPA_MACD_FLOW_MUL_SWITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH
Actual Value Range:

WCDMA RAN

CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH,
TCH,
CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH,
CH, CMP_IUR_SHO_DIVCTRL_SWITCH,
CMP_UU_ADJACENT_FREQ_CM_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,
CMP_UU_AMR_SID_MUST_CFG_SWITCH,
CMP_UU_FDPCH_COMPAT_SWITCH,
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,
ITCH,
TCH,
H,
ITCH,
ITCH,
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_HSUPA_MACD_FLOW_MUL_SWITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH
Default Value: None
DLFREQ NodeB ADD LOCELL Meaning: Indicates the downlink frequencies of the
MOD LOCELL local cell. The downlink and uplink frequencies of the
local cell must stay within the same frequency band.
SET LOCELLPRI Frequency(MHZ) = (Frequency Channel Number / 5)
+ Offset
Band1: Common Frequencies Channel Number:
[10562-10838] Offset: 0 Special Frequencies
Channel Number: none Offset: 0
[9662-9938] Offset: 0 Special Frequencies Channel
Number: (412, 437, 462, 487, 512, 537, 562, 587,
612, 637, 662, 687) Offset: 1850.1
Channel Number: (1887, 1912, 1937, 1962, 1987,
2012, 2037, 2062, 2087) Offset: 1735.1

WCDMA RAN

Number: (1007, 1012, 1032, 1037, 1062, 1087)
Offset: 670.1
Number: (1037, 1062) Offset: 670.1
Channel Number: (2587, 2612, 2637, 2662, 2687,
2712, 2737, 2762, 2787, 2812, 2837, 2862, 2887,
2912) Offset: 2105.1
Number: none Offset: 0.
The frequency of the local cell must be the same as
that of the bearing logical cell.
Default Value: None
FIRSTLOCEL NodeB ADD Meaning: Indicates the ID of local cell 1
L DUALCELLGRP .
Default Value: None
HspaPlusSwitc BSC6900 ADD Meaning: This parameter is used to select a feature
h UCELLALGOSWITC related to HSPA+.
H(Optional) If a feature is selected, it indicates that the
MOD corresponding algorithm is enabled. If a feature is not
UCELLALGOSWITC selected, it indicates that the corresponding algorithm
H(Optional) is disabled. Note that other factors such as license
and the physical capability of NodeB restrict whether
a feature can be used even if this feature is selected.
The EFACH/MIMO switch determines whether the
cell supports the E-FACH/MIMO feature but does not
affect the establishment of the E-FACH and the
MIMO cell.
GUI Value Range: 64QAM(Cell 64QAM Function
Switch), MIMO(Cell MIMO Function Switch),
E_FACH(Cell E_FACH Function Switch),
DTX_DRX(Cell DTX_DRX Function Switch),
HS_SCCH_LESS_OPERATION(Cell HS_SCCH
LESS OPERATION Function Switch),
DL_L2ENHANCED(Cell DL L2ENHANCED Function
Switch), 64QAM_MIMO(Cell 64QAM+MIMO

WCDMA RAN

Function Switch), UL_16QAM(Cell UL 16QAM
Function Switch), DC_HSDPA(Cell DC-HSDPA
Function Switch), UL_L2ENHANCED(Cell UL
L2ENHANCED Function Switch),
EDPCCH_BOOSTING(Cell E-DPCCH Boosting
Function Switch), DCMIMO_HSDPA(Cell
DC-HSDPA Combined with MIMO Function Switch),
E_DRX(Enhanced Discontinous Reception Function
Switch)
Actual Value Range: 64QAM, MIMO, E_FACH,
DTX_DRX, HS_SCCH_LESS_OPERATION,
DL_L2ENHANCED, 64QAM_MIMO, UL_16QAM,
DC_HSDPA, UL_L2ENHANCED,
EDPCCH_BOOSTING, DCMIMO_HSDPA, E_DRX
Default Value: None
MIMO64QAMo BSC6900 SET UFRC(Optional) Meaning: This switch is used to configure the priority
rDCHSDPASw of MIMO_64QAM or DC-HSDPA. According to
itch different protocols, the following situations may
occur: MIMO and DC-HSDPA cannot be used
together; both 64QAM and DC-HSDPA are
supported, but cannot be used together. In this case,
"MIMO64QAMorDCHSDPASwitch" is used to
configure the priorities of the features. When the
priority of MIMO is higher than that of DC-HSDPA,
the priority of 64QAM is higher than that of
DC-HSDPA. When the priority of DC-HSDPA is
higher than that of MIMO, the priority of DC-HSDPA
is higher than that of 64QAM.
GUI Value Range: MIMO_64QAM, DC_HSDPA
Actual Value Range: MIMO_64QAM, DC_HSDPA
Default Value: DC_HSDPA
SECCELLACT NodeB SET MACHSPARA Meaning: Indicates whether the anti-interference
DEASW HSUPA scheduling function takes effect. When this
parameter is set to ON, this function takes effect.
When this parameter is set to OFF, this function does
not take effect.
GUI Value Range: ON(ON), OFF(OFF)
Actual Value Range: ON, OFF
Default Value: OFF(OFF)
SECONDLOC NodeB ADD Meaning: Indicates the ID of local cell 2
ELL DUALCELLGRP .
Default Value: None
ServiceDiffDrd BSC6900 ADD Meaning: Whether the service steering DRD
Switch UCELLDRD(Optiona algorithm is applied.

WCDMA RAN

l) GUI Value Range: ON, OFF
MOD Actual Value Range: ON, OFF
UCELLDRD(Optiona Default Value: OFF
l)
TCell BSC6900 ADD Meaning: Difference between the System Frame
UCELLSETUP(Man Number (SFN) and NodeB Frame Number (BFN) of
datory) the NodeB which the cell belongs to. It is
ADD recommended that Tcell of difference cells under one
UCELLQUICKSETU NodeB should be unique. For detailed information of
P(Mandatory) this parameter, refer to 3GPP TS 25.433.
MOD GUI Value Range: CHIP0, CHIP256, CHIP512,
UCELLSETUP(Optio CHIP768, CHIP1024, CHIP1280, CHIP1536,
nal) CHIP1792, CHIP2048, CHIP2304
Actual Value Range: CHIP0, CHIP256, CHIP512,
CHIP768, CHIP1024, CHIP1280, CHIP1536,
CHIP1792, CHIP2048, CHIP2304
Default Value: None
ULFREQ NodeB ADD LOCELL Meaning: Indicates the uplink frequencies of the local
MOD LOCELL cell. The downlink and uplink frequencies of the local
cell must stay within the same frequency band.
Frequency(MHZ) = (Frequency Channel Number / 5)
+ Offset
Number: none Offset: 0
Number: (12, 37, 62, 87, 112, 137, 162, 187, 212,
237, 262, 287) Offset: 1850.1
Channel Number: (1662, 1687, 1712, 1737, 1762,
1787, 1812, 1837, 1862) Offset: 1380.1
Number: (782, 787, 807, 812, 837, 862) Offset: 670.1
Number: (812, 837) Offset: 670.1 Band7: Common
Frequencies Channel Number: [2012-2338] Offset:
2100 Special Frequencies Channel Number: (2362,
2387, 2412, 2437, 2462, 2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662, 2687) Offset: 2030.1

WCDMA RAN

Number: none Offset: 0.
Default Value: None
ULLdbDRDLo BSC6900 ADD Meaning: This parameter specifies the threshold of
adRemainThd UCELLDRD(Optiona triggering the uplink load balance for DC-HSDPA
DcHSDPA l) traffic. If the remaining number of equivalent users in
MOD the uplink is less than the value of this parameter,
UCELLDRD(Optiona uplink load balance for DC-HSDPA traffic is triggered.
l) GUI Value Range: 0~100
Default Value: 25
ULLdbDRDOff BSC6900 SET Meaning: If the difference of the remaining number of
setDcHSDPA UDRD(Optional) equivalent users in the uplink between the target cell
and the serving cell is greater than the value of this
parameter, the target cell meets one of the
qualifications to be the candidate cell for directed
retry.
Default Value: 10
ULLdbDRDSw BSC6900 ADD Meaning: This parameter specifies whether to enable
itchDcHSDPA UCELLDRD(Optiona the uplink load balance for DC-HSDPA traffic. The
l) uplink load balance is performed on the basis of the
MOD equivalent number of users.
UCELLDRD(Optiona GUI Value Range: ON, OFF
l) Actual Value Range: ON, OFF
Default Value: OFF

WCDMA RAN
DC-HSDPA 7 Counters
7 Counters
Table 7-1 Counter description
Counter Counter Name Counter Description Feature ID Feature
ID Name
50341702 VS.HSDPA.DCCfg The Ratio Of Dc Deact WRFD-010713 Traffic-Based
.SupCarrierDeact. Activation
TimeRatio and
Deactivation
of the
DC-HSDPA
Secondary
Carrier
73403828 VS.HSDPA.RAB.D Number of DC-HSDPA RAB Setup WRFD-010696 DC-HSDPA
C.AttEstab Requests in the primary carrier of
DC-HSDPA counted for cell
73403829 VS.HSDPA.RAB.D Number of DC-HSDPA RABs Setup WRFD-010696 DC-HSDPA
C.SuccEstab Successfully in the primary carrier of
DC-HSDPA counted for cell
73403830 VS.HSDPA.RAB.A Number of DC-HSDPA RABs Abnormal WRFD-010696 DC-HSDPA
bnormRel.DC Released in the primary carrier of DC
counted for Cell(including RF Cause)
73403831 VS.HSDPA.RAB.N Number of DC-HSDPA RABs Normal WRFD-010696 DC-HSDPA
ormRel.DC Released in the primary carrier of DC
counted for Cell
73410508 VS.HSDPA.DC.PR Average number of DC-HSDPA UEs in WRFD-010696 DC-HSDPA
IM.UE.Mean.Cell anchor carrier in a Cell
73410509 VS.HSDPA.DC.SE Average number of DC-HSDPA UEs in WRFD-010696 DC-HSDPA
C.UE.Mean.Cell supplementary carrier in a Cell

WCDMA RAN
DC-HSDPA 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

WCDMA RAN
DC-HSDPA 9 Reference Documents
9 Reference Documents
[1] 3GPP TS 25.331, "Radio Resource Control (RRC)"
[2] 3GPP TS 25.306, "UE Radio Access capabilities"
[3] HSDPA Feature Parameter Description
[4] Radio Bearers Feature Parameter Description
[5] Load Control Feature Parameter Description
[6] Directed Retry Decision Feature Parameter Description
[7] Handover Feature Parameter Description
[8] Green BTS Feature Parameter Description


Dual Carrier Multi Carrier Hsdpa Ran 13 Huawei PDF

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

Dual Carrier Multi Carrier Hsdpa Ran 13 Huawei PDF

Uploaded by

Copyright:

Available Formats

WCDMA RAN

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

4 Technical Description ..............................................................................................................4-1

Issue 02 (2011-06-30) Huawei Proprietary and Confidential ii

1.2 Intended Audience

1.3 Change History

Change Type Change Description Parameter Change

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 1-1

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 1-2

The requirements of DC-HSDPA are listed in Table 2-1.

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 2-1

3.2 Cell Configuration

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 3-1

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 3-2

3.3 Channel Mapping

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 3-3

Table 3-1 FDD HS-DSCH physical layer categories 21 to 24

Category 21 15 1 23370 345600 QPSK,

3.5 NodeB MAC-ehs

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 3-4

Figure 3-5 MAC-ehs architecture

3.6 Impact on Interfaces

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 3-5

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 3-6

4.2 Radio Bearers

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 4-1

4.3 State Transition

4.4 Mobility Management

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 4-2

Handover Between DC-HSDPA Cells

Handover from a DC-HSDPA Cell to a Non-DC-HSDPA Cell

Handover from a Non-DC-HSDPA Cell to a DC-HSDPA Cell

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 4-3

4.5 Load Control

Cell Group Selection Based on Service Priorities

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 4-4

DCH and DC-HSDPA HSDPA service priority

Cell Selection Based on UL Load

4.5.2 Call Admission Control

CAC Based on the DL Power

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 4-5

Figure 4-1 DL power of a DC-HSDPA cell group

The variables in Figure 4-1 are described as follows:

CAC Based on the ENU

CAC Based on the Number of HSDPA Users

4.5.3 Queuing and Preemption

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 4-6

4.5.4 Load Reshuffling and Overload Control

4.7 Activating or Deactivating Secondary Cell

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 4-7

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 4-8

5.1.2 Factors to Consider During Feature Deployment

5.1.3 Recommended Settings for Key Parameters

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 5-1

5.1.4 Feature Monitoring

5.2 Activating or Deactivating Secondary Cell

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 5-2

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 5-3

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 6-1

Parameter ID NE MML Command Description

Issue 02 (2011-06-30) Huawei Proprietary and Confidential 6-2