Huawei - Load Control PDF
Huawei - Load Control PDF
RAN15.0
Feature Parameter Description
Issue Draft A
Date 2013-01-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: [email protected]
WCDMA RAN
Load Control Contents
Contents
1 About This Document ..............................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview......................................................................................................................................2-1
2.1 Load Control in Different Scenarios .............................................................................................. 2-1
2.2 Functions of Load Control ............................................................................................................. 2-1
2.3 Priorities Involved in Load Control ................................................................................................ 2-3
2.3.1 User Priority .......................................................................................................................... 2-3
2.3.2 Integrated RAB Priority ......................................................................................................... 2-4
2.3.3 Integrated User Priority......................................................................................................... 2-4
8 Load Reshuffling.......................................................................................................................8-1
8.1 Basic Congestion Triggering ......................................................................................................... 8-1
8.1.1 Power Resource ................................................................................................................... 8-1
8.1.2 Code Resource ..................................................................................................................... 8-2
8.1.3 Iub Resource ........................................................................................................................ 8-3
8.1.4 NodeB Credit Resource........................................................................................................ 8-3
8.2 LDR Procedure.............................................................................................................................. 8-3
8.3 LDR Actions ................................................................................................................................... 8-8
8.3.1 Load-based Inter-Frequency Handover ............................................................................... 8-8
8.3.2 BE Rate Reduction ............................................................................................................. 8-11
8.3.3 QoS Renegotiation for Uncontrollable Real-Time Services ............................................... 8-12
8.3.4 Inter-RAT Handover in the CS Domain .............................................................................. 8-12
8.3.5 Inter-RAT Handover in the PS Domain............................................................................... 8-13
8.3.6 AMR Rate Reduction .......................................................................................................... 8-13
8.3.7 Code Reshuffling ................................................................................................................ 8-14
8.3.8 MBMS Power Reduction .................................................................................................... 8-15
8.3.9 PS Inter-RAT Handover from UMTS to LTE ....................................................................... 8-15
8.3.10 LDR Actions of One UE in the Uplink and Downlink ........................................................ 8-16
11 Engineering Guidelines.......................................................................................................11-1
11.1 WRFD-021104 Emergency Call ................................................................................................ 11-1
11.1.1 Deployment ....................................................................................................................... 11-1
11.2 WRFD-010506 RAB Quality of Service Renegotiation over Iu Interface .................................. 11-1
11.2.1 Deployment ....................................................................................................................... 11-1
11.3 WRFD-020102 Load Measurement .......................................................................................... 11-3
11.3.1 Deployment ....................................................................................................................... 11-3
11.4 WRFD-020106 Load Reshuffling .............................................................................................. 11-5
11.4.1 Deployment ....................................................................................................................... 11-5
11.5 WRFD-020107 Overload Control .............................................................................................. 11-8
11.5.1 Deployment ....................................................................................................................... 11-8
11.6 WRFD-020108 Code Resource Management .......................................................................... 11-9
12 Parameters .............................................................................................................................12-1
13 Counters..................................................................................................................................13-1
14 Glossary ..................................................................................................................................14-1
15 Reference Documents .........................................................................................................15-1
Document Versions
The document issue is as follows:
Draft A (2013-01-30)
Draft A (2013-01-30)
This is a draft for RAN15.0.
Compared with issue 02 (2012-07-20) of RAN14.0, Draft A (2012-12-30) of RAN15.0 includes the
following changes.
Quantities"
10.6 "Anti-Imbalance of the Different
Antenna" in chapter 10 "Network Impact"
11.15 "Anti-Imbalance of the Different
Antenna" in chapter 11 "Engineering
Guidelines"
Optimized the RRC Redirection for Service Added the RedirEcN0Thd parameter
Steering feature. Added network impact and
engineering guidelines for this feature. For
details, see following sections:
5.2.4 "RRC Redirection for Service
RESERVED_SWITCH_0_BIT15
ReservedSwitch0:
RESERVED_SWITCH_0_BIT28
Added the WRFD-150236 Load Based Added the following parameters:
Dynamic Adjustment of PCPICH feature. NBMLdcAlgoSwitch:
For details, see following sections: DLLOAD_BASED_PCPICH_PWR_A
7.2.2 "Load Based Dynamic Adjustment of DJ_SWITCH
PCPICH" PcpichPwrDownDlLoadState
10.7 "WRFD-150236 Load Based PcpichPwrUpDlLoadState
Dynamic Adjustment of PCPICH"
FuncSwitch2:
11.19 "WRFD-150236 Load Based LOAD_BASED_PCPICH_PWR_ADJ
Dynamic Adjustment of PCPICH"
Added descriptions about the Macro & None
Micro Joint Inter-frequency Redirection
feature. For details, see 5.2.1 "Procedure of
IAC During RRC Connection Setup."
Updated descriptions about queuing and None
preemption for DB-HSDPA and 4C-HSDPA
services. For details, see section 5.6
"Preemption" and section 5.7 "Queuing."
Introduced the CE resource preemption Added the PreemptEnhSwitch:
2 Overview
The WCDMA system is a self-interfering system. As the load of the system increases, the interference
rises. A relatively high interference can affect the coverage of cells and QoS of established services.
Therefore, the capacity, coverage, and QoS of the WCDMA system are mutually affected. To solve these
problems, the load control function is introduced to control the load in a cell.
Load control aims to maximize the system capacity while ensuring coverage and QoS by controlling the
key resources, such as power, downlink channelization codes, channel elements (CEs), and Iub
transmission resources, which directly affect user experience.
Each cell has its own set of load control functions that are responsible for monitoring and controlling the
resources of the cell. The load control functions monitor the load condition of the cell through load
measurement, make the admission decision for services through intelligent access control and call
admission control, and relieve congestion in a cell.
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: Inter-Frequency Load Balancing Based on Configurable Load Threshold(CLB),
intra-frequency Load Balancing (LDB), Load Reshuffling (LDR), and Overload Control (OLC)
The following sections provide detailed information about the load control functions performed in the
different UE access phases.
-: 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.
OLC always uses the measured RTWP value no matter whether the RNC uses the measured RTWP value. For details
about OLC, see chapter 9 "Overload Control".
Downlink Transmitted Carrier Power (TCP)
Non-HSPA power: TCP excluding the power used for transmission on HSPA channels. For the detailed
information about HSPA channels, see HSDPA Feature Parameter Description and HSUPA Feature
Parameter Description.
Uplink minimum guaranteed load: sum of R99 service load, HSUPA service load required by the
HSUPA GBR, and control channel load. Measuring the uplink minimum guaranteed load depends on
the NodeB hardware.
The HSUPA GBR is calculated as follows:
− If the function uplink enhanced L2 is disabled, GBR = max (bit rate of one RLC PDU, GBR).
− If the function uplink enhanced L2 is enabled, GBR = max (bit rate of the smallest RLC PDU, GBR).
The NodeB measures the major quantities related to load control. After layer 1 and layer 3 filtering, the
measurement values are reported to the RNC through the COMMON MEASUREMENT REPORT
message.
The RNC performs smooth filtering of the measurement values reported from the NodeB and then
obtains the measurement values, which further serve as data input for the load control algorithms.
The RNC calculates the actual uplink load based on the filtered RTWP, uplink total load, and uplink
minimum guaranteed load. The actual uplink load is one of the factors for the uplink load-related
algorithms.
When one base station uses multiple antennas, these antennas may cause interference to each other. If antenna
interference is imbalanced or if some antennas become invalid, the measured RTWP and uplink load may be inaccurate.
In this situation, the anti-imbalance of the different antenna algorithm can be used to correct the inaccurate measurement
results and reflect the actual cell load. In this way, system capacity and network coverage can be better balanced. This
algorithm helps address shrinking uplink coverage and reduced system capacity in multi-antenna scenarios.
Uplink load measurement involves the measurement of RSEPS, uplink total load, and uplink minimum guaranteed load.
The anti-imbalance of the different antenna algorithm is controlled by the ANTIANTENNAIMBALANCESW parameter on
the NodeB side.
In Figure 3-2:
A is the sampling value of the measurement.
B is the measurement value after layer 1 filtering.
C is the measurement value after layer 3 filtering.
C' is another measurement value (if any) for measurement evaluation.
where
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.
− For
load control algorithms (excluding OLC), k is specified by the UlBasicCommMeasFilterCoeff or
DlBasicCommMeasFilterCoeff parameter.
− For OLC 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.
Table 3-1 The smooth window length parameters for setting different functions
Function Smooth Window Length Parameter
PUC PucAvgFilterLen
CAC UlCacAvgFilterLen
DlCacAvgFilterLen
LDB LdbAvgFilterLen
LDR UlLdrAvgFilterLen
DlLdrAvgFilterLen
OLC UlOlcAvgFilterLen
DlOlcAvgFilterLen
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.
CLB measurements have the same smooth window length with LDR.
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 uplink total load measurement depends on the NodeB hardware. For details, see section 3.1 "Load-related
Measurement Quantities" When the uplink total load measurement is invalid, background noise update is not performed.
The initial value of the filter is set to the current background noise.
4. The RNC do the following:
(a). The RNC determines whether the current Equivalent Number of Users (ENU) in the cell is greater
than the value of BGNEqUserNumThd:
− Ifthe current ENU is greater than the value of BGNEqUserNumThd, the RNC infers that Mn includes
other noises in addition to the background noise, and therefore it does not feed Mn to the filter. In
addition, the RNC sets the counter to zero, retains the current background noise, and sets the initial
value of the filter to the current background noise. The background noise update procedure ends.
The RNC waits for the next RTWP measurement value and uplink total load measurement value.
− Ifthe current ENU in the cell is smaller than or equal to the value of BGNEqUserNumThd, the RNC
feeds Mn to the filter and performs the next step.
(b). The RNC determines whether the uplink total load measurement value is greater than the value
of BGNULLoadThd:
− If the latest uplink total load measurement value is greater than the value of BGNULLoadThd, the
RNC sets the counter to zero, retains the current background noise, and sets the initial value of the
filter to the current background noise. The background noise update procedure ends. The RNC waits
for the next RTWP measurement value and uplink total load measurement value.
− If the latest uplink total load measurement value is smaller than or equal to the value of
BGNULLoadThd, the RNC feeds Mn to the filter and performs the next step.
5. The RNC checks whether |Mn - Fn-1| is smaller than the value of BgnAbnormalThd. If it is smaller
than this threshold value, the RNC increments the counter by one, calculates Fn according to the
Alpha filter formula, and performs the next step. Otherwise, the RNC waits for the next RTWP
measurement value.
6. The RNC checks whether the counter reaches the counting threshold. If it reaches the counting
threshold, the RNC performs the next step. Otherwise, the RNC waits for the next RTWP
measurement value.
7. The RNC checks whether |Fn - BackgroundNoise| is smaller than the value of BgnAbnormalThd.
The purpose is to prevent burst interference and RTWP spike. If it is smaller than the value of
BgnAbnormalThd, the RNC performs the next step. Otherwise, the RNC sets the counter to zero
and waits for the next RTWP measurement value.
8. The RNC checks whether |Fn - current background noise| is greater than the value of
BgnUpdateThd. The purpose is to prevent frequent background noise upgrades on the Iub interface.
If it is greater than the value of BgnUpdateThd, the RNC sets the current background noise to Fn,
sets the counter to zero, and waits for the next RTWP measurement value. Otherwise, the RNC sets
the counter to zero and waits for the next RTWP measurement value.
----End
The PUC function is enabled only when the PUC sub-parameter 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:
− If
the load of the two cells is higher than their upper thresholds (SpucHeavy) plus their load level
division hysteresis (SpucHyst), the load of the cell group is considered heavy.
− If
the load of the two cells is lower than their lower thresholds (SpucLight) minus their load level
division hysteresis (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
Heavy, normal, or light Heavy Heavy
Normal Normal, or light Normal
Normal, or light Normal Normal
Light Light Light
The states of a cell load are heavy, normal, and light, as shown in Table 4-1.
Table 4-1 Cell load states
Depending on the load status of the serving cell, the cell reselection variable Sintersearch is adjusted up
or down or kept unchanged. Changes to the variable Sintersearch are made as shown in Table 4-3.
Table 4-3 Changes made to Sintersearch according to the load state
Load State of the S'intersearch Change to Sintersearch
Serving Cell
Light S'intersearch = Sintersearch + OffSinterLight
Normal S'intersearch = Sintersearch →
Heavy S'intersearch = Sintersearch + OffSinterHeavy
The configurations of Qoffset1 and Qoffset2 are related to the load of the serving cell and the load of the
neighboring cells. Changes to Qoffset1 and Qoffset2 are made as shown in Table 4-4.
Table 4-4 Changes made to Qoffset1 and Qoffset2 according to the load state
Load State of Load State Q'offset1 Change Q'offset2 Change
the of the to to
Neighboring Serving Qoffset1 Qoffset2
Cells Cell
Light Light Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
Light Normal Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
Light Heavy Q'offset1 = Qoffset1 Q'offset2 = Qoffset2
+ OffQoffset1Light + OffQoffset2Light
Normal Light Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
Normal Normal Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
Normal Heavy Q'offset1 = Qoffset1 Q'offset2 = Qoffset2
+ OffQoffset1Light + OffQoffset2Light
Heavy Light Q'offset1 = Qoffset1 Q'offset2 = Qoffset2
+ OffQoffset1Heavy +
OffQoffset2Heavy
Heavy Normal Q'offset1 = Qoffset1 Q'offset2 = Qoffset2
+ OffQoffset1Heavy +
OffQoffset2Heavy
Heavy Heavy Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
The prerequisite for changing the preceding parameters is that these parameters should be in their default values.
As shown in Figure 5-1, the procedure for 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. RRC redirection based on distance (only for UE-originating AMR services). For details, see section
5.2.3 "Inter-RAT 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. RRC redirection for service steering. For details, see section 5.2.4 "RRC Redirection for Service
Steering."
− If
the 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 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, see section 5.2 "IAC During RRC Connection Setup."
During the RAB connection processing, the RNC performs the following steps:
3. Performs inter-frequency DRD to select a suitable cell for service steering or load balancing. For
details about DRD, see Directed Retry Decision Feature Parameter Description.
4. Performs rate negotiation according to the service requested by the UE. For details, see section 5.4
"Rate Negotiation at Admission Control."
5. 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 Call
Admission Control Feature Parameter Description.
6. Selects a suitable cell, according to the inter-frequency DRD, from the cells where no admission
attempt has been made, and then performs step 7. If all the attempts fail, the RNC performs the next
step.
7. 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.
8. Makes a preemption attempt. For details about preemption, see section 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.
9. Makes a queuing attempt. For details about queuing, see section 5.7 "Queuing."
10. ." If the queuing is successful, UE access is granted. If the queuing fails or is not supported, the RNC
performs the next step.
11. Performs low-rate access. For details about low-rate access, see section 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.
12. 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.
DCH √ √ √ √ √ √ √ √ √
HSUPA - √ √ √ √ √ √ √ -
HSDPA - √ √ - - √ √ √ -
Inter-RAT RRC redirection based on weak coverage is controlled by the switch PerfEnhanceSwitch:
PERFENH_RRC_WEAK_REDIR_SWITCH, not by the switch DrSwitch: DR_RRC_DRD_SWITCH.
After receiving an RRC CONNECTION REQUEST message from the UE, the RNC performs inter-RAT
RRC redirection based on weak coverage when PERFENH_RRC_WEAK_REDIR_SWITCH under the
PerfEnhanceSwitch parameter is selected. If this check box is not selected, the RNC performs the RRC
redirection based on distance (only for UE-originating AMR services). For details, see section 5.2.3
"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 and Macro & Micro Joint
Inter-Frequency Redirection 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.
− If
the 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 six algorithms:
Inter-RAT RRC Redirection Based on Distance
Inter-Frequency RRC Redirection Based on Distance
RRC Redirection for Service Steering
Macro & Micro Joint Inter-frequency Redirection
RRC DRD
RRC Redirection After DRD Failure
Before enabling the six algorithms, turn on the DrSwitch: DR_RRC_DRD_SWITCH.
For details about the Macro & Micro Joint Inter-Frequency Redirection feature, see HetNet Co-Carrier Coordination Phase
1Feature Parameter Description.
− If
PERFENH_RRC_WEAK_REDIR_SWITCH under the PerfEnhanceSwitch parameter is not
selected, the RNC does not perform inter-RAT RRC redirection based on weak coverage. The RRC
connection setup request is then processed in the current cell.
− If
PERFENH_RRC_WEAK_REDIR_SWITCH under the PerfEnhanceSwitch parameter is selected,
the procedure goes to the next step.
2. The RNC obtains the Ec/N0 value of the current cell from the RACH Measurement Report IE in the
RRC CONNECTION REQUEST message.
− If
the Ec/N0 value is greater than or equal to the value of WeakCovRrcRedirEcNoThs, the RNC
does not perform inter-RAT RRC redirection based on weak coverage. The RRC connection setup
request is then processed in the current cell.
− If
the Ec/N0 value is smaller than the value of WeakCovRrcRedirEcNoThs, the procedure goes to
the next step.
3. 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 or the IE "RACH Measurement Report" does not contain the
Ec/N0 value, inter-RAT RRC redirection based on weak coverage is not performed.
− If
the cell is in the normal state, the RNC generates a random value ranging from 0 to 1 and
compares the value with the RedirFactorOfNorm 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 Inter-RAT 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 Inter-RAT 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.
The frequency information carried in the message can be set by running the SET UREDIRECTION command.
SCellLoadBsdRedirSwitch is effective when RedirSwitch is set to ONLY_TO_INTER_FREQUENCY.
The calculation method for the uplink/downlink power load of a cell is the same as that for the power load in the load
reshuffling algorithm.
− If RedirSwitch is set to ONLY_TO_INTER_RAT, the RNC performs the next step.
3. Based on the cell load and the redirection factors, the RNC decides whether to perform RRC
redirection for service steering.
− If
the cell is in the normal state, the RNC generates a random number between 0 and 1 and
compares it with the corresponding unconditional redirection factor (RedirFactorOfNorm). If the
random number is smaller than this factor, the RNC performs the next step. Otherwise, the RNC
handles the RRC connection setup request of the UE in the current cell.
− If
the cell is in the basic congestion or overload state, the RNC generates a random number between
0 and 1 and compares it with the value of RedirFactorOfLDR. If the random number is smaller than
this factor, the RNC performs the next step. Otherwise, the RNC handles the RRC connection setup
request of the UE in the current cell.
4. When RedirBandInd is set to a value ranging from Band1 to Band9, the RNC takes the following
actions:
− If
the measured CPICH Ec/N0 is contained in the RRC CONNECTION REQUEST message and the
value of CPICH Ec/N0 is larger than or equal to the value for RedirEcN0Thd, the RNC proceeds with
the next step. If the value of CPICH Ec/N0 is smaller than the value for RedirEcN0Thd, the RNC
processes the RRC CONNECTION REQUEST message in the current cell.
− If
the measured CPICH Ec/N0 is not contained in the RRC CONNECTION REQUEST message, the
RNC proceeds with the next step.
When RedirSwitch is set to ONLY_TO_INTER_FREQUENCY and RedirBandInd is set to
DependOnNCell, the target cell must be an intra-band inter-frequency cell under the same RNC with
the current cell and BlindHoFlag for the target cell is set to TRUE.
− If
a cell in the inter-frequency neighboring cell list meets the preceding requirements, the RNC
determines whether this neighboring cell is in the OLC state.
a. If this neighboring cell is in the OLC state, it cannot be the target cell of the UE. If all the
neighboring cells are in the OLC state, the RNC processes the RRC CONNECTION REQUEST
message in the current cell.
b. If this neighboring cell is not in the OLC state, the RNC proceeds with the next step.
− If
all the cells in the inter-frequency neighboring cell list do not meet the preceding requirements, the
RNC processes the RRC CONNECTION REQUEST message in the current cell.
If parameter settings do not meet the requirements in this step, the RNC skips this step and proceeds with the next step.
5. The RNC performs RRC redirection.
− 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.
− If
RedirSwitch is set to ONLY_TO_INTER_RAT, the RNC sends an RRC CONNECTION REJECT
message to the UE, redirecting the UE to inter-RAT neighboring cells carried in the message.
Identified Reference IE
Service
Type Establishment cause Domain Call type UE capability Access stratum
indicator indication release indicator
Call
AMR/VP Originating Conversational N/A N/A N/A R99
Call REL-4
Terminating Conversational REL-5
Call
VP Originating Conversational CS domain Video N/A REL-6
Call REL-7
Terminating Conversational
Call
PS R99 Originating Interactive Call N/A N/A N/A R99
Originating Background Call REL-4
Terminating Interactive Call
Terminating Background Call
PS R99 Originating Interactive Call PS domain N/A Not HS-DSCH REL-6
Originating Background Call or HS-DSCH REL-7
Terminating Interactive Call +E-DCH
Terminating Background Call
PS HSPA Originating Interactive Call PS domain N/A HS-DSCH or REL-6
Originating Background Call HS-DSCH REL-7
Terminating Interactive Call +E-DCH
Terminating Background Call
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.
UEs of REL-5 and earlier versions do not carry the Domain indicator, Call type, or UE capability indication IEs.
Therefore, the RNC cannot differentiate between AMR services and VP services. The RNC implements VP service
redirection the same way it implements AMR service redirection.
When the RRC DRD fails, the RNC performs RRC redirection as follows:
The RNC selects another frequency for redirection based on the setting of the ReDirBandInd parameter.
If the ReDirBandInd parameter is set to a specific band, the RNC selects the configured target
frequency number and redirects the UE. The target frequency number is configured by the following
parameters: ReDirUARFCNUplinkInd, ReDirUARFCNUplink, ReDirUARFCNDownlink.
If the ReDirBandInd parameter is set to DependOnNCell, the RNC selects the target frequency number
from the target frequency numbers corresponding to the intra-band inter-frequency neighboring cells of
the current cell. In addition, the RNC excludes the target frequency numbers corresponding to the cells
that have carried out inter-frequency RRC DRD attempts.
If more than one target frequency number is available, the RNC selects a target frequency number
randomly. Then, the RNC sends an RRC CONNECTION REJECT message to the UE, redirecting the
UE to the selected target frequency carried in the message.
If no target frequency number is available, the RNC continues to perform RRC redirection according to
the setting of the ConnectFailRrcRedirSwitch parameter.
− If ConnectFailRrcRedirSwitch is set to Only_To_Inter_Frequency, the RRC connection setup fails.
− If
ConnectFailRrcRedirSwitch is set to Allowed_To_Inter_RAT and there is a neighboring GSM cell,
the RNC sends the information about the neighboring GSM cell to the UE and redirects the UE to
GSM system. If ConnectFailRrcRedirSwitch is set to Allowed_To_Inter_RAT but there is no
neighboring GSM cell, the UE automatically searches for GSM cells and then selects one of them for
RRC connection setup attempts.
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 PS_STREAM_IU_QOS_NEG_SWITCH sub-parameter of the PsSwitch parameter is set to 0, the
GBR negotiation will be not performed. In such a case, the GBR contained in the IE "RAB Parameters"
of the RAB ASSIGNMENT REQUEST message is used.
For details about GBR negotiation, see 3GPP 25.413.
If the DCCC function is enabled and the PS_RAB_Downsizing_Switch sub-parameter 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.
The PS BE service mentioned in this section can be the single PS BE service or the PS BE service in combined services.
signaling load increases, and the CS call drop rate may also increase. The initial rate negotiation
function is recommended when most PS BE services in CS+PS combined services have low data
transmission requirements.
The BeInitBitrateTypeforCsPs parameter specifies the bearing policy for the PS BE service and the
initial rate for the PS BE service when the UE is in the CELL_DCH state or transitions to this state.
BeInitBitrateTypeforCsPs applies only to the PS BE service in CS+PS combined services in the
following scenarios:
Scenario 1: The UE is in the CELL_DCH state and is processing CS services or CS+PS combined
services (any PS service). Then, the UE initiates PS BE services.
Scenario 2: The UE is in the CELL_DCH state and is processing PS BE services. Then, the UE
initiates CS services.
Scenario 3: The UE is in the CELL_FACH state and is processing PS BE services. Then, the UE
initiates CS services. (The UE must transition to the CELL_DCH state before establishing CS
services.)
Scenario 4: The UE is in the CELL_PCH state and is processing PS BE services. Then, the UE
initiates CS services. (The UE must transition to the CELL_FACH or CELL_DCH state before
establishing CS services.)
This section describes the initial rate negotiation function only for the PS BE service in CS+PS combined services in the
preceding scenarios. For details about the initial rate negotiation function for the PS BE service in other scenarios, see
"Initial Rate Definition for DCH Services" and "Initial Rate Definition for HSPA Services".
The BeInitBitrateTypeforCsPs parameter can be set to OFF, DCH 0k, DCH 8k, or DCH 8k/HSDPA.
OFF: indicates that the initial rate negotiation function is disabled for the PS BE service in CS+PS
combined services in the preceding scenarios.
DCH 0k: indicates that both the initial uplink and downlink rates for the DCH are 0 kbit/s.
DCH 8k: indicates that both the initial uplink and downlink rates for the DCH are 8 kbit/s.
DCH 8k/HSDPA: indicates that the initial uplink rate for the DCH is 8 kbit/s and that downlink services
are carried on HSDPA channels.
The implementation of the initial rate negotiation function for the PS BE service in CS+PS combined
services varies depending on the protocol version that the UE complies with.
For UEs complying with versions later than 3GPP Release 5
− If
the BeInitBitrateTypeforCsPs parameter is not set to OFF and the following switches are turned
off:
ReservedSwitch0: RESERVED_SWITCH_0_BIT11
ReservedSwitch0: RESERVED_SWITCH_0_BIT15
ReservedSwitch0: RESERVED_SWITCH_0_BIT28
Then, the initial uplink and downlink rates for the PS BE service in CS+PS combined services are as
listed in Table 5-4.
Table 5-4 Initial uplink and downlink rates for the PS BE service in CS+PS combined services
Value of Initial Uplink and Downlink Rates for the PS BE Service
BeInitBitrateTypeforCsPs
DCH 0k DCH 0 kbit/s
DCH 8k DCH 8 kbit/s
Table 5-7 Initial uplink and downlink rates for the PS BE service in CS+PS combined services
Setting of ReservedSwitch0: Value of Initial Uplink and Downlink Rates
RESERVED_SWITCH_0_BIT14 BeInitBitrateTypeforCs for the PS BE Service
Ps
1 DCH 0k DCH 0 kbit/s
1 DCH 8k DCH 0 kbit/s
1 DCH 8k/HSDPA DCH 0 kbit/s
0 DCH 0k DCH 0 kbit/s
0 DCH 8k DCH 8 kbit/s
0 DCH 8k/HSDPA DCH 8 kbit/s
Versions earlier than 3GPP Release 5 support neither HSDPA nor HSUPA. If ReservedSwitch0:
RESERVED_SWITCH_0_BIT28 is turned on, the initial uplink and downlink rates for the PS BE service in CS+PS
combined services are as listed in Table 5-7.
If ReservedSwitch0: RESERVED_SWITCH_0_BIT28 is turned off, the initial uplink and downlink rates for the PS BE
service in CS+PS combined services are as listed in Table 5-8.
Table 5-8 Initial uplink and downlink rates for the PS BE service in CS+PS combined services
Value of Initial Uplink and Downlink Rates for the PS BE Service
BeInitBitrateTypeforCsPs
DCH 0k DCH 0 kbit/s
DCH 8k DCH 8 kbit/s
DCH 8k/HSDPA DCH 8 kbit/s
Table 5-9 Initial uplink and downlink rates for the PS BE service in CS+PS combined services
Value of Initial Uplink and Downlink Rates for the PS BE Service
BeInitBitrateTypeforCsPs
DCH 0k DCH 0 kbit/s
DCH 8k DCH 8 kbit/s
DCH 8k/HSDPA DCH 8 kbit/s
− Inscenario 1, BeInitBitrateTypeforCsPs can be set to DCH 0k, DCH 8k, or DCH 8k/HSDPA. The
initial uplink rate for the PS BE service is 8 kbit/s, and downlink services are carried on HSDPA
channels.
− In
scenario 4, when ReservedSwitch0: RESERVED_SWITCH_0_BIT28 is turned on, the initial
uplink and downlink rates for the PS BE service in CS+PS combined services are as listed in Table
5-10.
Table 5-10 Initial uplink and downlink rates for the PS BE service in CS+PS combined services
Setting of ReservedSwitch0: Value of Initial Uplink and Downlink Rates
RESERVED_SWITCH_0_BIT14 BeInitBitrateTypefor for the PS BE Service
CsPs
1 DCH 0k, DCH 8k, DCH 0 kbit/s
DCH 8k/HSDPA
0 DCH 0k DCH 0 kbit/s
0 DCH 8k, DCH DCH 8 kbit/s
8k/HSDPA
The CAC performs the admission decision based on resources such as code resource, power resource,
NodeB credit, and Iub resource. In the case of HSPA resource request, the admission decision is also
based on the number of HSPA users. The admission succeeds only when the resource on which CAC is
based is available.
For details about CAC, see Call Admission Control Feature Parameter Description.
5.6 Preemption
Common Preemption
This section describes the preemption 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 an 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. That is,
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:
Setup or modification of a service
Hard handover or SRNS relocation
UE state transition from CELL_FACH to CELL_DCH
The preemption procedure is as follows:
1. The RNC selects the target cell for preemption.
− Formulti-carrier services (such as DC-HSDPA, DB-HSDPA, 4C-HSDPA, or DC-HSUPA services), the
RNC selects the primary cell in the DC-HSDPA, DB-HSDPA, 4C-HSDPA, or DC-HSUPA cell group as
the target cell.
− Fornon-multi-carrier services, the RNC selects the cell with the highest service priority or lightest
load as the target cell.
2. The preemption algorithm determines the radio link sets to be preempted.
a. Selects SRNC UEs first. If no UEs under the SRNC are available, the algorithm selects UEs under
the DRNC.
b. Sorts the preemptable UEs by integrated user priority, or sorts the preemptable RABs by integrated
RAB priority.
c. Determines candidate UEs or RABs.
For RABs of streaming or BE services, if PriorityReference is set to Traffic Class and
PreemptRefArpSwitch is set to ON, only the ones with lower ARP priority than the RAB to be
established are selected.
For multi-carrier services, only the resource of UEs that use the target cell as the primary cell is
preemptable.
Select as many users or RABs as necessary in order to match the resources needed by the RAB to be
established. When the priorities of two users or RABs are the same, the algorithm selects the user or
RAB that can release the most resources.
Preemptable users or RABs must have lower priorities than RABs to be established. The type of
preemptable user or RAB varies, depending on the type of resources that triggers the preemption.
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.
For CS RABs with the preemption capability, the PsBERrcPreemptVulnerable parameter specifies
whether RRCs can be preempted when there are no RABs to be preempted.
− If
PsBERrcPreemptVulnerable is set to ON, the RRCs whose service request type is the PS BE
service and RABs have not been set up can be preempted by CS RABs.
− If PsBERrcPreemptVulnerable is set to OFF, RRCs cannot be preempted.
RRCs do not have preemption attributes or priorities. Therefore, preemption attributes and priorities are not considered
during the preemption.
3. The RNC releases the resources occupied by the candidate users, RABs, or RRCs.
4. The requested service directly uses the released resources to access the network without an
admission decision.
For details about preemption of MBMS services, see MBMS Feature Parameter Description.
Emergency calls take priority over other common users and therefore can preempt all non-emergency
services. The common preemption procedure can be performed regardless of the setting for
PreemptAlgoSwitch.
When NbmWpsAlgorithmSwitch is set to ON, the wireless priority service (WPS) function is enabled.
In such a case, the WPS users can trigger common preemption regardless of the setting for
PreemptAlgoSwitch. WPS users take priority over emergency call users.
WPS is a National Security/Emergency Preparedness (NS/EP) voice service managed by the USA government. The
National Communications System (NCS) is authorized to manage the execution of the WPS project. The
NbmWpsAlgorithmPriority parameter specifies the WPS user priority.
When enabling the common preemption function, the CE resource preemption enhancement function must also be
enabled (controlled by PREEMPT_ENH_NODEB_PREEMPT_CE_SWITCH under the PreemptEnhSwitch parameter).
When CE resource admission fails due to insufficient CE resources, the CE resource preemption enhancement function
can be triggered on the NodeB side to ensure the CE resource preemption success rate. However, this function may
occupy CE resources reserved for RRC connection setups and handovers, reducing the handover success rate and
RRC connection setup success rate. This function does not affect the handover success rate and access success rate
of the preempting UEs. The probability of the handover success rate and access success rate being reduced is low.
Therefore, this function does not affect the performance of the live network.
Forced Preemption
Common preemption requires that RABs have been set up or are being set up for preempting users and
that preempting users have higher priorities than preemptable users. Therefore, CS services cannot
trigger preemption in the RRC connection setup phase. Even in the RAB-related phases, CS services
may fail to preempt PS services because of insufficient priorities. When PS traffic volume is high and
radio resources are insufficient, the success rate for CS service setup may decrease. To solve this
problem, forced preemption is introduced. This function ensures preferred access of AMR services and a
high success rate for AMR service setup.
After forced preemption is enabled, only CS conversational services can trigger preemption and only PS BE service
resources can be preempted.
The forced preemption function is controlled by the following switches under the PreemptEnhSwitch
parameter:
PREEMPT_ENH_CSRRC_PREEMPT_PS_SWITCH: indicates whether CS services can preempt PS
service resources during the CS RRC connection setup procedure.
PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH: indicates whether CS services can preempt PS
BE service resources during the CS RAB-related procedures.
The following table describes how these two switches determine preemption.
Table 5-11 How these two switches determine preemption
PREEMPT_ENH_CSRA PREEMPT_ENH_CSRRC RRC Connection RAB-Related Phases
B_PREEMPT_PS_SWIT _PREEMPT_PS_SWITCH Setup Phase
CH
On Off CS conversational If RAB admission for CS
services cannot conversational services
preempt PS BE fails, PS BE service
service resources. resources can be
preempted unconditionally.
On On If RRC admission for If RAB admission for CS
CS conversational conversational services
services fails, PS BE fails, PS BE service
service resources can resources can be
be preempted preempted unconditionally.
unconditionally.
Off On If RRC admission for Common preemption is
CS conversational performed. That is, Service
services fails, Priorities and the
resources of PS BE Pre-emption Capability and
services whose Pre-emption Vulnerability
Pre-emption IEs determine whether to
Vulnerability IE is set perform preemption.
to "pre-emptable" can
be preempted.
Off Off CS conversational Common preemption is
services cannot performed. That is, Service
preempt PS BE Priorities and the
service resources. 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.
When a UE transits to the CELL_DCH state from the URA_PCH or CELL_PCH state due to a CS service
request, the RNC implements the policy of forced preemption based on the setting of
CsP2DPreemptSwitch.
If CsP2DPreemptSwitch is set to OFF, the CS service request does not support preemption during a
transition from the URA_PCH or CELL_PCH state to the CELL_DCH state.
If CsP2DPreemptSwitch is set to ON, the CS service can preempt only PS BE services during a
transition from the URA_PCH or CELL_PCH state to the CELL_DCH state, regardless of the
preemption attributes and priorities of the CS and PS BE services.
If there is no PS BE services to preempt, forced preemption is implemented and the RRCs for PS BE
services are preempted when PsBERrcPreemptVulnerable is set to ON. Otherwise, preemption fails.
For details about preemption of RRCs for PS BE services, see "Common Preemption" in section 5.6
"Preemption."
When enabling the forced preemption function, the CE resource preemption enhancement function must also be enabled
(controlled by PREEMPT_ENH_NODEB_PREEMPT_CE_SWITCH under the PreemptEnhSwitch parameter). When CE
resource admission fails due to insufficient CE resources, the CE resource preemption enhancement function can be
triggered on the NodeB side to ensure the CE resource preemption success rate. However, this function may occupy CE
resources reserved for RRC connection setups and handovers, reducing the handover success rate and RRC connection
setup success rate. This function does not affect the handover success rate and access success rate of the preempting
UEs. The probability of the handover success rate and access success rate being reduced is low. Therefore, this function
does not affect the performance of the live network.
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 an 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.
Multi-carrier services (such as DC-HSDPA, DB-HSDPA, 4C-HSDPA, or DC-HSUPA services) requested by the UE are
waiting to be processed in the primary cell.
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 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 after the
timer expires, the service is released, and the connection is also released for a single service.
If no data is transmitted for some time after the access, the UE state changes to another state. For
details about state transition, see State Transition Feature Parameter Description.
To guarantee successful access of emergency calls, the RNC takes special measures for emergency
calls.
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 section 5.6 "Preemption."
If the CAC function switch is off, the emergency calls are directly admitted.
For hard resources (that is, code, Iub, and CE), the resource-based admission is successful if the
current remaining resources are sufficient for the request.
3. The RNC selects a user with the lowest priority for the CLB inter-frequency handover and checks the
number of selected users.
− If
the number of selected users is lower than or equal to the value of the MaxUserNumforCLBIFHO
parameter, the procedure proceeds to the next step.
− If
the number of selected users is larger than the value of the MaxUserNumforCLBIFHO parameter,
the RNC waits for the next CLB period specified by the ClbPeriodTimerLen parameter and then
returns to step 2.
For details about user selection for a CLB inter-frequency handover, see section 6.3 "User Selection
for a CLB Inter-Frequency Handover."
4. The RNC selects the target cell or cells of a CLB inter-frequency handover for the selected users. For
details, see section 6.4 "Target Cell Selection for a CLB Inter-Frequency Handover."
5. When the NCovCMUserNumCtrlSwitch parameter is set to ON, the RNC checks the number of
users in compressed mode with spreading factor (SF)/2 reduction.
− If
the number of users in compressed mode with SF/2 reduction in the cell is lower than
CellSFCMUserNumThd, the procedure proceeds to the next step.
− If
the number of users in compressed mode with SF/2 reduction in the cell is larger than or equal to
CellSFCMUserNumThd, the RNC waits for a CLB period specified by the ClbPeriodTimerLen
parameter and then returns to step 2.
The first CLB period starts when a cell enters the CLB state.
6. The RNC performs inter-frequency measurements and handovers. For details, see section 6.5
"Inter-Frequency Measurements and Handovers." After the handovers are complete, the procedure
proceeds to 4.
If the uplink or downlink load on the power resource, code resource, or CE resource is higher than the
corresponding CLB triggering threshold listed in Table 6-2 for a period specified by the
UlLdTrnsHysTime or DlLdTrnsHysTime parameter, the cell enters the CLB state and the RNC
performs inter-frequency measurements and handovers towards the target cell. If the uplink or downlink
load on the power resource, code resource, or CE resource is lower than the corresponding CLB
Set the CLB releasing threshold to a value smaller than the CLB triggering threshold. It is recommended
that the difference value (in unit of %) be greater than or equal to 10.
The CLB state triggered by a CS service or the CS and PS combined services is referred to as the CS
CLB state, and the CLB state triggered by a PS service is referred to as the PS CLB state. Details are as
follows:
If the cell is in the CS CLB state, which means that the uplink or downlink cell load on the power
resource, code resource, or CE resource is higher than the CS CLB triggering threshold for a period
specified by the UlLdTrnsHysTime or DlLdTrnsHysTime parameter, the RNC selects the users
performing CS services.
For CS and PS combined services, the RNC determines their CS CLB state the same way it does with CS services.
If the cell is in the PS CLB state, which means that the uplink or downlink cell load on the power
resource, code resource, or CE resource is higher than the PS CLB triggering threshold for a period
specified by the UlLdTrnsHysTime or DlLdTrnsHysTime parameter, the RNC selects the users
performing PS services.
If the cell is in the CS and PS CLB states simultaneously, the RNC selects both the users performing
CS services and the users performing PS services.
Figure 6-2 shows the process for triggering and releasing the CLB state.
The RNC performs periodic CLB checks, checking whether the cells are in the CLB state. The period of
a CLB check is specified by the ClbPeriodTimerLen parameter.
If the current UL/DL load is higher than or equal to the UL/DL CLB triggering threshold for a hysteresis
time (UlLdTrnsHysTime/DlLdTrnsHysTime), the cell is in the CLB congestion state and the related
CLB actions are triggered.
If the current UL/DL load is lower than the UL/DL LDR releasing threshold for a hysteresis time
(UlLdTrnsHysTime / DlLdTrnsHysTime), the cell enters the normal state.
When a cell enters the CLB state, the RNC selects users for inter-frequency measurements based on
the following conditions:
The RNC selects users that support one of the frequencies used by the inter-frequency neighboring
cells whose CLBFlag is TRUE.
The RNC selects users based on the CLB state of a cell.
− If the cell is in the CS CLB state, the RNC selects the users performing CS services.
− If the cell is in the PS CLB state, the RNC selects the users performing PS services.
− If
the cell is in the CS and PS CLB states simultaneously, the RNC selects both the users performing
CS services and the users performing PS services.
The RNC selects users with a bandwidth smaller than or equal to the bandwidth upper limit.
The bandwidth of UEs processing non-HSPA services and HSPA CS AMR services is their current rate,
and the bandwidth of UEs processing HSPA PS BE services and streaming services is the GBR. The
parameters related to the bandwidth limit are UlInterFreqHoBWThd and DlInterFreqHoBWThd.
The RNC does not select DC-HSDPA users.
The RNC can select DC-HSUPA users whose primary cell is in the CLB state.
The RNC selects gold users only when the GoldUserLoadControlSwitch parameter is set to ON.
Then, the RNC sorts the selected users by integrated user priority in ascending order. The RNC selects
users with lower priorities first and then users with higher priorities. For users having the same integrated
priority, a user is randomly selected. The maximum number of selected users is specified by the
MaxUserNumforCLBIFHO parameter. For details about the integrated user priority, see section 2.3.3
"Integrated User Priority."
− From the candidate cells, the RNC selects a cell or cells with the highest priority as the target cell or
cells based on the CLB-capable neighboring cell priority (CLBPrio).
− When the reference user speed optimization switch (UESpdOptSwitch) is set to ON, high-speed
users cannot be handed over to a micro cell. For details on how to identify high-speed users, see
Handover Feature Parameter Description.
The CellLoadBalanceRange parameter is set to ONLY_TO_INTER_RNC, and
SepRNCNCellLoadEstSwitch is set to ON.
The RNC can identify the CLB state of the inter-RNC neighboring cell only by the "high load cell" mark. If the
SepRNCNCellLoadEstSwitch parameter is set to OFF, the RNC does not identify the CLB state by the "high load cell"
mark.
− The
RNC selects the inter-frequency neighboring cells whose CLBFlag is TRUE. The selected cells
must NOT be under the same RNC as the source cell in the CLB state.
− From the previously selected cells, the RNC excludes the inter-frequency neighboring cells working
on the frequencies that are not supported by UEs to be handed over and the inter-frequency
neighboring cells in the CLB state and the 3G cells marked "high load cell" as candidate cells. The
details about the 3G cells marked "high load cell" are as follows:
a During the time window defined by UmtsCellLoadEstSlidWindow, if the number of inter-RNC
handover failures due to neighboring cell congestion or high load reaches the value of the
UmtsCellIFHOFailNum parameter, the 3G cell is marked "high load cell". Inter-frequency
measurements on and handovers towards the 3G cell are forbidden. The handover failure
causes include Relocation Preparation Failure and Radio Link Setup Failure.
b When a 3G cell under a neighboring RNC is marked "high load cell", a penalty timer
(PenaltyTimeforHLoad3GCell) starts. The 3G cell cannot be selected as the target cell of a
CLB inter-frequency handover until the timer expires. When it expires, the "high load cell" mark
is removed from the 3G cell.
− From the candidate cells, the RNC selects a cell or cells with the highest priority as the target cell or
cells based on the CLB-capable neighboring cell priority (CLBPrio).
− When the reference user speed optimization switch (UESpdOptSwitch) is set to ON, high-speed
users cannot be handed over to a micro cell. For details on how to identify high-speed users, see
Handover Feature Parameter Description.
The CellLoadBalanceRange parameter is set to BOTH_TO_INTRA_RNC_AND_INTER_RNC.
− The
RNC selects the combination of target cells that are selected when this parameter is set to
ONLY_TO_INTRA_RNC and ONLY_TO_INTER_RNC as candidate cells.
− From the candidate cells, the RNC selects a cell or cells with the highest priority as the target cell or
cells based on the CLB-capable neighboring cell priority (CLBPrio).
In the preceding three scenarios, if the RNC selects a DC-HSUPA user, the target cell must not be an inter-frequency
neighboring cell from the same carrier group.
RNC waits for the next measurement report. If the UE cannot be handed over to any of the candidate
cells, the RNC decides that the UE cannot be handed over and processes the next one.
This feature dynamically adjusts the P-CPICH transmit power based on downlink non-HSPA load in a
cell to reduce downlink non-HSPA load for this cell. After the power adjustment, the maximum and
minimum transmit power of the DPCH carrying online UEs is also changed. To minimize the impact of
power adjustment on online UEs, this feature compensates the maximum and minimum DPCH transmit
power during the power adjustment procedure.
When DLLOAD_BASED_PCPICH_PWR_ADJ_SWITCH under the NBMLdcAlgoSwitch parameter is
selected, the Load Based Dynamic Adjustment of PCPICH feature is activated and the TCP-based
intra-frequency load balancing function becomes disabled. The RNC periodically checks the downlink
non-HSPA power load in the current cell and adjusts the P-CPICH transmit power.
Figure 7-2 shows the flowchart of the Load Based Dynamic Adjustment of PCPICH algorithm.
Figure 7-2 Flowchart of the Load Based Dynamic Adjustment of PCPICH algorithm
The RNC checks the downlink non-HSPA load in the current cell at an interval specified by the
IntraFreqLdbPeriodTimerLen parameter. Then the RNC adjusts the P-CPICH transmit power for this
cell.
If downlink non-HSPA load in the current cell is equal to or larger than the value specified in the
PcpichPwrDownDlLoadState parameter, this cell is heavily loaded. In this situation, the P-CPICH
transmit power is reduced according to the value of the PCPICHPowerPace parameter so that
cell-edge UEs can be handed over to neighboring cells with lighter load. This reduces downlink power
load and increases downlink capacity of the current cell.
The minimum transmit power of the P-CPICH (MinPCPICHPower) is the lower limit for power
adjustment. The P-CPICH transmit power will not be reduced if reaching this limit. The maximum
power reduction is the difference between the PCPICHPower and MinPCPICHPower parameters.
The PCPICHPower parameter specifies the P-CPICH transmit power.
If downlink non-HSPA load in the current cell is smaller than the value specified in the
PcpichPwrUpDlLoadState parameter, this cell is lightly loaded. In this situation, more services can be
processed in this cell and the P-CPICH transmit power can be increased according to the value of the
PCPICHPowerPace parameter. This widens cell coverage and the widened coverage can
accommodate cell-edge UEs from neighboring cells. This relieves load of the neighboring cells.
The maximum transmit power of the P-CPICH (MaxPCPICHPower) is the upper limit for power
adjustment. P-CPICH transmit power will not be increased if reaching this limit. The maximum power
increase is the difference between the MaxPCPICHPower and PCPICHPower parameters. The
PCPICHPower parameter specifies the P-CPICH transmit power.
To minimize the impact of power adjustment on online UEs, this feature compensates the maximum and
minimum DPCH transmit power during the power adjustment procedure.
If the adjusted P-CPICH transmit power is lower than the value of the PCPICHPower parameter, the
maximum transmit power of the DPCH carrying online UEs remains the same as the power before the
power adjustment to promote link stability for online UEs.
If the adjusted P-CPICH transmit power is higher than the value of the PCPICHPower parameter, the
minimum transmit power of the DPCH carrying online UEs remains the same as the power before the
power adjustment to reduce non-HSPA power consumption.
The maximum and minimum transmit power for online UEs before the power adjustment is the sum of the PCPICHPower
and RlMinDlPwr parameters, and the sum of the PCPICHPower and RlMaxDlPwr parameters, respectively. For details
about the RlMinDlPwr and RlMaxDlPwr parameters, see Power Control Feature Parameter Description.
As shown in Figure 7-3, the RNC performs the following actions in each ULB period (specified by the
IntraFreqULBPeriodTimerLen parameter):
1. The RNC obtains RTWP from the NodeB and then performs smooth filtering on the RTWP value. The
smooth filtering window is specified by the ULBAvgFilterLen parameter.
2. The RNC evaluates the uplink load of the current cell based on the filtered RTWP value.
− If
the filtered RTWP value is between RTWPHeavyThd and RTWPLightThd, the RNC considers the
load of the current cell to be normal. In this case, the RNC does not adjust the pilot power in this
period.
− If
the filtered RTWP value is more than or equal to RTWPHeavyThd, the RNC considers the load of
the current cell to be heavy. In this case, the RNC performs step 3.
− If
the filtered RTWP value is less than or equal to RTWPLightThd, the RNC considers the load of the
current cell to be light. In this case, the RNC performs step 4.
3. The RNC compares the current pilot power and MinPCPICHPower. If the current pilot power is more
than MinPCPICHPower, the RNC decreases the current pilot power by one step (specified by the
PCPICHPowerPace parameter). Otherwise, the RNC does not adjust the pilot power in this period.
4. The RNC compares the current pilot power and MaxPCPICHPower. If the current pilot power is less
than MaxPCPICHPower, the RNC increases the current pilot power by one step (specified by the
PCPICHPowerPace parameter). Otherwise, the RNC does not adjust the pilot power in this period.
8 Load Reshuffling
This chapter describes the WRFD-020106 Load Reshuffling feature.
When the usage of cell resources exceeds the basic congestion trigger threshold, the cell enters the
basic congestion state. In this case, LDR is required to reduce the cell load and increase the access
success rate.
For an HSUPA cell, if HSUPA_EDCH_RSEPS_MEAS under the NBMCacAlgoSwitch parameter is not selected,
regardless of the value of the parameter NBMUlCacAlgoSelSwitch, the uplink load reshuffling algorithm will trigger
basic congestion based on ENU.
If the measurement on the total uplink load corresponding to the actual uplink service load is unavailable, for example,
when the relevant NodeB boards cannot report the measurement results, the uplink load reshuffling algorithm will
trigger basic congestion based on ENU.
The downlink load reshuffling algorithm selection depends on the following conditions:
If the parameter NBMDlCacAlgoSelSwitch is set to ALGORITHM_OFF, ALGORITHM_First, or
ALGORITHM_THIRD, the downlink load reshuffling algorithm will trigger basic congestion based on
power resource.
If the parameter NBMDlCacAlgoSelSwitch is set to ALGORITHM_SECOND, the downlink load
reshuffling algorithm will trigger basic congestion based on ENU.
If the load of a cell is calculated based on power resource, the uplink load of the cell is calculated based
on the uncontrollable load in the HSUPA cell or total RTWP load in the R99 cell. And the downlink load of
the cell is calculated based on the load of non-HSPA power and GBP in the HSDPA cell or total TCP load
in the R99 cell. If the load of a cell is calculated based on ENU, the uplink load and the downlink load of
the cell are calculated based on the total ENU load in the cell, respectively. For details about the load of
a cell calculated based on power resource and based on ENU, see Call Admission Control Feature
Parameter Description.
In a DC-HSDPA or DC-HSUPA cell, if the cell load is calculated based on the number of equivalent users, only the
equivalent users on the primary carrier are counted in the DC-HSDPA or DC-HSUPA cell.
Congestion control based on power resource can be enabled through the DL_UU_LDR and
UL_UU_LDR sub-parameters of the NBMLdcAlgoSwitch parameter.
The following figure shows the triggering and relieving of basic congestion.
Figure 8-1 Triggering and relieving of basic congestion
As shown in Figure 8-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 8-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 changes 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 600 ms.
The DL LDR trigger threshold of a DC-HSDPA cell group equals the sum of the DL LDR trigger
thresholds of the two cells in this group. The DL LDR relief threshold of a DC-HSDPA cell group equals
the sum of the 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.
In a DC-HSUPA cell, LDR triggering and execution happen in the two cells respectively.
If the SF corresponding to the current remaining code of the cell is larger than the value of
CellLdrSfResThd, code congestion is triggered and the related load reshuffling actions, as listed in
Table 8-2, are taken.
For R99 cells, only DCH UEs are selected by LDR actions.
The GoldUserLoadControlSwitch parameter specifies whether LDR actions select gold users. The RNC selects gold
users only when the GoldUserLoadControlSwitch parameter is set to ON.
Load-based inter-frequency handover
Code reshuffling
BE service rate reduction
AMR rate reduction
Inter-RAT load-based handover in the CS domain, which involves the following actions:
− Inter-RAT Should Be Load-based Handover in the CS Domain
− Inter-RAT Should Not Be Load-based Handover in the CS Domain
The difference between the "Inter-RAT Should Be Load-based Handover In the CS/PS Domain" and "Inter-RAT Should
Not Be Load-based 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 Handover Feature Parameter Description.
Inter-RAT load-based handover in the PS domain, which involves the following actions:
− Inter-RAT Should Be Load-based Handover in the PS Domain
− Inter-RAT Should Not Be Load-based Handover in the PS Domain
QoS Renegotiation for Uncontrollable Real-Time Services
MBMS power reduction
PS inter-RAT handover from UMTS to LTE
The sequence of LDR actions can be changed by running the MOD UCELLLDR/MOD UNODEBLDR
command.
The following figure illustrates the detailed LDR procedure. In this example, the sequence of LDR
actions is fixed to load-based inter-frequency 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 load-based inter-frequency
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 load-based inter-frequency handover is initiated again.
If the handover fails, code reshuffling is performed:
− Ifthe 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, BE rate reduction, is taken.
The remaining actions to be performed may be deduced by analogy. For details about LDR actions, see
section 8.3 "LDR Actions."
The LDR actions that are triggered by basic congestion caused by different resources are different.
Table 8-2 describes the LDR actions intended for different resources.
When the basic congestion is triggered by different resources, the congestion can be relieved in an order
set by running the SET ULDCALGOPARA command.
Table 8-2 LDR actions intended for different resources
Reso UL/ Service LDR Actions
urces DL
Real-Time Services
QoS Renegotiation
BE Rate Reduction
for Uncontrollable
Code Reshuffling
Inter-Frequency
Handover in CS
Handover in PS
MBMS Power
Load-based
Reduction
Reduction
AMR Rate
Handover
Inter-RAT
Inter-RAT
Domain
Domain
Power UL DCH √ √ √ √ √* √
HSUPA √* √ √
DC-HS √ √
UPA
DL DCH √ √ √ √ √* √
HSDPA √ √ √
DC-HS √ √
DPA
FACH √*
(MBMS)
Iub UL DCH √ √ √ √
HSUPA √ √
DC-HS √
UPA
DL DCH √ √ √ √
HSDPA √ √
DC-HS √
DPA
FACH
(MBMS)
Code - -
DL DCH √* √ √
HSDPA
FACH
(MBMS)
Credit UL DCH √ √ √ √ √
Real-Time Services
QoS Renegotiation
BE Rate Reduction
for Uncontrollable
Code Reshuffling
Inter-Frequency
Handover in CS
Handover in PS
MBMS Power
Load-based
Reduction
Reduction
AMR Rate
Handover
Inter-RAT
Inter-RAT
Domain
Domain
HSUPA √ √ √ √
DC-HS √ √ √
UPA
DL DCH √ √ √ √
HSDPA
FACH
(MBMS)
− Cell-levelparameters take effect when power resources, code resources, or cell credit resources are
in basic congestion state.
If multiple UEs have the same lowest integrated priority, the algorithm selects the one with the highest rate for
handover.
The user rates of UEs processing non-HSPA services and HSPA CS AMR services are their actual rates, and the user
rates of UEs processing HSPA PS BE services and streaming services are their GBRs. The user rates must be less
than UlInterFreqHoBWThd and DlInterFreqHoBWThd in the uplink and downlink.
If the basic congestion is caused by the credit resource, only UEs processing PS services are selected as candidate
UEs. UEs processing CS services are not selected because they consume a small amount of credit resource and
therefore handovers of them can do little to ease credit congestion. In addition, selecting UEs processing CS services
as candidate UEs may increase the call drop rate of CS services.
3. The RNC selects the candidate cells that meet the following requirements:
− The cell is an inter-frequency neighboring cell of the current cell and is controlled by the same RNC.
− The frequency of the cell is within the band supported by the UE.
− CPICH RSCP of the current cell in the measurement report that is reported by UE is higher than or
equal to BlindHOQualityCondition of the candidate cells.
− Thealgorithm selects the candidate cells to be handed over according to the setting of
NbmLdcUeSelSwitch:
a. If NbmLdcUeSelSwitch is set to NBM_LDC_MATCH_UE_ONLY, the algorithm only selects
the candidate cells from the cells supporting the UE service.
b. If NbmLdcUeSelSwitch is set to NBM_LDC_MATCH_UE_FIRST, the algorithm first selects
the candidate cells from the cells supporting the UE service. If there are no such cells, the
algorithm selects the candidate cells from the cells not supporting the UE service.
c. If NbmLdcUeSelSwitch is set to NBM_LDC_ALL_UE, the condition is invalid for the algorithm.
− The load state of candidate cell is normal.
− The candidate cell meets the following conditions on load margin:
a. If the basic congestion is caused by power resource:
If the cell does not support DC-HSDPA, the algorithm checks whether the UL/DL load margin of
the cell is higher than UlInterFreqHoCellLoadSpaceThd/DlInterFreqHoCellLoadSpaceThd,
whether the load of the cell is normal and whether the CPICH RSCP of the current cell in the
measurement report is higher than or equal to BlindHOQualityCondition.
If a cell supports DC-HSDPA, the cell and its corresponding cell group must have sufficient load
margin to qualify as the candidate cell. That is, the load margin of the cell group must be greater
than twice the value for DlInterFreqHoCellLoadSpaceThd and the load margin of the cell must
be greater than DlInterFreqHoCellLoadSpaceThd.
The load margin refers to the difference between the load of the candidate cell and the basic congestion trigger threshold
of the candidate cell. If the load of a cell is calculated based on power resource, the uplink load of the cell is calculated
based on the uncontrollable load of the cell and the downlink load of the cell is calculated based on the load of non-HSPA
power and GBP in the cell. If the load of a cell is calculated based on ENU, the uplink load and the downlink load of the
cell are calculated based on the total ENU load in the cell, respectively. For details about the load of a cell calculated
based on power resource and based on ENU, see Call Admission Control Feature Parameter Description.
b. If the basic congestion is caused by code resource:
Whether there are blind handover candidate cells meeting the requirements is decided by the
following conditions:
The minimum SF of the candidate cell is not greater than that of the current cell.
The difference of code usage between the current cell and the candidate cell is greater than
LdrCodeUsedSpaceThd.
c. If the basic congestion is caused by the credit resource:
UL credit margin for LDR in the candidate cell > Credit resource corresponding to the SF specified
by UlInterFreqHoCeLDRSpaceThd
The UL credit margin for LDR is calculated by subtracting the credit resource corresponding to the
SF specified by UlLdrCreditSfResThd from the remaining credit resource in the cell group or
under the NodeB. The UL credit margin for LDR equals the smaller one of the UL credit margin for
LDR in the cell group and that under the NodeB.
4. The RNC selects the target cell from the candidate cells according to the following principles:
− If
there are more than one candidate cells meeting the requirements, the first cell in the list of the
neighbor cells is selected as the blind handover target cell.
− Ifthere is no such cell, the RNC selects the candidate user of the second lowest integrated user
priority to retry to select the target cell.
− If
all the candidate users have been tried and the RNC does not select the target cell, the action fails
and the algorithm takes the next action.
5. After selecting the target cell and the UE, the RNC makes blind handover decision. For details, see
Handover Feature Parameter Description.
1. The RNC issues a measurement control message to the UE, requesting the UE to measure the
signal quality of all candidate cells.
2. The UE measures the RSCP and Ec/N0 of the candidate cells and periodically reports the
measurement results to the RNC. The reporting period is specified by the PrdReportInterval
parameter.
3. Based on the received measurement results, the RNC selects the candidate cells. The candidate
cells must meet the following conditions:
− The cell is not in the basic congestion state.
− Themeasured RSCP is higher than the RSCP threshold that is specified by the TargetFreqThdRscp
parameter.
− Themeasured Ec/N0 is higher than the Ec/N0 threshold that is specified by the TargetFreqThdEcN0
parameter.
If such candidate cells do not exist, the load-based inter-frequency handover action fails and the
algorithm takes the next action.
If such candidate cells exist, the following step is performed.
4. The RNC selects the cell with the highest priority from the candidate cells to perform inter-frequency
hard handover.
− If the handover succeeds, the LDR action is complete.
− If
the handover fails, the RNC tries accessing the cell with the second highest priority to perform
inter-frequency hard handover until the handover succeeds or it has attempted to access all the
candidate cells.
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, do not configure the BE Rate Reduction as an LDR action in
order to avoid ping-pong effect.
BE rate reduction can only be performed when the DRA_DCCC_SWITCH sub-parameter 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:
− The
current rate of the BE RAB is higher than the GBR specified by running the SET UUSERGBR
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 DCCC Feature Parameter Description.
4. The handover module decides to trigger the inter-RAT handover, depending on the capability of the
UE to support the compressed mode.
5. If a UE that meets the handover criteria is not found, the algorithm takes the next action.
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 Handover Feature Parameter Description.
Some MBMS-related algorithms do not take effect on the BSC6910 because the BSC6910 does not support
MBMS-related features.
The downlink power load can be reduced by lowering the power on MBMS traffic channels.
The algorithm operates as follows:
1. Based on the integrated priority, the algorithm sorts the RABs in descending order.
2. The algorithm selects a RAB with the lowest integrated priority and with the current power higher than
the minimum transmit power of the corresponding MTCH. That is, it selects an RAB whose ARP
value is higher than MbmsDecPowerRabThd.
3. The algorithm triggers a reconfiguration procedure to set the power to the minimum transmit power of
the FACH onto which the MTCH is mapped.
The reconfiguration procedure on the Iub interface is implemented through the COMMON
TRANSPORT CHANNEL RECONFIGURATION REQUEST message.
− A RAB can be handed over or redirected to LTE cells only when the IE "E-UTRAN Service Handover"
in the RAB ASSIGNMENT REQUEST message is null and
HO_TO_EUTRAN_SHOULD_BE_PERFORM under the EUTRANSHIND parameter in the ADD
UTYPRABBASIC command is selected.
− If
the value of the IE "E-UTRAN Service Handover" in the RAB ASSIGNMENT REQUEST message
is "Handover to E-UTRAN shall not be performed", a RAB cannot be handed over or redirected to
LTE cells.
The UEs are UL dual-mode UEs or GUL triple-mode UEs.
There is LTE coverage.
− If
HO_U2L_REDIR_BASED_ABSOLUTE_FREQ_SWITCH under the HoSwitch1 parameter is
cleared, the current UMTS cell must be configured with neighboring LTE cells.
− If
HO_U2L_REDIR_BASED_ABSOLUTE_FREQ_SWITCH under the HoSwitch1 parameter is
selected, the current UMTS cell must be configured with LTE frequencies. For details about how to
configure LTE frequencies, see Interoperability Between UMTS and LTE Feature Parameter
Description.
The UMTS to LTE redirection switch based on absolution frequency is controlled by
HO_U2L_REDIR_BASED_ABSOLUTE_FREQ_SWITCH under the HoSwitch1 parameter.
The load-based PS redirection or handover from UMTS to LTE function is enabled.
− The
general switch for UMTS-to-LTE PS interoperations is turned on, that is,
HO_LTE_PS_OUT_SWITCH under the HoSwitch parameter is selected.
− To
Load Based PS Redirection from UMTS to LTE feature, the PS inter-RAT handover from UMTS to
LTE function must be enabled.
− Toactivate the Load Based PS Handover from UMTS to LTE feature, the PS handover from UMTS to
LTE function must be enabled and HO_U2L_REDIR_BASED_ABSOLUTE_FREQ_SWITCH under
the HoSwitch1 parameter must be cleared.
For details about redirection and handovers, see Interoperability Between UMTS and LTE Feature
Parameter Description.
3. The RNC selects UEs to perform the PS inter-RAT handover from UMTS to LTE LDR action.
After allowing UMTS-to-LTE PS redirection for handovers, the RNC selects UEs to perform this LDR
action.
a The RNC puts UL or GUL UEs that processes only PS services into a list.
b The RNC selects UEs that did not perform PS handovers from UMTS to LTE.
c The RNC arranges the selected UEs according to the user integrated priority. Then the RNC selects
several UEs to perform this LDR action in ascending order of user integrated priority.
For uplink LDR actions, the number of UEs is specified by the UlPSU2LHOUeNum parameter. For
downlink LDR actions, the number of UEs is specified by the DlPSU2LHOUeNum parameter.
If the UEs have the same user integrated priority, they will be selected randomly. Suppose there are
five UEs (UE A, UE B, UE C, UE D, and UE E) and the user integrated priority is A < B = C = D < E. If
three UEs are to be selected, the RNC preferentially selects UE A and then selects any two UEs
among UEs B, C, and D.
For example, BE service rate reduction must be performed simultaneously in the uplink and downlink
of the same UE. In this situation, the RNC sends only one RADIO BEARER RECONFIGURATION
message, indicating that BE service rate reduction is performed simultaneously in the uplink and
downlink of this UE.
If the uplink and downlink are going to perform different LDR actions, these LDR actions can be
performed as follows:
− If
uplink LDR actions are inter-frequency or inter-RAT handovers, or PS inter-RAT handovers from
UMTS to LTE, LDR actions can only be performed in the uplink.
− If
downlink LDR actions are inter-frequency or inter-RAT handovers, or PS inter-RAT handover from
UMTS to LTE, LDR actions can only be performed in the downlink.
LDR actions are performed in the direction with fewer UEs.
9 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 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, OLC must be performed.
For details about overload congestion caused by Iub bandwidth, see Transmission Resource Management Feature
Parameter Description.
For the overload triggered by power resources, the downlink OLC algorithm will trigger overload based
on total TCP load in the R99 cell or the load of non-HSPA power and HSDPA GBP in the HSDPA cell.
The uplink OLC algorithm selection depends on the following conditions:
If the parameter NBMUlCacAlgoSelSwitch is set to ALGORITHM_First, ALGORITHM_THIRD, or
ALGORITHM_OFF, the uplink OLC algorithm will trigger overload based on total RTWP load of the
cell.
If the parameter NBMUlCacAlgoSelSwitch is set to ALGORITHM_FORTH, the uplink OLC algorithm
will trigger overload based on the total uplink load corresponding to the actual uplink service load.
If the measurement on the total uplink load corresponding to the actual uplink service load is unavailable, for example,
when the relevant NodeB boards cannot report the measurement results, the uplink OLC algorithm will trigger overload
based on total RTWP load of the cell.
OLC can be enabled through the UL_UU_OLC and DL_UU_OLC sub-parameters of the
NBMLdcAlgoSwitch parameter.
The following figure shows the triggering and release of cell power overload.
As shown in Figure 9-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 parameter DlLdTrnsHysTime; for the uplink, the hysteresis time
is 600 ms.
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.
In a DC-HSUPA cell, OLC triggering and execution happen in the two cells respectively.
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.
The RSVDBIT13 under the RsvdPara1 parameter in the ADD UCELLALGOSWITCH command specifies whether OLC
actions select gold users. When RSVDBIT13 is selected, OLC actions select gold users.
− TFmax(N+1) is the maximum TB number during the period from (T1 + RateRecoverTimerLen x N)
to (T1 + (RateRecoverTimerLen x (N + 1)), where T1 is the time when the MAC receives the
congestion relief indication message.
− RateRecoverCoeff is specified by the RecoverCoef parameter.
If both the selected UEs and the current cell support enhanced CELL_FACH, these UEs can be
switched to the enhanced CELL_FACH state.
The preceding power adjustment is applicable to only the FACH carrying common services rather than MBMS services.
Some MBMS-related algorithms do not take effect on the BSC6910 because the BSC6910 does not support
MBMS-related features.
For the release of some RABs in the downlink, the OLC algorithm operates as follows:
If the SeqOfUserRel parameter is set to USER_REL, then:
1. Based on the integrated priority, the algorithm sorts all non-MBMS RABs in descending order.
2. The algorithm selects the RABs with the lowest integrated priorities. If the integrated priorities of
some RABs are identical, it selects the RAB with a higher rate (that is, the current rate for DCH RAB
or the GBR for HSDPA RAB) in the downlink. The number of selected RABs is specified by
DlOlcTraffRelRabNum.
3. The selected RABs are directly released.
4. If all non-MBMS RABs are released but congestion persists in the downlink, MBMS RABs are
selected.
If the SeqOfUserRel parameter is set to MBMS_REL, then:
1. Based on the ARP, the algorithm sorts all MBMS RABs in descending order.
2. The algorithm selects the RABs with the lowest integrated priorities. The number of selected RABs is
specified by MbmsOlcRelNum.
3. The selected RABs are directly released.
4. If all MBMS RABs are released but congestion persists in the downlink, non-MBMS RABs are
selected.
This function is disabled when the UlOlcTraffRelRabNum, DlOlcTraffRelRabNum, and MbmsOlcRelNum parameters
are set to 0.
The higher the value of UlOlcTraffRelRabNum or DlOlcTraffRelRabNum, the more the cell load decreases, which will
affect the users experience negatively.
10 Network Impact
10.1 Inter-Frequency Load Balancing
10.1.1 Network Performance
Inter-frequency load balancing based on uplink credit resource enables some UEs to be handed over to
an inter-frequency neighboring cell when the current cell is in the basic congestion state. In this way, the
admission failures due to CE resource congestion decrease.
In addition, this feature makes UEs processing PS services more likely to perform inter-frequency
handovers. This may slightly increase the PS call drop rate.
− More inter-frequency handovers may reduce the success rate of inter-frequency handovers and
increase the call drop rate.
− During
the inter-frequency handover measurement, the throughput of online UEs in compressed
mode with halved spreading factors (SF) will be reduced.
Suppose that the cell transmit power is 20 W, the P-CPICH transmit power is 10% of the cell transmit
power, and the FACH transmit power is 1 dB. If an additional 2 dB power is to be added, the amount of
power available for the dedicated channel may be insufficient and five AMR UEs may not be admitted
into this cell.
feature is activated. This feature improves uplink coverage and reduces the call drop rate.
However, the HSUPA throughput is also reduced.
The RTWP-based anti-interference function takes effect only when ALGORITHM_FOURTH under the
NBMUlCacAlgoSelSwitch parameter is selected.
When several HSUPA UEs are going to transmit a large amount of data simultaneously, the rise over
thermal (RoT) will become high due to HSUPA scheduling. In this case, the RTWPs of two antennas
are almost the same and the gains provided by this function are not noticeable because the corrected
RTWP is almost the same as the original RTWP.
Although this function increases the NodeB CPU usage, the increase is not noticeable because the
load on a CPU with a 1 GHz main frequency is only 0.001%.
11 Engineering Guidelines
11.1 WRFD-021104 Emergency Call
11.1.1 Deployment
Requirements
Hardware
This feature does not have any special requirements for hardware.
Other features
This feature does not depend on other features.
License
This feature is not under license control.
Data Preparation
None
Activation
This feature does not need to be activated.
Activation Observation
Use a UE to initiate an emergency call. The emergency call is successfully established.
Deactivation
This feature does not need to be deactivated.
Data Preparation
None
Activation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) to enable the cell-level LDR algorithm. In this
step, set Cell LDC algorithm switch to UL_UU_LDR(Uplink UU LDR Algorithm),
DL_UU_LDR(Downlink UU LDR Algorithm), and CELL_CREDIT_LDR(Credit LDR Algorithm).
2. Run the RNC MML command MOD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm Parameters;
CME batch modification center: Modifying Logical NodeB Parameters in Batches) to enable the
NodeB-level LDR algorithm. In this step, set NodeB LDC algorithm switch to IUB_LDR(IUB LDR
Algorithm), LCG_CREDIT_LDR(LCG Credit LDR Algorithm), and NODEB_CREDIT_LDR(NodeB
Credit LDR Algorithm).
3. Run the RNC MML command MOD UCELLLDM (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented LDM Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches) to set the cell-level LDR
trigger threshold. In this step, set UL/DL LDR Trigger threshold and DL State Trans Hysteresis
threshold according to the network plan.
4. Run the RNC MML command MOD UNODEBLDR (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB LDR Algorithm
Parameters; CME batch modification center: Modifying Logical NodeB Parameters in Batches) to set
the NodeB-level LDR credit spreading factor (SF) reserved threshold. In this step, set Ul LDR Credit
SF reserved threshold and Dl LDR Credit SF reserved threshold according to the network plan.
5. Run the RNC MML command MOD UCELLLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) to set the NodeB credit LDR
threshold for the local cell. In this step, set Ul LDR Credit SF reserved threshold and DL LDR
Credit SF reserved threshold according to the network plan.
6. Run the RNC MML command SET ULDCPERIOD (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC Oriented LDC
Algorithm Cycle Length; CME batch modification center: Modifying RNC Parameters in Batches).
In this step, set LDR period timer length according to the network plan.
7. Run the RNC MML command MOD UCELLLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) to enable QoS renegotiation on
real-time services. In this step, set DL LDR first action to QOSRENEGO.
Activation Observation
1. Establish a PS streaming service.
2. Trigger LDR in the cell according to the cell LDR threshold specified in the activation procedure.
3. If RAB MODIFY REQUEST is traced on the Iu interface, this feature has been activated.
Deactivation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) to disable the cell-level LDR algorithm. In this
step, clear UL_UU_LDR(Uplink UU LDR Algorithm), DL_UU_LDR(Downlink UU LDR Algorithm),
and CELL_CREDIT_LDR(Credit LDR Algorithm) from the Cell LDC algorithm switch drop-down
list box.
2. Run the RNC MML command MOD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm Parameters;
CME batch modification center: Modifying Logical NodeB Parameters in Batches) to disable the
NodeB-level LDR algorithm. In this step, clear IUB_LDR(IUB LDR Algorithm),
LCG_CREDIT_LDR(LCG Credit LDR Algorithm), and NODEB_CREDIT_LDR(NodeB Credit LDR
Algorithm) from the NodeB LDC algorithm switch drop-down list box.
Data Preparation
None
Activation
1. The function of measurement on RTWP, TCP, and non-HSPA power is always activated. Therefore,
this feature does not need to be activated.
2. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, select
HSDPA_PBR_MEAS(HSDPA PBR Meas Algorithm) and HSUPA_PBR_MEAS(HSUPA PBR
Meas Algorithm) from the Cell CAC algorithm switch drop-down list to activate the cell-level load
measurement for HSDPA and HSUPA.
3. Run the RNC MML command MOD UCELLLDM (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented LDM Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, set load
monitoring parameters, including the uplink/downlink load reshuffling (LDR) algorithm trigger/release
thresholds and uplink/downlink overload congestion (OLC) algorithm trigger/release thresholds to
appropriate values.
4. Run the RNC MML command SET ULDM (CME single configuration: UMTS Radio Global
Configuration Express > Load Monitoring Parameter Configuration > LDM Algorithm
Parameters of RNC; CME batch modification center: Modifying RNC Parameters in Batches). In this
step, set parameters associated with load measurement, report period, and smoothing filter length
according to the network plan.
Activation Observation
1. On the RNC LMT, open the Monitor tab page. In the Monitor navigation tree, double-click UMTS
Monitoring > Cell Performance Monitoring, and create tasks of monitoring Cell DL Carrier TX
Power and RTWP.
2. Check whether the uplink full-bandwidth RX power of the cell is displayed in the RTWP monitoring
window.
3. Check whether the downlink carrier TX power is displayed in the Cell DL Carrier TX Power
monitoring window.
Deactivation
1. The measurement on RTWP, TCP, and non-HSPA power has been activated and cannot be
deactivated.
2. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, clear
HSDPA_PBR_MEAS(HSDPA PBR Meas Algorithm) and HSUPA_PBR_MEAS(HSUPA PBR
Meas Algorithm) from the Cell CAC algorithm switch drop-down list to deactivate the cell-level
load measurement for HSDPA and HSUPA.
Data Preparation
None
Activation
The following section provides the related parameters and commands. The parameter settings depend on the network
plan.
1. Enable the related load reshuffling algorithms.
a Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, turn on the following switches of
Cell LDC algorithm switch:
− UL_UU_LDR(Uplink UU LDR Algorithm): UL UU load reshuffling algorithm
− DL_UU_LDR(Downlink UU LDR Algorithm): DL UU load reshuffling algorithm
− CELL_CODE_LDR(Code LDR Algorithm): Code reshuffling algorithm
− CELL_CREDIT_LDR(Credit LDR Algorithm): Credit reshuffling algorithm
b Run the RNC MML command MOD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm
Parameters; CME batch modification center: Modifying Logical NodeB Parameters in Batches). In
this step, turn on the following switches of NodeB LDC algorithm switch:
− IUB_LDR(IUB LDR Algorithm): NodeB Iub reshuffling algorithm
− NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm): NodeB-level credit reshuffling algorithm
− LCG_CREDIT_LDR(LCG Credit LDR Algorithm): cell-group-level credit reshuffling algorithm
2. Set the related thresholds.
− Runthe RNC MML command MOD UCELLLDM (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented LDM Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches) to set LDR thresholds
(UL/DL LDR Trigger/release threshold and DL State Trans Hysteresis threshold).
− Runthe RNC MML command MOD UCELLLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) to set code LDR threshold (Cell
LDR SF reserved threshold) and LDR actions.
− Runthe RNC MML command MOD UNODEBLDR (CME single configuration: NodeB Configuration
Express > IUB_RNC > NodeB Basic Information > NodeB LDR Algorithm Parameters; CME
batch modification center: Modifying Logical NodeB Parameters in Batches) to set the
cell-group-level or NodeB-level LDR thresholds (Ul/DL LDR Credit SF reserved threshold).
− Run the RNC MML command MOD UCELLLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) to set the cell-level credit LDR
thresholds (Ul/DL LDR Credit SF reserved threshold).
3. Run the RNC MML command SET ULDCPERIOD (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC Oriented LDC
Algorithm Cycle Length; CME batch modification center: Modifying RNC Parameters in Batches) to
set the LDR period (LDR period timer length).
4. Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC
Parameters in Batches) to enable the functions used in the LDR actions.
− Inter-frequency load handover
Set HandOver Switch to HO_INTER_FREQ_HARD_HO_SWITCH and
HO_ALGO_LDR_ALLOW_SHO_SWITCH.
− BE service rate reduction
Set Dynamic Resource Allocation Switch to DRA_DCCC_SWITCH.
− Uncontrolled real-time traffic QoS renegotiation
Set PS Rate Negotiation Switch to PS_BE_IU_QOS_NEG_SWITCH.
− CS domain inter-RAT load handover
Set HandOver Switch to HO_INTER_RAT_CS_OUT_SWITCH.
− PS domain inter-RAT load handover
Set HandOver Switch to HO_INTER_RAT_PS_OUT_SWITCH.
− Downsizing the bit rate of AMR voice
Set CS Algorithm Switch to CS_AMRC_SWITCH.
Activation Observation
The following section takes R99 non-real-time data services as examples to verify BE service rate
reduction in the basic congestion state.
1. Enable a UE in idle mode to camp on CELL_A11.
2. On the RNC LMT, open the Monitor tab page. In the Monitor Navigation Tree tab page,
double-click UMTS Monitoring > Cell Performance Monitoring. In the displayed dialog box, create
a Cell DL Throughput monitoring task.
3. Connect the UE to a laptop through the USB port and initiate a data service. Check the
rb-mappinginfo information element (IE) contained in the RRC_RB_SETUP message traced over
the Uu interface. The value of rrc-Stateinditator is CELL_DCH.
4. Use the UE to log in to the FTP server and then start FTP downloading. Data downloading is normal.
5. To simulate the scenario where power load reaches 75%, run the NodeB MML command STR
DLSIM. The RRC_RB_RECFG message is displayed in the Uu Interface Trace dialog box. In the
Cell DL Throughput of the Connection Performance Monitoring dialog box, you can view the
downlink RB rate decrease configured on the RNC.
6. To stop simulating power load, run the NodeB MML command STP DLSIM. In the Uu Interface Trace
dialog box, the RRC_RB_RECFG message is displayed. In the Cell DL Throughput of the
Connection Performance Monitoring dialog box, you can view the downlink RB rate increase
configured on the RNC.
Deactivation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, clear the following switches from
Cell LDC algorithm switch:
− UL_UU_LDR(Uplink UU LDR Algorithm): UL UU load reshuffling algorithm
− DL_UU_LDR(Downlink UU LDR Algorithm): DL UU load reshuffling algorithm
− CELL_CODE_LDR(Code LDR Algorithm): Code reshuffling algorithm
− CELL_CREDIT_LDR(Credit LDR Algorithm): Credit reshuffling algorithm
2. Run the RNC MML command MOD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm Parameters;
CME batch modification center: Modifying Logical NodeB Parameters in Batches). In this step, clear
the following switches from NodeB LDC algorithm switch:
− IUB_LDR(IUB LDR Algorithm): NodeB Iub reshuffling algorithm
− NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm): NodeB-level credit reshuffling algorithm
− LCG_CREDIT_LDR(LCG Credit LDR Algorithm): cell-group-level credit reshuffling algorithm
Data Preparation
None
Activation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) to enable the air interface OLC algorithm.
Select UL_UU_OLC(Uplink UU OLC Algorithm) and DL_UU_OLC(Downlink UU OLC Algorithm)
under the Switch for Cell Load Control parameter.
2. Run the RNC MML command MOD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm Parameters;
CME batch modification center: Modifying Logical NodeB Parameters in Batches) to enable the OLC
algorithm. Select IUB_OLC(IUB OLC Algorithm) under the parameter NodeB LDC algorithm.
3. Run the RNC MML command MOD UCELLLDM (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented LDM Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches) to set UL OLC trigger
threshold, DL OLC trigger threshold, UL OLC release threshold, and DL OLC release threshold.
4. Run the RNC MML command SET ULDCPERIOD (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC Oriented LDC
Algorithm Cycle Length; CME batch modification center: Modifying RNC Parameters in Batches) to
set the OLC period (OLC period timer value).
5. Run the RNC MML command ADD UCELLOLC (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Overload Congestion Control Algorithm
Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches) to set the
parameter related to OLC-related actions.
Activation Observation
1. Run the following RNC MML commands to verify whether the activation is successful.
− LST UCELLALGOSWTICH
− LST UCELLLDM
− LST UNODEBALGOPARA
− LST ULDCPERIOD
− LST UCELLOLC
Consult Huawei engineers about the verification solution to obtain professional technical support.
Deactivation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) to disable the air interface OLC algorithm.
Clear UL_UU_OLC(Uplink UU OLC Algorithm) and DL_UU_OLC(Downlink UU OLC Algorithm)
under the Switch for Cell Load Control parameter.
2. Run the RNC MML command MOD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm Parameters;
CME batch modification center: Modifying Logical NodeB Parameters in Batches) to disable the OLC
algorithm. Clear IUB_OLC(IUB OLC Algorithm) under the NodeB LDC algorithm parameter.
Data Preparation
None
Activation
The code allocation function is always activated. The activation procedure applies to only the code reshuffling function.
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches), and then enable the required LDR algorithm
switches for resources (CELL_CODE_LDR(Code LDR Algorithm)) through setting the Cell LDC
algorithm switch parameter.
2. Run the RNC MML command MOD UCELLLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) to set code LDR threshold (Cell
LDR SF reserved threshold) and set CodeAdj(Code adjust) as one of the DL LDR actions.
3. Run the RNC MML command SET ULDCPERIOD (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC Oriented LDC
Algorithm Cycle Length; CME batch modification center: Modifying RNC Parameters in Batches) to
set the LDR period (LDR period timer length).
Activation Observation
1. Enable the UE in the idle state to camp on CELL_A11.
2. Set the PS service type to interactive on the HLR.
3. Run the RNC MML command MOD UCELLLDR with Cell LDR SF reserved threshold set to SF8
and Max user number for code adjust to 1.
4. Connect the UE to a laptop on the USB port and enable the UE to initiate a data service.
Expected result: Services are set up on the DCH successfully. You can view the rb-mappinginfo
information element (IE) in the RRC_RB_SETUP message traced over the Uu interface. In the Cell
Code Tree Monitor window, you can view that the service occupies code SF32(4).
5. Enable the UE to log in to the FTP Internet server and then enable FTP download.
6. Run the RNC MML command DSP UCELLCHK to check the cell health status. The status of cell
code congestion is displayed as basic congestion.
7. Run the RNC MML command RMV URESERVEOVSF to release the service that occupies code
SF32(1).
8. Run the RNC MML command DSP UCELLCHK to check the cell health status. The status of cell
code congestion is displayed as not congested.
Deactivation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches), and then deactivate the required LDR
algorithm switches for resources (CELL_CODE_LDR(Code LDR Algorithm)) through setting the
Cell LDC algorithm switch parameter.
Data Preparation
None
Activation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) to select PUC(Potential User Control
Algorithm) from the Switch for Cell Load Control drop list to enable the cell-oriented PUC
algorithm.
2. Run the RNC MML command SET ULDCPERIOD (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC Oriented LDC
Algorithm Cycle Length; CME batch modification center: Modifying RNC Parameters in Batches) to
specify the period of potential user control. In this step, set PUC period timer length to an
appropriate value.
3. Run the RNC MML command ADD UCELLPUC (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented PUC Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches) to set the cell-oriented PUC
algorithm parameters.
Activation Observation
1. Configure two cells CELL_A11 and CELL_A12 as inter-frequency neighboring cells on the NodeB.
2. Run the RNC MML command MOD UCELLPUC to change the potential user control threshold for
CELL_A11.
3. Run the NodeB MML command STR DLSIM to simulate a situation where the cell has a high load.
The following messages can be traced on the Iub interface: The NBAP_SYS_INFO_UPDATE_REQ
from the RNC to the NodeB, and the NBAP_SYS_INFO_UPDATE_RSP message responded by the
NodeB.
The updated system information can be traced on the Uu interface. The value of the Sintersearch
signaling element (IE) of the SIB3 of CELL_A11 decreases, and the values of the Qoffset1s,n and
Qoffset2s,n IEs of the SIB11 of CELL_A11 increase.
4. Run the RNC MML command MOD UCELLPUC to change the potential user control threshold for
CELL_A12.
5. Run the NodeB MML command STR DLSIM to simulate a situation where CELL_A12 has a high
downlink load.
The following messages can be traced on the Iub interface: The NBAP_SYS_INFO_UPDATE_REQ
message from the RNC to the NodeB, and the NBAP_SYS_INFO_UPDATE_RSP response message
from the NodeB.
The updated system information can be traced on the Uu interface. The value of the Sintersearch IE of
the SIB3 of CELL_A11 decreases, and the values of the Qoffset1s,n and Qoffset2s,n IEs of the SIB11 of
CELL_A11 increase.
Deactivation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, clear PUC(Potential User
Control Algorithm) under the Cell LDC algorithm switch parameter.
Data Preparation
None
Activation
1. Enable load reshuffling (LDR) algorithms.
Enabling uplink load reshuffling on the Uu interface
a Run the RNC MML command ADD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, select UL_UU_LDR(Uplink UU
LDR Algorithm) under the Switch for Cell Load Control parameter.
Parameters > Cell Oriented LDM Algorithm Parameters; CME batch modification center:
Modifying UMTS Cell Parameters in Batches). In this step, set the following LDR-related thresholds:
UL LDR trigger threshold, UL LDR release threshold, DL LDR trigger threshold, DL LDR
release threshold, and DlLdTrnsHysTime.
− For uplink and downlink load reshuffling on the Uu interface and load reshuffling based on cell code
resources, run the Run the RNC MML command MOD UCELLLDR (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, set the
following LDR-related threshold: Cell LDR SF reserved threshold.
− For
NodeB-level or cell group-level load reshuffling based on credit resources, run the Run the RNC
MML command MOD UNODEBLDR (CME single configuration: NodeB Configuration Express >
IUB_RNC > NodeB Basic Information > NodeB LDR Algorithm Parameters; CME batch
modification center: Modifying Logical NodeB Parameters in Batches). In this step, set the following
LDR-related threshold: UL LDR Credit SF reserved threshold.
7. For load reshuffling based on cell code resources, run the Run the RNC MML command MOD
UCELLLDR (CME single configuration: UMTS Cell Configuration Express > Cell Parameters >
Cell LDR Algorithm Parameters; CME batch modification center: Modifying UMTS Cell Parameters
in Batches) to allow inter-frequency handovers in cases of code resource congestion. In this step, set
Code congestion select inter-freq indication to TRUE(TRUE).
8. Run the RNC MML command SET ULDCPERIOD (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC Oriented LDC
Algorithm Cycle Length; CME batch modification center: Modifying RNC Parameters in Batches).
In this step, set the LDR period LDR period timer length to an appropriate value.
9. For uplink and downlink load reshuffling on the Uu interface and load reshuffling based on cell code
resources, run the Run the RNC MML command MOD UCELLLDR (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, select
InterFreqLDHO(inter-freq load handover) under the DL LDR first action parameter and set other
parameters related to the LDR action based on the network plan.
10. For NodeB-level or cell group-level load reshuffling based on credit resources, run the Run the RNC
MML command MOD UNODEBLDR (CME single configuration: NodeB Configuration Express >
IUB_RNC > NodeB Basic Information > NodeB LDR Algorithm Parameters; CME batch
modification center: Modifying Logical NodeB Parameters in Batches). In this step, select
InterFreqLDHO(inter-freq load handover) under the UL LDR first action parameter and set other
parameters related to the LDR action based on the network plan.
Activation Observation
1. Run the following RNC to check whether this feature has been activated.
− LST UCELLALGOSWITCH
− LST UCELLLDR
− LST UCELLLDM
− LST ULDCPERIOD
− LST UCORRMALGOSWITCH
− LST UINTERFREQNCELL
− LST UCELLINTERFREQHONCOV(cell level)
− LST UINTERFREQHONCOV(RNC level)
− LST ULDCALGOPARA
− LST UNODEBALGOPARA
− LST UNODEBLDR
2. Check the value of the counter VS.LCC.LDR.InterFreq (Number of UEs Performing Inter-Frequency
Load Handovers in Basic Congestion for Cell). If the value is not 0, this feature has been activated.
Deactivation
1. Disabling load reshuffling algorithms
Disabling uplink LDR on the Uu interface
a Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, clear UL_UU_LDR(Uplink UU
LDR Algorithm) under the Switch for Cell Load Control parameter.
Disabling downlink LDR on the Uu interface
a Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, clear DL_UU_LDR(Downlink
UU LDR Algorithm) under the Switch for Cell Load Control parameter.
Disabling load reshuffling based on cell code resources
a Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, clear CELL_CODE_LDR(Code
LDR Algorithm) under the Switch for Cell Load Control parameter.
Disabling NodeB-level or cell-level load reshuffling based on credit resources
a Run the RNC MML command SET ULDCALGOPARA (CME single configuration: UMTS Radio
Global Configuration Express > Load Control Parameter Configuration > RNC Configuration
of Load Control; CME batch modification center: Modifying RNC Parameters in Batches). In this
step, clear NodeB-level NODEB_CREDIT_LDR_SWITCH(NodeB Credit LDR Switch) or cell
group-level LCG_CREDIT_LDR_SWITCH(Local Cell Group Credit LDR Switch) under the load
control algorithm switch parameter.
b Run the RNC MML command MOD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm
Parameters; CME batch modification center: Modifying Logical NodeB Parameters in Batches). In
this step, clear NodeB-level NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm) or cell
group-level LCG_CREDIT_LDR(LCG Credit LDR Algorithm) under the NodeB LDC algorithm
switch parameter.
2. Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC
Parameters in Batches) to disable inter-frequency handover. In this command, clear
HO_ALGO_LDR_ALLOW_SHO_SWITCH and HO_INTER_FREQ_HARD_HO_SWITCH under the
HandOver Switch parameter.
3. Run the RNC MML command MOD UCELLLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell LDR Algorithm Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) to prohibit inter-frequency
handovers in cases of code resource congestion. In this step, set Code congestion select
inter-freq indication to FALSE(FALSE).
4. Restore the parameter settings modified in the activation procedure.
11.9.2 Deployment
Requirements
Other features
This feature depends on the feature WRFD-020110 Multi Frequency Band Networking Management in
the inter-band networking scenario.
License
The licenses "Inter-Frequency Load Balancing Based on Configurable Load Threshold (per Cell)" on
the RNC side have been activated. For details about the license items and how to activate the license,
see License Management Feature Parameter Description.
Data Preparation
None
Activation
1. Run the RNC MML command ADD UCELLLICENSE (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell License Resource/Function Item; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) or MOD UCELLLICENSE (CME
single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell License
Resource/Function Item; CME batch modification center: Modifying UMTS Cell Parameters in
Batches). In this step, under FuncSwitch1, select
INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD(Inter-Frequency Load Balancing Based
on Config Load Thd) to enable the license of CLB for a specified cell.
2. Run the RNC MML command ADD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) or MOD UCELLALGOSWITCH (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Algorithm Switches;
CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this step, under
NBMLdcAlgoSwitch, select UL_UU_CLB to enable uplink Uu-interface load balancing, select
DL_UU_CLB to enable downlink Uu-interface load balancing, select CELL_CODE_CLB to enable
cell code resource load balancing, and select CELL_CREDIT_CLB to enable cell credit load
balancing for a specified cell.
3. Run the RNC MML command ADD UNODEBALGOPARA (CME single configuration: NodeB
Configuration Express > IUB_RNC > NodeB Basic Information > NodeB Algorithm Parameters;
CME batch modification center: Modifying Logical NodeB Parameters in Batches) or MOD
UNODEBALGOPARA (CME single configuration: NodeB Configuration Express > IUB_RNC >
NodeB Basic Information > NodeB Algorithm Parameters; CME batch modification center:
Modifying Logical NodeB Parameters in Batches). In this step, under NodeBLdcAlgoSwitch, select
NODEB_CREDIT_CLB_SWITCH(NodeB Credit CLB Algorithm) to enable NodeB credit load
balancing and select LCG_CREDIT_CLB_SWITCH(Local Cell Group Credit CLB Algorithm) to
enable local cell group credit load balancing for a specified NodeB.
4. Run the RNC MML command ADD UINTERFREQNCELL (CME single configuration: UMTS Cell
Configuration Express > Neighboring Cell > Inter-frequency Neighboring Cell; CME batch
modification center: not supported) or MOD UINTERFREQNCELL (CME single configuration: UMTS
Cell Configuration Express > Neighboring Cell > Inter-frequency Neighboring Cell; CME batch
modification center: not supported). In this step, set CLBFlag for the inter-frequency neighboring cell
of a specified cell to TRUE, and set CLBPrio based on the network plan.
The inter-frequency neighboring cell of intra-RNC whose CLBFlag is TRUE can be the target cell of an inter-frequency
handover using CLB only after step 1 is performed.
5. Run the RNC MML command ADD UCELLCLB (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell-Oriented Parameters for CLB interfreq Load
Balance Algorithm; CME batch modification center: Modifying UMTS Cell Parameters in Batches)
or MOD UCELLCLB (CME single configuration: UMTS Cell Configuration Express > Cell
Parameters > Cell-Oriented Parameters for CLB interfreq Load Balance Algorithm; CME batch
modification center: Modifying UMTS Cell Parameters in Batches). In this step, set the feature
parameters for a specified cell. Based on the site requirements, set CellLoadBalanceRange to
ONLY_TO_INTRA_RNC, ONLY_TO_INTER_RNC, or BOTH_TO_INTRA_RNC_AND_INTER_RNC
to enable intra-RNC inter-frequency load balancing, inter-RNC inter-frequency load balancing, or
intra- and inter-RNC inter-frequency load balancing, respectively. Keep the default settings of other
parameters, which are the thresholds for inter-frequency load balancing because of code resource,
cell credit resource, and MaxUserNumforCLBIFHO.
6. Optional: If CellLoadBalanceRange in step 5 is set to ONLY_TO_INTER_RNC or
BOTH_TO_INTRA_RNC_AND_INTER_RNC, Run the RNC MML commandSET UCLB (CME single
configuration: UMTS Radio Global Configuration Express > Load Control Parameter
Configuration > RNC Parameters for CLB interfreq Load Balance Algorithm; CME batch
modification center: Modifying RNC Parameters in Batches) to set the parameters related to the cell
load status of the neighboring RNC.
7. Optional: Run the RNC MML command SET ULDCPERIOD (CME single configuration: UMTS Radio
Global Configuration Express > Load Control Parameter Configuration > RNC Oriented LDC
Algorithm Cycle Length; CME batch modification center: Modifying RNC Parameters in Batches).
In this step, set ClbPeriodTimerLen.
8. Optional: If NODEB_CREDIT_CLB_SWITCH(NodeB Credit CLB Algorithm) or
LCG_CREDIT_CLB_SWITCH(Local Cell Group Credit CLB Algorithm)is selected under
NodeBLdcAlgoSwitch in step 3, Run the RNC MML command ADD UNODEBCLB (CME single
configuration: NodeB Configuration Express > IUB_RNC > NodeB Basic Information >
NodeB-Oriented Parameters for CLB interfreq Load Balance Algorithm; CME batch modification
center: Modifying Logical NodeB Parameters in Batches) or MOD UNODEBCLB (CME single
configuration: NodeB Configuration Express > IUB_RNC > NodeB Basic Information >
NodeB-Oriented Parameters for CLB interfreq Load Balance Algorithm; CME batch modification
center: Modifying Logical NodeB Parameters in Batches). In this step, set the feature parameters for
a specified NodeB. Keep the default parameter settings, which are the thresholds for inter-frequency
load balancing because of cell group credit resource and NodeB credit resource.
9. Optional: If UL_UU_CLB or DL_UU_CLB is selected under NBMLdcAlgoSwitch in step 2, Run the
RNC MML command ADD UCELLLDM (CME single configuration: UMTS Cell Configuration
Express > Cell Parameters > Cell Oriented LDM Algorithm Parameters; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) or MOD UCELLLDM (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Oriented LDM Algorithm
Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this
step, set the threshold for inter-frequency load balancing because of power resource for a specified
cell. Keep the default parameter settings.
10. Optional: Run the RNC MML command SET UCMCF (CME single configuration: UMTS Radio
Global Configuration Express > Compression Mode Parameter Configuration > RNC Oriented
CMCF Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in
Batches). In this step, set NCovCMUserNumCtrlSwitch and CellSFCMUserNumThd.
11. Optional: Run the RNC MML command ADD UCELLMCLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell-Oriented Based Measurement Inter-frequency
LDR Handover Algorithm Parameters; CME batch modification center: Modifying UMTS Cell
Parameters in Batches) or MOD UCELLMCLDR (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell-Oriented Based Measurement Inter-frequency
LDR Handover Algorithm Parameters; CME batch modification center: Modifying UMTS Cell
Parameters in Batches). In this step, set UESpdOptSwitch.
Activation Observation
Check the value of the counter VS.LCC.CLB.CS.InterFreq or VS.LCC.CLB.PS.InterFreq on the M2000.
If the value is not 0, this feature has been activated successfully.
Deactivation
1. Run the RNC MML command MOD UCELLLICENSE (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell License Resource/Function Item; CME batch
modification center: Modifying UMTS Cell Parameters in Batches). In this step, clear
//Enabling uplink Uu-interface load balancing, downlink Uu-interface load balancing, cell code resource
load balancing, and cell credit load balancing for a specified cell
ADD UCELLALGOSWITCH: CellId=1,
NBMLdcAlgoSwitch=UL_UU_CLB-1&DL_UU_CLB_1&CELL_CODE_CLB-1&CELL_CREDIT_CLB-1,
NBMUlCacAlgoSelSwitch=ALGORITHM_OFF, NBMDlCacAlgoSelSwitch=ALGORITHM_OFF; or
MOD UCELLALGOSWITCH: CellId=1,
NBMLdcAlgoSwitch=UL_UU_CLB-1&DL_UU_CLB_1&CELL_CODE_CLB-1&CELL_CREDIT_CLB-1;
//Enabling NodeB credit load balancing and local cell group credit load balancing for a specified NodeB
ADD UNODEBALGOPARA: IDTYPE=BYID, NodeBId=1,
NodeBLdcAlgoSwitch=NODEB_CREDIT_CLB_SWITCH-1&LCG_CREDIT_CLB_SWITCH-1; or
MOD UNODEBALGOPARA: IDTYPE=BYID, NodeBId=1,
NodeBLdcAlgoSwitch=NODEB_CREDIT_CLB_SWITCH-1&LCG_CREDIT_CLB_SWITCH-1;
//Setting the CLB priority for the inter-frequency neighboring cell of a specified cell
ADD UINTERFREQNCELL: RNCId=0, CellId=1, NCellRncId=1, NCellId=2, CLBFlag=TRUE, CLBPrio=1; or
MOD UINTERFREQNCELL: RNCId=0, CellId=1, NCellRncId=1, NCellId=2, CLBFlag=TRUE, CLBPrio=1;
//Disabling uplink Uu-interface load balancing, downlink Uu-interface load balancing, cell code resource
load balancing, and cell credit load balancing for a specified cell
MOD UCELLALGOSWITCH: CellId=1,
NBMLdcAlgoSwitch=UL_UU_CLB-0&DL_UU_CLB_0&CELL_CODE_CLB-0&CELL_CREDIT_CLB-0;
//Disabling NodeB credit load balancing and local cell group credit load balancing for a specified NodeB
MOD UNODEBALGOPARA: IDTYPE=BYID, NodeBId=1,
NodeBLdcAlgoSwitch=NODEB_CREDIT_CLB_SWITCH-0&LCG_CREDIT_CLB_SWITCH-0;
11.9.5 Troubleshooting
None
11.10.3 Deployment
Requirements
Hardware
This feature does not have any special requirements for hardware.
Other features
The feature WRFD-020400 DRD Introduction Package has been configured before this feature is
activated.
License
None
Data Preparation
Table 11-1 lists the data to prepare before activating this feature.
Table 11-1 Data to prepare before activating this feature
Parameter Name Parameter ID Setting Description Source
Inter-freq Redirect InterFreqRedirDelayThd 10 Network plan
Propa Delay Thres (internal plan)
Inter-freq Redirection InterFreqRedirFactorOfLD 50 Network plan
Factor of LDR R (internal plan)
Inter-freq Redirection InterFreqRedirFactorOfNo 0 Network plan
Factor of Normal rm (internal plan)
Redirection target RedirBandInd DependOnNCell Network plan
band indicator (internal plan)
Redirection Target UL ReDirUARFCNUplinkInd None Network plan
Frequency Index
Redirection target ReDirUARFCNUplink None Network plan
uplink UARFCN
Redirection target ReDirUARFCNDownlink None Network plan
downlink UARFCN
Activation
1. Run the RNC MML command SET UDISTANCEREDIRECTION (CME single configuration: UMTS
Radio Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented
Delay Based RRC Redirection Parameters; CME batch modification center: Modifying RNC
Parameters in Batches) for the RNC or ADD UCELLDISTANCEREDIRECTION (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell-Oriented Delay Based
RRC Redirection Parameters; CME batch modification center: Modifying UMTS Cell Parameters in
Batches)) for a cell. In this step, turn on InterFreqRedirSwitch, set RedirBandInd based on the
network plan, and set other parameters according to the prepared data.
− If
RedirBandInd is set to DependOnNCell, you do not need to set ReDirUARFCNUplinkInd,
ReDirUARFCNDownlink, and ReDirUARFCNUplink.
− If
RedirBandInd is set to other values, set ReDirUARFCNUplinkInd, ReDirUARFCNDownlink, and
ReDirUARFCNUplink based on the network plan.
Inter-frequency redirection based on distance does not select the inter-frequency neighboring cell under the DRNC as the
target cell. DRD and redirection at RRC connection setup do not select the inter-frequency neighboring cell that uses a
different frequency band from the cell where the RRC connection is to access.
Activation Observation
1. Start Uu Interface Trace on the RNC LMT. Under Uu Message Type, select
RRC_RRC_CONN_REJ.
2. Move a UE to a position where it has a distance from the NodeB but can still detect pilot signals.
Initiate a service using the UE, such as cs service.
The distance between the UE and the NodeB must be larger than InterFreqRedirDelayThd x 78.125 m/chip x 3 chips.
3. View the Uu interface tracing data.
− If
the RRC CONNECTION REJECT message includes the redirectionInfo IE and this IE contains
frequencyInfo (information about the cell), as shown in Figure 11-1, the RNC has redirected the UE
to an inter-frequency neighboring cell and this feature has been activated.
− If
the RRC CONNECTION REJECT message does not include the redirectionInfo IE, this feature
has not been activated.
Figure 11-1 redirectionInfo IE
Deactivation
To deactivate Inter-frequency Redirection Based on Distance at the RNC level, Run the RNC MML
command SET UDISTANCEREDIRECTION (CME single configuration: UMTS Radio Global
Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented Delay Based RRC
Redirection Parameters; CME batch modification center: Modifying RNC Parameters in Batches) to
turn off InterFreqRedirSwitch.
To deactivate Inter-frequency Redirection Based on Distance at the cell level, Run the RNC MML
command MOD UCELLDISTANCEREDIRECTION (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell-Oriented Delay Based RRC Redirection Parameters;
CME batch modification center: Modifying UMTS Cell Parameters in Batches) to turn off
InterFreqRedirSwitch.
11.10.5 Troubleshooting
You can check the propagation delay of the UEs in a cell to learn whether this feature is properly
triggered. If the value of the counter VS.RRC.Rej.Redir.Dist.IntraRat is not in accordance with the
propagation delay of the UEs in a cell, the feature is not functioning properly. For example, the counter
VS.RRC.Rej.Redir.Dist.IntraRat has a large value but the propagation delay of the UEs in a cell indicates
that this large number of redirections is not reasonable. If this happens, deactivate this feature.
Data Preparation
None
Activation
1. This feature can be activated by using either of the following methods according to the feature area:
− Toactivate this feature in the entire RNC, run the RNC MML command SET
UDISTANCEREDIRECTION (CME single configuration: UMTS Radio Global Configuration
Express > Directed Retry Parameter Configuration > RNC-Oriented Delay Based RRC
Redirection Parameters; CME batch modification center: Modifying RNC Parameters in Batches) to
set the RNC-level parameters.
− Set Redirection Switch to ON.
− Set Propagation delay threshold as specified in 3GPP TS 25.433.
− SetRedirection Factor Of LDR and Redirection Factor Of Normal to appropriate values based on
the network plan.
− To
activate this feature in a cell, run the RNC MML command ADD
UCELLDISTANCEREDIRECTION (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell-Oriented Delay Based RRC Redirection Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches) to set the cell-level parameters.
− Set Redirection Switch to ON.
− Set Propagation delay threshold as specified in 3GPP TS 25.433.
− SetRedirection Factor Of LDR and Redirection Factor Of Normal to appropriate values based on
the network plan.
Activation Observation
1. Initiate Uu interface message tracing on the RNC LMT, as shown in Figure 11-2
Figure 11-2 Uu Interface Trace dialog box
2. Simulate a scenario where pilot pollution occurs. Place the UE in a place where the UE is far away
from the NodeB and pilot signals are strong. Then, use the UE to establish a CS voice call.
3. Check the messages traced on the Uu interface.
− Asshown in Figure 11-3, if the RRC CONNECTION REJECT message contains the information
element (IE) GSM-Targetcellinfo, the RAN has redirected the UE to the GSM network, and this
feature has been activated.
− If
the RRC CONNECTION REJECT message does not contain the IE GSM-Targetcellinfo, this
feature is not activated.
Deactivation
1. This feature can be deactivated by using either of the following methods according to the feature
area:
− To deactivate this feature in the entire RNC, run the RNC MML command SET
UDISTANCEREDIRECTION (CME single configuration: UMTS Radio Global Configuration
Express > Directed Retry Parameter Configuration > RNC-Oriented Delay Based RRC
Redirection Parameters; CME batch modification center: Modifying RNC Parameters in Batches).
In this step, set Redirection Switch to OFF.
− To
deactivate this feature in a cell, run the RNC MML command MOD
UCELLDISTANCEREDIRECTION (CME single configuration: UMTS Cell Configuration Express >
Cell Parameters > Cell-Oriented Delay Based RRC Redirection Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches). In this step, set Redirection
Switch to OFF.
11.12.3 Deployment
Requirements
Hardware
This feature does not depend on the hardware.
Other features
The feature WRFD-020400 DRD Introduction Package has been configured before this feature is
activated.
License
The licenses "Inter System Redirect" on the RNC side have been activated. For details about the
license items and how to activate the license, see License Management Feature Parameter
Description.
Data Preparation
None
Activation
1. Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC
Parameters in Batches). In this step, set Direct Retry Switch to DR_RRC_DRD_SWITCH.
2. Run the RNC MML command SET UDRD (CME single configuration: UMTS Radio Global
Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented DRD
Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in Batches). In
this step, set ConnectFailRrcRedirSwitch to Allowed_To_Inter_RAT.
Activation Observation
1. Start Uu Interface Trace on the RNC LMT. Use a UE to initiate an RRC connection setup request.
2. The following procedure is traced on the Uu interface:
a The UE sends an RRC_SETUP_REQ message.
b The RNC responds with an RRC_CONN_REJ message, carrying GSM-TargetCellInfo in the IE
redirectioninfo.
Deactivation
1. Run the RNC MML command SET UDRD (CME single configuration: UMTS Radio Global
Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented DRD
Algorithm Parameters; CME batch modification center: Modifying RNC Parameters in Batches). In
this step, set RRC redirect switch to OFF or Only_To_Inter_Frequency.
11.13.3 Planning
N/A
11.13.4 Deployment
Requirements
License
The license for the WRFD-020120 Service Steering and Load Sharing in RRC Connection Setup
feature has been activated. For details about how to activate the license, see License Management
Feature Parameter Description.
Data Preparation
Table 11-2 lists the data to prepare before activating this feature.
Table 11-2 Data to prepare before activating this feature
Parameter Name Parameter ID Setting Notes Data source
Traffic Type TrafficType Determine which type of service can be Radio network plan
enabled with this feature by considering (internal)
the RAB DRD strategy.
Redirection Switch RedirSwitch Determine which type of service can be Radio network plan
enabled with this feature by considering (internal)
the RAB DRD strategy.
Direct Retry Switch DrSwitch: None Radio network plan
DR_RRC_DRD_ (internal)
SWITCH
RRC Redirection RedirEcN0Thd Set this parameter based on onsite Default
Ec/No Threshold situations. This parameter takes effect value/Recommend
only when the RedirBandInd parameter is ed value
set to a specific frequency band.
Redirection Factor Of RedirFactorOfN Set this parameter according to the Radio network plan
Normal orm service steering and load sharing strategy. (internal)
Redirection Factor Of RedirFactorOfL Set this parameter according to the Radio network plan
LDR DR service steering and load sharing strategy. (internal)
Redirection target RedirBandInd Set this parameter based on the carrier Radio network plan
band indicator information in section 11.13.2 "Required (internal)
Information."
If this parameter is set to
DependOnNCell, you do not need to set
the ReDirUARFCNUplinkInd,
ReDirUARFCNUplink, and
ReDirUARFCNDownlink parameters.
If this parameter is set to a specific
frequency band, frequencies configured
for the ReDirUARFCNUplink and
ReDirUARFCNDownlink parameters
must fall into this frequency band.
If this parameter is set to
BandIndNotUsed, frequencies
configured for the ReDirUARFCNUplink
and ReDirUARFCNDownlink
parameters are not restricted by the
Precautions
This feature must be considered in the radio network plan. Contact Huawei engineers before activating
this feature.
Configure parameters based on the Setting Notes in "Data Preparation" because parameters mutually affect each
other.
If one parameter is set both at the RNC level and at the cell level, the cell-level setting takes precedence.
Step 1 Run the RNC MML command SET UCORRMALGOSWITCH to activate RRC redirection. In this
step, select DR_RRC_DRD_SWITCH under the Direct Retry Switch parameter.
Step 2 Activate the Service Steering and Load Sharing in RRC Connection Setup feature and configure
related parameters.
RNC-level parameter configuration: Run the RNC MML command SET UREDIRECTION. In this step,
set the Traffic Type and Redirection Switch parameters to appropriate values to activate this feature
for the corresponding traffic type. Set the RRC Redirection Ec/No Threshold, Redirection Factor Of
Normal, Redirection Factor Of LDR, Redirection target band indicator, Redirection Target UL
Frequency Index, Redirection target uplink UARFCN, and Redirection target downlink UARFCN
parameters to appropriate values.
Cell-level configuration
− Forinitial parameter configuration: Run the RNC MML command ADD UCELLREDIRECTION. In this
step, set the Traffic Type and Redirection Switch parameters to appropriate values to activate this
feature for the corresponding traffic type. Set the RRC Redirection Ec/No Threshold, Redirection
Factor Of Normal, Redirection Factor Of LDR, Redirection target band indicator, Redirection
Target UL Frequency Index, Redirection target uplink UARFCN, and Redirection target
downlink UARFCN parameters to appropriate values.
− Forreconfiguration: Run the RNC MML command MOD UCELLREDIRECTION. In this step, set the
Traffic Type and Redirection Switch parameters to appropriate values to activate this feature for
the corresponding traffic type. Set the RRC Redirection Ec/No Threshold, Redirection Factor Of
Normal, Redirection Factor Of LDR, Redirection target band indicator, Redirection Target UL
Frequency Index, Redirection target uplink UARFCN, and Redirection target downlink
UARFCN parameters to appropriate values.
----End
//Activating RNC-level Service Steering and Load Sharing in RRC Connection Setup
SET UREDIRECTION: TrafficType=PSHSPA, RedirSwitch=ONLY_TO_INTER_FREQUENCY, RedirFactorOfNorm=0,
RedirFactorOfLDR=50, RedirBandInd=DependOnNCell, RedirEcN0Thd=-13;
//Activating cell-level Service Steering and Load Sharing in RRC Connection Setup for initial parameter
configuration
ADD UCELLREDIRECTION: CellId=1111, TrafficType=PSHSPA, RedirSwitch=ONLY_TO_INTER_FREQUENCY,
RedirFactorOfNorm=0, RedirFactorOfLDR=50, RedirBandInd=DependOnNCell, RedirEcN0Thd=-24;
//Activating cell-level Service Steering and Load Sharing in RRC Connection Setup for parameter
reconfiguration
MOD UCELLREDIRECTION: CellId=1111, TrafficType=PSHSPA, RedirSwitch=ONLY_TO_INTER_FREQUENCY,
RedirFactorOfNorm=0, RedirFactorOfLDR=50, RedirBandInd=DependOnNCell, RedirEcN0Thd=-24;
When configuring the Service Steering and Load Sharing in RRC Connection Setup 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.
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
Configure parameters based on the Setting Notes in "Data Preparation" because parameters mutually affect each
other.
SN 2 is for RNC-level parameter configuration and SN 3 is for cell-level parameter configuration. If one parameter is set
both at the RNC level and at the cell level, the cell-level setting takes precedence.
Activation Observation
After the Service Steering and Load Sharing in RRC Connection Setup feature is activated, query the
value of the VS.RRC.Rej.Redir.Service counter to determine whether this feature is activated. If the
value of this counter is not 0, this feature is activated.
//Deactivating cell-level Service Steering and Load Sharing in RRC Connection Setup
MOD UCELLREDIRECTION: CellId=1111, TrafficType=PSHSPA, RedirSwitch=OFF;
When configuring the Service Steering and Load Sharing in RRC Connection Setup 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.
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
SN 1 is for RNC-level parameter configuration and SN 2 is for cell-level parameter configuration. If one parameter is set
both at the RNC level and at the cell level, the cell-level setting takes precedence.
11.13.7 Troubleshooting
N/A
− Analyzethe VS.RRC.FailConnEstab.NoReply counter in the live network. The RRC connection setup
cause that has the largest contribution to RRC connection setup failures is the RRC connection setup
cause for enabling this function.
− Determine the RRC connection setup cause whose RRC connection setup success rate needs to be
improved in the live network.
Determine target cells for enabling this function:
Step 1 Determine cells that require this feature when the following requirements are met:
Most RRC connection setup failures are caused by the reason of the VS.RRC.FailConnEstab.NoReply
counter. That is, most RRC connection setup failures are caused by RRC connection setup timeout.
Step 2 Select cells where downlink weak coverage has large contribution to RRC connection setup
failures. For example, the contribution is larger than 50%. Collect the RRC setup success rate
corresponding to the RRC connection setup cause. Compare the effect of this feature on the
RRC setup success rate.
Step 3 Select cells where RRC and RAB establishment failures are caused by downlink power resource
congestion. Enable this function for these cells with caution. If the number of RRC and RAB
establishment failures caused by downlink power resource congestion is large, you are not
advised to enable this function.
You can monitor the following counters to determine the number of RRC connection setup and RAB
setup failures caused by downlink power resource congestion:
VS.RRC.Rej.DLPower.Cong
VS.RAB.FailEstabPS.DLPower.Cong
VS.RAB.FailEstabCS.DLPower.Cong
----End
Determine whether there are signaling storms and traffic bursts during gatherings or festivals in the
live network. If yes, you are not advised to enable this function.
11.14.3 Planning
N/A
11.14.4 Deployment
Requirements
None
Data Preparation
Table 11-5 lists the data to prepare before enabling this function.
Table 11-5 Data to prepare before enabling this function
Parameter Parameter Setting Notes Data Source
Name ID
Timer 381 T381 If N300 is set to 0, set this parameter to a Radio network plan
value other than D0 to trigger this function. (internal)
You can set this parameter to the
recommended value.
FACH Power FACHPowe Set this parameter to the recommended Radio network plan
Increase Ec/No r4RRCRep value. (internal)
Threshold EcNoThd
Max Transmit MaxFachPo Existing networks: Set this parameter to a Radio network plan
Power of FACH wer value 2 dB higher than the original value. (internal)
Note that the value of this parameter must
not be higher than 3 dB.
New networks: Set this parameter to 3 dB.
Bearing Signal SIGRBIND If FACHs whose MaxFACHPower is Radio network plan
Indication modified are used to send signaling (internal)
messages, this parameter must be set to
TRUE. This parameter must be used
together with the TrChId parameter.
Cell ID CellId None Radio network plan
(internal)
FACH ID TrChId This parameter is used to locate the Radio network plan
transmission channels whose SIGRBIND is (internal)
set to TRUE and to modify the settings of
MaxFACHPower and OffsetFACHPower of
the FACHs corresponding to this parameter.
Offset between OffsetFAC Existing networks: Set this parameter to a Default
Initial and Max HPower value that has the same increase as the value/Recommende
FACHPower MaxFACHPower parameter. d value
New networks: Set this parameter to 2 dB.
Precautions
You are not advised to enable this function if there are signaling storms and traffic bursts in the live
network.
You can perform either of the two operations in step 1 to trigger this function.
Step 2 Configure the RRC connection setup cause that requires this function and the corresponding
threshold.
Run the RNC MML command SET URRCESTCAUSE. In this step, set Cause of RRC connection
establishment and FACH Power Increase Ec/No Threshold to appropriate values.
Step 3 Modify parameters related to the FACH transmit power. For existing cells: Run the RNC MML
command MOD UFACH. In this step, set Cell ID, FACH ID, Max Transmit Power of FACH, and
Offset between Initial and Max FACHPower to appropriate values.
Step 4 For new cells: Run the RNC MML command ADD UFACH. In this step, set Cell ID, FACH ID,
Max Transmit Power of FACH, and Offset between Initial and Max FACHPower to
appropriate values.
You are only required to modify the Max Transmit Power of FACH and Offset between Initial and Max FACHPower of
the transmission channels whose Bearing Signal Indication is set to TRUE. You can use FACH ID to locate these
transmission channels.
Before running the RNC MML command MOD UFACH, run the RNC MML command LST UFACH to list the transmission
channels whose Bearing Signal Indication is set to TRUE.
----End
When configuring the FACH power control of RRC phase function 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 described in Table 11-6. For
instructions on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
You can perform either of the two operations in SN 1 to trigger this function.
In SN 3, you are only required to modify the Max Transmit Power of FACH and Offset between Initial and Max
FACHPower of the transmission channels whose Bearing Signal Indication is set to TRUE. You can use FACH ID to
locate these transmission channels. Before performing SN 3, query the transmission channels whose Bearing Signal
Indication is set to TRUE.
Activation Observation
Observe the cell tracing results on the RNC LMT.
If Transmit Power Level in the FACH FP packet is 0, this feature is enabled, as shown in 0. If
Transmit Power Level in the FACH FP packet is the value of the Offset between Initial and Max
FACHPower parameter, this feature is not enabled.
Figure 11-4 Transmit Power Level in the FACH FP packet
This function cannot be triggered if the traced cell is in the OLC state.
Run the RNC MML command MOD UFACH. In this step, set Cell ID, FACH ID, Max Transmit Power
of FACH, and Offset between Initial and Max FACHPower to appropriate values. Modify Max
Transmit Power of FACH and Offset between Initial and Max FACHPower to the original values.
When configuring the FACH power control of RRC phase function 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.
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
In SN 2, set Max Transmit Power of FACH and Offset between Initial and Max FACHPower to the values before
feature activation.
Table 11-9 lists counters related to the number of successful RRC connection setups corresponding to
different RRC connection setup causes.
Table 11-9 Counters related to the number of successful RRC connection setups
Counter Counter Name Description
ID
67179457 RRC.SuccConnEstab.OrgConvCall Number of Successful RRC Connection Setups for
Cell (Originating Conversational Call)
67179458 RRC.SuccConnEstab.OrgStrCall Number of Successful RRC Connection Setups for
Cell (Originating Streaming Call)
67179459 RRC.SuccConnEstab.OrgInterCall Number of Successful RRC Connection Setups for
Cell (Originating Interactive Call)
67179460 RRC.SuccConnEstab.OrgBkgCall Number of Successful RRC Connection Setups for
Cell (Originating Background Call)
67179461 RRC.SuccConnEstab.OrgSubCall Number of Successful RRC Connection Setups for
Cell (Originating Subscribed traffic Call)
67179462 RRC.SuccConnEstab.TmConvCall Number of Successful RRC Connection Setups for
Cell (Terminating Conversational Call)
11.14.7 Troubleshooting
None
− VS.MeanRTWP.Locell.SectorEqm.Ant2
− VS.MeanRTWP.Locell.SectorEqm.Ant3
NOTE
Each of the preceding counters indicates the mean RTWP of a specific antenna.
On the RNC side: VS.MeanRTWP
NOTE
The preceding counter indicates the mean RTWP of a cell.
Step 4 Collect the following RNC counters and KPIs in a cell before feature activation to observe the
effect of this function:
KPIs: CS RAB Setup Success Ratio, PS RAB Setup Success Ratio, CS Service Drop Ratio, and PS
Call Drop Ratio
Counters: VS.HSUPA.MeanChThroughput, VS.HSUPA.MeanBitRate,
VS.HSUPA.MeanBitRate.WithData, VS.MeanULActualPowerLoad, VS.ValidAntRatio.Mean, and
VS.MeanRTWP
----End
11.15.3 Planning
None
11.15.4 Deployment
Requirements
Hardware
The BTS3812E, BTS3812A, and BTS3812AE do not support this function.
The DBS3800 does not support this function.
3900 series base stations do not support this function if configured with the WBBPa board or the 20 W
RRU3801C.
Data Preparation
Table 11-11 lists the data to prepare before enabling this function.
Table 11-11 Data to prepare before enabling this function
Parameter Parameter Setting Notes Data Source
Name ID
Anti-Antenna ANTIANTE Enable this function if information in section Default
Imbalance NNAIMBAL 11.15.2 "Required Information" meets the value/Recommende
Algorithm ANCESW requirements in section 11.15.1 "When to d value
Switch Use Anti-Imbalance of the Different
Antenna."
When configuring the anti-imbalance of the different antenna function 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.
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
Activation Observation
Step 1 Run the NodeB MML command LST ULOCELLALGPARA to check whether this function is
enabled.
Step 2 Query the value of the VS.ValidAntRatio.Mean counter on the NodeB side.
Expected result: After this function is enabled, the value of this counter is smaller than or equal to the
value before the enabling of this function.
Step 3 Query the value of the VS.MeanRTWP counter on the RNC side.
Expected result: After this function is enabled, the value of this counter is smaller than or equal to the
value before the enabling of this function.
----End
When configuring the anti-imbalance of the different antenna function 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.
Step 1 Configure a single object (such as a cell) on the CME. Set the parameter described in Table
11-13 on the CME. For instructions on how to perform the CME single configuration, see CME
Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
11.15.7 Troubleshooting
None
11.16.3 Deployment
Requirements
None
Data Preparation
None
Activation
1. Run the RNC MML command ADD UINTRAFREQNCELL (CME single configuration: UMTS Cell
Configuration Express > Neighboring Cell > Intra-frequency Neighboring Cell; CME batch
modification center: not supported) to add an intra-frequency neighboring cell.
2. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, select
INTRA_FREQUENCY_LDB(Intra Frequency LDB Algorithm) from the Cell LDC algorithm switch
drop-down list.
3. Run the RNC MML command SET ULDCPERIOD (CME single configuration: UMTS Radio Global
Configuration Express > Load Control Parameter Configuration > RNC Oriented LDC
Algorithm Cycle Length; CME batch modification center: Modifying RNC Parameters in Batches).
In this step, set Intra-frequency LDB period timer length to an appropriate value.
4. Run the RNC MML command MOD UCELLLDB (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Oriented LDB Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches) to set the following
parameters associated with the cell-level intra-frequency load balancing (LDB) algorithm to
appropriate values:
− Cell overload threshold
− Pilot power adjustment step
− Cell under load threshold
5. Run the RNC MML command MOD UPCPICHPWR (CME single configuration: UMTS Cell
Configuration Express > Channel Configuration > PCPICH; CME batch modification center:
Modifying UMTS Channel Parameters in Batches). In this step, set P-CPICH parameters associated
with intra-frequency LDB, including Max transmit power of PCPICH and Min transmit power of
PCPICH to appropriate values.
Activation Observation
To verify that the RNC can balance the cell load by adjusting the P-CPICH power of a cell, perform the
following steps:
1. On the RNC LMT, open the Monitor tab page. Create the task of monitoring PCPICH TxPower of
CELL_A11.
2. Run the NodeB MML command STR DLSIM to simulate high load in CELL_A11.
3. In the Cell Performance Monitoring dialog box, check the pilot power of CELL_A11.
Expected result: As the cell load increases, the pilot power periodically decreases. The actual pilot
power must not be decreased to a level lower than the configured minimum pilot power.
4. The NBAP_CELL_RECFG_REQ and NBAP_CELL_RECFG_RSP messages should be displayed in
the Iub tracing result. In the NBAP_CELL_RECFG_REQ message, check whether the RNC has
reduced the pilot power.
5. Run the NodeB MML command STR DLSIM to stop simulating high load in CELL_A11.
6. In the Cell Performance Monitoring dialog box, check the pilot power of CELL_A11.
Expected result: As the cell load becomes normal, the pilot power periodically increases. The actual
pilot power must not be increased to a level higher than the configured maximum pilot power.
Deactivation
1. Run the RNC MML command MOD UCELLALGOSWITCH (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell Algorithm Switches; CME batch modification
center: Modifying UMTS Cell Parameters in Batches). In this step, clear INTRA_FREQUENCY_LDB
from the Cell LDC algorithm switch drop-down list.
2. Restore the parameter settings modified in the activation procedure.
//Setting parameters associated with the cell-oriented intra-frequency LDB algorithm to appropriate
values
MOD UCELLLDB: CellId=111, PCPICHPowerPace=2, CellOverrunThd=90, CellUnderrunThd=30;
11.17.3 Deployment
Requirements
Hardware
− Toenable the common preemption function, the CN must send the allocation/retention priority (ARP)
IE to the RNC during the RAB assignment procedure so that the RNC can obtain RAB service
priorities.
− The forced preemption function does not depend on the CN.
Other features
The following features must be configured before this feature is activated: WRFD-010610 HSDPA
Introduction Package and WRFD-010612 HSUPA Introduction Package.
License
The licenses "Queuing and Pre-emption" on the RNC side have been activated. For details about the
license items and how to activate the license, see License Management Feature Parameter
Description.
Data Preparation
None
If step 3 is performed, the preemption function enabled in step 1 will become disabled and the forced preemption function
will take effect.
----End
When configuring the Queuing and Preemption 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.
Step 1 Configure a single object (such as a cell) on the CME. Set the parameter described in Table
11-15. For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
If the forced preemption function is enabled, the preemption function enabled by setting the Preempt algorithm switch
parameter will become disabled.
Activation Observation
The queuing function is enabled if the value of any of the following counters is not 0.
VS.RAB.Estab.QueueTime.CS
VS.RAB.Estab.QueueTime.PS
The preemption function is enabled if the value of any of the following counters is not 0.
VS.RAB.AbnormRel.CS.Preempt
VS.RAB.AbnormRel.PS.Preempt
RRC.AttConnRelDCCH.Preempt
RRC.AttConnRelCCCH.Preempt
When configuring the Queuing and Preemption 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.
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
11.18.3 Deployment
Requirements
Hardware
This feature does not depend on the hardware.
Other features
This feature does not depend on other features.
License
The licenses "RAB Downsizing at Admission Control" on the RNC side have been activated. For
details about the license items and how to activate the license, see License Management Feature
Parameter Description.
Other prerequisites
− For Iu QoS negotiation, the CN nodes must support this feature.
− For RAB rate reduction, the CN nodes do not need to support this feature.
Data Preparation
None
Activation
Activating QoS negotiation
1. Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC
Parameters in Batches). In this step, set Dynamic Resource Allocation Switch to
DRA_DCCC_SWITCH, and set PS rate negotiation switch to PS_BE_IU_QOS_NEG_SWITCH
and PS_STREAM_IU_QOS_NEG_SWITCH.
Activating RAB rate reduction
1. Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC
Parameters in Batches). In this step, set Dynamic Resource Allocation Switch to
DRA_DCCC_SWITCH, and set PS rate negotiation switch to PS_RAB_DOWNSIZING_SWITCH.
Activation Observation
Verifying QoS negotiation
1. Run the RNC MML command LST UCORRMALGOSWITCH to query the activation result.
2. Start Iu message tracing on the RNC LMT and establish a PS service, as shown in Figure 11-5.
Deactivation
Deactivating QoS negotiation
1. Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC
Parameters in Batches). In this step, clear DRA_DCCC_SWITCH from the Dynamic Resource
Allocation Switch drop-down list box, and clear PS_BE_IU_QOS_NEG_SWITCH and
PS_STREAM_IU_QOS_NEG_SWITCH from the PS rate negotiation switch drop-down list box.
Deactivating RAB rate reduction
2. Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration: UMTS
Radio Global Configuration Express > Connection_Oriented RRM Switch Configuration >
Connection Oriented Algorithm Switches; CME batch modification center: Modifying RNC
Parameters in Batches). In this step, clear DRA_DCCC_SWITCH from the Dynamic Resource
Allocation Switch drop-down list box, and clear PS_RAB_DOWNSIZING_SWITCH from the PS
rate negotiation switch drop-down list box.
Before activating this feature, ensure that the current area is continuously covered by a carrier or
several carriers. If not, coverage holes will occur, causing the handover success rate and call drop rate
to deteriorate.
Network coverage
Obtain the coverage of carriers that are to be activated with this feature. If cell coverage shrinks when
the P-CPICH transmit power is within the adjustment scope, coverage holes will occur. In this situation,
you must estimate the impact of coverage holes on network performance to determine whether to
activate this feature. If the value of the KPI Soft Handover Overhead is high (higher than 30%), cell
coverage is good.
P-CPICH power in a cell
Obtain the P-CPICH power configured for the current cell before activating this feature. If the
configured P-CPICH power is low (For example, the proportion of PCPICHPower to MaxTxPower is
lower than 5%), the gains provided by this feature are small but the negative impact of this feature is
great. In this case, you are not advised to activate this feature.
Number of UEs in a cell
The gains provided by this feature are noticeable only when there is a large number of UEs in the cell.
Obtain the number of UEs in this cell by querying the value of the VS.CellDCHUEs counter.
Non-HSPA power load in a cell
This feature reduces the P-CPICH transmit power only when the downlink non-HSPA power load in
this cell is heavy. Before activating this feature, you are required to estimate the downlink non-HSPA
power load based on the linear value of the difference between the VS.MeanTCP.NonHS counter and
the MaxTxPower parameter. If the load is heavy, downlink non-HSPA power load in this cell is heavy.
11.19.3 Planning
None
11.19.4 Deployment
Requirements
License
The license for the WRFD-150236 Load Based Dynamic Adjustment of PCPICH feature has been
activated.
Feature ID Feature Name License Description NE Sales
Unit
WRFD-15023 Load Based Dynamic Load Based Dynamic RNC per cell
6 Adjustment of PCPICH Adjustment of PCPICH (per
cell)
Data Preparation
Table 11-17 lists the data to prepare before activating this feature.
Table 11-17 Data to prepare before activating this feature
Parameter Parameter ID Setting Notes Data Source
Name
Switch for NBMLdcAlgoSwitc Turn on this switch if the live network meets Default
When configuring the Load Based Dynamic Adjustment of PCPICH 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.
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
Activation Observation
This feature is activated if values of the VS.CellBreath.CPICHUp and VS.CellBreath.CPICHDown
counters are not 0.
Ensure that the TCP-based intra-frequency load balancing function is not enabled in the measurement period. Otherwise,
the value of the VS.CellBreath.CPICHUp or VS.CellBreath.CPICHDown counter may be collected based on the
TCP-based intra-frequency load balancing function.
When configuring the Load Based Dynamic Adjustment of PCPICH 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.
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions o how to perform a batch modification through the CME batch modification center, press F1
on the wizard interface to obtain online help.
----End
Counter Description
Breathing for Cell
Check the reduced downlink non-HSPA power consumption by querying the value of the counter listed
in Table 11-21 in the case of downlink power congestion.
The value of the VS.MeanTCP.NonHS counter decreases after feature activation if the traffic volume in
the cell remains unchanged.
Table 11-21 Counter
Counter Description
VS.MeanTCP.NonHS Mean Non-HSDPA Transmitted Carrier Power for Cell
11.19.7 Troubleshooting
None
12 Parameters
Table 12-1 Parameter description
Parameter NE MML Feature ID Feature Description
ID Command Name
BeInitBitrat BSC6900/BSC6 SET UFRC None None Meaning:Specifies the type of the
eTypeforC 910 channel for carrying PS BE services
BGNULLo BSC6900/BSC6 ADD WRFD-020 Admission Meaning:Uplink cell load threshold for
adThd 910 UCELLCA 101 Control the optimized background noise
C algorithm. When "BGNOptSwitch" is
set to ON, the RNC checks whether
MOD the "ULTotalLoad" value is equal to or
UCELLCA smaller than the "BGNULLoadThd"
C value. If yes, the algorithm uses the
difference between the current RTWP
and the "ULTotalLoad" value.
GUI Value Range:0~100
Actual Value Range:0~100
Unit:%
Default Value:10
CellOverru BSC6900/BSC6 ADD WRFD-020 Intra Meaning:If the cell downlink load
nThd 910 UCELLLD 104 Frequency exceeds this threshold, the algorithm
B Load Balance will decrease the pilot transmit power
of the cell so as to increase the whole
MOD system's capacity. This parameter is
UCELLLD based on network planning.
B
GUI Value Range:0~100
Actual Value Range:0~100
Unit:%
Default Value:90
CellSfCSCl BSC6900/BSC6 ADD WRFD-140 Inter-Frequen Meaning:SF usage threshold for the
bTrigThd 910 UCELLCL 217 cy Load CLB feature specific to CS services.
B Balancing When the SF usage in a cell is equal
Based on to or higher than this threshold, the
MOD Configurable RNC initiates inter-frequency
UCELLCL Load handovers specific to CS services in
B Threshold the cell to reduce Cell load. Because
of load fluctuation, the value
difference between
"CellSfCSClbRelThd" and
"CellSfCSClbTrigThd" should be
larger than 10%. Otherwise, a cell will
frequently enter and leave the CLB
state.
GUI Value Range:0~100
Actual Value Range:0~100
Unit:%
Default Value:100
CellSfPSCl BSC6900/BSC6 ADD WRFD-140 Inter-Frequen Meaning:SF usage threshold for the
bTrigThd 910 UCELLCL 217 cy Load CLB feature specific to PS services.
B Balancing When the SF usage in a cell is equal
Based on to or higher than this threshold, the
MOD Configurable RNC initiates inter-frequency
UCELLCL Load handovers specific to PS services in
B Threshold the cell to reduce Cell load.Because
of load fluctuation, the value
CellUnderr BSC6900/BSC6 ADD WRFD-020 Intra Meaning:If the cell downlink load is
unThd 910 UCELLLD 104 Frequency lower than this threshold, the
B Load Balance algorithm will increase the pilot
transmit power of the cell so as to
MOD share load of other cells. This
UCELLLD parameter is based on network
B planning.
GUI Value Range:0~100
Actual Value Range:0~100
Unit:%
Default Value:30
ChoiceRprt BSC6900/BSC6 SET WRFD-020 Load Meaning:If you set this parameter to
UnitForDlB 910 ULDM 102 Measurement TEN_MSEC, use [DL basic meas rprt
asicMeas cycle,Unit:10ms] to specify the
measurement 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.
GUI Value Range:TEN_MSEC, MIN
Actual Value Range:TEN_MSEC,
MIN
Unit:None
Default Value:TEN_MSEC
ChoiceRprt BSC6900/BSC6 SET WRFD-020 Load Meaning:If you set this parameter to
UnitForHsd 910 ULDM 102 Measurement TEN_MSEC, use [HSDPA need pwr
paPwrMea meas cycle,Unit:10ms] to specify the
s measurement report period. If you set
this parameter to MIN, use [HSDPA
ChoiceRprt BSC6900/BSC6 SET WRFD-020 Load Meaning:If you set this parameter to
UnitForHsd 910 ULDM 102 Measurement TEN_MSEC, use [HSDPA bit rate
paRateMe meas cycle,Unit:10ms] to specify the
as 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.
GUI Value Range:TEN_MSEC, MIN
Actual Value Range:TEN_MSEC,
MIN
Unit:None
Default Value:TEN_MSEC
ChoiceRprt BSC6900/BSC6 SET WRFD-020 Load Meaning:If you set this parameter to
UnitForHs 910 ULDM 102 Measurement TEN_MSEC, use [HSDPA bit rate
upaRateM meas cycle,Unit:10ms] to specify the
eas 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.
GUI Value Range:TEN_MSEC, MIN
Actual Value Range:TEN_MSEC,
MIN
Unit:None
Default Value:TEN_MSEC
ChoiceRprt BSC6900/BSC6 SET WRFD-020 Load Meaning:If you set this parameter to
UnitForUlB 910 ULDM 102 Measurement TEN_MSEC, use [UL basic meas rprt
asicMeas cycle,Unit:10ms] to specify the
DlBeTraffIn BSC6900/BSC6 SET UFRC WRFD-021 Dynamic Meaning:DL initial access rate of PS
itBitrate 910 101 Channel background or interactive service.
Configuration When DCCC function is enabled, the
Control downlink initial access rate will be set
DlLdrRelT BSC6900/BSC6 ADD WRFD-020 Load Meaning:If the ratio of DL load of the
hd 910 UCELLLD 106 Reshuffling cell to the downlink capacity is lower
M than this threshold, the DL load
reshuffling function of the cell is
DlLdrTrigT BSC6900/BSC6 ADD WRFD-020 Load Meaning:If the ratio of DL load of the
hd 910 UCELLLD 106 Reshuffling cell to the downlink capacity is not
M lower than this threshold, the DL load
reshuffling function of the cell is
MOD triggered. After the basic congestion
UCELLLD state of the cell load is released, the
M system no longer implements the
LDR action. Because the load
fluctuates, the difference between the
LDR release threshold and trigger
threshold should be higher than 10%.
The ping-pong effect of the
preliminary congestion state will occur
easily.
GUI Value Range:0~100
Actual Value Range:0~100
Unit:%
Default Value:70
DlLdTrnsH BSC6900/BSC6 ADD WRFD-020 Load Meaning:If the DL load state of the
ysTime 910 UCELLLD 102 Measurement cell is lasted longer than this
M threshold, the DL load state of the cell
transfers.
MOD
UCELLLD GUI Value Range:10~600000
M
Actual Value Range:10~600000
Unit:ms
Default Value:1000
DlOlcRelT BSC6900/BSC6 ADD WRFD-020 Overload Meaning:If the ratio of DL load of the
hd 910 UCELLLD 107 Control cell to the downlink capacity is lower
M than this threshold, the DL overload
and congestion control function of the
MOD cell is stopped. The value of the OLC
UCELLLD release threshold should not be much
M lower than or close to the OLC trigger
threshold, or the system state will
have a ping-pong effect easily. The
DlOlcTrigT BSC6900/BSC6 ADD WRFD-020 Overload Meaning:If the ratio of DL load of the
hd 910 UCELLLD 107 Control cell to the downlink capacity is not
M lower than this threshold, the DL
overload and congestion control
MOD function of the cell is triggered. The
UCELLLD value of the OLC release threshold
M should not be much lower than or
close to the OLC trigger threshold, or
the system state will have a
ping-pong effect easily. The
recommended difference between the
OLC release threshold and the OLC
DrSwitch BSC6900/BSC6 SET WRFD-010 HSDPA DRD Meaning:Direct retry switch group.
910 UCORRM 61112
ALGOSWI Service 1) DR_RRC_DRD_SWITCH(DRD
TCH WRFD-020 Steering and switch for RRC connection): When
120 Load Sharing the switch is on, DRD and redirection
in RRC is performed for RRC connection if
WRFD-020 Connection retry is required.
40001 Setup
2)
WRFD-020 Intra System DR_RAB_SING_DRD_SWITCH(DR
40002 Direct Retry D switch for single RAB): When the
WRFD-020 Inter System switch is on, DRD is performed for
40003 single service if retry is required.
Direct Retry
WRFD-020 Inter System 3)
40004 DR_RAB_COMB_DRD_SWITCH(DR
Redirect D switch for combine RAB): When the
Traffic switch is on, DRD is performed for
Steering and combined services if retry is required.
Load Sharing 4)
During RAB DR_INTER_RAT_DRD_SWITCH(INT
Setup ER-RAT DRD switch): When this
switch is turned on, inter-RAT directed
retry is supported.
GUI Value
Range:DR_RRC_DRD_SWITCH,
DR_RAB_SING_DRD_SWITCH,
DR_RAB_COMB_DRD_SWITCH,
DR_INTER_RAT_DRD_SWITCH
Actual Value
Range:DR_RRC_DRD_SWITCH,
DR_RAB_SING_DRD_SWITCH,
DR_RAB_COMB_DRD_SWITCH,
DR_INTER_RAT_DRD_SWITCH,
Unit:None
Default
Value:DR_RRC_DRD_SWITCH-1&D
EcN0Effect BSC6900/BSC6 ADD WRFD-010 3.4/6.8/13.6/2 Meaning:Time period for valid Ec/No
Time 910 UCELLFR 510 7.2Kbps RRC or RSCP. This parameter defines the
C Connection time period during which the reported
WRFD-150 and Radio values of Ec/No or RSCP are
MOD 232 Access considered as valid values. The time
UCELLFR Bearer period starts from the time the system
C Establishmen receives the first Ec/No or RSCP.
t and Release
GUI Value Range:0~65535
Multiband
Direct Retry Actual Value Range:0~65535
Based on UE Unit:ms
Location
Default Value:5000
HsupaInitia BSC6900/BSC6 SET UFRC WRFD-010 HSUPA Meaning:HSUPA BE traffic initial bit
lRate 910 61208 DCCC rate. When DCCC 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
MaxFachP BSC6900/BSC6 ADD WRFD-020 Open Loop Meaning:The offset between the
ower 910 UFACH 501 Power FACH transmit power and P-CPICH
Control transmit power in a cell.
MOD
UFACH GUI Value Range:-350~150
Actual Value Range:-35~15
Unit:0.1dB
Default Value:10
MbmsDec BSC6900 ADD WRFD-020 Load Meaning:When the priority of the RAB
PowerRab UCELLLD 106 Reshuffling of MBMS services exceeds this
Thd R threshold, reconfigure the MBMS
power to the minimum power. The
PCPICHPo BSC6900/BSC6 ADD WRFD-020 Open Loop Meaning:TX power of the P-CPICH in
wer 910 UPCPICH 501 Power a cell. This parameter should be set
Control based on the actual system
MOD environment such as cell coverage
UCELL (radius) and geographical
environment. For the cells to be
covered, the downlink coverage must
be guaranteed. For the cells requiring
soft handover area, this parameter
should satisfy the proportion of soft
handover areas stipulated in the
network plan. For detailed information
about this parameter, refer to 3GPP
TS 25.433.
GUI Value Range:-100~500
Actual Value Range:-10~50
Unit:0.1dBm
PenaltyTim BSC6900/BSC6 SET UCLB WRFD-140 Inter-Frequen Meaning:imer for cell punishment
eforHLoad 910 217 cy Load after a failed inter-RNC
3GCell Balancing inter-frequency handover. During the
Based on period specified by this timer, the cell
Configurable in question is no longer allowed to
Load accommodate the UEs handed over
Threshold from another cell.
GUI Value Range:0~7200
Actual Value Range:0~7200
Unit:s
Default Value:300
PollTimerL BSC6900/BSC6 SET WRFD-010 Queuing and Meaning:Timer length of the queue
en 910 UQUEUEP 505 Pre-Emption poll. The queue is polled for every
REEMPT time specified in this parameter.
During each poll, all 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.
GUI Value Range:1~80
Actual Value Range:10~800
Unit:10ms
Default Value:50
QueueLen BSC6900/BSC6 SET WRFD-010 Queuing and Meaning:Queue length. The total
910 UQUEUEP 505 Pre-Emption number of users in queue of each cell
REEMPT should not exceed the value specified
in this 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.
GUI Value Range:5~20
Actual Value Range:5~20
Unit:None
Default Value:5
RedirEcN0 BSC6900/BSC6 SET WRFD-020 Inter System Meaning:When the target UARFCN of
Thd 910 UREDIRE 40003 Redirect redirection indicates a specific
CTION frequency band and the Ec/N0 value
of the current cell carried in the RRC
Connection Request message is
smaller than the value of this
parameter, service-based RRC
redirection is forbidden. For details,
see 3GPP TS 25.215.
GUI Value Range:-24~0
Actual Value Range:-24~0
Unit:dB
Default Value:-24
RedirEcN0 BSC6900/BSC6 ADD WRFD-020 Inter System Meaning:When the target UARFCN of
Thd 910 UCELLRE 40003 Redirect redirection indicates a specific
DIRECTIO frequency band and the Ec/N0 value
N of the current cell carried in the RRC
Connection Request message is
MOD smaller than the value of this
UCELLRE parameter, service-based RRC
DIRECTIO redirection is forbidden. For details,
N see 3GPP TS 25.215.
GUI Value Range:-24~0
Actual Value Range:-24~0
Unit:dB
Default Value:-24
RedirFacto BSC6900/BSC6 ADD WRFD-020 Inter-RAT Meaning:When the load of the serving
rOfNorm 910 UCELLDIS 401 Redirection cell is within the normal range, a UE
TANCERE Based on may be redirected to another cell
DIRECTIO Distance according to the distance between UE
N and current cell. This parameter
specifies the possibility of inter-RAT
MOD RRC redirecting the UE to another
UCELLDIS cell. When this parameter is set to 0,
TANCERE the inter-RAT RRC redirection is not
DIRECTIO performed if the load of the serving
N cell is within the normal range.
GUI Value Range:0~100
Actual Value Range:0~100
Unit:%
Default Value:0
RlMaxDlP BSC6900/BSC6 ADD WRFD-020 Open Loop Meaning:This parameter specifies the
wr 910 UCELLRL 501 Power maximum DL RL power to be
PWR Control assigned.
WRFD-020
MOD 101 Admission This parameter should fulfill the
UCELLRL Control coverage requirement of the network
planning, and the value is relative to
RlMinDlPw BSC6900/BSC6 ADD WRFD-020 Open Loop Meaning:This parameter specifies the
r 910 UCELLRL 501 Power minimum DL RL power to be
PWR Control assigned.
MOD The value of this parameter varies
UCELLRL with the service type. In addition, this
PWR parameter is relevant to
"RlMaxDlPwr" and dynamic
adjustment range of power control.
Their relationship is explained in the
following formula:
RlMinDlPwr = RlMaxDlPwr - Dynamic
adjustment range of power control
Dynamic adjustment range of power
control is tunable and its
recommended value is 15 dB. For
detailed information of this parameter,
refer to 3GPP TS 25.433.
GUI Value Range:-350~150
Actual Value Range:-35~15
Unit:0.1dB
Default Value:None
RTWPLigh BSC6900/BSC6 ADD WRFD-020 Intra Meaning:RTWP light threshold for the
tThd 910 UCELLUL 104 Frequency load balancing algorithm based on
B Load Balance RTWP. If power in a cell is less than
the threshold, CPICH power in the
MOD cell will be increased.
UCELLUL
B GUI Value Range:0~100
Actual Value Range:0~100
Unit:%
Default Value:85
SCellLoad BSC6900/BSC6 ADD WRFD-020 Inter System Meaning:1. Whether the RNC
BsdRedirS 910 UCELLRE 40003 Redirect considers the load in the source cell
witch DIRECTIO before initiating a service-based RRC
N redirection. When this switch is turned
on, the RNC redirects UEs to an
MOD inter-frequency neighboring cell for
UCELLRE load sharing when either of the
DIRECTIO following conditions is met:
N
2. The uplink load in the source cell is
greater than or equal to
"UlLdrTrigThd" in the "ADD
UCELLLDM" command multiplied by
"OffloadRelativeThd" in the "ADD
UCELLLDM" command.
3. The downlink load in the source
cell is greater than or equal to
"DlLdrTrigThd" in the "ADD
UCELLLDM" command multiplied by
"OffloadRelativeThd" in the "ADD
UlBeTraffIn BSC6900/BSC6 SET UFRC WRFD-021 Dynamic Meaning:UL initial access rate of PS
itBitrate 910 101 Channel background or interactive service.
Configuration When DCCC function is enabled, the
Control uplink initial access rate will be set to
(DCCC) this value if the uplink maximum rate
is higher than the initial access rate. A
higher value indicates that it takes
shorter time for BE services to reach
the maximum rate. Note that the rate
will be decreased through negotiation
when congestion occurs. A smaller
value indicates that BE services is
easier to be accessed. It is not
recommended to set a too small
value, because it will take longer time
for BE services to adjust to a higher
rate when needed.
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
UlDcccRat BSC6900/BSC6 SET WRFD-021 Dynamic Meaning:Uplink bit rate threshold for
eThd 910 UDCCC 101 Channel DCCC. When the maximum uplink bit
Configuration rate of a BE service is larger than this
Control parameter value, the traffic-based
(DCCC) uplink DCCC function can take effect
for the UE. Otherwise, the function
cannot take effect for the UE.
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
UlLdrRelT BSC6900/BSC6 ADD WRFD-020 Load Meaning:If the ratio of UL load of the
hd 910 UCELLLD 106 Reshuffling cell to the uplink capacity is lower
M than this threshold, the UL load
reshuffling function of the cell is
MOD stopped. After the basic congestion
UCELLLD state of the cell load is released, the
M system no longer implements the
LDR action. Because the load
fluctuates, the difference between the
LDR release threshold and trigger
threshold should be higher than 10%.
The ping-pong effect of the
preliminary congestion state will occur
UlLdrTrigT BSC6900/BSC6 ADD WRFD-020 Load Meaning:If the ratio of UL load of the
hd 910 UCELLLD 106 Reshuffling cell to the uplink capacity is not lower
M than this threshold, the UL load
reshuffling function of the cell is
MOD triggered. After the basic congestion
UCELLLD state of the cell load is released, the
M system no longer implements the
LDR action. Because the load
fluctuates, the difference between the
LDR release threshold and trigger
threshold should be higher than 10%.
The ping-pong effect of the
preliminary congestion state will occur
easily.
GUI Value Range:0~100
Actual Value Range:0~100
Unit:%
Default Value:55
UlLdTrnsH BSC6900/BSC6 ADD WRFD-020 Load Meaning:If the UL load state of the
ysTime 910 UCELLLD 102 Measurement cell is lasted longer than this
M threshold, the UL load state of the cell
transfers.
MOD
UCELLLD GUI Value Range:10~600000
M
Actual Value Range:10~600000
Unit:ms
Default Value:600
UlOlcRelT BSC6900/BSC6 ADD WRFD-020 Overload Meaning:If the ratio of UL load of the
hd 910 UCELLLD 107 Control cell to the uplink capacity is lower
M than this threshold, the UL overload
and congestion control function of the
MOD cell is stopped. The value of the OLC
UCELLLD release threshold should not be much
M lower than or close to the OLC trigger
threshold, or the system state will
have a ping-pong effect easily. The
recommended difference between the
OLC release threshold and the OLC
trigger threshold is higher than 10%.
It is desirable to set the two
UlOlcTrigT BSC6900/BSC6 ADD WRFD-020 Overload Meaning:If the ratio of UL load of the
hd 910 UCELLLD 107 Control cell to the uplink capacity is not lower
M than this threshold, the UL overload
and congestion control function of the
MOD cell is triggered. The value of the OLC
UCELLLD release threshold should not be much
M lower than or close to the OLC trigger
threshold, or the system state will
have a ping-pong effect easily. The
UmtsCellL BSC6900/BSC6 SET UCLB WRFD-140 Inter-Frequen Meaning:Period during which the
oadEstSlid 910 217 cy Load RNC records the number of failed
Window Balancing inter-RNC inter-frequency handovers.
Based on During this period, if the number of
Configurable failed inter-frequency handovers in a
Load cell exceeds the threshold specified
Threshold by "UmtsCellIFHOFailNum", the
target cell accommodating the UEs
handed over from the original cell is
punished. Therefore, the target cell is
no longer allowed to accommodate
such UEs for a period of time
specified by
"PenaltyTimeforHLoad3GCell".
GUI Value Range:0~7200
Actual Value Range:0~7200
Unit:s
Default Value:30
WeakCovR BSC6900/BSC6 SET UFRC WRFD-020 Inter System Meaning:The cell signal quality is
rcRedirEc 910 40003 Redirect indicated by the Ec/No reported by
NoThs UEs in the cell. If the value of Ec/No is
13 Counters
Table 13-1 Counter description
Counter ID Counter Name Counter Description NE Feature ID Feature Name
67196031 VS.RRC.Rej.Re Number of RRC Connection BSC6900 WRFD-0201 Service Steering and
dir.Service Rejects Due to 20 Load Sharing in RRC
Service-based RRC Connection Setup
Redirection for Cell WRFD-0105
10 3.4/6.8/13.6/27.2Kbp
s RRC Connection
and Radio Access
Bearer
Establishment and
Release
67196031 VS.RRC.Rej.Re Number of RRC Connection BSC6910 WRFD-0201 Service Steering and
dir.Service Rejects Due to 20 Load Sharing in RRC
Service-based RRC Connection Setup
Redirection for Cell WRFD-0105
10 3.4/6.8/13.6/27.2Kbp
s RRC Connection
and Radio Access
Bearer
Establishment and
67203416 VS.RAB.SFOcc Mean Number of SFs that BSC6910 WRFD-0201 Code Resource
upy Have Been Occupied (Let 08 Management
the SFs that Have Been
Occupied a Unitary SF of
256) for Cell
67203416 VS.RAB.SFOcc Mean Number of SFs that BSC6900 WRFD-0201 Code Resource
upy Have Been Occupied (Let 08 Management
the SFs that Have Been
Occupied a Unitary SF of
256) for Cell
67203991 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6910 WRFD-0201 Load Reshuffling
me.ULPower Due to UL Power 06
Congestion for Cell
67203991 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6900 WRFD-0201 Load Reshuffling
me.ULPower Due to UL Power 06
Congestion for Cell
67203992 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6900 WRFD-0201 Load Reshuffling
me.DLPower Due to DL Power 06
Congestion for Cell
67203992 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6910 WRFD-0201 Load Reshuffling
me.DLPower Due to DL Power 06
Congestion for Cell
67203993 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6910 WRFD-0201 Load Reshuffling
me.DLCode Due to DL Code Resource 06
Congestion for Cell
67203993 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6900 WRFD-0201 Load Reshuffling
me.DLCode Due to DL Code Resource 06
Congestion for Cell
67203994 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6910 WRFD-0201 Load Reshuffling
me.ULCE Due to UL CE Resource 06
Congestion
67203994 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6900 WRFD-0201 Load Reshuffling
Due to UL CE Resource
67203995 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6900 WRFD-0201 Load Reshuffling
me.DLCE Due to DL CE Resource 06
Congestion
67203995 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6910 WRFD-0201 Load Reshuffling
me.DLCE Due to DL CE Resource 06
Congestion
67203996 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6900 WRFD-0201 Load Reshuffling
me.ULIub Due to UL Iub Transmission 06
Resource Congestion for
Cell
67203996 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6910 WRFD-0201 Load Reshuffling
me.ULIub Due to UL Iub Transmission 06
Resource Congestion for
Cell
67203997 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6910 WRFD-0201 Load Reshuffling
me.DLIub Due to DL Iub Transmission 06
Resource Congestion for
Cell
67203997 VS.LCC.LDR.Ti Duration of Cell in LDR State BSC6900 WRFD-0201 Load Reshuffling
me.DLIub Due to DL Iub Transmission 06
Resource Congestion for
Cell
73424787 VS.MaxULActua Max Uplink Actual Cell Load BSC6900 WRFD-0201 Load Measurement
lPowerLoad 02
73424787 VS.MaxULActua Max Uplink Actual Cell Load BSC6910 WRFD-0201 Load Measurement
lPowerLoad 02
73424788 VS.MinULActual Min Uplink Actual Cell Load BSC6900 WRFD-0201 Load Measurement
PowerLoad 02
73424788 VS.MinULActual Min Uplink Actual Cell Load BSC6910 WRFD-0201 Load Measurement
PowerLoad 02
73441144 VS.HSDPA.Mea Average Power Required for BSC6910 WRFD-0201 Load Measurement
nRequiredPwr.F Free HSDPA Users for Cell 02
ree
73441144 VS.HSDPA.Mea Average Power Required for BSC6900 WRFD-0201 Load Measurement
nRequiredPwr.F Free HSDPA Users for Cell 02
ree
73441505 VS.MeanULAct Mean Uplink Actual Cell BSC6910 WRFD-0201 Load Measurement
ualPowerLoad Load 02
73441505 VS.MeanULAct Mean Uplink Actual Cell BSC6900 WRFD-0201 Load Measurement
ualPowerLoad Load 02
14 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
15 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] DCCC Feature Parameter Description
[7] AMR Feature Parameter Description
[8] MBMS Feature Parameter Description
[9] HSDPA Feature Parameter Description
[10] HSUPA Feature Parameter Description
[11] Transmission Resource Management Feature Parameter Description
[12] Handover Feature Parameter Description