Differentiated HSPA Service (RAN16.0 - 01)

WCDMA RAN
Differentiated HSPA Service Feature

Parameter Description
Issue
01
Date
2014-04-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. 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 a 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:
support@huawei.com
Issue 01 (2014-04-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
WCDMA RAN
Differentiated HSPA Service Feature Parameter Description
Contents
Contents
1 About This Document..................................................................................................................1
1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
1.4 Differences Between Base Station Types.......................................................................................................................2
2 Overview.........................................................................................................................................4
3 Differentiated HSPA Service Based on Service Type............................................................6
4 Differentiated HSPA Service Based on User Priority............................................................8
5 Differentiated HSPA Service Based on Terminal.................................................................10
6 Settings for HSPA QoS Parameters.........................................................................................11
6.1 Description....................................................................................................................................................................11
6.2 Settings for the GBR.....................................................................................................................................................12
6.3 Settings for the HBR.....................................................................................................................................................13
6.4 Settings for User Priority..............................................................................................................................................13
6.5 Settings for THP Class.................................................................................................................................................14
6.6 Settings for the SPI.......................................................................................................................................................14
6.7 Settings for the SPI Weight..........................................................................................................................................15
6.7.1 Description.................................................................................................................................................................15
6.7.2 Mapping of E-DCH/HS-DSCH Category and MBR to Rate Range.........................................................................15
6.7.3 Mapping of the SPI and Rate Range to SPI Weight..................................................................................................17
7 Related Features...........................................................................................................................18
7.1 WRFD-020806 Differentiated Service Based on SPI Weight......................................................................................18
7.2 WRFD-150255 Differentiated Service Based on Terminal..........................................................................................19
8 Network Impact...........................................................................................................................21
9 Engineering Guidelines.............................................................................................................23
9.1.1 When to Use Differentiated Service Based on SPI Weight.......................................................................................23
Issue 01 (2014-04-30)

ii
WCDMA RAN
Contents
9.1.2 Required Information................................................................................................................................................24

9.1.3 Deployment...............................................................................................................................................................24
9.1.4 Performance Monitoring............................................................................................................................................33
9.1.5 Parameter Optimization.............................................................................................................................................36
9.1.6 Troubleshooting.........................................................................................................................................................36
9.2.1 When to Use Differentiated Service Based on Terminal...........................................................................................36
9.2.2 Required Information................................................................................................................................................36
9.2.3 Deployment...............................................................................................................................................................37
9.2.4 Performance Monitoring............................................................................................................................................47
9.2.5 Parameter Optimization.............................................................................................................................................49
9.2.6 Troubleshooting.........................................................................................................................................................49
10 Parameters...................................................................................................................................50
11 Counters....................................................................................................................................106
12 Glossary.....................................................................................................................................126
13 Reference Documents.............................................................................................................127
Issue 01 (2014-04-30)

iii
WCDMA RAN
1 About This Document
About This Document
1.1 Scope
This document describes WRFD-020806 Differentiated Service Based on SPI Weight, including
its technical principles, related features, network impact, and engineering guidelines.
1.2 Intended Audience

This document is intended for personnel who:
l
Need to understand the features described herein
Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l
Feature change
Changes in features of a specific product version
Editorial change
Changes in wording or addition of information that was not described in the earlier version
RAN16.0 01 (2014-04-30)
This issue includes the following changes.
Issue 01 (2014-04-30)
Change Type
Change Description
Parameter Change
Feature change
None
None

WCDMA RAN
Change Type
Change Description
Parameter Change
Editorial change
Added counters used to

monitor performance of
Differentiated Service Based
on SPI Weight. For details,
see section 9.1.4
Performance Monitoring.
None
Added information required

before deployment of
on Terminal. For details, see
section 9.2.2 Required
Information.
None
RAN 16.0 Draft A (2013-01-20)

Compared with Issue 02(2013-12-30) of RAN15.0, Draft A (2014-01-20) of RAN16.0 includes
the following changes.
Change Type
Change Description
Parameter Change
Feature change
Modified the engineering guideline of

the Differentiated Service Based on
Terminal feature. For details, see 9.2
WRFD-150255 Differentiated
Service Based on Terminal.
Added the following

parameters:
None
None
Editorial change
PROCESSSWITCH5
(BSC6900,BSC6910):
DIFF_SERVICE_ON_T
ERMINAL_SWITCH
1.4 Differences Between Base Station Types

This document applies to the following types of base stations.
Base Station
Model
Macro
l 3900 series base stations

l DBS3800
l BTS3812E
l BTS3812AE
Micro
l BTS3803E
l BTS3902E
Issue 01 (2014-04-30)

WCDMA RAN
Base Station
Model
LampSite
DBS3900
The features described in this document are implemented in the same way on macro, micro, and
LampSite base stations.
Issue 01 (2014-04-30)

WCDMA RAN
2 Overview
Overview
As HSPA technology develops, HSPA channels have become the main radio bearers for UMTS
services.
WRFD-020806 Differentiated Service Based on SPI Weight applies to HSPA channels. It
provides differentiated service for users based on service type and user priority.
WRFD-150255 Differentiated Service Based on Terminal applies to HSPA channels. It provides
differentiated service for users based on terminal type.
Uu interface resources, channel element (CE) resources, and Iub interface resources are allocated
to HSPA users according to resource scheduling algorithms. If these resources are insufficient
to provide the maximum bit rate (MBR) for all online HSPA users, the RAN will allocate these
resources based on service type and user priority. High service quality is preferentially
guaranteed for high-priority services and users. Higher-priority services such as conversational
services enjoy better service than lower-priority services such as best effort (BE) services.
Higher-priority users such as gold users enjoy better service than lower-priority users such as
copper users. Users using higher-priority terminals enjoy better service than users using lowerpriority terminals.
WRFD-020806 Differentiated Service Based on SPI Weight needs to be supported by the CN,
RAN, and UE, as described in Table 2-1.
Table 2-1 Dependencies on NEs
Issue 01 (2014-04-30)
Network
Element
Description
CN
The CN sends QoS parameters to the RNC.
RNC
Based on QoS mapping, the RNC converts the received QoS parameters into
those that can be used within the RAN.

WCDMA RAN
2 Overview
Network
Element
Description
NodeB
During Uu interface scheduling and Iub interface flow control, the NodeB
allocates resources to services and users based on the QoS parameters received
from the RNC. The NodeB provides:
l Differentiated service based on service type: The NodeB preferentially
provides service for higher-priority services.
l Differentiated service based on user priority: The NodeB preferentially
provides service for higher-priority users.
UE
Issue 01 (2014-04-30)
UEs report their E-DCH and HS-DSCH categories to the RNC for calculating
the scheduling priority indicator (SPI) weight.

WCDMA RAN
3 Differentiated HSPA Service Based on Service Type
Differentiated HSPA Service Based on

Service Type
PS services are generally carried on HSPA channels. CS AMR services can also be carried on
HSPA channels according to 3GPP Release 8.
Services carried on HSPA channels are classified into delay-sensitive services and throughputsensitive services. Table 3-1 lists typical service types.
Table 3-1 Typical service types
Service Type
Service
QoS Requirement
Delay-sensitive services
l Signaling
l Low traffic volume
l VoIP
l Short delay
l CS AMR
Throughput-sensitive
services
l Streaming
l High traffic volume
l Interactive
l High throughput
l Background
l IMS signaling
Different QoS strategies are used for different types of services:

l
For delay-sensitive services, the Uu interface scheduling function limits the packet
transmission delay to an acceptable 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 preferentially met 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 throughputsensitive services, flow control must be performed. If congestion occurs on the Iub
interface, bandwidth allocated to these services is decreased.
3GPP TS 23.107 defines only four service types (conversational, interactive, streaming, and
background), which cannot fully reflect the QoS requirements of services on a live network.
Issue 01 (2014-04-30)

WCDMA RAN
3 Differentiated HSPA Service Based on Service Type
Services on a live network are complex and have different QoS requirements. For example, a
web page may contain video streams in addition to text and images. Text and image browsing
belongs to interactive services while video playing belongs to streaming services. The RNC
identifies and classifies complex service types and provides appropriate QoS to improve user
experience.
Issue 01 (2014-04-30)

WCDMA RAN
4 Differentiated HSPA Service Based on User Priority
Differentiated HSPA Service Based on User

Priority
Differentiated HSPA service based on user priority applies to BE (throughput-sensitive)
services, which belong to 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 SPI weights for different user priorities. Based on these parameter settings,
the NodeB provides differentiated service during Uu interface scheduling and Iub interface flow
control to ensure better service quality for higher-priority users in the case of resource
insufficiency.
Differentiated HSPA service based on user priority is implemented in the following ways:
l
The operator configures different GBRs for users of different priorities on the RNC side.
The Uu interface scheduling function is used to guarantee GBRs for BE services.
HBR is the expected throughput of users. The operator configures different HBRs for users
of different priorities on the RNC side. When the data rate of a user reaches its HBR, the
HSPA scheduling function reduces the scheduling priority of this user.
SPI weight is the weight of the SPI configured based on user priority and service type. It
ranges from 1% to 100%. When radio resources are insufficient, HSPA scheduling and
flow control enable the NodeB to allocate resources based on user SPI weight; that is, the
resource allocation ratio is equal to the SPI weight ratio for users. For gold, silver, and
copper users, the ratio of their throughput approximately equals the ratio of their SPI weight
when the following conditions are both met:
Gold, silver, and copper users are in the same radio environment. They have the same
UE capabilities and sufficient traffic volume.
The Uu interface resources are insufficient.
Differentiated Service Based on SPI Weight (WRFD-020806 Differentiated Service Based on

SPI Weight) is implemented as follows:
When the Uu interface resources are insufficient, Iub flow control and Uu interface scheduling
enable the NodeB to allocate bandwidth based on their SPI weight. If the allocated bandwidth
does not meet GBR requirements of all BE services, the NodeB preferentially ensures the GBRs
of all BE services regardless of their SPI weight. Then, the NodeB allocates the remaining
bandwidth based on SPI weight.
Issue 01 (2014-04-30)

WCDMA RAN
4 Differentiated HSPA Service Based on User Priority
In this way, users of higher SPI weight enjoy better service. In addition, resource allocation
differentiation among users is quantified by the ratio of SPI weight among users.
Flow control over the Iub interface includes the NodeB HSDPA adaptive flow control algorithm
and the NodeB uplink bandwidth adaptive adjustment algorithm. For details, see Transmission
Resource Management Feature Parameter Description. For details about Uu scheduling, see
HSDPA Feature Parameter Description and HSUPA Feature Parameter Description.
The following is an example of differentiated service based on SPI weight:
l
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 insufficient to
meet the data transmission requirements of all the ten users.
The GBRs of cold, 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
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 service quality based on service types. For example, low-charge-rate BE service
users are provided with low service-quality if network resources are insufficient.
For SPI weight settings, see the next chapter.
Issue 01 (2014-04-30)

WCDMA RAN
5 Differentiated HSPA Service Based on Terminal
Differentiated HSPA Service Based on

Terminal
To support this feature, users can set the TAC(BSC6900,BSC6910) and DeviceGroupID
(BSC6900,BSC6910) parameters in the ADD UQOSTAC command to allocate the
IMEI_TACs of terminals to different terminal groups and set the DeviceGroupID
(BSC6900,BSC6910), DLSpiweight(BSC6900,BSC6910), and ULSpiweight
(BSC6900,BSC6910) parameters in the ADD UUSERGRPDEVICEMAP command to specify
the SPI weight for each terminal group.
The SPI weight affects the chances that each UE or service is scheduled by the HSPA resource
scheduling algorithms, and therefore affects the service quality enjoyed by each UE. Services
with larger SPI weights take precedence over services with smaller SPI weights in obtaining
satisfactory quality. For example, when the air interface resources are insufficient, services with
larger SPI weights can reach higher rates or have shorter transmission delay than services with
smaller SPI weights.
Issue 01 (2014-04-30)

10
WCDMA RAN
6 Settings for HSPA QoS Parameters
Settings for HSPA QoS Parameters
6.1 Description
The CN sends QoS parameters to the RAN over the Iu interface through a RAB ASSIGNMENT
REQUEST message. Based on QoS mapping, the RNC converts the received QoS parameters
into those that can be used within the RAN. Then, the RAN implements differentiated HSPA
service based on the QoS parameters. Figure 6-1 shows the HSPA QoS mapping. Operators
may configure the QoS mapping by setting QoS parameters on the RNC.
Issue 01 (2014-04-30)

11
WCDMA RAN
Figure 6-1 QoS mapping
QoS mapping can be configured at both the operator and RNC level:
l
If parameters for operator-level differentiated service are not configured, the settings of the
RNC-level differentiated service parameters automatically take effect.
When neither RAN sharing nor multi-operator core network (MOCN) is enabled,
parameters for operator-level differentiated service do not need to be set.
When only RAN sharing is enabled, parameters for operator-level differentiated service
can be set.
When only MOCN is enabled, parameters for operator-level differentiated service should
not be set. However, if operators use different CN strategies, for example, different settings
of allocation/retention priority (ARP) or traffic handling priority (THP), these parameters
should be set to guarantee service fairness among operators.
6.2 Settings for the GBR

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

12
WCDMA RAN
Table 6-1 Example of GBR mapping based on user priority

Service
Type
THP
Bearer
Type
User
Priority
UL GBR
DL GBR
Interactive
services
High
R99
Gold
64 kbit/s
128 kbit/s
Background
services
NULL
HSPA
Copper
16 kbit/s
64 kbit/s
Signaling
services
NULL
R99
Silver
64 kbit/s
64 kbit/s
R99
Gold
64 kbit/s
64 kbit/s
PTT services
Note: GBRs are configured based on user priority, traffic class (TC), THP, and R99/HSPA
bearers. The example only shows configuration of GBRs based on user priority.
The mapping of TrafficClass(BSC6900,BSC6910), THPClass(BSC6900,BSC6910),
BearType(BSC6900,BSC6910) and UserPriority(BSC6900,BSC6910) to GBR(UlGBR
(BSC6900,BSC6910)/ DlGBR(BSC6900,BSC6910)) is set by running the SET UUSERGBR
command on the RNC. The operator-oriented mapping is set by running the ADD
UOPERUSERGBR or MOD UOPERUSERGBR command.
6.3 Settings for the HBR

The HBR is controlled by the HappyBR(BSC6900,BSC6910) parameter.
When NodeB resources are limited, a user's HS-DSCH scheduling priority is reduced if the user's
HS-DSCH rate exceeds HappyBR(BSC6900,BSC6910). Moderately reducing the user's
scheduling priority in this case leaves more scheduling chances for users with throughput below
their HBRs. As a result, the total user satisfaction is improved. If this parameter is set to zero,
the NodeB does not dynamically adjust the HS-DSCH scheduling priority based on the HBR.
The mapping of TrafficClass(BSC6900,BSC6910), THPClass(BSC6900,BSC6910), and
UserPriority(BSC6900,BSC6910) to HappyBR(BSC6900,BSC6910) is set by running the SET
UUSERHappyBR command on the RNC. The operator-oriented mapping is set by running the
ADD UOPERUSERHAPPYBR command.
6.4 Settings for User Priority

The user priority is determined by ARP. The mapping of ARP to the user priority is set by running
the SET UUSERPRIORITY command. The operator-oriented mapping is set by running the
ADD UOPERUSERPRIORITY or MOD UOPERUSERPRIORITY command.
Issue 01 (2014-04-30)

13
WCDMA RAN
Table 6-2 Default mapping of ARP to UserPriority

ARP
UserP
riorit
y
Err
or
Gold
10
Silver
11
12
13
14
15
Copper
6.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 SET UTHPCLASS command. The operator-oriented mapping is set by running the ADD
UOPERTHPCLASS or MOD UOPERTHPCLASS command.
Table 6-3 Default mapping of THP to TrafficClass
THP
THPClass
High
Medium
10
11
12
13
14
15
Low
For details about THP, see "Priorities Involved in Load Control" in Load Control Feature
Parameter Description.
6.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
(BSC6900,BSC6910), UserPriority(BSC6900,BSC6910), and THPClass
(BSC6900,BSC6910) to SPI(BSC6900,BSC6910).
The ADD UOPERSCHEDULEPRIOMAP command is used to set the operator-oriented
mapping.
Table 6-4 Default mapping of THPClass, UserPriority, and TrafficClass to SPI
Issue 01 (2014-04-30)
TrafficClass
UserPriority
THPClass
SPI
Interactive
Gold
High
10
Gold
Medium
Gold
Low
Silver
High
Silver
Medium
Silver
Low

14
WCDMA RAN
TrafficClass
Background
UserPriority
THPClass
SPI
Copper
High
Copper
Medium
Copper
Low
Gold
None
Silver
None
Copper
None
6.7 Settings for the SPI Weight

6.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.
----End
6.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 the
UlCapacitySelect(BSC6900,BSC6910) and DlCapacitySelect(BSC6900,BSC6910)
parameters, E-DCH/HS-DSCH category, and MBR.
l
In the DL
If DlCapacitySelect(BSC6900,BSC6910) is set to MBR, the DL rate equals the MBR;
If DlCapacitySelect(BSC6900,BSC6910) is set to Min, the DL rate equals Min
(RateCate, MBR);
If DlCapacitySelect(BSC6900,BSC6910) is set to Max, the DL rate equals Max
(RateCate, MBR);
If DlCapacitySelect(BSC6900,BSC6910) is set to Category, the DL rate equals
RateCate.
In the UL
If UlCapacitySelect(BSC6900,BSC6910) is set to MBR, the UL rate equals the MBR;
If UlCapacitySelect(BSC6900,BSC6910) is set to Min, the UL rate equals Min
(RateCate, MBR);
Issue 01 (2014-04-30)

15
WCDMA RAN
If UlCapacitySelect(BSC6900,BSC6910) is set to Max, the UL rate equals Max

(RateCate, MBR);
If UlCapacitySelect(BSC6900,BSC6910) 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.
l
There are 10 rate ranges altogether, denoted by {<T1, T1-T2, T2-T3, ... T8-T9, >T9}. T1
to T9 are configured by setting the following parameters in the SET UCapaRateRange
command.
A rate range is the range that a DL or UL rate falls into. For example, if DlRateThreshold1
(BSC6900,BSC6910)< DL Rate < DlRateThreshold2(BSC6900,BSC6910),
(DlRateThreshold1(BSC6900,BSC6910)-DlRateThreshold2(BSC6900,BSC6910)) is
the DL rate range.
For details about the HS-DSCH category, see HSDPA Feature Parameter Description. For
details about the E-DCH category, see HSUPA Feature Parameter Description.
Table 6-5 Rate range parameters
Issue 01 (2014-04-30)
DL Parameter
Default Value
UL Parameter
Default Value
DlRateThreshold1
(BSC6900,BSC6910
)
128 kbit/s
UlRateThreshold1
(BSC6900,BSC6910
)
128 kbit/s
DlRateThreshold2
(BSC6900,BSC6910
)
384 kbit/s
UlRateThreshold2
(BSC6900,BSC6910
)
384 kbit/s
DlRateThreshold3
(BSC6900,BSC6910
)
512 kbit/s
UlRateThreshold3
(BSC6900,BSC6910
)
512 kbit/s
DlRateThreshold4
(BSC6900,BSC6910
)
1,000 kbit/s
UlRateThreshold4
(BSC6900,BSC6910
)
768 kbit/s
DlRateThreshold5
(BSC6900,BSC6910
)
2,000 kbit/s
UlRateThreshold5
(BSC6900,BSC6910
)
1,000 kbit/s
DlRateThreshold6
(BSC6900,BSC6910
)
4,000 kbit/s
UlRateThreshold6
(BSC6900,BSC6910
)
1,500 kbit/s
DlRateThreshold7
(BSC6900,BSC6910
)
8,000 kbit/s
UlRateThreshold7
(BSC6900,BSC6910
)
2,500 kbit/s

16
WCDMA RAN
DL Parameter
Default Value
UL Parameter
Default Value
DlRateThreshold8
(BSC6900,BSC6910
)
16,000 kbit/s
UlRateThreshold8
(BSC6900,BSC6910
)
5,500 kbit/s
DlRateThreshold9
(BSC6900,BSC6910
)
32,000 kbit/s
UlRateThreshold9
(BSC6900,BSC6910
)
7,500 kbit/s
Operator-oriented mapping to the rate range is set by running the ADD

UOperCapaRateRange command.
6.7.3 Mapping of the SPI and Rate Range to SPI Weight

The RNC determines SPI weight based on the following table:
Figure 6-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.
Issue 01 (2014-04-30)

17
WCDMA RAN
7 Related Features
Related Features
7.1 WRFD-020806 Differentiated Service Based on SPI

Weight
Prerequisite Features
l
WRFD-01061103 Scheduling based on EPF and GBR must be configured before

WRFD-020806 Differentiated 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 Resource

Management must be configured before WRFD-020806 Differentiated Service Based on
SPI Weight can be applied in the uplink over the Uu interface. When WRFD-020806
Differentiated Service Based on SPI Weight is used with WRFD-01061402 Enhanced Fast
UL Scheduling, only uplink Uu interface resources can be differentially scheduled.
However, when WRFD-020806 Differentiated Service Based on SPI Weight is used with
WRFD-010638 Dynamic CE Resource Management, both uplink Uu 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 Transmission must be configured before WRFD-020806 Differentiated
Service Based on SPI Weight can be applied in the downlink over the Iub interface.
WRFD-01061212 HSUPA Iub Flow Control in Case of Iub Congestion and WRFD-010612
HSUPA Introduction Package must be configured before WRFD-020806 Differentiated
Service Based on SPI Weight can be applied in the uplink over the Iub interface.
Mutually Exclusive Features

None
Impacted Features
This feature is affected by the following features:
Issue 01 (2014-04-30)

18
WCDMA RAN
7 Related Features
HSUPA Scheduling Based on UE Location, which is an enhancement to WRFD-01061209

HSUPA HARQ and Fast UL Scheduling in NodeB: HSUPA scheduling based on UE
locations reduces the SPI weight for UEs in soft handovers.
WRFD-150204 Platinum User Prioritizing: The SPI weight for platinum users is always
100.
WRFD-150255 Differentiated Service Based on Terminal: When the WRFD-150255

Differentiated Service Based on Terminal feature is enabled, each terminal group is
configured with an SPI weight, which will take effect on all the terminals in this terminal
group.
WRFD-150233 Differentiated Service Based on Resource Reservation: This feature can

provide differentiated services according to the SPI weights for different levels of UEs.
However, the WRFD-150233 Differentiated Service Based on Resource Reservation
feature limits the power used by different levels of UEs at busy hours. If both features are
used together, the differentiation implemented by this feature among UEs will be affected
by the maximum power percentages allocated by the WRFD-150233 Differentiated Service
Based on Resource Reservation feature to resource groups.
WRFD-020128 Quality Improvement for Subscribed Service/WRFD-020132 Web

Browsing Acceleration/WRFD-020133 P2P Downloading Rate Control during Busy Hour:
These features implement differentiated management among services based on the service
awareness function. According to the identified service type, the SPI weight adjustment
factor of a service is calculated. The final SPI weight of the UE equals the initial SPI weight
multiplied by the SPI weight adjustment factor. Therefore, the final SPI weight of a UE
depends on the service type as well as the initial SPI weight.
7.2 WRFD-150255 Differentiated Service Based on Terminal

Prerequisite Features
l
WRFD-01061103 Scheduling based on EPF and GBR must be configured before

WRFD-020806 Differentiated 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 Resource

Management must be configured before WRFD-020806 Differentiated Service Based on
SPI Weight can be applied in the uplink over the Uu interface. When WRFD-020806
Differentiated Service Based on SPI Weight is used with WRFD-01061402 Enhanced Fast
UL Scheduling, only uplink Uu interface resources can be differentially scheduled.
However, when WRFD-020806 Differentiated Service Based on SPI Weight is used with
WRFD-010638 Dynamic CE Resource Management, both uplink Uu 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 Transmission must be configured before WRFD-020806 Differentiated
Service Based on SPI Weight can be applied in the downlink over the Iub interface.
WRFD-01061212 HSUPA Iub Flow Control in Case of Iub Congestion and WRFD-010612
HSUPA Introduction Package must be configured before WRFD-020806 Differentiated
Service Based on SPI Weight can be applied in the uplink over the Iub interface.
Issue 01 (2014-04-30)

19
WCDMA RAN
7 Related Features
Mutually Exclusive Features

None
Impacted Features
This feature is affected by the following features:
l
HSUPA Scheduling Based on UE Location, which is an enhancement to WRFD-01061209

HSUPA HARQ and Fast UL Scheduling in NodeB: HSUPA scheduling based on UE
locations reduces the SPI weight for UEs in soft handovers.
WRFD-150204 Platinum User Prioritizing: The SPI weight for platinum users is always
100.
WRFD-150233 Differentiated Service Based on Resource Reservation: This feature can

provide differentiated services according to the SPI weights for different levels of UEs.
However, the WRFD-150233 Differentiated Service Based on Resource Reservation
feature limits the power used by different levels of UEs at busy hours. If both features are
used together, the differentiation implemented by this feature among UEs will be affected
by the maximum power percentages allocated by the WRFD-150233 Differentiated Service
Based on Resource Reservation feature to resource groups.
WRFD-020128 Quality Improvement for Subscribed Service/WRFD-020132 Web

Browsing Acceleration/WRFD-020133 P2P Downloading Rate Control during Busy Hour:
These features implement differentiated management among services based on the service
awareness function. According to the identified service type, the SPI weight adjustment
factor of a service is calculated. The final SPI weight of the UE equals the initial SPI weight
multiplied by the SPI weight adjustment factor. Therefore, the final SPI weight of a UE
depends on the service type as well as the initial SPI weight.
Issue 01 (2014-04-30)

20
WCDMA RAN
8 Network Impact
Network Impact

Weight
System Capacity
WRFD-020806 Differentiated Service Based on SPI Weight impacts the downlink system
capacity in the following ways:
l
Differentiated service is based on an SPI weight during HSDPA scheduling over the Uu
interface and flow control over the Iub interface. UEs with a larger SPI weight are allowed
to use more Uu interface power 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 approximately equal 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 UEs in strong coverage areas increases scheduling chances for the UEs,
increases cell resource usage efficiency, and increases cell throughput.
WRFD-020806 Differentiated Service Based on SPI Weight impacts the uplink system capacity
in the following ways:
l
Differentiated service is based on an SPI weight during HSUPA scheduling over the Uu
interface, flow control 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-related configurations (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 the same SPI weight.
Issue 01 (2014-04-30)

21
WCDMA RAN
8 Network Impact
Network Performance
No impact.

System Capacity
WRFD-150255 Differentiated Service Based on Terminal impacts the downlink system capacity
l
Differentiated service is based on an SPI weight during HSDPA scheduling over the Uu
interface and flow control over the Iub interface. UEs with a larger SPI weight are allowed
to use more Uu interface power 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 approximately equal 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 UEs in strong coverage areas increases scheduling chances for the UEs,
increases cell resource usage efficiency, and increases cell throughput.
WRFD-150255 Differentiated Service Based on Terminal impacts the uplink system capacity
l
Differentiated service is based on an SPI weight during HSUPA scheduling over the Uu
interface, flow control 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-related configurations (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 the same SPI weight.
Network Performance
No impact.
Issue 01 (2014-04-30)

22
WCDMA RAN
9 Engineering Guidelines
Engineering Guidelines

Weight
9.1.1 When to Use Differentiated Service Based on SPI Weight
Use this feature when the operator expects to achieve the following:
l
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 attract HSPA users. Some of these users perform heavy-traffic downloading, which
occupies a large amount of 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 the data 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 can deploy this feature to
reduce resources available to users whose total monthly traffic exceeds the specified 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, to increase 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 a differentiated policy for allocating resources to users with
different priorities. With this feature, postpaid service users are allocated more bandwidth
when resources are limited.
In scenarios where downlink Uu interface resources are limited and this feature is enabled, the
downlink scheduling algorithm allocates resources based on the SPI weight, reducing the weight
of channel conditions in the calculation of the scheduling priority. If high-priority UEs have
poor channel conditions, the cell throughput decreases. In contrast, if high-priority UEs have
good channel conditions, the cell throughput increases. This feature does not reduce cell
throughput when Iub interface resources, CE resources, or uplink Uu interface resources are
limited.
Issue 01 (2014-04-30)

23
WCDMA RAN
When cell load is heavy and congestion occurs on the uplink/downlink Uu interface, Iub
interface, or CE resources, it is recommended that you keep the GBR value of gold users less
than or equal to 64 kbit/s. This is to prevent high-priority users from preempting excess resources
and prevent the CS RAB setup success ratio from declining due to deployment of this feature.
The GBR value of users can be queried by running the LST UUSERGBR command.
9.1.2 Required Information

l
Charging policy and user priorities configured on the CN

When user priorities are configured on the CN based on the charging policy, this feature
provides better 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,
and transmission resources, may be insufficient. This feature reduces the cost per bit by
limiting the resources available to services that cause heavy traffic.
9.1.3 Deployment
This section describes how to activate, verify, and deactivate the optional feature WRFD-020806
Differentiated Service Based on SPI Weight.
Requirements
l
Dependencies on Hardware
This feature does not have any special requirements for hardware.
Dependencies on Other Features

The following features have been configured before this feature is enabled:
WRFD-01061103 Scheduling based on EPF and GBR has been configured before this
feature is applied in the downlink over the Uu interface.
WRFD-01061402 Enhanced Fast UL Scheduling or WRFD-010638 Dynamic CE
Resource Management has been configured before this feature is applied in the uplink
over the Uu interface. When this feature is enabled together with the optional feature
WRFD-01061402 Enhanced Fast UL Scheduling, only uplink Uu interface resources
can be differentially scheduled. When this feature is enabled together with the optional
feature RFD-010638 Dynamic CE Resource Management, both uplink Uu 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 Transmission have been configured before this
feature is applied in the downlink over the Iub interface.
WRFD-01061212 HSUPA Iub Flow Control in Case of Iub Congestion has been
configured before this feature is applied in the uplink over the Iub interface.
License
The license for Differentiated Service Based on SPI Weight has been activated on the RNC
side. For details about how to activate the license, see License Management Feature
Parameter Description.
Issue 01 (2014-04-30)

24
WCDMA RAN
Table 9-1 lists the license information for the Differentiated Service Based on SPI Weight
feature.
Table 9-1 License information for the TCP Accelerator feature
Feature ID
Feature Name
License Control Item
NE
Sales
Unit
WRFD-020806
Differentiated
Service Based
on SPI Weight

on SPI Weight (per kbps)
RNC
Mbps
Data Preparation
This section describes the key parameters and recommended settings for deploying
Differentiated Service 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
the SET 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 SET UTHPCLASS command. There are three THP classes: high, medium, and low.
MBR
The MBR of a UE in the RAN is determined by factors such as the MBR allocated by the CN,
Uu interface capability of the UE, and Uu interface bearer type.
l
If resources are sufficient on the RAN side, UEs experiencing heavy traffic can reach their
MBRs. To provide differentiated rates for gold, silver, and copper users, operators need to
configure MBRs in descending order for these types of users. If differentiated rates are not
required, operators can configure 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 SPI weights 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
policies without being limited by any rules on the RAN side. For example, gold users can be
configured with an MBR greater than or equal to the MBR of silver users. The RAN side does
not forcibly require that the MBR of gold users be greater than the MBR of silver users.
The following table lists example MBRs allocated by the CN.
Service Type
Issue 01 (2014-04-30)
HLR
25
WCDMA RAN
Subscriber Class
MBR
Postpaid service
High-end subscriber
7.2 Mbit/s
Prepaid service plan A

(monthly subscription for
12.99 USD)
Common subscriber
7.2 Mbit/s
Prepaid service plan B

12.99 USD)
Common subscriber
3.6 Mbit/s
Prepaid service plan C

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 the RAN side by running the SET UUSERGBR command. GBRs are mainly configured for
BE services.
When configuring GBRs, consider the following:
l
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
UEs processing PS BE services. This ensures better user experience for a service carried
on an HSPA channel.
To ensure throughput for specific UEs, operators can configure high GBRs for the UEs
based on network 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.
Issue 01 (2014-04-30)
Service
Type
HLR
CN
RAN
Subscriber
Class
MBR
ARP
THP
SPI
GBR
Postpaid
service
High-end
subscriber
7.2 Mbit/s
10
64 kbit/s
Prepaid
service
plan A
(monthly
subscripti
on for
12.99
USD)
Common
subscriber
7.2 Mbit/s
64 kbit/s

26
WCDMA RAN
Prepaid
service
plan B
(monthly
subscripti
on for
12.99
USD)
Common
subscriber
3.6 Mbit/s
64 kbit/s
Prepaid
service
plan C
(monthly
subscripti
on for 8.99
USD)
Low-end
subscriber
2 Mbit/s
64 kbit/s
Note that the GBR of an HSDPA UE can only be ensured in certain situations. For example, if
an HSDPA UE is at the edge of cell coverage and the channel quality is poor, a large amount of
cell resources are required to ensure the downlink GBR of the UE. This reduces the total cell
capacity, which is unfair to other UEs using services in the same cell.
To prevent this problem, operators need to configure the maximum percentage of power
resources available 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 required to 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.
Issue 01 (2014-04-30)
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%

27
WCDMA RAN
GBR
Maximum Percentage of Available

Power Resources
896 kbit/s
55%
1024 kbit/s
60%
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 is 30%. 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
percentage of available power resources is not configurable.
SPI
Operators can specify the SPI for resource allocation to different traffic classes. The SPI is
determined by the THP class (configured for interactive services), traffic class, and user priority.
The mapping of the traffic 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-time services (conversational and streaming services) have an SPI in the range of 12-15.
They are all high-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 the range of 2-11. The SPI varies according to the settings for the user
priority and THP class. This variation differentiates 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 well as 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,
ensure the following so that Differentiated Service Based on SPI Weight can produce the desired
effect:
l
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

(BSC6900,BSC6910).
Issue 01 (2014-04-30)

28
WCDMA RAN
Activation
Step 1 Run the RNC MML command SET UUSERPRIORITY (CME single configuration: UMTS
Radio Global Configuration Express > User Integrated Priority Parameters Configuration > RNC
Oriented User Priority Related Parameters; CME batch modification center: Modifying RNC
Parameters in Batches) to configure gold, silver, and copper users. In this step, set User_priority
of Allocation/Retention priority 1 through User_priority of Allocation/Retention priority
5 according to the network plan.
Step 2 Run the RNC MML command SET UTHPCLASS (CME single configuration: UMTS Radio
Global Configuration Express > Channel Management Configuration > THP Class for
Interactive Users; CME batch modification center: Modifying RNC Parameters in Batches) to
set priorities of PS interactive services to appropriate values. In this step, set User Class of
Traffic Handling Priority 1 through User Class of Traffic Handling Priority 15 to appropriate
values.
Step 3 Run the MML command SET UUSERHAPPYBR (CME single configuration: (CME single
configuration: UMTS Radio Global Configuration Express > User Integrated Priority
Parameters Configuration > RNC Oriented User Priority Related Parameters; CME batch
modification center: Modifying RNC Parameters in Batches) to set Traffic class, User
Priority, Traffic Handling Priority Class, and Happy bit rate according to the network plan.
Step 4 Run the RNC MML command SET USCHEDULEPRIOMAP (CME single configuration:
UMTS Radio Global Configuration Express > Channel Management Configuration > Schedule
Priority Map Information; CME batch modification center: not supported) to set the scheduling
priority mapping information. In this step, set Traffic Class, User Priority, Traffic Handling
Priority Class, Scheduling Priority Indicator to appropriate values.
Step 5 Run the RNC MML command SET UCAPARATERANGE (CME single configuration:
UMTS Radio Global Configuration Express > Channel Management Configuration > Rate
Thresholds for Differentiated HSPA Services Based on SPI Weight; CME batch modification
center: not supported) to set RNC-specific reference rates and rate thresholds of all levels in the
uplink and downlink. In this step, set Downlink Rate Selection, Downlink Rate Threshold
1 through Downlink Rate Threshold 9, Uplink Rate Selection, and Uplink Rate Threshold
1 through Uplink Rate Threshold 9 to appropriate values.
Step 6 Optional: Run the RNC MML command ADD UOPERCAPARATERANGE (CME single
configuration: UMTS Radio Global Configuration Express > Channel Management
Configuration > Operator-Level Rate Thresholds for SPI Weight of HSPA Services; CME batch
modification center: not supported) to set operator-specific reference rates and rate thresholds
of all levels in the uplink and downlink. In this step, set CN Operator Index, Downlink Rate
Selection, Downlink Rate Threshold 1 and Downlink Rate Threshold 2, Uplink Rate
Selection, Uplink Rate Threshold 1 through Uplink Rate Threshold 9 to appropriate values.
Step 7 Run the RNC MML command SET USPIWEIGHT (CME single configuration: UMTS Radio
Global Configuration Express > Channel Management Configuration > Factor of Schedule
Priority; CME batch modification center: Modifying RNC Parameters in Batches) to set RNCspecific scheduling priority weight. In this step, set Scheduling Priority Indicator, SPI
Weight, Configure SPI Weight Based on HSPA Rate Range, SPI Weight for HSDPA Rata
Range 1 through SPI Weight for HSDPA Rata Range 10, and SPI Weight for HSUPA Rata
Range 1 through SPI Weight for HSUPA Rata Range 10 to appropriate values.
Step 8 Optional: Run the RNC MML command ADD UOPERSPIWEIGHT (CME single
configuration: UMTS Radio Global Configuration Express > Channel Management
Issue 01 (2014-04-30)

29
WCDMA RAN
Configuration > Operator-Oriented Factor of Schedule Priority; CME batch modification center:
not supported) to set operator-specific scheduling priority weight. In this step, set CN Operator
Index, Scheduling Priority Indicator, SPI Weight, Configure SPI Weight Based on HSPA
Rate Range, SPI Weight for HSDPA Rata Range 1 through SPI Weight for HSDPA Rata
Range 10, and SPI Weight for HSUPA Rata Range 1 through SPI Weight for HSUPA Rata
Range 10 to appropriate values.
Step 9 Run the RNC MML command SET URRCTRLSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Process Switch Configuration > Process Switch; CME
batch modification center: Modifying RNC Parameters in Batches). In this step, set Process
switch to NODEB_PRIVATE_INTERFACE_SWITCH.
Step 10 Optional: When RAN Sharing or MOCN is enabled, run the RNC MML command SET
LICENSE to set the Differentiated Service Based on SPI Weight-kbps parameter for the primary
and secondary operators.
----End
MML Command Examples

//Configuring gold, silver, and copper users
SET UUSERPRIORITY: ARP1Priority=Gold, ARP2Priority=Gold, ARP3Priority=Gold,
ARP4Priority=Gold, ARP5Priority=Gold, ARP6Priority=Silver, ARP7Priority=Silver,
ARP8Priority=Silver, ARP9Priority=Silver, ARP10Priority=Silver,
ARP11Priority=Copper, ARP12Priority=Copper, ARP13Priority=Copper,
ARP14Priority=Copper, ARP15Priority=Copper, PriorityReference=ARP,
CarrierTypePriorInd=NONE;
//Setting the priorities of PS interactive services
SET UTHPCLASS: THP1Class=High, THP2Class=High, THP3Class=High, THP4Class=High,
THP5Class=High, THP6Class=Medium, THP7Class=Medium, THP8Class=Medium,
THP9Class=Medium, THP10Class=Medium, THP11Class=Low, THP12Class=Low,
THP13Class=Low, THP14Class=Low, THP15Class=Low;
//Setting the scheduling priority mapping information
SET USCHEDULEPRIOMAP: TrafficClass=INTERACTIVE, UserPriority=GOLD, THPClass=High,
SPI=7;
//Setting the RNC-specific reference rates and rate thresholds of all levels in the
uplink and downlink
SET UCAPARATERANGE: DlCapacitySelect=MBR, DlRateThreshold1=128,
DlRateThreshold2=256, DlRateThreshold3=512, DlRateThreshold4=1000,
DlRateThreshold8=20000, DlRateThreshold9=45000, UlCapacitySelect=MBR,
UlRateThreshold1=128, UlRateThreshold2=256, UlRateThreshold3=512,
UlRateThreshold7=10000, UlRateThreshold8=20000, UlRateThreshold9=45000;
//Setting the operator-specific reference rates and rate thresholds of all levels
in the uplink and downlink
ADD UOPERCAPARATERANGE: CnOpIndex=0, DlRateThreshold1=128, DlRateThreshold2=384,
DlRateThreshold9=32000, UlRateThreshold1=128, UlRateThreshold2=384,
UlRateThreshold9=7500;
//Setting the RNC-specific scheduling priority weight
SET USPIWEIGHT: SPI=7, SpiWeight=100, RateRangeSPIWeightInd=TRUE,
DlRateRange1SPIWeight=10, DlRateRange2SPIWeight=20, DlRateRange3SPIWeight=30,
DlRateRange10SPIWeight=100, UlRateRange1SPIWeight=10, UlRateRange2SPIWeight=20,
UlRateRange3SPIWeight=30, UlRateRange4SPIWeight=40, UlRateRange5SPIWeight=50,
UlRateRange9SPIWeight=90, UlRateRange10SPIWeight=100;
SET USPIWEIGHT: SPI=8, SpiWeight=10, RateRangeSPIWeightInd=TRUE,
Issue 01 (2014-04-30)

30
WCDMA RAN

DlRateRange10SPIWeight=100, UlRateRange1SPIWeight=10, UlRateRange2SPIWeight=20,
UlRateRange9SPIWeight=90, UlRateRange10SPIWeight=100;
//Setting the operator-specific scheduling priority weight
ADD UOPERSPIWEIGHT: CnOpIndex=0, SPI=7, RateRangeSPIWeightInd=TRUE;
ADD UOPERSPIWEIGHT: CnOpIndex=0, SPI=8, RateRangeSPIWeightInd=TRUE;
//Enabling the switch for a NodeB private interface
SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1;
Activation Observation
Step 1 Establish services on UE A and UE B. Assume that the SPI and SPI weight of UE A are 7 and
50, respectively, and the SPI and SPI weight of UE B are 7 and 100, respectively. In the traced
Iub interface messages, check the information element (IE) schedulingPriorityIndicator in the
NBAP_RL_RECFG_PREP message to obtain the SPI value; check the IE schedule-PriorIndication-Weight-Private to obtain the SPI weight, which is the actual SPI value for the
NodeB, as shown in Figure 9-1, Figure 9-2, Figure 9-3, and Figure 9-4.
Figure 9-1 SPI and SPI weight of UE A in the uplink
Issue 01 (2014-04-30)

31
WCDMA RAN
Figure 9-2 SPI and SPI weight of UE A in the downlink
Figure 9-3 SPI and SPI weight of UE B in the uplink
Issue 01 (2014-04-30)

32
WCDMA RAN
Figure 9-4 SPI and SPI weight of UE B in the downlink
Step 2 Check the real-time throughput of UEs by referring to Monitoring UL Throughput and
Bandwidth and Monitoring DL Throughput and Bandwidth.
Generally, if the throughput of the UE with higher SPI weight is higher than that of the UE with
lower SPI weight, this feature has taken effect. The throughput of UE B is approximately twice
the throughput of UE A, as shown in the NBAP_RL_RECFG_PREP message. If the throughput
of the UE with higher SPI weight is lower than that of the UE with lower SPI weight, this feature
has not taken effect.
----End
Deactivation
This function is not controlled by any switch but can be deactivated by setting the SPI weight
of all UEs to the same value using the RNC MML SET USPIWEIGHT command.
MML Command Example

//Setting the SPI weight of all UEs to the same value
SET USPIWEIGHT: SPI=7 , SpiWeight=10, RateRangeSPIWeightInd=FALSE;
SET USPIWEIGHT: SPI=8 , SpiWeight=10, RateRangeSPIWeightInd=FALSE;
9.1.4 Performance Monitoring

Monitor the effect of this feature by comparing values of the following cell counters measured
before and after the Differentiated Service Based on SPI Weight feature is enabled:
Issue 01 (2014-04-30)

33
WCDMA RAN
Table 9-2 Counters related to HSDPA services

Counter Name
Description
VS.HSDPA.MeanGold
enBeChThroughput.To
talBytes
Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow

of BE Service for Golden Subscriber for Cell
VS.HSDPA.MeanSilve
rBeChThroughput.TotalBytes

of BE Service for Silver Subscriber for Cell
VS.HSDPA.MeanCopp
erBeChThroughput.TotalBytes

of BE Service for Copper Subscriber for Cell
VS.HSDPA.MeanGoldenBeChThroughput
Mean Downlink Throughput of HSDPA MAC-d Flow of BE

Service for Golden Subscriber for Cell
VS.HSDPA.MeanSilverBeChThroughput

Service for Silver Subscriber for Cell
VS.HSDPA.MeanCopperBeChThroughput

Service for Copper Subscriber for Cell
VS.HSDPA.BeChThro
ughput.SPI2
Mean Downlink Throughput of HSDPA MAC-d flow of BE

Services with SPI Set to 2 for Cell
VS.HSDPA.BeChThro
ughput.SPI3

VS.HSDPA.BeChThro
ughput.SPI4

VS.HSDPA.BeChThro
ughput.SPI5

VS.HSDPA.BeChThro
ughput.SPI6

VS.HSDPA.BeChThro
ughput.SPI7

VS.HSDPA.BeChThro
ughput.SPI8

VS.HSDPA.BeChThro
ughput.SPI9

VS.HSDPA.BeChThro
ughput.SPI10

Auxiliary counter: VS.HSDPA.UE.Mean.Cell (Average Number of HSDPA UEs for Cell)
Issue 01 (2014-04-30)

34
WCDMA RAN
Table 9-3 Counters related to HSUPA services
Issue 01 (2014-04-30)
Counter Name
Description
VS.HSUPA.GoldenBeMeanChThroughput.
TotalBytes
Number of Total Bytes Received in Uplink of

HSUPA MAC-d Flow of BE Service for
Golden Subscriber for Cell
VS.HSUPA.SilverBeMeanChThroughput.T
otalBytes

Silver Subscriber for Cell
VS.HSUPA.CopperBeMeanChThroughput.
TotalBytes

Copper Subscriber for Cell
VS.HSUPA.GoldenBeMeanChThroughput
Mean Uplink Throughput of HSUPA MAC-d

Flow of BE Service for Golden Subscriber for
Cell
VS.HSUPA.SilverBeMeanChThroughput

Flow of BE Service for Silver Subscriber for
Cell
VS.HSUPA.CopperBeMeanChThroughput

Flow of BE Service for Copper Subscriber for
Cell
VS.HSUPA.BeChThroughput.SPI2

flow of BE Services with SPI Set to 2 for Cell









35
WCDMA RAN
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 in the same cell supporting HSPA services. Compare the statistics measured before
and after enabling the feature.
The expected result is as follows after Differentiated Service Based on SPI Weight is enabled:
l
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.
NOTE
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.
9.1.5 Parameter Optimization

If long-term observation shows that the throughput of gold, silver, and copper users does not
change as expected after this feature is enabled, 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
mapped to the SPI of the user type. Similarly, to reduce the throughput for a certain type of user
during peak hours, reduce the SPI weight mapped to the SPI. For example, assume that the ratio
of the SPI weight between gold, silver, and copper users is 9:3:1. When there is a large amount
of data to transmit and radio 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.
9.1.6 Troubleshooting
None

9.2.1 When to Use Differentiated Service Based on Terminal
Use this feature when the operator expects to provide differentiated services for different
terminals when the resources of a cell are insufficient. For example, when Uu resources are
insufficient, the operator may expect to provide high-value terminals more chances to reach high
rates or have short transmission delay.
9.2.2 Required Information

Observe the network load of the cell. If the network load of a cell is heavy, leading to deficiency
of resources, this feature provides differentiated services for UEs that use different terminals.
Issue 01 (2014-04-30)

36
WCDMA RAN
To determine whether to enable this feature, you are advised to collect the following information:
l
Cell-level service load

Collect the RNC-level performance counters VS.HSDPA.UE.Mean.Cell and
VS.HSDPA.MeanChThroughput. If the value of VS.HSDPA.UE.Mean.Cell is greater than
10 and the value of VS.HSDPA.MeanChThroughput is less than 1 Mbit/s, the traffic load
is high.
Cell resource occupancy

Downlink power
Obtain values of the RNC counters VS.MeanTCP.NonHS and VS.MeanTCP, and the
maximum transmit power (MaxTxPower(BSC6900,BSC6910)) of a cell based on RNC
data configurations.
VS.MeanTCP.NonHS, mean downlink transmitted carrier power (TCP) for nonHSDPA services in a cell during busy hours, is indicated as VS.MeanTCP.NonHS(W)
in the unit of W.
VS.MeanTCP, mean TCP in a cell during busy hours, is indicated as VS.MeanTCP(W)
in the unit of W.
MaxTxPower(BSC6900,BSC6910), maximum transmit power of a cell, is indicated as
configured PA capacity (W) in the unit of W. Based on the above information, nonHSDPA TCP usage and total TCP usage are calculated by using the following formulas:
Total TCP usage = VS.MeanTCP (W)/Configured PA Capacity (W) x 100%
Non-HS TCP usage = VS.MeanTCP.NonHS (W)/Configured PA Capacity (W) x 100%
where
VS.MeanTCP (W) = 10^(VS.MeanTCP/10 3)
VS.MeanTCP.NonHS (W) = 10^(VS.MeanTCP.NonHS/10 3)
Configured PA Capacity (W) = 10^(MaxTxPower/100 3)
If non-HSDPA TCP usage exceeds 70% or total TCP usage exceeds 80% during busy
hours, downlink power resources are considered to be insufficient.
Uplink power
Collect the value of the RNC-level performance counter VS.MeanRTWP.
This counter measures the average RTWP during busy hours in a cell. It is used to
determine whether the uplink power resources are insufficient. For example, when the
configured target load in an HSUPA cell is 75% and the background noise is 106 dBm,
the uplink power resources are insufficient if the value of this counter is greater than
100 dBm.
9.2.3 Deployment
Requirements
Other Features
Other features that this feature depends on have been activated. This feature depends on the
following features:
Issue 01 (2014-04-30)

37
WCDMA RAN
Differentiated services over the downlink radio interface depend on the WRFD-01061103
Scheduling based on EPF and GBR feature.
Differentiated services over the uplink radio interface depend on the WRFD-01061402
Enhanced Fast UL Scheduling or WRFD-010638 Dynamic CE Resource Management
feature. The WRFD-01061402 Enhanced Fast UL Scheduling feature only performs
differentiated scheduling for the uplink air interface interference resources, whereas the
WRFD-010638 Dynamic CE Resource Management feature performs differentiated
scheduling for both the uplink air interface interference resources and base station CE
resources.
Differentiated services over the downlink Iub interface depend on the WRFD-010610
HSDPA Introduction Package and WRFD-050405 Overbooking on ATM transmission
features or the WRFD-010610 HSDPA Introduction Package and WRFD-01061103
Scheduling based on EPF and GBR features.
Differentiated services over the uplink Iub interface depend on the WRFD-01061212
HSUPA Iub Flow Control in Case of Iub Congestion feature.
Hardware
None
License
Feature ID
Feature Name
License
Control Item
NE
Sales Unit
WRFD-150255
Differentiated
Service Based
on Terminal
Differentiated
Service Based
on Terminal
(per kbps)
BSC6900
BSC6910
per Mbps
Data Preparation
Issue 01 (2014-04-30)
Parameter Name
Parameter
ID
Setting Notes
Data Source
Process Control
Switch 5
PROCESS
SWITCH
(BSC6900,
BSC6910)
Select the
DIFF_SERVICE_ON_TER
MINAL_SWITCH check box
under this parameter.
Default/
Recommended
value
Downlink SPI
Weight
DLSpiweig
ht
(BSC6900,
BSC6910)
The larger the value of this

parameter, the higher priority of
downlink scheduling for an
HSDPA UE, and the higher
downlink throughput of the UE
when the Uu interface resources
are insufficient.
Radio network
plan (internal)

38
WCDMA RAN
Issue 01 (2014-04-30)
Parameter Name
Parameter
ID
Setting Notes
Data Source
Uplink SPI Weight
ULSpiweig
ht
(BSC6900,
BSC6910)
The larger the value of this

parameter, the higher priority of
uplink scheduling for an
HSUPA UE, and the higher
uplink throughput of the UE
when the Uu interface resources
are insufficient.
Radio network
plan (internal)
Terminal Group ID
DeviceGrou
pID
(BSC6900,
BSC6910)
None
Radio network
plan (internal)
TAC
TAC
(BSC6900,
BSC6910)
None
Radio network
plan (internal)
User Group
Classification Switch
UserPolicy
Switch
(BSC6900,
BSC6910)
Set this parameter to ON when

the Differentiated Service Based
on Terminal feature is enabled.
Default/
Recommended
value
User Group
Matching Priority
UserMatch
Priority
(BSC6900,
BSC6910)
Set this parameter to

Devicegroup when the
Differentiated Service Based on
Terminal feature is enabled.
Default/
Recommended
value
MonDevGrp0ID
MonDevGr
p0ID
(BSC6900,
BSC6910)
None
Engineering
design
MonDevGrp1ID
MonDevGr
p1ID
(BSC6900,
BSC6910)
None
Engineering
design
MonDevGrp2ID
MonDevGr
p2ID
(BSC6900,
BSC6910)
None
Engineering
design
MonDevGrp3ID
MonDevGr
p3ID
(BSC6900,
BSC6910)
None
Engineering
design
MonDevGrp4ID
MonDevGr
p4ID
(BSC6900,
BSC6910)
None
Engineering
design

39
WCDMA RAN
Parameter Name
Parameter
ID
Setting Notes
Data Source
MonDevGrp5ID
MonDevGr
p5ID
(BSC6900,
BSC6910)
None
Engineering
design
MonDevGrp6ID
MonDevGr
p6ID
(BSC6900,
BSC6910)
None
Engineering
design
MonDevGrp7ID
MonDevGr
p7ID
(BSC6900,
BSC6910)
None
Engineering
design
Activation
Using MML Commands
Step 1 Run the RNC MML command SET URRCTRLSWITCH to select the
RNC_PS_QUERY_UE_IMEI_SWITCH under the Process Control Switch 2 parameter.
Step 2 Run the RNC MML command SET UQOSALGOPARA and set User Group Classification
Switch to ON and User Group Matching Priority to Devicegroup.
Step 3 Assign TACs to different terminal groups by setting TAC and DeviceGroupID using the RNC
MML command ADD UQOSTAC during initial configuration or MOD UQOSTAC during
reconfiguration.
Step 4 Set SPI weight for different terminal groups.
Run the RNC MML command LST UUSERGRPDEVICEMAP to check whether each
terminal group is mapped to a corresponding user group.
l If a terminal group is mapped to a user group, run the RNC MML command MOD
UUSERGRPDEVICEMAP with Terminal Group ID, Uplink SPI Weight, and
Downlink SPI Weight set to appropriate values to modify the SPI weight of the terminal
group.
l If a terminal group is not mapped to a user group, run the RNC MML command ADD
UUSERGRPDEVICEMAP with Terminal Group ID, Uplink SPI Weight, and
Downlink SPI Weight set to appropriate values to modify the SPI weight of each terminal
group.
Step 5 Specify the terminal groups to be monitored.
Run the RNC MML command SET UMONDEVGRPID and specify terminal groups to be
monitored by setting the parameters MonDevGrp0ID through MonDevGrp7ID. Terminal
groups 0 to 7 are monitored by default.
Issue 01 (2014-04-30)

40
WCDMA RAN
Step 6 Turn on the switch for this feature.

Select the DIFF_SERVICE_ON_TERMINAL_SWITCH check box under the
PROCESSSWITCH5 parameter in the RNC MML command SET URRCTRLSWITCH.
Step 7 Run the RNC MML command SET URRCTRLSWITCH. In this step, select
NODEB_PRIVATE_INTERFACE_SWITCH under the Process switch parameter.
----End
MML Command Example

//Turning on the PS IMEI Request Switch
SET URRCTRLSWITCH: PROCESSSWITCH2=RNC_PS_QUERY_UE_IMEI_SWITCH-1;
//Turning on the switch for Differentiated Service Based on Terminal and specifying
the type of user matching priority
SET UQOSALGOPARA: UserPolicySwitch=ON, UserMatchPriority=Devicegroup;
//Assigning TACs to different terminal groups
ADD UQOSTAC: TAC=12345678, DeviceGroupID=1;
//Setting SPI weight for different terminal groups
ADD UUSERGRPDEVICEMAP: DeviceGroupID=1, UserGroupID=1, DLSpiweight=100,
ULSpiweight=100;
//Specifying the terminal groups to be monitored
SET UMONDEVGRPID: MonDevGrp0ID =0, MonDevGrp1ID =1, MonDevGrp2ID =2, MonDevGrp3ID
=3, MonDevGrp4ID =4, MonDevGrp5ID =5, MonDevGrp6ID =6, MonDevGrp7ID =7;
//Turning on the switch for Differentiated Service Based on Terminal
SET URRCTRLSWITCH: PROCESSSWITCH5= DIFF_SERVICE_ON_TERMINAL_SWITCH-1;
//Enabling the NodeB private interface
SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1;
Using the CME

NOTE
When configuring the Differentiated Service Based on Terminal feature on the CME, perform a single
configuration first, and then perform a batch modification if required. Configure the parameters of a single
object before a batch modification. Perform a batch modification before logging out of the parameter setting
interface.
1.
Configure a single object (such as a cell) on the CME.

Set parameters on the CME according to the operation sequence in .Table 9-4. For
instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.
2.
(Optional) Modify objects in batches on the CME. (CME batch modification center)
on the CME to start the batch modification wizard. For

To modify objects in batches, click
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
Issue 01 (2014-04-30)

41
WCDMA RAN
Table 9-4 Configuring parameters on the CME

SN
MO
NE
Parameter Name
Parameter ID
Configurabl
e in CME
Batch
Modificatio
n Center
UQOSALGOP
ARA
RNC
User Group
Classification
Switch
UserPolicySwit
ch
(BSC6900,
BSC6910)
No
User Group
Matching Priority
UserMatchPrio
rity
(BSC6900,
BSC6910)
TAC
TAC
(BSC6900,
BSC6910)
Terminal Group ID
DeviceGroupI
D
(BSC6900,
BSC6910)
Terminal Group ID
DeviceGroupI
D
(BSC6900,
BSC6910)
Downlink SPI
Weight
DLSpiweight
(BSC6900,
BSC6910)
Uplink SPI Weight
ULSpiweight
(BSC6900,
BSC6910)
MonDevGrp0ID
MonDevGrp0I
D
(BSC6900,
BSC6910)
MonDevGrp1ID
MonDevGrp1I
D
(BSC6900,
BSC6910)
MonDevGrp2ID
MonDevGrp2I
D
(BSC6900,
BSC6910)
Issue 01 (2014-04-30)
UQOSTAC
UUSERGRPD
EVICEMAP
UMONDEVG
RPID
RNC
RNC
RNC

No
No
42
WCDMA RAN
SN
MO
NE
URRCTRLS
WITCH
RNC
Parameter Name
Parameter ID
MonDevGrp3ID
MonDevGrp3I
D
(BSC6900,
BSC6910)
MonDevGrp4ID
MonDevGrp4I
D
(BSC6900,
BSC6910)
MonDevGrp5ID
MonDevGrp5I
D
(BSC6900,
BSC6910)
MonDevGrp6ID
MonDevGrp6I
D
(BSC6900,
BSC6910)
MonDevGrp7ID
MonDevGrp7I
D
(BSC6900,
BSC6910)
Process Control
Switch 5
PROCESSSWI
TCH5
(BSC6900,
BSC6910)
Process Control
Switch
PROCESSSWI
TCH
(BSC6900,
BSC6910)
Configurabl
e in CME
Batch
Modificatio
n Center
Yes
Activation Observation
Step 1 Establish services on UE A and UE B. Assume that the terminal group ID and SPI weight of UE
A are 0 and 50, respectively, and the terminal group ID and SPI weight of UE B are 1 and 100,
respectively.
Step 2 In the traced Iub interface messages, check the schedule-Prior-Indication-Weight-Private IE in
the NBAP_RL_RECFG_PREP message to obtain the SPI weight value, which is the actual SPI
weight value for the NodeB, as shown in Figure 9-5 through Figure 9-8.
Issue 01 (2014-04-30)

43
WCDMA RAN
Figure 9-5 SPI weight of UE A in the uplink
Figure 9-6 SPI weight of UE A in the downlink
Issue 01 (2014-04-30)

44
WCDMA RAN
Figure 9-7 SPI weight of UE B in the uplink
Figure 9-8 SPI weight of UE B in the downlink
Step 3 Check the real-time throughput of UEs by using functions of referring to Monitoring UL
Throughput and Bandwidth and Monitoring DL Throughput and Bandwidth.
Generally, if the throughput of the UE with higher SPI weight is higher than that of the UE with
lower SPI weight, this feature has taken effect. The throughput of UE B is approximately twice
Issue 01 (2014-04-30)

45
WCDMA RAN
the throughput of UE A, as shown in the NBAP_RL_RECFG_PREP message. If the throughput

of the UE with higher SPI weight is lower than that of the UE with lower SPI weight, this feature
has not taken effect.
----End
Deactivation
Using MML Commands
Step 1 Clear the DIFF_SERVICE_ON_TERMINAL_SWITCH check box under the
PROCESSSWITCH5 parameter in the RNC MML command SET URRCTRLSWITCH.
Step 2 Run the RNC MML command SET UQOSALGOPARA with UserPolicySwitch set to ON and
UserMatchPriority set to SPI(Schedule Priority Indication).
----End
MML Command Example

//Deactivation
SET URRCTRLSWITCH: PROCESSSWITCH5= DIFF_SERVICE_ON_TERMINAL_SWITCH-0;
SET UQOSALGOPARA: UserPolicySwitch=ON, UserMatchPriority=SPI;
Using the CME

NOTE
When configuring the Differentiated Service Based on Terminal feature on the CME, perform a single
configuration first, and then perform a batch modification if required. Configure the parameters of a single
object before a batch modification. Perform a batch modification before logging out of the parameter setting
interface.
1.
Configure a single object (such as a cell) on the CME.

Set parameters on the CME according to the operation sequence in Table 9-5. For
instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.
2.
(Optional) Modify objects in batches on the CME. (CME batch modification center)
on the CME to start the batch modification wizard. For

To modify objects in batches, click
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
Issue 01 (2014-04-30)

46
WCDMA RAN
Table 9-5 Configuring parameters on the CME

SN
MO
NE
Parameter Name
Parameter ID
Configurabl
e in CME
Batch
Modificatio
n Center
URRCTRLS
WITCH
RNC
Process Control
Switch 5
PROCESSSWI
TCH
(BSC6900,
BSC6910)
Yes
UQOSALGOP
ARA
RNC
User Group
Classification
Switch
UserPolicySwit
ch
(BSC6900,
BSC6910)
NO
User Group
Matching Priority
UserMatchPrio
rity
(BSC6900,
BSC6910)
9.2.4 Performance Monitoring

Monitor the effect of this feature by comparing values of the following cell counters measured
before and after the Differentiated Service Based on Terminal feature is enabled:
Table 9-6 Counters for HSDPA services
Issue 01 (2014-04-30)
Counter Name
Description
VS.HSDPA.BeChThroughput.DevGrp0
Average DL Throughput of HSDPA MAC-d

Flows Carrying BE Services of DevGrp0 UEs
for Cell

for Cell

for Cell

for Cell

for Cell

47
WCDMA RAN
Counter Name
Description

for Cell

for Cell

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

Table 9-7 Counters for HSUPA services
Issue 01 (2014-04-30)
Counter
Description
VS.HSUPA.BeChThroughput.DevGrp0
Average UL Throughput of HSUPA MAC-d

for Cell

for Cell

for Cell

for Cell

for Cell

for Cell

for Cell

for Cell

48
WCDMA RAN
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 UEs in different terminal
groups. Ensure that the statistics are measured hourly during peak and off-peak hours. Ensure
that the UEs are in the same cell supporting HSPA services. Compare the statistics measured
before and after enabling the feature.
After Differentiated Service Based on Terminal is enabled, the expected result is as follows:
l
During peak hours, the throughput of UEs in terminal groups with high SPI weight increases
but that of UEs in terminal groups with low SPI weight decreases.
During off-peak hours, UEs in terminal groups with low SPI weight obtain more bandwidth
than they would during peak hours because there are a smaller number of UEs and more
resources.
NOTE
The throughput ratio between UEs in different terminal groups may not perfectly match their SPI weight
ratio because of differences in user behavior, user distribution, data volume, and channel quality.
9.2.5 Parameter Optimization

If long-term observation shows that the throughput of UEs in different terminal groups does not
change as expected after this feature is enabled, adjust the mapping of terminal groups to SPI
weight to change the rates allocated to UEs in different terminal groups.
To increase the throughput for UEs in a certain terminal group during peak hours, increase the
SPI weight mapped to the terminal group. Similarly, to reduce the throughput for UEs in a certain
terminal group during peak hours, reduce the SPI weight mapped to the terminal group.
9.2.6 Troubleshooting
None
Issue 01 (2014-04-30)

49
WCDMA RAN
10 Parameters
10
Parameters
Table 10-1 Parameter description

Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
PROCE
SSSWIT
CH5
BSC690
0
SET
URRCT
RLSWI
TCH
WRFD150252
Video
Pacing
WRFD150253
VoIP
Applicat
ion
Manage
ment
Meaning: 1)
INTERRAT_LOAD_SINGLE_RPT_FOR_LTE_SWI
TCH(RIM-based and Request-based Load Information
Sharing Switch) Whether a UMTS cell sends its load
information to an LTE cell through the RIM procedure
after receiving a load information sharing request from
the LTE cell. 1: This switch is turned on. UMTS cells
support the RIM-based load information sharing
function. A UMTS cell sends its load information to an
LTE cell after receiving a load information sharing
request from the LTE cell. 0: This switch is turned off.
UMTS cells do not support the RIM-based load
information sharing function. A UMTS cell does not
respond to the load information sharing request from an
LTE cell. 2)
INTERRAT_LOAD_REPORT_FROM_LTE_SWITC
H(Learning LTE Load Through RIM Switch) Whether
the RNC obtains the load information about LTE cells
through the RAN information management (RIM)
procedure. For details about the RIM procedure, see
3GPP TS 48. 018. 1: This switch is turned on. The RNC
obtains the load information about LTE cells through
the RIM procedure. 0: This switch is turned off. The
RNC cannot obtain the load information about LTE
cells through the RIM procedure. 3)
UL_EVQI_SWITCH(UL EVQI Evaluation Switch)
Whether to enable the EVQI function in the uplink. 1:
This switch is turned on. EVQI is enabled in the uplink.
0: This switch is turned off. EVQI is disabled in the
uplink. 4)DL_EVQI_SWITCH(DL EVQI Evaluation
MRFD090211
Issue 01 (2014-04-30)

50
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
Switch) Whether to enable the EVQI function in the

