RAN

HSPA+ Parameter Description

Issue

01

Date

2009-03-30

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For
any assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address:

Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website:

http://www.huawei.com

Email:

support@huawei.com

Copyright Huawei Technologies Co., Ltd. 2009. 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 trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
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 the warranty of any kind, express or implied.

About This Document

Author
Prepared by

Sun Yafei, Liu Qi, and Zhang Shu

Date

2009-02-16

Edited by

Wang Deyang

Date

2009-02-19

Reviewed by

Zeng Yongmei, Mo Lin, Cao Yang, Huang Xin, Wang

Yiyun, Zhao Xiaofei, Sun Yafei, Liu Qi, Zhouli, Hu
Shengwu, Guo Bing, Zhang Lei, Lian Chunhai, Aravind,
Fang Qin, Wu Gongbo, and Zhang Lijun

Date

2009-02-18

Translated by

Wang Xiaofen (Chapters 1 to 4)

Date

2009-2-27

Tested by

Guo Bing

Date

2009-3-20

Approved by

Duan Zhongyi

Date

2009-03-30

Contents

1 Change History...................................................1-2

2 HSPA+ Introduction.............................................2-2

3 HSPA+ Overview.................................................3-2

3.1 Introduction......................................................................................................................3-2

3.2 Downlink Enhanced L2....................................................................................................3-2

3.3 Downlink 64QAM............................................................................................................3-2

3.4 MIMO...............................................................................................................................3-2

3.5 Enhanced CELL_FACH Operation..................................................................................3-2

3.6 CPC...................................................................................................................................3-2

3.6.1 Uplink DTX...................................................................................................................3-2

3.6.2 Downlink DRX..............................................................................................................3-2

3.6.3 HS-SCCH Less Operation.............................................................................................3-2

4 HSPA+ Algorithms...............................................4-2

4.1 Introduction to HSPA+ Algorithms..................................................................................4-2

4.2 HSPA+ Bearer Schemes...................................................................................................4-2

4.2.1 Feature Activation in the Cell........................................................................................4-2

4.2.2 Bearer Schemes for RRC Connection Setup.................................................................4-2

4.2.3 Bearer Schemes for RB Setup.......................................................................................4-2

4.3 HSPA+ State Transition....................................................................................................4-2

4.4 HSPA+ Flow Control........................................................................................................4-2

4.5 HSPA+ Scheduling and TFRC Selection..........................................................................4-2

4.6 HSPA+ Power Control......................................................................................................4-2

4.7 HSPA+ Handover.............................................................................................................4-2

4.7.1 Overview.......................................................................................................................4-2

4.7.2 Preselection Phase.........................................................................................................4-2

4.7.3 Fallback Phase...............................................................................................................4-2

4.7.4 Retry Phase....................................................................................................................4-2

5 HSPA+ Parameters..............................................5-2

5.1 Description........................................................................................................................5-2

5.2 Values and Ranges............................................................................................................5-2

6 Reference Documents.........................................6-2

Change History

The change history provides information on the changes in different document versions.

Document and Product Versions

Document Version

RAN Version

01 (2009-03-30)

11.0

Draft (2009-03-10)

11.0

Draft (2009-01-15)

11.0

This document is based on the BSC6810 and 3900 series NodeBs.

The available time of each feature is subject to the RAN product roadmap.
There are two types of changes, which are defined as follows:

Feature change: refers to the change in HSPA+.

Editorial change: refers to the change in the information that was inappropriately
described or the addition of the information that was not described in the earlier version.

01 (2009-03-30)
This is the document for the first commercial release of RAN11.0.
Compared with draft (2009-03-10) of RAN11.0, this issue optimizes the description.

Draft (2009-03-10)
This is the second draft of the document for RAN11.0.
Compared with draft (2009-01-15), draft (2009-03-10) optimizes the description.

Draft (2009-01-15)
This is the initial draft of the document for RAN11.0.

HSPA+ Introduction

HSPA+ (also known as HSPA evolution) is introduced in 3GPP Release 7. It is an

enhancement of HSPA, which is introduced in 3GPP Release 6. Compared with HSPA,
HSPA+ enhances both uplink and downlink transmission capabilities.
This document describes the enhanced and new features introduced in HSPA+, compared with
HSPA. For the original features, see the HSDPA Parameter Description and HSUPA
Parameter Description.

Intended Audience
This document is intended for:

System operators who need a general understanding of HSPA+.

Personnel working on Huawei products or systems.

Impact on system performance

Impact
HSPA+ increases the transmission rate and cell throughput. It also reduces the
transmission delay.

Impact on other features

HSPA+ does not affect other features, though it requires the support of other features
such as power control and load control.

Network Elements Involved

Table 2.1.1.I.1.1.1.1 lists the network elements (NEs) involved in HSPA+.
Table 2.1.1.I.1.1.1.1 NEs involved in HSPA+
UE

NodeB

RNC

MSC Server

MGW

SGSN

GGSN

HLR

NOTE:
: not involved
: involved
UE = User Equipment, RNC = Radio Network Controller, MSC Server = Mobile Service Switching
Center Server, MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN = Gateway
GPRS Support Node, HLR = Home Location Register

The peak rates of the SGSN, GGSN, and HLR need to be increased to support 28 Mbit/s in
the downlink. The functions of these NEs remain unchanged.

HSPA+ Overview

3.1 Introduction
3GPP Release 7 introduces a series of new features to enhance HSPA (including HSDPA and
HSUPA) to protect telecom operators' investments and improve network performance. All the
enhanced HSPA features are collectively termed HSPA+.
With regard to network performance, HSPA+ can reduce service delay, increase peak data
rates, improve spectrum efficiency, increase system capacity, and reduce UE power
consumption. The enhanced HSPA features in RAN11.0 are as follows:
Downlink
enhanced L2

Downlink enhanced L2 allows flexible PDU sizes at the RLC layer and
segmentation at the MAC layer on the Uu interface. The feature prevents
the L2 from becoming the bottleneck of higher Uu rates increased by

multiple-input multiple-output (MIMO) and 64QAM.

Downlink
64QAM

Downlink 64QAM allows the use of 64QAM in HSDPA to increase the

number of bits per symbol and thus to obtain higher transmission rates.
The peak rate at the MAC layer can reach 21 Mbit/s.

MIMO

MIMO increases transmission rates through space multiplexing and

improves channel qualities through space diversity. The network side can
dynamically select single- or dual-stream transmission based on channel
conditions. The peak rate at the MAC layer can reach 28 Mbit/s.

Enhanced
CELL_FACH
Operation

Enhanced CELL_FACH Operation allows the use of HSDPA technologies

for the UEs in the CELL_FACH, CELL_PCH, and URA_PCH states. The
purpose is to increase the peak rates in these states, reduce the signaling
transmission delay during service setup or state transition, and improve
user experience.

CPC

Continuous Packet Connectivity (CPC) allows uplink and downlink

transmissions at regular intervals. This feature reduces the transmit power
and thus prolongs the UE battery life because the UE does not have to
monitor and transmit overhead channels every TTl. This reduction in the
transmit power also helps to increase the uplink capacity by decreasing the
total interference. This improvement is especially significant when users
such as VoIP users transmit data discontinuously.
The CPC feature consists of downlink DRX, uplink DTX, and HS-SCCH
Less Operation.

Downlink 64QAM, MIMO, and Enhanced CELL_FACH Operation depend on HSDPA and
enhanced L2. CPC depends on both HSDPA and HSUPA. Figure 3.1.1.I.1.1.1 shows the
dependencies among these features.
Figure 3.1.1.I.1.1.1 Feature dependencies

Table 3.1.1.I.1.1.1.1 lists the UE categories that support HSPA+.

Table 3.1.1.I.1.1.1.1 UE categories that support HSPA+
HS-DSCH Category

Supported Modulations Without MIMO

Supported Modulations with MIMO

Category 13

QPSK, 16QAM, and 64QAM

None

Category 14

HS-DSCH Category

Supported Modulations Without MIMO

Supported Modulations with MIMO

Category 15

QPSK and 16QAM

QPSK and 16QAM

QPSK, 16QAM, and 64QAM

QPSK and 16QAM

Category 16
Category 17
Category 18

All such UEs must support downlink enhanced L2. These categories do not indicate whether
CPC and Enhanced CELL_FACH Operation are supported.
During RRC connection setup or service setup, the UE notifies the network of its capability to
support these features.

3.2 Downlink Enhanced L2

HSPA+ Features such as MIMO and 64QAM increase the downlink rates on the Uu interface.
The original downlink L2 function cannot adapt to such high rates. To prevent L2 from
becoming the bottleneck of the network, 3GPP introduces enhancements to L2, including
flexible PDU sizes at the RLC layer and segmentation at the MAC layer.
The original L2 uses fixed RLC PDU sizes. The typical fixed size is 336 or 656. This cannot
meet the requirement of high-speed transmission for larger RLC PDU sizes or the requirement
of edge coverage for smaller RLC PDU sizes, which is described as follows:

A small fixed RLC PDU size, together with a limited RLC sending window size, limits
the maximum transmission rate at the RLC layer. Figure 3.2.1.I.1.1.1 shows a typical
example, in which the maximum bit rate at the RLC layer is limited to 13.1 Mbit/s. This
rate is far below the peak rate that can be achieved by 64QAM (21 Mbit/s) or MIMO (28
Mbit/s).

Figure 3.2.1.I.1.1.1 MBR limited by a fixed PDU size

A large fixed RLC PDU size limits the cell coverage because the RLC PDU cannot be
segmented under the RLC layer.

The enhancements to L2 in the downlink are as follows:

Enhancing the RLC entity to support flexible RLC PDU sizes

Adding a new sublayer, the MAC-ehs, for data segmentation at the MAC layer and
multiplexing of multiple priority queues

Figure 3.2.1.I.1.1.2 shows the impact of enhanced L2 activation.

Figure 3.2.1.I.1.1.2 Impact of enhanced L2 activation

After the introduction of flexible RLC PDU sizes, the RLC layer will not segment higherlayer packets with sizes less than the maximum RLC PDU size. Thus, the RLC layer can
flexibly adapt to variations in traffic volume and reduce the overhead of the RLC PDU
header.
When the channel conditions of the UE are poor (for example, on the cell edge) and the Uu
interface fails to transmit an entire RLC PDU, the MAC-ehs can segment the RLC PDU into
smaller PDUs for transmission at lower rates to ensure the service continuity.
Enhanced L2 is a prerequisite for using 64QAM, MIMO, and enhanced CELL_FACH
operation. If the UE or the cell does not support enhanced L2, it cannot support 64QAM,
MIMO, or Enhanced CELL_FACH Operation in the downlink.
The RNC can be configured independently with enhanced L2, without 64QAM, MIMO, or
Enhanced CELL_FACH Operation.
Downlink enhanced L2 is an optional feature.

3.3 Downlink 64QAM

The AMC feature introduced in HSDPA enables adaptation of modulation and coding to
varying radio conditions. To improve the advantages of AMC even further, a new modulation
scheme, 64QAM, is introduced in HSPA+. Theoretically, 64QAM can provide a peak rate of
21 Mbit/s to a single UE. It enables the UE with good channel conditions to download data at
higher rates, improves user experience, and increases telecom operator competitiveness.
Figure 3.3.1.I.1.1.1 shows the modulation schemes for HSPA+.

Figure 3.3.1.I.1.1.1 Modulation schemes for HSPA+

Using the 64QAM mode in the downlink of HSPA+ enables each symbol to carry six bits, 1.5
times the number when using the 16QAM mode in HSDPA. Thus, 64QAM can provide
higher transmission rates on the Uu interface.
The TFRC selection function of the NodeB MAC-ehs can dynamically select QPSK, 16QAM,
or 64QAM for transmission based on channel conditions and available transmission resources
on the Uu interface. For the UEs with good channel conditions, the TFRC selection function
applies 64QAM to further increase the data rates. For the UEs with normal channel
conditions, the TFRC selection function applies QPSK or 16QAM to implement lower-speed
transmission and to ensure the transmission quality.
64QAM is used for the streaming service and BE service. For additional bearer scheme
information, see section 4.2"HSPA+ Bearer Schemes."
Downlink 64QAM is an optional feature. A prerequisite for using 64QAM is that HSDPA and
enhanced L2 are enabled.

3.4 MIMO
HSPA+ introduces closed-loop 2x2 MIMO in the downlink to improve the single-user
throughput and system performance. The principle of 2x2 MIMO is that two different data
streams are transmitted by utilizing the same set of resources, as shown in Figure 3.4.1.I.1.1.1.
MIMO requires two transmission antennas at the base station and two receiver antennas at the
UE.

Figure 3.4.1.I.1.1.1 Illustration of 2x2 MIMO

The NodeB MAC-ehs is responsible for scheduling and managing MIMO transmissions.
After the introduction of MIMO, the AMC function of HSDPA is extended accordingly. Based
on the channel conditions of the UE, AMC determines the dual-stream or single-stream
transmission mode. Through multiple antennas, MIMO builds up channels independent of
each other to avoid the interference between two streams.

In the dual-stream case, two MAC-ehs PDUs can be transmitted simultaneously in a TTI.
After coding, the two streams are mapped onto the corresponding HS-PDSCHs with the
same orthogonal code.

In the single-stream case, only one MAC-ehs PDU is transmitted in a TTI, and using
transmit diversity through two antennas can provide higher transmission qualities.

For the UE with good channel conditions, AMC uses space multiplexing and dual-stream
transmission to provide higher transmission rates. For the UE with normal channel conditions,
AMC uses transmit diversity and single-stream transmission to achieve higher transmission
qualities.
The UE with MIMO requires the pilot transmit diversity (STTD) from NodeB to estimate the
channel conditions between multiple receive antennas and multiple transmit antennas.
To support MIMO, the UE periodically and alternatively reports two types of CQIs to the
scheduler and AMC. The UE also reports PCI together with CQI as a reference for MIMO
spatial multiplexing or transmit diversity.
3GPP Release 7 supports simultaneous use of QPSK/16QAM and MIMO, but does not
support simultaneous use of 64QAM and MIMO. For detailed bearer schemes, see section
4.2"HSPA+ Bearer Schemes."
Simulation results show that MIMO has a relatively low gain in the macro-cell scenario while
it has a relatively high gain in the micro-cell or indoor scenario. Therefore, MIMO is
recommended in the micro-cell scenario and the indoor scenario, where the cell should be
well isolated from other cells. When the UE uses the Type3i receiver, MIMO can achieve a
higher gain even in the macro-cell scenario. This type of UE has the equalization reception
and interference cancellation functions.
22 MIMO is an optional feature. A prerequisite for using MIMO is that HSDPA and
enhanced L2 are enabled.

3.5 Enhanced CELL_FACH Operation

The RRC states of a UE in connected mode include CELL_DCH, CELL_FACH, CELL_PCH,
and URA_PCH. HSPA significantly increases the maximum achievable uplink and downlink
data rates, but only for UEs in the CELL_DCH state. The purpose of Enhanced CELL_FACH
Operation is to extend the use of HSDPA to the CELL_FACH, CELL_PCH, and URA_PCH
states. The enhancement lies in more flexible allocation of resources, increased data rates, and
reduced transmission delays. RAN 11.0 supports HSDPA only for UEs in the CELL_FACH
state.
Figure 3.5.1.I.1.1.1 shows the impact of activating Enhanced CELL_FACH Operation.
Figure 3.5.1.I.1.1.1 Impact of activating Enhanced CELL_FACH Operation

In releases earlier than Release 7, the data and signaling of the UE in the CELL_FACH state
are carried on the FACH. The resources of the channel cannot be allocated flexibly and the
transmission rates are limited.
In Release 7, the data and signaling (originally carried on the DTCH, DCCH, BCCH, and
CCCH) of the UE in the enhanced CELL_FACH state can be carried on the HS-DSCH. For
details, see section 4.2"HSPA+ Bearer Schemes." Between the UE and the network, no
dedicated physical connection is set up, and no HSDPA CQI or HARQ information is reported
in the uplink. The RNC sends the pilot measurement information (reported by the UE on the
RACH) to the NodeB for HSDPA scheduling and resource allocation. The UE does not report
whether the data is correctly received, and therefore the NodeB performs blind
retransmissions of HSDPA data in the downlink to reduce the block error rate (BLER).
The UEs in the enhanced CELL_FACH state and those in the CELL_DCH state can share the
code and power resources of the cell. The NodeB MAC-ehs is responsible for scheduling and
dynamic resource allocation as required.
The cell that supports Enhanced CELL_FACH Operation needs to broadcast the HSDPArelated information that is commonly used in the enhanced CELL_FACH state. To ensure the
backward compatibility, the cell also needs to be configured with the FACH if some UEs in
the cell do not support Enhanced CELL_FACH Operation.
After the introduction of Enhanced CELL_FACH Operation, more users can be admitted and
there is no need to reserve multiple FACHs. The UE can be dynamically switched between the
enhanced CELL_FACH state and the CELL_DCH state. If the UE in the CELL_DCH state
has no data to transmit during a period, it is switched to the enhanced CELL_FACH state to
reduce the system resource overhead. If the UE in the enhanced CELL_FACH state has large
amounts of data to transmit, it is switched to the CELL_DCH state. The telecom operator can
customize the strategy of switching between the enhanced CELL_FACH state and the
CELL_DCH state by setting the traffic volume threshold and the time threshold. For details,
see section 4.3"HSPA+ State Transition."

Enhanced CELL_FACH operation can be widely used on the network. The main benefits lie
in that it increases the data rates of the UE in the CELL_FACH state, greatly reduces the state
transition delay, and improves the "always-on" experience of end users.
Enhanced CELL_FACH operation is an optional feature. It is dependent on HSDPA and
enhanced L2.

3.6 CPC
CPC allows packet data users to remain in the CELL_DCH state to a larger extent, thus
avoiding frequent packet connection re-establishments.
According to the 3GPP specifications, the preconditions for CPC configuration are as follows:

The DCH cannot be configured in the uplink or downlink. The E-DCH must be
configured in the uplink, and the HS-DSCH and F-DPCH must be configured in the
downlink.

Signaling and data must be carried on HSPA channels. Therefore, CPC is dependent on
SRB over HSDPA and SRB over HSUPA.

The main benefits brought by CPC are as follows:

CPC greatly improves the system capacity. Under the condition that the bandwidth
remains unchanged, each cell can serve more users at the same time in Release 7 than in
Release 6. Thus, the telecom operator can improve revenue generation.

CPC provides an "always-on" experience for end users, increases the QoS, and enhances
the competitiveness of the telecom operator.

CPC reduces the UE power consumption and prolongs the UE battery life, which is one
of the key bottlenecks that affect the development of data services.

CPC is an optional feature. The main functions of CPC are uplink DTX, downlink DRX, and
HS-SCCH Less Operation. These three functions are described in the following sections.

3.6.1 Uplink DTX

The uplink DTX function allows a UE to stop transmission on the uplink DPCCH when there
is no data for transmission. As a consequence, uplink interference is reduced.
Uplink DTX is of particular importance for services such as VoIP and web browsing, with
intermittent data transmission.
Figure 3.6.1.I.1.1.1 shows the impact of uplink DTX activation.

