3G UL-DL Capacity Monitoring V1.0

Check et résolution des problèmes liés à la capacité UL ou DL
1. DL Capacity improvement
1.1 Capacity Definition
Downlink capacity improvement involves increase in the number of subscribers in a cell, throughput rate per
cell, cell throughput, and common channel (CCH) capacity. Features and parameters related to limited device
resources can also be used to increase the number of subscribers in a cell.
1.2 Radio Resource Limited

1.2.1 Scenario 1: Channel Quality Limited
1.2.1.1 Scenario Description
The cell coverage is poor. CQIs reported by UEs are low. Consequently, the throughput rate per subscriber and
the throughput rate per cell are low.
1.2.1.2 Criteria
Table 1: Criteria for identifying the channel quality limited scenario
Scenario Time Criteria Other Criteria

Channel quality limited Busy hours Mean CQI reported by the cell < 15 Not limited
1.2.1.3 Optimization Solutions
Solution 1: antenna adjustment
Check the azimuth and downtilt of the antenna and determine whether the coverage direction is correct.
Solution 2: optimization of neighboring cells
Check the configuration of neighboring cells and determine whether coverage overlap or neighboring cell
interference exists.
Solution 3: capacity expansion
If the interference in a cell increases and the CQI is low because the downlink load is higher than 90%, it is
recommended that more carriers or NodeBs be added to expand the capacity. For details about the
multicarrier policy, see the Multicarrier Technical Guide.
Solution 4: checking the CCH PO settings
Check whether the power settings of downlink CCHs are in the valid range. By default, the CCH power
proportion (the ratio of the CCH power to the total power) is 20% or below when CCHs do not carry any
service.
Table 2: Default CCH power settings
Channel Type Default Value of the Power

Proportion
BCH -20
SSCH -50
NOVATEL_IT_Algeria_Internal_Document_V032016 RNO_Departement
PSCH -50
AICH -6
PICH -7
Solution 5: pilot power adjustment
By default, the pilot power is 10% of the maximum cell power. If the pilot power is not the default value, check
why the setting is modified. Unless the pilot power is modified to meet the requirements of related features,
you are advised to use the default pilot power. To modify the pilot power, run the following command:
MOD UCELL: CellId=100, PCPICHPower=xxx;
Solution 6: MPO constant adjustment
The reported CQI may be small because the MPO constant is set to a value higher than the default 2.5 dB. In
this case, you are advised to modify the MPO constant to the default value. To modify the MPO constant, run
the following command:
MOD UCELLHSDPA: CellId=100, HsPdschMPOConstEnum=2.5DB;
1.2.2 Scenario 2: TCP Load Limited

The TCP power is an important resource for downlink data transmission. If the power consumed by non-HSDPA
services is too high or the total power load is too heavy, the downlink rate decreases.
1.2.2.2 Criteria
Criteria for identifying the TCP load limited scenario
Table 3: TCP load limited scenario

TCP load limited Busy hours Non-HS TCP utilization ratio > 70%, or downlink Not limited
power congestion ratio > 1%, or total TCP
utilization ratio > 80%
High RRC load (> 10%)
High FACH load (> 15%)
High PCH load (> 15%)
High R99 load (> 25%)
High HSDPA load (> 50%)
High CCH load (> 25%)
Solution 1: adding carriers
Add carriers for cells with high TCP load. For details about the multicarrier policy, see the Multicarrier Technical
Guide
Solution 2: adding NodeBs
Add NodeBs to share load in hotspot areas. It is recommended that the capacity-based automatic NodeB
addition tool be used to evaluate the location and quantity of NodeBs to be added.
Solution 3: Sector addition solution
If it is difficult to add carriers or split NodeBs in hotspot areas, adding sector solution is recommended.
Solution 4: mini NodeBs
If the TCP load is limited in the case of indoor coverage, it is recommended that mini NodeBs be used for
capacity expansion.
Solution 5: L2+
The enhanced L2 supports the variable PDU size, which provides large-sized PDUs for the high-rate
transmission and small-sized PDUs for the cell-edge coverage. In addition, the enhanced L2 eliminates the extra
header overhead of the PDUs with a fixed size, therefore improving the transmission efficiency on the Iub and
Uu interfaces.
The enhanced L2 is the prerequisite for the 64QAM, MIMO, and enhanced CELL_FACH. When adopted, it can
improve the transmission efficiency on the Iub and Uu interfaces.
For the radio link control (RLC) in AM mode, the downlink peak rate for a single user equipment (UE) is
determined by the RLC PDU size, the RLC transmit window, and the delay of the RLC end-to-end loopback. The
enhanced L2 introduces the variable RLC PDU size and new MAC-ehs entity. When the enhanced L2 is adopted,
the downlink peak rate is no longer determined by multiplying the PLC PDU size and the RLC transmit window.
When the 64QAM and the MIMO are also adopted, the downlink peak rate of a single UE can reach 20 Mbit/s.
To apply the enhanced L2, you should run the MML command to enable the feature in the cell.
To enable the L2+ feature, run the following command:
MOD UCELLALGOSWITCH: CellId=100, HspaPlusSwitch=DL_L2ENHANCED-1;
Solution 6: 64QAM
The 3GPP R7 protocols introduce the enhanced technology of 64QAM.
When the channel is of higher quality, the 64QAM, a more advanced modulation technology than the 16QAM,
can be applied to the downlink transmission. Theoretically, the 64QAM supports a peak rate of 21 Mbit/s on
the Uu interface, and increases the average throughput of the RNC. The simulation results show that the
64QAM, compared with the 16QAM, can increase the average throughput by 7% and 16% in a macro cell and in
a micro cell separately when the UEs in the cells use the type 3 receivers.
The enhanced L2 is a prerequisite for the implementation of the 64QAM.
The 64QAM increases the peak rate for the UE and expands the cell capacity.
The mobile network operators lay great emphasis on the PS service and regard it as an ever-expanding
profitable field. Predictions from many consulting companies indicate that the booming traffic volume of the PS
service will impose higher requirements on the network throughput. If the bandwidth remains unchanged, the
64QAM will increase the average throughput of the system by 7% to 16% and make better use of the spectrum.
As a result, the RNC is capable of providing higher throughput, therefore increasing the operators' profits on
each bandwidth.
In addition, the 64QAM provides a higher download data rate, which betters the user experience and enhances
the competitiveness of the mobile network operators.
First, the RNC acquires the information on whether the UE and the cell support the 64QAM. Then, if the RNC
determines that the 64QAM is applicable, it sends the information about the HS-DSCH Category of the UE to
the NodeB or the DRNC through the signaling on the Iub or Iur interface, to notify the two network elements
that the UE supports the 64QAM.
After that, the NodeB or the DRNC determines whether to apply the 64QAM. If the 64QAM is applied, the RNC
sets the parameters of the UE related to the 64QAM through the signaling on the Uu interface. Meanwhile, the
enhanced L2 technology is applied. In the MAC-hs scheduling performed once every two ms, the NodeB
determines whether to apply the 64QAM on the basis of the channel quality indicator (CQI) of the UE, the code
resources on the HS-PDSCH, and the power resources.
To apply the 64QAM, you should activate the license. Run the MML command to enable the algorithm for the
64QAM, and to enable the cell to support the 64QAM and the enhanced L2.
To enable the 64QAM feature, perform the following steps:
1. Activate the 64QAM license: ACT LICENSE: ISPRIMARYPLMN=YES,

FUNCTIONSWITCH4=HSPA_DOWN21_PER_USER-1, ACTOBJECT=LOCAL;
2. Turn on the RNC-level algorithm switch for the 64QAM feature: SET CORRMALGOSWITCH:
CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1;
3. Turn on the cell-level algorithm switch for the 64QAM feature: MOD CELLALGOSWITCH: CellId=100,
HspaPlusSwitch=64QAM-1&L2ENHANCED-1;
Solution 7: DC-HSDPA
When Dual Carrier-HSDPA (DC-HSDPA) is enabled, the downlink connections can be established simultaneously
between the UE and two inter-frequency co-coverage cells that are configured with consecutive frequencies
and controlled by the NodeB. The two cells can schedule the UE simultaneously, therefore increasing the
downlink peak throughput of the UE. When the UE is located at the edge of a cell, the gain of its downlink peak
throughput becomes greater.
The DC-HSDPA helps to increase the throughput of a single UE and a cell.
Increasing the throughput of a single UE
Owing to the application of DC-HSDPA, the throughput of the UE at both the center and edge of the cell is
doubled. If the DC-HSDPA is used together with 64QAM, the throughput of the UE at the center of a cell can
reach 42 Mbit/s theoretically.
Increasing the throughput of a cell
Owing to the application of DC-HSDPA, the total throughput of the two inter-frequency co-coverage cells is
increased by 5% to 10%. The gain of the throughput is inversely proportional to the number of the UEs in a cell.
The RNC checks whether the UE and cells support DC-HSDPA. When DC-HSDPA is required, the RNC configures
two radio links to the NodeB by using the Iub signaling RADIO LINK SETUP REQUEST, RADIO LINK ADDITION
REQUEST, and RADIO LINK RECONFIGURATION PREPARE and the RNC configures two radio links to the UE by
using Uu signaling RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION, ACTIVE SET UPDATE,
PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, CELL UPDATE CONFIRM. Then,
the downlink connections between the UE and two inter-frequency co-coverage cells can be established so that
DC-HSDPA can be applied.
Figure 1: DC-HSDPA procedure
Solution 8: Power Margin parameter

Supplementary Carrier DL HS-SCCH/HS-PDSCH
Power Margin indicates the power headroom reserved for soft handovers. The power cannot be consumed by
services. More power can be allocated to services if the value of Power Margin is set to a smaller value.
Table 4: Power margin parameters
Command NE Parameter Default Value

SET MACHSPARA NodeB PWRMGN 5
If the value of Power Margin is too small, soft handovers may fail. If the value of Power Margin is too large, only
a small amount of power can be allocated to other services and the service rate is low.
1.2.2.3.1 Sub-Scenario 1: high RRC load
Symptom
The RRC service consumes much power. Consequently, only a small amount of power is allocated to other
services.
The RRC load takes up more than 30% of the total load of a cell.
Solution 1: optimization of the periodic location update timer or the periodic route update timer
The duration of the periodic location or route update timer can be increased to reduce the number of RRC
connection requests initiated during registration.
MOD UCNDOMAIN: CNDomainId=CS_DOMAIN, T3212=40;
The advantages and disadvantages after T3212 is modified must be considered and reported to the customer
before the modification.
If the value of T3212 is too small, a lot of RRC requests are initiated and too many resources are consumed. If
the value of T3212 is too large, the paging success rate of UEs may decrease.
Solution 2: Reduce RRC related to LU at LAC borders
Reduce the number of RRC linked to REG ( a reasonable value is 20% or RRC are linked to LU at LAC borders). In
order to achieve this, check coverage and overlopping at LAC borders and try to reduce them as much as
possible by coverage control or by changing CIO and idleqoffset2sn (or idleqoffset1sn depending on reselection
strategy) or change LAC boundaries in order to be more reasonable and ovoid high traffic areas. For further
actions check section related to Handover.
Solution 3: Reduce RRC related to IRAT
Reduce the number of RRC linked to IRAT ( a reasonable value is around 20%). In order to achieve this, check
coverage of the area and EcNo level, or change IRAT parameters in order to reduce the number of IRAT
attempts. For further actions check section related to InterRAT Handover.
Solution 4: signaling storm solution
The PS non-active time can be extended and the CELL PCH, R8FD, and EFD features can be enabled to reduce
the number of RRC connection requests initiated during service access attempts.
1.2.2.3.2 Sub-Scenario 2: high FACH load
Symptom
The FACH consumes much power. Consequently, only a small amount of power is allocated to other services.
The FACH load takes up more than 30% of the total load of a cell.
Optimization Solutions
Solution 1: FACH UE power control
Supports two power control algorithms to FACH UE, which helps to relieve the cell power overload state:
1. Add power admission to FACH UE.

2. Decrease the transmit power of FACH channel (when the cell is in overload congestion state).
The RNC provides two methods to relieve the cell overload state:
 CELL_FACH UE admission algorithm: For RRC connection request and RAB assignment carried on FACH:
o If the switch of FACH_UU_ADCTRL is on, when the cell is in overload congestion state, the call
will be rejected if the cell is in the OLC state. Otherwise, the call will be accepted.
o If the switch of FACH_UU_ADCTRL is off, the call will be accepted no matter whether the cell
is in the state of OLC or not.
When the cell is in the OLC state, the RNC will decrease the maximum power of the FACH if possible. When the
cell exits the OLC state, the RNC will recover the power immediately.
To enable the FACH UE power control feature, perform the following steps:
Activate the FACH subscriber admission algorithm.
ADD UCELLALGOSWITCH: CellId=1101, NBMCacAlgoSwitch=FACH_UU_ADCTRL-1;
Configure the FACH power reduction parameter.
ADD UCELLOLC: CellId=1101, FACHPwrReduceValue=9;
Solution 2: Add a second S-CCPCH
Add a secondary SSCPCH in order to reduce FACH congestion in cells with high FACH usage ratio.
Solution 3: increasing the duration of the DCH-to-FACH state transition timer for best effort (BE)
services
The BeD2FStateTransTimer timer is used for the DCH-to-FACH state transition of BE services. It checks whether
UEs, which are using non-real-time services and are in the CELL_DCH state, are also in the stable low active
state. If the duration of this timer increases, the number of subscribers on the FACH and the service volume are
reduced.
Table 5: DCH to FACH transition timers.
Original
Default Recommended
Command NE Parameter Recommended
Value Value
Value
SET
RNC BeD2FStateTransTimer N/A 5 6
UUESTATETRANSTIMER
If the value of BeD2FStateTransTimer is too small, it is difficult to determine whether a UE is in the stable low
active state. If the value of BeD2FStateTransTimer is too large, the dedicated channel resources are wasted.
BeD2FStateTransTimer must be set based on the BE service model and the number of times that the low active
count is reported.
If the duration of the timer increases, services are carried on the dedicated channels for a longer time, which
consumes more dedicated channel resources.
Solution 4: increasing the duration of the HS-DSCH-to-FACH state transition timer for BE services
The BeH2FStateTransTimer timer is used for HS-DSCH-to-FACH state transition of BE services. It checks whether
UEs, which are using non-real-time services and are in CELL_DCH (used for HS-DSCH) state, are also in the
stable low active state. If the duration of this timer increases, the number of subscribers on the FACH and the
service volume are reduced.
Table 6: HSDPA to FACH transition timers.
Original
Default Recommended
Command NE Parameter Recommende
Value Value
d Value
SET RN
BeH2FStateTransTimer N/A 5 6
UUESTATETRANSTIMER C
If the value of BeH2FStateTransTimer is too small, it is difficult to determine whether a UE is in the stable low
active state. If the value of BeH2FStateTransTimer is too large, the dedicated channel resources are wasted.
BeH2FStateTransTimer must be set based on the BE service model and the number of times that the low active
count is reported.
If the duration of the timer increases, services are carried on the HS-DSCHs for a longer time, which consumes
more HS-DSCH resources.
Solution 5: decreasing the D2F/R or F/R2P 4B threshold of BE services
The D2F2PTvmThd parameter is used to check whether a UE is in the low active state. For UEs on the DCH, the
low active counter increases by 1 each time a 4B service volume event is reported. For UEs on the FACH, the
low active counter increases by 1 each time a 4B service volume event is reported and the 4B service volume is
0. If the value of D2F2PTvmThd decreases, the number of D2Fs can be reduced.
Table 7: DCH to FACH 4B thresholds.
Original
Default Recommended
Value Value
Value
SET UUESTATETRANS RNC D2F2PTvmThd N/A D64 D32
D2F2PTvmThd must meet the following requirements:
D2F2PTvmThd < F2DTvmThd
D2F2PTvmThd < BeEFach2DTvmThd
If the value of D2F2PTvmThd decreases, the number of D2Fs can be reduced. The D2F event may not be
reported as usual. Therefore, services continue to occupy the DCH resources.
Solution 6: decreasing the F/R2D 4A threshold of BE services
The BeF2DTvmThd parameter specifies the threshold for trigging the FACH-to-DCH 4A event. If the value of
BeF2DTvmThd decreases, it is easier to trigger the 4A event.
Table 8: FACH to DCH 4A thresholds.
Original
Default Recommended
Value Value
Value
SET UUESTATETRANS RNC BeF2DTvmThd N/A D1024 D512
BeF2DTvmThd must meet the following requirement:
D2F2PTvmThd < F2DTvmThd
If the value of BeF2DTvmThd decreases, it is easier to trigger the 4A event. Services may be migrated to DCHs
and more resources are occupied. If the value of BeF2DTvmThd is too large, CCH congestion may occur.
Solution 7: decreasing the HS-DSCH2F 4B threshold of BE services
The BeH2FTvmThd parameter is used to check whether a UE is in the low active state. For UEs on the HS-DSCH,
the low active counter increases by 1 each time a 4B service volume event is reported. If the value of
BeF2DTvmThd decreases, the 4B event may not be reported as usual.
Table 9: HSDSCH to FACH 4B Threshold.
Original
Default Recommended
Value Value
Value
SET UUESTATETRANS RNC BeH2FTvmThd N/A D64 D32
BeH2FTvmThd must meet the following requirements:
 BeH2FTvmThd < BeF2HTvmThd
 BeH2FTvmThd < BeEFach2HTvmThd
 BeH2FTvmThd < BeEFach2CpcTvmThd
 BeH2FTvmThd < BeF2CpcTvmThd
