ZWF25!05!001 QoS Mapping for HSUPA Service

Feature Deployment and Testing GuideQoS Mapping for HSUPA ServiceFeature ID: ZWF25-05-001

Version: V3.11.10

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 2012 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2012-6-18 First eition

Serial Number: SJ-20120802112720-228

Publishing Date: 2012-06-18 (R1.0)

SJ-20120802112720-228|2012-06-18 (R1.0) ZTE Proprietary and Confidential

ContentsChapter 1 Functional Description............................................................. 1-1

Chapter 2 Preparations.............................................................................. 2-1

Chapter 3 Data configuration .................................................................... 3-1

Chapter 4 Testing ....................................................................................... 4-14.1 Test Purpose...................................................................................................... 4-1

4.2 Steps for Test..................................................................................................... 4-1

4.3 Expected Results ............................................................................................... 4-3

Chapter 5 Counter List............................................................................... 5-1

I


II


Chapter 1Functional DescriptionRNC maps RAB QoS parameters from CN to the basic priority used in the UTRAN. AndRNC maps basic priority to Scheduling Priority Indicator (SPI)for HSUPA service.

The HSUPA packet scheduler determines system resource utilization and load based onthe following information, and then allocates system resources to different UEs by followingcertain priority policy:

l Uplink Reference Received Total Wide Band Power (RefRTWP) configured by RNCthrough NBAP.

l Maximum Target Received Total Wideband Power (MaxRTWP) (refer to ZXWR RNCRadio Network Controller Radio Parameter Reference (Volume II)).

l Target Non-serving E-DCH to Total E-DCH Power Ratio (NServToTotalPwr) (refer toZTE UTMS Overload Control Feature User Guide).

l UE reported status information.l UE QoS configured by RNC through NBAP.l Cell radio resources.l Node B resource processing resources information.

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

Figure 1-1 Operating mechanism of HSUPA packet scheduler

1-1


Feature Deployment and Testing Guide Feature ID: ZWF25-05-001

The following figure shows the HSUPA scheduling procedure:

Figure 1-2 HSUPA scheduling procedure in Node B

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:

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

l E-TFCI currently used by UE andMAC-e PDUmultiplexing information (containedin MAC-e PDU head and used to obtain the type of MAC-e PDU currently sent byUE and data volume).

l Current DPCCH and E-DCH signal quality of UE (SIR and Eb/No, reported by theBaseband Processing Unit and used to calculate UE-contributed load).

l 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 typethrough NBAP. For details, refer to ZTE UMTS QoS Feature User Guide).

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

l QoS parameter configured by RNC for UE services: Maximum Number ofBits per MAC-e PDU for Non-scheduled Transmission (The independent datatransmission capability obtained by UE without scheduling. This parameter isconfigured for Node B by RNC based on the service type through NBAP).

1-2


Chapter 1 Functional Description

l Cell interference information (RTWPcurrent is measured at Node B).l CE resource indication.l Reference Received Total Wide Band Power (RefRTWP), Maximum Target

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

2. Determine UE, air interface and Node B resource utilization and load:l The measurement unit of Node B measures air interface interference, and sends

the measurement result RTWPcurrent to the scheduler. The scheduler calculatescurrent 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)

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

Pn refers to background noise and takes the value of RefRTWP (ReferenceReceived Total Wide Band Power). The original unit of Pn is dBm and translatedinto mW in the above equation. RNC notifies of Node B of Pn through NBAPafter internal measurement.

MaxRTWP refers to the Maximum Target Received Total Wideband Power. Theoriginal 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 convertedinto dimensionless ratio during calculation.

