HSUPA(RAN13.0_05)

HSUPA RAN13.0

Feature Parameter Description

Issue

05

Date

2012-11-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. 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:

http://www.huawei.com

Email:

[email protected]

Copyright © Huawei Technologies Co., Ltd. 2012. 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:

http://www.huawei.com

Email:

[email protected]

WCDMA RAN HSUPA

Contents

Contents .................................................................. ............................................ ............................................ ........................................ ..................1-1 1 Introduction ............................................

1.1 Scope ............................................................................................................................................ ............................................................................................................................................ 1-1 1.2 Intended I ntended Audience......................................................................................................................... Audience......................................................................................................................... 1-1 1.3 Change History ............................................................... .............................................................................................................................. ............................................................... 1-1

2 Overview of HSUPA............................................. ................................................................... ............................................ ............................................. ......................... ..2-1 2.1 Main Characteristics ................................................................... ...................................................................................................................... ................................................... 2-1 2.2 HSUPA Channels .......................................................................................................................... .......................................................................................................................... 2-1 2.3 Im pact of HSUPA HSUPA on NEs .......................................................... .............................................................................................................. .................................................... 2-2 2.4 HSUPA Functions ........................................................................................................... .......................................................................................................................... ............... 2-3 2.4.1 HSUPA Control Plane Functions .......................................................................................... .......................................................................................... 2-3 2.4.2 HSUPA User Plane Functions F unctions .............................................................................................. .............................................................................................. 2-5 ................................................................. ............................................ ........................................ ..................3-1 3 Control Plane Functions ...........................................

3.1 Bearer Mapping .............................................................. ............................................................................................................................. ............................................................... 3-1 3.2 Channel Switching...................................................................... Switching......................................................................................................................... ................................................... 3-1 3.2.1 State Transition Based Base d on Traffic Volume ........................................................... ............................................................................. .................. 3-2 3.2.2 Channel Switching Based on UE Moving ........................................................... ............................................................................. .................. 3-3 3.2.3 Channel Switching Based on Load Change ..................................................................... ......................................................................... .... 3-3

4 User Plane Functions ............................................ ................................................................... ............................................. ........................................... .....................4-1 4.1 Fast Scheduling..................................................................................... Scheduling............................................................................................................................. ........................................ 4-1 4.1.1 Overview ................................................................. ............................................................................................................................... .............................................................. 4-1 4.1.2 Estimation of Remaining Rem aining Uu Load ........................................................... ........................................................................................ ............................. 4-2 4.1.3 Queuing ................................................................................................................................ ................................................................................................................................ 4-3 4.1.4 Uu resource r esource allocation .................................................................. .......................................................................................................... ........................................ 4-4 4.2 CE C E Resource Management ................................................................... ........................................................................................................... ........................................ 4-4 4.2.1 Overview ................................................................. ............................................................................................................................... .............................................................. 4-4 4.2.2 CE Sharing ........................................................................................................................... ........................................................................................................................... 4-5 4.2.3 CE Consumption an d Admission. ............................................................ ......................................................................................... ............................. 4-5 4.2.4 Dynamic CE Management.................................................................................................... 4-5 4.3 Uplink Macro Diversity Intelligent Receiving ................................................................................. ................................................................................. 4-9 4.3.1 Background Back ground ...................................................................................................................... .......................................................................................................................... .... 4-9 4.3.2 Function Implementation ...................................................................................................... ...................................................................................................... 4-9 4.4 HSUPA Adaptive Retransmission .......................................................... ................................................................................................ ...................................... 4-10 4.4.1 Background ........................................................... ........................................................................................................................ ............................................................. 4-10 4.4.2 Function Implementation .................................................................................................... .................................................................................................... 4-11 ............................................................... ............................................ ........................................ ..................4-1 5 HSUPA QoS Management .........................................

5.1 QoS Qo S Guarantee ............................................................................................................................. ............................................................................................................................. 4-1 5.2 Diff-Serv Management .................................................................................................................. .................................................................................................................. 4-2

6 Impact on the Network........................................... .................................................................. ............................................. ........................................... .....................4-1 Issue 05 (2012-11-30)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

ii

WCDMA RAN HSUPA

Contents

6.1 WRFD-020136 Anti-Interference Scheduling for HSUPA HSUPA ............................................................. 4-1 4-1 6.2 WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation .................... 4-1

7 Engineering Guidelines......................................... ............................................................... ............................................. ............................................ .....................4-2 7.1 HSUPA H SUPA Anti-interference Scheduling ............................................................................................ ............................................................................................ 4-2 7.1.1 When W hen to Use Anti-Interfer ence Scheduling for HSUPA ........................................................ 4-2 7.1.2 Inform ation to Be Collected .................................................................................................. .................................................................................................. 4-2 7.1.3 Overall Deployment Procedure ............................................................................................ 4-3 7.1.4 Feature Deployment ................................................................................ ............................................................................................................. ............................. 4-4 7.1.5 Feature Monitoring ............................................................................................................... ............................................................................................................... 4-4 7.2 Dual-Threshold Scheduling with HSUPA Interference Cancellation ............................................. 4-4 7.2.1 When to Use Dual-Threshold Scheduling with HSUPA Interference Cancellation .............. 4-4 7.2.2 Inform ation to Be Collected .................................................................................................. .................................................................................................. 4-4 7.2.3 Feature Deployment ................................................................................ ............................................................................................................. ............................. 4-5 7.2.4 Feature Monitoring ............................................................................................................... ............................................................................................................... 4-5 7.2.5 Troubleshooting .................................................................................................................... .................................................................................................................... 4-6 ................................................................. ............................................. ............................................ ........................................... .....................4-1 8 Parameters.......................................... ................................................................. ............................................ ............................................ ............................................. ......................... ..4-1 9 Counters ........................................... ................................................................... ............................................. ............................................ ........................................... .....................4-1 10 Glossary ............................................ ............................................................... ............................................. ............................................ .....................4-1 11 Reference Documents .........................................

Issue 05 (2012-11-30)


iii

WCDMA RAN HSUPA

1 Introduction 1.1 Scope HSUPA is an important feature of 3GPP Release 6. As an uplink high speed data transmission solution, HSUPA provides a theoretical maximum rate of 5.74 Mbit/s on the Uu interface.

1.2 Intended Audience This document is intended for: 

Personnel who are familiar with W CDMA basics



Personnel who need to understand HSUPA



Personnel who work with Huawei products

1.3 Change History This section provides information about the changes in different document versions. There are two types of changes, which are defined as follows: 

Feature change: refers to a change in the HSUPA feature of a specific product version.



Editorial change: refers to a change in wording or the addition of information that was not described in the earlier version.

Document Issues The document issues are as follows: 

05 (2012-11-30)



04 (2012-05-30)



03 (2011-10-30)



02 (2011-06-30)



01 (2011-04-30)



Draft B (2011-03-30)



Draft A (2010-12-30)

05 (2012-11-30) This is the document for the fifth commercial release of RAN13.0. Compared with issue 04 (2012-05-30) of RAN13.0, this issue incorporates the changes described in the following table. Change Type

Change Description

Parameter Change

Feature change

None.

None.

Editorial change

Added descriptions about the counters related to None. HSUPA Anti-interference Scheduling and Dual-Threshold Scheduling with HSUPA Interference Cancellation. For details, see sections 7.1.2 "Information to Be Collected" and 7.2.2 "Information to Be Collected." Collected."

Issue 05 (2012-11-30)


1-1

WCDMA RAN HSUPA

04 (2012-05-30) This is the document for the fourth commercial release of RAN13.0. Compared with issue 03 (2011-10-30) of RAN13.0, this issue has the following changes. Change Type

Change Description

Parameter Change

Feature change

None.

None.

Editorial change

Added chapter 6 "Impact on the Network."

None.

Optimized the engineering guideline. For details, see chapter 7 "Engineering Guidelines."

None.

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 description about HSUPA adaptive retransmission. For details, see section 4.4 "HSUPA Adaptive Retransmission."

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 has the following changes. Change Type

Change Description

Parameter Change

Feature change

None.

None.

Editorial change

Added engineering guidelines for Dual-Threshold Scheduling with HSUPA Interference Cancellation. For details, see section 7.2 "Dual-Threshold Scheduling with HSUPA Interference Cancellation."

None.

Added the network impact about HSUPA. For None. details, see chapter 2 "Overview of HSUPA." Added the network impact about dynamic CE None. resource management. For details, see section 4.2.4 "Dynamic CE Management."

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 has no change.

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 adds the engineering guidelines about HSUPA anti-interference scheduling. For details, see section 7.1 "HSUPA Anti-interference Scheduling."

Issue 05 (2012-11-30)


1-2

WCDMA RAN HSUPA

Draft A (2010-12-30) This is the draft of the document for RAN13.0. Compared with issue 03 (2010-12-20) of RAN12.0, this issue adds the information about anti-interference scheduling and dual-threshold scheduling.

Issue 05 (2012-11-30)


1-3

WCDMA RAN HSUPA

2 Overview of HSUPA

2 Overview of HSUPA Since the introduction of the HSDPA technology, the downlink transmission rate has been greatly increased. To meet the rapidly growing demands for data services, 3GPP Release 6 introduced HSUPA. By applying fast scheduling, fast hybrid automatic repeat request (HARQ), shorter transmission time interval (TTI), and macro diversity combining (MDC), HSUPA improves the uplink capacity, increases the user data rate greatly, and reduces the transmission delay on the WCDMA network. HSUPA provides a higher peak rate, which helps to improve user experience. It can also increase system capacity when there is only a small number of UEs transmitting data at high data rates. This feature has the following impacts: 



A new control channel that requires more power in the uplink, called E-DPCCH, was introduced for HSUPA. Therefore, activating this feature may increase the probability of call drops in a network with limited uplink coverage. When the uplink load is limited and there is a large number of UEs, the UEs can upload data only at a guaranteed bit rate (GBR), for example, 64 kbit/s. In such a case, the data transmission efficiency of HSUPA channels is slightly decreased, as compared to R99 channels, because the E-DPCCH consumes system resources.

2.1 Main Characteristics The main characteristics of HSUPA are as follows: Fast Scheduling

In HSUPA, fast scheduling is used to allocate system resources in the NodeB through signaling at the physical layer. By exploiting the burst transmission, the scheduler performs rapid resource allocation between UEs to adapt to cell interference variations. The scheduler also can provide Diff-Serv management for users with different priorities. This improves user experience and increases the system capacity.

Fast HARQ

Similar to HSDPA, HSUPA also introduces fast HARQ, which allows the NodeB to rapidly request retransmission of erroneously received data. HARQ reduces the number of retransmissions at the RLC layer and shortens the transmission delay. The NodeB performs soft combining of data erroneously received and data retransmitted from the UE before decoding. The combining uses the information transmitted each time and therefore increases the success rate of decoding.

Shorter TTI

HSUPA allows a 2 ms TTI, which further reduces the transmission delay and scheduling delay.

MDC

HSUPA supports soft handover. The cells in the active set can receive data from UEs. MDC increases the probability of proper data reception, improves the quality of data transmission, and greatly enhances the service stability of users at the cell border.

