ERAN Capacity Monitoring Guide (02) (PDF) - en

eRAN
Capacity Monitoring Guide

Issue
02
Date
2015-06-20
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. 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
Issue 02 (2015-06-20)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
eRAN
About This Document
About This Document
Purpose
Growing traffic in mobile networks requires more and more resources. Lack of resources will
affect user experience. This document provides guidelines on LTE FDD and LTE TDD
capacity monitoring including details on how to identify resource allocation problem and on
how to monitor network resource usage. Capacity monitoring provides data reference for
network reconfiguration and capacity expansion and enables maintenance personnel to take
measures before resources insufficiency affects network QoS and user experience.
NOTE
1. For details about the MML commands, parameters, alarms, and performance counters, see section
"Operation and Maintenance" in 3900 Series Base Station Product Documentation for 3900 series base
stations, BTS3202E Product Documentation for the BTS3202E.
2. The main control, transmission, and baseband processing units are deployed on the same board and share
the CPU for BTS3202E. The main control board and baseband board in this document are boards in
BTS3202E. The CPU usage of the main control board is the CPU usage of boards in BTS3202E.
3. This document does not apply to scenarios where a large amount of traffic volume is involved. For
guidance in these scenarios, contact Huawei technical support.
The following table lists the eNodeB types and the corresponding eNodeB models.
eNodeB Types
eNodeB Models
Macro
3900 series base stations, that is, BTS3900,

BTS3900A, BTS3900L, BTS3900AL, and
DBS3900
Micro
BTS3202E
LampSite
DBS3900 LampSite
Product Version
The following table lists the product version related to this document.
Issue 02 (2015-06-20)

ii
eRAN
About This Document
Product
Name
Solution Version
Product Version
BTS3900AL
l SRAN10.1
V100R010C10
BTS3900
l eRAN8.1
BTS3900A
BTS3900L
DBS3900
DBS3900
LampSite
BTS3202E
Intended Audience
This document is intended for:
l
Field engineers
Network planning engineers
Organization
1 Changes in eRAN Capacity Monitoring Guide
This section describes changes in each issue of this document.
2 Overview
This section describes the types of network resources to be monitored and the method of
performing capacity monitoring.
3 Network Resource Monitoring(FDD)
4 Network Resource Monitoring (TDD)
5 Resource Congestion Problem Identification
This section describes how to identify resource congestion problems. Network exceptions can
be found through KPI monitoring. If a KPI deteriorates, users can analyze relevant access
counters to decide whether the deterioration is caused by resource congestion.
6 Related Counters
Conventions
Symbol Conventions
Issue 02 (2015-06-20)

iii
eRAN
About This Document
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Issue 02 (2015-06-20)
Convention
Description
Boldface
The keywords of a command line are in boldface.

iv
eRAN
About This Document
Convention
Description
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl

+Alt+A means the three keys should be pressed
concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 02 (2015-06-20)

eRAN
Issue 02 (2015-06-20)
About This Document
Action
Description
Click
Select and release the primary mouse button without

moving the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.

vi
eRAN
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes in eRAN Capacity Monitoring Guide.......................................................................1
2 Overview......................................................................................................................................... 3
2.1 Network Resources(FDD).............................................................................................................................................. 4
2.2 Network Resources (TDD)............................................................................................................................................. 5
2.3 Capacity Monitoring Methods........................................................................................................................................8
3 Network Resource Monitoring(FDD)........................................................................................9

3.1 Overview...................................................................................................................................................................... 10
3.2 Downlink User Perception............................................................................................................................................12
3.3 User Capacity Usage.................................................................................................................................................... 13
3.4 PRACH Performance................................................................................................................................................... 15
3.5 PDCCH Resource Usage.............................................................................................................................................. 16
3.6 Throughput License Usage........................................................................................................................................... 18
3.7 Paging Resource Usage................................................................................................................................................ 19
3.8 Main-Control-Board CPU Usage................................................................................................................................. 20
3.9 Baseband-Processing-Unit CPU Usage........................................................................................................................21
3.10 Transport Resource Group Bandwidth Usage............................................................................................................ 23
3.11 Ethernet Port Bandwidth Usage..................................................................................................................................25
4 Network Resource Monitoring (TDD).................................................................................... 27

4.1 Introduction.................................................................................................................................................................. 28
4.2 User Throughput...........................................................................................................................................................31
4.3 RRC Connected User....................................................................................................................................................33
4.4 PRACH Resource Usage.............................................................................................................................................. 35
4.5 CCE Utilization Rate.................................................................................................................................................... 37
4.6 RRC Connected User License Utility Ratio................................................................................................................. 37
4.7 Traffic Volume License Utility Ratio........................................................................................................................... 38
4.8 Paging Resource Utility Ratio...................................................................................................................................... 39
4.9 CPU load Avg of MPT(%)........................................................................................................................................... 39
4.10 CPU load Avg of BBP(%).......................................................................................................................................... 40
4.11 Transport Resource Group Usage...............................................................................................................................41
4.12 Ethernet Port Traffic................................................................................................................................................... 43
Issue 02 (2015-06-20)

vii
eRAN
Contents
5 Resource Congestion Problem Identification........................................................................ 45

5.1 Resource Congestion Indicators................................................................................................................................... 46
5.1.1 RRC Resource Congestion Rate................................................................................................................................46
5.1.2 E-RAB Resource Congestion Rate............................................................................................................................46
5.2 Resource Allocation Problem Identification Process................................................................................................... 47
6 Related Counters......................................................................................................................... 48
Issue 02 (2015-06-20)

viii
eRAN
Changes in eRAN Capacity Monitoring

Guide
This section describes changes in each issue of this document.
02(2015-06-20)
This is the second official release.
Compared with issue 01 (2015-03-23), this issue includes the following information.
l
2.2 Network Resources (TDD)
Compared with issue 01 (2015-03-23), this issue includes the following changes.
Topic
Change Description
2.1 Network
Resources(FDD)
Changed name from "Network Resources" to "Network

Resources(FDD)".
3 Network Resource
Monitoring(FDD)
Changed name from "Capacity Monitoring" to "Capacity

Monitoring(FDD)".
6 Related Counters
Add related Counters of LTE TDD.
No information in issue 01 (2015-03-23) is deleted from this issue.
01(2015-03-23)
This is the first official release.
Compared with issue Draft A (2015-01-15), this issue does not include any new information
or deleted any issues.
Compared with issue Draft A (2015-01-15), this issue includes the following changes.
Issue 02 (2015-06-20)

eRAN
Topic
Change Description
3.8 Main-Control-Board
CPU Usage
Modified the monitoring principles of Main-Control-Board

CPU Usage.
3.9 Baseband-ProcessingUnit CPU Usage
Modified the monitoring principles of BasebandProcessing-Unit CPU Usage.
Draft A (2015-01-15)
This is a draft.
Compared with the multimode base station V100R009C00 and eNodeB V100R007C00, this
issue does not include any change.
Issue 02 (2015-06-20)

eRAN
2 Overview
Overview
About This Chapter

This section describes the types of network resources to be monitored and the method of
performing capacity monitoring.
2.1 Network Resources(FDD)
2.3 Capacity Monitoring Methods
Issue 02 (2015-06-20)

eRAN
2 Overview
2.1 Network Resources(FDD)

Figure 2-1 shows the resources to be monitored.
Figure 2-1 Network resources to be monitored
Table 2-1 describes the types of network resources to be monitored and impacts of resource
insufficiency on the system.
Table 2-1 Network resources
Issue 02 (2015-06-20)
Resource Type
Meaning
Impact of Resource
Insufficiency on the
System
Resource
Monitoring Item
Cell
resou
rces
Physical
resource
blocks
(PRBs)
Bandwidth
consumed on the
air interface
Users may fail to be

admitted, and
experience of admitted
users is affected.
3.2 Downlink User

Perception
Synchroniz
ed user
capacity
Maximum
number of
synchronized
users in a cell
User experience is
affected.
3.3 User Capacity

Usage

eRAN
2 Overview
Resource Type
eNod
eB
resou
rces
Meaning
Impact of Resource
Insufficiency on the
System
Resource
Monitoring Item
Physical
random
access
channel
(PRACH)
resources
Random access
preambles
carried on the
PRACH
Access delays are

prolonged, or even
access attempts fail.
3.4 PRACH
Performance
Physical
downlink
control
channel
(PDCCH)
resources
Downlink control
channel
resources
Uplink and downlink

scheduling delays are
prolonged, and user
experience is affected.
3.5 PDCCH
Resource Usage
Licensed
throughput
Maximum
throughput in an
eNodeB
User perception and

customer income are
affected.
3.6 Throughput
License Usage
Paging
resources
eNodeB paging
capacity
Paging messages may

be lost, affecting user
experience.
3.7 Paging Resource

Usage
Maincontrolboard CPU
Processing
capability of the
main control
board of the
eNodeB
KPIs deteriorate.
3.8 Main-ControlBoard CPU Usage
Basebandprocessingunit CPU
Processing
capability of the
baseband
processing unit
(BBP)
KPIs deteriorate.
3.9 BasebandProcessing-Unit CPU

Usage
Transport
resource
groups
eNodeB logical
transport
resources
Packets may be lost,

affecting user
experience.
3.10 Transport
Resource Group
Bandwidth Usage
Ethernet
ports
eNodeB physical
transport
resources
Packets may be lost,

affecting user
experience.
3.11 Ethernet Port

Bandwidth Usage

Figure 2-2 shows the network resources to be monitored.
Issue 02 (2015-06-20)

eRAN
2 Overview
Figure 2-2 Network resources to be monitored
Table 2-2 describes the types of network resources to be monitored and impacts of resource
insufficiency on the system.
Table 2-2 Network resources
Resource Type
Cell resources
Issue 02 (2015-06-20)
Meaning
Impact of
Resource
Insufficiency
on the System
Resource
Monitoring
Indicator
Physical
resource block
(PRB)
Physical
channels on the
air interface
Users may fail

to be admitted,
and experience
of admitted
users is
affected.
4.2 User
Throughput
Physical
random access
channel
(PRACH)
Random access
channel
Network access
fails and the
access delay is
prolonged.
4.4 PRACH
Resource
Usage

