zte umts (u9.3) hsupa packet scheduling feature guide_v4.0

Operator Logo

HSUPA Packet Scheduling WCDMA RAN

Feature Guide

HSUPA Packet Scheduling Feature Guide

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. I


Version Date Author Approved By Remarks

V4.0 2010-6-13 Wang Yue Peng Bei, Hu Ye June 30th

Version update

© 2010 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used without the prior written permission of ZTE.

Due to update and improvement of ZTE products and technologies, information in this document

is subjected to change without notice.


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. II

TABLE OF CONTENTS

1 Functional Attribute ............................................................................................1

2 Overview .............................................................................................................1 2.1 Function Introduction ............................................................................................1 2.1.1 HSUPA Fast Scheduling .......................................................................................2 2.1.2 HSUPA Flow Control ............................................................................................6

3 Technical Description .........................................................................................6 3.1 HSUPA Scheduling Algorithm ...............................................................................6 3.1.1 Features of Fast Scheduling .................................................................................6 3.1.2 Description of Packet Scheduler............................................................................7 3.1.3 Key Algorithms of Packet Scheduler ......................................................................8 3.1.4 CPC affection on HSUPA packet scheduling ........................................................15 3.2 HSUPA Flow Control Algorithm ...........................................................................16 3.2.1 E-DCH Uplink Congestion Control .......................................................................16 3.2.2 Back-pressure Flow Control ................................................................................18

4 Parameters and Configuration ..........................................................................22 4.1 Parameter List ...................................................................................................22 4.2 Parameter Configuration .....................................................................................22 4.2.1 E-DCH Uplink Nominal Bit Rate ........................................................................22 4.2.2 Maximum Target Received Total Wideband Power(dB) ........................................23 4.2.3 Target Non-serving E-DCH to Total E-DCH Power Ratio(%) .................................23 4.2.4 Maximum Number of Retransmissions for E-DCH ................................................24 4.2.5 Support Congestion Detection Indicator ...............................................................24 4.2.6 Transport Time Delay .........................................................................................24 4.2.7 Transport Time Jitter ..........................................................................................24 4.2.8 R_IPPARA Bandwidth ........................................................................................25 4.2.9 SPI_WEIGHT ( 0~15) .........................................................................................25

5 Counter And Alarm ...........................................................................................26 5.1 Counter List .......................................................................................................26 5.2 Alarm List ..........................................................................................................26

6 Glossary ...........................................................................................................26


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. III

FIGURES

Figure 1 HSUPA protocol architecture in UTRAN ..................................................................2

Figure 2 MAC-e functions ....................................................................................................2

Figure 3 Basic operating principle of HSUPA .........................................................................4

Figure 4 HSUPA fast scheduling mechanism in Node B .........................................................7

Figure 5 Operating mechanism of HSUPA packet scheduler ..................................................9

Figure 6 HSUPA scheduling procedure in Node B .................................................................9

Figure 7 Congestion processing procedure of scheduler ......................................................18

Figure 8 HSUPA flow control mechanism in Node B ............................................................18

Figure 9 lub interface bandwidth allocation in Node B ..........................................................19

Figure 10 Back-pressure control procedure of HSUPA scheduler ...........................................20

TABLES

Table 1 SPI_WEIGHT( 0~15)mapping table .......................................................................25


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 1

1 Functional Attribute

System version: [RNC V3.09, Node B V4.09, OMMR V3.09, OMMB V4.09]

Attribute: [Optional]

Involved NEs:

MS Node B RNC MSC MGW SGSN GGSN HLR

√ √ √ - - - - -

Note:

*-: Not involved. *√: Involved.

Dependency: [None]

Mutual exclusion: [None]

Remarks: [None]]

2 Overview

2.1 Function Introduction

The High Speed Uplink Packet Access (HSUPA) is a technology used in WCDMA to enhance uplink transmission capability.

HSUPA technology features shorter Transmission Time Interval (TTI), Node B-based scheduler and Hybrid Automatic Retransmission Request (HARQ), and new transport channel-Enhanced Dedicate Channel (E-DCH).

The adoption of the HSUPA technology brings the following advantages to the WCDMA system:

Obvious improvement over conventional WCDMA in terms of uplink service

transmission performance.

The WCDMA system adopting the HSUPA technology consists of the Radio Network Controller (RNC), Node B and User Equipment (UE). Node B contains several cells

which are a type of public radio resource serving UEs in the same area. The uplink load of system can be measured through cells in HSUPA. The UE scheduling by Node B is cell-based. The HSUPA technology leaves service control and scheduling functions to

Node B. Node B sends different grants to UE based on service scheduling information, buffer occupancy status, service priority, UE Uplink Power Headroom (UPH), cell uplink interference and load, and Node B processing capacity. UE sends data in response to

the grants from Node B.



The HSUPA packet scheduler contains two parts: HSUPA fast scheduling and flow control, which are respectively detailed as follows:

2.1.1 HSUPA Fast Scheduling

The HSUPA scheduler is located at Node B, as defined in 3GPP. Benefiting from close proximity to air interface, the HSUPA scheduler can obtain measurement infor mation about uplink interference in time, thus achieving fast control over uplink data rate.

Figure 1 shows the HSUPA protocol architecture in UMTS Terrestrial Radio Access Network (UTRAN).

Figure 1 HSUPA protocol architecture in UTRAN

MAC-d

MAC-es/MAC-e

PHY

MAC-e

PHY

MAC-d

EDCH FP

TNLTNL

EDCH FP

TNL TNL

MAC-es

DTCH DCCH DTCH DCCH

Uu Iub Iur

UE NODEB DRNC SRNC

Compared with R99, the functional changes of all protocol entities in HSUPA are as follows:

UE: New MAC entity (MAC-es/MAC-e) is added under MAC-d. MAC- es/MAC-e

implements such functions as HARQ, scheduling, MAC-e multiplexing and E-DCH

TFC selection.

Node B: MAC-e is added.

SRNC: MAC-es is added. MAC- es implements re-sequence and data combination

of different Node Bs in the case of soft handover.

Figure 2 shows the protocol block diagram of MAC-e (Node B side) where the HSUPA scheduler is located.

Figure 2 MAC-e functions



MAC-e

MAC – Control

E-DCH

Associated Downlink

Signalling

Associated Uplink

Signalling

MAC-d Flows

De-multiplexing

HARQ

E-DCH

Control (FFS)

E-DCH Scheduling (FFS)