2.2 HSUPA Channels To support the HSUPA technology, 3GPP TS 25.211 defines one transport channel (E-DCH) and five physical channels (E-DPCCH, E-DPDCH, E-HICH, E-RGCH, and E-AGCH).

Issue 05 (2012-11-30)


2-1

WCDMA RAN HSUPA

2 Overview of HSUPA

Figure 2-1 HSUPA physical channels

E-AGCH: E-DCH Absolute Grant Channel E-RGCH: E-DCH Relative Grant Channel E-HICH: E-DCH HARQ Acknowledgement Indicator Channel

E-DPCCH: E-DCH Dedicated Physical Control Channel E-DPDCH: E-DCH Dedicated Physical Data Channel UE: User Equipment

The TTI of the enhanced dedicated channel (E-DCH) can be 10 ms or 2 ms. The E-DCH is mapped onto the E-DPDCH or E-DPCCH. When the TTI is 10 ms, the E-DCH provides better uplink coverage performance; when the TTI is 2 ms, the E-DCH provides higher transmission rates. The E-DPDCH carries data in the uplink. The spreading factor of the E -DPDCH varies from SF256 to SF2 depending on the data transmission rate. A maximum of four E-DPDCHs can be used for parallel transmission. The SF of two E-DPDCHs is SF2, and the SF of the other two E-DPDCHs is SF4. The E-DPCCH carries control information related to data transmission in the uplink. The control information consists of the E-DCH transport format combination indicator (E-TFCI), retransmission sequence number (RSN), and happy bit. The SF of the E-DPCCH is fixed to 256. To implement the HARQ function, the E-HICH is introduced in the downlink. The E-HICH carries retransmission requests from the NodeB. The SF of the E-HICH is fixed to 128. The downlink E-AGCH and E-RGCH carry the HSUPA scheduling control information. The E-AGCH is a shared channel, which carries the maximum permissible E-DPDCH to DPCCH power ratio, that is, absolute grants. The SF of the E-AGCH is fixed to 256. The E-RGCH is a dedicated channel, which is used to indicate relative grants and increase or decrease the maximum permissible E-DPDCH to DPCCH power ratio. The SF of the E-RGCH is fixed to 128.

2.3 Impact of HSUPA on NEs HSUPA has an impact on the RNC, NodeB, and UE. On the control plane of the network side, the RNC processes the signaling about the HSUPA-capable cell configuration, E-DCH related channel configuration, and mobility management. On the user plane of the network side, the RLC layer and MAC-d of the RNC remain unchanged. In the RNC, the MAC-es is added under the MAC-d to implement the MDC, reordering, and decapsulation of MAC-es PDUs. In the NodeB, the MAC-e is added to implement HSUPA scheduling and HARQ management.

Issue 05 (2012-11-30)


2-2

WCDMA RAN HSUPA

2 Overview of HSUPA

In the UE, the MAC-e/es is added, which encapsulates the traffic data into an MAC-e PDU and transmits it on the E-DPDCH. To support HSUPA, 3GPP TS 25.306 defines six UE categories. These UEs support different peak rates at the MAC layer, ranging from 711 kbit/s to 5.74 Mbit/s. Only the UE of category 6 supports the peak rate of 5.74 Mbit/s. E-DCH Category

Max. Capability Combination

E-DCH TTI

Max. Data Rate (Mbit/s) MAC Layer

MAC Layer

Air Interface

10 ms TTI

2 ms TTI

0.71

-

0.96

Category 1

1 x SF4

10 ms only

Category 2

2 x SF4

10 ms and 2 ms 1.45

1.40

1.92

Category 3

2 x SF4

10 ms only

-

1.92

Category 4

2 x SF2

10 ms and 2 ms 2.0

2.89

3.84

Category 5

2 x SF2

10 ms only

-

3.84

Category 6

2 x SF4 + 2 x SF2 10 ms and 2 ms 2.0

5.74

5.76

1.45

2.0

Huawei RAN supports all the UE categories. HSUPA 2 ms TTI and parallel transmission of four E-DPDCHs are optional.

2.4 HSUPA Functions In the entire process of a call, the UTRAN performs a series of function coordination tasks to provide high-quality services, completely utilize the system resources, and maximize the system capacity. The UTRAN protocols are classified into the control plane protocol and user plane protocol. Accordingly, the UTRAN functions are classified into control plane functions and user plane functions. The control plane is responsible for setting up and maintaining E-DCH connections and controlling the system load. The user plane is responsible for implementing data transmission with satisfactory quality and allocating resources properly and efficiently to maximize the system capacity. Resources can be flexibly allocated among users in real time because HSUPA resources are shared by users. This affects the QoS of users to a great extent. To solve this problem, the HSUPA QoS management strategy is adopted, which requires the support of some HSUPA functions. This document describes the HSUPA QoS management strategy.

2.4.1 HSUPA Control Plane Functions Figure 2-2 shows the HSUPA control plane functions based on the service connection setup and maintenance procedure.

Issue 05 (2012-11-30)


2-3

WCDMA RAN HSUPA

2 Overview of HSUPA

Figure 2-2 HSUPA control plane functions

The HSUPA control plane functions are described as follows: 

Bearer mapping When a user initiates a service request, bearer mapping is performed to determine an appropriate physical channel for carrying data based on the attributes of the requested service, such as the service domain (CS or PS) and the traffic class and rate. If the service attributes meet the requirement for carrying on the HSUPA channel, the data can be carried on the HSUPA channel. For details on bearer mapping, see the Radio Bearers Feature Parameter Description.



Access control After bearer mapping determines that a service can be carried on the HSUPA channel, access control performs an access decision based on the cell l oad and the estimated increase in the load after the access of a new service. Access control ensures that a new service connection can obtain required resources after admission. Accordingly, the service quality is ensured, and the cell is not overloaded. If the resources of the cell are insufficient for the service connection setup on the HSUPA channel, or if the cell does not support HSUPA, access attempts can be performed in the inter-frequency same-coverage neighboring cell to increase the access probability and improve the QoS. For details on access control, see the Load Control Feature Parameter Description. If access control determines that the service connection can be set up on the HSUPA channel, the system sets up the HSUPA RB for the UE. Therefore, the UE can transmit data on the E-DPDCH. The service connection setup ends, and the power control, channel switching, mobility management, and load control are performed to control the UE. The first three functions control the RL of each UE. The last function controls all the UEs in the cell. The four functions work simultaneously.



Power control If a service can be carried on the HSUPA channel, the UE transmits control messages and traffic data to the network on the uplink channels (E-DPCCH and E-DPDCH), and the network transmits signaling to the UE on the downlink channels (E-RGCH, E-AGCH, and E-HICH). Power control assigns appropriate transmit power to each downlink channel to ensure that messages can be correctly received by UEs and to avoid wasting resources because of a high transmit power. Power control is also used to control the transmit power of the uplink channels to ensure the transmission quality of uplink data on the Uu interface. For details on power control, see the Power Control Feature Parameter Description.

Issue 05 (2012-11-30)


2-4

WCDMA RAN HSUPA 

2 Overview of HSUPA

Channel switching Channel switching monitors the data transmission requests of UEs in real time, estimates the change in the demands for system resources, and then adjusts the channel bandwidth or performs state transition based on the estimation. This function ensures the QoS and saves system resources. For details, see section 3.2 "Channel Switching."



Mobility management Mobility management processes transactions due to UE movement between cells. For example, when a UE moves from one cell to another cell, the serving cell must be switched to ensure service continuity; when a UE moves between a cell capable of HSUPA and a cell incapable of HSUPA, the HSUPA channel must be configured or removed on the basis of the cell capability to ensure service continuity and service quality. For details on mobility management, see the Handover Feature Parameter Description.



Load control Load control monitors the cell load in real time. If the load exceeds the congestion threshold, UEs in the cell can be handed over to other cells or the data rate can be decreased to reduce the load and reserve resources for subsequent access, thereby increasing the connection success rate. If the load further increases and exceeds the overload threshold, the RL can be released to reduce the load rapidly to ensure system stability. Load control can be performed for UEs with the traffic being carried on the HSUPA channel to reduce the system load. For details on load control, see the Load Control Feature Parameter Description.

2.4.2 HSUPA User Plane Functions Figure 2-3 shows the protocol layers associated with HSUPA user plane functions in the UTRAN. Figure 2-3 Protocol layers associated with HSUPA user plane functions in the UTRAN

Function Description On the UE side, after the service data at the application layer is passed to the RLC layer, the service data is segmented or concatenated to an RLC PDU and then passed to the physical layer for transmission. 

ETFC selection

Issue 05 (2012-11-30)


2-5

WCDMA RAN HSUPA

2 Overview of HSUPA

In each TTI, whether the UE can transmit data and how much data can be transmitted depend on E-DCH transfer format combination (ETFC) selection based on the following factors: − The

total transmit power of the UE.

− The

serving grant (SG) from the NodeB. The SG defines the maximum permissible power used to transmit data on the E-DPDCH, which carries the MAC-e PDU. The larger the SG is, the bigger the MAC-e TB size to be supported in one transmission time interval is.

− The

traffic volume in the RLC buffer of the UE.

ETFC selection is defined in 3GPP TS 25.321 and implemented on the UE side. 

HARQ After ETFC selection determines the amount of data to be transmitted in the current TTI, the RLC PDU is encapsulated into the MAC-es PDU and then into the MAC-e PDU, and then the MAC-e PDU is passed to the HARQ entity. The HARQ entity transmits the MAC-e PDU on the E-DPDCH. If the MAC-e PDU is erroneously received by the cell, the HARQ entity retransmits it until it is correctly received or the retransmission times reach the predefined maximum times. On the NodeB side, if the decoding of an MAC-e PDU fails, the HARQ reception process of the NodeB buffers the data received each time, performs maximum ratio combining (MRC) of received data, and then performs decoding. This increases the probability of correctly receiving packets. The network can control the retransmission times dynamically to ensure the correct reception of MAC-e PDUs. For details, see section4.4 "HSUPA Adaptive Retransmission."



Flow control After the data is correctly received by the NodeB, it is passed to the RNC. There is an Iub interface between the RNC and the NodeB, and the bandwidth on this interface may be limited. Therefore, the NodeB needs to allocate Iub bandwidth among UEs properly through the flow control function to avoid deterioration of transmission quality due to congestion on the Iub interface. If a UE in soft handover establishes several RLs towards the cells under different RNCs, the flow control function also needs to be implemented on the Iur interface to avoid congestion on the Iur interface. For details on flow control, see the Transmission Resource Management Feature Parameter Description.



MDC If a UE is performing soft handover, the same MAC-es PDU may be passed to the RNC from several NodeBs over several Iub interfaces or passed to the SRNC from the DRNC over the Iur interface. In this case, the SRNC performs the MDC function to combine the same data, increasing the probability of correct reception.



Fast scheduling Fast scheduling is very important on the NodeB side. The NodeB assigns the SG to each HSUPA UE through fast scheduling to control the maximum transmission rate of each UE on the Uu interface. Fast scheduling has a direct impact on the QoS of each UE. Therefore, when the NodeB assigns SGs, it must consider the available system resources and the QoS requirement of each UE. That is, when ensuring the QoS of each UE, fast scheduling maximizes the utilization of system resources. For details on fast scheduling, see section 4.1 "Fast Scheduling."



