ZTE - UMTS HSUPA Intro Feature Guide PDF

HSUPA Introduction Feature
Guide
WCDMA RAN
HSUPA Introduction Feature Guide

Version Date Author Reviewer Revision History
1. 1 Feature Attributes: Modified the

version information.
2. 4.24.2 Parameter Configurations:
Modified the OMC path.
3. 3.3.5 HSUPA 2ms TTI: Added 2ms
E-TTI Support Indicator for neighboring
RNC cell.
4. 3.3.10 ZWF25-01-024 HSUPA
5.76 Mbps Peak Bit Rate: Added
E-DCH SF Capability for neighboring
V7.0 2012-5-21 Huangmeiqing Xiang Zhijian
RNC cell.
5. 3.5.1 Introduction to HARQ: Added
E-DCH HARQ Combining Capability for
neighboring RNC cell.
6. 4.2.11 E-DCH HARQ Combining
Capability (Neighboring RNC Cell)
7. 4.2.12 E-DCH SF Capability
(Neighboring RNC Cell)
8. 4.2.13 2ms E-TTI Support Indicator
(Neighboring RNC Cell)
1 Feature Attributes: Modified the version
V8.0 2012-12-06 Huangmeiqing Xiang Zhijian
information.
1. Added Feature ID.
V8.5 2013-12-03 Huangmeiqing Xiang Zhijian 2. Added ZWF25-01-005 Flexible HSUPA
Deployment.
,
© 2014 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary 1

TABLE OF CONTENTS
1 Feature Attributes ........................................................................................... 5
2 Overview ............................................................................................................ 5
3 Feature Introduction.......................................................................................... 6
3.1 Architecture of HSUPA ........................................................................................ 6
3.2 Basic Principle of HSUPA .................................................................................... 7
3.2.1 Physical Channels Introduced to HSUPA ............................................................. 7
3.2.2 Basic Principles of HSUPA ................................................................................ 11
3.3 Basic Functions of HSUPA ................................................................................ 15
3.3.1 ZWF25-01-005 HSUPA Common Carrier with R99 ............................................ 15
3.3.2 ZWF25-01-005 HSUPA Dedicated Carrier ......................................................... 15
3.3.3 ZWF25-01-003 HSUPA Cell Indicator in Idle Mode ............................................ 16
3.3.4 ZWF25-01-004 HSUPA UE Category Support ................................................... 16
3.3.5 ZWF25-01-024 HSUPA 2ms TTI........................................................................ 17
3.3.6 ZWF25-01-014 HSUPA HARQ .......................................................................... 17
3.3.7 ZWF25-01-021 HSUPA 1.45Mbps Peak Bit Rate .............................................. 18
3.3.8 ZWF25-01-022 HSUPA 16 Users per Cell ......................................................... 18
3.3.9 ZWF25-01-023 HSUPA 2 Mbps Peak Bit Rate .................................................. 18
3.3.10 ZWF25-01-024 HSUPA 5.76 Mbps Peak Bit Rate.............................................. 18
3.3.14 ZWF25-02-001 PS Interactive/Background Service over HSUPA ...................... 19
3.3.15 ZWF25-02-002 PS Streaming Service over HSUPA .......................................... 20
3.3.16 ZWF25-02-003 RAB Combination for CS over DCH and PS over HSUPA ......... 20
3.3.17 ZWF25-02-004 RAB Combination for Multiple Packet Data Services over
HSUPA .............................................................................................................. 21
3.3.18 ZWF25-02-011 SRB over HSUPA ..................................................................... 21
3.3.19 ZWF25-05-002 HSUPA Nominal Bit Rate for I/B Service ................................... 21
3.3.20 ZWF25-01-030 HSUPA 192 Users per Cell ....................................................... 21
3.4 Key Algorithms in the RNC ................................................................................ 22
3.4.1 HSUPA Mobility Management ............................................................................ 22
3.4.2 ZWF25-04-005 HSUPA Dynamic Channel Adjustment ...................................... 26
3.4.3 ZWF25-04-007 Code Allocation for HSUPA ....................................................... 26
3.4.4 ZWF25-04-006 Power Allocation for HSUPA ..................................................... 26

3.4.5 ZWF25-04-001 Admission Control for HSUPA Service ...................................... 26

3.4.6 ZWF25-04-002 Overload Control for HSUPA Service ........................................ 27
3.4.7 ZWF25-04-003 Load Balance for HSUPA Service ............................................. 27
3.4.8 ZWF25-04-004 Congestion Control Strategy for HSUPA ................................... 27
3.4.9 ZWF25-05-001 QoS Mapping for HSUPA Service ............................................. 27
3.5 Key Calculations and Algorithms in Node B ....................................................... 27
3.5.1 Introduction to HARQ ......................................................................................... 27
3.5.2 Node B Based Quick Packet Scheduling Technology ........................................ 29
3.5.3 ZWF25-04-010 HSUPA E-AGCH CLPC ............................................................ 29
3.5.4 ZWF25-04-011 HSUPA E-RGCH/HICH CLPC................................................... 31
4 Parameters and Configurations ................................................................. 32

4.1 Parameter List ................................................................................................... 32
4.2 Parameter Configurations .................................................................................. 33
4.2.1 HSPA Support Method ....................................................................................... 33
4.2.2 HSPA Support Method (Neighboring RNC Cell) ................................................. 33
4.2.3 E-DCH Uplink Nominal Bit Rate ......................................................................... 34
4.2.4 Support HSUPA Iur Interface Process ............................................................... 34
4.2.5 Support Hard Handover DSCR .......................................................................... 34
4.2.6 HARQ RV Configuration .................................................................................... 34
4.2.7 Four E-DPDCHs Allowed Indicator .................................................................... 35
4.2.8 Switch of supporting SRB on E-DCH ................................................................. 35
4.2.9 Cell HSUPA 2ms TTI Support Indicator ............................................................. 35
4.2.10 HSUPA Function Status ..................................................................................... 35
4.2.11 E-DCH HARQ Combining Capability (Neighboring RNC Cell) ............................ 36
4.2.12 E-DCH SF Capability (Neighboring RNC Cell) ................................................... 36
4.2.13 2ms E-TTI Support Indicator (Neighboring RNC Cell) ........................................ 36
5 Counter and Alarm .......................................................................................... 37

5.1 Counter List ....................................................................................................... 37
5.1.1 Setup/Drop Rate Statistics ................................................................................. 37
5.1.2 Throughput Statistics ......................................................................................... 52
5.1.3 Traffic Hold Time Statistics ................................................................................ 53
5.1.4 Resource Usage Statistics ................................................................................. 53
5.1.5 Moblity Statistics ................................................................................................ 56
5.1.6 Channel Switching Statistics .............................................................................. 68
5.2 Alarm List ........................................................................................................... 70
6 Glossary ........................................................................................................... 70

FIGURES
Figure 3-1 Architecture of the HSUPA Protocol................................................................... 6

Figure 3-2 Frame Structure of the E-DPDCH ...................................................................... 8
Figure 3-3 Frame Structure of the E-DPCCH ...................................................................... 9
Figure 3-4 Frame Structure of the E-AGCH ........................................................................ 9
Figure 3-5 Frame Structure of the E-RGCH .......................................................................10
Figure 3-6 Basic Principles of HSUPA ...............................................................................13
Figure 3-7 Requirements of 3GPP on HSUPA UE Categories ...........................................17
Figure 3-8 E-DCH Intra-frequency Cell Change Flow ........................................................23
Figure 3-9 Intra-cell Fallback from E-DCH to DCH .............................................................25
Figure 3-10 Inter-cell Fallback from E-DCH to DCH ...........................................................25
Figure 3-11 SHO of HSUPA HARQ ...................................................................................29
TABLES
Table 3-1 Timeslot Formats of the E-DPDCH ..................................................................... 8

1 Feature Attributes
System version: [RNCV3.12.10/RNCV4.12.10, Node B V4.12.10, OMMR V12.12.41,
OMMB V12.12.40]
Attribute: [Mandatory]
NE involved:
UE Node B RNC MSCS MGW SGSN GGSN HLR
√ √ √ - - √ - -
Note:
*-: Not involved.
*√: Involved.
Dependency: [None]
Mutual exclusion: [None]
Note: None
2 Overview
High-Speed Uplink Packet Access (HSUPA) is an enhanced uplink technology
introduced by 3GPP R6 in the radio network, aiming at the further improvement of the
uplink packet access capability. HSUPA works at the frequency of 5 MHz and does not
alter the WCDMA network architecture and the access mode of the original R99/R4. By
introducing the MAC-e/es entity and physical channel to the protocol stack of the UTRAN
and adopting key technologies, such as Hybrid Automatic Repeat Request (HARQ),
Node B based fast scheduling and short frame transmission (2ms TTI), HSUPA
effectively improves the peak bit rate of the uplink channel from 384 Kbps of R99/R4 to
5.76 Mbps. HSUPA and HSDPA jointly comprise the uplink and downlink enhanced data
transmission technologies, greatly improving the system capacity and frequency
utilization rate.
The HSUPA technology has enhanced the UTRAN function of R99/R4 and is completely
compatible with the R99/R4 version. The original voice and data services can operate in

the HSUPA network.
3 Feature Introduction
3.1 Architecture of HSUPA
HSUPA is the enhanced uplink technology of the WCDMA. In system architecture,

HSUPA differs from R99/R4 in which it adds two new MAC entities. It introduces MAC-e
to the Node B and MAC-es to the SRNC. Figure 3-1 shows the architecture of the
HSUPA protocol.
Figure 3-1 Architecture of the HSUPA Protocol
DTCH DCCH DCCH DTCH
MAC-d MAC-d
MAC-es
MAC-es /
MAC-e
MAC-e MAC-e EDCH FP EDCH FP
PHY PHY TNL TNL TNL TNL
Uu
UE NodeB Iub DRNC Iur SRNC
From the architecture of Figure 3-1, it is obvious that HSUPA differs from R99/R4 in
which MAC-e and MAC-es have been introduced to the Node B and SRNC respectively.
The MAC-e entity of the Node B is mainly responsible for HARQ retransmission,
scheduling, and demultiplexing of MAC-e; the MAC-es entity of the SRNC is mainly
responsible for re-ordering and the macro diversity combination.

3.2 Basic Principle of HSUPA
3.2.1 Physical Channels Introduced to HSUPA
To realize the functions and attributes of HSUPA, 3GPP R6 introduces five new physical
channels to the physical layer: In the uplink direction, it adds a dedicated data channel
E-DPDCH (up to 4 E-DPDCHs for each UE) and a dedicated control channel E-DPCCH
for the UEs especially. In the downlink direction, it adds the common physical channels
E-HICH, E-AGCH, and E-RGCH.
 The E-DPDCH is an uplink physical channel for carrying the E-DCH data especially.
 The E-DPCCH is an uplink control channel for carrying the E-DCH control
information especially.
 The E-AGCH is a downlink common physical channel for carrying the E-DCH
absolute grant data.
 The E-RGCH is a downlink physical channel for carrying the E-DCH relative grant
data especially.
 The E-HICH is a downlink physical channel for carrying the E-DCH HARQ
acknowledgement indications.
3.2.1.1 Introduction to the E-DPDCH (E-DCH Dedicated Physical Data Channel)
The E-DPDCH is used to carry uplink data and its spreading factor ranges from 2 to 256.
The spread factor is in reverse proportion to the carried traffic volume. The modulation
mode of E-DPDCH is BPSK. Similar to HSDPA, the channel also introduces 2ms TTI
while reserving 10ms TTI. Figure 3-2 shows the frame structure of the E-DPDCH.

Figure 3-2 Frame Structure of the E-DPDCH
When the spreading factor is 2 or 4, the E-DPDCH supports multi-code transmission.