The functions of various modules of MAC-e (Node B side) are described as follows:

E-DCH scheduling: Manage E-DCH among UEs. Determine and transmit grants

based on scheduling request.

Demultiplexing: Provide demultiplexing of MAC-e PDUs. Send MAC-es PDUs to

MAC-d stream.

HARQ: One HARQ entity supports several Stop-and-Wait (SAW) HARQ process

instances. Each HARQ process generates ACKs or NACKs to indicate the transmit

status of E-DCH. The HARQ used in HSUPA is a multi-channel SAW concurrent

retransmission mechanism. The HARQ supports several HARQ processes, each of

which transmits data packets in sequence. For one UE, there is only one HARQ

process transmitting data at one moment. If Node B receives a data packet from

one HARQ process and the Cyclic Redundancy Check (CRC) is passed, Node B

will return a correct decoding indication (ACK); otherwise, it will return a block error

indication (NACK). If UE receives a NACK message, the related HARQ process

needs to retransmit the data packet at physical layer; if UE receives an ACK

message, the related HARQ process can transmit a new data packet. At the same

time, other HARQ processes can each transmit different data packets, irrespective

of whether the HARQ process receives ACK/NACK message. The adoption of

multi-channel HARQ lowers waiting time of SAW protocol and enhances

transmission rate. 3GPP defines 8 and 4 HARQ processes respectively for UE with

2ms and 10ms Transmission Time Intervals (TTIs) in HSUPA.

E-DCH Control: Receive scheduling information and transmit grants.

The following figure shows the basic operating principle of HSUPA

technology:



Figure 3 Basic operating principle of HSUPA

SRNC DRNC

MAC-es FP

MAC-d

NodeBs Iur/Iub FP

Scheduler

MAC-e

NodeBd FP

MAC-e

UE

MAC-e/ MAC-es

MAC-d

DTCHs

E-DPDCH E-DPCCH

E-AGCH (Absolute Grants, "E-RNTI" -> UE)

serving cell

E-HICH (ACK/NACKs) E-RGCH (relative grants) (ChCode, signature -> UE)

MRC MRC

1 TNL bearer per MAC-d flow

Iur/Iub FP

The above figure shows the connection relation between UTRAN and UE that uses E-DCH and stays in soft handover state, as well as HSUPA -related protocol entities on UE and network sides. The basic concept and operating principle of HSUPA are described

as follows:

E-DCH active set: The set of cells which carry the E-DCH for one UE. .It can be a

subset of DCH active set.

Serving E-DCH cell: Refers to the cell from which the UE receives the absolute

grants. UE only has one E-DCH serving cell. The serving cell change is triggered

when UE reports event 1D triggered by downlink pilot channel quality.

Serving E-DCH RLS or Serving RLS: Set of Cells which contains at least the

Serving E-DCH cell and from which the UE can receive and combine one Relative

Grant. The UE has only one Serving E-DCH RLS.

Non-serving E-DCH RL or Non-Serving RL: Cell which belongs to the E -DCH active

set but does not belong to the Serving E-DCH RLS and from which the UE can

receive one Relative Grant. The Ue can have zero, one or several Non-serving E-

DCH RL(s).



The HSUPA technology is mainly characterized by Node B-controlled scheduling, with procedure described as follows:

UE has one Serving E-DCH cell. The Node B where the Serving E-DCH cell is

located implements E-DCH scheduling. The Serving E-DCH cell sends scheduling

instruction, that is, absolute grant, to UE over downlink E-AGCH. The absolute grant

stipulates the absolute value of the maximum available resources for UE.

The Serving E-DCH cell and non-serving E-DCH cell sends relative grant to UE

over downlink E-RGCH. As a fine tuning of the absolute grant, the relative grant can

take one of the three values: UP, DOWN and HOLD, instructing the UE to increase,

decrease or not change the power limitation. Only the Serving E-DCH RLS can

send UP message and Non-Serving E-DCH RLS can only send HOLD or DOWN

message. Generally Non-Serving E-DCH RLS sends a DOWN message as a result

of uplink overload.

RNC may configure a percentage threshold (non-serving RL E-DCH received

power/total E-DCH received power) for Node B over physical shared channel

reconfiguration. Node B stores this threshold and uses it to control E-DCH

scheduling to ensure the power proportion of non-serving RL E-DCHs to all E-DCH

received in the cell does not exceed this threshold. Node B decreases the power of

non-serving RL UE by sending a DOWN message to UE.

UE performs E-TFC selection based on the grant information received, sends data

(including retransmitted data) on E-DPDCH and sends E-TFC information, HARQ

RV information (RSN) and one Happy Bit on E-DPCCH. The Happy bit is used to

notify Node B whether UE is satisfied with currently assigned resources (grant), that

is, whether UE needs higher grants.

The E-DCH collects E-DCH data received by different cells under the same Node B

for MRC combination and sends it to Mac -e. Each UE has one MAC-e in every

Node B. MAC-e demultiplexes MAC-e PDUs into MAC-es PDUs before sending

them to RNC. Mac-e also sends E-DCH scheduling messages as well as HARQ

ACK/NACK.

Each UE has one Mac-es entity in SRNC. Mac-es performs macro diversity

combination of MAC-es PDUs from different Node Bs and re-sequences and

disassembles them into Mac-d PDUs before sending them to Mac-d.

Handling of different grants by UE: UE may receive the AGs and RGs from the

serving cell as well as RG DOWN from non-serving cell at the same time. According

to 3GPP TS 25.321, when a UE receives grants from both serving and non-serving

E-DCH RLSs simultaneously, the Scheduling Grant (SG) of UE is set to the smaller

one of SGs calculated from non-serving and serving E-DCH RLS.

Resource recycling: If the scheduler finds the maximum LUPR (LUPRmax) of UE in

a past specified period (an internal parameter) is less than SG, it will update SG to

LUPRmax.



The HSUPA fast scheduling control function makes quick response to service requirements of all UEs in a cell, cell uplink interference and Node B processing load; assigns SGs for all UEs; notifies UEs of available SGs by sending AGs or RGs to UEs.

UEs transmit data using the data rate and power allowed by SGs.

2.1.2 HSUPA Flow Control

The data volume of different users constantly changes on the HSUPA uplink traffic

channel, and dedicated flow control mechanism is absent at L2. Therefore, an upper-layer flow control mechanism is necessitated to ensure multiple UEs to share lub bandwidth.