CE management CE resources are NodeB hard resources used for demodulating HSUPA data. CE resources usually become the bottlenecks for system resources. When the CE resources are limited, it is important to logically use the limited resources to meet the QoS requirement of each UE. CE management considers this factor, outputs the information about CE resource allocation for each UE, and then passes it to the scheduling module as a reference for Uu resource allocation. For details on CE management, see section 4.2 "CE Resource Management."

Relationships Between Key User Plane Functions The fast scheduling, Iub flow control, and CE management functions cooperate to achieve efficient utilization of system resources.

Issue 05 (2012-11-30)


2-6

WCDMA RAN HSUPA

2 Overview of HSUPA

Figure 2-4 Relationships between key user plane functions

The Iub flow control and CE management functions allocate appropriate resources to each UE based on the amount of available resources and the QoS requirement of each UE. Then, based on the resource allocation, the two functions calculate the maximum rate of each UE supported by the Iub resources and CE resources. The scheduling module provides an SG for the UE based on the received maximum rate. The SG ensures that the maximum rate of the HSUPA UE on the Uu interface does not exceed the received maximum rate, avoiding Iub resource or CE resource congestion.

Issue 05 (2012-11-30)


2-7

WCDMA RAN HSUPA

3 Control Plane Functions

3 Control Plane Functions 3.1 Bearer Mapping The HSUPA channel provides high transmission rates, reducing the transmission delay. In addition, the services carried on the HSUPA channel can share system resources, improving the resource utilization and system capacity. Therefore, the HSUPA channel becomes a preferred choice for an increasing number of service types. The transport channel carrying HSUPA services is the E-DCH. It can carry services of multiple types and service combinations, as listed in Table 3-1. Table 3-1 E-DCH bearer mapping CN Domain

Service Type

Can Be Carried on E-DCH?

Optional Feature?

-

Signaling (SRB)

Yes

Yes Feature name: SRB over HSUPA

CS

Voice

Yes

Yes Feature name: CS Voice over HSPA/HSPA+

PS

Videophone

No

No

Streaming

No

No

Conversational

Yes

Yes Feature name: VoIP over HSPA/HSPA+

Streaming

Yes

Yes Feature name: Streaming Traffic Class on HSUPA

Interactive

Yes

No

Background

Yes

No

IMS signaling

Yes

Yes Feature name: IMS Signaling over HSPA

During the service setup, the RNC selects appropriate channels based on the UE capability, cell capability, and service parameters to optimize the utilization of cell resources and ensure the QoS. Huawei RAN supports the setting of the types of RABs carried on the E-DCH according to service requirements. For details, see the Radio Bearers Feature Parameter Description.

3.2 Channel Switching After HSUPA is introduced, the UE can stay in a new RRC state, that is, CELL_DCH (with E-DCH). Therefore, when both the cell and the UE support the E-DCH, the state transition of the UE has two additional types, that is, state transition between CELL_DCH (with E-DCH) and CELL_FACH and state transition between CELL_DCH (with E-DCH) and CELL_DCH. This section mainly describes these two types of state transition.

Issue 05 (2012-11-30)


3-1

WCDMA RAN HSUPA


Figure 3-1 UE state transition

Table 3-2 lists the mapping between new state transition and new channel switching. Table 3-2 Mapping between new state transition and new channel switching New State Transition

New Channel Switching

CELL_DCH (with E-DCH) <-> CELL_FACH

E-DCH <-> FACH

CELL_DCH (with E-DCH) <-> CELL_DCH

E-DCH <-> DCH

The switching between E-DCH and FACH and the switching between E-DCH and DCH can be triggered in the following cases: 

The UE activity changes. The UE activity is measured by the amount of data to be transmitted by the UE. When the traffic volume is high, the UE is in the high activity state, and therefore high-rate transport channels are required to provide high service quality. When the traffic volume is low, the UE is in the low activity state, and therefore low-rate channels or shared channels can be used to reduce the resource usage.



The system capability changes during the movement of the UE. When the UE moves from an HSPA cell to a non-HSPA cell, the non-HSPA channel must be configured to ensure service continuity. When the UE moves from a non-HSPA cell to an HSPA cell, the HSPA channel must be configured if the UE supports HSPA to provide high service quality.



The system load changes. When the system enters the overload state, the UE in the CELL_DCH state may be switched to the common channel to reduce resource consumption and ensure system stability. This is applicable to the UE on the HSPA channel. When the UE attempts an access, the access may be rejected because of HSPA overload. Therefore, the UE accesses the network on the DCH. When the system load becomes normal, the UE is switched back to the HSPA channel.

3.2.1 State Transition Based on Traffic Volume When the UE is in the CELL_FACH state, event 4a is reported if data needs to be transmitted and the amount of data buffered at the RLC layer exceeds the predefined traffic volume threshold. In this case, if both the cell and the UE are HSUPA capable, the service can be carried on the HSUPA channel, and admission is successful, then the UE transits to the CELL_DCH (with E-DCH) state. For details, see the State Transition Feature Parameter Description. When the UE is in the CELL_DCH (with E-DCH) state, it does not report the buffered uplink traffic volume to the RNC, because of the restriction defined in 3GPP TS 25.331. Therefore, the RNC estimates the traffic volume only by monitoring the uplink throughput. The adjustments of the channel

Issue 05 (2012-11-30)


3-2

WCDMA RAN HSUPA


bandwidth and UE state are based on the throughput change. For details, see the DCCC Feature Parameter Description.

3.2.2 Channel Switching Based on UE Moving When a UE moves, the best cell changes, and HSUPA-related channel switching may occur i n the following cases: 

The original best cell supports HSUPA, and the traffic of the UE is carried on the E-DCH. In addition: − The new best cell does not support HSUPA. In this case,

the UE cannot set up the E-DCH towards the new best cell, and channel switching from E-DCH to DCH is performed.

− The

new best cell supports HSUPA, but a new HSUPA connection fails to be set up because of insufficient resources. In this case, a DCH is set up towards the new best cell, and therefore channel switching form E-DCH to DCH is performed.



The original best cell does not support HSUPA, and the traffic is carried on the DCH. When a cell supporting HSUPA becomes the best cell and the traffic can be carried on the E-DCH, channel switching from DCH to E-DCH is performed.

When the traffic that can be carried on the HSUPA channel is carried on the DCH in the previous cases, channel switching from DCH to E-DCH may be triggered if the following conditions are met: 

The UE supports HSUPA.



The current cell supports HSUPA or the inter-frequency same-coverage neighboring cell supports HSUPA.

The channel switching mechanisms are as follows: Channel switching based on timer: After the DCH is set up, this mechanism periodically attempts to perform channel switching from DCH to E-DCH.

3.2.3 Channel Switching Based on Load Change When the system load (downlink transmit power or uplink interference) exceeds the overload threshold, the HSUPA UE may be switched to the CELL_FACH state to reduce the system load and ensure system stability. For details, see the Load Control Feature Parameter Description. In the case of HSUPA overload, the access of a service to the HSUPA channel may fail and then the service is set up on the DCH, even if the traffic can be carried on the HSUPA channel and both the cell and the UE are HSUPA capable. Then, the UE periodically attempts to set up the HSUPA channel. If the HSUPA load is low, the UE sets up the HSUPA channel again.

Issue 05 (2012-11-30)


3-3

WCDMA RAN HSUPA

4 User Plane Functions

4 User Plane Functions 4.1 Fast Scheduling 4.1.1 Overview This section involves the following features: 

WRFD-01061209 HSUPA HARQ and Fast UL Scheduling in Node B



WRFD-01061402 Enhanced Fast UL Scheduling

The service carried on the E-DCH can be configured in two modes, non-scheduling mode and scheduling mode. 

Non-scheduling mode: Dedicated resource is reserved for the service to support its maximum bit rate (MBR). That is, the transmission rate is the MBR if the service has enough traffic volume. This mode can guarantee the QoS very well. When the service is transmitted in non-scheduling mode, the maximum available rate of the service is defined in service connection establishment and is not controlled by the scheduling module. In this mode, based on the MBR requested by the service, the RNC configures the available transport block with the maximum size for the service. If the transmit power permits, the UE can use the transport block with the maximum size to transmit data. The non-scheduling mode is generally applicable to services sensitive to delay or with constant source rates, such as VoIP.



Scheduling mode: The available maximum transmission rate is controlled by the HSUPA scheduler in the NodeB and it can be adjusted frequently by the HSUPA scheduler. If the cell resource is enough, the service configured in scheduling mode can get a bit rate in the range from the guaranteed bit rate (GBR) to the MBR. If the cell resource is congested, the bit rate is not higher than the GBR. When the service is transmitted in scheduling mode, the scheduling module, based on the load on the Uu interface and the CE resource and Iub bandwidth allocation results, adjusts the transmission rate of the HSUPA UE by controlling the SG to be assigned to the HSUPA UE. The scheduling module is applicable to services with variable source rates, such as the interactive service and background service.

Only the services configured in scheduling mode are controlled by the scheduling module. Therefore, the subsequent description is based on the services carried on the E-DCH and configured in scheduling mode. For detailed information about how to configure scheduling mode for different traffic classes, see Radio Bearers Feature Parameter Description. The scheduling period is based on the TTI. The scheduling period is 10 ms for the 10-ms TTI and 2 ms for the 2-ms TTI.

Issue 05 (2012-11-30)


4-1

WCDMA RAN HSUPA


Figure 4-1 HSUPA scheduling

The impacts of other functions on HSUPA scheduling are as follows: 

Estimation of remaining Uu load NodeB estimates the remaining Uu load according to the current measured RTWP values. The estimated remaining load indicates the load resources on the Uu interface that can be allocated to UEs. And then the NodeB performs resource allocation according to the estimation results.



Dynamic CE management Dynamic CE management module can request the HSUPA scheduling module to decrease the rates of some UEs due to lack of CE resources. The HSUPA scheduling module needs to send the AG or RG 'Down' message to the associated UEs.



Iub flow control module The Iub flow control module can request the HSUPA scheduling module to decrease the transmission rates of some UEs due to Iub congestion. The HSUPA scheduling module needs to send the RG 'Down' message to the associated UEs.



Responding to the MBR limitation result HSUPA scheduling module sends the RG 'Down' message to each UE of which the data rate exceeds the MBR on the Uu interface to decrease the data rate.

4.1.2 Estimation of Remaining Uu Load This section describes the feature WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation and WRFD-020136 Anti-Interference Scheduling for HSUPA.

Estimation of Remaining Uu Load In an HSUPA-capable cell without Interference Cancellation (IC), the estimated remaining load is calculated as follows: Estimated remaining load = target level of uplink load - Uu interface load corresponding to the current measured RTWP value Where: The target level of uplink load is specified by the

parameter.

In an HSUPA-capable cell with IC, the measured RTWP of the cell will be counteracted by IC to some extent. Therefore, the system introduces the function of dual-threshold scheduling (WRFD-020137

Issue 05 (2012-11-30)


4-2

WCDMA RAN HSUPA


Dual-Threshold Scheduling with HSUPA Interference Cancellation) to better estimate the remaining load. This function uses two thresholds (threshold one and threshold two) to calculate the remaining load. The formula is as follows: Estimated remaining load = min {(threshold one - Uu interface load corresponding to the measured RTWP after IC), (threshold two - Uu interface load corresponding to the measured RTWP before IC)} where 