When adopting multi-code transmission, the E-DPDCH supports the maximum
configuration of 2 × SF2 + 2 × SF4. Table 3-1 shows the timeslot formats of the
E-DPDCH.
Table 3-1 Timeslot Formats of the E-DPDCH
3.2.1.2 Introduction to the E-DPCCH (E-DCH Dedicated Physical Control Channel)
Figure 3-3 shows the frame structure the E-DPCCH. The E-DPCCH is used to carry the
control information of the E-DCH.
E-TFCI: the transmission format combination indicator of the E-DCH (7bit)

RSN: HARQ retransmission sequence number (2bit)
Happy Bit: scheduling feedback bit from the UE (1bit)
Figure 3-3 Frame Structure of the E-DPCCH
The E-DPCCH adopts the spreading factor of 256 invariably. The modulation mode is
BPSK. Similar to the E-DPDCH, the E-DPCCH supports 2ms TTI and reserves 10ms
TTI.
3.2.1.3 Introduction to the E-AGCH (E-DCH Absolute Grant Channel)
The E-AGCH is a downlink common physical channel for carrying E-DCH absolute grant
information. The channel only exists in the serving cells of an E-DCH. Figure 3-4 shows
the frame structure of the E-AGCH.
Figure 3-4 Frame Structure of the E-AGCH
The E-AGCH adopts a spreading factor of 256 invariably and the modulation mode of
QPSK. The absolute grant information consists of a grant value (5 bits) and process

activation indicator (1 bit). The process activation indication bit is used to indicate
whether the absolute grant targets at a specific HARQ process or all HARQ processes.
3.2.1.4 Introduction to the E-RGCH (E-DCH Relative Grant Channel)
The E-RGCH is a downlink physical channel for carrying E-DCH relative grant
information. Figure 3-5 shows the frame structure of the E-RGCH.
Figure 3-5 Frame Structure of the E-RGCH
The E-RGCH adopts a spreading factor of 128 invariably and the modulation of QPSK. A
relative grant is transmitted using 3, 12, or 15 consecutive slots and in each slot a
sequence of 40 ternary values is transmitted. The channels are divided into two types:
E-RGCH in the serving cell and E-RGCH in the non-serving cell. The E-RGCH in the
serving cell can carry instructions (UP, HOLD, and DOWN) of increasing, keeping, and
decreasing the power of a UE. The E-RGCH in the non-serving cell is used to carry cell
payload indication information and instructions of keeping and decreasing the power of a
UE. The UE can receive relative grant information from serving cells and non-serving
cells and combine the received grant information.
The setting of TTI decides the mode in which the E-RGCH relative grant information is
sent.
 When TTI is 2 ms, the relative grant information from the serving cell is sent once
every 2 ms.
 When TTI is 10 ms, the relative grant information from the serving cell must be sent
within 12 timeslots, that is, the relative grant instruction is sent once every 8 ms.

 The relative grant information from the non-serving cell must be sent within 15
timeslots, that is, the relative grant instruction is sent once every 10 ms.
3.2.1.5 Introduction to the E-HICH (E-DCH HARQ Acknowledge Indication

Channel)
The E-HICH is a downlink physical channel carrying HARQ confirmation indication (ACK
and NACK). An HARQ confirmation indication is carried over 3 or 12 consecutive
timeslots corresponding to TTI of 2ms or 10ms respectively. In RLS containing serving
cells, the HARQ confirmation indication value is 1 (ACK) or -1 (NACK); in RLS with
non-service E-DCH, the HARQ acknowledge indication value is 1 (ACK) or 0 (NACK).
The E-HICH adopts the spreading factor of 128 invariably and the modulation of QPSK
and has the same frame structure as the E-RGCH. If an E-RGCH and an E-HICH target
at the same UE, they share the same spreading factor of 128. They are distinguished
from each other through different signature sequences.
3.2.2 Basic Principles of HSUPA
During the working process of HSUPA, the UE first sends scheduling messages to the
Node B over the E-DPDCH. The scheduling message includes 4-bit high priority logical
channel ID, 9-bit UE buffer occupancy status (including 5-bit Total E-DCH Buffer Status,
namely TEBS, and 4-bit Highest Priority Logical Channel Buffer Status, namely HLBS),
5-bits UE power status, and the scheduling request of the Happy bit carried over the
E-DPCCH for requesting the Node B to distribute resources.
The serving Node B decides the scheduling grant according to the QoS information and
scheduling request information of the UE. The scheduling grant has the following
attributes:
 The scheduling grant is limited to the selection of E-DCH TFC and is not used in the
selection of DCH TFC.
 The scheduling grant controls the maximum E-DPDCH/DPCCH power ratio of the
activating process. In case of non-activating process, the power ratio is 0 and the
UE is prohibited to send data.

 All grants are certain and the scheduling grant can be sent at the interval of TTI or
lower frequency.
The scheduling grant sent by the Node B can be divided into two categories: absolute
grant and relative grant. The former is the absolute limitation on the maximum resources
available to the UE; the later increases or reduces the value of the previous grant. The
absolute grant is sent by the serving cell of the serving E-DCH and is effective to a UE, a
group of UEs, or all UEs. The relative grant (updating) is sent by the serving Node B or
non-serving Node B as the supplement of the absolute grant. The scheduling mechanism
controlled by the Node B can swiftly control the Raise over Thermal (RoT).
The UE sends data after selecting Retransmission Sequence Number (RSN), HARQ RV
version, and the power difference between E-DPDCH and E-DPCCH according to the
scheduling information (consisting of absolute grant and relative grant) and the
ACK/NACK sent previously.
From the perspective of the overall UTRAN protocol, the basic working principles of the
HSUPA technology are shown in Figure 3-6.

Figure 3-6 Basic Principles of HSUPA
SRNC DRNC
MAC-d
FP
MAC-es
Iur/Iub FP
1 TNL bearer per MAC-d flow
NodeBs Iur/Iub FP NodeBd FP
MAC-e MAC-e
Scheduler
MRC MRC
E-HICH (ACK/NACKs)
E-RGCH (relative grants)
serving cell (ChCode, signature -> UE)
E-AGCH
(Absolute Grants,
"E-RNTI" -> UE) E-DPDCH
E-DPCCH
UE
MAC-e/
MAC-es
MAC-d
DTCHs
Figure 3-6 shows the connection between the UE that uses the E-DCH and is in the soft
handover (SHO) status and the URTAN, as well as the protocols related to the HSUPA at
both the UE and network side. Figure 3-6 shows the basic working principles of the
HSUPA.
 E-DCH active set: the cell set carried by the E-DCH between the Node B and the
UE. An E-DCH active set can be a sub-set of the DCH active set.
 E-DCH serving cell: the cell where the UE receives the absolute grants. The UE has
only one E-DCH serving cell.
 E-DCH serving RLS: a group of RLs containing the E-DCH serving cell. It is
generally the cell set of the E-DCH active set under the Node B of the E-DCH
serving cell.

 Non-serving E-DCH RLS: the E-DCH cell set of all non-serving E-DCH RLS under
the Node B which has no E-DCH serving cell.
The HSUPA is characterized by the scheduling under control of the Node B. The
following describes the scheduling process:
 A UE has an E-DCH serving cell. The Node B of the E-DCH serving cell is
responsible for E-DCH scheduling. The E-DCH serving cell sends scheduling
command (namely absolute grant) over the downlink E-AGCH to the UE. The
absolute grant specifies the absolute value of the maximum resources available to a
UE. The absolute grant includes E-RNTI and maximum transmit power of the UE.
 The E-DCH serving cell and non-E-DCH serving cell send relative grant over the
downlink E-RGCH to the UE. The relative grant is used to adjust the absolute grant.
The values of the relative grant include UP, HOLD, and DOWN. Only serving
E-DCH RLS can send UP; while non-serving E-DCH RLS can only send HOLD or
DOWN. When the uplink payload is too large, the non-serving E-DCH RLS sends
DOWN.
 Upon receiving the grant information, the UE makes a choice in respect of the
E-TFC. It sends data (including resent data) over the E-DPDCH and sends the
E-TFC information, HARQ RV (RSN) and the Happy bit over E-DPCCH . The
Happy bit is used to inform the Node B whether the UE is satisfied with the allocated
resources and grants or not, that is, whether higher grant is needed.
 The Node B performs combination for the E-DCH data received by different cells of
the Node B and submits it to the Mac-e for processing. Each UE has a Mac-e in
Node B. The Mac-e demultiplexes Mac-e PDU into MAC-es PDU and sends it to the
RNC. The Mac-e also sends the E-DCH scheduling information and HARQ
response ACK/NACK.
 Each UE has a Mac-es entity in the SRNC. The Mac-es entity performs macro
diversity combination for MAC-es PDUs from different Node Bs, reorders and
divides them into Mac-d PDU, and then sends them to the Mac-d.
HSUPA also supports non-scheduling transmission which means UE can transmit at any
time without the scheduling information. The non-scheduling transmission is just like the

DPCH of R99 and is usually used to carry the service which is delay sensitive, such as
signaling, conversational service, and streaming service.
3.3 Basic Functions of HSUPA
3.3.1 ZWF25-01-005 HSUPA Common Carrier with R99
Carrier frequency sharing between HSUPA and R99 means that the cell can provide
uplink R99 service and HSUPA service simultaneously and can allocate common
resources reasonably between R99 and HSUPA. These common resources include
transmit power and downlink channels of E-AGCH, E-RGCH and E-HICH, transport
bandwidth of the Iub interface, and uplink interference of the cell.
HSUPA is generally used with HSDPA. If the operator is using the RAN of ZTE and has
purchased the license of the HSUPA basic function package, the HSUPA function can be
enabled in a cell supporting HSDPA. By configuring the parameter hspaSptMeth in
OMCR, both R99 and HSUPA services are also enabled simultaneously in a cell. The
perfect RRM algorithm of ZTE can guarantee reasonable allocation of cell common
resources between these two types of services.
If the operator wants to close the HSUPA function when the cell supports HSUPA
capability, the operator can set hsuStat to Inactive.
3.3.2 ZWF25-01-005 HSUPA Dedicated Carrier
HSUPA is generally used with HSDPA together. You can adopt the same carrier
frequency for R99 and HSUPA to realize R99 and HSUPA services simultaneously or use
different carrier frequency for them to support HSUPA/HSDPA service only.
When the operator has more frequency resources than the requirement of R99 service, it
can adopt different frequencies for HSUPA/HSDPA service. Since the frequency
utilization efficiency of the E-DCH is higher than that of the DCH, the operator can obtain
higher uplink peak rate and cell throughput, improve the QoS of the service, and reduce
the cost of high speed data service.

To realize the traditional CS service and low-speed PS service carried on the DCH, a
frequency to carry R99 service is also needed. The UMTS RAN of ZTE supports the
access to different frequencies for the users according to various service types.
If you use the UMTS RAN of ZTE and have purchased the license of the HSUPA basic
function package, you can enable the HSUPA function for a cell. By configuring the
parameter hspaSptMeth in OMCR, you can enable a cell to support HSUPA/HSDPA only.
The cell does not support the R99 service separately but supports concurrent
provisioning of the CS services and the PS services
If the operator wants to close the HSUPA function when the cell supports HSUPA
capability, the operator can set hsuStat to Inactive.
3.3.3 ZWF25-01-003 HSUPA Cell Indicator in Idle Mode
The indicator of a HSUPA cell can be broadcasted through the system message SIB5 or
SIB5bis. When searching cells, the terminal can figure out whether a cell supports the
HSUPA service according to the indicator and then selects a desired cell accordingly. For
example, a user holding the HSUPA data card can search the carrier frequency
supporting the HSUPA service within a sector. The terminal decides the policy of
selecting a cell according to the capability of cells.
3.3.4 ZWF25-01-004 HSUPA UE Category Support
The UMTS RAN of ZTE supports all HSUPA terminal category levels of the 3GPP
protocol. The category levels reflect the extent to which a terminal supports the HSUPA
service. For details, refer to 3GPP TS 25.306. RNC configures the Maximum Set of
E-DPDCHs (NBAP IE) to Node B according to the minimum SF between the SF
supported by UE category and the SF required by the MBR in RAB ASSIGNMENT
REQUEST.