When the realtime rate of services carried on E-DCH is high, packet out-of-sequence, loss or delay may occur due to problems at transport layer. SRNC needs to detect any of these situations, and informs Node B of the congestion so as to lower realtime rate of

UE, alleviate congestion and avoid impact on other services.

HSUPA flow control contains two parts:

RNC sends a TNL CONGESTION INDICATION message to scheduler. Upon receiving

the TNL CONGESTION INDICATION message, the scheduler restricts grants to UE.

The main control module of Node B measures traffic on lub interface, and sends bandwidth utilization to the scheduler. The scheduler decides whether to restrict grants

so as to lower traffic on lub interface based on the bandwidth utilization.

3 Technical Description

3.1 HSUPA Scheduling Algorithm

3.1.1 Features of Fast Scheduling

The HSUPA fast scheduling features the following:

Node B-based fast scheduling.

The HSUPA scheduler is located at Node B, facilitating the scheduler to obtain

more realtime information about uplink interference and perform faster control over uplink data rate.

Support fast HARQ with soft combining

HARQ transmits ACK/NACK on E -HICH to UE based on whether E -DPDCH deco

ding succeeds in each TTI. If decoding succeeds, HARQ sends MAC-e PDUs for demultiplexing. If decoding fails, HARQ will wait for retransmission and combine the retransmission data. Combining methods include chase combining and incremental

redundancy. Combining methods are decided by parameter HARQ RV Configuration,which is configured to Node B by RNC through NBAP IE HARQ Info for E-DCH(refer to ZTE UMTS HSUPA Introduction Feature Guide). If



retransmission reaches the maximum retransmission times, HARQ sends an HARQ Failure message to RNC through FP. RNC defines an HARQ profile for each MAC-d flow of UE. Each HARQ profile contains the parameter Maximum Number of

Retransmissions for E-DCH (MaxRetransEdch), which is set at OMMR based on service type. For details, refer to ZTE UMTS Power Control Feature Guide.

Support 10 ms and 2 ms TTIs.

The HSUPA scheduler supports 2 ms and 10 msTTIs. Compared with 10 ms TTI, 2 ms TTI enables a significant reduction of transmission delays. The interleaving processing gain is higher and the maximum rate is lower in 10 ms TTI compared to

2 ms TTI, and therefore, cell edge coverage can be ensured. For service rate higher than 2Mbps, only 2ms TTI can be used. The terminal type and transmit power restrict the maximum uplink data rate of UE. RNC selects a specific type of TTI

based on UE capability and subscribed rate. That is, for higher subscribed rate (2886000bps and above), select 2 ms TTI (provided UE supports 2 ms TTI; otherwise, select 10 ms TTI); for lower subscribed rate, select 10 ms TTI, and TTI

will not switch at cell edge.

Support CPC (Continuous Packet Connectivity) technical function introduced from

R7

CPC technical function introduced from R7 includes UL DTX, DL DRX and UL DRX in Node B. Thereinto, UL_DTX mainly affects HSUPA packet scheduling. UL DTX(Discontinuous Transmission) on uplink E-DPCCH can decrease cell uplink

interference, thus bringing uplink capacity gain and saving UE power consumption and extending UE standby time.

3.1.2 Description of Packet Scheduler

The HSUPA fast scheduler contains three parts: HSUPA packet scheduling, uplink processing and downlink processing, as shown in the following figure.

Figure 4 HSUPA fast scheduling mechanism in Node B

UE

HSUPA

SchedulerE-RGCH

E-AGCH

E-HICH

Downlink

E-DCHDe-mux HARQ

Associated

Uplink Schedule

Information

RNC

ACK/

NACK

Uplink Processing

AG

RG

NodeB

Uu

Uu

Uu

Uu

lub

Uplink processing: Implements such functions as transport layer processing,

HARQ, MAC-e PDU demultiplexing and Frame Protocol (FP). The uplink data from



UE is sent to Node B over UU interface. Upon detecting the signal, Node B

performs transport layer processing including descrambling and despreading. The

E-DCH data packets and uplink-related Scheduling Information (SI) are obtained

after transport layer processing. E-DCH data packets are sent to HARQ at MAC-e

layer for combining into MAC-e PDUs. At the same time, HARQ generates ACK or

NACK indication based on combining results and sends it to UE on downlink E-

HICH. MAC-e PDUs are sent to demultiplexing entity for demultiplexing into MAC-

es PDUs, and then sent to MAC-es layer of RNC over lub interface for further

processing.

HSUPA packet scheduling: The HSUPA packet scheduler offers a function that

meets uplink service requirements of all UEs in Node B by utilizing such information

as uplink load, UE service requirements and Node B processing capacity in

WCDMA system. The scheduler describes and classifies uplink service

requirements of UEs based on their urgency and priority. Then it allocates different

resources for UEs by means of fast control and scheduling to meet varied uplink

service requirements of UEs while ensuring effective utilization of uplink radio

resources.

Downlink processing: Implements coding of AG and RG/HI.

The functions of all above modules are implemented in EBBUB/BBUB. Each UE has one MAC-e entity in Node B. Each local cell group is configured with an HSUPA scheduler. The HSUPA scheduling is cell-based.

3.1.3 Key Algorithms of Packet Scheduler

The HSUPA packet scheduler determines system resource utilization and load based on the following information, and then allocates system resources to different UEs by

following certain priority policy:

Uplink Reference Received Total Wide Band Power (RefRTWP) configured by RNC

through NBAP. (refer to ZTE UMTS Admission Control Feature Guide).

Maximum Target Received Total Wideband Power (MaxRTWP) (refer to ZXWR

RNC Radio Network Controller Radio Parameter Reference (Volume II )).

Target Non-serving E-DCH to Total E-DCH Power Ratio (NServToTotalPwr) (refer

to ZTE UTMS Overload Control Feature Guide).

UE reported status information.

UE QoS configured by RNC through NBAP.

Cell radio resources.

Node B resource processing resources information.



The operating mechanism of the HSUPA packet scheduler is shown as follows:

Figure 5 Operating mechanism of HSUPA packet scheduler

HSUPA

PS Scheduler

RNC->:

MaxRTWP, RefRTWP

NServToTotalPwr

NodeB->:RTWPcurrent,

CE resource

UE->: SI, HappyBit

UE:AG, RG,

RNC->: UE QoS parameters：

SPI，GBR，

Non-scheduled BitRate

Uplink processing uni t ->:

