Professional Documents
Culture Documents
Guide
WCDMA RAN
HSDPA Introduction Feature Guide
TABLE OF CONTENTS
2 Overview ........................................................................................................... 5
6 Glossary ......................................................................................................... 84
FIGURES
TABLES
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]
Involved NEs:
UE Node B RNC MSCS MGW SGSN GGSN HLR
- - - -
Note:
*-: Not involved
*: Involved
Dependency: [None]
Note: [None]
2 Overview
High-Speed Downlink Packet Access (HSDPA) is a downlink enhanced technology
introduced by 3GPP R5. HSDPA is intended to enhance the downlink packet access
capability. Within the 5 MHz carrier bandwidth, HSDPA introduces new MAC-hs entities
and physical channels to the protocol stack at the UTRAN side without changing the
WCDMA network architecture and multiple access mode of the original R99/R4 version.
In addition, HSDPA adopts the following technologies:
As a result, HSDPA technology increases the downlink peak rate from 2 Mbps (in the
R99 version) to 14.4 Mbps. It also increases the system capacity and spectrum utilization.
Generally, HSDPA is an important technology that increases the downlink capacity and
data service rate for a WCDMA network.
3 Feature Introduction
DTCH DTCH
MAC-d MAC-d
As shown in the figure, the major difference between HSDPA and R99 is that the
MAC-hs sublayer is introduced in Node B and UE respectively. Through HS-DSCH FP,
the MAC-d entity of the RNC transfers the MAC-d PDU to the MAC-hs entity of Node B.
The MAC-hs entity of Node B transfers the MAC-hs PDU to the peer entity MAC-hs of the
UE through the Uu interface.
3. Improves the link adaptation performance of the AMC technology. The AMC
technology adjusts the modulation and coding mode according to the channel
quality. Its performance is sensitive to the delay in reporting the channel quality. The
longer the delay is, the worse the link adaptation performance is.
To implement the function of the HSDPA, new channels are introduced in the physical
layer of the 3GPP R5.
High-Speed Shared Control Channel (HS-SCCH): the signaling channel used for
the downlink in the physical layer
3.2.1.1 HS-PDSCH
Data
Ndata 1 bits
Tslot = 2560 chips, M*160 bits
1 subframe: Tf = 2 ms
M refers to the bit number represented by each modulation symbol. For QPSK, M is
equal to 2 and the bit number of the physical channel in the 2ms TTI is 960, which means
the bit rate is 480 kbps. For 16QAM, M is equal to 4 and the bit number of the physical
channel in the 2ms TTI is 1,920, which means the bit rate is 960 kbps. If 15 code
channels transmit data concurrently and the modulation mode is 16QAM, the peak rate
of the physical layer is 14.4 Mbps and the peak rate of the MAC-hs layer is 13.976 Mbps,
as shown in Figure 3-3.
The figure shows the coding process when the HS-PDSCH transmits the largest
transport block within 2ms TTI. As shown in Figure 3-3, the largest MAC-hs PDU to be
transmitted is 27,952 bits in size and the largest bit number of the physical channel is
3.2.1.2 HS-SCCH
The HS-SCCH is a physical downlink channel. It is introduced to carry the physical layer
signaling required by the coding HS-PDSCH. The spreading factor is 128, the modulation
mode is QPSK, channel codes are convolutional codes, and the first-order rate is used
for matching. As shown in Figure 3-4, the signaling carried by the HS-SCCH comprises
two parts:
The first part (Slot #0) includes channelization codes and modulation mode. The UE
decodes the information in Slot #1 to enable the HS-PDSCH receiving process at
the Slot #2 start time and avoid the chip-level data cache at the UE side.
The second part (Slot #1 and Slot #2) includes the size indication of transport block,
HARQ process number, RV parameter, and indication of new data.
The information in the second part is decoded within a certain period upon completion of
Slot #2. Before such information is decoded, the symbol-level data of HS-PDSCH
decoding is buffered. After such information is decoded, the HS-PDSCH undergoes rate
de-matching, soft bit combination, and Turbo decoding.
Data
Ndata 1 bits
Tslot = 2560 chips, 40 bits
1 subframe: Tf = 2 ms
As shown in the figure, the HS-SCCH transmits a fixed number of bits within 2ms TTI.
According to the maximum number of users supported by code multiplexing, the UTRAN
allocates a corresponding number of HS-SCCH code channels. Each UE can monitor a
maximum of four HS-SCCHs. Usually, a maximum of four users are scheduled within
one TTI (thus preventing the HS-SCCHs from consuming excessive power and code
channel resources). The number of HS-SCCHs can be configured according to the
power resource and code channel resource of the HSDPA service. If a UE is scheduled
continuously, the HS-SCCHs should use the same code channel within continuous TTIs,
so as to reduce UE complexity and enhance the reliability of signaling. In R5 and R6, the
HS-SCCH structure remains unchanged.
3.2.1.3 HS-DPCCH
HARQ-ACK CQI
Part I: The ACK/NACK domain indicates the decoding result of the HS-PDSCH. 10 bits
are used to indicate the downlink decoding information, including ACK/NACK/DTX. The
ACK domain indicates that the downlink HS-SCCH and HS-PDSCH decoding results are
correct. The NACK domain indicates that the downlink HS-SCCH decoding result is
correct but the HS-PDSCH decoding result is not correct. The DTX domain indicates that
the downlink HS-SCCH decoding result is not correct and the HS-PDSCH is not
demodulated.
Part II: The CQI domain indicates the channel quality of the UE. The CQI value ranges
from 0 to 30. 0 indicates that the channel quality is very bad and thus transmission is not
allowed. The CQI values of 1 to 30 indicates that the supported channel quality ranges
from single-code-channel QPSK transmission to 15-code-channel 16QAM transmission
(including diversified rates).
If downlink data needs to be transmitted after the UE accesses the HSDPA network, the
UE periodically reports the CQI to the Node B through the uplink HS-DPCCH, so as to
indicate the data rate (the coding and modulation policy and number of multiple codes)
supported by the UE in the current radio environment. After receiving the CQI reported
by the UE, the Node B selects an appropriate modulation mode (QPSK or 16QAM) and
the number of code channels according to the QoS of the transmitted data, radio
environment of the UE, and capability level of the UE, and sends the information to the
UE through the downlink HS-SCCH. The UE first receives the signaling information of
the HS-SCCH, and begins to receive the downlink data packets in the HS-PDSCH that
the Node B sends to the UE after two timeslots. After receiving each data packet, the UE
sends an ACK/NACK message to the Node B through the uplink HS-DPCCH, so that the
Node B can know whether the UE has received the downlink data packet correctly.
For R99, the retransmission of the lowest layer is RLC layer retransmission. The delay of
RLC layer retransmission includes the delay of physical layer processing and delay of
Iub interface retransmission. The delay of Iub interface retransmission accounts for a
large proportion. Unlike R99, HSDPA also supports physical layer retransmission. The
RLC is responsible for retransmission in case packets are lost in the physical layer. The
physical layer of HSDPA uses the 2-ms short frames and R99 uses the 10-ms, 20-ms,
40-ms, and 80-ms long TTIs. Therefore, the delay of the physical layer of HSDPA is far
lower than that of R99. The Round Trip Time (RTT) of HSDPA can be as low as 70 to 80
ms, but the RTT of R99 is 120 to 150 ms.
HSDPA can share a carrier frequency with R99. A cell can provide R99 services and
HSDPA services at the same time, and public resources (including channelization codes,
Node B transmit power, and Iub interface transmission bandwidth) of the cell can be
allocated between R99 services and HSDPA services.
The R99 CS/PS service shares frequency and power with the high-speed data
service supported by HSDPA, thus utilizing system resources fully.
Services can be selected flexibly, thus avoiding UE cell selection and camping
caused by the independent carrier frequency.
If an operator has limited frequency resources but has to provide the R99 services, the
mode of sharing the carrier frequency allows the operator to provide high-speed data
services through the residual resources of R99. However, the peak rate and throughput
provided by the cell are reduced and the experience of data service users is affected
when the R99 services occupy resources.
HSDPA can also use an independent carrier frequency. HSDPA uses a different carrier
frequency from R99 for building a dedicated network layer. In addition to the independent
carrier frequency of HSDPA, the carrier frequency of R99 should also be deployed so as
to support the traditional CS service and low-speed PS service (carry the DCH). The R99
network offers the solution to coverage and the high-speed PS service is carried over the
HSDPA network first.
The independent carrier frequency mode has the following advantages: independent
networking, simple planning, low adjacent-channel interference, and higher peak
capacity. HSDPA needs to occupy a separate precious frequency and related resources,
and incurs high expenses of network construction. In the initial phase of network
operation, the independent carrier frequency mode may cause the low degree of sharing.
Due to users different service needs (CS or PS), inter-frequency handover can occur,
thus affecting network reliability and user experience.
If the operator has more frequency resources than required by the R99 services, an
independent carrier frequency can be deployed to provide the HSDPA services. As the
spectrum utilization of the HS-DSCH is higher than that of the DCH, the independent
carrier frequency provides the following benefits:
In the initial phase of network construction, the independent carrier frequency mode is
not recommended. However, the number of PS users increases while the network is
developed to a certain phase or the application is an indoor network scenario. In this
case, a separate frequency can be deployed to build a network that only supports the PS
service, and HSDPA and R99 share another carrier frequency to win common mobile
users.
The indicator of an HSDPA cell is broadcasted in the SIB5 or SIB5bis system message.
When searching a cell, an HSDPA UE determines whether the cell supports HSDPA,
displays HSDPA coverage, and decides to select a cell according to the indicator. For
example, an HSDPA data card subscriber can search for the HSDPA-capable carrier
frequency in the same sector. The UE can set the strategy of selecting a cell according to
the cell capability at its discretion.
3GPP R6 introduces the HSDPA cell indicator. To identify a cell, the R5 HSDPA UEs
need to be upgraded to the R6 version.
ZTEs UMTS RAN supports all HSDPA UE capability levels defined by 3GPP. A capability
level reflects the extent to which the UE supports the HSDPA services. For details, refer
to 3GPP TS 25.306.
ZTEs UMTS RAN supports the peak rate of 1.8 Mbps for HSDPA When the UE uses an
interactive service or background service in an HS-DSCH. The peak rate in the MAC
layer can be as high as 1.8 Mbps. The HSDPA UE capability level is 3 to 10 or above,
except 11.
ZTEs UMTS RAN supports the peak rate of 3.6 Mbps for HSDPA. When the UE uses an
interactive service or background service in an HS-DSCH, the peak rate in the MAC
layer can be as high as 3.6 Mbps. The HSDPA UE capability level is 5 to 10 or above,
except 11 to 12.
The HSDPA services are carried by HS-DSCHs. The HS-DSCHs provides higher
channel rate and can be shared by more users through technologies such as high-order
16QAM, AMC, HARQ, and fast scheduling. Generally, HS-DSCHs are suitable to such
high-burst data services as the interactive services and background services. Higher
peak rate can also improve subscriber experience.
ZTEs UMTS RAN supports the maximum rate of 14.4 Mbps in the physical layer.
However, the actual maximum rate depends on the following factors:
UE capability level
System load
ZTEs UMTS RAN allows HSDPA to carry the PS interactive services and background
data services. The RAB parameters comply with the 3GPP TS 34.108 protocol.
No burst occurs
The HS-DSCH provides services for all UEs. An HSDPA cell mainly carries high-speed
data services and burst services, for example, interactive services and background
services. However, streaming services can also be transmitted through HS-DSCHs if
their BER and transmit delay are ensured through an appropriate scheduling
mechanism.
While the streaming services are in the coverage area of the network, the QoS must
remain stable. The QoS should not be degraded when the quality of signals is
deteriorated or when the number of users increases. HSDPA uses the AMC technology,
so users' throughput goes down when the quality of signals is deteriorated. In addition,
HSDPA users share the radio resources of the air interface. Therefore, the throughput of
one or more users goes down if the number of users decreases. However, the
phenomena are contrary to the features of the streaming service. ZTEs UMTS RAN
offers the following solution: The RNC gives a specific parameter identifier to a streaming
service, and Node B provides special services for a streaming service through a
scheduling algorithm and flow control algorithm. The main principles are as follows:
Control the waiting time of the streaming service users to an appropriate level (the
waiting time of the streaming services should be a little shorter than that of
interactive services and background services, so as to ensure the real-time
performance of the streaming services).
For details on the fast scheduling function of HSDPA, refer to ZTE UMTS NodeB HSDPA
Packet Scheduling Feature Guide.
ZTEs UTMS RAN allows HSDPA to carry the PS data service. The RAB parameters
completely comply with the 3GPP TS 34.108 protocol.
ZTEs UMTS RAN allows HSDPA to carry multiple concurrent PS services. The RAB
parameters comply with the 3GPP TS 34.108 protocol.
All the CS services supported by ZTEs UMTS RAN can be concurrent with the PS
AMR voice session services of the CS domain. For details, refer to ZTE UMTS
Services and Radio Access Bearers Feature Guide.
Data session services of the CS domain, for example, the video phone service. For
details, refer to ZTE UMTS Services and Radio Access Bearers Feature Guide.
Data streaming services of the CS domain, for example, the fax service. For details,
refer to ZTE UMTS Services and Radio Access Bearers Feature Guide.
WAMR voice session service of the CS domain. For details, refer to ZTE UMTS
AMR & WB-AMR Feature Guide.
When CS services are concurrent with the PS services carried by HSDPA, users actual
maximum rate depends on the UE capability level, system load, and local radio
environment.
ZTEs UMTS RAN allows HSDPA to carry the CS service and PS service concurrently.
The RAB parameters comply with the 3GPP TS 34.108 protocol.
When ZTEs UMTS RAN uses HSDPA to carry interactive services and background
services, hsNormBitRate can be configured. The RNC configures the GBR for the
interactive/background service according to the hsNormBitRate and sends the setting to
the Node B. When performing HSDPA fast scheduling, the Node B provides the minimum
guaranteed bit rate (GBR) for the interactive/background service.
ZTEs UMTS RAN supports the peak rate of 7.2 Mbps for HSDPA. When the UE uses an
interactive service or background service in an HS-DSCH, the peak rate in the MAC
layer can be as high as 7.2 Mbps. The HSDPA UE capability level is 7 to 10 or above,
except 11 to 12.
ZTEs UMTS RAN supports the peak rate of 14.4 Mbps for HSDPA. When the UE uses
an interactive service or background service in an HS-DSCH, the peak rate in the MAC
layer can be as high as 13.976 Mbps and the peak rate in the physical layer can be as
high as 14.4 Mbps. The HSDPA UE capability level is 10 or above, except 11 to 12.
ZTEs UMTS RAN supports up to 192 concurrent HSDPA users in a cell which is
controlled by the parameter of hsdschTrafLimit. For details, refer to ZTE UMTS
Admission Control Feature Guide.
ZTEs UMTS RAN supports the HS-DPCCH ACK/NACK enhancement function. It can be
switched on or off according to the ackNackEncInd.
ZTEs UMTS RAN supports the Fractional Dedicated Physical Channel (F-DPCH).
The F-DPCH is introduced by R6. When the SRB of the downlink signaling is carried by
the HS-DSCH, the downlink DPCH of the UE only needs to transfer the inner loop power
control information field TPC. To save the code channel resources of the downlink, the
F-DPCH is introduced. The SF of the F-DPCH is 256, each timeslot of the TPC field is 2
bits, and each timeslot of the code channel with the SF of 256 can carry 20 bits.
Therefore, one F-DPCH can implement time division multiplexing for up to 10 UEs, thus
occupying fewer code channels.
512 chips
TPC
(Tx OFF) (Tx OFF)
NTPC bits
1 radio frame: Tf = 10 ms
As shown in the following figure, three UEs use the F-DPCH of the same channelization
code and the offset of the F-DPCH needs to be staggered, thus saving the
channelization codes used by the associated DPCH significantly.
vvv
Any CPICH
10 ms 10 ms
P-CCPCH Radio framewith (SFN modulo 2) = 0 Radio framewith (SFN modulo 2) = 1
UE 1 DPCH DPCH1
Fractional
Dedicated
Physical Channel
HS-PDSCH Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe
Subframes #0 #1 #2 #3 #4 #5 #6 #7
Ttx_diff 0 2 6 9
UL 1 DPCCH
T0
UL 2 DPCCH
UL 3 DPCCH
RAN can provide F-DPCH service only if RNC supports F-DPCH, which corresponds
to rncFdpchSupInd with value 1: Supported, and the target cell supports F-DPCH,
For details on the F-DPCH code resource management function of HSDPA, refer to ZTE
UMTS Code Resource Feature Guide.
The high-speed feature of HSDPA allows the signaling flow in the Uu interface to speed
up and thus reduces the call delay in the subsequent service setup when the SRBs are
carried by HSDPA. On the other hand, the overhead of the downlink channelization
codes can be reduced because of the F-DPCH.
When the SRBs are carried by HSDPA, the DCCH is mapped to the HS-DSCH, the
SRBs are carried by an independent MAC-d Flow, and four SRBs are multiplexed to one
MAC-d Flow. At the RNC side, the appropriate MAC-d Flow parameters are configured
according to the QoS of the SRB. Such parameters include Allocation/Retention Priority
(ARP), preemption, and no preemption. The ARP can be configured to the highest
priority. The Scheduling Priority Indicator (SPI) enjoys the highest priority. The MAC-hs
guaranteed bit rate need not be configured. DiscardTime is configured to 4s. When the
HSDPA scheduler schedules the RRC signaling at the Node B side, the reliability of the
RRC signaling is ensured.
For details on the SRB on HSDPA channel allocation strategy, refer to ZTE UMTS DRBC
Algorithm Feature Guide.
ZTEs UMTS RAN supports seamless handover inside the HSDPA coverage area,
between the HSDPA coverage area and R99 coverage area, and between the HSDPA
coverage area and 2G coverage area.
The cell attribute hspaSptMeth of the R99 coverage area is Not Support HSUPA and
HSDPA.
For improving the compatibility of HSDPA over Iur, the UMTS RAN of ZTE supplies two
more parameters RNCFEATSWITCHBit1 and RNCFEATSWITCHBit4 which can be
configured based on the neighboring RNC. The RNCFEATSWITCHBit1 is used to
configure whether the neighboring RNC supports HSDPA or not. If the neighboring RNC
doesnt support HSDPA, ZTE RNC will transfer HS-DSCH to DCH before performing the
Iur signaling flow. The RNCFEATSWITCHBit4 is configured to indicate whether to use
DSCR or not when doing hard handover SRNS relocation for HS-DSCH configuration.
For details on the mobility management algorithm of HSDPA, refer to ZTE UMTS
Handover Control Feature Guide.
Compared with R99, there are two types of handover in the HSDPA system, that is,
change of HS-DSCH serving cell and migration between the HS-DSCH and DCH.
The HS-DSCH does not support soft handover, but the associated dedicated physical
channels support soft handover. Compared with the handover flow of R99, the handover
flow of HSDPA is changed. Figure 3-9 shows the intra-frequency serving HS-DSCH cell
change.
2. Decide to
Change HS-DSCH
Serving Cell
3. Radio Link Reconfiguration Prepare
4. Radio Link Reconfiguration Prepare
Before the serving cell of the HS-DSCH is changed, the UE is connected to multiple
cells:
The HSDPA service connection to the source cell of Source Serving Node B
1. According to the measurement control of the RNC, the UE measures the quality of
the co-frequency adjacent cells in the adjacent cell list, judges the occurrence of the
co-frequency event (for example, 1D event), and hands in the measurement report
(for example, the 1D events) to the RNC.
2. The RNC decides to change the HS-DSCH serving cell according to the event and
radio resource status reported by the UE.
3. The RNC sends a NBAP message, Radio Link Reconfiguration Prepare, to Source
Serving Node B.
4. The RNC sends an NBAP message, Radio Link Reconfiguration Prepare, to Target
Serving Node B.
7. The RNC sends an NBAP message, Radio Link Reconfiguration Commit, to Source
Serving Node B.
8. The RNC sends an NBAP message, Radio Link Reconfiguration Commit, to Target
Serving Node B.
9. The RNC sends an RRC message, Physical Channel Reconfiguration, to the UE.
10. The UE sends an RRC message, Physical Channel Reconfiguration, to the RNC.
When the UE roams between the HSDPA cell and R99 cell, the migration between the
HS-DSCH and DCH occurs. As the service traffic and radio coverage quality of the UE is
changed in the HSDPA and R99 hybrid cell, the migration between the HS-DSCH and
DCH may occur. The following section describes the channel migration between
intra-frequency cells.
Non-Serving Serving
UE RNC
Node B Node B
1. Measurement Report (e.g. 1D)
2. Decide
HS-DSCHDCH
The flow on the migration from the HS-DSCH to the DCH is as follows:
1. According to the measurement control of the RNC, the UE measures the quality of
the co-frequency adjacent cells in the adjacent cell list, judges the occurrence of the
co-frequency event (for example, 1D event), and hands in the measurement report
(for example, the 1D events) to the RNC.
2. The RNC decides to migrate the HS-DSCH to the DCH according to the event and
radio resource status reported by the UE.
9. The RNC sends an RRC message, Transport Channel Reconfiguration, to the UE.
10. The UE sends an RRC message, Transport Channel Reconfiguration, to the RNC.
2. Decide
DCHHS-DSCH
The flow on the migration from the DCH to the HS-DSCH is as follows:
1. According to the measurement control of the RNC, the UE measures the quality of
the intra-frequency adjacent cells in the adjacent cell list, judges the occurrence of
the intra-frequency event (for example, 1D event), and hands in the measurement
report (for example, the 1D events) to the RNC.
2. The RNC decides to migrate the DCH to the HS-DSCH according to the event
reported by the UE, radio resource status, and UE service status.
3. The RNC sends an NBAP message, Radio Link Setup Request, to Target Serving
Node B.
5. The RNC sends an RRC message, Transport Channel Reconfiguration, to the UE.
7. The RNC sends an NBAP message, Radio Link Delete Request, to Source Node B.
(1) The dynamical channel adjustment function of HSDPA, refer to ZTE UMTS DRBC
Algorithm Feature Guide.
(2) The code resource management function of HSDPA, refer to ZTE UMTS Code
Resource Feature Guide.
(3) The power control function of HSDPA, refer to ZTE UMTS Power Control Feature
Guide.
(4) The admission control function of HSDPA, refer to ZTE UMTS Admission Control
Feature Guide.
(5) The load control function of HSDPA, refer to ZTE UMTS Overload Control Feature
Guide.
(6) The load balance function of HSDPA, refer to ZTE UMTS Load Balance Feature
Guide.
(7) The congestion control function of HSDPA, refer to ZTE UMTS Congestion Control
Feature Guide.
(8) The QoS mapping function of HSDPA, refer to ZTE UMTS QoS Feature Guide.
(9) The flow control function of HSDPA, refer to ZTE UMTS NodeB HSDPA Packet
Scheduling Feature Guide.
In the same scrambling code, there are a total of 16 codes with the SF of 16. Because of
the occupation by the public channel resources, a maximum of 15 channelization codes
are available. Therefore, ZTEs UMTS Node B supports the multiplexing of up to 15
codes within a 2ms TTI. If various factors are taken into account, ZTEs UMTS Node B
allows up to four UEs to be scheduled within a 2ms TTI in a cell, that is, allow a maximum
of four UEs to multiplex the HS-DSCH code channels at the same time.
The HS-PDSCH is shared by all HSDPA users in the cell, thus improving channel
utilization. The sharing mode is code division multiplexing and time division multiplexing.
Code division multiplexing has the following two features:
Transmit the information of multiple users within one TTI at the same time.
Time division multiplexing means that different users can multiplex the same code
resource after the TTI is changed. The number of the channelization codes allocated to
one subscriber within one TTI is restricted by the UE capability level. The UE can select
five, ten, or 15 code words. During code division multiplexing, the channelization codes
can be divided into several subsets, which are allocated to different users. This mode
can support not only the transmission of a small amount of data (in this case, the
transmitted data needs only some channelization codes of the HS-DSCH in the cell), but
also the UE that cannot completely dispread all channelization code sets.
Figure 3-12 HS-DSCH Time Division Multiplexing Structure and Code Division
Multiplexing Structure
The figure shows the example of HSDPA multiplexing. Eight channelization codes
(corresponding to eight HS-PDSCHs) are allocated to HSDPA. These channelization
codes undergo time division multiplexing by the UE, and can also undergo code division
multiplexing within the same TTI. In the first TTI, three channelization codes are
allocated to UE3 and thus three HS-PDSCHs can be used to receive data. Five
channelization codes are allocated to UE1. In this way, channelization codes can be
utilized more flexibly and effectively to suit different UE capability levels. As stipulated by
the protocol, there are 12 or more UE capability levels, which support a maximum of five,
ten, and 15 codes respectively. Therefore, channelization codes need to be allocated to
different subsets, that is, undergo code division multiplexing by different UEs. The
number of channelization codes in each subset is changing. However, the number of
channelization codes allocated to a UE should not exceed the receiving capability of the
UE.
ZTEs UMTS RAN supports not only QPSK, but also high-order 16QAM. R99 only
supports QPSK.
The following figure shows the 16QAM constellation. Compared with QPSK, 16QAM
doubles the spectrum utilization, but increases the complexity of the receiver. 16QAM
requires not only amplitude estimation, but also more accurate phase estimation. During
amplitude estimation, the received power difference between the CPICH and
HS-PDSCH should be estimated.
For 16QAM, the bit number of the physical channel in each code channel is 1,920 within
the 2ms TTI, that is, 960 kbps. If 15 code channels transmit data concurrently and the
modulation mode is16QAM, the peak rate of the physical layer is 14.4 Mbps and the
peak rate of the MAC-hs layer is 13.976 Mbps.
In the mobile radio transmission environment, the quality of the signals received by the
UE depends on the distance between Node B and the UE, as well as channel fading
(including logarithmic normal slow fading and Rayleigh fast fading).The link adaptation
technology is to adjust the transmit power, symbol rate, modulation order, coding rate,
coding scheme, or combination of them adaptively according to the change of the fading
channel, thus attaining real-time balance of the link. The link adaptation technology is
intended to increase system capacity and improve communication quality. Fast power
control adopted by the traditional WCDMA is a link adaptation technology.
AMC works on the following principle: According to the radio channel quality status (CQI
report) reported by the current UE and the utilization of network resources, Node B
selects the optimal downlink modulation and coding mode at the network side, so as to
determine the rate of data transmitting, raising the data throughput of the UE, and
reducing transmission delay. Data rate is adjusted by changing the modulation strategy,
setting effective coding rate and appropriate number of HS-PDSCH codes. When the UE
is at a favorable communication point (for example, the UE is close to Node B), a
high-order modulation and high-rate channel coding mode (for example, 16QAM and 3/4
coding rate) can be selected to transmit subscriber data, thus attaining high transmission
rate. When the UE is at an unfavorable communication point (for example, far from Node
B), a low-order modulation and low-rate channel coding mode (for example, QPSK and
1/4 coding rate) can be selected to ensure communication quality.
As shown in Figure 3-14, there are two types of link adaptation technologies, including
inner loop link adaptation and outer loop link adaptation.
Node B
BLER Target MPO
HS- DSCH
ACK/NACK/DTX CQI
HS- DPCCH
Inner loop link adaptation should be based on the CQI. The core principle is that Node B
selects the modulation and coding mode and size of the transmission block according to
the CQI reported by the UE. When the UE is at a favorable communication point (for
example, the UE is close to Node B or a direct ray path is available), a high-order
modulation and high-rate channel coding mode (for example, 16QAM and 3/4 coding
rate) can be selected to transmit subscriber data, thus attaining high transmission rate.
When the UE is at a far point of the cell, or in a high-fading area or shadow area, a
low-order modulation and low-rate channel coding mode (for example, QPSK and 1/4
coding rate) can be selected to ensure communication quality. Figure 3-15 shows the
AMC mechanism.
S
N
R
TTI
Outer loop link adaptation is based on the ACK/NACK/DTX sent back by the HS-DPCCH.
The CQI reports that there exists a delay. Therefore, the single inner loop link adaptation
mode cannot control the downlink BLER to the target value approximately under any
circumstance. In this case, outer loop link adaptation is required. ZTEs UMTS Node B
uses the outer loop link adaptation mode. For details, refer to the CQI adjustment of
HSDPA.
The following shows how inner loop link adaptation selects a transmission format
according to the CQI. Figure 3-16 shows the relation between the UE with the capability
level of 10 and throughput, modulation mode, and number of code channels.
Figure 3-16 Relation Between CQI and Throughput, Modulation Mode, and Number of
Code Channels
14000
12000
10000
10
UserThroughput kbps
QPSK 15
8000 8
4000
4
2 3
2000 1
16QAM
0
0 5 10 15 20 25 30
CQI
As shown in Figure 3-16, the valid CQI range is from 1 to 30. The difference of channel
quality (SNR) between CQIs is about 1 dB. The number of used code channels is
increased while the CQI is raised. When the CQI is not greater than 15, QPSK is used.
When the CQI is greater than 15, 16QAM is used. The throughput ranges from 68.5 kbps
to 12.8 Mbps. The throughput is 12.8 Mbps when the CQI is 30 and the corresponding
transmission block is 25,558 bits. The largest transmission block supported by the
protocol is 27,952 bits, that is, 13.976 Mbps.
AMC is the most important link adaptation technology of HSDPA. When the channel
conditions are favorable, the 16QAM mode with high spectrum utilization is used, thus
raising the throughput of the UE and cell. AMC is related to resource allocation. When
selecting a transmission format for the subscriber, AMC should consider the channel
conditions, as well as the available radio resources and data amount in the subscriber
data buffer.
HARQ is among the key technologies of the HSPDA system. Compared with AMC,
HARQ is a hidden link adaptation technology. AMC sets the modulation and coding
format through an explicit C/I or similar measurement. HARQ uses the link layer
acknowledgement (ACK/NACK) for the retransmission judgment.
The HARQ technology is a hybrid of Automatic Repeat Request (ARQ) and Forward
Error Correction (FEC). In conjunction with AMC, HARQ is used to adapt to the channel
quality accurately and quickly. HARQ provides a low error rate. When a data packet is
retransmitted, the Redundancy Variable (RV) parameter and transmission power can be
different from those during initial transmission. The RV parameter determines the
combination strategy when the UE receives the retransmitted data. The first strategy is
called Chase Combine (CC) or Soft Combining: The retransmitted data is the same as
the initially transmitted data. The second strategy is called Incremental Redundancy (IR):
The relative number of system bits and the relative number of check bits are varying
every time. The IR strategy requires the UE to have more memory. Through the
retransmission combining technology, the HARQ technology utilizes every
retransmission, thus raising the success rate of data retransmission. By default, the
number of retransmission is configured to 3.
HS-PDSCH HARQ1 HARQ2 HARQ3 HARQ4 HARQ5 HARQ6 HARQ1 HARQ2 HARQ3
The figure shows the schematic diagram on multiple HARQ processes. It is assumed
that there are six HARQs and the feedback delay of the HARQs is less than six TTIs. In
the initial six TTIs, different HARQs are used respectively to transfer new data. When the
seventh TTI is used, HARQ 1 can be used continuously because the feedback
In the HSDPA system, a modulation and coding scheme (MCS) is used to transfer the
downlink data. The MCS must be adjusted to the ever-changing channel conditions, thus
maximizing the channel capacity and throughput. In the current system, the UE
measures and sends back the CQI. Node B determines the MCS that is used to transmit
the subsequent downlink data of the UE according to the CQI and other resource status.
When the UE generates the CQI, the target BLER is 10%. Due to the implementation
difference among vendors and measurement error, the reported CQI is not accurate.
Therefore, the following results are obtained:
The mechanism cannot acquire the optimal MCS timely and effectively.
If the CQI of the UE is overestimated, the transmission block is extremely large and the
downlink BER exceeds 10%. If the CQI of the UE is underestimated, the transmission
block is extremely small and system throughput is reduced.
To solve the problem, ZTEs UMTS Node B implements outer loop power control, tracks
the changes of the channel conditions effectively, and controls the BLER of the newly
transmitted MAC-hs TB to the target value of 10% approximately. Node B adjusts the
target CQI according to the CQI and ACK fed back by the UE. The intent is to reduce the
measurement error of the CQI, relieve the impact of the implementation difference
among the UE vendors, ensure the QoS of the UE, and raise system throughput.
For the CQI adjustment algorithm principle, refer to ZTE UMTS NodeB HSDPA Packet
Scheduling Feature Guide.
4.1 HSDPA
4.1.2.1 UUtranCellFDD.hspaSptMeth
OMC path
Parameter configuration
4.1.2.2 UExternalUtranCellFDD.hspaSptMeth
OMC path
Parameter configuration
4.1.2.3 hsNormBitRate
OMC path
Parameter configuration
4.1.2.4 hsdschTrafLimit
OMC path
Parameter configuration
It shows the maximum concurrent HSDPA users in a cell. The default value is 64.
4.1.2.5 ackNackEncInd
OMC path
Parameter configuration
4.1.2.6 RNCFEATSWITCHBit1
OMC path
Parameter configuration
4.1.2.7 RNCFEATSWITCHBit4
OMC path
Parameter configuration
It is based on the capability of DRNC. The parameter is set to 1 if the DRNC needs
DSCR to do hard handover. Otherwise, it is set 0.
4.1.2.8 UUtranCellFDD.hsdStat
OMC path
Parameter configuration
The parameter indicates whether the HSDPA function is active or not. The default
value is active.
4.1.2.9 UExternalUtranCellFDD.hsdStat
OMC path
Parameter configuration
The parameter indicates whether the HSDPA function is active or not. The default
value is active.
4.2 F-DPCH
4.2.2.1 rncFdpchSupInd
OMC path
Parameter configuration
OMC path
Parameter configuration
OMC path
Parameter configuration
This parameter indicates whether the adjacent cell supports F-DPCH or not.
C310080056 Number of attempted RRC connection ,UE Support HSDPA & EDCH
Class
C310170623 Number of failed HSDPA RAB assignment setup in cell for PS domain,UE send
rb setup failed
C310170641 Number of failed HSDPA RAB assignment setup in cell for PS domain,Access
Number of failed HSDPA RAB assignment setup in cell for PS domain,RL Setup
C310170644
or Reconfig Fail
Number of failed HSDPA RAB assignment setup in cell for PS domain,RL Setup
C310170645
or Reconfig Timeout
C310220659 Number of failed HSDPA RAB assignment setup in cell for PS domain,UCPMC
Exception
Number of failed HSDPA RAB assignment setup in cell for CS domain,UE send
C310175763
rb setup failed
Number of failed HSDPA RAB assignment setup in cell for CS domain,RL Setup
C310175784
or Reconfig Fail
C310175785 Number of failed HSDPA RAB assignment setup in cell for CS domain,RL Setup
or Reconfig Timeout
C310225803 Number of failed HSDPA RAB assignment setup in cell for CS domain,RPM
Exception
C310171138 Number of failed HSDPA MAC-d setup ,compressed mode not supported
C310171140 Number of failed HSDPA MAC-d setup ,requested configulation not supported
C310171142 Number of failed HSDPA MAC-d setup ,power balancing status not compatible
Number of failed HSDPA MAC-d setup ,message not compatible with received
C310171145
state
10,conversation
18,interactive
8,conversation
16,interactive
Number of RNC initiate RAB release by release request for CS-HSDPA by uesr
C310275889
inactive
Number of RNC initiate RAB release by release request for CS-HSDPA by lost
C310275892
UE connection
Number of RNC initiate RAB release by release request for CS-HSDPA by radio
C310275894
interface fail
Number of RNC initiate RAB release by release request for CS-HSDPA by OMC
C310275902
intervention
Number of RNC initiate RAB release by release request for CS-HSDPA by RAB
C310275904
pre-empty
Number of RNC initiate RAB release by release request for CS-HSDPA by IUUP
C310275905
fail
Number of RNC initiate RAB release by release request for CS-HSDPA by radio
C310275900
link fail
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281823
uesr inactive
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281824
repeat integrity check
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281825
UE initiate release
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281826
lost UE connection
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281827
relocation overall timer exceed
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281831
OMC intervention
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281832
overload control
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281833
RAB pre-empty
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281834
IUUP fail
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281835
UTRAN generating
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281836
unspecific fail
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281828
radio interface fail
Number of RNC initiate RAB release by RAB release request for PS-HSDPA by
C310281829
DL RLC error on TRB
Number of RNC initiate RAB release by release request for PS-HSDPA by uesr
C310281889
inactive
Number of RNC initiate RAB release by release request for PS-HSDPA by lost
C310281892
UE connection
Number of RNC initiate RAB release by release request for PS-HSDPA by radio
C310281894
interface fail
Number of RNC initiate RAB release by release request for PS-HSDPA by OMC
C310281902
intervention
Number of RNC initiate RAB release by release request for PS-HSDPA by RAB
C310281904
pre-empty
Number of RNC initiate RAB release by release request for PS-HSDPA by IUUP
C310281905
fail
Number of RNC initiate RAB release by release request for PS-HSDPA by radio
C310281900
link fail
Number of RAB release for HSDPA in cell,Ue not involved relocation UMI
C310286367
expiry.
C310286373 Number of RAB release for HSDPA in cell,Security mode configuration expiry.
C310286374 Number of RAB release for HSDPA in cell, signal reconfiguration fail
C310286375 Number of RAB release for HSDPA in cell,cell update not process
C310286376 Number of RAB release for HSDPA in cell,Cell update process error
6,inactive
16,conversation
24,inactive
C310040151 Cur Holding time of NONDC-HSDPA traffic in best cell (from cell point of view)
C310040152 Holding time of NONDC-HSDPA traffic in best cell (from cell point of view)
C310040153 Cur Holding time of DC-HSDPA traffic in best cell (from cell point of view)
C310040154 Holding time of DC-HSDPA traffic in best cell (from cell point of view)
C310010165 Conversational class UL R99 Traffic generated due to HSDPA in best cell
C310010166 Streaming class UL R99 Traffic generated due to HSDPA in best cell
C310010167 Interactive class UL R99 Traffic generated due to HSDPA in best cell
C310010168 Background class UL R99 Traffic generated due to HSDPA in best cell
C310010184 Conversational class UL R99 Traffic generated due to HSDPA in non-best cell
C310010185 Streaming class UL R99 Traffic generated due to HSDPA in non-best cell
C310010186 Interactive class UL R99 Traffic generated due to HSDPA in non-best cell
C310010187 Background class UL R99 Traffic generated due to HSDPA in non-best cell
C310010306 Conversational class UL Iub R99 volume generated due to HSDPA in cell
C310010307 Streaming class UL Iub R99 volume generated due to HSDPA in cell
C310010308 Interactive class UL Iub R99 volume generated due to HSDPA in cell
C310010309 Background class UL Iub R99 volume generated due to HSDPA in cell
C310030438 Number of including only HSDPA + HSUPA users in the best cell
C310030448 Max Number of including only HSDPA users in the best cell
C310030450 Max Number of including only HSDPA + HSUPA users in the best cell
C310030460 Average Number of including only HSDPA users in the best cell
C310030462 Average Number of including only HSDPA + HSUPA users in the best cell
C310063385 Number of including only HSDPA + HSUPA users in the DRNC cell
C310063394 Max Number of including only HSDPA users in the DRNC cell
C310063396 Max Number of including only HSDPA + HSUPA users in the DRNC cell
C310063405 Average Number of including only HSDPA users in the DRNC cell
C310063407 Average Number of including only HSDPA + HSUPA users in the DRNC cell
C310525648 Number of cell downlink load state change from normal to HSDPA overload
Number of cell downlink load state change from R99 common overload to
C310525649
HSDPA overload
Number of cell downlink load state change from R99 serious overload to
C310525650
HSDPA overload
Number of cell downlink load state change from HSDPA overload to R99
C310525651
common overload
Number of cell downlink load state change from HSDPA overload to R99
C310525652
serious overload
C310525653 Number of cell downlink load state change from HSDPA overload to normal
Number of outgoing inter-RNC intra frequency hard handover via Iur attempt for
C310332574
HS-DSCH
Number of outgoing inter-RNC inter frequency hard handover via Iur attempt for
C310332581
HS-DSCH
Number of outgoing inter-RNC intra frequency hard handover via Iur failed for
C310332588
HS-DSCH
Number of outgoing inter-RNC inter frequency hard handover via Iur failed for
C310332595
HS-DSCH
C310363235 Number of intra frequency HS-DSCH serving cell change failed,Protocol Error
C310363239 Number of intra frequency HS-DSCH serving cell change failed,No Reply
C310363240 Number of intra frequency HS-DSCH serving cell change failed,Other Causes
C310363246 Number of inter frequency HS-DSCH serving cell change failed,Protocol Error
C310363250 Number of inter frequency HS-DSCH serving cell change failed,No Reply
C310363251 Number of inter frequency HS-DSCH serving cell change failed,Other Causes
C310363254 Number of iur HS-DSCH serving cell change failed,Physical Channel failed
C310363256 Number of iur HS-DSCH serving cell change failed,Compress Mode Error
C310363258 Number of iur HS-DSCH serving cell change failed,Cell Update Occurred
C310393941 Number of intra frequency HS-DSCH to DCH failure due to moving,No Reply
C310393952 Number of inter frequency HS-DSCH to DCH failure due to moving,No Reply
C310393963 Number of intra frequency DCH to HS-DSCH failure due to moving,No Reply
C310393974 Number of inter frequency DCH to HS-DSCH failure due to moving,No Reply
C310545123 Mean number of users with data per TTI in MAC-hs buffer
C311785738 Number of DPCH /F-DPCH Code Reassign Failure due to Code Re-assignment
6 Glossary
16QAM 16 Quadrature Amplitude Modulation
ACK ACKnowledgement
TB Transmission Block
UE User Equipment