Figure 3-7 Requirements of 3GPP on HSUPA UE Categories
3.3.5 ZWF25-01-024 HSUPA 2ms TTI
The UMTS RAN of ZTE supports the HSUPA with the TTI of 2ms. Each cell can be
configured supporting 2ms TTI or not by the parameter tti2msSuptInd (for neighboring
RNC cell, by the parameter edchTti2SuptInd).
When adopting 2ms short frame, HSUPA can reduce the transmission time delay. As a
result, the air interface can transmit data at a time delay shorter than that of 10ms frame,
and the frame alignment time during the data framing of the transmitter also decreases.
The use of 2ms frame can reduce the Round Trip Time (RTT) of HARQ process under
the control of the Node B and decrease the fast scheduling response time. In contrast to
10ms frame, 2ms frame can more effectively utilize the resources and obtain larger
system capacity.
The 2ms TTI HSUPA adopts the scheduling interval of 2ms. The Node B specifies the
value of Rate Grant (RG) according to the payload of the current cell and sends it to the
user. With the increase of cell load, the 2ms TTI HSUPA, in contrast to the 10ms TTI
HSUPA, can improve the performance generated from the cell throughput. Obviously, the
smaller the TTI is, the larger the performance will be.
3.3.6 ZWF25-01-014 HSUPA HARQ
HSUPA adopts a fast HARQ which allows the Node B to fast retransmit data wrongly
received. The fast HARQ is implemented in the MAC-e layer, which is terminated at the
Node B. In the traditional R99, the data packets are retransmitted by the Radial Link
Controller (RLC) under the control of the RNC. In the acknowledgement mode, the RLC

retransmits the RLC signaling and data from the Iub interface with the time delay of more
than 100 ms. The retransmission time delay of HARQ (the retransmission time delay of
10ms TTI is 40 ms and the retransmission time delay of 2ms TTI is 16 ms) is much
shorter than the retransmission time delay in the RLC layer, greatly reducing the time
delay jittering of TCP/IP service and services sensitive to response time.
3.3.7 ZWF25-01-021 HSUPA 1.45Mbps Peak Bit Rate
The UMTS RAN of ZTE supports the HSUPA peak rate of 1.45 Mbps. When a terminal
uses interactive or background services carried over the E-DCH, the peak rate on the
MAC layer can reach to 1.45 Mps.
3.3.8 ZWF25-01-022 HSUPA 16 Users per Cell
The UMTS RAN of ZTE supports the running of 16 HSUPA users in a single cell, which is
controlled by parameter of EdchTrafLimit. For details of the parameter, refer to ZTE
UMTS Admission Control Feature Guide.
3.3.9 ZWF25-01-023 HSUPA 2 Mbps Peak Bit Rate
The UMTS RAN of ZTE supports the HSUPA peak rate of 2 Mbps. When a terminal uses
interactive or background services carried over the E-DCH, the peak rate on the MAC
layer can reach to 2 Mbps.
3.3.10 ZWF25-01-024 HSUPA 5.76 Mbps Peak Bit Rate
The UMTS RAN of ZTE supports the HSUPA peak rate of 5.76 Mbps. By adopting the
2ms TTI and the multiplexing of 2 SF2 * 2 SF4, a UE can enjoy interactive or background
services carried over the E-DCH at the uplink peak rate of 5.76 Mbps. This function can
be controlled by parameter fourEChAllowedInd. For neighboring RNC cell, the cell of
E-DCH SF Capability can be configured by the parameter edchSfCap.
ZTE plays a leading role in the R&D of HSPA. The HSUPA high-performance radio
resources scheduling algorithm has solved the problem of mutual-interference between
HSDAP and HSUPA when they are transmitted by the same terminal at the maximum bit
rate. ZTE has won the recognition from the telecom industry for its achievement in this

aspect. In the telecom exhibition held in Barcelona on February 11 2008, ZTE

demonstrated its UMTS HSUPA 5.76 Mbps.
controlled by the parameter of EdchTrafLimit. For details of the parameter, refer to ZTE
3.3.14 ZWF25-02-001 PS Interactive/Background Service over HSUPA
HSUPA services are carried over the enhanced dedicated channel E-DCH. Adopting the
BPSK modulation and HARQ, the E-DCH provides higher bit rate and enables multiple
users to share the load of uplink cells, which make it suitable to carry interactive and
background services with the high bursting feature. The peak rate of the channel can
effectively improve the QoS.
The UMTS RAN of ZTE supports the maximum uplink bit rate of 5.76 Mbps. But the
actual maximum bit rate available to users depends on the capability level of the terminal,
the maximum bit rate (MBR) subscribed in the core network (CN), payload of the system,
and the radio environment at the time of access.
The RAB radio parameters of the interactive/background PS data services of the ZTE
UMTS RAN comply with 3GPP TS 34.108 protocol.

3.3.15 ZWF25-02-002 PS Streaming Service over HSUPA
The UMTS RAN of ZTE supports carrying PS streaming services over the E-DCH.
The PS streaming service requires guaranteed transmission bit rate and shorter time
delay. According to the RAB parameters assigned by the CN, the RNC sends the GBR
configured for the PS streaming service to the Node B, instructs the service to use the
non-scheduling grants, so as to guarantee that the PS streaming service enjoys the
priority in the scheduling by the Node B and meets the requirement of GBR. The
mapping of scheduling priority is related to the QoS mapping of the RRM. Refer to
section 3.4 for more details. Section of 3.5.2 provides the details on the scheduling
mechanism of the Node B.
The RAB Radio parameters of the streaming PS data services of ZTE UMTS RAN
completely comply with 3GPP TS 34.108.
3.3.16 ZWF25-02-003 RAB Combination for CS over DCH and PS over

HSUPA
The UMTS RAN of ZTE supports concurrent provisioning of the CS services and the PS
I/B/S services carried over HSUPA. The CS services include:
 CS AMR voice conversation services
 CS data conversation services, such as video telephony service
 CS data streaming service, such as FAX service
 CS WAMR voice conversation services
The current provisioning of one CS service and up to three PS services is supported.
When the CS services and the PS services carried over the HSUPA channel are
provided concurrently, the actual maximum bit rate of the uplink PS services depends on
the capability level of the terminal, the MBR subscribed in the core network (CN),
payload of the system, and the radio environment at the time of access.
The RAB radio parameters used for the concurrent carrying of CS service and PS
service over the HSUPA of the ZTE UMTS RAN comply with 3GPP TS 34.108.

3.3.17 ZWF25-02-004 RAB Combination for Multiple Packet Data Services

over HSUPA
This attribute supports the concurrent provisioning of up to three PS

interactive/background/streaming services. The MBR of each PS service depends on the
subscribed bit rate in the CN, and the total bit rate of all services cannot exceed the
highest bit rate supported by HSUPA. The highest bit rate depends on the UE category
level, load of the system, and radio environment at the time of access.
The RAB radio parameters used for carrying the multiple concurrent PS services over
the HSUPA of the ZTE UMTS RAN comply with the 3GPP TS 34.108.
3.3.18 ZWF25-02-011 SRB over HSUPA
The attribute supports carrying signaling over the E-DCH. The signaling RB has higher
requirement on time delay. Therefore, the signaling RB can be processed as a special
streaming service. In comparison with normal streaming service, the signaling RB has
higher scheduling priority. The mapping of scheduling priority is related to the QoS
mapping of the RRM. Section 3.4 provides more details. Section 3.5.2 provides details
on the scheduling mechanism of the Node B. This function can be controlled by
parameter srbOnEdchSwch. For more details, refer to ZTE UMTS DRBC Algorithm
Feature Guide.
3.3.19 ZWF25-05-002 HSUPA Nominal Bit Rate for I/B Service
When the UMTS RAN of ZTE uses the E-DCH to carry the interactive/background
services, it supports configuring the nominal bit rate edchNormBitRate. For more details,
refer to ZTE UMTS QoS Feature Guide. The RNC configures GBR for
interactive/background services according to the edchNormBitRate and sends the
setting to the Node B. When performing HSUPA fast scheduling, the Node B provides
minimum GBR for interactive/background services. The edchNormBitRate can be
configured as 0.
The UMTS RAN of ZTE supports the running of 192 HSUPA users in a single cell, which

is controlled by the parameter of EdchTrafLimit. For details of the parameter, refer to ZTE
3.4 Key Algorithms in the RNC
3.4.1 HSUPA Mobility Management
The UMTS RAN of ZTE supports seamless handover of a UE inside the coverage of
HSUPA, between the coverage of HSUPA and R5/R99, and between the coverage of
HSUPA and 2G. The cell attribute (hspaSptMeth) of the HSUPA coverage can be set to
Support HSUPA, HSDPA and DCH, or Support HSUPA and HSDPA; the cell attribute
(hspaSptMeth) of the HSDPA coverage can be set to Support HSDPA and DCH, Support
HSDPA only, Support HSUPA, HSDPA and DCH, or Support HSUPA and HSDPA; the
cell attribute (hspaSptMeth) of R99 can be set to Not Support HSUPA and HSDPA.
If the cell attribute hsuStat is Inactive, the RNC considers the cell doesn’t support
HSUPA.
For improving the compatibility of HSUPA over Iur, the UMTS RAN of ZTE supplies two
more parameters RncFeatSwitch2 and RncFeatSwitch4 which can be configured based
on office direction. The RncFeatSwitch2 is used to configure whether the neighbor RNC
supports HSUPA or not. If the neighbor RNC doesn’t support HSUPA, ZTE RNC will
transfer EDCH to DCH before processing the Iur signaling flow. The RncFeatSwitch4 is
used to configure whether DSCR is adopted or not when doing hard handover SRNS
relocation for HS-DSCH configuration.
For details on the algorithm related to HSUPA mobility, refer to ZTE UMTS Handover
Control Feature Guide.
Similar to DCH, E-DCH is a dedicated uplink channel that supports SHO. Most mobility
algorithms of the E-DCH are the same as those of the DCH. The only difference between
them lies in the fact that the E-DCH supports E-DCH serving cell variation and switching
from the E-DCH to the DCH caused by the mobility.
The following takes the intra-RNC E-DCH handover as an example to describe the flow.
The inter-RNC E-DCH handover is similar to the intra-RNC E-DCH handover.

3.4.1.1 ZWF25-03-002 E-DCH Serving Cell Change inside Active Set
Similar to the HSDPA, the HSUPA also has a serving cell change flow. The difference lies
in the fact that the E-DCH is an uplink link that supports SHO. The bearer of the E-DCH
serving cell is the same as that of the E-DCH non-serving cell. When the E-DCH serving
cell varies within the active set, the Iub/Iur interface does not need to set up a new
E-DCH bearer.
The following figure shows the E-DCH serving cell change flow.
Figure 3-8 E-DCH Intra-frequency Cell Change Flow
Target Serving
UE RNC
NodeB NodeB
1. Measurement Report 1D
2. Decide to
Change E-DCH
Serving Cell
3. Radio Link Reconfiguration Prepare
5. Radio Link Reconfiguration Ready
7. Radio Link Reconfiguration Commit
9. Physical Channel Reconfiguration
10. Physical Channel Reconfiguration Complete
Before the E-DCH serving cell changes, the UE has maintained connections with
multiple cells:
1. The UE measures the quality of the intra-frequency cells in the neighboring cell list
according to the measurement control mechanism of the RNC, judges the
occurrence of intra-frequency events, and sends the measurement report to the
RNC.
2. The RNC decides to change the E-DCH serving cell according to the events
reported by the UE and availability of the radio resources.
3. The RNC sends the NBAP message Radio Link Reconfiguration Prepare to the
serving Node B and reconfigures it as the non-serving E-DCH RL.