E-TFCI, Eb/No，DPCCH SIR

The following figure shows the HSUPA scheduling procedure:

Figure 6 HSUPA scheduling procedure in Node B

Update information of UEs ,radio resource of cell and Node B process resource information

Determine the resource and load of contributed by the UEsand the radio resource of radio interface and used

resource of Node B

Determine the schedule priority of UEs in a HSUPA cell

Allocation the available system resource according to the schedule priority, from high priority to low priority



The key algorithm of the scheduler implements scheduling in the following steps:

1 Collect and update UE status, cell radio resource and Node B processing information.

Collected information includes:

The SI reported by UE (including SI and happy bit, used to obtain buffer area size and UPH of UE).

E-TFCI currently used by UE and MAC-e PDU multiplexing information

(contained in MAC-e PDU head and used to obtain the type of MAC-e PDU currently sent by UE and data volume).

Current DPCCH and E-DCH signal quality of UE (SIR and Eb/No, reported by

the Baseband Processing Unit and used to calculate UE-contributed load. The SIR Filter Period (40ms) is an internal parameter that cannot be configured. For details, refer to ZTE UMTS Node B Interface Parameter Description).

QoS parameter configured by RNC for UE services: Scheduling Priority Indicator (SPI) (This parameter is configured for Node B by RNC based on the service type through NBAP. For details, refer to ZTE UMTS QoS Feature

Guide).

QoS parameter configured by RNC for UE services: MAC-es Guaranteed Bit Rate (This parameter is configured for Node B by RNC based on the service type through NBAP. For details, refer to ZTE UMTS QoS Feature Guide).

QoS parameter configured by RNC for UE services: Maximum Number of Bits per MAC-e PDU for Non-scheduled Transmission (The independent data transmission capability obtained by UE without scheduling. This parameter is

configured for Node B by RNC based on the service type through NBAP).

Cell interference information (RTWPcurrent is measured at Node B).

CE resource indication.

Reference Received Total Wide Band Power (RefRTWP), Maximum Target

Received Total Wideband Power (MaxRTWP), Target Non-serving E-DCH to Total E-DCH Power Ratio (NServToTotalPwr) configured by RNC through NBAP.

2 Determine UE, air interface and Node B resource utilization and load:

The measurement unit of Node B measures air interface interference, and sends the measurement result RTWPcurrent to the scheduler. The scheduler

calculates current cell load Cell_Load_current and maximum target load Cell_Load_max (unit: %) through the following equations:

RoT = Itotal/Pn (1)

Cell_Load_current = 1–1/RoT (2)

Cell_Load_max = 1–1/(MaxRTWP /Pn) (3)



Where,

Itotal refers to the total receive bandwidth power inclusive of background noise power (unit: mW) and takes the value of RTWPcurrent. The RTWP Filter Period (40 ms) is an

internal parameter and cannot be configured. For details, see Node B Interface Parameter Description.

Pn refers to background noise and takes the value of RefRTWP (Reference

Received Total Wide Band Power). The original unit of Pn is dBm and translated into mW in the above equation. RNC notifies of Node B of Pn through NBAP after internal measurement.

MaxRTWP refers to the Maximum Target Received Total Wideband Power. The original unit of MaxRTWP is dBm and translated into mW in the above equation. MaxRTWP is configured at combining and sent to Node B by RNC through NBAP.

RoT refers to Rise over Thermal. The original unit of RoT is dB, and converted into dimensionless ratio during calculation.

The scheduler calculates UE-contributed load by using the following method:

The Uplink Process Unit of Node B demodulates E-DPDCH in each TTI to obtain

MAC-e PDU, SI and Eb/No, and sends MAC-e PDU multiplexing information to the scheduler which calculates UE-contributed load in the following equation:

UEload = 1/(1+(W/((Eb/No)R))) (4)

Where,

Itotal refers to the total receive bandwidth power inclusive of background noise power (unit: mW) and takes the value of RTWPcurrent.

W refers to WCDMA chip rate and equals to 3.84M chips/s.

Eb/No refers to per bit signal energy divided by noise power spectral density, and reflects service signal quality. It is dimensionless

R refers to the bit rate of UE (unit: bits/s).

3 Determine UE scheduling priority in HSUPA cell.

The HSUPA scheduler adopts the Enhanced Proportional Fair (PF) Algorithm, and

calculates scheduling priority which is a variable for each UE based on realtime collected parameters, so as to ensure traffic fairness among UEs and make full use of system resources as well. The PF algorithm features the following:

The scheduling priority is in direct proportion to current uplink to-be-transmitted data volume (or current available transmission rate), that is, the larger the data volume in the buffer area of UE, the higher the scheduling priority and the more

chance the UE will be scheduled preferentially.

The scheduling priority is in reverse proportion to the uplink average throughput (or history throughput) of UE, that is, the lower the average

throughput, the higher the scheduling priority. The UE with low t ransmission throughput will be scheduled preferentially so as to ensure fairness.



UEs with higher scheduling priorities will take precedence over UEs with lower ones in preempting more resources, resulting in rate decrease for the latter. But UEs originally with lower scheduling priorities are given higher scheduling priorities

because of their low transmission throughput, and thus they will be scheduled preferentially to ensure fairness among all UEs.

The specific calculation procedure of scheduling priority is as follows:

At first, the average uplink throughput Rn obtained by UE m (the mth

UE) before n TTI(s) (n refers to current time).

The uplink throughput offered for UEs in past TTIs can be updated for all UEs in each TTI by using the recursive expression:

If services are offered for UE m:

Rn = (1-a)Rn-1 + aDn (5)

Other cases:

Rn = (1-a)Rn-1 (6)

Where,

Rn-1 refers to the value of Rn in last TTI (Unit: bits/s).

R0 refers to the uplink rate of UE at initial moment (Unit: bits/s).

Dn refers to available uplink transmission rate of UE (Unit: bits/s), and takes the smallest one of the following values: Data size in UE buffer area, size of data that

can be transmitted in relation to the rest power of UE, and maximum rate limit of UE.

n refers to the nth

transmission moment.

m refers to the mth

UE.

a refers to forgetting factor. 1/a indicates the tolerability when a UE group cannot receive data. It is an internal parameter and cannot be configured.

Then calculate the scheduling priority of all UEs in a cell:

Priority = (Dn/Rn) ̂FairnessWgt×QoSweight×UE_buff_status (7)

Where,