If the value of BeF2DTvmThd decreases, the 4B event may not be reported as usual. Therefore, BE services
continue to occupy the HS-DSCH resources.
Solution 8: decreasing the F2HS-DSCH 4A threshold of BE services
The BeF2HTvmThd parameter specifies the threshold for trigging the FACH-to-HS-DSCH 4A event. If the value of
BeF2HTvmThd decreases, it is easier to trigger the 4A event.
Table 10: FACH to HSDSCH 4A tresholds.
Original
Default Recommended
Value Value
Value
SET UUESTATETRANS RNC BeF2HTvmThd N/A D1024 D512
BeF2HTvmThd must meet the following requirement:
BeH2FTvmThd < BeF2HTvmThd
If the value of BeF2HTvmThd decreases, it is easier to trigger the FACH-to-HS-DSCH 4A event. Therefore,
services may be migrated to HS-DSCHs and more HS-DSCH resources are occupied. If the value of
BeF2HTvmThd is too large, CCH congestion may occur.
1.2.2.3.3 Sub-Scenario 3: high R99 load
Symptom
The R99 services consume much power. Consequently, the power allocated to HSPA services is insufficient.
The R99 load takes up more than 50% of the total load of a cell.
Solution 1: downlink load–based LDR BE rate reduction
When the downlink power reaches a specified threshold, the R99 BE service rate reduction is triggered to
reduce the power consumption of R99 subscribers. During the BE rate reduction process, RABs queue up in
descending order of the comprehensive priority. The BE rate reduction algorithm selects the BE service that has
the lowest comprehensive priority and is transmitted at a rate higher than the GBR. If multiple RABs have the
lowest comprehensive priority, the BE service with the highest rate is selected. You can set the
DlLdrBERateReductionRabNum parameter to specify the number of selected RABs.
Table 11: DL LDR action BE Rate reduction
Command NE Parameter Default Value Recommended

Value
MOD UCELLLDR RNC DlLdrThirdAction N/A BERateRed
If the power- and NodeB credit-based admission control is disabled, you are advised not to enable the LDR BE
reduction feature to prevent ping-pong handovers. LDR BE rate reduction takes effect only after the DCCC
algorithm is activated. After the BE rate reduction, the downlink data rates of some R99 subscribers decrease,
affecting the service experience of these subscribers.
1.2.2.3.4 Sub-Scenario 4: high HSDPA load
Symptom
The HSDPA services consume much power. The HSDPA load takes up more than 50% of the total load of a cell.
Solution 1: power/code balancing
In power preferred resource allocation mode, HSDPA services preferentially use the power resource. In
power/code balancing allocation mode, HSDAP performance degradation caused by exhaustion of a single type
of resources can be prevented, and the cell capacity can be improved.
Table 12: MAC HSDPA ressorce balancing parameters.
Command NE Parameter Default Recommended Value

Value
SET MACHSPARA NodeB RSCALLOCM N/A POWERCODE_BAL
Solution 2: HSSCCH dynamic power control
SET MACHSPARA: HSSCCHPWRCMINDCH=CQI;
Solution 3: R99/HSDPA multicarrier dynamic power sharing
In multi-carriers mode, the carrier bearing the HSDPA services can dynamically share the power unused by
another carrier. In this way, the power usage of the power amplifier and HSDPA service rate can be improved.
 The performance of the network and usage of the existing network devices is improved.
 According to the emulation results, the capacity of the HSDPA cell is improved by 5% to 6% in two-
carrier dynamic sharing mode.
If there are an R99 carrier and an HSDPA carrier, the R99 carrier periodically sends the current excessive power
for sharing to the HSDPA carrier according to the UE configuration and load of the current services. In this case,
the HSDPA carrier uses the excessive power shared by the R99 carrier based on the original power allocation
when performing the HSDPA service scheduling.
To enable the R99/HSDPA multicarrier dynamic power sharing feature, perform the following steps:
1. Activate the following license: LQW9PASHR01 Power Sharing (per NodeB)

2. Add a power sharing group: ADD PAGRP: SLOCELL = 0, DLOCELL = 1, MAXSHRTO = 50, SHMGN =10;
Solution 5: HS-SCCH Less Operation
The HS-SCCH Less Operation is the key feature of the CPC. When the feature is applied, the HS-DSCH does not
need to be accompanied by the HS-SCCH in the initial transmission of data, whereas the HS-DSCH needs to be
accompanied by the HS-SCCH in the data re-transmission in HARQ mechanism.
The HS-SCCH Less Operation is applicable when the UE is in CELL_DCH state and is configured with the F-DPCH
instead of the DCH. The HS-SCCH Less Operation is independent of the DTX and DRX.
This feature reduces the transmission on the HS-SCCH, therefore increasing the capacity of PS services on the
uplink channels.
First, the RNC acquires the information on whether the UE and the cell support the HS-SCCH Less Operation.
Then, if the RNC determines that the HS-SCCH Less Operation is applicable, it sets the parameters of the NodeB
or the DRNC related to the HS-SCCH Less Operation through the signaling on the Iub or Iur interface. After that,
the RNC sets parameters of the UE related to the HS-SCCH Less Operation through the signaling on the Uu
interface.
To apply the HS-SCCH Less Operation, you should activate the license. Run the MML command to enable the
algorithm for the HS-SCCH Less Operation and to enable the cell to support the HS-SCCH Less Operation.
To enable the HS-SCCH Less Operation feature, perform the following steps:
1. Activate the license of the HS-SCCH Less Operation feature: SET LICENSE: SETOBJECT=UMTS,
ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=CPC_HS_SCCH-1;
2. Turn on the RNC-level algorithm switch for the HS-SCCH Less Operation feature: SET
UCORRMALGOSWITCH: CfgSwitch= CFG_HSPA_HSSCCH_LESS_OP_SWITCH-1;
3. Turn on the cell-level algorithm switch for the HS-SCCH Less Operation feature: MOD
UCELLALGOSWITCH: CellId=100, HspaPlusSwitch=HS_SCCH_LESS_OPERATION-1;
1.2.2.3.5 Sub-Scenario 5: high CCH load
Symptom
The CCH consumes too much power of the cell. Consequently, the power allocated to services is low. The CCH
load takes up more than 20% of the total load of a cell.
Solution 1: pilot power reduction
If the pilot power decreases, more power can be saved for data transmission of services and the throughput of
a cell can increase, but the cell coverage is affected. It is recommended that the default pilot power be used. By
default, the pilot power is set to 10% of the maximum transmit power of the cell.
To modify the pilot power, run the following command:
MOD UCELL: CellId=100, PCPICHPower=xxx;
Solution 2: CCH PO optimization
If the power proportion of CCHs (such as the PSCH, SSCH, and BCH) is reduced, the CQI reported by a UE can
slightly increase and the CCH power can be reduced. In this way, more power can be allocated to services.
The following configuration is recommended for the CCH PO optimization:
ADD UBCH: CellId=100, BCHPower=-60;
MOD UPICHPWROFFSET: CellId=100, PICHPowerOffset=-2;
If the power proportion of CCHs is reduced, subscriber access KPIs may be affected.
1.2.3 Scenario 3: BLER Limited

The BLER of a cell is high. Consequently, the throughput rate per subscriber and the throughput rate per cell
are low.
1.2.3.2 Criteria
Criteria for identifying the BLER limited scenario
Table 13: BLER Limited criteria

BLER limited Busy hours BLER > 20% Not limited
Solution 1: dynamic BLER–based CQI correction
To enable the dynamic BLER–based CQI correction feature, run the following command:
SET MACHSPARA:CQIADJALGOFNONCON=CQI_ADJ_BY_DYN_BLER;
Solution 2: MPO constant adjustment
If the MPO constant is not properly set, the CQI may be unreasonably high. Therefore, an appropriate MPO
constant can be set so that the CQI is closer to the actual value. This can reduce the BLER, and increase the
power utilization ratio and the throughput rate per cell. It is recommended that the MPO constant be set to the
default value (2.5 dB).
To modify the MPO constant, run the following command:
MOD UCELLHSDPA: CellId=100, HsPdschMPOConstEnum=2.5DB; //The default value is 2.5 dB.
1.3 Device Resource Limited

1.3.1 Scenario Description
CE, code, and Iub-interface resources on the network side are limited. Consequently, subscribers cannot access
the network, or the service rates of online subscribers are low. For this type of cells, you can improve the
capacity by analyzing the causes of device resource limitation.
1.3.2 Criteria
Criteria for identifying the device resource limited scenario
Table 14: Ressource limited senario
Scenario Time Criteria Other

Device resource limited Busy hours HSDPA CELL Active& Number of HSDPA subscribers
Number of HSDPA subscribers > limited
Maximum number of subscribers
supported by a cell x 85%
NodeB admission CE utilization ratio > Admission CE limited
70%
CE congestion occurs.
NodeB physical CE utilization ratio > 70% Physical CE limited
CE congestion occurs.
Iub-interface downlink congestion rate > Iub-interface bandwidth limited
1%
Downlink Iub-interface congestion Iub-interface QoS limited
duration > 0
R99 code utilization ratio > 70%, or Code resource limited
R99+HSPA code utilization ratio > 80%,
or code congestion rate > 1%
1.3.3 Optimization Solutions
1.3.3.1 Sub-Scenario 1: number of HSDPA subscribers limited
Symptom
The number of HSDPA subscribers is large, or access to HSDPA services fails. Consequently, the service rate is
low.
Solution 1: increasing the maximum number of uplink HSDPA subscribers
If the maximum number of HSDPA subscribers configured for a cell is small, increase the number of HSDPA
subscribers to allow more subscribers to use the HSDPA bearer. In this way, the throughput rate increases.
To modify the maximum number of HSDPA subscribers of the cell, run the following command:
MOD UCELLCAC: CellId=100, MaxHsdpaUserNum=64;
Solution 2: adding carriers
Add carriers for cells with high TCP load. For details about the multicarrier policy, see the Multicarrier Technical
Guide.
Solution 3: adding NodeBs
Add NodeBs to share load in hotspot areas. It is recommended that the capacity-based automatic NodeB
addition tool be used to evaluate the location and quantity of NodeBs to be added.
Solution 5: mini NodeBs
If the TCP load is limited in the case of indoor coverage, it is recommended that mini NodeBs be used for
capacity expansion.
1.3.3.2 Sub-Scenario 2: admission CE limited
Symptom
The downlink admission CE utilization ratio of a NodeB is high and admission failures caused by CE congestion
exist. Consequently, subscribers cannot access the network and the throughput rate per cell is low.
Solution 1: GBR adjustment
R99 subscribers are admitted based on the GBR. As the GBR becomes larger, the number of admission CEs also
increases and congestion is more likely to occur. If the GBR is decreased, more subscribers can be admitted and
admission of data transmission subscribers can be ensured.
To modify the GBR, run the following command:
SET UUSERGBR: TrafficClass=INTERACTIVE, DlGBR=D16;
Solution 2: initial bit rate adjustment
When R99 DCCC is enabled, subscribers are admitted based on the initial bit rate. If the initial bit rate is too
high, the number of admission CEs is large. This increases the possibility of congestion and affects the timely
access of subscribers who need to transmit data. Reduction of the initial bit rate allows admission of more
subscribers and increases the throughput rate per cell.
To modify the initial bit rate, run the following command:
SET UFRC: DlBeTraffInitBitrate=D16;
Solution 3: reduction of the HSDPA bearer threshold
HSDPA services do not consume CEs. When the R99 downlink CEs are limited, the HSDPA bear threshold
(DlBeTraffThsOnHsdpa) can be reduced to admit subscribers to the HSDPA bearer. In this way, the throughput
rate per cell increases.
If the current DlBeTraffThsOnHsdpa is 64 kbit/s, you are advised to modify the threshold to 32 kbit/s or 16
kbit/s.
To modify the threshold to 32 kbit/s, run the following command:
SET UFRCCHLTYPEPARA: DlBeTraffThsOnHsdpa=D32;
1.3.3.3 Sub-Scenario 3: physical CE limited
Symptom
The downlink physical CE utilization ratio of a NodeB is high and admission failures caused by CE congestion
exist. Consequently, subscribers cannot access the network and the throughput rate per cell is low.
Add CE license or WBBP boards.
Before capacity expansion, you must consider whether the hardware supports expansion of the CE license. If
the physical CEs are insufficient, related boards must be added.
Solution 2: resource group adjustment
Downlink CE resources cannot be shared between boards. If cells are not properly allocated among boards, CEs
on some boards may be limited. In this case, you can adjust the resource group of the cell to solve the CE
limited problem.
To adjust the resource group of a cell, perform the following steps:
Query the configurations of the downlink resource group.
LST DLGROUP: ;
Query the board specifications.
DSP BBPTC: SRN=0;
Query the resource allocation information of the cell.
DSP LOCELLRES:;
If a cell where the CE resource is limited is provided by a board with poor capability, or cell resources are not
allocated evenly among resource groups, you are advised to modify the resource group of the cell.
1.3.3.4 Sub-Scenario 4: Iub-interface admission bandwidth limited
Symptom
The Iub-interface admission bandwidth is limited. Consequently, admission of subscribers fails, the data
transmission requirement of subscribers cannot be satisfied, and the cell throughout rate is low.
Solution 1: GBR adjustment
R99 subscribers are admitted based on the GBR. As the GBR becomes larger, the number of admission CEs also
increases and congestion is more likely to occur. If the GBR is decreased, more subscribers can be admitted and
admission of data transmission subscribers can be ensured.
To modify the GBR, run the following command:
SET UUSERGBR: TrafficClass=INTERACTIVE, DlGBR=D16;
Solution 2: initial bit rate adjustment
When R99 DCCC is enabled, subscribers are admitted based on the initial bit rate. If the initial bit rate is too
high, the number of admission CEs is large. This increases the possibility of congestion and affects the timely
access of subscribers who need to transmit data. Reduction of the initial bit rate allows admission of more
subscribers and increases the throughput rate per cell.
To modify the initial bit rate, run the following command:
SET UFRC: DlBeTraffInitBitrate=D16;
Solution 3: activation factor adjustment
Data transmission of subscribers is not continuous. A lot of accessed subscribers do not transmit data for a long
time, but occupy large admission bandwidth, causing admission failures of other subscribers. If the activation
factor of each service is reduced, the Iub-interface admission threshold decreases, allowing admission of more
subscribers.
You can configure the activation factor based on the service types and adjacent nodes:
The activation factor has a default value which can be queried by running LST TRMFACTOR. You can run ADD
TRMFACTOR to dynamically configure activation factors for different services.
You can configure the same activation factor table for different adjacent nodes by setting the FTI parameter in
ADD ADJMAP.
To configure the activation factor table for adjacent nodes, perform the following steps:
Add the activation factor table.
Figure 2: Activity factor table
Map adjacent nodes to the activation factor table.