destination Node B and reconfigures it as the serving E-DCH RL.
5. The serving Node B returns the Radio Link Reconfiguration Ready message to the
RNC.
6. The destination Node B returns the Radio Link Reconfiguration Ready message to
the RNC.
7. The RNC sends the Radio Link Reconfiguration Commit message with the time of
changing the E-DCH serving RL to the serving Node B.
changing the E-DCH serving RL to the destination Node B.
9. The RNC sends the RRC message Physical Channel Reconfiguration to the UE
and instructs it to change the E-DCH serving cell.
10. The UE switches to the new E-DCH serving RL at the time specified by the RNC
and sends the RRC message Physical Channel Reconfiguration Complete to the
RNC.
3.4.1.2 ZWF25-03-003 & ZWF25-03-004 Switching between E-DCH and DCH
The switching between E-DCH and DCH includes intra-cell switching and inter-cell
switching.
The following figure shows the flow of intra-cell switching between E-DCH and DCH. For
example, the UE supports handover from the cell that supports the E-DCH to an
inter-frequency neighboring cell that does not supports the E-DCH. In this case, it is
necessary to enable the compression mode. Because the UE does not support
concurrent processing of the E-DCH and compression mode, it is necessary to perform
intra-cell fallback from the E-DCH to the DCH.

Figure 3-9 Intra-cell Fallback from E-DCH to DCH
UE NodeB RNC

4. Transport Channel Reconfiguration
5. Transport Channel Reconfiguration Complete
Node B to reconfigure the E-DCH as a DCH.
2. The Node B returns the Radio Link Reconfiguration Ready message to the RNC.
channel switching to the Node B.
4. The RNC sends the RRC message Transport Channel Reconfiguration to the UE to
reconfigure the E-DCH as a DCH.
5. The UE switch the E-DCH to the DCH at the time specified by the RNC and sends
the RRC message Transport Channel Reconfiguration Complete to the RNC.
Figure 3-10 shows the flow of inter-cell switching between E-DCH and DCH. This
example describes a scenario of fallback from the inter-cell E-DCH to the DCH. The UE
takes the hard handover from a cell that supports the E-DCH to an intra-frequency
neighboring cell that does not support the E-DCH.
Figure 3-10 Inter-cell Fallback from E-DCH to DCH
Target Source
UE RNC
NodeB NodeB
1. Radio Link Setup Request
2. Radio Link Setup Response
3. Transport Channel Reconfiguration
4. Transport Channel Reconfiguration Complete
5. Radio Link Deletion Request
6. Radio Link Deletion Response

1. The RNC sends the NBAP message Radio Link Setup Request to the target Node
B to set up a radio link of the DCH.
2. The destination Node B returns the Radio Link Setup Response message to the
RNC.
3. The RNC sends the RRC message Transport Channel Reconfiguration to the UE to
reconfigure the E-DCH as a DCH.
4. The UE sends the RRC message Transport Channel Reconfiguration Complete to

the RNC to switch the E-DCH to a DCH.
5. The RNC sends the NBAP message Radio Link Deletion Request to the source
NdoeB to delete the bearer of the original E-DCH.
6. The source Node B returns the Radio Link Deletion Response message to the
RNC.
3.4.2 ZWF25-04-005 HSUPA Dynamic Channel Adjustment
For details on the HSUPA channel dynamic adjustment algorithms, refer to ZTE UMTS
DRBC Algorithm Feature Guide.
3.4.3 ZWF25-04-007 Code Allocation for HSUPA
For details on the HSUPA code resources management algorithms, refer to ZTE UMTS
Code Resource Feature Guide.
3.4.4 ZWF25-04-006 Power Allocation for HSUPA
For details on the HSUPA power control algorithms, refer to ZTE UMTS Power Control
Feature Guide.
3.4.5 ZWF25-04-001 Admission Control for HSUPA Service
For details on the HSUPA admission control algorithms, refer to ZTE UMTS Admission

3.4.6 ZWF25-04-002 Overload Control for HSUPA Service
For details on the HSUPA load control algorithms, refer to ZTE UTMS Overload Control
Feature Guide.
3.4.7 ZWF25-04-003 Load Balance for HSUPA Service
For details on the HSUPA load balance algorithms, refer to ZTE UMTS Load Balance
Feature Guide.
3.4.8 ZWF25-04-004 Congestion Control Strategy for HSUPA
For details on the HSUPA congestion control algorithms, refer to ZTE UMTS Congestion
3.4.9 ZWF25-05-001 QoS Mapping for HSUPA Service
For details on the HSUPA QoS mapping algorithms, refer to ZTE UMTS QoS Feature
Guide.
3.5 Key Calculations and Algorithms in Node B
3.5.1 Introduction to HARQ
HARQ integrates the Forward Error Correction (FEC) and Automatic Repeat Request
(ARQ). HARQ adjusts the bit rate of a channel according to the condition of the link and
integrates the FEC with retransmission. HARQ allows the receiver to save the received
data when decoding fails and requests the transmitter to retransmit data. The receiver
combines the retransmitted data with the previously-received data. The HARQ
technology can improve the system performance, effectively adjust the bit rate of valid
code elements, and compensate the code errors brought about by the link adaptation.
Introduced to HSUPA by the 3GPP, HARQ can effectively reduce the transmission time
delay and improve the retransmission efficiency.
A basic principle of the fast HARQ of HSUPA is to add a HARQ entity to the Node B. In
case of receiving failure, the Node B requests the UE to retransmit the uplink packets. In

the uplink direction, the HARQ adopts N channels SAW protocol (NSAW), which is
similar to the protocols used by HSDPA. Additionally, the Node B can also use different
methods to combine the retransmission tasks of a packet and reduce the reception
Ec/No of each transmission requirement. The HARQ function of HSUPA is mainly
applied in the MAC-e and physical layer of the Node B. Through the HARQ, the Node B
can effectively improve the data transmission speed and reduce the time delay.
In HSUPA, 10ms TTI corresponds to 4 HARQ processes; and 2ms TTI corresponds to 8
HARQ processes.
The HARQ technology has two implementation modes: If the retransmitted data is the
same as the data transmitted initially, this mode is referred to as Chase Combine (CC) or
soft combining; if the retransmitted data is different from the data transmitted initially, this
mode is referred to as Incremental Redundancy (IR).The later mode is better than the
former in performance and requires larger memory in the terminal. The default memory
of a terminal is designed according to the MBR and soft combining mode supported by
the terminal. When the terminal works at the MBR, it can only use the soft combining.
When working at lower transmission rate, the terminal supports both of the two modes.
The IR mode needs a more complex memory of the UE. The 3GPP does not impose
limitations on the specific mode. The CC mode can be viewed as a special form of the IR
mode. The parameter harqRvConfig is used to specify which HARQ mode should be
used (for neighboring RNC cell, by the parameter edchHarqCombCap).
The system adopting the fast HARQ may have a higher Block Error Rate (BLER) in the
first transmission. This is because the time delay of the packets with retransmission
reception errors drops obviously in comparison with the RLC retransmission. Higher
BLER target can reduce the transmission power requirement on the UE when it transmits
data at a certain bit rate. If two cells have the same payload, the application of the fast
HARQ can improve the capacity of the cell. When the data rate is invariable, reducing the
energy of each bit helps to improve the coverage. Certainly, improving the BLER target
excessively is costly because the time delay at the peak rate does not occur frequently
when the RLC retransmission is not started, but data is retransmitted in large quantity,
the user can feel the average time delay. Because more and more packets need to be
retransmitted, the valid throughput of invariable bit rate also drops with the increase of
the BLER.

In the SHO process, the HSUPA HARQ introduces a complex process that is unavailable
in the HSDPA HARQ. In the CDMA system, the SHO gain comes from the correct
reception of packets at a Node B while another Node B is unable of decoding. Therefore,
one Node B sends an ACK and another Node B sends a NACK. On this occasion, the
network has received the packet, and the UE shall no longer send the same packet. See
Figure 3-11. Accordingly, in the Node B with reception failure, the HARQ process can
recover from the incorrect reception. The RNC must ensure the sequence of packet
transmission and combine the packets received from different Node Bs selectively.
Figure 3-11 SHO of HSUPA HARQ
3.5.2 Node B Based Quick Packet Scheduling Technology
The fast scheduling is a key technology of the HSUPA and is realized in the MAC-e of
the Node B. For details on the HSUPA fast scheduling function, refer to ZTE UMTS Node
B HSUPA Packet Scheduling Feature Guide.
3.5.3 ZWF25-04-010 HSUPA E-AGCH CLPC
E-AGCH closed-loop power control which can make a closed-loop according to the
feedback of DPCCH and CQI will apply the service channel power control on the control
channels. When the channel quality information obtained by DPCCH or CQI forms the
power control command, this command will not only be transmitted to service channel
but also to the corresponding control channel in order to implement the consistent

association of service channel and corresponding control channel and ensure the
reliable transfer of control information. The power control can be used to resist the
modification of radio environment.
The advantages of E-AGCH closed-loop power control are shown as below:
 To effectively reduce the network interference from the channel without power
control to increase system capacity
 To effectively use downlink transmit power, reduce interference and improve

HSUPA performance
From the protocol description, E-AGCH power control is controlled by Node B. ZTE
adopts two methods in the following:
 Fixed power control
 Concomitant CQI/HS-SCCH power control
If the concomitant CQI/HS-SCCH power control method is used for E-AGCH, RNC will
change the power-offset value during the soft hand-over because E-AGCH has no soft
hand-over combination. HS-SCCH can control the channel quality due to the
outer-power control. Therefore the concomitant CQI/HS-SCCH power control for
E-AGCH can provide better performance.
The first method is directly controlled by HSUPA scheduler to adjust E-AGCH power
value. For the second method, HSDPA will report the latest scheduled HS-SCCH power
to HSUPA. The last E-AGCH power is derived from the sum of HS-SCCH power and the
fixed power offset of HS-SCCH relative to E-AGCH.
The power control method selection is configured by OAM.
Fixed power control arithmetic
The purpose of fixed power control arithmetic is to use high enough fixed transmit power
for each HSUPA user (The fixed power transmission must be satisfied with the
performance when the UE is located in the cell margin). The power configuration is
easier for this method. However, it will possibly waste Node B power resources and
create unnecessary interference in the cell.

Concomitant CQI/HS-SCCH power control arithmetic
E-AGCH is HSUPA control channel which is transmitted to UE by Node B. Based on an

overall consideration of E-AGCH, the power control strategy is described in the following.
According to the description of 3GPP protocol, one UE can be HSUPA user and HSDPA
user simultaneously because the same serving cell exists between HSUPA and HSDPA.
The E-AGCH which belongs to HSUPA serving cell can use CQI and HS-SCCH of
HSDPA information to implement E-AGCH power control and can adjust E-AGCH
transmit power according to CQI information reported by UE and HS-SCCH power
control.
CQI is the HS-SCCH quality indicator and will not be affected by the handover state and
service type. Due to the feedback of HS-SCCH demodulation in Node B, the influence of
the receiver performance and the speed of different UE can be shielded by the outer
power control arithmetic to control the channel quality.
Because of the same demodulation requirement between E-AGCH and HS-SCCH, the
concomitant HS-SCCH power control for E-AGCH power based on the blinding of
E-AGCH and HS-SCCH transmit power can effectively use HS-SCCH outer power
control to dynamically adjust E-AGCH transmit power with the channel quality. This
method can save E-AGCH power loss and reduce unnecessary interference to other
downlink channels.
3.5.4 ZWF25-04-011 HSUPA E-RGCH/HICH CLPC
E-RGCH/HICH closed-loop power control which can make a closed-loop according to

the feedback of DPCCH and CQI will apply the service channel power control on the
control channels. When the channel quality information obtained by DPCCH or CQI
forms the power control command, this command will not only be transmitted to service
channel but also to the corresponding control channel in order to implement the
consistent association of service channel and corresponding control channel and ensure
the reliable transfer of control information. The power control can be used to resist the
modification of radio environment.
The advantages of E-RGCH/HICH closed-loop power control are shown as below:

 To effectively reduce the network interference from the channel without power
control to increase system capacity
 To effectively use downlink transmit power, reduce interference and improve

HSUPA performance
From the protocol description, E-RGCH/HICH power control is controlled by Node B.

