differentiated hspa service(ran13.0_03)

7/27/2019 Differentiated HSPA Service(RAN13.0_03)

http://slidepdf.com/reader/full/differentiated-hspa-serviceran13003 1/35

Differentiated HSPA ServiceRAN13.0

Feature Parameter Description

Issue 03

Date 2012-05-30

HUAWEI TECHNOLOGIES CO., LTD.



Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/


mailto:[email protected]






WCDMA RAN

Differentiated HSPA Service Contents

Issue 03 (2012-05-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd

i

Contents

1 Introduction ................................................................................................................................ 1-1 1.1 Scope ............................................................................................................................................ 1-1 1.2 Intended Audience......................................................................................................................... 1-1 1.3 Change History .............................................................................................................................. 1-1

2 Overview...................................................................................................................................... 2-1 3 Differentiated HSPA Service Based on Service Type ...................................................... 3-1 4 Differentiated HSPA Service Based on User Priority ...................................................... 4-1 5 Settings for HSPA QoS Parameters ..................................................................................... 5-1

5.1 Description .................................................................................................................................... 5-1 5.2 Settings for the GBR ..................................................................................................................... 5-2 5.3 Settings for the HBR ..................................................................................................................... 5-2 5.4 Settings for User Priority ............................................................................................................... 5-2 5.5 Settings for THP Class .................................................................................................................. 5-2 5.6 Settings for the SPI ....................................................................................................................... 5-3 5.7 Settings for the SPI Weight ........................................................................................................... 5-3

5.7.1 Description ............................................................................................................................ 5-3 5.7.2 Mapping of E-DCH/HS-DSCH Category and MBR to Rate Range ...................................... 5-4 5.7.3 Mapping of the SPI and Rate Range to SPI Weight ............................................................ 5-4

6 Related Features ....................................................................................................................... 6-1 6.1 WRFD-020806 Differentiated Service Based on SPI Weight ....................................................... 6-1

7 Impact on the Network............................................................................................................. 7-1 7.1 WRFD-020806 Differentiated Service Based on SPI Weight ....................................................... 7-1

8 Engineering Guidelines........................................................................................................... 8-1 8.1 When to Use Differentiated Service Based on SPI Weight ........................................................... 8-1 8.2 Information to Be Collected ........................................................................................................... 8-1 8.3 Recommended Settings for Key Parameters ................................................................................ 8-1 8.4 Feature Deployment ...................................................................................................................... 8-4 8.5 Performance Optimization ............................................................................................................. 8-5

9 Parameters.................................................................................................................................. 9-1 10 Counters.................................................................................................................................. 10-1 11 Glossary .................................................................................................................................. 11-1 12 Reference Documents ......................................................................................................... 12-1



WCDMA RAN

Differentiated HSPA Service 1 Introduction



1-1

1 Introduction

1.1 Scope

This document describes the feature Differentiated HSPA Service. Differentiated HSPA service isclassified into differentiated HSPA service based on service type and differentiated HSPA service basedon user priority.

1.2 Intended Audience

This document is intended for:

Personnel who are familiar with WCDMA basics

Personnel who need to understand Differentiated HSPA Service

Personnel who work with Huawei products

1.3 Change HistoryThis section provides information on changes in different document versions.

There are two types of changes, which are defined as follows:

Feature change: refers to a change in the feature Differentiated HSPA Service.

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

Document Issues

The document issues are as follows:

03 (2012-05-30)

02 (2011-06-30)

01 (2011-04-30)

Draft B (2011-03-30)

Draft A (2010-12-30)

03 (2012-05-30)

This is the document for the third commercial release of RAN13.0.

Compared with issue 02 (2011-06-30) of RAN13.0, this issue has the following changes.

Change Type Change Description Parameter Change

Feature change None. None.

Editorial change The following chapters are added:

6 Related Features

7 Impact on the Network

None.

The engineering guideline is optimized. For details, see8 "Engineering Guidelines."

None.



WCDMA RAN

Differentiated HSPA Service 1 Introduction



1-2

02 (2011-06-30)

This is the document for the second commercial release of RAN13.0.

Compared with issue 01 (2011-04-30) of RAN13.0, this issue add the engineering guidelines about

Differentiated Service Based on SPI Weight.

01 (2011-04-30)

This is the document for the first commercial release of RAN13.0.

Compared with issue Draft B (2011-03-30) of RAN13.0, this issue has no change.

Draft B (2011-03-30)

This is the draft of the document for RAN13.0.

Compared with Draft A (2010-12-30) of RAN13.0, this issue optimizes the description.

Draft A (2010-12-30)This is the draft of the document for RAN13.0.

Compared with issue 01 (2010-12-20) of RAN12.0, this issue incorporates the following change:

SPI weight can be configured based on the SPI and rate range instead of based on SPI.



WCDMA RAN

Differentiated HSPA Service 2 Overview



2-1

2 Overview

As HSPA technology develops, HSPA channels have become the main radio bearers for UMTS services.

This feature is applicable only to HSPA channels. It provides differentiated service for users based onservice type and user priority.

Uu interface resources, channel element (CE) resources, and Iub interface resources are allocated toHSPA users according to resource scheduling algorithms. If these resources are not sufficient to providethe maximum bit rate (MBR) for all online HSPA users, the RAN will allocate these resources to usersbased on service type and user priority. High service quality is preferentially guaranteed for high-priorityservices and users. Higher-priority services such as speech services enjoy better service thanlower-priority services such as Best Effort (BE) services. Higher-priority users such as Gold users enjoybetter service than lower-priority users such as Copper users.

Differentiated HSPA service needs to be supported by CN, RAN and UE, as described in Table 2-1.

Table 2-1 Dependencies on NEs

NetworkElement

Description

CN The CN sends QoS parameters to the RNC.

RNC The RNC supports QoS mapping. Based on QoS mapping, the RNC converts the receivedQoS parameters into those that can be used within the RAN.

NodeB During Uu interface scheduling and Iub interface flow control, the NodeB allocates resourcesto services and users based on the QoS parameters received from the RNC. The NodeBprovides:

Differentiated service based on service type: The NodeB preferentially provides service for

higher-priority services. Differentiated service based on user priority: The NodeB preferentially provides service for

higher-priority users.

UE UEs report their E-DCH and HS-DSCH categories to the RNC for calculating the SchedulingPriority Index (SPI) weight.



WCDMA RAN

Differentiated HSPA Service

3 Differentiated HSPA Service Based on Service

Type



3-1

3 Differentiated HSPA Service Based on Service Type

PS services are generally carried on HSPA channels. According to 3GPP Release 8, CS AMR servicescan also be carried on HSPA channels.

Services carried on HSPA channels are classified into delay-sensitive services and throughput-sensitiveservices. Table 3-1 lists typical service types.

Table 3-1 Service types

Service Type Service QoS Requirement

Delay-sensitive services Signaling

VoIP

CS AMR

Low traffic volume

Short delay

Throughput-sensitive services Streaming

Interactive Background

IMS signaling

High traffic volume

High throughput

Different QoS strategies are provided for different types of services:

For delay-sensitive services, the Uu scheduling function limits the packet transmission delay to anacceptable range. For throughput-sensitive services, this function strives to provide rates not lower than the Guaranteed Bit Rate (GBR). QoS requirements of delay-sensitive services are preferentiallymet during scheduling because users are more sensitive to these services.

For delay-sensitive services, the NodeB does not perform flow control on the Iub interface. Therefore,these services are always allocated sufficient bandwidth. For throughput-sensitive services, flowcontrol must be performed. If congestion occurs on the Iub interface, bandwidth for these services isdecreased.

3GPP TS 23.107 defines only four service types, which cannot fully reflect the QoS requirements of services on a live network. For example, a Web page may contain video streams in addition to text andimages; email, video website browsing, and Bit Torrent (BT) downloads are all mapped to thebackground service. Services on a live network are complex and have different QoS requirements. TheRNC identifies and classifies complex service types and provides appropriate QoS to improve user experience.



WCDMA RAN


4 Differentiated HSPA Service Based on User

Priority



4-1

4 Differentiated HSPA Service Based on User Priority

Differentiated HSPA service based on user priority is mainly applicable to BE (throughput-sensitive)services: interactive and background services. There are three user priorities: Gold, Silver, and Copper.

This function enables telecom operators to set different GBRs, Happy Bit Rates (HBRs), and SPIweights for different user priorities. Based on these parameter settings, the NodeB providesdifferentiated service for different user priorities during Uu interface scheduling and Iub interface flowcontrol.

In case of resource insufficiency, higher-priority users are provided with better service quality.

Differentiated HSPA service based on user priority is implemented in the following ways:

Based on user priorities, GBRs are configured for BE services by the RNC, not the CN. HSPAscheduling strives to guarantee GBRs for BE services, so that users with different priorities obtaindifferent GBRs.

HBR is the expected throughput of users. When the data rate of a user reaches its HBR, the

scheduling function reduces the scheduling priority of this user. The RNC configures different HBRs for users of different priorities.

SPI weight is the weight of the SPI configured based on user priority and service type. It ranges from1% to 100%. When radio resources are insufficient, HSPA scheduling and flow control enableresources to be allocated among users based on SPI weight. If Gold, Silver, and Copper users are inthe same radio environment, the ratio of their throughput approximately equals the ratio of their SPIweight. Operators can set different SPI weight for users with different priorities.

Differentiated Service Based on SPI Weight (WRFD-020806 Differentiated Service Based on SPI Weight)is implemented as follows:

Generally, Iub flow control and Uu scheduling enable the NodeB to allocate bandwidth to users based ontheir SPI weight. If allocating bandwidth based on SPI weight does not meet GBR requirements of all BE

services, the RAN preferentially allocates bandwidth to the BE services to ensure all their GBRsregardless of their SPI weight. Then, the RAN allocates the remaining bandwidth based on SPI weight.

In this way, users of higher SPI weight enjoy better service. In addition, resource allocation differentiationamong users is quantified by the ratio of SPI weight among users.

The following is an example of differentiated service based on SPI weight:

The ratio of SPI weight between Gold, Silver, and Copper users is 9:3:1.

A cell has a total bandwidth of 3 Mbit/s.

There are altogether ten online users in the cell. Resources in the cell are not sufficient to meet thedata transmission requirements of all ten users.

The GBRs of Gold, Silver, and Copper users are all 64 kbit/s.

The following table lists how resources are allocated:

User Priority Gold Silver Copper

Number of Online Users 1 3 6

Mean User Throughput 1.1 Mbit/s 380 kbit/s 120 kbit/s

Differentiated Service Based on SPI Weight supports differentiated billing policies. For example,higher-charge-rate users are provided with better service. It also provides users with differentiated



WCDMA RAN


4 Differentiated HSPA Service Based on User

Priority



4-2

service quality based on service types. For example, low-charge-rate BE service users are provided withlow service-quality if network resources are insufficient.

For SPI weight settings, see the next chapter.



WCDMA RAN

Differentiated HSPA Service 5 Settings for HSPA QoS Parameters



5-1

5 Settings for HSPA QoS Parameters

5.1 Description

The CN sends QoS parameters to the RAN over the Iu interface through an RAB ASSIGNMENTREQUEST message. Based on QoS mapping, the RAN converts the received QoS parameters intothose that can be used within the RAN. Then, the RAN implements differentiated HSPA service based onthe QoS parameters. Figure 5-1 shows the HSPA QoS mapping. Operators may configure the QoSmapping by setting QoS parameters on the RNC.

Figure 5-1 QoS mapping

QoS mapping can be configured for individual operators:

If parameters for operator-oriented differentiated service are not configured, or the corresponding MMLcommands are unavailable, the settings of the RNC-oriented differentiated service parametersautomatically take effect.

When neither RAN sharing nor multi-operator core network (MOCN) is enabled, parameters for operator-oriented differentiated service do not need to be set.

When only RAN sharing is enabled, parameters for operator-oriented differentiated service can be set.

When only MOCN is enabled, parameters for operator-oriented differentiated service should not be set.However, if operators use different CN strategies, for example, different settings of allocation retentionpriority (ARP) or traffic handling priority (THP), these parameters should be set to guarantee servicefairness among operators.



WCDMA RAN




5-2

5.2 Settings for the GBR

The CN does not set GBRs for interactive and background services. To guarantee basic rates for thesetwo types of services, the RNC allows GBRs to be configured for them. GBRs vary according to user priority and link direction (uplink or downlink).

Table 5-1 Example of GBR mapping based on user priority

Direction Gold Silver Copper

Downlink 256 kbit/s 128 kbit/s 64 kbit/s

Uplink 256 kbit/s 128 kbit/s 64 kbit/s

Note: GBRs are configured based on user priority, traffic class (TC), traffic handling priority (THP), andR99/HSPA bearers. The example only shows configuration of GBRs based on user priority.

The mapping of TrafficClass , THPClass , BearType and UserPriority to GBR is set by running the SETUUSERGBR command on the RNC. The operator-oriented mapping is set by running the ADDUOPERUSERGBR or MOD UOPERUSERGBR command.

5.3 Settings for the HBR

The HBR is determined by the HappyBR parameter. The RNC delivers HappyBR to the NodeB on theIub interface.

When NodeB resources are limited, a user's HS-DSCH scheduling priority is reduced if the user'sHS-DSCH rate exceeds HappyBR . Moderately reducing the user's scheduling priority in this caseleaves more scheduling chances for users with throughput below their HBRs. As a result, the total

satisfaction level is increased. If this parameter is set to zero, it indicates that the NodeB does notdynamically adjust the HS-DSCH scheduling priority based on the HBR.

The mapping of TrafficClass , THPClass , and UserPriority to HappyBR is set by running the SETUUSERHAPPYBR command on the RNC. The operator-oriented mapping is set by running the ADDUOPERUSERHAPPYBR command.

5.4 Settings for User Priority

The user priority is determined by ARP. The mapping of ARP to the user priority is set by running theSET UUSERPRIORITY command. The operator-oriented mapping is set by running the ADDUOPERUSERPRIORITY or MOD UOPERUSERPRIORITY command.

Table 5-2 Default mapping of ARP to UserPriority

ARP 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

UserPriority Error Gold Silver Copper

5.5 Settings for THP Class

The THP class is determined by THP. The mapping of THP to the THP class is set by running the SETUTHPCLASS command. The operator-oriented mapping is set by running the ADD UOPERTHPCLASS or MOD UOPERTHPCLASS command.

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uusergbr_trafficclass.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uusergbr_thpclass.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uusergbr_beartype.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uusergbr_userpriority.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uuserhappybr_happybr.html









http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uuserhappybr_trafficclass.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uuserhappybr_thpclass.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uuserhappybr_userpriority.html



















WCDMA RAN




5-3

Table 5-3 Default mapping of THP to THPClass

THP 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

THPClass High Medium Low

5.6 Settings for the SPI

The mapping of TC, user priority, and THP class to the SPI is set on the RNC.

The SET USCHEDULEPRIOMAP command is used to set the mapping of TrafficClass , UserPriority , and THPClass to SPI .

The ADD UOPERSCHEDULEPRIOMAP command is used to set the operator-oriented mapping.

Table 5-4 Default mapping of TrafficClass, UserPriority, and THPClass to SPITrafficClass UserPriority THPClass SPI

Interactive Gold High 10

Gold Medium 9

Gold Low 8

Silver High 7

Silver Medium 6

Silver Low 5

Copper High 4

Copper Medium 3

Copper Low 2

Background Gold None 8

Silver None 5

Copper None 2

5.7 Settings for the SPI Weight

5.7.1 Description

The RNC determines SPI weight as follows:

Step 1 The RNC determines the rate range based on the UE’s E-DCH/HS-DSCH category and MBR.The rate range varies according to link direction.

Step 2 The RNC determines SPI weight based on the SPI and rate range.

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uschedulepriomap_trafficclass.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uschedulepriomap_userpriority.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uschedulepriomap_thpclass.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/uschedulepriomap_spi.html









WCDMA RAN




5-4

5.7.2 Mapping of E-DCH/HS-DSCH Category and MBR to Rate Range

The RNC determines the uplink (UL) and downlink (DL) rates based on the values of theUlCapacitySelect and DlCapacitySelect parameters, E-DCH/HS-DSCH category, and MBR.

In the DL− If DlCapacitySelect is set to MBR, the DL rate equals the MBR;

− If DlCapacitySelect is set to Min, the DL rate equals Min (RateCate, MBR);

− If DlCapacitySelect is set to Max, the DL rate equals Max (RateCate, MBR);

− If DlCapacitySelect is set to Category, the DL rate equals RateCate.

In the UL

− If UlCapacitySelect is set to MBR, the UL rate equals MBR;

− If UlCapacitySelect is set to Min, the UL rate equals Min (RateCate, MBR);

− If UlCapacitySelect is set to Max, the UL rate equals Max (RateCate, MBR);

−

If UlCapacitySelect is set to Category, the UL rate equals RateCate. RateCate is the peak rate supported by the HS-DSCH/E-DCH category.

Then the RNC determines the rate range based on the UL and DL rates. A rate range is the range that aDL or UL rate falls into. For example, if DlRateThreshold1 < DL Rate < DlRateThreshold2 , (DlRateThreshold1 -DlRateThreshold2 ) is the DL rate range.

There are 10 rate ranges altogether, denoted by {<T1, T1-T2, T2-T3, ... T8-T9, >T9}. T1 to T9 areconfigured by setting the following parameters in the SET UCAPARATERANGE command.

Table 5-5 Rate range parameters

DL Parameter Default Value UL Parameter Default Value

DlRateThreshold1 128 kbit/s UlRateThreshold1 128 kbit/s



DlRateThreshold4 1,000 kbit/s UlRateThreshold4 768 kbit/s

DlRateThreshold5 2,000 kbit/s UlRateThreshold5 1,000 kbit/s



DlRateThreshold8 16,000 kbit/s UlRateThreshold8 5,500 kbit/sDlRateThreshold9 32,000 kbit/s UlRateThreshold9 7,500 kbit/s

Operator-oriented mapping to the rate range is set by running the ADD UOPERCAPARATERANGE command.

5.7.3 Mapping of the SPI and Rate Range to SPI Weight

The RNC determines SPI weight based on the following table:

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucaparaterange_ulcapacityselect.html


http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucaparaterange_dlcapacityselect.html


























http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucaparaterange_dlratethreshold1.html


























WCDMA RAN




5-5

Figure 5-2 Mapping of SPI and rate range to SPI weight

The mapping of the SPI and rate range to SPI weight is set by running the SET USPIWEIGHT command.The operator-oriented mapping is set by running the ADD UOPERSPIWEIGHT command.



WCDMA RAN

Differentiated HSPA Service 6 Related Features



6-1

6 Related Features

6.1 WRFD-020806 Differentiated Service Based on SPI Weight

Required Features

WRFD-01061103 Scheduling based on EPF and GBR must be configured before WRFD-020806Differentiated Service Based on SPI Weight can be applied in the downlink over the Uu interface.

WRFD-01061402 Enhanced Fast UL Scheduling or WRFD-010638 Dynamic CE ResourceManagement must be configured before WRFD-020806 Differentiated Service Based on SPI Weightcan be applied in the uplink over the Uu interface. When WRFD-020806 Differentiated Service Basedon SPI Weight is used with WRFD-01061402 Enhanced Fast UL Scheduling, only uplink Uu interfaceresources can be differentially scheduled. However, when WRFD-020806 Differentiated ServiceBased on SPI Weight is used with WRFD-010638 Dynamic CE Resource Management, both uplinkUu interface resources and CE resources can be differentially scheduled.

WRFD-010610 HSDPA Introduction Package and WRFD-050405 Overbooking on ATM Transmission,

or WRFD-010610 HSDPA Introduction Package and WRFD-050408 Overbooking on IP Transmissionmust be configured before WRFD-020806 Differentiated Service Based on SPI Weight can be appliedin the downlink over the Iub interface.

WRFD-010637 HSUPA Iub Flow Control in Case of Iub Congestion must be configured beforeWRFD-020806 Differentiated Service Based on SPI Weight can be applied in the uplink over the Iubinterface.

Mutually Exclusive Features

N/A

Affected Features

N/A



WCDMA RAN

Differentiated HSPA Service 7 Impact on the Network



7-1

7 Impact on the Network

7.1 WRFD-020806 Differentiated Service Based on SPI Weight

Impact on System Capacity

WRFD-020806 Differentiated Service Based on SPI Weight impacts the downlink system capacity in thefollowing ways:

Differentiated service is based on an SPI weight during HSDPA scheduling over the Uu interface andflow control over the Iub interface. UEs with a larger SPI weight are allowed to use more Uu interfacepower resources, code resources, and Iub bandwidth resources, and therefore achieve a higher downlink throughput. When there is a large amount of data to transmit, the downlink throughput ratio of the UEs with the same conditions, such as the same GBR configuration and location, is approximatelyequal to their SPI weight ratio.

Increasing the SPI weight for UEs in weak coverage areas increases scheduling chances for the UEs,

reduces cell resource usage efficiency, and reduces cell throughput. Increasing the SPI weight for UEsin strong coverage areas increases scheduling chances for the UEs, increases cell resource usageefficiency, and increases cell throughput.

WRFD-020806 Differentiated Service Based on SPI Weight impacts the uplink system capacity in thefollowing ways:

Differentiated service is based on an SPI weight during HSUPA scheduling over the Uu interface, flowcontrol over the Iub interface, and CE scheduling (if Dynamic CE Resource Management is enabled).UEs with a larger SPI weight are allowed to use more Uu interface resources, Iub bandwidth resources,and CE resources, and therefore achieve a higher uplink throughput. When there is a large amount of data to transmit and the rate is not limited by the transmit power, UE capabilities, and QoS-relatedconfigurations (such as the GBR and MBR), the uplink throughput ratio of the UEs is approximately

equal to their SPI weight ratio. In scenarios with the same number of UEs and the same configurations, the uplink system throughput

when the UEs are assigned different SPI weight values is larger than when they are assigned thesame SPI weight.

Impact on Network Performance

No impact.



WCDMA RAN

Differentiated HSPA Service 8 Engineering Guidelines



8-1

8 Engineering Guidelines

8.1 When to Use Differentiated Service Based on SPI Weight

Use this feature when the operator expects to achieve the following:

Reduce the cost per bit by limiting the resources available to heavy-traffic service users.

At the initial phase of HSPA network deployment, operators may charge a monthly flat fee to attractHSPA users. Some of these users perform heavy-traffic downloading, which occupies a large amountof Uu or Iub interface resources. At the same time, the network load increases. Therefore, the cost per bit increases. Deploying Differentiated Service Based on SPI Weight enables operators to limit thedata rate for heavy-traffic service users, reducing the cost per bit. Before deploying this feature,operators must collect statistics, such as each user's total monthly traffic. Then, the operators candeploy this feature to reduce resources available to users whose total monthly traffic exceeds thespecified value. These users will be assigned lower priorities.

Increase revenue by implementing differentiated charging policies.

Operators implement differentiated charging policies, such as postpaid and prepaid services, toincrease revenue. Postpaid service users have higher priorities than prepaid service users. User priorities must be configured on the CN based on the charging policy. The RAN needs to adopt adifferentiated policy for allocating resources to users with different priorities. With this feature, postpaidservice users are allocated more bandwidth when resources are limited.

When this feature is activated, the downlink scheduling algorithm allocates resources based on the SPIweight, reducing the weight of channel conditions in the calculation of the scheduling priority. When mosthigh-priority UEs have poor channel conditions, the cell throughput decreases. In contrast, when mosthigh-priority UEs have good channel conditions, the cell throughput increases. When Iub resources, CEresources, and uplink Uu interface resources are limited, the cell throughput does not decrease.

8.2 Information to Be Collected Charging policy and user priorities configured on the CN

When user priorities are configured on the CN based on the charging policy, this feature providesbetter user experience for higher-priority users. This helps operators to increase revenue.

Cell load

When cell load is heavy, some resources, such as Uu interface resources, CE resources, andtransmission resources, may be insufficient. This feature reduces the cost per bit by limiting theresources available to heavy-traffic service users.

8.3 Recommended Settings for Key Parameters This section describes the key parameters and recommended settings for deploying DifferentiatedService Based on SPI Weight.

User Priority

The user priority is determined by ARP. The mapping of ARP to the user priority is set by running theSET UUSERPRIORITY command. There are three user priorities: gold, silver, and copper.

THP Class

The THP class is determined by THP. The mapping of THP to the THP class is set by running the SETUTHPCLASS command. There are three THP classes: high, medium, and low.



WCDMA RAN




8-2

MBR

The MBR of a UE in the RAN is determined by factors such as the MBR allocated by the CN, Uuinterface capability of the UE, and Uu interface bearer type.

If resources are sufficient on the RAN side, UEs experiencing heavy traffic can reach their MBRs. Toprovide differentiated rates for gold, silver, and copper users, operators need to configure MBRs indescending order for these types of users. If differentiated rates are not required, operators canconfigure the same MBR for all of the users.

If resources are insufficient on the RAN side, UEs may fail to reach their MBRs. The opportunities for UEs to obtain resources are closely related to their SPI weight. Operators can configure different SPIweights for gold, silver, and copper users to provide differentiated resource allocation.

Operators can configure MBRs for gold, silver, and copper users on the HLR based on their own policieswithout being limited by any rules on the RAN side. For example, gold users can be configured with anMBR greater than or equal to the MBR of silver users. The RAN side does not forcibly require that theMBR of gold users be greater than the MBR of silver users.

The following table lists example MBRs allocated by the CN.

Service Type HLR

Subscriber Class MBR

Postpaid service High-end subscriber 7.2 Mbit/s

Prepaid service plan A (monthlysubscription for 12.99 USD)

Common subscriber 7.2 Mbit/s

Prepaid service plan B (monthlysubscription for 12.99 USD)

Common subscriber 3.6 Mbit/s

Prepaid service plan C (monthlysubscription for 8.99 USD)

Low-end subscriber 2.0 Mbit/s

GBR

Differentiated guaranteed bit rates (GBRs) for gold, silver, and copper users are configurable on theRAN side by running the SET UUSERGBR command. GBRs are mainly configured for BE services.

When configuring GBRs, consider the following:

The GBR should be smaller than the planned full-coverage rate.

GBRs of UEs processing HSPA services should be greater than or equal to those of R99 UEsprocessing PS BE services. This ensures that the user experience for a service carried on an HSPAchannel is better than that for a service carried on an R99 channel.

To ensure throughput for specific UEs, operators can configure high GBRs for the UEs based onnetwork plan requirements on the CN and RAN sides.

Do not set GBRs to a large value unless necessary.

The following table lists example GBR configurations.



WCDMA RAN




8-3

Service Type HLR CN RAN

Subscriber Class MBR ARP THP SPI GBR

Postpaid service High-end

subscriber

7.2 Mbit/s 1 1 10 64 kbit/s

Prepaid service plan A(monthly subscription for 12.99 USD)

Commonsubscriber

7.2 Mbit/s 2 1 9 64 kbit/s

Prepaid service plan B(monthly subscription for 12.99 USD)

Commonsubscriber

3.6 Mbit/s 2 2 8 64 kbit/s

Prepaid service plan C(monthly subscription for 8.99 USD)

Low-endsubscriber

2 Mbit/s 3 1 7 64 kbit/s

Note that the GBR of an HSDPA UE can only be ensured in certain situations. For example, if an HSDPAUE is at the edge of cell coverage and channel quality is poor, a large amount of cell resources arerequired to ensure the downlink GBR of the UE. This reduces the total cell capacity, which is unfair toother UEs using services in the same cell.

To prevent this problem, operators need to configure the maximum percentage of power resourcesavailable for different downlink GBRs by running the SET RSCLMTPARA command on the NodeB side.If the Uu interface is congested, the GBR of a UE cannot be ensured if the percentage of power requiredto ensure the GBR in the maximum transmit power of the cell exceeds the maximum percentage of available power resources. The following table lists the default mapping between a GBR and the

maximum percentage of available power resources in the maximum transmit power of the cell.

GBR Maximum Percentage of Available Power Resources

8 kbit/s 10%

16 kbit/s 10%

32 kbit/s 15%

64 kbit/s 15%

128 kbit/s 20%

256 kbit/s 25%

384 kbit/s 30%

512 kbit/s 40%

640 kbit/s 45%

768 kbit/s 50%

896 kbit/s 55%

1024 kbit/s 60%



WCDMA RAN




8-4

GBR Maximum Percentage of Available Power Resources

1536 kbit/s 65%

1800 kbit/s 70%

Assuming that the GBR of a UE is 384 kbit/s, the maximum percentage of available power resources is30%. If the planned full-coverage rate for the cell is 384 kbit/s and Uu interface resources are insufficient,UEs at the cell edge can only obtain a rate lower than 384 kbit/s.

Uplink GBRs have a similar limitation on available power resources, but the uplink maximum percentageof available power resources is not configurable.

SPI

Operators can specify the SPI for resource allocation to different traffic classes. The SPI is determinedby the THP class (configured for interactive services), traffic class, and user priority. The mapping of thetraffic class, user priority, and THP class to the SPI is set by running the SET USCHEDULEPRIOMAP command. Signaling radio bearer (SRB) at the RRC layer, IP multimedia subsystem (IMS) signaling, and real-timeservices (conversational and streaming services) have an SPI in the range of 12-15. They are allhigh-priority services. For signaling and conversational services, the SPI does not vary with the user priority. BE services (background and interactive services) need to be configured with an SPI in therange of 2-11. The SPI varies according to the settings for the user priority and THP class. This variationdifferentiates BE services.

SPI Weight

Operators can specify the SPI weight to enable UEs of a class to obtain a certain percentage of resources. The SPI weight is given as a percentage and is configurable in the SET USPIWEIGHT command.

From RAN13.0 releases, the SPI weight can be configured based on the UE category and MBR, as wellas the user priority and traffic class. This configuration helps ensure that a UE with a high MBR(specified during the service subscription) or with a high capability class obtains high-priority services.

If Differentiated Service Based on SPI Weight and the Service Awareness feature are enabled, ensurethe following so that Differentiated Service Based on SPI Weight can produce the desired effect:

Maximum SPI weight x Service priority adjusting coefficient ≤ 100%

Minimum SPI weight x Service priority adjusting coefficient ≥ 1%

The service priority adjusting coefficient is specified by SERVICEPRIADJCOEF .

8.4 Feature Deployment For details on how to activate, verify, and deactivate this feature, see Configuring Differentiated ServiceBased on SPI Weight in the Feature Activation Guide.

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/udpucfgdata_servicepriadjcoef.html



http://localhost/var/www/apps/conversion/tmp/FAGHtml/mbsc/m-bsc-reconfiguration-guide/WRFD-020806.html









WCDMA RAN




8-5

8.5 Performance Optimization

Monitoring

Monitor the effect of this feature by comparing values of the following cell counters measured before andafter the Differentiated Service Based on SPI Weight feature is activated:

Table 8-1 Counters related to HSDPA services

Counter Name Description

VS.HSDPA.MeanGoldenBeChThroughput.TotalBytes

Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flowof BE Service for Golden Subscriber for Cell

VS.HSDPA.MeanSilverBeChThroughput.TotalBytes

Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flowof BE Service for Silver Subscriber for Cell

VS.HSDPA.MeanCopperBeChThro

ughput.TotalBytes

Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow

of BE Service for Copper Subscriber for CellVS.HSDPA.MeanGoldenBeChThroughput

Mean Downlink Throughput of HSDPA MAC-d Flow of BEService for Golden Subscriber for Cell

VS.HSDPA.MeanSilverBeChThroughput

Mean Downlink Throughput of HSDPA MAC-d Flow of BEService for Silver Subscriber for Cell

VS.HSDPA.MeanCopperBeChThroughput

Mean Downlink Throughput of HSDPA MAC-d Flow of BEService for Copper Subscriber for Cell

Auxiliary counter: VS.HSDPA.UE.Mean.Cell (Average Number of HSDPA UEs for Cell)

Table 8-2 Counters related to HSUPA services

Counter Name Description

VS.HSUPA.GoldenBeMeanChThroughput.TotalBytes

Number of Total Bytes Received in Uplink of HSUPA MAC-dFlow of BE Service for Golden Subscriber for Cell

VS.HSUPA.SilverBeMeanChThroughput.TotalBytes

Number of Total Bytes Received in Uplink of HSUPA MAC-dFlow of BE Service for Silver Subscriber for Cell

VS.HSUPA.CopperBeMeanChThroughput.TotalBytes

Number of Total Bytes Received in Uplink of HSUPA MAC-dFlow of BE Service for Copper Subscriber for Cell

VS.HSUPA.GoldenBeMeanChThroughput

Mean Uplink Throughput of HSUPA MAC-d Flow of BE Servicefor Golden Subscriber for Cell

VS.HSUPA.SilverBeMeanChThroughput

Mean Uplink Throughput of HSUPA MAC-d Flow of BE Servicefor Silver Subscriber for Cell

VS.HSUPA.CopperBeMeanChThroughput

Mean Uplink Throughput of HSUPA MAC-d Flow of BE Servicefor Copper Subscriber for Cell

Auxiliary counter: VS.HSUPA.UE.Mean.Cell (Average Number of HSUPA UEs for Cell)

To monitor this feature, collect statistics on the average throughput of gold, silver, and copper users.Ensure that the statistics are measured hourly during peak and off-peak hours. Ensure that the users are



WCDMA RAN




8-6

in the same cell supporting HSPA services. Compare the statistics measured before and after activatingthe feature.

The expected result is as follows after Differentiated Service Based on SPI Weight is activated:

During peak hours, the throughput of gold users increases but that of lower-priority users decreases. During off-peak hours, lower-priority users obtain more bandwidth than they would during peak hours

because there are a smaller number of UEs and more resources.

The total uplink and downlink throughput in the cell does not decrease.

The throughput ratio between gold, silver, and copper users may not perfectly match their SPI weight ratio because of differences in user behavior, user distribution, data volume, and channel quality.

Parameter Optimization

If long-term observation shows that the throughput of gold, silver, and copper users does not change asexpected after this feature is activated, adjust the mapping of SPI to SPI weight to change the rates

allocated to the three types of users.

To increase the throughput for a certain type of user during peak hours, increase the SPI weight mappedto the SPI of the user type. Similarly, to reduce the throughput for a certain type of user during peakhours, reduce the SPI weight mapped to the SPI. For example, assume that the ratio of the SPI weightbetween gold, silver, and copper users is 9:3:1. When there is a large amount of data to transmit andradio resources are insufficient, gold, silver, and copper users in the same radio environment have their throughput in descending order. The ratio of their throughput is approximately equal to the ratio of their SPI weight. If you want to increase the throughput of silver users, you could change the ratio to 9:5:1.



WCDMA RAN

Differentiated HSPA Service 9 Parameters



9-1

9 Parameters

Table 9-1 Parameter description

Parameter ID NE MML Command Feature ID Feature Name Description

BearType BSC6900

SETUUSERGBR(Mandatory)

WRFD-050424 Traffic PriorityMapping ontoTransmissionResources

Meaning:Bearer typeof the service. R99indicates that theservice is carried ona non-HSPA channel.HSPA indicates thatthe service is carriedon an HSPA channel.

GUI ValueRange:R99, HSPA

Actual ValueRange:R99, HSPA

Unit:None

Default Value:None

DlCapacitySelect

BSC6900

SETUCAPARATERANGE(Optional)

WRFD-020806 DifferentiatedService Based onSPI Weight

Meaning:Method of determining anHSDPA service ratewhen thedifferentiated HSPA

service based on SPIweight function isenabled. Value MBRindicates that theHSDPA service rateis the downlink MBRassigned by the CN.Value Categoryindicates that thepeak ratecorresponding to theUE HSDPA category

is used. Value Minindicates that thesmaller one betweenMBR and the peakrate corresponding tothe UE HSDPAcategory is used.Value Max indicatesthat the greater onebetween MBR andthe peak ratecorresponding to theUE HSDPA category



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-uusergbr.html







http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-ucaparaterange.html















WCDMA RAN




9-2


is used.

GUI Value

Range:MBR~0Category~1

Min~2

Max

Actual ValueRange:MBR,Category, Min, Max

Unit:None

Default Value:Min

DlRateThreshold1

BSC6900



Meaning:Downlinkrate threshold 1. Thisparameter is used todetermine the valuerange of an HSDPAservice rate when thedifferentiated HSPAservice based on SPIweight function isenabled. The SPIweight is determinedaccording to thevalue range.

GUI ValueRange:0~256000

Actual ValueRange:0~256000

Unit:kbit/s

Default Value:128

DlRateThreshold2

BSC6900



Meaning:Downlinkrate threshold 2. Thisparameter is used todetermine the valuerange of an HSDPAservice rate when thedifferentiated HSPAservice based on SPIweight function isenabled. The SPIweight is determinedaccording to the

value range.



























WCDMA RAN




9-3




Unit:kbit/s

Default Value:384

HappyBR BSC6900

SETUUSERHAPPYBR(Optional)

WRFD-01061010 HSDPA FlowControl

Meaning:Defines thehappy bit rate of thebest effort (BE)service with differentuser priorities(user priorities can be set

by parameter UserPriority). ThisHappy bit rate is sentto NodeB by RNCthrough the Iubinterface. When theNodeB resource islimited and theHS-DSCH bit rate of the user exceeds theHappy bit rate, theHS-DSCH

scheduling prioritywill be decreased.When this parameter is set to zero, itindicates that NodeBwill not adjust theHS-DSCHscheduling priority.If the value of theparameter HappyBRin command ADDUOPERUSERHAPPYBR is larger than5000, it will be set tothe minimum of theHappyBR value inSETUUSERHAPPYBRand 5000.





http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-uuserhappybr.html










WCDMA RAN




9-4


Unit:kbit/s

Default Value:0

ServicePriAdjCoef

BSC6900

SETUDPUCFGDATA(Optional)

None None Meaning:Specifiesthe coefficient for adjusting servicepriority weight in thematchingrecord.(Adjusted SPIWeight = min (InitialSPI weight *ServicePriAdjCoef *10%, 100),Initial SPIweight is set by the

"SpiWeight"parameter on RNC.).

Note: Parameter "ServicePriAdjCoef"will be replaced with"ServPriAdjCoefHigh","ServPriAdjCoefMiddle", and"ServPriAdjCoefLow"in current and later versions.


Actual ValueRange:10%~1000%

Unit:0.1

Default Value:10

SPI BSC6900

SETUSCHEDULEPRIOM

AP(Mandatory)

WRFD-020806 DifferentiatedService Based on

SPI Weight

Meaning:Schedulingpriority of interactive

and backgroundservices. Value 11indicates the highestpriority, while value 2indicates the lowestpriority. Values 0, 1,12, 13, 14, and 15are reserved for theother services.

GUI ValueRange:2~11

Actual Value




http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-udpucfgdata.html






http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-uschedulepriomap.html















WCDMA RAN




9-5


Range:2~11

Unit:None

Default Value:None

THPClass BSC6900

SETUSCHEDULEPRIOM AP(Mandatory)

WRFD-050424

WRFD-020806

Traffic PriorityMapping ontoTransmissionResources

DifferentiatedService Based onSPI Weight

Meaning:TrafficHandling Priority(THP) class that theTHP

priority ismapped to. Thisparameter is valid for only

interactiveservices. Themapping relationshipbetween the

traffic handlingpriority value of INTERACTIVEservice and its

correspondingclass can be setthrough command

"SET

UTHPCLASS".

GUI ValueRange:High,Medium, Low

Actual ValueRange:High,Medium, Low

Unit:None

Default Value:None

THPClass BSC6900


WRFD-050424

WRFD-020806





interactive

services. The























WCDMA RAN




9-6


mapping relationshipbetween the

traffic handlingpriority value of INTERACTIVEservice and its

correspondingclass can be setthrough command"SET

UTHPCLASS".

GUI ValueRange:High,Medium, Low


Unit:None

Default Value:None

THPClass BSC6900

SETUUSERHAPPYBR(Mandatory)

WRFD-050424

WRFD-020806





interactiveservices. Themapping relationshipbetween the

traffic handling

priority value of INTERACTIVEservice and its

correspondingclass can be setthrough command"SET

UTHPCLASS".

GUI ValueRange:High,

Medium, Low













WCDMA RAN




9-7



Unit:None

Default Value:None

TrafficClass BSC6900



Meaning:Traffic classwhich includes BestEffort(BE) and PTT.BE servicescomprise interactiveservices, backgroundservices, and IMS.

GUI ValueRange:INTERACTIVE, BACKGROUND,IMSSIGNALLING,PTT

Actual ValueRange:INTERACTIVE, BACKGROUND,IMSSIGNALLING,PTT

Unit:None

Default Value:None



WRFD-01061010 HSDPA FlowControl

Meaning:Traffic class

GUI ValueRange:INTERACTIVE, BACKGROUND

Actual ValueRange:INTERACTIVE, BACKGROUND

Unit:None

Default Value:None



WRFD-050424

WRFD-020806



Meaning:Trafficclass. Thisparameter onlyapplies to interactiveand backgroundservices, as theScheduling PriorityIndicator (SPI) of the

other classes suchas conversational or

































WCDMA RAN




9-8


streaming areconfigured bydefault.

GUI ValueRange:INTERACTIVE, BACKGROUND

Actual ValueRange:INTERACTIVE, BACKGROUND

Unit:None

Default Value:None

UlCapacitySelect BSC6900 SETUCAPARATERANGE(Optional)


Meaning:Method of determining anHSUPA service ratewhen thedifferentiated HSPAservice based on SPIweight function isenabled. Value MBRindicates that theHSUPA service rateis the uplink MBRassigned by the CN.Value Categoryindicates that thepeak ratecorresponding to theUE HSUPA categoryis used. Value Minindicates that thesmaller one betweenMBR and the peakrate corresponding tothe UE HSUPAcategory is used.Value Max indicates

that the greater onebetween MBR andthe peak ratecorresponding to theUE HSUPA categoryis used.

GUI ValueRange:MBR~0

Category~1

Min~2















WCDMA RAN




9-9


Max

Actual Value

Range:MBR,Category, Min, Max

Unit:None

Default Value:Min

UserPriority BSC6900



Meaning:User priority that is definedaccording to the Allocation/RetentionPriority (ARP) fromthe RAB assignment.

The user classes indescending order of priority are Gold,Silver, and Copper.For details, see helpinformation of the"SETUUSERPRIORITY"command.

GUI ValueRange:GOLD,SILVER, COPPER

Actual ValueRange:GOLD,SILVER, COPPER

Unit:None

Default Value:None



WRFD-050424

WRFD-020806



Meaning:User priority that is definedaccording to the Allocation/RetentionPriority (ARP) fromthe RAB assignment.The user classes indescending order of priority are Gold,Silver, and Copper.For details, see helpinformation of the"SETUUSERPRIORITY"command.

GUI Value























WCDMA RAN




9-10


Range:GOLD,SILVER, COPPER


Unit:None

Default Value:None




Meaning:User priority that is definedaccording to the Allocation/RetentionPriority (ARP) from

the RAB assignment.The user classes indescending order of priority are Gold,Silver, and Copper.For details, see helpinformation of the"SETUUSERPRIORITY"command.

GUI ValueRange:GOLD,SILVER, COPPER


Unit:None

Default Value:None













WCDMA RAN

Differentiated HSPA Service 10 Counters



10-1

10 Counters

There are no specific counters associated with this feature.



WCDMA RAN

Differentiated HSPA Service 11 Glossary



11-1

11 Glossary

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

http://localhost/var/www/apps/conversion/tmp/scratch_8/Glossary.htm






WCDMA RAN

Differentiated HSPA Service 12 Reference Documents

12 Reference Documents

None.