Figure 3.6.1.I.1.1.1 Impact of uplink DTX activation

Even when there is no data for transmission, the UE needs to maintain power control
signaling and link synchronization. For this purpose, the UE can be configured to periodically
start transmission on the DPCCH. There are two types of "wake-up" interval, namely cycle 1
and cycle 2, for the UE with uplink DTX. Generally, the UE uses cycle 1 for uplink DTX. If
the UE has no data to transmit for a longer time, the UE uses cycle 2 for uplink DTX. When
there is data for transmission, the UE uses cycle 1 again. Figure 3.6.1.I.1.1.2 shows the
switching between the two cycles. The telecom operator can configure different cycles
through the SET DTXDRXPARA command for different services to increase the system
capacity while ensuring service qualities. For each UE, the NodeB can dynamically activate
or deactivate uplink DTX. If the E-DCH data is transmitted continuously, the DPCCH has to
be transmitted and DTX becomes unavailable.
Figure 3.6.1.I.1.1.2 Switching between cycle 1 and cycle 2

3.6.2 Downlink DRX

The UE in connected mode needs to listen to the control channel (HS-SCCH) continuously
and therefore power consumption is high. If downlink DRX is used, the UE needs to receive
the HS-SCCH only at some time points.

Figure 3.6.2.I.1.1.1 Impact of downlink DRX activation

Downlink DRX depends on uplink DTX. Thus, downlink DRX can be activated only after
uplink DTX is activated. Downlink DRX, together with uplink DTX, allows the UE to
periodically shut down the TX and RX function in the UE, thus lowering the UE battery
consumption and prolonging the UE battery life. The telecom operator can adjust the DTX
and DRX cycles by running the SET DTXDRXPARA command to meet the requirements of
the UE.
For each UE, the NodeB can dynamically activate or deactivate downlink DRX.

3.6.3 HS-SCCH Less Operation

In the case of HSDPA, the overhead of the HS-SCCH is relatively high for small-packet
services such as VoIP, and the power consumption of the HS-SCCH may be higher than that
of a traffic channel. In addition, the HS-SCCH limits the maximum number of HSDPA users
that can be scheduled in each TTI. This results in the increasing of the transmission delay and
the decreasing of the user capacity of delay-sensitive services.
The HS-SCCH Less Operation function allows that the initial transmission with a small
amount of data takes place without the HS-SCCH. Retransmission still requires the HSSCCH. Thus, HS-SCCH Less Operation reduces the power consumption and occupation of
the HS-SCCH during downlink transmission, allows more services to be scheduled at the
same time, and improves the system capacity.
There is no control information during the initial transmission. Therefore, a predefined set of
transport block sizes are used in the downlink, and the UE receives the data through blind
detection. In the case of HS-SCCH Less Operation, four predefined transport block sizes and
QPSK modulation can be used for transmission. The peak rate is limited to 742 kbit/s.
The RAN determines whether to use HS-SCCH Less Operation based on downlink traffic volume.

Figure 3.6.3.I.1.1.1 shows the impact of HS-SCCH Less Operation activation.

Figure 3.6.3.I.1.1.1 impact of HS-SCCH Less Operation activation

HSPA+ Algorithms

4.1 Introduction to HSPA+ Algorithms

HSPA+ Phase 1 mainly enhances the downlink data transmission. The algorithms of HSPA+
are similar to those already introduced in HSDPA, but are enhanced to support new features of
HSPA+. For details on HSDPA algorithms, see the HSDPA Parameter Description.
To support new features of HSPA+, some new parameters are used in the enhanced
algorithms. Table 4.1.1.I.1.1.1.1 lists these enhanced algorithms.
Table 4.1.1.I.1.1.1.1 Enhanced algorithms associated with new features of HSPA+
Enhanced
Algorithm

Downlink
Enhanced L2

Downlink
64QAM

MIMO

Enhanced
CELL_FACH
Operation

DTX/DRX

HS-SCCH Less
Operation

Bearer scheme

State transition

Flow control

Scheduling and

Enhanced
Algorithm

Downlink
Enhanced L2

Downlink
64QAM

MIMO

Enhanced
CELL_FACH
Operation

DTX/DRX

HS-SCCH Less
Operation

Power control

Handover

TFRC selection

4.2 HSPA+ Bearer Schemes

Different types of traffic and signaling require different bearer schemes and parameter
settings. Appropriate parameter settings help increase the system capacity and ensure the QoS.
Bearer schemes include the SRB bearer schemes used in the RRC connection setup procedure
and the SRB and TRB bearer schemes used in the RB setup procedure.
This section describes how to activate the HSPA+ features and select bearer channels for
signaling radio bearer (SRB) and traffic radio bearer (TRB) associated with HSPA+. For
details of pre-HSPA+ bearer schemes, see the Radio Bearers Parameter Description.

4.2.1 Feature Activation in the Cell

The HSPA+ features are controlled by the parameters listed in Table 4.2.1.I.1.1.1.1 and can be
activated by the telecom operator.
Table 4.2.1.I.1.1.1.1 Feature activation in the cell
Feature

Activation Method

Downlink enhanced L2

Select L2ENHANCED of the parameter HspaPlusSwitch.

Downlink 64QAM

Select 64QAM of the parameter HspaPlusSwitch, and

CFG_HSDPA_64QAM_SWITCH of the parameter CfgSwitch.

MIMO

Select MIMO of the parameter HspaPlusSwitch, and

CFG_HSDPA_MIMO_SWITCH of the parameter CfgSwitch.

Enhanced CELL_FACH
operation

Select E_FACH of the parameter HspaPlusSwitch.

CPC: DTX/DRX

Select DTX_DRX of the parameter HspaPlusSwitch, and

CFG_HSPA_DTX_DRX_SWITCH of the parameter CfgSwitch.

CPC: HS-SCCH Less

Operation

Select HS_SCCH_LESS_OPERATION of the parameter HspaPlusSwitch, and

CFG_HSPA_HSSCCH_LESS_OP_SWITCH of the parameter CfgSwitch.

Currently, 64QAM and MIMO cannot be used at the same time; HS-SCCH Less Operation
and MIMO cannot be used at the same time. Therefore, you need to specify the preferred
feature by setting the parameter HSPAPlusSelection:

If HSPAPlusSelection is set to MIMO, MIMO is selected when both MIMO and

64QAM are configured or when both MIMO and HS-SCCH Less Operation are
configured.

If HSPAPlusSelection is set to 64QAM, 64QAM is selected when both MIMO and

64QAM are configured, or HS-SCCH Less Operation is selected when both MIMO and
HS-SCCH Less Operation are configured.

4.2.2 Bearer Schemes for RRC Connection Setup

The RRC connection setup procedure involves only the SRB. The SRB can be handled in the
following ways:

The SRB is set up in the enhanced CELL_FACH state.

The SRB is set up in a normal state (CELL_DCH or CELL_FACH). For details, see the
Radio Bearers Parameter Description.

If the cell activates Enhanced CELL_FACH Operation, the UE supports Enhanced

CELL_FACH Operation, and EFachSwitch is set to ON, then the SRB is set up in the
enhanced CELL_FACH state. Otherwise, the SRB is set up in a normal state.

4.2.3 Bearer Schemes for RB Setup

Overview
The Radio Bearers Parameter Description determines the transport channel (FACH/RACH,
DCH, HS-DSCH, or E-DCH) onto which the service is mapped. This section describes only
the HSPA+ features associated with the service bearer schemes of HSPA+.
HSPA+ can carry multiple types of services, as listed in Table 4.2.3.I.1.1.1.1. If the required
HSPA+ features are unavailable for a bearer scheme, the bearer scheme is the same as that
used in pre-HSPA+. For details, see the Radio Bearers Parameter Description.
Table 4.2.3.I.1.1.1.1 HSPA+ features associated with the bearer schemes
Service Type

HSPA+ Features

CS voice over
HSPA+

The HS-DSCH is used in the downlink and the E-DCH is used in

the uplink. The available features are DTX/DRX and HS-SCCH
Less Operation.

VoIP over HSPA+

The HS-DSCH is used in the downlink and the E-DCH is used in

the uplink. The available features are DTX/DRX and HS-SCCH
Less Operation.

PS streaming service

If Enhanced CELL_FACH Operation is available, use this feature

with the HS-DSCH in the downlink and the RACH in the uplink.
Otherwise, the available features are determined as follows:

PS BE service
(Interactive and
background)

If the HS-DSCH is used in the downlink and the DCH is used in

the uplink, the available features are MIMO and 64QAM.
If the HS-DSCH is used in the downlink and the E-DCH is used
in the uplink, all the HSPA+ features are available except
Enhanced CELL_FACH Operation.

If the FACH and RACH are used in the downlink and uplink
respectively, the available feature is Enhanced CELL_FACH
Operation, with the HS-DSCH in the downlink and the RACH in
the uplink.
If the DCH is used in the downlink and the DCH/E-DCH is used in

Service Type

HSPA+ Features

the uplink, no HSPA+ feature can be used.

If the HS-DSCH is used in the downlink and Enhanced
CELL_FACH Operation is available, use Enhanced CELL_FACH
Operation. Otherwise, the available features are determined as
follows:

If the HS-DSCH is used in the downlink and the DCH is used in

the uplink, the available features are MIMO and 64QAM.
If the HS-DSCH is used in the downlink and the E-DCH is used
in the uplink, all the HSPA+ features are available except
Enhanced CELL_FACH Operation.

IMS signaling

No HSPA+ feature can be used.