Threshold one is specified by the

parameter.



Threshold two is a dynamic threshold, varying based on measured RTWP after IC.

and Uu-interface load corresponding to the

To prevent the interference on neighboring cells due to an increased threshold two, threshold two must vary in the allowed range. The maximum value of threshold two is calculated based on threshold one and . The function of dual-threshold scheduling increases the estimated remaining load and further the resources that can be scheduled in the cell. In this way, the HSUPA throughput of the cell increases. Note that the function of dual-threshold scheduling does not take effect if is set to0.

Anti-Interference Scheduling In an HSUPA-capable cell suffering from strong external interference, the cell throughput is extremely low, resulting in an adverse HSUPA-user experience. Huawei introduces the function of anti-interference scheduling for HSUPA (WRFD-020136 Anti-Interference Scheduling for HSUPA) to suppress strong external interference. This function ensures a stable system performance, and also improves user experience by increasing the cell throughput. With this function, the RNC not only calculates the remaining load based on the measured RTWP of the cell, but also considers the load f actor of users in the cell. When the load of users (including HSUPA users and R99 users) in the cell is lower than x , the HSUPA scheduler can ensure that the remaining resources are available for users in the cell, until the measured RTWP reaches or exceeds the RTWP corresponding to . is the load threshold for the minimum uplink coverage. The larger the value of , the higher the HSUPA throughput of the cell suffering from strong external interference. However, a large value of leads to a high RTWP and a reduced cell coverage. To enable anti-interference scheduling, turn on the function switch and the RTWP-based anti-interference function switch : RTWP_RESIST_DISTURB. In any of the following cases, you can enable anti-interference scheduling by only turning on the function switch : 

The UL_UU_OLC option of the

parameter is deselected;



The ALGORITHM_OFF option of the



The ALGORITHM_SECOND option of the

parameter is selected; parameter is selected.

4.1.3 Queuing The main purpose of Uu resource scheduling is to efficiently utilize Uu resources, provide satisfactory QoS for more users, and provide differentiated services. The HSUPA scheduling has two sub-functions: scheduling queuing and Uu resource allocation. The purposes of UE queuing are as follows: 

To ensure the QoS of UEs: to try to ensure that the UEs can obtain the guaranteed bit rate (GBR)

Issue 05 (2012-11-30)


4-3

WCDMA RAN HSUPA




To differentiate UEs: to ensure that the UEs with a great scheduling priority indicator (SPI) weight obtain resources preferentially



To ensure fairness: to ensure that the UEs with the same SPI weight have the same opportunity to obtain resources

The factors that affect queuing are as follows: 

The priority of users with the effective rate higher than the GBR is lower than the priority of users with the effective rate lower than the GBR.



The priority of users with a greater SPI weight is higher; the priority of users with a smaller SPI weight is lower. This helps provide differentiated services.



Happy Bit: reported by the UE.



Effective rate: The actual rate obtained by the UE is monitored by the NodeB on a real-time basis.



GBR: The GBR is configured on the basis of user priorities. Generally, the GBR increases with the user priority. The GBR can be set through the SET UUSERGBR and ADD UCELLEFACH commands on the RNC.



SPI weight: The SPI weight (SPIweight ) is configured on the basis of the SPI . Generally, the SPIweight increases with the SPI . And SPIweight can be configured in the RNC. For details, see section 5.2 "Diff-Serv Management."

4.1.4 Uu resource allocation Based on the scheduling queuing result and the Uu interface load of each cell participating in scheduling, the Uu resource allocation module allocates Uu resources to users and sends the AG or RG to the users. During the rate adjustment, the QoS of users with the GBR requirement can be further ensured. When the NodeB switch HSUPAOLSCHSWITCH is set to ON and the system load exceeds the target load threshold but does not exceeds overload threshold, the users with the actual rate lower than the GBR is not decreased or even can be increased during the rate adjustment.

4.2 CE Resource Management 4.2.1 Overview A channel element (CE) is defined as the baseband resources required in the Node B. On the RNC side, it is referred to as the NodeB credit. On the NodeB side, it is referred to as the Channel Element (CE). The consumed NodeB resource of one equivalent 12.2 kbit/s AMR voice service, i ncluding 3.4 kbit/s signaling on the Dedicated Control Channel (DCCH), is defined as one CE. If there is only 3.4 kbit/s signaling on the DCCH, one CE is consumed. There are two kinds of CE. One is uplink CE supporting uplink services, and the other is downlink CE supporting downlink services. Therefore, one 12.2 kbit/s AMR voice service consumes one uplink CE and one downlink CE. Figure 4-2 Baseband CE Resources

Issue 05 (2012-11-30)


4-4

WCDMA RAN HSUPA


Maximum CE resources in one NodeB depend on the baseband card capabilities and on the CE licenses (uplink and downlink). The CE licenses in one NodeB can be shared between carriers and sectors 

Common Channels have dedicated CE resources (No impact on CE license)



HSDPA (UL, DL) have dedicated CE resources (No impact on CE license)



R99 DCH (UL, DL) and HSUPA take resources from CE license



R99 and HSUPA channels share the same pool of CE resources

4.2.2 CE Sharing A cell must be set up in an uplink resource group (ULGROUPN ) and a downlink resource group (DLGROUPN ) respectively. In the uplink, CE resources can be shared in one resource group dynamically. In the downlink, CE resources can be shared in one board. A cell can be set up in only one board of the downlink resource group.

4.2.3 CE Consumption and Admission. CEs consumption is determined by SF. RNC performs admission based on the NodeB capability, license CEs and the service required CEs. For details, see Call Admission Control Feature Parameter Description.

4.2.4 Dynamic CE Management Overview This section involves the feature "WRFD-010638 Dynamic CE Resource Management." CE resources are hard resources used for channel modulation and demodulation. Generally, if the service rate is higher, more CE resources are required. To ensure the QoS, CE resources need to be allocated on the basis of the maximum bit rate of users. In this case, if fixed CE resources are allocated to users, the resources are wasted when the rate of the service source is low. The rate of the services that are carried on the HSUPA channel and configured in scheduling mode can be controlled by the scheduling module. Therefore, dynamic CE management is used. That is, CE resources to be allocated to users are adjusted dynamically according to the conditions of CE resources and the change of user requirements to improve the utilization of CE resources. The following shows an example of comparison between CE consumption with or without dynamic CE management.

Issue 05 (2012-11-30)


4-5

WCDMA RAN HSUPA


Figure 4-3 comparison between CE consumption with or without dynamic CEmanagement

The rules for dynamic CE resource allocation are as follows: 

When the rate of the service source decreases, the redundant CE resources are called back.



When there is a need to increase the service rate, CE resources are reserved.



When there are insufficient available CE resources, CE resources are allocated to users in the serving RLS preferentially because the QoS of users depends on the resource allocation of the serving cell.



When the available CE resources are insufficient to meet the requirements of all the users in the serving RLS, user priorities need to be considered to provide differentiated services.

In addition, the dynamic CE management module needs to process messages from external functional modules, such as the resource allocation request during the establishment of a new connection and the channel reassignment request. In such a case, the QoS requirement of users and user priorities must be considered. Dynamic CE management has no function switch parameter. Dynamic CE resource management increases CE resource utilization for the network, improving system capacity. This feature also reduces the service access delay by quickly allocating and retrieving CE resources, improving user experience. With Dynamic CE resource management, the throughput of HSUPA-capable UEs can be increased, leading to a slight increase in Rise of Thermal (ROT), a slight decrease in coverage, and an increased probability of call drops. When CE resources are insufficient, Dynamic CE resource management has a negative impact on the admission success rate. In RAN10.0, Dynamic CE resource management and HSUPA DCCC cannot be enabled at the same time. In RAN11.0 and later, HSUPA DCCC does not take effect in cells in the active set of an HSUPA-capable UE that have dynamic CE resource management enabled. If Dynamic CE Resource Management is enabled for the entire network, disable HSUPA DCCC.

Issue 05 (2012-11-30)


4-6

WCDMA RAN HSUPA


Procedure Figure 4-4 Procedure of dynamic CE management

The main functions of the dynamic CE management module are shown in Figure 4-4. The procedure of dynamic CE management is as follows: Step 1 Calling back CE resources Based on the actual data rate of users, the CE management module calls back the idle CE resources to improve the utilization of resources and updates the information about available system resources. Step 2 Processing external related messages Based on the requirement of external signaling messages, the CE management module allocates appropriate CE resources to users and updates the information about available system resources. Step 3 Increasing CE resources dynamically Based on the estimation of the requirement for CE resources, the CE management module increases CE resources for users with the requirement for increasing CE resources. If the available CE resources are insufficient after the processing in the first two steps, the CE management module provides differentiated services and adjusts CE resources among users dynamically based on user priorities. ----End Steps 1 to 3 can be triggered periodically, and the periods can be different. Step 2 is triggered by events. If several processing tasks are triggered at a time, the CE management module performs the processing by following the procedure shown in Figure 4-4.

CE Resource Requirement Monitoring The CE management module monitors the requirements of users f or CE resources periodically. That is, in a specified monitoring period, the CE management module extracts the maximum traffic volume in a TTI as the current maximum traffic volume. Then, the CE management module estimates the new maximum traffic volume in a TTI if the scheduler sends RG UP to the UE based on the current maximum traffic volume requirement. In this case, the CE management module calculates the new CE requirement and takes it as the CE requirement of the user.

Issue 05 (2012-11-30)


4-7

WCDMA RAN HSUPA


In the calculation of the CE requirement, some resources are reserved for the user. Therefore, the QoS can be ensured in the case of user rate fluctuation.

User Priority Queuing The calculation of user priorities considers the following factors:  

Happy Bit reported by the UE Actual rate obtained by the UE through real-time monitoring on the NodeB



GBR requirement of the UE



SPI



The queuing method is the same as that of the HSUPA fast scheduling algorithm. For details, see section 4.1 "Fast Scheduling."

CE Resource Callback CE resource callback is based on the monitoring of CE resource requirement of each user. For users with the currently allocated CE resources more than the calculated CE requirement, the required CE resources are reserved and the redundant CE resources are called back.

External Message Processing The external message processing module processes the requests for CE resource allocation triggered by external messages, such as requests for adjusting CE resource allocation because of RL establishment, RL addition, RL reconfiguration, and compression mode start, and requests for increasing CE resources in the case of rate increase triggered by MAC-e scheduling. If the available CE resources are sufficient, CE resources are allocated as required. If the available CE resources are insufficient, the CE resources allocated to other users can be preempted when some external messages arrive to ensure the access success rate or meet the rate adjustment requirement of the scheduling module. During the preemption process, the CE resources of low-priority users are preempted preferentially.