l 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 obtainMAC-e PDU, SI and Eb/No, and sends MAC-e PDU multiplexing information tothe 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 noisepower (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, andreflects 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, andcalculates scheduling priority which is a variable for each UE based on realtime

1-3



collected parameters, so as to ensure traffic fairness among UEs and make full useof system resources as well. The PF algorithm features the following:

l The scheduling priority is in direct proportion to current uplink to-be-transmitteddata volume (or current available transmission rate), that is, the larger the datavolume in the buffer area of UE, the higher the scheduling priority and the morechance the UE will be scheduled preferentially.

l 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 higherthe scheduling priority. The UEwith low transmission throughput will be scheduledpreferentially so as to ensure fairness.

UEs with higher scheduling priorities will take precedence over UEs with lower ones inpreempting more resources, resulting in rate decrease for the latter. But UEs originallywith lower scheduling priorities are given higher scheduling priorities because of theirlow transmission throughput, and thus they will be scheduled preferentially to ensurefairness 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 nTTI(s) (n refers to current time).

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

l If services are offered for UE m:

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

l Other cases:

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

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 thesmallest one of the following values: Data size in UE buffer area, size of data thatcan be transmitted in relation to the rest power of UE, and maximum rate limit ofUE.

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 cannotreceive data. It is an internal parameter and cannot be configured.

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

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

FairnessWgt refers to fairness factor. It is an internal parameter (value: 1) andcannot be configured.

1-4



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 ofUE.

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

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

SPI_WEIGHT is mapped through Table 1 according to SPI(0~15) configuredby RNC. The default mapping is the second column of Table 1. Operators canconfigure the mapping.

l For UEs with Rn not less than GBR:

GBRweight = 0, (9)

l For UEs with Rn less than GBR:

GBRweight = MaxGBRWeightValue, (10)

MaxGBRWeightValue is an internal parameter, with value of 389376. If the actualrate of a UE is lower than GBR, GBRweight will increase, resulting in a raise in UEscheduling priority so that resources can be preferentially allocated for this UE.

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

l When interactive-/background-class services are carried on E-DCH, RNCprovides configuration of nominal bit rate EdchNormBitRate. For details,see ZTE UMTS QoS Feature User Guide. For interactive-/background-classservices, RNC maps EdchNormBitRate into the QoS parameter of UE: MAC-esGuaranteed 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 comparativelylow, so the ultimate scheduling priority of them will be lower than that of Streamingservices with higher SPI.

4. Allocate available system resources in descending sequence of UE priorities.l Calculate available cell load based on the cell and UE load obtained in steps 1

and 2 as well as Node B processing capacity.l Reserve load for R99RT, R99NRT, SRB andHSUPA non-scheduled transmission

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

l Determine the transmission rate requested by UE. The UE requestedtransmission rate is subject to the service requirements (Service requirementsare jointly determined by the buffer area size in the SI as well as HappyBitreported by UE. For UEs with HappyBit = Unhappy, their service requirementsequal to the size of buffer area; for UEs with HappyBit = Happy, their servicerequirements equal to the size of data block corresponding with current grantsobtained), maximum rate in relation to UE category, maximum subscribed rate

1-5



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

l The HSUPA scheduler allocates resources for UEs in descending sequence oftheir scheduling priorities.

l If current available system load and CE resources are larger than the summationof load contributed by all UE requested transmission rates, the scheduler allocatesgrants in relation to requested rates for all UEs.

l If current available system load or CE resources are less than the summationof load contributed by all UE requested transmission rates, the scheduler firstcalculates the load and CE resources contributed by the rate requested by theUE with highest priority.

l The scheduler releases grants of UEs with low priorities one by one in ascendingsequence of scheduling priorities. Then it calculates the load contributed afterreleasing grants until the load and CE resources released from UEs with lowpriorities meet the requirements of the UEwith highest priority. If the load releasedfromUEswith low priorities still fails tomeet all requirements of the UEwith highestpriority, the UE with highest priority will have to use the load and CE resourcesreleased from those with low priorities.

l When allocating resources, the scheduler calculates CE resources currently usedby each UE as well as available CE resources of Node B. Then it allocates theminimum available CE resources and load of Node B to the UE with highestpriority.

l The scheduler allocates CE resources and load to the rest UEs with high prioritiesin the queue by following the above rule until all system resources are used up(all UEs with low priorities have their resources released).

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

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

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

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 relationbetween receive powers of Node B DPCCH and E-DCH is given by the followingequation:

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

And,

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

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:

1-6



((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 andUE grant. The UE service grant can be obtained through UE-contributed load, or viceversa.

l For a UE with highest scheduling priority, the scheduler needs to send AG forscheduling to facilitate the UE to quickly obtain required grant. The AG cannotbe used for the rest UEs after it is engaged because AGCH is shared among allUEs. The RGCH, however, is dedicated control channel allocated for each UE.Therefore, for the rest UEs, they can either get more resources or release theirresources by RG commands. The scheduler sends RG=UP to UEs allocated withmore resources, RG=DOWN to UEs with resources released and RG=HOLD toUEs with grants retained during scheduling.

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

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

1-7



This page intentionally left blank.

1-8


Chapter 2PreparationsLicense

N/A

Hardware Requirement

Hardware requirement is shown in Table 2-1.

Table 2-1 Hardware Requirement

NE Requirement

RNC None

NodeB None

Software Requirement

Software requirement is shown in Table 2-2.

Table 2-2 Software Requirement

NE Involved Version Requirement

UE YES UMTS FDD Number: 2

Category: 6 (E-DCH

category)

Release : R6

NodeB NO V4.11.10.14 None

RNC YES V3.11.10.11 ZTE equipment

MSCS YES None ZTE equipment

MGW YES None ZTE equipment

SGSN YES None ZTE equipment

GGSN NO None None

HLR NO None None

Topology

Topology is shown in Figure 2-1.

2-1



Figure 2-1 Topology

2-2


Chapter 3Data configurationSGSN/GGSN - ZTE

N/A

MSC/MGW - ZTE

N/A

HLR – ZTE

1. UE1 subscribes background service, MBR= UL2Mbps/ DL8Mbps, with ARP1.

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_background

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[0] = 8192000


TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.priorityLevel = 11

2. UE2 subscribes background service, MBR= UL2Mbps/ DL8Mbps, with ARP2.

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_background



TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItemFirst.rAB_Parameters.allocationOrRetentionPriority.priorityLevel = eRANAP_PriorityLevel_highest

RNC

l HSPA Support Method: Support HSUPA, HSDPA and DCH

3-1



Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and CellReselection > HSPA Support Method

l Maximum Target Received Total Wideband Power: 6

Path: View > Configuration Management > RNC Managed Element > RNC RadioResource Management > UTRAN Cell > UTRAN Cell xxx > Advanced Parameter> HSPA Configuration Information in A Cell

l Check UE1 and UE2's SPI

à UE1's APR is 2, so APR Segment is 1, Basic Priority is 7, Scheduling Priority is7.

3-2


Chapter 3 Data configuration

Path: View > Configuration Management > RNC Managed Element > RNCRadio Resource Management > QOS Relevance Configuration > QOSConfiguration

à UE1's APR is 11, so APR Segment is 3, Basic Priority is 0, Scheduling Priority is0.

Path: View > Configuration Management > RNC Managed Element > RNCRadio Resource Management > QOS Relevance Configuration > QOSConfiguration

NodeB

N/A

3-3




3-4


Chapter 4TestingTable of Contents

Test Purpose ..............................................................................................................4-1Steps for Test .............................................................................................................4-1Expected Results .......................................................................................................4-3

4.1 Test PurposeThe purpose of this test case is to verify if the function of QoS Mapping for HSUPA Serviceis working normally.

Related document:

l ZTE UMTS QoS Feature Guide.docxl ZTE UMTS HSUPA Packet Scheduling Feature Guide.docx

4.2 Steps for Test1. UE1 activates a PS call in Cell1 and starts FTP uploading.

4-1



UE1 DU Meter Speed

2. UE2 activates another PS call in Cell1 and starts FTP uploading.

4-2


Chapter 4 Testing

UE1 DU Meter Speed

UE2 DU Meter Speed

3. Deactivate both the PDPs.

4.3 Expected ResultsThe UL data rate of UE1 is decreased after UE2 activates the second PS call. Accordingto the service priority, the data rate of UE2 is higher than that of UE1.

4-3




4-4


Chapter 5Counter List

C310010153 Uplink traffic of HSUPA for Conversational class in best cell

C310010154 Uplink traffic of HSUPA for Streaming class in best cell

C310010155 Uplink traffic of HSUPA for Interactive class in best cell

C310010156 Uplink traffic of HSUPA for Background class in best cell

C310010177 Uplink traffic of HSUPA for Conversational class in non-best cell

C310010178 Uplink traffic of HSUPA for Streaming class in non-best cell

C310010179 Uplink traffic of HSUPA for Interactive class in non-best cell

C310010180 Uplink traffic of HSUPA for Background class in non-best cell

C310010292 Uplink Iub volume of HSUPA RAB for Conversational class

C310010293 Uplink Iub volume of HSUPA RAB for Streaming class

C310010294 Uplink Iub volume of HSUPA RAB for Interactive class

C310010295 Uplink Iub volume of HSUPA RAB for Background class

C310020426 Number of uplink HSUPA RLC PDU, Conversational class

C310020427 Number of uplink HSUPA RLC PDU, Streaming class

C310020428 Number of uplink HSUPA RLC PDU, Interactive class

C310020429 Number of uplink HSUPA RLC PDU, Background class

C310790005 Iu Uplink volume of HSUPA

C310800021 HSUPA Uplink volume of Iub for Conversational class

C310800022 HSUPA Uplink volume of Iub for Streaming class

C310800023 HSUPA Uplink volume of Iub for Interactive class

C310800024 HSUPA Uplink volume of Iub for Background class

C310800029 Uplink header volume of Iub HSUPA traffic

C310010162 Uplink volume of VoIP in E-DCH in best cell

C310010181 Uplink volume of VoIP in E-DCH in non-best cell

C310010303 Uplink Iub volume of VoIP in E-DCH

C310020407 Number of UL SDU sent by RLC, Traffic on E-DCH for PS domain

C310020415 Number of UL SDU received by RLC, Traffic on E-DCH for PS domain

5-1


Documents

ZWF25!05!001 QoS Mapping for HSUPA Service