PRB usage
eRAN
2 Overview
Resource Type
eNodeB
resources
Issue 02 (2015-06-20)
Meaning
Impact of
Resource
Insufficiency
on the System
Resource
Monitoring
Indicator
Physical
downlink
control channel
(PDCCH)
Downlink
control channel
Uplink and
downlink
scheduling
delays are
prolonged, and
user experience
is affected.
4.5 CCE
Utilization
Rate
Connected user
Number of
RRC_CONNE
CTED users
The key
performance
indicators
(KPIs)
deteriorate, and
user experience
is affected.
4.3 RRC
Connected
User
Connected user
license
Maximum
number of users
that can be
served by the
eNodeB
New services
cannot be
admitted, and
experience of
admitted users
is affected.
4.3 RRC
Connected
User
Throughput
license
Maximum
traffic volume
supported by
the eNodeB
User experience
and customers'
income are
affected.
4.7 Traffic
Volume
License Utility
Ratio
Paging
eNodeB paging
capacity
Paging
messages may
be discarded,
and user
experience is
affected.
4.8 Paging
Resource
Utility Ratio
MPT CPU
Processing
capability of the
MPT in the
eNodeB
KPIs
deteriorate.
4.9 CPU load

Avg of
MPT(%)
BBP CPU
Processing
capability of the
BBPs in the
eNodeB
KPIs
deteriorate.
4.10 CPU load

Avg of
BBP(%)
Transport
resource group
Logic transport
resources of the
eNodeB
Exceptions such
as packet loss
occur, and user
experience is
affected.
4.11 Transport
Resource
Group Usage

eRAN
2 Overview
Resource Type
Ethernet port
Meaning
Impact of
Resource
Insufficiency
on the System
Resource
Monitoring
Indicator
Physical
transport
resources of the
eNodeB
Exceptions such
as packet loss
occur, and user
experience is
affected.
4.12 Ethernet
Port Traffic
2.3 Capacity Monitoring Methods

l
Daily monitoring for prediction

Counters are used to indicate the load or usage of various types of resources on the LTE
network. Thresholds for resource consumption are specified so that preventive measures
such as reconfiguration and expansion can be taken to prevent network congestion when
the consumption of a type of resource continually exceeds the threshold. For details, see
3 Network Resource Monitoring(FDD) and 4 Network Resource Monitoring (TDD).
Problem-driven analysis
This method helps identify whether a problem indicated by counters is caused by
network congestion through in-depth analysis. With this method, problems can be
precisely located so that users can work out a proper network optimization and
expansion solution. For details, see 5 Resource Congestion Problem Identification.
NOTE
1. Thresholds defined for resource monitoring are generally lower than those triggering alarms so that risks
of resource insufficiency can be detected as early as possible.
2. Thresholds given in this document apply to networks experiencing a steady growth. Thresholds are
determined based on product specifications and experiences in working with existing networks. For
example, the CPU usage threshold 60% is specified based on the CPU flow control threshold 80%. The
eNodeB's RRC connected user license usage threshold 60% is specified based on the peak-to-average
ratio (about 1.5:1). When the average usage reaches 60%, the peak usage approaches 100%. Threshold
determining considers both average and peak values.
3. Telecom operators are encouraged to formulate an optimization solution for resource capacity based on
prediction and analysis for networks that are experiencing fast development, scheduled to deploy new
services, or about to employ new charging plans. If you require services related to resource capacity
optimization, such as prediction, evaluation, optimization, reconfiguration, and capacity expansion,
contact Huawei technical support.
Issue 02 (2015-06-20)

eRAN
Network Resource Monitoring(FDD)
About This Chapter

3.1 Overview
This section describes monitoring principles and methods, as well as related counters, of all
types of service resources. Information about how to locate resource bottlenecks and the
related handling suggestions are also provided. Note that resource insufficiency may be
determined by usage of more than one type of service resource. For example, a resource
bottleneck can be claimed only when both RRC connected user license usage and maincontrol-board CPU usage exceed the predefined thresholds.
3.2 Downlink User Perception
3.3 User Capacity Usage
3.4 PRACH Performance
3.5 PDCCH Resource Usage
3.6 Throughput License Usage
3.7 Paging Resource Usage
3.8 Main-Control-Board CPU Usage
3.9 Baseband-Processing-Unit CPU Usage
3.10 Transport Resource Group Bandwidth Usage
3.11 Ethernet Port Bandwidth Usage
Issue 02 (2015-06-20)

eRAN
3.1 Overview
This section describes monitoring principles and methods, as well as related counters, of all
types of service resources. Information about how to locate resource bottlenecks and the
related handling suggestions are also provided. Note that resource insufficiency may be
determined by usage of more than one type of service resource. For example, a resource
bottleneck can be claimed only when both RRC connected user license usage and maincontrol-board CPU usage exceed the predefined thresholds.
NOTE
For accurate monitoring, all resources must be monitored during busy hours. It is recommended that busy
hours be defined as a period when the system or a cell is undergoing the maximum resource consumption of a
day.
Differences in Monitoring Between eNodeB Types

Table 3-1 lists the differences in monitoring between eNodeB types.
Table 3-1 Differences in monitoring between eNodeB types
Monitoring Item
Difference
Main-ControlBoard CPU Usage
If the main-control-board CPU usage of a Micro or LampSite

eNodeB reaches or exceeds a threshold, the problem cannot be solved
by replacing the main control board.
Thresholds and Handling Suggestions

Table 3-2 describes the thresholds and handling suggestions for the resources to be
monitored.
Table 3-2 Thresholds and handling suggestions for the resources to be monitored
Issue 02 (2015-06-20)
Res
ourc
e
Typ
e
Resource
Monitoring
Item
Conditions
Handling Suggestions
Cell
reso
urce
s
3.2
Downlink
User
Perception
User-perceived rate < n

Mbit/s (user-configurable)
Optimize RF performance, expand

the cell bandwidth, add carriers, or
add eNodeBs.

10
eRAN
Res
ourc
e
Typ
e
Resource
Monitoring
Item
Conditions
3.3 User
Capacity
Usage
l Synchronized user
capacity usage of a cell
60%
Optimize parameter settings,

optimize RF performance, expand
the cell bandwidth, add carriers, or
split cells.
l RRC connected user

capacity usage of a board
60%
l RRC connected user
license usage of an
eNodeB 60%
3.4 PRACH
Performanc
e
3.5 PDCCH
Resource
Usage
Conflict probability for

contention-based preambles
5%
(Optional) Enable the PRACH

resource adjustment algorithm.
Assignment success rate for

dedicated preambles < 99%
Enable the PRACH resource

adjustment algorithm and reuse of
dedicated preambles.
CCE usage
80%
Add carriers, split cells, or optimize

RF performance.
PDCCH
Symbol
Number
Adjust
Switchis set to
OFF(Off).
PDCCH
Symbol
Number
Adjust
Switchis set to
ON(On), and
uplink or
downlink PRB
usage reaches
or exceeds
70%.
eNo
deB
reso
urce
s
Issue 02 (2015-06-20)
3.6
Throughput
License
Usage
Throughput license usage

80%
Increase the licensed throughput.

11
eRAN
Res
ourc
e
Typ
e
Resource
Monitoring
Item
Conditions
3.7 Paging
Resource
Usage
Percentage of paging
messages received on the S1
interface 60%
Take one of the following

measures:
l Decrease the number of cells in
the tracking area list (TAL) that
the congested cell belongs to.
l Adjust the paging policy of the
core network to reduce signaling
overhead.
l If the core network is deployed
by Huawei, enable the precise
paging function.
3.8 MainControlBoard CPU

Usage
Average main-control-board
CPU usage 60% or
percentage of time the CPU
usage reaches or exceeds
85% 5%
Balance the loads, replace old

boards with those of higher
specifications, or add eNodeBs.
3.9
BasebandProcessingUnit CPU
Usage
Average baseband
processing unit (BBP) CPU
usage 60% or percentage
of time the CPU usage
reaches or exceeds 85%
5%
Add boards, replace old boards with

those of higher specifications, or
balance inter-BBP loads.
3.10
Transport
Resource
Group
Bandwidth
Usage
Proportion of average
transmission rate to
configured bandwidth
80% or Proportion of
maximum transmission rate
to configured bandwidth
90%
Expand the bandwidth of the

transport resource group.
3.11
Ethernet
Port
Bandwidth
Usage
Proportion of average
allocated bandwidth 70%
or Proportion of maximum
Expand the eNodeB transmission

capacity.
3.2 Downlink User Perception

Monitoring Principles
Issue 02 (2015-06-20)

12
eRAN
Growing traffic leads to a continuous increase in PRB usage, and UE rates decrease as an
increasing number of UEs share the limited PRBs. The PRB usage reflects the degree of
bandwidth usage over the air interface while the perceived-rate reflects user experience.
Monitoring the two items together can reflect user experience under a certain bandwidth
usage over the air interface.
As downlink is a major concern in an LTE network, this document describes only how to
monitor the user-perceived downlink rate.
NOTE
The monitoring principles also apply to uplink.
Monitoring Methods
The following items are used in monitoring this case:
l
Downlink PRB usage = L.ChMeas.PRB.DL.Used.Avg / L.ChMeas.PRB.DL.Avail x

100%
Downlink user-perceived rate (Mbit/s) = (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI) /

L.Thrp.Time.DL.RmvLastTTI / 1000
where, 15-minute statistical values are needed for the counters:

l
L.ChMeas.PRB.DL.Used.Avg indicates the average number of used downlink PRBs.
L.ChMeas.PRB.DL.Avail indicates the number of available downlink PRBs.
L.Thrp.bits.DL indicates the total downlink traffic volume for PDCP SDUs in a cell.
L.Thrp.bits.DL.LastTTI indicates the downlink traffic volume sent in the last TTI for
PDCP SDUs before the buffer is empty.
L.Thrp.Time.DL.RmvLastTTI indicates the data transmission duration except the last

TTI before the downlink buffer is empty.
Suggested Measures
If the downlink PRB usage reaches or exceeds 70% and the downlink user-perceived rate is
smaller than a user-defined threshold (3 Mbit/s by default) for X days (three days by default)
in a week:
l
If the average CQI of the cell is lower than the threshold (7 by default), you are advised
to increase the cell throughput by optimizing RF performance.
If the average CQI of the cell is higher than the threshold, you are advised to:
Add carriers or expand the bandwidth of the existing carrier.
Add eNodeBs.
The method of calculating the average CQI is as follows:

Average CQI = (Y x L.ChMeas.CQI.DL.Y) / (L.ChMeas.CQI.DL.Y)
In the preceding formula, L.ChMeas.CQI.DL.Y indicates the number of wideband CQI reports
with the value of Y.
3.3 User Capacity Usage

Issue 02 (2015-06-20)