CE Resource Increase If the CE resources requested by a user are more than the current allocated CE resources, resources must be increased. In addition, it is possible that the available CE resources do not meet the requirements of all users. In such a case, user priorities need to be considered. For details, see User Priority Queuing in this section. At the same time, the conditions of the serving cell also need to be considered. If the serving cell of the user belongs to the current NodeB, the user is called serving user. If the serving cell of the user does not belong to the current NodeB, the user is called non-serving user. A serving user has a higher priority than a non-serving user because the QoS of the user mainly depends on the QoS obtained in the serving cell. The CE resource increase consists of the following functions: 

CE resource adjustment among serving users

After the connection is established, serving users cannot preempt resources mutually during the dynamic CE resource allocation. Therefore, it is possible that high-priority users cannot obtain sufficient resources because low-priority users occupy a large amount of resources. In such a case, the resource fairness adjustment must be performed among serving RLs. The method is as follows: If the current available CE resources do not meet the requirement of user rate increase, reduce the CE resources occupied by the serving user with the lowest priority to reserve resources and meet the rate increase requirement of high-priority users.

Issue 05 (2012-11-30)


4-8

WCDMA RAN HSUPA 


Resource increase for serving users − If

the monitoring of CE resource requirements shows that the CE resources allocated to the serving users are less than the CE resources requested, CE resources must be increased.

− If the

available resources meet the requirements of resource increase, CE resources are allocated according to the requirements of users.

− If the

available resources are insufficient to meet the requirements of resource increase, CE resources are allocated in descending order of user priorities.



Resource increase for non-serving users

After the resource allocation to serving RLs is complete, CE resources are allocated to non-serving users requesting resource increase in descending order of user priorities only when there are redundant resources.

4.3 Uplink Macro Diversity Intelligent Receiving This section involves the feature "WRFD-010640 Uplink Macro Diversity Intelligent Receiving."

4.3.1 Background This feature is intended for the NodeB. In the case of soft handovers, if the serving cell of the user belongs to the current NodeB, the user is called serving user. If the serving cell of the user does not belong to the current NodeB, the user is called non-serving user. Though soft handovers can improve the reception quality of HSUPA link data, the quality is improved at the price of multiplied resource consumption, especially for Iub resources and CE resources. These two types of resources are the bottlenecks for system resources. The service quality mainly depends on the reception quality in the serving cell. Therefore, when the Iub resources and CE resources are insufficient to meet the data transmission requirements of all the users, the non-serving RL resources are allocated to the serving RLs of other users at the price of soft handover gains of some users. This improves the utilization of resources and increases the total throughput. If the Iub resources or CE resources are limited, this feature reduces the resources allocated to the non-serving users to ensure the service quality of serving users and increase the capacity of the entire system.

4.3.2 Function Implementation Iub Resource Allocation for Non-Serving RLs The Iub resources are allocated in the following ways: 

When the Iub resources are in the normal state, each user is allocated Iub resources uniformly. For details, see the Transmission Resource Management Feature Parameter Description.



When the Iub resources are in the congestion state, most resources are allocated to serving users.

This resource allocation policy ensures the service quality of serving users preferentially, and it is applicable only to BE services.

CE Resource Allocation for Non-Serving RLs This feature depends on dynamic CE resource allocation. When dynamic CE resource allocation is enabled, this feature ensures that the priorities of serving RLs are always higher than the priorities of non-serving RLs.

Issue 05 (2012-11-30)


4-9

WCDMA RAN HSUPA




When a serving RL is established or added, the RL preempts the resources allocated to non-serving users preferentially if the idle resources do not meet its requirement. If the resources do not meet the requirement even after the resources of non-serving users that can be preempted are all preempted, the RL preempts resources of serving users.



When a non-serving RL is established or added, the non-serving RL can preempt only the resources occupied by non-serving users if the idle resources do not meet its requirement.

Dynamic CE resource allocation is responsible for monitoring the requirement of each user for CE resources and increasing CE resources for the user with the currently allocated CE resources less than the CE resources requested. 

Dynamic CE resource allocation increases CE resources for serving users preferentially. If the idle CE resources do not meet the requirement of serving users for CE resource increase, serving users can preempt CE resources of non-serving users.



If there are idle CE resources even after the requirement of serving users for CE resources is met, dynamic CE resource allocation increases resources according to the requirement of non-serving users for CE resources.

During the preemption process, the CE resources of non-serving users can be reduced to only one CE. That is, E-DPCCH demodulation is supported, but the E-DPDCH carrying data is not demodulated. The CE resources of serving RL must meet or exceed the GBR demodulation requirement.

4.4 HSUPA Adaptive Retransmission This section involves the feature WRFD-010641 HSUPA Adaptive Retransmission.

4.4.1 Background The retransmission times of the MAC-e PDU are the average retransmission times at which the MAC-e PDU of the user can be correctly received by the NodeB. The UTRAN can adjust the interference of an UE to the cell and the requirement of service transmission for UE transmit power by setting the different target retransmission times of MAC-e PDU. The reasons are as f ollows: 

If the signal-to-noise ratio (Eb/No) of the uplink E-DPDCH carrying the MAC-e PDU that reaches the NodeB each time is increased, the probability in which the MAC-e PDU is correctly received is also increased. This decreases the required retransmission times, but increases the interference to the NodeB.



If the signal-to-noise ratio of the uplink E-DPDCH that reaches the NodeB each time is reduced, the retransmission times required for correctly receiving the MAC-e PDU are increased, but the interference to the NodeB is reduced.

The HSUPA power control algorithm can adjust the signal-to-noise ratio of the E-DPDCH that reaches the NodeB each time by comparing the actual retransmission times with the target retransmission times to control the retransmission times of the MAC-e PDU within the target value range. In this manner, the interference level of the UE to the system is adjusted, and the requirement for UE transmit power is also adjusted. Generally, to enable the user to obtain a higher rate, set the target retransmission times to a smaller value at the price of increasing the load properly. This case is called "small target retransmission times". The "small target retransmission times" configuration, however, may have a negative effect in the following cases: 

The UE transmit power is limited. When the UE moves to the edge of the cell, the transmit power is not enough. Therefore, the probability in which the MAC-e PDU is correctly received is reduced, and therefore the UE throughput is reduced promptly.

Issue 05 (2012-11-30)


4-10

WCDMA RAN HSUPA 


The cell load is limited. When the load of the cell serving the UE is high, the scheduling algorithm may no longer provide additional rate grants for the UE. Therefore, the UE throughput is also limited.

HSUPA adaptive retransmission increases the target retransmission times adaptively based on the previous two cases to achieve the following purposes: 

Increasing retransmission times can obtain the gain of time diversity, reduce the requirement for UE transmit power, enlarge the coverage range, and increase the UE throughput.



Reducing interference of the UE to the system enables the UE to obtain a higher rate grant and increase the UE throughput, increasing the cell throughput and uplink capacity.

When the problems in the previous two cases are solved, HSUPA adaptive retransmission restores the target retransmission times to a smaller value. Accordingly, the transmit power resources of the UE and the load resources of the cell can be fully used to enable the UE rate to approach or reach the throughput limit, improving user experience. HSUPA adaptive retransmission helps to increase the throughput per user and the uplink capacity of a cell. It has the following benefits: 

When uplink coverage is limited, it increases the uplink throughput of UEs at the cell edge.



When the uplink power load in a cell is limited, it increases the target number of uplink retransmissions to increase the uplink throughput and capacity of the cell.

When CE resources are insufficient, HSUPA adaptive retransmission does not adjust the target number of uplink retransmissions. As a result, it does not increase the uplink cell capacity.

4.4.2 Function Implementation Implementation Procedure If the PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH parameter is set to ON in the RNC (SET UCORRMALGOSWITCH: P c S w i t c h = PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-1), this function can be activated. Figure 4-5 shows the procedure of HSUPA adaptive retransmission.

Issue 05 (2012-11-30)


4-11

WCDMA RAN HSUPA


Figure 4-5 HSUPA adaptive retransmission

The HSUPA adaptive retransmission algorithm periodically determines whether the target retransmission times of each user need to be adjusted. To avoid fluctuation of system load, the maximum number of users are fixed for adjustment in each period. When determining whether to adjust the target retransmission times, the NodeB needs to periodically monitor the conditions of UE transmit power, UE effective rate and resources such as the Uu load resources and CE resources. 

Determining whether the transmit power of the HSUPA UE is limited The UE reports the Scheduling Information (SI) to the NodeB. The SI contains the actual transmit power of the UE. Based on the SI, the NodeB estimates whether the transmit power of the UE meets the requirement of the current service rate and determines whether the transmit power of the UE is limited.



Determining whether the effective rate of the HSUPA UE is limited by the physical capability Based on the monitoring result of the UE effective rate, the NodeB determines whether the uplink physical capability of UE is limited.



Determining whether the load on the Uu interface is limited Based on the monitoring result of the Uu interface load, the NodeB determines that the load on the Uu interface is limited when the load is high and that the load on the Uu interface is restored when the load is low.



Monitoring CE resources The NodeB monitors the available CE resources. If the available CE resources are sufficient, retransmission is allowed. Otherwise, retransmission is rejected.

Retransmission Times Increase If the transmit power of the UE is limited, the transmission times of the user need to be increased. If several users meet the conditions, user queuing is performed. The user queuing method is the same as the priority queuing method of the HSUPA fast scheduling. If the load on the Uu interface is limited, the transmission times of the user need to be increased. The user queuing method is the same as the priority queuing method of the HSUPA fast scheduling. Issue 05 (2012-11-30)


4-12

WCDMA RAN HSUPA


The user with the transmit power of the UE limited is selected preferentially because only one user is allowed for the adjustment in a period. If there is no such user, the user with the load on the Uu interface limited is selected. The user with the highest priority is selected preferentially. The retransmission times can be adjusted only when the available CE resources are sufficient for the retransmissions.

Retransmission Times Decrease Once the load on the Uu interface is no longer limited, the user needs to check whether the transmit power of the UE is not limited either. If the transmit power of the UE is no longer limited, the retransmission times need to be decreased to completely utilize the resources. If the physical capability of UE is limited, the retransmission times need to be decreased to increase the effective rate of the UE. If several users meet the conditions, user queuing is performed. The user queuing method is the same as the priority queuing method of the HSUPA fast scheduling.

Issue 05 (2012-11-30)


4-13

WCDMA RAN HSUPA

5 HSUPA QoS Management

5 HSUPA QoS Management After HSUPA is introduced, a series of functions are performed to meet the QoS requirements and provide differentiated services.

5.1 QoS Guarantee HSUPA QoS guarantee ensures that the basic QoS requirements of services can be met. It considers three main QoS indicators: service delay, service rate, and service connectivity. 

For delay-sensitive real-time services such as the CS voice service and VoIP service, HSUPA functions ensure that the packet transmission delay is smaller than the acceptable delay limit.



For rate-sensitive non-real-time services such as the interactive service, background service, and streaming service, HSUPA functions allocate them the service rates that are higher than or equal to the GBR. Increasing service rates can improve the user satisfaction.



HSUPA QoS management ensures the connectivity of services.

HSUPA QoS guarantee meets the QoS requirements of services through related HSUPA functions. Table 5-1 lists the relationships between HSUPA functions and QoS indicators. Table 5-1 Relationships between HSUPA functions and QoS indicators Function

Service Connectivity

Service Delay

Service Rate

√

√

Fast scheduling

√

√

Flow control

√

√

Bearer mapping Mobility management