CS service except CS
voice over HSPA+

No HSPA+ feature can be used.

For IMS signaling and CS services (except CS voice over HSPA+), the bearer schemes
remain unchanged, compared with those used in pre-HSPA+. For other services, whether the
bearer schemes for SRB and TRB can use HSPA+ features depends on the conditions
described in Table 4.2.3.I.1.1.1.1 to Table 4.2.3.I.1.1.1.3.

PS or CS Voice Service Bearer Schemes

If the PS or CS voice service is carried on the HS-DSCH in the downlink and on the E-DCH
in the uplink, the HSPA+ features that can be used are listed in Table 4.2.3.I.1.1.1.1.
Otherwise, no HSPA+ feature can be used.
Table 4.2.3.I.1.1.1.1 Bearer schemes for the PS or CS voice service (with the HS-DSCH in the downlink and the EDCH in the uplink)
DTX/DRX is activated in the cell

Yes

HS-SCCH Less Operation is activated in the cell

Yes

Bearer scheme

DTX/DRX

HS-SCCH Less
Operation

The rules followed in Table 4.2.3.I.1.1.1.1 to Table 4.2.3.I.1.1.1.3 are as follows:

If a UE or a cell does not support a feature, the feature is unavailable for this UE or cell. For the
feature activation method in the cell, see section 4.2.1"Feature Activation in the Cell."

If all the conditions listed in a column of the table are met, the corresponding scheme can be used; if
all the conditions listed in several columns are met, all the corresponding schemes can be used.

The symbol "-" in the table means that the corresponding condition is not applicable.

The word "Yes" in the table means that the switch is on or the feature is activated.

PS Streaming Service Bearer Schemes

If the PS streaming service is carried on the DCH in the downlink and on the DCH or E-DCH
in the uplink, no HSPA+ feature can be used. Otherwise, see Table 4.2.3.I.1.1.1.1 to determine
whether to perform Enhanced CELL_FACH Operation:

If the conditions for Enhanced CELL_FACH Operation are not met, determine whether
to use MIMO, 64QAM, HS-SCCH Less Operation, or DTX/DRX:

If the service is carried on the HS-DSCH in the downlink and on the DCH in the
uplink, the HSPA+ features that can be used are listed in Table 4.2.3.I.1.1.1.2.

If the service is carried on the HS-DSCH in the downlink and on the E-DCH in the
uplink, the HSPA+ features that can be used are listed in Table 4.2.3.I.1.1.1.3.

Table 4.2.3.I.1.1.1.1 Bearer schemes related to Enhanced CELL_FACH Operation in the RB setup procedure
Service Type

Streaming

BE

Others

The switch for the PS streaming service in Enhanced

CELL_FACH Operation is selected

Yes

The switch for the PS BE service in Enhanced

CELL_FACH Operation is selected

Yes

Enhanced CELL_FACH operation is applied in the

scenario provided in section 4.2.2"Bearer Schemes for
RRC Connection Setup"

Yes

Yes

The UE state transition algorithm takes effective

Yes

Yes

Transport channel

HS-DSCH
in the
downlink

HSDSCH in
the
downlink

FACH in
the
downlin
k

Enhanced CELL_FACH operation is activated in the cell

Yes

Yes

Yes

Bearer scheme (in Enhanced CELL_FACH Operation )

Yes

Yes

Yes

No

For the activation of the UE state transition algorithm, see the Rate Control Parameter Description.

For the selection of transport channel, see the Radio Bearers Parameter Description.

The switch for the PS BE service in Enhanced CELL_FACH Operation is set through the
MAP_PS_BE_ON_E_FACH_SWITCH of the parameter MapSwitch.

The switch for the PS streaming service in Enhanced CELL_FACH Operation is set through the
MAP_PS_STREAM_ON_E_FACH_SWITCH of the parameter MapSwitch.

Table 4.2.3.I.1.1.1.2 Bearer schemes for the PS streaming service and BE service (with the HS-DSCH in the downlink
and the DCH in the uplink)
Enhanced L2 is activated in the cell

Yes

Yes

Yes

Yes

Yes

MIMO is activated in the cell

Yes

No

Yes

Yes

64QAM is activated in the cell

No

Yes

Yes

Yes

Preferred HSPA+ feature

MIMO

64QAM

Bearer scheme

Enhance
d L2

MIMO

64QAM

MIMO

64QAM

Table 4.2.3.I.1.1.1.3 Bearer schemes for the PS streaming service and BE service (with the HS-DSCH in the downlink
and the E-DCH in the uplink)
Enhanced
L2 is
activated in
the cell

Yes

Yes

Yes

Yes

Yes

Yes

MIMO is
activated
in the cell

Yes

No

No

Yes

Yes

Yes

Yes

64QAM is
activated
in the cell

No

Yes

Yes

Yes

HS-SCCH
Less
Operation
is activated
in the cell

No

Yes

Yes

Yes

DTX/DRX
is activated
in the cell

Yes

MIM
O

64QA
M

MIM
O

64QAM

MIM
O

64QA
M

HSSCCH
Less
Operation

MIM
O

64QA
M

MIM
O

HSSCCH
Less
Operation

DTX/DR
X

Preferred
HSPA+
feature
Bearer
scheme

Enhance
d L2

PS BE Service Bearer Schemes

For the PS BE service, including the interactive service and background service, the bearer
schemes are determined as follows:

If the service is carried on the FACH in the downlink and on the RACH in the uplink,
see Table 4.2.3.I.1.1.1.1 to determine whether to use Enhanced CELL_FACH Operation.

If the service is carried on the DCH in the downlink and on the DCH or E-DCH in the
uplink, no HSPA+ feature can be used.

In other cases, see Table 4.2.3.I.1.1.1.1 to determine whether to use Enhanced

CELL_FACH Operation. If Enhanced CELL_FACH Operation is unavailable, determine
whether to use MIMO, 64QAM, HS-SCCH Less Operation, or DTX/DRX:

If the service is carried on the HS-DSCH in the downlink and on the DCH in the
uplink, the HSPA+ features that can be used are listed in Table 4.2.3.I.1.1.1.2.

If the service is carried on the HS-DSCH in the downlink and on the E-DCH in the
uplink, the HSPA+ features that can be used are listed in Table 4.2.3.I.1.1.1.3.

Combined Services Bearer Schemes

The first service to be set up by the UE uses the single-service bearer schemes mentioned
previously.
The combined services use the bearer scheme for the service with the highest speed if the
bearer schemes for different services cannot work together.
For example, the combined services are VoIP service and BE service (384 kbit/s). If the VoIP
service is to be configured with HS-SCCH Less Operation and the BE service is to be
configured with MIMO, then the combined services use the bearer scheme for the higherspeed service, namely the BE service.
If all the services already set up for the UE are in the enhanced CELL_FACH state and a new
service is also to be set up in this state according to the single-service bearer scheme, then the
new service is set up in the enhanced CELL_FACH state. Otherwise, the new service is set up
in the CELL_DCH state.

4.3 HSPA+ State Transition

After the RRC connection is set up, the RNC observes the UE activity and uses the state
transition algorithm for UE state transition.
This section describes the new functionality of the state transition introduced in HSPA+.
HSPA+ requires two new states to be introduced: CELL_DCH (CPC) state and enhanced
CELL_FACH state. The CELL_DCH (CPC) state corresponds to the CELL_DCH state with
CPC enabled, and the enhanced CELL_FACH state corresponds to the CELL_FACH state
with Enhanced CELL_FACH Operation enabled.
Figure 4.3.1.I.1.1.1 shows the new types of state transitions introduced in HSPA+.
Figure 4.3.1.I.1.1.1 New types of state transitions introduced in HSPA+

These state transitions are triggered by the event 4A or event 4B. The corresponding
algorithms are the same as those for the state transitions between CELL_DCH and

CELL_FACH, except that some new parameters are introduced. For details on the state
transition algorithms, see the Rate Control Parameter Description.
The only impact of the following new state transitions is that new timers to trigger event 4B
are introduced:

CELL_DCH (CPC) to CELL_FACH state transition

The new timers are as follows:

BeCpc2FStateTransTimer: BE service state transition timer (CPC_HS-DSCH to

F/RACH)

RtCpc2FStateTransTimer: real-time service state transition timer (CPC_HSPA to

F/RACH)

CELL_DCH to enhanced CELL_FACH state transition

The new timers are as follows:

BeD2EFachStateTransTimer: BE service state transition timer (DCH to E_FACH)

BeH2EFachStateTransTimer: BE service state transition timer (HS-DSCH to

E_FACH)

RtDH2EFachStateTransTimer: real-time service state transition timer (DCH or

HSPA to E_FACH)

CELL_DCH (CPC) to enhanced CELL_FACH state transition

The new timers are as follows:

BeCpc2EFachStateTransTimer: BE service state transition timer (CPC_HS-DSCH

to E_FACH)

RtCpc2EFachStateTransTimer: real-time service state transition timer

(CPC_HSPA to E_FACH)

The only impact of the following new state transitions is that new timers and thresholds to
trigger 4A are introduced:

CELL_FACH to CELL_DCH (CPC) state transition

The new thresholds are as follows:

BeF2CpcHTvmThd: event 4A threshold for BE service state transition (F/RACH to

CPC_HS-DSCH)

RtF2CpcTvmThd: event 4A threshold of real-time service state transition (F/RACH

to CPC_HSPA)

BeF2CpcETvmThd: event 4A threshold for BE service state transition (F/RACH to

CPC_E-DCH)

The new timers are as follows:

BeF2CpcHTvmTimeToTrig: event 4A trigger time for BE service state transition