ZTE adopts two methods in the following:
 Fixed power control
 Concomitant DPCCH outer power control
The method of concomitant DPCCH outer power control will achieve better performance
because E-RGCH/HICH has soft handover combination to ensure the performance
without power-offset change.
For the method 1, E-RGCH/HICH power value is directly controlled by HSUPA scheduler.
For the method 2, the association between E-RGCH/HICH and DPCCH channel power
is directly implemented by hardware.
The power control method selection is configured by OAM.
4 Parameters and Configurations
4.1 Parameter List

Logic Name Parameter Name
hspaSptMeth(UUtranCellF
HSPA Support Method
DD)
hspaSptMeth(UExternalUtr
HSPA Support Method
anCellFDD)
edchNormBitRate E-DCH Uplink Nominal Bit Rate
RncFeatSwitchBit2 Support HSUPA Iur Interface Process
RncFeatSwitchBit4 Support Hard Handover DSCR
harqRvConfig HARQ RV Configuration

fourEChAllowedInd Four E-DPDCHs Allowed Indicator

srbOnEdchSwch Switch of supporting SRB on E-DCH
tti2msSuptInd Cell HSUPA 2ms TTI Support Indicator
hsuStat HSUPA Function Status
edchHarqCombCap
E-DCH HARQ Combining Capability
(UExternalUtranCellFDD)
edchSfCap
E-DCH SF Capability
edchTti2SuptInd
2ms E-TTI Support Indicator
4.2 Parameter Configurations
4.2.1 HSPA Support Method
 OMC path
Path: GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN

Cell->HSPA Support Method
 Parameter configuration
The serving cell supports the HSPA capability.
4.2.2 HSPA Support Method (Neighboring RNC Cell)
 OMC path
Path: GUI: Managed Element ->UMTS Logical Function Configuration->External

Resource Configuration->External RNC Function->External UTRAN Cell->HSPA
Support Method
The neighboring RNC cell supports the HSPA capability.

4.2.3 E-DCH Uplink Nominal Bit Rate
 OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->Service

Configuration->QOS Function->Qos Basic Configuration->E-DCH Uplink Nominal Bit
Rate
When the interactive/background service is carried over the E-DCH, the uplink nominal
bit rate is equivalent to the GBR configured by the RNC for the Node B.
4.2.4 Support HSUPA Iur Interface Process
 OMC path
Path: GUI: Managed Element->UMTS Logical Function Configuration->Link

Configuration->Iur Link->Whether Support HSUPA Iur Interface Process
It is based on the capability of DRNC. The parameter of RncFeatSwitch2 is set to 1 if the

DRNC supports HSUPA. Otherwise, it is set to 0.
4.2.5 Support Hard Handover DSCR
 OMC path
Path: GUI: Managed Element->UMTS Logical Function Configuration->Link

Configuration->Iur Link->Whether Support Hard Handover DSCR
It is based on the capability of DRNC. The parameter of RncFeatSwitch4 is set to 1 if the

DRNC needs DSCR to do hard handover. Otherwise, it is set to 0.
4.2.6 HARQ RV Configuration

 OMC path

Path: GUI: Managed Element ->UMTS Logical Function Configuration->HARQ RV

Configuration.
The default configuration is used.
4.2.7 Four E-DPDCHs Allowed Indicator

 OMC path
Path: GUI: Managed Element ->UMTS Logical Function Configuration->PLMN Relating

Configuration->Logic RNC Configuration->Four E-DPDCHs Allowed Indicator.
4.2.8 Switch of supporting SRB on E-DCH

 OMC path
Path: GUI: Managed Element ->UMTS Logical Function Configuration->PLMN Relating

Configuration->Logic RNC Configuration->Switch of supporting SRB on E-DCH.
4.2.9 Cell HSUPA 2ms TTI Support Indicator

 OMC path

Cell->Cell HSUPA 2ms TTI Support Indicator
4.2.10 HSUPA Function Status

 OMC path


Cell->HSUPA Function Status
4.2.11 E-DCH HARQ Combining Capability (Neighboring RNC Cell)
 OMC path

Resource Configuration->External RNC Function->External UTRAN Cell->E-DCH HARQ
Combining Capability.
It is set according to the actual HARQ combining capability of the neighboring cell of the
DRNC.
4.2.12 E-DCH SF Capability (Neighboring RNC Cell)
 OMC path

Resource Configuration->External RNC Function->External UTRAN Cell->E-DCH SF
Capability
It is set according to the actual E-DCH SF capability of the neighboring cell of the DRNC.
4.2.13 2ms E-TTI Support Indicator (Neighboring RNC Cell)
 OMC path

Resource Configuration->External RNC Function->External UTRAN Cell->2ms E-TTI
Support Indicator

It is set according to the actual E-DCH 2ms TTI capability of the neighboring cell of the
DRNC.
5 Counter and Alarm
5.1 Counter List
5.1.1 Setup/Drop Rate Statistics

Counter No. Description
C310080056 Number of RRC connection attempt,UE Support HSDPA & EDCH
Number of RRC connection access success,UE Support HSDPA +

C310080198
EDCH
C310080219 Number of RRC connection access success by UE HSUPA categories 1
Number of Failed RAB establishment in cell for CS domain,HSUPA user

C310110345
number limit
Number of Failed RAB establishment in cell for PS domain,HSUPA user

C310110402
number limit
Number of Failed HSUPA RAB establishment for PS

C310170483
domain,Conversational Class
Number of Failed HSUPA RAB establishment for PS domain,Streaming

C310170495
Class

C310170496
Class,UE hsupa category 1

C310170497


C310170498

C310170499

C310170500

C310170501

C310170502
Number of Failed HSUPA RAB establishment for PS domain,Interactive

C310170514
Class

C310170515

C310170516

C310170517

C310170518

C310170519

C310170520

C310170521
Number of Failed HSUPA RAB establishment for PS domain,Background

C310170533
Class

C310170534

C310170535

C310170536
C310170537 Number of Failed HSUPA RAB establishment for PS domain,Background



C310170538

C310170539

C310170540
Number of Failed HSUPA RAB establishment in cell for PS

C310170666
domain,Invalid RAB Parameters Value

C310170667
domain,Failure in the Radio Interface Procedure
Number of Failed HSUPA RAB establishment in cell for PS domain,UE

C310170668
send rb setup fail

C310170669
domain,Timeout of UU rb setup.

C310170670
domain,TQUEUING Expiry

C310170671
domain,Requested Traffic Class not Available

C310170672
domain,Requested Guaranteed Bit Rate not Available

C310170673
domain,Requested Guaranteed Bit Rate for DL not Available
Number of Failed HSUPA RAB establishment in cell for PS domain,No

C310170674
Resource Available

C310170675
Resource Available In SRNC

C310170676
domain,Downlink CE Congestion

C310170677
domain,Downlink CE Congestion

C310170678
domain,Downlink Power Resource Congestion
Number of Failed HSUPA RAB establishment in cell for PS domain,Other

C310170679
Downlink Resource Congestion


C310170680
domain,Uplink CE Congestion

C310170681
domain,Uplink Power Resource Congestion
Number of Failed HSUPA RAB establishment in cell for PS domain,Other

C310170682
Uplink Resource Congestion

C310170683
domain,HSUPA user number limit

C310170685
Resource Available In DRNC

C310170686
domain,Access Restricted Due to Shared Networks

C310170687
domain,Non-Standard Cause
Number of Failed HSUPA RAB establishment in cell for PS domain,Due

C310170688
to NodeB
Number of Failed HSUPA RAB establishment in cell for PS domain,RL

C310170689
Setup or Reconfig Fail
Number of Failed HSUPA RAB establishment in cell for PS domain,RL

C310170690
Setup or Reconfig Timeout

C310170691
to IUB
Number of Failed HSUPA RAB establishment in cell for PS domain,Iub

C310170692
Congestion

C310170693
UL Congestion

C310170694
DL Congestion

C310170695
TB Failure

C310170696
FB Cause
Number of Failed HSUPA RAB establishment in cell for PS domain,Iur

C310170697
Congestion
C310170698 Number of Failed HSUPA RAB establishment in cell for PS domain,Iur


Congestion

C310170699
TB Failure

C310170700
FB Failure
Number of Failed HSUPA RAB establishment in cell for PS domain,UP

C310170701
CE Limit

C310170702
to RNC
Number of Failed HSUPA RAB establishment in cell for PS domain,RB

C310220703
Fail,UP Fail

C310220704
domain,UCPMC Exception

C310220705
domain,RLMM Exception
Number of Failed HSUPA RAB establishment in cell for PS domain,CRM

C310220706
Exception

C310220707
domain,SCPM Exception
Number of Failed HSUPA RAB establishment in cell for PS domain,RPM

C310220708
Exception

C310220709
domain,Othere RNC Cause

C310170710
domain,Unspecified failure
Number of Successful HSUPA RAB establishment for PS

C310170831
domain,Conversational Class

C310170843
domain,Streaming Class

C310170844
domain,Streaming Class,UE hsupa category 1

C310170845

C310170846


C310170847

C310170848

C310170849

C310170850

C310170862
domain,Interactive Class

C310170863
domain,Interactive Class,UE hsupa category 1

C310170864

C310170865

C310170866

C310170867

C310170868

C310170869

C310170881
domain,Background Class,UE hsupa category 1

C310170882

C310170883

C310170884

C310170885
C310170886 Number of Successful HSUPA RAB establishment for PS



C310170887

C310170888
C310180965 Attempted HSUPA RB setup number
C310171135 Attempted HSUPA MAC-d setup number
C310171149 Failed HSUPA MAC-d setup number,UL SF not supported
C310171150 Failed HSUPA MAC-d setup number,DL SF not supported
C310171151 Failed HSUPA MAC-d setup number,compressed mode not supported
C310171152 Failed HSUPA MAC-d setup number,invalid CM settings
Failed HSUPA MAC-d setup number,requested configulation not

C310171153
supported
C310171154 Failed HSUPA MAC-d setup number,nodeB Resources unavailable
Failed HSUPA MAC-d setup number,power balancing status not

C310171155
compatible
C310171156 Failed HSUPA MAC-d setup number,cell not available
C310171157 Failed HSUPA MAC-d setup number,transport resource unavailable
Failed HSUPA MAC-d setup number,message not compatible with

C310171158
receiver state
C310171159 Failed HSUPA MAC-d setup number,hardware faliure
C310171160 Failed HSUPA MAC-d setup number,uncertainty failure
C310171161 Failed HSUPA MAC-d setup number,none response
Number Of RAB release for UTRAN Abnormal Reason for HSUPA:UE

C310251515
HSUPA categories 1,conversation

C310251516
HSUPA categories 1,streaming

C310251517
HSUPA categories 1,interactive

C310251518
HSUPA categories 1,backgroud

C310251519


C310251520

C310251521

C310251522

C310251523

C310251524

C310251525

C310251526

C310251527

C310251528

C310251529

C310251530

C310251531

C310251532

C310251533

C310251534

C310251535

C310251536
C310251537 Number Of RAB release for UTRAN Abnormal Reason for HSUPA:UE



C310251538

C310251539

C310251540

C310251541

C310251542
Number Of RAB normal release for UTRAN :UE HSUPA categories

C310251543
1,conversation

C310251544
1,streaming

C310251545
1,interactive

C310251546
1,backgroud

C310251547
2,conversation

C310251548
2,streaming

C310251549
2,interactive

C310251550
2,backgroud

C310251551
3,conversation

C310251552
3,streaming

C310251553
3,interactive

C310251554
3,backgroud


C310251555
4,conversation

C310251556
4,streaming

C310251557
4,interactive

C310251558
4,backgroud

C310251559
5,conversation

C310251560
5,streaming

C310251561
5,interactive

C310251562
5,backgroud

C310251563
6,conversation

C310251564
6,streaming

C310251565
6,interactive

C310251566
6,backgroud

C310251567
7,conversation

C310251568
7,streaming

C310251569
7,interactive

C310251570
7,backgroud
Total number Of RAB release for UTRAN for PS-HSUPA

