Professional Documents
Culture Documents
Load Control
Load Control
RAN12.0
Feature Parameter Description
Issue 03
Date 2011-12-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
WCDMA RAN
Load Control Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
9 Parameters..................................................................................................................................9-1
10 Counters..................................................................................................................................10-1
11 Glossary ..................................................................................................................................11-1
12 Reference Documents .........................................................................................................12-1
1 Introduction
1.1 Scope
This document describes the features related to the load control. It also describes the related
parameters.
Document Issues
The document issues are as follows:
03 (2011-12-30)
02 (2010-12-20)
01 (2010-03-30)
Draft (2009-12-05)
03 (2011-12-30)
This is the document for the third commercial release of RAN12.0.
Compared with issue 02 (2010-12-30) of RAN12.0, adding the description of parameter RsvdPara1 in
the chapter 9 “Parameters.”
02 (2010-12-20)
This is the document for the second commercial release of RAN12.0.
Compared with issue 01 (2010-03-30) of RAN12.0, this issue incorporates the changes described in the
following table.
01 (2010-03-30)
This is the document for the first commercial release of RAN12.0.
Compared with issue Draft (2009-12-05) of RAN12.0, this issue incorporates the changes described in
the following table.
RedirFactorOfNorm
RedirFactorOfLDR
The description about PS GBR None.
negotiation is optimized. For details, see
5.4.2 "PS GBR Negotiation."
Editorial change None. None.
Draft (2009-12-05)
This is the draft of the document for RAN12.0.
Compared with issue 02 (2009-06-30) of RAN11.0, this issue incorporates the changes described in the
following table.
PrdReportInterval
TargetFreqThdRscp
TargetFreqThdEcN0
InterFreqMeasTime
Editorial change The information about Directed Retry Decision The information about the related
(DRD) is transferred to the Directed Retry parameters are also transferred to the
Decision Feature Parameter Description. Directed Retry Decision Feature
Parameter Description.
The information about Call Admission Control The information about the related
(CAC) is transferred to the Call Admission parameters are also transferred to the
Control Feature Parameter Description. Call Admission Control Feature
Parameter Description.
The information about dynamic power sharing The information about the related
among carriers is transferred to the Dynamic parameters are also transferred to the
Power Sharing Among Carriers Feature Dynamic Power Sharing Among Carriers
Parameter Description. Feature Parameter Description.
The load control functions are applied to different UE access phases as follows:
Before UE access: Potential User Control (PUC)
During UE access: Intelligent Access Control (IAC) and Call Admission Control (CAC)
After UE access: intra-frequency Load Balancing (LDB), Load Reshuffling (LDR), and Overload
Control (OLC)
The following sections will provide detailed information about the load control functions performed in the
different UE access phases.
IAC √ √ √ √
PUC √ - - -
LDB √ - - -
LDR √ √ √ √
OLC √ - - √
NOTE
- : not considered
√: considered
If ARP is not received in messages from the Iu interface, the user priority is regarded as copper.
3 Load Measurement
This chapter describes the WRFD-020102 Load Measurement Feature.
The load control functions, such as OLC and CAC, use load measurement values in the uplink and the
downlink. A common Load Measurement (LDM) function is used to control load measurement in the
uplink and the downlink separately.
Load measurement is implemented by the NodeB. The filtering of measurement quantities is
implemented by the NodeB and the RNC.
RTWP ChoiceRprtUnitForUlBasicMeas
TenMsecForUlBasicMeas
RSEPS
MinForUlBasicMeas
TCP ChoiceRprtUnitForDlBasicMeas
Non-HSDPA power TenMsecForDlBasicMeas
MinForDlBasicMeas
GBP ChoiceRprtUnitForHsdpaPwrMeas
TenMsecForHsdpaPwrMeas
MinForHsdpaPwrMeas
HS-DSCH PBR ChoiceRprtUnitForHsdpaRateMeas
TenMsecForHsdpaPrvidRateMeas
MinForHsdpaPrvidRateMeas
E-DCH PBR ChoiceRprtUnitForHsupaRateMeas
TenMsecForHsupaPrvidRateMeas
MinForHsupaPrvidRateMeas
In Figure 3-2:
A is the sampling value of the measurement.
B is the measurement value after layer 1 filtering.
Here:
Fn is the new post-filtering measurement value.
Fn-1 is the last post-filtering measurement value.
Mn is the new measurement value from the physical layer.
α = (1/2)k/2, k is the measure filter coefficient which is specified by the following parameters.
− Forload control algorithms (excluding OLC), k is specified by the UlBasicCommMeasFilterCoeff
or DlBasicCommMeasFilterCoeff parameter.
− ForOLC algorithm, k is specified by the UlOlcMeasFilterCoeff or DlOlcMeasFilterCoeff
parameter.
LDM must apply different smooth window length and measurement periods to PUC, CAC, LDR, and
OLC to obtain appropriate filtered values.
The following table lists the smooth window length parameters for setting different functions.
GBP measurements have the same smooth window length in all related functions. The filter length for GBP measurement
is specified by the HsdpaNeedPwrFilterLen parameter.
The length of the PBR smooth filter window is specified by the HsdpaPrvidBitRateFilterLen /
HsupaPrvidBitRateFilterLen parameter.
The Alpha filter formula is: Fn = (1 - α) x Fn-1 + α x Mn (n≥1). For details about this formula, see section 3.3.1 "Layer 3
Filtering on the NodeB Side."
Counting threshold = (Duration of background noise)/(RTWP reporting period). The duration of background noise is
used in auto-adaptive upgrade decision and is set by the BGNAdjustTimeLen parameter. For the setting of RTWP
reporting period, see section 3.2 "Reporting Period."
The PUC function is enabled only when the PUC subparameter of the NBMLdcAlgoSwitch parameter
is set to 1.
For a cell not supporting DC-HSDPA, the RNC periodically monitors the downlink load of the cell.
If the cell load is higher than the upper threshold (SpucHeavy) plus the load level division hysteresis
(SpucHyst), the cell load is considered heavy.
If the cell load is lower than the lower threshold (SpucLight) minus SpucHyst, the cell load is
considered light.
For a cell supporting DC-HSDPA, the RNC concurrently monitors the load state of each single cell and
load state of the cell group.
The checking of load state of a single cell is the same as that of a cell not supporting DC-HSDPA.
The checking of load state of the cell group is as follows:
− Ifthe load of the two cells is higher than their upper thresholds (SpucHeavy) plus their load level
division hystereses (SpucHyst), the load of the cell group is considered heavy.
− Ifthe load of the two cells is lower than their lower thresholds (SpucLight) minus their load level
division hystereses (SpucHyst), the load of the cell group is considered light.
The load state of a cell supporting DC-HSDPA is determined based on the following table.
Load of Single Cell Load of Cell Group Load of Cell Supporting DC-HSDPA
Heavy Heavy, normal, or light Heavy
The states of a cell load are heavy, normal, and light, as shown in Figure 4-2.
Figure 4-2 Cell load states
Depending on the load status of the serving cell, the cell reselection parameters Sintersearch are
adjusted up or down or kept unchanged. Changes to the variable Sintersearch are carried out as shown
in Table 4-2.
Table 4-2 Changes to Sintersearch according to the load state
Load State of the S'intersearch Change to Sintersearch
Serving Cell
The configurations of Qoffset1 and Qoffset are related to the load of the serving cell and the load of the
neighboring cells. Changes to Qoffset1 and Qoffset2 are carried out as shown in Table 4-3.
Table 4-3 Changes of Qoffset1 and Qoffset2 according to the load state
Load State of Load State of Q'offset1 Change to Q'offset2 Change to
the Neighboring the Serving Qoffset1 Qoffset2
Cells Cell
The prerequisite for the changes of the preceding parameters is that these parameters retain their default values.
As shown in Figure 5-1, the procedure of service access includes the procedures for RRC connection
setup and RAB setup. The successful setup of the RRC connection is one of the prerequisites for the
RAB setup.
During the RRC connection processing, the RNC performs the following steps.
1. Performs the RRC redirection based on distance (only for UE-originating AMR services). For details,
see section 5.2.2 "RRC Redirection based on Distance". If the RNC decides to obtain UE access
from another cell, it sends an RRC connection reject message to the UE; otherwise, the RNC
performs the next step.
2. Performs RRC redirection for service steering. For details, see section 5.2.3 "RRC Redirection for
Service Steering."
− Ifthe RNC decides to obtain UE access from the current cell, it then makes a resource-based
admission decision. If the resource-based admission fails, the RNC performs directed retry decision
(DRD) and redirection.
− If
the RNC decides to obtain UE access from another cell, it then sends an RRC connection reject
message to the UE. The message carries the information about the cell and instructs the UE to set
up an RRC connection to the cell.
For details, see5.2 "IAC During RRC Connection Setup."
During the RAB connection processing, the RNC performs the following steps:
1. Performs inter-frequency DRD to select a suitable cell for service steering or load balancing. For
details about DRD, see the Directed Retry Decision Feature Parameter Description
2. Performs rate negotiation according to the service requested by the UE. For details, see 5.4 "Rate
Negotiation."
3. Makes cell resource-based admission decision. If the admission is successful, UE access is granted.
Otherwise, the RNC performs the next step. For details about admission decision, see the Call
Admission Control Feature Parameter Description.
4. Selects a suitable cell, according to the inter-frequency DRD, from the cells where no admission
attempt has been made, and then go to 2. If all the attempt fails, the RNC performs the next step.
5. Selects a suitable cell according to the inter-RAT DRD. If the inter-RAT admission is successful, UE
access is granted in the inter-RAT cell. If the inter-RAT DRD fails or is not supported, the RNC
performs the next step.
6. Makes a preemption attempt. For details about preemption, see 5.6 "Preemption" If the preemption is
successful, UE access is granted. If the preemption fails or is not supported, the RNC performs the
next step.
7. Makes a queuing attempt. For details about queuing, see 5.7 "Queuing." If the queuing is successful,
UE access is granted. If the queuing fails or is not supported, the RNC performs the next step.
8. Performs low-rate access. For details about low-rate access, see 5.8 "Low-Rate Access of the PS BE
Service." If the low-rate access is admitted, UE access is granted. If the low-rate access is
unsuccessful, the RNC performs the next step.
9. Rejects UE access.
After the admission attempts of an HSPA service request fail in all candidate cells, the service falls back to the DCH. Then,
the service reattempts to access the network.
Target Rate
Negotiation
Negotiation
Negotiation
Negotiation
Frequency
Initial Rate
Inter-RAT
Inter-
MBR
GBR
DCH √ √ √ √ √ √ √ √ √
HSUPA - √ √ √ √ √ √ √ -
HSDPA - √ √ - - √ √ √ -
After receiving an RRC CONNECTION REQUEST message from the UE, the RNC performs the RRC
redirection based on distance (only for UE-originating AMR services). For details, see section 5.2.2
"RRC Redirection based on Distance". If the RNC decides to obtain UE access from another cell, it
sends an RRC connection reject message to the UE; otherwise, the RNC performs the next step.
Then, the RNC uses the RRC redirection algorithm for service steering to decide whether the UE can
access the network from the current cell:
If the UE can access the network from the current cell according to the decision result, the RNC uses
the CAC algorithm to decide whether an RRC connection can be set up between the UE and the
current cell.
− If
the RRC connection can be set up between the UE and the current cell, the RNC sends an RRC
CONNECTION SETUP message to the UE.
− Ifthe RRC connection cannot be set up between the UE and the current cell, the RNC attempts to
select a cell for RRC connection setup through RRC DRD. If the RRC DRD fails, RRC redirection
will be performed.
If the UE needs to access the network from another cell according to the decision result, the RNC
sends an RRC CONNECTION REJECT message to the UE. The message carries the information
about this cell.
DrSwitch: DR_RRC_DRD_SWITCH is the general switch of the following four algorithms:
RRC Redirection based on Distance
RRC Redirection for Service Steering
RRC DRD
RRC Redirection After DRD Failure
Before enabling the four algorithms, turn on the DrSwitch: DR_RRC_DRD_SWITCH.
smaller than the parameter, the RNC performs the next step. Otherwise, the RNC does not perform
RRC redirection based on distance, and handles the RRC connection setup request of the UE in the
current cell.
− If the cell is in the basic congestion state or is overloaded, the RNC generates a random value
ranging from 0 to 1 and compares the value with the RedirFactorOfLDR parameter. If the random
value is equal to or smaller than the parameter, the RNC performs the next step. Otherwise, the
RNC does not perform RRC redirection based on distance, and handles the RRC connection setup
request of the UE in the current cell.
4. The RNC sends the UE an RRC CONNECTION REJECT message containing information on the
neighboring GSM cells of the current cell.
If the current cell does not have any neighboring GSM cell, the UE spontaneously selects a proper cell to access.
− If
RedirSwitch is set to ONLY_TO_INTER_FREQUENCY, the RNC sends an RRC CONNECTION
REJECT message to the UE, redirecting the UE to the target frequency carried in the message.
The frequency information carried in the message can be set by running the SET UREDIRECTION command.
If the RedirBandInd parameter is set to DependOnNCell, only intra-band inter-frequency neighboring cell can be
selected as target frequency.
− If
RedirSwitch is set to ONLY_TO_INTER_RAT, the RNC sends an RRC CONNECTION REJECT
message to the UE. The message carries the information about inter-RAT neighboring cells.
PS R99 and PS HSPA services for UEs of the REL-5 version cannot be identified by the RNC because these UEs do
not carry the Domain indicator, Call type, or UE capability indication IEs in the RRC CONNECTION REQUEST
message.
In order to reduce the waiting time of the peer UE and ensure that the terminated call can be admitted as soon as
possible, the RRC redirection based on service steering is not applicable to the terminated call.
contained in the IE "RAB Parameters" of the RAB ASSIGNMENT REQUEST message is used. In
addition, the subsequent RAB ASSIGNMENT RESPONSE message does not contain the GBR.
If the IE "Type of Alternative Guaranteed Bit Rate Information" in the RAB ASSIGNMENT REQUEST
message is set to "value range", the sole GBR contained in the IE "Alternative Guaranteed Bit Rates"
is used. In addition, the subsequent RAB ASSIGNMENT RESPONSE message contains the GBR.
If the IE "Type of Alternative Guaranteed Bit Rate Information" in the RAB ASSIGNMENT REQUEST
message is set to "Discrete values", the largest GBR contained in the IE "Alternative Guaranteed Bit
Rates" is used. In addition, the subsequent RAB ASSIGNMENT RESPONSE message contains the
GBR.
If the subparameter PS_STREAM_IU_QOS_NEG_SWITCH of the parameter PsSwitch is set to 0, the
GBR negotiation will be not performed. In such a case, the GBR contained in the IE "RAB Parameters" in
the RAB ASSIGNMENT REQUEST message is used.
For details about GBR negotiation, see 3GPP 25.413.
If the DCCC function is enabled and PS_RAB_Downsizing_Switch subparameter of the PsSwitch parameter is set to 1,
the RNC can decrease the rate through the RAB rate decrease function when the admission based on the initial rate fails.
− If
the DRA_HSUPA_DCCC_SWITCH subparameter of the DraSwitch parameter is set to 0, the
initial access rate is the MBR for there won't be any rate upsizing reconfiguration when the
DRA_HSUPA_DCCC_SWITCH subparameter of the DraSwitch parameter is set to 0.
For the HSDPA service, the initial admission rate and the initial access are both GBR.
5.6 Preemption
5.6.1 Common Preemption
This section describes the pre-emption algorithm in the WRFD-010505 Queuing and Pre-Emption
feature.
By forcibly releasing the resources of lower-priority users, the preemption (pre-emption) function
increases the access success rate of higher-priority users.
After cell/cell group resource-based admission fails, the RNC performs preemption if the following
conditions are met:
The RNC receives a RAB ASSIGNMENT REQUEST message indicating that preemption is
supported.
In the RAB ASSIGNMENT REQUEST message sent by the CN, the Pre-emption Capability IE
specifies whether a service can trigger preemption and the Pre-emption Vulnerability IE specifies
whether a service can be preempted. Service priorities and the Pre-emption Capability and
Pre-emption Vulnerability IEs determine whether to perform preemption.
The preemption algorithm switch (PreemptAlgoSwitch) is set to ON.
Preemption is applicable to the following scenarios:
The preemption algorithm checks whether the resources released by preempted UEs or RABs are sufficient for setting
up new RABs. It does not consider the remaining resources in the cell, because they may be used by other UEs during
the preemption.
For the preemption triggered for power, the preempted objects can be R99 users, R99 + HSPA combined users, or
HSPA RABs.
For the preemption triggered for the Iub bandwidth, the preempted objects can only be RABs.
For the preemption triggered for the credit resource, more than one user or RAB can be preempted.
For the preemption triggered for the code, only one user can be preempted.
3. The RNC releases the resources occupied by the candidate users or RABs.
4. The requested service directly uses the released resources to access the network without admission
decision.
For details about preemption of MBMS services, see the MBMS Feature Parameter Description.
This function is determined by the RsvdPara1 parameter. This parameter consists of two subparameters:
RSVDBIT4 and RSVDBIT5.
Table 5-3 describes how these two subparameters determine preemption.
Table 5-3 Forced preemption
RsvdPara1: RsvdPara1: RRC Connection Setup Phase RAB-Related Phases
RSVDBIT5 RSVDBIT4
On Off CS conversational services cannot If RAB admission for CS
preempt PS BE services. conversational services fails, PS BE
services can be preempted
unconditionally.
On On If RRC admission for CS If RAB admission for CS
conversational services fails, PS BE conversational services fails, PS BE
services can be preempted services can be preempted
unconditionally. unconditionally.
Off On If RRC admission for CS Common preemption is performed.
conversational services fails, PS BE That is, service priorities and the
services whose Pre-emption Pre-emption Capability and
Vulnerability IE is set to Pre-emption Vulnerability IEs
"pre-emptable" can be preempted. determine whether to perform
preemption.
Off Off CS conversational services cannot Common preemption is performed.
preempt PS BE services. That is, service priorities and the
Pre-emption Capability and
Pre-emption Vulnerability IEs
determine whether to perform
preemption.
In the RRC connection setup phase, if an RRC setup request is from the CS domain and the cause of RRC setup is
Originating Conversational Call or Terminating Conversational Call, the RNC regards the corresponding service as CS
conversational service.
In the case of unconditional preemption, the RNC does not compare the priority of CS conversational
services with that of PS BE services. In addition, it does not consider the Pre-emption Capability or
Pre-emption Vulnerability IE delivered by the CN. In this case, PS BE services can be preempted by any
CS conversational services and only PS BE services can be preempted. Preempted PS BE services are
ranked by priority and PS BE services with the lowest priority are preempted.
5.7 Queuing
This section describes the queuing algorithm in the WRFD-010505 Queuing and Pre-Emption feature.
For PS services, after preemption fails, the RNC performs queuing if the following conditions are met:
The RNC receives a RAB ASSIGNMENT REQUEST message indicating that queuing is supported.
The queuing algorithm switch (QueueAlgoSwitch) is set to ON.
The queuing function is triggered by the heartbeat timer that is set by the PollTimerLen parameter. Each
time the timer expires, the RNC selects the service that meets the requirement to make an admission
attempt.
The UE requesting DC-HSDPA services will be queued in the selected anchor-carrier cell.
Not full Stamps this request with the request time (T_request)
Puts this request into the queue
Starts the heartbeat timer if it is not started
Full Checks whether the integrated priority of any existing request is lower than that
of the new request
If yes, then the queuing algorithm:
- Checks the queuing time of each request. The algorithm removes the
request with the longest queuing time from the queue
- Stamps the new request with the request time (T_request) and then puts it
into the queue
- Starts the heartbeat timer if it is not started
If no, then the queuing algorithm rejects the new request directly
After the heartbeat timer expires, the queuing algorithm performs resource-based admission attempts as
follows:
Rejects the request if the queuing time of the request(Telapsed ) is longer than the maximum queuing
time (MaxQueueTimeLen). Here, Telapsed is equal to the current time minus the request time
(T_request).
Selects the request with the highest integrated priority for a resource-based admission attempt.
If more than one service has the highest integrated priority, the RNC selects the request with the
longest queuing time.
If the attempt is successful, the heartbeat timer is restarted for the next processing.
If the attempt fails, the queuing algorithm proceeds as follows:
− Putsthe service request back into the queue with the request time (T_request) unchanged for the next
attempt.
− Selectsthe request with the longest queuing time from the rest and makes another attempt until a
request is accepted or all requests are rejected.
After an appropriate access action is determined, the service attempts to access the network.
If the action of access from the DCH at 0 kbit/s is determined, the service attempts to access the
network at 0 kbit/s for traffic and at the normal rate for signaling. For details about the methods of
resource-based admission decision, see the Call Admission Control Feature Parameter Description.
If the action of access from the FACH/E-FACH is determined, the service attempts to access the
network from the FACH/E-FACH.
If the attempt fails, this service is rejected.
For the service that accesses the network at 0 kbit/s, the ZeroRateUpFailToRelTimerLen timer is
started after the service rate fails to increase for the first time. If the rate fails to increase even when the
timer expires, the service is released, and the connection is also released for a single service.
If no data is transmitted during a period after the access, the UE state changes to another state. For
details about state transition, see the State Transition Feature Parameter Description.
The RNC does not perform RRC redirection for service steering.
In the case of power-based admission, the emergency call is admitted regardless of whether the CAC
function is enabled or not.
In the case of hard resource-based admission, the emergency call is admitted if the current remaining
resources are sufficient for RRC connection setup. If the admission fails, preemption is performed
regardless of whether the preemption is enabled or not. The emergency call that triggers preemption has
the highest priority. The range of users who can be preempted is specified by the
EmcPreeRefVulnSwitch parameter.
If EmcPreeRefVulnSwitch is set to ON, all non-emergency users who have accessed the network
can be preempted, regardless of the preemption-prohibited attribute of the users.
If EmcPreeRefVulnSwitch is set to OFF, only the non-emergency users with preemption-allowed
attribute can be preempted.
The principles for selection of specific users to be preempted are the same as those for common
services. For details, see 5.6 "Preemption."
If the downlink load of a cell is lower than the cell underload threshold (CellUnderrunThd), it is an
indication that the cell has sufficient remaining capacity for more load. In this case, the transmit power
of the P-CPICH can be increased step by step to help lighten the load of neighboring cells. The step is
specified by the PCPICHPowerPace parameter.
If the current transmit power is equal to the maximum transmit power of P-CPICH ( ), the current
transmit power is not adjusted.
7 Load Reshuffling
This chapter describes the WRFD-020106 Load Reshuffling feature.
When the usage of cell resource exceeds the basic congestion triggering threshold, the cell enters the
basic congestion state. In this case, Load Reshuffling (LDR) is required to reduce the cell load and
increase the access success rate.
The following figure shows the triggering and relieving of basic congestion.
Figure 7-1 Triggering and relieving of basic congestion
As shown in Figure 7-1, if the UL/DL load of the cell is higher than or equal to the UL/DL LDR trigger
threshold (UlLdrTrigThd or DlLdrTrigThd) for a hysteresis time, the cell is in the basic congestion state,
and the related load reshuffling actions, as listed in Table 7-2, are taken. If the current UL/DL load of the
cell is lower than the UL/DL LDR relief threshold (UlLdrRelThd or DlLdrRelThd) for a hysteresis time,
the cell backs to the normal state and the related load reshuffling actions are stopped.
For the downlink, the hysteresis time is specified by the DlLdTrnsHysTime parameter; for the uplink, the hysteresis time
is 600ms
The UL or DL LDR trigger threshold of a DC-HSDPA cell group equals the sum of the UL or DL LDR
trigger thresholds of the two cells in this group. The UL or DL LDR relief threshold of a DC-HSDPA cell
group equals the sum of the UL/DL LDR relief thresholds of the two cells in this group. If a DC-HSDPA
cell group is in the basic congestion state, the related LDR actions are performed in each cell separately.
The uplink load of an HSUPA cell is calculated based on the uncontrollable load of the cell. The downlink
load of an HSDPA cell is calculated based on the load of non-HSPA power and GBP in the cell.
The following table lists the LDR switches that need to be set to 1 for different algorithm types.
Table 7-1 LDR switches to be set to 1
Algorithm Load Control Algorithm Switch LDC Algorithm Switch
Type A LC_CREDIT_LDR_SWITCH CELL_CREDIT_LDR
For R99 cells, only DCH UEs are selected by LDR actions.
The GoldUserLoadControlSwitch parameter specifies whether the users of gold priority are selected by LDR actions..
Inter-frequency load handover
Code reshuffling
BE service rate reduction
AMR rate reduction
Inter-RAT load handover in the CS domain, which involves the following actions:
− Inter-RAT Should Be Load Handover in the CS Domain
− Inter-RAT Should Not Be Load Handover in the CS Domain
The difference between the "Inter-RAT Should Be Load Handover In the CS/PS Domain" and "Inter-RAT Should Not Be
Load Handover In the CS/PS Domain" actions lies in the selection of users. The former only involves CS/PS users with
the "service handover" IE in RAB ASSIGNMENT REQUEST set to "handover to GSM should be performed", while the
latter only involves CS/PS users with the "service handover" IE set to "handover to GSM should not be performed". For
details about the "service handover" IE, see the Handover Feature Parameter Description.
Inter-RAT load handover in the PS domain, which involves the following actions:
− Inter-RAT Should Be Load Handover in the PS Domain
− Inter-RAT Should Not Be Load Handover in the PS Domain
QoS Renegotiation for Uncontrollable Real-Time Services
MBMS power reduction
The LDR actions concerning DC-HSDPA are inter-frequency load handover and inter-RAT handover in
PS domain.
The sequence of LDR actions can be changed by running the ADD UCELLLDR command.
The following figure illustrates the detailed LDR procedure. In this example, the sequence of LDR
actions is fixed to inter-frequency load handover, code reshuffling, BE rate reduction, inter-RAT handover
in CS domain, inter-RAT handover in PS domain, AMR rate reduction, QoS Renegotiation for
Uncontrollable Real-Time Services, and MBMS power reduction.
As shown in the preceding figure, when the system is congested, the inter-frequency load handover is
initiated first.
If the handover succeeds, the algorithm continues to check whether the system is congested. If the
system is still congested, the inter-frequency load handover is initiated again.
If the handover fails, code reshuffling is performed:
− If the code reshuffling succeeds, the algorithm continues to check whether the system is congested.
If the system is still congested, the code reshuffling is initiated again.
− If the code reshuffling fails, the next action, that is, BE rate reduction, is taken.
The rest actions to be performed may be deduced by analogy. For details about LDR actions, see
section 7.3 "LDR Actions."
The LDR actions that are triggered by basic congestion caused by different resources are different.
Table 7-2describes the LDR actions intended for different resources.
When the basic congestion is triggered by different resources, the congestion can be relieved in a order
set by running the SET ULDCALGOPARA command.
Inter-RAT Handover in
Inter-Frequency Load
Real-Time Services
BE Rate Reduction
Code Reshuffling
Uncontrollable
CS Domain
PS Domain
Power UL DCH √ Handover √ √ √ √ √
HSUPA √ √ √
DL DCH √ √ √ √ √* √
HSDPA √ √ √
DC-HSDPA √ √
FACH √*
(MBMS)
Iub UL DCH √ √ √
HSUPA √ √
DL DCH √ √ √
HSDPA √ √
FACH
(MBMS)
Code - -
DL DCH √ √ √
HSDPA
FACH
(MBMS)
Credit UL DCH √ √ √ √
HSUPA √ √ √
DL DCH √ √ √ √
HSDPA
FACH
(MBMS)
In the Table 7-2, there are several attentions described in the following.
The Inter-RAT Handover in CS Domain action can be performed for the HSUPA services that are in the
non-scheduling mode.
The Inter-RAT Handover in CS Domain action can be performed for the HSDPA services only when
the HsdpaCMPermissionInd parameter is set to TRUE.
If the downlink power-based admission uses the ENU algorithm, the basic congestion can also be
caused by the ENU. In this situation, LDR actions do not involve AMR rate reduction or MBMS power
reduction, as indicated by the symbol "*" in the preceding table.
In the same environment, different rates have different downlink transmit powers. The higher the rate,
the greater the downlink transmit power. Therefore, the load can be reduced by bandwidth
reconfiguration.
For HSUPA services, the CE consumption, which is calculated on the basis of the Maximum Bit Rate
(MBR), can be reduced through rate downsizing. Therefore, the BE service rate downsizing for
HSUPA is applicable only for reduing CE resource congestion.
The load margin refers to the difference between the load of the target cell and the basic congestion triggering
threshold of the target cell.
If the margin is no higher than the threshold, the action fails, and the algorithm takes the next action.
If there is more than one cell meeting the requirements, the first one is selected as the blind
handover target cell.
If multiple UEs have the same lowest integrated priority, the algorithm selects the one with the highest rate for handover.
The UL and DL handover bandwidth thresholds are specified by UlInterFreqHoBWThd and DlInterFreqHoBWThd
respectively. Both the thresholds are considered in the selection of the target UE.
4. After selecting the target cell and the UE, the RNC makes blind handover decision. For details, see
the Handover Feature Parameter Description.
If the compressed mode is required for the UE to perform inter-frequency measurement, the RNC starts the
inter-frequency measurement timer (specified by the InterFreqMeasTime parameter) as soon as the measurement
control message is issued. If inter-frequency handover remains unsuccessful until the timer expires, the RNC stops the
inter-frequency measurement and cancels the compressed mode.
When admission control of Power/NodeB Credit is disabled, it is not recommended that the BE Rate Reduction be
configured as an LDR action in order to avoid ping-pong effect.
BE rate reduction can only be performed when the DRA_DCCC_SWITCH subparameter of the
DraSwitch parameter is set to 1.
The LDR algorithm operates as follows:
1. Based on the integrated priority, the algorithm sorts the BE RABs in descending order.
2. The algorithm selects the BE RABs that meet the following condition:
− Thecurrent rate of the BE RAB is higher than the GBR specified by running the SET USERGBR
command.
− The BE RAB has the lower integrated priorities.
The number of selected RABs is specified by the UlLdrBERateReductionRabNum or
DlLdrBERateReductionRabNum parameter.
If the integrated priorities of some RABs are identical, the RAB with the highest rate is selected.
3. If services can be selected, the action is successful. If services cannot be selected, the action fails.
The algorithm takes the next action.
4. The bandwidth of the selected services is reduced to the specified rate. For details about the rate
reduction procedure, see the DCCC Feature Parameter Description.
5. The reconfiguration is complete as indicated by the RADIO BEARER RECONFIGURATION
message on the Uu interface and through the synchronized radio link reconfiguration procedure on
the Iub interface.
The RNC will request a new MBR and GBR that are the lowest ones among the alternative
configurations in the RAB ASSIGNMENT message from the CN. However, the CN can decide how to
react to the request upon reception of the RAB MODIFY REQUEST message.
The LDR algorithm operates as follows:
1. Based on the integrated priority, the algorithm sorts the RABs for real-time services in the PS domain
in descending order.
2. The algorithm selects the RABs with the lowest integrated priorities for QoS renegotiation. The
number of selected RABs is specified by the UlLdrPsRTQosRenegRabNum or
DlLdrPsRTQosRenegRabNum parameter. If the RNC cannot find an appropriate service for the
QoS renegotiation, the action fails. The algorithm takes the next action.
3. The algorithm performs QoS renegotiation for the selected services. The GBR during the service
setup is the minimum rate of the service after the QoS renegotiation.
4. The RNC initiates the RAB MODIFY REQUEST message to the CN for the QoS renegotiation. Upon
reception of the RAB MODIFY REQUEST message, the CN sends the RAB ASSIGNMENT
REQUEST message to the RNC for RAB parameter reconfiguration.
HSPA services can be selected only when HsdpaCMPermissionInd is set to TRUE and HsupaCMPermissionInd is not
set to Limited.
For details about the two parameters, see the Handover Feature Parameter Description.
To optimize the code usage efficiency, the "left most" principle is adopted in initial code allocation
procedure, that is, the code with minimum SF is reserved to ensure that the codes are available for use
continuously. However, the code tree may not obey the "left most" principle during actual use. Code
reshuffling can be used to make the code tree obey "left most"‟ principle.
When the cell is in the basic congestion state caused by code resource, code reshuffling can be
performed to reserve sufficient code resources for subsequent services. Code subtree adjustment refers
to the switching of users from one code subtree to another. It is used for decreasing the code fragments
to release smaller codes first..
The algorithm operates as follows:
1. Initializes SF_Cur to CellLdrSfResThd.
2. Traverses all the subtrees with this SF_Cur at the root node except the subtrees occupied by
common channels and HSDPA channels, and takes the subtrees in which the number of users is not
larger than the value of MaxUserNumCodeAdj as candidate subtrees for code reshuffling.
− If such candidate subtrees are available, the algorithm goes to step 3.
− If no such candidate subtree is available, subtree selection fails. This procedure ends.
3. Selects a subtree from the candidate subtrees according to the setting of LdrCodePriUseInd.
− Ifthis parameter is set to TRUE, the algorithm selects the subtree with the largest code number from
the candidates.
− Ifthis parameter is set to FALSE, the algorithm selects the subtree with the smallest number of
users from the candidates. if multiple subtrees have the same number of users, the algorithm
selects the subtree with the largest code number.
4. Treats each user in the subtree as a new user and allocates code resources to each user.
5. Initiates the reconfiguration procedure for each user in the subtree and reconfigures the
channelization codes of the users to the newly allocated code resources.
The reconfiguration procedure on the UU interface is initiated through the PHYSICAL CHANNEL
RECONFIGURATION message and that on the Iub interface through the RL RECONFIGURATION
message.
The following figure shows an example of code reshuffling. In this example, CellLdrSfResThd is set to
SF8, and MaxUserNumCodeAdj is set to 1.
Figure 7-3 Code reshuffling
8 Overload Control
This chapter describes the WRFD-020107 Overload Control feature.
After the UE access is allowed, the power consumed by a single link is adjusted by the single link power
control function. The power varies with all kinds of factors such as the mobility of the UE and the
changes in the environment. In some situations, the total power load of the cell can be higher than the
target load. To ensure the system stability, Overload Control (OLC) must be performed.
For details about overload congestion caused by Iub bandwidth and details about user release, see the Transmission
Resource Management Feature Parameter Description.
OLC can be enabled through the UL_UU_OLC and DL_UU_OLC subparameters of the
NBMLdcAlgoSwitch parameter.
The following figure shows the triggering and release of cell power overload.
Figure 8-1 Triggering and release of cell power overload
As shown in Figure 8-1, if the UL/DL load of the cell is higher than or equal to the UlOlcTrigThd or
DlOlcTrigThd for a hysteresis time, the cell is in the overload state, and the related overload handling
action is taken. If the current UL/DL load of the cell is lower than the UlOlcRelThd or DlOlcRelThd for a
hysteresis time, the overload state of the cell is released and the related overload handling is stopped.
For the downlink, the hysteresis time is specified by the DlLdTrnsHysTime parameter; for the uplink, the hysteresis time
is 600ms.
The UL or DL OLC trigger threshold of a DC-HSDPA cell group equals the sum of the UL or DL OLC
trigger thresholds of the two cells in this group. The UL or DL OLC relief threshold of a DC-HSDPA cell
group equals the sum of the UL or DL OLC relief thresholds of the two cells in this group. If a DC-HSDPA
cell group is overloaded, the related overload handling is performed in each cell separately.
The uplink load of an HSUPA cell is calculated based on the uncontrollable load of the cell. The downlink
load of an HSDPA cell is calculated based on the load of non-HSPA power and GBP in the cell.
In addition to periodic measurement, event-triggered measurement is applicable to OLC.
If OLC_EVENTMEAS is set to 1, the RNC sends the NodeB a request for event measurement based on
power resource. In the associated request message, the reporting criterion is specified, including
UlOlcTrigHyst / DlOlcTrigHyst, UlOlcTrigThd / DlOlcTrigThd, and UlOlcRelThd / DlOlcRelThd. Then
the NodeB checks the current power load in real time according to this criterion and reports the status to
the RNC periodically if the conditions of reporting are met.
Limited by 3GPP, the NodeB cannot check the total load of the non-HSDPA power and the GBP. Therefore, the
recommended setting of OLC_EVENTMEAS is 0 for HSDPA cells.
whether the uplink equivalent user load proportion of the cell is lower than 40%. If it is lower than 40%,
the RNC does not perform this operation.
For switching BE services to common channels, the OLC algorithm operates as follows:
1. Based on the integrated priority, the algorithm sorts all the UEs in the PS domain in descending
order.
2. The algorithm selects the UEs with the lowest integrated priorities. The number of selected UEs is
specified by TransCchUserNum. If the selection fails, the OLC takes the next action.
The preceding power adjustment is applicable to only the FACH carrying common services rather than MBMS services.
This function is disabled when all the UlOlcTraffRelRabNum, DlOlcTraffRelRabNum, and MbmsOlcRelNum
parameters are set to 0.
The higher the value of UlOlcTraffRelRabNum or DlOlcTraffRelRabNum is, the more the cell load decreases, which will
affect the users experience negatively.
9 Parameters
Table 9-1 Parameter description
Parameter ID NE MML Command Description
BgnEndTime BSC690 ADD Meaning: (1) This parameter, along with the [Algorithm start
0 UCELLCAC(Man time], is used to limit the validation time of the background
datory) noise automatic update algorithm. If [Algorithm stop time] is
MOD greater than [Algorithm start time], and the background noise
UCELLCAC(Man automatic update algorithm is enabled, then the algorithm is
datory) activated during the period of [Algorithm stop time] to
[Algorithm start time] each day. In other periods, the algorithm
fails. If [Algorithm stop time] is less than [Algorithm start time],
and the background noise automatic update algorithm is
enabled, then the algorithm is activated during the period of
[Algorithm stop time] each day to [Algorithm start time] of the
next day. In other periods, the algorithm fails
(2) Input format: HH&MM&SS
BGNEqUser BSC690 ADD Meaning: When the number of uplink equivalent users is not
NumThd 0 UCELLCAC(Opti larger than this parameter, the RTWP could be regarded as
onal) background noise. Therefore, the measured RTWP could be
MOD input to the auto-adaptive background noise update filter;
UCELLCAC(Opti otherwise, the RTWP could not be regarded as background
onal) noise, and should not be input to the filter, and at the same
time, the auto-adaptive status should be reset.
BGNSwitch BSC690 ADD Meaning: When the parameter is 'OFF', the auto-adaptive
0 UCELLCAC(Opti background noise update algorithm is switched off. Otherwise,
onal) the algorithm is switched on.
MOD
UCELLCAC(Opti GUI Value Range: OFF, ON
onal) Actual Value Range: OFF, ON
Unit: None
Default Value: ON
BgnUpdateT BSC690 ADD Meaning: The difference of RTWP that trigger the update of
hd 0 UCELLCAC(Opti background noise. If the difference is larger than the threshold,
onal) the background will be updated.
MOD
UCELLCAC(Opti GUI Value Range: 1~100
onal) Actual Value Range: 0.1~10, step:0.1
Unit: dBm
Default Value: 5
CarrierTypeP BSC690 ADD Meaning: Decide which carrier is prior when ARP and
riorInd 0 UOPERUSERPRI TrafficClass are both identical.
ORITY(Optional)
MOD GUI Value Range: NONE, DCH, HSPA
UOPERUSERPRI Actual Value Range: NONE, DCH, HSPA
ORITY(Optional) Unit: None
Default Value: NONE
CellLdrSfRes BSC690 ADD Meaning: This parameter specifies the Cell SF reserved
Thd 0 UCELLLDR(Optio threshold used for judging whether the code load reshuffling
nal) (LDR) is allowed. The code load reshuffling could be triggered
MOD only when the minimum available SF of a cell is higher than
UCELLLDR(Optio this threshold
nal)
GUI Value Range: SF4(SF4), SF8(SF8), SF16(SF16),
SF32(SF32), SF64(SF64), SF128(SF128), SF256(SF256)
Actual Value Range: SF4, SF8, SF16, SF32, SF64, SF128,
SF256
Unit: None
Default Value: SF8
CellOverrunT BSC690 ADD Meaning: If the cell downlink load exceeds this threshold, the
hd 0 UCELLLDB(Optio algorithm will decrease the pilot transmit power of the cell so
nal) as to increase the whole system's capacity. This parameter is
MOD based on network planning.
UCELLLDB(Optio
nal) GUI Value Range: 0~100
Actual Value Range: 0~1, step:0.01
Unit: %
Default Value: 90
CellUnderrun BSC690 ADD Meaning: If the cell downlink load is lower than this threshold,
Thd 0 UCELLLDB(Optio the algorithm will increase the pilot transmit power of the cell
nal) so as to share load of other cells. This parameter is based on
MOD network planning.
UCELLLDB(Optio
nal) GUI Value Range: 0~100
Actual Value Range: 0~1, step:0.01
Unit: %
Default Value: 30
ChoiceRprtU BSC690 SET Meaning: If you set this parameter to TEN_MSEC, use [DL
nitForDlBasic 0 ULDM(Optional) basic meas rprt cycle,Unit:10ms] to specify the measurement
Meas report period. If you set this parameter to MIN, use [DL basic
meas rprt cycle,Unit:min] to specify measurement report
period. For detailed information of this parameter, refer to
3GPP TS 25.433.
ChoiceRprtU BSC690 SET Meaning: If you set this parameter to TEN_MSEC, use
nitForHsupa 0 ULDM(Optional) [HSDPA bit rate meas cycle,Unit:10ms] to specify the
RateMeas measurement report period. If you set this parameter to MIN,
use [HSDPA bit rate meas cycle,Unit:min] to specify
measurement report period. For detailed information of this
parameter, refer to 3GPP TS 25.433.
ConnectFail BSC690 SET Meaning: RRC redirection switch used in the case of
RrcRedirSwit 0 UDRD(Optional) admission failure. It is valid only when the
ch "DR_RRC_DRD_SWITCH" parameter is set to ON.
- OFF indicates that the RRC redirection is not allowed.
- Only_To_Inter_Frequency indicates that only RRC
redirection to inter-frequency cells is allowed.
- Allowed_To_Inter_RAT indicates that both RRC redirection
to inter-frequency cells and redirection to inter-RAT cells are
allowed.
DlBasicCom BSC690 SET Meaning: L3 filtering coefficient. The larger the value of this
mMeasFilter 0 ULDM(Optional) parameter, the stronger the smoothing effect and the higher
Coeff the anti-slow-fading capability, but the lower the signal change
tracing capability. For detailed information of this parameter,
refer to 3GPP TS 25.433.
GUI Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9,
D11, D13, D15, D17, D19
Actual Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9,
D11, D13, D15, D17, D19
Unit: None
Default Value: D6
DlBeTraffInit BSC690 SET Meaning: DL initial access rate of PS background or interactive
Bitrate 0 UFRC(Optional) service. When DCCC function is enabled, the downlink initial
access rate will be set to this value if the downlink maximum
rate is higher than the initial access rate.
GUI Value Range: D8, D16, D32, D64, D128, D144, D256,
D384
Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
Unit: kbit/s
Default Value: D64
DlCacAvgFilt BSC690 SET Meaning: Length of smoothing filter window of downlink CAC.
erLen 0 ULDM(Optional)
GUI Value Range: 1~32
Actual Value Range: 1~32
Unit: None
Default Value: 5
DlCSInterRat BSC690 ADD Meaning: Number of users selected in a DL LDR CS domain
ShouldBeHO 0 UCELLLDR(Optio inter-RAT SHOULDBE load handover. The target subscribers
UeNum nal) of this parameter are the CS domain subscribers. Because the
MOD CS domain subscribers are session subscribers in general and
UCELLLDR(Optio they have little impact on load, you can set this parameter to a
nal) comparatively high value.
DlDcccRateT BSC690 SET Meaning: For a BE service that has a low maximum rate, the
hd 0 UDCCC(Optional) DCCC algorithm is not obviously effective yet it increases
algorithm processing. Thus, the traffic-based DCCC algorithm
is applied to BE services whose maximum DL rate is greater
than the threshold.
GUI Value Range: D8, D16, D32, D64, D128, D144, D256,
D384
Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
Unit: kbit/s
Default Value: D64
DlInterFreqH BSC690 ADD Meaning: The UE can be selected to process load handover
oBWThd 0 UCELLLDR(Optio only when its bandwidth is less than this threshold.
nal)
MOD GUI Value Range: 0~400000
UCELLLDR(Optio Actual Value Range: 0~400000
nal) Unit: bit/s
Default Value: 200000
DlInterFreqH BSC690 ADD Meaning: The inter-frequency neighboring cell could be
oCellLoadSp 0 UCELLLDR(Optio selected as the destination of load handover only when its load
aceThd nal) remaining space is larger than this threshold. The lower the
MOD parameter is, the easier it is to find a qualified target cell for the
UCELLLDR(Optio blind handover. Excessively small value of the parameter,
nal) however makes the target cell easily enter the congestion
status. The higher the parameter is, the more difficult it is for
the inter-frequency blind handover occurs.
DlLdrAMRRa BSC690 ADD Meaning: The mechanism of the LDR is that an action is
teReduction 0 UCELLLDR(Optio performed in each [LDR period] and some services are
RabNum nal) selected based on the action rules to perform this action. This
MOD parameter defines the maximum number of RABs selected in
UCELLLDR(Optio executing downlink LDR-AMR voice service rate reduction. If
nal) the parameter value is too high, the LDR action may fluctuate
greatly and over control may occur (the state of basic
congestion turns into another extreme--under load). If the
parameter value is too low, the LDR action has a slow
response and the effect is not apparent, affecting the LDR
performance.
DlLdrCreditSf BSC690 ADD Meaning: Reserved SF threshold in downlink credit LDR. The
ResThd 0 UCELLLDR(Optio downlink credit LDR could be triggered only when the SF
nal) factor corresponding to the downlink reserved credit is higher
MOD than the uplink or downlink credit SF reserved threshold.
UCELLLDR(Optio
nal) GUI Value Range: SF4(SF4), SF8(SF8), SF16(SF16),
SF32(SF32), SF64(SF64), SF128(SF128), SF256(SF256)
Actual Value Range: SF4, SF8, SF16, SF32, SF64, SF128,
SF256
Unit: None
Default Value: SF8
DlLdrRelThd BSC690 ADD Meaning: If the ratio of DL load of the cell to the downlink
0 UCELLLDM(Opti capacity is lower than this threshold, the DL load reshuffling
onal) function of the cell is stopped. After the basic congestion state
MOD of the cell load is released, the system no longer implements
UCELLLDM(Opti the LDR action. Because the load fluctuates, the difference
onal) between the LDR release threshold and trigger threshold
should be higher than 10%. The ping-pong effect of the
preliminary congestion state may occur.
GUI Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9,
D11, D13, D15, D17, D19
Actual Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9,
D11, D13, D15, D17, D19
Unit: None
Default Value: D3
DlOlcRelThd BSC690 ADD Meaning: If the ratio of DL load of the cell to the downlink
0 UCELLLDM(Opti capacity is lower than this threshold, the DL overload and
onal) congestion control function of the cell is stopped. The value of
MOD the OLC release threshold should not be much lower than or
UCELLLDM(Opti close to the OLC trigger threshold, or the system state may
onal) have a ping-pong effect. The recommended difference
between the OLC release threshold and the OLC trigger
threshold is higher than 10%. It is desirable to set the two
parameters a bit higher given that the difference between OLC
trigger threshold and OLC release threshold is fixed.
DlOlcTraffRel BSC690 ADD Meaning: User release is an extreme method in reducing the
RabNum 0 UCELLOLC(Optio cell load and recovering the system when the cell is
nal) overloaded and congested.
MOD The mechanism of the OLC is that an action is performed in
UCELLOLC(Optio each [OLC period] and some services are selected based on
nal) the action rules to perform this action. This parameter defines
the maximum number of RABs released in executing downlink
OLC service release.
For the users of a single service, the releasing of RABs means
the complete releasing of the users. The releasing of RABs
causes call drops, so UlOlcFTFRstrctTimes or
DlOlcFTFRstrctTimes should be set to a low value. Higher
values of the parameter get the cell load to decrease more
obviously, but the QoS will be affected.
DlOlcTrigHys BSC690 SET Meaning: DL OLC trigger hysteresis.This parameter can avoid
t 0 ULDM(Optional) touching off OLC event continually.
DlOlcTrigThd BSC690 ADD Meaning: If the ratio of DL load of the cell to the downlink
0 UCELLLDM(Opti capacity is not lower than this threshold, the DL overload and
onal) congestion control function of the cell is triggered. The value
MOD of the OLC release threshold should not be much lower than or
UCELLLDM(Opti close to the OLC trigger threshold, or the system state may
onal) have a ping-pong effect. The recommended difference
between the OLC release threshold and the OLC trigger
threshold is higher than 10%. It is desirable to set the two
parameters a bit higher given that the difference between OLC
trigger threshold and OLC release threshold is fixed.
DRDEcN0Th BSC690 ADD Meaning: DRD Ec/No threshold for determining whether to
reshhold 0 U2GNCELL(Optio perform the blind handover. The DRD is permitted if Ec/No of
nal) the current cell is greater than the DRD Ec/No threshold of a
MOD inter-RAT/inter-frequency neighboring cell.
U2GNCELL(Optio
nal) GUI Value Range: -24~0
Actual Value Range: -24~0
Unit: dB
Default Value: -18
DrdOrLdrFla BSC690 ADD Meaning: Specify the flags of the cells that the DRD
g 0 UINTERFREQNC measurement or LDR measurement is performed.
ELL(Optional) The value "TRUE" indicates that the cell can be considered as
MOD the measurement object in the DRD measurement algorithm
UINTERFREQNC or LDR measurement algorithm. The value "FALSE" indicates
ELL(Optional) that the cell is invalid.
EcN0Ths BSC690 SET Meaning: Threshold for determining the signal quality in a cell.
0 UFRC(Optional) If the reported Ec/No exceeds the value of this parameter, you
can infer that the signal quality in the cell is good and a high
code rate can be set for initial access.
HsdpaCMPer BSC690 SET Meaning: Whether the compressed mode (CM) can coexist
missionInd 0 UCMCF(Optional) with the HSDPA service. If this parameter is set to TRUE: 1.
the RNC can enable the CM for HSDPA services. 2. The
HSDPA services can be enabled when the CM is enabled. If
this parameter is set to FALSE: 1. the CM for HSDPA services
can be enabled only after the H2D (HS-DSCH to DCH)
channel switch. 2. The HSDPA services cannot be enabled
when the CM is enabled.
This switch is used for the compatibility of the HSDPA
terminals that do not support CM when HSDPA is enabled.
HsdpaNeedP BSC690 SET Meaning: Length of smoothing filter window of HSDPA power
wrFilterLen 0 ULDM(Optional) requirement.
HsupaInitialR BSC690 SET Meaning: HSUPA BE traffic initial bit rate. When DCCC
ate 0 UFRC(Optional) algorithm switch and HSUPA DCCC algorithm switch are
enabled, the uplink initial bit rate will be set to this value if the
uplink max bit rate is higher than the initial bit rate.
GUI Value Range: D8, D16, D32, D64, D128, D144, D256,
D384, D608, D1280, D2048, D2720, D5440
Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384, 608,
1280, 2048, 2720, 5440
Unit: kbit/s
Default Value: D256
HsupaPrvidB BSC690 SET Meaning: Length of smoothing filter window of HSUPA bit rate.
itRateFilterLe 0 ULDM(Optional)
n GUI Value Range: 1~32
Actual Value Range: 1~32
Unit: None
Default Value: 5
InterFreqLdH BSC690 ADD Meaning: This parameter specifies the forbidden traffic classes
oForbidenTC 0 UCELLLDR(Optio when perform inter-frequency handover, in order to prevent
nal) disarranging of the layers.
MOD
UCELLLDR(Optio GUI Value Range: R99_CONVERSATIONAL(R99
nal) Conversational), R99_STREAMING(R99 Streaming),
R99_BE(R99 BE), HSDPA_CONVERSATIONAL(HSDPA
Conversational), HSDPA_STREAMING(HSDPA Streaming),
HSDPA_BE(HSDPA BE), HSPA_CONVERSATIONAL(HSPA
Conversational), HSPA_STREAMING(HSPA Streaming),
HSPA_BE(HSPA BE)
Actual Value Range: R99_CONVERSATIONAL,
R99_STREAMING, R99_BE, HSDPA_CONVERSATIONAL,
HSDPA_STREAMING, HSDPA_BE,
HSPA_CONVERSATIONAL, HSPA_STREAMING, HSPA_BE
Unit: None
Default Value: None
InterFreqMea BSC690 ADD Meaning: This parameter defines the timer length for
sTime 0 UCELLMCLDR(O inter-frequency measurement.
ptional) After inter-frequency measurement starts, if no inter-frequency
MOD handover is performed when this timer expires, the
UCELLMCLDR(O inter-frequency measurement and the compressed mode (if
ptional) started) are stopped.
This parameter is used to prevent the long inter-frequency
measurement state (compressed mode) due to unavailable
measurement of the target cells that meet the handover
requirements.
LdrPeriodTim BSC690 SET Meaning: Identifying the period of the LDR execution. When
erLen 0 ULDCPERIOD(O basic congestion occurs, execution of LDR can dynamically
ptional) reduce the cell load. The lower the parameter value is, the
more frequently the LDR action is executed, which decreases
the load quickly. If the parameter value is excessively low, an
LDR action may overlap the previous one before the previous
result is displayed in LDM. The higher the parameter value is,
the more likely this problem can be prevented. If the parameter
value is excessively high, the LDR action may be executed
rarely, failing to lower the load timely.
The LDR algorithm aims to slowly reduce the cell load and
control the load below the admission threshold, each LDR
action takes a period (for example the inter-RAT load
handover needs a delay of about 5 s if the compressed mode
is needed), and there is a delay for the LDM module responds
to the load decreasing (the delay is about 3 s when the L3 filter
coefficient is set to 6), so the parameter value should be higher
than 8s.
MaxFachPo BSC690 ADD Meaning: The offset between the FACH transmit power and
wer 0 UFACH(Optional) P-CPICH transmit power in a cell.
MaxUserNu BSC690 ADD Meaning: This parameter specifies the number of users
mCodeAdj 0 UCELLLDR(Optio selected in code reshuffling. Code reshuffling can be triggered
nal) only when the number of users on a code is no greater than
MOD the threshold. Code reshuffling has a big impact on the QoS. In
UCELLLDR(Optio addition, the reshuffled subscribers occupy two code
nal) resources during code reshuffling. Thus, the parameter should
be set to a comparatively low value.
MbmsDecPo BSC690 ADD Meaning: When the priority of the RAB of MBMS services
werRabThd 0 UCELLLDR(Optio exceeds this threshold, reconfigure the MBMS power to the
nal) minimum power. The MBMS service at each rate is set on the
MOD basis of two power levels. The power set for an MBMS service
UCELLLDR(Optio is determined according to cell load during the service access.
nal) In addition, the FACH power of the MBMS service must be
decreased as required in the duration of cell congestion. Some
services with high priority, for example the disaster pre-alert,
however, do not need the coverage shrink caused by cell load.
In such a case, you can adjust the service priority threshold to
protect the services with high priority against the impact of the
service access failure and the load control algorithm.
MinForHsdpa BSC690 SET Meaning: This parameter specifies the HSDPA bit rate
PrvidRateMe 0 ULDM(Mandatory measurement report period. For detailed information of this
as ) parameter, refer to 3GPP TS 25.433.
NBMCacAlgo BSC690 ADD Meaning: "The above values of the algorithms represent the
Switch 0 UCELLALGOSWI following information:
TCH(Optional) CRD_ADCTRL: Control Cell Credit admission control
MOD algorithm
UCELLALGOSWI Only when NODEB_CREDIT_CAC_SWITCH which is set by
TCH(Optional) the SET UCACALGOSWITCH command and this switch are
on,the Cell Credit admission control algorithm is valid.
HSDPA_UU_ADCTRL: Control HSDPA UU Load admission
control algorithm
HSDPA_GBP_MEAS: Control HSDPA HS-DSCH Required
Power measurement
HSDPA_PBR_MEAS: Control HSDPA HS-DSCH Provided Bit
Rate measurement
HSUPA_UU_ADCTRL: Control HSUPA UU Load admission
control algorithm
MBMS_UU_ADCTRL: Control MBMS UU Load admission
control algorithm
HSUPA_PBR_MEAS: Control HSUPA Provided Bit Rate
measurement
HSUPA_EDCH_RSEPS_MEAS: Control HSUPA Provided
Received Scheduled EDCH Power Share measurement
EMC_UU_ADCTRL: Control power admission for emergency
user
RTWP_RESIST_DISTURB: Control algorithm of resisting
disturb when RTWP is abnormal
FACH_UU_ADCTRL: The switch for resource admission to the
FACH over the Uu interface (FACH_UU_ADCTRL) is used to
enable or disable the user admission function to FACH.
1. If this switch is enabled: if the current cell is congested
due to overload, and the users are with RAB connection
requests or RRC connection requests(except the cause of
""Detach"", ""Registration"", or ""Emergency Call""), the users
will be rejected. Otherwise FACH user admission procedure is
initiated. A user can access the cell after the procedure
succeeds.
2. If this switch is disabled: FACH user admission
procedure is initiated without the consideration of cell state.
MIMOCELL_LEGACYHSDPA_ADCTRL: Legacy HSDPA
admission control algorithm in MIMO cell.
FAST_DORMANCY_ADCTRL: Whether to enable or disable
state transition of users in the CELL-DCH state, who are
enabled with fast dormancy, to ease FACH congestion in a
NBMLdcAlgo BSC690 ADD Meaning: The algorithms with the above values represent are
Switch 0 UCELLALGOSWI as follow:
TCH(Optional) INTRA_FREQUENCY_LDB: Intra-frequency load balance
MOD algorithm. It is also named cell breathing algorithm.Based on
UCELLALGOSWI the cell load, this algorithm changes the pilot power of the cell
TCH(Optional) to control the load between intra-frequency cells.
PUC: Potential user control algorithm. Based on the cell load,
this algorithm changes the selection/reselection parameters of
a cell to lead the UE to a lighter loaded cell.
UL_UU_OLC: UL UU overload congestion control algorithm.
When the cell is overloaded in UL, this algorithm reduces the
cell load in UL by quick TF restriction or UE release.
DL_UU_OLC: DL UU overload congestion control algorithm.
When the cell is overloaded in DL, this algorithm reduces the
cell load in DL by quick TF restriction or UE release.
UL_UU_LDR: UL UU load reshuffling algorithm. When the cell
is heavily loaded in UL, this algorithm reduces the cell load in
UL by using inter-frequency load handover, BE service rate
reduction, uncontrollable real-time service QoS renegotiation,
CS should be inter-RAT, PS should be inter-RAT handover,
CS should not be inter-RATand, PS should not be inter-RAT
handover and AMR service rate reduction.
DL_UU_LDR: DL UU load reshuffling algorithm. When the cell
is heavily loaded in DL, this algorithm reduces the cell load in
DL by using inter-frequency load handover, BE service rate
reduction, uncontrollable real-time service QoS renegotiation,
CS should be inter-RAT, PS should be inter-RAT handover,
CS should not be inter-RATand, PS should not be inter-RAT
handover, AMR service rate reduction and MBMS service
power decrease.
OLC_EVENTMEAS: Control OLC event measurement. This
algorithm starts the OLC event measurement.
CELL_CODE_LDR: Code reshuffling algorithm. When the cell
CODE is heavily loaded, this algorithm reduces the cell CODE
load by using BE service rate reduction and code tree
NbmLdcUeS BSC690 ADD Meaning: The algorithms with the above values represent are
elSwitch 0 UCELLALGOSWI as follow:
TCH(Optional) NBM_LDC_ALL_UE: When inter-freq handover select user
MOD occurs, no need to consider whether target cell support Ue.
UCELLALGOSWI NBM_LDC_MATCH_UE_ONLY: When inter-freq handover
TCH(Optional) select user occurs, only consider Ues supported by target cell.
NBM_LDC_MATCH_UE_FIRST: When inter-freq handover
select user occurs, first consider Ues supported by target cell.
NBMUlCacAl BSC690 ADD Meaning: The algorithms with the above values represent are
goSelSwitch 0 UCELLALGOSWI as follow:
TCH(Mandatory) ALGORITHM_OFF: Disable uplink call admission control
MOD algorithm.
UCELLALGOSWI ALGORITHM_FIRST: The load factor prediction algorithm will
TCH(Optional) be used in uplink CAC.
ALGORITHM_SECOND: The equivalent user number
algorithm will be used in uplink CAC.
ALGORITHM_THIRD: The loose call admission control
algorithm will be used in uplink CAC.
NodeBLdcAl BSC690 ADD Meaning: IUB_LDR (Iub congestion control algorithm): When
goSwitch 0 UNODEBALGOP the NodeB Iub load is heavy, users are assembled in priority
ARA(Optional) order among all the NodeBs and some users are selected for
MOD LDR action (such as BE service rate reduction) in order to
UNODEBALGOP reduce the NodeB Iub load.
ARA(Optional) NODEB_CREDIT_LDR (NodeB level credit congestion control
algorithm): When the NodeB level credit load is heavy, users
are assembled in priority order among all the NodeBs and
some users are selected for LDR action in order to reduce the
NodeB level credit load.
LCG_CREDIT_LDR (Cell group level credit congestion control
algorithm): When the cell group level credit load is heavy,
users are assembled in priority order among all the NodeBs
and some users are selected for LDR action in order to reduce
the cell group level credit load.
IUB_OLC (Iub Overload congestion control algorithm): When
the NodeB Iub load is Overload, users are assembled in
priority order among all the NodeBs and some users are
selected for Olc action in order to reduce the NodeB Iub load.
To enable some of the algorithms above, select them.
Otherwise, they are disabled.
OffQoffset2H BSC690 ADD Meaning: Offset of Qoffset2 when neighboring cell load is
eavy 0 UCELLPUC(Opti heavier than that of the center cell (Note: Qoffset2 is used as a
onal) priority to decide which cell will be selected in cell selection or
MOD reselection) For detailed information of this parameter, refer to
UCELLPUC(Opti 3GPP TS 25.304.
onal)
GUI Value Range: -20~20
Actual Value Range: -20~20
Unit: dB
Default Value: 4
OffQoffset2Li BSC690 ADD Meaning: Offset of Qoffset2 when neighboring cell load is
ght 0 UCELLPUC(Opti lighter than that of the center cell (Note: Qoffset2 is used as a
onal) priority to decide which cell will be selected in cell selection or
MOD reselection) For detailed information of this parameter, refer to
UCELLPUC(Opti 3GPP TS 25.304.
onal)
GUI Value Range: -20~20
Actual Value Range: -20~20
Unit: dB
Default Value: -4
OffSinterHea BSC690 ADD Meaning: Offset of Sintersearch when center cell load level is
vy 0 UCELLPUC(Opti "Heavy" (Note: Sintersearch is used to decide whether to start
onal) the inter-frequency cell reselection). For detailed information of
MOD this parameter, refer to 3GPP TS 25.304.
UCELLPUC(Opti
onal) GUI Value Range: -10~10
Actual Value Range: -20~20, step:2
Unit: dB
Default Value: 2
OffSinterLigh BSC690 ADD Meaning: Offset of Sintersearch when center cell load level is
t 0 UCELLPUC(Opti "Light" (Note: Sintersearch is used to decide whether to start
onal) the inter-frequency cell reselection). For detailed information of
MOD this parameter, refer to 3GPP TS 25.304.
UCELLPUC(Opti
onal) GUI Value Range: -10~10
Actual Value Range: -20~20, step:2
Unit: dB
Default Value: -2
OlcPeriodTi BSC690 SET Meaning: Identifying the period of the OLC execution. When
merLen 0 ULDCPERIOD(O overload occurs, execution of OLC can dynamically reduce the
ptional) cell load. When setting the parameter, consider the hysteresis
for which the load monitoring responds to the load change. For
example, when the layer 3 filter coefficient is 6, the hysteresis
for which the load measurement responds to the step-function
signals is about 2.8s, namely that the system can trace the
load control effect about 3 s later after each load control. In this
case, the OLC period timer length cannot be smaller than 3s.
OlcPeriodTimerLen along with ULOLCFTFRstrctUserNum,
DLOLCFTFRstrctUserNum, ULOLCFTFRSTRCTTimes,
DLOLCFTFRSTRCTTimes, ULOLCTraffRelUserNum, and
DLOLCTraffRelUserNum determine the time it takes to release
the uplink/downlink overload. If the OLC period is excessively
long, the system may respond very slowly to overload. If the
OLC period is excessively short, unnecessary adjustment may
occur before the previous OLC action has taken effect, and
therefore the system performance is affected.
PCPICHPow BSC690 ADD Meaning: Pilot power adjustment step increased or decreased
erPace 0 UCELLLDB(Optio in each increase of the cell breathing algorithm or decrease of
nal) cell pilot. For detailed information of this parameter, refer to
MOD 3GPP TS 25.433.
UCELLLDB(Optio
nal) GUI Value Range: 0~100
Actual Value Range: 0~10, step:0.1
Unit: dB
Default Value: 2
PollTimerLen BSC690 SET Meaning: Timer length of the queue poll. The queue is polled
0 UQUEUEPREEM for every time specified in this parameter. During each poll, all
PT(Optional) the expired users are removed from the queue and this user
fails in access. Among all the unexpired users, resources are
allocated in the order of high priority to low priority. If resource
allocation is successful, the user succeeds in access and
traverse of this queue is stopped. Otherwise, the rest users are
traversed until all the unexpired users go through this.
PrdReportInt BSC690 ADD Meaning: Interval between periodic reporting for the
erval 0 UCELLINTERFR inter-frequency handover.
EQHOCOV(Optio In periodic reporting mode, the inter-frequency handover
nal) attempts is reported at the preset interval. It is not
MOD recommended that this parameter be set to
UCELLINTERFR "NON_PERIODIC_REPORT" since the UE behavior may be
EQHOCOV(Optio unknown. This parameter has impact on the Uu signaling flow.
nal) If the interval is too short and the frequency is too high, the
RNC may have high load when processing signaling. If the
interval is too long, the network cannot detect the signal
changes in time. This may delay the inter-frequency handover,
thus causing call drops.
PucAvgFilter BSC690 SET Meaning: Length of smoothing filter window of potential user
Len 0 ULDM(Optional) control (PUC).
QueueLen BSC690 SET Meaning: Queue length. The total number of users in queue of
0 UQUEUEPREEM each cell should not exceed the value specified in this
PT(Optional) parameter. When a new user needs queuing, 1) If the queue
has vacancy, the user joins the queue immediately. 2) If the
queue is full and there is a user whose queue time exceeds
the allowed maximum queue time, this user is out of the queue
and access fails. At the same time, the new user joins the
queue. 3) If the queue has a user whose priority is lower than
that of the new user, the user in the queue with the lowest
priority is out of the queue and access fails. At the same time,
the new user joins the queue. 4)For other situations, the user
cannot join the queue.
RedirBandIn BSC690 ADD Meaning: Frequency band of the target UL and DL UARFCNs
d 0 UCELLREDIREC to which the UE is redirected. It is recommended that this
TION(Optional) parameter is set to Depending on the configuration of
MOD neighboring cells without the consideration of NRNC
UCELLREDIREC neighboring cells, that is, in the non-overlapped network. This
TION(Optional) helps avoid auto-redirection. Auto-redirection is a case in
which redirection is initiated in the current cell when the
UARFCN to which the UE is redirected is the same as that of
the current cell.
ReDirUARFC BSC690 ADD Meaning: Target uplink UARFCN of a cell for RRC redirection.
NUplink 0 UCELLDRD(Opti The value range of the UL UARFCN depends on the value of
onal) "RedirBandInd". The relation between "RedirBandInd" and the
MOD value range of the UL UARFCN is as follows:
UCELLDRD(Opti BAND1
onal) Common UARFCNs: [9612-9888]
Special UARFCNs: none
BAND2
Common UARFCNs: [9262-9538]
Special UARFCNs: {12, 37, 62, 87, 112, 137, 162, 187, 212,
237, 262, 287}
BAND3
Common UARFCNs: [937-1288]
Special UARFCNs: none
BAND4
Common UARFCNs: [1312-1513]
Special UARFCNs: {1662, 1687, 1712, 1737, 1762, 1787,
1812, 1837, 1862}
BAND5
Common UARFCNs: [4132-4233]
Special UARFCNs: {782, 787, 807, 812, 837, 862}
BAND6
Common UARFCNs: [4162-4188]
Special UARFCNs: {812, 837}
BAND7
Common UARFCNs: [2012-2338]
Special UARFCNs: {2362, 2387, 2412, 2437, 2462, 2487,
2512, 2537, 2562, 2587, 2612, 2637, 2662, 2687}
BAND8
Common UARFCNs: [2712-2863]
Special UARFCNs: none
BAND9
Common UARFCNs: [8762-8912]
Special UARFCNs: none
BandIndNotUsed: [0-16383]
If the UL UARFCN is not manually configured, if RedirBandInd
is set to BAND1, BAND2, BAND3, BAND4, BAND5, BAND6,
BAND7, BAND8, or BAND9, and if the DL UARFCN is valid,
then the target UL UARFCN of the redirection is automatically
configured according to the following principles:
If the DL UARFCN is a common UARFCN, the relation
between the UL UARFCN and the DL UARFCN is as follows:
BAND1: UL UARFCN = DL UARFCN - 950
BAND2: UL UARFCN = DL UARFCN - 400
BAND3: UL UARFCN = DL UARFCN - 225
BAND4: UL UARFCN = DL UARFCN - 225
BAND5: UL UARFCN = DL UARFCN - 225
BAND6: UL UARFCN = DL UARFCN - 225
BAND7: UL UARFCN = DL UARFCN - 225
BAND8: UL UARFCN = DL UARFCN - 225
BAND9: UL UARFCN = DL UARFCN - 475
If the DL UARFCN is a special UARFCN, the relation between
the UL UARFCN and the DL UARFCN is as follows:
ReDirUARFC BSC690 ADD Meaning: Whether the target UL UARFCN to which the UE is
NUplinkInd 0 UCELLDRD(Opti redirected needs to be configured. TRUE indicates that the UL
onal) UARFCN needs to be configured. FALSE indicates that the UL
MOD UARFCN need not be manually configured and it is
UCELLDRD(Opti automatically configured according to the relation between the
onal) UL and DL UARFCNs.
ReDirUARFC BSC690 ADD Meaning: Whether the target UL UARFCN to which the UE is
NUplinkInd 0 UCELLREDIREC redirected needs to be configured. TRUE indicates that the UL
TION(Optional) UARFCN needs to be configured. FALSE indicates that the UL
MOD UARFCN need not be manually configured and it is
UCELLREDIREC automatically configured according to the relation between the
TION(Optional) UL and DL UARFCNs.
RedirSwitch BSC690 ADD Meaning: Whether the RRC redirection algorithm is valid for
0 UCELLREDIREC the specified service. The algorithm is valid only when the
TION(Optional) RRC direct redirection switch is enabled and when this
MOD parameter is set to ONLY_TO_INTER_FREQUENCY or
UCELLREDIREC ONLY_TO_INTER_RAT.
TION(Optional) - OFF indicates that RRC redirection is not allowed.
- Only_To_Inter_Frequency indicates that only RRC
redirection to inter-frequency cells is allowed.
- Only_To_Inter_Frequency indicates that only RRC
redirection to inter-RAT cells is allowed.
SeqOfUserR BSC690 ADD Meaning: This parameter indicates whether the MBMS service
el 0 UCELLOLC(Optio is released first or user first when the overload occurs.
nal)
GUI Value Range: MBMS_REL(MBMS service),
USER_REL(UE)
Actual Value Range: MBMS_REL, USER_REL
Unit: None
Default Value: MBMS_REL
SpucHeavy BSC690 ADD Meaning: It is used to decide whether the cell load level is
0 UCELLPUC(Opti "Heavy" or not. It is denoted by the ratio of NodeB TX power to
onal) the maximum TX power.
MOD If the load of a cell is equal to or higher than this threshold, the
UCELLPUC(Opti load level of this cell is heavy.
onal) If the load level of a cell is heavy, the PUC algorithm will
configure selection/reselection parameters for this cell to lead
the UE camping on this cell to reselect another inter-frequency
neighboring cell with light load.
SpucLight BSC690 ADD Meaning: It is used to decide whether the cell load level is
0 UCELLPUC(Opti "Light" or not. It is denoted by the ratio of NodeB TX power to
onal) the maximum TX power.
MOD If the load of a cell is equal to or lower than this threshold, the
UCELLPUC(Opti load level of this cell is light.
onal) If the load level of a cell is light, the PUC algorithm will
configure selection/reselection parameters for this cell to lead
the UE to reselect this cell rather than the previous
inter-frequency neighboring cell with heavy load.
TargetFreqT BSC690 ADD Meaning: RSCP Threshold for the target cell. This parameter
hdRscp 0 UCELLMCDRD( is used to estimate the signal quality of the periodic
Optional) reports.The DRD is triggered only when the signal quality of
MOD the target cell is higher than this parameter. If this parameter is
UCELLMCDRD( set to a greater value, it is difficult for subscribers to re-access
Optional) another cell with a higher priority; however, the re-attempt
success rate is high. If this parameter is set to a lower value, it
is easy for subscribers to re-access another cell with a higher
priority; however, the re-attempt success rate however is low.
Note: The threshold can be reached only when RSCP and
Ec/No of the target cell are above the RSCP and Ec/No that
are set in the command.
TenMsecFor BSC690 SET Meaning: DL basic common measurement report cycle. For
DlBasicMeas 0 ULDM(Mandatory detailed information of this parameter, refer to 3GPP TS
) 25.433.
TenMsecFor BSC690 SET Meaning: UL basic common measurement report cycle. For
UlBasicMeas 0 ULDM(Mandatory detailed information of this parameter, refer to 3GPP TS
) 25.433.
UlBasicCom BSC690 SET Meaning: L3 filtering coefficient. The larger the value of this
mMeasFilter 0 ULDM(Optional) parameter, the stronger the smoothing effect and the higher
Coeff the anti-slow-fading capability, but the lower the signal change
tracing capability. For detailed information of this parameter,
refer to 3GPP TS 25.433.
GUI Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9,
D11, D13, D15, D17, D19
Actual Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9,
D11, D13, D15, D17, D19
Unit: None
Default Value: D6
GUI Value Range: D8, D16, D32, D64, D128, D144, D256,
D384
Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
Unit: kbit/s
Default Value: D64
UlCacAvgFilt BSC690 SET Meaning: Length of smoothing filter window of uplink CAC.
erLen 0 ULDM(Optional)
GUI Value Range: 1~32
Actual Value Range: 1~32
Unit: None
Default Value: 5
UlCSInterRat BSC690 ADD Meaning: Number of users selected in a UL LDR CS domain
ShouldBeHO 0 UCELLLDR(Optio inter-RAT SHOULDBE load handover. The target subscribers
UeNum nal) of this parameter are the CS domain subscribers. Because the
MOD CS domain subscribers are session subscribers in general and
UCELLLDR(Optio they have little impact on load, you can set this parameter to a
nal) comparatively high value.
UlDcccRateT BSC690 SET Meaning: For a BE service that has a low maximum rate, the
hd 0 UDCCC(Optional) DCCC algorithm is not obviously effective yet it increases
algorithm processing. Thus, the traffic-based DCCC algorithm
is applied to BE services whose maximum UL rate is greater
than the threshold.
GUI Value Range: D8, D16, D32, D64, D128, D144, D256,
D384
Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
Unit: kbit/s
Default Value: D64
UlInterFreqH BSC690 ADD Meaning: The UE can be selected to process load handover
oBWThd 0 UCELLLDR(Optio only when its bandwidth is less than this threshold.
nal)
MOD GUI Value Range: 0~400000
UCELLLDR(Optio Actual Value Range: 0~400000
nal) Unit: bit/s
Default Value: 200000
UlInterFreqH BSC690 ADD Meaning: The inter-frequency neighboring cell could be
oCellLoadSp 0 UCELLLDR(Optio selected as the destination of load handover only when its load
aceThd nal) remaining space is larger than this threshold. The lower the
MOD parameter is, the easier it is to find a qualified target cell for the
UCELLLDR(Optio blind handover. Excessively small value of the parameter,
nal) however makes the target cell easily enter the congestion
status. The higher the parameter is, the more difficult it is for
the inter-frequency blind handover occurs.
UlLdrAvgFilte BSC690 SET Meaning: Length of smoothing filter window of uplink LDR.
rLen 0 ULDM(Optional)
GUI Value Range: 1~32
Actual Value Range: 1~32
Unit: None
Default Value: 5
UlLdrBERate BSC690 ADD Meaning: Number of RABs selected in a UL LDR BE traffic
ReductionRa 0 UCELLLDR(Optio rate reduction. In the actual system, this parameter can be set
bNum nal) on the basis of the actual circumstances. If the high-rate
MOD subscribers occupy a high proportion, set the parameter to a
UCELLLDR(Optio comparatively low value. If the high-rate subscribers occupy a
nal) low proportion, set the parameter to a comparatively high
value. Because the basic congestion control algorithm is
designed to slowly decrease cell load, you need to set this
parameter to a comparatively low value.
UlLdrCreditSf BSC690 ADD Meaning: Reserved SF threshold in uplink credit LDR. The
ResThd 0 UCELLLDR(Optio uplink credit LDR could be triggered only when the SF factor
nal) corresponding to the uplink reserved credit is higher than the
MOD uplink or downlink credit SF reserved threshold.
UCELLLDR(Optio
nal) GUI Value Range: SF4(SF4), SF8(SF8), SF16(SF16),
SF32(SF32), SF64(SF64), SF128(SF128), SF256(SF256)
Actual Value Range: SF4, SF8, SF16, SF32, SF64, SF128,
SF256
Unit: None
Default Value: SF8
UlLdrRelThd BSC690 ADD Meaning: If the ratio of UL load of the cell to the uplink capacity
0 UCELLLDM(Opti is lower than this threshold, the UL load reshuffling function of
onal) the cell is stopped. After the basic congestion state of the cell
MOD load is released, the system no longer implements the LDR
UCELLLDM(Opti action. Because the load fluctuates, the difference between
onal) the LDR release threshold and trigger threshold should be
higher than 10%. The ping-pong effect of the preliminary
congestion state may occur.
GUI Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9,
D11, D13, D15, D17, D19
Actual Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9,
D11, D13, D15, D17, D19
Unit: None
Default Value: D3
UlOlcRelThd BSC690 ADD Meaning: If the ratio of UL load of the cell to the uplink capacity
0 UCELLLDM(Opti is lower than this threshold, the UL overload and congestion
onal) control function of the cell is stopped. The value of the OLC
MOD release threshold should not be much lower than or close to
UCELLLDM(Opti the OLC trigger threshold, or the system state may have a
onal) ping-pong effect. The recommended difference between the
OLC release threshold and the OLC trigger threshold is higher
than 10%. It is desirable to set the two parameters a bit higher
given that the difference between OLC trigger threshold and
OLC release threshold is fixed.
UlOlcTraffRel BSC690 ADD Meaning: User release is an extreme method in reducing the
RabNum 0 UCELLOLC(Optio cell load and recovering the system when the cell is
nal) overloaded and congested.
MOD The mechanism of the OLC is that an action is performed in
UCELLOLC(Optio each [OLC period] and some services are selected based on
nal) the action rules to perform this action. This parameter defines
the maximum number of RABs released in executing uplink
OLC service release.
For the users of a single service, the releasing of RABs means
the complete releasing of the users. The releasing of RABs
causes call drops, so UlOlcFTFRstrctTimes or
DlOlcFTFRstrctTimes should be set to a low value. Higher
values of the parameter get the cell load to decrease more
obviously, but the QoS will be affected.
UlOlcTrigHys BSC690 SET Meaning: UL OLC trigger hysteresis.This parameter can avoid
t 0 ULDM(Optional) touching off OLC event continually.
UlOlcTrigThd BSC690 ADD Meaning: If the ratio of UL load of the cell to the uplink capacity
0 UCELLLDM(Opti is not lower than this threshold, the UL overload and
onal) congestion control function of the cell is triggered. The value
MOD of the OLC release threshold should not be much lower than or
UCELLLDM(Opti close to the OLC trigger threshold, or the system state may
onal) have a ping-pong effect. The recommended difference
between the OLC release threshold and the OLC trigger
threshold is higher than 10%. It is desirable to set the two
parameters a bit higher given that the difference between OLC
trigger threshold and OLC release threshold is fixed.
ZeroRateUp BSC690 SET Meaning: For the PS BE service at a rate of 0 kbit/s, this
FailToRelTim 0 UCOIFTIMER(Op parameter is used for the rate upsizing for DCCC triggered by
erLen tional) event 4A. Unsuccessful rate upsizing indicates that the
resources are insufficient in the cell. The service may run at a
rate of 0 kbit/s for a long time. If the timer is started, the 0 kbit/s
service of the UE is released after the timer expires. If the
length is set to 0, the timer is not started.
10 Counters
For details, see the BSC6900 UMTS Performance Counter Reference and the NodeB Performance
Counter Reference.
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
12 Reference Documents
[1] 3GPP TS 25.133: Requirements for Support of Radio Resource Management (FDD)
[2] 3GPP TS 25.215: Physical layer - Measurements (FDD)
[3] 3GPP TS 25.321: Medium Access Control (MAC) protocol specification
[4] 3GPP TS 25.331: Radio Resource Control (RRC)
[5] 3GPP TS 25.413: UTRAN Iu Interface RANAP Signaling
[6] AMR Feature Parameter Description
[7] DCCC Feature Parameter Description
[8] State Transition Feature Parameter Description
[9] MBMS Feature Parameter Description
[10] HSDPA Feature Parameter Description
[11] HSUPA Feature Parameter Description
[12] Transmission Resource Management Feature Parameter Description
[13] Handover Feature Parameter Description