downlink. 1: This switch is turned on. EVQI is enabled
in the downlink. 0: This switch is turned off. EVQI is
disabled in the downlink. 5)
VIDEO_RATE_ADAPTION_SWITCH (Video
Service Rate Adaption Switch) Whether the Video
Service Rate Adaption feature is enabled. 1: This switch
is turned on. The Video Service Rate Adaption feature
is enabled for PS UEs processing video services. That
is, the rate of video service is ensured or is limited for
these PS UEs. 0: This switch is turned off. The Video
Service Rate Adaption feature is disabled for PS UEs.
6) VOIP_MANAGE_SWITCH (VoIP Application
Management Switch) Whether the VoIP application
management function is enabled. 1: This switch is
turned on. VoIP application management actions are
performed on PS UEs that are processing VoIP services.
VoIP application management actions can either be
VoIP application rate ensurance or VoIP application
speed limit. 0: This switch is turned off. the VoIP
application management function is disabled for PS
UEs. 7) DIFF_SERVICE_ON_TERMINAL_SWITCH
(Differentiated Service Based on Terminal Switch)
Whether the Differentiated Service Based on Terminal
feature is enabled. 1: This switch is turned on. PS UEs
processing BE services are grouped into different
terminal groups based on their type approval codes
(TACs) in IMEIs, and each terminal group is assigned
an SPI weight for BE services, thereby achieving
differentiated services. 0: This switch is turned off. The
Differentiated Service Based on Terminal feature is
disabled for PS UEs processing BE services. 8)
APP_GRP_RES_RSV_SWITCH (Differentiated
Service Based on Application Resource Reservation
Switch) Whether the Differentiated Service Based on
Application Resource Reservation feature is enabled. 1:
This switch is turned on. The RNC identifies service
types, maps different service types to different resource
groups, and configure different resource reservation
policies for these resource groups. In this way, resource
reservation is performed based on service types. 0: This
switch is turned off. The RNC does not reserve
resources based on service types or service groups. 9)
RIM_ON_ECO_SWITCH(Support RIM by
eCoordinator Switch) Whether the RIM procedure is
implemented through the eCoordinator. 1: This switch
is turned on. The RIM procedure is implemented
Issue 01 (2014-04-30)