C310251571
domain,conversation
C310251572 Total number Of RAB release for UTRAN for PS-HSUPA


domain,streaming

C310251573
domain,interactive

C310251574
domain,background
Number of RNC initiate HSUPA release by Rab Release Request for

C310251583
PS domain,conversation
Number of RNC initiate HSUPA release by Rab Release Request for PS

C310251584
domain,streaming

C310251585
domain,interactive

C310251586
domain,backgroud
Number of RAB HSUPA release by RNC receive Iu-release :

C310251587
conversation
C310251588 Number of RAB HSUPA release by RNC receive Iu-release : streaming
C310251589 Number of RAB HSUPA release by RNC receive Iu-release : interactive
C310251590 Number of RAB HSUPA release by RNC receive Iu-release : backgroud
Number of RAB release by RNC initiate RAB release request for

C310281856
PS-HSUPA by uesr inactive

C310281857
PS-HSUPA by repeat integrity check

C310281858
PS-HSUPA by UE initiate release

C310281859
PS-HSUPA by lost UE connection

C310281860
PS-HSUPA by relocation complete timer exceed

C310281861
PS-HSUPA by radio interface fail

C310281862
PS-HSUPA by DL RLC error on TRB

C310281863
C310281864 Number of RAB release by RNC initiate RAB release request for


PS-HSUPA by OMC intervention

C310281865
PS-HSUPA by overload control

C310281866
PS-HSUPA by RAB pre-empty

C310281867
PS-HSUPA by UTRAN generating

C310281868
PS-HSUPA by IUUP fail

C310281869
PS-HSUPA by unspecific fail
Number of RAB release by RNC initiate Iu release request for

C310281870

C310281871

C310281872

C310281873

C310281874

C310281875

C310281876
PS-HSUPA by active set update timer exceed

C310281877
PS-HSUPA by UL RLC error on SRB

C310281878
PS-HSUPA by UL RLC error on TRB

C310281879
PS-HSUPA by DL RLC error on SRB

C310281880

C310281881
PS-HSUPA by radio link fail


C310281882
PS-HSUPA by radio interface other fail

C310281883

C310281884

C310281885

C310281886

C310281887

C310281888
Number of RAB release by RNC initiate release request for

C310281908

C310281909

C310281910

C310281911

C310281912

C310281913

C310281914
PS-HSUPA by active set update timer exceed

C310281915
PS-HSUPA by UL RLC error on SRB

C310281916
PS-HSUPA by UL RLC error on TRB

C310281917
PS-HSUPA by DL RLC error on SRB
C310281918 Number of RAB release by RNC initiate release request for



C310281919
PS-HSUPA by radio link fail

C310281920
PS-HSUPA by radio interface other fail

C310281921

C310281922

C310281923

C310281924

C310281925

C310281926
Number of abnormal release RAB by Uu-fail,UE HSUPA categories

C310291990
1,conversation

C310291991
1,streaming

C310291992
1,inactive

C310291993
1,backgroud

C310291994
2,conversation

C310291995
2,streaming

C310291996
2,inactive

C310291997
2,backgroud

C310291998
3,conversation


C310291999
3,streaming

C310292000
3,inactive

C310292001
3,backgroud

C310292002
4,conversation

C310292003
4,streaming

C310292004
4,inactive

C310292005
4,backgroud

C310292006
5,conversation

C310292007
5,streaming

C310292008
5,inactive

C310292009
5,backgroud

C310292010
6,conversation

C310292011
6,streaming

C310292012
6,inactive

C310292013
6,backgroud

C310292014
7,conversation

C310292015
7,streaming
C310292016 Number of abnormal release RAB by Uu-fail,UE HSUPA categories


7,inactive

C310292017
7,backgroud
5.1.2 Throughput Statistics

C310010153 Uplink traffic of HSUPA for Conversational class in best cell
C310010154 Uplink traffic of HSUPA for Streaming class in best cell
C310010155 Uplink traffic of HSUPA for Interactive class in best cell
C310010156 Uplink traffic of HSUPA for Background class in best cell
C310010177 Uplink traffic of HSUPA for Conversational class in non-best cell
C310010178 Uplink traffic of HSUPA for Streaming class in non-best cell
C310010179 Uplink traffic of HSUPA for Interactive class in non-best cell
C310010180 Uplink traffic of HSUPA for Background class in non-best cell
C310010292 Uplink Iub volume of HSUPA RAB for Conversational class
C310010293 Uplink Iub volume of HSUPA RAB for Streaming class
C310010294 Uplink Iub volume of HSUPA RAB for Interactive class
C310010295 Uplink Iub volume of HSUPA RAB for Background class
C310020426 Number of uplink HSUPA RLC PDU,Conversational class
C310020427 Number of uplink HSUPA RLC PDU,Streaming class
C310020428 Number of uplink HSUPA RLC PDU,Interactive class
C310020429 Number of uplink HSUPA RLC PDU,Background class
C310790005 Iu Uplink volume of HSUPA
C310800021 HSUPA Uplink volume of Iub for Conversational class
C310800022 HSUPA Uplink volume of Iub for Streaming class
C310800023 HSUPA Uplink volume of Iub for Interactive class
C310800024 HSUPA Uplink volume of Iub for Background class
C310800029 Uplink header volume of Iub HSUPA traffic
C310010162 Uplink volume of VoIP in E-DCH in best cell
C310010181 Uplink volume of VoIP in E-DCH in non-best cell
C310010303 Uplink Iub volume of VoIP in E-DCH

C310020407 Number of UL SDU sent by RLC,Traffic on E-DCH for PS domain
C310020415 Number of UL SDU received by RLC,Traffic on E-DCH for PS domain
5.1.3 Traffic Hold Time Statistics

C310040071 Holding time of E-DCH,Conversational class,on best cell
C310040072 Holding time of E-DCH,Streaming class,on best cell
C310040073 Holding time of E-DCH,Interactive class,on best cell
C310040074 Holding time of E-DCH,Background class,on best cell
C310040141 Holding time of E-DCH,Conversational class,on non-best cell
C310040142 Holding time of E-DCH,Streaming class,on non-best cell
C310040143 Holding time of E-DCH,Interactive class,on non-best cell
C310040144 Holding time of E-DCH,Background class,on non-best cell
C310073366 Holding time of E-DCH,Conversational class,on DRNC cell
C310073367 Holding time of E-DCH,Streaming class,on DRNC cell
C310073368 Holding time of E-DCH,Interactive class,on DRNC cell
C310073369 Holding time of E-DCH,Background class,on DRNC cell
5.1.4 Resource Usage Statistics

C310030437 Number of including only HSUPA users in the best cell
C310030438 Number of including only HSDPA + HSUPA users in the best cell
C310030449 Max Number of including only HSUPA users in the best cell
C310030450 Max Number of including only HSDPA + HSUPA users in the best cell
C310030461 Average Number of including only HSUPA users in the best cell
Average Number of including only HSDPA + HSUPA users in the best

C310030462
cell
C310030620 Number of including only HSUPA users in the non-best cell
C310030628 Max Number of including only HSUPA users in the non-best cell
C310030636 Average Number of including only HSUPA users in the non-best cell
C310063384 Number of including only HSUPA users in the DRNC cell
C310063385 Number of including only HSDPA + HSUPA users in the DRNC cell

C310063395 Max Number of including only HSUPA users in the DRNC cell
Max Number of including only HSDPA + HSUPA users in the DRNC

C310063396
cell
C310063406 Average Number of including only HSUPA users in the DRNC cell
Average Number of including only HSDPA + HSUPA users in the

C310063407
DRNC cell
C310650101 Number of HSUPA cells in Working State
C310650102 Number of HSUPA cells in Manual Blocked
C310650103 Number of HSUPA cells in Error
C310454544 Current Value of Reported HSUPA Power
C310454545 Maximun Value of Reported HSUPA Power
C310454546 Minimum Value of Reported HSUPA Power
C310454547 Summation of Reported HSUPA Power
C310454548 The Times of Reported HSUPA Power
C310840012 Current Utilization Ratio of HSUPA Uplink CE
C310840013 Maximum Utilization Ratio of HSUPA Uplink CE
C310840014 Minimum Utilization Ratio of HSUPA Uplink CE
C310840015 Summation of Utilization Ratio of HSUPA Uplink CE
C310464563 HSUPA Cell In Service Time
C310030492 Number of Conversational class in E-DCH in the best cell
C310030493 Number of Streaming class in E-DCH in the best cell
C310030494 Number of Interactive class in E-DCH in the best cell
C310030495 Number of Background class in E-DCH in the best cell
C310030566 Average number of Conversational class in E-DCH in the best cell
C310030567 Average number of Streaming class in E-DCH in the best cell

C310030568 Average number of Interactive class in E-DCH in the best cell
C310030569 Average number of Background class in E-DCH in the best cell
C310030660 Number of Conversational class in E-DCH in the non-best cell
C310030661 Number of Streaming class in E-DCH in the non-best cell
C310030662 Number of Interactive class in E-DCH in the non-best cell
C310030663 Number of Background class in E-DCH in the non-best cell
Average number of Conversational class in E-DCH in the non-best

C310030730
cell
C310030731 Average number of Streaming class in E-DCH in the non-best cell
C310030732 Average number of Interactive class in E-DCH in the non-best cell
C310030733 Average number of Background class in E-DCH in the non-best cell
C310063437 Number of Conversational class in E-DCH in the DRNC cell
C310063438 Number of Streaming class in E-DCH in the DRNC cell
C310063439 Number of Interactive class in E-DCH in the DRNC cell
C310063440 Number of Background class in E-DCH in the DRNC cell
C310063511 Average number of Conversational class in E-DCH in the DRNC cell
C310063512 Average number of Streaming class in E-DCH in the DRNC cell
C310063513 Average number of Interactive class in E-DCH in the DRNC cell
C310063514 Average number of Background class in E-DCH in the DRNC cell
C310210961 Total PS HSUPA RAB connection set-up time
C310484610 Times of Successfully Applying HSUPA User Resource
C310484611 Times of failed Applying HSUPA User Resource
Number of attempted access services,HSUPA conversation class

C310504789
services
Number of attempted access services,HSUPA Background class

C310504790
services
Number of attempted access services,HSUPA Streaming class

C310504791
services
Number of attempted access services,HSUPA Streaming class

C310504792
services
C310504793 Number of rejected services,HSUPA conversation class services
C310504794 Number of rejected services,HSUPA Interactive class services
C310504795 Number of rejected services,HSUPA Background class services

C310504796 Number of rejected services,HSUPA Streaming class services
Number of users pre-empted caused by congestion control, HSUPA

C311775721
user number limit
C310484614 Times of Successfully Applying EdchSignature Resource
C310484615 Times of failed Applying EdchSignature Resource
C310504763 Number of rejected services,EDCH not available
C310505615 Number of rejected services,E-DCH uplink_RTWP limit
C310505616 Number of rejected services,E-DCH uplink user limit
C310505617 Number of rejected services,E-DCH uplink CREDIT_LIMIT
C310505618 Number of rejected services,E-DCH uplink Channel Capability LIMIT
5.1.5 Moblity Statistics

Number of active set update attempted to add cell for E-DCH, softer
C310322297
handover
Number of active set update attempted to add cell for E-DCH, soft
C310322298
handover
Number of active set update attempted to add cell for E-DCH, Iur soft
C310322299
handover
Number of active set update failed to add cell for E-DCH, softer
C310322300
handover
Number of active set update failed to add cell for E-DCH, soft
C310322301
handover
Number of active set update failed to add cell for E-DCH, Iur soft
C310322302
handover
Number of active set update failed to add cell for E-DCH,configuration

C310322303
unsupported
Number of active set update failed to add cell for E-DCH,Physical

C310322304
Channel Failure
Number of active set update failed to add cell for E-DCH,Incompatible

C310322305
Simultaneous Reconfiguration
Number of active set update failed to add cell for E-DCH,Compress

C310322306
Mode Error
Number of active set update failed to add cell for E-DCH,Protocol