√

Load control

√

Dynamic CE management

√

HSUPA adaptive retransmission √

√

These relationships between HSUPA functions and QoS indicators are described as follows: 

Bearer mapping The HSUPA channel can provide a higher peak rate than the DCH and reduce data transmission delay. Therefore, bearer mapping enables services that require high rate or small delay to be carried on the HSUPA channel to improve user experience. For details, see the Radio Bearers Feature Parameter Description.



Mobility management Mobility management ensures service continuity. When a UE moves to an HSUPA-capable cell, services supporting HSUPA bearer should be carried on the HSUPA channel to ensure service continuity. For details, see the Handover Feature Parameter Description.



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 to ensure the QoS of the admitted users.

Issue 05 (2012-11-30)


4-1

WCDMA RAN HSUPA

5 HSUPA QoS Management

When a cell is overloaded, the overload control function is required to relieve congestion and ensure the QoS of most users. For details, see the Load Control Feature Parameter Description. 

Fast scheduling Based on the achieved service rate, GBR, and MBR, the fast scheduling function tries to allocate enough resources to meet the requirement for transmission rate on the Uu interface. After a required rate is allocated, the requirement for transmission delay is also met. For details, see section4.1 "Fast Scheduling."



Flow control By allocating appropriate Iub bandwidth to users, the flow control function reduces the transmission time on the Iub interface. For details, see the Transmission Resource Management Feature Parameter Description.



Dynamic CE management Dynamic CE management ensures efficient utilization of CE resources. In addition, dynamic CE management allocates more CE resources according to the requirements of users to ensure the QoS of users. For details, see section 4.2 "CE Resource Management."



HSUPA adaptive retransmission When a UE moves to the edge of a cell and the transmit power is not sufficient, the uplink data transmission may be interrupted. In such cases, HSUPA adaptive retransmission increases the retransmission times automatically to ensure the continuity of data transmission. When the transmit power is high enough, the retransmission times decrease automatically to increase the service rate. For details, see section 4.4 "HSUPA Adaptive Retransmission."

5.2 Diff-Serv Management HSUPA QoS management considers the service delay, service rate, and service connectivity. It tries to provide satisfactory QoS and maximize the efficiency of resource utilization. HSUPA Diff-Serv management provides differentiated services based on service types and user priorities. The application scenarios are as follows: 

When the basic QoS requirements of some users cannot be met because of system resource congestion, high-priority users or services are allocated resources preferentially, improving the user satisfaction.



When the system resources are redundant even after the basic QoS requirements of all the users are met, the redundant resources are allocated to users additionally. High-priority users or services are allocated more additional resources, further improving the user satisfaction.

HSUPA Diff-Serv management provides the following QoS differentiated service policies: 

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 are introduced. This section describes the differentiated services based on SPI weights and the differentiated service policies. For detailed information, see the Differentiated HSPA Service Feature Parameter Description.

Issue 05 (2012-11-30)


4-2

WCDMA RAN HSUPA

6 Impact on the Network

6 Impact on the Network 6.1 WRFD-020136 Anti-Interference Scheduling for HSUPA Impact on System Capacity In a cell experiencing strong interference, activating the Anti-Interference Scheduling for HSUPA feature increases High Speed Uplink Packet Access (HSUPA) capacity for the cell. In optimal conditions, this feature can protect the HSUPA capacity of such cells from deteriorating at all.

Impact on Network Performance In a cell experiencing strong interference, this feature helps increase the available power of the cell. As a result: 

The cell's uplink load increases.



The cell coverage narrows.



At the cell edge, the access success rate and call drop rate deteriorate, such as: − Radio

resource control (RRC) connection setup rate

− Radio

access bearer (RAB) assignment success rate

− Handover success

rate

With a load threshold for the minimum coverage, this feature limits the cell load and ensures the minimum coverage. If there is no strong interference, this feature does not work and no KPIs deteriorate.

6.2 WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation Impact on System Capacity Dual-Threshold Scheduling with HSUPA Interference Cancellation further increases HSUPA throughput by around 5% to 15% for cells enabled with HSUPA UL Interference Cancellation.

Impact on Network Performance This feature has the following impact on cell coverage and cell capacity: 

Cell coverage The RTWP threshold remains unchanged after interference cancellation (IC) is introduced. Therefore, this feature does not negatively affect the coverage of serving cells or their neighboring cells. For the latter, this is true, regardless of whether they are enabled with IC or not, because they are also controlled by the RTWP threshold.



Cell capacity This feature increases the RTWP before IC is used, generating interference to the neighboring cells. The capacity of the neighboring cells will not decrease if they are enabled with this feature and the related parameters are set to the same values as the serving cells. The capacity of the neighboring cells will decrease due to stronger interference from the serving cells if the neighboring cells are not enabled with this feature, regardless of whether these neighboring cells are enabled with IC or not.

Issue 05 (2012-11-30)


4-1

WCDMA RAN HSUPA

7 Engineering Guidelines

7 Engineering Guidelines 7.1 HSUPA Anti-interference Scheduling 7.1.1 When to Use Anti-Interference Scheduling for HSUPA Some sites in commercial networks are exposed to strong, random external interference in the uplink. As a result, these sites provide extremely low HSUPA throughput even though their received total wideband power (RTWP) is high. This leads to poor user experience. To address this issue, the Anti-Interference Scheduling for HSUPA feature is introduced to reduce the impact of strong interference on the network, maintaining a high HSUPA throughput and significantly improving user experience. This feature yields notable gains when external interference reaches 3 dB or above. This feature is recommended when the downlink coverage is not planned as wide or good as the uplink coverage. That is, the uplink coverage is f ar wider and better than the downlink coverage. This feature is not recommended in any of the following scenarios: 

Local cells experience strong interference from their neighboring cells because of an inappropriate network plan, in which case the network must be optimized first.



Network KPIs such as the access success rate and call drop rate deteriorate because of poor coverage, in which case activating Anti-Interference Scheduling for HSUPA will further compromise the coverage.



The RRU Multi-Site Cell feature is activated, in which case the Anti-Interference Scheduling for HSUPA feature may underperform or even stop working.

When symmetric services (for example, adaptive multirate (AMR) and video phone (VP) services) have been planned, this feature is recommended if the network frequently suffers from external interference and enduring interference in the uplink, for example, 10 minutes of interference during busy hours every day; this feature is not recommended if the network does not suffer from external interference in the uplink.

7.1.2 Information to Be Collected The following table describes the counters that are used for determining a suitable cell where this feature is to be activated. Counter Name

Counter Description

VS.MeanRTWP

Average power of totally received bandwidth for a cell

VS.MinRTWP

Minimum power of totally received bandwidth for a cell

Issue 05 (2012-11-30)

Remarks The difference between VS.MeanRTWP and VS.MinRTWP indicates the external interference to a cell. During off-peak hours, the greater the difference, the stronger the external interference and the higher the probability that this feature provides gains. However, if the external interference is stronger than LOADTHRESH4MINULCOV , triggering this feature does not provide gains.


4-2

WCDMA RAN HSUPA


Counter Name

Counter Description

Remarks

VS.HSUPA.MeanBitRate.WithDat a

Average throughput of HSUPA users in a cell when data is transmitted

The higher the average throughput of HSUPA users with data transmission, the higher the probability that this feature provides gains.

VS.HSUPA.DataUserNum.Mean

Average number of HSUPA users that transmit data for a cell

The larger the average number of HSUPA users, the higher the probability that this feature provides gains.

VS.HSUPA.UnHappyUserNum

Number of Unhappy HSUPA users for a cell

VS.HSUPA.UnHappyUserNumRa tio

Ratio of the number of Unhappy HSUPA users to the total number of HSUPA users for a cell

These counters indicate potential HSUPA traffic volume, that is, potential capacity expansion requirements. The larger the counter values, the higher the probability that this feature provides gains.

VS.HSUPA.LeftPwrLmtUserRatio

Ratio of the number of HSUPA users with limited uplink load to the total number of HSUPA users for a cell

7.1.3 Overall Deployment Procedure Figure 7-1 shows the overall procedure for deploying Anti-Interference Scheduling for HSUPA. Figure 7-1 Overall procedure for deploying Anti-Interference Scheduling for HSUPA

Issue 05 (2012-11-30)


4-3

WCDMA RAN HSUPA


7.1.4 Feature Deployment For details on how to activate, verify, and deactivate this feature, see Configuring Anti-Interference Scheduling for HSUPA in the Feature Activation Guide.

7.1.5 Feature Monitoring After Anti-Interference Scheduling for HSUPA is activated, check the values of the following RNC counters to track changes to the HSUPA throughput in a cell when the network suffers from external interference: 

VS.HSUPA.MeanChThroughput: measures the average uplink throughput of individual MAC-d flows for HSUPA in a cell



VS.MeanRTWP: measures the average RTWP in a cell (unit: dBm)

After this feature is enabled, the value of VS.MeanRTWP or VS.HSUPA.MeanChThroughput either increases or remains unchanged. If the two values increase, the user experience at the cell edge and in neighboring cells may deteriorate, and KPIs such as the RRC connection setup success rate, RAB assignment success rate, handover success rate, and call drop rate may also deteriorate.

7.2 Dual-Threshold Scheduling with HSUPA Interference Cancellation 7.2.1 When to Use Dual-Threshold Scheduling with HSUPA Interference Cancellation This feature is recommended for a cell where the following conditions are met: 

The feature HSUPA UL Interference Cancellation is activated.



The operator wants to further increase the HSUPA capacity in the uplink.



The cell's uplink load is heavy. For example, the load constantly exceeds the value for MaxTargetUlLoadFactor .

This feature is also recommended in contiguous areas, but the capacity of neighboring cells that border the areas must not be limited. The reason is as follows: Assuming cells A and B are neighboring cells, cell A generates more interference for cell B after this feature is activated in cell A but not in cell B. As a result, the uplink throughput of cell B may decrease. If this feature is activated with identical parameter settings for both cells, the cells cause each other a lot of interference, but their uplink throughput remains unchanged because they are both configured with a high pre-IC target load.

7.2.2 Information to Be Collected Before activating Dual-Threshold Scheduling with HSUPA Interference Cancellation, collect the following information: 

Activation state of HSUPA UL Interference Cancellation: This feature is dependent on HSUPA UL Interference Cancellation. Therefore, HSUPA UL Interference Cancellation must be activated before this feature can be used.



Uplink load of cells: When the uplink load is restricted, this feature yields notable capacity gains. When the uplink load is not restricted, this feature yields no gains.



Board configuration: For 3800 or 3900 series base stations that support inter-board IC, this feature takes effect immediately after being enabled. For base stations that do not support inter-board IC,

Issue 05 (2012-11-30)


4-4

WCDMA RAN HSUPA


such as the BTS3812E, this feature works only for cells in which all services are processed by the same IC-capable board. The following table describes the counters that are used for determining a suitable cell where this feature is to be activated. Counter Name

Counter Description

Remarks

VS.MeanRTWP(dBm)

Mean power of totally received bandwidth for a cell

The more the corresponding UlLoad of the average RTWP exceeds MaxTargetUlLoadFactor , the higher the probability that this feature provides gains.

VS.HSUPA.MeanBitRate.WithDat a