(F/RACH to CPC_HS-DSCH)

RtF2CpcTvmTimeToTrig: event 4A trigger time for real-time service state

transition (F/RACH to CPC_HSPA)

BeF2CpcETvmTimeToTrig: event 4A trigger time for real-time service state

transition (F/RACH to CPC_E-DCH)

Enhanced CELL_FACH to CELL_DCH state transition

The new thresholds are as follows:

BeEFach2DTvmThd: event 4A threshold for BE service state transition (E_FACH to

DCH)

BeEFach2HTvmThd: event 4A threshold for BE service state transition (E_FACH

to HS-DSCH)

RtEFach2DHTvmThd: event 4A threshold for real-time service state transition

(E_FACH to DCH or HSPA)

The new timers are as follows:

BeEFach2DTvmTimeToTrig: event 4A trigger time for BE service state transition

(E-FACH to DCH)

BeEFach2HTvmTimeToTrig: event 4A trigger time for BE service state transition

(E_FACH to HS-DSCH)

RtEFach2DHTvmTimeToTrig: event 4A trigger time for real-time service state

transition (E_FACH to DCH/HSPA)

Enhanced CELL_FACH to CELL_DCH (CPC) state transition

The new thresholds are as follows:

BeEFach2CpcTvmThd: event 4A threshold for BE service state transition (E_FACH

to CPC_HS-DSCH)

RtEFach2CpcTvmThd: event 4A threshold for PS real-time service state transition

(E_FACH to CPC_HSPA)

The new timers are as follows:

BeEFach2CpcTvmTimeToTrig: event 4A trigger time for BE service state transition

(E_FACH to CPC_HS-DSCH)

RtEFach2CpcTvmTimeToTrig: event 4A trigger time for real-time service state

transition (E_FACH to CPC_HSPA)

The algorithm for the state transitions between enhanced CELL_FACH and CELL_PCH is
the same as that for the state transitions between CELL_FACH and CELL_PCH.

4.4 HSPA+ Flow Control

HSPA+ flow control is used to control HSPA+ data flows on the Iub and Iur interfaces.
After the introduction of flexible RLC PDU sizes in enhanced L2, both data frames and
control frames in flow control are changed in frame formats. HSPA+ uses new data frames
and capacity allocation control frames to enable the Iub and Iur interfaces to handle higher
rates on the Uu interface.
The transmission quality and efficiency in the enhanced CELL_FACH state are lower than
those in the CELL_DCH state. Therefore, when the UE in the enhanced CELL_FACH state
has huge amounts of data to transmit, it should be switched to the CELL_DCH state as soon
as possible. For this purpose, flow control of HSDPA users in the enhanced CELL_FACH
state is introduced in HSPA+.
The basic procedure of HSDPA users in the enhanced CELL_FACH state is described here.
When the UE is in the enhanced CELL_FACH state, the data of the UE can be carried on the
HS-DSCH. Within the RNC, the MAC-d sends the data to MAC-c common queues. Then, the
MAC-c sends the data to the MAC-ehs common queues at the NodeB through the Iub
interface. The NodeB calculates the capacity for each of the MAC-c common queues based on
the rate at the exit of each MAC-ehs common queue. In addition, the NodeB configures the
highest bit rate for each MAC-c stream to avoid overflow of the MAC-c common queues in
the case of Iub congestion. Thus, the MAC-c ensures that the total amount of data sent by all

its UEs in the enhanced CELL_FACH state does not exceed the capacity allocated to the
MAC-c common queues or the highest bit rates configured for the MAC-c common queues.
The state transition from enhanced CELL_FACH to CELL_DCH is performed by the RNC
mainly based on the RLC buffer occupancy. Therefore, the bandwidth allocated to the UE in
the enhanced CELL_FACH state should not be too high. If the bandwidth is too high, the data
in the RLC buffer cannot reach the threshold or trigger the transition to the CELL_DCH state.
On the other hand, the bandwidth allocated to the UE in the enhanced CELL_FACH state
should not be too low. If the bandwidth is too low, the RRC signaling delay increases.
Each UE in the enhanced CELL_FACH state is allocated the bandwidth specified by the
parameter BandWidthForFACH. The amount of data sent to the UE cannot exceed this fixed
bandwidth. In addition, differentiated services can be provided through the allocation of
different bandwidths based on service types and user priorities.

4.5 HSPA+ Scheduling and TFRC Selection

Scheduling determines the users for data transmission in each TTI on the Uu interface and
selects them in a certain order to provide good user experience and high system capacity.
TFRC selection is used to select an appropriate transmission rate by adjusting the modulation
scheme and coding rate based on the channel quality of the UE.
The scheduling and TRFC selection functionality needs to be upgraded to support the HSPA+
features. Only Enhanced CELL_FACH Operation introduces new parameters into scheduling
and TFRC selection.
The UE in the enhanced CELL_FACH state does not report ACK, NACK, or CQI in the
uplink. The HARQ processes of the UE use the blind retransmission mechanism. The
maximum number of retransmissions for the UE in Enhanced CELL_FACH Operation is
specified by the parameter MaxEfachHarqRt.
Among delay-insensitive queues, the enhanced CELL_FACH DTCH queue with the highest
priority is scheduled first. The maximum power and code resources that can be used by this
queue are limited to prevent the queue from consuming too many resources and affecting the
throughput of other CELL_DCH users. The maximum power resource is specified by the
parameter EfachDtchGbp. The maximum number of codes is not configurable and is fixed to
2.

4.6 HSPA+ Power Control

A new power control algorithm is introduced to control the HS-SCCH power of a UE in the
enhanced CELL_FACH state.
When the UE is in the enhanced CELL_FACH state, its data and control information are
transmitted through the HS-PDSCH and HS-SCCH. The UE in the enhanced CELL_FACH
state has no dedicated connection with the physical layer of the NodeB, and the UE does not
report the CQI, ACK, or NACK to the NodeB. Therefore, the algorithm for HS-SCCH power
control needs to be modified.
For the UE in the enhanced CELL_FACH state, the following scenarios need to be
considered:

The HS-PDSCH carries the BCCH.

In this scenario, the power allocated to the HS-SCCH is fixed. The power is specified by
the parameter BcchHsscchPower.

The HS-PDSCH carries user data.

In this scenario, the HS-SCCH power is fixed or controlled on the basis of CQI.

If the parameter HsSssccPwrCMInEfach is set to the default value FIXED, the HSSCCH power is specified by the parameter BcchHsscchPower, which is a fixed
offset from the P-CPICH power.

If the parameter HsSssccPwrCMInEfach is set to CQI, the HS-SCCH works under

CQI-based power control. Here, the CQI is derived from the measured CPICH Ec/No
in the HS-DSCH data frame.
Note that the CQI-based power control in the enhanced CELL_FACH state is
different from that in the CELL_DCH state.

4.7 HSPA+ Handover

4.7.1 Overview
The basic mechanisms of handover remain unchanged after the introduction of HSPA+. New
functions are added to handle the scenario where the source cell and target cell support
different HSPA+ features or where admission control prevents the UE from using the
preferred configuration.
Figure 4.7.1.I.1.1.1 shows the procedure of HSPA+ configuration during the handover.
Figure 4.7.1.I.1.1.1 Procedure of HSPA+ configuration during the handover

The procedure of HSPA+ configuration during the handover is as follows:

1

In the preselection phase (during handover decision)

The feature configuration is determined on the basis of the configuration provided for the
UE in the source cell and the capability of the target cell.

2.

In the fallback phase (during handover execution)

If the UE is not allowed to use the preselected feature configuration, a fallback
configuration is selected.

3.

In the retry phase (after handover)

After the handover, the UE may retry to use the configuration that fails to be admitted in
the fallback or preselection phase.

4.7.2 Preselection Phase

Preselection is handled during handover decision. In the preselection phase, the RNC
preselects a feature configuration in the target cell based on the available configuration in the
target cell and the actual configuration in the source cell.

Preselection for 64QAM, MIMO, or Enhanced L2

If the target cell supports the same configuration as the source cell and the bearer scheme
allows the target cell to continue using the configuration of the source cell, the handover
algorithm preselects this configuration for the target cell. Otherwise, the handover algorithm
attempts to preselect another available configuration for the UE.
Assume that the UE is configured with MIMO in the source cell. If the target cell supports
MIMO and the bearer scheme allows MIMO in the target cell, then the handover algorithm
preselects MIMO in the target cell for the UE. If the bearer scheme does not allow MIMO in
the target cell, the handover algorithm attempts to preselect another configuration for the UE
as suggested by the bearer scheme.

Preselection for DTX/DRX

During an intra-frequency soft handover, the handover algorithm preselects DTX/DRX in the
target cell for the UE if all the cells in the active set are configured with DTX/DRX and the
target cell supports DTX/DRX.
During an intra- or inter-frequency hard handover, the handover algorithm preselects
DTX/DRX in the target cell for the UE if the target cell supports DTX/DRX and the bearer
scheme allows DTX/DRX in the target cell.

Preselection for HS-SCCH Less Operation

If the UE is configured with HS-SCCH Less Operation, and the bearer scheme allows HSSCCH Less Operation in the target cell, the handover algorithm preselects HS-SCCH Less
Operation in the target cell for the UE.

4.7.3 Fallback Phase

Fallback is handled during handover execution. In the fallback phase, the RNC performs
admission control based on the preselected feature configuration. If the admission fails, the
configuration is degraded from MIMO/64QAM to HSDPA (enhanced L2), from HS-DSCH to
DCH, or from CPC to non-CPC.

4.7.4 Retry Phase