FairnessWgt refers to fairness factor. It is an internal parameter (value: 1) and cannot be configured. For details, see Fairness Weight in Node B Interface

Parameter Description.

UE_buff _status: Refers to information about buffer area size in SI reported by UE. The larger the data volume in the buffer area, the higher the scheduling priority of UE.

QoSweight: refers to comprehensive weight after taking into account the QoS information configured by RNC, including the Scheduling Priority Indicator (SPI), and MAC-es Guaranteed Bit Rate (GBR). QoSweight is given in the following equation:



QoSweight =(SPI_WEIGHT) × (1 + GBRweight) (8)

SPI_WEIGHT is mapped through Table 1 according to SPI(0~15) configured by RNC. The default mapping is the first column. Operators can configure the

mapping. For details, refer to Node B radio interface parameter description.

For UEs with Rn not less than GBR:

GBRweight = 0, (9)

For UEs with Rn less than GBR:

GBRweight = MaxGBRWeightValue, (10)

MaxGBRWeightValue is an internal parameter, with value of 389376. If the actual rate of a UE is lower than GBR, GBRweight will increase, resulting in a raise in UE

scheduling priority so that resources can be preferentially allocated for this UE.

When Streaming services are carried on E-DCH, RNC informs Node B of the QoS parameter MAC-es Guaranteed Bit Rate (GBR) through NBAP.

When interactive-/background-class services are carried on E -DCH, RNC provides configuration of nominal bit rate EdchNormBitRate. For details, see ZTE UMTS QoS Feature Guide. For interactive-/background-class services,

RNC maps EdchNormBitRate into the QoS parameter of UE: MAC-es Guaranteed Bit Rate, and informs the HSUPA packet scheduler through NBAP. The scheduler schedules such types of services according to the specified

GBR. The SPI configured for interactive-/background-class services is comparatively low, so the ultimate scheduling priority of them will be lower than that of Streaming services with higher SPI.

4 Allocate available system resources in descending sequence of UE priorities.

Calculate available cell load based on the cell and UE load obtained in steps 1 and 2 as well as Node B processing capacity.

Reserve load for R99 RT, R99 NRT, SRB and HSUPA non-scheduled

transmission services from the available cell load. (The scheduler thinks the load contributed by these services is constant before or after scheduling).

Determine the transmission rate requested by UE. The UE requested

transmission rate is subject to the service requirements (Service requirements are jointly determined by the buffer area size in the SI as well as HappyBit reported by UE. For UEs with HappyBit = Unhappy, their service requirements

equal to the size of buffer area; for UEs with HappyBit = Happy, their service requirements equal to the size of data block corresponding with current grants obtained), maximum rate in relation to UE category, maximum subscribed rate

(MBR) and maximum rate in relation to the UPH reported by UE (UPH in SI). The smallest one of these values is taken as UE requested transmission rate.

The HSUPA scheduler allocates resources for UEs in descending sequence of their scheduling priorities.



If current available system load and CE resources are larger than the summation of load contributed by all UE requested transmission rates, the scheduler allocates grants in relation to requested rates for all UEs.

If current available system load or CE resources are less than the summation

of load contributed by all UE requested transmission rates, the scheduler first calculates the load and CE resources contributed by the rate requested by the UE with highest priority.

The scheduler releases grants of UEs with low priorities one by one in ascending sequence of scheduling priorities. Then it calculates the load contributed after releasing grants until the load and CE resources released

from UEs with low priorities meet the requirements of the UE with highest priority. If the load released from UEs with low priorities still fails to meet all requirements of the UE with highest priority, the UE with highest priority will

have to use the load and CE resources released from those with low priorities.

When allocating resources, the scheduler calculates CE resources currently used by each UE as well as available CE resources of Node B. Then it

allocates the minimum available CE resources and load of Node B to the UE with highest priority.

The scheduler allocates CE resources and load to the rest UEs with high priorities in the queue by following the above rule until all system resources are

used up (all UEs with low priorities have their resources released).

Map load contributed by UEs into grants of UEs (the relation between UE-contributed load and grant is as follows):

UE Serving Grants refers to the ratio of available E-DCH transmit power to DPCCH transmit power:

SG = PE-DCH,TX / PDPCCH,TX (11)

Where,

PE-DCH,TX refers to E-DCH transmit power.

PDPCCH,TX refers to DPCCH transmit power.

DPCCH and E-DCH undergo the same fading process, and therefore, the relation between receive powers of Node B DPCCH and E-DCH is given by the following equation:

PE-DCH,RX / PDPCCH,RX = PE-DCH,TX / PDPCCH,TX (12)

And,

PDPCCH,RX(1 + SG)= PDPCCH,RX + PE-DCH,RX (13)

Where,

PE-DCH,RX refers to the receive power of E-DCH in Node B.

PDPCCH,RX refers to the receive power of DPCCH in Node B.



The relation between grant and UE-contributed load is given as follows:

((Eb/No)R)/W = (PDPCCH.RX + PE-DCH.RX)/No (14)

Substitute (13) into (14),

((Eb/No)R)/W = PDPCCH,RX(1 + SG)/No (15)

3GPP TS 25.214 defines the UE DPCCH SIR measured by Node B.

SIR = 256 × PDPCCH,RX/No (16)

In the above equation, 256 refers to the processing gain of DPCCH. Substitute (16) into (15):

((Eb/No)R)/W = SIR(1 + SG)/256 (17)

Substitute (17) into (4),

UEload = SIR(1 + SG)/ (256 + SIR(1 + SG)) (18)

The above equation indicates the correspondence between UE-contributed load

and UE grant. The UE service grant can be obtained through UE -contributed load, or vice versa.

For a UE with highest scheduling priority, the scheduler needs to send AG for scheduling to facilitate the UE to quickly obtain required grant. The AG cannot

be used for the rest UEs after it is engaged because AGCH is shared among all UEs. The RGCH, however, is dedicated control channel allocated for each UE. Therefore, for the rest UEs, they can either get more resources or release

their resources by RG commands. The scheduler sends RG=UP to UEs allocated with more resources, RG=DOWN to UEs with resources released and RG=HOLD to UEs with grants retained during scheduling.

When the ratio of the receive power of non-serving E-DCH RLS to the total receive power of E-DCH is larger than NservToTotalPwr, Node B sends RG=DOWN to non-serving RL UE.

The AGCH and RGCH may transmit data to UE in each TTI based on scheduling requirements.

