ERAN3 0 Capacity Monitoring

eRAN3.
Capacity Monitoring Guide
Issue
02
Date
2013-03-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
02 (2013-03-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
eRAN3.0
About This Document
About This Document

Purpose
Growing traffic in mobile networks, especially in newly deployed networks, requires more
and more resources such as radio and transport resources. Lack of resources will affect user
experience. Therefore, monitoring network resources, locating bottlenecks, and performing
optimizations or expansion are critical to the provision of high quality services.
This document provides guidelines on LTE FDD capacity monitoring (including resource
allocation problem identification) to help maintenance personnel monitor resource usage and
prevent network congestion.
The description in this document is based on 3900 series base stations.
NOTE
For definitions of the man-machine language (MML) commands, parameters, alarms, and performance
counters mentioned in this document, see the "Operation and Maintenance" part in 3900 Series LTE
eNodeB Product Documentation.
Intended Audience
This document is intended for:
Field engineers
Network planning engineers
Organization
This document describes the principles and methods of capacity monitoring.
02 (2013-03-30)
Chapter
Description
1 "Overview"
Provides an introduction to capacity monitoring methods,

network resources, and a guideline process of capacity
monitoring and handling.
2 "General Capacity
Monitoring"
Provides the capacity monitoring principles, monitoring

methods, and suggested measures.
3 "Resource Allocation
Problem Identification"
Provides guidelines on resource allocation problem

identification.

ii
eRAN3.0
About This Document
Chapter
Description
A "Appendix"
Describes the query methods mentions in chapter 2 "General

Capacity Monitoring."
Change History
This section describes changes in each issue of this document.
02 (2013-03-30)
This is the second official release.
The document name has been changed from Capacity Monitoring Guidelines to Capacity
Monitoring Guide.
Compared with 01 (2012-12-30), this issue includes an appendix and the changes described in
the following table.
Section
Change Description
1.3 "General Process"
Modified the general process of

capacity monitoring and handling.
1 "Overview"
Modified these chapters to conform to

a new template.
2 "General Capacity Monitoring"

3 "Resource Allocation Problem Identification"
No information in 01 (2012-12-30) is deleted from 02 (2013-03-30).
01 (2012-12-30)
This is the first official release.
02 (2013-03-30)

iii
eRAN3.0
Contents
Contents
About This Document .................................................................................................................... ii
1 Overview......................................................................................................................................... 1
1.1 Capacity Monitoring Methods.......................................................................................................................... 1
1.2 Network Resources .......................................................................................................................................... 1
1.2.1 eNodeB Resources .................................................................................................................................. 2
1.2.2 Cell Resources ........................................................................................................................................ 2
1.3 General Process ................................................................................................................................................ 3
2 General Capacity Monitoring ..................................................................................................... 6

2.1 Introduction ...................................................................................................................................................... 6
2.2 Connected User License Usage ........................................................................................................................ 8
2.2.1 Monitoring Principles ............................................................................................................................. 8
2.2.2 Monitoring Methods ............................................................................................................................... 8
2.2.3 Suggested Measures ................................................................................................................................ 8
2.3 PRB Usage ....................................................................................................................................................... 8
2.3.3 Suggested Measures ................................................................................................................................ 9
2.4 PUCCH Resource Usage .................................................................................................................................. 9
2.4.3 Suggested Measures .............................................................................................................................. 10
2.5 SRS Resource Usage ...................................................................................................................................... 10
2.5.1 Monitoring Principles ........................................................................................................................... 10
2.5.2 Monitoring Methods ............................................................................................................................. 10
2.6 PRACH Resource Usage ................................................................................................................................ 10
2.7 PDCCH Resource Usage ................................................................................................................................ 11
02 (2013-03-30)

iv
eRAN3.0
Contents

2.8 Paging Resource Usage .................................................................................................................................. 12
2.9 Control-Board CPU Usage ............................................................................................................................. 13
2.10 LBBP CPU Usage ........................................................................................................................................ 14
2.10.1 Monitoring Principles ......................................................................................................................... 14
2.10.2 Monitoring Methods ........................................................................................................................... 14
2.10.3 Suggested Measures ............................................................................................................................ 14
2.11 Transport Resource Group Usage ................................................................................................................. 15
2.11.1 Monitoring Principles .......................................................................................................................... 15
2.11.2 Monitoring Methods............................................................................................................................ 15
2.12 Ethernet Port Traffic ..................................................................................................................................... 16
2.12.1 Monitoring Principles ......................................................................................................................... 16
2.12.2 Monitoring Methods ........................................................................................................................... 16
3 Resource Allocation Problem Identification ......................................................................... 17

3.1 Resource Congestion Indicators ..................................................................................................................... 17
3.1.1 RRC Resource Congestion Rate ........................................................................................................... 17
3.1.2 E-RAB Resource Congestion Rate ....................................................................................................... 17
3.2 Resource Allocation Problem Identification Process ..................................................................................... 18
A Appendix ..................................................................................................................................... 19
A.1 Querying the Maximum Number of UEs Supported by the PUCCH ............................................................ 19
A.2 Querying the Maximum Number of UEs Supported by SRS Resources....................................................... 20
A.3 Querying the Maximum Number of CCEs .................................................................................................... 23
A.4 Querying Ethernet Port Traffic ...................................................................................................................... 24
02 (2013-03-30)

eRAN3.0
1 Overview
Overview
This chapter provides an introduction to capacity monitoring methods, network resources, and
a general process of capacity monitoring and handling.
1.1 Capacity Monitoring Methods

Capacity monitoring can be implemented using the following two methods:
Prediction-based monitoring: monitors various types of resource consumption and makes

room for preventive measures such as optimization or expansion to prevent network
congestion. This method applies to daily monitoring because it is simple and easy to
follow. For details, see chapter 2 "General Capacity Monitoring."
Problem-driven analysis: uses analysis tools and techniques to identify resource

allocation problems when network congestion occurs. This method helps utilize potential
network value and reduce demands on network expansion. For details, see chapter 3
"Resource Allocation Problem Identification."
1.2 Network Resources

Figure 1-1 shows the network resources to be monitored.
Figure 1-1 Network resources to be monitored
02 (2013-03-30)

eRAN3.0
1 Overview
1.2.1 eNodeB Resources

The following are the eNodeB resources to be monitored:
Connected user license

The connected user license specifies the maximum permissible number of users in
RRC_CONNECTED mode. Each connected user consumes radio, device, and transport
resources.
If there are too many connected users, they cannot be well served by the eNodeB and
new services cannot be admitted.
Paging resources
If the actual number of paging messages exceeds the paging capacity, the eNodeB will
be unable to process all the paging messages and user experience will be affected.
Control-board CPU
If the load on the main control board exceeds the CPU capacity, severe problems may
occur, for example, the deterioration of key performance indicators (KPIs).
LBBP CPU
If the load on an LTE baseband process unit (LBBP) exceeds the CPU capacity, severe
problems may occur, for example, the deterioration of KPIs.
Transport resource groups

If the load on a transport resource group exceeds the bandwidth configured for the group,
exceptions may occur (for example, packets may be lost), affecting user experience.
Ethernet ports
If the load on an Ethernet port exceeds the bandwidth configured for the port, exceptions
may occur (for example, packets may be lost), affecting user experience.
1.2.2 Cell Resources
PRBs
The usage of physical resource blocks (PRBs) reflects the uplink and downlink
bandwidth consumed on the air interface.
PUCCH resources
Insufficient physical uplink control channel (PUCCH) resources have negative impacts
on the following:
Admission of new services and handovers
Number of UEs that can be scheduled
Cell throughput and UE throughput
Uplink scheduling delay
SRS resources
Sounding reference signal (SRS) resources are allocated to UEs for network access. If an
LBBPd is used, UEs can access the network even when SRS resources are not allocated
to them.
If SRS resources are insufficient, the eNodeB cannot obtain accurate measurement
information, which then affects efficient use of radio resources.
PRACH resources
Physical random access channel (PRACH) resources are random access preambles
carried on the PRACH.
02 (2013-03-30)

eRAN3.0
1 Overview
If PRACH resources are insufficient for handling all access attempts, access delays are
prolonged or even access attempts fail.
PDCCH resources
If physical downlink control channel (PDCCH) resources are limited, scheduling delays
are long and user experience is affected.
1.3 General Process

Figure 1-2 shows a general process of capacity monitoring and handling.
02 (2013-03-30)

eRAN3.0
1 Overview
Figure 1-2 General process of capacity monitoring and handling
02 (2013-03-30)

eRAN3.0
1 Overview
Some indicators need to be used with others in order to locate resource bottlenecks. For
example, the connected user license usage must be used with the control-board CPU usage;
the PDCCH resource usage must be used with the uplink or downlink PRB usage.
For details about capacity monitoring, see chapter 2 "General Capacity Monitoring" or contact
Huawei technical support.
The process shown in Figure 1-2 is applicable in most cases. If the resource overload is not
due to increased traffic but due to other factors, identify resource allocation problems by
referring to chapter 3 "Resource Allocation Problem Identification."
02 (2013-03-30)

eRAN3.0
2 General Capacity Monitoring
General Capacity Monitoring
2.1 Introduction
For monitoring resource consumption on the network, counters and corresponding limits are
defined in the eNodeB. For better monitoring, busy hours should be defined; it is
recommended that the period with maximum resource consumption be defined as busy hours.
Table 2-1, Table 2-2, Table 2-3, and Table 2-4 describe the counters related to radio resources,
device resources, transport resources, and reactive KPIs, respectively.
Table 2-1 Counters related to radio resources
02 (2013-03-30)
Performance Counter
Description
L.Traffic.User.Avg
Average number of users in a cell
L.Traffic.User.Max
Maximum number of users in a cell
L.Traffic.User.Ulsync.Avg
Average number of uplink-synchronized users in a cell

(that is, average number of scheduled users in a cell)
L.ChMeas.PRB.UL.Used.Avg
Average number of used uplink PRBs in a cell
L.ChMeas.
PRB.DL.Used.Avg
Average number of used downlink PRBs in a cell
L.ChMeas.PRB.PUCCH.Avg
Average number of used PRBs in the PUCCH in a cell
L.RA.GrpA.Att
Number of times that random preambles in group A are

received in a cell
L.RA.GrpB.Att
Number of times that random preambles in group B are

received in a cell
L.RA.Dedicate.Att
Number of times that dedicated preambles are received

(uplink synchronization restoration) in a cell
L.ChMeas.CCE.CommUsed
Number of PDCCH control channel elements (CCEs)

used for common signaling in a cell
L.ChMeas.CCE.ULUsed
Number of PDCCH CCEs used for uplink scheduling in a

cell

eRAN3.0
Performance Counter
Description
L.ChMeas.CCE.DLUsed
Number of PDCCH CCEs used for downlink scheduling

in a cell
L.Paging.S1.Rx
Number of paging messages received over the S1

interface in a cell
L.Paging.Dis.Num
Number of discarded paging messages over the Uu

interface in a cell
Table 2-2 Counters related to device resources

Performance Counter
Description
VS.Board.CPUload.Max
Maximum CPU usage of a board
VS.Board.CPUload.Mean
Average CPU usage of a board
VS.Board.CPULoad.Cumulati
veHighloadCount
Number of times that the CPU usage of a board exceeds

the preconfigured threshold
Table 2-3 Counters related to transport resources

Performance Counter
Description
VS.FEGE.TxMaxSpeed
Maximum transmission rate on an Ethernet port
VS.FEGE.TxMeanSpeed
Average transmission rate on an Ethernet port
VS.FEGE.RxMaxSpeed
Maximum reception rate on an Ethernet port
VS.FEGE.RxMeanSpeed
Average reception rate on an Ethernet port
VS.RscGroup.TxPkts
Number of packets transmitted by a transport resource

group
VS.RscGroup.TxDropPkts
Number of packets discarded by a transport resource

group due to transmission failures
VS.RscGroup.TxMaxSpeed
Maximum transmission rate in a transport resource group
VS.RscGroup.TxMeanSpeed
Average transmission rate in a transport resource group
Table 2-4 Counters related to reactive KPIs
02 (2013-03-30)
Performance Counter
Description
L.RRC.ConnReq.Att
Number of RRC Connection Request messages received

from UEs in a cell

eRAN3.0
Performance Counter
Description
L.RRC.ConnReq.Succ
Number of RRC Connection Setup Complete messages

received from UEs in a cell
L.E-RAB.AttEst
Number of E-UTRAN radio access bearer (E-RAB) setup

attempts initiated by UEs in a cell
L.E-RAB.SuccEst
Number of successful E-RAB setups initiated by UEs in a

cell
L.E-RAB.AbnormRel
Number of times that the eNodeB abnormally releases

E-RABs that are transmitting data in a cell
L.E-RAB.NormRel
Number of times that the eNodeB normally releases

E-RABs in a cell
2.2 Connected User License Usage

2.2.1 Monitoring Principles
If the radio resource control (RRC) connection setup failure rate exceeds 1%, check the
connected user license usage immediately. If the usage reaches the expansion threshold, users
cannot access the network. In this case, if the LMPT CPU usage is also abnormal, you can
perform capacity expansion.
2.2.2 Monitoring Methods

Connected user license usage = Average number of connected users served by the eNodeB
during busy hours (indicated by L.Traffic.User.Avg for each cell)/Licensed number of
connected users x 100%
2.2.3 Suggested Measures

If the connected user license usage exceeds 80%, check the LMPT CPU usage and take one of
the following actions:
If the LMPT CPU usage is lower than 60%, you are advised to increase the licensed
limit.
If the LMPT CPU usage is greater than or equal to 60%, adding more users will result in
LMPT CPU overload, and you are advised to add an eNodeB.
2.3 PRB Usage

When the data volume in a cell is high, the PRB usage is high. If the cell is not expanded
promptly, UEs may not be able to access the cell and user experience is affected.
02 (2013-03-30)

eRAN3.0

The following items are used in monitoring this case:
Uplink PRB usage = Average number of used uplink PRBs during busy hours (indicated
by L.ChMeas.PRB.UL.Used.Avg)/Total number of uplink PRBs x 100%
Downlink PRB usage = Average number of used downlink PRBs during busy hours
(indicated by L.ChMeas.PRB.DL.Used.Avg)/Total number of downlink PRBs x 100%

Consider the PRB usage and the PDCCH resource usage before performing system expansion.
For details about the PDCCH resource usage, see section 2.7 "PDCCH Resource Usage."
2.4 PUCCH Resource Usage

PUCCH resources include:
Scheduling request indicator (SRI) resources used by scheduled UEs
Channel quality indicator (CQI) resources used by scheduled UEs
Acknowledgment (ACK) resources
The impacts of insufficient PUCCH resources are as follows:
UE admission and handover failure: When a UE requests an RRC connection be

established for a service admission or a handover, the eNodeB allocates CQI resources,
SRI resources, and ACK resources for the UE in semi-persistent scheduling mode. If the
allocation of SRI and CQI resources fails, the UE handover admission fails.
Limited number of scheduled UEs: If an out-of-synchronization UE requests uplink

synchronization for data transmission, the eNodeB allocates CQI resources, SRI
resources, and ACK resources for the UE. If the allocation of SRI and CQI resources
fails, the UE cannot restore uplink synchronization and therefore cannot transmit data.
Decrease in cell and UE throughput: If CQI resources are insufficient or limited, the
eNodeB selects a CQI reporting period of 40 ms for UEs, which results in less accurate
CQIs and lower spectral efficiency. In addition, these UEs cannot be chosen to perform
frequency selective scheduling.
Increase in uplink scheduling delay: If SRI resources are insufficient or limited, the
eNodeB selects an SRI period of 20 ms for UEs, which results in longer uplink
scheduling delays for these UEs.

PUCCH resource usage = Average number of scheduled UEs in a cell during busy hours
(indicated by L.Traffic.User.Ulsync.Avg)/Total number of UEs supported by the PUCCH x
100%
In the formula, the total number of UEs supported by the PUCCH is equal to the total number
of UEs supported by the configured CQI and SRI resources. For query methods, see chapter A
"Appendix."
02 (2013-03-30)

eRAN3.0

If the PUCCH resource usage exceeds 75%, you are advised to turn on the PUCCH flexible
configuration switch by running the following command:
MOD CELLALGOSWITCH: LocalCellId=xxx, PucchAlgoSwitch=PucchSwitch-1;
2.5 SRS Resource Usage

The eNodeB allocates sounding reference signal (SRS) resources to UEs that access the
network. By measuring SRSs, the eNodeB can estimate uplink channel quality for uplink
adaptive modulation and coding (AMC) and frequency selective scheduling. In addition, the
eNodeB can measure the UE uplink timing to maintain uplink synchronization. For each UE,
the SRS is not sent together with the physical uplink shared channel (PUSCH) or PUCCH.

SRS resource usage = Average number of scheduled UEs in a cell during busy hours
(indicated by L.Traffic.User.Ulsync.Avg)/Maximum number of UEs supported under the
current SRS configuration x 100%
In the formula, the maximum number of UEs supported under the current SRS configuration
can be queried. For the query method, see chapter A "Appendix."

If the SRS resource usage exceeds 75%, you are advised to take either of the following
measures:
Prolong the SRS period until it reaches the maximum SRS subframe configuration by
running the following command:
MOD SRSADAPTIVECFG: SrsPeriodAdaptive=OFF, UserSrsPeriodCfg=ms40;
Turn on the SRS period adaptation switch by running the following command:
MOD SRSADAPTIVECFG: SrsPeriodAdaptive=ON;
2.6 PRACH Resource Usage

The PRACH transmits preambles during contention-based or non-contention-based random
access procedures. If more than 100 non-contention-based random access attempts are
initiated per second, dedicated preambles will become insufficient and the eNodeB will
instruct the UE to initiate contention-based random access instead, increasing the access delay
for the UE. In handover scenarios, the handover procedure is prolonged.
If more than 100 contention-based random access attempts are initiated per second, the
collision probabilities and access delays increase.
02 (2013-03-30)

10
eRAN3.0

Random preamble usage = [Number of times that random preambles in group A are
received during a busy hour (indicated by L.RA.GrpA.Att) + Number of times that
random preambles in group B are received during this hour (indicated by
L.RA.GrpB.Att)]/3600/100 x 100%
Dedicated preamble usage = Number of times that dedicated preambles are received
during busy hours (indicated by L.RA.Dedicate.Att)/3600/100 x 100%

If the percentage of the total number of times that random preambles in group A and group B
are received exceeds 75% during busy hours, you are advised to enable the adaptive backoff
function by running the following command to help reduce the peak RACH load and average
access delay:
MOD CELLALGOSWITCH: LocalCellId=x, RachAlgoSwitch=BackOffSwitch-1;
If the percentage of the number of times that dedicated preambles are received exceeds 75%
during busy hours, you are advised to enable reuse of dedicated preambles between UEs by
running the following command:
MOD CELLALGOSWITCH: LocalCellId=x, RachAlgoSwitch=MaksIdxSwitch-1;
This helps reduce the probability of UEs initiating contention-based random access in the case
of dedicated preamble insufficiencies and therefore helps reduce the access delay.
2.7 PDCCH Resource Usage

This capacity indicator measures the number of control channel elements (CCEs) that can be
used by the PDCCH.
In each radio frame, CCEs must be allocated to uplink and downlink UEs to be scheduled and
common control signaling. PDCCH CCEs must be properly configured and allocated to
minimize downlink control overheads as well as to ensure satisfactory user-plane throughput.
If PDCCH symbols are insufficient, CCEs may fail to be allocated to UEs to be

scheduled, which will result in a long service delay and unsatisfactory user experience.
In addition to the long service delay, if the UEs to be scheduled have small-sized buffers
but need to transmit a large amount of user plane data, the PRBs and power allocated to
the physical downlink shared channel (PDSCH) and PUSCH may be more than
necessary, resulting in low spectral efficiency.
If PDCCH symbols are excessive, which indicates that the usage of PDCCH CCEs is low,
the resources that can be used by the PDSCH decreases. This will also result in low
spectral efficiency.

CCE usage = [Number of PDCCH CCEs used for common signaling during a busy hour
(indicated by L.ChMeas.CCE.CommUsed) + Number of PDCCH CCEs used for uplink
02 (2013-03-30)

11
eRAN3.0
scheduling during this hour (indicated by L.ChMeas.CCE.ULUsed) + Number of PDCCH

CCEs used for downlink scheduling during this hour (indicated by
L.ChMeas.CCE.DLUsed)]/3600/Total number of PDCCH CCEs in the cell x 100%

If the PDCCH symbol adjustment switch is turned on (by setting the PdcchSymNumSwitch
parameter to ON), the eNodeB automatically adjusts the number of PDCCH symbols based
on the CCE load, to meet the CCE requirement while preventing excessive PDSCH resource
consumption. In this scenario, PDCCH resource usage does not need to be monitored.
If the PDCCH symbol adjustment switch is turned off (by setting the PdcchSymNumSwitch
parameter to OFF), you are advised to turn on the switch by running the following command
when the CCE usage in a cell exceeds 80% and the uplink or downlink PRB resource usage is
below 90%:
MOD CELLPDCCHALGO: LocalCellId=x, PdcchSymNumSwitch=ON;
2.8 Paging Resource Usage

In eRAN3.0, the eNodeB can process a maximum of 500 paging messages per second. If the
number of paging messages exceeds the that capacity, the eNodeB may discard paging
messages, which leads to a decrease in the call completion rate.

The monitoring item can be either of the following:
Percentage of paging messages received over the S1 interface = Number of paging

messages received over the S1 interface during busy hours (indicated by
L.Paging.S1.Rx)/3600/Maximum number of paging messages that can be processed per
second x 100%
Number of paging messages discarded over the Uu interface during busy hours
(indicated by L.Paging.Dis.Num)

If either of the following conditions is met, you are advised to decrease the number of cells in
the tracking area list (TAL) that the congested cell belongs to:
02 (2013-03-30)
In an eNodeB, the percentage of the number of paging messages received by the eNodeB
over the S1 interface exceeds 60% of the eNodeB paging capacity.
In an eNodeB, more than 1500 paging messages from the mobility management entity
(MME) to UEs are discarded during busy hours.

12
eRAN3.0
2.9 Control-Board CPU Usage

The CPU usage reflects the eNodeB status during busy hours. If the control-board CPUs are
busy processing control plane or user plane data, signaling-related KPIs may deteriorate, and
users may experience a low access success rate, low E-RAB setup success rate, or high
service drop rate. Table 2-5 describes the signaling- and service-related measurement units.
Table 2-5 Signaling- and service-related measurement units
Category
Measurement Unit
Description
Signaling-related
Measurement related to
RRC setup
RRC connection setup measurement

(RRC.Setup.Cell)
E-RAB establish
E-RAB setup measurement

(E-RAB.Est.Cell)
E-RAB release
E-RAB release measurement

(E-RAB.Rel.Cell)
Intra eRan HOIN
Incoming handover measurement

(HO.eRAN.In.Cell)
MCS
Modulation and coding scheme (MCS)

measurement (ChMeas.MCS.Cell)
MAC
Media Access Control (MAC) data unit

measurement (Traffic.MAC.Cell)
Service-related
Operators can use the information described in Table 2-5 to determine whether KPI
deterioration is caused by insufficient control-board CPU processing capability or poor radio
conditions. The evaluation is as follows:
If the MCS measurement and initial-transmission failure measurement indicate that the
channel quality is poor, KPI deterioration may not be caused by control-board CPU
overload but by deterioration in channel quality.
If the KPIs deteriorate and the control-board CPU usage exceeds the expansion threshold,
you are advised to perform capacity expansion according to section 2.9.3 "Suggested
Measures."

02 (2013-03-30)
Average control-board CPU usage during busy hours (indicated by

VS.Board.CPUload.Mean)
Number of times that the control-board CPU usage exceeds the threshold during busy
hours (indicated by VS.Board.CPULoad.CumulativeHighloadCount)

13
eRAN3.0

In eRAN3.0, the control-board CPU becomes overloaded if one of the following conditions is
met:
The average control-board CPU usage (VS.Board.CPUload.Mean) exceeds 70% in one

busy hour for x consecutive days (x is configurable).
The percentage of the number of times that the control-board CPU usage exceeds 85%
(VS.Board.CPULoad.CumulativeHighloadCount/3600) exceeds 20% in one busy hour
for x consecutive days (x is configurable).
If the control-board CPU is overloaded, you are advised to perform capacity expansion on the
eNodeB control plane as follows:
1.
Upgrade the software to increase the capacity.
2.
If the main control board is an LMPT, replace with the LMPT with a UMPT.
3.
Add an eNodeB, and connect it to the evolved packet core (EPC) through a new S1
interface.
2.10 LBBP CPU Usage

If the eNodeB receives too much traffic volume, which is expressed either in bit/s or packet/s,
the LBBP CPU responsible for user plane processing is heavily loaded. As a result, the
eNodeB has a low RRC connection setup success rate, low E-RAB setup success rate, low
handover success rate, and high service drop rate.

Average LBBP CPU usage during busy hours (indicated by VS.Board.CPUload.Mean)
Number of times that the LBBP CPU usage exceeds the threshold during busy hours
(indicated by VS.Board.CPULoad.CumulativeHighloadCount)

In eRAN3.0, the LBBP CPU becomes overloaded if one of the following conditions is met:
The average LBBP CPU usage (VS.Board.CPUload.Mean) exceeds 75% in one busy
hour for x consecutive days (x is configurable).
The percentage of the number of times that the LBBP CPU usage exceeds 85%
(VS.Board.CPULoad.CumulativeHighloadCount/3600) is more than 20% in one busy
hour for x consecutive days (x is configurable).
If the LBBP CPU is overloaded, you are advised to perform capacity expansion on the
eNodeB user plane as follows:
02 (2013-03-30)
If the LBBP is an LBBPc, replace the LBBPc with an LBBPd.
Add an LBBP to share the network load, and then determine whether to move the
existing cells or add new cells based on the number of UEs. The capacity expansion
methods are as follows:
14
eRAN3.0
If the radio resources are sufficient, move a cell from the existing LBBP to the new
LBBP.
If the radio resources are insufficient, set up new cells on the new LBBP.
If the eNodeB has multiple LBBPs and one of them is overloaded, move cells from the
overloaded LBBP to an LBBP with a lighter load.
NOTE
LBBP load is indicated by the following:
Average CPU usage
Percentage of times that the CPU usage exceeds the threshold
Number of cells established on an LBBP
If the eNodeB already has a maximum of six LBBPs and more LBBPs are required, add
an eNodeB.
2.11 Transport Resource Group Usage

Each transport resource group is a monitored object.

Packet discard rate = Number of packets discarded because of transmission failures of

the transport resource group during busy hours/Number of packets sent by the transport
resource group during busy hours
Proportion of transmission rate to configured bandwidth = Maximum transmission rate

of the transport resource group during busy hours/Bandwidth configured for the transport
resource group

The main counters are VS.RscGroup.TxMeanSpeed, VS.RscGroup.TxMaxSpeed,
VS.RscGroup.TxPkts, and VS.RscGroup.TxDropPkts. A transport resource group is
congested if one of the following conditions is met:
The proportion of the average transmission rate to the configured bandwidth during busy
hours exceeds 4/5 in 80% of monitoring periods throughout an entire week.
The proportion of the maximum transmission rate to the configured bandwidth during
busy hours exceeds 9/10 in 10% of monitoring periods throughout an entire week.
The packet loss rate exceeds 0.05% during busy hours for a whole week. The packet loss
rate is the ratio of VS.RscGroup.TxDropPkts to RscGroup.TxPkts in a specific period.
When a transport resource group is congested, you are advised to adjust the bandwidth
configuration for the transport resource group on the eNodeB. The following is an example
command:
MOD RSCGRP: CN=0, SRN=0, SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=0,
RU=KBPS, TXBW=15000, RXBW=20000;
02 (2013-03-30)

15
eRAN3.0
If the problem persists after the bandwidth adjustment, you are advised to perform capacity
expansion on the transport resource group.
2.12 Ethernet Port Traffic

The Ethernet port traffic is the channel traffic at the physical layer, including uplink and
downlink traffic. The eNodeB Ethernet port traffic reflects the throughput and communication
quality of the Ethernet ports on the main control board of the eNodeB. Based on the
monitoring results, you can determine whether the transmission capacity allocated by an
operator for the S1 and X2 interfaces on the eNodeB meet the requirements for uplink and
downlink transmissions.

Proportion of uplink transmission rate to configured bandwidth = Uplink transmission

rate of the Ethernet port during busy hours/Uplink transmission bandwidth configured by
the operator
Proportion of downlink reception rate to configured bandwidth = Downlink reception

rate of the Ethernet port during busy hours/Downlink reception bandwidth configured by
the operator
The following table describes how to use these items.

Table 2-6 Ethernet port traffic conditions for capacity expansion
Monitored Item
When to Perform Capacity Expansion
Average and peak rate

during busy hours
The proportion of average uplink transmission rate or average

downlink reception rate to configured bandwidth exceeds 7/10 in
80% of monitoring periods throughout an entire week.
The proportion of peak uplink transmission rate or peak downlink
reception rate to configured bandwidth exceeds 85/100 in 10% of
monitoring periods throughout an entire week.

If the eNodeB Ethernet port bandwidth is less than the eNodeB traffic limit, you are advised
to expand the port bandwidth. Otherwise, you are advised to increase the licensed eNodeB
traffic capacity or replace an LMPT with a universal main processing and transmission unit
(UMPT).
02 (2013-03-30)

16
eRAN3.0
3 Resource Allocation Problem Identification
Resource Allocation Problem

Identification
Guidelines provided in chapter 2 "General Capacity Monitoring" provide methods to take

preventive measures to prevent network congestion. If the network is already congested, see
the contents of this chapter for steps to assess the cause of the congestion.
3.1 Resource Congestion Indicators

Resource congestion indicators (such as the RRC resource congestion rate and E-RAB
resource congestion rate) can be used to check whether the network is congested.
3.1.1 RRC Resource Congestion Rate

The RRC resource congestion rate is a cell-level indicator. It is calculated using the following
formula:
RRC resource congestion rate = Number of RRC connection setup failures due to resource
allocation failures (indicated by L.RRC.SetupFail.ResFail)/Number of RRC connection setup
requests (indicated by L.RRC.ConnReq.Att) x 100%
3.1.2 E-RAB Resource Congestion Rate

The E-RAB resource congestion rate is a cell-level indicator. It is calculated using the
following formula:
E-RAB resource congestion rate = Number of E-RAB setup failures due to radio resource
insufficiency (indicated by L.E-RAB.FailEst.NoRadioRes)/Number of E-RAB setup attempts
(indicated by L.E-RAB.AttEst) x 100%
02 (2013-03-30)

17
eRAN3.0
3.2 Resource Allocation Problem Identification Process

Figure 3-1 Resource allocation problem identification process
The fault location procedure begins with the identification of abnormal KPIs, followed up by
selecting and performing a KPI analysis on the top N cells.
Cell congestion mainly results from insufficient system resources. Bottlenecks can be
detected by analyzing the access KPIs.
02 (2013-03-30)

18
eRAN3.0
Appendix
A.1 Querying the Maximum Number of UEs Supported

by the PUCCH
The SRI/ACK resources are adjusted based on the SRI period and the number of PDCCH
symbols per subframe. An eNodeB allocates SRI resources together with CQI resources to a
UE. Therefore, the maximum number of UEs supported by the PUCCH can be represented by
the maximum number of UEs supported by CQI resources.
To query the maximum number of UEs supported by CQI resources, perform the following
steps:
Step 1 Run the LST CELLALGOSWITCH command to query the value of the PUCCH algorithm
switch parameter.
If the value is PucchSwitch:On, query the maximum number of UEs supported by CQI
resources in Table A-1.
If the value is PucchSwitch:Off, go to Step 2.
Step 2 Run the LST CQIADAPTIVECFG command to query the value of the CQI period
adaptive switch parameter.
If the value is On, query the maximum number of UEs supported by CQI resources in
Table A-1.
If the value is Off, go to Step 3.
Step 3 Calculate the maximum number of UEs supported by CQI resources.

Maximum number of UEs supported by CQI resources = Min (12/Delta shift x CQI RB
number x User CQI period config, Maximum number of UEs supported by the system)
where
02 (2013-03-30)
The Delta shift parameter specifies the interval between cyclic shifts used for the
PUCCH. Its value can be queried by running the LST PUCCHCFG command.
The CQI RB number parameter specifies the number of PRBs allocated for CQIs. Its
value can be queried by running the LST PUCCHCFG command.
The User CQI period config parameter specifies the CQI reporting period. Its value can
be queried by running the LST CQIADAPTIVECFG command.

19
eRAN3.0
Table A-1 Maximum number of UEs supported by CQI resources

Channel Bandwidth (Configurable)
Maximum Number of UEs
5 MHz
200
10 MHz
400
15 MHz
400
20 MHz
400
----End
A.2 Querying the Maximum Number of UEs Supported

by SRS Resources
To query the maximum number of UEs supported by SRS resources, perform the following
steps:
Step 1 Run the LST CELLALGOSWITCH command to query the value of the SoundingRS
algorithm switch parameter.
If the value is SrsSubframeRecfSwitch:On, query the maximum number of UEs

supported by SRS resources in Table A-2.
If the value is SrsSubframeRecfSwitch:Off, go to Step 2.
Step 2 Run the LST SRSCFG command to query the value of the SRS subframe configuration
parameter, and then query the maximum number of UEs supported by SRS resources based
on Table A-3.
Table A-2 Maximum number of UEs supported by SRS resources (SrsSubframeRecfSwitch set
to On)
02 (2013-03-30)
Channel Bandwidth
(Configurable)
Number of SRS
Subframes per Frame
Maximum Number of UEs
5 MHz
Automatically adjusted
in the range of 1 to 10
200
10 MHz
400, for normal cyclic prefix (CP)
370, for extended CP
15 MHz
400
20 MHz
400

20
eRAN3.0
Table A-3 Maximum number of UEs supported by SRS resources (SrsSubframeRecfSwitch set
to Off)
CP Length
(Configurable)
Channel
Bandwidth
(Configurable)
SRS Subframe
Position
(Configurable)
Number of SRS
Subframes per
Frame
Maximum
Number of
UEs
Normal CP
5 MHz
9, 10, 11, 12
3, 4, 5, 6
16
7, 8
40
1, 2
56
13
120
14
152
10
200
9, 10, 11, 12
12
3, 4, 5, 6
24
7, 8
120
1, 2
168
13
264
14
312
10
400
9, 10, 11, 12
15
3, 4, 5, 6
30
7, 8
60
1, 2
120
13
240
14
300
10
400
9, 10, 11, 12
15
3, 4, 5, 6
30
7, 8
90
1, 2
120
13
240
14
300
10
400
10 MHz
15 MHz
20 MHz
02 (2013-03-30)

21
eRAN3.0
CP Length
(Configurable)
Channel
Bandwidth
(Configurable)
SRS Subframe
Position
(Configurable)
Number of SRS
Subframes per
Frame
Maximum
Number of
UEs
Extended CP
5 MHz
9, 10, 11, 12
3, 4, 5, 6
30
7, 8
78
1, 2
102
13
150
14
174
10
200
9, 10, 11, 12
10
3, 4, 5, 6
50
7, 8
130
1, 2
170
13
250
14
290
10
370
9, 10, 11, 12
20
3, 4, 5, 6
40
7, 8
120
1, 2
160
13
280
14
360
10
400
9, 10, 11, 12
22
3, 4, 5, 6
67
7, 8
157
1, 2
202
13
292
14
337
10
400
10 MHz
15 MHz
20 MHz
----End
02 (2013-03-30)

22
eRAN3.0
A.3 Querying the Maximum Number of CCEs

To query the maximum number of CCEs, perform the following steps:
Step 1 Run the LST CELLPDCCHALGO command to query the value of the PDCCH Symbol
Number Adjust Switch parameter.
If the value is On, query the maximum number of CCEs based on Table A-4.
If the value is Off, go to Step 2.
Step 2 Run the LST PHICHCFG command to the query the value of the PHICH resource
parameter.
The value can be ONE_SIXTH, HALF, and ONE, TWO, which are the same as the values
of Ng in Table A-4. The maximum number of CCEs can be queried based on Ng in Table A-4.
Table A-4 Maximum number of CCEs
Channel
Bandwidth
Ng
(Configurable)
(Configurable)
5 MHz
10 MHz
15 MHz
20 MHz
PDCCH Symbol Number

Adjust Switch = Off
Number of PDCCH
Symbols (Configurable)
1
1/6
13
21
1/2
12
21
12
20
11
19
1/6
10
26
43
1/2
26
42
25
41
23
39
1/6
15
40
65
1/2
14
39
64
12
37
62
34
59
1/6
20
54
87
1/2
19
52
86
17
50
84
13
46
80
PDCCH
Symbol
Number
Adjust
Switch = On
21
43
65
87
----End
02 (2013-03-30)

23
eRAN3.0
A.4 Querying Ethernet Port Traffic

Ethernet port traffic can be queried by running the LST LR command to query values of
parameters LR Switch, UL Committed Information Rate, and DL Committed
Information Rate.
If LR Switch is set to Disable, set the denominator (S1 allocated bandwidth) in the
following formulas to 1 GHz for the UMPT or 360 MHz for the LMPT:
VS. FEGE.TxMeanSpeed/S1 allocated bandwidth
VS. FEGE.TxMaxSpeed/S1 allocated bandwidth
If LR Switch is set to Disable, set the denominator (S1 allocated bandwidth) in the
following formulas to 1 GHz for the UMPT or 540 MHz for the LMPT:
VS.FEGE.RxMeanSpeed/S1 allocated bandwidth
VS.FEGE.RxMaxSpeed/S1 allocated bandwidth
If LR Switch is set to Enable, set the denominator (S1 allocated bandwidth) in the
following formulas to the value of UL Committed Information Rate:
VS.FEGE.TxMeanSpeed/S1 allocated bandwidth
VS.FEGE.TxMaxSpeed/S1 allocated bandwidth
If LR Switch is set to Enable, set the denominator (S1 allocated bandwidth) in the
following formulas to the value of DL Committed Information Rate:
VS.FEGE.RxMeanSpeed/S1 allocated bandwidth
VS.FEGE.RxMaxSpeed/S1 allocated bandwidth
NOTE
The main control board type (UMPT or LMPT) is specified by the Board Type parameter and can be
queried by running the DSP BRD command. Because many types of boards exist in the baseband unit
(BBU), you must search all boards for the main control board.
02 (2013-03-30)

24

ERAN3 0 Capacity Monitoring

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ERAN3 0 Capacity Monitoring

Uploaded by

Copyright:

Available Formats

eRAN3.

Capacity Monitoring Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Network planning engineers

Provides an introduction to capacity monitoring methods,

Provides the capacity monitoring principles, monitoring

Provides guidelines on resource allocation problem

Huawei Proprietary and Confidential

About This Document

Describes the query methods mentions in chapter 2 "General

1.3 "General Process"

Modified the general process of

Modified these chapters to conform to

2 "General Capacity Monitoring"

No information in 01 (2012-12-30) is deleted from 02 (2013-03-30).

Huawei Proprietary and Confidential

2 General Capacity Monitoring ..................................................................................................... 6

Huawei Proprietary and Confidential

2.7.3 Suggested Measures .............................................................................................................................. 12

3 Resource Allocation Problem Identification ......................................................................... 17

Huawei Proprietary and Confidential

1.1 Capacity Monitoring Methods

Prediction-based monitoring: monitors various types of resource consumption and makes

Problem-driven analysis: uses analysis tools and techniques to identify resource

1.2 Network Resources

Huawei Proprietary and Confidential

1.2.1 eNodeB Resources

Connected user license

Transport resource groups

1.2.2 Cell Resources

Admission of new services and handovers

Number of UEs that can be scheduled

Cell throughput and UE throughput

Uplink scheduling delay

Huawei Proprietary and Confidential

1.3 General Process

Huawei Proprietary and Confidential

Figure 1-2 General process of capacity monitoring and handling

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

2 General Capacity Monitoring

General Capacity Monitoring

Average number of users in a cell

Maximum number of users in a cell

Average number of uplink-synchronized users in a cell

Average number of used uplink PRBs in a cell

Average number of used downlink PRBs in a cell

Average number of used PRBs in the PUCCH in a cell

Number of times that random preambles in group A are

Number of times that random preambles in group B are

Number of times that dedicated preambles are received

Number of PDCCH control channel elements (CCEs)

Number of PDCCH CCEs used for uplink scheduling in a

Huawei Proprietary and Confidential

2 General Capacity Monitoring

Number of PDCCH CCEs used for downlink scheduling

Number of paging messages received over the S1