C310322307
Error

Number of active set update failed to add cell for E-DCH,Cell Update
C310322308
Occurred
Number of active set update failed to add cell for E-DCH,invalid

C310322309
configuration
Number of active set update failed to add cell for E-DCH,configuration

C310322310
incomplete
C310322311 Number of active set update failed to add cell for E-DCH,No Reply
C310322312 Number of active set update failed to add cell for E-DCH,Other Failure
Number of active set update attempted to del cell for E-DCH.softer

C310322313
handover
Number of active set update attempted to del cell for E-DCH,soft

C310322314
handover
Number of active set update attempted to del cell for E-DCH,Iur soft
C310322315
handover
Number of active set update failed to del cell for E-DCH,configuration

C310322316
unsupported
Number of active set update failed to del cell for E-DCH,Physical

C310322317
Channel Failure
Number of active set update failed to del cell for E-DCH,Incompatible

C310322318
Number of active set update failed to del cell for E-DCH,Compress

C310322319
Mode Error
C310322320 Number of active set update failed to del cell for E-DCH,Protocol Error
Number of active set update failed to del cell for E-DCH,Cell Update
C310322321
Occurred
Number of active set update failed to del cell for E-DCH,invalid

C310322322
configuration
Number of active set update failed to del cell for E-DCH,configuration

C310322323
incomplete
C310322324 Number of active set update failed to del cell for E-DCH,No Reply
C310322325 Number of active set update failed to del cell for E-DCH,Other Failure
Number of active set update attempted to add cell for

C310322326
E-DCH,Conversational class

C310322327
E-DCH,Streaming class


C310322328
E-DCH,Interactive class

C310322329
E-DCH,Background class
Number of active set update failed to del cell for

C310322330
Number of active set update failed to del cell for E-DCH,Streaming

C310322331
class
Number of active set update failed to del cell for E-DCH,Interactive

C310322332
class
Number of active set update failed to del cell for E-DCH,Background

C310322333
class
Number of active set update attempted to del cell for

C310322334

C310322335
E-DCH,Streaming class

C310322336
E-DCH,Interactive class

C310322337
E-DCH,Background class
Number of active set update failed to del cell for

C310322338
Number of active set update failed to del cell for E-DCH,Streaming

C310322339
class
Number of active set update failed to del cell for E-DCH,Interactive

C310322340
class
Number of active set update failed to del cell for E-DCH,Background

C310322341
class
C310322361 Duration of one E-DCH Radio Link state
C310322362 Duration of two E-DCH radio Link state
C310322363 Duration of three E-DCH radio Link state
C310322364 Duration of four E-DCH radio Link state
C310322475 Number of UE having one E-DCH active set cell in cell
C310322476 Number of UE having two E-DCH active set cell in cell
C310322477 Number of UE having three E-DCH active set cell in cell

C310322478 Number of UE having four E-DCH active set cell in cell
C310322479 Average number of UE having one E-DCH active set cell in cell
C310322480 Average number of UE having two E-DCH active set cell in cell
C310322481 Average number of UE having three E-DCH active set cell in cell
C310322482 Average number of UE having four E-DCH active set cell in cell
C310322483 Max number of UE having one E-DCH active set cell in cell
C310322484 Max number of UE having two E-DCH active set cell in cell
C310322485 Max number of UE having three E-DCH active set cell in cell
C310322486 Max number of UE having four E-DCH active set cell in cell
Number of outgoing inter-RNC intra frequency hard handover via Iur

C310332575
attempt for E-DCH
Number of outgoing inter-RNC inter frequency hard handover via Iur

C310332582
attempt for E-DCH
Number of outgoing inter-RNC intra frequency hard handover via Iur

C310332589
failure for E-DCH
Number of outgoing inter-RNC inter frequency hard handover via Iur

C310332596
failure for E-DCH
C310332679 Number of outgoing intra frequency hard handover attempt,E-DCH
C310332686 Number of outgoing inter frequency hard handover attempt,E-DCH
C310332693 Number of outgoing intra frequency hard handover failure,E-DCH
C310332700 Number of outgoing inter frequency hard handover failure,E-DCH
C310342707 Number of attempted relocation preparation ,E-DCH
C310342714 Number of failure relocation preparation ,E-DCH
C310342721 Number of attempted outgoing relocation,E-DCH
C310342728 Number of failure outgoing relocation,E-DCH
C310353035 Number of attempted outgoing inter-RAT handovers,E-DCH
Number of failed relocation preparation for outgoing E-DCH inter-RAT

C310353036
handovers,TRELOCalloc Expiry

C310353037
handovers,Relocation Failure In Target CN/RNC Or Target System

C310353038 handovers,Relocation Not Supported In Target RNC Or Target
System
C310353039 Number of failed relocation preparation for outgoing E-DCH inter-RAT

handovers,Relocation Target not allowed

C310353040
handovers,No Radio Resources Available in Target Cell

C310353041 handovers,Traffic Load In The Target Cell Higher Than In The Source
Cell

C310353042
handovers,Unknown Target RNC

C310353043
handovers,Other Causes

C310353044
handovers,No Reply
Number of attempted outgoing inter-RAT

C310353045
handovers,HS-DSCH/E-DCH VoIP
Number of failed relocation preparation for outgoing

C310353046
HS-DSCH/E-DCH VoIP inter-RAT handovers,TRELOCalloc Expiry

C310353047 HS-DSCH/E-DCH VoIP inter-RAT handovers,Relocation Failure In
Target CN/RNC Or Target System

C310353048 HS-DSCH/E-DCH VoIP inter-RAT handovers,Relocation Not
Supported In Target RNC Or Target System

C310353049 HS-DSCH/E-DCH VoIP inter-RAT handovers,Relocation Target not
allowed

C310353050 HS-DSCH/E-DCH VoIP inter-RAT handovers,No Radio Resources
Available in Target Cell

C310353051 HS-DSCH/E-DCH VoIP inter-RAT handovers,Traffic Load In The
Target Cell Higher Than In The Source Cell

C310353052
HS-DSCH/E-DCH VoIP inter-RAT handovers,Unknown Target RNC

C310353053
HS-DSCH/E-DCH VoIP inter-RAT handovers,Other Causes

C310353054
HS-DSCH/E-DCH VoIP inter-RAT handovers,No Reply

C310353104 Number of attempted outgoing inter-RAT handovers,E-DCH
C310353105 Number of E-DCH to 2G handover failure,Configuration Error
C310353106 Number of E-DCH to 2G handover failure,Physical Channel Failure
C310353107 Number of E-DCH to 2G handover failure,Protocol Error
C310353108 Number of E-DCH to 2G handover failure,Inter-RAT Protocol Error
C310353109 Number of E-DCH to 2G handover failure,Unspecified Failure
C310353110 Number of E-DCH to 2G handover failure,No Reply

C310353111
handovers,HS-DSCH/E-DCH VoIP
Number of HS-DSCH/E-DCH VoIP to 2G handover

C310353112
failure,Configuration Error
Number of HS-DSCH/E-DCH VoIP to 2G handover failure,Physical

C310353113
Channel Failure
Number of HS-DSCH/E-DCH VoIP to 2G handover failure,Protocol

C310353114
Error
Number of HS-DSCH/E-DCH VoIP to 2G handover failure,Inter-RAT

C310353115
Protocol Error
Number of HS-DSCH/E-DCH VoIP to 2G handover failure,Unspecified

C310353116
Failure
C310353117 Number of HS-DSCH/E-DCH VoIP to 2G handover failure,No Reply
Number of attempted outgoing inter-RAT handovers,E-DCH based on

C310353174
RSCP

C310353175
EcN0

C310353176
UETxP

C310353177
DLTxP
Number of successful outgoing inter-RAT handovers,E-DCH based

C310353178
on RSCP

C310353179
on EcN0

C310353180
on UETxP
C310353181 Number of successful outgoing inter-RAT handovers,E-DCH based

on DLTxP

C310353190
handovers,HS-DSCH/E-DCH VoIP based on RSCP

C310353191
handovers,HS-DSCH/E-DCH VoIP based on EcN0

C310353192
handovers,HS-DSCH/E-DCH VoIP based on UETxP

C310353193
handovers,HS-DSCH/E-DCH VoIP based on DLTxP
Number of successful outgoing inter-RAT

C310353194
handovers,HS-DSCH/E-DCH VoIP based on RSCP

C310353195
handovers,HS-DSCH/E-DCH VoIP based on EcN0

C310353196
handovers,HS-DSCH/E-DCH VoIP based on UETxP

C310353197
handovers,HS-DSCH/E-DCH VoIP based on DLTxP
C310363263 Number of intra frequency E-DCH serving cell change attempt
Number of intra frequency E-DCH serving cell change

C310363264
failure,configuration unsupported
Number of intra frequency E-DCH serving cell change failure,Physical

C310363265
Channel Failure

C310363266
failure,Incompatible Simultaneous Reconfiguration

C310363267
failure,Compress Mode Error
Number of intra frequency E-DCH serving cell change failure,Protocol

C310363268
Error
Number of intra frequency E-DCH serving cell change failure,Cell

C310363269
Update Occurred
Number of intra frequency E-DCH serving cell change failure,invalid

C310363270
configuration

C310363271
failure,configuration incomplete
Number of intra frequency E-DCH serving cell change failure,No

C310363272
Reply

Number of intra frequency E-DCH serving cell change failure,Other

C310363273
Causes
C310363274 Number of inter frequency E-DCH serving cell change attempt
Number of inter frequency E-DCH serving cell change

C310363275
failure,configuration unsupported
Number of inter frequency E-DCH serving cell change failure,Physical

C310363276
Channel Failure

C310363277
failure,Incompatible Simultaneous Reconfiguration

C310363278
failure,Compress Mode Error
Number of inter frequency E-DCH serving cell change failure,Protocol

C310363279
Error
Number of inter frequency E-DCH serving cell change failure,Cell

C310363280
Update Occurred
Number of inter frequency E-DCH serving cell change failure,invalid

C310363281
configuration

C310363282
failure,configuration incomplete
Number of inter frequency E-DCH serving cell change failure,No

C310363283
Reply
Number of inter frequency E-DCH serving cell change failure,Other

C310363284
Causes
C310363285 Number of Iur E-DCH serving cell change attempt
Number of Iur E-DCH serving cell change failure,configuration

C310363286
unsupported
Number of Iur E-DCH serving cell change failure,Physical Channel

C310363287
Failure
Number of Iur E-DCH serving cell change failure,Incompatible

C310363288
Number of Iur E-DCH serving cell change failure,Compress Mode

C310363289
Error
C310363290 Number of Iur E-DCH serving cell change failure,Protocol Error
Number of Iur E-DCH serving cell change failure,Cell Update

C310363291
Occurred
C310363292 Number of Iur E-DCH serving cell change failure,invalid configuration

Number of Iur E-DCH serving cell change failure,configuration

C310363293
incomplete
C310363294 Number of Iur E-DCH serving cell change failure,No Reply
C310363295 Number of Iur E-DCH serving cell change failure,Other Causes
C310393976 Number of intra frequency E-DCH to DCH attempt due to moving
Number of intra frequency E-DCH to DCH failure due to

C310393977
moving,Configuration unsupport

C310393978
moving,Configuration invalid

C310393979
moving,Configuration Incomplete

C310393980
moving,Physical Channel Failure

C310393981
moving,Incompatible Simultaneous Reconfiguration

C310393982
moving,Compress Mode Error

C310393983
moving,Protocol Error
Number of intra frequency E-DCH to DCH failure due to moving,Cell

C310393984
Update Occurred
Number of intra frequency E-DCH to DCH failure due to moving,No

C310393985
Reply
Number of intra frequency E-DCH to DCH failure due to moving,Other

C310393986
Causes
C310393987 Number of inter frequency E-DCH to DCH attempt due to moving
Number of inter frequency E-DCH to DCH failure due to

C310393988

C310393989

C310393990

C310393991

C310393992


C310393993