51
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
through the eCoordinator. 0: This switch is turned off.

the RIM procedure is implemented through the CN.
This parameter is an advanced parameter. Therefore,
modify the setting of this parameter under the
instruction of Huawei technical support. 10)
SRBCHG_DRD_FAST_RB_SETUP_SWITCH(RB
Fast Setup Switch for RB Setups Accompanied by
DRDs with Changing SRBs) Whether to use the RB fast
setup function for RB setups accompanied by DRDs
with changing SRBs. 1: This switch is turned on. The
RB fast setup function is used for RB setups
accompanied by DRDs with changing SRBs. 0: This
switch is turned off. The simultaneous setup procedure
is used for RB setups accompanied by DRDs with
changing SRBs. 11)
SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH
(RB Fast Setup Switch for RB Setups Accompanied by
DRDs with Unchanged SRBs) Whether to use the RB
fast setup function for RB setups accompanied by DRDs
with unchanged SRBs. 1: This switch is turned on. The
accompanied by DRDs with unchanged SRBs. 0: This
unchanged SRBs. 12)
FACH_RB_RECFG_FAIL_SPEC_CAUSE_SWITC
H Whether the RNC releases a UE's RRC connection
after an RB reconfiguration failure with the cause of
"incompatibleSimultaneousReconfiguration" or
"invalid configuration." This switch is set to off by
default. 1: This switch is turned on. The RNC releases
the UE's RRC connection. 0: This switch is turned off.
The RNC does not release the UE's RRC connection and
rolls back the procedure. 13)
WBAMR_HHO_FAIL_ROLLBACK_SWITCH
Whether RNC performs rollback operations when
AMR-WB services experience hard handover failures.
1: This switch is turned on. The RNC performs rollback
operations when AMR-WB services experience hard
handover failures. Before setting this switch to ON, you
are advised to run the "SET UCONNMODETIMER"
command to set T312 to 1s. Otherwise, some UEs
experience garbled noise. 0: This switch is turned off.
The RNC does not perform rollback operations when
AMR-WB services experience hard handover failures,
and UEs experience call drops.
Issue 01 (2014-04-30)