13
eRAN
User capacity usage can be evaluated by the following three items:
l
Synchronized user capacity usage of a cell
RRC connected user capacity usage of a board
RRC connected user license usage of an eNodeB
An RRC connected user in the LTE is one who is in the RRC_Connected state, and a
synchronized user is an RRC connected user in the synchronization state. When the number of
users processed within a cell or by a board exceeds the maximum number defined in the
product specifications, network KPIs deteriorate. When the number of users processed by an
eNodeB exceeds the maximum number defined in the license, user admission failures.
NOTE
When the number of users reaches or exceeds the preconfigured threshold, the user-perceived rate has already
decreased to an unacceptable level. Therefore, the user-perceived rate should be considered first. The number
of users should be considered first when capacity takes priority over user experience.
Monitoring Methods
l

The calculation formula is as follows:
Synchronized user capacity usage of a cell = L.Traffic.User.Ulsync.Avg / Maximum
number of synchronized users in a cell x 100%
where
L.Traffic.User.Ulsync.Avg indicates the average number of uplink synchronized

users in a cell.
To learn the maximum number of synchronized users in a cell, see Technical

Specifications of the eNodeB FDD in 3900 Series Base Station Technical
Description.
RRC connected user capacity usage of a board

The RRC connected user capacity usage of a board involves the baseband processing
unit (BBP) and the main control board. The calculation formula is as follows:
RRC connected user capacity usage of a board = (L.Traffic.User.Avg) / Maximum
number of RRC connected users of a board x 100%
where
(L.Traffic.User.Avg) indicates the total number of RRC connected users in all

cells served by a board.
To learn the maximum number of RRC connected users of a BBP or main control
board, see Technical Specifications of the eNodeB FDD in 3900 Series Base Station
Technical Description.
RRC connected user license usage of an eNodeB

RRC connected user license usage of an eNodeB = (L.Traffic.User.Avg) / Number of
licensed RRC connected users of an eNodeB x 100%
where
Issue 02 (2015-06-20)
(L.Traffic.User.Avg) indicates the total number of RRC connected users in all

cells served by an eNodeB.
14
eRAN
The method of querying the licensed number of RRC connected users is as follows:
Run the command DSP LICINFO: FUNCTIONTYPE=eNodeB;. In the displayed
command output, view the line in which Model is LT1S0ACTUS00. The value in
the Allocated column is the number of licensed RRC connected users.
Suggested Measures
l
If the synchronized user capacity usage of a cell reaches or exceeds 60% for X days
(three days by default) in a week, you are advised to take either of the following
measures:
Release UEs in idle mode as early as possible: Reduce the UE inactivity timer
length by running the MOD RRCCONNSTATETIMER command with the
UeInactiveTimer parameter specified. This measure lifts signaling overhead and
increases CPU usage.
Transfer UEs out of the local cell: If a neighboring cell is lightly loaded, adjust the
antenna downtilt angle or decrease the transmit power of the local cell to shrink the
coverage area and reduce the number of users in the local cell. In addition, expand
the coverage area of the neighboring cell for load balancing.
Add cells or expand the local cell bandwidth.
Split the local cell into multiple cells.
If the RRC connected user capacity usage of a main control board reaches or exceeds
60% for X days (three days by default) in a week, you are advised to take measures
given in 3.8 Main-Control-Board CPU Usage.
If the RRC connected user capacity usage of a BBP reaches or exceeds 60% for X days
(three days by default) in a week, you are advised to take measures given in 3.9
Baseband-Processing-Unit CPU Usage.
If the RRC connected user license usage of an eNodeB reaches or exceeds 60% for X
days (three days by default) in a week, you are advised to determine the main-controlboard CPU usage first by referring to 3.8 Main-Control-Board CPU Usage:
If the main-control-board CPU usage is less than 60%, you are advised to expand
the capacity defined in the license.
If the main-control-board CPU usage reaches or exceeds 60%, you are advised to
add eNodeBs.
3.4 PRACH Performance

The physical random access channel (PRACH) transmits preambles during random access
procedures. Preamble is classified into contention preamble and non-contention preamble.
Contention preambles are used in the following scenarios: initial connection establishment,
reestablishment, handover, downlink data transmission for UEs in the out-of-synchronization
state, and uplink data transmission for UEs in the out-of-synchronization state. Noncontention preambles are used in two scenarios: handover and downlink data transmission for
UEs in the out-of-synchronization state. Therefore, PRACH performance can be measured
using the following factors:
l
Issue 02 (2015-06-20)
Conflict probability for contention-based preambles: The more frequently the

contention-based access is performed, the higher probability that the preambles are
15
eRAN
conflicted. When the conflict probability reaches a certain extent, the access delay
increases, severely affecting user experience.
l
Assignment success rate for dedicated preambles: The assignment success rate for
dedicated preambles decreases with the increase of non-contention-based accesses.
When the success rate decreases to a certain extent, the handover delay increases,
affecting user experience.
Monitoring Methods
l
Conflict probability for contention-based preambles =

L.RA.UeRaInfoRspWithCon.Num / L.RA.UeRaInfoRsp.Num x 100%
NOTE
Values of the counter in the formula takes effect only when the UeRaInforInqSwitch is set to on
and there are UEs supporting 3GPP Release 9 and later on the network. You can query the value of
the UeRaInforInqSwitch by running the LST CELLALGOSWITCH: LocalCellId=xxx;
command.
Assignment success rate for dedicated preambles =

L.RA.Dedicate.PreambleAssign.Num / L.RA.Dedicate.PreambleReq.Num x 100%
where
l
L.RA.UeRaInfoRspWithCon.Num indicates number of times the

UEInformationResponse message in which contentionDetected IE value is TRUE is
received, that is, the number of times the conflicting UEInformationResponse message is
received.
L.RA.UeRaInfoRsp.Num indicates the number of times the UEInformationResponse

message containing RACH information is received.
L.RA.Dedicate.PreambleAssign.Num indicates the number of times the non-connectionbased preambles are assigned.
L.RA.Dedicate.PreambleReq.Num indicates the number of times the non-contentionbased preamble is requested.
Suggested Measures
l
If the conflict probability for contention-based preambles reaches or exceeds 5% for

X days (three days by default) in a week, enable the RACH adjustment algorithm by
running the command MOD CELLALGOSWITCH: LocalCellId=x,
RachAlgoSwitch=RachAdjSwitch-1.
If the assignment success rate for dedicated preambles is less than 99% for X days
(three days by default) in a week, enable the RACH resource adjustment algorithm and
reuse of dedicated PRACH preambles between UEs by running the command MOD
CELLALGOSWITCH: LocalCellId=x, RachAlgoSwitch=RachAdjSwitch-1,
RachAlgoSwitch=MaksIdxSwitch-1;.
3.5 PDCCH Resource Usage

This capacity indicator measures the number of control channel elements (CCEs) that can be
used by the PDCCH. If the CCE usage is excessively high, CCEs may fail to be allocated to
Issue 02 (2015-06-20)

16
eRAN
the new UEs to be scheduled, which will result in a long service delay and unsatisfactory user
experience.
Monitoring Methods
The following item is used in monitoring this case:
CCE usage = (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed +
L.ChMeas.CCE.DLUsed) / measurement period (in the unit of second) / 1000 / Maximum
number of PDCCH CCEs x 100%
where
l
L.ChMeas.CCE.CommUsed indicates the number of PDCCH CCEs used for common

signaling.
L.ChMeas.CCE.ULUsed indicates the number of PDCCH CCEs used for uplink

scheduling.
L.ChMeas.CCE.DLUsed indicates the number of PDCCH CCEs used for downlink

scheduling.
Table 3-3 lists the maximum number of PDCCH CCEs in different configurations.
Table 3-3 Maximum number of PDCCH CCEs
System
Bandwidth
(Configurable
)
Ng
5 MHz
10 MHz
15 MHz
20 MHz
Issue 02 (2015-06-20)
Maximum Number of PDCCH CCEs

Number of
PDCCH
Symbols = 1
Number of
PDCCH
Symbols = 2
Number of
PDCCH
Symbols = 3
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
eRAN
System
Bandwidth
(Configurable
)
Ng
Maximum Number of PDCCH CCEs

Number of
PDCCH
Symbols = 1
Number of
PDCCH
Symbols = 2
Number of
PDCCH
Symbols = 3
17
50
84
13
46
80
In the preceding table:

l
The number of PDCCH symbols depends on the PDCCH Symbol Number Adjust
Switch parameter value, which can be queried by running the LST
CELLPDCCHALGO command.
If the parameter value is On, the number of PDCCH symbols is 3.
If the parameter value is Off, the number of PDCCH symbols is equal to the
PDCCH Initial Symbol Number parameter value.
The value of Ng is equal to the PHICH resource parameter value, which can be queried
by running the LST PHICHCFG command.
Suggested Measures
If the CCE usage during busy hours reaches or exceeds 80% for X days (three days by
default) in a week, perform the following operations:
l
If the PDCCH Symbol Number Adjust Switch parameter value is Off, you are advised
to set this parameter to On by running the command MOD CELLPDCCHALGO:
LocalCellId=x, PdcchSymNumSwitch=ON;.
If the PDCCH Symbol Number Adjust Switch parameter value is On, you are advised
to:
Add cells or split existing cells.
Optimize RF performance to reduce the interference to PDCCH from neighboring

cells.
3.6 Throughput License Usage

When the eNodeB throughput reaches or exceeds the licensed throughput, user perception and
customer income are affected.
Monitoring Methods
The following item is used in monitoring this case:
Throughput license usage of an eNodeB = (L.Thrp.bits.UL.PDCP.SDU + L.Thrp.bits.DL) /
(Licensed eNodeB throughput x measurement period (in the unit of second)) x 100%
where
Issue 02 (2015-06-20)

18
eRAN
L.Thrp.bits.UL.PDCP.SDU and L.Thrp.bits.DL the uplink traffic volume and downlink

traffic volume of a cell, respectively. (L.Thrp.bits.UL.PDCP.SDU + L.Thrp.bits.DL)
indicates the sum of uplink and downlink throughput of all cells served by an eNodeB.
The method of querying the licensed eNodeB throughput is as follows:

Run the command DSP LICINFO: FUNCTIONTYPE=eNodeB;. In the displayed
command output, view the line in which Model is LT1S0ACTUS00. The value in the
Allocated column is the licensed throughput of the eNodeB.
Suggested Measures
If the eNodeB throughput license usage reaches or exceeds 80% for X days (three days by
default) in a week, you are advised to increase the licensed throughput.
3.7 Paging Resource Usage