Retry is handled after handover. In the retry phase, the UE retries to use the configuration that
fails to be admitted in the fallback or preselection phase. The RNC tries to promote the
configuration to the highest configuration. The possible promotion is from HSDPA to
MIMO/64QAM, from DCH to HS-DSCH, or from non-CPC to CPC.
The HSPA+ features that can be retried are specified by the parameter RetryCapability. If
MIMO, 64QAM, L2_ENHANCE, DTX_DRX, or HSSCCH_LESS_OPERATION of the
parameter is selected and the UE is not configured with it, then the algorithm can retry the
corresponding configuration. Otherwise, no retry is performed.

To avoid ping-pong handovers, the handover protection timer (ChannelRetryHoTimerLen)

is started after handover. After the timer expires, the algorithm retries the configuration. If the
retry fails, the retry timer (ChannelRetryTimerLen) is started for periodic retry attempts.

HSPA+ Parameters

5.1 Description
Table 5.1.1.I.1.1.1.1 HSPA+ parameter description
Parameter ID

Description

RtF2CpcTvmTimeToTrig

This parameter specifies the occurrence time of 4A event for triggering the
transition from FACH to DCH or HSPA that adopts the CPC function. This
parameter prevents unnecessary reports that are caused by traffic volume
instability from being triggered. If the value of this parameter is too high,
the period of reporting 4A event is delayed and congestion may occur over
the common channel.

RtF2CpcTvmThd

This parameter specifies the threshold of the traffic volume of 4A event for
triggering the transition from FACH to DCH or HSPA that adopts the CPC
function. If the value of this parameter is too high, congestion may occur
over the common channel.

RtEFach2DHTvmTimeToTrig

This parameter specifies the occurrence time of 4A event for triggering the
transition from E_FACH to DCH or HSPA. This parameter prevents
unnecessary reports that are caused by traffic volume instability from being
triggered. If the value of this parameter is too high, the period of reporting
4A event is delayed and congestion may occur over the common channel.

RtEFach2DHTvmThd

This parameter specifies the threshold of the traffic volume of 4A event for
triggering the transition from E_FACH to DCH or HSPA. If the value of
this parameter is too high, congestion may occur over the common channel.

RtEFach2CpcTvmTimeToTri
g

This parameter specifies the occurrence time of 4A event for triggering the
transition from E_FACH to DCH or HSPA that adopts the CPC function.
This parameter prevents unnecessary reports that are caused by traffic
volume instability from being triggered. If the value of this parameter is too
high, the period of reporting 4A event is delayed and congestion may occur
over the common channel.

RtEFach2CpcTvmThd

This parameter specifies the threshold of the traffic volume of 4A event for
triggering the transition from E_FACH to DCH or HSPA that adopts the

Parameter ID

Description

CPC function. If the value of this parameter is too high, congestion may
occur over the common channel.
RtDH2EFachStateTransTimer

Timer for state transition from DCH or HSPA to E_FACH of real-time

services, used to detect whether a real-time service UE in CELL_DCH state
is in stable low activity state. The too small parameter cannot probably
confirm that a UE is in relatively stable low activity state, but the too big
will waste the dedicated channel resource. This parameter should be set
based on the real-time service model.

RtCpc2FStateTransTimer

Timer for state transition from CPC_HSPA to FACH of real-time services,

used to detect whether a real-time service UE that adopts the CPC function
in CELL_DCH(with CPC_HSPA) state is in stable low activity state. The
too small parameter cannot probably confirm that a UE is in relatively
stable low activity state, but the too big will waste the dedicated channel
resource. This parameter should be set based on the real-time service model.

RtCpc2EFachStateTransTimer

Timer for state transition from CPC_HSPA to E_FACH of real-time

services, used to detect whether a real-time service UE that adopts the CPC
function in CELL_DCH(with CPC_HSPA) state is in stable low activity
state. The too small parameter cannot probably confirm that a UE is in
relatively stable low activity state, but the too big will waste the dedicated
channel resource. This parameter should be set based on the real-time
service model.

RetryCapability

Each bit indicates whether to retry the corresponding HSPA function. If a

bit is set the 1, then the RNC retries the corresponding HSPA function if the
UE is not using the corresponding HSPA function. Otherwise, no retry is
performed.

MaxEfachHarqRt

Maximum Efach Retransmission Times

MapSwitch

Service mapping strategy switch.

1) MAP_HSUPA_TTI_2MS_SWITCH: When the switch is on, 2 ms TTI is
supported for HSUPA.
2) MAP_INTER_RAT_PS_IN_CHANLE_LIMIT_SWITCH: When the
switch is on, the PS services are transmitted on the DCH during the 2G-to3G handover. When the switch is not on, the PS services can be transmitted
on suitable channels according to the algorithm parameter configured for
the RNC during the 2G to 3G handover.
3) MAP_PS_BE_ON_E_FACH_SWITCH: When the switch is on, the PS
BE services can be transmitted on the E-FACH.
4) MAP_PS_STREAM_ON_E_FACH_SWITCH: When the switch is on,
the PS streaming services can be transmitted on the E-FACH.
5) MAP_PS_STREAM_ON_HSDPA_SWITCH: When the switch is on, a
PS streaming service is mapped on the HS-DSCH if the DL maximum rate
of the service is greater than or equal to the HSDPA threshold for streaming
services.
6) MAP_PS_STREAM_ON_HSUPA_SWITCH: When the switch is on, a
PS streaming service is mapped on the E-DCH if the UL maximum rate of
the service is greater than or equal to the HSUPA threshold for streaming
services.
7) MAP_SRB_6800_WHEN_RAB_ON_HSDSCH_SWITCH: When the
switch is on, the signaling is transmitted at a rate of 6.8 kbit/s if all the
downlink traffic is on the HSDPA channel.

Parameter ID

Description

HsScchPwrCMInEfach

EFACH HS-SCCH Power Control Method

HspaPlusSwitch

If the corresponding item of this parameter is selected, it indicates that the

HspaPlusSwitch is enabled. Otherwise, it indicates that the HspaPlusSwitch
is not enabled. Note that the actual use of this function is restricted by the
license and the physical capability of the NodeB. The EFACH/MIMO
switch specifies whether this EFACH/MIMO service is supported in the
cell. The setting of the EFACH/MIMO switch does not affect the EFACH in
the cell and the establishment of the MIMO cell.

HSPAPlusSelection

According to the relevant protocols, MIMO, 64QAM, and HS-SCCH Less

Operation cannot be configured concurrently to the same UE. This
parameter specifies the configuration preference of MIMO, 64QAM, and
HS-SCCH Less Operation when both the UE and the cell support these
three features.

EFachSwitch

This parameter specifies whether the RRC connection is established

preferentially on the E-FACH. If this parameter is set to ON and both the
UE and the serving cell support E-FACH, then the RRC connection is
established preferentially on the E-FACH, regardless of the setting of
SigChType. According to the related protocols, the UE cannot transmit
signals over the FACH if both the UE and the cell support E-FACH. Thus, if
this parameter is set to OFF and both the UE and the serving cell support EFACH, then the RRC connection can only be established on the non-FACH,
regardless of the setting of SigChType.

EFACHDTCHGBP

This parameter specifies the minimum guaranteed power of the DTCH

mapped onto the EFACH.

ChannelRetryTimerLen

This parameter specifies the value of the channel retry timer. The timer will
start after traffic is set up or reconfigured, if higher technique is available.
Channel retry will be performed after this timer expires. If the value of the
parameter is set to 0, channel retry cannot be performed.

ChannelRetryHoTimerLen

This parameter specifies the value of the handover protection timer. If

services can be set up on channels based on a higher technique after channel
handover is completed, the handover protection timer will be started. When
the timer expires, the RNC will try to carry services on channels based on a
higher technique. Channel retry cannot be performed before this timer
expires.

CfgSwitch

Channel configuration strategy switch.

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_MIMO_SWITCH: When the switch is on, MIMO can be
configured for the HSDPA service.
4) CFG_HSPA_DTX_DRX_SWITCH: When the switch is on, DTX_DRX
can be configured for the HSDPA service.
5) CFG_HSPA_HSSCCH_LESS_OP_SWITCH: When the switch is on,
HS-SCCH Less Operation can be configured for the HSDPA service.
6) CFG_IMS_SUPPORT_SWITCH: When the switch is on and the IMS
license is activated, the RNC supports IMS signaling.

Parameter ID

Description

7) CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH: When the switch

is on, DL lossless RLC PDU size change is supported.
8) 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.
9) CFG_MULTI_RAB_SWITCH: When the switch is on, the RNC supports
multi-RABs combinations such as 2CS, 2CS+1PS, 1CS+2PS, and 2PS.
10) 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.
11) CFG_PDCP_RFC2507_HC_SWITCH: When the switch is on and the
PDCP IPHC license is activated, the PDCP IPHC header compression
algorithm is used for the RNC.
12) CFG_PDCP_RFC3095_HC_SWITCH: When the switch is on and the
PDCP ROHC license is activated, the PDCP ROHC header compression
algorithm is used for the RNC.
BeH2EFachStateTransTimer

Timer for state transition from HS-DSCH to E_FACH of BE services, used

to detect whether a BE UE in CELL_DCH(with HS-DSCH) state is in
stable low activity state. The too small parameter cannot probably confirm
that a UE is in relatively stable low activity state, but the too big will waste
the dedicated channel resource. This parameter should be set based on the
BE service model.

BeF2CpcHTvmTimeToTrig

This parameter specifies the occurrence time of 4A event for triggering the
transition from FACH to CPC_HS-DSCH. This parameter prevents
unnecessary reports that are caused by traffic volume instability from being
triggered. If the value of this parameter is too high, the period of reporting
4A event is delayed and congestion may occur over the common channel.