Figure 3: Adjacent node activity factor
1.3.3.5 Sub-Scenario 5: Iub-interface physical bandwidth limited
Symptom
The actual Iub-interface physical bandwidth is limited. Consequently, the subscriber rate is low due to the flow
control.
Increase the Iub-interface physical bandwidth. You are advised to calculate the bandwidth to be increased by
using the transmission resource forecast.
1.3.3.6 Sub-Scenario 6: Iub-interface QoS limited
Symptom
Packet loss or delay exists on the Iub interface. Consequently, the throughput rate per subscriber and the
throughput rate per cell are low.
Solution 1: troubleshooting and capacity expansion
If packet loss or delay is caused by the transmission quality.
If packet loss or delay is caused by the limited physical bandwidth, it is recommended that the bandwidth be
increased.
Solution 3: overbooking on ATM transmission
As a response to ATM HUB NodeB, it provides 5 class VP Shaping and flow control and every class NodeB will be
flow shaped and flow control to get the balance and ability of data transmission.
Every class NodeB will be flow shaped on ATM HUB NodeB network.
Overbooking on ATM transmission is used to improve the usage efficiency on ATM transmission scenario.
Backpressure on the interface board
Such fast inner loop backpressure mechanism is implemented in the interface board (AOUa/UOIa/AEUa) and it
works as described below:
The RNC monitors the Buffer Occupancy (BO) status of each physical port and VP or PVC at the Iub transport
network layer user plane continuously.
 If the BO exceeds the congestion threshold (TH2), the system enters congestion state and a congestion
backpressure signal will be generated and sent to radio network layer user plane. Then the RNL UP will
decrease the data sending rate to release the congestion.
 If the BO is lower than the congestion release threshold (TH1), the system enters the normal state and
a congestion release backpressure signal will be generated and sent to the RNL UP. Then the RNL UP
will increase the data sending rate.
If the BO is higher than the discard threshold (TH3), the system enters the extreme congestion state and the
data is discarded at the TNL UP directly.
To enable the overbooking on ATM transmission feature, perform the following step:
Activate the license of the overbooking on ATM transmission feature: ATM IUB overbooking Function=ON
Enable the RLC retransmission rate–based downlink congestion control function: SET UCORRMALGOSWITCH:
DraSwitch=DRA_HSDPA_DL_FLOW_CONTROL_SWITCH-1&DRA_R99_DL_FLOW_CONTROL_SWITCH-1;
Enable the backpressure-based downlink congestion control function: ADD PORTFLOWCTRLPARA: FCINDEX=10,
PORTPROTYPE=ATM; MOD IMAGRP: SRN=1, SN=14, BT=AOUa, IMAGRPN=1, FLOWCTRLSWITCH=ON,
FCINDEX=100; ADD UNILNK: SRN=1, SN=14, UNILNKN=1, FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF; ADD
FRALNK: SRN=1, SN=14, FRALNKN=12, E1T1PN=0, TSBITMAP=TS1-1, FRALNKT=FRAATM,
FLOWCTRLSWITCH=ON, OPSEPFLAG=OFF; ADD ATMLOGICPORT: SRN=1, SN=14, LPNTYPE=Leaf, BT=AOUa,
LPN=0, CARRYT=ATMLOGICPORT, UPPERVP=0, TXBW=512, RXBW=512, FLOWCTRLSWITCH=ON;
Enable the shaping function: ADD ATMLOGICPORT: SRN=1, SN=14, LPNTYPE=Leaf, BT=AOUa, LPN=0,
CARRYT=ATMLOGICPORT, UPPERVP=0, TXBW=512, RXBW=512, FLOWCTRLSWITCH=ON; ADD AAL2PATH:
ANI=0, PATHID=1, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=0, CARRYVPN=0, VPI=0, VCI=0, TXTRFX=0,
RXTRFX=0, AAL2PATHT=HSPA;
Solution 4: overbooking on IP Transmission–backpressure on the interface board
IP Shaping can restrict flow of every NodeB to avoid dropping and retransmitting NodeB user plane packet or
and to improve the ability of transmission.
Fast inner loop backpressure on the interface board
Such fast inner loop backpressure mechanism is implemented in the interface board
(PEUa/FG2a/GOUa/UOIa/POUa) and it works as described below:
The RNC monitors the Buffer Occupancy (BO) status of each physical port and logical port at the Iub transport
network layer user plane continuously.
 If the BO exceeds the congestion threshold (TH2), the system enters congestion state and a congestion
backpressure signal will be generated and sent to radio network layer user plane. Then the RNL UP will
decrease the data sending rate to release the congestion.
 If the BO is lower than the congestion release threshold (TH1), the system enters the normal state and
a congestion release backpressure signal will be generated and sent to the RNL UP. Then the RNL UP
will increase the data sending rate.
 If the BO is higher than the discard threshold (TH3), the system enters the extreme congestion state
and the data is discarded at the TNL UP directly.
Buffer Occupancy
TH3
TH2
TH1
Time
Figure 4: Iub overbooking BO.
From CN
RNL User Plane
① ② ③ ④ ⑤
Iub TNL User Plane
To NodeB
Figure 5: Iub overbooking principal
To enable the overbooking on IP transmission feature, perform the following step:
Activate the license of the overbooking on IP transmission feature: IP IUB overbooking Function=ON
Enable the RLC retransmission rate–based downlink congestion control function: SET UCORRMALGOSWITCH:
DraSwitch=DRA_HSDPA_DL_FLOW_CONTROL_SWITCH-1&DRA_R99_DL_FLOW_CONTROL_SWITCH-1;
Enable the backpressure-based downlink congestion control function: ADD PORTFLOWCTRLPARA: FCINDEX=10,
PORTPROTYPE=IP; ADD PPPLNK: SRN=0, SN=27, BRDTYPE=PEUa, LGCAPPTYPE=IP, PPPLNKN=1, DS1=2,
TSBITMAP=TS1-1, BORROWDEVIP=NO, LOCALIP="5.5.5.5",MASK="255.255.255.0", PEERIP="5.5.5.6",
PPPMUX=Enable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON; ADD MPGRP: SRN=0, SN=27, BRDTYPE=PEUa,
LGCAPPTYPE=IP, MPGRPN=1, MPTYPE=MCPPP, BORROWDEVIP=No, LOCALIP="9.9.9.99",
MASK="255.255.255.0", PEERIP="9.9.9.98", MHF=LONG, PPPMUX=Disable, FLOWCTRLSWITCH=ON,
AUTHTYPE=NO_V, ERRDETECTSW=OFF; ADD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPNTYPE=Leaf, LPN=0,
CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=1000, FLOWCTRLSWITCH=ON;
Enable the IP shaping function: ADD IPLOGICPORT: SRN=0, SN=27, BT=FG2a, LPNTYPE=Leaf, LPN=0,
CARRYT=ETHER, PN=0, RSCMNGMODE=SHARE, BWADJ=OFF, CIR=1000, FLOWCTRLSWITCH=ON; ADD IPPATH:
ANI=0, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=BE, IPADDR="80.1.1.1", PEERIPADDR="10.161.0.1",
PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000, CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=0,
VLANFlAG=DISABLE, PATHCHK=DISABLED;
Solution 5: R99 single service congestion control
Iub rate control is provided for both uplink and downlink R99 best-efforts service.
As the complement of existing flow control functions, This feature effectively prevents the transmission from
packet loss and increases the R99 BE service transmission efficiency.
 The Spare Extension IE in the Iub DCH FP frame is used for taking the statistic of sent and received
frame number, which helps the RNC to detect the packet loss state.
 When the congestion in the uplink is detected, the RNC reduces the uplink rate of the UE by sending
the TRANSPORT FORMAT COMBINATION CONTROL message to the UE.
 When the congestion recovery in the uplink is detected, the RNC stops the TF restriction and raises the
uplink rate of the UE.
 When the congestion in the downlink is detected, the Mac-d reduces the downlink data transmission
rate by TF limitation.
When the congestion recovery in the downlink is detected, the Mac-d stops the TF restriction and raises the
uplink rate of the UE.
To active the license of the R99 single service congestion control feature, run the following command: SET
LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH4=UPLINK_CONTROL_OF_USER-1;
Solution 6: adjustment of the HSDPA flow control mode
During the HSDPA flow control, the Iub-interface bandwidth that needs to be reserved for the MAC-hs queue is
calculated based on the transmission rate of the Uu interface and the buffered data on the NodeB side. In
addition, the Uu-interface transmission rate of the MAC-hs queue is determined by the scheduling algorithm.
For the MAC-hs queue, if the Iub-interface transmission rate is higher than the Uu-interface transmission rate,
data packets are buffered. If the amount of buffered data on the NodeB side is too large, delay or packet loss
may occur. Therefore, the amount of data buffered in each MAC-hs queue on the NodeB side cannot be too
large. In addition, to prevent wasting the Uu-interface resources when no data is transmitted, the amount of
data buffered in each MAC-hs queue on the NodeB side cannot be too small.
The brief flow control procedure is as follows:
The NodeB calculates the amount of data to be buffered in each MAC-hs queue and the average Uu-interface
transmission rate.
The NodeB obtains the buffer time by evaluating the calculation result.
The NodeB adjusts the Iub-interface bandwidth for MAC-hs queues.
Different flow control modes are applicable to different scenarios. In a serious congestion scenario, flow
control may result in a low rate. To ease the low rate problem caused by the transmission quality, you can
disable the flow control function.
Run SET HSDPAFLOWCTRLPARA on the NodeB and select the NodeB HSDPA flow control algorithm by setting
the Flow Control Switch parameter. You are advised to select the adaptive flow control algorithm.
Four NodeB HSDPA flow control algorithms are available:
When Flow Control Switch is set to STATIC_BW_SHAPING, the NodeB does not adjust the bandwidth based on
the delay and packet loss rate of the transmission network. Instead, after subtracting the bandwidth occupied
by R99 services from the configured Iub-interface bandwidth, the NodeB adjusts the Iub bandwidth and
allocates the remaining bandwidth to HSDPA subscribers.
When Flow Control Switch is set to DYNAMIC_BW_SHAPING, the NodeB adjusts the available bandwidth of
HSDPA subscribers based on the delay and packet loss rate on the Iub interface. Based on the radio interface
rate, the NodeB adjusts the Iub-interface bandwidth and allocates the bandwidth to HSDPA subscribers.
When Flow Control Switch is set to NO_BW_SHAPING, the NodeB does not adjust the available bandwidth of
HSDPA subscribers based on the delay and packet loss rate on the Iub interface. The NodeB reports the status
of the radio interface to the RNC and the RNC allocates the bandwidth.
When Flow Control Switch is set to BW_SHAPING_ONOFF_TOGGLE, the port flow control policy of the NodeB is
determined by the congestion detection mechanism. The flow control policy can be DYNAMIC_BW_SHAPING or
NO_BW_SHAPING. This flow control algorithm is recommended.
1.3.3.7 Sub-Scenario 7: code resource limited
Symptom
The code resource utilization ratio is high. The throughput rate is low because the code resources are limited.
Solution 1: power preferred or power/code balancing
In power preferred resource allocation mode, HSDPA services preferentially use the power resource. In
power/code balancing allocation mode, HSDAP performance degradation caused by exhaustion of a single type
of resources can be prevented, and the cell capacity can be improved.
Table 15: MAC HSDPA ressource allocation parameters.
Command NE Parameter Default Value Recommended

Value
SET MACHSPARA NodeB RSCALLOCM N/A CODE_PRI
Solution 3: HSDPA code expansion
A small number of configured HSDPA code licenses may lead to a low HSDPA throughput rate. Therefore, you
can increase the throughput rate per subscriber by configuring more code resources.
Activate the following license to add the HSDPA codes to the NodeB:
LQW9HDCODE01 HSDPA codes 45
It is recommended that 15 HSDPA codes be configured for a cell.
Solution 4: HSDPA dynamic code allocation mode
The HSDPA dynamic code allocation mode can ensure that code resources are allocated to HSDPA subscribers
whenever possible if the code resources are not occupied by R99 services. This can increase the HSDPA
throughput rate.
On the RNC, run the following command to change the code allocation mode to Automatic:
MOD UCELLHSDPA: CellId=100, AllocCodeMode=Automatic, HsPdschMaxCodeNum=15,