Paging messages are sent over the S1 interface. Therefore, paging resource usage can be
evaluated by the percentage of paging messages received on the S1 interface. If the number of
paging times exceeds the maximum, the paging messages sent from the eNodeB to UEs may
be discarded, resulting in a decreased call success rate.
On the eNodeB side, paging messages received by the main control board over the S1
interface will be finally sent over the air interface through the baseband processing unit
(BBP). If all the cells served by an BBU belong to the same tracking area identified by the
tracking area code (TAC), all the paging messages received by the main control board need to
be sent out through each BBP. Whether the paging messages can be sent out through the BBP
depends on the overall paging capability of the BBP.
The overall paging capability of the BBU is determined by the smaller specification between
the main control board and BBP. The specifications of the main control board and BBP are as
follows:
l
UMPT\LBBPd3\UBBPd: 2400 messages/second; LMPT\LBBPc\LBBPd1\LBBPd2:

1800 messages/second.
The eNodeBs BTS3202E can send a maximum of 500 paging messages per second.
Monitoring Methods
The paging resource usage is evaluated by the percentage of paging messages received on the
S1 interface. The calculation formula is as follows:
Percentage of paging messages received on the S1 interface = L.Paging.S1.Rx / measurement
period (in the unit of second) / Maximum number of paging messages that can be processed
per second x 100%
In the preceding formula, L.Paging.S1.Rx indicates the number of paging messages received
over the S1 interface.
Issue 02 (2015-06-20)

19
eRAN
Suggested Measures
If the percentage of paging messages received on the S1 interface reaches or exceeds 60%
for X days (three days by default) in a week, you are advised to take either of the following
measures:
l
Decrease the number of cells in the tracking area list (TAL) that the congested cell
belongs to.
Adjust the paging policy of the core network. That is, reduce the number of paging
messages sent after the first or second paging failures to reduce signaling overhead.
Enable the precise paging function if the core network is deployed by Huawei.
3.8 Main-Control-Board CPU Usage

The CPU usage of the main control board becomes high occasionally due to some reasons.
However, the occasional high CPU usage is not necessarily the basis for capacity expansion.
Therefore, the main-control-board CPU usage is jointly evaluated by the average maincontrol-board CPU usage and the percentage of times that the main-control-board CPU usage
reaches or exceeds a preconfigured threshold (85%).
The main-control-board CPU usage reflects the busy level of the eNodeB. If the main-controlboard CPUs are busy processing control plane or user plane data, signaling-related KPIs may
deteriorate, and UEs may experience a low access success rate, low E-RAB setup success
rate, or high service drop rate.
Monitoring Methods
The main-control-board CPU usage is evaluated by the average CPU usage and the percent of
times that the main-control-board CPU usage reaches or exceeds a preconfigured threshold
(85%).
l
Average CPU usage: VS.BBUBoard.CPULoad.Mean
Percentage of times that the main-control-board CPU usage reaches or exceeds a

preconfigured threshold (85%) = VS.BBUBoard.CPULoad.CumulativeHighloadCount /
Measurement period (in the unit of second) / 5 x 100%
where, VS.BBUBoard.CPULoad.CumulativeHighloadCount indicates the number of times

that the CPU usage of the board exceeds a preconfigured threshold.
Suggested Measures
The main-control-board CPU of a local eNodeB becomes overloaded if either of the following
conditions is met for X days (three days by default) in a week:
l
VS.BBUBoard.CPULoad.Mean reaches or exceeds 60%.
The percentage of times that the main-control-board CPU usage reaches or exceeds
85% is greater than or equal to 5%.
Take one of the following measures:

Issue 02 (2015-06-20)

20
eRAN
Figure 3-1 Suggested Measures
1.
Transfer UEs from the local eNodeB: If a neighboring eNodeB is lightly loaded, adjust
the antenna downtilt angles or decrease the transmit power of the local eNodeB to shrink
the coverage area and reduce the CPU load of the local eNodeB. In addition, expand the
coverage area of the neighboring eNodeB for load balancing.
2.
Replace the main control board with a UMPT: If the main control board is an LMPT,
replace it with a UMPT. This measure can not be used in BTS3202E.
3.
Add eNodeBs.
3.9 Baseband-Processing-Unit CPU Usage

The CPU usage of the baseband processing unit (BBP) becomes high occasionally due to
some reasons. However, the occasional high CPU usage is not necessarily the basis for
capacity expansion. Therefore, the BBP CPU usage is jointly evaluated by the average BBP
CPU usage and the percentage of times that the BBP CPU usage reaches or exceeds a
preconfigured threshold (85%).
This capacity indicator measures the BBP CPU usage. If the eNodeB receives too much
traffic, the BBP CPU responsible for user plane processing will be heavily loaded. As a result,
the eNodeB will experience a low RRC setup success rate, low E-RAB setup success rate,
low handover success rate, and high service drop rate.
Issue 02 (2015-06-20)

21
eRAN
Monitoring Methods
Based on the type of data processed by the BBP, the BBP CPU usage is classified into
control-plane CPU usage and user-plane CPU usage. The BBP CPU usage is jointly evaluated
by the average BBP CPU usage and the percentage of times that the BBP CPU usage reaches
or exceeds a preconfigured threshold (85%). The involved indicators are described as follows:
Control-plane CPU usage
l
Average control-plane CPU usage: VS.BBUBoard.CPULoad.Mean
Percentage of times that the control-plane CPU usage reaches or exceeds a preconfigured
threshold (85%) = VS.BBUBoard.CPULoad.CumulativeHighloadCount / Measurement
period (in the unit of second) / 5 x 100%
where, VS.BBUBoard.CPULoad.CumulativeHighloadCount indicates the number of times

that the CPU usage of the board exceeds a preconfigured threshold.
User-plane CPU usage
l
Average user-plane CPU usage: L.Traffic.Board.UPlane.CPULoad.AVG
Percentage of times that the user-plane CPU usage reaches or exceeds a preconfigured
threshold (85%) = L.Traffic.Board.UPlane.CPULoad.CumulativeHighloadCount /
Measurement period (in the unit of second) / 5 x 100%
where, L.Traffic.Board.UPlane.CPULoad.CumulativeHighloadCount indicates the number of

times that the user-plane CPU usage of the board exceeds a preconfigured threshold.
Suggested Measures
The BBP CPU of a local eNodeB becomes overloaded if either of the following conditions is
met for X days (three days by default) in a week:
l
VS.BBUBoard.CPULoad.Mean reaches or exceeds 60%.
The percentage of times that the BBP CPU usage reaches or exceeds 85% is greater
than or equal to 5%.
When the BBP CPU usage is high, you are advised to perform capacity expansion as follows:
Issue 02 (2015-06-20)

22
eRAN
Figure 3-2 Capacity Expansion
1.
Migrate cells in the eNodeB. If the eNodeB has multiple BBPs and one of them is
overloaded, move cells from the overloaded BBP to a BBP with a lighter load.
The BBP load can be indicated by the average CPU usage, the percentage of times that
the CPU usage reaches or exceeds a preconfigured threshold, or the number of cells
established on a BBP.
2.
Replace a BBP with low specifications with one with high specifications. For example, if
the BBP is an LBBPc, replace the LBBPc with an LBBPd or a UBBP. If the BBP is an
LBBPd, replace the LBBPd with a UBBP.
3.
Add a BBP. If the eNodeB has vacant slots, add a BBP and migrate existing cells to the
new BBP for load sharing.
4.
Add eNodeBs. Add an eNodeB for capacity expansion if the number of BBP boards has
reached the maximum value that can be added.To expand the capacity of a BTS3202E,
you can only add another BTS3202E.
3.10 Transport Resource Group Bandwidth Usage

A transport resource group carries a set of data streams, which can be local data or forwarded
data. Local data is classified into control plane, user plane, operation and maintenance (OM),
Issue 02 (2015-06-20)

23
eRAN
and IP clock data. Forwarded data is not divided into different types. Wen the proportion of
the transport resource group's transmission rate to the configured bandwidth (that is, the
transport resource group bandwidth usage) reaches a predefined value, data congestion may
occur, degrading the transmission quality and affecting eNodeB services. The transport
resource group bandwidth usage can be jointly evaluated by the proportion of the average
transmission rate to the configured bandwidth and the proportion of the maximum
transmission rate to the configured bandwidth.
Figure 3-3 shows the position of the transport resource group in the TCP/IP model.
Figure 3-3 Position of the transport resource group
Monitoring Methods
l
Proportion of the average transmission rate to the configured bandwidth =

VS.RscGroup.TxMeanSpeed / Bandwidth configured for the transport resource group x
100%
Proportion of the maximum transmission rate to the configured bandwidth =

VS.RscGroup.TxMaxSpeed / Bandwidth configured for the transport resource group x
100%
where
l
VS.RscGroup.TxMeanSpeed indicates the average transmission rate of a transport

resource group.
VS.RscGroup.TxMaxSpeed indicates the maximum transmission rate of a transport

resource group.
The bandwidth configured for a transport resource group can be queried by running the DSP
RSCGRP command.
In the command output, the value of Tx Bandwidth is the bandwidth configured for the
Suggested Measures
A transport resource group is congested if either of the following conditions is met:
Issue 02 (2015-06-20)

24
eRAN
The proportion of the average transmission rate to the configured bandwidth

reaches or exceeds 80% for five days in a week.
The proportion of the maximum transmission rate to the configured bandwidth reaches
or exceeds 90% for two days in a week.
When a transport resource group is congested, you are advised to expand the bandwidth of the
transport resource group by running the MOD RSCGRP command with the TXBW value set
to a larger value. If the problem persists after the bandwidth adjustment, you are advised to
expand the eNodeB bandwidth.
3.11 Ethernet Port Bandwidth Usage

The physical bandwidth of the eNodeB Ethernet ports is limited, and packet loss and long
service delay will occur if the downlink or uplink throughput exceeds the allocated
bandwidth, affecting user experience. By monitoring the proportion of the Ethernet ports' data
rate to the physical bandwidth, you can decided whether the Ethernet transmission is
congested.
Monitoring Methods
l
(Item 1) Proportion of the average uplink transmission rate to the allocated bandwidth =
VS.FEGE.TxMeanSpeed / Allocated bandwidth x 100%
(Item 2) Proportion of the maximum uplink transmission rate to the allocated bandwidth
= VS.FEGE.TxMaxSpeed / Allocated bandwidth x 100%
(Item 3) Proportion of the average downlink reception rate to the allocated bandwidth =
VS.FEGE.RxMeanSpeed / Allocated bandwidth x 100%
(Item 4) Proportion of the maximum downlink reception rate to the allocated bandwidth
= VS.FEGE.RxMaxSpeed / Allocated bandwidth x 100%
where,
l
VS.FEGE.TxMeanSpeed indicates the average transmission rate of an Ethernet port.
VS.FEGE.TxMaxSpeed indicates the maximum transmission rate of an Ethernet port.
VS.FEGE.RxMeanSpeed indicates the average reception rate of an Ethernet port.
VS.FEGE.RxMaxSpeed indicates the maximum reception rate of an Ethernet port.
The allocated bandwidth can be queried by referring to Table 3-4.

