Академический Документы
Профессиональный Документы
Культура Документы
HSDPA Description
Issue 03
Date 2008-11-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 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, expressed or implied.
Contents
5 HSDPA Parameters....................................................................................................................5-1
6 HSDPA Reference Documents................................................................................................6-1
HSDPA Change History provides information on the changes between different document
versions.
03 (2008-11-30)
This is the document for the second commercial release of RAN10.0.
Compared with 01(2008-07-30) of RAN10.0, issue 03 (2008-11-30) of RAN10.0 incorporates
the changes described in the following table.
02 (2008-07-30)
This is the document for the first commercial release of RAN10.0.
Compared with 01(2008-05-30) of RAN10.0, issue 02 (2008-07-30) of RAN10.0 incorporates
the changes described in the following table.
01 (2008-05-30)
This is the document for the first commercial release of RAN10.0.
Feature change CQI filtering of CQI Adjustment The parameters that are changed to
Algorithm is removed. be non-configurable are listed as
follows:
CQI Filter Alpha
None The parameters renamed are
described as follows:
Discard Rate Threshold is
modified to Discard Rate.
Time Delay Threshold is
modified to Time Delay.
The name of CQI Adjustment
Algorithm Switch is modified to
CQI Adjust Algorithm Switch.
Editorial change General documentation change: None.
The HSDPA Parameters is
removed because of the
creation of RAN10.0 parameter
reference.
Draft (2008-03-20)
This is the draft of the document for first commercial release of RAN10.0.
Compared with issue 03 (2008-01-20) of RAN6.1, this issue incorporates the changes
described in the following table.
2 HSDPA Introduction
HSDPA (High Speed Downlink Packet Access) is an important feature of 3GPP R5. As a
downlink (DL) high-speed data transmission solution, it has a theoretical maximum rate of
14.4 Mbit/s on the Uu interface.
The main features of HSDPA are as follows:
Each subframe transmitted over the Uu interface has a size of 2 ms.
The Hybrid Automatic Repeat Request (HARQ) and Adaptive Modulation and Coding
(AMC) technologies are applied at the physical layer.
The high-order 16QAM modulation mode is used to improve spectral efficiency.
Both code division and time division are used to schedule User Equipments (UEs).
HSDPA improves the performance of UMTS network in the following aspects:
Higher peak transmission rate in the downlink
The highest rate reaches 14.4 Mbit/s.
Shorter service delay
HSDPA enhances the subscriber experience with high-speed services, such as receiving
e-mails and browsing web pages.
Higher utilization of DL codes and power
The HSDPA capabilities are as follows:
Peak rate per cell: 14.4 Mbit/s
Peak rate per user: 14.4 Mbit/s
Maximum number of users per cell: 64
Multiple RABs: 3 PS RABs
SRB over HSDPA
HSDPA over Iur
VoIP over HSPA
IMS signaling over HSPA
HS-DPCCH Preamble
F-DPCH
Impact
Impact on System Performance
HSDPA increases the system capacity and shortens the data transmission delay.
Impact on Other Features
The impact of HSDPA on other RAN features is as follows:
− HSDPA requires the support of power control, load control, admission control, and
mobility management.
− HSDPA and other features have influences on each other.
3 HSDPA Principles
Figure 3-2 shows the HSDPA protocol architecture with the MAC-c/sh.
The differences between the HSDPA protocol architecture and the R99 protocol architecture
are as follows:
RLC and MAC-d are unchanged.
The HS-DSCH FP is added to handles the data transport from SRNC to CRNC if the Iur
interface is involved and the data transport between CRNC and NodeB. In R99, it is the
DCH FP that handles such data transport.
A new entity called MAC-hs is added at the MAC layer of both UE and NodeB. The
MAC-hs handles new functions, such as HARQ and HS-DSCH scheduling.
There are two types of MAC protocol configurations on the UTRAN side:
− Configuration with the MAC-c/sh: The MAC-c/sh implements flow control between
MAC-d, MAC-c/sh, and MAC-hs.
− Configuration without MAC-c/sh: The MAC-hs and HS-DSCH FP implement flow
control between MAC-hs and MAC-d over Iub/Iur.
When Fractional-Dedicated Physical Control Channel (F-DPCH) is configured, all RABs/SRBs are
carried on HS-DSCH. The associated DPCH is replaced with the F-DPCH and there is no DPDCH
The basic uplink channel configuration of HSDPA is the same as that of R99, except that one
HS-DPCCH is added for one UE.
Seen from the UE side, the processing at the HSDPA-related physical layer is as follows:
In each TTI, the UE detects the HS-SCCH channel to check whether the UE is scheduled
or not.
− If the UE is scheduled, it demodulates and decodes the data from HS-PDSCHs
specified by the related HS-SCCH. An ACK or NACK will be generated on the basis
of the decoding result of HS-PDSCHs and will be sent to the serving cell through
HS-DPCCH.
− If the UE is not scheduled, it does not demodulate or decode the data from
HS-PDSCHs.
The channel quality indicator (CQI) is periodically reported through the HS-DPCCH
regardless of whether the UE is scheduled. CQI is a key input for Transport Format and
Resource Combination (TFRC) selection and scheduling based on channel quality at the
MAC-hs layer.
Seen from the UTRAN side, the processing at the HSDPA-related physical layer is as follows:
Multiple UEs can be multiplexed in the code domain within an HS-DSCH TTI. This
process is called code division in one TTI.
The physical resources of HS-DSCH are time shared by all HS-DSCH UEs in the cell.
HS-SCCH
The High Speed Shared Control Channel (HS-SCCH) is a downlink physical channel used to
carry downlink signaling related to High Speed Physical Downlink Shared Channel
(HS-PDSCH). The HS-SCCH has a fixed rate of 60 kbit/s (SF = 128). The following figure
shows the subframe structure of the HS-SCCH.
HS-PDSCH
The High Speed Physical Downlink Shared Channel (HS-PDSCH) is used to carry the
HS-DSCH data. The HS-PDSCH SF can be 16 only. The modulation mode of HS-PDSCH is
QPSK or 16QAM.
Each cell provides a maximum of 15 HS-PDSCH codes. The UE of category 10 supports a
maximum of 15 HS-PDSCH codes and the 16QAM modulation mode, with the peak rate of
14.4 Mbit/s on the Uu interface.
Figure 3-5 shows the subframe structure of the HS-PDSCH.
For QPSK, M = 2.
For 16QAM, M = 4.
HS-DPCCH
The High Speed Dedicated Physical Control Channel (HS-DPCCH) carries uplink feedback
signaling related to HS-PDSCH. It has a fixed rate of 15 kbit/s (SF = 256, that is, 10 bits per
timeslot).
The feedback signaling consists of Hybrid Automatic Repeat
Request-Acknowledgement/Negative Acknowledgement (HARQ-ACK/NACK) and Channel
Quality Indicator (CQI). The HARQ-ACK/NACK is carried in the first timeslot of the
HS-DPCCH subframe, and the CQI is carried in the second and the third timeslots of the
subframe.
Figure 3-6 shows the subframe structure of the HS-DPCCH.
Figure 3-8 Timing of the uplink DPCCH, HS-DPCCH, and HS-PDSCH at the UE
The flow control entity controls the HSDPA data flow between RNC and NodeB.
Purpose: to reduce the transmission time of HSDPA data on the UTRAN side and to
reduce the data discarded and retransmitted when the Iub interface or Uu interface is
congested.
The transmission capabilities of the Uu interface and Iub interface are taken into account
in a dynamic manner in the flow control. For details of flow control, refer to 4.2 HSDPA
Flow Control in NodeB.
The scheduling entity handles the priority of the queues and schedules the priority queues or
NACK HARQ processes of the HS-DSCH UEs in a cell to be transmitted on the HS-DSCH
related physical channels in each TTI.
The reordering entity reorders the received MAC-hs PDUs according to their
transmission sequence number (TSN) and the TSN may be out of sequence because of
parallel HARQ processes. For each queue ID, one reordering entity is configured on the
UE.
The disassembly entity extracts the MAC-d PDUs from the MAC-hs PDUs and delivers
them to the higher layer.
The round trip time at the physical layer is approximately 12 ms, much shorter than that
at the RLC layer. The round trip time at the RLC layer may reach hundreds of
milliseconds.
Soft combining improves the efficiency of the physical layer resource.
The round trip time at the physical layer is 12 ms. Therefore, it is necessary for one UE to
have multiple parallel instances (HARQ processes) of the stop and wait HARQ protocol to
increase the Uu interface throughput.
One issue in the receiver caused by multiple HARQ processes is that, in a specific time
window, the TBs may arrive out of sequence. Therefore, it is necessary to have reordering
functionality on the receiver side.
4 HSDPA Algorithms
Step 1 When a cell is set up, the initial allocation of power and codes for HSDPA are allocated. After
that, the power and code resource available for HS-DSCHs in a HSDPA cell are dynamically
adjusted by the algorithms of 4.5 HSDPA Power Resource Management and 4.6 HSDPA
Code Resource Management. R99 and HSDPA can dynamically share the resource of the cell
in this way.
Step 2 When one user initiates a service at the beginning of RAB setup procedure, the channel
mapping algorithm determines whether the RAB should be mapped onto the HS-DSCH or
DCH depending on the service Qos attributes. QoS of the service is mapped to the parameters
of radio bearer, such as SPI, discard timer, and GBR for HS-DSCH bearer. For details of
radio bearers, refer to Mapping of Signaling and Traffic onto Transport Channels and
Mapping of Combined Services onto Transport Channels (in Radio Bearers).
RAB is set up after admission control (in Load control). Admission control determines
whether the system resources are enough to accept a new user's access request. Data transport
begins after the RAB is set up. Data transport of HS-DSCH bearer is controlled by the
functions such as 0
Step 3 HSDPA Flow Control in NodeB, 4.3 HSDPA MAC-hs Scheduling, and 4.4 HSDPA TFRC
Selection.
Step 4 During the HS-DSCH transport, the movement of the user will trigger the mobility
management. For example, the best cell change occurring in the active set may trigger
HS-DSCH serving cell change or channel switching between HS-DSCH and DCH. For details,
− For details of setting EPF Schedule Algorithm Switch, refer to 4.3 HSDPA MAC-hs
Scheduling.
For details of setting Flow Control Algorithm Switch, refer to 0
− HSDPA Flow Control in NodeB.
The user priority–oriented parameters are also configured on an SPI basis on the NodeB
side. For example, the weight factor corresponding to the user priority is named Weight
of SPI on the NodeB side. For details, refer to Table 4-2.
Guaranteed Bit Rate (GBR): It is configured on an MAC-hs queue basis. For the
streaming service, the GBR specifies the rate that can meet the requirement of the user
for viewing and the GBR of a queue is determined by the NAS. For the BE service, the
GBR specifies the required minimum rate for the service of the users in the RAN. The
GBR of a BE service user is set through the SET USERGBR command on the RNC side.
The setting is based on the user priority, namely, gold user, silver user, or copper user.
Services with different QoS requirements require different QoS guarantee policies. For
example, the VoIP service has a high requirement for delay. To limit the delay caused by
flow control or scheduling within a proper range, the algorithm grants the VoIP queue a
priority to occupy resources first. The streaming service has a high requirement for GBR.
Therefore, the scheduling and flow control algorithms guarantee that the average rate of
the service is not lower than the GBR during Iub traffic distribution and Uu resources
allocation. The BE service has a high requirement for reliability, which can be achieved
through more retransmissions on the Uu interface.
Scheduling Priority Indicator (SPI) is the relative priority of the HS-DSCH FP data
frame and the SDUs included. The SPI is set according to the Traffic Class (TC),
Traffic Handling Priority (THP) of the interactive service, and User Priority. The SPI
is set on the RNC LMT and sent to the NodeB through NBAP signaling.
User Priority is determined by the Allocation Retention Priority (ARP), as listed in the
following table.
The traffic class, user priority, and THP determine only one SPI. The default mapping is
described in the following table, where user priority 1 corresponds to Gold, 2 corresponds to
Silver, and 3 corresponds to Copper.
Table 4-2 Default mapping of traffic class, user priority, and THP to SPI
Traffic Class User Priority THP SPI
NodeB and RNC can provide flow control functions. In NodeB, there are two types of flow
control policies.
Flow control free
Dynamic flow control
Dynamic flow control has three methods.
No shaping
Shaping without adaptive Iub bandwidth.
Shaping with adaptive Iub bandwidth
Figure 4-4 Signaling procedure for HSDPA capacity request and allocation
The NodeB sends an HS-DSCH Capacity Allocation message to the CRNC as the
response to the HS-DSCH capacity request or to the requirement of the Iub HSDPA flow
control algorithm.
The following figure shows the structure of the capacity request frame. The frame includes
the queue priority and the data buffer size at the RNC RLC layer.
The following figure shows the structure of the capacity allocation frame.
In the HS-DSCH Interval, the user can send a maximum number of HS-DSCH Credits
MAC-d PDUs. The PDU size is limited by Maximum MAC-d PDU Length. The user can
repeat the HS-DSCH Interval in the period defined by HS-DSCH repetition period.
CmCH-PI: Scheduling Priority Indicator (SPI) of the queue.
HS-DSCH Interval: time interval during which the HS-DSCH Credits granted in the
HS-DSCH CAPACITY ALLOCATION control frame can be used.
HS-DSCH Credits: number of MAC-d PDUs that a CRNC can transmit during an
HS-DSCH Interval granted in the HS-DSCH CAPACITY ALLOCATION control frame.
Maximum MAC-d PDU Length: maximum PDU size among the MAC-d PDU sizes
configured in the NBAP messages.
HS-DSCH repetition period: number of subsequent intervals during which the HS-DSCH
Credits IE granted in the HS-DSCH CAPACITY ALLOCATION control frame can be
used and the value 0 means that there is no limit to the repetition period.
If the resource on the Iub interface is the bottleneck, the bandwidth allocation is based on
the rate on the Uu interface and the available Iub bandwidth.
− The algorithm considers the following factors of the MAC-hs queues: the bit rate
allocated by Adaptive Capacity Allocation Based on Uu Rate, NodeB buffer
occupancy, RNC buffer occupancy, and the bottleneck bandwidth available for
HSDPA on the Iub interface from Adaptive Adjustment of Available HSDPA
Bandwidth.
− First, Iub resource for GBR is allocated. That is, the algorithm first considers the
basic requirements for guaranteeing the user experience.
− Then, the algorithm considers the requirement for user differentiation. For all the
users in the cell, the scheduler intends to allocate the Iub resource in proportion to
their Weight of SPI, which is based on user priorities, eg. gold, silver and copper.
User priority differentiation is implemented when Iub is the bottleneck. The gold, silver, and
copper users obtain the resources in proportion to their priority weight factors (Weight of
SPI). In addition, the resources necessary for guaranteeing the GBR must be allocated first
before the resource allocation based on the proportion.
For example, assume that Iub is the bottleneck, gold, silver and copper users are using
FTP service simultaneously. Then the Iub throughputs of gold, silver and copper users
are in proportion to the ratio of their SPI weights.
For another example, assume that the silver user is using HTTP service, the gold and the
copper user are using FTP service, and the silver user is reading the HTTP page. Then
the gold and copper users share the Iub resource and the Iub throughput of the gold and
copper users are in proportion to the ratio of their SPI weight.
If the frames are not in sequence, the frames are lost. Then the number of lost frames is
counted and the frame loss ratio at the Iub level in a specific time window is calculated.
Delay buildup is calculated as follows:
The HS-DSCH data frame transmission delay is the interval from the time when
HS-DSCH data frame is generated in the RNC (identified as DRT) to the time when the
frame arrives at the NodeB MAC-hs layer, including the buffer time in Iub Transport
Network Layer (TNL).
The delay buildup is the transmission delay increment comparing the sample delay with
the reference one obtained when Iub is free of congestion, as shown in Figure 4-8.
When the HS-DSCH carries only the BE service, the PF scheduling algorithm can make a
tradeoff between user equity and cell throughput. When the HS-DSCH carries more types of
services, such as VoIP, streaming, SRB, and IMS, the HSDPA scheduling algorithm needs to
guarantee the QoS. The reason is that such services have high requirements for delay or GBR.
Based on the PF, the EPF algorithm is designed to guarantee the QoS of the following
services:
SRB and IMS have high requirements for service connection delay and handover delay.
In addition, the average traffic volume and the consumption of the Uu interface are low.
Therefore, the algorithm always selects the MAC-hs queues of SRB and IMS first.
The VoIP service is highly delay sensitive. The maximum delay of MAC-d PDUs in a
queue is specified by the discard timer of the MAC-hs queue. The scheduler needs to
send out the MAC-d PDUs before the discard timer expires. The discard timer is usually
shorter than 100 ms. Therefore, the scheduler has little chance of considering the channel
quality. The scheduler always selects VoIP services after scheduling SRB and IMS
services. Among MAC-hs queues of VoIP, the selection is based on both delay and
channel quality.
The streaming service is usually the CBR (Constant Bit Rate) streaming service. If the
rate of this service is not lower than the GBR, the user can obtain good experience.
Therefore, the scheduler needs to guarantee the GBR. When the average rate of the
streaming service is lower than the GBR, the queues of the streaming service are selected
first after SRB, IMS, and VoIP. Among the MAC-hs queues of the streaming service, the
selection is based on PF.
The BE service is allocated with the remaining resource after the resource requirements
of the SRB, IMS, VoIP, and streaming services are met. Among the MAC-hs queues of
the BE service, the selection is based on PF. In addition, the resource allocation complies
with the following rules. Firstly, the GBR should be guaranteed first. Secondly, the
algorithm considers the requirement for user differentiation. For all the users in the cell,
the scheduler intends to allocate the radio resource in proportion to their Weight of SPI,
which is based on user priorities, eg. gold, silver and copper. For example, assuming that
radio resource is the bottleneck, gold , silver and copper users of same channel quality
are using FTP service simultaneously, then the Uu throughputs of gold, silver and copper
users are in proportion to the ratio of their SPI weights. For another example, assuming
that the silver user is using HTTP service, the gold and copper user are using FTP service,
and the silver user are reading the HTTP page, then the gold and copper users share the
radio resource, and the Uu throughput of the gold and copper users are in proportion to
the ratio of their SPI weight.
In a network, some UEs may be in a poor radio environment. More cell resources are used to
ensure the GBR of these UEs, and consequently, quite few cell resources are available for
other UEs. To avoid this problem, the resource limiting function is used. This function can be
enabled through the parameter Resource Limiting Switch, which can be set on the NodeB
LMT.
If Scheduling Method is set to EPF and Resource Limiting Switch is set to OPEN, the
resource limiting function is enabled.
The parameter that specifies the switch for resource limiting is shown as follows:
Resource limiting ratio is fixed according to GBR. The maximum ratio of the resource that
can be used by GBR users is shown as follows:
8k 10%
16k 10%
32k 15%
64k 15%
128k 20%
256k 25%
384k 30%
After scheduling, HSDPA users will be allocated to different time and code. The following
figure shows the time division and code division over the air interface for HSDPA users in one
cell.
Figure 4-9 HSDPA scheduling based on time division and code division
− DS_PQ_SCHEDULE: SRB/IMS scheduling policy. The SRB and IMS queues are
scheduled before the VoIP, streaming and BE queues. DS means delay sensitive. PQ
means priority queue.
− DS_URGENT_SCHEDULE: VoIP scheduling policy. The VoIP queues are scheduled
before the streaming and BE queues but after the SRB and IMS queues.
− TS_SCHEDULE: streaming/BE scheduling policy. The streaming and BE queues are
scheduled after the SRB, IMS, and VoIP queues. Among the streaming and BE
queues, the resources for GBR are allocated first. The remaining resources are
allocated as required by golden, silver, and copper users. TS means throughput
sensitive.
− Δ is the reference power adjustment. For detailed information, see 3GPP TS 25.214.
− Γ = Max(-6, Min(13, PCellMAX - PCPICH - MPOconstant))
− PCell-MAX - PCPICH = maximum transmit power of the cell - CPICH transmit power
− MPOconstant represents HS-PDSCH MPO Constant and can be set on the RNC LMT.
UE capability
It denotes that the maximum number of HS-PDSCH code that the UE can use, the
maximum size of the transport block that the UE can receive, and whether the UE
supports 16QAM.
2. If there is sufficient amount of data cached in the MAC-hs queue (TBSmax < Queue
length), the data is scheduled for the UE as much as possible in the maximum format of
TFRC, that is, TBS = TBSmax.
3. If there is insufficient amount of data cached in the queue (TBSmax > Queue length), the
Uu resources necessary for the UE are allocated on the basis of the amount of data in the
queue.
Select the TFRC (power, code, and modulation mode) by searching the CQI-Max TBS
mapping table and taking the amount of data cached in the queue into consideration. The
search is based on the priority defined by the Resource Allocate Method parameter, that
is, code preferable or power preferable.
Outdoor cells usually have sufficient code resources but limited power resources.
Therefore, for outdoor cells, codes take precedence over power during TFRC selection,
so as to achieve resource efficiency in both code and power and to improve the cell
throughput. For indoor cells, the priorities of codes and power are just the opposite, that
is, power usually takes precedence over codes.
The following figure shows an example of TBSmax searching.
4. After TFRC is determined, the matched CQI of TBS in the CQI-MaxTBS mapping table
is determined. This CQI is expressed as CQIused. Then, the transmit power of the
HS-PDSCHs is calculated as follows:
POWERHS-PDSCH = PCPICH + Γ – (CQI - CQIused).
Within one TTI, the HS-PDSCH power and HS-SCCH power allocated to one UE cannot
exceed the value of the MAX POWER PER HS-USER parameter. The limitation on
the total transmit power of a single user is made for the following reason. In the initial
deployment, only a few HSDPA users are included in a cell without high cell load
expected. The function of HSDPA power limitation per user can limit the HSDPA cell
load in this case. The HSDPA cell load is limited by the The Offset of HSPA Total
Power parameter.
Setting MPO
If the value of HS-PDSCH MPO Constant is set properly, the probability of CQI being
equal to 0 or 30 is very low, for example, 1% or lower. Otherwise, the parameter value should
be adjusted. This parameter is set for the purpose that the CQI reported is within the range of
1 to 30.
As shown in the figure, the NodeB detects the R99 power occupancy every 2 ms to determine
the power available for HSDPA. A certain Power Margin must be reserved to handle the
power increase caused by R99 power control in each 2 ms.
The Code Number for HS-PDSCH parameter can be set on the RNC LMT. The value of
Code Number for HS-PDSCH is determined by the service model and the cell traffic model.
A minimum number of codes, defined by the Code Min Number for HS-PDSCH parameter,
are reserved for the HS-PDSCH in a cell. When the channelization codes in the cell are idle
and adjacent to the reserved HS-PDSCH codes, the number of codes for the HS-PDSCH can
be increased but cannot exceed the value of the Code Max Number for HS-PDSCH
parameter. The difference codes between Code Max Number for HS-PDSCH and Code
Min Number for HS-PDSCH are shared by the HS-PDSCH and the DPCH. The shared
codes are allocated to the HS-PDSCH only when the DPCH does not use them. The dynamic
allocation includes the increase and decrease of the codes for the HS-PDSCH.
After increasing the codes for the HS-DSCH, the SF of the remaining codes should be
equal to or smaller than the value of Cell LDR SF reserved threshold.
Cell LDR SF reserved threshold is used to reserve code resources for new admission and
avoid code resource congestion. For details of Cell LDR SF reserved threshold, refer to
Basic Congestion Triggering in Load Control.
The NodeB detects the SF16 codes that are not for the HS-PDSCH every 2 ms. If the codes or
sub-codes are allocated by the RNC to the DCH or common channels, they are regarded as
occupied. Otherwise, they are regarded as unoccupied. Therefore, the HS-PDSCH codes
available for the HS-PDSCH include the codes allocated by the RNC and those unoccupied
consecutive SF16 codes that are adjacent to the reserved HS-DSCH codes.
For example, in a cell HS-PDSCH, the RNC allocates SF16 codes numbered 11 to 15 to
HS-PDSCH, SF16 codes numbered 0 to 5 to the DCH and common channels. Then, in this
TTI, the HS-PDSCH can use SF16 codes numbered 6 to 15.
If the DCH codes allocated by the RNC are temporarily occupied by the HS-PDSCH before
the setup of a radio link, the NBAP message is sent to the RNC, indicating that the radio link
is set up successfully. Then, the DCH occupies the codes. The HS-PDSCH cannot use these
codes until they are released by the DCH.
Optimized scheduling for VoIP over HSPA, refer to HSDPA Description and HSUPA
Description.
RoHC, refer to PDCP Header Compression Description.
Figure 4-19 Inter-Node B (inter DRNC) synchronized serving HS-DSCH cell change at hard
handover
UE State Transition
Channel Switching Between HS-DSCH and FACH
Channel Switching Between HS-DSCH and DCH
UE State Transition
After the HSDPA technology is introduced, a UE has a new RRC state, CELL_DCH (with
HS-DSCH). The following figure shows the UE state transition.
The following table lists the UE state transition and channel switching.
5 HSDPA Parameters
HSDPA Parameters provides information on the effective level and configuration of the
parameters related to the feature.
Cell(SET
EPFSA NodeB
EPF Schedule Algorithm Switch MACHSSPIPARA)
Cell(SET
FCA NodeB
Flow Control Algorithm Switch MACHSSPIPARA)
Cell(SET
CQIADJA NodeB
CQI Adjust Algorithm Switch MACHSSPIPARA)
Cell(SET
MAXRETRANS NodeB
Max Retransmission Count MACHSSPIPARA)
Cell(SET
RBLERTARGET NodeB
Residual Bler Target MACHSSPIPARA)
Cell(SET
SPIWEIGHT NodeB
Weight of SPI MACHSSPIPARA)
NodeB(SET
SWITCH HSDPAFLOWCTRLPAR NodeB
Hsdpa Switch A)
NodeB(SET
DR HSDPAFLOWCTRLPAR NodeB
Discard Rate A)
Scheduling Method SM Cell(SET MACHSPARA) NodeB
Resource Limiting Switch RSCLMSW Cell(SET MACHSPARA) NodeB
Cell(SET
EPFSA NodeB
EPF Schedule Algorithm Switch MACHSSPIPARA)
MAX POWER PER HS-USER MXPWRPHUSR Cell(SET MACHSPARA) NodeB
Resource Allocate Method RSCALLOCM Cell(SET MACHSPARA) NodeB
Cell(SET
MAXRETRANS NodeB
Max Retransmission Count MACHSSPIPARA)
Cell(SET
RBLERTARGET NodeB
Residual Bler Target MACHSSPIPARA)
Power Margin PWRMGN Cell(SET MACHSPARA) NodeB
Dynamic Code Switch DYNCODESW Cell(SET MACHSPARA) NodeB
Time delay TD NodeB(SET NodeB
HSDPAFLOWCTRLPAR
A)