HsPdschMinCodeNum=5;
On the NodeB, activate the following license:
LQW9HDPCK01 HSDPA RRM Package1 (per NodeB) 1
Solution 5: Code tree reshuffling–based LDR
In the case of code resource congestion, the code resource LDR is triggered and the code tree reshuffling is
conducted. In this way, some code resources can be spared for subscriber admission or services and the
throughput rate can be increased.
To enable code tree reshuffling–based LDR, perform the following steps:
Activate the cell code resource–based LDR algorithm.
ADD UCELLALGOSWITCH: CellId=100, NBMLdcAlgoSwitch=CELL_CODE_LDR-1;
Set LDR actions.
ADD UCELLLDR: CellId=100, DlLdrFirstAction=CodeAdj;
Solution 7: HSPDA-based code tree reshuffling
When the HSPDA-based code tree reshuffling algorithm is activated, codes occupied by R99 services are
reshuffled in descending order of the code number to release the shared code resources of adjacent HSDPA
subscribers. When AllocCodeMode of HSDPA services is set to Automatic, or the NodeB automatic code
resource allocation algorithm is activated, the released codes can be used by HSDPA services to increase the
HSDPA throughput rate.
Table 16: Code Adjustment for HSDPA switch.
Command NE Parameter Default Recommended

Value Value
MOD UCELLHSDPA RNC CodeAdjForHsdpaSwitch N/A ON
When AllocCodeMode of HSDPA services is set to Automatic, or the NodeB automatic code resource algorithm
is activated, the released codes can be used by HSDPA subscribers. Code tree reshuffling increases the signaling
traffic on the radio interface and the call drop risk.
1.3.3.8 Sub-Scenario 8: NodeB CPU/DSP processor limited
Symptom
The main control or baseband CPU/DSP processor of the NodeB is overloaded. Consequently, subscriber
admission fails, affecting the throughput rate per subscriber and the throughput rate per cell.
Solution 1: version upgrade
Upgrade NodeBs to the latest version to support more powerful CNBAP capability.
Solution 2: adding UTRP boards
Add UTRP boards to improve the CNBAP capability of the main control board.
Solution 3: adding the WBBP boards
Add WBBP boards to improve the CNBAP capability of the baseband boards and provide more DSP processor
resources.
Solution 4: resource group optimization
The CNABP capability of baseband boards can be shared only within the resource group. If the CPU of a
baseband board is overloaded and no more baseband boards are available, you are advised to check whether
multiple resource groups exist. If some resource groups are relatively idle, you can temporarily adjust the
distribution of cells among boards to prevent the CNBAP limitation of baseband boards.
2. UL Capacity improvement
2.1 Capacity-related Definitions
Uplink capacity improvement involves the number of users, R99 per user throughput, HSUPA per user
throughput, cell throughput, number of random access channel (RACH) users, and RACH throughput.
Currently, the uplink admission based on the uplink load RTWP is immature, and RTWP fluctuates greatly as
affected by external interference. Generally, the admission based on the number of equivalent users is used or
the admission algorithm is disabled. The number of equivalent users is usually large; therefore, the possibility
of admission rejection due to the uplink load is quite small. The scenario where the number of uplink users is
limited due to other resources, such as CE and Iub resources, should be analyzed in capacity resource
assessment in network audit to provide expansion or optimization solutions. This scenario is not described in
this document.
With the development of networks and evolution of technologies, the penetration rate of HSUPA users will
continuously increase. The traditional R99 user scheduling is not affected by the radio load, and the rate
depends more on system hardware resources such as CEs. HSUPA scheduling is greatly affected by the radio
load, and a high rate is more prone to be limited by the resource capacity. Factors such as interference, radio
efficiency, device resource, and spectral capacity may affect HSUPA user experience. Therefore, uplink capacity
improvement focuses on the HSUPA throughput and cell throughput and additionally also considers the
features and parameters for R99 load optimization and increase of users.
2.2 Factors Affecting the Uplink Capacity
Generally, the uplink throughput is affected by factors such as the number of users, radio RTWP resource,
NodeB CE, Iub bandwidth, and user behavior.
If the load factor is certain, the maximum cell capacity is limited. With the increase of the number of users,
resources are shared among users, and the average per user throughput is decreased. In addition, WCDMA is a
self-interference system. If the number of users increases, the interference between users increases. As a
result, the user power increases, the uplink load is worsened, and single user throughput and accessibility
decrease.
RTWP is an important factor of HSUPA scheduling. The RTWP load factor determines the maximum uplink cell
capacity. Generally, the larger the uplink load factor is set, the larger the uplink capacity can be provided.
However, if the uplink load is set to a large value, the raise of thermal (RoT) increases, and the uplink coverage
shrinks. According to simulation results, the cell coverage shrinks by 18% every time when the uplink load is
increased by 3 dB. Coverage shrink affects key performance indicators (KPIs) such as accessibility and call drop
rate. Therefore, the uplink load must be set to a proper value with multiple indicators considered
comprehensively.
As the HSUPA feature is introduced, HSUPA users can be provided with a higher uplink rate (HSUPA PHASE II:
5.76 Mbit/s, HSPA+: 11.52 Mbit/s). However, more device resources are consumed, and system resource
congestion may occur. Uplink device resources mainly refer to CE and Iub bandwidth. After the HSUPA feature
is enabled, more CE resources need to be reserved, and a higher uplink bandwidth needs to be configured.
2.3 Uplink Capacity Improvement Scenarios
Uplink capacity improvement involves the improvement in the number of users and the improvement in
throughput and improvement in accessibility, either of which is further classified by radio resource limitation
and device resource limitation.
The uplink accessibility and throughput are greatly affected by radio resources and is also affected by device
resources. In terms of capacity improvement, there is no necessary association between radio resource
limitation and device resource limitation. Therefore, radio resource limitation and device resource limitation
are considered as two independent perspectives for scenario classification. Generally, uplink radio admission is
based on the number of equivalent users; therefore, it is classified into the scenario of device resource
limitation. The scenarios are as follows:
 Radio resource limitation (symptom: cell breakdown)

o System interference
o Target load limitation
o UE power limitation
o Normal
 Device resource limitation (reflected by the ratio of the number of cells in each scenario to the total
number of cells)
o Limitation on the number of equivalent users
o Limitation on the number of HSUPA users
o Admission CE limitation
o Physical CE limitation
o Admission Iub limitation
o Physical Iub limitation
o Iub quality of service (QoS) limitation
o NodeB XPU limitation
2.4 Radio Resource Limitation
2.4.1 Scenario 1 — System Interference
For a cell, either of the following symptoms indicates that internal or external system interference may occur:
 In idle hours (such as early morning), the number of users is small, but the average RTWP is high. That
is, the high RTWP is not caused by actual uplink services.
 In busy hours (when the CS+PS throughput is highest), the number of users is small, and the average
per user throughput is low, but the RTWP is high. That is, the high RTWP is not caused by actual uplink
services.
2.4.1.2 Identification Rules
Rules for identifying external interference
Table 17: Criteria for Interference detection
Scenario Time RTWP Other

External Idle hours > -100 (configurable) Theoretical load < 1 dB
interference
Busy > target load (configurable) Theoretical load < 1 dB

hours
Solution: interference troubleshooting
Check related paragraph for this item.
2.4.1.4 Sub-scenario 2 — Constant Interference
Fault symptom
Trace the RTWP of a cell in real time. If the RTWP is high and relatively constant, constant interference occurs.
Solution 1: automatic background noise update
MML: MOD UCELLCAC
Table 18: Automatic Background Noise adjustment parameters.
Parameter ID Parameter Name

CellId Cell ID
CellEnvType Cell environment type
BackgroundNoise Background noise
BGNSwitch Switch of automatic background noise update
BGNAdjustTimeLen Triggering time length of automatic background noise update
BGNEqUserNumThd Threshold of the number of equivalent users in the case of
automatic background noise update
BgnStartTime Algorithm start time
BgnEndTime Algorithm end time
BgnUpdateThd Triggering threshold of automatic background noise update
BgnAbnormalThd Abnormal background noise threshold
The following configuration is recommended:
MOD UCELLCAC: BGNSwitch=ON, BGNAdjustTimeLen=120, BGNEqUserNumThd=0, BgnStartTime=01&00&00,

BgnEndTime=06&00&00, BgnUpdateThd=5, BgnAbnormalThd=100;
Solution 2: background noise modification
If the automatic background noise update algorithm is not enabled or background noise cannot be
automatically updated, you can modify the background noise value be consistent with the actual background
noise so that the impact of interference on HSUPA is reduced.
Baseline: 61 (corresponding to –106 dB)
MML:
MOD UCELLCAC: BackgroundNoise=xxx;
Here, xxx indicates the RTWP value when there is no user in idle hours. The value can be obtained from the
performance measurement results.
2.4.2 Scenario 2 — Target Load Limitation

RTWP RoT is a key factor that affects HSUPA scheduling. If the RTWP is high, the HSUPA-scheduled rate is
affected, and the user rate is reduced. Possible symptoms of target load limitation are as follows:
 The number of cell users is large. The RTWP of the cell is high continuously. The average RTWP
exceeds the target load. The RTWP is uncontrollable.
 The RTWP is high only when users transmit data. The average RTWP does not exceed the target load.
The RTWP is controllable. However, a large number of UEs report UNHAPPY indications due to
insufficient authorization in the case of radio load limitation.
The preceding symptoms are caused by radio load limitation. You can use the related parameters or features to
improve the spectral efficiency or spectral capacity to improve single user throughput or cell throughput.
Rules for identifying target load limitation
Table 19: Load Limitation criteria.

Target load Busy hours > target load N/A
limitation (configurable)
High R99 load (load > 25%)
High HSUPA load (load > 25%)
High HSDPA accompany load
(load > 20%)
High RRC load (load > 10%)
High RACH load (load > 15%)
Solution 1: carrier expansion
Based on the frequency resources of a customer, adopt dual-carrier or multi-carrier expansion to implement
inter-carrier service sharing to relieve radio congestion.
The key to multi-carrier expansion is the networking policy. For details, see the Multi-carrier Technical Guide.
Solution 2: site expansion
If frequency resources are insufficient, new sites can be deployed in service intensive areas to counteract radio
capacity limitation.
Solution 3: sectors addition solution
If site expansion is infeasible, the sector addition solution can be used to implement sector split to effectively
relieve the spectral capacity bottleneck and improve the radio capacity.
Solution 4: 4-way receive diversity solution
Run the NodeB MML command ADD SEC, set ANTM to 4, and set ANT1CN, ANT1SRN, ANT1N, ANT2CN,
ANT2SRN, ANT2N, ANT3CN, ANT3SRN, ANT3N, ANT4CN, ANT4SRN, and ANT4N.
ADD SEC: STN=0, SECN=0, SECT=LOCAL_SECTOR, ANTM=4, ANT1CN=0, ANT1SRN=4, ANT1N=N0A, ANT2CN=0,
ANT2SRN=4, ANT2N=N0B, ANT3CN=0, ANT3SRN=4, ANT3N=N1A, ANT4CN=0, ANT4SRN=4, ANT4N=N1B;
Run the NodeB MML command ADD ULGROUP and set DEMMODE to DEM_4_CHAN or DEM_ECON_4_CHAN.
ADD ULGROUP: ULGROUPN=0, DEMMODE=DEM_4_CHAN, SNE1=0;
Solution 6: increasing the target load
The HSUPA throughput is related to the target load of the cell. Increasing the target load can improve the cell
capacity. For the cell that encounters spectral limitation, it is recommended that the target load be increased
to 90% to improve single user throughput and cell throughput.
Baseline: The default HSUPA cell target load is 75%.
ADD UCELLHSUPA: MaxTargetUlLoadFactor=90;
Change the target load of the cell to 90%.
If the target load is extra-high, coverage shrink may be caused, affecting the throughput and KPIs of cell edge
users. Therefore, you must consider the capacity and KPIs jointly when enabling this feature.
2.4.2.4 Sub-scenario 1 — High R99 Load
Fault symptom
More than 50% of uplink load is generated by R99 services. In this case, optimization is required for R99
services.
Solution 1: CCPIC
From this release on, the Common Channel Parallel Interference Cancellation (CCPIC) is supported.
CCPIC is a simplified and practical application of MUD technology for base station receivers. It cancels the
uplink control channel and therefore decreases the uplink interference and improves the performance.
In the scenario of an urban macro cell, TU3 channel, and AMR 12.2 kbit/s user with a 50% load, the CCPIC will
bring 11% capacity improvement; in the case of a 75% load, the capacity improvement is 18%.
The control channels are always active and they are a substantial sources of interference especially to those
lower-data-rate and lower-activity services before 3GPP R7.
Because there are known slot formats of different users, the DPCCH pilot symbols of all users are clear to the
receiver. With a high spreading factor, the TPC, TFCI, or FBI bits can be judged accurately. The demodulation
performance of one user can be improved when the DPCCH signals received from the other users are
reconstructed and canceled.
Solution 2: carrier load balancing
In the multi-carrier networking, if load is not balanced between carriers and the uplink load differs a lot, it is
recommended that random camping and load balancing be adopted and that the load balancing triggering
threshold be lowered.
ADD UCELLDRD: LdbDRDSwitchHSDPA=ON, LdbDRDchoice=UserNumber, ReDirBandInd=DependOnNCell;
SET UDRD: LdbDRDSwitchDCH=ON, LdbDRDSwitchHSDPA=ON, LdbDRDOffsetDCH=5, LdbDRDOffsetHSDPA=5;
Solution 3: RTWP-based LDR
If the uplink load of the cell is higher than the uplink LDR triggering threshold for a certain period (600 ms), the
cell is in the basic congestion state, and load-based LDR is triggered. In this case, perform R99 BE rate reduction
to relieve the radio congestion and improve HSUPA user experience.
Enable the LDR based on the uplink radio load.
ADD UCELLALGOSWITCH: NBMLdcAlgoSwitch=UL_UU_LDR-1;
Set the triggering and releasing thresholds.
ADD UCELLLDM: UlLdrTrigThd=55, UlLdrRelThd=45;
Set the LDR action.
ADD UCELLLDR: UlLdrFirstAction=BERateRed;
If radio load congestion occurs, BE service rate reduction is preferred.
When radio load congestion occurs, R99 BE rate reduction can relieve the congestion, improve HSUPA user
experience, and reduce the impact of services on KPIs, but R99 user experience is affected. Therefore, you
must consider R99 and HSUPA users jointly when enabling this feature.
2.4.2.5 Sub-scenario 2 — High HSDPA Accompany Load
Fault symptom
If HSDPA uplink accompany channels contribute a high load ratio to uplink load (for example, 30%), high HSDPA
accompany load occurs.
Solution 1: CQI feedback period optimization
Theoretically, a shorter CQI feedback period means that UEs can feed back channel quality feedback more
timely and higher downlink AMC gain can be obtained. However, frequent channel quality feedback increases
the uplink load factor. According to simulation results, if the CQI feedback period is changed from 4 ms to 2 ms,
the impact on AMC gain is slight, but the impact on the uplink load factor is great. Default CQI feedback period
is 2 ms, which indicates a large optimization space for the uplink load contributed by CQI feedback.
It is recommended that the CQI feedback period be changed from the default 2 ms to 8 ms to reduce the uplink
load contributed by HSDPA accompany channels.
RNC level:
SET UHSDPCCH: CQIFBCK=D8, CQIFBCKFORSHO=D8; //The CQI feedback period is 8 ms.
Cell level:
ADD UCELLHSDPCCH: CELLID=100, CQIFbCk=D8, CQIFbCkforSHO=D8;
Solution 2: activation and deactivation of the secondary carrier based on the traffic volume
This feature can deactivate the secondary carrier of a UE supporting DC-HSDPA when the traffic volume of DC-
HSDPA services to be processed by the UE is low. When the traffic volume rises, the secondary carrier can then
be activated.
Deactivating the secondary carrier of a UE can reduce the power consumption of the UE and the transmit
power of the UE on the HS-DPCCH, thereby lightening the uplink load of the cell.
The secondary carrier of the UE can be activated when the traffic volume rises, thereby increasing the downlink
throughput of the UE.
The NodeB decides whether to deactivate the secondary carrier of a UE based on the amount of data to be
transmitted by the UE and the throughput of the UE. Given a small amount of data and low throughput, the
NodeB deactivates the secondary carrier and sends an HS-SCCH order to notify the UE of the deactivation.
When the amount of data becomes large or the throughput becomes high, the NodeB activates the secondary
carrier and sends an HS-SCCH order to notify the UE of the activation.
Activate the license.
On the NodeB, run DSP LICENSE to check license activation.
LQW9DEASC01 //activation and deactivation of the secondary carrier (per cell)
Enable the feature.
Run the NodeB MML command SET MACHSPARA to set the MAC-HS scheduling parameter of the cell. Set
SECCELLACTDEASW to ON.
SET MACHSPARA: SECCELLACTDEASW=ON;
2.4.2.6 Sub-scenario 3 — High RRC Load
Fault symptom
If the uplink load consumed by RRC is high (for example 30%), optimization is required.
Solution 1: optimization of the periodic location or routing update timer
Increase the duration of the periodic location update timer to decrease the number of RRC registration
attempts.
MOD UCNDOMAIN: CNDomainId=CS_DOMAIN, T3212=40;
A small value of this parameter causes a large number of RRC attempts. A large value of this parameter causes
non-timely network paging, which affects user experience. It is recommended that you determine the value
with the customer.
Solution 2: signaling storm
Lengthen the packet switched (PS) deactivation time and enable cell PCH, R8FD and EFD to reduce RRC
attempts caused by service attempts.
2.4.2.7 Sub-scenario 4 — High HSUPA Load
Fault symptom
HSUPA services contribute a lot to RTWP load. If HSUPA services contribute more than 50% to RTWP load,
optimize the HSUPA service load.
Solution 1: HSUPA data channel power adaptation
The power offset of E-DCH Dedicated Physical Data Control Channel (E-DPDCH) and DPCCH determines the
Signal to Interference Ratio (SIR) of the DPCCH in the uplink.
This feature enables the RNC to configure an optimal power offset for HSUPA 10 ms TTI UEs with a small target
number of retransmissions based on the rate of the UEs.
If the data rate is lower than 300 kbit/s, a large power offset of E-DPDCH and DPCCH can be configured.
Configuring a larger offset decreases power on the DPCCH and reduces power consumption on the uplink
control channel. In this way, more power can be used to transmit user data in the uplink, thereby increasing
capacity of HSUPA cells.
If the data rate is higher than 300 kbit/s, a small power offset of E-DPDCH and DPCCH can be configured.
Configuring a smaller offset increases power on the DPCCH, thereby meeting power requirements in cases of
multipath searching and channel assessment and improving performance of HSUPA services.
This feature improves HSUPA capacity of a cell serving a large number of HSUPA 10 ms TTI UEs without
increasing its received total wideband power (RTWP). This capacity improvement is indicated in increased
average cell throughput and the increased number of UEs.
The parameter PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH is added to control whether this feature is