C310393994
Number of inter frequency E-DCH to DCH failure due to moving,Cell

C310393995
Update Occurred
Number of inter frequency E-DCH to DCH failure due to moving,No

C310393996
Reply
Number of inter frequency E-DCH to DCH failure due to moving,Other

C310393997
Causes
C310393998 Number of intra frequency DCH to E-DCH attempt due to moving
Number of intra frequency DCH to E-DCH failure due to

C310393999

C310394000

C310394001

C310394002

C310394003

C310394004

C310394005
Number of intra frequency DCH to E-DCH failure due to moving,Cell

C310394006
Update Occurred
Number of intra frequency DCH to E-DCH failure due to moving,No

C310394007
Reply
Number of intra frequency DCH to E-DCH failure due to moving,Other

C310394008
Causes
C310394009 Number of inter frequency DCH to E-DCH attempt due to moving
Number of inter frequency DCH to E-DCH failure due to

C310394010

C310394011


C310394012

C310394013

C310394014

C310394015

C310394016
Number of inter frequency DCH to E-DCH failure due to moving,Cell

C310394017
Update Occurred
Number of inter frequency DCH to E-DCH failure due to moving,No

C310394018
Reply
Number of inter frequency DCH to E-DCH failure due to moving,Other

C310394019
Causes
Number of channel changing in UE only one RAB E-DCH TO DCH to

C310394022
moving ,intra frequency
Number of channel changing in UE only one RAB DCH TO E-DCH to

C310394023
Number of channel changing in UE only one RAB E-DCH TO DCH to

C310394026
moving ,inter frequency
Number of channel changing in UE only one RAB DCH TO E-DCH to

C310394027
Number of successful channel changing in UE only one RAB E-DCH

C310394030
TO DCH to moving ,intra frequency
Number of successful channel changing in UE only one RAB DCH TO

C310394031
E-DCH to moving ,intra frequency
Number of successful channel changing in UE only one RAB E-DCH

C310394034
TO DCH to moving ,inter frequency
Number of successful channel changing in UE only one RAB DCH TO

C310394035
E-DCH to moving ,inter frequency
Number of channel changing in UE multi-RAB E-DCH TO DCH to

C310394038
Number of channel changing in UE multi-RAB DCH TO E-DCH to

C310394039

Number of channel changing in UE multi-RAB E-DCH TO DCH to

C310394042
Number of channel changing in UE multi-RAB DCH TO E-DCH to

C310394043
Number of successful channel changing in UE multi-RAB E-DCH TO

C310394046
DCH to moving ,intra frequency
Number of successful channel changing in UE multi-RAB DCH TO

C310394047
E-DCH to moving ,intra frequency
Number of successful channel changing in UE multi-RAB E-DCH TO

C310394050
DCH to moving ,inter frequency
Number of successful channel changing in UE multi-RAB DCH TO

C310394051
E-DCH to moving ,inter frequency
C310394074 Number of E-DCH to DCH attempt due to moving over Iur
Number of E-DCH to DCH failure due to moving(over

C310394075
Iur),Configuration unsupport

C310394076
Iur),Configuration invalid

C310394077
Iur),Configuration Incomplete
Number of E-DCH to DCH failure due to moving(over Iur),Physical

C310394078
Channel Failure

C310394079
Iur),Incompatible Simultaneous Reconfiguration
Number of E-DCH to DCH failure due to moving(over Iur),Compress

C310394080
Mode Error
Number of E-DCH to DCH failure due to moving(over Iur),Protocol

C310394081
Error
Number of E-DCH to DCH failure due to moving(over Iur),Cell

C310394082
Update Occurred
C310394083 Number of E-DCH to DCH failure due to moving(over Iur),No Reply
Number of E-DCH to DCH failure due to moving(over Iur),Other

C310394084
Causes
C310394085 Number of DCH to E-DCH attempt due to moving over Iur
Number of DCH to E-DCH failure due to moving(over

C310394086
Iur),Configuration unsupport
C310394087 Number of DCH to E-DCH failure due to moving(over

Iur),Configuration invalid

C310394088
Iur),Configuration Incomplete
Number of DCH to E-DCH failure due to moving(over Iur),Physical

C310394089
Channel Failure

C310394090
Iur),Incompatible Simultaneous Reconfiguration
Number of DCH to E-DCH failure due to moving(over Iur),Compress

C310394091
Mode Error
Number of DCH to E-DCH failure due to moving(over Iur),Protocol

C310394092
Error
Number of DCH to E-DCH failure due to moving(over Iur),Cell

C310394093
Update Occurred
C310394094 Number of DCH to E-DCH failure due to moving(over Iur),No Reply
Number of DCH to E-DCH failure due to moving(over Iur),Other

C310394095
Causes
5.1.6 Channel Switching Statistics

C310414182 Number of channel successful changing from HSUPA toDCH,PS-C
C310414183 Number of channel successful changing from HSUPA toDCH,PS-S
C310414184 Number of channel successful changing from HSUPA toDCH,PS-I
C310414185 Number of channel successful changing from HSUPA toDCH,PS-B
C310414186 Number of channel successful changing from HSUPA toRACH,PS-I
C310414187 Number of channel successful changing from HSUPA toRACH,PS-B
C310414188 Number of channel successful changing from HSUPA toPCH,PS-I
C310414189 Number of channel successful changing from HSUPA toPCH,PS-B
Number of channel successful changing from HSUPA,UE HSUPA

C310414190
categories 1

C310414191
categories 2

C310414192
categories 3

C310414193
categories 4


C310414194
categories 5

C310414195
categories 6

C310414196
categories 7
Number of channel successful changing for first access,HSUPA to

C310414199
DCH
Number of channel successful changing for first access,DCH to

C310414200
HSUPA
Number of intra frequency Transport Channel Changing attempt,

C310414104
E-DCH to DCH
Number of intra frequency Transport Channel Changing attempt, DCH

C310414105
to E-DCH

C310414106
E-DCH to RACH

C310414107
RACH to E-DCH
Number of intra frequency Transport Channel successful Changing

C310414116
attempt, E-DCH to DCH

C310414117
attempt, DCH to E-DCH

C310414118
attempt, E-DCH to RACH

C310414119
attempt, RACH to E-DCH
Number of inter frequency Transport Channel Changing attempt,

C310414138
E-DCH to DCH
Number of inter frequency Transport Channel Changing attempt, DCH

C310414139
to E-DCH

C310414140
E-DCH to RACH

C310414141
RACH to E-DCH
Number of inter frequency Transport Channel successful Changing

C310414150
attempt, E-DCH to DCH


C310414151
attempt, DCH to E-DCH

C310414152
attempt, E-DCH to RACH

C310414153
attempt, RACH to E-DCH
5.2 Alarm List
This feature has no related alarm.
6 Glossary
3GPP 3rd Generation Partnership Project
ACK ACKnowledgement
ARQ Automatic Repeat Request
BLER Block Error Rate
BPSK Binary phase shift keying
CDMA Code Division Multiple Access
DCH Dedicated Channel
DL Downlink (Forward link)
DPCCH Dedicated Physical Control Channel

DPCH Dedicated Physical Channel
DPDCH Dedicated Physical Data Channel
E-AGCH E-DCH Absolute Grant Channel
E-RGCH E-DCH Relative Grant Channel
E-HICH E-DCH HARQ Acknowledgement Indicator Channel
E-TFCI E-DCH Transport Format Combination Indicator
HARQ Hybrid Automatic Retransmission Request
HS-DPCCH High Speed Dedicated Physical Control Channel
HS-DSCH High Speed Downlink Shared Channel
HS-PDSCH High Speed Physical Downlink Shared Channel
HS-SCCH High Speed Shared Control Channel
HSDPA High Speed Downlink Packet Access
HSPA High Speed Packet Access
HSUPA High Speed Uplink Packet Access
Kbps kilo-bits per second
MAC Medium Access Control
Mbps Mega-bits per second

NACK Negative ACKnowledgement
OMCR OMC of the RNC
QPSK Quaternary Phase Shift Keying
RAB Radio Access Bearer
RLC Radio Link Control
RNC Radio Network Controller
RR Round Robin
RRC Radio Resource Control
RoT Rise Over Thermal
SAW Stop And Wait
TFC Transport Format Combination
TTI Transmission Time Interval
UE User Equipment
UTRAN Universal Terrestrial Radio Access Network

WCDMA Wideband Code Division Multiple Access

ZTE - UMTS HSUPA Intro Feature Guide PDF

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

ZTE - UMTS HSUPA Intro Feature Guide PDF

Cargado por

Copyright:

Formatos disponibles

HSUPA Introduction Feature

HSUPA Introduction Feature Guide

1. 1 Feature Attributes: Modified the

© 2014 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

1 Feature Attributes ........................................................................................... 5

ZTE Confidential Proprietary 2

3.4.5 ZWF25-04-001 Admission Control for HSUPA Service ...................................... 26

4 Parameters and Configurations ................................................................. 32

5 Counter and Alarm .......................................................................................... 37

ZTE Confidential Proprietary 3

Figure 3-1 Architecture of the HSUPA Protocol................................................................... 6

Table 3-1 Timeslot Formats of the E-DPDCH ..................................................................... 8

ZTE Confidential Proprietary 4

Mutual exclusion: [None]

ZTE Confidential Proprietary 5

the HSUPA network.

3.1 Architecture of HSUPA

HSUPA is the enhanced uplink technology of the WCDMA. In system architecture,

Figure 3-1 Architecture of the HSUPA Protocol

DTCH DCCH DCCH DTCH

PHY PHY TNL TNL TNL TNL

ZTE Confidential Proprietary 6

3.2 Basic Principle of HSUPA

3.2.1 Physical Channels Introduced to HSUPA

3.2.1.1 Introduction to the E-DPDCH (E-DCH Dedicated Physical Data Channel)

ZTE Confidential Proprietary 7

Figure 3-2 Frame Structure of the E-DPDCH

When the spreading factor is 2 or 4, the E-DPDCH supports multi-code transmission.

Table 3-1 Timeslot Formats of the E-DPDCH

3.2.1.2 Introduction to the E-DPCCH (E-DCH Dedicated Physical Control Channel)

E-TFCI: the transmission format combination indicator of the E-DCH (7bit)

ZTE Confidential Proprietary 8

RSN: HARQ retransmission sequence number (2bit)

Happy Bit: scheduling feedback bit from the UE (1bit)

Figure 3-3 Frame Structure of the E-DPCCH

3.2.1.3 Introduction to the E-AGCH (E-DCH Absolute Grant Channel)

Figure 3-4 Frame Structure of the E-AGCH

ZTE Confidential Proprietary 9

3.2.1.4 Introduction to the E-RGCH (E-DCH Relative Grant Channel)

Figure 3-5 Frame Structure of the E-RGCH

ZTE Confidential Proprietary 10

3.2.1.5 Introduction to the E-HICH (E-DCH HARQ Acknowledge Indication

3.2.2 Basic Principles of HSUPA

ZTE Confidential Proprietary 11

ZTE Confidential Proprietary 12

Figure 3-6 Basic Principles of HSUPA

1 TNL bearer per MAC-d flow

NodeBs Iur/Iub FP NodeBd FP

ZTE Confidential Proprietary 13

ZTE Confidential Proprietary 14

3.3 Basic Functions of HSUPA

3.3.1 ZWF25-01-005 HSUPA Common Carrier with R99

3.3.2 ZWF25-01-005 HSUPA Dedicated Carrier

ZTE Confidential Proprietary 15

3.3.3 ZWF25-01-003 HSUPA Cell Indicator in Idle Mode

3.3.4 ZWF25-01-004 HSUPA UE Category Support

ZTE Confidential Proprietary 16

Figure 3-7 Requirements of 3GPP on HSUPA UE Categories

3.3.5 ZWF25-01-024 HSUPA 2ms TTI

3.3.6 ZWF25-01-014 HSUPA HARQ

ZTE Confidential Proprietary 17

3.3.7 ZWF25-01-021 HSUPA 1.45Mbps Peak Bit Rate