The higher the average throughput of HSUPA users with data transmission, the higher the probability that this feature provides gains.

VS.HSUPA.DataUserNum.Mean

Average number of HSUPA users availing data transfer in a cell within a TTI during the measurement period

The larger the average number of HSUPA users, the higher the probability that this feature provides gains.

VS.HSUPA.UnHappyUserNum


VS.HSUPA.UnHappyUserNumRa tio

Ratio of the number of Unhappy HSUPA users to the total number of HSUPA users in a cell

These counters indicate potential HSUPA traffic volume. The larger the counter values, the higher the probability that this feature provides gains.

VS.HSUPA.LeftPwrLmtUserRatio

Ratio of the number of HSUPA users with limited uplink load to the total number of HSUPA users in a cell

7.2.3 Feature Deployment For details on how to activate, verify, and deactivate this feature, see Configuring Dual-Threshold Scheduling with HSUPA Interference Cancellation in the Feature Activation Guide.

7.2.4 Feature Monitoring To determine whether Dual-Threshold Scheduling with HSUPA Interference Cancellation has taken effect, check the value of the RNC counter VS.MeanRTWP, which measures the average RTWP in a cell. When the uplink load for a cell is restricted and this feature is enabled, the value of VS.MeanRTWP is greater than the RTWP calculated based on the parameter MaxTargetUlLoadFactor . This feature increases the uplink throughput of cells. To find out how much the uplink throughput of a cell has increased, track changes in the uplink throughput before and after this feature is activated. The following NodeB counters and RNC counters indicate the uplink throughput in a cell:

Issue 05 (2012-11-30)


4-5

WCDMA RAN HSUPA 


NodeB counters total number of bits in MAC-d protocol data units (PDUs) received from all UEs within a measurement period

− VS.HSUPA.Thruput:

− VS.HSUPA.MeanBitRate:

average bit rate of MAC-d data flows received from all UEs within a

measurement period − VS.HSUPA.MeanBitRate.WithData:

average bit rate of MAC-d data flows received from all UEs during data transmission within a measurement period



RNC counters − VS.HSUPA.MeanChThroughput:

mean uplink throughput of single HSUPA MAC-d flows in HSUPA cells in active set within a measurement period

− VS.HSUPA.MeanChThroughput.TotalBytes:

number of total bytes received in uplink of all the HSUPA MAC-d flows in a cell within a measurement period

After this feature is activated, the values of the preceding counters increase.

7.2.5 Troubleshooting Dual-Threshold Scheduling with HSUPA Interference Cancellation offers notable gains when the following conditions are met: 

Users have a high demand for uplink data transmission.



The Uu-interface load is restricted.



Board configurations meet the configuration requirements of this feature.



The value for MaxDeltaOfTargetRoT is greater than 0.

After this feature is activated, check the preceding items if uplink throughput gains fall short of expectations.

Issue 05 (2012-11-30)


4-6

WCDMA RAN HSUPA

8 Parameters

8 Parameters Table 8-1 Parameter description Parameter ID NE

DLGROUPN

MML Command Feature ID

NodeB ADD DLGROUP None

Feature Name

Description

None

Meaning:Indicates the DL BB Resource Group No.

MOD DLGROUP

GUI Value Range:0~5

RMV DLGROUP

Actual Value Range:0~5 Unit:None Default Value:None HSUPAOLSC NodeB HSWITCH

SET MACEPARA WRFD-0106 HSUPA 1209 HARQ and Fast UL Schedulin g in Node B

Meaning:Indicates the HSUPA overload scheduling switch. When this switch is turned on and the guaranteed bit rates (GBRs) of users are not met, the cell load will exceed the planned target and reach the congestion threshold, thereby guaranteeing users' GBRs. GUI Value Range:OPEN(open), CLOSE(close) Actual Value Range:OPEN, CLOSE Unit:None Default Value:OPEN(open)

LOADTHRES NodeB H4MINULCOV

SET MACEPARA WRFD-0201 Anti-Interf Meaning:Indicates the Min UL Cover 36 erence Load Threshold. Schedulin GUI Value Range:0~40 g for HSUPA Actual Value Range:0~40 Unit:dB Default Value:13

MAXDELTAOF NodeB TARGETROT

SET MACEPARA WRFD-0201 Dual-Thre Meaning:Indicates the max target 37 shold RoT difference before and after IC. Schedulin GUI Value Range:0~6 g with HSUPA Actual Value Range:0~3, step:0.5 Unit:0.5dB Default Value:0

MaxTargetUlLoBSC690 ADD Issue 05 (2012-11-30)

WRFD-0106 HSUPA

Meaning:The parameter specifies


4-1

WCDMA RAN HSUPA

8 Parameters

Parameter ID NE


Feature Name

Description

adFactor

UCELLHSUPA(O 1203 ptional)

Power Control

the target value of the uplink load. HSUPA power control on the NodeB side keeps uplink load close to the target value. For details about this parameter, refer to 3GPP TS 25.433.

0

MOD UCELLHSUPA(O ptional)

GUI Value Range:0~100 Actual Value Range:0~1 Unit:% Default Value:75 PcSwitch

BSC690 SET WRFD-0205 0 UCORRMALGOS 03 WITCH(Optional) WRFD-0205 04

Outer Loop Power Control

Meaning:Power control switch group.

1) PC_CFG_ED_POWER_INTERPOL Inner ATION_SWITCH: When the switch WRFD-0205 Loop is on, E-DPDCH power interpolation 02 Power formula is allowed. Otherwise, interpolation formula is not allowed. WRFD-0106 Control When the interpolation formula is 1203 Downlink used, E-TFCI and PO is involved in WRFD-0107 Power the calculation of transmit power for Balance 12 block transmission on the E-DPDCH. In addition, the WRFD-0201 HSUPA extrapolation formula is also used. Power 38 the interpolation formular is used for Control high-speed services, whereas the Adaptive extrapolation formula is used for Configurat low-speed services. For details, see ion of the 3GPP TS 25.214. Traffic Channel 2) PC_DL_INNER_LOOP_PC_ACTIV Power offset for E_SWITCH: When the switch is on, HSUPA the status of inner loop DL power control is set to "Active." When the HSUPA switch is not on, the status is set to Coverage "Inactive." Enhance ment at 3) UE power PC_DOWNLINK_POWER_BALAN limitation CE_SWITCH: When the switch is on, the RNC supports DL power balancing. During soft handover, TPC bit errors may cause DL power drift. DL power balancing is enabled to balance the DL power between links, thus achieving the optimal gain of soft handover.

Issue 05 (2012-11-30)


4-2

WCDMA RAN HSUPA

Parameter ID NE

8 Parameters


Feature Name

Description 4) PC_EFACH_ECN0_DYN_ADJ_SWI TCH: When the switch is on, the target value of Ec/N0 can be dynamically reconfigured on the E-FACH. When the switch is disabled, the minimum value of Ec/N0 is directly configured for the NodeB. 5) PC_FP_MULTI_RLS_IND_SWITCH : When the switch is on, the RNC informs the NodeB of the current RLS number through the FP inband signaling. 6) PC_HSUPA_COVER_EN_AT_POLI MIT_SWITCH: When the switch is on, the HSUPA Coverage Improvement Under Limited UE Power algorithm is used for the RNC. 7) PC_HSUPA_DATA_CH_PO_ADAP TIVE_ADJ_SWITCH: When the switch is on, the Power Offset Adaptive Adjustment on HSUPA Data Channel algorithm is used for the RNC. 8) PC_HSUPA_HARQNUM_AUTO_A DJUST_SWITCH: When the switch is on, the HSUPA service can use the smaller target number of retransmissions when the uplink is not congested. If the uplink is congested, the HSUPA service can use the typical target number of retransmissions. 9) PC_INNER_LOOP_LMTED_PWR_I NC_SWITCH: When the switch is on, the limited power increase function is used for DL inner loop power control. 10) PC_OLPC_SWITCH: When the switch is on, the RNC updates the UL SIR TARGET of radio links on

Issue 05 (2012-11-30)


4-3

WCDMA RAN HSUPA

Parameter ID NE

8 Parameters


Feature Name

Description the NodeB side through IUB DCH FP inband signaling. 11) PC_RL_RECFG_SIR_TARGET_CA RRY_SWITCH: When the switch is not on, a new initial SIRTarget value, during radio link reconfiguration, is based on the converged SIRTarget value of current outer loop power control. In addition, the UL SIRTarget value is not included in the radio link reconfiguration messages to the NodeB. This switch is only valid when the OLPC switch is ON. 12) PC_SIG_DCH_OLPC_SWITCH: When the switch is on, SIG DCH is involved in UL OLPC as service DCH is. If the current link has only SIG DCH, SIG DCH is always involved in UL OLPC. 13) PC_UL_SIRERR_HIGH_REL_UE_ SWITCH: When the switch is on, the UE is unconditionally released if the SIR error is high and the cell is overloaded. Otherwise, the UE is not released. GUI Value Range:PC_CFG_ED_POWER_INT ERPOLATION_SWITCH, PC_DL_INNER_LOOP_PC_ACTIV E_SWITCH, PC_DOWNLINK_POWER_BALAN CE_SWITCH, PC_EFACH_ECN0_DYN_ADJ_SWI TCH, PC_FP_MULTI_RLS_IND_SWITCH , PC_HSUPA_COVER_EN_AT_POLI MIT_SWITCH, PC_HSUPA_DATA_CH_PO_ADAP TIVE_ADJ_SWITCH, PC_HSUPA_HARQNUM_AUTO_A DJUST_SWITCH, PC_INNER_LOOP_LMTED_PWR_I NC_SWITCH, PC_OLPC_SWITCH, PC_RL_RECFG_SIR_TARGET_CA RRY_SWITCH,

Issue 05 (2012-11-30)


4-4

WCDMA RAN HSUPA

8 Parameters

Parameter ID NE


Feature Name

Description PC_SIG_DCH_OLPC_SWITCH, PC_UL_SIRERR_HIGH_REL_UE_ SWITCH Actual Value Range:PC_CFG_ED_POWER_INT ERPOLATION_SWITCH, PC_DL_INNER_LOOP_PC_ACTIV E_SWITCH, PC_DOWNLINK_POWER_BALAN CE_SWITCH, PC_EFACH_ECN0_DYN_ADJ_SWI TCH, PC_FP_MULTI_RLS_IND_SWITCH , PC_HSUPA_COVER_EN_AT_POLI MIT_SWITCH, PC_HSUPA_DATA_CH_PO_ADAP TIVE_ADJ_SWITCH, PC_HSUPA_HARQNUM_AUTO_A DJUST_SWITCH, PC_INNER_LOOP_LMTED_PWR_I NC_SWITCH, PC_OLPC_SWITCH, PC_RL_RECFG_SIR_TARGET_CA RRY_SWITCH, PC_SIG_DCH_OLPC_SWITCH, PC_UL_SIRERR_HIGH_REL_UE_ SWITCH Unit:None Default Value:None

SPI

