Issue 02
Date 2015-05-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 Background.....................................................................................................................................................................3
2.2 Introduction....................................................................................................................................................................3
2.3 Benefits...........................................................................................................................................................................3
3 Technical Description...................................................................................................................4
3.1 Introduction....................................................................................................................................................................4
3.2 Principles........................................................................................................................................................................4
3.2.1 Decision Conditions for Different Congestion States.................................................................................................5
3.2.2 Automatic Congestion Relief Actions.......................................................................................................................10
4 Related Features...........................................................................................................................17
5 Network Impact...........................................................................................................................18
6 Engineering Guidelines.............................................................................................................21
6.1 When to Use Automatic Congestion Handler..............................................................................................................21
6.2 Required Information...................................................................................................................................................21
6.3 Network Planning.........................................................................................................................................................30
6.4 Deployment..................................................................................................................................................................30
6.4.1 Requirements.............................................................................................................................................................30
6.4.2 Data Preparation........................................................................................................................................................32
6.4.3 Precautions.................................................................................................................................................................38
6.4.4 Hardware Adjustment................................................................................................................................................38
6.4.5 Activation..................................................................................................................................................................38
6.4.6 Activation Observation..............................................................................................................................................43
6.4.7 Deactivation...............................................................................................................................................................43
6.4.8 Reconfiguration.........................................................................................................................................................44
6.5 Performance Monitoring...............................................................................................................................................45
6.6 Parameter Optimization................................................................................................................................................49
6.7 Troubleshooting............................................................................................................................................................49
7 Parameters.....................................................................................................................................50
8 Counters......................................................................................................................................146
9 Glossary.......................................................................................................................................153
10 Reference Documents.............................................................................................................154
1.1 Scope
This document describes the WRFD-160253 Automatic Congestion Handler feature, including
the working 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
RAN17.1 02 (2015-05-20)
This issue includes the following changes.
Feature Modified the performance monitoring methods. For details, see None
change section 6.5 Performance Monitoring.
Editorial Modified the deployment requirements. For details, see section None
change 6.4.1 Requirements.
RAN17.1 01 (2015-03-25)
This issue does not include any changes.
2 Overview
2.1 Background
Special events, such as festivals, parades, or major demonstrations, often result in unpredictable
network congestion depending on crowd levels and community participation. In this case,
network configuration optimization cannot be performed in advance. With Automatic
Congestion Handler, congestion relief can be performed automatically in these scenarios.
2.2 Introduction
Automatic Congestion Handler monitors network congestion in real time. If network congestion
occurs, this feature automatically performs corresponding congestion relief actions based on the
congestion state. This relieves network congestion.
2.3 Benefits
This feature automatically relieves congestion in scenarios where special events result in
unanticipated crowd levels, thereby reducing the operation and maintenance workload. This
improves system stability and performance.
3 Technical Description
3.1 Introduction
This feature monitors load-related measurement quantities for a cell in real time. If a
measurement quantity or a set of measurement quantities meets certain requirements, the RNC
determines that the cell is congested and performs corresponding congestion relief actions, which
can be implemented by activating existing congestion relief algorithms or adjusting the settings
of existing network configuration parameters.
3.2 Principles
When the automatic congestion control switch (ADAP_CELL_CONGEST_SWITCH under
the AdapAlgoSwitch(BSC6900,BSC6910) parameter) is set to on, the RNC determines the
congestion state of a cell based on measurement quantities such as downlink non-HSPA power
load, actual uplink load, and number of users on the FACH.
After determining the congestion state, the RNC performs corresponding congestion relief
actions to improve the cell performance. Figure 3-1 outlines the mapping between congestion
states and congestion relief actions.
Figure 3-1 Mapping between congestion states and congestion relief actions
NOTE
The preceding figure shows only the working principle of the automatic congestion control algorithm. For
details about how to determine the congestion states in actual conditions, see section 3.2.1 Decision
Conditions for Different Congestion States.
l Downlink power load of a cell: This measurement object includes the downlink non-HSPA
power load. For details about the downlink non-HSPA power load, see Load Measurement
Feature Parameter Description.
l Uplink power load of a cell: This measurement object includes the actual uplink load, uplink
rise over thermal (RoT) or received total wideband power (RTWP) and number of users
on the DCH.
NOTE
If the actual uplink load cannot be obtained, the uplink RoT is used instead. For details about the
actual uplink load, see Load Measurement Feature Parameter Description.
l FACH of a cell: The state of each channel carried over the FACH determines whether the
FACH of a cell is congested.
l Number of users on the FACH: This is determined based on the number of users in the
CELL_FACH state.
Table 3-1 describes the decision conditions for each measurement object.
Normal state
When the number of users on the DCH is greater than or equal to the
normal state threshold for the number of users on the DCH, the number
of users on the DCH enters the normal state.
NOTE
The default value of the normal state threshold for the number of users on the DCH
is 25.
Light-load state
l When the number of users on the DCH is greater than or equal to the
light-load state triggering threshold, the number of users on the DCH
enters the light-load state.
l When the number of users on the DCH is less than or equal to the light-
load state release threshold, the number of users on the DCH exits the
light-load state.
NOTE
The light-load state triggering and release thresholds for the number of users on the
DCH are 20 and 10, respectively.
Normal state
When the downlink non-HSPA power load is greater than or equal to the
normal state threshold for the downlink non-HSPA power load, the
downlink power load of the cell enters the normal state.
NOTE
The default value of the normal state threshold for the downlink non-HSPA power
load is DL_NORMAL_STATE.
Light-load state
When the number of users on the FACH is greater than or equal to the
light-load state threshold for the number of users on the FACH, the
number of users on the FACH enters the light-load state.
NOTE
The default value of the light-load state threshold for the number of users on the
FACH is 5.
All the thresholds in the preceding table are configurable. For details about how to configure
these thresholds, see section 6.4.5 Activation.
NOTE
l CS Preference includes the following functions: CS RAB setup optimization, CS services preempting
PS BE service resources, preemption algorithm, CS RRC preemption, high SPU CPU load preemption.
l FACH Congestion Control includes the following functions: RLC transmission suspension after UL
4A, RLC transmission suspension after DL F2D, P2D in FACH congestion, TVM-based P2D, and F2P
state transition through physical channel reconfiguration.
N300/T300 1 l When the downlink power load of a cell enters the second-level
parameter congestion state or the uplink power load of a cell (actual uplink
optimizatio load) enters the congestion state, the cell-level parameter N300
n (BSC6900,BSC6910) is set to 1, and T300
(BSC6900,BSC6910) is set to D2000.
l When the downlink power load of a cell exits the second-level
congestion state and the uplink power load of a cell (actual
uplink load) exits the congestion state, the cell-level parameter
N300(BSC6900,BSC6910) and T300(BSC6900,BSC6910) are
reset to its original value.
RRC 2 l When the downlink power load of a cell enters the second-level
connection congestion state or the uplink power load of a cell (actual uplink
release load) enters the congestion state, the cell-level parameter
wait time LowRrcConnRejWaitTmr(BSC6900,BSC6910) is set to 15.
parameter l When the downlink power load of a cell exits the second-level
optimizatio congestion state and the uplink power load of a cell (actual
n uplink load) exits the congestion state, the cell-level parameter
LowRrcConnRejWaitTmr(BSC6900,BSC6910) is reset to its
original value.
Inter-RAT 6 l When the downlink power load of a cell enters the second-level
redirection congestion state or the uplink power load of a cell (actual uplink
load) enters the congestion state, the cell-level parameter
ConnectFailRrcRedirSwitch(BSC6900,BSC6910) is set to
Allowed_To_Inter_RAT.
l When the downlink power load of a cell exits the second-level
congestion state and the uplink power load of a cell (actual
uplink load) exits the congestion state, the cell-level parameter
ConnectFailRrcRedirSwitch(BSC6900,BSC6910) is reset to
its original value.
Inter-RAT 7 l When the downlink power load of a cell enters the second-level
DRD congestion state or the uplink power load of a cell (actual uplink
load) enters the congestion state, the cell-level parameter
InterRATDRDSwitch(BSC6900,BSC6910) is set to ON.
l When the downlink power load of a cell exits the second-level
congestion state and the uplink power load of a cell (actual
uplink load) exits the congestion state, the cell-level parameter
InterRATDRDSwitch(BSC6900,BSC6910) is reset to its
original value.
Cell 3 l When the uplink power load of a cell (actual uplink load) enters
HSUPA the congestion state, the MaxUpaUserNumDynAdjFactor
user (BSC6900,BSC6910) parameter is set to 50. This reduces the
number maximum number of HSUPA users in a cell.
parameter l When the uplink power load of a cell (actual uplink load) exits
optimizatio the congestion state, the MaxUpaUserNumDynAdjFactor
n (BSC6900,BSC6910) parameter is reset to its original value.
This increases the maximum number of HSUPA users in a cell.
Uplink 5 l When the uplink power load of a cell (actual uplink load) enters
initial the congestion state, the cell-level parameter UlBeTraffInitBi-
access rate trate(BSC6900,BSC6910) is decreased by one level (for
example, decreased from D64 to D32). This decreases the
uplink initial access rate of R99 users that are processing PS BE
services.
l When the uplink power load of a cell (actual uplink load) exits
the congestion state, the cell-level parameter UlBeTraffInitBi-
trate(BSC6900,BSC6910) is reset to its original value. This
increases the uplink initial access rate of R99 users that are
processing PS BE services.
Downlink 21 l When the downlink power load of a cell enters the first-level
initial congestion state, the cell-level parameterDlBeTraffInitBitrate
access rate (BSC6900,BSC6910) is decreased by one level (for example,
decreased from D64 to D32). This decreases the downlink
initial access rate of R99 users that are processing PS BE
services.
l When the downlink power load of a cell exits the first-level
congestion state, the cell-level parameter DlBeTraffInitBitrate
(BSC6900,BSC6910) is reset to its original value. This
increases the downlink initial access rate of R99 users that are
processing PS BE services.
CS RAB 8 When the uplink power load of a cell (actual uplink load) or
setup downlink power load of a cell enters the normal state, the cell-level
optimizatio parameter CSRABCacOptSwitch(BSC6900,BSC6910) is
n automatically set to ON to enable the CS RAB setup optimization
function.
CS services 11 When the uplink power load of a cell (actual uplink load) or
preempting downlink power load of a cell enters the normal state, the
PS BE PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH under
service the cell-level parameter PreemptEnhSwitch
resources (BSC6900,BSC6910) is automatically set to 1. This enables CS
services to preempt resources occupied by PS services to access
the cell.
NOTE
This function is disabled by default. If you need to use this function, activate
it according to the instructions in 6.4.5 Activation.
Preemption 9 When the uplink power load of a cell (actual uplink load) or
algorithm downlink power load of a cell enters the normal state, the cell-level
parameter PreemptAlgoSwitch(BSC6900,BSC6910) is
automatically set to ON to activate the preemption algorithm.
CS RRC 10 When the uplink power load of a cell (actual uplink load) or
preemption downlink power load of a cell enters the normal state, the
PREEMPT_ENH_CSRRC_PREEMPT_PS_SWITCH under
the cell-level parameter PreemptEnhSwitch
(BSC6900,BSC6910) is automatically set to 1. This enables RRC
connection requests for CS services to preempt resources occupied
by PS services.
High SPU 12 When the uplink power load of a cell (actual uplink load) or
CPU load downlink power load of a cell enters the normal state, the
preemption PREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWITCH
under the cell-level parameter PreemptEnhSwitch
(BSC6900,BSC6910) is automatically set to 0. This enables the
preemption when the SPU CPU load is high.
P2D CS 13 When the uplink power load of a cell (actual uplink load) or
preemption downlink power load of a cell enters the normal state, the cell-level
parameter CsP2DPreemptSwitch(BSC6900,BSC6910) is
automatically set to ON. This enables CS services of a user to
preempt resources occupied by PS BE services during the transition
from CELL_PCH or URA_PCH to CELL_DCH (P2D).
Increasing 14 When the number of users on the FACH in a cell enters the normal
number of state, the FACH_60_USER_SWITCH under the cell-level
UEs on parameter NBMFACHCTRLALGOSWITCH
FACH to (BSC6900,BSC6910) is automatically set to 1. This enables a
60 maximum of 60 UEs to be carried on the FACH.
RLC 18 l When the DTCH carried over the FACH in a cell enters the
transmissio congestion state, the
n PERFENH_TX_INTERRUPT_AFT_TRIG_SWITCH
suspension under the parameter CORRMFACHCTRLALGOSWITCH
after UL (BSC6900,BSC6910) is automatically set to 1. This enables the
4A RNC to suspend the RLC data transmission for a certain period
of time after reporting 4A measurement reports.
l When the DTCH carried over the FACH in a cell exits the
congestion state, the
PERFENH_TX_INTERRUPT_AFT_TRIG_SWITCH
under the parameter CORRMFACHCTRLALGOSWITCH
(BSC6900,BSC6910) is automatically reset to its original
value.
RLC 17 l When the DTCH carried over the FACH in a cell enters the
transmissio congestion state, the
n RNC_F2D_RLC_SUSPEND_SWITCH under the
suspension RRFACHCTRLALGOSWITCH(BSC6900,BSC6910)
after DL parameter is automatically set to 1. This enables the RNC to
F2D suspend the RLC data transmission during F2D state
transitions.
l When the DTCH carried over the FACH in a cell exits the
congestion state, the
RNC_F2D_RLC_SUSPEND_SWITCH under the
RRFACHCTRLALGOSWITCH(BSC6900,BSC6910)
parameter is automatically reset to its original value.
P2D in 16 When the number of users on the FACH enters the normal state,
FACH the P2D_SWITCH under the RRFACHCTRLALGOSWITCH
congestion (BSC6900,BSC6910) parameter is automatically set to 1. This
enables the RNC to switch the user from the CELL_PCH or
URA_PCH state to the CELL_DCH state when the FACH is
congested.
TVM- 19 When the number of users on the FACH enters the light-load state,
based P2D the RNC_TVM_BASED_P2D_SWITCH under the
RRFACHCTRLALGOSWITCH(BSC6900,BSC6910) parameter
is automatically set to 1. This enables the RNC to trigger a P2D
state transition for a user when the RNC receives from the user a
CELL UPDATE message with the Traffic volume indicator IE set
to TRUE or receives from the CN a dynamic traffic volume
measurement value that meets a specified threshold.
F2P state 20 When the number of users on the FACH enters the light-load state,
transition the CMP_F2P_PROCESS_OPTIMIZATION_SWITCH under
through the CORRMFACHCTRLALGOSWITCH(BSC6900,BSC6910)
physical parameter is automatically set to 1. This enables the F2P state
channel transition to be performed through the physical channel
reconfigura reconfiguration procedure.
tion
RxLevMin 22 l When the uplink power load of a cell (RoT) enters the
parameter congestion state, the value of the Qrxlevmin
optimizatio (BSC6900,BSC6910) parameter is automatically increased by
n 5.
l When the uplink power load of a cell (RoT) exits the congestion
state, the value of the Qrxlevmin(BSC6900,BSC6910)
parameter is reset to its original value.
HSDPA 23 When the number of users on the DCH enters the normal state, the
user MaxHsdpaUserNum(BSC6900,BSC6910) parameter is
number automatically set to the larger value between the current value and
restriction 128.
cancellatio NOTE
n The maximum number of HSDPA users allowed in a cell equals the smaller
value between MaxHsdpaUserNum(BSC6900,BSC6910) and the license
capacity.
Cell-level 24 When the number of users on the DCH enters the normal state, the
static CellCallShockSwitch(BSC6900,BSC6910) parameter is
CAPS flow automatically set to ON. This enables the cell-level static CAPS
control flow control function.
NOTE
This function is disabled by default. If you need to use this function, activate
it according to the instructions in 6.4.5 Activation.
Cell-level 25 When the number of users on the DCH enters the normal state, the
dynamic CELLKPITOCAPS(BSC6900,BSC6910) parameter is
CAPS flow automatically set to ON. This enables the cell-level dynamic CAPS
control flow control function.
NOTE
This function is disabled by default. If you need to use this function, activate
it according to the instructions in 6.4.5 Activation.
DPCH 26 l When the number of users on the DCH enters the light-load
pilot power state, the PilotPOOptiSwitch parameter is automatically set to
adjustment ON. This enables the DPCH pilot power adjustment function.
l When the number of users on the DCH exits the light-load state,
the PilotPOOptiSwitch parameter is reset to its original value.
FACH PS 27 l When the FACH DTCH of a cell enters the congestion state,
TRB the TimerPollForFachPsTRB(BSC6900,BSC6910)
polling parameter is automatically set to D500.
timer l When the FACH DTCH of a cell exits the congestion state, the
adjustment TimerPollForFachPsTRB(BSC6900,BSC6910) parameter is
automatically set to D300.
NOTE
This function is disabled by default. If you need to use this function,
activate it according to the instructions in 6.4.5 Activation.
FACH 28 l When the FACH DCCH or FACH CCCH of a cell enters the
SRB congestion state, the TimerPollForFachSRB
polling (BSC6900,BSC6910) parameter is automatically set to D250.
timer l When the FACH DCCH or FACH CCCH of a cell exits the
adjustment congestion state, the TimerPollForFachSRB
(BSC6900,BSC6910) parameter is automatically set to D200.
NOTE
This function is disabled by default. If you need to use this function,
activate it according to the instructions in 6.4.5 Activation.
NOTE
l When this feature is disabled or a function in the preceding table is deactivated, the parameters involved
in this feature or function are reset to their original values.
l If values of parameters related to this feature are manually adjusted after this feature is enabled, the
adjusted values will be overwritten because these values will be automatically adjusted later. Therefore,
do not manually adjust related parameters after this feature is enabled.
4 Related Features
Prerequisite Features
Inter-RAT redirection, inter-RAT DRD, and preemption-related are automatically enabled when
the cell load meets certain requirements (as listed in Table 3-2). These functions depend on the
following features:
Impacted Features
None
5 Network Impact
System Capacity
Network configuration optimization cannot be performed in advance for special events where
unanticipated network congestion often occurs. With Automatic Congestion Handler,
congestion relief can be performed automatically when cells are congested. This improves
system capacity. This feature involves multiple algorithms and functions.
l RxLevMin parameter optimization: This function increases the value of the RxLevMin
parameter when a cell enters the congestion state so that some UEs will not camp on this
cell. This affects the cell capacity but realizes load balancing, without affecting system
capacity.
l HSDPA user number restriction cancellation: This function increases the number of
admitted HSDPA users.
l DPCH pilot power adjustment: When the downlink load is heavy due to heavy traffic, this
function reduces downlink DPCH power consumption by reducing the length and power
offset of the pilot field. Ultimately, system capacity is increased.
In cell congestion scenarios, congestion relief actions help reduce cell load and improve the
efficiency of resource utilization. This feature also helps improve cell capacity when there are
sufficient services.
Network Performance
The impact of each algorithm or function on network performance is as follows:
If CS admission fails before this feature is enabled, the CS access success rate significantly
increases after this feature is enabled.However, the PS call drop rate also increases when PS or
CS preemption occurs.
NOTE
l After this feature is enabled, some of the preceding functions take effect simultaneously and affect
each other.Therefore, the impact of this feature on system capacity and network performance cannot
be quantified.
l After this feature is enabled, the RNC dynamically adjusts parameters and therefore the CPU usage of
the SPU subsystem slightly increases. The increase in the CPU usage is in direct proportion to the
number of cells enabled with this feature on the SPU subsystem. When all the cells on the SPU
subsystem are enabled with this feature, the CPU usage of the SPU subsystem increases by less than
3%.
6 Engineering Guidelines
For details about how to determine whether the network configuration needs to be optimized
and whether a cell is congested, see section 6.2 Required Information
– For the number of users on the FACH, the value of the VS.CellFACHUEs
(BSC6900,BSC6910) counter is greater than 25 or the value of the
VS.CellFACHUEs.MAX(BSC6900,BSC6910) counter is greater than or equal to 30.
l Check the settings of related parameters and determine whether this feature is necessary
based on the congestion relief actions described in 3.2.2 Automatic Congestion Relief
Actions.
For details about how to activate or deactivate a single function, see section 6.4 Deployment.
6.4 Deployment
6.4.1 Requirements
Feature
The prerequisite features for this feature must have been configured before this feature is
activated. For the prerequisite features, see "4 Related Features".
For details about WRFD-02040003 Inter System Redirect and WRFD-02040002 Inter System
Direct Retry features, see Intelligent Access Control Feature Parameter Description.
For details about WRFD-010505 Queuing and Pre-Emption feature, see Directed Retry Decision
Feature Parameter Description.
Hardware
None.
License
For details about how to activate the license, see License Management Feature Parameter
Description.
If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary and
secondary operators according to the value of the "License Allocation for Multiple Operators
parameter".
Method 1: it is recommended that the license allocation proportion of a feature be consistent
with that of the capacity license item "Voice Erlang-Erlang". The licensed values can be set by
running the SET LICENSE command. If the FeatureResAssignMode parameter in this
command is set to AutoAssign, the licensed values are automatically allocated among the
primary and secondary operators. If the FeatureResAssignMode parameter in this command is
set to ManualAssign, you also need to specify the related license parameters to implement
manual license allocation.
Method 2: it is recommended that the license allocation proportion of a feature be consistent
with that of the capacity license item "PS throughput only-kbps". The licensed values can be set
by running the SET LICENSE command. If the FeatureResAssignMode parameter in this
command is set to AutoAssign, the licensed values are automatically allocated among the
primary and secondary operators. If the FeatureResAssignMode parameter in this command is
set to ManualAssign, you also need to specify the related license parameters to implement
manual license allocation.
Other Requirements
None.
AtomRuleID
(BSC6900,BSC6910)
parameter to 15.
l When the congestion
triggering threshold for the
actual uplink load needs to be
adjusted, run the MOD
UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 2.
l When the congestion release
threshold for the actual uplink
load needs to be adjusted, run
the MOD
UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 5.
l When the normal state
threshold for the actual uplink
load needs to be adjusted, run
the MOD
UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 11.
l When the congestion
triggering threshold for the
uplink RoT needs to be
adjusted, run the MOD
UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 16.
l When the congestion release
threshold for the uplink RoT
needs to be adjusted, run the
MOD UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 17.
l When the congestion
triggering threshold for the
uplink RTWP needs to be
adjusted, run the MOD
UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 18.
l When the congestion release
threshold for the uplink RTWP
needs to be adjusted, run the
MOD UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 19.
l When the congestion
triggering threshold for the
number of users on the DCH
needs to be adjusted, run the
MOD UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 3.
l When the congestion release
threshold for the number of
users on the DCH needs to be
adjusted, run the MOD
UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 6.
l When the normal state
threshold for the number of
users on the DCH needs to be
adjusted, run the MOD
UIOPTATOMRULE
command to set the
AtomRuleID
(BSC6900,BSC6910)
parameter to 12.
ThresholdRa See Using MML The thresholds must meet the Network
ngeValue Commands. following conditions: plan
l The second-level congestion
triggering threshold for the
downlink non-HSPA power
load is greater than the second-
level congestion release
threshold for the downlink
non-HSPA power load.
l The first-level congestion
triggering threshold for the
downlink non-HSPA power
load is greater than the first-
level congestion release
threshold for the downlink
non-HSPA power load.
l The congestion triggering
threshold for the actual uplink
load is greater than the
congestion release threshold
for the actual uplink load.
l The congestion triggering
threshold for the uplink RoT is
greater than the congestion
release threshold for the uplink
RoT.
l The congestion triggering
threshold for the uplink RTWP
is greater than the congestion
release threshold for the uplink
RTWP.
l The congestion triggering
threshold for the number of
users on the DCH is greater
than the congestion release
threshold for the number of
users on the DCH.
l The light-load state triggering
threshold for the number of
users on the DCH is greater
than the light-load state release
threshold for the number of
users on the DCH.
6.4.3 Precautions
None
6.4.5 Activation
Configure the second-level congestion thresholds for the downlink non-HSPA power load.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set
AtomRuleID to 1, MeasureObjType to CELL, MeasureObject to
DL_NONH_PWR_STATUS, and ThresholdEnumValue to an appropriate value to adjust
the second-level congestion triggering threshold for the downlink non-HSPA power load.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set
AtomRuleID to 4, MeasureObjType to CELL, MeasureObject to
DL_NONH_PWR_STATUS, and ThresholdEnumValue to an appropriate value to adjust
the second-level congestion release threshold for the downlink non-HSPA power load.
Configure the first-level congestion thresholds for the downlink non-HSPA power load.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set
AtomRuleID to 7, MeasureObjType to CELL, MeasureObject to
DL_NONH_PWR_STATUS, and ThresholdEnumValue to an appropriate value to adjust
the first-level congestion triggering threshold for the downlink non-HSPA power load.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set
AtomRuleID to 8, MeasureObjType to CELL, MeasureObject to
DL_NONH_PWR_STATUS, and ThresholdEnumValue to an appropriate value to adjust
the first-level congestion release threshold for the downlink non-HSPA power load.
Configure the normal state threshold for the downlink non-HSPA power load.
Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set AtomRuleID
to 15, MeasureObjType to CELL, MeasureObject to DL_NONH_PWR_STATUS, and
ThresholdEnumValue to an appropriate value to adjust the normal state threshold for the
downlink non-HSPA power load.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the
AtomRuleID parameter to 2, MeasureObjType to CELL, MeasureObject to
UL_ACTUAL_LOAD, and set the ThresholdRangeValue parameter to adjust the
congestion triggering threshold for the actual uplink load.
l Run the RNC MML command MOD UIOPTATOMRULE.In this substep, set the
AtomRuleID parameter to 5, MeasureObjType to CELL, MeasureObject to
Configure the normal state threshold for the uplink non-HSPA power load.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the
AtomRuleID parameter to 11, MeasureObjType to CELL, MeasureObject to
UL_ACTUAL_LOAD, and set the ThresholdRangeValue parameter to adjust the normal
state threshold for the actual uplink load.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the
AtomRuleID parameter to 12, MeasureObjType to CELL, MeasureObject to
DCH_USER_NUM, and set the ThresholdRangeValue parameter to adjust the normal
state threshold for the number of users on the DCH.
Configure the state thresholds for the number of users on the FACH.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the
AtomRuleID parameter to 13, MeasureObjType to CELL, MeasureObject to
FACH_USER_NUM, and set the ThresholdRangeValue parameter to adjust the normal
state threshold for the number of users on the FACH.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the
AtomRuleID parameter to 14, MeasureObjType to CELL, MeasureObject to
FACH_USER_NUM, and set the ThresholdRangeValue parameter to adjust the light-load
state threshold for the number of users on the FACH.
Configure the light-load state thresholds for the number of users on the DCH.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the
AtomRuleID parameter to 20 and set the ThresholdRangeValue parameter to adjust the
light-load state triggering threshold for the number of users on the DCH.
l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the
AtomRuleID parameter to 21 and set the ThresholdRangeValue parameter to adjust the
light-load state release threshold for the number of users on the DCH.
Step 2 (Optional) Activate or deactivate the functions involved in this feature based on the descriptions
in 3.2.1 Decision Conditions for Different Congestion States and 3.2.2 Automatic
Congestion Relief Actions.
l Run the RNC MML command ACT UIOPTFUNCTION or DEA UIOPTFUNCTION to
activate or deactivate rules of a function. The following table lists the intelligent optimization
function ID of each function.
Inter-RAT redirection 6
Inter-RAT DRD 7
Preemption algorithm 9
CS RRC preemption 10
P2D CS preemption 13
TVM-based P2D 19
NOTE
l All the functions listed in the preceding table except CS services preempting PS BE service resources,
cell-level static CAPS flow control, cell-level dynamic CAPS flow control, FACH PS TRB polling
timer adjustment, and FACH SRB polling timer adjustment are activated by default. You need to
perform this step only when one of these functions needs to be activated or a function needs to be
deactivated after this feature is enabled.
l Check whether related parameter settings are proper when activating the cell-level static CAPS flow
control function. For detailed operations, see section "Cell Static CAPS Control" in Flow Control
Feature Parameter Description.
l When activating the cell-level dynamic CAPS flow control function, run the SET
UNBMPHYPARA command with the FlowCtrlSwitch(BSC6900,BSC6910) parameter set to
HIGH_PRI_RRC_DYN_CAPS_FC_OPT_SWITCH to raise the priority of CS services. For
detailed operations, see section "Cell Dynamic CAPS Control" in Flow Control Feature Parameter
Description.
----End
// (Optional) Configuring the normal state threshold for the downlink non-HSPA
power load
MOD UIOPTATOMRULE: AtomRuleID=15, MeasureObjType=CELL,
MeasureObject=DL_NONH_PWR_STATUS, ThresholdEnumValue=DL_NORMAL_STATE;
MeasureObject=UL_ACTUAL_LOAD, ThresholdRangeValue=70;
MOD UIOPTATOMRULE: AtomRuleID=5, MeasureObjType=CELL,
MeasureObject=UL_ACTUAL_LOAD, ThresholdRangeValue=40;
MOD UIOPTATOMRULE: AtomRuleID=6, MeasureObjType=CELL, MeasureObject=DCH_USER_NUM,
ThresholdRangeValue=25;
MOD UIOPTATOMRULE: AtomRuleID=3, MeasureObjType=CELL, MeasureObject=DCH_USER_NUM,
ThresholdRangeValue=35;
// (Optional) Configuring the normal state threshold for the uplink non-HSPA power
load
MOD UIOPTATOMRULE: AtomRuleID=11, MeasureObjType=CELL,
MeasureObject=UL_ACTUAL_LOAD, ThresholdRangeValue=40;
MOD UIOPTATOMRULE: AtomRuleID=12, MeasureObjType=CELL, MeasureObject=DCH_USER_NUM,
ThresholdRangeValue=25;
// (Optional) Configuring the state thresholds for the number of users on the FACH
MOD UIOPTATOMRULE: AtomRuleID=13, MeasureObjType=CELL,
MeasureObject=FACH_USER_NUM, ThresholdRangeValue=15;
MOD UIOPTATOMRULE: AtomRuleID=14, MeasureObjType=CELL,
MeasureObject=FACH_USER_NUM, ThresholdRangeValue=5;
// (Optional) Configuring the light-load state thresholds for the number of users
on the DCH
MOD UIOPTATOMRULE: AtomRuleID=20, MeasureObjType=CELL, MeasureObject=DCH_USER_NUM,
ThresholdRangeValue=20;
MOD UIOPTATOMRULE: AtomRuleID=21, MeasureObjType=CELL, MeasureObject=DCH_USER_NUM,
ThresholdRangeValue=10;
When configuring the Automatic Congestion Handler 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 6-2. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
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 while
running the wizard to obtain online help.
----End
Step 2 On the displayed SON Log tab page, click Query SON Log. Set Log Category to UMTS
Automatic Congestion Handler log and Event Name to All. In addition, specify Event Source
Object and Time Period as required.
Step 3 Click Synchronize in the bottom right corner of the SON Log tab page.
Step 4 Click Query. If there is a Cell-level Parameter Adjustment record in the specified time period,
this feature has taken effect.
----End
After this feature is activated, operating information about this feature will be recorded in SON
logs.
6.4.7 Deactivation
When configuring the Automatic Congestion Handler 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.
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 while
running the wizard to obtain online help.
----End
6.4.8 Reconfiguration
None
Counter/KPI Description
Counter/KPI Description
l To evaluate the changes in the congestion state of a cell, compare the values of the
VS.CellDCHUEs(BSC6900,BSC6910), VS.MeanTCP.NonHS(BSC6900,BSC6910),
VS.MeanULActualPowerLoad(BSC6900,BSC6910), VS.MeanRTWP
(BSC6900,BSC6910), and VS.CellFACHUEs(BSC6900,BSC6910) counters before and
after this feature is activated.
l When the function of Cell HSUPA user number parameter optimization is enabled in a cell
where the uplink power load is congested, if the value of the VS.HSUPA.UE.Max.Cell
(BSC6900,BSC6910) counter is greater than half the value of the MaxHsupaUserNum
counter before the feature activation, the value of the VS.HSUPA.UE.Mean.Cell
(BSC6900,BSC6910) counter decreases after the feature activation.
l When CS Preference functions such as CS RAB setup optimization and CS services
preempting PS BE service resources are enabled in a congested cell, if CS admission fails
before this feature is activated, the AMR RAB setup success rate and number of CS users
increase after this feature is activated. However, the PS call drop rate also increases when
PS or CS preemption occurs.
l When the maximum number of FACH users is greater than or equal to 30 before this feature
is activated and the function of increasing number of UEs on FACH to 60 is enabled, the
value of the VS.CellFACHUEs(BSC6900,BSC6910) counter increases after the feature
activation.
l After this feature is activated in a congested cell, the cell load decreases and resource usage
increases. In addition, the cell traffic increases when there are sufficient service demands.
The uplink and downlink cell loads are indicated by the VS.MeanRTWP
If the value of the VS.MeanRTWP(BSC6900,BSC6910) counter does not decrease, the reason may be
that the total uplink PS traffic volume (the sum of uplink PS R99 traffic volume over the Iub and the HSUPA
traffic volume) slightly increases.
If the value of the VS.MeanTCP.NonHS(BSC6900,BSC6910) counter does not decrease, the reason may
be that the total downlink PS traffic volume (the sum of downlink PS R99 traffic volume over the Iub
interface and the HSDPA traffic volume) slightly increases.
You are advised to use the data one week before and after feature activation to determine the
feature gain.
6.7 Troubleshooting
None
7 Parameters
TimerPo BSC690 ADD WRFD- Logical Meaning: Timer for the transmitting side of a PS TRB
llForFac 0 UCELL 020900 Channel AM RLC entity to wait for a response from the peer end
hPsTRB FACHC Manage after sending the peer end polling RLC PDUs in the
ONGCT ment CELL_FACH state. This parameter takes effect only
RL when the transmitting side of an AM RLC entity is
MOD configured with the polling function. The transmitting
UCELL side of an AM RLC entity starts this timer after sending
FACHC polling RLC PDUs to the peer end. If the transmitting
ONGCT side does not receive any status report from the peer end
RL after this timer expires, the transmitting side retransmits
polling RLC PDUs and restarts this timer. For details
about this parameter, see 3GPP TS 25.322.
GUI Value Range: D10, D20, D30, D40, D50, D60,
D70, D80, D90, D100, D110, D120, D130, D140,
D150, D160, D170, D180, D190, D200, D210, D220,
D230, D240, D250, D260, D270, D280, D290, D300,
D310, D320, D330, D340, D350, D360, D370, D380,
D390, D400, D410, D420, D430, D440, D450, D460,
D470, D480, D490, D500, D510, D520, D530, D540,
D550, D600, D650, D700, D750, D800, D850, D900,
D950, D1000
Unit: ms
Actual Value Range: 10, 20, 30, 40, 50, 60, 70, 80, 90,
100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 200,
210, 220, 230, 240, 250, 260, 270, 280, 290, 300, 310,
320, 330, 340, 350, 360, 370, 380, 390, 400, 410, 420,
430, 440, 450, 460, 470, 480, 490, 500, 510, 520, 530,
540, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000
Default Value: D300
TimerPo BSC691 ADD WRFD- Logical Meaning: Timer for the transmitting side of a PS TRB
llForFac 0 UCELL 020900 Channel AM RLC entity to wait for a response from the peer end
hPsTRB FACHC Manage after sending the peer end polling RLC PDUs in the
ONGCT ment CELL_FACH state. This parameter takes effect only
RL when the transmitting side of an AM RLC entity is
MOD configured with the polling function. The transmitting
UCELL side of an AM RLC entity starts this timer after sending
FACHC polling RLC PDUs to the peer end. If the transmitting
ONGCT side does not receive any status report from the peer end
RL after this timer expires, the transmitting side retransmits
polling RLC PDUs and restarts this timer. For details
about this parameter, see 3GPP TS 25.322.
GUI Value Range: D10, D20, D30, D40, D50, D60,
D70, D80, D90, D100, D110, D120, D130, D140,
D150, D160, D170, D180, D190, D200, D210, D220,
D230, D240, D250, D260, D270, D280, D290, D300,
D310, D320, D330, D340, D350, D360, D370, D380,
D390, D400, D410, D420, D430, D440, D450, D460,
D470, D480, D490, D500, D510, D520, D530, D540,
D550, D600, D650, D700, D750, D800, D850, D900,
D950, D1000
Unit: ms
Actual Value Range: 10, 20, 30, 40, 50, 60, 70, 80, 90,
100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 200,
210, 220, 230, 240, 250, 260, 270, 280, 290, 300, 310,
320, 330, 340, 350, 360, 370, 380, 390, 400, 410, 420,
430, 440, 450, 460, 470, 480, 490, 500, 510, 520, 530,
540, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000
Default Value: D300
TimerPo BSC690 ADD WRFD- Logical Meaning: Timer for the transmitting side of an SRB AM
llForFac 0 UCELL 020900 Channel RLC entity to wait for a response from the peer end after
hSRB FACHC Manage sending the peer end polling RLC PDUs in the
ONGCT ment CELL_FACH state. This parameter takes effect only
RL when the transmitting side of an AM RLC entity is
MOD configured with the polling function. The transmitting
UCELL side of an AM RLC entity starts this timer after sending
FACHC polling RLC PDUs to the peer end. If the transmitting
ONGCT side does not receive any status report from the peer end
RL after this timer expires, the transmitting side retransmits
polling RLC PDUs and restarts this timer. For details
about this parameter, see 3GPP TS 25.322.
GUI Value Range: D10, D20, D30, D40, D50, D60,
D70, D80, D90, D100, D110, D120, D130, D140,
D150, D160, D170, D180, D190, D200, D210, D220,
D230, D240, D250, D260, D270, D280, D290, D300,
D310, D320, D330, D340, D350, D360, D370, D380,
D390, D400, D410, D420, D430, D440, D450, D460,
D470, D480, D490, D500, D510, D520, D530, D540,
D550, D600, D650, D700, D750, D800, D850, D900,
D950, D1000
Unit: ms
Actual Value Range: 10, 20, 30, 40, 50, 60, 70, 80, 90,
100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 200,
210, 220, 230, 240, 250, 260, 270, 280, 290, 300, 310,
320, 330, 340, 350, 360, 370, 380, 390, 400, 410, 420,
430, 440, 450, 460, 470, 480, 490, 500, 510, 520, 530,
540, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000
Default Value: D200
TimerPo BSC691 ADD WRFD- Logical Meaning: Timer for the transmitting side of an SRB AM
llForFac 0 UCELL 020900 Channel RLC entity to wait for a response from the peer end after
hSRB FACHC Manage sending the peer end polling RLC PDUs in the
ONGCT ment CELL_FACH state. This parameter takes effect only
RL when the transmitting side of an AM RLC entity is
MOD configured with the polling function. The transmitting
UCELL side of an AM RLC entity starts this timer after sending
FACHC polling RLC PDUs to the peer end. If the transmitting
ONGCT side does not receive any status report from the peer end
RL after this timer expires, the transmitting side retransmits
polling RLC PDUs and restarts this timer. For details
about this parameter, see 3GPP TS 25.322.
GUI Value Range: D10, D20, D30, D40, D50, D60,
D70, D80, D90, D100, D110, D120, D130, D140,
D150, D160, D170, D180, D190, D200, D210, D220,
D230, D240, D250, D260, D270, D280, D290, D300,
D310, D320, D330, D340, D350, D360, D370, D380,
D390, D400, D410, D420, D430, D440, D450, D460,
D470, D480, D490, D500, D510, D520, D530, D540,
D550, D600, D650, D700, D750, D800, D850, D900,
D950, D1000
Unit: ms
Actual Value Range: 10, 20, 30, 40, 50, 60, 70, 80, 90,
100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 200,
210, 220, 230, 240, 250, 260, 270, 280, 290, 300, 310,
320, 330, 340, 350, 360, 370, 380, 390, 400, 410, 420,
430, 440, 450, 460, 470, 480, 490, 500, 510, 520, 530,
540, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000
Default Value: D200
N300 BSC690 ADD WRFD- 3GPP Meaning: Maximum number of RRC Connection
0 UCELLI 010101 R9 Request message retransmissions.
DLEMO Specific GUI Value Range: 0~7
DETIM ations
ER Unit: s
N300 BSC691 ADD WRFD- 3GPP Meaning: Maximum number of RRC Connection
0 UCELLI 010101 R9 Request message retransmissions.
DLEMO Specific GUI Value Range: 0~7
DETIM ations
ER Unit: s
LowRrc BSC690 ADD WRFD- 3.4/6.8/1 Meaning: Waiting time carried in low-priority RRC
ConnRej 0 UCELL 010510 3.6/27.2 Connection Reject messages. This parameter specifies
WaitTm STATE Kbps the minimum time a UE has to wait before sending a
r TIMER RRC second RRC Connection Request message. An RRC
MOD Connect Connection Request message is considered as a high-
UCELL ion and priority one when the message is initiated in the CS
STATE Radio domain and carries the cause value "Originating
TIMER Access Conversational Call", "Terminating Conversational
Bearer Call", or "Emergency Call." All other RRC Connection
Establis Request messages are low-priority ones.
hment GUI Value Range: 0~15
and
Release Unit: s
Actual Value Range: 0~15
Default Value: 4
LowRrc BSC691 ADD WRFD- 3.4/6.8/1 Meaning: Waiting time carried in low-priority RRC
ConnRej 0 UCELL 010510 3.6/27.2 Connection Reject messages. This parameter specifies
WaitTm STATE Kbps the minimum time a UE has to wait before sending a
r TIMER RRC second RRC Connection Request message. An RRC
MOD Connect Connection Request message is considered as a high-
UCELL ion and priority one when the message is initiated in the CS
STATE Radio domain and carries the cause value "Originating
TIMER Access Conversational Call", "Terminating Conversational
Bearer Call", or "Emergency Call." All other RRC Connection
Establis Request messages are low-priority ones.
hment GUI Value Range: 0~15
and
Release Unit: s
Actual Value Range: 0~15
Default Value: 4
InterRA BSC690 ADD None None Meaning: Whether to support inter-RAT DRD.When
TDRDS 0 UCELLI this switch is set to ON, inter-RAT DRD is supported.
witch NTERR If a UE cannot access an intra-RAT cell, the UE can
ATDR initiate access requests to inter-RAT cells. When this
MOD switch is set to OFF, inter-RAT DRD is not supported
UCELLI and UEs cannot initiate access requests to inter-RAT
NTERR cells.
ATDR GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF
InterRA BSC691 ADD None None Meaning: Whether to support inter-RAT DRD.When
TDRDS 0 UCELLI this switch is set to ON, inter-RAT DRD is supported.
witch NTERR If a UE cannot access an intra-RAT cell, the UE can
ATDR initiate access requests to inter-RAT cells. When this
MOD switch is set to OFF, inter-RAT DRD is not supported
UCELLI and UEs cannot initiate access requests to inter-RAT
NTERR cells.
ATDR GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF
MaxUpa BSC690 ADD WRFD- HSUPA Meaning: Factor for dynamically adjusting the
UserNu 0 UCELL 0106120 Admissi maximum number of HSUPA users in a cell. The RNC
mDynA CAC 2 on determines the number of HSUPA users in a cell before
djFactor MOD WRFD- Control admitting a new user. If the number of HSUPA users
UCELL 010670 128 admitted to a cell is smaller than the rounded-down
CAC HSUPA value of this parameter x "MaxHsupaUserNum", the
WRFD- RNC proceeds with the admission decision operation.
020101 Users
per Cell Otherwise, the RNC rejects the admission requests of
WRFD- new HSUPA users. The value of this parameter is
010639 Admissi automatically adjusted when the Automatic Congestion
on Handler (ACH) algorithm is enabled, that is, the
WRFD- Control
0106121 ADAP_CELL_CONGEST_SWITCH under the
1 96 "AdapAlgoSwitch" parameter in the "ADD
HSUPA UCELLALGOSWITCH" command is set to on. This
WRFD- Users parameter is an advanced parameter and manual
010634 per Cell modification of the parameter value is not
20 recommended. If you need to modify the value of this
HSUPA parameter, perform the modification with the assistance
Users of Huawei technical support.
per Cell GUI Value Range: 0~100
60 Unit: %
HSUPA
Users Actual Value Range: 0~100
per Cell Default Value: 100
MaxUpa BSC691 ADD WRFD- HSUPA Meaning: Factor for dynamically adjusting the
UserNu 0 UCELL 0106120 Admissi maximum number of HSUPA users in a cell. The RNC
mDynA CAC 2 on determines the number of HSUPA users in a cell before
djFactor MOD WRFD- Control admitting a new user. If the number of HSUPA users
UCELL 010670 128 admitted to a cell is smaller than the rounded-down
CAC HSUPA value of this parameter x "MaxHsupaUserNum", the
WRFD- RNC proceeds with the admission decision operation.
020101 Users
per Cell Otherwise, the RNC rejects the admission requests of
WRFD- new HSUPA users. The value of this parameter is
010639 Admissi automatically adjusted when the Automatic Congestion
on Handler (ACH) algorithm is enabled, that is, the
WRFD- Control
0106121 ADAP_CELL_CONGEST_SWITCH under the
1 96 "AdapAlgoSwitch" parameter in the "ADD
HSUPA UCELLALGOSWITCH" command is set to on. This
WRFD- Users parameter is an advanced parameter and manual
010634 per Cell modification of the parameter value is not
20 recommended. If you need to modify the value of this
HSUPA parameter, perform the modification with the assistance
Users of Huawei technical support.
per Cell GUI Value Range: 0~100
60 Unit: %
HSUPA
Users Actual Value Range: 0~100
per Cell Default Value: 100
DlBeTra BSC690 ADD WRFD- Dynami Meaning: Downlink initial access rate for UEs
ffInitBit 0 UCELL 021101 c processing PS background or interactive services. When
rate FRC WRFD- Channel the DCCC function takes effect, the downlink initial
MOD 010507 Configu access rate is used if the maximum downlink rate is
UCELL ration higher than the downlink initial access rate.
FRC Control GUI Value Range: D8, D16, D32, D64, D128, D144,
(DCCC) D256, D384
Rate Unit: kbit/s
Negotiat
ion at Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
Admissi Default Value: D64
on
Control
DlBeTra BSC691 ADD WRFD- Dynami Meaning: Downlink initial access rate for UEs
ffInitBit 0 UCELL 021101 c processing PS background or interactive services. When
rate FRC WRFD- Channel the DCCC function takes effect, the downlink initial
MOD 010507 Configu access rate is used if the maximum downlink rate is
UCELL ration higher than the downlink initial access rate.
FRC Control GUI Value Range: D8, D16, D32, D64, D128, D144,
(DCCC) D256, D384
Rate Unit: kbit/s
Negotiat
ion at Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
Admissi Default Value: D64
on
Control
CSRAB BSC690 ADD WRFD- Admissi Meaning: Whether resource allocation is optimized
CacOpt 0 UCELL 020101 on during CS RAB setups. When this parameter is set to
Switch ALGOS Control ON, the RNC allocates power resources, code
WITCH resources, channel element (CE) resources during CS
MOD RAB setups based on the loose CAC algorithm. This
UCELL setting increases the CS service setup success rate.
ALGOS When this parameter is set to OFF, the RNC does not
WITCH allocate resources during CS RAB setups based on the
loose CAC algorithm.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: ON, OFF
Default Value: OFF
CSRAB BSC691 ADD WRFD- Admissi Meaning: Whether resource allocation is optimized
CacOpt 0 UCELL 020101 on during CS RAB setups. When this parameter is set to
Switch ALGOS Control ON, the RNC allocates power resources, code
WITCH resources, channel element (CE) resources during CS
MOD RAB setups based on the loose CAC algorithm. This
UCELL setting increases the CS service setup success rate.
ALGOS When this parameter is set to OFF, the RNC does not
WITCH allocate resources during CS RAB setups based on the
loose CAC algorithm.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: ON, OFF
Default Value: OFF
switch is set to off for a cell in the OLC state, only users
processing emergency calls and platinum users can
preempt resources. Users processing common CS
services and PTT services cannot preempt resources.
10.
PREEMPT_ENH_MULTIRAB_CS_INCR_PMT_S
WITCH: Whether to optimize the PS service bearing
policy and CS resource preemption when a UE that has
already had PS RABs attempts to set up a CS RAB but
the CS RAB setup fails and resource preemption is
triggered.When this switch is set to on, if a UE that has
already had PS RABs in the CELL_DCH state attempts
to set up a CS RAB but the CS RAB setup fails and
resource preemption is triggered, PS services can still
be carried on channels using more advanced
technologies and the UE preempts only the incremental
resources required for the CS RAB setup. When this
switch is set to off, PS services must be switched back
to R99 channels when resource preemption is triggered
and the UE preempts the resources required for
processing all the ongoing services.
11.PREEMPT_ENH_MULTIRAB_PRIO_OPT_SWI
TCH: Whether to prevent PS RABs from triggering
preemption if a UE that has already had a CS RAB
attempts to set up PS RABs when the forcible CS
preemption policy is used in combined service
scenarios.When the forcible CS preemption policy
(controlled by the
PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH
under the "PreemptEnhSwitch" parameter) is used and
this switch is set to on, if a UE that has already had a CS
RAB attempts to set up PS RABs, preemption cannot
be triggered for PS services if PS RAB admission fails.
When the forcible CS preemption policy is used and this
switch is set to off, preemption can be triggered for SP
services if PS RAB admission fails.
12. PREEMPT_ENH_PS_IU_CS_PMTED_SWITCH:
Whether resources of a PS user who has sent requests
of setting up CS connections but the CS RABs have not
been established can be preempted. When this switch is
turned on, resources of the PS user cannot be preempted
before the CS RABs are established. When this switch
is turned off, resources of the PS user can be preempted
before the CS RABs are established.
13.
PREEMPT_ENH_CS_PREEMPT_CELL_EXT_SWI
PREEMPT_ENH_CS_PREEMPT_CELL_EXT_SWI
TCH, PREEMPT_ENH_WPS_USER_SWITCH
Unit: None
Actual Value Range:
PREEMPT_ENH_NODEB_PREEMPT_CE_SWITC
H,
PREEMPT_ENH_HSSCCH_PREEMPT_SF_SWITC
H,
PREEMPT_ENH_CSRRC_PREEMPT_PS_SWITCH
,
PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH
,
PREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWIT
CH,
PREEMPT_ENH_RRC_RAB_COMBINE_SWITCH,
PREEMPT_ENH_PT_USER_PREEMPT_ENH_SWI
TCH,
PREEMPT_ENH_DRNC_CS_RAB_PREEMPT_SW
ITCH,
PREEMPT_ENH_CS_PREEMPT_WHEN_OLC_SW
ITCH,
PREEMPT_ENH_MULTIRAB_CS_INCR_PMT_S
WITCH,
PREEMPT_ENH_MULTIRAB_PRIO_OPT_SWITC
H, PREEMPT_ENH_PS_IU_CS_PMTED_SWITCH,
PREEMPT_ENH_CS_PREEMPT_CELL_EXT_SWI
TCH, PREEMPT_ENH_WPS_USER_SWITCH
Default Value:
PREEMPT_ENH_NODEB_PREEMPT_CE_SWITC
H:
0,PREEMPT_ENH_HSSCCH_PREEMPT_SF_SWIT
CH:
1,PREEMPT_ENH_CSRRC_PREEMPT_PS_SWITC
H:
0,PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITC
H:
0,PREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWI
TCH:
1,PREEMPT_ENH_RRC_RAB_COMBINE_SWITC
H:
1,PREEMPT_ENH_PT_USER_PREEMPT_ENH_S
WITCH:
0,PREEMPT_ENH_DRNC_CS_RAB_PREEMPT_S
WITCH:
0,PREEMPT_ENH_CS_PREEMPT_WHEN_OLC_S
WITCH:
0,PREEMPT_ENH_MULTIRAB_CS_INCR_PMT_S
WITCH:
0,PREEMPT_ENH_MULTIRAB_PRIO_OPT_SWIT
CH:
0,PREEMPT_ENH_PS_IU_CS_PMTED_SWITCH:
0,PREEMPT_ENH_CS_PREEMPT_CELL_EXT_S
WITCH:0,PREEMPT_ENH_WPS_USER_SWITCH:
0
switch is set to off for a cell in the OLC state, only users
processing emergency calls and platinum users can
preempt resources. Users processing common CS
services and PTT services cannot preempt resources.
10.
PREEMPT_ENH_MULTIRAB_CS_INCR_PMT_S
WITCH: Whether to optimize the PS service bearing
policy and CS resource preemption when a UE that has
already had PS RABs attempts to set up a CS RAB but
the CS RAB setup fails and resource preemption is
triggered.When this switch is set to on, if a UE that has
already had PS RABs in the CELL_DCH state attempts
to set up a CS RAB but the CS RAB setup fails and
resource preemption is triggered, PS services can still
be carried on channels using more advanced
technologies and the UE preempts only the incremental
resources required for the CS RAB setup. When this
switch is set to off, PS services must be switched back
to R99 channels when resource preemption is triggered
and the UE preempts the resources required for
processing all the ongoing services.
11.PREEMPT_ENH_MULTIRAB_PRIO_OPT_SWI
TCH: Whether to prevent PS RABs from triggering
preemption if a UE that has already had a CS RAB
attempts to set up PS RABs when the forcible CS
preemption policy is used in combined service
scenarios.When the forcible CS preemption policy
(controlled by the
PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH
under the "PreemptEnhSwitch" parameter) is used and
this switch is set to on, if a UE that has already had a CS
RAB attempts to set up PS RABs, preemption cannot
be triggered for PS services if PS RAB admission fails.
When the forcible CS preemption policy is used and this
switch is set to off, preemption can be triggered for SP
services if PS RAB admission fails.
12. PREEMPT_ENH_PS_IU_CS_PMTED_SWITCH:
Whether resources of a PS user who has sent requests
of setting up CS connections but the CS RABs have not
been established can be preempted. When this switch is
turned on, resources of the PS user cannot be preempted
before the CS RABs are established. When this switch
is turned off, resources of the PS user can be preempted
before the CS RABs are established.
13.
PREEMPT_ENH_CS_PREEMPT_CELL_EXT_SWI
PREEMPT_ENH_CS_PREEMPT_CELL_EXT_SWI
TCH, PREEMPT_ENH_WPS_USER_SWITCH
Unit: None
Actual Value Range:
PREEMPT_ENH_NODEB_PREEMPT_CE_SWITC
H,
PREEMPT_ENH_HSSCCH_PREEMPT_SF_SWITC
H,
PREEMPT_ENH_CSRRC_PREEMPT_PS_SWITCH
,
PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH
,
PREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWIT
CH,
PREEMPT_ENH_RRC_RAB_COMBINE_SWITCH,
PREEMPT_ENH_PT_USER_PREEMPT_ENH_SWI
TCH,
PREEMPT_ENH_DRNC_CS_RAB_PREEMPT_SW
ITCH,
PREEMPT_ENH_CS_PREEMPT_WHEN_OLC_SW
ITCH,
PREEMPT_ENH_MULTIRAB_CS_INCR_PMT_S
WITCH,
PREEMPT_ENH_MULTIRAB_PRIO_OPT_SWITC
H, PREEMPT_ENH_PS_IU_CS_PMTED_SWITCH,
PREEMPT_ENH_CS_PREEMPT_CELL_EXT_SWI
TCH, PREEMPT_ENH_WPS_USER_SWITCH
Default Value:
PREEMPT_ENH_NODEB_PREEMPT_CE_SWITC
H:
0,PREEMPT_ENH_HSSCCH_PREEMPT_SF_SWIT
CH:
1,PREEMPT_ENH_CSRRC_PREEMPT_PS_SWITC
H:
0,PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITC
H:
0,PREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWI
TCH:
1,PREEMPT_ENH_RRC_RAB_COMBINE_SWITC
H:
1,PREEMPT_ENH_PT_USER_PREEMPT_ENH_S
WITCH:
0,PREEMPT_ENH_DRNC_CS_RAB_PREEMPT_S
WITCH:
0,PREEMPT_ENH_CS_PREEMPT_WHEN_OLC_S
WITCH:
0,PREEMPT_ENH_MULTIRAB_CS_INCR_PMT_S
WITCH:
0,PREEMPT_ENH_MULTIRAB_PRIO_OPT_SWIT
CH:
0,PREEMPT_ENH_PS_IU_CS_PMTED_SWITCH:
0,PREEMPT_ENH_CS_PREEMPT_CELL_EXT_S
WITCH:0,PREEMPT_ENH_WPS_USER_SWITCH:
0
Preempt BSC690 ADD WRFD- MBMS Meaning: Whether preemption is supported. When this
AlgoSwi 0 UCELL 010660 Phase 2 switch is turned on, the RNC allows privileged users or
tch QUEUE WRFD- MBMS services to preempt cell resources from the users or
PREEM 010661 over Iur services with the preempted attributes and lower
PT priority in the case of cell resource insufficiency. When
WRFD- Dynami this switch is turned off, the RNC terminates the service
MOD 010662 c Power
UCELL for the user due to the failure in cell resource application.
WRFD- Estimati
QUEUE on for GUI Value Range: OFF, ON
PREEM 010663
MTCH Unit: None
PT WRFD-
MSCH Actual Value Range: OFF, ON
010665
Scheduli Default Value: OFF
WRFD- ng
010505
MBMS
WRFD- Channel
0106600 Audienc
4 e Rating
WRFD- Statistic
0106160 s
6 Queuing
WRFD- and Pre-
0106600 Emption
2 Inter-
WRFD- Frequen
0106600 cy
3 Neighbo
WRFD- ring Cell
0106600 Selectio
1 n for
MBMS
WRFD- PTP
0106160 Users
1
Streami
WRFD- ng
0106160 Service
3 on
WRFD- MBMS
0106160 MBMS
2 P2P over
WRFD- HSDPA
0106160 MBMS
5 Admissi
WRFD- on
0106160 Enhance
4 ment
WRFD- MBMS
010616 Enhance
WRFD- d
0106160 Broadca
8 st Mode
WRFD- MBMS
010626 Broadca
st Mode
WRFD-
010627 MBMS
Load
Control
MBMS
Admissi
on
Control
MBMS
Transpo
rt
Resourc
e
Manage
ment
MBMS
Soft/
Selectiv
e
Combini
ng
MBMS
Introduc
tion
Package
16/32/64
/
128Kbp
s
Channel
Rate on
MBMS
MBMS
FLC
(Freque
ncy
Layer
Converg
ence)/
FLD
(Freque
ncy
Layer
Dispersi
on)
FACH
Transmi
ssion
Sharing
for
MBMS
Preempt BSC691 ADD WRFD- MBMS Meaning: Whether preemption is supported. When this
AlgoSwi 0 UCELL 010660 Phase 2 switch is turned on, the RNC allows privileged users or
tch QUEUE WRFD- MBMS services to preempt cell resources from the users or
PREEM 010661 over Iur services with the preempted attributes and lower
PT priority in the case of cell resource insufficiency. When
WRFD- Dynami this switch is turned off, the RNC terminates the service
MOD 010662 c Power
UCELL for the user due to the failure in cell resource application.
WRFD- Estimati
QUEUE on for GUI Value Range: OFF, ON
PREEM 010663
MTCH Unit: None
PT WRFD-
MSCH Actual Value Range: OFF, ON
010665
Scheduli Default Value: OFF
WRFD- ng
010505
MBMS
WRFD- Channel
0106600 Audienc
4 e Rating
WRFD- Statistic
0106160 s
6 Queuing
WRFD- and Pre-
0106600 Emption
2 Inter-
WRFD- Frequen
0106600 cy
3 Neighbo
WRFD- ring Cell
0106600 Selectio
1 n for
MBMS
WRFD- PTP
0106160 Users
1
Streami
WRFD- ng
0106160 Service
3 on
WRFD- MBMS
0106160 MBMS
2 P2P over
WRFD- HSDPA
0106160 MBMS
5 Admissi
WRFD- on
0106160 Enhance
4 ment
WRFD- MBMS
010616 Enhance
WRFD- d
0106160 Broadca
8 st Mode
WRFD- MBMS
010626 Broadca
st Mode
WRFD-
010627 MBMS
Load
Control
MBMS
Admissi
on
Control
MBMS
Transpo
rt
Resourc
e
Manage
ment
MBMS
Soft/
Selectiv
e
Combini
ng
MBMS
Introduc
tion
Package
16/32/64
/
128Kbp
s
Channel
Rate on
MBMS
MBMS
FLC
(Freque
ncy
Layer
Converg
ence)/
FLD
(Freque
ncy
Layer
Dispersi
on)
FACH
Transmi
ssion
Sharing
for
MBMS
RNC_F2D_RLC_SUSPEND_SWITCH,
P2D_SWITCH,
RNC_TVM_BASED_P2D_SWITCH
Default Value:
RNC_F2D_RLC_SUSPEND_SWITCH:
0,P2D_SWITCH:
0,RNC_TVM_BASED_P2D_SWITCH:0
RNC_F2D_RLC_SUSPEND_SWITCH,
P2D_SWITCH,
RNC_TVM_BASED_P2D_SWITCH
Default Value:
RNC_F2D_RLC_SUSPEND_SWITCH:
0,P2D_SWITCH:
0,RNC_TVM_BASED_P2D_SWITCH:0
MaxHsd BSC690 ADD WRFD- 128 Meaning: Maximum number of users supported by the
paUserN 0 UCELL 010654 HSDPA HSDPA channel. The user in this parameter refers to the
um CAC WRFD- Users user with services on the HSDPA channel, regardless of
MOD 020101 per Cell the number of RABs carried on the HSDPA channel.
UCELL Admissi Maximum HSDPA user number cannot exceed the
WRFD- HSDPA capability of the NodeB product, In practice,
CAC 0106100 on
Control the value can be set based on the cell type and the
3 richness of the available HSDPA power and code
WRFD- HSDPA resources.
010653 Admissi
on GUI Value Range: 0~192
WRFD- Control Unit: None
0106111
2 96 Actual Value Range: 0~192
HSDPA Default Value: 64
Users
per Cell
HSDPA
DRD
MaxHsd BSC691 ADD WRFD- 128 Meaning: Maximum number of users supported by the
paUserN 0 UCELL 010654 HSDPA HSDPA channel. The user in this parameter refers to the
um CAC WRFD- Users user with services on the HSDPA channel, regardless of
MOD 020101 per Cell the number of RABs carried on the HSDPA channel.
UCELL Admissi Maximum HSDPA user number cannot exceed the
WRFD- HSDPA capability of the NodeB product, In practice,
CAC 0106100 on
Control the value can be set based on the cell type and the
3 richness of the available HSDPA power and code
WRFD- HSDPA resources.
010653 Admissi
on GUI Value Range: 0~192
WRFD- Control Unit: None
0106111
2 96 Actual Value Range: 0~192
HSDPA Default Value: 64
Users
per Cell
HSDPA
DRD
CELLK BSC690 ADD WRFD- Inter Meaning: Whether to activate the cell-level dynamic
PITOC 0 UCELL 020103 Frequen CAPS flow control algorithm based on the ratio of RRC
APS FCALG WRFD- cy Load connection setup failures. When the switch is turned on,
OPARA 040100 Balance flow control is triggered if the ratio of RRC connection
MOD Flow setup failures is higher than or equal to the value of
UCELL Control "RejectKPICTHD"; flow control is stopped if the ratio
FCALG of RRC connection setup failures is lower than or equal
OPARA to the value of "RejectKPIRTHD". When flow control
is triggered, the number of allowed RRC connection
requests per second in the cell decreases based on the
value of "KPIstepdownpercentage". When flow control
is stopped, the number of allowed RRC connection
requests per second in the cell increases based on the
value of "KPIstepuppercentage". The number of RRC
connection requests does not change once the cell flow
control status becomes stable.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF
CELLK BSC691 ADD WRFD- Inter Meaning: Whether to activate the cell-level dynamic
PITOC 0 UCELL 020103 Frequen CAPS flow control algorithm based on the ratio of RRC
APS FCALG WRFD- cy Load connection setup failures. When the switch is turned on,
OPARA 040100 Balance flow control is triggered if the ratio of RRC connection
MOD Flow setup failures is higher than or equal to the value of
UCELL Control "RejectKPICTHD"; flow control is stopped if the ratio
FCALG of RRC connection setup failures is lower than or equal
OPARA to the value of "RejectKPIRTHD". When flow control
is triggered, the number of allowed RRC connection
requests per second in the cell decreases based on the
value of "KPIstepdownpercentage". When flow control
is stopped, the number of allowed RRC connection
requests per second in the cell increases based on the
value of "KPIstepuppercentage". The number of RRC
connection requests does not change once the cell flow
control status becomes stable.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF
PilotPO BSC690 ADD WRFD- DPCH Meaning: Whether the pilot power offset (PO)
OptiSwi 0 UCELL 150230 Pilot optimization algorithm takes effect. The pilot PO
tch PCSWI Power optimization algorithm sets the pilot PO and pilot bit
TCH Adjustm number to a value less than the actual configurations in
MOD ent the case of cell downlink non-HSPA power congestion
UCELL so as to relieve cell power congestion.
PCSWI GUI Value Range: OFF, ON
TCH Unit: None
Actual Value Range: OFF, ON
Default Value: OFF
HSDPA DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWI
DRD TCH
Default Value: DR_RRC_DRD_SWITCH:
1,DR_RAB_SING_DRD_SWITCH:
1,DR_RAB_COMB_DRD_SWITCH:
0,DR_INTER_RAT_DRD_SWITCH:
1,DR_RAB_COMB_DRD_SWITCH_FOR_CSUS-
ER:
1,DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SW
ITCH:0
HSDPA DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SWI
DRD TCH
Default Value: DR_RRC_DRD_SWITCH:
1,DR_RAB_SING_DRD_SWITCH:
1,DR_RAB_COMB_DRD_SWITCH:
0,DR_INTER_RAT_DRD_SWITCH:
1,DR_RAB_COMB_DRD_SWITCH_FOR_CSUS-
ER:
1,DR_INTER_RAT_CSPS_MULTI_RAB_DRD_SW
ITCH:0
Qrxlevm BSC690 ADD WRFD- Intra Meaning: The minimum required quality threshold
in 0 UCELL 010801 RNC corresponding to CPICH RSCP. When the measured
SELRE WRFD- Cell CPICH RSCP is larger than the value of this parameter,
SEL 010802 Update the cell meets the S criteria of RX level for cell selection/
MOD Inter reselection. The RNC decides whether the UE can camp
UCELL RNC on the cell according to the cell selection/reselection
SELRE Cell criteria. The setting of Qrxlevmin should be related to
SEL Update Qqualmin. For details about this parameter, see section
10.3.2.3 in 3GPP TS 25.331.
GUI Value Range: -58~-13
Unit: 2dBm
Actual Value Range: -115~-25
Default Value: -58
Qrxlevm BSC691 ADD WRFD- Intra Meaning: The minimum required quality threshold
in 0 UCELL 010801 RNC corresponding to CPICH RSCP. When the measured
SELRE WRFD- Cell CPICH RSCP is larger than the value of this parameter,
SEL 010802 Update the cell meets the S criteria of RX level for cell selection/
MOD Inter reselection. The RNC decides whether the UE can camp
UCELL RNC on the cell according to the cell selection/reselection
SELRE Cell criteria. The setting of Qrxlevmin should be related to
SEL Update Qqualmin. For details about this parameter, see section
10.3.2.3 in 3GPP TS 25.331.
GUI Value Range: -58~-13
Unit: 2dBm
Actual Value Range: -115~-25
Default Value: -58
H,
PC_INNER_LOOP_LMTED_PWR_INC_SWITCH,
PC_OLPC_SWITCH,
PC_RL_RECFG_SIR_TARGET_CARRY_SWITCH,
PC_SIG_DCH_OLPC_SWITCH,
PC_UL_SIRERR_HIGH_REL_UE_SWITCH,
PC_CFG_ED_POWER_INTERPOLATION_SWITC
H,
PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH,
PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SW
ITCH,
PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWIT
CH, PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH,
PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH,
PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH,
PC_CQI_CYCLE_BASE_COVERAGE_SWITCH,
PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH,
PC_BLER_TARGET_BASE_CELLLOAD_SWITCH
, PC_HSUPA_DATA_CH_PO_INIT_SEL_SWITCH,
PC_PILOT_PO_OPTI_SWITCH,
PC_HSUPA_LOWRATE_FLEXPC_SWITCH,
PC_COMB_HSUPA_LOWRATE_FLEXPC_SWITC
H,
PC_FP_MULTI_RLS_IND_SEND_TIME_OPT_SWI
TCH,
PC_HSUPA_RGSTEPTHDCONFIG_CORRECT_S
WITCH
Unit: None
Actual Value Range:
PC_CFG_ED_POWER_INTERPOLATION_SWITC
H, PC_DL_INNER_LOOP_PC_ACTIVE_SWITCH,
PC_DOWNLINK_POWER_BALANCE_SWITCH,
PC_EFACH_ECN0_DYN_ADJ_SWITCH,
PC_FP_MULTI_RLS_IND_SWITCH,
PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH,
PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SW
ITCH,
PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITC
H,
PC_INNER_LOOP_LMTED_PWR_INC_SWITCH,
PC_OLPC_SWITCH,
PC_RL_RECFG_SIR_TARGET_CARRY_SWITCH,
PC_SIG_DCH_OLPC_SWITCH,
PC_UL_SIRERR_HIGH_REL_UE_SWITCH,
PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWIT
CH, PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH,
PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH,
PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH,
PC_CQI_CYCLE_BASE_COVERAGE_SWITCH,
PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH,
PC_BLER_TARGET_BASE_CELLLOAD_SWITCH
, PC_HSUPA_DATA_CH_PO_INIT_SEL_SWITCH,
PC_PILOT_PO_OPTI_SWITCH,
PC_HSUPA_LOWRATE_FLEXPC_SWITCH,
PC_COMB_HSUPA_LOWRATE_FLEXPC_SWITC
H,
PC_FP_MULTI_RLS_IND_SEND_TIME_OPT_SWI
TCH,
PC_HSUPA_RGSTEPTHDCONFIG_CORRECT_S
WITCH
Default Value:
PC_CFG_ED_POWER_INTERPOLATION_SWITC
H:
0,PC_DL_INNER_LOOP_PC_ACTIVE_SWITCH:
1,PC_DOWNLINK_POWER_BALANCE_SWITCH:
1,PC_EFACH_ECN0_DYN_ADJ_SWITCH:
0,PC_FP_MULTI_RLS_IND_SWITCH:
1,PC_HSUPA_COVER_EN_AT_POLIMIT_SWITC
H:
0,PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_S
WITCH:0,
PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITC
H:
0,PC_INNER_LOOP_LMTED_PWR_INC_SWITCH
:0,PC_OLPC_SWITCH:
1,PC_RL_RECFG_SIR_TARGET_CARRY_SWITC
H:1,PC_SIG_DCH_OLPC_SWITCH:
0,PC_UL_SIRERR_HIGH_REL_UE_SWITCH:
0,PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWI
TCH:
0,PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH:
0,PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH:
0,PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH:
0,PC_CQI_CYCLE_BASE_COVERAGE_SWITCH:
0,PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH:
0,PC_BLER_TARGET_BASE_CELLLOAD_SWITC
H:
0,PC_HSUPA_DATA_CH_PO_INIT_SEL_SWITCH
:0,PC_PILOT_PO_OPTI_SWITCH:
0,PC_HSUPA_LOWRATE_FLEXPC_SWITCH:
0,PC_COMB_HSUPA_LOWRATE_FLEXPC_SWIT
CH:
H,
PC_INNER_LOOP_LMTED_PWR_INC_SWITCH,
PC_OLPC_SWITCH,
PC_RL_RECFG_SIR_TARGET_CARRY_SWITCH,
PC_SIG_DCH_OLPC_SWITCH,
PC_UL_SIRERR_HIGH_REL_UE_SWITCH,
PC_CFG_ED_POWER_INTERPOLATION_SWITC
H,
PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH,
PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SW
ITCH,
PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWIT
CH, PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH,
PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH,
PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH,
PC_CQI_CYCLE_BASE_COVERAGE_SWITCH,
PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH,
PC_BLER_TARGET_BASE_CELLLOAD_SWITCH
, PC_HSUPA_DATA_CH_PO_INIT_SEL_SWITCH,
PC_PILOT_PO_OPTI_SWITCH,
PC_HSUPA_LOWRATE_FLEXPC_SWITCH,
PC_COMB_HSUPA_LOWRATE_FLEXPC_SWITC
H,
PC_FP_MULTI_RLS_IND_SEND_TIME_OPT_SWI
TCH,
PC_HSUPA_RGSTEPTHDCONFIG_CORRECT_S
WITCH
Unit: None
Actual Value Range:
PC_CFG_ED_POWER_INTERPOLATION_SWITC
H, PC_DL_INNER_LOOP_PC_ACTIVE_SWITCH,
PC_DOWNLINK_POWER_BALANCE_SWITCH,
PC_EFACH_ECN0_DYN_ADJ_SWITCH,
PC_FP_MULTI_RLS_IND_SWITCH,
PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH,
PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SW
ITCH,
PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITC
H,
PC_INNER_LOOP_LMTED_PWR_INC_SWITCH,
PC_OLPC_SWITCH,
PC_RL_RECFG_SIR_TARGET_CARRY_SWITCH,
PC_SIG_DCH_OLPC_SWITCH,
PC_UL_SIRERR_HIGH_REL_UE_SWITCH,
PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWIT
CH, PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH,
PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH,
PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH,
PC_CQI_CYCLE_BASE_COVERAGE_SWITCH,
PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH,
PC_BLER_TARGET_BASE_CELLLOAD_SWITCH
, PC_HSUPA_DATA_CH_PO_INIT_SEL_SWITCH,
PC_PILOT_PO_OPTI_SWITCH,
PC_HSUPA_LOWRATE_FLEXPC_SWITCH,
PC_COMB_HSUPA_LOWRATE_FLEXPC_SWITC
H,
PC_FP_MULTI_RLS_IND_SEND_TIME_OPT_SWI
TCH,
PC_HSUPA_RGSTEPTHDCONFIG_CORRECT_S
WITCH
Default Value:
PC_CFG_ED_POWER_INTERPOLATION_SWITC
H:
0,PC_DL_INNER_LOOP_PC_ACTIVE_SWITCH:
1,PC_DOWNLINK_POWER_BALANCE_SWITCH:
1,PC_EFACH_ECN0_DYN_ADJ_SWITCH:
0,PC_FP_MULTI_RLS_IND_SWITCH:
1,PC_HSUPA_COVER_EN_AT_POLIMIT_SWITC
H:
0,PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_S
WITCH:0,
PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITC
H:
0,PC_INNER_LOOP_LMTED_PWR_INC_SWITCH
:0,PC_OLPC_SWITCH:
1,PC_RL_RECFG_SIR_TARGET_CARRY_SWITC
H:1,PC_SIG_DCH_OLPC_SWITCH:
0,PC_UL_SIRERR_HIGH_REL_UE_SWITCH:
0,PC_HSUPA_LITRETNUM_AUTO_ADJUST_SWI
TCH:
0,PC_OLPC_FASTDOWN_OPTIMIZE_SWITCH:
0,PC_HSUPA_LITRETNUM_INIT_SEL_SWITCH:
0,PC_CQI_CYCLE_BASE_CELLLOAD_SWITCH:
0,PC_CQI_CYCLE_BASE_COVERAGE_SWITCH:
0,PC_CQI_CYCLE_BASE_CS_PLUS_PS_SWITCH:
0,PC_BLER_TARGET_BASE_CELLLOAD_SWITC
H:
0,PC_HSUPA_DATA_CH_PO_INIT_SEL_SWITCH
:0,PC_PILOT_PO_OPTI_SWITCH:
0,PC_HSUPA_LOWRATE_FLEXPC_SWITCH:
0,PC_COMB_HSUPA_LOWRATE_FLEXPC_SWIT
CH:
TrafficC BSC690 SET WRFD- 3GPP Meaning: This parameter specifies the traffic class.
lass 0 UFACH 010101 R9 GUI Value Range: SRB, PS_TRB
CFGPA Specific
RA ations Unit: None
Actual Value Range: SRB, PS_TRB
Default Value: None
TrafficC BSC691 SET WRFD- 3GPP Meaning: This parameter specifies the traffic class.
lass 0 UFACH 010101 R9 GUI Value Range: SRB, PS_TRB
CFGPA Specific
RA ations Unit: None
Actual Value Range: SRB, PS_TRB
Default Value: None
RRC),
CS_RRC_CELL_DYN_CAPS_FC_OPT_SWITCH
(CS Cell Dynamic CAPS FC Optimization Switch)
Unit: None
Actual Value Range:
CELL_UPDATE_QUEUE_FLOW_CTRL_SWITCH,
HIGH_PRI_RRC_DYN_CAPS_FC_OPT_SWITCH,
CS_RRC_CELL_DYN_CAPS_FC_OPT_SWITCH
Default Value:
CELL_UPDATE_QUEUE_FLOW_CTRL_SWITCH:
0,HIGH_PRI_RRC_DYN_CAPS_FC_OPT_SWITCH
:
1,CS_RRC_CELL_DYN_CAPS_FC_OPT_SWITCH:
0
RRC),
CS_RRC_CELL_DYN_CAPS_FC_OPT_SWITCH
(CS Cell Dynamic CAPS FC Optimization Switch)
Unit: None
Actual Value Range:
CELL_UPDATE_QUEUE_FLOW_CTRL_SWITCH,
HIGH_PRI_RRC_DYN_CAPS_FC_OPT_SWITCH,
CS_RRC_CELL_DYN_CAPS_FC_OPT_SWITCH
Default Value:
CELL_UPDATE_QUEUE_FLOW_CTRL_SWITCH:
0,HIGH_PRI_RRC_DYN_CAPS_FC_OPT_SWITCH
:
1,CS_RRC_CELL_DYN_CAPS_FC_OPT_SWITCH:
0
8 Counters
9 Glossary
10 Reference Documents
None