52
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
GUI Value Range:

TCH,
H, UL_EVQI_SWITCH, DL_EVQI_SWITCH,
VIDEO_RATE_ADAPTION_SWITCH,
VOIP_MANAGE_SWITCH,
DIFF_SERVICE_ON_TERMINAL_SWITCH,
APP_GRP_RES_RSV_SWITCH,
RIM_ON_ECO_SWITCH,
SRBCHG_DRD_FAST_RB_SETUP_SWITCH,
SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH,
H, WBAMR_HHO_FAIL_ROLLBACK_SWITCH
Unit: None
Actual Value Range:
TCH,
VOIP_MANAGE_SWITCH,
RIM_ON_ECO_SWITCH,
Default Value:
TCH:
0,INTERRAT_LOAD_REPORT_FROM_LTE_SWIT
CH:0,UL_EVQI_SWITCH:0,DL_EVQI_SWITCH:
0,VIDEO_RATE_ADAPTION_SWITCH:
0,VOIP_MANAGE_SWITCH:
0,DIFF_SERVICE_ON_TERMINAL_SWITCH:
0,APP_GRP_RES_RSV_SWITCH:
0,RIM_ON_ECO_SWITCH:
0,SRBCHG_DRD_FAST_RB_SETUP_SWITCH:
0,SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH:
0,FACH_RB_RECFG_FAIL_SPEC_CAUSE_SWIT
CH:
0,WBAMR_HHO_FAIL_ROLLBACK_SWITCH:0
Issue 01 (2014-04-30)

53
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
PROCE
SSSWIT
CH5
BSC691
0
SET
URRCT
RLSWI
TCH
WRFD150252
Video
Pacing
WRFD150253
VoIP
Applicat
ion
Manage
ment
Meaning: 1)
TCH(RIM-based and Request-based Load Information
Sharing Switch) Whether a UMTS cell sends its load
information to an LTE cell through the RIM procedure
after receiving a load information sharing request from
the LTE cell. 1: This switch is turned on. UMTS cells
support the RIM-based load information sharing
function. A UMTS cell sends its load information to an
LTE cell after receiving a load information sharing
request from the LTE cell. 0: This switch is turned off.
UMTS cells do not support the RIM-based load
information sharing function. A UMTS cell does not
respond to the load information sharing request from an
LTE cell. 2)
H(Learning LTE Load Through RIM Switch) Whether
the RNC obtains the load information about LTE cells
through the RAN information management (RIM)
procedure. For details about the RIM procedure, see
3GPP TS 48. 018. 1: This switch is turned on. The RNC
obtains the load information about LTE cells through
the RIM procedure. 0: This switch is turned off. The
RNC cannot obtain the load information about LTE
cells through the RIM procedure. 3)
UL_EVQI_SWITCH(UL EVQI Evaluation Switch)
Whether to enable the EVQI function in the uplink. 1:
This switch is turned on. EVQI is enabled in the uplink.
0: This switch is turned off. EVQI is disabled in the
uplink. 4)DL_EVQI_SWITCH(DL EVQI Evaluation
Switch) Whether to enable the EVQI function in the
downlink. 1: This switch is turned on. EVQI is enabled
in the downlink. 0: This switch is turned off. EVQI is
disabled in the downlink. 5)
VIDEO_RATE_ADAPTION_SWITCH (Video
Service Rate Adaption Switch) Whether the Video
Service Rate Adaption feature is enabled. 1: This switch
is turned on. The Video Service Rate Adaption feature
is enabled for PS UEs processing video services. That
is, the rate of video service is ensured or is limited for
these PS UEs. 0: This switch is turned off. The Video
Service Rate Adaption feature is disabled for PS UEs.
6) VOIP_MANAGE_SWITCH (VoIP Application
Management Switch) Whether the VoIP application
management function is enabled. 1: This switch is
turned on. VoIP application management actions are
performed on PS UEs that are processing VoIP services.
MRFD090211
Issue 01 (2014-04-30)

54
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
VoIP application management actions can either be