enabled.
The parameter Punishment Timer for HSUPA Adaptive Retrans is added to determine the interval at which the
target number of retransmissions is adjusted by using the feature WRFD-010641 HSUPA Adaptive Transmission.
This parameter is valid only when the algorithm of this feature Adaptive Configuration of Traffic Channel Power
Offset for HSUPA is enabled.
Three parameters are added to set Hybrid Automatic Repeat Request Power Offset (HARQ PO) for UEs at
different rates: HARQ PO for Large Retransmission, HARQ PO for Small Retrans at Low Speed, and HARQ PO for
Small Retrans at High Speed.
After this feature is enabled, the RNC configures an optimal power offset for 10 ms TTI UEs in the following
ways:
Based on the retransmission state and rate of the UEs during service establishment, modification, or
reconfiguration.
Dynamically based on the real-time rate of the UEs in the small retransmission state if the peak rate of the UEs
exceeds the high-speed service rate threshold (300 kbit/s).
Based on the retransmission state and rate of the UEs after the target number of retransmissions is adjusted
using the feature WRFD-010641 HSUPA Adaptive Transmission.
After this feature is enabled, PO optimization cannot be enabled. In addition, in the scenario where adaptive
retransmission is enabled and takes effect, this feature brings little gain; therefore, disable the feature in this
scenario.
Enable the algorithm of RNC-level HSUPA data channel power offset adaptation.
SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH-1;
Activate the license of this feature.
SET LICENSE: SETOBJECT=UMTS, ISPRIMARYPLMN=YES, FUNCTIONSWITCH5=ADAPTIVE_CONF_TC_PO_HSUPA-

1;
Set the punitive timer of the HSUPA adaptive retransmission algorithm.
SET UCOIFTIMER: AdapRetranPunTimer=10;
Set the power offset parameters for typical services.
MOD UTYPRABHSUPAPC: RabIndex=48, SubflowIndex=0, TrchType=TRCH_EDCH_10MS, Ul16QamInd=FALSE,

UlL2EnhanceInd=FALSE, EdPwrInterpolationInd=FALSE, UlEcBoostingInd=FALSE, HarqPOLargeRetr=0,
HarqPOLitRetrLRate=4, HarqPOLitRetrHRate=4;
Solution 2: PO optimization
Under the current HSUPA power distribution, if the rate is certain, the load consumed by HSUPA services is
higher than that consumed by R99 services. Optimize the HSUPA PO to reduce the uplink load and improve the
throughput. Increase the reference PO to reduce the DPCCH SIR work level. This reduces the load overhead of
uplink control channels and increases the HSUPA cell throughput or maximum number of HSUPA users in the
multi-user low-speed scenario. Use this solution if the current version does not support solution 1.
Optimize PO in the following aspects (the following values are recommended values):
 Reference PO optimization: increased by 4 dB

 Optimization of the target DPCCH SIR value: decreased by 4 dB
 step 3 step threshold: increased by 4 dB
Use scripts to modify the PO of typical HSUPA services.
After PO optimization, the DPCCH SIR is reduced. The channel estimation for high-speed users may be affected,
which may affect the peak rate. PO optimization gain is related to the network service model. Detailed gain
information requires more network data.
Solution 3: HSUPA IC
HSUPA UL Interference Cancellation (IC) is performed to cancel the interference caused by the UL high rate
EDPDCH data to improve the demodulation signal-to-noise ratio (SNR) and to increase the UL system capacity
of the network.
The introduction of the IC technology significantly improves the UL capacity of the UMTS. In certain scenarios,
the gain of the IC technology is significant. For example, if the system needs to support a small number of
HSUPA users with high throughput and a large number of HSUPA users with low throughput, the IC is required
to cancel the uplink interference brought by HSUPA users with high throughput. Without the IC technology, the
high UL interference may be generated from the high speed HSUPA users. In such a case, if the rate of the
original high rate HSUPA users must be guaranteed, the number of low speed users (such as VoIP users) must
be limited. Otherwise, the original high speed HSUPA users may be affected and the speed of services may
decrease to the minimum.
The IC technology supports different categories of HSUPA users, including UEs of categories 1 to 7. The
principle of the IC technology is that the receiver of the NodeB demodulates the HSUPA data on the UL
EDPDCH and reconstructs the baseband data based on the demodulated data and received baseband data. The
NodeB then demodulates the reconstructed baseband data. For the reconstructed baseband data, the
interference from the reconstructed EDPDCH data is eliminated and the colored noise in the cell caused by the
self-interference feature of the UMTS is reduced. Therefore, the SNR of the reconstructed data is improved.
Run DSP LICENSE to check whether the license is activated.
LQW9UIC01 //IC function (per cell)
Enable the feature.
ADD LOCELL: LOCELL=xxx, SECT=REMOTE_SECTOR, IC_MODE=TRUE;
Solution 4: dual thresholds of IC
This feature is applicable to cells enabled with the HSUPA UL Interference Cancellation feature. With this
feature, scheduling is based on received total wideband power (RTWP) thresholds before and after
interference cancellation (IC). This can increase the HSUPA throughput of the cell.
This feature further increases the HSUPA throughput of cells enabled with the HSUPA UL Interference
Cancellation feature by around 10%.
This feature dynamically raises the RTWP target value of the cell before IC while keeping it always higher than
the RTWP of the cell after IC. In this manner, the HSUPA throughput of the cell can be increased. To minimize
the impact on neighboring cells, this feature adopts a predefined upper threshold for the RTWP target value of
the cell before IC.
Activate the licenses of IC and IC dual-threshold scheduling.
Enable HSUPA IC for the local cell.
ADD LOCELL: LOCELL=xxx, STN=0, SECN=0, SECT=REMOTE_SECTOR, ULGROUPNO=1, SRN1=60, ULFREQ=9612,

DLFREQ=10562, MXPWR=430, HISPM=FALSE, RMTCM=FALSE, VAM=FALSE, IC_MODE=TRUE;
Enable dual-threshold scheduling.
SET MACEPARA: LOCELL=***, SCHEDULEPARA=YES, MAXDELTAOFTARGETROT=2, EAGCHPCPARA=NO,
SERGCHPCPARA=NO, NSERGCHPCPARA=NO, SEHICHPCPARA=NO, NSEHICHPCPARA=NO;
MAXDELTAOFTARGETROT is the dual-threshold switch and also indicates the difference between the RoT
thresholds of the delay antenna and the real-time antenna (the step is 0.5).
If MAXDELTAOFTARGETROT is set to 0, single-threshold scheduling is used.
If MAXDELTAOFTARGETROT is not set to 0, dual-threshold scheduling is used.
If the RoT is extra-high, network KPIs are probably affected. Therefore, it is recommended to set
MAXDELTAOFTARGETROT to 2. That is, the difference between the two thresholds is 1 dB.
Solution 5: HSUPA adaptive retransmission
With comprehensive considerations of cell uplink power load, CE resources, and limited uplink coverage, this
feature enables the adaptive adjustment of the number of target uplink retransmissions to improve the
throughput per user and cell uplink capacity.
In a limited uplink coverage scenario, a user's uplink cell edge throughput can be increased, in order to enhance
user experience. According to simulation results, single user throughput has been show to increase by 15%-
60%.
In a scenario where the cell uplink power load is limited, increasing the retransmission number can improve cell
throughput and cell uplink capacity. Simulation results have shown an increase of 53% in cell throughput under
multi-user scenarios.
This feature is only effective in BE traffic. If a user, only has BE traffic (with the exception of SRB) on E-DCH,
then dynamic adjustment of the target retransmission number is allowed. Adjusting the users target
retransmission number to a relatively smaller value is permitted when the uplink power of all the cells
belonging to the serving RLS is smaller than a certain threshold, the UE uplink power is not limited, and uplink
CEs are limited. When the uplink power of any cell belonging to the serving RLS experiences congestion or UE's
uplink power is limited, then setting the users target retransmission number to a relatively larger value is
permitted, as long as the uplink CE resources are sufficient.
Activate the RNC license.
Run DSP LICUSAGE to check whether the license is activated.
LQW1HSUPA09 HSUPA Adaptive Retransmission (per Mbit/s) 6.40 0
Enable the algorithm.
Run the RNC MML command SET URRCTRLSWITCH and set PROCESSSWITCH to
NODEB_PRIVATE_INTERFACE_SWITCH-1 to send private interface data of the NodeB to the NodeB by means of
Iub protocol messages.
SET URRCTRLSWITCH: PROCESSSWITCH=NODEB_PRIVATE_INTERFACE_SWITCH-1;
Run the RNC MML command SET UCORRMALGOSWITCH and set PcSwitch to
PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-1 to enable HSUPA adaptive retransmission.
SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_HARQNUM_AUTO_ADJUST_SWITCH-1;
Run the NodeB MML command SET ADPRETRANSSWTCH and set SWITCH to OPEN to enable HSUPA adaptive
retransmission on the NodeB.
SET ADPRETRANSSWTCH: SWITCH=OPEN;
Solution 6: RTWP-based 2 ms/10 ms switching
The operator can flexibly adjust the TTI for the Best Effort (BE) service that is carried over HSUPA according to
the load over the Uu interface by configuring algorithm switch and parameters. In this manner, the network
load can be reduced and the throughput can be increased while differentiated services are provided to UEs of
different priorities.
The TTI for the BE services over HSUPA can be adjusted from 2 ms to 10 ms when the load capability is limited
on the Uu interface and the throughput is low at layer 2. In this manner, differentiated services can be provided
for the UEs of different priorities (Gold, Silver, and Copper) without loosing equality, and UEs of higher
priorities can be provided with better services.
When the throughput is high, the TTI for the BE services over HSUPA can be adjusted from 10 ms to 2 ms. In
this manner, the throughput can be increased.
The DRA_BASE_RES_BE_TTI_RECFG_SWITCH parameter is added to control whether the algorithm for dynamic
TTI adjustment for the BE service based on equality and differentiation takes effect.
The DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH parameter is added to control whether the algorithm for

dynamic TTI adjustment for the BE service based on equality and differentiation can be implemented on the UE
that is enabled with UL layer 2 enhancement.
The Highest User Priority Guarantee Option parameter is added to control on UEs of which priorities the
adjustment of TTI from 2 ms to 10 ms can be implemented. The adjustment of TTI from 10 ms to 2 ms,
however, is not controlled by this parameter.
If the algorithm for dynamic TTI adjustment for the BE service based on equality and differentiation takes
effect:
The RNC triggers the adjustment of TTI from 2 ms to 10 ms when the load capability is limited on the Uu
interface and the throughput is low at layer 2.
The RNC triggers the adjustment of TTI from 2 ms to 10 ms when the throughput is high.
This algorithm better ensures fairness between 2 ms TTI users and 10 ms TTI users, optimizes the uplink load,
and improves user experience. It is recommended that the 2 ms periodic attempt switch be disabled to prevent
frequent 2 ms/10 ms ping-pong switching. If the HSUPA DCCC algorithm takes effect, the 2 ms TTI switching
becomes invalid automatically. Therefore, you must ensure that the HSUPA DCCC algorithm is disabled.
Enable the feature.
SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_RES_BE_TTI_RECFG_SWITCH-1;
If the algorithm needs to be configured based on user priorities (gold, silver, and bronze), you can run the
following MML command on the RNC and set PriorityOpt.
For example, set PriorityOpt to Gold.
SET UEDCHTTIRECFG: PriorityOpt=Gold, ResourceOption=RTWP-1;
 If PriorityOpt is set to Gold, this algorithm is valid for gold, silver, and bronze subscribers.
 If PriorityOpt is set to Silver, this algorithm is valid for silver and bronze subscribers.
 If PriorityOpt is set to Bronze, this algorithm is valid only for bronze subscribers.
 Disable the 2 ms periodic attempt switch: SET UFRC: RetryCapability=TTI_2MS-0;