The Schedule Period is related to TTI and not adjustable (the schedule period is 40ms). For details, see Node B Interface Parameter Description.

3.1.4 CPC affection on HSUPA packet scheduling

CPC affection on HSUPA packet scheduling algorithm is mainly from UL DTX.

UL DTX predefines two DPCCH discontinuous transmission duration: UE_DTX_cycle_2 and UE_DTX_cycle_1, the former is integral multiple times of latter. If there is no data transmission on UL, UE will transmit DPCCH with a cycle

duration of UE_DTX_cycle_1 subframes, and subframe number to be transmitted in every cycle duration is controlled by UE_DPCCH_burst_1. If there is no E-DCH data transmission in number of continuous Inactivity_Threshold_for_UE_DTX_cycle_2 E-



DCH TT, the cycle duration will change to UE_DTX_cycle_2 subframes, and subframe number to be transmitted in every cycle duration is controlled by UE_DPCCH_burst_2. Related parameters can be referenced from ZTE UMTS HSPA Evolution Feature Guide.

When CPC is activated in UE, Node B HSUPA packet scheduling algorithm needs to know UE in cycle1 or cycle2 status, and process this UE scheduling according to the status.

After activation of CPC in UEs, RNC will stagger individual UE’s burst instance through parameter UE DTX DRX Offset to decrease UL interference as much as possible. So in order to save UE t ransmission power, UE needs to complete HP( HARQ Process)with

the burst time instance.

HSUPA packet scheduling algorithm will average the historical load of each UE in the recent RTT, After introducing CPC, sometimes UE maybe transmit UL DPCCH only and

no E-DCH, accurate SIR and the power offset between UL DPCCH and other uplink physical channels must be included in UL decoding report message as same as CPC non-activation.

When HSUPA packet scheduling algorithm try to forecast UE UL load, the estimated SIR is the historical average value in recent RTT. After introducing CPC, DTX maybe happen with DPCCH transmission. In order to estimate the SIR in the future, it’s

suggested to consider the influence of the DPCCH DTX.

3.2 HSUPA Flow Control Algorithm

The flow control implemented by the HSUPA scheduler consists of the following two

parts:

E-DCH uplink congestion control.

Back-pressure flow control.

E-DCH uplink congestion control is detected by RNC and implemented by Node B, and Back-pressure flow control is implemented in Node B. The back-pressure function exercises control over the uplink service rate of E-DCH UEs based on lub bandwidth

utilization status.

3.2.1 E-DCH Uplink Congestion Control

3.2.1.1 RNC detects E-DCH congestion

When the realtime rate of services carried on E-DCH is high, packet out-of-sequence,

loss or delay may occur due to problems on the transmission path from Node B to SRNC. SRNC needs to detect any of these situations, and informs Node B of the congestion so as to lower realtime rate of UE, alleviate congestion and avoid impact on other services.

Whether the function of E -DCH congestion detection and indication is switched off or on can be configured in OMM. Please refer to the parameter of SuptCgtDetInd in OMM.



E-DCH congestion detection and indication procedure on RNC side is described as follows:

1 Upon receiving E-DCH FP, the RNC records such information as data frame

receiving time, FSN, CFN, sub-frame No. as well as TTI.

2 If it is the first data frame received on uplink, RNC only records such information as frame receiving time, FSN, CFN, and sub-frame No. and the processing ends. If

RNC does not receive any uplink data for a long time, it will process subsequently received data frames in the same way as the first data frame.

3 Frame loss judgment: RNC compares the FSN of one frame with that of its previous

frame. If the FSNs of them are not consecutive, RNC will set out-of-sequence tolerance period (out-of-sequence tolerance period =20ms+ TimeDelayJitter *2; TimeDelayJitter can be configured in OMM). The out-of-sequence tolerance period

is introduced to reduce frame out-of-sequence caused by transmission jitter and avoid false or excessive report of transmission congestion execution frames of ―Frame loss‖ type. The out-of-sequence tolerance period is related to office direction

transmission jitter.

4 Frame delay judgment: By comparing the CFNs and sub-frame Nos. of two E-DCH FP frames with consecutive FSNs, RNC obtains Uu interface time difference of

these two frames; by comparing the receiving time of two consecutive E-DCH FP frames, RNC obtains the receiving time difference of them. If the receiving time difference is x ms (x = TTI + TimeDelayJitter *2; TimeDelayJitter can be configured

in OMM) larger than the Uu interface time difference, RNC considers it as ―Frame delay‖.

5 Upon detecting E-DCH congestion (for example, after frame delay and loss), RNC

sends a TNL Congestion Indication message to Node B. To prevent Node B from failing to respond to the TNL Congestion Indication message due to transmission delay or other causes, RNC sets a protection timer (timer duration = 100ms +

TimeDelay; TimeDelay can be configured in OMM) after sending the TNL Congestion Indication message to avoid repeated transmission of TNL Congestion Indication with identical congestion status.

3.2.1.2 Node B implements E-DCH congestion control

Upon receiving the TNL Congestion Indication message from certain UE, the congestion