VoIP application rate ensurance or VoIP application
speed limit. 0: This switch is turned off. the VoIP
application management function is disabled for PS
UEs. 7) DIFF_SERVICE_ON_TERMINAL_SWITCH
(Differentiated Service Based on Terminal Switch)
Whether the Differentiated Service Based on Terminal
feature is enabled. 1: This switch is turned on. PS UEs
processing BE services are grouped into different
terminal groups based on their type approval codes
(TACs) in IMEIs, and each terminal group is assigned
an SPI weight for BE services, thereby achieving
differentiated services. 0: This switch is turned off. The
Differentiated Service Based on Terminal feature is
disabled for PS UEs processing BE services. 8)
APP_GRP_RES_RSV_SWITCH (Differentiated
Service Based on Application Resource Reservation
Switch) Whether the Differentiated Service Based on
Application Resource Reservation feature is enabled. 1:
This switch is turned on. The RNC identifies service
types, maps different service types to different resource
groups, and configure different resource reservation
policies for these resource groups. In this way, resource
reservation is performed based on service types. 0: This
switch is turned off. The RNC does not reserve
resources based on service types or service groups. 9)
RIM_ON_ECO_SWITCH(Support RIM by
eCoordinator Switch) Whether the RIM procedure is
implemented through the eCoordinator. 1: This switch
is turned on. The RIM procedure is implemented
through the eCoordinator. 0: This switch is turned off.
the RIM procedure is implemented through the CN.
This parameter is an advanced parameter. Therefore,
modify the setting of this parameter under the
instruction of Huawei technical support. 10)
SRBCHG_DRD_FAST_RB_SETUP_SWITCH(RB
Fast Setup Switch for RB Setups Accompanied by
DRDs with Changing SRBs) Whether to use the RB fast
setup function for RB setups accompanied by DRDs
with changing SRBs. 1: This switch is turned on. The
accompanied by DRDs with changing SRBs. 0: This
changing SRBs. 11)
SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH
(RB Fast Setup Switch for RB Setups Accompanied by
Issue 01 (2014-04-30)

55
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
DRDs with Unchanged SRBs) Whether to use the RB

fast setup function for RB setups accompanied by DRDs
with unchanged SRBs. 1: This switch is turned on. The
accompanied by DRDs with unchanged SRBs. 0: This
unchanged SRBs. 12)
H Whether the RNC releases a UE's RRC connection
after an RB reconfiguration failure with the cause of
"incompatibleSimultaneousReconfiguration" or
"invalid configuration." This switch is set to off by
default. 1: This switch is turned on. The RNC releases
the UE's RRC connection. 0: This switch is turned off.
The RNC does not release the UE's RRC connection and
rolls back the procedure. 13)
WBAMR_HHO_FAIL_ROLLBACK_SWITCH
Whether RNC performs rollback operations when
AMR-WB services experience hard handover failures.
1: This switch is turned on. The RNC performs rollback
operations when AMR-WB services experience hard
handover failures. Before setting this switch to ON, you
are advised to run the "SET UCONNMODETIMER"
command to set T312 to 1s. Otherwise, some UEs
experience garbled noise. 0: This switch is turned off.
The RNC does not perform rollback operations when
AMR-WB services experience hard handover failures,
and UEs experience call drops.
GUI Value Range:
TCH,
VOIP_MANAGE_SWITCH,
RIM_ON_ECO_SWITCH,
Unit: None
Actual Value Range:
Issue 01 (2014-04-30)

56
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
TCH,
VOIP_MANAGE_SWITCH,
RIM_ON_ECO_SWITCH,
Default Value:
TCH:
0,INTERRAT_LOAD_REPORT_FROM_LTE_SWIT
CH:0,UL_EVQI_SWITCH:0,DL_EVQI_SWITCH:
0,VIDEO_RATE_ADAPTION_SWITCH:
0,VOIP_MANAGE_SWITCH:
0,DIFF_SERVICE_ON_TERMINAL_SWITCH:
0,APP_GRP_RES_RSV_SWITCH:
0,RIM_ON_ECO_SWITCH:
0,SRBCHG_DRD_FAST_RB_SETUP_SWITCH:
0,SRBNOCHG_DRD_FAST_RB_SETUP_SWITCH:
0,FACH_RB_RECFG_FAIL_SPEC_CAUSE_SWIT
CH:
0,WBAMR_HHO_FAIL_ROLLBACK_SWITCH:0
TAC
BSC690
0
ADD
UQOST
AC
MOD
UQOST
AC
RMV
UQOST
AC
None
None
Meaning: Type Allocation Code (TAC) is proportion of

the International Mobile Station Equipment Identity
(IMEI) and represent the first eight digits of the IMEI.
TAC is used to differentiate between the MSs of
different models. This parameter consists of an eight
digit string. If the string is less than eight digits, the
system fills the higher orders with 0s to achieve an eight
digit string.
GUI Value Range: 0~99999999
Unit: None
Actual Value Range: 0~99999999
Default Value: None
Issue 01 (2014-04-30)

57
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
TAC
BSC691
0
ADD
UQOST
AC
None
None
Meaning: Type Allocation Code (TAC) is proportion of

the International Mobile Station Equipment Identity
(IMEI) and represent the first eight digits of the IMEI.
TAC is used to differentiate between the MSs of
different models. This parameter consists of an eight
digit string. If the string is less than eight digits, the
system fills the higher orders with 0s to achieve an eight
digit string.
MOD
UQOST
AC
RMV
UQOST
AC

Unit: None
Default Value: None
DeviceG
roupID
BSC690
0
ADD
UQOST
AC
None
None
MOD
UQOST
AC
Meaning: ID of a terminal group. A terminal group

consists of different types of terminals. The terminal
type is determined by the TAC. You can run the "ADD
UDEVICEGROUP" command to add a terminal group
ID.
Unit: None
Default Value: None
DeviceG
roupID
BSC691
0
ADD
UQOST
AC
MOD
UQOST
AC
None
None

ID.
Unit: None
Default Value: None
Issue 01 (2014-04-30)

58
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DeviceG
roupID
BSC690
0
ADD
UUSER
GRPDE
VICEM
AP
None
None

ID.
MOD
UUSER
GRPDE
VICEM
AP

Unit: None
Default Value: None
RMV
UUSER
GRPDE
VICEM
AP
DeviceG
roupID
BSC691
0
ADD
UUSER
GRPDE
VICEM
AP
None
None
MOD
UUSER
GRPDE
VICEM
AP

ID.
Unit: None
Default Value: None
RMV
UUSER
GRPDE
VICEM
AP
DLSpiw
eight
BSC690
0
ADD
UUSER
GRPDE
VICEM
AP
MOD
UUSER
GRPDE
VICEM
AP
Issue 01 (2014-04-30)
None
None
Meaning: This parameter is used for setting UE-based

downlink SPI scheduling weight. When this parameter
is set to 0, it indicates that the configuration is invalid.
Unit: None
Default Value: 100

59
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DLSpiw
eight
BSC691
0
ADD
UUSER
GRPDE
VICEM
AP
None
None

downlink SPI scheduling weight. When this parameter
is set to 0, it indicates that the configuration is invalid.
Unit: None
MOD
UUSER
GRPDE
VICEM
AP
ULSpiw
eight
BSC690
0
ADD
UUSER
GRPDE
VICEM
AP

Default Value: 100
None
None

Unit: None
MOD
UUSER
GRPDE
VICEM
AP
ULSpiw
eight
BSC691
0
ADD
UUSER
GRPDE
VICEM
AP
MOD
UUSER
GRPDE
VICEM
AP
Issue 01 (2014-04-30)

uplink SPI scheduling weight. When this parameter is
set to 0, it indicates that the configuration is invalid.

Default Value: 100
None
None

uplink SPI scheduling weight. When this parameter is
set to 0, it indicates that the configuration is invalid.
Unit: None
Default Value: 100

60
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
TrafficC
lass
BSC690
0
SET
UUSER
GBR
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Traffic class which includes Best Effort(BE)

and PTT. BE services comprise interactive services,
background services, and IMS.
WRFD050424
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
TrafficC
lass
BSC691
0
SET
UUSER
GBR
WRFD020806
WRFD050424
Differen
tiated
Service
Based
on SPI
Weight
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
THPCla
ss
BSC690
0
Issue 01 (2014-04-30)
SET
UUSER
GBR
WRFD020806
WRFD050424
GUI Value Range: INTERACTIVE, BACKGROUND,

IMSSIGNALLING, PTT
Unit: None
Actual Value Range: INTERACTIVE,
BACKGROUND, IMSSIGNALLING, PTT
Default Value: None
Meaning: Traffic class which includes Best Effort(BE)

and PTT. BE services comprise interactive services,
background services, and IMS.
GUI Value Range: INTERACTIVE, BACKGROUND,
IMSSIGNALLING, PTT
Unit: None
BACKGROUND, IMSSIGNALLING, PTT
Default Value: None
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Traffic Handling Priority (THP) class that the

THP priority is mapped to. This parameter is valid for
only interactive services. The mapping relationship
between the traffic handling priority value of
INTERACTIVE service and its corresponding class can
be set through command "SET UTHPCLASS".
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
GUI Value Range: High, Medium, Low

Unit: None
Actual Value Range: High, Medium, Low
Default Value: None

61
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
THPCla
ss
BSC691
0
SET
UUSER
GBR
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Bearer type of the service. R99 indicates that

the service is carried on a non-HSPA channel. HSPA
indicates that the service is carried on an HSPA channel.
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Actual Value Range: R99, HSPA
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Bearer type of the service. R99 indicates that

the service is carried on a non-HSPA channel. HSPA
indicates that the service is carried on an HSPA channel.
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Actual Value Range: R99, HSPA
BearTyp
e
BearTyp
e
BSC690
0
BSC691
0
Issue 01 (2014-04-30)
SET
UUSER
GBR
SET
UUSER
GBR
WRFD050424
WRFD020806
WRFD050424
WRFD020806
WRFD050424
Unit: None
Default Value: None
GUI Value Range: R99, HSPA

Unit: None
Default Value: None
GUI Value Range: R99, HSPA

Unit: None
Default Value: None

62
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
UserPrio
rity
BSC690
0
SET
UUSER
GBR
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: User priority that is defined according to the

Allocation/Retention Priority (ARP) from the RAB
assignment. The user classes in descending order of
priority are Gold, Silver, and Copper. For details, see
help information of the "SET UUSERPRIORITY"
command.
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
GUI Value Range: GOLD, SILVER, COPPER
Differen
tiated
Service
Based
on SPI
Weight

command.
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Uplink GBR of the BE and PTT services.

GBR is the minimum bit rate that the system can
guarantee for the admitted services. When "BearType"
is set to R99, the parameter value is not greater than
D384.
UserPrio
rity
UlGBR
BSC691
0
BSC690
0
SET
UUSER
GBR
SET
UUSER
GBR
WRFD050424
WRFD020806
WRFD050424
WRFD020806
WRFD050424
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Issue 01 (2014-04-30)
Unit: None
Actual Value Range: GOLD, SILVER, COPPER
Default Value: None
Unit: None
Default Value: None
GUI Value Range: D0, D8, D16, D32, D64, D128,

D144, D256, D384, D608, D1280, D2048, D2720,
D5440
Unit: kbit/s
Actual Value Range: 0, 8, 16, 32, 64, 128, 144, 256, 384,
608, 1280, 2048, 2720, 5440
Default Value: D16

63
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
UlGBR
BSC691
0
SET
UUSER
GBR
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Uplink GBR of the BE and PTT services.

D384.
WRFD050424
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
DlGBR
BSC690
0
SET
UUSER
GBR
WRFD020806
WRFD050424
WRFD0106110
3
Differen
tiated
Service
Based
on SPI
Weight
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Scheduli
ng based
on EPF
and
GBR
Issue 01 (2014-04-30)

D144, D256, D384, D608, D1280, D2048, D2720,
D5440
Unit: kbit/s
608, 1280, 2048, 2720, 5440
Default Value: D16
Meaning: Downlink GBR of the BE and PTT services.
D384.
D144, D256, D384, D512, D768, D1024, D1536,
D1800, D2048, D3600, D7200, D8640, D10100,
D13900, D16000, D21000
Unit: kbit/s
512, 768, 1024, 1536, 1800, 2048, 3600, 7200, 8640,
10100, 13900, 16000, 21000
Default Value: D16

64
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlGBR
BSC691
0
SET
UUSER
GBR
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Downlink GBR of the BE and PTT services.

D384.
WRFD050424
WRFD0106110
3
HappyB
R
BSC690
0
SET
UUSER
HAPPY
BR
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es

D144, D256, D384, D512, D768, D1024, D1536,
D1800, D2048, D3600, D7200, D8640, D10100,
D13900, D16000, D21000
Unit: kbit/s
512, 768, 1024, 1536, 1800, 2048, 3600, 7200, 8640,
10100, 13900, 16000, 21000
Scheduli
ng based
on EPF
and
GBR
Default Value: D16
WRFD0106101
0
HSDPA
Flow
Control
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Happy bit rate. This parameter defines the

happy bit rate of the best effort (BE) service with
different user priorities. The RNC sends the happy bit
rate to the NodeB through the Iub interface. When the
NodeB resource is limited and the HS-DSCH bit rate of
the user exceeds the Happy bit rate, the HS-DSCH
scheduling priority will be decreased. When this
parameter is set to 0, it indicates that NodeB will not
adjust the HS-DSCH scheduling priority. This value of
parameter can be set by "HappyBR" in the "ADD
UOPERUSERHAPPYBR" command. If the value of
"HappyBR" in the "ADD UOPERUSERHAPPYBR"
command is larger than 5000, it will be set to the
minimum of the "HappyBR" parameter value in the
"SET UUSERHAPPYBR" and 5000.
WRFD0106110
3
Scheduli
ng based
on EPF
and
GBR

Unit: kbit/s
Default Value: 0
Issue 01 (2014-04-30)

65
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
HappyB
R
BSC691
0
SET
UUSER
HAPPY
BR
WRFD0106101
0
HSDPA
Flow
Control
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Happy bit rate. This parameter defines the

happy bit rate of the best effort (BE) service with
different user priorities. The RNC sends the happy bit
rate to the NodeB through the Iub interface. When the
NodeB resource is limited and the HS-DSCH bit rate of
the user exceeds the Happy bit rate, the HS-DSCH
scheduling priority will be decreased. When this
parameter is set to 0, it indicates that NodeB will not
adjust the HS-DSCH scheduling priority. This value of
parameter can be set by "HappyBR" in the "ADD
UOPERUSERHAPPYBR" command. If the value of
"HappyBR" in the "ADD UOPERUSERHAPPYBR"
command is larger than 5000, it will be set to the
minimum of the "HappyBR" parameter value in the
"SET UUSERHAPPYBR" and 5000.
WRFD0106110
3
Scheduli
ng based
on EPF
and
GBR

Unit: kbit/s
Default Value: 0
TrafficC
lass
TrafficC
lass
BSC690
0
BSC691
0
Issue 01 (2014-04-30)
SET
UUSER
HAPPY
BR
SET
UUSER
HAPPY
BR
WRFD0106101
0
HSDPA
Flow
Control
Meaning: Traffic class whose Happy Bit Rate

parameters are to be set.
WRFD150233
Differen
tiated
Service
Based
on
Resourc
e
Reservat
ion
Unit: None
WRFD0106101
0
HSDPA
Flow
Control
Meaning: Traffic class whose Happy Bit Rate

parameters are to be set.
WRFD150233
Differen
tiated
Service
Based
on
Resourc
e
Reservat
ion
Unit: None
GUI Value Range: INTERACTIVE, BACKGROUND

BACKGROUND
Default Value: None

BACKGROUND
Default Value: None

66
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
THPCla
ss
BSC690
0
SET
UUSER
HAPPY
BR
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Differen
tiated
Service
Based
on SPI
Weight

Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
THPCla
ss
BSC691
0
Issue 01 (2014-04-30)
SET
UUSER
HAPPY
BR
WRFD050424
WRFD020806
WRFD050424
Unit: None
Default Value: None
Unit: None
Default Value: None

67
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
UserPrio
rity
BSC690
0
SET
UUSER
HAPPY
BR
WRFD050424
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es

command.
WRFD150233
Differen
tiated
Service
Based
on
Resourc
e
Reservat
ion
UserPrio
rity
BSC691
0
SET
UUSER
HAPPY
BR
WRFD050424
WRFD150233
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Differen
tiated
Service
Based
on
Resourc
e
Reservat
ion
Issue 01 (2014-04-30)

Unit: None
Default Value: None

command.
Unit: None
Default Value: None

68
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
TrafficC
lass
BSC690
0
SET
USCHE
DULEP
RIOMA
P
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Traffic handling priority (THP) class that the

THP priority for interactive services is mapped to. The
THP classes are High, Medium, and Low. The mapping
between the THPs and THP classes is configured by
running the "SET UTHPCLASS" command.
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Unit: None
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Traffic handling priority (THP) class that the

THP priority for interactive services is mapped to. The
THP classes are High, Medium, and Low. The mapping
between the THPs and THP classes is configured by
running the "SET UTHPCLASS" command.
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Unit: None
Differen
tiated
Service
Based
on SPI
Weight
Meaning: User priority. The user classes in descending

order of priority are Gold, Silver, and Copper. The user
priority is defined according to the allocation/retention
priority (ARP) that is carried in the RAB assignment
message sent by the CN. The mapping between the
ARPs and user priorities is configured by running the
"SET UUSERPRIORITY" command.
TrafficC
lass
UserPrio
rity
BSC691
0
BSC690
0
SET
USCHE
DULEP
RIOMA
P
SET
USCHE
DULEP
RIOMA
P
WRFD050424
WRFD020806
WRFD050424
WRFD020806
WRFD050424
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Issue 01 (2014-04-30)

BACKGROUND
Default Value: None

BACKGROUND
Default Value: None

Unit: None
Default Value: None

69
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
UserPrio
rity
BSC691
0
SET
USCHE
DULEP
RIOMA
P
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: User priority. The user classes in descending

order of priority are Gold, Silver, and Copper. The user
priority is defined according to the allocation/retention
priority (ARP) that is carried in the RAB assignment
message sent by the CN. The mapping between the
ARPs and user priorities is configured by running the
"SET UUSERPRIORITY" command.
WRFD050424
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
THPCla
ss
THPCla
ss
BSC690
0
BSC691
0
Issue 01 (2014-04-30)
SET
USCHE
DULEP
RIOMA
P
SET
USCHE
DULEP
RIOMA
P
WRFD020806
WRFD050424
WRFD020806
WRFD050424

Unit: None
Default Value: None
Differen
tiated
Service
Based
on SPI
Weight

Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Differen
tiated
Service
Based
on SPI
Weight

Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
Unit: None
Default Value: None
Unit: None
Default Value: None

70
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
SPI
BSC690
0
SET
USCHE
DULEP
RIOMA
P
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Relative priority when RAB data in the PS

domain is scheduled. The larger the value of this
parameter, the higher the scheduling priority. Values
2-11 indicate the scheduling priorities of background
and interactive services.Value 12 indicates the
scheduling priority of the streaming service. Value 13
indicates the scheduling priority of the conversational
service. Value 14 indicates the scheduling priority of the
IMS signaling. Value 15 indicates the scheduling
priority of the SRB service. Values 0 and 1 are reserved
for other services.
Unit: None
Default Value: None
SPI
BSC691
0
SET
USCHE
DULEP
RIOMA
P
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Relative priority when RAB data in the PS

domain is scheduled. The larger the value of this
parameter, the higher the scheduling priority. Values
2-11 indicate the scheduling priorities of background
and interactive services.Value 12 indicates the
scheduling priority of the streaming service. Value 13
indicates the scheduling priority of the conversational
service. Value 14 indicates the scheduling priority of the
IMS signaling. Value 15 indicates the scheduling
priority of the SRB service. Values 0 and 1 are reserved
for other services.
Unit: None
Default Value: None
Issue 01 (2014-04-30)

71
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
UlCapac
itySelect
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Method of determining an HSUPA service

rate when the differentiated HSPA service based on SPI
weight function is enabled. Value MBR indicates that
the HSUPA service rate is the uplink MBR assigned by
the CN. Value Category indicates that the peak rate
corresponding to the UE HSUPA category is used.
Value Min indicates that the smaller one between MBR
and the peak rate corresponding to the UE HSUPA
category is used. Value Max indicates that the greater
one between MBR and the peak rate corresponding to
the UE HSUPA category is used.
GUI Value Range: MBR, Category, Min, Max
Unit: None
Actual Value Range: MBR, Category, Min, Max
Default Value: Min
UlCapac
itySelect
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Method of determining an HSUPA service

the HSUPA service rate is the uplink MBR assigned by
the CN. Value Category indicates that the peak rate
corresponding to the UE HSUPA category is used.
and the peak rate corresponding to the UE HSUPA
the UE HSUPA category is used.
Unit: None
Default Value: Min
Issue 01 (2014-04-30)

72
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlCapac
itySelect
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Method of determining an HSDPA service

the HSDPA service rate is the downlink MBR assigned
by the CN. Value Category indicates that the peak rate
corresponding to the UE HSDPA category is used.
and the peak rate corresponding to the UE HSDPA
the UE HSDPA category is used.
Unit: None
Default Value: Min
DlCapac
itySelect
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Method of determining an HSDPA service

the HSDPA service rate is the downlink MBR assigned
by the CN. Value Category indicates that the peak rate
corresponding to the UE HSDPA category is used.
and the peak rate corresponding to the UE HSDPA
the UE HSDPA category is used.
Unit: None
Default Value: Min
DlRateT
hreshold
1
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Downlink rate threshold 1. This parameter is

used to determine the value range of an HSDPA service
weight function is enabled. The SPI weight is
determined according to the value range.
Unit: kbit/s
Default Value: 128
Issue 01 (2014-04-30)

73
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlRateT
hreshold
1
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 128
DlRateT
hreshold
2
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 384
DlRateT
hreshold
2
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 384
UlRateT
hreshold
1
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Uplink rate threshold 1. This parameter is

used to determine the value range of an HSUPA service
Unit: kbit/s
Default Value: 128
Issue 01 (2014-04-30)

74
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
UlRateT
hreshold
1
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 128
UlRateT
hreshold
2
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 384
UlRateT
hreshold
2
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 384
DlRateT
hreshold
3
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 512
Issue 01 (2014-04-30)

75
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlRateT
hreshold
3
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 512
UlRateT
hreshold
3
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 512
UlRateT
hreshold
3
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 512
DlRateT
hreshold
4
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 1000
Issue 01 (2014-04-30)

76
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlRateT
hreshold
4
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 1000
UlRateT
hreshold
4
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 768
UlRateT
hreshold
4
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 768
DlRateT
hreshold
5
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 2000
Issue 01 (2014-04-30)

77
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlRateT
hreshold
5
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 2000
UlRateT
hreshold
5
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 1000
UlRateT
hreshold
5
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 1000
DlRateT
hreshold
6
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 4000
Issue 01 (2014-04-30)

78
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlRateT
hreshold
6
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 4000
UlRateT
hreshold
6
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 1500
UlRateT
hreshold
6
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 1500
DlRateT
hreshold
7
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 8000
Issue 01 (2014-04-30)

79
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlRateT
hreshold
7
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 8000
UlRateT
hreshold
7
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 2500
UlRateT
hreshold
7
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 2500
DlRateT
hreshold
8
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 16000
Issue 01 (2014-04-30)

80
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlRateT
hreshold
8
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
UlRateT
hreshold
8
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 5500
UlRateT
hreshold
8
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 5500
DlRateT
hreshold
9
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Issue 01 (2014-04-30)

81
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
DlRateT
hreshold
9
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
UlRateT
hreshold
9
BSC690
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 7500
UlRateT
hreshold
9
BSC691
0
SET
UCAPA
RATER
ANGE
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight

Unit: kbit/s
Default Value: 7500
ServiceP
riAdjCo
ef
BSC690
0
SET
UDPUC
FGDAT
A
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Specifies the coefficient for adjusting service

priority weight in the matching record.(Adjusted SPI
Weight = min (Initial SPI weight * ServicePriAdjCoef
* 10%, 100),Initial SPI weight is set by the "SpiWeight"
parameter on RNC.).
Unit: 0.1
Actual Value Range: 10~1000(%)
Default Value: 10
Issue 01 (2014-04-30)

82
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
ServiceP
riAdjCo
ef
BSC691
0
SET
UDPUC
FGDAT
A
WRFD020806
Differen
tiated
Service
Based
on SPI
Weight
Meaning: Specifies the coefficient for adjusting service

priority weight in the matching record.(Adjusted SPI
Weight = min (Initial SPI weight * ServicePriAdjCoef
* 10%, 100),Initial SPI weight is set by the "SpiWeight"
parameter on RNC.).
Unit: 0.1
Actual Value Range: 10~1000(%)
Default Value: 10
MaxTxP
ower
BSC690
0
ADD
UCELL
SETUP
WRFD020501
MOD
UCELL
Open
Loop
Power
Control
Meaning: Sum of the maximum transmit power of all

DL channels in a cell. For detailed information of this
parameter, see 3GPP TS 25.433.
Unit: 0.1dBm
Default Value: 430
MaxTxP
ower
BSC691
0
ADD
UCELL
SETUP
MOD
UCELL
WRFD020501
Open
Loop
Power
Control
Meaning: Sum of the maximum transmit power of all

DL channels in a cell. For detailed information of this
parameter, see 3GPP TS 25.433.
Unit: 0.1dBm
Default Value: 430
Issue 01 (2014-04-30)

83
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
PROCE
SSSWIT
CH
BSC690
0
SET
URRCT
RLSWI
TCH
WRFD021102
Cell
Barring
WRFD150205
Layered
Paging
in Idle
Mode
Meaning: 1)INVOKE_TRACE_SWITCH. 1: This

switch is turned on. RNC will start Invoke Trace
procedure upon receiving INVOKE TRACE Message
form CN. 0: This switch is turned off. RNC won't start
the Invoke Trace procedure though it receives the
INVOKE TRACE message. 2)
SYS_INFO_UPDATE_FOR_IU_RST. 1: This switch
is turned on. The SIB1 does not contain broken-down
CN information. In this case, the UE will not select
broken-down network when Iu transmission failure
occurs. 0: This switch is turned off. The SIB1 contains
the broken-down CN information. In this case, the UE
will select broken-down network but the RNC will
reject the request when Iu transmission failure occurs.
3)DRNC_DIRECT_DSCR. Whether the Directed
Signaling Connection re-establishment (DSCR)
procedure is triggered during a cell update over the Iur
interface for UEs that are not in the CELL_DCH state
or for UEs that are in the CELL_DCH state and do not
have an Iur connection. This switch is set on the drift
radio network controller (DRNC) side. 1: This switch is
turned on. DRNC will start DSCR procedure directly in
RRC states other than CELL_DCH or CELL_DCH that
do not have an Iur connection. 0: This switch is turned
off. DRNC will transfer RRC CELL UPDATE message
to SRNC. 4)PTUSER_IDENTIFY_ENH_SWITCH
(Platinum user identify enhancement switch) Whether
platinum users are identified in DRNC or relocation
scenarios. 1: This switch is turned on. Platinum users
are identified and their services are guaranteed in DRNC
or relocation scenarios. 0: This switch is turned off.
Platinum users are not identified in DRNC or relocation
scenarios. 5)RNC_SHARE_SWITCH. 1: This switch is
turned on. The traffic sharing function is enabled. 0:
This switch is turned off. The traffic sharing function is
disabled, service access will be affected under heavy
traffic. 6)RNCAP_IMSI_HO_SWITCH. 1: This switch
is turned on. Imsi handover function will be used. 0:
This switch is turned off. Imsi handover function will
not be used. 7)
TERMINAL_VERSION_DEBASE_SWITCH. 1: This
switch is turned on. Terminal version R4 will debase to
R99. 0: This switch is turned off. Terminal version R4
will not debase to R99. 8)
SYS_HO_OUT_CIPHER_SWITCH. 1: This switch is
turned on. The RNC will add ciphering byte at GSM
HANDOVER COMMAND if the GSM system do not
WRFD150204
WRFD010101
WRFD150231
WRFD020500
WRFD021303
WRFD020132
WRFD020124
WRFD140206
WRFD020134
WRFD020128
WRFD0106121
2
WRFD010641
WRFD020806
Platinu
m User
Prioritizi
ng
3GPP
R9
Specific
ations
RIM
Based
UMTS
Target
Cell
Selectio
n for
LTE
Enhance
d Fast
Dorman
cy
IMSI
Based
Handov
er
Web
browsin
g
accelerat
ion
Uplink
Flow
Control
of User
Plane
Layered
Paging
in
Issue 01 (2014-04-30)

84
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
URA_P
CH
add any cipher information at that message. 0: This

switch is turned off. The RNC will not add ciphering
byte at GSM HANDOVER COMMAND if the GSM
system do not add any cipher information at that
message. 9)SYS_HO_CIPHER_CONFIG. 1: This
switch is turned on. The cipher configuration in the
added cipher byte in GSM will be A5/1. 0: This switch
is turned off. The cipher configuration is A5/0. 10)
BARRED_CELL_FOR_CSDOMAIN_RST. 1: This
switch is turned on. Cell will be bared when CS domain
is invalid. 0: This switch is turned off. The CS domain
will be bared when CS domain is invalid. It is invalid If
SYS_INFO_UPDATE_FOR_IU_RST is not checked.
11)CR2284R1_SWITCH. 1: This switch is turned on.
The RNC performs the processing based on CR2284R1,
that is, based on the description in section 8.6.6.28 of
Release 5 TS 25.331. In this section, it describes that the
HFN is increased by one when RB setup is accompanied
by a Timing re-initialized hard handover. 0: This switch
is turned off. The HFN is not increased by one when RB
setup is accompanied by a Timing re-initialized hard
handover. 12)CDT_MSG_FULL_TRACE. 1: This
switch is turned on. CDT trace function starts tracing
from message RRC CONNECT REQUEST. 0: This
switch is turned off. CDT trace function starts tracing
from message COMMON ID. 13)
CR2284R1_COMPATIBLE_SWITCH. CR2284R1
causes the compatible problem. if UE is not consistent
with RNC regarding whether accept the CR2284R1 or
not, it will cause the problem of streaming when UEs
are communicating with each other. So RNC creates this
switch. when it is checked, RNC is auto-adaptive to
accept the CR2284R1 according to UE version
information. The principles that RNC judges UE
whether to accept the CR2284R1 are as follows: R5 and
above UE accepts the CR; R99/R4 UE, if it receives the
START LIST value from RB SETUP
COMPLETE,RNC figures that UE accepts the CR;
R99/R4 UE, if it only receives the START value from
RB SETUP COMPLETE,RNC figures that UE does not
accept the CR; when it is not checked, whether RNC
accept the CR or not is according to
CR2284R1_SWITCH. The relations between these two
switches CR2284R1_SWITCH and
CR2284R1_COMPATIBLE_SWITCH are as follows:
1: This switch is turned on. RNC is self-compatible, so
the CR2284R1_SWITCH is invalid; 0: This switch is
Push to
Talk
Quality
Improve
ment for
Subscrib
ed
Service
HSUPA
Iub Flow
Control
in Case
of Iub
Congesti
on
HSUPA
Adaptiv
e
Transmi
ssion
Differen
tiated
Service
Based
on SPI
Weight
Issue 01 (2014-04-30)
10 Parameters

85
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
turned off. The CR2284R1_SWITCH is valid. 14)

COMBINE_OPERATION_DRD_SWITCH. 1: This
switch is turned on. RNC will not reject the message RB
SETUP CMP without the IE active time. 0: This switch
is turned off. RNC will reject the message RB SETUP
CMP without the IE active time. 15)
UL_INTER_PROTECT_SWITCH. Although the
configuration interface in this version supports delivery
and synchronization of the bit field value, the bit field
value is no longer internally used. 1: This switch is
turned on. RNC will do integrity protection check for
uplink RRC messages. 0: This switch is turned off. RNC
will not do integrity protection check for uplink RRC
messages. 16)FAST_DORMANCY_SWITCH. 1: This
switch is turned on. RNC will apply FAST
DORMANCY function. 0: This switch is turned off.
RNC will not apply FAST DORMANCY function. 17)
SYS_HO_IN_CIPHER_SWITCH. During an
incoming GSM-to-UMTS handover, if the RNC cannot
obtain a UE's encryption capability information from
the RELOC REQ message: 1: This switch is turned on.
The encryption algorithm that is configured for both the
RNC and CN is used. For example, if the CN is
configured with the encryption algorithm UEA1 and the
RNC is configured with encryption algorithms UEA0
and UEA1, then the RNC uses the encryption algorithm
UEA1. 0: This switch is turned off. Default configured
of encrypted parameter UIA1 and UEA0 is used. 18)
PTT_EARLY_TRANS_SWITCH_OFF. 1: This switch
is turned on. PTT user will not apply the early
transmission function. 0: This switch is turned off. PTT
user will apply the early transmission function. 19)
UPLINK_MDC_ENHENCEMENT_SWITCH. This
switch has become invalid. 20)
NODEB_PRIVATE_INTERFACE_SWITCH. 1: This
switch is turned on. The NodeB private interface data
can be taken to the NodeB through the IUB protocol
message. 0: This switch is turned off. The NodeB
private interface data can not be taken to the NodeB
through the IUB protocol message. 21)
PTT_SPEC_LI_SWITCH_OFF. 1: This switch is
turned on. Special LI(Length Indicator) will not be used
for PTT user. 0: This switch is turned off. Special LI
(Length Indicator) will be used for PTT user. 22)
RNC_DF_2_URA_PCH_SWITCH. 1: This switch is
turned on. RNC will support transferring Fast
Dormancy UE from CELL_DCH or CELL_FACH to
Issue 01 (2014-04-30)

86
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
URA_PCH. 0: This switch is turned off. RNC will not

support transferring Fast Dormancy UE from
CELL_DCH or CELL_FACH to URA_PCH. 23)
FD_TAC_MATCH_SWITCH. 1: This switch is turned
on. The RNC uses TAC matching to determine whether
to apply the FAST DORMANCY function for pre fast
dormancy UEs. 0: This switch is turned off. The RNC
applies the FAST DORMANCY function for pre fast
dormancy UEs of 3GPP Release 5 or later. 24)
NONPTT_L1_FAST_SYNC_SWITCH. 1: This switch
is turned on. If a UE sets up a non-PTT service on the
DCH, the RNC includes the Post-verification period
information element (IE) in a Uu message to instruct the
UE to perform concurrent uplink and downlink
synchronization. 0: This switch is turned off. If a UE
sets up a non-PTT service on the DCH, the RNC does
not include the Post-verification period IE in a Uu
message. The UE first performs downlink
synchronization and then uplink synchronization. 25)
URAPCH_LAYERED_PAGING_RT_SWITCH.
Whether the RNC allows Layered Paging in URA_PCH
for a UE processing real-time services. 1: This switch
is turned on. The RNC sends paging messages to the cell
on which a UE processing real-time services camped
recently and to the neighboring cells of this cell. The
RNC pages the UE in the entire UTRAN registration
area (URA) only when it does not receive a response
from the UE. This significantly reduces the number of
paging messages on the Uu interface. 0: This switch is
turned off. The RNC directly pages the UE in the entire
URA. 26)
URAPCH_LAYERED_PAGING_NRT_SWITCH.
for a UE processing non-real-time services. 1: This
switch is turned on. The RNC sends paging messages
to the cell on which a UE processing non-real-time
services camped recently and to the neighboring cells
of this cell. The RNC pages the UE in the entire URA
only when the RNC does not receive a response from
the UE. This significantly reduces the number of paging
messages on the Uu interface. 0: This switch is turned
off. The RNC directly pages the UE in the entire URA.
27)IDLE_LAYERED_PAGING_NRT_SWITCH.
Whether to enable layered paging for UEs in the idle
state who will establish non-real-time service. 1: This
switch is turned on. The first broadcasts a paging
message in the cell who has interacted with the UE for
Issue 01 (2014-04-30)

87
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
the last time and its neighboring cells. If the UE cannot

be paged, the RNC then broadcasts a paging message in
the LAC or RAC area. 0: This switch is turned off. The
RNC directly broadcasts a paging message in the LAC
or RAC area. 28)
IDLE_LAYERED_PAGING_RT_SWITCH. Whether
to enable layered paging for UEs in the idle state who
will establish real-time service. 1: This switch is turned
on. First broadcasts a paging message in the cell who
has interacted with the UE for the last time and its
neighboring cells. If the UE cannot be paged, the RNC
then broadcasts a paging message in the LAC or RAC
area. 0: This switch is turned off. The RNC directly
broadcasts a paging message in the LAC or RAC area.
29)INTELLIGENT_WIFI_DETECT_AND_SELECTION. Whether to enable intelligent Wi-Fi detection
and selection for the RNC. 1: This switch is turned on.
The RNC supports intelligent Wi-Fi detection and
selection. 0: This switch is turned off. The RNC does
not supports intelligent Wi-Fi detection and selection.
30)
INTERRAT_LOAD_REPORT_FOR_LTE_SWITCH.
Whether to enable the RIM-based cell load sharing
function(Multiple Report). 1: This switch is turned on.
RIM-based load sharing can be achieved between
UMTS and LTE cells. Upon receiving a load sharing
request from an LTE cell, a UMTS cell responds with
its own load information. 0: This switch is turned off.
UMTS cells do not support the RIM-based cell load
sharing function. Therefore, UMTS cells do not respond
to load sharing requests from LTE cells. 31)
PTUSER_IDENTIFY_SWITCH. Whether to
preferentially guarantee platinum users in terms of
network access, voice quality, or PS service rate. 1: This
switch is turned on. The RNC recognizes platinum users
and preferentially guarantees their user experience. 0:
This switch is turned off. The RNC does not recognize
platinum users and does not preferentially guarantee
their user experience. Disuse Statement:In future
versions, the RNC_SHARE_SWITCH,
TERMINAL_VERSION_DEBASE_SWITCH,
CR2284R1_SWITCH,
CR2284R1_COMPATIBLE_SWITCH,
COMBINE_OPERATION_DRD_SWITCH and
UPLINK_MDC_ENHENCEMENT_SWITCH bit
field value under the PROCESSSWITCH parameter
will be deleted. Although the configuration interface in
Issue 01 (2014-04-30)

88
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
this version supports delivery and synchronization of

the bit field value, the bit field value is no longer
internally used. Instead, the function of
RNC_SHARE_SWITCH will be controlled by the
RncShareSwitch parameter in the SET
UCTRLPLNSHAREPARA command.
GUI Value Range: INVOKE_TRACE_SWITCH,
SYS_INFO_UPDATE_FOR_IU_RST,
DRNC_DIRECT_DSCR,
PTUSER_IDENTIFY_ENH_SWITCH,
RNC_SHARE_SWITCH,
RNCAP_IMSI_HO_SWITCH,
SYS_HO_OUT_CIPHER_SWITCH,
SYS_HO_CIPHER_CONFIG,
BARRED_CELL_FOR_CSDOMAIN_RST,
CR2284R1_SWITCH, CDT_MSG_FULL_TRACE,
COMBINE_OPERATION_DRD_SWITCH,
UL_INTER_PROTECT_SWITCH,
FAST_DORMANCY_SWITCH,
SYS_HO_IN_CIPHER_SWITCH,
PTT_EARLY_TRANS_SWITCH_OFF,
UPLINK_MDC_ENHENCEMENT_SWITCH,
NODEB_PRIVATE_INTERFACE_SWITCH,
PTT_SPEC_LI_SWITCH_OFF,
RNC_DF_2_URA_PCH_SWITCH,
FD_TAC_MATCH_SWITCH,
NONPTT_L1_FAST_SYNC_SWITCH,
URAPCH_LAYERED_PAGING_RT_SWITCH,
URAPCH_LAYERED_PAGING_NRT_SWITCH,
IDLE_LAYERED_PAGING_NRT_SWITCH,
IDLE_LAYERED_PAGING_RT_SWITCH,
INTELLIGENT_WIFI_DETECT_AND_SELECTION,
INTERRAT_LOAD_REPORT_FOR_LTE_SWITCH,
PTUSER_IDENTIFY_SWITCH
Unit: None
Actual Value Range: INVOKE_TRACE_SWITCH,
DRNC_DIRECT_DSCR,
RNC_SHARE_SWITCH,
Issue 01 (2014-04-30)

89
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
Default Value: INVOKE_TRACE_SWITCH:
0,SYS_INFO_UPDATE_FOR_IU_RST:
0,DRNC_DIRECT_DSCR:
0,PTUSER_IDENTIFY_ENH_SWITCH:
0,RNC_SHARE_SWITCH:
1,RNCAP_IMSI_HO_SWITCH:
0,TERMINAL_VERSION_DEBASE_SWITCH:
0,SYS_HO_OUT_CIPHER_SWITCH:
0,SYS_HO_CIPHER_CONFIG:
1,BARRED_CELL_FOR_CSDOMAIN_RST:
0,CR2284R1_SWITCH:
0,CDT_MSG_FULL_TRACE:
0,CR2284R1_COMPATIBLE_SWITCH:
1,COMBINE_OPERATION_DRD_SWITCH:
1,UL_INTER_PROTECT_SWITCH:
0,FAST_DORMANCY_SWITCH:
0,SYS_HO_IN_CIPHER_SWITCH:
0,PTT_EARLY_TRANS_SWITCH_OFF:
0,UPLINK_MDC_ENHENCEMENT_SWITCH:
0,NODEB_PRIVATE_INTERFACE_SWITCH:
0,PTT_SPEC_LI_SWITCH_OFF:
0,RNC_DF_2_URA_PCH_SWITCH:
0,FD_TAC_MATCH_SWITCH:
Issue 01 (2014-04-30)

90
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
0,NONPTT_L1_FAST_SYNC_SWITCH:
0,URAPCH_LAYERED_PAGING_RT_SWITCH:
0,URAPCH_LAYERED_PAGING_NRT_SWITCH:
0,IDLE_LAYERED_PAGING_NRT_SWITCH:
0,IDLE_LAYERED_PAGING_RT_SWITCH:
0,INTELLIGENT_WIFI_DETECT_AND_SELECTION:
0,INTERRAT_LOAD_REPORT_FOR_LTE_SWITC
H:0,PTUSER_IDENTIFY_SWITCH:0
Issue 01 (2014-04-30)

91
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
PROCE
SSSWIT
CH
BSC691
0
SET
URRCT
RLSWI
TCH
WRFD021102
Cell
Barring
WRFD150205
Layered
Paging
in Idle
Mode
Meaning: 1)INVOKE_TRACE_SWITCH. 1: This

switch is turned on. RNC will start Invoke Trace
procedure upon receiving INVOKE TRACE Message
form CN. 0: This switch is turned off. RNC won't start
the Invoke Trace procedure though it receives the
INVOKE TRACE message. 2)
SYS_INFO_UPDATE_FOR_IU_RST. 1: This switch
is turned on. The SIB1 does not contain broken-down
CN information. In this case, the UE will not select
broken-down network when Iu transmission failure
occurs. 0: This switch is turned off. The SIB1 contains
the broken-down CN information. In this case, the UE
will select broken-down network but the RNC will
reject the request when Iu transmission failure occurs.
3)DRNC_DIRECT_DSCR. Whether the Directed
Signaling Connection re-establishment (DSCR)
procedure is triggered during a cell update over the Iur
interface for UEs that are not in the CELL_DCH state
or for UEs that are in the CELL_DCH state and do not
have an Iur connection. This switch is set on the drift
radio network controller (DRNC) side. 1: This switch is
turned on. DRNC will start DSCR procedure directly in
RRC states other than CELL_DCH or CELL_DCH that
do not have an Iur connection. 0: This switch is turned
off. DRNC will transfer RRC CELL UPDATE message
to SRNC. 4)PTUSER_IDENTIFY_ENH_SWITCH
(Platinum user identify enhancement switch) Whether
platinum users are identified in DRNC or relocation
scenarios. 1: This switch is turned on. Platinum users
are identified and their services are guaranteed in DRNC
or relocation scenarios. 0: This switch is turned off.
Platinum users are not identified in DRNC or relocation
scenarios. 5)RNC_SHARE_SWITCH. 1: This switch is
turned on. The traffic sharing function is enabled. 0:
This switch is turned off. The traffic sharing function is
disabled, service access will be affected under heavy
traffic. 6)RNCAP_IMSI_HO_SWITCH. 1: This switch
is turned on. Imsi handover function will be used. 0:
This switch is turned off. Imsi handover function will
not be used. 7)
TERMINAL_VERSION_DEBASE_SWITCH. 1: This
switch is turned on. Terminal version R4 will debase to
R99. 0: This switch is turned off. Terminal version R4
will not debase to R99. 8)
SYS_HO_OUT_CIPHER_SWITCH. 1: This switch is
turned on. The RNC will add ciphering byte at GSM
HANDOVER COMMAND if the GSM system do not
WRFD150204
WRFD010101
WRFD150231
WRFD020500
WRFD021303
WRFD020132
WRFD020124
WRFD140206
WRFD020134
WRFD020128
WRFD0106121
2
WRFD010641
WRFD020806
Platinu
m User
Prioritizi
ng
3GPP
R9
Specific
ations
RIM
Based
UMTS
Target
Cell
Selectio
n for
LTE
Enhance
d Fast
Dorman
cy
IMSI
Based
Handov
er
Web
browsin
g
accelerat
ion
Uplink
Flow
Control
of User
Plane
Layered
Paging
in
Issue 01 (2014-04-30)

92
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
URA_P
CH
add any cipher information at that message. 0: This

switch is turned off. The RNC will not add ciphering
byte at GSM HANDOVER COMMAND if the GSM
system do not add any cipher information at that
message. 9)SYS_HO_CIPHER_CONFIG. 1: This
switch is turned on. The cipher configuration in the
added cipher byte in GSM will be A5/1. 0: This switch
is turned off. The cipher configuration is A5/0. 10)
BARRED_CELL_FOR_CSDOMAIN_RST. 1: This
switch is turned on. Cell will be bared when CS domain
is invalid. 0: This switch is turned off. The CS domain
will be bared when CS domain is invalid. It is invalid If
SYS_INFO_UPDATE_FOR_IU_RST is not checked.
11)CR2284R1_SWITCH. 1: This switch is turned on.
The RNC performs the processing based on CR2284R1,
that is, based on the description in section 8.6.6.28 of
Release 5 TS 25.331. In this section, it describes that the
HFN is increased by one when RB setup is accompanied
by a Timing re-initialized hard handover. 0: This switch
is turned off. The HFN is not increased by one when RB
setup is accompanied by a Timing re-initialized hard
handover. 12)CDT_MSG_FULL_TRACE. 1: This
switch is turned on. CDT trace function starts tracing
from message RRC CONNECT REQUEST. 0: This
switch is turned off. CDT trace function starts tracing
from message COMMON ID. 13)
CR2284R1_COMPATIBLE_SWITCH. CR2284R1
causes the compatible problem. if UE is not consistent
with RNC regarding whether accept the CR2284R1 or
not, it will cause the problem of streaming when UEs
are communicating with each other. So RNC creates this
switch. when it is checked, RNC is auto-adaptive to
accept the CR2284R1 according to UE version
information. The principles that RNC judges UE
whether to accept the CR2284R1 are as follows: R5 and
above UE accepts the CR; R99/R4 UE, if it receives the
START LIST value from RB SETUP
COMPLETE,RNC figures that UE accepts the CR;
R99/R4 UE, if it only receives the START value from
RB SETUP COMPLETE,RNC figures that UE does not
accept the CR; when it is not checked, whether RNC
accept the CR or not is according to
CR2284R1_SWITCH. The relations between these two
switches CR2284R1_SWITCH and
CR2284R1_COMPATIBLE_SWITCH are as follows:
1: This switch is turned on. RNC is self-compatible, so
the CR2284R1_SWITCH is invalid; 0: This switch is
Push to
Talk
Quality
Improve
ment for
Subscrib
ed
Service
HSUPA
Iub Flow
Control
in Case
of Iub
Congesti
on
HSUPA
Adaptiv
e
Transmi
ssion
Differen
tiated
Service
Based
on SPI
Weight
Issue 01 (2014-04-30)
10 Parameters

93
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
turned off. The CR2284R1_SWITCH is valid. 14)

COMBINE_OPERATION_DRD_SWITCH. 1: This
switch is turned on. RNC will not reject the message RB
SETUP CMP without the IE active time. 0: This switch
is turned off. RNC will reject the message RB SETUP
CMP without the IE active time. 15)
UL_INTER_PROTECT_SWITCH. Although the
configuration interface in this version supports delivery
and synchronization of the bit field value, the bit field
value is no longer internally used. 1: This switch is
turned on. RNC will do integrity protection check for
uplink RRC messages. 0: This switch is turned off. RNC
will not do integrity protection check for uplink RRC
messages. 16)FAST_DORMANCY_SWITCH. 1: This
switch is turned on. RNC will apply FAST
DORMANCY function. 0: This switch is turned off.
RNC will not apply FAST DORMANCY function. 17)
SYS_HO_IN_CIPHER_SWITCH. During an
incoming GSM-to-UMTS handover, if the RNC cannot
obtain a UE's encryption capability information from
the RELOC REQ message: 1: This switch is turned on.
The encryption algorithm that is configured for both the
RNC and CN is used. For example, if the CN is
configured with the encryption algorithm UEA1 and the
RNC is configured with encryption algorithms UEA0
and UEA1, then the RNC uses the encryption algorithm
UEA1. 0: This switch is turned off. Default configured
of encrypted parameter UIA1 and UEA0 is used. 18)
PTT_EARLY_TRANS_SWITCH_OFF. 1: This switch
is turned on. PTT user will not apply the early
transmission function. 0: This switch is turned off. PTT
user will apply the early transmission function. 19)
UPLINK_MDC_ENHENCEMENT_SWITCH. This
switch has become invalid. 20)
NODEB_PRIVATE_INTERFACE_SWITCH. 1: This
switch is turned on. The NodeB private interface data
can be taken to the NodeB through the IUB protocol
message. 0: This switch is turned off. The NodeB
private interface data can not be taken to the NodeB
through the IUB protocol message. 21)
PTT_SPEC_LI_SWITCH_OFF. 1: This switch is
turned on. Special LI(Length Indicator) will not be used
for PTT user. 0: This switch is turned off. Special LI
(Length Indicator) will be used for PTT user. 22)
RNC_DF_2_URA_PCH_SWITCH. 1: This switch is
turned on. RNC will support transferring Fast
Dormancy UE from CELL_DCH or CELL_FACH to
Issue 01 (2014-04-30)

94
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
URA_PCH. 0: This switch is turned off. RNC will not

support transferring Fast Dormancy UE from
CELL_DCH or CELL_FACH to URA_PCH. 23)
FD_TAC_MATCH_SWITCH. 1: This switch is turned
on. The RNC uses TAC matching to determine whether
to apply the FAST DORMANCY function for pre fast
dormancy UEs. 0: This switch is turned off. The RNC
applies the FAST DORMANCY function for pre fast
dormancy UEs of 3GPP Release 5 or later. 24)
NONPTT_L1_FAST_SYNC_SWITCH. 1: This switch
is turned on. If a UE sets up a non-PTT service on the
DCH, the RNC includes the Post-verification period
information element (IE) in a Uu message to instruct the
UE to perform concurrent uplink and downlink
synchronization. 0: This switch is turned off. If a UE
sets up a non-PTT service on the DCH, the RNC does
not include the Post-verification period IE in a Uu
message. The UE first performs downlink
synchronization and then uplink synchronization. 25)
URAPCH_LAYERED_PAGING_RT_SWITCH.
for a UE processing real-time services. 1: This switch
is turned on. The RNC sends paging messages to the cell
on which a UE processing real-time services camped
recently and to the neighboring cells of this cell. The
RNC pages the UE in the entire UTRAN registration
area (URA) only when it does not receive a response
from the UE. This significantly reduces the number of
paging messages on the Uu interface. 0: This switch is
turned off. The RNC directly pages the UE in the entire
URA. 26)
URAPCH_LAYERED_PAGING_NRT_SWITCH.
for a UE processing non-real-time services. 1: This
switch is turned on. The RNC sends paging messages
to the cell on which a UE processing non-real-time
services camped recently and to the neighboring cells
of this cell. The RNC pages the UE in the entire URA
only when the RNC does not receive a response from
the UE. This significantly reduces the number of paging
messages on the Uu interface. 0: This switch is turned
off. The RNC directly pages the UE in the entire URA.
27)IDLE_LAYERED_PAGING_NRT_SWITCH.
Whether to enable layered paging for UEs in the idle
state who will establish non-real-time service. 1: This
switch is turned on. The first broadcasts a paging
message in the cell who has interacted with the UE for
Issue 01 (2014-04-30)

95
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
the last time and its neighboring cells. If the UE cannot

be paged, the RNC then broadcasts a paging message in
the LAC or RAC area. 0: This switch is turned off. The
RNC directly broadcasts a paging message in the LAC
or RAC area. 28)
IDLE_LAYERED_PAGING_RT_SWITCH. Whether
to enable layered paging for UEs in the idle state who
will establish real-time service. 1: This switch is turned
on. First broadcasts a paging message in the cell who
has interacted with the UE for the last time and its
neighboring cells. If the UE cannot be paged, the RNC
then broadcasts a paging message in the LAC or RAC
area. 0: This switch is turned off. The RNC directly
broadcasts a paging message in the LAC or RAC area.
29)INTELLIGENT_WIFI_DETECT_AND_SELECTION. Whether to enable intelligent Wi-Fi detection
and selection for the RNC. 1: This switch is turned on.
The RNC supports intelligent Wi-Fi detection and
selection. 0: This switch is turned off. The RNC does
not supports intelligent Wi-Fi detection and selection.
30)
INTERRAT_LOAD_REPORT_FOR_LTE_SWITCH.
Whether to enable the RIM-based cell load sharing
function(Multiple Report). 1: This switch is turned on.
RIM-based load sharing can be achieved between
UMTS and LTE cells. Upon receiving a load sharing
request from an LTE cell, a UMTS cell responds with
its own load information. 0: This switch is turned off.
UMTS cells do not support the RIM-based cell load
sharing function. Therefore, UMTS cells do not respond
to load sharing requests from LTE cells. 31)
PTUSER_IDENTIFY_SWITCH. Whether to
preferentially guarantee platinum users in terms of
network access, voice quality, or PS service rate. 1: This
switch is turned on. The RNC recognizes platinum users
and preferentially guarantees their user experience. 0:
This switch is turned off. The RNC does not recognize
platinum users and does not preferentially guarantee
their user experience. Disuse Statement:In future
versions, the RNC_SHARE_SWITCH,
CR2284R1_SWITCH,
COMBINE_OPERATION_DRD_SWITCH and
UPLINK_MDC_ENHENCEMENT_SWITCH bit
field value under the PROCESSSWITCH parameter
will be deleted. Although the configuration interface in
Issue 01 (2014-04-30)

96
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
this version supports delivery and synchronization of

the bit field value, the bit field value is no longer
internally used. Instead, the function of
RNC_SHARE_SWITCH will be controlled by the
RncShareSwitch parameter in the SET
UCTRLPLNSHAREPARA command.
GUI Value Range: INVOKE_TRACE_SWITCH,
DRNC_DIRECT_DSCR,
RNC_SHARE_SWITCH,
Unit: None
Actual Value Range: INVOKE_TRACE_SWITCH,
DRNC_DIRECT_DSCR,
RNC_SHARE_SWITCH,
Issue 01 (2014-04-30)

97
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
Default Value: INVOKE_TRACE_SWITCH:
0,SYS_INFO_UPDATE_FOR_IU_RST:
0,DRNC_DIRECT_DSCR:
0,PTUSER_IDENTIFY_ENH_SWITCH:
0,RNC_SHARE_SWITCH:
1,RNCAP_IMSI_HO_SWITCH:
0,TERMINAL_VERSION_DEBASE_SWITCH:
0,SYS_HO_OUT_CIPHER_SWITCH:
0,SYS_HO_CIPHER_CONFIG:
1,BARRED_CELL_FOR_CSDOMAIN_RST:
0,CR2284R1_SWITCH:
0,CDT_MSG_FULL_TRACE:
0,CR2284R1_COMPATIBLE_SWITCH:
1,COMBINE_OPERATION_DRD_SWITCH:
1,UL_INTER_PROTECT_SWITCH:
0,FAST_DORMANCY_SWITCH:
0,SYS_HO_IN_CIPHER_SWITCH:
0,PTT_EARLY_TRANS_SWITCH_OFF:
0,UPLINK_MDC_ENHENCEMENT_SWITCH:
0,NODEB_PRIVATE_INTERFACE_SWITCH:
0,PTT_SPEC_LI_SWITCH_OFF:
0,RNC_DF_2_URA_PCH_SWITCH:
0,FD_TAC_MATCH_SWITCH:
Issue 01 (2014-04-30)

98
WCDMA RAN
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
10 Parameters
Description
0,NONPTT_L1_FAST_SYNC_SWITCH:
0,URAPCH_LAYERED_PAGING_RT_SWITCH:
0,URAPCH_LAYERED_PAGING_NRT_SWITCH:
0,IDLE_LAYERED_PAGING_NRT_SWITCH:
0,IDLE_LAYERED_PAGING_RT_SWITCH:
0,INTELLIGENT_WIFI_DETECT_AND_SELECTION:
0,INTERRAT_LOAD_REPORT_FOR_LTE_SWITC
H:0,PTUSER_IDENTIFY_SWITCH:0
UserPoli
cySwitc
h
BSC690
0
SET
UQOSA
LGOPA
RA
None
None
Meaning: Whether to perform user group matching.

When this switch is turned on, the RNC determines
which user group a UE belongs to. When this switch is
turned off, the RNC does not perform user group
matching.
GUI Value Range: ON, OFF
Unit: None
Actual Value Range: ON, OFF
Default Value: OFF
UserPoli
cySwitc
h
BSC691
0
SET
UQOSA
LGOPA
RA
None
None
Meaning: Whether to perform user group matching.