Solution 7: uplink layer 2 enhancement
With the introduction of the uplink layer 2 enhancements, the uplink RLC supports flexible PDU and the MAC-
i/is entity is introduced in the MAC layer. The main difference between the MAC-i/is and the MAC-es/s is that
the former supports data segmentation and reassembling. The MAC-is/i can choose a suitable PDU on the basis
of air interface quality, improving data transmission efficiency.
The peak data rate of a single user is increased, and the uplink throughput of the weak-coverage cell is
improved.
The MAC-i/is entity is introduced in the uplink layer 2 enhancement and the NodeB implements the functions
of the MAC-I entity.
Enable the feature.
Enable uplink layer 2 enhancement on the RNC.
ADD UCELLALGOSWITCH: HspaPlusSwitch=UL_L2ENHANCED-1;
Enable uplink layer 2 enhancement on the NodeB.
ADD LOCELL: LOCELL=xxx, UL_L2PLUS=TRUE;
Set the parameters.
Set the maximum and minimum PDUs for RLC layer 2 enhancement.
SET UFRC: RlcPduMaxSizeForUlL2Enhance=402, RlcPduMinSizeForUlL2Enhance=4;
Solution 8: uplink frequency domain equivalent (FDE)
With the HSUPA uplink frequency domain balancing feature, the NodeB uplink receiver balances the spectrum
in the frequency domain of the HSUPA E-DPDCH and reduces the inter-path interference of the E-DPDCH. In
this way, the Signal Noise Ratio (S/N) of the E-DPDCH increases, the uplink system capacity of the HSUPA
network is improved, and the user rate on multi-path scenario increases.
The uplink inter-path interference of HSUPA users is reduced, helping to enhance a higher peak data rate for
HSUPA users.
The NodeB uplink receiver balances the spectrum in the frequency domain of the HSUPA E-DPDCH and reduces
the inter-path interference of the E-DPDCH.
Enable the feature.
Enable FDE on the NodeB.
ADD LOCELL: LOCELL=1, FDE_MODE=TRUE;
Solution 9: uplink 16 quadrature amplitude modulation (16QAM)
The UE category 7 is introduced in 3GPP R7. The UE of this category supports 16QAM and reaches 11.5 Mbit/s
in the uplink.
The uplink system capacity of the HSUPA network is improved, and HSUPA users (UE category 7) reach higher
peak data rate.
The processing of the E-DCH using 16QAM at the physical layer is supported, and scheduling of UE category 7 is
supported.
Enable the single user rate of 11.5 Mbit/s. on the RNC
Enable the feature.
Enable RNC-level uplink 16QAM.
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSUPA_16QAM_SWITCH-1;
Enable cell-level uplink 16QAM or layer 2 enhancement.
MOD UCELLALGOSWITCH: CellId=xxx, HspaPlusSwitch=UL_16QAM-1&UL_L2ENHANCED-1;
Enable SRB over EDCH.
SET UFRCCHLTYPEPARA: SrbChlType=HSUPA, SrbChlTypeRrcEffectFlag=FALSE;
Enable FDE on the NodeB.
ADD LOCELL: LOCELL=1, FDE_MODE=TRUE;
Enable 16QAM on the NodeB.
ADD LOCELL: LOCELL=1, UL_16QAM=TRUE;
Solution 10: E-DPCCH boosting
The E-DPCCH boosting technique is introduced in 3GPP Release 7. This technique is used in high-speed data
transmission of HSUPA UEs. It rapidly increases transmit power of the E-DPCCH, which is used for channel
estimation. As a result, accuracy of channel estimation is increased and high-speed data transmission of UEs is
guaranteed.
Performance of high-speed uplink data transmission is improved. Uplink peak throughput and cell uplink
throughput are increased.
Performance improvement is more obvious when 16QAM is used during high-speed uplink data transmission.
Therefore, the E-DPCCH boosting technique is more necessary in this case where more accurate channel
estimation is required.
The NodeB uses the E-DPCCH with higher transmit power for channel estimation during high-speed uplink data
transmission. In this way, good demodulation performance is guaranteed and therefore high uplink throughput
is achieved.
Enable the feature.
Enable the feature on the RNC.
SET UCORRMALGOSWITCH: CfgSwitch= CFG_EDPCCH_BOOSTING_SWITCH-1;
MOD UCELLALGOSWITCH: CellId=xxx, HspaPlusSwitch= EDPCCH_BOOSTING-1;
SET UFRC: RetryCapability=EDPCCH_BOOSTING-1;
Enable the feature on the NodeB.
MOD LOCELL: LOCELL=xxx, SECT=REMOTE_SECTOR, Boosting=TRUE;
Note: In the uplink, the single user rate can reach 11.5 Mbit/s only when 16QAM, FDE, and E-DPCCH boosting
are all enabled.
Solution 11: CPC DTX
The discontinuous transmission (DTX) and the discontinuous reception (DRX) are the key features of the CPC.
The DTX is used in the uplink and the DRX in the downlink.
When the DTX is adopted, the UE automatically performs discontinuous transmission on the DPCCH according
to a certain scheme when the transmission does not take place on the uplink EDCH or HS-DPCCH. The UL
DPCCH DTX scheme, configured by SRNC, adheres to the following principles: The transmission on DPCCH must
be minimized and the uplink between the NodeB and the UE must be synchronized. The DTX reduces the noises
and the redundant transmission on the DPCCH.
When the DRX is adopted, the UE receives data from the HS-SCCH according to the transmission mode
configured by the RNC. In this case, the UE does not need to detect the HS-SCCH when no data is transmitted.
The DTX and DRX enable the user to be always on, expand the system capacity, and reduce the power
consumption of the UE.
First, the RNC acquires the information on whether the UE and the cell support the DTX and DRX. Then, if the
RNC determines that the DTX and DRX are applicable, it sends the information about the DTX and DRX to the
NodeB or the DRNC over the Iub or Iur interface. After that, the RNC configures the DTX and DRX on the UE
through the signaling on the Uu interface.
To apply the DTX and DRX, you should activate the license, enable the relevant algorithm, and enable the cell
to support the DTX and DRX.
LQW1CPCDTR01 CPC-DTX / DRX (per Mbit/s)
Enable the feature.
Run the BSC6900 MML command MOD UCELLALGOSWITCH and set HspaPlusSwitch to DTX_DRX-1.
MOD UCELLALGOSWITCH: CellId=0, HspaPlusSwitch=DTX_DRX-1;
Run the BSC6900 MML command SET UCORRMALGOSWITCH and set CfgSwitch to
CFG_HSPA_DTX_DRX_SWITCH-1.
SET UCORRMALGOSWITCH: CfgSwitch=CFG_HSPA_DTX_DRX_SWITCH-1;
Run the BSC6900 MML command SET UFRCCHLTYPEPARA and set SrbChlType to HSPA.
SET UFRCCHLTYPEPARA: SrbChlType=HSPA;
2.4.2.8 Sub-scenario 5 — High RACH Load
Fault symptom
If RACH channels contribute a lot to the uplink load, you need to consider RACH load optimization.
Solution 1: RACH parameter optimization
Reduce the sharp impact of preamble open-loop power control on uplink RTWP in initial RACH access. In a cell
with dense RACH access (several thousand access requests per hour), the RTWP can be significantly reduced.
The following configuration is recommended:
MOD UPRACHUUPARAS: CellId=xxx, PhyChId=4, Constantvalue=-30, PowerRampStep=1,

PreambleRetransMax=40;
Solution 2: optimization of RACH-caused sharp increase in the RTWP
The Received Total Wideband Power (RTWP) may increase sharply if the NodeB admits UEs that have a high
transmit power.
When cell load is heavy, the preambles of the UEs that have a high transmit power lead to a sharp increase in
the RTWP.
The RTWP increases sharply.
Solution 3: expansion
Carrier expansion, site expansion, and sector addition solution can be used.
2.4.3 Scenario 3 — UE Power Limitation

A limitation on the uplink UE transmit power limits data transmission. If mass scheduling limitation is caused by
power limitation in an HSUPA cell, the possible cause of the low rate is uplink UE power limitation.
Rules for identifying UE coverage limitation
Table 20: Coverage limitation criteria.

UE coverage Busy hours RTWP < High ratio (for example, > 30%) of
limitation Target load users that encounter power limitation
Solution 1: coverage improvement
This feature improves coverage of HSUPA services at the HSUPA cell edge. The feature is based on the
enhanced HSUPA power scaling technique introduced in 3GPP Release 8.
This feature improves coverage performance at the HSUPA cell edge for BE services and voice.
The emulation results show that the coverage of BE services can be increased by about 20% and the coverage
of voice services can be increased by about 7%.
When a UE detects that transmit power is limited, the UE enters the power scaling mode. In this mode, the
transmit power on uplink physical channels is reduced proportionately to improve coverage performance.
In the traditional power scaling technique, the power offset of E-DPDCH relative to DPCCH is not the most
appropriate value, and therefore scaling mode offers only limited gains.
In the enhanced power scaling technique, the network sends the optimized transport block size and the power
offset of E-DPDCH relative to DPCCH to the UE.
The UE uses these optimized settings when its power is limited at the cell edge. In contrast to the traditional
power scaling technique, the enhanced technique allows for more appropriate transport block size and E-
DPDCH power offset, improving coverage performance at the HSUPA cell edge.
This feature is controlled by license.
Run the following MML command to enable the algorithm of HSUPA coverage improvement in the case of UE
power limitation:
SET UCORRMALGOSWITCH: PcSwitch=PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH.
The parameter that controls this feature is the minimum E-DPDCH gain factor BetaEdMin. The parameter can
be set to a value larger than 8/15.
ADD/MOD UTYPRABHSUPAPC: BetaEdMin=4.
Solution 4: coverage-based E2D
After HSUPA is activated in a cell by running the ACT CELLHSUPA command, the call drop rate of PS BE services
at the cell edge increases.
The coverage area of an HSUPA cell is smaller than that of an R99 cell. Therefore, after HSUPA is enabled in a
cell, the signal strength at the cell edge decreases and the call drop rate of PS BE services at the cell edge
increases.
The call drop rate of PS BE services at the cell edge increases.
Table 21: Coverage based E2D transition parameters.
Parameter ID NE Description
NbmInnerResvRara2 RNC Event 4B Threshold, unit:10 kbit/s, step: 10 kbit/s
BeThd6A1 RNC Event 6A1/6B1/6A2/6B2 Threshold for E-DCH To
DCH, detailed as Appendix
BeThd6B1
BeThd6A2
BeThd6B2
BETRIGTIME6A1 RNC The lasting time for triggering Event 6A1/6B1/6A2/6B2
for DCH to E-DCH, detailed as Appendix. Unit: ms
BETRIGTIME6B1
BETRIGTIME6A2
BETRIGTIME6B2
ResvervedU8Para0 RNC Event6A/6B Threshold for DCH To E-DCH, detailed as
Appendix
ResvervedU8Para1
ULBETRIGTIMER6A2 RNC The lasting time for triggering Event 6A/6B for DCH to
E-DCH, detailed as Appendix. Unit: ms
ULBETRIGTIMER6B2
ReservedSwitch0 RNC The Switch of EDCH to DCH
ReservedU32Para0 RNC The EcN0 threshold, actual Value=(ReservedU32Para0-
49)/2 dB
Run MML commands.
Event 4B Threshold
SET UNBMINNERPAPA: NbmInnerResvPara2=2;
Event6A1/6B1/6A2/6B2 Threshold for E-DCH To DCH
SET UEDCHTTIRECFG: BeThd6A1=4, BeThd6B1=4, BeThd6A2=5, BeThd6B2=5, BETRIGTIME6A1=D1280,

BETRIGTIME6B1=D640, BETRIGTIME6A2=D1280, BETRIGTIME6B2=D640;
Event6A/6B Threshold for DCH To E-DCH
SET UCORRMALGOSWITCH: ResvervedU8Para0=9, ResvervedU8Para1=10;
SET UQUALITYMEAS: ULBETRIGTIMER6B2=D5000, ULBETRIGTIMER6A2=D1280;
E2D Switch in Access State
SET UCORRMALGOSWITCH: ResvervedSwitch0=RESERVED_SWITCH_0_BIT5-1;
E2D Switch in Connection State
SET UCORRMALGOSWITCH: ResvervedSwitch0=RESERVED_SWITCH_0_BIT7-1;
The EcN0 threshold
SET UCORRMALGOSWITCH: ReservedU32Para0=25;
Solution 5: coverage-based 2 ms/10 ms switching
In the case of the HSUPA best effort (BE) services, the related algorithm switches and parameters can be
properly set so that the Transmission Time Interval (TTI) for the UEs at the edge of a cell can be changed to 10
ms to ensure the network coverage whereas the TTI for the UEs at the center of the cell can be changed to 2
ms to increase the throughput.
If the transmit power of a UE is limited and the throughput is low, the TTI for the HSUPA-based BE services can
be adjusted from 2 ms to 10 ms to ensure the quality of service (QoS) and to prevent call drops.
If the transmit power of the UE is not limited and the throughput is high, the TTI for the HSUPA BE services can
be adjusted from 10 ms to 2 ms to increase the throughput.
 The DRA_BASE_COVER_BE_TTI_RECFG_SWITCH parameter is added to control whether the algorithm

for dynamic TTI adjustment for BE services based on coverage takes effect.
 The DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH parameter is added to control whether the algorithm
for dynamic TTI adjustment for BE services based on coverage can be implemented on the UE that is
enabled with UL layer 2 enhancement.
 If the algorithm for dynamic TTI adjustment for BE services based on coverage takes effect, then
 The RNC triggers the adjustment of TTI from 2 ms to 10 ms when the transmit power of a UE is limited
and the throughput is low.
The RNC triggers the adjustment of TTI from 10 ms to 2 ms when the transmit power of a UE is not limited and
the throughput is high.
Activate the license on the RNC.
Run DSP LICUSAGE to check whether the license is activated.
LQW1THOBC01 TTI Switch for BE Services Based on Coverage (per Mbit/s) 6.40 0
Enable the algorithm.
Run the MML command SET UCORRMALGOSWITCH and set DraSwitch to

DRA_BASE_COVER_BE_TTI_RECFG_SWITCH-1 to enable the algorithm of coverage-based dynamic TTI
adjustment for BE services.
SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_RECFG_SWITCH-1;
Optional: If users require this feature after uplink layer 2 enhancement is used, run the MML command SET
UCORRMALGOSWITCH and set DraSwitch to DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH-1.
SET UCORRMALGOSWITCH: DraSwitch=DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH-1;
Parameter configuration
6A/6B power threshold:
SET UEDCHTTIRECFG: BeThd6A1=3, BeThd6B1=3, BeThd6A2=4, BeThd6B2=4.
4A/4B rate threshold:
SET UEDCHTTIRECFG: UpRatioFor2msTo10msBaseRtwp=28, RatioFor10msTo2ms=83;
2.4.4 Scenario 4 — Normal Cell

