Академический Документы
Профессиональный Документы
Культура Документы
HSUPA
Parameter Description
Issue 02
Date 2009-06-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided “AS IS” without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
5 Parameters.............................................................................................................................. 5-1
1.1 Scope
HSUPA is an important feature of 3GPP Release 6. As an uplink high speed data transmission
solution, HSUPA provides a theoretical maximum rate of 5.74 Mbit/s on the Uu interface.
Document Issues
The document issues are as follows:
l 02 (2009-06-30)
l 01 (2009-03-30)
l Draft (2009-03-10)
l Draft (2009-01-15)
02 (2009-06-30)
This is the document for the second commercial release of RAN11.0.
Compared with issue 01 (2009-03-30), issue 02 (2009-06-30) incorporates the following
changes:
01 (2009-03-30)
This is the document for the first commercial release of RAN11.0.
Compared with draft (2009-03-10), issue 01 (2009-03-30) optimizes the description.
Draft (2009-03-10)
This is the second draft of the document for RAN11.0.
Compared with draft (2009-01-15), draft (2009-03-10) optimizes the description.
Draft (2009-01-15)
This is the initial draft of the document for RAN11.0.
Compared with issue 03 (2008-11-30) of RAN10.0, draft (2009-01-15) incorporates the
following changes:
2 Overview of HSUPA
Since the introduction of the HSDPA technology, the downlink transmission rate has been
greatly increased. To meet the rapidly growing demands for data services, 3GPP Release 6
introduced HSUPA. By applying fast scheduling, fast hybrid automatic repeat request
(HARQ), shorter transmission time interval (TTI), and macro diversity combining (MDC),
HSUPA improves the uplink capacity, increases the user data rate greatly, and reduces the
transmission delay on the WCDMA network.
Fast Scheduling In HSUPA, fast scheduling is used to allocate system resources in the
NodeB through signaling at the physical layer. By exploiting the
burstiness in fast transmission, the scheduler performs rapid resource
allocation between UEs to adapt to cell interference variations. This
improves user experience and increases the system capacity.
Fast HARQ Similar to HSDPA, HSUPA also introduces fast HARQ, which allows
the NodeB to rapidly request retransmission of erroneously received
data. HARQ reduces the number of retransmissions at the RLC layer
and shortens the transmission delay. The NodeB performs soft
combining of data erroneously received and data retransmitted from the
UE before decoding. The combining makes full use of the information
transmitted each time and thus increases the success rate of decoding.
Shorter TTI HSUPA allows a 2 ms TTI, which further reduces the transmission
delay and scheduling delay.
MDC HSUPA supports soft handover. The cells in the active set can receive
data from UEs. MDC increases the probability of proper data reception,
improves the quality of data transmission, and greatly enhances the
service stability of users at the cell border.
The TTI of the enhanced dedicated channel (E-DCH) can be 10 ms or 2 ms. The E-DCH is
mapped onto the E-DPDCH or E-DPCCH. When the TTI is 10 ms, the E-DCH provides
better uplink coverage performance; when the TTI is 2 ms, the E-DCH provides higher
transmission rates.
The E-DPDCH carries data in the uplink. The spreading factor of the E-DPDCH varies from
SF256 to SF2 depending on the data transmission rate. A maximum of four E-DPDCHs can
be used for parallel transmission. The SF of two E-DPDCHs is SF2, and the SF of the other
two E-DPDCHs is SF4.
The E-DPCCH carries control information related to data transmission in the uplink. The
control information consists of the E-DCH transport format combination indicator (E-TFCI),
retransmission sequence number (RSN), and happy bit. The SF of the E-DPCCH is fixed to
256.
To implement the HARQ function, the E-HICH is introduced in the downlink. The E-HICH
carries retransmission requests from the NodeB.
The downlink E-AGCH and E-RGCH carry the HSUPA scheduling control information. The
E-AGCH is a shared channel, which carries the maximum permissible E-DPDCH to DPCCH
power ratio, that is, absolute grants.
The E-RGCH is a dedicated channel, which is used to indicate relative grants and increase or
decrease the maximum permissible E-DPDCH to DPCCH power ratio.
HSUPA QoS management strategy is adopted, which requires the support of some HSUPA
functions. This document describes the HSUPA QoS management strategy.
first three functions control the RL of each UE. The last function controls all the UEs in the
cell. The four functions work simultaneously.
l Power control
If a service can be carried on the HSUPA channel, the UE transmits control messages and
traffic data to the network on the uplink channels (E-DPCCH and E-DPDCH), and the
network transmits signaling to the UE on the downlink channels (E-RGCH, E-AGCH, and
E-HICH). Power control assigns appropriate transmit power to each downlink channel to
ensure that messages can be correctly received by UEs and to avoid wasting resources
because of very high transmit power. Power control is also used to control the transmit
power of the uplink channels to ensure the transmission quality of uplink data on the Uu
interface. For details on power control, see the Power Control Parameter Description.
l Channel switching
Channel switching monitors the data transmission requests of UEs in real time, estimates
the change in the demands for system resources, and then adjusts the channel bandwidth or
performs state transition based on the estimation. This function ensures the QoS and saves
system resources. For details, see section 3.2 "Channel Switching."
l Mobility management
Mobility management processes transactions due to UE movement between cells. For
example, when a UE moves from one cell to another cell, the serving cell must be switched
to ensure service continuity; when a UE moves between a cell capable of HSUPA and a
cell incapable of HSUPA, the HSUPA channel must be configured or removed on the basis
of the cell capability to ensure service continuity and service quality. For details on
mobility management, see the Handover Parameter Description.
Figure 2-3 Protocol layers associated with HSUPA user plane functions in the UTRAN
Function Description
On the UE side, after the service data at the application layer is passed to the RLC layer, the
service data is segmented or concatenated to an RLC PDU and then passed to the physical
layer for transmission.
l ETFC selection
In each TTI, whether the UE can transmit data and how much data can be transmitted
depend on E-DCH transfer format combination (ETFC) selection based on the following
factors:
− The total transmit power of the UE.
− The serving grant (SG) from the NodeB. The SG defines the maximum permissible
power used to transmit data on the E-DPDCH, which carries the MAC-e PDU. The
larger the SG is, the bigger the MAC-e TB size to be supported in one transmission
time interval is.
− The traffic volume in the RLC buffer of the UE.
ETFC selection is defined in 3GPP TS 25.321 and implemented on the UE side.
l HARQ
After ETFC selection determines the amount of data to be transmitted in the current TTI,
the RLC PDU is encapsulated into the MAC-es PDU and then into the MAC-e PDU, and
then the MAC-e PDU is passed to the HARQ entity. The HARQ entity transmits the
MAC-e PDU on the E-DPDCH. If the MAC-e PDU is erroneously received by the cell, the
HARQ entity retransmits it until it is correctly received or the retransmission times reach
the predefined maximum times. On the NodeB side, if the decoding of an MAC-e PDU
fails, the HARQ reception process of the NodeB buffers the data received each time,
performs maximum ratio combining (MRC) of received data, and then performs decoding.
This increases the probability of correctly receiving packets. The network can control the
retransmission times dynamically to ensure the correct reception of MAC-e PDUs. For
details, see section 4.4 "HSUPA Adaptive Retransmission."
l Flow control
After the data is correctly received by the NodeB, it is passed to the RNC. There is an Iub
interface between the RNC and the NodeB, and the bandwidth on this interface may be
limited. Therefore, the NodeB needs to allocate Iub bandwidth among UEs properly
through the flow control function to avoid deterioration of transmission quality due to
congestion on the Iub interface. If a UE in soft handover establishes several RLs towards
the cells under different RNCs, the flow control function also needs to be implemented on
the Iur interface to avoid congestion on the Iur interface.
l MDC
If a UE is performing soft handover, the same MAC-es PDU may be passed to the RNC
from several NodeBs over several Iub interfaces or passed to the SRNC from the DRNC
over the Iur interface. In this case, the SRNC performs the MDC function to combine the
same data, thus increasing the probability of correct reception.
l Fast scheduling
Fast scheduling is very important on the NodeB side. The NodeB assigns the SG to each
HSUPA UE through fast scheduling to control the maximum transmission rate of each UE
on the Uu interface. Fast scheduling has a direct impact on the QoS of each UE. Thus,
when the NodeB assigns SGs, it must consider the available system resources and the QoS
requirement of each UE. That is, when ensuring the QoS of each UE, fast scheduling
maximizes the utilization of system resources. For details on fast scheduling, see section
4.1 "Fast Scheduling."
l CE management
CE resources are NodeB hardware resources used for demodulating HSUPA data. CE
resources usually become the bottlenecks for system resources. When the CE resources
are limited, it is important to logically use the limited resources to meet the QoS
requirement of each UE. CE management considers this factor, outputs the information
about CE resource allocation for each UE, and then passes it to the scheduling module as a
reference for Uu resource allocation. For details on CE management, see section 4.2
"Dynamic CE Management."
The Iub flow control and CE management functions allocate appropriate resources to each UE
based on the amount of available resources and the QoS requirement of each UE. Then, based
on the resource allocation, the two functions calculate the maximum rate of each UE
supported by the Iub resources and CE resources.
The scheduling module provides an SG for the UE based on the received maximum rate. The
SG ensures that the maximum rate of the HSUPA UE on the Uu interface does not exceed the
received maximum rate, thus avoiding Iub resource or CE resource congestion.
During the service setup, the RNC selects appropriate channels based on the UE capability,
cell capability, and service parameters to optimize the utilization of cell resources and ensure
the QoS.
Table 3-2 lists the mapping between new state transition and new channel switching.
Table 3-2 Mapping between new state transition and new channel switching
The switching between E-DCH and FACH and the switching between E-DCH and DCH can
be triggered in the following cases:
l The UE activity changes. The UE activity is measured by the amount of data to be
transmitted by the UE. When the traffic volume is high, the UE is in the high activity
state, and thus high-rate transport channels are required to provide high service quality.
When the traffic volume is low, the UE is in the low activity state, and thus low-rate
channels or shared channels can be used to reduce the resource usage.
l The system capability changes during the movement of the UE. When the UE moves
from an HSPA cell to a non-HSPA cell, the non-HSPA channel must be configured to
ensure service continuity. When the UE moves from a non-HSPA cell to an HSPA cell,
the HSPA channel must be configured if the UE supports HSPA to provide high service
quality.
l The system load changes. When the system enters the overload state, the UE in the
CELL_DCH state may be switched to the common channel to reduce resource
consumption and ensure system stability. This is applicable to the UE on the HSPA
channel. When the UE attempts an access, the access may be rejected because of HSPA
overload. Therefore, the UE accesses the network on the DCH. When the system load
becomes normal, the UE is switched back to the HSPA channel.
l The current cell supports HSUPA or the inter-frequency same-coverage neighboring cell
supports HSUPA.
The channel switching mechanisms are as follows:
Channel switching based on timer: After the DCH is set up, this mechanism periodically
attempts to perform channel switching from DCH to E-DCH.
Implementation Procedure
As defined in 3GPP TS 25.321 the Relative Grant (RG) information sent by the cells that
belong to the serving E-DCH RLS to the UE must be the same. If the RG information that the
UE receives from different cells is different, the following processing is performed:
l The rate is decreased if any cell sends a rate decrease command.
l The rate is increased only when no cell sends any rate decrease command and the serving
cell sends a rate increase command.
Thus, Huawei HSUPA fast scheduling algorithm is based on NodeBs. It schedules the cells on
the same frequency in the NodeB uniformly and sends the uniform rate adjustment command
to the UEs establishing several RLs in the cells to control the rates of UEs effectively.
The HSUPA scheduling module, which is the only functional module that can control the
uplink rates of HSUPA UEs on the Uu interface, needs to perform the following tasks:
l Provides a timely response based on the results of CE scheduling, Iub flow control, and
MBR limitation and completes associated functions.
l Provides grants of rate increase or decrease for UEs rapidly based on the conditions of the
load and resources on the Uu interface to completely utilize the resources and ensure
system stability.
l Provides satisfactory QoS for more UEs and provides different UEs with different
priorities when providing grants for UEs.
The HSUPA scheduling consists of two submodules: coordination module and Uu resource
scheduling module.
The scheduling period is based on the TTI.
l If the TTI is equal to 10 ms, the scheduling period is 10 ms.
l If the TTI is equal to 2 ms, the scheduling period is 2 ms.
When the scheduling function is performed, the coordination module updates the status of
Uu resources and the status of the remaining available resources in the cell.
l Responding to the request of the dynamic CE management module
Based on the resource requirements of UEs and the resource adjustment between UEs, the
dynamic CE management module requests the fast scheduling module to decrease the
rates of some UEs. The fast scheduling module needs to respond to the request rapidly and
send the AG or RG 'Down' message to the associated UEs.
l Responding to the request of the Iub flow control module
Based on the conditions of Iub resources and UE priorities, the Iub flow control module
requests the fast scheduling module to decrease the transmission rates of some UEs. In this
case, the fast scheduling module needs to respond to the request rapidly and send the RG
'Down' message to the associated UEs.
l Responding to the MBR limitation result
The coordination module sends the RG 'Down' message to each UE of which the data rate
exceeds the MBR on the Uu interface to decrease the data rate.
The processing procedure is as follows:
Step 1 The coordination module initializes the estimated Uu interface load and the estimated
remaining load of all the cells that it controls.
Estimated Uu interface load = Uu interface load corresponding to the current measured RTWP
value
Estimated remaining load = MaxTargetUlLoadFactor – Uu interface load corresponding to
the current measured RTWP value
In this expression, MaxTargetUlLoadFactor is a parameter configured in the RNC. It
specifies the target level of uplink load control. The estimated remaining load indicates the load
resources on the Uu interface that can be allocated to UEs.
Step 2 According to the requests of external algorithms such as Iub flow control, dynamic CE
management, and MBR limitation, the coordination module sends the RG 'Down' message to
associated UEs to decrease the rate and updates the estimated Uu interface load and the
estimated remaining load of all the related cells.
l The UEs for scheduling may be in softer handover. An E-DCH RLS may contain several cells.
l "Related cells" refer to the cells that belong to the NodeB in the E-DCH RLS.
Step 3 The coordination module activates the Uu resource scheduling module and sends the estimated
Uu interface load and the estimated remaining load of all the related cells after update to the Uu
resource scheduling module.
----End
l Scheduling queuing
The HSUPA fast scheduling module schedules the cells on the same frequency in a NodeB
uniformly. Thus, all the UEs that establish one or more RLs with the cells participate in
queuing.
The purposes of UE queuing are as follows:
− To ensure the QoS of UEs: to try to ensure that the UEs can obtain the guaranteed bit
rate (GBR)
− To differentiate UEs: to ensure that the UEs with a great scheduling priority indicator
(SPI) weight obtain resources preferentially
− To ensure fairness: to ensure that the UEs with the same SPI weight have the same
opportunity to obtain resources
The factors that affect queuing are as follows:
− Happy Bit: reported by the UE.
− Effective rate: The actual rate obtained by the UE is monitored by the NodeB on a
real-time basis.
− GBR: The GBR is configured on the basis of user priorities. Generally, the GBR
increases with the user priority. The GBR can be set through the SET USERGBR and
ADD CELLEFACH commands on the RNC.
− SPI weight: The SPI weight (FACTOR) is configured on the basis of the SPI.
Generally, the FACTOR increases with the SPI. And FACTOR can be configured in
the RNC.
− Figure 4-3 shows the general principle for scheduling queuing.
− The priority of users with Happy Bit to be Unhappy is higher than the priority of users
with Happy Bit to be Happy.
− In the unhappy users, the priority of users with the effective rate higher than the GBR is
higher than the priority of users with the effective rate lower than the GBR.
− In the three types of users, the priority of users with a greater SPI weight is higher; the
priority of users with a smaller SPI weight is lower. This helps provide differentiated
services.
l Uu resource allocation
Based on the scheduling queuing result and the Uu interface load of each cell participating
in scheduling, the Uu resource allocation module allocates Uu resources to users and sends
the AG or RG to the users.
The procedure for allocating Uu resources is as follows:
Step 1 Based on the estimated remaining load passed by the coordination module to all the cells, the
Uu resource allocation module maximizes the estimated remaining load. According to the
scheduling principle, some resources of happy users can be released to unhappy users in the
case of insufficient load resources. If the rate of all happy users decreases, the remaining load
increases. The Uu resource allocation module calculates the maximum estimated remaining
load that all the related cells can obtain. Note that the Uu resource allocation module only
estimates the maximum remaining load, but does not send rate decrease grants to happy users.
Thus, the estimated Uu interface load does not need to be updated.
Step 2 The Uu resource allocation module polls all the users in the unhappy queue one by one in
descending order of priorities. If the estimated remaining load of all the related cells permits
rate increase, the Uu resource allocation module increases the rate of the user, sends the rate
increase grant, and updates the estimated Uu interface load and the estimated remaining load of
all the related cells. Otherwise, the rate is not adjusted.
Step 3 The Uu resource allocation module polls all the users in the unhappy queue one by one in
ascending order of priorities. If the user is not granted in this scheduling period and the
estimated Uu interface load of at least one cell in all the related cells is higher than the
MaxTargetUlLoadFactor, the Uu resource allocation module decreases the rate of the user,
sends the rate decrease grant, and updates the estimated Uu interface load. Otherwise, the rate is
not adjusted.
During the rate adjustment of unhappy users, the QoS of users with the GBR requirement can
be further ensured. When the parameter HSUPAOLSCHSWITCH is set to ON in the NodeB
and the system load exceeds the target load threshold without overload, the rate of the unhappy
users with the actual rate lower than the GBR is not decreased or even can be increased during
the rate adjustment.
----End
The main functions of the dynamic CE management module are shown in Figure 4-4. The
procedure of dynamic CE management is as follows:
Step 1 Calling back CE resources
Based on the actual data rate of users, the CE management module calls back the idle CE
resources to improve the utilization of resources and updates the information about available
system resources.
Steps 1 to 3 can be triggered periodically, and the periods can be different. Step 2 is triggered by
events. If several processing tasks are triggered at a time, the CE management module performs
the processing by following the procedure shown in Figure 4-4.
l When the Iub resources are in the congestion state, most resources are allocated to serving
users.
This resource allocation policy ensures the service quality of serving users preferentially, and
it is applicable only to BE services.
The HSUPA power control algorithm can adjust the signal-to-noise ratio of the E-DPDCH
that reaches the NodeB each time by comparing the actual retransmission times with the
target retransmission times to control the retransmission times of the MAC-e PDU within the
target value range. In this manner, the interference level of the UE to the system is adjusted,
and the requirement for UE transmit power is also adjusted.
Generally, to enable the user to obtain a higher rate, set the target retransmission times to a
smaller value at the price of increasing the load properly. This case is called "small target retx
times". The "small target retx times" configuration, however, may have a negative effect in
the following cases:
l The UE transmit power is limited. When the UE moves to the edge of the cell, the
transmit power is not enough. Therefore, the probability in which the MAC-e PDU is
correctly received is reduced, and therefore the UE throughput is reduced promptly.
l The cell load is limited. When the load of the cell serving the UE is high, the scheduling
algorithm may no longer provide additional rate grants for the UE. Therefore, the UE
throughput is also limited.
HSUPA adaptive retransmission increases the target retransmission times adaptively based on
the previous two cases to achieve the following purposes:
l Increasing retransmission times can obtain the gain of time diversity, reduce the
requirement for UE transmit power, enlarge the coverage range, and increase the UE
throughput.
l Reducing interference of the UE to the system enables the UE to obtain a higher rate grant
and increase the UE throughput, thus increasing the cell throughput and uplink capacity.
When the problems in the previous two cases are solved, HSUPA adaptive retransmission
restores the target retransmission times to a smaller value. Accordingly, the transmit power
resources of the UE and the load resources of the cell can be fully used to enable the UE rate to
approach or reach the throughput limit, thus improving user experience.
HSUPA adaptive retransmission is an optional function and is controlled by the license.
The HSUPA adaptive retransmission algorithm periodically determines whether the target
retransmission times of each user need to be adjusted. To avoid fluctuation of system load, a
maximum of two users are allowed for retransmission times adjustment in each period, that is,
one for retransmission times increase and the other for retransmission times decrease.
When determining whether to adjust the target retransmission times, the NodeB needs to
monitor the conditions of transmit power and resources such as the Uu load resources and CE
resources.
l Determining whether the transmit power of the HSUPA UE is limited
The UE reports the Scheduling Information (SI) to the NodeB. The SI contains the actual
transmit power of the UE. Based on the SI, the NodeB estimates whether the transmit
power of the UE meets the requirement of the current service rate and thus determines
whether the transmit power of the UE is limited.
l Determining whether the load on the Uu interface is limited
Based on the monitoring result of the Uu interface load, the NodeB determines that the
load on the Uu interface is limited when the load is high and that the load on the Uu
interface is restored when the load is low.
l Monitoring CE resources
The NodeB monitors the available CE resources. If the available CE resources are
sufficient, retransmission is allowed. Otherwise, retransmission is rejected.
The user with the transmit power of the UE limited is selected preferentially because only one
user is allowed for the adjustment in a period. If there is no such user, the user with the load on
the Uu interface limited is selected. The user with the highest priority is selected preferentially.
The retransmission times can be adjusted only when the available CE resources are sufficient
for the retransmissions.
5 Parameters
Parameter ID Description
MaxTargetUlLoadFactor Maximum target uplink load factor. It is the target load defined
by the RNC and obtained by the NodeB HSUPA power control
from the uplink load. This parameter is based on network
planning. The cell throughput varies with the value of this
parameter. The greater the value is, the more interferences
exist. For details about this parameter, refer to the 3GPP TS
25.433.
HSUPAOLSCHSWITC HSUPA overload scheduling switch
H
FACTOR This parameter specifies the factor associated with the
scheduling priority indicator. This factor is used to calculate
the step of rate upsizing.
SPI Scheduling Priority Indicator
The Default Value column is valid for only the optional parameters.
The "-" symbol indicates no default value.
6 Counters
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
8 Reference Documents