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

Version V4.0 Date 2010-6-13 Author Wang Yue Approved By Peng Bei, Hu Ye Remarks June 30 Version update
th
2010 ZTE Corporation. All rights reserved. ZTE CONFIDENTIAL: This document contains propriet ary 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.
TABLE OF CONTENTS
1 2 2.1 2.1.1 2.1.2 3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.2 3.2.1 3.2.2 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.2.7 4.2.8 4.2.9 5 5.1 5.2 6 Functional Attribute ............................................................................................1 Overview .............................................................................................................1 Function Introduction ............................................................................................1 HSUPA Fast Scheduling .......................................................................................2 HSUPA Flow Control ............................................................................................6 Technical Description .........................................................................................6 HSUPA Scheduling Algorithm ...............................................................................6 Features of Fast Scheduling .................................................................................6 Description of Packet Scheduler............................................................................7 Key Algorithms of Packet Scheduler ......................................................................8 CPC affection on HS UPA packet scheduling ........................................................15 HSUPA Flow Control Algorithm ...........................................................................16 E-DCH Uplink Congestion Cont rol .......................................................................16 Back-pressure Flow Control ................................................................................18 Parameters and Configuration ..........................................................................22 Parameter List ...................................................................................................22 Parameter Configuration .....................................................................................22 E-DCH Uplink Nominal Bit Rate ........................................................................22 Maximum Target Received Total Wideband Power(dB) ........................................23 Target Non-serving E-DCH to Total E-DCH Power Ratio(%) .................................23 Maximum Number of Retransmissions for E-DCH ................................................24 Support Congestion Detection Indicator ...............................................................24 Trans port Time Delay .........................................................................................24 Trans port Time Jitter ..........................................................................................24 R_IPPARA Bandwidth ........................................................................................25 SPI_WEIGHT ( 0~15) .........................................................................................25 Counter And Alarm ...........................................................................................26 Counter List .......................................................................................................26 Alarm List ..........................................................................................................26 Glossary ...........................................................................................................26
II
FIGURES
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 HSUPA protocol architecture in UTRAN ..................................................................2 MAC-e functions ....................................................................................................2 Basic operating principle of HSUPA .........................................................................4 HSUPA fast scheduling mechanism in Node B .........................................................7 Operating mechanism of HSUPA packet scheduler ..................................................9 HSUPA scheduling proc edure in Node B .................................................................9 Congestion proc essing procedure of scheduler ......................................................18 HSUPA flow control mechanism in Node B ............................................................18 lub interface bandwidth allocation in Node B ..........................................................19 Back-pressure control procedure of HSUPA scheduler ...........................................20
TABLES
Table 1 SPI_WEIGHT( 0~15)mapping table .......................................................................25
III
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
2.1
Overview
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 (HA RQ), and new transport channel-Enhanced Dedicat e 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 Cont roller (RNC), Node B and Us er 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 (UP H), 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: HS UPA fast scheduling and flow control, which are respectively detailed as follows:
2.1.1
HSUPA Fast Scheduling