BSC690 SET WRFD-0208 Differentia Meaning:Scheduling priority of 0 USPIWEIGHT(M 06 ted interactive and background andatory) Service services. Value 11 indicates the Based on highest priority, while value 2 SPI indicates the lowest priority. Values Weight 0, 1, 12, 13, 14, and 15 are reserved for the other services. GUI Value Range:0~15 Actual Value Range:0~15 Unit:None Default Value:None

SpiWeight

BSC690 SET WRFD-0208 Differentia Meaning:Specifies the weight for 0 USPIWEIGHT(Op 06 ted service scheduling priority. This tional) Service weight is used in two algorithms. In Based on scheduling algorithm, it is used to SPI adjust the handling priority for

Issue 05 (2012-11-30)


4-5

WCDMA RAN HSUPA

8 Parameters

Parameter ID NE


Feature Name

Description

Weight

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 Unit:% Default Value:100

ULGROUPN

NodeB ADD ULGROUP None MOD ULGROUP RMV ULGROUP

None

Meaning:Indicates the UL BB Resource Group No. GUI Value Range:0~5 Actual Value Range:0~5 Unit:None Default Value:None

Issue 05 (2012-11-30)


4-6

WCDMA RAN HSUPA

9 Counters

9 Counters Table 9-1 Counter description Counter ID Counter Name

Counter Description

NE

Feature ID

Feature Name

50331850

VS.HSUPA.Lo Number of Cell Ul Load adOutput.0 Between 0db to 0.5db

NodeB

WRFD-010612 HSUPA Introduction Package

50331851

VS.HSUPA.Lo Number of Cell Ul Load adOutput.1 Between 0.5db to 1db

NodeB


50331852

VS.HSUPA.Lo Number of Cell Ul Load NodeB adOutput.2 Between 1.0db to 1.5db


50331853


NodeB


50331854



50331855



50331856



50331857


NodeB


50331858

VS.HSUPA.Lo Number of Cell Ul Load adOutput.8 Between 4db to 5db

NodeB


50331859


NodeB


50331860


NodeB


50331861


NodeB


50331862


NodeB


50331863


NodeB


Issue 05 (2012-11-30)


4-1

WCDMA RAN HSUPA

Counter ID Counter Name

9 Counters

Counter Description

NE

Feature ID

Feature Name

50331864


NodeB


50331865


NodeB


50331866


NodeB


50331867


NodeB


50331868


NodeB


50331869


NodeB


50331870


NodeB


50331871


NodeB


50331872


NodeB


50331873


NodeB


50331874


NodeB


50331875

VS.HSUPA.Lo Number of Cell Ul Load adOutput.25 above 30db

NodeB


50331876

NodeB VS.HSUPA.Ov Number of times the erLoadNum uplink is overloaded in a cell


50331877

VS.HSUPA.Un Number of Unhappy HappyUserNu HSUPA users in a cell m

NodeB

WRFD-010612 HSUPA Introduction Package WRFD-0106121 1 20 HSUPA Users per Cell

Issue 05 (2012-11-30)


4-2

WCDMA RAN HSUPA


9 Counters

Counter Description

NE

Feature ID

Feature Name

WRFD-010634 60 HSUPA Users per Cell WRFD-010639 96 HSUPA Users per Cell 50331878

VS.HSUPA.Us Number of TTIs in which NodeB erTtiNum at least one HSUPA user exists in a cell


50331879

VS.HSUPA.Da Number of TTIs in which NodeB taTtiNum HSUPA users transmit data in a cell


50331885

VS.HSUPA.AC Number of transmitted KTotal ACKs

NodeB


50331886

VS.HSUPA.NA Number of transmitted CKTotal NACKs

NodeB


50331887

VS.HSUPA.DT Number of transmitted XTotal DTXs

NodeB


50331888

VS.HSUPA.PD Number of successfully UNum received MAC-e PDUs from the UE in a cell

NodeB


50331889

VS.HSUPA.Re Number of MAC-e PDUs NodeB transPDUNum to be retransmitted by the UE in a cell


50331903

VS.HSUPA.A Max value of AGCH GCHCodeUtil. usage ratio Max

NodeB

WRFD-0106140 Enhanced Fast UL 2 Scheduling

50331904

VS.HSUPA.A Max value of AGCH GCHCodeColli Collision ration sion.Max

NodeB


50331908

VS.HSUPA.Da Number of TTIs in which NodeB taTtiNum.TRB HSUPA users transmit TRB data in a cell


50332378

VS.HSUPA.Tr HSUPA MAC-d TRB data NodeB

WRFD-010612 HSUPA Introduction

Issue 05 (2012-11-30)


4-3

WCDMA RAN HSUPA

Counter ID Counter Name affic.TRB

9 Counters

Counter Description

NE

Feature ID

volume in the cell

Feature Name Package

50332551

VS.HSUPA.Th Total traffic volume of ruput HSUPA users in a cell

NodeB


50341849

VS.HSUPA.Un Ratio of the number of NodeB HappyUserNu Unhappy HSUPA users to mRatio the total number of HSUPA users in a cell

WRFD-010612 HSUPA Introduction Package WRFD-0106121 1 20 HSUPA Users per Cell WRFD-010634 60 HSUPA Users per Cell WRFD-010639 96 HSUPA Users per Cell

50341850

VS.HSUPA.Da Average number of taUserNum.M HSUPA users that ean transmit data in a cell

NodeB


50341851

VS.HSUPA.Da Maximum number of taUserNum.M HSUPA users that ax transmit data in a cell

NodeB


50341852

NodeB VS.HSUPA.Sc Average number of heduleUserNu scheduled HSUPA users m.Mean in a cell

WRFD-010612 HSUPA Introduction Package WRFD-0106140 2 Enhanced Fast UL Scheduling

50341853

NodeB VS.HSUPA.Sc Maximum number of heduleUserNu scheduled HSUPA users m.Max in a cell

WRFD-010612 HSUPA Introduction Package WRFD-0106140 2 Enhanced Fast UL Scheduling

50341855

VS.HSUPA.Lef Ratio of the number of NodeB tPwrLmtUserR HSUPA users with limited atio uplink load to the total number of HSUPA users in a cell

Issue 05 (2012-11-30)

WRFD-0106120 HSUPA Admission 2 Control

WRFD-0106140 Enhanced Fast UL


4-4

WCDMA RAN HSUPA


9 Counters

Counter Description

NE

Feature ID

Feature Name

2

Scheduling

50341864

VS.HSUPA.A average number of GCHCodeColli AGCH collision ratio sion.Mean

NodeB


50341865

VS.HSUPA.A average number of GCHCodeUtil. AGCH usage ratio Mean

NodeB


50341866

VS.HSUPA.An The anti-intereference tiInterfSch.Act scheduling algrithm Ratio active ratio

NodeB

WRFD-020136 HSUPA anti-interference schdeduling

50342552

VS.HSUPA.Me Average throughput of anBitRate HSUPA users in a cell

NodeB


50342553

VS.HSUPA.Me Average throughput of NodeB anBitRate.Wit HSUPA users in a cell hData when data is transmitted


67192110

VS.HSUPA.M Number of Successful ACD.SuccSet EDCH MAC-d Flow up Establishments for Cell

67192486

BSC6900 WRFD-010612 HSUPA Introduction VS.HSUPA.Me Number of Total Bytes anChThrough Received in Uplink of Package put.TotalBytes HSUPA MAC-d Flow for Cell

67192978

VS.RAB.RelR eqPS.BE.HSU PA.Cong.Gold en

Number of HSUAP RABs BSC6900 WRFD-010612 HSUPA Introduction Carrying Golden Users Package WRFD-020107 BE Traffic Released Due Overload Control to Congestion for Cell

67192979

VS.RAB.RelR eqPS.BE.HSU PA.Cong.Silve r

Number of HSUPA RABs BSC6900 WRFD-010612 HSUPA Introduction Carrying Silver Users BE Package WRFD-020107 Traffic Released Due to Overload Control Congestion for Cell

67192980

VS.RAB.RelR Number of HSUAP RABs BSC6900 WRFD-010612 HSUPA Introduction eqPS.BE.HSU Carrying Copper Users Package WRFD-020107 PA.Cong.Copp BE Traffic Released Due Overload Control er to Congestion for Cell

67193599

VS.HSUPA.UE Maximum Number of .Max.CAT1.4 HSUPA UEs with

Issue 05 (2012-11-30)

BSC6900 WRFD-010612 HSUPA Introduction Package

BSC6900 WRFD-0106120 HSUPA UE Category 1 1 to 7


4-5

WCDMA RAN HSUPA


9 Counters

Counter Description

NE

Feature ID

Feature Name

Category1-4 in a Cell 67193602

VS.HSUPA.UE Maximum Number of .Max.CAT5 HSUPA UEs with Category 5 in a Cell


67193605



67193608



67203850

VS.HSUPA.UE Average Number of .Mean.Cell HSUPA UEs in a Cell

BSC6900 WRFD-0106121 20 HSUPA Users per 1 Cell WRFD-010634 60 HSUPA Users per Cell WRFD-010639 96 HSUPA Users per Cell

67203932

VS.HSUPA.Me Mean Uplink Throughput BSC6900 WRFD-010612 HSUPA Introduction anChThrough of single HSUPA MAC-d Package put Flow for Cell

67204266

VS.HSUPA.UE Average Number of .Mean.CAT1.4 HSUPA UEs with Category 1-4 in a Cell


67204267

VS.HSUPA.UE Average Number of .Mean.CAT5 HSUPA UEs with Category 5 in a Cell


67204268



67204269



73393829

VS.HSUPA.M Number of EDCH MAC-d BSC6900 WRFD-010612 HSUPA Introduction ACD.AttSetup Flow Setup Requests for Package Cell

73393956

VS.HSUPA.Rs Number of Times that nSmall2Large. HSUPA 2ms TTI Users

Issue 05 (2012-11-30)

BSC6900 WRFD-010641 HSUPA Adaptive


4-6

WCDMA RAN HSUPA

Counter ID Counter Name TTI2ms

9 Counters

Counter Description

NE

Feature ID

Transfer from Small Retransmission to Large Retransmission for Cell

Feature Name Transmission

73393957

BSC6900 WRFD-010641 HSUPA Adaptive VS.HSUPA.Rs Number of Times that nSmall2Large. HSUPA 10ms TTI Users Transmission TTI10ms Transfer from Small Retransmission to Large Retransmission for Cell

73393958

BSC6900 WRFD-010641 HSUPA Adaptive VS.HSUPA.Rs Number of Times that nLarge2Small. HSUPA 2ms TTI Users Transmission TTI2ms Transfer from Large Retransmission to Small Retransmission for Cell

73393959

VS.HSUPA.Rs Number of Times that BSC6900 WRFD-010641 HSUPA Adaptive nLarge2Small. HSUPA 10ms TTI Users Transmission TTI10ms Transfer from Large Retransmission to Small Retransmission for Cell

73410500

VS.SRNCIubB Number of UL Bytes over BSC6900 WRFD-010612 HSUPA Introduction ytesHSUPA.R Iub EDCH for Cell Package x

Issue 05 (2012-11-30)


4-7

WCDMA RAN HSUPA

10 Glossary

10 Glossary For the acronyms, abbreviations, terms, and definitions, see the Glossary .

Issue 05 (2012-11-30)


4-1

HSUPA(RAN13.0_05)

Recommend Documents