Table 3-4 Allocated bandwidth
Issue 02 (2015-06-20)
LR Switch Value
Main
Control
Board
Allocated Bandwidth
DISABLE
UMPT
Min(1.5 Gbit/s, the transmission bandwidth of the

Ethernet port)

25
eRAN
LR Switch Value
Main
Control
Board
Allocated Bandwidth
LMPT
l For items 1 and 2: 300 Mbit/s

ENABLE
Boards in
BTS3202E
UMPT
l For items 1 and 2: value of UL Committed

Information Rate(kbit/s)
l For items 3 and 4: value of DL Committed
Information Rate(kbit/s)
LMPT
Boards in
BTS3202E
where
l
You can run the LST LR command to query the values of LR Switch, UL Committed
Information Rate(kbit/s), and DL Committed Information Rate(kbit/s).
The types of main control boards can be queried by running the DSP BRD command
and checking the value of Config Type in the command output. Because there are
various types of boards in the baseband unit (BBU), you need to search in the output for
the main control board type.
Suggested Measures
You are advised to expand the eNodeB transmission capacity if either of the following
conditions is met:
l
The proportion of the average uplink transmission rate (or average downlink reception
rate) to the allocated bandwidth reaches or exceeds 70% for at least five days in a week.
The actually allocated bandwidth can be obtained from the operator.
The proportion of the maximum uplink transmission rate (or maximum downlink
reception rate) to the allocated bandwidth reaches or exceeds 85% for at least two days
in a week.
Issue 02 (2015-06-20)

26
eRAN
Network Resource Monitoring (TDD)
About This Chapter

4.1 Introduction
This section describes principles and methods, as well as related counters, for monitoring each
type of resources. Information about how to identify resource insufficiency and the related
handling suggestions are also provided. Resource insufficiency may be determined jointly by
more than one indicator. For example, a resource insufficiency problem can be claimed only
when both RRC Connected User License Utility Ratio and CPU load Avg of MPT(%) exceed
the predefined thresholds.
4.2 User Throughput
4.3 RRC Connected User
4.4 PRACH Resource Usage
4.5 CCE Utilization Rate
4.6 RRC Connected User License Utility Ratio
4.7 Traffic Volume License Utility Ratio
4.8 Paging Resource Utility Ratio
4.9 CPU load Avg of MPT(%)
4.10 CPU load Avg of BBP(%)
4.11 Transport Resource Group Usage
4.12 Ethernet Port Traffic
Issue 02 (2015-06-20)

27
eRAN
4.1 Introduction
This section describes principles and methods, as well as related counters, for monitoring each
type of resources. Information about how to identify resource insufficiency and the related
handling suggestions are also provided. Resource insufficiency may be determined jointly by
more than one indicator. For example, a resource insufficiency problem can be claimed only
when both RRC Connected User License Utility Ratio and CPU load Avg of MPT(%) exceed
the predefined thresholds.
NOTE
For accurate monitoring, busy hours must be determined. It is recommended that busy hours be defined
as a period when the system or a cell is undergoing the maximum resource consumption during a day.
The following table describes the thresholds and handling suggestions for the resources to be
monitored.
Table 4-1 Thresholds and handling suggestions for the resources to be monitored
Resource
Type
Resource
Monitoring
Indicator
Criteria for Determining

Resource Insufficiency
Handling
Suggestion
Cell resources
User
Throughput
Both conditions are met:
Add carriers or
eNodeBs.
l Downlink PRB usage 30%

l Downlink user-perceived rate <
5 Mbit/s (customized)
Competitive
Preamble
Utilization
Rate, Dedicated
Preamble
Utilization Rate
Issue 02 (2015-06-20)
Usage of preambles for

contention-based random access
75%
Enable the
PRACH
backoff
algorithm.
Usage of preambles for noncontention-based random access

75%
Enable the
PRACH
resource
adjustment
algorithm and
dedicated
preamble
multiplexing
algorithm.

28
eRAN
Resource
Type
Resource
Monitoring
Indicator

Handling
Suggestion
CCE Utilization
Rate
CCE Utilization
Rate 70%
Downlink PRB
usage < 50%
Enable PDCCH
symbol
adaptation, or
perform RF
optimization to
reduce the
interference
from
neighboring
cells to the
PDCCH.
Uplink or
downlink PRB
usage 50%
Expand
capacity, add
carriers, or split
cells.
RRC Connected
User
Uplink CCE power usage > 60%
Perform RF or
parameter
optimization,
add carrier or
eNodeBs, or
increase the
bandwidth.
Downlink CCE power usage >

60%
Perform RF or
parameter
optimization,
add carrier or
eNodeBs, or
increase the
bandwidth.
1. Synchronized user capacity

usage of a cell 60%
Perform RF or
parameter
optimization,
add carrier or
eNodeBs, or
increase the
bandwidth.
2. RRC connected user capacity

usage of a board 60%
3. RRC connected user license
usage of an eNodeB 60%
eNodeB
resources
Issue 02 (2015-06-20)
RRC Connected
User License
Utility Ratio
RRC Connected
User License
Utility Ratio
60%
CPU load Avg

of MPT(%) <
60%
Increase the
licensed
number of
RRC_CONNE
CTED users.
CPU load Avg

of MPT(%)
60%
Add eNodeBs.

29
eRAN
Resource
Type
Resource
Monitoring
Indicator

Handling
Suggestion
Traffic Volume
License Utility
Ratio
Traffic Volume License Utility

Ratio 80%
Increase the
licensed traffic
volume.
Paging
Resource
Utility Ratio
Percentage of paging messages

received on the S1 interface 60%
Decrease the
number of cells
in the tracking
area list (TAL)
to which the
congested cell
belongs.
CPU load Avg

of MPT(%)
One of the following conditions is

met:
Enable load
balancing, use
MPTs with
higher
specifications to
replace original
ones, or add
eNodeBs.
l CPU load Avg of MPT(%)

60%
l Percentage of the number of
times that the CPU load Avg of
MPT(%) exceeds the threshold
(85%) 5%
CPU load Avg
of BBP(%)

met:
l CPU load Avg of BBP(%)
60%
l Percentage of the number of
times that the CPU load Avg of
BBP(%) exceeds the threshold
(85%) 5%
Transport
resource group

met:
l Packet loss rate (PLR) 0.05%
l Proportion of the average
transmission rate to configured
bandwidth 80%
Enable interBBP load

balancing, use
BBPs with
higher
specifications to
replace original
ones, or add
BBPs.
Increase the
bandwidth of
the transport
resource group.
l Proportion of the maximum

transmission rate to configured
bandwidth 90%
Issue 02 (2015-06-20)

30
eRAN
Resource
Type
Resource
Monitoring
Indicator

Handling
Suggestion
Ethernet port

met:
Expand the
eNodeB
transmission
capacity.
l Proportion of uplink or
downlink average transmission
rate to the allocated bandwidth
70%
l Proportion of uplink or
downlink maximum
transmission rate to the
4.2 User Throughput

User quantity growth leads to a continuous increase in the PRB usage. If the PRB usage
approaches 100%, user-perceived rates will decrease due to insufficient PRBs.
Monitoring Methods
Uplink and downlink user perception are evaluated based on the uplink and downlink PRB
usages and user-perceived rates, which are calculated using the following formulas:
l
Downlink user-perceived rate (Mbit/s) = L.Thrp.bits.DL/L.Thrp.Time.DL/1000
Uplink user-perceived rate (Mbit/s) = L.Thrp.bits.UL/L.Thrp.Time.UL/1000 x Uplink

coefficient
Downlink PRB usage = L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail x

100%
Uplink PRB usage = L.ChMeas.PRB.UL.Used.Avg/L.ChMeas.PRB.UL.Avail x 100%
Downlink spectral efficiency (bit/Hz) = L.Thrp.bits.DL/3600/

L.ChMeas.PRB.DL.DrbUsed.Avg x L.ChMeas.PRB.DL.Avail/Carrier bandwidth/
Downlink coefficient
Uplink spectral efficiency (bit/Hz) = L.Thrp.bits.UL/3600/

L.ChMeas.PRB.UL.DrbUsed.Avg x L.ChMeas.PRB.UL.Avail/Carrier bandwidth/Uplink
coefficient
In the preceding formulas,

l
Issue 02 (2015-06-20)
The related counters are described as follows:
L.ChMeas. PRB.DL.Used.Avg indicates that the average number of used downlink

PRBs.
L.ChMeas.PRB.DL.Avail indicates the number of available downlink PRBs.
L.ChMeas.PRB.UL.Used.Avg indicates that the average number of used uplink

PRBs.
31
eRAN
L.ChMeas.PRB.UL.Avail indicates the number of available uplink PRBs.
L.Thrp.bits.DL indicates the total downlink data throughput at the PDCP layer in a
cell.
L.Thrp.Time.DL indicates the duration for transmitting downlink data at the PDCP
layer in a cell.
L.Thrp.bits.UL indicates the total uplink data throughput at the PDCP layer in a
cell.
L.Thrp.Time.UL indicates the duration for transmitting uplink data at the PDCP
layer in a cell.
L.ChMeas.PRB.DL.DrbUsed.Avg indicates the average number of PRBs used by

PDSCH DRBs.
L.ChMeas.PRB.UL.DrbUsed.Avg indicates the average number of PRBs used by

PUSCH DRBs.
The uplink and downlink coefficients vary with uplink-downlink subframe

configurations. Table 4-2 lists the values of the uplink and downlink coefficients.
Table 4-2 Uplink and downlink coefficients
UplinkDownlink
Subframe
Assignment
UplinkDownlink
Subframe
Configuration
Uplink
Coefficient
Downlink
Coefficient
SA0
3:1
0.6
0.2
SA1
2:2
0.4
0.4
SA2
1:3
0.2
0.6
SA3
3:6
0.3
0.6
SA4
2:7
0.2
0.7
SA5
1:8
0.1
0.8
SA6
5:3
0.5
0.3
Suggested Measures
If the downlink PRB usage is greater than or equal to 30% and a user-perceived rate is smaller
than the user rate threshold (which is customized and set to 5 Mbit/s by default):
l
If the spectral efficiency in the cell is smaller than 1.3 bit/Hz, increase the throughput by
performing RF optimization or adding eNodeBs.
If the spectral efficiency in the cell is greater than or equal to 1.3 bit/Hz:
Add carriers or increase the carrier bandwidth.
Add eNodeBs.
The downlink PRB usage threshold varies with the downlink user rate threshold, according to
the following chart. Eg: If the customer requires that the downlink user rate threshold be set to
2 Mbit/s, the downlink PRB usage threshold must be changed to 50%.
Issue 02 (2015-06-20)