When this switch is turned on, the RNC determines
which user group a UE belongs to. When this switch is
turned off, the RNC does not perform user group
matching.
GUI Value Range: ON, OFF
Unit: None
Actual Value Range: ON, OFF
Default Value: OFF
UserMat
chPriorit
y
BSC690
0
SET
UQOSA
LGOPA
RA
None
None
Meaning: User group matching keyword. When this

parameter is set to SPI, the RNC determines which user
group a UE belongs to based on the SPI of the UE. With
the SPI, the RNC can obtain the SPI weight of the UE.
When this parameter is set to Devicegroup, the RNC
determines which user group a UE belongs to based on
the terminal group ID of the UE. With the terminal
group ID, the RNC can obtain the SPI weight of the UE.
GUI Value Range: SPI(Schedule Priority Indication ),
Devicegroup(Devicegroup)
Unit: None
Actual Value Range: SPI, Devicegroup
Default Value: SPI(Schedule Priority Indication )
Issue 01 (2014-04-30)

99
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
UserMat
chPriorit
y
BSC691
0
SET
UQOSA
LGOPA
RA
None
None
Meaning: User group matching keyword. When this

parameter is set to SPI, the RNC determines which user
group a UE belongs to based on the SPI of the UE. With
the SPI, the RNC can obtain the SPI weight of the UE.
When this parameter is set to Devicegroup, the RNC
determines which user group a UE belongs to based on
the terminal group ID of the UE. With the terminal
group ID, the RNC can obtain the SPI weight of the UE.
GUI Value Range: SPI(Schedule Priority Indication ),
Devicegroup(Devicegroup)
Unit: None
Actual Value Range: SPI, Devicegroup
Default Value: SPI(Schedule Priority Indication )
MonDev
Grp0ID
BSC690
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l
Meaning: ID of the terminal group to be monitored by

monitoring group 0. The average throughput of HSDPA
MAC-d flow carried on the BE service queue of users
in this terminal group is included in the counter
VS.HSDPA.BeChThroughput.DevGrp0. The average
throughput of HSUPA MAC-d flow carried on the BE
service queue of users in this terminal group is included
in the counter VS.HSUPA.BeChThroughput.DevGrp0.
Unit: None
Default Value: 0
MonDev
Grp0ID
BSC691
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 0
Issue 01 (2014-04-30)

100
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
MonDev
Grp1ID
BSC690
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 1
MonDev
Grp1ID
BSC691
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 1
MonDev
Grp2ID
BSC690
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 2
Issue 01 (2014-04-30)

101
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
MonDev
Grp2ID
BSC691
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 2
MonDev
Grp3ID
BSC690
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 3
MonDev
Grp3ID
BSC691
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 3
Issue 01 (2014-04-30)

102
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
MonDev
Grp4ID
BSC690
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 4
MonDev
Grp4ID
BSC691
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 4
MonDev
Grp5ID
BSC690
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 5
Issue 01 (2014-04-30)

103
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
MonDev
Grp5ID
BSC691
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 5
MonDev
Grp6ID
BSC690
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 6
MonDev
Grp6ID
BSC691
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 6
Issue 01 (2014-04-30)

104
WCDMA RAN
10 Parameters
Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
MonDev
Grp7ID
BSC690
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 7
MonDev
Grp7ID
BSC691
0
SET
UMON
DEVGR
PID
WRFD150255
Differen
tiated
Service
Based
on
Termina
l

Unit: None
Default Value: 7
Issue 01 (2014-04-30)

105
WCDMA RAN
11 Counters
11
Counters
Table 11-1 Counter description

Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
67194867
VS.HSDPA.Me
anGoldenBeCh
Throughput.TotalBytes
Number of Total
Bytes Sent in
Downlink of
HSDPA MAC-d
Flow of BE
Service for
Golden
Subscriber for
Cell
BSC6900
WRFD-010610
08
Interactive and
Background
Traffic Class on
HSDPA
Number of Total
Bytes Sent in
Downlink of
HSDPA MAC-d
Flow of BE
Service for
Silver
Subscriber for
Cell
BSC6900
Number of Total
Bytes Sent in
Downlink of
HSDPA MAC-d
Flow of BE
Service for
Copper
Subscriber for
Cell
BSC6900
67194869
67194871
VS.HSDPA.Me
anSilverBeChT
hroughput.Total
Bytes
VS.HSDPA.Me
anCopperBeCh
Issue 01 (2014-04-30)
WRFD-020806
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806

Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
106
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
67194873
VS.HSUPA.Gol
denBeMeanChT
hroughput.Total
Bytes
Number of Total
Bytes Received
in Uplink of
HSUPA MAC-d
Flow of BE
Service for
Golden
Subscriber for
Cell
BSC6900
WRFD-010610
08
Interactive and
Background
Traffic Class on
HSDPA
Number of Total
Bytes Received
in Uplink of
HSUPA MAC-d
Flow of BE
Service for
Silver
Subscriber for
Cell
BSC6900
Number of Total
Bytes Received
in Uplink of
HSUPA MAC-d
Flow of BE
Service for
Copper
Subscriber for
Cell
BSC6900
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE
Service for
Golden
Subscriber for
Cell
BSC6900
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE
Service for
Silver
Subscriber for
Cell
BSC6900
67194875
67194889
67204510
67204511
VS.HSUPA.Sil
verBeMeanChT
hroughput.Total
Bytes
VS.HSUPA.Co
pperBeMeanCh
VS.HSDPA.Me
anGoldenBeChThroughput
VS.HSDPA.Me
anSilverBeChThroughput
Issue 01 (2014-04-30)
WRFD-020806
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806

Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
107
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
67204512
VS.HSDPA.Me
anCopperBeChThroughput
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE
Service for
Copper
Subscriber for
Cell
BSC6900
WRFD-010610
08
Interactive and
Background
Traffic Class on
HSDPA
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE
Service for
Golden
Subscriber for
Cell
BSC6900
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE
Service for
Silver
Subscriber for
Cell
BSC6900
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE
Service for
Copper
Subscriber for
Cell
BSC6900
67204513
67204514
67204515
VS.HSUPA.Gol
denBeMeanChThroughput
VS.HSUPA.Sil
verBeMeanChThroughput
VS.HSUPA.Co
pperBeMeanCh
Throughput
WRFD-020806
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
67204829
VS.IuPS.Golde
nBE.Bytes.Tx
Number of UL
Bytes of PS BE
Service for
Golden
Subscriber on
Iu-PS Interface
BSC6900
WRFD-020806
Differentiated
Service Based
on SPI Weight
67204830
VS.IuPS.Silver
BE.Bytes.Tx
Number of UL
Bytes of PS BE
Service for
Silver
Subscriber on
Iu-PS Interface
BSC6900
WRFD-020806
Differentiated
Service Based
on SPI Weight
Issue 01 (2014-04-30)

108
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
67204831
VS.IuPS.Coppe
rBE.Bytes.Tx
Number of UL
Bytes of PS BE
Service for
Copper
Subscriber on
Iu-PS Interface
BSC6900
WRFD-020806
Differentiated
Service Based
on SPI Weight
67204832
VS.IuPS.Golde
nBE.Bytes.Rx
Number of DL
Bytes of PS BE
Service for
Golden
Subscriber on
Iu-PS Interface
BSC6900
WRFD-020806
Differentiated
Service Based
on SPI Weight
67204833
VS.IuPS.Silver
BE.Bytes.Rx
Number of DL
Bytes of PS BE
Service for
Silver
Subscriber on
Iu-PS Interface
BSC6900
WRFD-020806
Differentiated
Service Based
on SPI Weight
67204834
VS.IuPS.Coppe
rBE.Bytes.Rx
Number of DL
Bytes of PS BE
Service for
Copper
Subscriber on
Iu-PS Interface
BSC6900
WRFD-020806
Differentiated
Service Based
on SPI Weight
73444380
VS.HSDPA.Be
ChThroughput.
DevGrp0
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp0 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444381
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp0
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp0 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

109
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444383
VS.HSDPA.Be
ChThroughput.
DevGrp1
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp1 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444384
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp1
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp1 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444386
VS.HSDPA.Be
ChThroughput.
DevGrp2
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp2 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444387
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp2
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp2 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444389
VS.HSDPA.Be
ChThroughput.
DevGrp3
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp3 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

110
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444390
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp3
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp3 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444392
VS.HSDPA.Be
ChThroughput.
DevGrp4
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp4 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444393
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp4
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp4 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444395
VS.HSDPA.Be
ChThroughput.
DevGrp5
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp5 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444396
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp5
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp5 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

111
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444398
VS.HSDPA.Be
ChThroughput.
DevGrp6
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp6 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444399
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp6
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp6 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444401
VS.HSDPA.Be
ChThroughput.
DevGrp7
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp7 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444402
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp7
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp7 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444404
VS.HSUPA.Be
ChThroughput.
DevGrp0
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp0 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

112
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444405
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp0
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp0 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444407
VS.HSUPA.Be
ChThroughput.
DevGrp1
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp1 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444408
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp1
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp1 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444410
VS.HSUPA.Be
ChThroughput.
DevGrp2
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp2 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444411
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp2
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp2 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

113
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444413
VS.HSUPA.Be
ChThroughput.
DevGrp3
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp3 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444414
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp3
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp3 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444416
VS.HSUPA.Be
ChThroughput.
DevGrp4
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp4 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444417
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp4
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp4 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444419
VS.HSUPA.Be
ChThroughput.
DevGrp5
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp5 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

114
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444420
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp5
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp5 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444422
VS.HSUPA.Be
ChThroughput.
DevGrp6
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp6 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444423
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp6
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp6 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444425
VS.HSUPA.Be
ChThroughput.
DevGrp7
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp7 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
73444426
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp7
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp7 UEs
for Cell
BSC6900
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

115
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
67194867
VS.HSDPA.Me
anGoldenBeCh
Number of Total
Bytes Sent in
Downlink of
HSDPA MAC-d
Flow of BE
Service for
Golden
Subscriber for
Cell
BSC6910
WRFD-010610
08
Interactive and
Background
Traffic Class on
HSDPA
Number of Total
Bytes Sent in
Downlink of
HSDPA MAC-d
Flow of BE
Service for
Silver
Subscriber for
Cell
BSC6910
Number of Total
Bytes Sent in
Downlink of
HSDPA MAC-d
Flow of BE
Service for
Copper
Subscriber for
Cell
BSC6910
Number of Total
Bytes Received
in Uplink of
HSUPA MAC-d
Flow of BE
Service for
Golden
Subscriber for
Cell
BSC6910
Number of Total
Bytes Received
in Uplink of
HSUPA MAC-d
Flow of BE
Service for
Silver
Subscriber for
Cell
BSC6910
67194869
67194871
67194873
67194875
VS.HSDPA.Me
anSilverBeChT
hroughput.Total
Bytes
VS.HSDPA.Me
anCopperBeCh
VS.HSUPA.Gol
denBeMeanChT
hroughput.Total
Bytes
VS.HSUPA.Sil
verBeMeanChT
hroughput.Total
Bytes
Issue 01 (2014-04-30)
WRFD-020806
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806

Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
116
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
67194889
VS.HSUPA.Co
pperBeMeanCh
Number of Total
Bytes Received
in Uplink of
HSUPA MAC-d
Flow of BE
Service for
Copper
Subscriber for
Cell
BSC6910
WRFD-010610
08
Interactive and
Background
Traffic Class on
HSDPA
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE
Service for
Golden
Subscriber for
Cell
BSC6910
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE
Service for
Silver
Subscriber for
Cell
BSC6910
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE
Service for
Copper
Subscriber for
Cell
BSC6910
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE
Service for
Golden
Subscriber for
Cell
BSC6910
67204510
67204511
67204512
67204513
VS.HSDPA.Me
anGoldenBeChThroughput
VS.HSDPA.Me
anSilverBeChThroughput
VS.HSDPA.Me
anCopperBeChThroughput
VS.HSUPA.Gol
denBeMeanChThroughput
Issue 01 (2014-04-30)
WRFD-020806
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806

Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
117
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
67204514
VS.HSUPA.Sil
verBeMeanChThroughput
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE
Service for
Silver
Subscriber for
Cell
BSC6910
WRFD-010610
08
Interactive and
Background
Traffic Class on
HSDPA
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE
Service for
Copper
Subscriber for
Cell
BSC6910
67204515
VS.HSUPA.Co
pperBeMeanCh
Throughput
WRFD-020806
Differentiated
Service Based
on SPI Weight
WRFD-010610
08
WRFD-020806
Interactive and
Background
Traffic Class on
HSDPA
Differentiated
Service Based
on SPI Weight
67204829
VS.IuPS.Golde
nBE.Bytes.Tx
Number of UL
Bytes of PS BE
Service for
Golden
Subscriber on
Iu-PS Interface
BSC6910
WRFD-020806
Differentiated
Service Based
on SPI Weight
67204830
VS.IuPS.Silver
BE.Bytes.Tx
Number of UL
Bytes of PS BE
Service for
Silver
Subscriber on
Iu-PS Interface
BSC6910
WRFD-020806
Differentiated
Service Based
on SPI Weight
67204831
VS.IuPS.Coppe
rBE.Bytes.Tx
Number of UL
Bytes of PS BE
Service for
Copper
Subscriber on
Iu-PS Interface
BSC6910
WRFD-020806
Differentiated
Service Based
on SPI Weight
67204832
VS.IuPS.Golde
nBE.Bytes.Rx
Number of DL
Bytes of PS BE
Service for
Golden
Subscriber on
Iu-PS Interface
BSC6910
WRFD-020806
Differentiated
Service Based
on SPI Weight
Issue 01 (2014-04-30)

118
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
67204833
VS.IuPS.Silver
BE.Bytes.Rx
Number of DL
Bytes of PS BE
Service for
Silver
Subscriber on
Iu-PS Interface
BSC6910
WRFD-020806
Differentiated
Service Based
on SPI Weight
67204834
VS.IuPS.Coppe
rBE.Bytes.Rx
Number of DL
Bytes of PS BE
Service for
Copper
Subscriber on
Iu-PS Interface
BSC6910
WRFD-020806
Differentiated
Service Based
on SPI Weight
73444380
VS.HSDPA.Be
ChThroughput.
DevGrp0
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp0 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444381
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp0
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp0 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444383
VS.HSDPA.Be
ChThroughput.
DevGrp1
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp1 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444384
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp1
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp1 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

119
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444386
VS.HSDPA.Be
ChThroughput.
DevGrp2
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp2 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444387
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp2
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp2 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444389
VS.HSDPA.Be
ChThroughput.
DevGrp3
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp3 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444390
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp3
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp3 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444392
VS.HSDPA.Be
ChThroughput.
DevGrp4
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp4 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

120
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444393
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp4
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp4 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444395
VS.HSDPA.Be
ChThroughput.
DevGrp5
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp5 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444396
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp5
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp5 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444398
VS.HSDPA.Be
ChThroughput.
DevGrp6
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp6 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444399
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp6
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp6 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

121
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444401
VS.HSDPA.Be
ChThroughput.
DevGrp7
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp7 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444402
VS.HSDPA.Be
ChThroughput.
TotalBytes.Dev
Grp7
Number of
Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying
BE Services of
DevGrp7 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444404
VS.HSUPA.Be
ChThroughput.
DevGrp0
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp0 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444405
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp0
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp0 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444407
VS.HSUPA.Be
ChThroughput.
DevGrp1
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp1 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

122
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444408
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp1
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp1 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444410
VS.HSUPA.Be
ChThroughput.
DevGrp2
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp2 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444411
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp2
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp2 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444413
VS.HSUPA.Be
ChThroughput.
DevGrp3
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp3 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444414
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp3
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp3 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

123
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444416
VS.HSUPA.Be
ChThroughput.
DevGrp4
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp4 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444417
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp4
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp4 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444419
VS.HSUPA.Be
ChThroughput.
DevGrp5
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp5 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444420
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp5
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp5 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444422
VS.HSUPA.Be
ChThroughput.
DevGrp6
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp6 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

124
WCDMA RAN
11 Counters
Counter ID
Counter Name
Counter
Description
NE
Feature ID
Feature Name
73444423
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp6
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp6 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444425
VS.HSUPA.Be
ChThroughput.
DevGrp7
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying
BE Services of
DevGrp7 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
73444426
VS.HSUPA.Be
ChThroughput.
TotalBytes.Dev
Grp7
Number of
Bytes Received
by HSUPA
MAC-d Flows
Carrying BE
Services of
DevGrp7 UEs
for Cell
BSC6910
WRFD-150255
Differentiated
Service Based
on Terminal
Issue 01 (2014-04-30)

125
WCDMA RAN
12 Glossary
12
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 01 (2014-04-30)

126
WCDMA RAN
13
13 Reference Documents
Reference Documents
1.
3GPP TS 23.107, "Quality of Service (QoS) concept and architecture"
2.
Service Awareness-based QoS Management Feature Parameter Description
3.
Transmission Resource Management Feature Parameter Description
4.
HSDPA Feature Parameter Description
5.
HSUPA Feature Parameter Description
6.
Load Control Feature Parameter Description
7.
Platinum User Prioritizing Feature Parameter Description
8.
License Management Feature Parameter Description
Issue 01 (2014-04-30)

127

Differentiated HSPA Service (RAN16.0 - 01)

Uploaded by

Document Information

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

Differentiated HSPA Service (RAN16.0 - 01)

Uploaded by

Copyright:

Available Formats

WCDMA RAN

Differentiated HSPA Service Feature

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

9.1.2 Required Information................................................................................................................................................24

Huawei Proprietary and Confidential

1 About This Document

About This Document

1.2 Intended Audience

Need to understand the features described herein

Work with Huawei products

1.3 Change History

Huawei Proprietary and Confidential

1 About This Document

Added counters used to

Added information required

RAN 16.0 Draft A (2013-01-20)

Modified the engineering guideline of

Added the following

1.4 Differences Between Base Station Types

l 3900 series base stations

Huawei Proprietary and Confidential

1 About This Document

Huawei Proprietary and Confidential

The CN sends QoS parameters to the RNC.

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

3 Differentiated HSPA Service Based on Service Type

Differentiated HSPA Service Based on

l Low traffic volume

l High traffic volume

Different QoS strategies are used for different types of services:

Huawei Proprietary and Confidential

3 Differentiated HSPA Service Based on Service Type

Huawei Proprietary and Confidential

4 Differentiated HSPA Service Based on User Priority

Differentiated HSPA Service Based on User

Differentiated Service Based on SPI Weight (WRFD-020806 Differentiated Service Based on

Huawei Proprietary and Confidential

4 Differentiated HSPA Service Based on User Priority

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

The following table lists how resources are allocated:

Huawei Proprietary and Confidential

5 Differentiated HSPA Service Based on Terminal

Differentiated HSPA Service Based on

Huawei Proprietary and Confidential

6 Settings for HSPA QoS Parameters

Settings for HSPA QoS Parameters

Huawei Proprietary and Confidential

6 Settings for HSPA QoS Parameters

Figure 6-1 QoS mapping

6.2 Settings for the GBR

Huawei Proprietary and Confidential

6 Settings for HSPA QoS Parameters

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

6.3 Settings for the HBR

6.4 Settings for User Priority

Huawei Proprietary and Confidential