The HS UPA scheduler is located at Node B, as defined in 3GPP. Benefiting from close proximity to air interface, the HS UPA scheduler can obtain measurement infor mation about uplink interference in time, thus achieving fast control over uplink dat a rate. Figure 1 shows the HSUPA protocol architecture in UMTS Terrestrial Radio Access Network (UTRA N).
Figure 1
HSUPA protocol architecture in UTRAN
DTCH DCCH
DTCH DCCH
MAC-d
MAC-d MAC-es
MAC-es/MAC-e
Uu
MAC-e
EDCH FP
Iub Iur
EDCH FP
PHY
PHY
TNL
TNL
TNL
TNL
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 HA RQ, 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 MA C-e (Node B side) where the HS UPA scheduler is located.
Figure 2
MAC-e functions
MAC-d Flows
MAC-e
MAC Control E-DCH Scheduling (FFS) E-DCH Control (FFS) De-multiplexing
HARQ
Associated Uplink Signalling
Associated Downlink Signalling
E-DCH
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 HA RQ entity supports several Stop -and-Wait (SAW) HARQ process instances. Each HARQ proc ess generates ACKs or NACKs to indicate the transmit status of E-DCH. The HARQ used in HS UPA is a multi-channel SAW concurrent retransmission mechanism. The HA RQ supports several HARQ processes, each of which transmits data packets in sequence. For one UE, there is only one HA RQ process transmitting data at one moment. If Node B receives a data packet from one HA RQ 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 rec eives a NACK message, the related HA RQ 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 HA RQ proc esses 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 enhanc es 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
MAC-d MAC-es FP
DRNC
Iur/Iub FP
1 TNL bearer per MAC-d flow
NodeBs
Iur/Iub FP
NodeBd
FP
MAC-e Scheduler MRC
MAC-e
MRC
serving cell
E-HICH (ACK/NACKs) E-RGCH (relative grants) (ChCode, signature -> UE)
E-AGCH (Absolute Grants, "E-RNTI" -> UE)
E-DPDCH E-DPCCH
UE
MAC-e/ MAC-es MAC-d
DTCHs
The above figure shows the connection relation bet ween UTRA N and UE that uses EDCH 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 EDCH 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 absolut e grant, the r elative grant can take one of the three values: UP, DOWN and HOLD, instructing the UE to inc reas e, 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 res ult of uplink overload. RNC may configure a percentage thres hold (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-DP DCH and sends E-TFC information, HA RQ 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 res ourc es (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 HA RQ 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 paramet er) is less than SG, it will update SG to LUP Rmax.
The HS UPA fast scheduling control function makes quick response to service requirements of all UEs in a c ell, 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 dat a 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 upperlayer flow control mechanism is necessitated to ens ure 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 CONGES TION INDICA TION message to scheduler. Upon receiving the TNL CONGES TION INDICA TION 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 interfac e based on the bandwidth utilization.
3
3.1
3.1.1
Technical Description
HSUPA Scheduling Algorithm
Features of Fast Scheduling
The HS UPA fast scheduling features the following: Node B-based fast scheduling. The HS UPA scheduler is located at Node B, facilitating the scheduler to obtain more realtime information about uplink interference and perform faster control over uplink dat a rate. Support fast HARQ with soft combining HARQ transmits ACK/NACK on E -HICH to UE based on whether E -DP DCH 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 HA RQ RV Configuration, which is configured to Node B by RNC through NBAP IE HA RQ Info for E-DCH(refer to ZTE UMTS HS UPA Introduction Feature Guide). If
retransmission reaches the maximum retransmission times, HA RQ sends an HA RQ Failure message to RNC through FP. RNC defines an HARQ profile for each MACd flow of UE. Each HA RQ 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 int erleaving 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 s elects 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 tec hnical 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-DP CCH 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 HS UPA 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
lub RNC
De-mux Associated Uplink Schedule Information
HARQ
E-DCH
Uu UE
Uplink Processing
ACK/ NACK
Uu E-HICH Uu E-AGCH Uu E-RGCH Downlink
AG HSUPA Scheduler NodeB RG
Uplink proce ssing: 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 det ecting the signal, Node B performs transport layer processing including descrambling and despreading. The E-DCH data packets and uplink-relat ed Scheduling Information (SI) are obtained after transport layer processing. E-DCH data packets are sent to HARQ at MAC -e layer for combining int o MAC-e PDUs. At the same time, HARQ generates ACK or NACK indication based on combining results and sends it to UE on downlink EHICH. MAC-e PDUs are sent to demultiplexing entity for demultiplexing into MA Ces PDUs, and then sent to MAC-es layer of RNC over lub interface for further processing. HSUP A packet scheduling: The HS UPA 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 HS UPA 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 Rec eived Tot al Wide Band Power (RefRTWP) configured by RNC through NBAP. (refer to ZTE UMTS Admission Control Feat ure Guide). Maximum Target Received Total Wideband Power ( MaxRTWP) (refer to ZXWR RNC Radio Net work Controller Radio Parameter Reference (Volume II )). Target Non-serving E-DCH to Total E-DCH Power Ratio (NS ervToTotalP wr) (refer to ZTE UTMS Overload Control Feature Guide). UE report ed 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
UE->: SI, HappyBit
Uplink processing uni t ->: E-TFCI, Eb/NoDPCCH SIR
HSUPA
NodeB->:RTWPcurrent, CE resource
PS Scheduler
UE:AG, RG,
RNC->: MaxRTWP, RefRTWP NServToTotalPwr RNC->: UE QoS parameters SPIGBR Non-scheduled BitRate
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 UEs and 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 UP H of UE). E-TFCI currently used by UE and MAC-e PDU multiplexing information (contained in MA C-e P DU head and used to obtain the type of MA C-e P DU 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 paramet er 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 paramet er 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 (RTWP current is measured at Node B). CE resource indication. Referenc e Received Total Wide Band Power ( Ref RTWP), Maximum Target Received Total Wideband Power (MaxRTWP), Target Non-serving E-DCH to Total E-DCH Power Ratio (NS ervToTotalP wr) configured by RNC through NBAP.
Determine UE, air interface and Node B resource utilization and load: The measurement unit of Node B meas ures air interface interference, and sends the measurement result RTWP current to the scheduler. The scheduler calculates current cell load Cell _Load_current and maximum target load Cell_Load_max (unit: %) through the following equations: (1) (2) (3)
RoT = Itotal/Pn
Cell_Load_current = 11/RoT
Cell_Load_max = 11/(MaxRTWP /Pn)
10
Where, Itotal refers to the total rec eive bandwidth power inclusive of background noise power (unit: mW) and takes the value of RTWP current . The RTWP Filter Period (40 ms) is an internal parameter and cannot be configured. For det ails, see Node B Int erface Parameter Description. Pn refers to background noise and takes the value of RefRTWP (Reference Received Total Wide Band Power). The original unit of P n 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-DP DCH 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))) Where, Itotal refers to the total rec eive bandwidth power inclusive of background noise power (unit: mW) and takes the value of RTWP current. 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 HS UPA scheduler adopts the Enhanced Proportional Fair (PF) Algorithm, and calculates scheduling priority which is a variable for eac h 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 wit h low t ransmission throughput will be scheduled preferentially so as to ensure fairness. (4)
11
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 m UE) before n TTI(s) (n refers to current time).
th
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: (5)
Rn = (1-a)Rn-1 + aDn Other cases:
Rn = (1-a)Rn-1 Where,
(6)
Rn-1 refers to the value of Rn in last TTI (Unit: bits/s). R0 refers to the uplink rat e 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 n transmission moment. m refers to the m 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:
th th
Priority = (Dn/Rn)^ FairnessWgtQoS weight 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 Int erface Parameter Description. UE_buff _status: Refers to information about buffer area size in SI report ed 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 MA C-es Guarant eed Bit Rat e (GB R). QoS weight is given in the following equation:
12
QoSweight =(SPI_WEIGHT) (1 + GB Rweight )
(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: (9)
GBRweight = 0, For UEs with Rn less than GB R:
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 MA C-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 det ails, see ZTE UMTS QoS Feature Guide. For interactive-/background-class services, RNC maps EdchNormBitRate into the QoS parameter of UE: MA C-es Guarant eed Bit Rate, and informs the HSUPA packet scheduler through NBAP. The scheduler schedules such types of servic es 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 servic es with higher SP I.
Allocate available system resources in descending sequence of UE priorities. Calculat e 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 HS UPA non-scheduled transmission services from the available cell load. (The scheduler thinks the load cont ribut ed by these services is constant before or after scheduling). Determine the transmission rate requested by UE. The UE requested transmission rat e is subject to the service requirements (Service requirements are jointly determined by the buffer area size in the S I 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 UP H 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.
13
If current available system load and CE resources are larger than the summation of load contributed by all UE requested transmission rates, the scheduler allocat es 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 res ourc es 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 contribut ed 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 loa d 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 contribut ed by UEs into grants of UEs (the relation bet ween UE contribut ed load and grant is as follows):
UE Serving Grants refers to the ratio of available E-DCH t ransmit power to DP CCH transmit power: SG = P E-DCH,TX / PDPCCH,TX 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 = P E-DCH,TX / PDPCCH,TX And, PDPCCH,RX(1 + SG)= P DPCCH,RX + P E-DCH,RX 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. (13) (12) (11)
14
The relation between grant and UE-contributed load is given as follows: ((Eb/ No)R)/W = (P DPCCH.RX + PE-DCH.RX)/No Substitute (13) into (14), ((Eb/ No)R)/W = P DPCCH,RX(1 + SG)/No (15) (14)
3GPP TS 25.214 defines the UE DP CCH S IR measured by Node B. SIR = 256 P DPCCH,RX/No (16)
In the above equation, 256 refers to the processing gain of DP CCH. Substitute (16) into (15): ((Eb/ No)R)/W = SIR(1 + SG)/256 Substitute (17) into (4), UEload = SIR(1 + SG)/ (256 + SIR(1 + SG)) (18) (17)
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 aft er it is engaged because AGCH is shared am ong all UEs. The RGCH, however, is dedicated control channel allocat ed 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 NservToTotalP wr, 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 HS UPA 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-
15
DCH TT, the cycle duration will c hange t o UE_DTX_cycle_2 subframes, and subframe number to be transmitted in every cycle duration is controlled by UE_DP CCH_burst_2. Relat ed parameters can be referenced from ZTE UMTS HSPA Evolution Feat ure Guide. When CP C is activated in UE, Node B HSUPA packet scheduling algorithm needs to know UE in cycle1 or cycle2 status, and proc ess this UE scheduling according to the status. After activation of CP C in UEs, RNC will stagger individual UEs burst instance through parameter UE DTX DRX Offset to decrease UL interferenc e as much as possible. So in order to save UE t ransmission power, UE needs to complete HP( HA RQ Process)with the burst time instance. HSUPA packet scheduling algorithm will average the historical load of each UE in the recent RTT, A fter introducing CP C, sometimes UE maybe transmit UL DPCCH only and no E-DCH, accurate SIR and the power offset bet ween UL DP CCH and other uplink physical channels must be included in UL decoding report message as same as CPC non-activation. When HS UPA packet scheduling algorithm try to forecast UE UL load, the estimated SIR is the historic al average value in recent RTT. After introducing CP C, DTX maybe happen with DP CCH transmission. In order to estimate the S IR in the future, its suggested to consider the influence of the DP CCH DTX.
3.2
HSUPA Flow Control Algorithm

The flow cont rol implemented by the HS UPA scheduler c onsists 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
3.2.1.1
E-DCH Uplink Congestion Control

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 pat h from Node B to SRNC. SRNC needs to det ect 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 SuptCgt DetInd in OMM.
16
E-DCH congestion detection and indication proc edure on RNC side is described as follows: 1 Upon receiving E -DCH FP, the RNC rec ords such information as data frame receiving time, FSN, CFN, sub-frame No. as well as TTI. If it is the first dat a frame received on uplink, RNC only records such information as frame receiving time, FS N, CFN, and sub-frame No. and the processing ends. If RNC does not receive any uplink data for a long time, it will proc ess subsequently received data frames in the same way as the first data frame. Frame loss judgment: RNC compares the FS N of one frame wit h that of its previous frame. If the FS Ns of them are not consecutive, RNC will set out-of-sequence tolerance period (out-of-s equence tolerance period =20ms+ TimeDelayJitter *2; TimeDelayJitter can be configured in OMM). The out-of-sequence tolerance period is introduced to reduc e frame out-of-sequenc e caused by transmission jitter and avoid false or excessive report of transmission congestion exec ution frames of Frame loss type. The out-of-sequence tolerance period is related to office direction transmission jitter. 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 differenc e 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 receivi ng time differenc e is x ms (x = TTI + TimeDelayJitter *2; TimeDelayJitter can be configured in OMM) larger t han t he Uu interface time difference, RNC c onsiders it as Frame delay. Upon detecting E-DCH congestion (for example, after frame delay and loss), RNC sends a TNL Congestion Indication message t o 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 wit h 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 TS 25.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 t he scheduler, with constant and unadjustable timing cycle. If the scheduler fails to receive new TNL Congestion Indication messages to indicat e 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 increas es 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 value37. The maximum grant threshold in congestion control, however, will be used in UE grant allocation in HSUPA scheduling procedure. The grant allocat ed by the scheduler for the UE cannot exceed this maximum threshold, thus realizing control over UE grant through threshold.
17
Congestion proc essing procedure is as follows:
Figure 7
Congestion processing procedure of scheduler
Start
Receive TNL congestion Indication of UEi yes
no
Timer is up Indicate Congestion
yes yes no The upper limit of SG is smaller than 37 yes Upgrade the upper limit of SG;restart the timer
Reduce the up limit of SG;start or restart the timer
no
end
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 calculat es 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 bandwidt h utilization so as to lower traffic and avoid congestion on lub interface.
Figure 8
HSUPA flow control mechanism in Node B
18
Uu Uplink Processing RNC lub TNS UE
Measure report
AG HSUPA Scheduler RG
Uu E-AGCH Uu E-RGCH Downlink
NodeB
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
Reserved Bandwidth
Total Bandwidth Assignable Bandwidth Used Bandwidth
The meanings of bandwidths shown in the above figure are described as follows: Total Bandwidt h 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 bandwidt h margin for buffer protection so as to avoid congestion on lub interfac e; (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.
19
Assignable Bandwidth = Tot al 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 R bw and periodically reports measurement and calculation results to the HSUPA scheduler. Upon receiving R bw, the HS UPA 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 proc edu re. Realtime bandwidth measurement policy on lub int erface: 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). The TNS reports current rat e to the UPA scheduler at a cert ain time interval.
In IPoverE1 mode:
The TNS realtime obtains the number of bytes transmitted through PPP/MLPPP at a specific time interval, and converts it into current rat e (unit: bps). The TNS reports current rat e to the UPA scheduler at a cert ain time interval.
In A TM 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 TNS reports current rate to the UPA scheduler at a certain time interval.
The following figure shows the back-pressure control procedure.
Figure 10 Back-pressure control procedure of HSUPA scheduler
20
Start
Rbw > R_BW_LMT_UP

YES
NO
Suppress SGlmtIub processing
Rbw < R_BW_LMT_DOWN

YES
Resume SGlmtIub processing
NO
end
The back-pressure grant threshold control procedure: 1 Assign current grant as the back-pressure grant threshold SGlmtIub of all UEs on the channel. 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 rec overy procedure: 1 Set SGlmtIub of the UE wit h 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). Assign current grant as the back-pressure grant threshold SGlmtIub of the rest UEs on the channel.
The back-pressure grant thres hold SGlmtIub is an internal variable of the HS UPA 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 allocat ed for UEs, not e that these thresholds cannot be exceeded so as to s eparate 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 HS UPA scheduler and is not adjustabl e.
21
Pre-defined lower threshold for bandwidth utilization: R_BW_LMT_DOW N. This parameter is an internal variable of the HS UPA scheduler and is not adjustable. The bandwidt h 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
4.1
Parameters and Configuration

Parameter List
Abbreviated name EdchNormBitRate Maximum Target Received Total Wideband Power NServToTotalP wr MaxRetransEdch SuptCgt Det Ind TimeDelay TimeDelayJitter R_IPPARABandwidth SPI_WEIGHT Parameter name E-DCH Uplink Nominal Bit Rate(kbps) MaxRTWP(dB) Target Non-serving E-DCH to Total E-DCH Power Ratio(%) Maximum Number of Retransmissions for E-DCH Support Congestion Detection Indicator Transport Time Delay Transport Time Jitter Bandwidth SPI WEIGHT( 0~15)
4.2
4.2.1
Parameter Configuration
E-DCH Uplink Nominal Bit Rate
OMM Path
View -> Configuration Resource Tree > OMM -> UTRA N Subnet work XXX -> RNC Managed Element XXX -> RNC Config Set XXX (Choose the us ed config set) -> QoS ConfigurationXXX -> Priority and Rate Segment of QoS Advanced Parameter Parameter Configuration
Relat ed description
22
This parameter is configured for Nominal Bit Rate (NB R) of I-/B-class services on EDCH, related to basic priority level. UEs with high priority have high NBRs. EdchNormBitRate is used as the minimum guaranteed rat e 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 bas ed 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 Parameter Configuration
This paramet er indicates the maximum target UL interference allowed by a cell, which is an offset relative to the UL interferenc e 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 Parameter Configuration
If the value of this parameter increases, Node B sends RG=DOWN to non-serving RL UE only when the ratio of the rec eive power of non-serving E-DCH RLS t o the total receive power of E -DCH is larger than NservToTotalP wr, 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-s erving RL UE only when the ratio of the receive power of non-serving E-DCH RLS to the tot al receive power of E-DCH is smaller than NservToTotalP wr, and it is comparatively easy for Node B to trigger RG= DOWN procedure.
23
4.2.4
Maximum Number of Retransmissions for E-DCH

OMM Path
View-> Configuration Management -> RNC NE-> Rnc Radio Resource Management>Modify Advanced Parameter ->Servic e Basic Configuration Information Parameter Configuration
None.
4.2.5
Support Congestion Detection Indicator

OMM Path
View-> Configuration Management ->RNC NE-> Rnc Radio Res ource Management-> Node B Configuration Information-> Node B Configuration Information xx-> Modify Advanced Parameter View-> Configuration Management ->OMM->UTRA N SubNetwork->RNC Managed Element-> Rnc Radio Resource Management->External UTRA N Cell ->External UTRAN Cell xx-> Modify Advanced Parameter Parameter Configuration
Configure this parameter based on Node B office direction; for c ell 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
24
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 radio
View-> Configuration Management -> NodeB NE ->SdrFunction object->UMTS network object->Baseband resource pool object->HS UPA SPI Parameter Configuration
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 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
SPI_WEIGHT =SPI+1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
SPI_WEIGHT =EXP((SPI+1)/2) 2 3 4 7 12 20 33 55 90 148 245 403 665 1097 1808
SPI_WEIGHT =SPI^3 1 8 27 64 125 216 343 512 729 1000 1331 1728 2197 2744 3375
25
15
16
2981
4096
5
5.1
Counter And Alarm

Counter List
There is no counter in this feature.
5.2
Alarm List
There is no alarm in this feature.
Glossary
A ACK AG C CFN D DPCCH E E-AGCH E-DCH E-DP CCH E-DP DCH E-HICH E-RGCH E-TFCI F FSN Frame Sequence Number E-DCH Absolute Grant Channel Enhanced Uplink Dedicated Channel E-DCH Dedicat ed Physical Control Channel E-DCH Dedicat ed Physical Data Channel E-DCH Hybrid A RQ Indicatior Channel E-DCH Relative Grant Channel E-DCH Transport Format Combination Indicator Dedic ated Physical Control Channel Connection Frame Number (counter) Acknowledgement Absolute Grant
26
FP G GBR H HARQ HSUPA I IR L LUP R M MAC-es/e E-DCH MA C MAC-d MAC MLPPP N Node B NACK NRT O OMM OMMB OMMR P PF PPP Q QoS
Frame Protocol
Guarant eed Bit Rat e
Hybrid Automatic Repeat Request High-Speed Uplink Packet Access
Incremental Redundancy
Last Used Power Ratio
Dedic ated MAC Medium Acess Control Multi-Label PPP
Base Station Negative Acknowledgement Non Real Time
Operate & Management Control OMM in Node B OMM in RNC
Proportional Fair Point to Point Protocol
Quality of Servic e
27
R RNC RG RTWP RL RLS RSN RNC RoT S SF SI SIR SPI SRNC SRB T TTI TNL TNS U UE UPH UMTS User Equipment UE Transmission Power Headroom Universal Mobile Telecommunications System Transmission Time Int erval Trans port Networdk Layer Trans port Network Subsystem Spreading Factor Scheduling Information Signal to Interference Ratio Scheduling Priority Indic ator Serving RNC Singalling Radio Bearer Radio Network Controller Relative Grant Received Total Wideband Power Radio Link Radio Link Set Retransmission Sequence Number Radio Network Controller Rise of Thermal
28

ZTE UMTS (U9.3) HSUPA Packet Scheduling Feature Guide - V4.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE UMTS (U9.3) HSUPA Packet Scheduling Feature Guide - V4.0

Uploaded by

Copyright:

Available Formats

Operator Logo

HSUPA Packet Scheduling

HSUPA Packet Scheduling Feature Guide

HSUPA Packet Scheduling Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

HSUPA Fast Scheduling

HSUPA protocol architecture in UTRAN

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

Associated Uplink Signalling

Associated Downlink Signalling

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

Basic operating principle of HSUPA

1 TNL bearer per MAC-d flow

MAC-e Scheduler MRC

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

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

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

HSUPA Flow Control

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

Description of Packet Scheduler

HSUPA fast scheduling mechanism in Node B

De-mux Associated Uplink Schedule Information

Uu E-HICH Uu E-AGCH Uu E-RGCH Downlink

AG HSUPA Scheduler NodeB RG

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

Key Algorithms of Packet Scheduler

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide

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

Operating mechanism of HSUPA packet scheduler

UE->: SI, HappyBit

Uplink processing uni t ->: E-TFCI, Eb/NoDPCCH SIR

The following figure shows the HSUPA scheduling procedure:

HSUPA scheduling procedure in Node B

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

HSUPA Packet Scheduling Feature Guide