If the MeanRTWP of a cell is lower than the target load and the current scheduling meets the requirements of
HSUPA users for data transmission (that is, the UnHAPPY ratio is low), radio limitation does not occur, and the
cell is normal.
Rules for identifying normal cells
Table 22: Normal cell criteria.

Normal cell Busy hours RTWP < Target load
2.4.4.3 Sub-scenario 1 — R99 Cell
Fault symptom
The cell load does not reach the target load and the HSUPA function is not activated in the cell. The uplink load
that the cell can endure is low, the capacity of the cell is low, and the user rate is low.
Solution 1: HSUPA 10 ms
The HSUPA 10 ms feature employs technologies such as fast NodeB scheduling, HARQ, and Iub macro diversity
combination to improve single user throughput and cell throughput. After this feature is used, the transmission
delay is reduced, and the maximum uplink rate for a single user is 1.92 Mbit/s.
Run DSP LICENSE to check whether the license is activated on the NodeB.
LQW9HSUPA01 //HSUPA function (per NodeB)
Run MML commands.
Run the BSC6900 MML command ADD UCELLHSUPA to add the HSUPA function to a cell.
ADD UCELLHSUPA: CellId=xxx;
Run the BSC6900 MML command ACT UCELLHSUPA to activate the HSUPA function for the cell.
ACT UCELLHSUPA: CellId=xxx;
Solution 2: HSUPA 2 ms
Run DSP LICENSE to check whether the 2 ms TTI license is activated on the NodeB.
LQW9HU2MS01 //HSUPA 2 ms TTI function (per NodeB)
Run DSP LICUSAGE to check whether the RNC supports 5.74 Mbit/s.
LQW1HSUPA04 HSUPA 5.74 Mbit/s per User (per Mbit/s) 6.40 0
LQW1HSUPA06 SRB over HSUPA (per Mbit/s) 6.40 0
Run MML commands.
On the RNC, run the MML command SET UCORRMALGOSWITCH and set MapSwitch to
MAP_HSUPA_TTI_2MS_SWITCH-1.
SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-1;
On the RNC, run the MML command SET UFRC and set StreamHsupa2msTtiRateThs and
BeHsupa2msTtiRateThs based on network planning.
SET UFRC: StreamHsupa2msTtiRateThs=D64, BeHsupa2msTtiRateThs=D64;
On the RNC, run the MML command SET UFRCCHLTYPEPARA and set SrbChlType to HSPA.
SET UFRCCHLTYPEPARA: SrbChlType=HSPA;
2.4.4.4 Sub-scenario 2 — HSUPA Cell
Fault symptom
HSUPA has been activated in a cell to provide higher per user throughput and cell throughput, and additional
load resources are available. Some features can be used to improve user experience.
Solution 1: TPE
The Uplink TPE feature helps accelerate the slow start and recovery of uplink data transmission through the
split ACK technique. In this way, the impact of packet loss on the uplink TCP data transmission is reduced.
The slow start and recovery of uplink packet transmission at the UE is accelerated.
The performance of uplink TCP data transmission is improved, and therefore the user experience is also
improved.
The TPE feature processes TCP/IP packets with the following technologies:
 Uplink TCP packet sorting.

 Downlink split ACK for accelerating slow start and packet
 transmission at the UE.
This feature is controlled by license and switch.
MML
Table 23: TPE Switch
Parameter NE MML Description

ID
TpeSwitch BSC6900 SET Meaning: TCP Accelerator function switch. 1)
UDPUCFGDATA TPE_DOWNLINK_SWITCH: When the switch is on, the
(Optional) Downlink TCP Accelerator function is supported. 2)
TPE_UPLINK_SWITCH: When the switch is on, the Uplink
TCP Accelerator function is supported. GUI Value Range:
TPE_DOWNLINK_SWITCH, TPE_UPLINK_SWITCH Actual
Value Range: TPE_DOWNLINK_SWITCH,
TPE_UPLINK_SWITCH Unit: None Default Value:
TPE_DOWNLINK_SWITCH: OFF
TPE_UPLINK_SWITCH: OFF
Solution 2: uplink CELL_FACH enhancement
This feature is introduced in 3GPP Release 8. It adopts a common E-DCH for uplink transmission in the
CELL_FACH state to increase the uplink peak data rate.
A UE that supports this feature can use HSUPA to carry its signaling and data. This increases uplink data rates,
reduces service setup delay and state transition delay, and improves "always on" experience and service
quality.
If a UE accesses the network through an E-RACH, a common E-DCH is set up for uplink data transmission.
LQW1EFACH01 Enhanced CELL_FACH (per Mbit/s)
Enable the feature.
Run the BSC6900 MML command ADD UERACHBASIC and set CommonEdchTTISelect.
ADD UERACHBASIC: CellId=xxx, CommonEdchTTISelect=TTI_10MS;
Run the BSC6900 MML command ADD UERACHASC and add information about the available resources of the
access service type for uplink CELL_FACH enhancement.
ADD UERACHASC: CellId=xxx;
Run the BSC6900 MML command ADD UERACHACTOASCMAP and add the AC-ASC (that is, access class – access
service class) mapping for CELL_FACH enhancement.
ADD UERACHACTOASCMAP: CellId=xxx;
Run the BSC6900 MML command ACT UCELLERACH to activate the feature.
ACT UCELLERACH: CellId=xxx;
2.5 Device Resource Limitation

2.5.1 Scenario Description
The radio RTWP resources are not limited and the RTWP is lower than the target load. Single user throughput
or cell throughput is low. The possible cause is that device resources are limited, which results in a low rate or
small number of concurrent access or data transmission users.
2.5.2 Identification Rules
Rules for identifying device resource limitation
Table 24: Device limited ressource senario identification.
Scenario Time Identification Rules Sub-Scenario

Device resource busy hours Equivalent user ratio (UL_ENU_RATIO) > ENURatio (60% by Limitation on the
limitation default) & (Uplink power congestion exists number of equivalent
(VS.RRC.Rej.ULPower.Cong + users
VS.RAB.FailEstabCs.ULPower.Cong +
VS.RAB.FailEstabPS.ULPower.Cong != 0) or Number of
equivalent users allowed (UlTotalEqUserNum) > 160)
HSUPA CELL Active & Limitation on the
number of HSUPA
Number of HSUPA users (VS.HSUPA.UE.Mean.Cell) > Number users
of users allowed in the cell (MAXHSUPAUSERNUM) x
HSUPARatio (85% by default)
Scenario Time Identification Rules Sub-Scenario
NodeB admission CE usage (UL CE Utility Ratio) > CEUtility Admission CE
(70%) & CE congestion exists (Total UL CE Congestion != 0) limitation
NodeB admission CE usage (NODEB UL CE Utility Ratio) > Physical CE limitation
CEUtility (70%) & CE congestion exists (Total UL CE
Congestion != 0)
IP: Uplink user-plane assigned usage (UL Assign Peak Utility Admission Iub
Ratio (IP)) > IUBBWUtility (70%) limitation
ATM: Uplink user-plane assigned usage (UL Assign Peak Utility

Ratio (ATM)) > IUBBWUtility (70%)
& Number of uplink Iub congestion times

(VS.RRC.Rej.ULIUBBand.Cong +
VS.RAB.FailEstab.CS.ULIUBBand.Cong +
VS.RAB.FailEstab.PS.ULIUBBand.Cong) > IUBCongTimes (0
by default)
IP: Uplink user-plane actual usage (UL Real Utility Ratio (IP)) > Physical Iub limitation
IUBBWUtility (70%)
ATM: Uplink user-plane actual usage (UL Real Utility Ratio

(ATM)) > IUBBWUtility (70%)
& Number of uplink Iub congestion times

(VS.RRC.Rej.ULIUBBand.Cong +
VS.RAB.FailEstab.CS.ULIUBBand.Cong +
VS.RAB.FailEstab.PS.ULIUBBand.Cong) > IUBCongTimes (0
by default)
Uplink Iub congestion time > IUBFlowTime (0 by default) Iub QoS limitation
High CNBAP usage (CNBAP CPU Load) (> 60%) or Number of NodeB XPU limitation
RL Fail times (VS.RRC.Rej.RL.Fail) > RLFailTimes (0 by
default)
2.5.3 Optimization Solutions
2.5.3.1 Sub-scenario 1 — Limitation on the Number of Equivalent Users
Fault symptom
The usage of the ratio of equivalent users in a cell is high. As a result, uplink power congestion occurs and user
access is affected.
Solution 2: modifying the number of equivalent users
Modify the maximum number of uplink equivalent users of the cell.
MOD UCELLCAC: CellId=100, UlTotalEqUserNum=120;
After the modification, more access users are allowed in the uplink. However, in the admission mode based on
the number of equivalent users, the cell load cannot be predicted precisely. As a result, the cell load may be
increased or even uncontrollable, which affects the coverage and KPIs of edge users.
2.5.3.2 Sub-scenario 2 — Limitation on the Number of HSUPA Users
Fault symptom
The number of HSUPA users in a cell is large, for example, reaches the maximum number of HSUPA users
allowed in the cell. As a result, new HSUPA users access R99 services, and user experience is affected.
Solution 1: modifying the maximum number of HSUPA users in the cell
If the maximum number of HSUPA users in the cell is set to a small value, you can increase the value.
MOD UCELLCAC: CellId=100, MaxHsupaUserNum=20;
On condition that the radio load is not limited, more users can access the cell and the cell throughput can be
improved after the value of this parameter is increased. However, if the cell load is high, the cell load will be
increased and the user experience is affected after the value of this parameter is increased
Solution 3: 60/96 HSUPA users per cell
If the number of HSUPA users in a cell is large, it is recommended that the feature of 60/96 HSUPA users per
cell be enabled.
MOD UCELLCAC: CellId=100, MaxHsupaUserNum=60;
License: LQW1HSUPA07 60 HSUPA Users per Cell (per Mbit/s)
RGCHs and HICHs must be added so that the cell can allow 60 HSUPA users.
MOD UCELLHSUPA: CellId=100, ErgchEhichCodeNum=2;
Check the uplink load before modifying this parameter. If the uplink load reaches the target load, the uplink
load will be uncontrollable if more HSUPA users access the cell. It is recommended that the CCPIC and IC
features be enabled jointly with this feature to reduce the interference between control channels and between
users.
2.5.3.3 Sub-scenario 3 — Admission CE Limitation
Fault symptom
The admission CE usage of a cell is high. As a result, user admission fails.
Increase the number of CEs specified in the license or add baseband boards to relieve CE congestion. If the
number of CEs specified in the license exceeds the number of physical CEs, admission fails. Therefore, license
expansion must be consistent with physical CEs.
Solution 2: dynamic CE
From this release on, the dynamic CE resource management is supported.
The dynamic CE allocation can retrieve the CE resources in time when the throughput of users decreases,
saving the CE resources.
The NodeB retrieves the CE resources if the throughput of users decreases, allocates the CE resources during
the radio link setup or reconfiguration, allocates the CE resources for the Absolute Grant (AG) UP users, and
preempts the CE resources for the Relative Grant (RG) UP users.
Whether to support dynamic CE = Yes
Dynamic CE improves CE utilization, single user throughput, and cell throughput. However, dynamic CE results
in coverage shrink and may affect the access success rate and the call drop rate.
Solution 3: 2 ms/10 ms TTI switching based on admission CE
Table 25: 2ms/10ms switching based on CE parameters.
DRA_BASE_ADM_CE_BE_TTI_RE RNC The Switch of TTI Switch based on CE congestion
CFG_SWITCH
UlTtiCreditSfResThd RNC The threshold of the reserved SF is used for judging the uplink credit
state for TTI switchover decision. When uplink credit is lower than
the threshold, the credit state of TTI switchover algorithm is set to
restricted. The smaller the parameter value is, the easier the credit
state is set to restricted. 2 parameters are provided with the same
name; one is configured for NodeB and the other for cell level.
Rate threshold for 2 ms to 10 ms RNC Not Configurable, 326 kbit/s.
Rate threshold for 10 ms to 2 ms RNC Not Configurable, 710 kbit/s.
Run MML commands.
TTI switching based on admission CE
SET UCORRMALGOSWITCH: DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH-1;
Reserved SF threshold for determining the uplink CE state
Cell: ADD UCELLLDR: CELLID=x, ULTTICREDITSFRESTHD=4SF4; (4SF4 means 32 CEs)
NodeB: ADD UNODEBLDR: NodeBName=x, ULTTICREDITSFRESTHD=4SF4;
Solution 4: disabling the 2 ms feature
If the 2 ms feature is not necessary for the office and mass admission CE congestion occurs, it is recommended
that the 2 ms feature be disabled to relieve CE congestion, allow more access users, and improve the cell
HSUPA throughput.
MML:
SET UCORRMALGOSWITCH: MapSwitch=MAP_HSUPA_TTI_2MS_SWITCH-0;
Alternatively, you can use the license on the NodeB to disable the feature.
Impact
After the 2 ms feature is disabled, the HSUPA peak rate cannot reach 5.74 Mbit/s. If the customer requires the
peak rate to reach 5.74 Mbit/s, the 2 ms feature cannot be disabled.
Solution: modifying the GBR
For BE services, if the dynamic CE feature is enabled on the NodeB, the RNC performs admission based on the
GBR. If admission CE congestion occurs, you can decrease the GBR to relieve the congestion.
If the current GBR for HSUPA users is 64 kbit/s, it is recommended that the GBR be changed to 32 kbit/s or 16
kbit/s.
SET UUSERGBR: UlGBR=D32;
Solution 6: LDR rate reduction based on CE congestion
The congestion based on CE resources is classified as follows:
Congestion of the local cell
If the remaining uplink CE resource is lower than the congestion threshold (set by ADD UCELLLDR), the LDR
action is triggered to reduce the rate of R99 services to relieve the CE congestion.
Congestion of the local cell group/NodeB
If the remaining uplink CE resource is lower than the congestion threshold (set by ADD UNODEBLDR), the LDR
action is triggered to reduce the rate of R99 services to relieve the CE congestion.
MML:
Cell-level CE LDR switch
MOD UCELLALGOSWITCH: NBMLdcAlgoSwitch=CELL_CREDIT_LDR-1;
NodeB-level CE LDR switch
MOD UNODEBALGOPARA: NodeBLdcAlgoSwitch=NODEB_CREDIT_LDR-1&LCG_CREDIT_LDR-1;
Setting the threshold and action for CE congestion of the local cell
MOD UCELLLDR: UlLdrFirstAction=BERateRed, UlLdrCreditSfResThd=SF8;
Setting the threshold and action for CE congestion of the local cell group/NodeB
MOD UNODEBLDR: UlLdrFirstAction=BERateRed, UlLdrCreditSfResThd=SF8;
Solution 7: CE overbooking (R14)
This feature is controlled only by the license.
2.5.3.4 Sub-scenario 4 — Physical CE Limitation
Fault symptom
The physical CE usage of the NodeB is high, and admission fails due to CE congestion.
Add baseband boards and increase the number of CEs specified in the license.
License expansion must match the physical hardware capability. If the number of CEs specified in the license
exceeds the number of physical CEs, you must add boards.
Solution 2: dynamic CE
On the NodeB, activate the dynamic CE license.
Uplink CEs are shared in a resource group. In the case that multiple resource groups are used for cell bearing
and CE insufficiency occurs in some resource groups due to inter-cell load unbalancing, you can adjust resource
groups, boards, or cell distribution if hardware expansion is unavailable.
2.5.3.5 Sub-scenario 5 — Admission Iub Limitation
Fault symptom
Iub admission bandwidth congestion occurs or the actual Iub usage is high. As a result, the user throughput is
affected.
Add Iub transmission resources.
Solution 2: Iub overbooking
The activation factor can be configured based on the service type and adjacent nodes.
You can run LST TRMFACTOR to query the default configuration of the activation factor and run ADD
TRMFACTOR to configure the activation factor for different services dynamically.
You can run ADD ADJMAP and set FTI to configure the same activation factor for different adjacent nodes.
Step 1 Add the activation factor.
Figure 6: Activity factor parameters.
Step 2 Map the activation factor to adjacent nodes.
Figure 7: Activity factor parameters for adjacent node.
Solution 3: LDR rate reduction based on Iub congestion
Iub congestion control is implemented in the uplink and downlink of the NodeB by using the NodeB LDC
parameter IUB LDR. When Iub congestion is detected, R99 service rate reduction is triggered to release
bandwidth to relieve the congestion. In this manner, more access users are allowed, and the resource usage
and the cell throughput are improved.
Rate reduction is triggered for R99 BE services when Iub admission congestion occurs.
ADD UNODEBALGOPARA: NodeBLdcAlgoSwitch=IUB_LDR-1;
ADD UNODEBLDR: UlLdrFirstAction=BERateRed;
ADD TRMLOADTH: TRANST=IP, THTYPE=PERCENTAGE, BWDCONGTH=15, BWDCONGCLRTH=20;
2.5.3.6 Sub-scenario 6 — Physical Iub Limitation
Fault symptom
Physical Iub bandwidth limitation causes admission failure or low rate after flow control.
Add physical Iub transmission resources.
2.5.3.7 Sub-scenario 7 — Iub QoS Limitation
Fault symptom
When low Iub transmission quality or bandwidth congestion causes packet loss or large delay, flow control is
performed, and the rate is low.
If packet loss and large delay are caused by congestion of actual physical bandwidth, expansion is
recommended.
Solution 2: transmission troubleshooting
If packet loss or large delay is caused by low transmission quality, it is recommended that you locate the root
cause of the fault.
2.5.3.8 Sub-scenario 8 — NodeB XPU Limitation
Fault symptom
Admission fails because the CNBAP usage of the NodeB is high or mass RL FAIL occurs.
Solution 1: version upgrade
Upgrade the software to the latest version to provide higher CNBAP capability.
Solution 2: adding UTRP boards
Add UTRP boards to improve the CNBAP capability of the main control board.
Solution 3: adding WBBP boards
Add WBBP boards to improve the CNBAP capability of the baseband board and provide more DSP processing
resources.
The CNBAP capability of the baseband board is shared only in resource groups. If the CPU of the baseband
board is overloaded and hardware expansion is unavailable, it is recommended that you check whether
multiple resource groups are available.
3. Diagrams
 UL