32
eRAN
Table 4-3 Downlink PRB usage threshold varying with the downlink user rate threshold
Downlink User Rate Threshold
(Mbit/s)
Downlink PRB Usage Threshold
60%
50%
43%
37%
30%
25%
20%
4.3 RRC Connected User

This indicator represents the number of RRC_CONNECTED users in a cell. When the
number of RRC_CONNECTED users in a cell exceeds the maximum number defined in the
product specifications, cell KPIs deteriorate. RRC_CONNECTED users include synchronized
users and users in the out-of-synchronization state. Synchronized users consume air interface
resources and therefore the number of synchronized users needs to be monitored. By default,
the number of synchronized users is approximately equal to the number of
RRC_CONNECTED users. Therefore, the number of RRC_CONNECTED users (instead of
synchronized users) is monitored.
User capacity usage can be evaluated by the following three items:
l
RRC_CONNECTED user capacity usage of a board
RRC_CONNECTED user license usage of an eNodeB

NOTE
When the number of RRC_CONNECTED users in a cell reaches or exceeds the preconfigured
threshold, the user-perceived rate has already decreased to an unacceptable level. Therefore, the userperceived rate should be preferentially considered. The number of RRC_CONNECTED users in a cell
can be preferentially considered when the capacity of a cell takes priority over user experience.
Monitoring Methods
l

Synchronized user capacity usage of a cell = L.Traffic.User.Max/Synchronized user
capacity of a cell x 100%
where
L.Traffic.User.Max indicates the maximum number of uplink synchronized users in a
cell.
Issue 02 (2015-06-20)

33
eRAN
The following table lists the synchronized user capacity of a cell.
BBP Model
Item
Number of
Users
Supported
by a Single
Cell
LBBPc
Combined cell (one to

six single-channel or
dual-channel RRUs)
Number of
RRC_CONNECTED
users
400
LBBPd4
Combined cell (one to

six single-channel or
dual-channel RRUs)
Number of
RRC_CONNECTED
users
600
UBBPd9
Combined cell (1 to 12
single-channel or dualchannel RRUs)
Number of
RRC_CONNECTED
users
1200
RRC_CONNECTED user capacity usage of a board

The RRC_CONNECTED user capacity usage of a board includes the capacity usage of
the baseband processing unit (BBP) and that of the main control board. The calculation
formula is as follows:
RRC_CONNECTED user capacity usage of a board = (L.Traffic.User.Max)/
RRC_CONNECTED users capacity of a board x 100%
where
(L.Traffic.User.Avg) indicates the total number of RRC_CONNECTED users in

all cells served by a board.
The following table lists the RRC_CONNECTED user capacity of a board.

BBP Model
Item
LBBPc
Combined cell (one

to six single-channel
or dual-channel
RRUs)
Number of
RRC_CONNEC
TED users
600
LBBPd4
Combined cell (one

to six single-channel
or dual-channel
RRUs)
Number of
RRC_CONNEC
TED users
1800
UBBPd9
Combined cell (1 to
12 single-channel or
dual-channel RRUs)
Number of
RRC_CONNEC
TED users
3600
Number of
Users Supported
by a Single Cell
RRC_CONNECTED user license usage of an eNodeB

Issue 02 (2015-06-20)

34
eRAN
RRC_CONNECTED user license usage of an eNodeB = L.Traffic.User.Max/Number

of licensed RRC_CONNECTED users of an eNodeB x 100%
where
(L.Traffic.User.Avg) indicates the total number of RRC_CONNECTED users in

all cells served by an eNodeB.
The method of querying the licensed number of RRC_CONNECTED users is as

follows:
Run the DSP LICINFO command with the FUNCTIONTYPE parameter set to
eNodeB. In the displayed command output, view the line in which Model is
LT1S0ACTUS00. The value in the Allocated column is the number of licensed
RRC_CONNECTED users.
Suggested Measures
If the synchronized user capacity usage of a cell exceeds 60%, take the following measures:
l
Reduce the UE inactivity timer length by running the MOD

RRCCONNSTATETIMER command with the UeInactiveTimer parameter specified.
This measure increases the signaling overhead and CPU usage.
If a neighboring cell is lightly loaded, adjust the antenna downtilt or decrease the
transmit power of the local cell to reduce the coverage area and to reduce the number of
users in the local cell, and expand the coverage area of the neighboring cell for load
sharing.
Add carriers or increase the carrier bandwidth.
Split the local cell into multiple cells.
If the RRC_CONNECTED user capacity usage of a main control board reaches or

exceeds 60% for X days (three days by default) in a week, take measures given in 4.9
CPU load Avg of MPT(%).
If the RRC_CONNECTED user capacity usage of a BBP reaches or exceeds 60% for X
days (three days by default) in a week, you are advised to take measures given in 4.10
CPU load Avg of BBP(%).
If the RRC_CONNECTED user license usage of an eNodeB reaches or exceeds 60% for
X days (three days by default) in a week, you are advised to determine the main-controlboard CPU usage first by referring to 4.9 CPU load Avg of MPT(%).
If CPU load Avg of MPT(%) is less than 60%, increase the number of licensed
If CPU load Avg of MPT(%) reaches or exceeds 60%, you are advised to add
eNodeBs.
4.4 PRACH Resource Usage

The PRACH transmits preambles during random access procedures.
l
Issue 02 (2015-06-20)
If the number of contention-based random access attempts per second reaches or exceeds
N (which is set during preamble design to meet the requirement that the conflict
probability is less than 1%), the conflict probability increases and the access delay is
prolonged during UE-initiated random access.
35
eRAN
If the number of non-contention-based random access attempts per second is greater than
or equal to 100, no dedicated preambles can be allocated to UEs. In this case, the
eNodeB instructs UEs to initiate contention-based random access. The total access delay
is prolonged. In handover scenarios, the handover delay is prolonged.
Monitoring Methods
The PRACH resource usage is evaluated based on the usage of preambles for contentionbased or non-contention-based random access, which is calculated using the following
formulas:
l
Usage of preambles for contention-based random access =

(L.RA.GrpA.Att + L.RA.GrpB.Att)/3600/N x 100%
Usage of preambles for non-contention-based random access = L.RA.Dedicate.Att/

3600/100 x 100%

l
L.RA.GrpA.Att indicates the number of times that the preamble in group A for
contention-based random access is received.
L.RA.GrpB.Att indicates the number of times that the preamble in group B for
contention-based random access is received.
L.RA.Dedicate.Att indicates the number of times that the preamble for non-contentionbased random access is received.
The value of N is specified as follows:
When the system bandwidth is 15 MHz or 20 MHz, the value of N is 100.
When the system bandwidth is 5 MHz or 10 MHz, the value of N is 50 if the

PRACH resource adjustment algorithm is disabled, or is 100 if the PRACH
resource adjustment algorithm is enabled. To check whether the PRACH resource
adjustment algorithm is enabled, run the LST CELLALGOSWITCH command and
then view the setting of the RachAlgoSwitch parameter.
Suggested Measures
l
When the usage of preambles for contention-based random access is greater than or
equal to 75% in X (configurable, 3 by default) days in a week, run the following
command to enable the PRACH backoff algorithm, which decreases the peak load and
average delay on the RACH:
MOD CELLALGOSWITCH: LocalCellId=x, RachAlgoSwitch=BackOffSwitch-1;
In this case, if the system bandwidth is 5 MHz or 10 MHz, run the following command
to enable the PRACH resource adjustment algorithm:
MOD CELLALGOSWITCH: LocalCellId=x, RachAlgoSwitch= RachAdjSwitch-1;
When the usage of preambles for non-contention-based random access is greater than or
equal to 75% in X (configurable, 3 by default) days in a week, run the following
command to enable the PRACH resource adjustment algorithm and dedicated preamble
multiplexing algorithm, which reduce the probability that UEs use preambles for
contention-based random access and decrease the access delay for UEs:
MOD CELLALGOSWITCH: LocalCellId=x, RachAlgoSwitch= RachAdjSwitch-1,
RachAlgoSwitch=MaksIdxSwitch-1;
Issue 02 (2015-06-20)

36
eRAN
4.5 CCE Utilization Rate

This indicator measures the number of control channel elements (CCEs) that can be used by
the PDCCH.
In each radio frame, the eNodeB allocates CCEs to UEs to be scheduled in the uplink and
downlink, and to other common control signaling. The number of CCEs for the PDCCH must
be properly configured and allocated to minimize the downlink control overhead 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 increase the scheduling delay and affect user experience. If the number of PDCCH
symbols is excessive (indicating that the PDCCH CCE usage is low), resources that can be
used by PDSCH decreases, which will decrease the spectral efficiency.
Monitoring Methods
The PDCCH resource usage is evaluated using the CCE Utilization Rate, which is calculated
using the following formula:
CCE Utilization Rate =
(L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed)/
L.ChMeas.CCE.Avail x 100%
In the preceding formula,
l
L.ChMeas.CCE.CommUsed indicates the number of CCEs used for common signaling.
L.ChMeas.CCE.ULUsed indicates the number of CCEs used for uplink scheduling.
L.ChMeas.CCE.DLUsed indicates the number of CCEs used for downlink scheduling.
L.ChMeas.CCE.Avail indicates the number of available CCEs.
Suggested Measures
If CCE Utilization Rate is greater than 50%:
l
If PDCCH symbol adaptation is disabled, run the following command to enable this
function:
MOD CELLPDCCHALGO:LocalCellId=x,PdcchSymNumSwitch=ON;
If PDCCH symbol adaptation is enabled and the downlink or uplink PRB usage is
greater than 50%, expand capacity, add carrier, or split cells. Otherwise, perform RF
optimization to reduce interference from neighboring cells to the PDCCH.
4.6 RRC Connected User License Utility Ratio

The RRC_CONNECTED user license specifies the maximum allowable number of
RRC_CONNECTED users. If the RRC Connected User License Utility Ratio exceeds a
preconfigured threshold, users may fail to access the network.
Issue 02 (2015-06-20)

37
eRAN
Monitoring Methods
The RRC Connected User License Utility Ratio is calculated using the following formula:
RRC Connected User License Utility Ratio = (L.Traffic.User.Avg)/Licensed number of
RRC_CONNECTED users x 100%
In the preceding formula:
l
L.Traffic.User.Avg indicates the average number of users in a cell.
(L.Traffic.User.Avg) indicates the sum of the average number of RRC_CONNECTED