BeF2CpcHTvmThd

This parameter specifies the threshold of the traffic volume of 4A event for
triggering the transition from FACH to CPC_HS-DSCH. If the value of this
parameter is too high, congestion may occur over the common channel.

BeF2CpcETvmTimeToTrig

This parameter specifies the occurrence time of 4A event for triggering the
transition from FACH to E-DCH that adopts the CPC function. This
parameter prevents unnecessary reports that are caused by traffic volume
instability from being triggered. If the value of this parameter is too high,
the period of reporting 4A event is delayed and congestion may occur over
the common channel.

BeF2CpcETvmThd

This parameter specifies the threshold of the traffic volume of 4A event for
triggering the transition from FACH to E-DCH that adopts the CPC
function. If the value of this parameter is too high, congestion may occur
over the common channel.

BeEFach2HTvmTimeToTrig

This parameter specifies the occurrence time of 4A event for triggering the
transition from E_FACH to HS-DSCH. This parameter prevents
unnecessary reports that are caused by traffic volume instability from being
triggered. If the value of this parameter is too high, the period of reporting
4A event is delayed and congestion may occur over the common channel.

BeEFach2HTvmThd

This parameter specifies the threshold of the traffic volume of 4A event for
triggering the transition from E_FACH to HS-DSCH. If the value of this
parameter is too high, congestion may occur over the common channel.

Parameter ID

Description

BeEFach2DTvmTimeToTrig

This parameter specifies the occurrence time of 4A event for triggering the
transition from E_FACH to DCH. This parameter prevents unnecessary
reports that are caused by traffic volume instability from being triggered. If
the value of this parameter is too high, the period of reporting 4A event is
delayed and congestion may occur over the common channel.

BeEFach2DTvmThd

This parameter specifies the threshold of the traffic volume of 4A event for
triggering the transition from E_FACH to DCH. If the value of this
parameter is too high, congestion may occur over the common channel.

BeEFach2CpcTvmTimeToTri
g

This parameter specifies the occurrence time of 4A event for triggering the
transition from E_FACH to CPC_HS-DSCH. This parameter prevents
unnecessary reports that are caused by traffic volume instability from being
triggered. If the value of this parameter is too high, the period of reporting
4A event is delayed and congestion may occur over the common channel.

BeEFach2CpcTvmThd

This parameter specifies the threshold of the traffic volume of 4A event for
triggering the transition from E_FACH to CPC_HS-DSCH. If the value of
this parameter is too high, congestion may occur over the common channel.

BeD2EFachStateTransTimer

Timer for state transition from DCH to E_FACH of BE services, used to

detect whether a BE UE in CELL_DCH (with DCH) state is in stable low
activity state. The too small parameter cannot probably confirm that a UE is
in relatively stable low activity state, but the too big will waste the
dedicated channel resource. This parameter should be set based on the BE
service model.

BeCpc2FStateTransTimer

Timer for state transition from CPC_HS-DSCH to FACH of BE services,

used to detect whether a BE UE in CELL_DCH(with CPC_HS-DSCH)
state is in stable low activity state. The too small parameter cannot probably
confirm that a UE is in relatively stable low activity state, but the too big
will waste the dedicated channel resource. This parameter should be set
based on the BE service model.

BeCpc2EFachStateTransTime
r

Timer for state transition from CPC_HS-DSCH to E_FACH of BE services,

used to detect whether a BE UE in CELL_DCH(with CPC_HS-DSCH)
state is in stable low activity state. The too small parameter cannot probably
confirm that a UE is in relatively stable low activity state, but the too big
will waste the dedicated channel resource. This parameter should be set
based on the BE service model.

BcchHsscchPower

This parameter specifies the power of the HS-SCCH adopted by the BCCH
mapped onto the EFACH.

BandWidthForFACH

This parameter specifies the maximum available bandwidth for each traffic
class in the Cell_FACH state with the downlink HSDSCH in use. If the
actual data flow exceeds the maximum bandwidth, the traffic is buffered so
that the buffer occupancy is increased. As a result, the state transition from
Cell-FACH to DCH occurs. This parameter should be set according to the
traffic class.

5.2 Values and Ranges

Table 5.2.1.I.1.1.1.1 HSPA+ parameter values and parameter ranges
Parameter ID

Default
Value

GUI Value Range

Actual Value Range

Unit

MML
Command

NE

RtF2CpcTvm
TimeToTrig

D0, D10, D20, D40,

D60, D80, D100,
D120, D160, D200,
D240, D320, D640,
D1280, D2560, D5000

0, 10, 20, 40, 60, 80,

100, 120, 160, 200,
240, 320, 640, 1280,
2560, 5000

ms

SET
UESTATETR
ANS(Optional
)

RNC

RtF2CpcTvm
Thd

D16, D32, D64, D128,

D256, D512, D1024,
D2k, D3k, D4k, D6k,
D8k, D12k, D16k,
D24k, D32k, D48k,
D64k, D96k, D128k,
D192k, D256k, D384k,
D512k, D768k

16, 32, 64, 128, 256,

512, 1024, 2k, 3k,
4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k,
96k, 128k, 192k,
256k, 384k, 512k,
768k

byte

SET
UESTATETR
ANS(Optional
)

RNC

RtEFach2DH
TvmTimeToTr
ig

D0, D10, D20, D40,

D60, D80, D100,
D120, D160, D200,
D240, D320, D640,
D1280, D2560, D5000

0, 10, 20, 40, 60, 80,

100, 120, 160, 200,
240, 320, 640, 1280,
2560, 5000

ms

SET
UESTATETR
ANS(Optional
)

RNC

RtEFach2DH
TvmThd

D16, D32, D64, D128,

D256, D512, D1024,
D2k, D3k, D4k, D6k,
D8k, D12k, D16k,
D24k, D32k, D48k,
D64k, D96k, D128k,
D192k, D256k, D384k,
D512k, D768k

16, 32, 64, 128, 256,

512, 1024, 2k, 3k,
4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k,
96k, 128k, 192k,
256k, 384k, 512k,
768k

byte

SET
UESTATETR
ANS(Optional
)

RNC

RtEFach2Cpc
TvmTimeToTr
ig

D0, D10, D20, D40,

D60, D80, D100,
D120, D160, D200,
D240, D320, D640,
D1280, D2560, D5000

0, 10, 20, 40, 60, 80,

100, 120, 160, 200,
240, 320, 640, 1280,
2560, 5000

ms

SET
UESTATETR
ANS(Optional
)

RNC

RtEFach2Cpc
TvmThd

D16, D32, D64, D128,

D256, D512, D1024,
D2k, D3k, D4k, D6k,
D8k, D12k, D16k,
D24k, D32k, D48k,
D64k, D96k, D128k,
D192k, D256k, D384k,
D512k, D768k

16, 32, 64, 128, 256,

512, 1024, 2k, 3k,
4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k,
96k, 128k, 192k,
256k, 384k, 512k,
768k

byte

SET
UESTATETR
ANS(Optional
)

RNC

RtDH2EFach
StateTransTim
er

1~65535

1~65535

SET
UESTATETR
ANSTIMER(
Optional)

RNC

RtCpc2FState

1~65535

1~65535

SET

RNC

Parameter ID

Default
Value

GUI Value Range

Actual Value Range

Unit

TransTimer

MML
Command

NE

UESTATETR
ANSTIMER(
Optional)

RtCpc2EFach
StateTransTim
er

1~65535

1~65535

SET
UESTATETR
ANSTIMER(
Optional)

RNC

RetryCapabilit
y

SRB_OVER_HSDPA,
SRB_OVER_HSUPA,
TTI_2MS, MIMO,
64QAM,
L2_ENHANCE,
DTX_DRX,
HSSCCH_LESS_OPE
RATION

None

None

SET
FRC(Optional
)

RNC

MaxEfachHar
qRt

0~10

0~10

Times

SET
MACHSPAR
A(Optional)

Node
B

MapSwitch

MAP_HSUPA_TTI_2
MS_SWITCH,
MAP_INTER_RAT_P
S_IN_CHANLE_LIMI
T_SWITCH,
MAP_PS_BE_ON_E_
FACH_SWITCH,
MAP_PS_STREAM_
ON_E_FACH_SWITC
H,
MAP_PS_STREAM_
ON_HSDPA_SWITCH
,
MAP_PS_STREAM_
ON_HSUPA_SWITCH
,
MAP_SRB_6800_WH
EN_RAB_ON_HSDS
CH_SWITCH

MAP_HSUPA_TTI
_2MS_SWITCH,
MAP_INTER_RAT
_PS_IN_CHANLE_
LIMIT_SWITCH,
MAP_PS_BE_ON_
E_FACH_SWITCH,
MAP_PS_STREAM
_ON_E_FACH_SW
ITCH,
MAP_PS_STREAM
_ON_HSDPA_SWI
TCH,
MAP_PS_STREAM
_ON_HSUPA_SWI
TCH,
MAP_SRB_6800_
WHEN_RAB_ON_
HSDSCH_SWITCH

None

SET
CORRMALG
OSWITCH(O
ptional)

RNC

HsScchPwrC
MInEfach

CQI (CQI-based power

control), FIXED (Fixed
Power)

CQI, FIXED

None

SET
MACHSPAR
A(Optional)

Node
B

HspaPlusSwit
ch

64QAM, MIMO,
E_FACH, DTX_DRX,
HS_SCCH_LESS_OP
ERATION,
L2ENHANCED

64QAM,MIMO,
E_FACH,
DTX_DRX,
HS_SCCH_LESS_
OPERATION,
L2ENHANCED

None