processing module of the HSUPA scheduler lowers the maximum grant threshold (the initial value is 37, the maximum SG as stipulated in 3GPP TS25.321) of the UE to MIN (Current grant of UE –DownStep, maximum grant threshold of UE –DownStep;

DownStep is an internal parameter of scheduler and is not adjustable), and starts CongestionTimer (CongestionTimer refers to the timer internally used in the scheduler, with constant and unadjustable timing cycle. If the scheduler fails to receive new TNL

Congestion Indication messages to indicate congestion status or receives a message indicating congestion recovery before timeout of CongestionTimer, it may consider the uplink FP data flow on IUB interface is no longer congested. Then it increases the

maximum grant threshold of the UE to current threshold + Upstep (Upstep is an internal parameter of scheduler and not adjustable), and re-starts CongestionTimer until the threshold reaches the maximum value—37. The maximum grant threshold in congestion

control, however, will be used in UE grant allocation in HSUPA scheduling procedure. The grant allocated by the scheduler for the UE cannot exceed this maximum threshold, thus realizing control over UE grant through threshold.



Congestion processing procedure is as follows:

Figure 7 Congestion processing procedure of scheduler

Start

Receive TNL

congestion

Indication of UEi

Reduce the up limit of

SG;start or restart the

timer

Indicate Congestion

Upgrade the upper

limit of SG;restart

the timer

The upper limit

of SG is smaller

than 37

Timer is up

yes

no

yes

yes

yes

end

no

no

3.2.2 Back-pressure Flow Control

As shown in the following figure, the Transport Network Subsystem of Node B measures uplink data traffic on lub interface, converts measured traffic into actual used bandwidth

and calculates bandwidth utilization. Then it sends the bandwidth utilization to the HSUPA scheduler. The HSUPA scheduler then determines whether to restrict UE grant threshold based on bandwidth utilization so as to lower traffic and avoid congestion on

lub interface.

Figure 8 HSUPA flow control mechanism in Node B



UE

HSUPA

SchedulerE-RGCH

E-AGCH

Downlink

RNC

Uplink Processing

AG

RG

NodeB

Uu

Uu

Uu

lubTNS

Measure

report

3.2.2.1 R99 and HSUPA non-scheduled services

The data transmission of both R99 and HSUPA non-scheduled services is determined by RNC instead of Node B, so certain bandwidth is reserved in Node B for data

transmission of these services. For example, Reserved Bandwidth in the following figure.

Figure 9 lub interface bandwidth allocation in Node B

Used Bandwidth

Assignable Bandwidth

Total Bandwidth

Reserved Bandwidth

The meanings of bandwidths shown in the above figure are described as follows:

Total Bandwidth refers to the bandwidth configured through Node B transmission

parameters. For details see R_IPPARA·Bandwidth in Node B Transmission

Interface Parameter Description.

Reserved Bandwidth has two roles: (1) Reserve certain bandwidth margin for buffer

protection so as to avoid congestion on lub interface; (2) Reserved for R99 and

HSUPA non-scheduled services. Reserved Bandwidth is an internal variable of the

HSUPA scheduler and the value is not adjustable.



Assignable Bandwidth = Total Bandwidth - Reserved Bandwidth. Assignable

Bandwidth is an internal variable of Node B and is not adjustable.

Used Bandwidth: Refers to the bandwidth measured through TNS, including uplink

traffic of all services.

Unit of all above parameters or variables: bits/s.

3.2.2.2 Back-pressure Control of HSUPA scheduled services

The lub interface bandwidth measurement module in the Transport Network Subsystem

(TNS) of Node B realtime measures the uplink data traffic of each channel on lub interface, calculates their bandwidth utilization Rbw and periodically reports measurement and calculation results to the HSUPA scheduler. Upon receiving Rbw, the HSUPA

scheduler compares it with pre-defined threshold (R_BW_LMT_UP); if Rbw exceeds R_BW_LMT_UP, it initiates back-pressure control over grant threshold for all UEs on the channel. If Rbw gradually decreases below pre-defined threshold (R_BW_LMT_DOWN),

the HSUPA scheduler initiates back-pressure grant threshold recovery procedure.

Realtime bandwidth measurement policy on lub interface:

In FE mode:

1 The TNS realtime obtains the number of bytes transmitted on the network interface at a specific time interval, and converts it into current rate (unit: bps).

2 The TNS reports current rate to the UPA scheduler at a certain time interval.

In IPoverE1 mode:

3 The TNS realtime obtains the number of bytes transmitted through PPP/MLPPP at a specific time interval, and converts it into current rate (unit: bps).


In ATM mode:

1 The TNS realtime obtains the number of bytes transmitted through AAL2 PVC at a specific time interval, and converts it into current rate (unit: bps).


The following figure shows the back-pressure control procedure.

Figure 10 Back-pressure control procedure of HSUPA scheduler



Start

Rbw >

R_BW_LMT_UP？

Suppress

SGlmtIub

processing

Rbw <

R_BW_LMT_DOWN

？

Resume

SGlmtIub

processing

YES

end

NO

YES

NO

The back-pressure grant threshold control procedure:

1 Assign current grant as the back-pressure grant threshold SGlmtIub of all UEs on the channel.

2 Set SGlmtIub of the two UEs with lowest scheduling priority among all UEs on the channel to: current SGlmtIub – DownStep (DownStep is an internal parameter of the scheduler and is not adjustable).

The back-pressure grant threshold recovery procedure:

1 Set SGlmtIub of the UE with highest scheduling priority among all UEs on the channel to: current SGlmtIub + UpStep (UpStep is an internal parameter of the scheduler and

is not adjustable).

2 Assign current grant as the back-pressure grant threshold SGlmtIub of the rest UEs on the channel.

The back-pressure grant threshold SGlmtIub is an internal variable of the HSUPA scheduler, and one of upper grant thresholds including congestion and maximum bit rate of UE. These thresholds are set to perform more effective scheduling and appropriate

grant allocation. When scheduling grants are allocated for UEs, note that these thresholds cannot be exceeded so as to separate control procedure from scheduling procedure and realize smooth grant allocation.

Parameters related to congestion control are described as follows:

Pre-defined upper threshold for bandwidth utilization: R_BW_LMT_UP. This

parameter is an internal variable of the HSUPA scheduler and is not adjustable.



Pre-defined lower threshold for bandwidth utilization: R_BW_LMT_DOWN. This

parameter is an internal variable of the HSUPA scheduler and is not adjustable.

The bandwidth utilization Rbw is given by the following equation:

Rbw = Used Bandwidth / Assignable Bandwidth

Where,

Used Bandwidth refers to channel -used bandwidth measured by TNS (Unit: bits/s)

Assignable Bandwidth = Total Bandwidth - Reserved Bandwidth. (Unit: bits/s)

4 Parameters and Configuration

4.1 Parameter List Abbreviated name Parameter name

EdchNormBitRate E-DCH Uplink Nominal Bit Rate(kbps)

Maximum Target Received Total

Wideband Power

MaxRTWP(dB)

NServToTotalPwr Target Non-serving E-DCH to Total E-DCH Power

Ratio(%)

MaxRetransEdch Maximum Number of Retransmissions for E-DCH

SuptCgtDet Ind Support Congestion Detection Indicator

TimeDelay Transport Time Delay

TimeDelayJitter Transport Time Jitter

R_IPPARA•Bandwidth Bandwidth

SPI_WEIGHT SPI WEIGHT( 0~15)

4.2 Parameter Configuration

4.2.1 E-DCH Uplink Nominal Bit Rate

OMM Path

View -> Configuration Resource Tree –> OMM -> UTRAN SubnetworkXXX -> RNC

Managed ElementXXX -> RNC Config SetXXX (Choose the used config set) -> QoS

ConfigurationXXX -> Priority and Rate Segment of QoS Advanced Parameter

Parameter Configuration

Related description



This parameter is configured for Nominal Bit Rate (NBR) of I-/B-class services on E-DCH, related to basic priority level. UEs with high priority have high NBRs. EdchNormBitRate is used as the minimum guaranteed rate in NodeB HSUPA packet

scheduling.

Parameter description:

This parameter is used to configure the uplink NBR of interactive/background-class

services with basic priority.

Note: This parameter is only valid for the uplink rate of I-/B-class services.

Recommendation: Set an appropriate value for this parameter based on actual

conditions.

4.2.2 Maximum Target Received Total Wideband Power(dB)

OMM Path

View->Configuration Management ->RNC NE->RNC Radio Resource Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Hspa Configuration information In A Cell


This parameter indicates the maximum target UL interference allowed by a cell, which is an offset relative to the UL interference when there is zero load in the cell. This

parameter can also be deemed as the maximum RTWP used for Node B scheduling. The RTWP increases by increasing the configuration of this parameter and decreases by decreasing the configuration of this parameter.

4.2.3 Target Non-serving E-DCH to Total E-DCH Power Ratio(%)

OMM Path

View->Configuration Management->RNC NE->RNC Radio Resource Management-

>Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Hspa Configuration information In A Cell


If the value of this parameter increases, Node B sends RG=DOWN to non-serving RL UE only when the ratio of the receive power of non-serving E-DCH RLS to the total receive power of E-DCH is larger than NservToTotalPwr, and it is comparatively hard for

Node B to trigger RG=DOWN procedure; If the value of this parameter decreases, Node B sends RG=DOWN to non-serving RL UE only when the ratio of the receive power of non-serving E-DCH RLS to the total receive power of E-DCH is smaller than

NservToTotalPwr, and it is comparatively easy for Node B to trigger RG=DOWN procedure.



4.2.4 Maximum Number of Retransmissions for E-DCH

OMM Path

View->Configuration Management ->RNC NE->Rnc Radio Resource Management-

>Modify Advanced Parameter ->Service Basic Configuration Information


None.

4.2.5 Support Congestion Detection Indicator

OMM Path

View->Configuration Management ->RNC NE->Rnc Radio Resource Management->

Node B Configuration Information-> Node B Configuration Information xx-> Modify Advanced Parameter

View->Configuration Management ->OMM->UTRAN SubNetwork->RNC Managed

Element->Rnc Radio Resource Management->External UTRAN Cell ->External UTRAN Cell xx-> Modify Advanced Parameter


Configure this parameter based on Node B office direction; for cell not controlled by current RNC, configure this parameter based on cell settings.

4.2.6 Transport Time Delay

OMM Path

View->Configuration Management ->RNC NE->Rnc Radio Resource Management->Node B Configuration Information->Node B Configuration Information xx-> Modify

Advanced Parameter

Parameter configuration

None.

4.2.7 Transport Time Jitter

OMM Path

View->Configuration Management ->RNC NE->Rnc Radio Resource Management-

>Node B Configuration Information->Node B Configuration Information xx-> Modify Advanced Parameter

Parameter configuration



None.

4.2.8 R_IPPARA Bandwidth

OMM Path

View->Configuration Management ->NodeB NE->Transport network object->Physical

Capacity -> IP port ->Tx bandwidth(kbps)

Parameter Configuration.

None.

4.2.9 SPI_WEIGHT ( 0~15)

OMMB Path

View->Configuration Management ->NodeB NE->SdrFunction object->UMTS radio

network object->Baseband resource pool object->HSUPA SPI


SPI_WEIGHT ( 0~15)is mapping in Node B according to the SPI configured by RNC. Operators can define the mapping relation. There are three mappings in Table 1. The

default mapping is the first column.

Table 1 SPI_WEIGHT( 0~15)mapping table

SPI SPI_WEIGHT =SPI+1

SPI_WEIGHT =EXP((SPI+1)/2)

SPI_WEIGHT =SPI^3

0 1 2 1

1 2 3 8

2 3 4 27

3 4 7 64

4 5 12 125

5 6 20 216

6 7 33 343

7 8 55 512

8 9 90 729

9 10 148 1000

10 11 245 1331

11 12 403 1728

12 13 665 2197

13 14 1097 2744

14 15 1808 3375



15 16 2981 4096

5 Counter And Alarm

5.1 Counter List

There is no counter in this feature.

5.2 Alarm List

There is no alarm in this feature.

6 Glossary

A

ACK Acknowledgement

AG Absolute Grant

C

CFN Connection Frame Number (counter)

D

DPCCH Dedicated Physical Control Channel

E

E-AGCH E-DCH Absolute Grant Channel

E-DCH Enhanced Uplink Dedicated Channel

E-DPCCH E-DCH Dedicated Physical Control Channel

E-DPDCH E-DCH Dedicated Physical Data Channel

E-HICH E-DCH Hybrid ARQ Indicatior Channel

E-RGCH E-DCH Relative Grant Channel

E-TFCI E-DCH Transport Format Combination Indicator

F

FSN Frame Sequence Number



FP Frame Protocol

G

GBR Guaranteed Bit Rate

H

HARQ Hybrid Automatic Repeat Request

HSUPA High-Speed Uplink Packet Access

I

IR Incremental Redundancy

L

LUPR Last Used Power Ratio

M

MAC-es/e E-DCH MAC

MAC-d Dedicated MAC

MAC Medium Acess Control

MLPPP Multi-Label PPP

N

Node B Base Station

NACK Negative Acknowledgement

NRT Non Real Time

O

OMM Operate & Management Control

OMMB OMM in Node B

OMMR OMM in RNC

P

PF Proportional Fair

PPP Point to Point Protocol

Q

QoS Quality of Service



R

RNC Radio Network Controller

RG Relative Grant

RTWP Received Total Wideband Power

RL Radio Link

RLS Radio Link Set

RSN Retransmission Sequence Number

RNC Radio Network Controller

RoT Rise of Thermal

S

SF Spreading Factor

SI Scheduling Information

SIR Signal to Interference Ratio

SPI Scheduling Priority Indicator

SRNC Serving RNC

SRB Singalling Radio Bearer

T

TTI Transmission Time Interval

TNL Transport Networdk Layer

TNS Transport Network Subsystem

U

UE User Equipment

UPH UE Transmission Power Headroom

UMTS Universal Mobile Telecommunications System

zte umts (u9.3) hsupa packet scheduling feature guide_v4.0

Documents