o Radio capacity limitation
 System interference: Idle hours & Small number of users (DCHUE < 1) & High
RTWP (> Loadtarget) or Busy hours & Small number of users (Full rate load <
30% x Loadtarget) & High RTWP (> Loadolc)
 Target load limitation: Busy hours & (MeanRTWP > Target load or NodeB
performance measurement exists & HSUPA Active & MeanRTWP < Target load
& Unhappy user ratio > 30%)
 UE coverage limitation: Busy hours & MeanRTWP < Target load & HSUPA
CELL & NodeB performance measurement exists & Low ratio of power-limited
users (> 30%)
o Device capacity limitation
 Admission user limitation: Ratio of equivalent users > 60% & (Uplink power
congestion exists or Number of allowed equivalent users > 160)
 Admission user limitation: Number of HSUPA users > Maximum number of
users in the cell (maximum capacity of the cell) x 85%
 CE resource limitation: Admission CE usage of the NodeB > 70% & CE
congestion exists, Physical CE usage of the NodeB > 70% & CE congestion
exists
 Iub resource limitation: IP/ATM: uplink user-plane assigned usage > 70% &
uplink Iub congestion exists
 Iub resource limitation: Uplink Iub congestion time > 0
 NodeB XPU limitation: High CNBAP usage (> 60%) or RL Fail exists
 DL
o Channel quality limited: Average channel quality indicator (CQI) of cells < 15
o TCP load limited: R99 TCP utilization ratio > 70% or Total TCP utilization ratio > 80%
o BLER limited: BLER of a cell > 20%
 Other device limited
o Number of HSDPA subscribers limited: HSDPA is activated in the cell and Number of
HSDPA subscribers > Maximum number of subscribers supported by a celx 85%
o CE resource limited: NodeB admission CE utilization ratio > 70% and CE congestion
occurs.
o Iub-interface resource limited: Actuadownlink user plane IP/ATM assignment utilization
ratio at the user plane > 70% and Downlink Iub-interface resource congestion occurs.
o NodeB CPU/DSP processor limited: CNBAP utilization ratio > 60% and RLfailure exists.
TCP usage
Accessibility KPIs under threshold >=80% or False Check other congestion
or congestion or throughput per power cong>= causes
1%
user low (DL branch)
True
True
Cell has True

Problem False Is cell True
Alarms troubleshooting
alarms solved coverage
reasonable
False
False
Neighboring optimization and

chek (relations, strategy, CIO,
idleoffset2sn, …)
Problem Problem RF optimization: azimuth
change, tilt change, CPICH
solved solved change.
Add NodeBs and/or carrier
and/or sector
True True
Change Power preferred Reduce RRC related to

or power/code balancing IRAT
strategy at NodeB
Periodic LAU and RAU

DL L2+
Non-HS TCP parameters
>= 50% False
Power margin optimization Reduce RRC related to

REG
True
Enable HS-SCCH less

operation feature Enable EFD feature
Is RRC load
heavy True
Add DL power capacity if

license ok and/or add PA
or RFU if hardware limited
FACH UE power control False
FACH load >= CCH load

Add S-CCPCH True 30% >=20% False
Change and optimize cell

transition timers and True
False
parameters (4A,4B, …)
CCH PO optimization
R99 load >= False
Load based LDR actions True 50% of cell
load
End
Is DL power
Accessibility KPIs under threshold problem True
Check graph for DL power
or congestion or throughput per
user low (DL branch)
False
True
Cell has True Problem False Is cell True

reasonable
False False

Problem idleoffset2sn, …)
Problem RF optimization: azimuth
and/or sector
True True
Mean CQI
CCH PO check Code tree reshuffling LDR
R99 code utilization
per user ratio > 70%, or
<=15 R99+HSPA code
utilization ratio > 80%,
HSDPA based code tree or code congestion rate
MPO optimization reshuffling > 1%
Dynamic BLER based CQI Add board: according to

DL BLER >=
adjustment case WBBP, UMPT CNBAP
10%
utilization ratio
> 60%
andRLfailure
Ressource group exists
Iub overbooking
adjustment
DL Iub
congestion >=
1%
GBR adjustment CE overbooking
Add CE license in NodeB

Decrease initial bit rate
and if required expand NodeB DL
RNC total and/or WBBP physical/licens
e usage >=
DL Iub 70% and/or DL
congestion
False Add Iub transmission Change power preferred CE cong>= 1%
duration >= 1% capacity or power/code balancing
and DL Iub at Node B level
usage <= 70%
Reduce HSDPA bearer

Activate LDR actions
threshold
True Transmission troubleshooting
HSDPA active
users >= 85% Modify max number of
Max HSDPA users per cell
supported/auth
orized users
End
Is RTWP >= -
Accessibility KPIs under threshold 100 dBm False Check other congestion
or congestion or throughput per causes
user low (UL branch)
True
True

reasonable
False False

and/or sector
True True
Interference Coverage based TTI

RTWP >=- troubleshooting 2ms/10ms switching
100 and Number of UE
limited in
small
power
number of Change Background Noise important
users Coverage based E2D
according to situation
Enable auto adaptative RACH parameters

Background Noise optimization
RACH load >=
End 30%
Increase target load Enable CPC DTX feature
Enable CCPIC feature UL/DL L2+

R99 load >=
50% of cell
load Is HSUPA load
Disable TTI 2ms license or
Activate LDR actions heavy
2ms/10ms switching
based on RTWP
CQI feedback period HSUPA adaptative

optimization retransmission
HSDPA
accompagny
traffic >= 30%
of cell load
Reduce RRC related to
PO optimization
IRAT
Periodic LAU and RAU HSUPA data channel

parameters power adaptation
Is RRC load
heavy
Reduce RRC related to

Enable EFD feature
REG
End
Is UL power
Accessibility KPIs under threshold problem True
Check graph for UL power
or congestion or throughput per
user low (UL branch)
False
True

reasonable
False False

and/or sector
True
Modify max Equivalent Add CE license in NodeB

UL ENU ratio
user number per cell and if required expand
>= 70% and/
RNC total and/or WBBP
or ENU >=
150
CE based TTI 2ms/10ms
Add Iub transmission switching
capacity
UL Iub
congestion >=
Ressource group
1%
Iub overbooking adjustment
Enable/check if enabled
NodeB UL
GBR adjustment dynamic CE license physical/licens
e usage >=
UL Iub
70% and/or DL
congestion
CE cong>= 1%
duration >= 1%
and UL Iub CE overbooking Activation
Disable TTI 2ms/10ms
usage <= 70%
Activate LDR actions
CNBAP
Add board: according to utilization ratio
False Transmission troubleshooting
case WBBP, UMPT > 60%
andRLfailure
exists
HSUPA active
users >= 85% Modify max number of
Max HSUPA users per cell
supported/auth
orized users
End
Start
RRC.AttConnEstab RRC.AttConnEstab
Reduce number of IRAT False
False .IRATCelRes/VS.RR True .Reg/VS.RRC.AttCo
reselections (Check
C.AttConnEstab.Su related document) nnEstab.Sum>=
m>= 30% 30%
True
Check neighboring Check LAU/RAU timers and Check overshooting (check

configuration (check relative
parameters relative document)
document)
Is OK ? False
Make needed corrections.
True
Change LAC/RAC border in Change IdleQoffset2sn to higher

order to be more suitable and value with configured neighbor
make less LAU/RAU. cells from different LAC/RAC.
Check from Ucell-Ncell, the cells

from other LAC/RAC having high
number of SHO with cell
Is
Solve overshooting of False Change IdleQoffset2sn to higher
True neighborscellso
neighbors(check relative value and CIO to lower value for
document) vershooting ? the relations.
IsCSSR and CDR True

in the area OK?
False
Make a roll back in parameters

settings.
End

3G UL-DL Capacity Monitoring V1.0

Diunggah oleh

Informasi Dokumen

Hak Cipta

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

3G UL-DL Capacity Monitoring V1.0

Diunggah oleh

Hak Cipta:

Check et résolution des problèmes liés à la capacité UL ou DL

1.2 Radio Resource Limited

Table 1: Criteria for identifying the channel quality limited scenario

Scenario Time Criteria Other Criteria

1.2.1.3 Optimization Solutions

Solution 1: antenna adjustment

Solution 2: optimization of neighboring cells

Solution 3: capacity expansion

Solution 4: checking the CCH PO settings

Table 2: Default CCH power settings

Channel Type Default Value of the Power

MOD UCELL: CellId=100, PCPICHPower=xxx;

Solution 6: MPO constant adjustment

MOD UCELLHSDPA: CellId=100, HsPdschMPOConstEnum=2.5DB;

1.2.2 Scenario 2: TCP Load Limited

Criteria for identifying the TCP load limited scenario

Table 3: TCP load limited scenario

Scenario Time Criteria Other Criteria

Solution 1: adding carriers

Solution 2: adding NodeBs

Solution 4: mini NodeBs

To enable the L2+ feature, run the following command:

MOD UCELLALGOSWITCH: CellId=100, HspaPlusSwitch=DL_L2ENHANCED-1;

The 3GPP R7 protocols introduce the enhanced technology of 64QAM.

The enhanced L2 is a prerequisite for the implementation of the 64QAM.

To enable the 64QAM feature, perform the following steps:

1. Activate the 64QAM license: ACT LICENSE: ISPRIMARYPLMN=YES,

The DC-HSDPA helps to increase the throughput of a single UE and a cell.

Increasing the throughput of a single UE

Increasing the throughput of a cell

Solution 8: Power Margin parameter

Table 4: Power margin parameters

Command NE Parameter Default Value

1.2.2.3.1 Sub-Scenario 1: high RRC load

MOD UCNDOMAIN: CNDomainId=CS_DOMAIN, T3212=40;

Solution 2: Reduce RRC related to LU at LAC borders

Solution 3: Reduce RRC related to IRAT

Solution 4: signaling storm solution

1.2.2.3.2 Sub-Scenario 2: high FACH load

Solution 1: FACH UE power control

1. Add power admission to FACH UE.

Activate the FACH subscriber admission algorithm.

ADD UCELLALGOSWITCH: CellId=1101, NBMCacAlgoSwitch=FACH_UU_ADCTRL-1;

Configure the FACH power reduction parameter.

ADD UCELLOLC: CellId=1101, FACHPwrReduceValue=9;

Solution 2: Add a second S-CCPCH

Table 5: DCH to FACH transition timers.

Table 6: HSDPA to FACH transition timers.

Solution 5: decreasing the D2F/R or F/R2P 4B threshold of BE services

Table 7: DCH to FACH 4B thresholds.

D2F2PTvmThd < F2DTvmThd

D2F2PTvmThd < BeEFach2DTvmThd

Solution 6: decreasing the F/R2D 4A threshold of BE services

Table 8: FACH to DCH 4A thresholds.

SET UUESTATETRANS RNC BeF2DTvmThd N/A D1024 D512

BeF2DTvmThd must meet the following requirement:

D2F2PTvmThd < F2DTvmThd

Solution 7: decreasing the HS-DSCH2F 4B threshold of BE services

Table 9: HSDSCH to FACH 4B Threshold.

Solution 8: decreasing the F2HS-DSCH 4A threshold of BE services

Table 10: FACH to HSDSCH 4A tresholds.

BeH2FTvmThd < BeF2HTvmThd

1.2.2.3.3 Sub-Scenario 3: high R99 load

Solution 1: downlink load–based LDR BE rate reduction

Table 11: DL LDR action BE Rate reduction

Command NE Parameter Default Value Recommended

Solution 1: power/code balancing