Hsdpa (Ran13.0 03)

HSDPA RAN13.
Feature Parameter Description
Issue Date
03 2011-10-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: Email: http://www.huawei.com support@huawei.com
WCDMA RAN HSDPA
Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1 1.2 Intended Audience ........................................................................................................................ 1-1 1.3 Change History.............................................................................................................................. 1-1
2 Overview of HSDPA ..................................................................................................................2-1

2.1 General Principles of HSDPA ........................................................................................................ 2-1 2.2 HSDPA Channels .......................................................................................................................... 2-1 2.2.1 HS-DSCH and HS-PDSCH .................................................................................................. 2-2 2.2.2 HS-SCCH ............................................................................................................................. 2-2 2.2.3 HS-DPCCH ........................................................................................................................... 2-2 2.2.4 DPCCH and DPCH/F-DPCH ................................................................................................ 2-3 2.3 Impact of HSDPA on NEs .............................................................................................................. 2-3 2.4 HSDPA Functions .......................................................................................................................... 2-3 2.4.1 HSDPA Control Plane Functions .......................................................................................... 2-3 2.4.2 HSDPA User Plane Functions .............................................................................................. 2-5
3 Control Plane .............................................................................................................................3-1

3.1 Bearer Mapping ............................................................................................................................. 3-1 3.2 Access Control .............................................................................................................................. 3-2 3.3 Mobility Management .................................................................................................................... 3-2 3.4 Channel Switching......................................................................................................................... 3-2 3.5 Load Control .................................................................................................................................. 3-4 3.6 Power Resource Management...................................................................................................... 3-5 3.7 Code Resource Management ....................................................................................................... 3-5 3.7.1 HS-SCCH Code Resource Management ............................................................................. 3-6 3.7.2 HS-PDSCH Code Resource Management........................................................................... 3-6 3.7.3 Dynamic Code Tree Reshuffling ........................................................................................... 3-7
4 User Plane...................................................................................................................................4-1
4.1 Flow Control and Congestion Control ........................................................................................... 4-1 4.1.1 Flow Control ......................................................................................................................... 4-1 4.1.2 Congestion Control ............................................................................................................... 4-2 4.2 RLC and MAC-d ............................................................................................................................ 4-2 4.2.1 RLC....................................................................................................................................... 4-2 4.2.2 MAC-d .................................................................................................................................. 4-3 4.3 MAC-hs Scheduling ...................................................................................................................... 4-3 4.3.1 Determining the Candidate Set ............................................................................................ 4-4 4.3.2 Calculating Priorities ............................................................................................................. 4-4 4.3.3 Time and HS-PDSCH Codes Multiplex ................................................................................ 4-6 4.4 HARQ ............................................................................................................................................ 4-7
Issue 03 (2011-10-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
ii
WCDMA RAN HSDPA
Contents
4.4.1 HARQ Retransmission Principles......................................................................................... 4-7 4.4.2 Soft Combining During HARQ .............................................................................................. 4-8 4.4.3 Preamble and Postamble ..................................................................................................... 4-8 4.5 TFRC Selection ............................................................................................................................. 4-9 4.6 CQI Adjustment Based on Dynamic BLER Target ...................................................................... 4-10 4.7 Modulation Scheme .................................................................................................................... 4-10
5 QoS and Diff-Serv Management ...........................................................................................5-1

5.1 QoS Management ......................................................................................................................... 5-1 5.2 Diff-Serv Management .................................................................................................................. 5-2
6 Parameters .................................................................................................................................6-1 7 Counters ......................................................................................................................................7-1 8 Glossary ......................................................................................................................................8-1 9 Reference Documents .............................................................................................................9-1
Issue 03 (2011-10-30)
iii
WCDMA RAN HSDPA
1 Introduction
1 Introduction
1.1 Scope
This document describes the HSDPA functional area. It provides an overview of the main functions and goes into details regarding HSDPA control and user plane functions.
1.2 Intended Audience

This document is intended for:

Personnel who are familiar with WCDMA basics Personnel who need to understand HSDPA Personnel who work with Huawei products
1.3 Change History

This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows:

Feature change: refers to the change in the HSDPA feature. Editorial change: refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows:

03 (2011-10-30) 02 (2011-06-30) 01 (2011-04-30) Draft B (2011-03-30) Draft A (2010-12-30)
03 (2011-10-30)
This is the document for the third commercial release of RAN13.0. Compared with issue 02 (2011-06-30) of RAN13.0, this issue optimizes the dynamic code tree reshuffling function. For details, see 3.7.3 "Dynamic Code Tree Reshuffling."
02 (2011-06-30)
This is the document for the second commercial release of RAN13.0. Compared with issue 01 (2011-04-30) of RAN13.0, this issue adds the information about CQI adjustment based on dynamic BLER target. For details, see 4.6 CQI Adjustment Based on Dynamic BLER Target.
01 (2011-04-30)
This is the document for the first commercial release of RAN13.0. Compared with issue Draft B (2011-03-30) of RAN13.0, this issue optimizes the description about dynamic code tree reshuffling. For details, see 3.7.3 "Dynamic Code Tree Reshuffling."
Issue 03 (2011-10-30)
1-1
WCDMA RAN HSDPA
1 Introduction
Draft B (2011-03-30)
This is the draft of the document for RAN13.0. Compared with issue Draft A (2010-12-30) of RAN13.0, this issue optimizes the description.
Draft A (2010-12-30)
This is the draft of the document for RAN13.0. Compared with issue 02 (2010-06-20) of RAN12.0, this issue optimizes the description.
Issue 03 (2011-10-30)
1-2
WCDMA RAN HSDPA
2 Overview of HSDPA
2 Overview of HSDPA
2.1 General Principles of HSDPA
To meet the rapidly growing demands for data services on the mobile network, 3GPP Release 5 introduced HSDPA in 2005. HSDPA improves the downlink capacity, increases the user data rate greatly, and reduces the transmission delay on the WCDMA network. The characteristics of HSDPA are as follows: Fast scheduling Fast scheduling introduced into the NodeB determines the UEs for data transmission in each TTI (2 ms) and dynamically allocates resources to these UEs. It improves the usage of system resources and increases the system capacity. For details about how Huawei RAN implements fast scheduling, see section4.3 "MAC-hs Scheduling." Fast HARQ Fast hybrid automatic repeat request (HARQ) is used to rapidly request the retransmission of erroneously received data. Specifically, when the UE detects an erroneous data transmission, it saves the received data and requests the NodeB to retransmit the original data at the physical layer. Before decoding, the UE performs soft combining of the saved data and the retransmitted data. The combining makes full use of the data transmitted each time and therefore increases the decoding success rate. In addition, the retransmission delay at the physical layer is reduced greatly, compared with that at the RLC layer. For details about how Huawei RAN implements fast HARQ, see section 4.4 "HARQ." Fast AMC To compensate for channel variations, the DCH performs power control. To achieve this goal, HSDPA also performs fast adaptive modulation and coding (AMC), that is, adjusts the modulation scheme and coding rate in each TTI. AMC is based on the channel quality indicator (CQI) reported by the UE, and its purpose is to select an appropriate transmission rate so as to meet channel conditions. When the channel conditions are good, 16QAM can be used to provide higher transmission rates. When the channel conditions are poor, QPSK can be used to ensure the transmission quality. For details about how Huawei RAN implements fast AMC, see section 4.5 "TFRC Selection."
The MAC-hs, a new MAC sublayer, is introduced into the UE and NodeB to support HSDPA.
2.2 HSDPA Channels

To support the HSDPA technologies, 3GPP defines one transport channel (HS-DSCH) and three physical channels (HS-PDSCH, HS-SCCH, and HS-DPCCH). Figure 2-1 shows the physical channels of HSDPA in the shaded area.
Issue 03 (2011-10-30)
2-1
WCDMA RAN HSDPA
2 Overview of HSDPA
Figure 2-1 Physical channels of HSDPA
2.2.1 HS-DSCH and HS-PDSCH

HS-DSCH is a high speed downlink shared channel. Its TTI is fixed to 2 ms. It may be mapped onto one or more HS-PDSCHs. HS-PDSCH is a high speed physical downlink shared channel. Its spreading factor is fixed to 16. According to 3GPP TS 25.433, a maximum of 15 HS-PDSCHs can be used for transmission at the same time. The number of HS-PDSCHs per cell is configurable. Generally, the NodeB can use the HS-PDSCH codes only allocated by the RNC. The NodeB-controlled dynamic code allocation, however, allows the NodeB to temporarily allocate idle codes to the HS-PDSCH. The use of 2 ms TTI reduces the round trip time (RTT) on the Uu interface and, together with AMC, improves the tracking of channel variations. In addition, the use of 2 ms TTI enables fast scheduling and resource allocation and therefore improves the usage of transmission resources. In each TTI, HSDPA assigns the HS-PDSCHs onto which the HS-DSCH maps. More HS-PDSCHs can provide higher transmission rates. Unlike the DCH, the HS-DSCH cannot support soft handover. The reason is that this type of handover requires different cells to use the same radio resource for sending the same data to the UE, but the scheduling function can be performed only within the cell.
2.2.2 HS-SCCH
HS-SCCH is a high speed shared control channel. It carries the control information related to the HS-PDSCH. The control information includes the UE identity, HARQ-related information, and information about transport format and resource combination (TFRC). For each transmission of the HS-DSCH, one HS-SCCH is required to carry the related control information. One cell can be configured with several HS-SCCHs. The number of HS-SCCHs determines the maximum number of UEs that can be scheduled simultaneously in each TTI.
2.2.3 HS-DPCCH
HS-DPCCH is a high speed dedicated physical control channel. In the uplink, each HSDPA UE must be configured with an HS-DPCCH. This channel is mainly used by the UE to report the CQI and whether a transport block is correctly received. The information about the transport block is used for fast retransmission at the physical layer. The CQI is used for AMC and scheduling to allocate Uu resources.
Issue 03 (2011-10-30)
2-2
WCDMA RAN HSDPA
2 Overview of HSDPA
2.2.4 DPCCH and DPCH/F-DPCH

DPCCH is a dedicated physical control channel in the uplink. DPCH is a dedicated physical channel in the downlink. F-DPCH is a fractional dedicated physical channel in the downlink. The HSDPA UE must be configured with dedicated physical control channels in both the uplink and the downlink. The uplink DPCCH is used for providing reference information about the transmit power of HSDPA channels. In addition, it is used for closed-loop power control by working with the DPCH or F-DPCH. In SRB over HSDPA mode, the downlink channel can be established on the F-DPCH without the dedicated assisted DPCH. In this case, a maximum of 10 UEs use an SF256 to transmit the TPC, saving a large amount of downlink codes.
2.3 Impact of HSDPA on NEs

HSDPA has an impact on the RNC, NodeB, and UE. On the control plane of the network side, the RNC processes the signaling about HSDPA cell configuration, HS-DSCH related channel configuration, and mobility management. On the user plane of the network side, the RLC layer and MAC-d of the RNC are unchanged. At the NodeB, the MAC-hs is added to implement HSDPA scheduling, Uu resource allocation, AMC, and Iub flow control. The MAC-hs implements these management functions in a short time. Therefore, it reduces both unnecessary delays and processing complexity caused by Iub message exchange. On the UE side, the MAC-hs is added between the MAC-d and the physical layer for data reception. To support HSDPA, 3GPP defines 12 UE categories. These UEs support different peak rates at the physical layer, ranging from 912 kbit/s to 14 Mbit/s. The UE of category 10 supports the highest rate. The UE of category 11 or 12 supports only the QPSK mode. For details, see 3GPP TS 25.306. Huawei RAN supports all the UE categories.
2.4 HSDPA Functions

HSDPA functions are implemented on the HSDPA control plane and user plane.
2.4.1 HSDPA Control Plane Functions

The control plane is responsible for setting up and maintaining HS-DSCH connections and managing cell resources. Figure 2-2 shows the HSDPA control plane functions based on the service connection setup and maintenance procedure.
Issue 03 (2011-10-30)
2-3
WCDMA RAN HSDPA
2 Overview of HSDPA
Figure 2-2 HSDPA control plane functions
The HSDPA control plane functions are described as follows:
Bearer mapping The bearer mapping is used by the network side to configure the RAB during the setup of a service connection in the cell. The network side then configures bearer channels for the UE based on the requested service type, service rate, UE capability, and cell capability. For details, see section 3.1 "Bearer Mapping."
Access control Access control, a sub-function of load control, checks whether the current resources of the cell are sufficient for the service connection setup. If the resources are insufficient, intelligent access control is triggered. If the resources are sufficient, the service connection can be set up. For details, see section 3.2 "Access Control."
Mobility management For the established HS-DSCH connection, mobility management decides whether to switch it to another cell for providing better services, based on the channel quality of the UE. For details, see section 3.3 "Mobility Management."
Channel switching Channel switching is responsible for switching the transport channel among the HS-DSCH, DCH, and FACH based on the requirements of mobility management or load control. For details, see section 3.4 "Channel Switching."
Load control When the cell load increases, the load control function adjusts the resources configured for the established radio connections to avoid cell overload. For details, see section 3.5 "Load Control."
Resource management Resource management coordinates the power resource between the HS-DSCH and the DCH and the code resource between the HS-SCCH and the HS-PDSCH. The downlink power and codes are the bottleneck resources of the cell. Resource management can increase the HSDPA capacity.
Issue 03 (2011-10-30)
2-4
WCDMA RAN HSDPA
2 Overview of HSDPA
Power resource management reserves power for channels of different types and allocates power for them. For details, see section 3.6 "Power Resource Management." Code resource management allocates and reserves code resources for channels of different types. In addition, it collects and reshuffles idle code resources. For details, see section 3.7 "Code Resource Management."
2.4.2 HSDPA User Plane Functions

After the service is set up, the user plane is responsible for implementing data transmission. Figure 2-3 shows the HSDPA user plane functions based on the data processing procedure. Figure 2-3 HSDPA user plane functions
The service data carried on the HS-DSCH is passed to the RLC layer and MAC-d of the RNC for processing and encapsulation. Then, the MAC-d PDU is formed and passed through the Iub/Iur interface to the NodeB/RNC. To avoid congestion, the flow control and congestion control functions control the traffic on the Iub/Iur interface through the HS-DSCH frame protocol (3GPP TS 25.435). After the MAC-d PDU is received by the NodeB, it is passed through the MAC-hs to the physical layer and then sent out through the Uu interface. The MAC-hs provides MAC-hs scheduling, TFRC selection, and HARQ. MAC-hs scheduling determines the HSDPA users in the cell for data transmission. TFRC selection determines the transmission rates and Uu resources to be allocated to the HSDPA UEs. HARQ is used to implement the hybrid automatic repeat request function.
Issue 03 (2011-10-30)
2-5
WCDMA RAN HSDPA
3 Control Plane
3 Control Plane
This chapter consists of the following sections:

Bearer Mapping Access Control Mobility Management Channel Switching Load Control Power Resource Management Code Resource Management
3.1 Bearer Mapping

The HS-DSCH can carry services of multiple types and service combinations, as listed in Table 3-1. Table 3-1 Bearer mapping CN Domain Service Type Signaling (SRB) Can Be Carried on HS-DSCH? Yes Optional Feature? Yes Feature name: SRB over HSDPA CS Voice Yes Yes Feature name: CS Voice over HSPA/HSPA+ Videophone Streaming PS Conversational No No Yes No No Yes Feature name: VoIP over HSPA/HSPA+ Streaming Yes Yes Feature name: Streaming Traffic Class on HSDPA Interactive Background IMS signaling Yes Yes Yes No No Yes Feature name: IMS Signaling over HSPA MBMS PTP Yes Yes Feature name: MBMS P2P over HSDPA
During the service setup, the RNC selects appropriate channels based on the UE capability, cell capability, and service parameters to optimize the use of cell resources and ensure the QoS. Huawei RAN supports the setting of the types of RABs carried on the HS-DSCH according to service requirements. For details, see the Radio Bearers Feature Parameter Description.
Issue 03 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 3-1
WCDMA RAN HSDPA
3 Control Plane
3.2 Access Control

Access control determines whether an HS-DSCH connection can be set up under the precondition that the QoS is ensured. The determination is based on the status of cell resources and the situation of Iub/Iur congestion. When the resources are insufficient, the HS-DSCH is switched to the DCH and only the DCH connection is set up. When the resources are sufficient, the DCH is switched to the HS-DSCH. The implementation of this function requires the support of channel switching. Access control allows the HSDPA UE to access an inter-frequency neighboring cell that has the same-coverage area as the source cell. The purpose is to achieve load balance between the cells and improve HSDPA user experience. This is HSDPA directed retry decision (DRD), an optional feature. For details, see the Directed Retry Decision Feature Parameter Description.
3.3 Mobility Management

The DCH supports soft handover, and therefore downlink data can be concurrently sent out from all the cells in the active set in DCH transmission. In comparison, the HS-DSCH does not support soft handover, and therefore downlink data can be sent out only from the HS-DSCH serving cell and inter-cell handover has to be performed through the change of the serving cell. Therefore, HSDPA mobility management (WRFD-01061006 HSDPA Mobility Management) focuses on the change of the HS-DSCH serving cell. For the UE with the HS-DSCH service, the best cell in the active set acts as the HS-DSCH serving cell. When the best cell changes, the UE disconnects the HS-DSCH from the source cell and attempts to set up a new HS-DSCH connection with the new best cell. For details, see the Handover Feature Parameter Description. By changing the HS-DSCH switching threshold, you can modify the conditions for triggering the change of the best cell. Lowering this threshold can increase both the handover frequency and the sensitivity of HS-DSCH switching to signal variations in the serving cell. Raising this threshold can reduce the handover frequency but may increase the probability of the HS-DSCH service being discontinuous or even dropping on the cell edge. For the HS-DSCH service, Huawei supports inter-cell intra-frequency handover, inter-cell inter-frequency handover, and inter-RAT handover. Mobility management may trigger the switching from the HS-DSCH to the DCH. If the UE with the HS-DSCH service cannot set up the HS-DSCH connection with the target cell, the channel switching function, together with mobility management, switches the HS-DSCH to the DCH. When the HS-DSCH connection is available, the channel switching function switches the DCH back to the HS-DSCH. When the HSDPA user returns from the DCH cell to the HSDPA cell, the DCH is set up to ensure successful handover. A certain period later after the handover, the channel switching function switches the DCH to the HS-DSCH. For details, see section 3.4 "Channel Switching."
3.4 Channel Switching

After the HS-DSCH is introduced, the UE can stay in a new state, CELL_DCH (with HS-DSCH). Therefore, there are additional transitions between CELL_DCH (with HS-DSCH) and CELL_FACH and transitions between CELL_DCH (with HS-DSCH) and CELL_DCH even when both the cell and the UE support the HS-DSCH, as shown in Figure 3-1.
Issue 03 (2011-10-30)
3-2
WCDMA RAN HSDPA
3 Control Plane
Figure 3-1 UE state transition (WRFD-01061111 HSDPA State Transition)
Table 3-2 lists new state transition and new channel switching. Table 3-2 New state transition and new channel switching New State Transition CELL_DCH (with HS-DSCH) <-> CELL_FACH CELL_DCH (with HS-DSCH) <-> CELL_DCH New Channel Switching HS-DSCH <-> FACH HS-DSCH <-> DCH
Here, the switching between HS-DSCH and FACH can be triggered by traffic volume, which is similar to the switching between DCH and FACH. When the cell load is too high, load control may also trigger the switching from the HS-DSCH to the FACH to relieve congestion. For details, see the Load Control Feature Parameter Description. When the cell load becomes low, channel switching aids load control in attempting to switch the transport channel back to the HS-DSCH. For details, see the State Transition Feature Parameter Description. As the HS-DSCH is introduced later, it is inevitable that some cells support the HS-DSCH but others do not. This is also the case with UEs. When a service is set up, the channel switching function selects an appropriate bearer channel based on the cell capability and UE capability to ensure the QoS while efficiently using the cell resources. When the user is moving, the channel switching function adjusts the channel type based on the UE capability to ensure service continuity while improving user experience.
Issue 03 (2011-10-30)
3-3
WCDMA RAN HSDPA
3 Control Plane
Figure 3-2 Relationships between channel switching and other functions
Triggers for switching from the HS-DSCH to the DCH are as follows:
The HS-DSCH is selected during the service setup but neither the resources of the serving cell nor the resources of the inter-frequency same-coverage neighboring cell are sufficient. In such a case, the HS-DSCH is switched to the DCH. The HS-DSCH serving cell changes. The UE attempts to set up a new HS-DSCH connection with the new best cell. In such a case, the possible scenarios are as follows:
If If
the new best cell does not support the HS-DSCH, the UE cannot set up the HS-DSCH connection. In this case, the HS-DSCH is switched to the DCH. the new best cell supports the HS-DSCH but a new HS-DSCH connection cannot be set up because the resources are insufficient, the DCH connection is set up and the HS-DSCH is switched to this DCH. The user moves from a cell supporting the DCH but not supporting the HS-DSCH to a cell supporting the HS-DSCH. In this case, the DCH connection is also set up because the DCH supports soft handover, which can increase the handover success rate.
In one of the cases described previously, the DCH connection is set up in a cell supporting the HS-DSCH or in an inter-frequency same-coverage neighboring cell supporting the HS-DSCH. Then, the DCH is switched to the HS-DSCH by either of the following mechanisms:
Channel switching based on timer After the DCH connection is set up, this mechanism periodically attempts to switch the DCH to the HS-DSCH. Channel switching based on traffic volume When the traffic volume of the UE increases and the RNC receives an event 4A report, this mechanism attempts to switch the DCH to the HS-DSCH. For details on the event 4A report, see the State Transition Feature Parameter Description.
3.5 Load Control

When the cell is congested, load control selects some users (including HSDPA users) for congestion relief. The selection is based on the integrated priority, which considers the allocation retention priority (ARP), traffic class (TC), traffic handling priority (THP), and bearer type. When the cell load is high, the basic congestion control selects some HSDPA users for handover to an inter-frequency same-coverage neighboring cell or an inter-RAT neighboring cell with lower load. When the cell load is too high, the overload congestion control selects some HSDPA BE services for the switching to a common channel or releases some HSDPA services. For details, see the Load Control Feature Parameter Description.
Issue 03 (2011-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 3-4
WCDMA RAN HSDPA
3 Control Plane
3.6 Power Resource Management

Power resource management (WRFD-01061019 HSDPA Dynamic Power Allocation) determines the transmit power of the HS-PDSCH, HS-SCCH, and HS-DPCCH. Generally, an HSDPA cell has the same-coverage as the corresponding R99 cell. To improve the resource usage in this case, the downlink power resources of HSDPA can be dynamically allocated as follows: 1. The downlink power resources are first reserved for common physical channels and allocated to the DPCH. The remaining power resources are available for HSPA, including HSUPA and HSDPA. 2. The HSPA power resources are first allocated to the HSUPA downlink control channels, including the E-AGCH, E-RGCH, and E-HICH. The remaining power resources are available for HSDPA. 3. The HSDPA power resources are first allocated to the downlink control channel HS-SCCH. For details, see the Power Control Feature Parameter Description. The remaining power resources are allocated to the traffic channel HS-PDSCH. For details on power resource allocation, see section 4.5 "TFRC Selection." Figure 3-3 shows the dynamic HSDPA power resource allocation. Figure 3-3 Dynamic HSDPA power resource allocation
Every TTI, the NodeB detects the power usage of R99 channels to determine the power available for HSPA. To reserve the power for R99 power control itself, the power margin PwrMgn needs to be set on the NodeB side. In addition, the power allocated to HSPA must not exceed the maximum permissible power HspaPower, which can be set on the RNC side. For details on uplink HS-DPCCH power control, see the Power Control Feature Parameter Description.
3.7 Code Resource Management

Code resource management allocates code resources to the HS-SCCH and HS-PDSCH.
Issue 03 (2011-10-30)
3-5
WCDMA RAN HSDPA
3 Control Plane
The NodeB supports HS-DSCH transmissions to multiple users in parallel in a TTI. If more than one HS-PDSCH code can be allocated by the NodeB, then code multiplexing can be used to allocate the codes to multiple users so as to improve resource usage and system throughput.
3.7.1 HS-SCCH Code Resource Management

Each HS-SCCH uses an SF128 code. The number of HS-SCCHs determines the maximum number of HSDPA users that can be scheduled simultaneously in a TTI. Generally, the number of HS-SCCHs depends on the traffic characteristics of the cell. The default number is 4, which is specified by the parameter HsScchCodeNum on the RNC side. If the default setting is used, the HS-PDSCH can use only 14 SF16 codes. To enable the HS-PDSCH to use 15 SF16 codes, you are advised to configure 2 HS-SCCHs.
3.7.2 HS-PDSCH Code Resource Management

This section describes the feature WRFD-01061005 HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation and the feature WRFD-010631 Dynamic Code Allocation Based on NodeB. The transport channel HS-DSCH is mapped on one or several High-Speed Physical Downlink Shared Channels (HS-PDSCHs) which are simultaneously received by the UE. As indicated in 3GPP specifications, there are up to 15 HS-PDSCHs per cell with the spreading factor fixed to 16. The number of the HS-PDSCHs per NodeB is configurable and dependent on the license. The NodeB can dynamically allocate license codes to the HS-PDSCHs between cells based on the actual requirements. The number of available HS-PDSCH codes for a cell is the number of license codes allocated by the NodeB or the number of idle SF16 codes in the cell, whichever is smaller. The DPCH and the HS-PDSCH coexist in a cell. Therefore, sharing the cell code resources between them to improve the resource usage is of critical importance in HSDPA code resource management. Huawei supports both RNC-level and NodeB-level code resource management. RNC-controlled static or dynamic code allocation is enabled through the parameter AllocCodeMode. NodeB-controlled dynamic code allocation is enabled through the parameter DynCodeSw. The dynamic code allocation controlled by the NodeB is more flexible than that controlled by the RNC. It shortens the response time and saves the Iub signaling used for code reallocation.
If the RNC-controlled static code allocation is used: number of HS-PDSCH codes is specified by the parameter HsPdschCodeNum. minimum number of HS-PDSCH codes is specified by the parameter HsPdschMinCodeNum. maximum number of HS-PDSCH codes is specified by the parameter HsPdschMaxCodeNum. If the RNC-controlled dynamic code allocation is used:
The
The The
If the NodeB-Controlled Dynamic Code Allocation is used:
Every If
TTI, the NodeB-controlled dynamic code allocation allows the NodeB to temporarily allocate idle codes to the HS-PDSCH that are not used by DPCH. the setup of an RL requires a DPCH code that is already allocated by the NodeB to the HS-PDSCH, the NodeB releases this code and sends an NBAP message to the RNC, indicating that the RL is set up successfully.
Huawei recommends the following code allocation modes, where the first mode is preferred:

Configure the RNC to use static code allocation and the NodeB to use dynamic code allocation. If the NodeB does not support dynamic code allocation, configure the RNC to use dynamic code allocation.
Issue 03 (2011-10-30)
3-6
WCDMA RAN HSDPA
3 Control Plane
If not all the NodeBs controlled by an RNC support dynamic code allocation, the RNC-controlled dynamic code allocation is recommended. In this case, the NodeB-controlled dynamic code allocation can also be enabled for those supporting NodeBs.
3.7.3 Dynamic Code Tree Reshuffling

Regardless of whether dynamic code allocation is controlled by the RNC or the NodeB, the number of continuous codes available for the HS-PDSCH shall be maximized. The dynamic code tree reshuffling function can achieve this goal by reallocating DPCH/F-DPCH codes. Dynamic code tree reshuffling takes effect only when the following conditions are met:

The cell is not in the basic congestion state which is triggered by code resource. For details about basic congestion state, see the Load Control Feature Parameter Description. The switch parameter CodeAdjForHsdpaSwitch is set to ON.
Whether the F-DPCH codes can be reallocated through dynamic code tree reshuffling is determined by the parameter RsvdPara1: RSVDBIT6 in the MML command ADD UCELLALGOSWITCH When dynamic code tree reshuffling takes effect, the RNC reshuffles the codes used by the DPCH/F-DPCH to provide more continuous SF16 codes for HSDPA through this function. This function is described as follows: Every time the codes used by the DPCH are changed, the RNC will choose an SF16 subtree which are not used by HS-PDSCH from right to left. The selected subtree must meet the following conditions:

The selected subtree belongs to the code trees that can be shared between HS-PDSCH and DPCH. The number of DPCHs and F-DPCHs on the selected subtree is smaller than or equal to the threshold specified by the parameter CodeAdjForHsdpaUserNumThd. The parameter CodeAdjForHsdpaUserNumThd limits the number of users that can be reshuffled each time, to prevent too many users from being reshuffled in a short time and therefore to avoid affecting user experience.
When the above conditions are met, the RNC will select this subtree for reshuffling and relocate the users to the positions where the codes are idle. Figure 3-4 Dynamic code tree reshuffling
Issue 03 (2011-10-30)
3-7
WCDMA RAN HSDPA
4 User Plane
4 User Plane

Flow Control and Congestion Control RLC and MAC-d MAC-hs Scheduling HARQ TFRC Selection CQI Adjustment Based on Dynamic BLER Target Modulation Scheme
4.1 Flow Control and Congestion Control

HSDPA flow control (WRFD-01061010 HSDPA Flow Control) and congestion control are used to control the HSDPA data flow on the Iub and Iur interfaces. HSDPA data packets are sent through the Iub interface to the NodeB and then through the Uu interface to the UE. Therefore, congestion may occur on the Uu, Iub, or Iur interface. Flow control is used to relieve Uu congestion, and congestion control is used to relieve Iub/Iur congestion. The two types of control are implemented by the NodeB. HSDPA flow control and congestion control are part of the HSDPA Iub frame protocol (3GPP TS 25.435). They are implemented for each MAC-hs queue through the Capacity Request message sent by the RNC and the Capacity Allocation message sent by the NodeB. Figure 4-1 shows the basic principles of flow control and congestion control. Figure 4-1 Basic principles of Iub flow control and congestion control
4.1.1 Flow Control

For each MAC-hs queue, flow control calculates the pre-allocated Iub bandwidth based on the Uu transmission rate and the amount of data buffered in the NodeB. The Uu transmission rate of the MAC-hs queue is determined by the scheduling algorithm. For each MAC-hs queue, if the Iub
Issue 03 (2011-10-30)
4-1
WCDMA RAN HSDPA
4 User Plane
transmission rate is higher than the Uu transmission rate, the data packets are buffered. Too much data buffered in the NodeB leads to transmission delay and even packet loss. Therefore, each MAC-hs queue should not have too much data buffered in the NodeB. On the other hand, it should keep a certain amount of data to avoid wasting the Uu resources due to no data to transmit. The flow control procedure is as follows: 1. The NodeB measures the buffered data amount of each MAC-hs queue and the average Uu transmission rate. 2. The NodeB estimates the buffering time based on the measurements. 3. The NodeB adjusts the Iub bandwidth pre-allocated to the MAC-hs queue. The pre-allocated Iub bandwidth is adjusted as follows:
If the buffering time is too short, you can infer that the RNC slows down the data transmission, that is, the Iub transmission rate is lower than the Uu transmission rate. In this case, the pre-allocated Iub bandwidth is adjusted to a value greater than the average Uu transmission rate. If the buffering time is appropriate, the pre-allocated Iub bandwidth is adjusted to the average Uu transmission rate. If the buffering time is too long, the pre-allocated Iub bandwidth is adjusted to a value smaller than the average Uu transmission rate.
4.1.2 Congestion Control

The Iub bandwidth may be lower than the Uu bandwidth. If the RNC uses the Iub bandwidth pre-allocated to each MAC-hs queue, the Iub bandwidth for HSDPA is insufficient. This may lead to congestion and even packet loss. The amount of data to be transmitted is sent by the RNC to each MAC-hs queue through the Capacity Request message. Based on this amount and the total Iub bandwidth available for HSDPA, the congestion control function adjusts the bandwidth pre-allocated to each MAC-hs queue. Therefore, congestion control ensures that the total bandwidth actually allocated to all the MAC-hs queues is not higher than the total available Iub bandwidth. The total Iub bandwidth available for HSDPA depends on the variations in HSDPA packet delay and the situation of packet loss. HSDPA shares the bandwidth with the DCH and control signaling, and the DCH and control signaling has higher priorities than HSDPA. Therefore, when the HSDPA packet delay or packet loss increases, you can infer that the number of DCHs or the amount of control signaling increases. In such a case, the bandwidth available for HSDPA decreases and the bandwidth actually allocated for HSDPA decreases. For details on congestion control, see the Transmission Resource Management Feature Parameter Description.
For the Iur interface, flow control and congestion control are also applied. The control principles and processing procedures are the same as those for the Iub interface.
4.2 RLC and MAC-d

4.2.1 RLC
One of the main purposes of HSDPA is to reduce latency by handling retransmissions at NodeB level. Retransmissions, however, may still be triggered at the RLC layer of the RNC under the following circumstances:
The NodeB misinterprets an NACK sent by the UE.
Issue 03 (2011-10-30)
4-2
WCDMA RAN HSDPA

4 User Plane
The number of HARQ retransmissions exceeds the maximum permissible number. The data buffered in the NodeB is lost when the HS-DSCH serving cell changes.
Therefore, HARQ retransmission cannot totally replace RLC retransmission, which is described in 3GPP TS 25.322. For services with high requirements for data transmission reliability, Huawei recommends that the RLC acknowledged mode (AM) also be used to ensure correct transmission on the Uu interface even when the services such as the BE service are carried on HSDPA channels. Before the introduction of HSDPA, the size of an RLC PDU is usually 336 bits, where 320 bits are for the payload and 16 bits for the RLC header. Without additional overhead, the MAC PDU is of the same size as the RLC PDU. According to the 3GPP specifications, a maximum of 2,047 RLC PDUs can be transmitted within an RLC window, and the RTT at the RLC layer is about 100 ms (50 TTIs). In this condition, the maximum peak rate can only be 336 bits x (2047/50)/2 ms = 6.88 Mbit/s. To reach higher rates, an RLC PDU of 656 bits is introduced, where 640 bits are for the payload and 16 bits for the RLC header. The RLC PDU size can be set for each typical service. For high-speed services, the size is set to 656 bits by default.
4.2.2 MAC-d
The MAC-d functionality is unchanged after the introduction of HSDPA. The HS-DSCH bearers are mapped onto MAC-d flows on the Iub/Iur interface. Each MAC-d flow has its own priority queue. The theoretical peak rate of HSDPA on the Uu interface is 14.4 Mbit/s. It is calculated on the assumption that the chip rate of WCDMA is 3.84 Mcps, the spreading factor for HSDPA is SF16, the maximum number of available codes is 15, and the gain of 16QAM is 4. Therefore, the rate is 3.84 Mcps/16 x 15 x 4 = 14.4 Mbit/s. Limited by many factors, the theoretical peak rate of 14.4 Mbit/s is unreachable in actual situations. The UE capability is one factor. For example, 3GPP specifies that the UE of category 10 can use a maximum of 15 codes and receive a transport block with a maximum of 27,952 bits. For details, see 3GPP TS 25.306. Therefore, the theoretical peak rate is 27952 bits/2 ms = 13.976 Mbit/s. In addition, the RLC PDU size is fixed to 656 bits, and a transport block of 27,952 bits can contain a maximum of 42 PDUs. Therefore, the maximum RLC payload rate is (656 bits 16 bits) x 42/2 ms = 13.44 Mbit/s. In practice, the radio channel quality, retransmission probability, and available power also need to be considered. Therefore, the UE of category 10 cannot reach 13.44 Mbit/s at the RLC layer in most tests.
4.3 MAC-hs Scheduling

This section describes the feature WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF). With the limited Uu resources for HSDPA in a cell, the user expects to maximize the service rate while the telecom operator expects to maximize the system capacity. MAC-hs scheduling is used to coordinate the Uu resources, user experience, and system capacity. It is implemented at the NodeB MAC-hs. The scheduling algorithm consists of two steps. At first, the algorithm determines which initial transmission queues or retransmission processes can be put into the candidate set for scheduling. Then, the algorithm calculates their priorities based on factors such as the CQI, user fairness, and differentiated services. If the algorithm is weighted more towards the channel quality of the UE, the HSDPA cell can have a higher capacity but user fairness and differentiated services may be affected. If the algorithm is weighted more towards user fairness and differentiated services, the system capacity may be affected. Huawei provides four scheduling algorithms: maximum C/I (MAXCI), round-robin (RR), proportional fair (PF), and Enhanced Proportional Fair (EPF). The EPF algorithm is optional.
Issue 03 (2011-10-30)
4-3
WCDMA RAN HSDPA
4 User Plane
4.3.1 Determining the Candidate Set

The candidate for scheduling contains new data packets (initial transmission queues) or data packets to be retransmitted (retransmission processes), with the following exceptions:

If the UE starts the compressed mode, its data cannot be put into the candidate set during the GAP. If the UE category requires the UE to wait for several TTIs before it can be scheduled again, its data cannot be put into the candidate set in this period. The UE of category 1 or 2 needs to wait for 3 TTIs, and the UE of category 3, 4, and 11 must wait for 2 TTIs. If the number of retransmissions of a data packet reaches or exceeds the maximum number, the data of this UE cannot be put into the candidate set. The data should be discarded. Huawei supports that the maximum number of retransmissions is set on a service basis: the maximum number of non-conversational service retransmissions in the
MaxNonConverHarqRt:
CELL_DCH state
MaxEfachHarqRt:
the UE in the enhanced CELL_FACH state does not report ACK, NACK, or CQI in the uplink. The HARQ processes of the UE use the blind retransmission mechanism. The maximum number of retransmissions for the UE in Enhanced CELL_FACH Operation is specified by this parameter.
Other user data can be put into the candidate set.
4.3.2 Calculating Priorities

Four algorithms are available for calculating the priorities of data packets in the candidate set. The scheduling policies vary according to the algorithms for calculating the priorities of data packets. The algorithm to be used is specified by the parameter SM on the NodeB LMT.
Comparison of Four Algorithms

Table 4-1 lists the factors considered in the four scheduling algorithms. Table 4-1 Factors considered in the four scheduling algorithms Factor Service type Initial transmission or retransmission Maximum power Waiting time CQI Actual throughput SPI GBR HBR MAXCI No Yes No No Yes No No No No RR No Yes No Yes No No No No No PF No Yes No No Yes Yes No No No EPF Yes Yes Yes Yes Yes Yes Yes Yes Yes
Table 4-2 lists the effects of the four scheduling algorithms.
Issue 03 (2011-10-30)
4-4
WCDMA RAN HSDPA
4 User Plane
Table 4-2 Effects of the four scheduling algorithms Item System capacity User fairness Differentiated services Real-time services MAXCI Highest Not guaranteed Not guaranteed Not guaranteed RR High Best Not guaranteed Not guaranteed PF Higher Guaranteed Not guaranteed Not guaranteed EPF Higher Guaranteed Guaranteed Guaranteed
MAXCI Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues. The retransmission processes are sorted in first-in first-out (FIFO) mode. The initial transmission queues are sorted in the CQI order. A higher CQI means a higher data priority. The MAXCI algorithm aims to maximize the system capacity but cannot ensure user fairness and differentiated services. The UE estimates the CQI based on the assumption that the transmit power of the HS-PDSCH on the network side is as follows:
PHS PDSCH PCPICH

where

PCPICH is the transmit power of the CPICH.
is the measurement power offset (MPO). It is specified by the parameter HsPdschMPOConstEnum on the RNC side and sent to the NodeB and UE.
is the reference power adjustment. It is set to 0 in most cases. For details, see 3GPP TS 25.214.
RR Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues. The retransmission processes are sorted in FIFO mode. The initial transmission queues are sorted in the order of the waiting time in the MAC-hs queue. A longer waiting time means a higher data priority. The RR algorithm aims to ensure user fairness but cannot provide differentiated services. Not considering the CQI reported by the UE leads to lower system capacity.
PF Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission queues. The retransmission processes are sorted in FIFO mode. The initial transmission queues are sorted in the order of R/r. Here, R represents the throughput corresponding to the CQI reported by the UE, and r represents the throughput achieved by the UE. A greater R/r value means a higher data priority. The PF algorithm aims to make a tradeoff between system capacity and user fairness. It provides the user with an average throughput that is proportional to the actual channel quality. The system capacity provided by PF is between the system capacity provided by RR and that provided by MAXCI.
Issue 03 (2011-10-30)
4-5
WCDMA RAN HSDPA
4 User Plane
EPF Algorithm
The EPF algorithm (WRFD-01061103 Scheduling based on EPF and GBR) can meet the requirements of telecom operators related to user fairness and differentiated services and also provide a high system capacity. By calculating the priority of each queue, the scheduling algorithm achieves the following:
When the system resources are sufficient to meet the basic QoS requirements of all users, the transmission delay of delay-sensitive data is within the permissible range and the transmission rate of throughput-sensitive data is not lower than the GBR. High-priority users can obtain more resources for higher QoS. When the system resources are insufficient to meet the basic QoS requirements of all users, delay-sensitive data has higher priorities than throughput-sensitive data. High-priority users can obtain more resources to ensure the basic QoS.
Queue priorities are determined on the basis of service types. The EPF algorithm distinguishes between delay-sensitive data and throughput-sensitive data based on the QoS requirements. The following factors are considered: the waiting time, CQI reported by the UE, throughput achieved by the UE, guaranteed bit rate (GBR), scheduling priority indicator (SPI) weight, happy bit rate (HBR), and power consumed in the queue for a certain period. User fairness is implemented in EPF as follows:

EFP algorithm guarantees the user fairness in the same way as that PF algorithm. HBR and Resource Limit is used in EPF to limit the use of single users and improve fairness. HBR is used to determine the throughput expected by the user based on a study on user experience.
When
the rate for a user reaches the HBR, the scheduling probability for the user is decreased. The HBR is specified by the parameter HappyBR on the RNC side. Resource Limit is used to prevent the users in areas with poor coverage from consuming too many cell resources so that there is no decrease in system capacity.
When
the resource limitation switch (RscLmSw) is on, the algorithm allocates the lowest priority to a queue whose power consumption exceeds the threshold. The ratio of the maximum available power of a queue to the total power of the cell is specified by the NodeB MML command SET RSCLMTPARA.
Differentiated service is implemented in EPF as follows:
Differentiated services are provided based on SPI and SPI weights. is a parameter specified on the basis of service types and users priorities. can be specified according to the SPI to provide differentiated services.
SPI
SPIweight
The SPI weight affects the calculation of queue priorities. It is used to quantify the differentiated services. If resource is insufficient, the proportion of SPI weights determines the approximate proportion of rates among users. For example, for three throughput-sensitive service users with the same channel quality, the same GBR and the proportion of SPI weights is 100:50:30, the proportion of actual rates is close to 100:50:30.
For details on the parameters related to QoS management, such as the GBR, SPI, SPI weight, and HBR, see QoS Management Feature Parameter Description.
4.3.3 Time and HS-PDSCH Codes Multiplex

This section describes the feature WRFD-01061018 Time and HS-PDSCH Codes Multiplex.
Issue 03 (2011-10-30)
4-6
WCDMA RAN HSDPA
4 User Plane
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-2 HSDPA scheduling based on time division and code division
The feature of time and HS-PDSCH codes multiplex enables the allocation of different codes in the same TTI to different users or the time division multiplexing of the same code in different TTIs for different users to provide the utilization of code resources and the system throughput. The parallel data transmission of multiple users over HS-DSCH requires more HS-SCCH codes and HS-PDSCH codes within a single TTI. Code multiplexing is adopted and is found useful when the NodeB has more HS-PDSCH codes for allocation than those supported by the UE. For instance, the UE supports 5 codes and the NodeB has 10 codes available in a single TTI. The code multiplexing can increase the resource utilization and system throughput.
4.4 HARQ
The main purpose of introducing HARQ is to reduce the retransmission delay and improve the retransmission efficiency. HARQ enables fast retransmission at the physical layer. Before decoding, the UE combines the retransmitted data and the previously received data, making full use of the data transmitted each time. In addition, HARQ can fine-tune the effective rate to compensate for the errors made by TFRC section.
4.4.1 HARQ Retransmission Principles

The HARQ process of HSDPA involves only the NodeB and the UE, without involving the RNC. After receiving a MAC-hs PDU sent by the NodeB, the UE performs a CRC check and reports an ACK or NACK on the HS-DPCCH to the NodeB:

If the UE reports an ACK, the NodeB transmits the next new data. If the UE reports an NACK, the NodeB retransmits the original data. After receiving the data, the UE performs soft combining of this data and the data received before, decodes the combined data, and then reports an ACK or NACK to the NodeB.
RLC retransmission on the DCH involves the RNC, and therefore the RTT is relatively long. In comparison, HARQ involves only the physical layer and MAC-hs of the NodeB and those of the UE, and therefore the RTT is reduced to only 6 TTIs. After a transmission, the HARQ process must wait at least 10 ms before it can transmit the next new data or retransmit the original data. Therefore, to improve transmission efficiency, other HARQ processes can transmit data during the waiting time. A maximum of six HARQ processes can be configured in each of the NodeB HARQ entity and the UE HARQ entity. Note that not all UE categories support six HARQ processes. For example, the UEs of some categories can receive data every one or
Issue 03 (2011-10-30)
4-7
WCDMA RAN HSDPA
4 User Plane
two TTIs. Therefore, only two or three HARQ processes can be configured. The RAN can automatically choose the most appropriate configuration based on UE capability. Figure 4-3 HARQ retransmission principles
4.4.2 Soft Combining During HARQ

Before decoding a MAC-hs PDU, the UE performs soft combining of all the data received before to improve the utilization of Uu resources and therefore increase the cell capacity. The size of the UE buffer determines the number of coded bits or the size of transport blocks. For HARQ retransmission between the NodeB and the UE, two combining strategies are available. They are Chase Combining (CC) and Incremental Redundancy (IR). In the case of CC, all retransmitted data is the same as previously transmitted data. In the case of IR, the retransmitted data may be different from the previously transmitted data. In comparison, IR has a higher gain than CC but requires more buffer space. CC can be regarded as a special case of IR. The IR strategy is hard-coded in Huawei RAN.
4.4.3 Preamble and Postamble

If the HS-SCCH is received, the UE checks whether the HS-PDSCH is also correctly received and then reports an ACK or NACK in the first slot of the HS-DPCCH subframe. If the HS-SCCH is erroneously received, the UE does not report any information in the first slot of the HS-DPCCH subframe. This type of transmission is called DTX. In the case of high interference, the NodeB may demodulate DTX as ACK by mistake when demodulating the HS-DPCCH. Therefore, the lost data blocks cannot be retransmitted through HARQ retransmission, and the reception can be ensured only through RLC retransmission. To meet the requirement of the 3GPP specifications for a low DTX misjudgment probability, more power has to be allocated for HS-DPCCH ACK/NACK. To solve this problem, 3GPP TS 25.214 introduces preamble and postamble (WRFD-01061113 HS-DPCCH Preamble Support). When the NodeB demodulates an HS-DPCCH ACK/NACK, it considers the subframe prior to and the subframe next to the HS-DPCCH subframe in addition to the HS-DPCCH subframe itself. Therefore, for a certain DTX misjudgment probability, the introduction of preamble and postamble reduces the power required by ACK/NACK, lower the downlink load level, and increase the uplink capacity.
Issue 03 (2011-10-30)
4-8
WCDMA RAN HSDPA
4 User Plane
Figure 4-4 HS-DPCCH preamble and postamble
4.5 TFRC Selection

The TFRC selection algorithm handles the MAC-hs queues in descending order of their priorities determined by the scheduler. The main tasks of the algorithm for each queue in each TTI are as follows:

Determining the amount of data that can be transmitted by the queue Determining the modulation scheme of the queue Allocating appropriate power and channelization codes to the queue
During the handling, the TFRC selection algorithm considers the following factors:

Channel conditions of the UE (represented by CQI) Available resources power for every HSDPA user is restricted by MXPWRPHUSR. Amount of data buffered in the MAC-hs queue
The
Based on these factors, the algorithm allocates appropriate resources and selects appropriate transport block sizes (TBSs) to ensure the transmission quality and avoid wasting the resources.

When the channel conditions are bad, the algorithm selects small TBSs to ensure that the data is received correctly and transmitted continuously. When the channel conditions are good, the algorithm selects large TBSs for higher transmission rates and QoS.
Huawei supports three TFRC methods, which are specified by the parameter RscAllocM on the NodeB side:

If the parameter is set to Code_Pri, the TFRC algorithm prefers the use of codes. This setting is applicable the outdoor macro base station with limited power. If the parameter is set to Power_Pri, the TFRC algorithm prefers the use of power. This setting is applicable to indoor application with limited codes.
Issue 03 (2011-10-30)
4-9
WCDMA RAN HSDPA
4 User Plane
If the parameter is set to PowerCode_Bal, the algorithm balances the use of power and the use of codes. This setting protects the codes or power from being used up, improving the resource usage and increasing the cell capacity.
4.6 CQI Adjustment Based on Dynamic BLER Target

Overview
The CQI measures the channel conditions of a UE and is reported from the UE to the NodeB. Without this feature, the NodeB determines an appropriate TBS based on the reported CQI, system resources, and the TFRC policy. If the reported CQI and related conditions remain the same, the NodeB does not change the TBS because it does not consider the ever-changing radio environments. The constant changes in radio environments, caused by multipath effects and UE mobility, lead to fluctuating channel quality. Under these circumstances, choosing a TBS based on the reported CQI makes it difficult to always achieve the optimum downlink throughput. With this feature, the NodeB monitors the channel quality fluctuations for HSDPA users in a cell in real time and dynamically selects a proper BLER target based on the monitoring result. The NodeB then uses the BLER target to adjust the CQI reported by the UE. Based on the adjusted CQI, the NodeB determines an appropriate TBS to achieve higher downlink throughput for HSDPA users and higher cell throughput. The required BLER target may be high in some environments; therefore this feature is not suitable for networks that limit the BLER target. This feature requires that both the network and UE support HSDPA. In RAN13.0, this feature is applicable only to non-MIMO users. This feature can be enabled by selecting the CQI_ADJ_BY_DYN_BLER check box under the CQIADJALGOFNONCON parameter.
CQI Adjustment Process

CQI adjustment based on dynamic BLER target is performed in each TTI. The following describes the adjustment process: 1. Based on the CQI reported by the UE, the NodeB checks the actual radio environment, which is affected by multipath effects and UE mobility. 2. Based on the actual radio environment and channel quality of the UE, the NodeB obtains an optimum BLER target, which helps to achieve the highest possible throughput for the UE. 3. Based on the ACK, NACK, or DTX indication from the UE in the current TTI and on the optimum BLER target, the NodeB calculates the CQI offset, which can be a positive or negative number. The NodeB then uses the CQI offset to adjust the CQI. 4. Based on the adjusted CQI, the NodeB selects an appropriate TBS by using the TFRC algorithm.
4.7 Modulation Scheme

QPSK and 16QAM
The HS-PDSCH is used to carry the HS-DSCH data. HS-PDSCH can use QPSK (WRFD-01061017 QPSK Modulation) or 16QAM (WRFD-010629 DL 16QAM Modulation) modulation symbols.

When the UE is in the unfavorable radio environment, the transmission can adopt the low-order QPSK modulation mode and small transport blocks to ensure communication quality. When the UE is in the favorable radio environment, the transmission can adopt the high-order 16QAM modulation mode and large transport blocks to reach a high peak rate.
Issue 03 (2011-10-30)
4-10
WCDMA RAN HSDPA
4 User Plane
QPSK modulation is a basic downlink data modulation function that is used after HSDPA is introduced. Compared with the QPSK modulation, the 16QAM modulation is a higher-order downlink data modulation mode. This feature enables the peak rate on the Uu interface to reach 14.4 Mbit/s.
64QAM
3GPP R5 introduces 16QAM to increase the peak rate per user and expands the system capacity, whereas 64QAM introduced in 3GPP R7 protocols is a further enhancement of 16QAM. With downlink 64QAM, higher-order modulation technology than 16QAM can be used when the channel is of higher quality. Theoretically, 64QAM supports a peak data rate of 21 Mbit/s and at the same time increases the average throughput of the system. Simulation shows that compared with 16QAM, 64QAM can increase the average throughput by 7% and 16% respectively in macro cell and in micro cell, if the UEs in the cells use the type 3 receivers. The 3GPP R7 protocols define the categories of the UEs that support 64QAM, and add the information elements (IEs) that support 64QAM in the reporting of local cell capability. The RNC determines whether the RL between the NodeB and the UE supports 64QAM according to the local cell capability reported by the NodeB and the UE capability. If the RL supports 64QAM, the MAC-hs scheduler of the NodeB determines every 2 ms whether to use 64QAM according to the following aspects:

Channel Quality Indicator (CQI) reported by the UE HS-PDSCH code resources and power resources of the NodeB
Compared with the 16QAM modulation, the 64QAM modulation is a higher-order downlink data modulation mode. This feature enables the peak rate on the Uu interface to reach 21 Mbit/s.
Issue 03 (2011-10-30)
4-11
WCDMA RAN HSDPA
5 QoS and Diff-Serv Management


QoS Management Diff-Serv Management
5.1 QoS Management

The goal of service-oriented QoS management is to improve user experience by reducing the service delay and BLER and by increasing the service rate and continuity. The requirements for QoS vary according to the type of service:

The conversational service (including the CS voice and VoIP) has a relatively high requirement for service delay and a certain requirement for BLER. The streaming service has a requirement for guaranteed bit rate (GBR). The FTP service has a high requirement for BLER and error-free transmission. In addition, this service requires higher service rates to provide better user experience. The HTTP service has a high requirement for error-free transmission and a certain requirement for response delay. In addition, this service requires shorter delay to provide better user experience.
HSDPA QoS management is implemented by related HSDPA functions. The following table lists the relationships between HSDPA functions and QoS indicators. Table 5-1 Relationships between HSDPA functions and QoS indicators Function Mobility management HSDPA bearer mapping Load control RLC retransmission Flow control Congestion control HARQ MAC-hs scheduling TFRC selection Service Connectivity Service Delay Service Rate BLER
These relationships between HSDPA functions and QoS indicators are described as follows:
Mobility management Service continuity is implemented by mobility management. For details, see section 3.3 "Mobility Management" and the Handover Feature Parameter Description.
Bearer mapping
Issue 03 (2011-10-30)
5-1
WCDMA RAN HSDPA
HSDPA bearers increase the service rate greatly and reduce the service delay. For details, see section 3.1 "Bearer Mapping."
Load control The network resources are limited. Therefore, when a large number of users attempt to access the network, the access control function is required to control the access so as to ensure the QoS of the admitted users. The network resources consumed by the admitted users vary with the changed channel qualities, which may lead to network congestion. To relieve congestion, the overload control function is required to ensure the QoS of most users. For details on load control, see the Load Control Feature Parameter Description.
RLC retransmission and HARQ To achieve error-free transmission and improve transmission efficiency, HSDPA introduces HARQ at the physical layer. HARQ, however, cannot completely ensure error-free transmission. Therefore, it should work with RLC retransmission and TCP retransmission. For details, see sections 4.2 "RLC and MAC-d" and 4.4 "HARQ."
Flow control and congestion control By allocating appropriate Iub bandwidth to users, the flow control function reduces the transmission time. Therefore, it prevents too much data from waiting in the buffer at the MAC-hs and avoids unnecessary RLC retransmissions. In addition, it protects service data from overflowing from the buffer at the MAC-hs. Through congestion detection and congestion control, the congestion control function reduces the packet loss probability. For details, see section 4.1 "Flow Control and Congestion Control."
MAC-hs scheduling Based on the waiting time, achieved service rate, and GBR, the MAC-hs scheduling function sorts the users to meet the requirements for transmission delay and transmission rate on the Uu interface. For details, see section 4.3 "MAC-hs Scheduling."
TFRC selection Based on the available power, available codes, actual channel quality, and actual data amount, the TFRC selection function selects appropriate transport blocks and modulation schemes to increase data rates. For details, see section 4.5 "TFRC Selection."
5.2 Diff-Serv Management

Different services have different service types, and different users have different priorities. During resource allocation, differentiated services are provided. Differentiated services for HSDPA users are as follows:

Differentiated services based on service types Differentiated services based on user priorities To further quantify the effect of Diff-Serv management, differentiated services based on SPI weights (WRFD-020806 Differentiated Service Based on SPI Weight) are introduced. This section describes the differentiated services based on SPI weights and the differentiated service policies.
For details, see Differentiated HSPA Service Feature Parameter Description.
Issue 03 (2011-10-30)
5-2
WCDMA RAN HSDPA
6 Parameters
6 Parameters
Table 6-1 Parameter description Parameter ID AllocCodeMode NE BSC6900 MML Command Description
ADD Meaning: If Manual is chosen, parameter " Code UCELLHSDPA(Opt Number for HS-PDSCH " determines HS-PDSCH ional) code number to be allocated. If Automatic is chosen, allocate HS-PDSCH code number between MOD UCELLHSDPA(Opt configured " Code Max Number for HS-PDSCH " and " Code Min Number for HS-PDSCH ". For detailed ional) information of this parameter, refer to 3GPP TS 25.308. GUI Value Range: Manual(Manual), Automatic(Automatic) Actual Value Range: Manual, Automatic Default Value: Automatic
CQIADJALGOFN NodeB ONCON
SET MACHSPARA Meaning: Indicates the Channel Quality Indicator(CQI) Adjust Algorithm Switch of non-Conversational Service. GUI Value Range: NO_CQI_ADJ(Not CQI Adjust Algorithm), CQI_ADJ_BY_IBLER(CQI Adjusted by IBLER), CQI_ADJ_BY_DYN_BLER(CQI Adjusted by Dynamic BLER) Actual Value Range: NO_CQI_ADJ, CQI_ADJ_BY_IBLER, CQI_ADJ_BY_DYN_BLER Default Value: NO_CQI_ADJ(Not CQI Adjust Algorithm)
CodeAdjForHsdp BSC6900 aSwitch
ADD Meaning: This parameter specifies code reshuffling UCELLHSDPA(Opt switch for HDSPA. If the switch is set as ON, codes ional) occupied by the R99 service can be adjusted toward codes with small numbers to release the sharing MOD UCELLHSDPA(Opt codes adjacent to HSDPA code. When " Allocate Code Mode " is set to Automatic or the NodeB ional) automatic code algorithm is enabled, the released codes can be used by HSDPA and thus HSDPA throughput can be improved. GUI Value Range: OFF(OFF), ON(ON) Actual Value Range: OFF, ON Default Value: ON
Issue 03 (2011-10-30)
6-1
WCDMA RAN HSDPA
6 Parameters
Parameter ID
NE
MML Command
Description
CodeAdjForHsdp BSC6900 aUserNumThd
ADD Meaning: H-based code tree reshuffle user number UCELLHSDPA(Opt threshold. When the switch "Code Adjust Switch for ional) HSDPA"is enabled, if the number of users on the tree to be reshuffled is no greater than this parameter, the MOD UCELLHSDPA(Ma reshuffle is allowed. Otherwise, the reshuffle is given up. This parameter limits the number of users ndatory) involved in one reshuffle so that reshuffle on lots of users at a time is avoided. GUI Value Range: 1~16 Actual Value Range: 1~16 Default Value: 3
DYNCODESW
NodeB
SET MACHSPARA Meaning: Indicates the Dynamic Code Switch. GUI Value Range: OPEN(open), CLOSE(close) Actual Value Range: OPEN, CLOSE Default Value: OPEN(open)
HappyBR
BSC6900
SET Meaning: Defines the happy bit rate of the best effort UUSERHAPPYBR( (BE) service with different user priorities(user Optional) priorities can be set by parameter UserPriority). This Happy bit rate is sent to NodeB by RNC through the Iub interface. When the NodeB resource is limited and the HS-DSCH bit rate of the user exceeds the Happy bit rate, the HS-DSCH scheduling priority will be decreased. When this parameter is set to zero, it indicates that NodeB will not adjust the HS-DSCH scheduling priority.If the value of the parameter HappyBR in command ADD UOPERUSERHAPPYBR is larger than 5000, it will be set to the minimum of the HappyBR value in SET UUSERHAPPYBR and 5000. GUI Value Range: 0~27900 Actual Value Range: 0~27900 Default Value: 0
HsPdschCodeNu BSC6900 m
ADD Meaning: The parameter specifies the number of UCELLHSDPA(Opt HS-DPSCH codes. This parameter is valid only when ional) "Allocate Code Mode" is set to "Manual". For detailed information about this parameter, refer to 3GPP TS MOD UCELLHSDPA(Opt 25.308. ional) GUI Value Range: 1~15 Actual Value Range: 1~15 Default Value: 5
Issue 03 (2011-10-30)
6-2
WCDMA RAN HSDPA
6 Parameters
Parameter ID
NE
MML Command
Description
HsPdschMPOCo BSC6900 nstEnum
ADD Meaning: This parameter named Measure Power UCELLHSDPA(Opt Offset Constant is used to compute measurement ional) power offset. Measurement power offset is used by UE to obtain total received HS-PDSCH power. The MOD UCELLHSDPA(Opt calculation for Measure Power Offset is as shown below: ional) Measure Power Offset = Max(-6, Min(13,CellMaxPower - PcpichPower - Measure Power OffsetConstant)). For details of the IE "Measure Power Offset", refer to 3GPP TS 25.214. GUI Value Range: Minus3.0DB(-3.0dB), Minus2.5DB(-2.5dB), Minus2.0DB(-2.0dB), Minus1.5DB(-1.5dB), Minus1.0DB(-1.0dB), Minus0.5DB(-0.5dB), 0.0DB(0.0dB), 0.5DB(0.5dB), 1.0DB(1.0dB), 1.5DB(1.5dB), 2.0DB(2.0dB), 2.5DB(2.5dB), 3.0DB(3.0dB), 3.5DB(3.5dB), 4.0DB(4.0dB), 4.5DB(4.5dB), 5.0DB(5.0dB), 5.5DB(5.5dB), 6.0DB(6.0dB), 6.5DB(6.5dB), 7.0DB(7.0dB), 7.5DB(7.5dB), 8.0DB(8.0dB), 8.5DB(8.5dB), 9.0DB(9.0dB), 9.5DB(9.5dB), 10.0DB(10.0dB), 10.5DB(10.5dB), 11.0DB(11.0dB), 11.5DB(11.5dB), 12.0DB(12.0dB), 12.5DB(12.5dB), 13.0DB(13.0dB), 13.5DB(13.5dB), 14.0DB(14.0dB), 14.5DB(14.5dB), 15.0DB(15.0dB), 15.5DB(15.5dB), 16.0DB(16.0dB), 16.5DB(16.5dB), 17.0DB(17.0dB), 17.5DB(17.5dB), 18.0DB(18.0dB), 18.5DB(18.5dB), 19.0DB(19.0dB) Actual Value Range: -3.0dB, -2.5dB, -2.0dB, -1.5dB, -1.0dB, -0.5dB, 0.0dB, 0.5dB, 1.0dB, 1.5dB, 2.0dB, 2.5dB, 3.0dB, 3.5dB, 4.0dB, 4.5dB, 5.0dB, 5.5dB, 6.0dB, 6.5dB, 7.0dB, 7.5dB, 8.0dB, 8.5dB, 9.0dB, 9.5dB, 10.0dB, 10.5dB, 11.0dB, 11.5dB, 12.0dB, 12.5dB, 13.0dB, 13.5dB, 14.0dB, 14.5dB, 15.0dB, 15.5dB, 16.0dB, 16.5dB, 17.0dB, 17.5dB, 18.0dB, 18.5dB, 19.0dB Default Value: 2.5dB
Issue 03 (2011-10-30)
6-3
WCDMA RAN HSDPA
6 Parameters
Parameter ID
NE
MML Command
Description
HsPdschMaxCod BSC6900 eNum
ADD Meaning: The parameter determines the maximum UCELLHSDPA(Opt number of HS-PDSCH codes (SF=16). This ional) parameter is valid only when "Allocate Code Mode" is set to "Automatic". The number of codes used by the MOD UCELLHSDPA(Opt HS-PDSCH is dynamically set between "Code Min Number for HS-PDSCH" and "Code Max Number for ional) HS-PDSCH", based on whether the code tree is idle or busy. When the code resource used by the non-HSPA services is little, the HS-PDSCH uses the rest idle codes as much as possible, and the maximum number of idle codes (SF=16 continuous codes) is equal to the value of "Code Max Number for HS-PDSCH". GUI Value Range: 1~15 Actual Value Range: 1~15 Default Value: 5
HsPdschMinCode BSC6900 Num
ADD Meaning: The parameter specifies the minimum UCELLHSDPA(Opt number of the HS-PDSCH codes (SF=16). This ional) parameter is valid only when "Allocate Code Mode" is set to Automatic. The number of codes used by the MOD UCELLHSDPA(Opt HS-PDSCH is dynamically set between "Code Min Number for HS-PDSCH" and "Code Max Number for ional) HS-PDSCH", based on the idle state of the code tree. When the non-H services need more code resources, the non-H service will gradually occupy the codes used by the HS-PDSCH. The number of codes (SF=16 continuous codes) the HS-DPSCH reserved is not less than the value of "Code Min Number for HS-PDSCH". GUI Value Range: 1~15 Actual Value Range: 1~15 Default Value: 1
HsScchCodeNum BSC6900
ADD Meaning: This parameter decides the maximum UCELLHSDPA(Opt number of subscribers that the NodeB can schedule ional) in a TTI period. For detailed information of this parameter, refer to 3GPP TS 25.308. MOD UCELLHSDPA(Opt GUI Value Range: 1~15 ional) Actual Value Range: 1~15 Default Value: 4
Issue 03 (2011-10-30)
6-4
WCDMA RAN HSDPA
6 Parameters
Parameter ID HspaPower
NE BSC6900
MML Command
Description
ADD Meaning: This parameter specifies the offset UCELLHSDPA(Opt between the total HSPA power and the maximum ional) transmission power of a cell. The total HSPA power is the maximum value of HSPA dynamical power can MOD UCELLHSDPA(Opt be adjusted. For details about this parameter, refer to 3GPP TS 25.308. ional) GUI Value Range: -500~0 Actual Value Range: -50~0 Default Value: 0
MAXEFACHHAR NodeB QRT
SET MACHSPARA Meaning: Indicates the MAX HARQ Retransmission Times of E_FACH user. GUI Value Range: 0~10 Actual Value Range: 0~10 Default Value: 2
MAXNONCONVE NodeB RHARQRT
SET MACHSPARA Meaning: Indicates the MAX HARQ Retransmission Times of Non-Conversational service in CELL DCH state. GUI Value Range: 0~10 Actual Value Range: 0~10 Default Value: 4
MXPWRPHUSR NodeB
SET MACHSPARA Meaning: Indicates the Max Power Per Hs-user. GUI Value Range: 1~100 Actual Value Range: 1~100 Default Value: 100
PWRMGN
NodeB
SET MACHSPARA Meaning: Indicates the Power Margin Ratio. GUI Value Range: 0~100 Actual Value Range: 0~100 Default Value: 5
RSCALLOCM
NodeB
SET MACHSPARA Meaning: Indicates the Resource Allocate Method. GUI Value Range: CODE_PRI(Code Priority), POWER_PRI(Power Priority), POWERCODE_BAL(Balance between Code and Power) Actual Value Range: CODE_PRI, POWER_PRI, POWERCODE_BAL Default Value: CODE_PRI(Code Priority)
RSCLMSW
NodeB
SET MACHSPARA Meaning: Indicates the Resource Limiting Switch. GUI Value Range: OPEN(open), CLOSE(close) Actual Value Range: OPEN, CLOSE Default Value: OPEN(open)
Issue 03 (2011-10-30)
6-5
WCDMA RAN HSDPA
6 Parameters
Parameter ID RsvdPara1
NE BSC6900
MML Command
Description
ADD Meaning: The algorithms with the above values UCELLALGOSWIT represent are as follow: CH(Optional) RSVDBIT1~RSVDBIT16:Reserved Switch. MOD GUI Value Range: RSVDBIT1(Reserved Switch 1), UCELLALGOSWIT RSVDBIT2(Reserved Switch 2), CH(Optional) RSVDBIT3(Reserved Switch 3), RSVDBIT4(Reserved Switch 4), RSVDBIT5(Reserved Switch 5), RSVDBIT6(Reserved Switch 6), RSVDBIT7(Reserved Switch 7), RSVDBIT8(Reserved Switch 8), RSVDBIT9(Reserved Switch 9), RSVDBIT10(Reserved Switch 10), RSVDBIT11(Reserved Switch 11), RSVDBIT12(Reserved Switch 12), RSVDBIT13(Reserved Switch 13), RSVDBIT14(Reserved Switch 14), RSVDBIT15(Reserved Switch 15), RSVDBIT16(Reserved Switch 16) Actual Value Range: RSVDBIT1, RSVDBIT2, RSVDBIT3, RSVDBIT4, RSVDBIT5, RSVDBIT6, RSVDBIT7, RSVDBIT8, RSVDBIT9, RSVDBIT10, RSVDBIT11, RSVDBIT12, RSVDBIT13, RSVDBIT14, RSVDBIT15, RSVDBIT16 Default Value: None
SM
NodeB
SET MACHSPARA Meaning: Indicates the HSDPA Scheduling Method. GUI Value Range: EPF(Enhanced PF), PF(PF), RR(Round Robin), MAXCI(Max C/I) Actual Value Range: EPF, PF, RR, MAXCI Default Value: EPF(Enhanced PF)
SPI
BSC6900
SET Meaning: Scheduling priority of interactive and USPIWEIGHT(Man background services. Value 11 indicates the highest datory) priority, while value 2 indicates the lowest priority. Values 0, 1, 12, 13, 14, and 15 are reserved for the other services. GUI Value Range: 0~15 Actual Value Range: 0~15 Default Value: None
Issue 03 (2011-10-30)
6-6
WCDMA RAN HSDPA
6 Parameters
Parameter ID SpiWeight
NE BSC6900
MML Command
Description
SET Meaning: Specifies the weight for service scheduling USPIWEIGHT(Opti priority. This weight is used in two algorithms. In onal) scheduling algorithm, it is used to adjust the handling priority for different services. In Iub congestion algorithm, it is used to allocate bandwidth for different services. If the weight is higher, it is more possible to increase the handling priority of the user or get more Iub bandwidth, respectively. GUI Value Range: 1~100 Actual Value Range: 1~100 Default Value: 100
Issue 03 (2011-10-30)
6-7
WCDMA RAN HSDPA
7 Counters
7 Counters
Table 7-1 Counter description Counter Counter Name ID 50331654 VS.AckTotal Counter Description Total number of ACKs received Feature ID Feature Name WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF) WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF)
50331655 VS.NackTotal
Total number of NACKs received
50331656 VS.DtxTotal
Total number of TTIs when the NodeB cannot translate the acknowledgment information from the UE Number of ACKs received after 1st transmission Number of ACKs received after 1st retransmission Number of ACKs received after 2nd retransmission Number of ACKs received after 3rd retransmission Number of ACKs received after 4th retransmission Number of ACKs received after 5th retransmission Number of ACKs received after 6th retransmission Number of ACKs received after 7th retransmission Number of ACKs received after 8th retransmission Number of ACKs received after 9th retransmission
50331657 VS.AckFirst
50331658 VS.AckRetrans.1
Issue 03 (2011-10-30)
7-1
WCDMA RAN HSDPA
7 Counters
Counter Counter Name ID
Counter Description
Feature ID Feature Name WRFD-010 HSDPA H-ARQ & 61009 Scheduling (MAX C/I, RR and PF)
50331667 VS.AckRetrans.10 Number of ACKs received after 10th retransmission 50331668 VS.AckRemain
Number of times the NodeB does not WRFD-010 HSDPA H-ARQ & receive the ACK from the UE after the last 61009 Scheduling (MAX retransmission C/I, RR and PF) WRFD-010 HSDPA 610 Introduction Package WRFD-010 61009 HSDPA H-ARQ & Scheduling (MAX C/I, RR and PF)
50331724 VS.HSDPA.All.Sch Total number of times all the users are eduledNum scheduled in a cell
50332724 VS.IUB.FlowCtrol.D IUB logic port_1 maximum DL HSDPA L.AdjBW.LgcPort1. available bandwidth Max 50332725 VS.IUB.FlowCtrol.D IUB logic port_1 minimum DL HSDPA L.AdjBW.LgcPort1. available bandwidth Min 50332726 VS.IUB.FlowCtrol.D IUB logic port_1 average DL HSDPA L.AdjBW.LgcPort1. available bandwidth Avg 50332728 VS.IUB.FlowCtrol.D IUB logic port_1 DL HSDPA available L.Delay.UpBW.Nu bandwidth increase times after jitter m.LgcPort1 congestion released
WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control
50332729 VS.IUB.FlowCtrol.D IUB logic port_1 DL HSDPA available WRFD-010 HSDPA Flow Control L.Drop.UpBW.Num. bandwidth increase times after packet loss 61010 LgcPort1 congestion released 50332731 VS.IUB.FlowCtrol.D IUB logic port_1 DL HSDPA available L.DelayCong.Down bandwidth decrease times for jitter BWNum.LgcPort1 congestion WRFD-010 HSDPA Flow 61010 Control
50332733 VS.IUB.FlowCtrol.D IUB logic port_1 DL HSDPA available WRFD-010 HSDPA Flow Control L.DropCong.DownB bandwidth decrease times for packet loss 61010 WNum.LgcPort1 congestion 50332735 VS.IUB.FlowCtrol.D IUB logic port_1 Number of DL HSDPA L.ReceiveNum.Lgc frames IUB logic port received Port1 50332737 VS.IUB.FlowCtrol.D IUB logic port_1 Number of lost DL L.DropNum.LgcPort HSDPA frames 1 WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control
Issue 03 (2011-10-30)
7-2
WCDMA RAN HSDPA
7 Counters
Counter Description
Feature ID Feature Name WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control
50332741 VS.IUB.FlowCtrol.D IUB logic port_1 maximum DL HSDPA L.DelayVara.LgcPo delay jitter rt1.Max 50332742 VS.IUB.FlowCtrol.D IUB logic port_1 minimum DL HSDPA L.DelayVara.LgcPo delay jitter rt1.Min
50332743 VS.IUB.FlowCtrol.D IUB logic port_1 average DL HSDPA delay WRFD-010 HSDPA Flow 61010 Control L.DelayVara.LgcPo jitter rt1.Avg 50332745 VS.IUB.FlowCtrol.D IUB logic port_1 DL HSDPA congestion L.CongTime.LgcPor duration t1 50332749 VS.IUB.FlowCtrol.D IUB logic port_2 maximum DL HSDPA L.AdjBW.LgcPort2. available bandwidth Max 50332750 VS.IUB.FlowCtrol.D IUB logic port_2 minimum DL HSDPA L.AdjBW.LgcPort2. available bandwidth Min 50332751 VS.IUB.FlowCtrol.D IUB logic port_2 average DL HSDPA L.AdjBW.LgcPort2. available bandwidth Avg 50332753 VS.IUB.FlowCtrol.D IUB logic port_2 DL HSDPA available L.Delay.UpBW.Nu bandwidth increase times after jitter m.LgcPort2 congestion released WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control
50332754 VS.IUB.FlowCtrol.D IUB logic port_2 DL HSDPA available WRFD-010 HSDPA Flow Control L.Drop.UpBW.Num. bandwidth increase times after packet loss 61010 LgcPort2 congestion released 50332756 VS.IUB.FlowCtrol.D IUB logic port_2 DL HSDPA available L.DelayCong.Down bandwidth decrease times for jitter BWNum.LgcPort2 congestion WRFD-010 HSDPA Flow 61010 Control
50332758 VS.IUB.FlowCtrol.D IUB logic port_2 DL HSDPA available WRFD-010 HSDPA Flow Control L.DropCong.DownB bandwidth decrease times for packet loss 61010 WNum.LgcPort2 congestion 50332760 VS.IUB.FlowCtrol.D IUB logic port_2 Number of DL HSDPA L.ReceiveNum.Lgc frames IUB logic port received Port2 50332762 VS.IUB.FlowCtrol.D IUB logic port_2 Number of lost DL L.DropNum.LgcPort HSDPA frames 2 50332766 VS.IUB.FlowCtrol.D IUB logic port_2 maximum DL HSDPA L.DelayVara.LgcPo delay jitter rt2.Max WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control WRFD-010 HSDPA Flow 61010 Control
Issue 03 (2011-10-30)
7-3
WCDMA RAN HSDPA
7 Counters
Counter Description
Feature ID Feature Name WRFD-010 HSDPA Flow 61010 Control
50332767 VS.IUB.FlowCtrol.D IUB logic port_2 minimum DL HSDPA L.DelayVara.LgcPo delay jitter rt2.Min
50332768 VS.IUB.FlowCtrol.D IUB logic port_2 average DL HSDPA delay WRFD-010 HSDPA Flow 61010 Control L.DelayVara.LgcPo jitter rt2.Avg 50332770 VS.IUB.FlowCtrol.D IUB logic port_2 DL HSDPA congestion L.CongTime.LgcPor duration t2 50341648 VS.ScchCodeUtil.M Average usage of HS-SCCH code ean resources in a cell WRFD-010 HSDPA Flow 61010 Control WRFD-010 15 Codes per Cell 61001 Time and WRFD-010 HS-PDSCH 61018 Codes Multiplex WRFD-010 HSDPA Static 61005 Code Allocation and RNC-Controlled WRFD-010 Dynamic Code 631 Allocation Dynamic Code Allocation Based on NodeB 50341649 VS.ScchCodeUtil.M Maximum usage of HS-SCCH code ax resources in a cell WRFD-010 15 Codes per Cell 61001 Time and WRFD-010 HS-PDSCH 61018 Codes Multiplex WRFD-010 HSDPA Static 61005 Code Allocation and RNC-Controlled WRFD-010 Dynamic Code 631 Allocation Dynamic Code Allocation Based on NodeB
Issue 03 (2011-10-30)
7-4
WCDMA RAN HSDPA
7 Counters
Counter Description
Feature ID Feature Name WRFD-010 15 Codes per Cell 61001 Time and WRFD-010 HS-PDSCH 61018 Codes Multiplex WRFD-010 HSDPA Static 61005 Code Allocation and RNC-Controlled WRFD-010 Dynamic Code 631 Allocation Dynamic Code Allocation Based on NodeB
50341650 VS.ScchCodeUtil.M Minimum usage of HS-SCCH code in resources in a cell
50341651 VS.PdschCodeUtil. Average usage of HS-PDSCH code Mean resources in a cell
WRFD-010 15 Codes per Cell 61001 Time and WRFD-010 HS-PDSCH 61018 Codes Multiplex WRFD-010 HSDPA Static 61005 Code Allocation and RNC-Controlled WRFD-010 Dynamic Code 631 Allocation Dynamic Code Allocation Based on NodeB
Issue 03 (2011-10-30)
7-5
WCDMA RAN HSDPA
7 Counters
Counter Description
50341652 VS.PdschCodeUtil. Maximum usage of HS-PDSCH code Max resources in a cell
50341653 VS.PdschCodeUtil. Minimum usage of HS-PDSCH code Min resources in a cell
WRFD-010 15 Codes per Cell 61001 Time and WRFD-010 HS-PDSCH 61018 Codes Multiplex WRFD-010 HSDPA Static 61005 Code Allocation and RNC-Controlled WRFD-010 Dynamic Code 631 Allocation Dynamic Code Allocation Based on NodeB
Issue 03 (2011-10-30)
7-6
WCDMA RAN HSDPA
7 Counters
Counter Description
50341654 VS.ScchCodeUtil.M Average usage of HS-SCCH code ean.User resources when HSDPA users camp on the cell
50341655 VS.ScchCodeUtil.M Average usage of HS-SCCH code WRFD-010 15 Codes per Cell ean.Data resources when at least one HSDPA user 61001 has data to transmit in the queue buffer Time and WRFD-010 HS-PDSCH 61018 Codes Multiplex WRFD-010 HSDPA Static 61005 Code Allocation and RNC-Controlled WRFD-010 Dynamic Code 631 Allocation Dynamic Code Allocation Based on NodeB
Issue 03 (2011-10-30)
7-7
WCDMA RAN HSDPA
7 Counters
Counter Description
50341656 VS.PdschCodeUtil. Average usage of HS-PDSCH code Mean.User resources when HSDPA users camp on the cell
50341657 VS.PdschCodeUtil. Average usage of HS-PDSCH code WRFD-010 15 Codes per Cell Mean.Data resources when at least one HSDPA user 61001 has data to transmit in the queue buffer Time and WRFD-010 HS-PDSCH 61018 Codes Multiplex WRFD-010 HSDPA Static 61005 Code Allocation and RNC-Controlled WRFD-010 Dynamic Code 631 Allocation Dynamic Code Allocation Based on NodeB 50341668 VS.DataOutput.Me Average cell throughput at the an MAC-hs/MAC-ehs layer 50341669 VS.DataOutput.Max Maximum cell throughput at the MAC-hs/MAC-ehs layer 50341670 VS.DataOutput.Min Minimum cell throughput at the MAC-hs/MAC-ehs layer 50341671 VS.DataOutput.Use Average cell throughput when HSDPA r users camp on the cell WRFD-010 HSDPA 611 Enhanced Package WRFD-010 HSDPA 611 Enhanced Package WRFD-010 HSDPA 611 Enhanced Package WRFD-010 HSDPA 611 Enhanced Package
Issue 03 (2011-10-30)
7-8
WCDMA RAN HSDPA
7 Counters
Counter Description
Feature ID Feature Name
50341672 VS.DataOutput.Use Average cell throughput when at least one WRFD-010 HSDPA rData HSDPA user has data to transmit in the 611 Enhanced queue buffer Package 50341673 VS.DataOutput.Rab Average throughput of each RAB when HSDPA users camp on the cell WRFD-010 HSDPA 611 Enhanced Package
50341674 VS.DataOutput.Rab Average throughput of each RAB when at WRFD-010 HSDPA Data 611 least one HSDPA user has data to Enhanced transmit in the queue buffer Package 50341685 VS.DataDiscardRati Average ratio of discarded HSDPA data o.Mean due to timer expiry WRFD-010 HSDPA 610 Introduction Package WRFD-010 61009 HSDPA H-ARQ & Scheduling (MAX C/I, RR and PF) 50341686 VS.DataDiscardRati Maximum ratio of discarded HSDPA data WRFD-010 HSDPA o.Max due to timer expiry 610 Introduction Package WRFD-010 61009 HSDPA H-ARQ & Scheduling (MAX C/I, RR and PF) 50341687 VS.DataDiscardRati Minimum ratio of discarded HSDPA data WRFD-010 HSDPA o.Min due to timer expiry 610 Introduction Package WRFD-010 61009 HSDPA H-ARQ & Scheduling (MAX C/I, RR and PF) 67190698 VS.HSDPA.SHO.S Number of Intra-RNC HSDPA Serving Cell WRFD-010 HSDPA Mobility ervCellChg.AttOut Change Attempts for Cell 61006 Management 67190699 VS.HSDPA.SHO.S Number of Intra-RNC HSDPA Serving Cell WRFD-010 HSDPA Mobility 61006 Management ervCellChg.SuccOu Change Success in RNC for Cell t 67190700 VS.HSDPA.HHO.H Number of Intra-RNC HSDPA Service 2H.AttOutIntraFreq Intra-Frequency HHO Attempts Without Channel Change for Cell WRFD-010 HSDPA Mobility 61006 Management
67190701 VS.HSDPA.HHO.H Number of Successful Intra-Frequency WRFD-010 HSDPA Mobility Management 2H.SuccOutIntraFre HSDPA Hard Handovers Without Channel 61006 q Change for Cell
Issue 03 (2011-10-30)
7-9
WCDMA RAN HSDPA
7 Counters
Counter Description
Feature ID Feature Name
67190702 VS.HSDPA.HHO.H Number of Inter-Frequency HSDPA Hard WRFD-010 HSDPA Mobility 2H.AttOutInterFreq Handover Attempts Without Channel 61006 Management Change for Cell 67190703 VS.HSDPA.HHO.H Number of Successful Inter-Frequency WRFD-010 HSDPA Mobility Management 2H.SuccOutInterFre HSDPA Hard Handovers Without Channel 61006 q Change for Cell 67190708 VS.HSDPA.HHO.N Number of HSDSCH-to-HSDSCH hard oChR.Att.NCell Handover Requests Without Channel Change Between Neighboring Cells 67190709 VS.HSDPA.HHO.N Number of Successful oChR.Succ.NCell HSDSCH-to-HSDSCH hard Handovers Without Channel Change Between Neighboring Cells 67190710 VS.HSDPA.ServCel Number of HSDPA Serving Cell Change lChg.Att.NCell Attempts Between Neighboring Cells WRFD-010 HSDPA Mobility 61006 Management WRFD-010 HSDPA Mobility 61006 Management
WRFD-010 HSDPA Mobility 61006 Management
67190711 VS.HSDPA.ServCel Number of Successful HSDPA Serving WRFD-010 HSDPA Mobility lChg.Succ.NCell Cell Changes Between Neighboring Cells 61006 Management 67191155 VS.IRATHO.HSDP Number of PS Inter-RAT Outgoing A.AttOutPSUTRAN Handover Attempts for HSDPA Services for Cell WRFD-010 HSDPA Mobility 61006 Management
67191156 VS.IRATHO.HSDP Number of Successful PS Outgoing WRFD-010 HSDPA Mobility Management A.SuccOutPSUTRA Inter-RAT Handovers for HSDPA Services 61006 N for Cell 67191157 VS.HSDPA.HHO.H Number of Intra-Frequency H2D Hard 2D.AttOutIntraFreq Handover Attempts for Cell 67191158 VS.HSDPA.HHO.H Number of Successful Intra-Frequency 2D.SuccOutIntraFre H2D Hard Handovers for Cell q 67191159 VS.HSDPA.HHO.H Number of Inter-Frequency H2D Hard 2D.AttOutInterFreq Handover Attempts for Cell 67191160 VS.HSDPA.HHO.H Number of Successful Inter-Frequency 2D.SuccOutInterFre H2D Hard Handovers for Cell q 67193578 VS.HSDPA.UE.Max Maximum Number of HSDPA UEs with .CAT1.6 Category 1-6 in a Cell 67193581 VS.HSDPA.UE.Max Maximum Number of HSDPA UEs with .CAT7.10 Category 7-10 in a Cell 67193584 VS.HSDPA.UE.Max Maximum Number of HSDPA UEs with .CAT11.12 Category 11-12 in a Cell 67193587 VS.HSDPA.UE.Max Maximum Number of HSDPA UEs with .CAT13.14 Category 13-14 in a Cell WRFD-010 HSDPA Mobility 61006 Management WRFD-010 HSDPA Mobility 61006 Management WRFD-010 HSDPA Mobility 61006 Management WRFD-010 HSDPA Mobility 61006 Management WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28
Issue 03 (2011-10-30)
7-10
WCDMA RAN HSDPA
7 Counters
Counter Description
Feature ID Feature Name WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28
67193590 VS.HSDPA.UE.Max Maximum Number of HSDPA UEs with .CAT15.16 Category 15-16 in a Cell 67193593 VS.HSDPA.UE.Max Maximum Number of HSDPA UEs with .CAT17.20 Category 17-20 in a Cell 67193596 VS.HSDPA.UE.Max Maximum Number of HSDPA UEs with .CAT21.24 Category 21-24 in a Cell
67195481 VS.HSDPA.SHO.S Number of Inter-RNC HSDPA Serving Cell WRFD-010 HSDPA Mobility 61006 Management ervCellChg.AttOutIu Change Attempts for Cell r 67195482 VS.HSDPA.SHO.S Number of Inter-RNC HSDPA Serving Cell WRFD-010 HSDPA Mobility 61006 Management ervCellChg.SuccOu Change Success for Cell tIur 67195483 VS.HSDPA.HHO.H Number of Inter-RNC HSDPA Hard 2H.AttOutIur Handover Attempts Without Channel Change for Cell WRFD-010 HSDPA Mobility 61006 Management
67195484 VS.HSDPA.HHO.H Number of Successful Inter-RNC HSDPA WRFD-010 HSDPA Mobility 2H.SuccOutIur Management Hard Handovers Without Channel Change 61006 for Cell 67202932 VS.HSDPA.UE.Me Average Number of HSDPA UEs in a Cell WRFD-010 16 HSDPA Users an.Cell 61016 per Cell WRFD-010 32 HSDPA Users 622 per Cell WRFD-010 64 HSDPA Users 623 per Cell 67202941 VS.HSDPA.MACD. Average Number of MAC-d Flows in a Cell WRFD-010 16 HSDPA Users Mean.Cell 61016 per Cell WRFD-010 32 HSDPA Users 622 per Cell WRFD-010 64 HSDPA Users 623 per Cell 67204259 VS.HSDPA.UE.Me Average Number of HSDPA UEs with an.CAT1.6 Category 1-6 in a Cell 67204260 VS.HSDPA.UE.Me Average Number of HSDPA UEs with an.CAT7.10 Category 7-10 in a Cell 67204261 VS.HSDPA.UE.Me Average Number of HSDPA UEs with an.CAT11.12 Category 11-12 in a Cell 67204262 VS.HSDPA.UE.Me Average Number of HSDPA UEs with an.CAT13.14 Category 13-14 in a Cell 67204263 VS.HSDPA.UE.Me Average Number of HSDPA UEs with an.CAT15.16 Category 15-16 in a Cell WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28
Issue 03 (2011-10-30)
7-11
WCDMA RAN HSDPA
7 Counters
Counter Description
Feature ID Feature Name WRFD-010 HSDPA UE 61002 Category 1 to 28 WRFD-010 HSDPA UE 61002 Category 1 to 28
67204264 VS.HSDPA.UE.Me Average Number of HSDPA UEs with an.CAT17.20 Category 17-20 in a Cell 67204265 VS.HSDPA.UE.Me Average Number of HSDPA UEs with an.CAT21.24 Category 21-24 in a Cell
73403764 VS.HSDPA.HHO.H number of Inter-RNC H2D Hard Handover WRFD-010 HSDPA Mobility 2D.AttOutIur Attempts for Cell 61006 Management 73403765 VS.HSDPA.HHO.H Number of Successful inter-RNC Hard 2D.SuccOutIur Handovers from HSDPA to DCH for Cell WRFD-010 HSDPA Mobility 61006 Management
Issue 03 (2011-10-30)
7-12
WCDMA RAN HSDPA
8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 03 (2011-10-30)
8-1
WCDMA RAN HSDPA
9 Reference Documents
9 Reference Documents
[1] 3GPP TS 25.214, "Physical layer procedures (FDD)" [2] 3GPP TS 25.306, "UE Radio Access capabilities" [3] 3GPP TS 25.308, "UTRA High Speed Downlink Packet Access (HSDPA); Overall description" [4] 3GPP TS 25.433, "UTRAN Iub interface NBAP signaling" [5] 3GPP TS 25.435, "UTRAN Iub interface user plane protocols for CCH data flows" [6] Transmission Resource Management Feature Parameter Description [7] Load Control Feature Parameter Description [8] Directed Retry Decision Feature Parameter Description [9] Radio Bearers Feature Parameter Description [10] State Transition Feature Parameter Description [11] Power Control Feature Parameter Description [12] Handover Feature Parameter Description
Issue 03 (2011-10-30)
9-1

Hsdpa (Ran13.0 03)

Cargado por

Información del documento

Descripción original:

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Hsdpa (Ran13.0 03)

Cargado por

Copyright:

Formatos disponibles

HSDPA RAN13.

Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

WCDMA RAN HSDPA

2 Overview of HSDPA ..................................................................................................................2-1

3 Control Plane .............................................................................................................................3-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

5 QoS and Diff-Serv Management ...........................................................................................5-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

1.2 Intended Audience

1.3 Change History

03 (2011-10-30) 02 (2011-06-30) 01 (2011-04-30) Draft B (2011-03-30) Draft A (2010-12-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

2.2 HSDPA Channels

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

Figure 2-1 Physical channels of HSDPA

2.2.1 HS-DSCH and HS-PDSCH

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

2.2.4 DPCCH and DPCH/F-DPCH

2.3 Impact of HSDPA on NEs

2.4 HSDPA Functions

2.4.1 HSDPA Control Plane Functions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

Figure 2-2 HSDPA control plane functions

The HSDPA control plane functions are described as follows:

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

2.4.2 HSDPA User Plane Functions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

3.1 Bearer Mapping

WCDMA RAN HSDPA

3.2 Access Control

3.3 Mobility Management

3.4 Channel Switching

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

Figure 3-1 UE state transition (WRFD-01061111 HSDPA State Transition)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

Figure 3-2 Relationships between channel switching and other functions

3.5 Load Control

WCDMA RAN HSDPA

3.6 Power Resource Management

3.7 Code Resource Management

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN HSDPA

3.7.1 HS-SCCH Code Resource Management

3.7.2 HS-PDSCH Code Resource Management

If the NodeB-Controlled Dynamic Code Allocation is used:

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd