Professional Documents
Culture Documents
HUAWEI Capacity-Monitoring-Guide PDF
HUAWEI Capacity-Monitoring-Guide PDF
1
Capacity Monitoring Guide
Issue Draft A
Date 2012-07-23
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer.
All or part of the products, services and features described in this document may not be within the purchase scope or
the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this
document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or
implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation
of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this
document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Purpose
Traffic on a mobile telecommunications network, especially a newly deployed network,
increases over time. To support the ever-increasing traffic, more and more network resources
are required, such as signaling processing resources, transmission resources, and air interface
resources.
If any type of network resource is insufficient, the key performance indicators (KPIs) decline
(for example, the call drop rate increases), and user experience deteriorates. Therefore,
real-time resource monitoring, resource bottleneck detection, and timely network expansion
are critical to good user experience on a mobile telecommunications network. This document
is intended to help network maintenance personnel monitor UTRAN system capacity and
detect network resource bottlenecks.
This document applies to RAN14.1 UTRAN products, including BSC6910 and 3900 series
base stations. This document is only to be used as a reference for RNCs and NodeBs of earlier
versions.
Organization
This document provides guidelines for preventing resource congestion. When following these
guidelines, you must consider intuitiveness and operability based on site requirements.
This document consists of the following chapters.
Chapter Description
1 Network Resource Describes basic concepts associated with network resources, including definitions
Monitoring Methods and monitoring activities.
2 Network Resource Describes the counters for monitoring various network resources.
Performance Counters
3 HSPA-related Resource Describes how to monitor network resources when High Speed Packet Access
Monitoring (HSPA) is enabled.
4 Diagnosis of Problems Describes fault analysis and diagnosis methods that experienced WCDMA network
Related to Network maintenance personnel can use to handle network congestion or overload
Resources efficiently.
5 Counter Definitions Lists all performance counters mentioned in the preceding chapters and provides
the definitions of these counters.
Change History
Issue Date Description Version Prepared By
1 2012-07-23 This is the Draft A release of Draft A Inventory Solutions Department
RAN14.1.
Contents
Two methods are available for monitoring network resources and detecting resource
bottlenecks:
Prediction-based monitoring
This method monitors various network resources simultaneously. You can monitor the usage
of a network resource (for example, the downlink transmit power of a cell), compare the
detected resource usage with a preset upper threshold, predict the resource usage trend and
impact, and determine whether to perform network expansion. If the resource usage remains
above the preset upper threshold for a long time (for example, a cell remains overloaded
during busy hours for several consecutive days), you can split the cell or add carriers for
network expansion.
This method is used to identify high-load cells and RNCs. It is a conventional means of
monitoring resource usage and is easy to implement.
This chapter describes how to use this method to monitor network resources.
NOTE
For details about the counters for monitoring network resources, see chapter 2 "Network Resource
Performance Counters." For details about HSPA-related resources, see chapter 3 "HSPA-related
Resource."
Problem-driven analysis
This method is used to analyze decreased network performance counters after network
congestion has occurred. This method is more complex than prediction-based monitoring
because it requires more analysis instruments and skills. However, this method can maximize
how the system utilizes existing resources and eliminate the need for immediate network
expansion. For details about this method, see chapter 4 "Diagnosis of Problems Related to
Network Resources."
NOTE
Experienced network maintenance engineers can also use other methods to analyze network resource
problems.
not result from insufficient capacities of interface boards but from low bandwidth
available on the IP transport network.
Other resource usages are not used to determine whether the RNC is overloaded.
This flowchart applies to most resource monitoring scenarios, except when the system
overload is caused by an unexpected event rather than a service increase. To simplify the
procedure, unexpected events are not considered in this flowchart. The causes of unexpected
events might be located through a comprehensive analysis of various resource bottlenecks.
For details about how to locate a resource-related problem, see chapter 4 "Diagnosis of
Problems Related to Network Resources."
This chapter provides the performance counters for monitoring the network resources
described in chapter 1 and their upper thresholds. These counters indicate the resource usage
or load on a UTRAN.
Identifying the busy hour is crucial to accurate counter monitoring. There are various methods
for identifying the busy hour. The simplest method is recommended, that is, determining the
hour during which the most resources are consumed. If the value of a counter during the busy
hour exceeds the upper threshold for three consecutive days, consider capacity expansion.
pools. Control-plane resources form a control-plane resource pool, and user-plane resources
form a user-plane resource pool. The number of resources allocated to the control plane and
user plane can be adjusted based on service requirements so that load is balanced between the
two planes. Consider the control-plane load and user-plane load comprehensively before
performing capacity expansion.
For details about other parameters in the SET UCPUPFLEXCFG command, see BSC6910
UMTS MML Command Reference.
Counters for Monitoring Average CPU Usage on the Control and User Planes
The VS.SUBSYS.CPULOAD.MEAN counter measures the average CPU usage of a
subsystem during a measurement period and reflects the CPU load and quality of the
subsystem during the measurement period.
The average CPU usage on the control plane is calculated by the following formula:
Average CPU usage on the control plane = Average (VS.SUBSYS.CPULOAD.MEAN
measured for all CP subsystems)
The average CPU usage on the user plane is calculated by the following formula:
Average CPU usage on the user plane = Average (VS.SUBSYS.CPULOAD.MEAN measured
for all UP subsystems)
The recommended upper thresholds for monitoring the average CPU usage on the control and
user planes are 50% and 60%, respectively.
When FlexCfgMode is set to ManulMode or FrozenMode, you are advised to enable
dynamic sharing or to adjust the ratio of resources split between processing user plane data
and control plane data if the control plane or user plane is overloaded. If the control-plane or
user-plane resources cannot meet your traffic model's requirements, perform capacity
expansion immediately.
The counters for monitoring the CPU usage on the interface board are as follows:
VS.INT.CPULOAD.MEAN
This counter measures the average CPU usage of an interface board as a percentage.
Average CPU usage for session load
This counter is calculated by the following formula:
Average CPU usage for session load = VS.INT.CFG.INTERWORKING.NUM/Number
of established or released sessions per second x 60 x SP x 100%
where
VS.INT.CFG.INTERWORKING.NUM is the number of call setup attempts on an
interface board. SP is the measurement period (in minutes).
The number of established or released sessions per second is subject to system
specifications: 5000 for the GOUc and FG2c boards and 50,000 for the EXOUa
board.
It is recommended that an interface board be added when the CPU usage or session load of an
interface board exceeds 50%.
Introduction
If active and standby SCUa boards are used, the inter-subrack bandwidth is 4 Gbit/s. If active
and standby SCUb boards are used, the inter-subrack bandwidth is 40 Gbit/s.
If the active or standby SCUa/SCUb board is faulty, the inter-subrack bandwidth decreases by
half.
If the value of Frame Peak Utility Ratio is greater than 60%, a prewarning is required.
Frame Mean Utility Ratio
This counter measures the average usage of inter-subrack traffic and is calculated by the
following formula:
Frame Mean Utility Ratio = VS.Frame.Flux.Mean.TxRate/Inter-subrack bandwidth x
100%
where
VS.Frame.Flux.Mean.TxRate is the average traffic volume transmitted between
subracks.
If the value of Frame Mean Utility Ratio is greater than 40%, a prewarning is required.
Frame DropPackets Ratio
This counter measures the packet loss rate between subracks and is calculated by the
following formula:
Frame DropPackets Ratio = VS.Frame.Flux.DropPackets/VS.Frame.Flux.TxPackets x
100%
where
VS.Frame.Flux.DropPackets is the number of packets discarded during packet
transmission between subracks.
VS.Frame.Flux.TxPackets is the number of packets transmitted between subracks.
If the value of Frame DropPackets Ratio is greater than 0.01%, a prewarning is required.
If the prewarning threshold is reached or an inter-subrack bandwidth congestion alarm is
reported, contact Huawei engineers for problem handling.
CNBAP usage
where
VS.IUB.AttRLSetup is the number of Iub RL setup requests in a cell.
VS.IUB.AttRLAdd is the number of Iub RL addition requests in a cell.
VS.IUB.AttRLRecfg is the number of Iub RL reconfiguration attempts in a cell.
SP is the measurement period (in seconds).
CNBAP capacity of the NodeB depends on the configuration of the WMPT/UMPT,
WBBP, and UTRP boards.
If the CNBAP usage of the WMPT/UMPT board is above 60% on a Huawei NodeB, you are
advised to perform capacity expansion by adding a WBBP/UTRP board or splitting the
NodeB.
2.2.3 CE Usage
Channel elements (CEs) are baseband resources provided by NodeBs. One CE resource can
be consumed by a 12.2 kbit/s voice call. If available CE resources are insufficient, a new call
request is rejected.
The total available CE resources are limited by the hardware and configured licenses. If CE
resources on the WBBP board are sufficient, the CE resources are limited by only licenses. In
this case, expand the licensed capacity. CE resources are managed and shared in a resource
group of the NodeB.
Separate baseband processing units are used in the uplink and downlink directions of a NodeB.
Therefore, uplink and downlink CE resources are managed and used independently of each
other.
The number of licensed CE resources is distributed by the M2000. The number of CE resources
provided by boards on a NodeB and the number of CE resources provided by boards in an uplink
resource group are calculated based on NodeB board configuration and specifications. You can run
MML commands to query the NodeB board configuration.
Uplink CE Usage
Since RAN14.0, the CE Overbooking feature has been introduced for uplink CE resources.
The counters for monitoring uplink CE usage vary depending on whether CE Overbooking is
enabled.
If CE Overbooking is enabled, the following counters are used to monitor uplink CE usage:
VS.NodeB.ULCreditUsed.Mean
This counter measures the average uplink NodeB credit resource usage when CE
Overbooking is enabled.
NodeB_UL_CE_MEAN_RATIO
This counter measures the uplink CE usage on a NodeB and is calculated by the
following formula:
NodeB_UL_CE_MEAN_RATIO = Sum_AllCells_of_NodeB
(VS.NodeB.ULCreditUsed.Mean/2)/UL CE Cfg Number
where
VS.NodeB.ULCreditUsed.Mean is the average uplink NodeB credit resource usage
when CE Overbooking is enabled.
UL CE Cfg Number is the number of available uplink CE resources on a NodeB. The
number is the smaller of the values for two counters: NodeB License UL CE Number
and NodeB Physical UL CE Capacity. NodeB License UL CE Number measures the
number of licensed uplink CE resources on a NodeB. NodeB Physical UL CE
Capacity measures the number of uplink CE resources provided by boards on a
NodeB.
If CE Overbooking is disabled, the following counters are used to monitor uplink CE usage:
NodeB_UL_GRP_CE_MEAN_RATIO
This counter measures the CE usage in an uplink resource group of a NodeB. Each
NodeB allows for multiple uplink resource groups. This counter is calculated by the
following formula:
NodeB_UL_GRP_CE_MEAN_RATIO = Sum_AllCells_of_ResourceGroup
(VS.LC.ULCreditUsed.Mean/2)/UL GRP CE Cfg Number
where
VS.LC.ULCreditUsed.Mean is the average uplink NodeB credit resource usage in a
cell.
UL GRP CE Cfg Number is the number of available CE resources in an uplink
resource group. The number is the smaller of the values for two counters: NodeB
License UL CE Number and NodeB Physical UL group CE Capacity. NodeB
Physical UL group CE Capacity measures the number of CE resources provided by
boards in an uplink resource group.
NodeB_UL_CE_MEAN_RATIO
This counter measures the uplink CE usage on a NodeB and is calculated by the
following formula:
NodeB_UL_CE_MEAN_RATIO = Sum_AllCells_of_NodeB
(VS.LC.ULCreditUsed.Mean/2)/UL CE Cfg Number
where
VS.LC.ULCreditUsed.Mean is the average uplink NodeB credit resource usage in a
cell.
UL CE Cfg Number is the number of available uplink CE resources on a NodeB.
The upper threshold for uplink CE usage is 70%. If CE usage is above 70% in an uplink
resource group of a NodeB, add a WBBP board to the uplink resource group even if the
CE usage is low on the NodeB.
Downlink CE Usage
The NodeB_DL_CE_MEAN_RATIO counter measures the downlink CE usage and is
calculated by the following formula:
NodeB_DL_CE_MEAN_RATIO =
Sum_AllCells_of_NodeB(VS.LC.DLCreditUsed.Mean)/DL CE Cfg Number
where
VS.LC.DLCreditUsed.Mean is the average downlink NodeB credit resource usage in a
cell.
The BSC6910 does not support logical ports. The EGPUa board does not support virtual ports (VPs).
Figure 2-1 Relationship between RTWP, interference increase, and uplink load
The recommended uplink load threshold is 75%, and the corresponding RTWP value is
smaller than -100 dBm. If the RNC uses algorithm 2 during admission control, the value of
the UL ENU Ratio counter should be smaller than 75%. UL ENU Ratio measures the ratio of
uplink equivalent users to users supported in the cell. Algorithm 2 is the Equivalent Number
of Users (ENU) algorithm.
If the RTWP value is greater than -100 dBm, the cell is overloaded in the uplink.
Generally, if a cell is overloaded or the RTWP value is too large, the cell coverage shrinks, the
quality of ongoing services deteriorates, and new service requests may be rejected.
The following counters related to RTWP and ENU are used on Huawei RNCs:
VS.MeanRTWP: average RTWP (in dBms) in a cell
VS.MinRTWP: minimum RTWP (in dBms) in a cell
VS.RAC.UL.EqvUserNum: number of uplink equivalent users on all dedicated channels
in a cell
UL ENU Ratio: this counter is calculated by the following formula:
UL ENU Ratio = VS.RAC.UL.EqvUserNum/UlTotalEqUserNum
where
UlTotalEqUserNum is the maximum number of equivalent users in a cell, which can be
set by running the ADD UCELLCAC command.
In some areas, the background noise increases to far higher than -106 dBm due to other
interference or hardware problems, such as antennas or feeder connectors of poor quality. In
this case, the VS.MinRTWP counter, which measures the RTWP when there is no traffic in a
cell, reflects the background noise in the cell. If the VS.MinRTWP value during the idle hour
is larger than -100 dBm or smaller than -110 dBm for three consecutive days in one week,
there are hardware problems or external interference. Find the cause, and troubleshoot the
problems or eliminate the external interference.
The recommended uplink load threshold is indicated by the VS.MeanRTWP counter. A cell is
considered heavily loaded in the uplink when either of the following is true for two or three
days in one week:
The VS.MeanRTWP value during the busy hour remains above -100 dBm, which
corresponds to a 6 dB interference increase or 75% load.
The UL ENU Ratio value during the busy hour remains above 75%.
When the cell is heavily loaded, perform capacity expansion by adding a carrier or increasing
the UlTotalEqUserNum value.
If Then
Downlink Maximum Upper Threshold for Upper TCP Threshold That
Transmit Power TCP Usage Triggers Cell Overload
If the TCP usage during the busy hour remains above 85% for three consecutive days in one
week, the cell is heavily loaded in the downlink. Then, perform capacity expansion by adding
a carrier.
Some live networks use hierarchical cell structures with multiple carriers. The cell power
settings and the corresponding upper TCP thresholds vary depending on the networking
policy and cell service priority.
In the downlink, the maximum spreading factor (SF) 256 can be used.
In a cell, only one OVSF code tree is available. In the OVSF code tree, sibling codes are
orthogonal to each other, but are not with their parent or child codes. As a result, once a code
is allocated to a user, neither its parent nor child code can be allocated to any other user.
OVSF code resources are limited. If available OVSF codes are insufficient to achieve the
desired quality of service (QoS), a new call request may be rejected.
An OVSF code tree can be divided into 4 SF4 codes, 8 SF8 codes, 16 SF16 codes, or 256
SF256 codes. Codes with various SFs can be considered as equivalent codes with SF 256. For
example, a code with SF 8 is equivalent to 32 codes with SF 256. Based on this equivalence
mapping, the OVSF code usage can be calculated for a user or in a cell.
Huawei RNCs monitor the average code usage of an OVSF code tree based on the number of
equivalent codes with SF 256. The VS.RAB.SFOccupy counter measures the average code
usage of an OVSF code tree.
The counters for monitoring the OVSF code usage are as follows:
OVSF_Utilization, which is calculated by the following formula:
OVSF_Utilization = VS.RAB.SFOccupy/256
DCH_OVSF_Utilization, which is calculated by the following formula:
DCH_OVSF_Utilization = DCH_OVSF_CODE/256
where
DCH_OVSF_CODE is calculated as follows:
DCH_OVSF_CODE = ((<VS.SingleRAB.SF4> + <VS.MultRAB.SF4>) x 64 +
(<VS.MultRAB.SF8> + <VS.SingleRAB.SF8>) x 32 + (<VS.MultRAB.SF16> +
<VS.SingleRAB.SF16>) x 16 + (<VS.SingleRAB.SF32> + <VS.MultRAB.SF32>) x 8 +
(<VS.MultRAB.SF64> + <VS.SingleRAB.SF64>) x 4 + (<VS.SingleRAB.SF128> +
<VS.MultRAB.SF128>) x 2 + (<VS.SingleRAB.SF256> + <VS.MultRAB.SF256>))
If the DCH_OVSF_Utilization value during the busy hour remains above 70% for three
consecutive days in one week, the cell runs out of OVSF codes. Perform capacity expansion
by splitting the cell or adding a carrier.
Common channel resource analysis involves the monitoring of both PCHs and FACHs. If the
PCH usage is too high, paging messages may be lost. Paging messages are broadcast across
an area identified by location area code (LAC), which is referred to as a LAC area for short.
Therefore, improper LAC planning leads to high PCH usage. High FACH usage is mainly
caused by two factors:
State transition of a large number of UEs performing packet switched (PS) services
RRC signaling storms
Based on the default parameter settings for Huawei RNCs, the PCH and FACH usages are
calculated as follows:
PCH usage
The PCH Physical Channel Utility Ratio counter measures the PCH usage and is
calculated by the following formula:
where
VS.FACHUEs is the number of users on the FACH.
If FACH_60_USER_SWITCH is set to ON, this counter is calculated by the
following formula:
FACH UserNum Utility Ratio = VS.FACHUEs/60 x 100%
where
VS.FACHUEs is the number of users on the FACH.
If the FACH usage or the ratio of users on the FACH to users allowed to use the FACH
reaches 70%, you are advised to modify the parameter settings.
HSPA includes High Speed Downlink Packet Access (HSDPA) and High Speed Uplink
Packet Access (HSUPA). HSDPA and HSUPA protocols are part of the WCDMA standard.
HSPA includes techniques such as fast scheduling, adaptive modulation, and hybrid automatic
repeat request (HARQ) to achieve high speed data transmission.
HSPA carries PS services. Conversational services are prioritized over PS services, and
therefore HSPA uses network resources only after conversational services are served. This
chapter describes how to monitor network resources when HSPA is enabled.
3.1 HSDPA
3.1.1 Power Resources
Figure 3-1 illustrates how the downlink transmit power in a cell is allocated. The dashed line
indicates the total downlink transmit power in a cell.
You can reduce high OVSF code usage by modifying the parameter settings.
3.2 HSUPA
3.2.1 CE Resources
HSUPA channels are dedicated channels, and resource consumption of HUSPA services is
measured by CEs. When HSUPA is enabled, uplink CE resources are shared between R99
services and HSUPA services.
HSUPA increases uplink throughput and improves user experience. However, HSUPA
consumes more uplink CE overhead for HARQ and soft handovers. Therefore, uplink CE
resources may become a system bottleneck. Uplink CE usage needs to be monitored when
HSUPA is enabled. Huawei NodeBs support dynamic HSUPA CE resource management,
which uses CE resources efficiently.
3.2.2 RTWP
Just as HSDPA makes the most of downlink power resources, HSUPA maximizes uplink
capacity. HSUPA data can always be sent in authorized mode unless the RTWP rises to 6
dBm.
HSUPA increases uplink cell throughput but consumes a large amount of uplink RTWP. The
uplink RTWP is monitored in the same way regardless of whether HSUPA is enabled. If
RTWP overload occurs, HSUPA service rates must be lowered to ensure the QoS of
conversational services.
The preceding chapters describe the basic methods for monitoring network resources. These
methods can be used to resolve most problems caused by high resource usage. In certain
scenarios, further problem diagnosis is required to determine whether high resource usage is
caused by a traffic increase or exceptions.
This chapter describes how to diagnose problems related to network resources, including the
following topics:
4.1 Call Congestion in the Basic Call Flow
4.2 Call Congestion Counters
4.3 Signaling Storms and Solutions
4.4 Resource Usage Analysis
This chapter is intended for experts who have a deep understanding of WCDMA networks.
Figure 4-1 Call flowchart showing possible block and failure points
instruction, or the UE receives the message but finds the configuration incorrect, as
shown by failure points 5 and 6.
8. If the RRC connection is set up, the UE sends non-access stratum (NAS) messages to
negotiate with the CN about service setup. If the CN determines to set up a service, the
CN sends an RAB assignment request to the RNC.
9. Upon receiving the RAB assignment request, the RNC accepts or rejects the request
based on the resource usage on the RAN side. If the RNC rejects the request, the failure
is shown by block point 7.
10. If the RNC accepts the RAB assignment request, the RNC initiates a radio bearer (RB)
setup procedure. During the procedure, the RNC allocates resources as follows:
The RNC allocates transmission resources over the Iub interface by setting up an RL
to the NodeB.
The RNC allocates channel resources over the Uu interface by sending an RB setup
message to the UE.
A failure may occur in the RL or RB setup process, as shown by failure points 8 and 9.
VS.RAB.FailEstabPs.DLCE.Cong
Counters for measuring the number of failed RAB establishments due to downlink code
resource congestion, including:
VS.RAB.FailEstabCs.Code.Cong
VS.RAB.FailEstabPs.Code.Cong
Counters for measuring the number of failed RAB establishments due to Iub bandwidth
congestion, including:
VS.RAB.FailEstabCS.DLIUBBand.Cong
VS.RAB.FailEstabCS.ULIUBBand.Cong
VS.RAB.FailEstabPS.DLIUBBand.Cong
VS.RAB.FailEstabPS.ULIUBBand.Cong
VS.RAB.AttEstab.Cell
This counter measures the total number of RAB establishment requests in a cell.
VS.RAB.Block.Rate
This counter measures the RAB congestion rate and is calculated by the following
formula:
VS.RAB.Block.Rate = Total number of failed RAB establishments regardless of the
cause of failure/VS.RAB.AttEstab.Cell
Table 4-1 describes solutions to signaling storms. These solutions aim to reduce signaling load
so that the network capacity does not need to be expanded immediately.
In most cases, an abnormal KPI triggers the troubleshooting process. Determining the
possible top N problem cells facilitates follow-up troubleshooting.
You are advised to analyze accessibility KPIs to identify the system bottleneck that causes
access congestion.
Figure 4-5 Process for analyzing the CPU usage of the control plane
As shown in Figure 4-5, if the CPU usage of the control plane is above 50%, identify the
causes to prevent a continuous increase in the CPU usage. If the high CPU usage is caused by
signaling storms, determine whether the parameter settings are correct. If the high CPU usage
is caused by a traffic increase, add an EGPUa board.
Control-plane and user-plane sharing adjusts the load on EGPUa boards to balance the
average load on the control and user planes. NodeB Management (NBM) load cannot be
shared between the control and user planes. Therefore, you must perform dynamic cell
reallocation to balance the NBM load among EGPUa boards in the control-plane resource
pool. After the traffic model changes, reduce the number of cells under the RNC or add an
EGPUa board when both of the following conditions are met:
Control-plane and user-plane sharing is enabled.
The load is imbalanced between the control and user planes. For example, the
control-plane load is lighter than the user-plane load, but the available control-plane
resources are insufficient to add a NodeB or cell.
Figure 4-6 Process for analyzing the CPU usage of the user plane
If the CPU usage of the user plane is above 60%, identify the causes to prevent a continuous
increase in the CPU usage. If the high CPU usage is caused by a traffic increase, add an
EGPUa board.
NOTE
The preceding table assumes that signaling radio bearers (SRBs) are carried over HSUPA. If an SRB is
carried on an R99 DCH separately, an extra CE is consumed by the SRB. In this case, add 1 to each
number listed in the preceding table.
HSDPA services do no consume downlink R99 CE resources. HSUPA services and R99
services share uplink CE resources.
CE congestion or routine CE usage monitoring may trigger CE resource analysis.
If the CE usage remains above a preset capacity expansion threshold or CE congestion occurs,
the CE resources are insufficient and must be increased to ensure system stability.
CE resources can be shared within a resource group. Therefore, CE usage on the NodeB must
be calculated to determine where CE congestion occurs in a resource group or on the NodeB.
If CE congestion occurs in a resource group, reallocate CE resources between resource groups.
If CE congestion occurs on the site, perform site capacity expansion and modify parameter
settings.
If insufficient Iub bandwidth causes congestion, check the Iub bandwidth usage.
If the Iub bandwidth usage remains above 80% for a period of time, the Iub bandwidth is
insufficient.
If no more Iub bandwidth is available or the issue is not urgent, decrease the activity factor for
PS services to admit more users. The activity factor, which is the ratio of actual bandwidth
occupied by a UE to the allocated bandwidth, is used to estimate the real bandwidth usage.
The activity factor can be set on a per-NodeB basis. The default activity factor is 0.7 for voice
services and 0.4 for PS best effort (BE) services.
NOTE
RRC-related counters are updated based on the cause values in the RRC connection requests. This
facilitates analysis of risks related to signaling storms.
Generally, adding a carrier is the most effective means for relieving uplink power congestion.
If no additional carrier is available, consider deploying a new site or splitting the cell by
reducing the tilt angle of the antenna.
5 Counter Definitions
Table 5-1 defines all performance counters mentioned in the preceding chapters.
NodeB_UL_GR NodeB_UL_GRP_CE_MEAN_RATIO =
P_CE_MEAN_R Sum_AllCells_of_ResourceGroup(VS.LC.ULCr
ATIO editUsed.Mean/2)/UL GRP CE Cfg Number
Sum_AllCells_of_NodeB
NodeB_DL_CE_ (VS.LC.DLCreditUsed.Mean)/MIN(NodeB
VS.LC.DLCreditUsed.Mean
MEAN_RATIO License DL CE Number, NodeB Physical DL CE
Capacity)