users in each cell under an eNodeB.
The licensed number of RRC_CONNECTED users can be queried by running the

following command:
DSP LICENSE: FUNCTIONTYPE=eNodeB;
In the command output, the value in the Allocated column corresponding
to LLT1ACTU01 is the licensed number of RRC_CONNECTED users.
Suggested Measures
In addition to this indicator, also consider CPU load Avg of MPT(%) for capacity expansion.
If the RRC Connected User License Utility Ratio reaches or exceeds 60% in X (configurable,
3 by default) days in a week, you are advised to take the following measures:
l
If CPUload Avg of MPT(%) is less than 60%, increase the licensed number of
If CPU load Avg of MPT(%) reaches or exceeds 60%, add eNodeBs.
For details about CPU load Avg of MPT(%), see CPU load Avg of MPT(%).
4.7 Traffic Volume License Utility Ratio

When the throughput of an eNodeB reaches or exceeds the licensed volume, the eNodeB
performs flow control, which affects user experience and customer income.
Monitoring Methods
The Traffic Volume License Utility Ratio is calculated using the following formula:
Traffic Volume License Utility Ratio = (L.Thrp.bits.UL + L.Thrp.bits.DL)/(Licensed
eNodeB throughput volume x 3600) x 100%
In the preceding formula,
l
Issue 02 (2015-06-20)
The related counters are described as follows:
L.Thrp.bits.UL and L.Thrp.bits.DL indicate the uplink throughput volume and

downlink throughput volume of a cell, respectively.
(L.Thrp.bits.UL + L.Thrp.bits.DL) indicates the sum of uplink and downlink

traffic volumes of all cells under an eNodeB.
38
eRAN
The licensed eNodeB traffic volume can be queried by running the following command:
DSP LICENSE: FUNCTIONTYPE=eNodeB;
In the command output, the value in the Allocated column corresponding
to LLT1THRUL01 is the licensed eNodeB traffic volume.
Suggested Measures
If the Traffic Volume License Utility Ratio in busy hours reaches or exceeds 80% in X
(configurable, 3 by default) days in a week, increase the licensed eNodeB traffic volume.
4.8 Paging Resource Utility Ratio

The eNodeB can send a maximum of 750 paging messages per second. If the number of
paging messages to be sent exceeds this specification, the eNodeB may discard paging
messages to be sent to UEs, resulting in a decreased connection success rate.
Monitoring Methods
The Paging Resource Utility Ratio is evaluated by the value of L.Paging.Dis.Num and the
percentage of paging messages received on the S1 interface, which is calculated using the
following formula:
Percentage of paging messages received on the S1 interface = L.Paging.S1.Rx/3600/
Maximum number of paging messages that can be sent per second x 100%
In the preceding formula, L.Paging.S1.Rx indicates the number of paging messages that the
eNodeB receives on the S1 interface.
Suggested Measures
If the percentage of paging messages received on the S1 interface per day reaches or exceeds
60% for X (configurable, 3 by default) days in a week, take the following measures:
l
Decrease the number of cells in the TAL to which the congested cell belongs.
Modify the paging policies on the core network side to reduce the number of re-pagings
upon paging failures to decrease the signaling load.
Enable the precise paging function if the core network is provided by Huawei.
4.9 CPU load Avg of MPT(%)

The CPU usage reflects the busy level of the eNodeB. If the eNodeB's CPUs for signaling and
data processing are heavily loaded, signaling-related KPIs deteriorate, and users may
experience a low access success rate, low E-RAB setup success rate, or high service drop rate.
Operators can determine whether signaling-related KPI deterioration is caused by insufficient
MPT CPU processing capability or poor radio conditions. Determine the cause of the
deterioration as follows:
Issue 02 (2015-06-20)

39
eRAN
If the MCS measurement and initial-transmission failure measurement indicate that the
channel quality is poor, KPI deterioration may not be caused by insufficient MPT CPU
processing capability, but by deterioration in channel quality.
If the KPIs deteriorate and the CPU load Avg of MPT(%) exceeds a preconfigured
threshold, KPI deterioration may be caused by insufficient MPT CPU processing
capability. In this situation, perform capacity expansion according to Suggested
Measures.
Monitoring Methods
The CPU load Avg of MPT(%) is evaluated by the following factors:
l
VS.BBUBoard.CPULoad.Mean, which indicates the average CPU usage of boards.
Percentage of the number of times that the CPU load Avg of MPT(%) exceeds the
threshold (85%), which is calculated using the following formula:
Percentage of the number of times that the CPU load Avg of MPT(%) exceeds the
threshold (85%) = VS.Board.CPULoad.CumulativeHighloadCount/(3600/5) x 100%
In the preceding formula, VS.Board.CPULoad.CumulativeHighloadCount indicates the

number of times that the CPU usage of boards exceeds a preconfigured threshold.
Suggested Measures
Take measures if either of the following conditions is met:
l
The CPU load Avg of MPT(%) (VS.Board.CPUload.Mean) reaches or exceeds 60% in X

(configurable, 3 by default) days in a week.
The percentage of the number of times that the CPU load Avg of MPT(%) exceeds the
threshold (85%) reaches or exceeds 5% in X (configurable, 3 by default) days in a week.
The following measures are suggested:

l
If a neighboring eNodeB is lightly loaded, adjust the antenna downtilt or decrease the
power to reduce the local eNodeB's coverage area and to decrease the CPU load of the
local eNodeB. At the same time, expand the coverage area of the neighboring eNodeB to
share the load.
If the LMPT is used, replace it with the UMPT.
Add eNodeBs at existing or new sites.
4.10 CPU load Avg of BBP(%)

If the eNodeB receives too much traffic, the BBP CPU for user-plane data processing is
heavily loaded. In this case, the eNodeB has a low RRC connection setup success rate, low ERAB setup success rate, low handover success rate, and high service drop rate.
Monitoring Methods
The CPU load Avg of BBP(%) is evaluated by the following factors:
l
Issue 02 (2015-06-20)
VS.BBUBoard.CPULoad.Mean, which indicates the average CPU usage of boards.

40
eRAN
Percentage of the number of times that the CPU load Avg of BBP(%) exceeds the
threshold (85%), which is calculated using the following formula:
Percentage of the number of times that the CPU load Avg of BBP(%) exceeds the
threshold (85%) = VS.Board.CPULoad.CumulativeHighloadCount/3600 x 100%
In the preceding formula, VS.Board.CPULoad.CumulativeHighloadCount indicates the

number of times that the CPU usage of boards exceeds a preconfigured threshold.
Suggested Measures
The BBP CPU is heavily loaded if either of the following conditions is met:
l
The CPU load Avg of BBP(%) (VS.Board.CPUload.Mean) reaches or exceeds 60% in X

(configurable, 3 by default) days in a week.
The percentage of the number of times that the CPU load Avg of BBP(%) exceeds the
threshold (85%) reaches or exceeds 5% in X (configurable, 3 by default) days in a week.
In this case, expand the eNodeB user-plane capacity. The following measures are suggested
for capacity expansion:
l
If the LBBPc is used, replace it with the LBBPd.
Add BBPs to share the network load.
If the radio resources are sufficient (that is, all the indicators related to air-interface
resource usage do not exceed the thresholds), transfer a cell established on the existing
BBP to the new BBP.
If the radio resources are insufficient, establish new cells on the new BBP.
If the eNodeB has multiple BBPs and one of them is overloaded, transfer the cells
established on the overloaded BBP to a BBP with a lighter load.
The BBP load can be evaluated based on the average CPU usage, the percentage of times
that the CPU usage exceeds the threshold, or the number of cells established on a BBP.
If the eNodeB already has six (maximum number) BBPs and more BBPs are required,
add eNodeBs.
4.11 Transport Resource Group Usage

A transport resource group carries a set of data streams, which can be local control-plane,
user-plane, operation and maintenance (OM), and IP clock data or bypass data (data types not
considered). If a transport resource group is congested, it cannot transmit or forward data,
which affects service provision.
The usage of each transport resource group is monitored based on the packet loss rate and the
proportion of the transmission rate to the bandwidth configured for the transport resource
group.
Figure 2-1 shows the position of transport resource groups in the TCP/IP model.
Issue 02 (2015-06-20)

41
eRAN
Figure 4-1 Position of transport resource groups in the TCP/IP model
Monitoring Methods
The packet loss rate and the proportion of the transmission rate to the bandwidth configured
for the transport resource group are calculated using the following formulas:
l
Packet loss rate = VS.RscGroup.TxDropPkts/VS.RscGroup.TxPkts x100%
Proportion of the average transmission rate to the configured bandwidth =

VS.RscGroup.TxMeanSpeed/Bandwidth configured for the transport resource group x
100%
Proportion of the maximum transmission rate to the configured bandwidth =

VS.RscGroup.TxMaxSpeed/Bandwidth configured for the transport resource group x
100%
VS.RscGroup.TxDropPkts indicates the number of packets discarded due to failed

transmissions using the resource group.
VS.RscGroup.TxPkts indicates the number of packets transmitted using the

resource group.
VS.RscGroup.TxMeanSpeed indicates the average transmission rate of the resource
group.
VS.RscGroup.TxMaxSpeed indicates the maximum transmission rate of the

resource group.
The bandwidth configured for a transport resource group can be queried by running the
following command:
DSP RSCGRP: CN=x, SRN=x, SN=x, BEAR=xx, SBT=xxxx, PT=xxx;
In the command output, the value of Tx Bandwidth is the bandwidth configured for the
Suggested Measures
The measurement counters VS.RscGroup.TxMeanSpeed,VS.RscGroup.TxMaxSpeed,
VS.RscGroup.TxPkts, and VS.RscGroup.TxDropPkts are used to monitor the traffic of
Issue 02 (2015-06-20)

42
eRAN
transport resource groups. A transport resource group is congested if either of the following
conditions is met:
l
The proportion of the average transmission rate to the configured bandwidth reaches or
exceeds 80% in five days in a week.
The proportion of the maximum transmission rate to the configured bandwidth reaches
or exceeds 90% in two days in a week.
When a transport resource group is congested, increase the bandwidth of the transport
resource group by running the following command with TXBW set to a larger value:
MOD RSCGRP: CN=x, SRN=x, SN=x, BEAR=IP, SBT=BASE_BOARD, PT=ETH, PN=x,
RSCGRPID=x, RU=x, TXBW=xxxx, RXBW=xxxx;
If the congestion persists after the bandwidth adjustment, expand the eNodeB bandwidth.
4.12 Ethernet Port Traffic