ADD
CELLALGOS
WITCH(Optio
nal)

RNC

HSPAPlusSele
ction

MIMO, 64QAM

MIMO, 64QAM

None

SET
FRC(Optional

RNC

Parameter ID

Default
Value

GUI Value Range

Actual Value Range

Unit

MML
Command

NE

)
EFachSwitch

OFF, ON

OFF, ON

None

SET
RRCESTCAU
SE(Optional)

RNC

EFACHDTCH
GBP

10

-350~150

-35~15, step:0.1

dB

ADD
CELLEFACH
(Optional)

RNC

ChannelRetry
TimerLen

0~180

0~180

SET
COIFTIMER(
Optional)

RNC

ChannelRetry
HoTimerLen

0~999

0~999

SET
COIFTIMER(
Optional)

RNC

CfgSwitch

CFG_DL_BLIND_DE
TECTION_SWITCH,
CFG_HSDPA_64QAM
_SWITCH,
CFG_HSDPA_MIMO_
SWITCH,
CFG_HSPA_DTX_DR
X_SWITCH,
CFG_HSPA_HSSCCH
_LESS_OP_SWITCH,
CFG_IMS_SUPPORT
_SWITCH,
CFG_LOSSLESS_DL
RLC_PDUSIZECHG_
SWITCH,
CFG_LOSSLESS_RE
LOC_CFG_SWITCH,
CFG_MULTI_RAB_S
WITCH,
CFG_PDCP_IPV6_HE
AD_COMPRESS_SW
ITCH,
CFG_PDCP_RFC2507
_HC_SWITCH,
CFG_PDCP_RFC3095
_HC_SWITCH

CFG_DL_BLIND_
DETECTION_SWI
TCH,
CFG_HSDPA_64Q
AM_SWITCH,
CFG_HSDPA_MIM
O_SWITCH,
CFG_HSPA_DTX_
DRX_SWITCH,
CFG_HSPA_HSSC
CH_LESS_OP_SWI
TCH,
CFG_IMS_SUPPO
RT_SWITCH,
CFG_LOSSLESS_
DLRLC_PDUSIZE
CHG_SWITCH,
CFG_LOSSLESS_
RELOC_CFG_SWI
TCH,
CFG_MULTI_RAB
_SWITCH,
CFG_PDCP_IPV6_
HEAD_COMPRES
S_SWITCH,
CFG_PDCP_RFC25
07_HC_SWITCH,
CFG_PDCP_RFC30
95_HC_SWITCH

None

SET
CORRMALG
OSWITCH(O
ptional)

RNC

BeH2EFachSt
ateTransTimer

1~65535

1~65535

SET
UESTATETR
ANSTIMER(
Optional)

RNC

BeF2CpcHTv
mTimeToTrig

D0, D10, D20, D40,

D60, D80, D100,

0, 10, 20, 40, 60, 80,

100, 120, 160, 200,

ms

SET
UESTATETR

RNC

Parameter ID

Default
Value

GUI Value Range

Actual Value Range

D120, D160, D200,

D240, D320, D640,
D1280, D2560, D5000

240, 320, 640, 1280,

2560, 5000

Unit

MML
Command

NE

ANS(Optional
)

BeF2CpcHTv
mThd

D16, D32, D64, D128,

D256, D512, D1024,
D2k, D3k, D4k, D6k,
D8k, D12k, D16k,
D24k, D32k, D48k,
D64k, D96k, D128k,
D192k, D256k, D384k,
D512k, D768k

16, 32, 64, 128, 256,

512, 1024, 2k, 3k,
4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k,
96k, 128k, 192k,
256k, 384k, 512k,
768k

byte

SET
UESTATETR
ANS(Optional
)

RNC

BeF2CpcETv
mTimeToTrig

D0, D10, D20, D40,

D60, D80, D100,
D120, D160, D200,
D240, D320, D640,
D1280, D2560, D5000

0, 10, 20, 40, 60, 80,

100, 120, 160, 200,
240, 320, 640, 1280,
2560, 5000

ms

SET
UESTATETR
ANS(Optional
)

RNC

BeF2CpcETv
mThd

D16, D32, D64, D128,

D256, D512, D1024,
D2k, D3k, D4k, D6k,
D8k, D12k, D16k,
D24k, D32k, D48k,
D64k, D96k, D128k,
D192k, D256k, D384k,
D512k, D768k

16, 32, 64, 128, 256,

512, 1024, 2k, 3k,
4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k,
96k, 128k, 192k,
256k, 384k, 512k,
768k

byte

SET
UESTATETR
ANS(Optional
)

RNC

BeEFach2HT
vmTimeToTri
g

D0, D10, D20, D40,

D60, D80, D100,
D120, D160, D200,
D240, D320, D640,
D1280, D2560, D5000

0, 10, 20, 40, 60,

80, 100, 120, 160,
200, 240, 320, 640,
1280, 2560, 5000

ms

SET
UESTATETR
ANS(Optional
)

RNC

BeEFach2HT
vmThd

D16, D32, D64, D128,

D256, D512, D1024,
D2k, D3k, D4k, D6k,
D8k, D12k, D16k,
D24k, D32k, D48k,
D64k, D96k, D128k,
D192k, D256k, D384k,
D512k, D768k

16, 32, 64, 128, 256,

512, 1024, 2k, 3k,
4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k,
96k, 128k, 192k,
256k, 384k, 512k,
768k

byte

SET
UESTATETR
ANS(Optional
)

RNC

BeEFach2DT
vmTimeToTri
g

D0, D10, D20, D40,

D60, D80, D100,
D120, D160, D200,
D240, D320, D640,
D1280, D2560, D5000

0, 10, 20, 40, 60, 80,

100, 120, 160, 200,
240, 320, 640, 1280,
2560, 5000

ms

SET
UESTATETR
ANS(Optional
)

RNC

BeEFach2DT
vmThd

D16, D32, D64, D128,

D256, D512, D1024,
D2k, D3k, D4k, D6k,
D8k, D12k, D16k,
D24k, D32k, D48k,
D64k, D96k, D128k,

16, 32, 64, 128, 256,

512, 1024, 2k, 3k,
4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k,
96k, 128k, 192k,
256k, 384k, 512k,

byte

SET
UESTATETR
ANS(Optional
)

RNC

Parameter ID

Default
Value

GUI Value Range

Actual Value Range

D192k, D256k, D384k,

D512k, D768k

768k

Unit

MML
Command

NE

BeEFach2Cpc
TvmTimeToTr
ig

D0, D10, D20, D40,

D60, D80, D100,
D120, D160, D200,
D240, D320, D640,
D1280, D2560, D5000

0, 10, 20, 40, 60, 80,

100, 120, 160, 200,
240, 320, 640, 1280,
2560, 5000

ms

SET
UESTATETR
ANS(Optional
)

RNC

BeEFach2Cpc
TvmThd

D16, D32, D64, D128,

D256, D512, D1024,
D2k, D3k, D4k, D6k,
D8k, D12k, D16k,
D24k, D32k, D48k,
D64k, D96k, D128k,
D192k, D256k, D384k,
D512k, D768k

16, 32, 64, 128, 256,

512, 1024, 2k, 3k,
4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k,
96k, 128k, 192k,
256k, 384k, 512k,
768k

byte

SET
UESTATETR
ANS(Optional
)

RNC

BeD2EFachSt
ateTransTimer

1~65535

1~65535

SET
UESTATETR
ANSTIMER(
Optional)

RNC

BeCpc2FState
TransTimer

1~65535

1~65535

SET
UESTATETR
ANSTIMER(
Optional)

RNC

BeCpc2EFach
StateTransTim
er

1~65535

1~65535

SET
UESTATETR
ANSTIMER(
Optional)

RNC

BcchHsscchP
ower

-30

-350~150

-35~15, step:0.1

dB

ADD
CELLEFACH
(Optional)

RNC

BandWidthFo
rFACH

1~1000

1~1000

kbit/s

SET
FACHBAND
WIDTH(Opti
onal)

RNC

The Default Value column is valid for only the optional parameters.
The symbol "-" indicates that no default value is available.

Reference Documents

The following lists the reference documents related to the feature:

1.

3GPP TS 25.101: User Equipment (UE) radio transmission and reception (FDD)

2.

3GPP TS 25.211: Physical channels and mapping of transport channels onto physical
channels (FDD)

3.

3GPP TS 25.212: Multiplexing and channel coding (FDD)

4.

3GPP TS 25.213: Spreading and modulation (FDD)

5.

3GPP TS 25.214: Physical layer procedures (FDD)

6.

3GPP TS 25.308, "UTRA High Speed Downlink Packet Access (HSPDA); Overall
description"

7.

3GPP TS 25.309: FDD Enhanced Uplink

8.

3GPP TS 25.301: Radio Interface Protocol Architecture

9.

3GPP TS 25.302: Services provided by the physical layer

10. 3GPP TS 25.321: Medium Access Control (MAC) protocol specification

11. 3GPP TS 25.420: UTRAN Iur interface general aspects and principles
12. 3GPP TS 25.423: UTRAN Iur interface RNSAP signaling
13. 3GPP TS 25.430: UTRAN Iub interface: general aspects and principles
14. 3GPP TS 25.433: UTRAN Iub interface NBAP signaling
15. HSDPA Parameter Description
16. HSUPA Parameter Description
17. Radio Bearers Parameter Description
18. Transmission Resource Management Parameter Description
19. Power Control Parameter Description
20. Handover Parameter Description
21. Rate Control Parameter Description
22. Basic Feature Description of Huawei UMTS RAN11.0 V1.5
23. Optional Feature Description of Huawei UMTS RAN11.0 V1.5