Escolar Documentos
Profissional Documentos
Cultura Documentos
RAN14.0
Feature Parameter Description
Issue 05
Date 2013-06-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
WCDMA RAN
Load Control Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
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-13
8.3.3 QoS Renegotiation for Uncontrollable Real-Time Services ............................................... 8-13
8.3.4 Inter-RAT Handover in the CS Domain .............................................................................. 8-14
8.3.5 Inter-RAT Handover in the PS Domain............................................................................... 8-14
8.3.6 AMR Rate Reduction .......................................................................................................... 8-15
8.3.7 Code Reshuffling ................................................................................................................ 8-15
8.3.8 MBMS Power Reduction .................................................................................................... 8-16
8.3.9 UL and DL LDR Action Combination of a UE ..................................................................... 8-17
11 Engineering Guidelines.......................................................................................................11-1
11.1 WRFD-021104 Emergency Call ................................................................................................ 11-1
11.1.1 Feature Deployment ......................................................................................................... 11-1
11.2 WRFD-010506 RAB Quality of Service Renegotiation over Iu Interface .................................. 11-1
11.2.1 Feature Deployment ......................................................................................................... 11-1
11.3 WRFD-020102 Load Measurement .......................................................................................... 11-3
11.3.1 Feature Deployment ......................................................................................................... 11-3
11.4 WRFD-020106 Load Reshuffling .............................................................................................. 11-5
11.4.1 Feature Deployment ......................................................................................................... 11-5
11.5 WRFD-020107 Overload Control .............................................................................................. 11-8
11.5.1 Feature Deployment ......................................................................................................... 11-8
11.6 WRFD-020108 Code Resource Management ........................................................................ 11-10
11.6.1 Feature Deployment ....................................................................................................... 11-10
11.7 WRFD-020105 Potential User Control ..................................................................................... 11-11
11.7.1 Feature Deployment ........................................................................................................ 11-11
11.8 WRFD-020103 Inter-Frequency Load Balancing .................................................................... 11-13
11.8.1 When to Use ................................................................................................................... 11-13
11.8.2 Required Information ...................................................................................................... 11-13
11.8.3 Planning .......................................................................................................................... 11-13
11.8.4 Feature Deployment ....................................................................................................... 11-13
11.8.5 Performance Monitoring ................................................................................................. 11-19
11.8.6 Parameter Optimization .................................................................................................. 11-19
11.8.7 Troubleshooting .............................................................................................................. 11-19
11.9 WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load Threshold .... 11-20
11.9.1 When to Use Inter-Frequency Load Balancing Based on Configurable Load Threshold11-20
11.9.2 Required Information ...................................................................................................... 11-20
11.9.3 Feature Deployment ....................................................................................................... 11-21
11.9.4 Performance Optimization .............................................................................................. 11-26
11.9.5 Parameter Optimization .................................................................................................. 11-29
11.9.6 Troubleshooting .............................................................................................................. 11-29
11.10 WRFD-020401 Inter-Frequency Redirection Based on Distance ......................................... 11-29
11.10.1 When to Use Inter-Frequency Redirection Based on Distance .................................... 11-29
12 Parameters .............................................................................................................................12-1
13 Counters..................................................................................................................................13-1
14 Glossary ..................................................................................................................................14-1
15 Reference Documents .........................................................................................................15-1
1 Introduction
1.1 Scope
This document describes the features related to the load control. It also describes the related
parameters.
Document Issues
The document issue is as follows:
05 (2013-06-20)
04 (2013-05-10)
03 (2012-11-30)
02 (2012-07-20)
01 (2012-04-30)
Draft A (2012-02-15)
05 (2013-06-20)
This is the fifth commercial release.
Compared with 04 (2013-05-10), issue 05 (2013-06-20) of RAN14.0 incorporates the changes described
in the following table.
04 (2013-05-10)
This is the fourth commercial release.
Compared with 03 (2012-11-30), issue 04 (2013-05-10) of RAN14.0 incorporates the changes described
in the following table.
03 (2012-11-30)
This is the third commercial release.
Compared with (2012-07-20) of RAN14.0, issue 02 (2012-11-30) of RAN14.0 incorporates the changes
described in the following table.
RESERVED_SWITCH_0_BIT28
Editorial Modified descriptions about LDR None
change actions intended for different
resources. For details, see chapter 8.2
02 (2012-07-20)
This is the second commercial release.
Compared with 01 (2012-04-30) of RAN14.0, issue 02 (2012-07-20) of RAN14.0 incorporates the
changes described in the following table.
01(2012-04-30)
This is the first commercial release.
Compared with draft A (2012-02-15) of RAN14.0, issue 01 (2012-04-30) of RAN14.0 incorporates the
changes described in the following table.
Added the description of inter-frequency RRC The following parameters have been added:
redirection based on distance. For details, see InterFreqRedirSwitch
"Inter-Frequency RRC Redirection Based on InterFreqRedirDelayThd
Distance" in section 5.2.3 "RRC Redirection
based on Distance".
InterFreqRedirFactorOfLDR
Draft A (2012-02-15)
This is the draft of the document for RAN14.0.
Compared with issue 02 (2011-04-30) of RAN13.0, this issue incorporates the changes described in the
following table.
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 will provide detailed information about the load control functions performed in the
different UE access phases.
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 the HSDPA Feature Parameter Description and the HSUPA
Feature Parameter Description.
Provided Bit Rate (PBR) on HS-DSCH. For details about PBR, see the 3GPP 25.321.
Power Requirement for GBR (GBP) on HS-DSCH: minimum power required to ensure the GBR on
HS-DSCH
PBR on E-DCH
Received Scheduled E-DCH Power Share (RSEPS): power of the E-DCH scheduling service in the
serving cell
Uplink total load: sum of R99 service load, HSUPA service load, and control channel load. Measuring
the uplink total load depends on the NodeB hardware. For details on the dependency, see 11.3
WRFD-020102 Load Measurement.
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. For details on the dependency, see 1.3 WRFD-020102 Load Measurement.
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.
The measurement procedure is shown in Figure 3-1.
Figure 3-1 LDM procedure
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.
D is the reported measurement value.
Layer 1 filtering is not standardized by protocols and it depends on vendor equipment. Layer 3 filtering is
standardized. The filtering effect is controlled by a higher layer. The alpha filtering that applies to layer 3
filtering is calculated according to the following formula:
Fn=(1-a)Fn-1+aMn
Here:
Fn is the new post-filtering measurement value.
Fn-1 is the last post-filtering measurement value.
Mn is the new measurement value from the physical layer.
a = (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.
If the temperature in the equipment room varies with the ambient temperature, the background noise
changes greatly. In this case, the background noise requires auto-adaptive upgrade.
The following figure shows the flow chart of auto-adaptive background noise update, which is enabled by
the BGNSwitch parameter.
The Alpha filter formula is: Fn = (1 - ) x Fn-1 + x Mn (n1). 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 "3.1 " 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. (a).The RNC determines whether the current Equivalent Number of Users (ENU) in the cell is
greater than the value of BGNEqUserNumThd:
If
the 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.
If
the 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:
Ifthe 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 F n 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.
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 Figure 4-2.
Figure 4-2 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-2.
Table 4-2 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-3.
Table 4-3 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 the 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 the 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." If the queuing is
successful, UE access is granted. If the queuing fails or is not supported, the RNC performs the next
step.
10. 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.
11. 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
HSUP - -
A
HSDP - - - -
A
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 the PERFENH_RRC_WEAK_REDIR_SWITCH check
box under the PerfEnhanceSwitch parameter is selected. If the 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 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 five algorithms:
Inter-RAT RRC Redirection Based on Distance
Inter-Frequency RRC Redirection Based on Distance
RRC Redirection for Service Steering
RRC DRD
RRC Redirection After DRD Failure
Before enabling the five algorithms, turn on the DrSwitch: DR_RRC_DRD_SWITCH.
If the current cell does not have any neighboring GSM cell or the IE "RACH Measurement Report" does not contain the
Ec/No value, inter-RAT RRC redirection based on weak coverage is not performed.
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.
If the RedirBandInd parameter is set to DependOnNCell, only intra-band inter-frequency neighboring cell can be
selected as target frequency.
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 sends an RRC Connection Reject
message to the UE. The message carries the information about inter-RAT neighboring cells.
Identified Reference IE
Service
Type Establishment cause Domain Call type UE capability Access stratum
indicator indication release indicator
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.
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" in
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.
If
the DRA_HSUPA_DCCC_SWITCH sub-parameter of the DraSwitch parameter is set to 1, the
initial access rate is the initial rate of the HSUPA BE service (HsupaInitialRate).
If
the DRA_HSUPA_DCCC_SWITCH sub-parameter of the DraSwitch parameter is set to 0, the
initial access rate is the MBR for there will not be any rate upsizing reconfiguration when the
DRA_HSUPA_DCCC_SWITCH sub-parameter of the DraSwitch parameter is set to 0.
For the HSDPA service, the initial admission rate and the initial access are both GBR.
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 RsvU8Para0 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 RsvU8Para0 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 RsvU8Para0 Initial Uplink and Downlink Rates for the PS BE Service
DCH 0k DCH 0 kbit/s
DCH 8k DCH 8 kbit/s
DCH 8k/HSDPA DCH 8 kbit/s; HSDPA
If
ReservedSwitch0: RESERVED_SWITCH_0_BIT11 is turned on and RsvU8Para0 is not set to
OFF, the initial uplink rates for the PS BE service in CS+PS combined services are as listed in Table
5-5.
Table 5-5 Initial uplink rates for the PS BE service in CS+PS combined services
Setting of ReservedSwitch0: Value of Initial Uplink Rate for the PS BE
RESERVED_SWITCH_0_BIT11 RsvU8Para0 Service
Turned on DCH 0k DCH 0 kbit/s
Turned on DCH 8k DCH 8 kbit/s
Turned on DCH 8k/HSDPA DCH 8 kbit/s
If
ReservedSwitch0: RESERVED_SWITCH_0_BIT15 is turned on and RsvU8Para0 is not set to
OFF, the initial downlink rates for the PS BE service in CS+PS combined services are as listed in
Table 5-6.
Table 5-6 Initial downlink rates for the PS BE service in CS+PS combined services
Setting of ReservedSwitch0: Value of RsvU8Para0 Initial Downlink Rate for the PS
RESERVED_SWITCH_0_BIT15 BE Service
Turned on DCH 0k DCH 0 kbit/s
Turned on DCH 8k DCH 8 kbit/s
Turned on DCH 8k/HSDPA 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 RsvU8Para0 Initial Uplink and Downlink
RESERVED_SWITCH_0_BIT14 Rates for the PS BE Service
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 RsvU8Para0 Initial Uplink and Downlink Rates for the PS BE Service
DCH 0k DCH 0 kbit/s
DCH 8k DCH 8 kbit/s
DCH 8k/HSDPA DCH 8 kbit/s
Value of RsvU8Para0 Initial Uplink and Downlink Rates for the PS BE Service
DCH 8k DCH 8 kbit/s
DCH 8k/HSDPA DCH 8 kbit/s
Inscenario 1, RsvU8Para0 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 RsvU8Para0 for the PS BE Service
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
5.6 Preemption
Common Preemption
This section describes the pre-emption algorithm in the WRFD-010505 Queuing and Pre-Emption
feature.
By forcibly releasing the resources of lower-priority users, the preemption (pre-emption) function
increases the access success rate of higher-priority users.
After cell/cell group resource-based admission fails, the RNC performs preemption if the following
conditions are met:
The RNC receives 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. 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 procedure for preemption is as follows:
1. The RNC selects the target cell for preemption.
For DC-HSDPA/DC-HSUPA services, the RNC selects the primary cell in the DC-HSDPA/DC-HSUPA
cell group as the target cell.
Fornon-DC-HSDPA/non-DC-HSUPA services, the RNC selects a suitable cell with higher service
priority or lower load.
2. The preemption algorithm determines the radio link sets to be preempted.
a. Selects SRNC users first. If no user under the SRNC is available, the algorithm selects users under
the DRNC.
b. Sorts the preemptable users by integrated user priority, or sorts the preemptable RABs by
integrated RAB priority.
c. Determines candidate users 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.
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.
IfPsBERrcPreemptVulnerable 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 can not 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 the 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.
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 services can
be preempted.
The forced preemption function is controlled by PreemptAlgoSwitch and RsvdPara1 together. The
RsvdPara1 parameter consists of two sub-parameters: RSVDBIT4 and RSVDBIT5. RSVDBIT4
indicates whether CS services can preempt the resources for PS services during a CS RRC connection
setup. RSVDBIT5 indicates whether CS services can preempt the resources for PS BE services during a
CS RAB-related phase.
The following table describes how these two sub-parameters determine preemption.
Table 5-11 How these two sub-parameters determine preemption
RsvdPara1: RsvdPara1: RRC Connection RAB-Related Phases
RSVDBIT5 RSVDBIT4 Setup Phase
On Off CS conversational If RAB admission for CS
services cannot conversational services fails, PS BE
preempt PS BE services can be preempted
services. unconditionally.
On On If RRC admission for If RAB admission for CS
CS conversational conversational services fails, PS BE
services fails, PS BE services can be preempted
services can be unconditionally.
preempted
unconditionally.
Off On If RRC admission for Common preemption is performed.
CS conversational That is, service priorities and the
services fails, PS BE Pre-emption Capability and
services whose Pre-emption Vulnerability IEs
Pre-emption determine whether to perform
Vulnerability IE is set to preemption.
"pre-emptable" can be
preempted.
Off Off CS conversational Common preemption is performed.
services cannot That is, service priorities and the
preempt PS BE Pre-emption Capability and
services. 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."
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.
The UE requesting DC-HSDPA/DC-HSUPA services will be queued in the selected primary cell.
Full Checks whether the integrated priority of any existing request is lower than that of
the new request
If yes, then the queuing algorithm:
- Checks the queuing time of each request. The algorithm removes the request
with the longest queuing time from the queue
- Stamps the new request with the request time (T_request) and then puts it into
the queue
- Starts the heartbeat timer if it is not started
If no, then the queuing algorithm rejects the new request directly
After the heartbeat timer expires, the queuing algorithm performs resource-based admission attempts as
follows:
Rejects the request if the queuing time of the request (Telapsed) is longer than the maximum queuing
time (MaxQueueTimeLen). Here, Telapsed is equal to the current time minus the request time
(T_request).
Selects the request with the highest integrated priority for a resource-based admission attempt.
If more than one service has the highest integrated priority, the RNC selects the request with the
longest queuing time.
If the attempt is successful, the heartbeat timer is restarted for the next processing.
If the attempt fails, the queuing algorithm proceeds as follows:
Putsthe service request back into the queue with the request time (T_request) unchanged for the next
attempt.
Selectsthe request with the longest queuing time from the rest and makes another attempt until a
request is accepted or all requests are rejected.
After an appropriate access action is determined, the service attempts to access the network.
If the action of access from the DCH at 0 kbit/s is determined, the service attempts to access the
network at 0 kbit/s for traffic and at the normal rate for signaling. For details about the methods of
resource-based admission decision, see the Call Admission Control Feature Parameter Description.
If the action of access from the FACH/E-FACH is determined, the service attempts to access the
network from the FACH/E-FACH.
If the attempt fails, this service is rejected.
For the service that accesses the network at 0 kbit/s, the ZeroRateUpFailToRelTimerLen timer is
started after the service rate fails to increase for the first time. If the rate fails to increase even 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 the State Transition Feature Parameter Description.
The RNC does not perform RRC redirection for service steering.
In the case of power-based admission, the emergency call is admitted regardless of whether the CAC
function is enabled or not.
In the case of hard resource-based admission, the emergency call is admitted if the current remaining
resources are sufficient for RRC connection setup. If the admission fails, preemption is performed
regardless of whether the preemption is enabled or not. The emergency call that triggers preemption has
the highest priority. The range of users who can be preempted is specified by the
EmcPreeRefVulnSwitch parameter.
If EmcPreeRefVulnSwitch is set to ON, all non-emergency users who have accessed the network
can be preempted, regardless of the preemption-prohibited attribute of the users.
If EmcPreeRefVulnSwitch is set to OFF, only the non-emergency users with preemption-allowed
attribute can be preempted.
The principles for selection of specific users to be preempted are the same as those for common
services. For details, see section 5.6 "Preemption."
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."
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 CLB 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 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 the
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 are not allowed to be handed over to a micro cell. For details on how to identify high-speed
users, see the 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.
As shown in Figure 7-2, 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.
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 of the cell, respectively. For details about the load of
a cell calculated based on power resource and based on ENU, see the 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 the 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
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.
Cell-level
parameters take effect when power resources, code resources, or cell credit resources are
in basic congestion state.
When HO_INTER_FREQ_HARD_HO_SWITCH under the HoSwitch parameter is set to ON, the RNC
is allowed to initiate inter-frequency measure control or the load-based inter-frequency hard handover
upon the handover decision on inter-frequency load.
The CodeCongSelInterFreqHoInd parameter can be set so that the inter-frequency handover can
relieve the basic congestion caused by code resource.
User Selection
The RNC selects the UEs that meet the following requirements. Then, RNC sorts the UEs by integrated
user priority and selects the UE of the lowest integrated user priority to perform the next step. If there are
no candidate users, the action fails.
The service types of UEs are not restricted for LDR handover by parameter
InterFreqLdHoForbidenTC.
The user rate of UEs is smaller than the handover bandwidth threshold. The handover bandwidth
thresholds of uplink and downlink are respectively specified by the UlInterFreqHoBWThd and
DlInterFreqHoBWThd parameters.
If the basic congestion is caused by the credit resource, only UEs processing PS services are selected
as candidate UEs.
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.
If the UE is in the soft handover state, load-based inter-frequency handover can be performed only
when HO_ALGO_LDR_ALLOW_SHO_SWITCH under the HoSwitch parameter is set to 1 and the
cell that triggers LDR is the best cell of the UE
Blind Handover
If the InterFreqLDHOMethodSelection parameter is set to BLINDHO, the load-based inter-frequency
handover based on blind handover performs the following steps:
1. The select the target UEs. For details, see 3.2 User Selection.
2. The RNC selects the candidate cells that meet the following requirements:
The cell supports blind handover. Whether the neighboring cells support blind handover is specified by
the parameter BlindHoFlag.
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.
The algorithm selects the candidate cells to be handed over according to the setting of
NbmLdcUeSelSwitch:
If
NbmLdcUeSelSwitch is set to NBM_LDC_MATCH_UE_ONLY, the algorithm only selects the
candidate cells from the cells supporting the UE service.
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.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:
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.
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.
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.
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.
3. The RNC starts intra-frequency measurement
The inter-frequency cells with the same coverage area have the same CPICH RSCP values. By
measuring the CPICH RSCP of the cell, the quality of the cells with the same coverage area can be
determined, which increases the probability of successful blind handover.
The RNC initializes the timer of intra-frequency measurement for blind handover. The timer is
specified by internal algorithm and does not need to be configured.
The RNC initiates a periodical intra-frequency measurement.
The reporting period is BlindHOIntrafreqMRInterval.
The number of measurement reports is BlindHOIntrafreqMRAmount.
The intra-frequency handover measurement quantity is CPICH RSCP.
The list of measured cells contains only the cells that trigger LDR.
After receiving from the UE the intra-frequency measurement reports for conditional blind handover,
the RNC checks whether the following condition is met: CPICH RSCP of the cell in the measurement
report BlindHOQualityCondition
If
the condition is met, the RNC increments the counter of the number of intra-frequency
measurement reports for blind handover by 1.
If
the condition is not met, the RNC does not perform a blind handover to the cell that triggers LDR
and stops intra-frequency measurement for blind handover.
When the counter reaches the value of BlindHOIntrafreqMRAmount, the RNC initiates a blind
handover to the target cell. If the counter does not reach this value, the RNC waits for the next
intra-frequency measurement report from the UE.
If the timer of intra-frequency measurement for blind handover expires, the RNC does not perform a
blind handover to the target cell and stops intra-frequency handover measurement for blind handover.
If the inter-frequency handover based on coverage or QoS is triggered, the RNC stops the
intra-frequency measurement for conditional blind handover.
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.
If
there 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.
Measured Handover
The load-based inter-frequency handover based on measurement can be performed if the basic
congestion is caused by power or credit resource.
Load-based inter-frequency handovers triggered by code resource congestion support blind handovers
but do not support measurement-based handovers.
If the InterFreqLDHOMethodSelection parameter is set to MEASUREHO, the load-based
inter-frequency handover is performed based on measurement. The LDR algorithm is implemented by
performing the following steps:
1. The RNC selects the UE whose service types are not restricted for LDR handover by parameter
InterFreqLdHoForbidenTC, and then sorts the selected UEs according to their integrated priority
and performs load-based inter-frequency handover based on measurement on the UE with the
lowest integrated priority.
If the basic congestion is caused by the credit resource, only UEs processing PS services are selected
as candidate UEs. This is the same as in cases of blind handovers.
If the UE is in the soft handover state, load-based inter-frequency handover can be performed only
when HO_ALGO_LDR_ALLOW_SHO_SWITCH under the HoSwitch parameter is set to 1 and the
cell that triggers LDR is the best cell of the UE.
2. The RNC selects the candidate cells that meet the following conditions:
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.
The algorithm selects the candidate cells to be handed over according to the setting of
NbmLdcUeSelSwitch:If NbmLdcUeSelSwitch is set to NBM_LDC_MATCH_UE_ONLY, the
algorithm only selects the candidate cells from the cells supporting the UE service.
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.
If NbmLdcUeSelSwitch is set to NBM_LDC_ALL_UE, the condition is invalid for the algorithm.
The 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
target cell is higher than UlInterFreqHoCellLoadSpaceThd / DlInterFreqHoCellLoadSpaceThd
and whether the load of the target cell is normal.
If the cell supports DC-HSDPA, the cell and its corresponding cell group must have sufficient load
margin. 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.
b. 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.
And the load state of target cell is normal.
The DrdOrLdrFlag parameter of the cell is set to True, indicating that the cell can be measured.
If
the NbmLdcUeSelSwitch parameter is set to NBM_LDC_MATCH_UE_ONLY, the cell must
support the service requested by the UE.
If
the UESpdOptSwitch parameter is set to ON, the RNC identifies high-speed users. To high-speed
users, the value of HCSPrio for candidate cells must be higher than that for the serving cell. For
details on how to identify high-speed users, see Handover Feature Parameter Description.
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.
3. The RNC issues a measurement control message to the UE, requesting the UE to measure the
signal quality of all candidate cells.
4. 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.
5. 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.
6. 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, it is not recommended that the BE Rate Reduction be
configured as an LDR action in order to avoid ping-pong effect.
BE rate reduction can only be performed when the DRA_DCCC_SWITCH 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 the DCCC Feature Parameter Description.
5. The reconfiguration is complete as indicated by the RADIO BEARER RECONFIGURATION
message on the Uu interface and through the synchronized radio link reconfiguration procedure on
the Iub interface.
3. The algorithm performs QoS renegotiation for the selected services. The GBR during the service
setup is the minimum rate of the service after the QoS renegotiation.
4. The RNC initiates the RAB MODIFY REQUEST message to the CN for the QoS renegotiation. Upon
reception of the RAB MODIFY REQUEST message, the CN sends the RAB ASSIGNMENT
REQUEST message to the RNC for RAB parameter reconfiguration.
HSPA services can be selected only when HsdpaCMPermissionInd is set to TRUE and HsupaCMPermissionInd is not
set to Limited.
For details about the two parameters, see the Handover Feature Parameter Description.
The reconfiguration procedure on the Iub interface is implemented through the COMMON
TRANSPORT CHANNEL RECONFIGURATION REQUEST message.
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 the 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 parameter NBMUlCacAlgoSelSwitch is set to ALGORITHM_Second, the uplink OLC algorithm
is disabled because EN does not cause overload congestion.
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 sub-parameter of 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.
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.
CLB is used in other scenarios the similar way the WRFD-020103 Inter-Frequency Load Balance feature
is used. The difference is that CLB can implement load balancing before a cell enters the basic
congestion state so that the traffic load can evenly be distributed among cells. CLB helps prevent a cell
from being heavily loaded or having deteriorated KPIs.
Negative impact
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.
11 Engineering Guidelines
11.1 WRFD-021104 Emergency Call
11.1.1 Feature Deployment
Requirements
Dependencies on Hardware
This feature does not have any special requirements for hardware.
Dependencies on Other Features
This feature does not depend on other features.
License
This feature is not under license control.
Data Preparation
None
Feature Activation
This feature need not be activated.
Activation Check
Use a UE to initiate an emergency call.. The emergency call is successfully established.
Feature Deactivation
This feature need not be deactivated.
Data Preparation
None
Feature Activation
1. Run the BSC6900 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 BSC6900 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 BSC6900 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 BSC6900 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 BSC6900 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 BSC6900 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 BSC6900 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 Check
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.
Feature Deactivation
1. Run the BSC6900 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, deselect 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 BSC6900 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, deselect 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.
Example
/*Activating RAB Quality of Service Renegotiation over Iu Interface*/
//Enabling the cell-level LDR algorithm
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=
UL_UU_LDR-1&DL_UU_LDR-1&CELL_CREDIT_LDR-1;
//Enabling the NodeB-level LDR algorithm
MOD UNODEBALGOPARA: NodeBName="NODEB1",
NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1;
//Enable QoS renegotiation on real-time services
MOD UCELLLDR: CellId=111, DlLdrFirstAction=QoSRenego;
/*Deactivating RAB Quality of Service Renegotiation over Iu Interface*/
//Disabling the cell-level LDR algorithm
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=
UL_UU_LDR-0&DL_UU_LDR-0&CELL_CREDIT_LDR-0;
//Disabling the NodeB-level LDR algorithm
MOD UNODEBALGOPARA: NodeBName="NODEB1",
NodeBLdcAlgoSwitch=IUB_LDR-0&NODEB_CREDIT_LDR-0&LCG_CREDIT_LDR-0;
Data Preparation
None
Feature 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 BSC6900 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 BSC6900 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 BSC6900 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 Check
1. On the BSC6900 LMT, open the Monitor 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.
Feature Deactivation
1. The measurement on RTWP, TCP, and non-HSPA power has been activated and cannot be
deactivated.
2. Run the BSC6900 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, deselect
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.
Example
//Activating load measurement
MOD UCELLALGOSWITCH: CellId=100,
NBMCacAlgoSwitch=HSDPA_PBR_MEAS-1&HSUPA_PBR_MEAS-1;
Data Preparation
None
Feature 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 BSC6900 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:
b. Run the BSC6900 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:
Activation Check
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 BSC6900 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.
Feature Deactivation
1. Run the BSC6900 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, deselect 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 BSC6900 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,
deselect 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
Example
//Activating Load Reshuffling
//Enabling load reshuffling algorithms
MOD UCELLALGOSWITCH: CellId=100,
NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR-1;
MOD UNODEBALGOPARA: NodeBName="nodeb1",
NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1;
//Setting load reshuffling thresholds
MOD UCELLLDM: CellId=100, UlLdrTrigThd=55, UlLdrRelThd=45, DlLdrTrigThd=70, DlLdrRelThd=60,
UlOlcTrigThd=95, UlOlcRelThd=85, DlOlcTrigThd=95, DlOlcRelThd=85, DlLdTrnsHysTime=1000;
//Setting code reshuffling thresholds
MOD UCELLLDR: CellId=100, DlLdrFirstAction=CodeAdj, DlLdrSecondAction=InterFreqLDHO,
CellLdrSfResThd=SF8;
//Setting NodeB-level credit reshuffling thresholds
Data Preparation
None
Feature Activation
1. Run the BSC6900 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 the UL_UU_OLC(Uplink UU OLC Algorithm) and DL_UU_OLC(Downlink UU
OLC Algorithm) check boxes under the parameter Switch for Cell Load Control.
2. Run the BSC6900 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 the IUB_OLC(IUB OLC Algorithm) check box under the parameter NodeB LDC
algorithm.
3. Run the BSC6900 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 BSC6900 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 BSC6900 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 Check
1. Run the following BSC6900 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.
Feature Deactivation
1. Run the BSC6900 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 dienable the air interface OLC
algorithm. Clear the UL_UU_OLC(Uplink UU OLC Algorithm) and DL_UU_OLC(Downlink UU
OLC Algorithm) check boxes under the parameter Switch for Cell Load Control.
2. Run the BSC6900 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 disenable the
OLC algorithm, Clear the IUB_OLC(IUB OLC Algorithm) check box under the parameter NodeB
LDC algorithm.
Example
//Activating Overload Control
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=UL_UU_OLC-1&DL_UU_OLC-1;
MOD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_OLC-1;
SET ULDCPERIOD: OlcPeriodTimerLen=3000;
ADD UCELLOLC: CellId=111;
//Deactivating Overload Control
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=UL_UU_OLC-0&DL_UU_OLC-0;
MOD UNODEBALGOPARA: NodeBName="NodeB1", NodeBLdcAlgoSwitch=IUB_OLC-0;
Data Preparation
None
Feature Activation
The code allocation function is always activated. The activation procedure applies to only the code reshuffling function.
1. Run the BSC6900 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 BSC6900 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 BSC6900 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 length of LDR period (LDR period timer length).
Activation Check
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 BSC6900 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 BSC6900 MML command DSP UCELLCHK to check the cell health status. The status of cell
code congestion is displayed as basic congestion.
7. Run the BSC6900 MML command RMV URESERVEOVSF to release the service that occupies code
SF32(1).
8. Run the BSC6900 MML command DSP UCELLCHK to check the cell health status. The status of cell
code congestion is displayed as not congested.
Feature Deactivation
1. Run the BSC6900 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.
Example
//Activating Code Resource Management
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=CELL_CODE_LDR-1;
MOD UCELLLDR: CellId=111, DlLdrFirstAction=CodeAdj, CellLdrSfResThd=SF8;
SET ULDCPERIOD: LdrPeriodTimerLen=10;
//Verifying Code Resource Management
MOD UCELLLDR: CellId=111, CellLdrSfResThd=SF8, MaxUserNumCodeAdj=1;
DSP UCELLCHK: CHECKSCOPE=CELLID, CELLID=111;
RMV URESERVEOVSF: CellId=111, DLOVSFSF=SF32, DLCODENO=1;
//Deactivating Code Resource Management
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=CELL_CODE_LDR-0;
Data Preparation
None
Feature Activation
1. Run the BSC6900 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 BSC6900 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 BSC6900 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 Check
1. Configure two cells CELL_A11 and CELL_A12 as inter-frequency neighboring cells on the NodeB.
2. Run the BSC6900 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 BSC6900 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.
Feature Deactivation
1. Run the BSC6900 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, deselect the
PUC(Potential User Control Algorithm) check box under the parameter Cell LDC algorithm
switch.
Example
//Activating Potential User Control
MOD UCELLALGOSWITCH: CellId=111, NBMLdcAlgoSwitch=PUC-1;
SET ULDCPERIOD: PucPeriodTimerLen=1800;
ADD UCELLPUC: CELLID=1, SPUCLIGHT=45, SPUCHEAVY=70, SPUCHYST=5,
OFFSINTERLIGHT=-2, OFFSINTERHEAVY=2, OFFQOFFSET1LIGHT=-4, OFFQOFFSET2LIGHT=-4,
OFFQOFFSET1HEAVY=4, OFFQOFFSET2HEAVY=4;
VS.LCC.LDR.Num.ULCE
VS.RAC.NewCallReq.Fail.ULCE.Cong
VS.RAB.FailEstabPS.ULCE.Cong
VS.RAB.FailEstabCS.ULCE.Cong
VS.HSUPAPSLoad.ULThruput.RNC
KPI
RRC setup success ratio
CS RAB setup success ratio
PS RAB setup success ratio
PS call drop ratio
11.8.3 Planning
None
License
The licenses "Inter frequency load handover" 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.
Feature ID Feature Name License Description NE Sales Unit
WRFD-02010 Inter Frequency Inter frequency load RN Erl+Mbps
3 Load Balance handover C
Data Preparation
None
Feature Activation
1. Enable load reshuffling (LDR) algorithms.
Enabling uplink load reshuffling on the Uu interface
a. Run the Run the BSC6900 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 the UL_UU_LDR(Uplink UU LDR Algorithm) check box under the
parameter Switch for Cell Load Control.
a. Run the Run the BSC6900 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 the DL_UU_LDR(Downlink UU LDR Algorithm) check box under the
parameter Switch for Cell Load Control.
a. Run the Run the BSC6900 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 the CELL_CODE_LDR(Code LDR Algorithm) check box under the
parameter Switch for Cell Load Control.
b. Run the 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
CELL_CREDIT_LDR (cell credit reshuffling algorithm) under the Switch for Cell Load
Control parameter.
a. Run the Run the BSC6900 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, select the NodeB-level
NODEB_CREDIT_LDR_SWITCH(NodeB Credit LDR Switch) or cell group-level
LCG_CREDIT_LDR_SWITCH(Local Cell Group Credit LDR Switch) check box under
the parameter load control algorithm switch.
b. Run the Run the BSC6900 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). In this step, select the NodeB-level
NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm) or cell group-level
LCG_CREDIT_LDR(LCG Credit LDR Algorithm) check box under the parameter NodeB
LDC algorithm switch.
2. Run the Run the BSC6900 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 inter-frequency handover. In this command, select
the HO_ALGO_LDR_ALLOW_SHO_SWITCH and HO_INTER_FREQ_HARD_HO_SWITCH check
boxes under the parameter HandOver Switch.
3. Run the Run the BSC6900 MML command ADD UINTERFREQNCELL (CME single configuration:
UMTS Cell Configuration Express > Neighboring Cell > Inter-frequency Neighboring Cell; CME
batch modification center: not supported) to add an inter-frequency neighboring cell supporting blind
handover, or to add an inter-frequency neighboring cell supporting measurement by setting the
parameter DrdOrLdrFlag to an appropriate value.
4. Run the Run the BSC6900 MML command ADD UCELLINTERFREQHONCOV (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Oriented
None-Coverage Based Inter-frequency Handover Measurement Algorithm Parameters; CME
batch modification center: Modifying UMTS Cell Parameters in Batches) (cell level) or SET
UINTERFREQHONCOV (CME single configuration: UMTS Radio Global Configuration Express >
HandOver Parameter Configuration > RNC Oriented None-Coverage Based Inter-frequency
Handover Measurement Algorithm Parameters; CME batch modification center: Modifying RNC
Parameters in Batches) (RNC level) to set parameters related to load-based inter-RAT hard
handovers to appropriate values based on the network plan.
5. For a load-based inter-frequency handover that is based on measurement, run the Run the BSC6900
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 InterFreq Load Handover Method Selection to
MEASUREHO(MEASUREHO).
6. Set LDR-related thresholds based on the network plan.
Foruplink and downlink load reshuffling on the Uu interface, run the Run the BSC6900 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 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 BSC6900 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
BSC6900 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 BSC6900 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 Run the BSC6900 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 BSC6900 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 the
InterFreqLDHO(inter-freq load handover) check box under the parameter DL LDR first action 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
BSC6900 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 the
InterFreqLDHO(inter-freq load handover) check box under the parameter UL LDR first action and
set other parameters related to the LDR action based on the network plan.
11. Run the 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 set the policy for selecting users to be
handed over. In this step, set Inter-freq NbmLdcUeSelSwitch (Handover Select User algorithm
switch).
Activation Check
Check the value of the following counters. If the value is not 0, this feature has been activated
VS.LCC.LDR.InterFreq: Number of UEs Performing Inter-Frequency Load Handovers in Basic
Congestion for Cell
VS.HHO.AttInterFreqOut.PS.UlCE: Number of PS Inter-Frequency Hard Handover Attempts Based on
UL CE for Cell
VS.HHO.SuccInterFreqOut.PS.UlCE: number of Successful PS Inter-Frequency Hard Handovers
Based on UL CE for Cell.
Feature Deactivation
1. Disabling load reshuffling algorithms
Disabling uplink LDR on the Uu interface
a. Run the Run the BSC6900 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 UL_UU_LDR(Uplink UU LDR Algorithm) check box under the
parameter Switch for Cell Load Control.
a. Run the Run the BSC6900 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 DL_UU_LDR(Downlink UU LDR Algorithm) check box under the
parameter Switch for Cell Load Control.
a. Run the Run the BSC6900 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 CELL_CODE_LDR(Code LDR Algorithm) check box under the
parameter Switch for Cell Load Control.
b. Run the 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, clear
CELL_CREDIT_LDR (cell credit reshuffling algorithm) under the Switch for Cell Load
Control parameter.
a. Run the Run the BSC6900 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 the NodeB-level
NODEB_CREDIT_LDR_SWITCH(NodeB Credit LDR Switch) or cell group-level
LCG_CREDIT_LDR_SWITCH(Local Cell Group Credit LDR Switch) check box under
the parameter load control algorithm switch.
b. Run the Run the BSC6900 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 NodeB-level
NODEB_CREDIT_LDR(NodeB Credit LDR Algorithm) or cell group-level
LCG_CREDIT_LDR(LCG Credit LDR Algorithm) check box under the parameter NodeB
LDC algorithm switch.
2. Run the Run the BSC6900 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
the HO_ALGO_LDR_ALLOW_SHO_SWITCH and HO_INTER_FREQ_HARD_HO_SWITCH check
boxes under the parameter HandOver Switch.
3. Run the Run the BSC6900 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.
Example
//Activating Inter Frequency Load Balance
MOD UCELLALGOSWITCH: CellId=111,
NBMLdcAlgoSwitch=UL_UU_LDR-1&DL_UU_LDR-1&CELL_CODE_LDR-1&CELL_CREDIT_LDR-1;
SET ULDCALGOPARA:
LdcSwitch=NODEB_CREDIT_LDR_SWITCH-1&LCG_CREDIT_LDR_SWITCH-1;
ADD UNODEBALGOPARA: IDTYPE=BYID, NodeBId=10,
NodeBLdcAlgoSwitch=NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1;
SET UCORRMALGOSWITCH:
HoSwitch=HO_ALGO_LDR_ALLOW_SHO_SWITCH-1&HO_INTER_FREQ_HARD_HO_SWITCH-1;
ADD UINTERFREQNCELL: RNCId=11, CellId=111, NCellRncId=22, NCellId=222, SIB11Ind=TRUE,
SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=FALSE, NPrioFlag=FALSE,
DrdOrLdrFlag=TRUE, InterNCellQualReqFlag=FALSE;
ADD UCELLINTERFREQHONCOV: CellId=111, InterFreqFilterCoef=D3, Hystfor2C=6,
TrigTime2C=D640, InterFreqCovHOThdEcN0=-16, InterFreqMeasTime=60, PeriodFor2C=4,
AmntOfRpt2C=5;
MOD UCELLLDR: CellId=111, InterFreqLDHOMethodSelection=MEASUREHO;
MOD UCELLLDM: CellId=111, UlLdrTrigThd=55, UlLdrRelThd=45, DlLdrTrigThd=70, DlLdrRelThd=60,
DlLdTrnsHysTime=1000;
MOD UCELLLDR: CellId=111, CellLdrSfResThd=SF8;
MOD UNODEBLDR: IDTYPE=BYID, NodeBId=10, UlLdrFirstAction=InterFreqLDHO,
UlLdrCreditSfResThd=SF8, UlInterFreqHoCeLDRSpaceThd=SF8;MOD UCELLLDR: CellId=111,
CodeCongSelInterFreqHoInd=TRUE;
SET ULDCPERIOD: LdrPeriodTimerLen=10;
MOD UCELLLDR: CellId=111, DlLdrFirstAction=InterFreqLDHO, UlLdrFirstAction=InterFreqLDHO,
UlInterFreqHoCellLoadSpaceThd=20, DlInterFreqHoCellLoadSpaceThd=20,
UlInterFreqHoBWThd=2000000, DlInterFreqHoBWThd=200000;
MOD UNODEBLDR: IDTYPE=BYID, NodeBId=10, UlLdrFirstAction=InterFreqLDHO;
MOD UCELLALGOSWITCH: NbmLdcUeSelSwitch=NBM_LDC_MATCH_UE_ONLY;
//Deactivating Inter Frequency Load Balance
MOD UCELLALGOSWITCH: CellId=111,
NBMLdcAlgoSwitch=UL_UU_LDR-0&DL_UU_LDR-0&CELL_CODE_LDR-0&CELL_CREDIT_LDR-0;
SET ULDCALGOPARA:
LdcSwitch=NODEB_CREDIT_LDR_SWITCH-0&LCG_CREDIT_LDR_SWITCH-0;
MOD UNODEBALGOPARA: IDTYPE=BYID, NodeBId=11,
NodeBLdcAlgoSwitch=NODEB_CREDIT_LDR-0&LCG_CREDIT_LDR_SWITCH-0;
SET UCORRMALGOSWITCH:
HoSwitch=HO_ALGO_LDR_ALLOW_SHO_SWITCH-0&HO_INTER_FREQ_HARD_HO_SWITCH-0;
MOD UCELLLDR: CellId=111, CodeCongSelInterFreqHoInd= FALSE;
MOD UNODEBLDR: IDTYPE=BYID, NodeBId=10, UlLdrFirstAction=NoAct;
11.8.7 Troubleshooting
CE-triggerred inter-frequency blind handover
If
handover success ratio is low, check if the Blind Handover Quality Condition
BlindHOQualityCondition of the current cell is too low.
If
there is no CE-triggerred inter-frequency blind handover but there are many times of CE-triggerred
load reshufulling, check if neighbouring cells for blind handover are configured.
CE-triggerred inter-frequency handover based on measurement
If
handover success ratio is low, check the signal quality threshold of the target cell
TargetFreqThdRscp and TargetFreqThdEcN0
If
there is no CE-triggerred inter-frequency handover but there are many times of CE-triggerred load
reshufulling, check if neighbouring cells for measurement are configured.
Data Preparation
None
Feature Activation
1. Run the BSC6900 MML commandADD 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 BSC6900 MML commandADD 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 BSC6900 MML commandADD 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 BSC6900 MML commandADD 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 BSC6900 MML command ADD UCELLCLB (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell-Oriented Parameters for CLB interfreq Load
Banlance 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 Banlance 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 based on code resources,
cell credit resources, and MaxUserNumforCLBIFHO.
The thresholds for inter-frequency load balancing caused by code resource and cell credit resource
congestion are as follows:
UlCreditCSClbTrigThd
UlCreditPSClbTrigThd
DlCreditCSClbTrigThd
DlCreditPSClbTrigThd
UlCreditCSClbRelThd
UlCreditPSClbRelThd
DlCreditCSClbRelThd
DlCreditPSClbRelThd
UlClbCreditSfSpaceThd
DlClbCreditSfSpaceThd
CellSfCSClbTrigThd
CellSfPSClbTrigThd
CellSfCSClbRelThd
CellSfPSClbRelThd
ClbCodeUsedSpaceThd
UlPwrLoadSpaceThd
DlPwrLoadSpaceThd
The thresholds for inter-frequency load balancing caused by cell group credit resource and NodeB
credit resource congestion are as follows:
UlCreditCSClbTrigThd
UlCreditPSClbTrigThd
DlCreditCSClbTrigThd
DlCreditPSClbTrigThd
UlCreditCSClbRelThd
UlCreditPSClbRelThd
DlCreditCSClbRelThd
DlCreditPSClbRelThd
9. Optional: If UL_UU_CLB or DL_UU_CLB is selected under NBMLdcAlgoSwitch in step 2, Run the
BSC6900 MML commandADD 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.
The thresholds for inter-frequency load balancing caused by power resource congestion are as
follows:
UlPwrCSClbTrigThd
UlPwrPSClbTrigThd
DlPwrCSClbTrigThd
DlPwrPSClbTrigThd
UlPwrCSClbRelThd
UlPwrPSClbRelThd
DlPwrCSClbRelThd
DlPwrPSClbRelThd
UlLdTrnsHysTime
DlLdTrnsHysTime
10. Optional: Run the BSC6900 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 BSC6900 MML commandADD 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 Check
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.
Feature Deactivation
1. Run the BSC6900 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
INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD under FuncSwitch1 to disable the license
of the feature for a specified cell.
2. Run the BSC6900 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, under
NBMLdcAlgoSwitch, clear UL_UU_CLB to disable uplink Uu-interface load balancing, clear
DL_UU_CLB to disable downlink Uu-interface load balancing, clear CELL_CODE_CLB to disable
cell code resource load balancing, and clear CELL_CREDIT_CLB to disable cell credit load
balancing for a specified cell.
3. Run the BSC6900 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, under
NodeBLdcAlgoSwitch, clear NODEB_CREDIT_CLB_SWITCH to disable NodeB credit load
balancing and clear LCG_CREDIT_CLB_SWITCH to disable local cell group credit load balancing
for a specified NodeB.
Example
/*Activating the feature WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load
Threshold*/
//Activating the feature WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load
Threshold
//Enabling the license of CLB for a specified cell
ADD UCELLLICENSE: CellId=1, FuncSwitch1=INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD-1; or
MOD UCELLLICENSE: CellId=1, FuncSwitch1=INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD-1;
//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;
//Setting the thresholds for triggering and stopping inter-frequency load balancing caused by code
resource and cell credit resource congestion for a specified cell
//Setting the thresholds for triggering and stopping inter-frequency load balancing caused by cell group
credit resource and NodeB credit resource congestion for a specified cell
ADD UNODEBCLB: IDTYPE=BYID, UlCreditCSClbTrigThd=100, UlCreditPSClbTrigThd=82, DlCreditCSClbTrigThd=100,
DlCreditPSClbTrigThd=82, UlCreditCSClbRelThd=87, UlCreditPSClbRelThd=69, DlCreditCSClbRelThd=87,
DlCreditPSClbRelThd=69; or
MOD UNODEBCLB: IDTYPE=BYID, UlCreditCSClbTrigThd=100, UlCreditPSClbTrigThd=82, DlCreditCSClbTrigThd=100,
DlCreditPSClbTrigThd=82, UlCreditCSClbRelThd=87, UlCreditPSClbRelThd=69, DlCreditCSClbRelThd=87,
DlCreditPSClbRelThd=69;
//Setting the thresholds for triggering and stopping inter-frequency load balancing caused by power
resource congestion for a specified cell
ADD UCELLLDM: UlPwrCSClbTrigThd=100, UlPwrPSClbTrigThd=40, DlPwrCSClbTrigThd=100,
DlPwrPSClbTrigThd=40, UlPwrCSClbRelThd=90, UlPwrPSClbRelThd=30, DlPwrCSClbRelThd=90,
DlPwrPSClbRelThd=30; or
MOD UCELLLDM: UlPwrCSClbTrigThd=100, UlPwrPSClbTrigThd=40, DlPwrCSClbTrigThd=100,
DlPwrPSClbTrigThd=40, UlPwrCSClbRelThd=90, UlPwrPSClbRelThd=30, DlPwrCSClbRelThd=90,
DlPwrPSClbRelThd=30;
/*Deactivating the feature WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load
Threshold*/
//Disabling the license of CLB for a specified cell
MOD UCELLLICENSE: CellId=1,
FuncSwitch1=INTER_FREQ_LOAD_BALANCE_BASEON_CFG_THD-0;
//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;
The counters listed in Table 11-2 measure the number of inter-frequency handovers triggered by the LDR and CLB
features.
Feature Performance
The CLB feature is working properly if the following conditions are met:
The inter-frequency hard handover success rate does not decrease noticeably.
The values of VS.MeanTCP and VS.MeanRTWP are nearly the same for two cells involved in load
balancing.
If the CLB feature is enabled for CS services:
TheCS RAB setup success rate, AMR RAB setup success rate, and CS service drop rate do not
decrease noticeably in the source cell. If any of them decreases noticeably, perform parameter
optimization by referring to 11.9.5 Parameter Optimization.
The values of VS.RAB.AMR.Erlang.cell and VS.AMR.Erlang.BestCell decrease in the source cell.
If the CLB feature is enabled for PS services:
ThePS RAB setup success rate, PS call drop rate, HSDPA call drop rate, and HSUPA call drop rate
do not decrease noticeably in the source cell. If any of them decreases noticeably, perform parameter
optimization by referring to section 11.9.5 Parameter Optimization.
Thevalues of VS.HSUPA.MeanChThroughput.TotalBytes and
VS.HSDPA.MeanChThroughput.TotalBytes decrease in the source cell.
The number of online UEs decreases in the source cell.
The values of VS.CellDCHUEs, VS.HSDPA.UE.Mean.Cell, and VS.HSUPA.UE.Mean.Cell decrease in
the source cell.
11.9.6 Troubleshooting
None
Use this information to determine whether you need to enable Inter-Frequency Redirection Based on
Distance.
Confirm that there are UMTS cells that are not configured with GSM neighbouring cells.
Use this information to determine whether you need to enable Inter-Frequency Redirection Based on
Distance.
Network band and frequencies
Use this information to configure the target band and frequency for distance-based inter-frequency
RRC redirection.
KPI of the cells before activation
Compare the KPI after activation with the KPI before activation to observe the effect
Data Preparation
Parameter Name Parameter ID Setting Description Source
Inter-freq Redirection InterFreqRedirSwitch Decide whether to Network plan
Switch enable this feature
according to the
requirements in 11.10.1
When to Use
Inter-Frequency
Redirection Based on
Distance.
Inter-freq Redirect InterFreqRedirDelayThd 10 Network plan
Propa Delay Thres (internal plan)
Inter-freq Redirection InterFreqRedirFactorOfL 50 Network plan
Factor of LDR DR (internal plan)
Inter-freq Redirection InterFreqRedirFactorOfN 0 Network plan
Factor of Normal orm (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
Feature Activation
1. Run the BSC6900 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 Check
1. Start Uu Interface Trace on the BSC6900 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
Feature Deactivation
o deactivate Inter-frequency Redirection Based on Distance at the RNC level, Run the BSC6900 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 BSC6900 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.
Example
//Activating Inter-frequency Redirection Based on Distance
SET UDISTANCEREDIRECTION: InterFreqRedirSwitch=ON, InterFreqRedirDelayThd=10,
InterFreqRedirFactorOfLDR=50, InterFreqRedirFactorOfNorm=0, RedirBandInd=DependOnNCell;
ADD UCELLDISTANCEREDIRECTION: CellId=1, InterFreqRedirSwitch=ON,
InterFreqRedirDelayThd=10, InterFreqRedirFactorOfLDR=50, InterFreqRedirFactorOfNorm=0,
RedirBandInd=DependOnNCell;
//Deactivating Inter-frequency Redirection Based on Distance
SET UDISTANCEREDIRECTION: InterFreqRedirSwitch =OFF;
MOD UCELLDISTANCEREDIRECTION: CellId=1, InterFreqRedirSwitch =OFF;
11.10.4 Monitoring
Effectivity
You can use the counter VS.RRC.Rej.Redir.Dist.IntraRat to monitor Inter-Frequency Redirection
Based on Distance. If the value of this counter remains steady or keeps increasing, this feature is
functioning properly.
RRC Setup Sucess Rate and Call Drop Rate
You can evaluate the impact of this feature on the cell performance. After activation. this feature
improves RRC setup success rate and reduces call drop rate by redirecting the users on the edge or in
the excessive coverage of a cell.
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
Feature 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 BSC6900, run the BSC6900 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 BSC6900-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 BSC6900 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 Check
1. Initiate Uu interface message tracing on the BSC6900 LMT, as shown in Figure 11-2
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 inFigure 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.
Feature 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 BSC6900, run the BSC6900 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 BSC6900 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.
Example
//Activating Inter-RAT Redirection Based on Distance
//Activating this feature in the entire BSC6900
SET UDISTANCEREDIRECTION: RedirSwitch=ON, DelayThs=100, RedirFactorOfLDR=70,
RedirFactorOfNorm=60;
//Activating this feature in a specified cell
ADD UCELLDISTANCEREDIRECTION: CellId=1, RedirSwitch=ON, DelayThs=100,
RedirFactorOfLDR=80, RedirFactorOfNorm=60;
//Deactivating Inter-RAT Redirection Based on Distance
//Deactivating this feature in the entire BSC6900
SET UDISTANCEREDIRECTION: RedirSwitch=OFF;
//Deactivating this feature in a specified cell
Data Preparation
None
Feature Activation
1. Run the BSC6900 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 BSC6900 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 Check
1. Start Uu Interface Trace on the BSC6900 LMT. Use a UE to initiate an RRC connection setup
request.
2. The following procedure is traced on the Uu interface:
Feature Deactivation
1. Run the BSC6900 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.
Example
//Activating Inter-System Redirect
SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-1;
SET UDRD: ConnectFailRrcRedirSwitch=Allowed_To_Inter_RAT;
//Deactivating Inter-System Redirect
SET UDRD: ConnectFailRrcRedirSwitch=OFF;
Data Preparation
None
Feature Activation
The adaptive multirate (AMR) service that is redirected to an inter-RAT cell during RRC connection setup is used as an
example.
1. Run the BSC6900 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 RRC directed retry decision (DRD) function. In this step, set
Direct Retry Switch to DR_RRC_DRD_SWITCH.
2. Run the BSC6900 MML command SET UREDIRECTION (CME single configuration: UMTS Radio
Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented RRC
Redirection Parameters; CME batch modification center: Modifying RNC Parameters in Batches).
In this step, set RNC-level Traffic Type to AMR and Redirection Switch to
ONLY_TO_INTER_RAT.
3. Optional: Run the BSC6900 MML command MOD UCELLREDIRECTION (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell-level RRC Redirection
Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this
step, set cell-level Traffic Type to AMR and Redirection Switch to ONLY_TO_INTER_RAT.
If a cell is configured with both the RNC-level and cell-level parameters, the cell-level parameter settings take effect.
Activation Check
1. Use a UE to send an RRC_SETUP_REQ message with the cause value "Originating Conversational
Call."
2. The BSC6900 responds with an RRC_CONN_REJ message. If "redirectioninfo" of the message
contains "GSM-TargetCellInfo," this feature has been activated.
Feature Deactivation
1. Run the BSC6900 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 the RRC DRD function.
2. Run the BSC6900 MML command SET UREDIRECTION (CME single configuration: UMTS Radio
Global Configuration Express > Directed Retry Parameter Configuration > RNC-Oriented RRC
Redirection Parameters; CME batch modification center: Modifying RNC Parameters in Batches).
In this step, set Redirection Switch to an appropriate value to disable the RNC-level RRC DRD
based on service steering.
3. Optional: Run the BSC6900 MML command MOD UCELLREDIRECTION (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell-level RRC Redirection
Parameters; CME batch modification center: Modifying UMTS Cell Parameters in Batches). In this
step, set Redirection Switch to an appropriate value to disable the cell-level RRC DRD based on
service steering.
Example
/*Activating Service Steering and Load Sharing in RRC Connection Setup*/
/*Enabling the RRC DRD function*/
SET UCORRMALGOSWITCH: DrSwitch=DR_RRC_DRD_SWITCH-1;
//Setting the RNC-level DRD switch
Data Preparation
None
Feature Activation
1. Run the BSC6900 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 BSC6900 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 BSC6900 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 BSC6900 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 BSC6900 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 Check
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 BSC6900 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.
Feature Deactivation
1. Run the BSC6900 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, deselect
INTRA_FREQUENCY_LDB from the Cell LDC algorithm switch drop-down list.
2. Restore the parameter settings modified in the activation procedure.
Example
//Activating Intra Frequency Load Balance
Data Preparation
None
Feature Activation
1. Run the BSC6900 MML command SET UQUEUEPREEMPT (CME single configuration: UMTS
Radio Global Configuration Express > Queue Preempt Parameters Configuration > RNC
Oriented Queue Preempt Algorithm Parameters; CME batch modification center: Modifying RNC
Parameters in Batches) to turn on the queuing and preemption switches. In this step, set Preempt
algorithm switch to ON and set Queue algorithm switch to ON.
Activation Check
1. Run the BSC6900 MML command LST UQUEUEPREEMPT to check whether the queuing and
preemption switches are turned on.
Feature Deactivation
1. Run the BSC6900 MML command SET UQUEUEPREEMPT (CME single configuration: UMTS
Radio Global Configuration Express > Queue Preempt Parameters Configuration > RNC
Oriented Queue Preempt Algorithm Parameters; CME batch modification center: Modifying RNC
Parameters in Batches) to turn off the queuing and preemption switches. In this step, set Preempt
algorithm switch to OFF and set Queue algorithm switch to OFF.
Example
//Activating Queuing and Preemption
SET UQUEUEPREEMPT: PreemptAlgoSwitch=ON, QueueAlgoSwitch=ON;
//Deactivating Queuing and Preemption
SET UQUEUEPREEMPT: PreemptAlgoSwitch=OFF, QueueAlgoSwitch=OFF;
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
Feature Activation
Activating QoS negotiation
1. Run the BSC6900 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 BSC6900 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 Check
Verifying QoS negotiation
1. Run the BSC6900 MML command LST UCORRMALGOSWITCH to query the activation result.
2. Start Iu message tracing on the BSC6900 LMT and establish a PS service, as shown in Figure 11-4.
Feature Deactivation
Deactivating QoS negotiation
1. Run the BSC6900 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, deselect DRA_DCCC_SWITCH from the Dynamic Resource
Allocation Switch drop-down list box, and deselect 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
1. Run the BSC6900 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, deselect DRA_DCCC_SWITCH from the Dynamic Resource
Allocation Switch drop-down list box, and deselect PS_RAB_DOWNSIZING_SWITCH from the PS
rate negotiation switch drop-down list box.
Example
//Activating Rate Negotiation at Admission Control
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1, PsSwitch
=PS_BE_IU_QOS_NEG_SWITCH-1&PS_STREAM_IU_QOS_NEG_SWITCH-1;
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-1,
PsSwitch=PS_RAB_DOWNSIZING_SWITCH-1;
//Deactivating Rate Negotiation at Admission Control
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-0, PsSwitch
=PS_BE_IU_QOS_NEG_SWITCH-0&PS_STREAM_IU_QOS_NEG_SWITCH-0;
SET UCORRMALGOSWITCH: DraSwitch=DRA_HSUPA_DCCC_SWITCH-0,
PsSwitch=PS_RAB_DOWNSIZING_SWITCH-0;
12 Parameters
Table 12-1 Parameter description
Parameter ID NE MML Feature ID Feature Name Description
Command
CellOverrunTh BSC6900 ADD WRFD-020104 Intra Frequency Meaning:If the cell downlink
d UCELLLDB Load Balance load exceeds this threshold,
the algorithm will decrease
MOD the pilot transmit power of
UCELLLDB the cell so as to increase the
whole system's capacity.
This parameter is based on
network planning.
GUI Value Range:0~100
Actual Value Range:0~1
Unit:%
Default Value:90
CellUnderrunT BSC6900 ADD WRFD-020104 Intra Frequency Meaning:If the cell downlink
hd UCELLLDB Load Balance load is lower than this
threshold, the algorithm will
MOD increase the pilot transmit
UCELLLDB power of the cell so as to
ChoiceRprtUni BSC6900 SET ULDM WRFD-020102 Load Meaning:If you set this
tForHsdpaPwr Measurement parameter to TEN_MSEC,
Meas use [HSDPA need pwr meas
cycle,Unit:10ms] to specify
the measurement report
period. If you set this
parameter to MIN, use
[HSDPA need pwr 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
ChoiceRprtUni BSC6900 SET ULDM WRFD-020102 Load Meaning:If you set this
tForHsdpaRat Measurement parameter to TEN_MSEC,
eMeas use [HSDPA bit rate meas
cycle,Unit:10ms] to specify
the 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
ChoiceRprtUni BSC6900 SET ULDM WRFD-020102 Load Meaning:If you set this
tForHsupaRat Measurement parameter to TEN_MSEC,
eMeas use [HSDPA bit rate meas
cycle,Unit:10ms] to specify
the 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
DlCacAvgFilter BSC6900 SET ULDM WRFD-020102 Load Meaning:The RNC filters the
Len Measurement common measurements
reported by the NodeB. The
filtered values are used for
call admission control (CAC)
DlLdrAvgFilter BSC6900 SET ULDM WRFD-020102 Load Meaning:The RNC filters the
Len Measurement common measurements
reported by the NodeB. The
filtered values are used for
Load Reshuffle (LDR).
This parameter sets the
length of a filter window and
is applied to filtering of the
following common
measurements:
1. Transmitted Carrier Power
2. Transmitted carrier power
of all codes not used for
HS-PDSCH, HS-SCCH,
E-AGCH, E-RGCH, or
E-HICH transmission
GUI Value Range:1~32
Actual Value Range:1~32
Unit:None
Default Value:5
DlOlcAvgFilter BSC6900 SET ULDM WRFD-020102 Load Meaning:The RNC filters the
Len Measurement common measurements
reported by the NodeB. The
filtered values are used for
Overload Control (OLC).
This parameter sets the
length of a filter window and
is applied to filtering of the
following common
measurements:
1. Transmitted Carrier Power
2. Transmitted carrier power
MaxFachPowe BSC6900 ADD UFACH WRFD-020501 Open Loop Meaning:The offset between
r Power Control the FACH transmit power
MOD UFACH and P-CPICH transmit
power in a cell.
GUI Value Range:-350~150
Actual Value Range:-35~15
Unit:0.1dB
Default Value:10
UlCacAvgFilter BSC6900 SET ULDM WRFD-020102 Load Meaning:The RNC filters the
Len Measurement common measurements
reported by the NodeB. The
filtered values are used for
UlLdrAvgFilter BSC6900 SET ULDM WRFD-020102 Load Meaning:The RNC filters the
Len Measurement common measurements
reported by the NodeB. The
filtered values are used for
Load Reshuffle(LDR).
This parameter sets the
length of a filter window and
is applied to filtering of the
following common
measurements:
1. Received Total Wide Band
Power
2. Received Scheduled
E-DCH Power Share
GUI Value Range:1~32
Actual Value Range:1~32
Unit:None
Default Value:5
UlOlcAvgFilter BSC6900 SET ULDM WRFD-020102 Load Meaning:The RNC filters the
Len Measurement common measurements
reported by the NodeB. The
filtered values are used for
Overload Control(OLC).
This parameter sets the
length of a filter window and
is applied to filtering of the
following common
measurements:
1. Received Total Wide Band
Power
2. Received Scheduled
E-DCH Power Share
GUI Value Range:1~32
WeakCovRrcR BSC6900 SET UFRC WRFD-0204000 Inter System Meaning:The cell signal
edirEcNoThs 3 Redirect quality is indicated by the
Ec/No reported by UEs in
the cell. If the value of Ec/No
is lower than the threshold,
the cell signal quality is poor,
and the UEs are redirected
to the neighboring GSM cell
when the
"PERFENH_RRC_WEAK_R
EDIR_SWITCH" parameter
in the "SET UCORRMPARA"
command is set to ON.
Actual Value = (GUI Value -
49(offset)) x 0.5.
GUI Value Range:0~49
Actual Value Range:-24.5~0
Unit:dB
Default Value:13
13 Counters
Table 13-1 Counter description
Counter ID Counter Name Counter Description NE Feature ID Feature Name
14 Glossary
For the acronyms, abbreviations, terms, and definitions, see the 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