Platinum User Prioritizing (RAN16.0 - Draft A) PDF
Platinum User Prioritizing (RAN16.0 - Draft A) PDF
Platinum User Prioritizing (RAN16.0 - Draft A) PDF
Issue Draft A
Date 2014-01-20
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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview.........................................................................................................................................3
2.1 Introduction....................................................................................................................................................................3
2.2 Benefits...........................................................................................................................................................................3
2.3 Architecture....................................................................................................................................................................3
2.4 Classification of Users....................................................................................................................................................5
8 Network Impact...........................................................................................................................23
9 Engineering Guidelines.............................................................................................................25
9.1 When to Use Platinum User Prioritizing......................................................................................................................25
9.2 Required Information...................................................................................................................................................25
9.3 Planning........................................................................................................................................................................26
9.4 Deployment..................................................................................................................................................................27
9.4.1 Requirements.............................................................................................................................................................27
9.4.2 Data Preparation........................................................................................................................................................27
9.4.3 Activation..................................................................................................................................................................30
9.4.4 MML Command Examples.......................................................................................................................................32
9.4.5 Activation (Using the CME)......................................................................................................................................32
9.4.6 Activation Observation..............................................................................................................................................34
9.4.7 Deactivation...............................................................................................................................................................34
9.4.8 MML Command Examples.......................................................................................................................................35
9.4.9 Deactivation (Using the CME)..................................................................................................................................35
9.5 Performance Monitoring...............................................................................................................................................35
9.5.1 Increase in Connection Success Rates of Platinum Users.........................................................................................36
9.5.2 Voice Quality Improvement of Platinum Users........................................................................................................37
9.5.3 HSPA Throughput Improvement of Platinum Users.................................................................................................37
9.5.4 Increase in Call Drop Rate for Cell...........................................................................................................................37
9.5.5 RLC Retransmission Rate and Average Service Establishment Delay for Cell........................................................37
9.6 Parameter Optimization................................................................................................................................................38
9.7 Troubleshooting............................................................................................................................................................38
10 Parameters...................................................................................................................................39
11 Counters....................................................................................................................................148
12 Glossary.....................................................................................................................................153
13 Reference Documents.............................................................................................................154
1.1 Scope
This document describes the WRFD-150204 Platinum User Prioritizing, including its technical
principles, related features, network impact, and engineering guidelines.
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier version
Draft A (2014-01-20)
Compared with Issue 01 (2013-04-28) of RAN15.0, Draft A (2014-01-20) of RAN16.0 includes
the following changes.
2 Overview
2.1 Introduction
If network congestion occurs during, for example, large gatherings, sports events, or festivals,
it can become difficult for users to access the network. With the Platinum User Prioritizing
feature, the RNC allows platinum users to preferentially access the network during network
congestion. In addition, this feature improves voice quality for platinum users when they are in
weak downlink coverage and increases their High Speed Packet Access (HSPA) throughput.
2.2 Benefits
When network congestion occurs, platinum users have a higher radio resource control (RRC)
connection setup success rate and radio access bearer (RAB) setup success rate than common
users. When the RRC connection setup success rate and RAB setup success rate of common
users are high, this feature does not, however, provide a considerable improvement.
This feature is applied when network access fails due to insufficient resources, including power,
credit, code, and Iub transmission resources. This feature cannot increase the network access
rate if the RRC connection setup and RAB setup failures are caused by other factors, such as
insufficient-capacity licenses.
When downlink coverage is weak, this feature allows NodeBs to increase the maximum
downlink transmit power for platinum users' conversational services, thereby increasing their
mean opinion scores (MOSs).
When there is a great amount of data to transmit and the rate is not limited by the maximum bit
rate (MBR), the data rate ratio of platinum users to common users is equal to the configured SPI
weight ratio. If resources cannot meet the guaranteed bit rates (GBRs) of all users, platinum
users have higher throughput than common users because the configured SPI weight of platinum
users is higher. For details about SPI weight, see Differentiated HSPA Service Feature
Parameter Description.
2.3 Architecture
Figure 2-1 shows the service procedure with Platinum User Prioritizing enabled.
The Platinum User Prioritizing feature works as follows during a service procedure:
1. The RNC identifies platinum users and maintains the IMSI-to-TMSI mapping table.
The operator configures platinum users' IMSIs by running the ADD UPLATINUMIMSI
command. The RNC maintains the IMSI-to-TMSI mapping table for platinum users based
on the RRC Connection Request, Common ID, and Non-Access Stratum (NAS) messages.
Upon receiving an RRC Connection Request message, if the message contains the IMSI
or TMSI, the RNC searches the IMSI-to-TMSI mapping table. If the RNC finds the IMSI
or TMSI in the table, it identifies the user as platinum. If the message contains the P-TMSI,
the RNC identifies the user as non-platinum.
NOTE
During the flow control of RRC connection setup, the RNC raises all services for platinum
users to the same priority as conversational services, which have the highest priority among
all services except emergency calls. During the RRC connection setup phase, platinum
users can unconditionally preempt the resources for non-platinum users. The purpose is to
increase the RRC connection setup success rate of platinum users.
3. The RNC allows platinum users to preferentially establish RAB connections during the
RAB setup phase.
During the RAB setup phase, platinum users can unconditionally preempt the resources for
non-platinum users. The purpose is to increase the RAB setup success rate of platinum
users.
4. The Platinum User Prioritizing feature takes the following measures to improve the service
quality of platinum users during the service processing phase.
l NodeBs increase the maximum downlink transmit power for platinum users' conversational
services by 3 dB. This improves the voice quality of platinum users in weak downlink
coverage areas.
l The initial SPI weight of platinum users is fixed to 100%. If different SPI weights are
configured, platinum users are preferentially scheduled so that they can obtain the required
resources. If the SPI weight of some non-platinum users (for example, gold users) is also
set to 100%, platinum and non-platinum users have the same scheduling priority.
The relationships between platinum users and the gold, silver, and bronze users are as follows:
1. The operator runs the ADD UPLATINUMIMSI command to configure IMSIs for
platinum users. The RNC determines whether users are gold, silver, or bronze users based
on the ARP-to-user-type mapping in RAB Assignment Request messages.
2. The network access of platinum users can be guaranteed during RRC connection setup and
RAB setup, whereas the network access of gold, silver, and bronze users can be guaranteed
only during the RAB setup phase.
3. A user can be a platinum user and at the same time a gold, silver, or bronze user. For such
a user, the initial SPI weight is 100%, and the maximum downlink transmit power for
conversational services is increased by 3 dB. Other processing mechanisms, such as the
GBR and the mapping of SPI and rate range to SPI weight, are the same as those for a gold,
silver, or bronze user.
RAB Setup Platinum users Gold users Silver users Bronze users
Phase
In this document, only two types of users are involved: platinum users and common users.
Common users refer to non-platinum users during the RRC connection setup phase and gold,
silver, and bronze users during the RAB setup phase.
The IMSIs of platinum users must be configured on the RNC so that the RNC can identify them.
To ensure information security of platinum users, only the administrator or a user who has been
granted rights by the administrator can run the commands for configuring the platinum users'
IMSIs. The RNC maintains the IMSI-to-TMSI mapping table of platinum users, identifies
platinum users based on the TMSI or IMSI information in RRC Connection Request, Common
ID, and NAS messages, and allows platinum users to preferentially access the network.
Figure 3-1 and Figure 3-2 show the procedure for identifying and maintaining platinum users
during location update and TMSI reallocation, respectively.
Figure 3-1 Identifying and maintaining platinum users during location update
Figure 3-2 Identifying and maintaining platinum users during TMSI reallocation
According to section 8.5.1 in 3GPP TS 25.331, the priority of reporting the ID of a UE in descending
order is TMSI, P-TMSI, IMSI, and IMEI. That is, a UE preferentially reports its TMSI to the RNC,
regardless of whether the UE initiates a CS or PS service.
3. When the RNC receives a Common ID message from the CN, the RNC identifies the user
as platinum if the IMSI in this message is among the list of platinum users' IMSIs. If the
RRC Connection Request message for the user contains the TMSI, the RNC updates the
TMSI information of the user. Otherwise, the RNC does not update the TMSI information.
4. If the Location Update Accept or TMSI Reallocation Command message for a platinum
user contains the TMSI, the RNC updates the TMSI information of the platinum user.
NOTE
In cross-Iur handover, SRNS relocation, and Direct Signaling Connection Re-establishment (DSCR)
scenarios, the target RNC or DRNC can identify platinum users only when
PTUSER_IDENTIFY_ENH_SWITCH underthe PROCESSSWITCH parameter in the SET
URRCTRLSWITCH command is set to 1.
The identification of platinum users may be incorrect under the following conditions:
l After the IMSIs of platinum users are configured, a platinum user sends the first RRC
Connection Request message.
In such a scenario, the TMSI information has not been saved. The RNC cannot identify the
platinum user during the RRC connection setup phase. However, after receiving a Common
ID message, the RNC can identify this platinum user and maintain the TMSI information.
l After a platinum user leaves the RNC service area, the CN reallocates the TMSI of the
platinum user to a common user under the RNC.
Because the platinum user's TMSI is still contained in the IMSI-to-TMSI mapping table,
the RNC still identifies the user as platinum when receiving the first RRC Connection
Request message. After receiving a Common ID message, the RNC identifies this user as
common and deletes the TMSI from the IMSI-to-TMSI mapping table.
l When a platinum user powers off his or her UE for a long time, the CN reallocates its TMSI
to another user.
In such a scenario, the TMSI of the platinum user is no longer contained in the IMSI-to-
TMSI mapping table. When the platinum user powers on its UE again and sends an RRC
Connection Request message to the RNC, the RNC does not identify this user as platinum.
However, after receiving a Common ID message from the CN, the RNC then identifies this
user as platinum.
The preceding analysis shows that identification of platinum users may be incorrect only when
the RNC receives the first RRC Connection Request message. The incorrect identification is
rectified when the RNC receives a Common ID message from the CN. Therefore, the
identification of platinum users is rarely incorrect.
During the RRC connection setup phase, the RNC allows platinum users to preferentially
establish RRC connections. This increases the RRC connection setup success rate for platinum
users.
During the RRC connection setup phase, both platinum and common users have the same priority
to initiate emergency calls. The RNC takes measures of flow control and preemption during the
RRC connection setup phase to preferentially process service requests from platinum users.
Regardless of whether the preemption is triggered during RRC connection or RAB setup, if a
RAB is to be preempted, the preemption priority depends on the user comprehensive priority.
The higher the user comprehensive priority, the less likely its resources to be preempted. The
user comprehensive priority is ranked, depending on the setting of the PriorityReference
parameter:
l If the PriorityReference parameter is set to ARP, the RNC first considers allocation/
retention priority (ARP) and ranks the user comprehensive priority in descending order of
platinum, gold, silver, and bronze users. For the users having the same ARP, the RNC then
considers TrafficClass and ranks the user comprehensive priority in descending order of
conversational, streaming, interactive, and background services.
l If the PriorityReference parameter is set to TrafficClass, the RNC first considers
TrafficClass and ranks the user comprehensive priority in descending order of
conversational, streaming, interactive, and background services. For the users having the
same TrafficClass, the RNC then considers ARP and ranks the user comprehensive priority
in descending order of platinum, gold, silver, and bronze users.
l The platinum user's RRC connection request can preempt the RABs of all users, except the
RABs for platinum users' conversational services, regardless of the setting of the
Platinum users first preempt RABs and then RRC resources. The user preemption priority of PS
BE RRC connections for platinum users is higher than that for common users.
l If the PriorityReference parameter is set to ARP, the priority of all services for platinum
users is higher than the priority of common users, according to the ranking of the user
comprehensive priority described in section 4.3 RRC Preemption In this case, platinum
users can preempt all RABs (including the RABs for conversational services) of common
users. The RAB with the lowest user comprehensive priority is preempted first. The PS BE
RRC resources occupied by common users can also be preempted. Platinum users first
preempt RABs and then RRC resources.
l If the PriorityReference parameter is set to TrafficClass, preemption is related to the
setting of the PtUserAbsolutePriority parameter.
If the PtUserAbsolutePriority parameter is set to True, the RNC preferentially
processes PS service requests from platinum users. The platinum users can preempt all
RABs (including the RABs for conversational services) of common users. The RAB
with the lowest user comprehensive priority is preempted first. The PS BE RRC
resources occupied by common users can also be preempted. Platinum users first
preempt RABs and then RRC resources.
If the PtUserAbsolutePriority parameter is set to False, platinum users can preempt the
RABs (excluding the RABs for conversational services) of common users. The RAB
with the lowest user comprehensive priority is preempted first. The PS BE RRC
resources occupied by common users can also be preempted. Platinum users first
preempt RABs and then RRC resources.
NOTE
l The RNC allows a platinum user to preempt resources, regardless of whether the platinum user supports
preemption or whether the user to be preempted can be preempted.
For platinum users, the RABs for conversational services and the RABs for combined services
containing conversational services cannot be preempted.
During the RAB setup phase, the RNC allows platinum users to preferentially establish RABs.
l If RAB requests of conversational services for platinum users fail, preemption is triggered.
In this scenario, the RAB preemption of platinum users is the same as the preemption
triggered by RRC connection request failures of conversational services for platinum users.
For details about preemption, see section 4.3.1 Preemption Triggered by RRC
Connection Request Failures with the Cause Value "Originating Conversational
Call" or "Terminating Conversational Call" .
l If RAB requests of non-conversational services for platinum users fail, preemption is as
follows:
If the PriorityReference parameter is set to ARP, the priority of all services for platinum
users is higher than the priority of common users, according to the ranking of the user
comprehensive priority described in section 4.3 RRC Preemption In this case, platinum
users preempt the RABs of common users. If the preemption fails, preemption is then
performed between platinum users. If the user comprehensive priority of a platinum
user is lower than that of the platinum user that triggers the preemption, the RABs for
the former can be preempted. In addition, PS BE RRC resources occupied by common
users can be preempted. Platinum users first preempt RABs and then RRC resources.
If the PriorityReference parameter is set to TrafficClass, preemption is related to the
setting of the PtUserAbsolutePriority parameter.
can be preempted. The PS BE RRC resources occupied by common users can also be
preempted. The priority of PS BE RRC resources is higher than the priority of all RABs.
NOTE
l When a platinum user triggers a preemption, the RNC does not consider whether the platinum user
supports preemption or whether the user to be preempted can be preempted.
l Whether platinum users can preempt resources or the resources for platinum users can be preempted
does not depend on the settings of the DemarcPreemptSwitch and PreemptEnhSwitch parameters. In
addition, preemption cannot be performed on a per operator basis.
l When the MbmsPreemptAlgoSwitch switch is turned off, Multimedia Broadcast Multicast Services
(MBMSs) of platinum users cannot trigger preemption.
l For platinum users, the RABs for conversational services and the RABs for combined services
containing conversational services cannot be preempted.
l Wireless Priority Service (WPS) users can preempt the resources for platinum users' non-conversational
services, whereas platinum users cannot preempt the resources for WPS users. For details about WPS,
see Load Control Feature Parameter Description.
l When the WRFD-010505 Queuing and Pre-Emption feature is enabled and the QueueAlgoSwitch
switch in the SET UQUEUEPREEMPT command is turned on, platinum users can perform queuing.
The queuing priority of platinum users is the same as the preemption priority.
NOTE
For details about the priority of the candidate DRD cells, see section "4.2.1 Inter-Frequency DRD" of the
Directed Retry Decision Feature Parameter Description.
During soft handovers, neither platinum users nor common users can trigger preemption.
The maximum downlink transmit power for platinum users' conversational services is increased
by 3 dB. The RlMaxDlPwr parameter specifies the maximum downlink transmit power.
If a platinum user is using a weak reception UE to process 12.2 kbit/s adaptive multirate (AMR)
services, the maximum downlink transmit power for the platinum user's conversational services
is max(RlMaxDlPwr + 3 dB, SpecUserRlMaxDlPwr).
NOTE
If a weak reception UE is used, the maximum transmit power for the UE is determined by the
SpecUserRlMaxDlPwr parameter. Generally, the value of the SpecUserRlMaxDlPwr parameter is greater
than the value of the RlMaxDlPwr parameter. For details, see Voice Service Experience Improvement for
Weak Reception UEs Feature Parameter Description.
If a platinum user is processing combined services, the maximum downlink transmit power for
the platinum user's conversational services is calculated based on the maximum downlink
transmit power for each service, rate matching gain, and spectrum spreading gain. The maximum
downlink transmit power for the platinum user should meet the power requirements of each
service.
The initial SPI weight of platinum users is set to the highest value, 100%. If the operator wants
to implement service differentiation between platinum users and common users based on the
SPI weight, then the SPI weights of common users must be set to values less than 100%. In
cross-Iur handover scenarios, to implement service differentiation between platinum users and
common users based on the SPI weight under the DRNC, set IubCPPrivateInterfaceSwitch to
ON so that the SRNC will send the SPI weights of platinum users to the DRNC.
The setting and processing mechanism of GBR for platinum users is the same as that for common
users.
For details about WRFD-020107, WRFD-020106, and WRFD-140217, see Load Control
Feature Parameter Description.
For details about WRFD-150233, see Differentiated Service Based on Resource Reservation
Feature Parameter Description.
7 Related Features
l The initial SPI weight of platinum users is set to the highest value, 100%, which cannot be
increased. Therefore, the performance of the following features related to SPI weight
adjustment may be affected: WRFD-020132 Web Browsing Acceleration, WRFD-020133
P2P Downloading Rate Control during Busy Hour, and WRFD-140221 HSDPA
Scheduling Based on UE Location.
l The initial SPI weight of platinum users is set to 100% regardless of whether the Scheduling
Based on UE Location function in the WRFD-01061209 HSUPA HARQ and Fast UL
Scheduling in NodeB feature is enabled.
l When WRFD-021103 Access Class Restriction, WRFD-020114 Domain Specific Access
Control (DSAC), or WRFD-140213 Intelligent Access Class Control is enabled, users of
access classes 0 through 9 are barred by turns and therefore cannot initiate services. If a
platinum user is of access class 0 to 9, user experience will deteriorate. However, during
the period when the access class of the platinum user is allowed to access the network, the
RNC preferentially processes service requests from the platinum user.
8 Network Impact
System Capacity
The maximum downlink transmit power for platinum users' conversational services is 3 dB
higher than that for common users. When platinum users are located in weak coverage areas,
the downlink load of the network increases. As a result, the power available to other services,
such as HSPA services, decreases. This reduces cell throughput.
l If the proportion of platinum users is low in a cell, the impact on network capacity is very
small and can be hardly noticed.
l If the proportion of platinum users is high in a cell, RLC retransmission rates and service
establishment delay increase.
Network Performance
l RRC Connection Setup Success Rate for Cell
After the Platinum User Prioritizing feature is enabled, the RRC connection setup success
rate in a cell may increase. This is because the RRC connection setup success rate of
platinum users increases. However, if platinum users account for only a small proportion
of the total users in a cell, this feature has only a small impact on the RRC connection setup
success rate.
l RAB Setup Success Rate for Cell
After the Platinum User Prioritizing feature is enabled, the RAB setup success rate in a cell
may increase. This is because the RAB setup success rate of platinum users increases.
However, if platinum users account for only a small proportion of the total users in a cell,
this feature has only a small impact on the RAB setup success rate.
l CS call drop rate for Cell
Platinum users preempt the resources of common users, which increases the CS call drop
rate. However, if there are a large number of PS services in the cell, the probability that the
resources of CS services are preempted is low, and therefore the impact of this feature on
the CS call drop rate is small.
If downlink weak coverage is the major reason for call drops, the call drop rate of platinum
users decreases because NodeBs increase the maximum downlink transmit power for
platinum users' conversational services by 3 dB. Therefore, the CS call drop rate in the cell
decreases. If the proportion of platinum users is low and signal quality in the network is
good, the impact of this feature on the CS call drop rate is not obvious.
l PS call drop rate for Cell
When congestion occurs, platinum users preempt the resources of PS services, increasing
the PS call drop rate. The larger the proportion of platinum users and the severer the
congestion, the higher the PS call drop rate.
9 Engineering Guidelines
NodeBs increase the maximum downlink transmit power for platinum users' conversational
services by 3 dB. Therefore, the power consumption of platinum users is higher than that of
common users. This reduces the cell capacity. If the proportion of platinum users is low, the
impact on cell capacity is small. If the proportion of platinum users is high, RLC retransmission
rates and service establishment delay in the cell increase slightly.
l The following counters indicate the RLC retransmission rates for different types of services:
VS.AM.RLC.Rtx.HsdpaTrf.PDU/VS.RLC.AM.Tx.HsdpaTrf.PDU
VS.AM.RLC.Rtx.R99Trf.PDU/VS.RLC.AM.Tx.R99Trf.PDU
VS.AM.RLC.Rtx.HsdpaSig.PDU/VS.AM.RLC.Tx.HsdpaSig.PDU
VS.AM.RLC.Rtx.R99Sig.PDU/VS.AM.RLC.Tx.R99Sig.PDU
l The following counters indicate the average service establishment delay for different types
of services:
VS.AMR.Estab.MeanTime
VS.CS64.Estab.MeanTime
VS.PSR99.Estab.MeanTime
VS.HSDPA.Estab.MeanTime
VS.HSUPA.Estab.MeanTime
9.3 Planning
None
9.4 Deployment
9.4.1 Requirements
l License
The license for the WRFD-150204 Platinum User Prioritizing feature has been activated.
For details about the license control item and how to activate a license, see License
Management Feature Parameter Description.
Preempti PreemptEnhS When this switch is set to on, platinum users can Engineerin
on witch: preempt resources of common users if cell g design
Enhance PREEMPT_ admission fails during procedures such as DRD,
ment ENH_PT_US channel fallback, or rate re-negotiation during
Switch ER_PREEM admission control.
PT_ENH_S
WITCH
To implement differentiated services based on scheduling priorities, the operator also needs to
purchase the WRFD-020806 Differentiated Service Based on SPI Weight feature or some
functions related to SPI weight adjustment. In this case, you need to collect the values of the
following parameters.
Process PROCESSSWI This parameter specifies whether the RNC Default value/
switch TCH: sends NodeB private interface data to the Recommende
NODEB_PRIV NodeB through an Iub protocol message. d value
ATE_INTERF When the license for the WRFD-020806
ACE_SWITC Differentiated Service Based on SPI Weight
H feature is not activated, turn on the
NODEB_PRIVATE_INTERFACE_SWI
TCH switch.
l When this switch is turned on, the RNC
sends NodeB private interface data to the
NodeB through an Iub protocol message.
l When this switch is turned off, the RNC
does not send NodeB private interface data
to the NodeB through an Iub protocol
message.
The setting of this parameter determines
whether the SPI weight of common users
is sent to the NodeB. If the SPI weight of
common users is not sent to the NodeB,
common users and platinum users have the
same SPI weight, 100%. In this case,
differentiated services based on SPI
weight cannot be implemented. Therefore,
you are advised to turn on this switch.
9.4.3 Activation
Step 1 Obtain the IMSIs of platinum users and configure a list. Note that only the administrator or a
user who has been granted rights by the administrator can perform this step.
Run the RNC MML command ADD UPLATINUMIMSI with Platinum IMSI set to the IMSI
of a platinum user. You can configure a maximum of 1000 platinum users.
NOTE
Run the ADD UPLATINUMIMSI command for each platinum user you want to add.
On the LMT, only the users who have the administrator's rights can run the following commands: ADD
UPLATINUMIMSI, LST UPLATINUMIMSI, and RMV UPLATINUMIMSI.
On the U2000, the administrator and the users who have been granted rights can perform IMSI-related
operations for platinum users. For details about user rights of the U2000, see User Management in the
U2000 product documentation.
On the CME, the administrator and the users who have been granted rights by the administrator can perform
IMSI-related operations for platinum users.
In operation logs, the IMSI information in these commands is anonymous.
Step 2 Run the RNC MML command SET UQUEUEPREEMPT to turn on the NodeB CE based
preemption . In this step, select PREEMPT_ENH_NODEB_PREEMPT_CE_SWITCH under
Preemption Enhancement Switch.
Step 3 (Optional) To enable the target RNC or DRNC to identify platinum users in cross-Iur handover,
SRNS relocation, and DSCR scenarios, run the RNC MML command SET
URRCTRLSWITCH with PTUSER_IDENTIFY_ENH_SWITCH under Process switch
parameter set to on. In addition, configure the IMSIs of platinum users on the target RNC and
DRNC by referring to Step 1.
Step 4 (Optional) Determine whether to modify the related parameter values based on operators'
requirements and the parameter setting notes provided in section 9.4.2 Data Preparation. To
modify the parameter values, perform the following sub-steps:
1. Run the RNC MML command SET UUSERPRIORITY to set the Integrate Priority
Configured Reference parameter.
2. If platinum users are required to have the highest preemption priority, run the RNC MML
command SET UQUEUEPREEMPT with Platinum User Prioritizing set to True.
Otherwise, set Platinum User Prioritizing to False.
3. To enable platinum users to preferentially access the first candidate cell for DRD, to
preferentially establish services on E-DCHs/HS-DSCHs during channel fallback, and to
preferentially access the network at a data rate as high as possible during rate re-negotiation,
run the RNC MML command SET UQUEUEPREEMPT with
PREEMPT_ENH_PT_USER_PREEMPT_ENH_SWITCH under the Preemption
Enhancement Switch parameter set to on.
Step 5 (Optional) If the license for the WRFD-020806 Differentiated Service Based on SPI Weight
feature is not activated and the SPI weight for platinum users has been set to 100%, you are
advised to turn on the NODEB_PRIVATE_INTERFACE_SWITCH switch so that
differentiated services can be implemented between platinum users and common users based on
scheduling priorities.
1. Run the RNC MML command SET URRCTRLSWITCH. In this step, select the
NODEB_PRIVATE_INTERFACE_SWITCH switch under the Process switch
parameter.
2. Run the RNC MML command SET UFRC with Default SPI Weight set to a value smaller
than 100.
Step 6 (Optional) If the license for the WRFD-020806 Differentiated Service Based on SPI Weight
feature is activated and the SPI weight for platinum users has been set to 100%, perform the
following sub-step so that differentiated services can be implemented between platinum users
and common users based on scheduling priorities:
Run the RNC MML command SET USPIWEIGHT to with SPI Weight set to a value smaller
than 100.
NOTE
l Whether you need to modify other parameters related to the SPI weight depends on scenario
requirements.
l Modifying the SPI weight does not immediately take effect for online users.
l Whether you need to perform Step 3 or Step 4 above depends on whether the WRFD-020806
Differentiated Service Based on SPI Weight feature has been activated. If this feature has not been
activated, perform Step 3 to configure the SPI weight for common users. If this feature has been
activated, perform Step 4 to configure different SPI weights.
Step 7 (Optional) To enable the DRNC to perform service differentiation between platinum users and
common users based on the SPI weight in cross-Iur handover scenarios, run the RNC MML
command ADD UNRNC or MOD UNRNC with the Iub Private Interface Switch of Control
Plane parameter set to ON.
Step 8 (Optional) When RAN Sharing or MOCN is enabled, run the RNC MML command SET
LICENSE to set the Platinum User Prioritizing-Erlang and Platinum User Prioritizing-
kbps parameters. The Platinum User Prioritizing-Erlang parameter specifies the Erlangs for
the primary or secondary operator. The Platinum User Prioritizing-kbps parameter specifies
the PS throughput for the primary or secondary operator.
Step 9 Run the RNC MML command SET URRCTRLSWITCH. In this step, select
PTUSER_IDENTIFY_SWITCH under the Process switch parameter to enable the Platinum
User Prioritizing feature.
----End
When configuring the Platinum User Prioritizing 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.
Set parameters on the CME according to the operation sequence in Table 9-1. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
----End
NOTE
In operations 5 and 6, set the SPI weights for common users based on scenario requirements.
In operations 5 and 6, modifying the SPI weight does not immediately take effect for online users.
When RAN Sharing/MOCN is enabled, you need to run the RNC MML command SET LICENSE to set
the Platinum User Prioritizing (per Erl) or Platinum User Prioritizing (per kbps) parameter on the
LMT because the CME does not support license operations. The Platinum User Prioritizing (per Erl)
and Platinum User Prioritizing (per kbps) parameters specify the Erlangs and PS throughput,
respectively, that can be used by the primary and secondary operators.
9.4.7 Deactivation
Run the RNC MML command SET URRCTRLSWITCH. In this step, deselect the
PTUSER_IDENTIFY_SWITCH switch under the Process switch parameter to deactivate the
Platinum User Prioritizing feature.
NOTE
Deactivating the Platinum User Prioritizing feature does not immediately take effect for online users.
When configuring the Platinum User Prioritizing 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.
Set parameters on the CME according to the operation sequence in Table 9-2. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
----End
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
NOTE
Deactivating the Platinum User Prioritizing feature does not immediately take effect for online users.
The RRC connection setup and the RAB setup success rates of platinum users are calculated by
using the following formulas:
The RRC connection setup and the RAB setup success rates of common users are calculated by
using the following formulas:
You can obtain the KPIs for common users by subtracting the KPIs for platinum users from
the cell-level KPIs.
The following describes how preemption affects the call drop rate in a cell.
l If preemption is triggered only by platinum users, the increase in call drop rates of CS and
PS services caused by platinum users can be calculated by using the following formulas:
CS services: VS.RAB.AbnormRel.CS.Preempt/(VS.RAB.AbnormRel.CS +
VS.RAB.NormRel.CS)
PS services: VS.RAB.AbnormRel.PS.Preempt/(VS.RAB.AbnormRel.PS +
VS.RAB.NormRel.PS)
l If preemption is also triggered by other factors, you can compare the calculation results of
the preceding two formulas with those calculated in a similar congestion scenario when the
Platinum User Prioritizing feature is not enabled. The comparison results are only for
reference.
l The VS.RAC.Platinum.Preempt.Cong counter indicates the number of preemptions
performed during platinum user admission.
l The following counters indicate the RLC retransmission rates for different types of services:
RLC retransmission rate of HSDPA services = VS.AM.RLC.Rtx.HsdpaTrf.PDU/
VS.RLC.AM.Tx.HsdpaTrf.PDU
RLC retransmission rate of R99 services = VS.AM.RLC.Rtx.R99Trf.PDU/
VS.RLC.AM.Tx.R99Trf.PDU
RLC retransmission rate of HSDPA service signaling = VS.AM.RLC.Rtx.HsdpaSig.PDU/
VS.AM.RLC.Tx.HsdpaSig.PDU
9.7 Troubleshooting
If the RRC connection setup and the RAB setup success rates of platinum users are lower than
those of common users, the possible causes are as follows:
l There are only a small number of platinum users, the platinum users account for only a
small proportion of all users, and the number of service requests initiated by platinum users
is small. Therefore, the values of the RRC connection setup and the RAB setup success
rates fluctuate greatly. Under such conditions, you can use the traffic statistics of a longer
period of time to evaluate performance.
l Resources are insufficient. To determine whether the network access failures of platinum
users are caused by insufficient resources, perform the following steps:
If the RRC connection setup success rate of platinum users is lower than that of common
users, check the value of VS.RRC.FailConnEstab.Cong/VS.RRC.Rej.Sum. If the value
is very small, the Platinum User Prioritizing feature returns a small improvement or
none at all.
If the RAB setup success rate of platinum users is lower than that of common users,
check the values of VS.RAB.FailEstabCS.Cong/VS.RAB.FailEstabCS.RNL and
VS.RAB.FailEstabPS.Cong/VS.RAB.FailEstabPS.RNL. If either value is very small,
the Platinum User Prioritizing feature returns a small improvement or none at all.
10 Parameters
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_V
ERSION_DEB
ASE_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_SWI
TCH. 1: This
switch is turned
on. The RNC
will add
ciphering byte at
GSM
HANDOVER
COMMAND if
the GSM system
do not 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_CIPH
ER_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_CEL
L_FOR_CSDO
MAIN_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_UP
DATE_FOR_I
U_RST is not
checked. 11)
CR2284R1_SW
ITCH. 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_FU
LL_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_CO
MPATIBLE_S
WITCH.
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,R
NC figures that
UE accepts the
CR; R99/R4 UE,
if it only
receives the
START value
from RB
SETUP
COMPLETE,R
NC figures that
UE does not
accept the CR;
when it is not
checked,
whether RNC
accept the CR or
not is according
to
CR2284R1_SW
ITCH. The
relations
between these
two switches
CR2284R1_SW
ITCH and
CR2284R1_CO
MPATIBLE_S
WITCH are as
follows: 1: This
switch is turned
on. RNC is self-
compatible, so
the
CR2284R1_SW
ITCH is invalid;
0: This switch is
turned off. The
CR2284R1_SW
ITCH is valid.
14)
COMBINE_OP
ERATION_DR
D_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_PR
OTECT_SWIT
CH. 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_DORM
ANCY_SWITC
H. 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_C
IPHER_SWITC
H. 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_SWIT
CH_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
_ENHENCEM
ENT_SWITCH.
This switch has
become invalid.
20)
NODEB_PRIV
ATE_INTERF
ACE_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_U
RA_PCH_SWI
TCH. 1: This
switch is turned
on. RNC will
support
transferring Fast
Dormancy UE
from
CELL_DCH or
CELL_FACH to
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_MAT
CH_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_F
AST_SYNC_S
WITCH. 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_LAY
ERED_PAGIN
G_RT_SWITC
H. 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_LAY
ERED_PAGIN
G_NRT_SWIT
CH. Whether the
RNC allows
Layered Paging
in URA_PCH
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
in the LAC or
RAC area. 28)
IDLE_LAYER
ED_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_DETEC
T_AND_SELE
CTION.
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_L
OAD_REPORT
_FOR_LTE_S
WITCH.
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_IDEN
TIFY_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_V
ERSION_DEB
ASE_SWITCH,
CR2284R1_SW
ITCH,
CR2284R1_CO
MPATIBLE_S
WITCH,
COMBINE_OP
ERATION_DR
D_SWITCH
and
UPLINK_MDC
_ENHENCEM
ENT_SWITCH
bit field value
under the
PROCESSSWI
TCH parameter
will be deleted.
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. Instead,
the function of
RNC_SHARE_
SWITCH will
be controlled by
the
RncShareSwitc
h parameter in
the SET
UCTRLPLNSH
AREPARA
command.
GUI Value
Range:INVOK
E_TRACE_SW
ITCH,
SYS_INFO_UP
DATE_FOR_I
U_RST,
DRNC_DIREC
T_DSCR,
PTUSER_IDEN
TIFY_ENH_S
WITCH,
RNC_SHARE_
SWITCH,
RNCAP_IMSI_
HO_SWITCH,
TERMINAL_V
ERSION_DEB
ASE_SWITCH,
SYS_HO_OUT
_CIPHER_SWI
TCH,
SYS_HO_CIPH
ER_CONFIG,
BARRED_CEL
L_FOR_CSDO
MAIN_RST,
CR2284R1_SW
ITCH,
CDT_MSG_FU
LL_TRACE,
CR2284R1_CO
MPATIBLE_S
WITCH,
COMBINE_OP
ERATION_DR
D_SWITCH,
UL_INTER_PR
OTECT_SWIT
CH,
FAST_DORM
ANCY_SWITC
H,
SYS_HO_IN_C
IPHER_SWITC
H,
PTT_EARLY_
TRANS_SWIT
CH_OFF,
UPLINK_MDC
_ENHENCEM
ENT_SWITCH,
NODEB_PRIV
ATE_INTERF
ACE_SWITCH,
PTT_SPEC_LI_
SWITCH_OFF,
RNC_DF_2_U
RA_PCH_SWI
TCH,
FD_TAC_MAT
CH_SWITCH,
NONPTT_L1_F
AST_SYNC_S
WITCH,
URAPCH_LAY
ERED_PAGIN
G_RT_SWITC
H,
URAPCH_LAY
ERED_PAGIN
G_NRT_SWIT
CH,
IDLE_LAYER
ED_PAGING_
NRT_SWITCH,
IDLE_LAYER
ED_PAGING_
RT_SWITCH,
INTELLIGENT
_WIFI_DETEC
T_AND_SELE
CTION,
INTERRAT_L
OAD_REPORT
_FOR_LTE_S
WITCH,
PTUSER_IDEN
TIFY_SWITCH
Unit:None
Actual Value
Range:INVOK
E_TRACE_SW
ITCH,
SYS_INFO_UP
DATE_FOR_I
U_RST,
DRNC_DIREC
T_DSCR,
PTUSER_IDEN
TIFY_ENH_S
WITCH,
RNC_SHARE_
SWITCH,
RNCAP_IMSI_
HO_SWITCH,
TERMINAL_V
ERSION_DEB
ASE_SWITCH,
SYS_HO_OUT
_CIPHER_SWI
TCH,
SYS_HO_CIPH
ER_CONFIG,
BARRED_CEL
L_FOR_CSDO
MAIN_RST,
CR2284R1_SW
ITCH,
CDT_MSG_FU
LL_TRACE,
CR2284R1_CO
MPATIBLE_S
WITCH,
COMBINE_OP
ERATION_DR
D_SWITCH,
UL_INTER_PR
OTECT_SWIT
CH,
FAST_DORM
ANCY_SWITC
H,
SYS_HO_IN_C
IPHER_SWITC
H,
PTT_EARLY_
TRANS_SWIT
CH_OFF,
UPLINK_MDC
_ENHENCEM
ENT_SWITCH,
NODEB_PRIV
ATE_INTERF
ACE_SWITCH,
PTT_SPEC_LI_
SWITCH_OFF,
RNC_DF_2_U
RA_PCH_SWI
TCH,
FD_TAC_MAT
CH_SWITCH,
NONPTT_L1_F
AST_SYNC_S
WITCH,
URAPCH_LAY
ERED_PAGIN
G_RT_SWITC
H,
URAPCH_LAY
ERED_PAGIN
G_NRT_SWIT
CH,
IDLE_LAYER
ED_PAGING_
NRT_SWITCH,
IDLE_LAYER
ED_PAGING_
RT_SWITCH,
INTELLIGENT
_WIFI_DETEC
T_AND_SELE
CTION,
INTERRAT_L
OAD_REPORT
_FOR_LTE_S
WITCH,
PTUSER_IDEN
TIFY_SWITCH
Default
Value:INVOKE
_TRACE_SWI
TCH:
0,SYS_INFO_
UPDATE_FOR
_IU_RST:
0,DRNC_DIRE
CT_DSCR:
0,PTUSER_ID
ENTIFY_ENH_
SWITCH:
0,RNC_SHARE
_SWITCH:
1,RNCAP_IMS
I_HO_SWITCH
:
0,TERMINAL_
VERSION_DE
BASE_SWITC
H:
0,SYS_HO_OU
T_CIPHER_S
WITCH:
0,SYS_HO_CIP
HER_CONFIG:
1,BARRED_CE
LL_FOR_CSD
OMAIN_RST:
0,CR2284R1_S
WITCH:
0,CDT_MSG_F
ULL_TRACE:
0,CR2284R1_C
OMPATIBLE_
SWITCH:
1,COMBINE_O
PERATION_D
RD_SWITCH:
1,UL_INTER_P
ROTECT_SWI
TCH:
1,FAST_DOR
MANCY_SWI
TCH:
0,SYS_HO_IN_
CIPHER_SWIT
CH:
0,PTT_EARLY
_TRANS_SWI
TCH_OFF:
0,UPLINK_MD
C_ENHENCE
MENT_SWITC
H:
0,NODEB_PRI
VATE_INTER
FACE_SWITC
H:
0,PTT_SPEC_L
I_SWITCH_OF
F:
0,RNC_DF_2_
URA_PCH_SW
ITCH:
0,FD_TAC_M
ATCH_SWITC
H:
0,NONPTT_L1
_FAST_SYNC_
SWITCH:
0,URAPCH_L
AYERED_PAG
ING_RT_SWIT
CH:
0,URAPCH_L
AYERED_PAG
ING_NRT_SWI
TCH:
0,IDLE_LAYE
RED_PAGING
_NRT_SWITC
H:
0,IDLE_LAYE
RED_PAGING
_RT_SWITCH:
0,INTELLIGE
NT_WIFI_DET
ECT_AND_SE
LECTION:
0,INTERRAT_
LOAD_REPOR
T_FOR_LTE_S
WITCH:
0,PTUSER_ID
ENTIFY_SWIT
CH:0
Iu transmission
failure occurs. 3)
DRNC_DIREC
T_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_IDEN
TIFY_ENH_S
WITCH
(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
information at
that message. 9)
SYS_HO_CIPH
ER_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_CEL
L_FOR_CSDO
MAIN_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_UP
DATE_FOR_I
U_RST is not
checked. 11)
CR2284R1_SW
ITCH. 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_FU
LL_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_CO
MPATIBLE_S
WITCH.
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,R
NC figures that
UE accepts the
CR; R99/R4 UE,
if it only
receives the
START value
from RB
SETUP
COMPLETE,R
NC figures that
UE does not
accept the CR;
when it is not
checked,
whether RNC
accept the CR or
not is according
to
CR2284R1_SW
ITCH. The
relations
between these
two switches
CR2284R1_SW
ITCH and
CR2284R1_CO
MPATIBLE_S
WITCH are as
follows: 1: This
switch is turned
on. RNC is self-
compatible, so
the
CR2284R1_SW
ITCH is invalid;
0: This switch is
turned off. The
CR2284R1_SW
ITCH is valid.
14)
COMBINE_OP
ERATION_DR
D_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_PR
OTECT_SWIT
CH. 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_DORM
ANCY_SWITC
H. 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_C
IPHER_SWITC
H. 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_SWIT
CH_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
_ENHENCEM
ENT_SWITCH.
This switch has
become invalid.
20)
NODEB_PRIV
ATE_INTERF
ACE_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_U
RA_PCH_SWI
TCH. 1: This
switch is turned
on. RNC will
support
transferring Fast
Dormancy UE
from
CELL_DCH or
CELL_FACH to
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_MAT
CH_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_F
AST_SYNC_S
WITCH. 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
This switch is
turned off. The
RNC directly
pages the UE in
the entire URA.
26)
URAPCH_LAY
ERED_PAGIN
G_NRT_SWIT
CH. Whether the
RNC allows
Layered Paging
in URA_PCH
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_LAYER
ED_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
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_LAYER
ED_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_DETEC
T_AND_SELE
CTION.
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_L
OAD_REPORT
_FOR_LTE_S
WITCH.
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_IDEN
TIFY_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_V
ERSION_DEB
ASE_SWITCH,
CR2284R1_SW
ITCH,
CR2284R1_CO
MPATIBLE_S
WITCH,
COMBINE_OP
ERATION_DR
D_SWITCH
and
UPLINK_MDC
_ENHENCEM
ENT_SWITCH
bit field value
under the
PROCESSSWI
TCH parameter
will be deleted.
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. Instead,
the function of
RNC_SHARE_
SWITCH will
be controlled by
the
RncShareSwitc
h parameter in
the SET
UCTRLPLNSH
AREPARA
command.
GUI Value
Range:INVOK
E_TRACE_SW
ITCH,
SYS_INFO_UP
DATE_FOR_I
U_RST,
DRNC_DIREC
T_DSCR,
PTUSER_IDEN
TIFY_ENH_S
WITCH,
RNC_SHARE_
SWITCH,
RNCAP_IMSI_
HO_SWITCH,
TERMINAL_V
ERSION_DEB
ASE_SWITCH,
SYS_HO_OUT
_CIPHER_SWI
TCH,
SYS_HO_CIPH
ER_CONFIG,
BARRED_CEL
L_FOR_CSDO
MAIN_RST,
CR2284R1_SW
ITCH,
CDT_MSG_FU
LL_TRACE,
CR2284R1_CO
MPATIBLE_S
WITCH,
COMBINE_OP
ERATION_DR
D_SWITCH,
UL_INTER_PR
OTECT_SWIT
CH,
FAST_DORM
ANCY_SWITC
H,
SYS_HO_IN_C
IPHER_SWITC
H,
PTT_EARLY_
TRANS_SWIT
CH_OFF,
UPLINK_MDC
_ENHENCEM
ENT_SWITCH,
NODEB_PRIV
ATE_INTERF
ACE_SWITCH,
PTT_SPEC_LI_
SWITCH_OFF,
RNC_DF_2_U
RA_PCH_SWI
TCH,
FD_TAC_MAT
CH_SWITCH,
NONPTT_L1_F
AST_SYNC_S
WITCH,
URAPCH_LAY
ERED_PAGIN
G_RT_SWITC
H,
URAPCH_LAY
ERED_PAGIN
G_NRT_SWIT
CH,
IDLE_LAYER
ED_PAGING_
NRT_SWITCH,
IDLE_LAYER
ED_PAGING_
RT_SWITCH,
INTELLIGENT
_WIFI_DETEC
T_AND_SELE
CTION,
INTERRAT_L
OAD_REPORT
_FOR_LTE_S
WITCH,
PTUSER_IDEN
TIFY_SWITCH
Unit:None
Actual Value
Range:INVOK
E_TRACE_SW
ITCH,
SYS_INFO_UP
DATE_FOR_I
U_RST,
DRNC_DIREC
T_DSCR,
PTUSER_IDEN
TIFY_ENH_S
WITCH,
RNC_SHARE_
SWITCH,
RNCAP_IMSI_
HO_SWITCH,
TERMINAL_V
ERSION_DEB
ASE_SWITCH,
SYS_HO_OUT
_CIPHER_SWI
TCH,
SYS_HO_CIPH
ER_CONFIG,
BARRED_CEL
L_FOR_CSDO
MAIN_RST,
CR2284R1_SW
ITCH,
CDT_MSG_FU
LL_TRACE,
CR2284R1_CO
MPATIBLE_S
WITCH,
COMBINE_OP
ERATION_DR
D_SWITCH,
UL_INTER_PR
OTECT_SWIT
CH,
FAST_DORM
ANCY_SWITC
H,
SYS_HO_IN_C
IPHER_SWITC
H,
PTT_EARLY_
TRANS_SWIT
CH_OFF,
UPLINK_MDC
_ENHENCEM
ENT_SWITCH,
NODEB_PRIV
ATE_INTERF
ACE_SWITCH,
PTT_SPEC_LI_
SWITCH_OFF,
RNC_DF_2_U
RA_PCH_SWI
TCH,
FD_TAC_MAT
CH_SWITCH,
NONPTT_L1_F
AST_SYNC_S
WITCH,
URAPCH_LAY
ERED_PAGIN
G_RT_SWITC
H,
URAPCH_LAY
ERED_PAGIN
G_NRT_SWIT
CH,
IDLE_LAYER
ED_PAGING_
NRT_SWITCH,
IDLE_LAYER
ED_PAGING_
RT_SWITCH,
INTELLIGENT
_WIFI_DETEC
T_AND_SELE
CTION,
INTERRAT_L
OAD_REPORT
_FOR_LTE_S
WITCH,
PTUSER_IDEN
TIFY_SWITCH
Default
Value:INVOKE
_TRACE_SWI
TCH:
0,SYS_INFO_
UPDATE_FOR
_IU_RST:
0,DRNC_DIRE
CT_DSCR:
0,PTUSER_ID
ENTIFY_ENH_
SWITCH:
0,RNC_SHARE
_SWITCH:
1,RNCAP_IMS
I_HO_SWITCH
:
0,TERMINAL_
VERSION_DE
BASE_SWITC
H:
0,SYS_HO_OU
T_CIPHER_S
WITCH:
0,SYS_HO_CIP
HER_CONFIG:
1,BARRED_CE
LL_FOR_CSD
OMAIN_RST:
0,CR2284R1_S
WITCH:
0,CDT_MSG_F
ULL_TRACE:
0,CR2284R1_C
OMPATIBLE_
SWITCH:
1,COMBINE_O
PERATION_D
RD_SWITCH:
1,UL_INTER_P
ROTECT_SWI
TCH:
1,FAST_DOR
MANCY_SWI
TCH:
0,SYS_HO_IN_
CIPHER_SWIT
CH:
0,PTT_EARLY
_TRANS_SWI
TCH_OFF:
0,UPLINK_MD
C_ENHENCE
MENT_SWITC
H:
0,NODEB_PRI
VATE_INTER
FACE_SWITC
H:
0,PTT_SPEC_L
I_SWITCH_OF
F:
0,RNC_DF_2_
URA_PCH_SW
ITCH:
0,FD_TAC_M
ATCH_SWITC
H:
0,NONPTT_L1
_FAST_SYNC_
SWITCH:
0,URAPCH_L
AYERED_PAG
ING_RT_SWIT
CH:
0,URAPCH_L
AYERED_PAG
ING_NRT_SWI
TCH:
0,IDLE_LAYE
RED_PAGING
_NRT_SWITC
H:
0,IDLE_LAYE
RED_PAGING
_RT_SWITCH:
0,INTELLIGE
NT_WIFI_DET
ECT_AND_SE
LECTION:
0,INTERRAT_
LOAD_REPOR
T_FOR_LTE_S
WITCH:
0,PTUSER_ID
ENTIFY_SWIT
CH:0
services when
cell resources
are
insufficient.Wh
en this switch is
turned on, CS
services
preempt
resources
occupied by PS
services to
access the cell, if
CS access
requests fail due
to insufficient
cell
resources.When
this switch is
turned off, CS
access requests
cannot initiate a
preemption for
resources
occupied by PS
services. 3.
PREEMPT_EN
H_CPU_HIGH
LOAD_CTRL_
SWITCH:
Whether
preemption is
allowed when
the CPU load is
high. When this
switch is turned
on, a user checks
the CPU load
when attempting
to preempt other
users' resources
due to
insufficient cell
resources and
cannot preempt
other users'
resources when
the CPU usage is
higher than
HLOAD_CTRL
_SWITCH:1
services when
cell resources
are
insufficient.Wh
en this switch is
turned on, CS
services
preempt
resources
occupied by PS
services to
access the cell, if
CS access
requests fail due
to insufficient
cell
resources.When
this switch is
turned off, CS
access requests
cannot initiate a
preemption for
resources
occupied by PS
services. 3.
PREEMPT_EN
H_CPU_HIGH
LOAD_CTRL_
SWITCH:
Whether
preemption is
allowed when
the CPU load is
high. When this
switch is turned
on, a user checks
the CPU load
when attempting
to preempt other
users' resources
due to
insufficient cell
resources and
cannot preempt
other users'
resources when
the CPU usage is
higher than
HLOAD_CTRL
_SWITCH:1
Default
Value:ARP
Default
Value:ARP
Switch 8),
RSVDBIT9
(Reserved
Switch 9),
RSVDBIT10
(Reserved
Switch 10),
RSVDBIT11
(Reserved
Switch 11),
RSVDBIT12
(Reserved
Switch 12),
RSVDBIT13
(Reserved
Switch 13),
RSVDBIT14
(Reserved
Switch 14),
RSVDBIT15
(Reserved
Switch 15),
RSVDBIT16
(Reserved
Switch 16)
Unit:None
Actual Value
Range:RSVDBI
T1, RSVDBIT2,
RSVDBIT3,
RSVDBIT4,
RSVDBIT5,
RSVDBIT6,
RSVDBIT7,
RSVDBIT8,
RSVDBIT9,
RSVDBIT10,
RSVDBIT11,
RSVDBIT12,
RSVDBIT13,
RSVDBIT14,
RSVDBIT15,
RSVDBIT16
Default
Value:RSVDBI
T1:OFF,RSVD
BIT2:OFF,RSV
DBIT3:OFF,RS
VDBIT4:OFF,R
SVDBIT5:OFF,
RSVDBIT6:OF
F,RSVDBIT7:O
FF,RSVDBIT8:
OFF,RSVDBIT
9:OFF,RSVDBI
T10:OFF,RSV
DBIT11:OFF,R
SVDBIT12:OF
F,RSVDBIT13:
OFF,RSVDBIT
14:OFF,RSVD
BIT15:OFF,RS
VDBIT16:OFF
Switch 8),
RSVDBIT9
(Reserved
Switch 9),
RSVDBIT10
(Reserved
Switch 10),
RSVDBIT11
(Reserved
Switch 11),
RSVDBIT12
(Reserved
Switch 12),
RSVDBIT13
(Reserved
Switch 13),
RSVDBIT14
(Reserved
Switch 14),
RSVDBIT15
(Reserved
Switch 15),
RSVDBIT16
(Reserved
Switch 16)
Unit:None
Actual Value
Range:RSVDBI
T1, RSVDBIT2,
RSVDBIT3,
RSVDBIT4,
RSVDBIT5,
RSVDBIT6,
RSVDBIT7,
RSVDBIT8,
RSVDBIT9,
RSVDBIT10,
RSVDBIT11,
RSVDBIT12,
RSVDBIT13,
RSVDBIT14,
RSVDBIT15,
RSVDBIT16
Default
Value:RSVDBI
T1:OFF,RSVD
BIT2:OFF,RSV
DBIT3:OFF,RS
VDBIT4:OFF,R
SVDBIT5:OFF,
RSVDBIT6:OF
F,RSVDBIT7:O
FF,RSVDBIT8:
OFF,RSVDBIT
9:OFF,RSVDBI
T10:OFF,RSV
DBIT11:OFF,R
SVDBIT12:OF
F,RSVDBIT13:
OFF,RSVDBIT
14:OFF,RSVD
BIT15:OFF,RS
VDBIT16:OFF
GUI Value
Range:False,
True
Unit:None
Actual Value
Range:False,
True
Default
Value:False
GUI Value
Range:False,
True
Unit:None
Actual Value
Range:False,
True
Default
Value:False
based on the
ratio of available
HS-DSCH
required power
(also called
GBP, indicating
power required
for the
guaranteed bit
rate) between
operators when
the demarcation
function is
enabled. This
switch is set on
the RNC. When
this switch is
turned on and
the cell-level
demarcation
license is valid,
users who fail in
power-based
admission can
preempt the
power resources
of those from the
operator that
occupies the
most excess
power.
GUI Value
Range:ICR_DE
MARC_PREE
MPT_SF(ICR
Demarcation
Preemption
Based on
Availability
Percent),
ICR_DEMARC
_PREEMPT_G
BP(ICR
Demarcation
Preemption
Based on GBP)
Unit:None
Actual Value
Range:ICR_DE
MARC_PREE
MPT_SF,
ICR_DEMARC
_PREEMPT_G
BP
Default
Value:ICR_DE
MARC_PREE
MPT_SF:
0,ICR_DEMAR
C_PREEMPT_
GBP:0
based on the
ratio of available
HS-DSCH
required power
(also called
GBP, indicating
power required
for the
guaranteed bit
rate) between
operators when
the demarcation
function is
enabled. This
switch is set on
the RNC. When
this switch is
turned on and
the cell-level
demarcation
license is valid,
users who fail in
power-based
admission can
preempt the
power resources
of those from the
operator that
occupies the
most excess
power.
GUI Value
Range:ICR_DE
MARC_PREE
MPT_SF(ICR
Demarcation
Preemption
Based on
Availability
Percent),
ICR_DEMARC
_PREEMPT_G
BP(ICR
Demarcation
Preemption
Based on GBP)
Unit:None
Actual Value
Range:ICR_DE
MARC_PREE
MPT_SF,
ICR_DEMARC
_PREEMPT_G
BP
Default
Value:ICR_DE
MARC_PREE
MPT_SF:
0,ICR_DEMAR
C_PREEMPT_
GBP:0
for vacant SF
resources to set
up HS-SCCHs
in scenarios
where SF
resources are
occupied by R99
users. 3.
PREEMPT_EN
H_CSRRC_PR
EEMPT_PS_S
WITCH:
Whether RRC
connection
requests for CS
services
preempt
resources for PS
services when
cell resources
are
insufficient.Wh
en this switch is
turned on, CS
services
preempt
resources
occupied by PS
services to
access the cell, if
RRC connection
requests for CS
services fail due
to insufficient
cell
resources.When
this switch is
turned off, RRC
connection
requests for CS
services cannot
initiate a
preemption for
resources
occupied by PS
services. 4.
PREEMPT_EN
H_CSRAB_PR
EEMPT_PS_S
WITCH:
Whether CS
access requests
preempt
resources for PS
services when
cell resources
are
insufficient.Wh
en this switch is
turned on, CS
services
preempt
resources
occupied by PS
services to
access the cell, if
CS access
requests fail due
to insufficient
cell
resources.When
this switch is
turned off, CS
access requests
cannot initiate a
preemption for
resources
occupied by PS
services. 5.
PREEMPT_EN
H_CPU_HIGH
LOAD_CTRL_
SWITCH:
Whether
preemption is
allowed when
the CPU load is
high. When this
switch is turned
on, a user checks
the CPU load
when attempting
to preempt other
users' resources
due to
insufficient cell
resources and
cannot preempt
other users'
resources when
the CPU usage is
higher than
70%. When this
switch is turned
off, the user does
not consider the
CPU load when
preempting
other users'
resources. 6.
PREEMPT_EN
H_RRC_RAB_
COMBINE_SW
ITCH: Whether
to combine radio
resources of
UEs that have
RRC
connections and
UEs that are
allocated RABs
when the
preempting UE
is allowed to
preempt radio
resources of
multiple UEs. If
this switch is
turned on, the
RNC combines
radio resources
of these two
types of UEs
when
preemption is
required due to
insufficient
radio resources.
If this switch is
turned off, the
preempting UE
can preempt
radio resources
of only UEs that
have RRC
connections or
UEs that have
been allocated
RABs. 7.
PREEMPT_EN
H_PT_USER_P
REEMPT_ENH
_SWITCH:
Whether to
support the
preemption
enhancement
function for
platinum users.
When this
switch is set to
on, platinum
users can
preempt
resources of
other users if cell
admission fails
during the DRD,
channel
fallback, or rate
re-negotiation
during
admission
control
procedure.
When this
switch is set to
on, platinum
users perform
the same actions
as common
users. That is,
DRD, channel
fallback, rate re-
negotiation
during
admission
control, and
preemption are
performed in
sequence. 8.
PREEMPT_EN
H_DRNC_CS_
RAB_PREEMP
T_SWITCH:
Whether to
trigger the
preemption
function during
a CS RAB setup
under the
DRNC. When
this switch is set
to on,
preemption is
triggered during
a CS RAB setup
under the
DRNC. When
this switch is set
to off,
preemption is
not triggered
during a CS
RAB setup
under the
DRNC.
GUI Value
Range:PREEM
PT_ENH_NOD
EB_PREEMPT
_CE_SWITCH,
PREEMPT_EN
H_HSSCCH_P
REEMPT_SF_S
WITCH,
PREEMPT_EN
H_CSRRC_PR
EEMPT_PS_S
WITCH,
PREEMPT_EN
H_CSRAB_PR
EEMPT_PS_S
WITCH,
PREEMPT_EN
H_CPU_HIGH
LOAD_CTRL_
SWITCH,
PREEMPT_EN
H_RRC_RAB_
COMBINE_SW
ITCH,
PREEMPT_EN
H_PT_USER_P
REEMPT_ENH
_SWITCH,
PREEMPT_EN
H_DRNC_CS_
RAB_PREEMP
T_SWITCH
Unit:None
Actual Value
Range:PREEM
PT_ENH_NOD
EB_PREEMPT
_CE_SWITCH,
PREEMPT_EN
H_HSSCCH_P
REEMPT_SF_S
WITCH,
PREEMPT_EN
H_CSRRC_PR
EEMPT_PS_S
WITCH,
PREEMPT_EN
H_CSRAB_PR
EEMPT_PS_S
WITCH,
PREEMPT_EN
H_CPU_HIGH
LOAD_CTRL_
SWITCH,
PREEMPT_EN
H_RRC_RAB_
COMBINE_SW
ITCH,
PREEMPT_EN
H_PT_USER_P
REEMPT_ENH
_SWITCH,
PREEMPT_EN
H_DRNC_CS_
RAB_PREEMP
T_SWITCH
Default
Value:PREEMP
T_ENH_NODE
B_PREEMPT_
CE_SWITCH:
0,PREEMPT_E
NH_HSSCCH_
PREEMPT_SF_
SWITCH:
1,PREEMPT_E
NH_CSRRC_P
REEMPT_PS_S
WITCH:
0,PREEMPT_E
NH_CSRAB_P
REEMPT_PS_S
WITCH:
0,PREEMPT_E
NH_CPU_HIG
HLOAD_CTRL
_SWITCH:
1,PREEMPT_E
NH_RRC_RAB
_COMBINE_S
WITCH:
1,PREEMPT_E
NH_PT_USER
_PREEMPT_E
NH_SWITCH:
0,PREEMPT_E
NH_DRNC_CS
_RAB_PREEM
PT_SWITCH:0
for vacant SF
resources to set
up HS-SCCHs
in scenarios
where SF
resources are
occupied by R99
users. 3.
PREEMPT_EN
H_CSRRC_PR
EEMPT_PS_S
WITCH:
Whether RRC
connection
requests for CS
services
preempt
resources for PS
services when
cell resources
are
insufficient.Wh
en this switch is
turned on, CS
services
preempt
resources
occupied by PS
services to
access the cell, if
RRC connection
requests for CS
services fail due
to insufficient
cell
resources.When
this switch is
turned off, RRC
connection
requests for CS
services cannot
initiate a
preemption for
resources
occupied by PS
services. 4.
PREEMPT_EN
H_CSRAB_PR
EEMPT_PS_S
WITCH:
Whether CS
access requests
preempt
resources for PS
services when
cell resources
are
insufficient.Wh
en this switch is
turned on, CS
services
preempt
resources
occupied by PS
services to
access the cell, if
CS access
requests fail due
to insufficient
cell
resources.When
this switch is
turned off, CS
access requests
cannot initiate a
preemption for
resources
occupied by PS
services. 5.
PREEMPT_EN
H_CPU_HIGH
LOAD_CTRL_
SWITCH:
Whether
preemption is
allowed when
the CPU load is
high. When this
switch is turned
on, a user checks
the CPU load
when attempting
to preempt other
users' resources
due to
insufficient cell
resources and
cannot preempt
other users'
resources when
the CPU usage is
higher than
70%. When this
switch is turned
off, the user does
not consider the
CPU load when
preempting
other users'
resources. 6.
PREEMPT_EN
H_RRC_RAB_
COMBINE_SW
ITCH: Whether
to combine radio
resources of
UEs that have
RRC
connections and
UEs that are
allocated RABs
when the
preempting UE
is allowed to
preempt radio
resources of
multiple UEs. If
this switch is
turned on, the
RNC combines
radio resources
of these two
types of UEs
when
preemption is
required due to
insufficient
radio resources.
If this switch is
turned off, the
preempting UE
can preempt
radio resources
of only UEs that
have RRC
connections or
UEs that have
been allocated
RABs. 7.
PREEMPT_EN
H_PT_USER_P
REEMPT_ENH
_SWITCH:
Whether to
support the
preemption
enhancement
function for
platinum users.
When this
switch is set to
on, platinum
users can
preempt
resources of
other users if cell
admission fails
during the DRD,
channel
fallback, or rate
re-negotiation
during
admission
control
procedure.
When this
switch is set to
on, platinum
users perform
the same actions
as common
users. That is,
DRD, channel
fallback, rate re-
negotiation
during
admission
control, and
preemption are
performed in
sequence. 8.
PREEMPT_EN
H_DRNC_CS_
RAB_PREEMP
T_SWITCH:
Whether to
trigger the
preemption
function during
a CS RAB setup
under the
DRNC. When
this switch is set
to on,
preemption is
triggered during
a CS RAB setup
under the
DRNC. When
this switch is set
to off,
preemption is
not triggered
during a CS
RAB setup
under the
DRNC.
GUI Value
Range:PREEM
PT_ENH_NOD
EB_PREEMPT
_CE_SWITCH,
PREEMPT_EN
H_HSSCCH_P
REEMPT_SF_S
WITCH,
PREEMPT_EN
H_CSRRC_PR
EEMPT_PS_S
WITCH,
PREEMPT_EN
H_CSRAB_PR
EEMPT_PS_S
WITCH,
PREEMPT_EN
H_CPU_HIGH
LOAD_CTRL_
SWITCH,
PREEMPT_EN
H_RRC_RAB_
COMBINE_SW
ITCH,
PREEMPT_EN
H_PT_USER_P
REEMPT_ENH
_SWITCH,
PREEMPT_EN
H_DRNC_CS_
RAB_PREEMP
T_SWITCH
Unit:None
Actual Value
Range:PREEM
PT_ENH_NOD
EB_PREEMPT
_CE_SWITCH,
PREEMPT_EN
H_HSSCCH_P
REEMPT_SF_S
WITCH,
PREEMPT_EN
H_CSRRC_PR
EEMPT_PS_S
WITCH,
PREEMPT_EN
H_CSRAB_PR
EEMPT_PS_S
WITCH,
PREEMPT_EN
H_CPU_HIGH
LOAD_CTRL_
SWITCH,
PREEMPT_EN
H_RRC_RAB_
COMBINE_SW
ITCH,
PREEMPT_EN
H_PT_USER_P
REEMPT_ENH
_SWITCH,
PREEMPT_EN
H_DRNC_CS_
RAB_PREEMP
T_SWITCH
Default
Value:PREEMP
T_ENH_NODE
B_PREEMPT_
CE_SWITCH:
0,PREEMPT_E
NH_HSSCCH_
PREEMPT_SF_
SWITCH:
1,PREEMPT_E
NH_CSRRC_P
REEMPT_PS_S
WITCH:
0,PREEMPT_E
NH_CSRAB_P
REEMPT_PS_S
WITCH:
0,PREEMPT_E
NH_CPU_HIG
HLOAD_CTRL
_SWITCH:
1,PREEMPT_E
NH_RRC_RAB
_COMBINE_S
WITCH:
1,PREEMPT_E
NH_PT_USER
_PREEMPT_E
NH_SWITCH:
0,PREEMPT_E
NH_DRNC_CS
_RAB_PREEM
PT_SWITCH:0
11 Counters
12 Glossary
13 Reference Documents
1. 3GPP TS 25.101, "User Equipment (UE) radio transmission and reception (FDD)"
2. 3GPP TS 25.211, "Physical channels and mapping of transport channels onto physical
channels (FDD)"
3. 3GPP TS 25.306, "UE Radio Access capabilities"
4. 3GPP TS 25.308, "UTRA High Speed Downlink Packet Access (HSPDA); Overall
description"
5. 3GPP TS 25.321, "Medium Access Control (MAC) protocol specification"