The eNodeB Ethernet port traffic is the channel traffic at the physical layer, including uplink
traffic and downlink traffic. It reflects the throughput and communication quality of the
Ethernet ports on the MPT 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 meets the requirements for uplink and downlink transmissions.
Monitoring Methods
The proportion of the uplink or downlink transmission rates to the transmission bandwidth
allocated to the eNodeB is used to evaluate the Ethernet port resources usage. The proportion
is calculated using the following formulas:
l
(Formula 1) Proportion of the uplink average transmission rate to the allocated

bandwidth = VS.FEGE.TxMeanSpeed/Bandwidth allocated to the eNodeB x 100%
(Formula 2) Proportion of the uplink maximum transmission rate to the allocated

bandwidth = VS.FEGE.TxMaxSpeed/Bandwidth allocated to the eNodeB x 100%
(Formula 3) Proportion of the downlink average transmission rate to the allocated

bandwidth = VS.FEGE.RxMeanSpeed/Bandwidth allocated to the eNodeB x 100%
(Formula 4) Proportion of the downlink maximum transmission rate to the allocated

bandwidth = VS.FEGE.RxMaxSpeed/Bandwidth allocated to the eNodeB x 100%
In the preceding formulas, the related counters are described as follows:

l
VS.FEGE.TxMeanSpeed indicates the average transmission rate over an Ethernet port.
VS.FEGE.TxMaxSpeed indicates the maximum transmission rate over an Ethernet port.
VS.FEGE.RxMeanSpeed indicates the average reception rate over an Ethernet port.
VS.FEGE.RxMaxSpeed indicates the maximum reception rate over an Ethernet port.
The bandwidth allocated by an operator to the eNodeB can be queried by referring to Table
4-4.
Issue 02 (2015-06-20)

43
eRAN
Table 4-4 Bandwidth allocated by an operator to the eNodeB

Value of LR Switch
MPT Type
Allocated Bandwidth
Disable
UMPT
1 Gbit/s
LMPT
l 360 Mbit/s for formulas

1 and 2
l 540 Mbit/s for formulas
3 and 4
Enable
UMPT
LMPT
l Value of UL Committed
Information Rate (in
kbit/s) for formulas 1 and
2
l Value of DL Committed
Information Rate (in
kbit/s) for formulas 3 and
4
To query the values of LR Switch, UL Committed Information Rate, or DL

Committed Information Rate, run the LST LR command.
To query the MPT type, run the following command and check the values of Config
Type: DSP BRD: CN=x, SRN=x, SN=x; Multiple types of boards may be installed in the
baseband unit (BBU), you may need to view all the Config Type values to determine the
MPT type.
Suggested Measures
Expand the transmission capacity if either of the following conditions is met:
l
The proportion of the uplink average transmission rate or downlink reception rate to the
allocated bandwidth reaches or exceeds 70% in at least five days in a week.
The actual allocated bandwidth can be obtained from the operator. The maximum
bandwidth 750 Mbit/s is allocated by default.
Issue 02 (2015-06-20)
The proportion of the uplink maximum transmission rate or downlink reception rate to
the allocated bandwidth reaches or exceeds 85% in at least two days in a week.

44
eRAN
Resource Congestion Problem

Identification
About This Chapter

This section describes how to identify resource congestion problems. Network exceptions can
be found through KPI monitoring. If a KPI deteriorates, users can analyze relevant access
counters to decide whether the deterioration is caused by resource congestion.
5.1 Resource Congestion Indicators
5.2 Resource Allocation Problem Identification Process
Issue 02 (2015-06-20)

45
eRAN
5.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. Table 5-1
lists the counters related to KPIs.
Table 5-1 Counters related to KPIs
Counter
Description
L.RRC.ConnReq.Att
Number of RRC Connection Request messages received from

UEs in a cell (excluding retransmitted messages)
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
5.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 = L.RRC.SetupFail.ResFail / L.RRC.ConnReq.Att x 100%
where
L.RRC.SetupFail.ResFail indicates the number of RRC connection setup failures due to
resource allocation failures.
L.RRC.ConnReq.Att indicates the number of RRC connection setup requests.
If the RRC resource congestion rate is higher than 0.2%, KPI deterioration is caused by
resource congestion.
5.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 = L.E-RAB.FailEst.NoRadioRes / L.E-RAB.AttEst x 100%
where
Issue 02 (2015-06-20)

46
eRAN
L.E-RAB.FailEst.NoRadioRes indicates the number of E-RAB setup failures due to radio

resource insufficiency.
L.E-RAB.AttEst indicates the number of E-RAB setup attempts.
If the E-RAB resource congestion rate is higher than 0.2%, KPI deterioration is caused by
resource congestion.
5.2 Resource Allocation Problem Identification Process

Figure 5-1 shows the process of identifying resource allocation problems.
Figure 5-1 Process of identifying resource allocation problems
The fault location process 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 counters (RRC resource congestion rate and E-RAB resource
congestion rate).
Issue 02 (2015-06-20)

47
eRAN
6 Related Counters
Related Counters
Table 6-1 lists the counters involved in capacity monitoring.

Table 6-1 Counters involved in capacity monitoring
Resource
Type
Counter
Description
PRBs
L.ChMeas.PRB.DL.Used.Avg
Average number of used downlink

PRBs
L.ChMeas.PRB.DL.Avail
Number of available downlink PRBs
L.Thrp.bits.DL
Total downlinktraffic volume for

PDCP SDUs in a cell
L.Thrp.Time.DL
Total transmit duration of downlink

PDCP SDUs in a cell
L.Thrp.bits.UL
Total uplink data throughput at the

PDCP layer in a cell
L.Thrp.Time.UL
Total duration for transmitting uplink

data at the PDCP layer in a cell
L.ChMeas.PRB.DL.DrbUsed.
Avg
Average number of PRBs used by

PDSCH DRBs
L.ChMeas.PRB.UL.DrbUsed.
Avg
Average number of PRBs used by

PUSCH DRBs
L.RA.UeRaInfoRspWithCon.Num
Number of times the

UEInformationResponse messages in
which the contentionDetected IE
value is TRUE is received
L.RA.UeRaInfoRsp.Num
Number of times the

UEInformationResponse message
containing RACH information is
received
PRACH
resources(FDD)
Issue 02 (2015-06-20)

48
eRAN
6 Related Counters
Resource
Type
PRACH
resources(TDD)
Counter
Description
L.RA.Dedicate.PreambleAssig
n.Num
Number of times the non-contentionbased preambles are assigned
L.RA.Dedicate.PreambleReq.N
um
Number of times the non-contentionbased preambles are requested
L.RA.GrpA.Att
Number of times that the preamble in

group A for contention-based random
access is received
L.RA.GrpB.Att
L.RA.Dedicate.Att
Number of times that the preamble in

group B for contention-based random
access is received
Number of times that the preamble for
non-contention-based random access
is received
PDCCH
resources
L.ChMeas.CCE.CommUsed
Number of PDCCH CCEs used for

common DCI
L.ChMeas.CCE.ULUsed

uplink DCI
L.ChMeas.CCE.DLUsed

downlink DCI
RRC connected
users
L.Traffic.User.Avg
Average number of UEs in a cell
Throughput
license usage
L.Thrp.bits.UL.PDCP.SDU
Total uplink traffic volume of PDCP

SDUs in a cell
L.Thrp.bits.DL
Total downlink traffic volume for

PDCP SDUs in a cell
L.Paging.S1.Rx
Number of received paging messages

over the S1 interface in a cell
L.Paging.Dis.Num(TDD)
Number of MME-to-UE paging

messages discarded due to flow
control in a cell
VS.BBUBoard.CPULoad.Mea
n
Average board CPU usage
VS.BBUBoard.CPULoad.Cum
ulativeHighloadCount
Number of times that the CPU usage

of boards exceeds the preconfigured
threshold
VS.RscGroup.TxMeanSpeed
Average transmit rate of the resource

group
Paging
resources
Board CPU
resources
Transport
resource
groups(FDD)
Issue 02 (2015-06-20)

49
eRAN
Resource
Type
Transport
resource
groups(TDD)
Ethernet ports
Issue 02 (2015-06-20)
6 Related Counters
Counter
Description
VS.RscGroup.TxMaxSpeed
Maximum transmit rate of the

resource group
VS.RscGroup.TxPkts
Number of packets transmitted using

the resource group
VS.RscGroup.TxDropPkts
Number of packets discarded due to

failed transmissions using the
resource group.
VS.RscGroup.TxMaxSpeed
Maximum transmission rate of the

resource group
VS.RscGroup.TxMeanSpeed
Average transmission rate of the

resource group
VS.FEGE.TxMaxSpeed
Maximum transmit rate on the

Ethernet port
VS.FEGE.TxMeanSpeed
Average transmit rate on the Ethernet

port
VS.FEGE.RxMaxSpeed
Maximum receive rate on the Ethernet

port
VS.FEGE.RxMeanSpeed
Average receive rate on the Ethernet

port

50

ERAN Capacity Monitoring Guide (02) (PDF) - en

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ERAN Capacity Monitoring Guide (02) (PDF) - en

Enviado por

Direitos autorais:

Formatos disponíveis

eRAN

Capacity Monitoring Guide

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

3900 series base stations, that is, BTS3900,

Huawei Proprietary and Confidential

About This Document

Network planning engineers

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

About This Document

Command arguments are in italics.

Items (keywords or arguments) in brackets [ ] are optional.

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Press the keys concurrently. For example, pressing Ctrl

Press the keys in turn. For example, pressing Alt, A means

Huawei Proprietary and Confidential

About This Document

Select and release the primary mouse button without

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

3 Network Resource Monitoring(FDD)........................................................................................9

4 Network Resource Monitoring (TDD).................................................................................... 27

Huawei Proprietary and Confidential

5 Resource Congestion Problem Identification........................................................................ 45

Huawei Proprietary and Confidential

1 Changes in eRAN Capacity Monitoring Guide

Changes in eRAN Capacity Monitoring

4 Network Resource Monitoring (TDD)

2.2 Network Resources (TDD)

Changed name from "Network Resources" to "Network

Changed name from "Capacity Monitoring" to "Capacity

Add related Counters of LTE TDD.

No information in issue 01 (2015-03-23) is deleted from this issue.

Huawei Proprietary and Confidential

1 Changes in eRAN Capacity Monitoring Guide

Modified the monitoring principles of Main-Control-Board

3.9 Baseband-ProcessingUnit CPU Usage

Modified the monitoring principles of BasebandProcessing-Unit CPU Usage.

Huawei Proprietary and Confidential

About This Chapter

Huawei Proprietary and Confidential

2.1 Network Resources(FDD)

Users may fail to be

3.2 Downlink User

3.3 User Capacity