ERAN7.0 Capacity Monitoring Guide (05) (PDF) - en

eRAN
Capacity Monitoring Guide
Issue 05
Date 2014-12-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. 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 05 (2014-12-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
Capacity Monitoring Guide 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 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, and BTS3203E LTE Product
Documentation for the BTS3203E.
2. The main control, transmission, and baseband processing units are deployed on the same board and share
the CPU for BTS3202E and BTS3203E LTE. The main control board and baseband board in this document
are boards in BTS3202E and BTS3203E LTE. The CPU usage of the main control board is the CPU usage
of boards in BTS3202E and BTS3203E LTE.
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 and BTS3203E
LampSite DBS3900
Product Version
The following table lists the product version related to this document.
Issue 05 (2014-12-30) Huawei Proprietary and Confidential ii

eRAN
Product Solution Version Product Version

Name
BTS3900AL l SRAN9.0 V100R09C00

l eRAN7.0
BTS3900
BTS3900A
BTS3900L
DBS3900
BTS3202E
BTS3203E
LTE
Intended Audience
This document is intended for:
l Field engineers
l 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
4 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.
5 Related Counters
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Issue 05 (2014-12-30) Huawei Proprietary and Confidential iii

eRAN
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.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
Issue 05 (2014-12-30) Huawei Proprietary and Confidential iv

eRAN
[] 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.
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 05 (2014-12-30) Huawei Proprietary and Confidential v

eRAN
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.
Issue 05 (2014-12-30) Huawei Proprietary and Confidential vi

eRAN
Capacity Monitoring Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Changes in eRAN Capacity Monitoring Guide.......................................................................1
2 Overview.........................................................................................................................................4
2.1 Network Resources.........................................................................................................................................................5
2.2 Capacity Monitoring Methods........................................................................................................................................6
3 Network Resource Monitoring...................................................................................................8

3.1 Overview........................................................................................................................................................................9
3.2 Downlink User Perception............................................................................................................................................12
3.3 User Capacity Usage....................................................................................................................................................13
3.4 PRACH Performance...................................................................................................................................................14
3.5 PDCCH Resource Usage..............................................................................................................................................16
3.6 Throughput License Usage...........................................................................................................................................17
3.7 Paging Resource Usage................................................................................................................................................18
3.8 Main-Control-Board CPU Usage.................................................................................................................................19
3.9 Baseband-Processing-Unit CPU Usage........................................................................................................................20
3.10 Transport Resource Group Bandwidth Usage............................................................................................................22
3.11 Ethernet Port Bandwidth Usage.................................................................................................................................24
4 Resource Congestion Problem Identification........................................................................26

4.1 Resource Congestion Indicators...................................................................................................................................27
4.1.1 RRC Resource Congestion Rate................................................................................................................................27
4.1.2 E-RAB Resource Congestion Rate............................................................................................................................27
4.2 Resource Allocation Problem Identification Process...................................................................................................28
5 Related Counters.........................................................................................................................30
Issue 05 (2014-12-30) Huawei Proprietary and Confidential vii

eRAN
Capacity Monitoring Guide 1 Changes in eRAN Capacity Monitoring Guide
1 Changes in eRAN Capacity Monitoring

Guide
This section describes changes in each issue of this document.
05 (2014-12-30)
This is the fifth official release.
Compared with issue 04 (2014-11-13), this issue does not include any new information.
Compared with issue 04 (2014-11-13), this issue includes the following changes.
Topic Change Description
3.7 Paging Resource Usage Modified the monitoring principles in the Paging Resource
Usage.
No information in issue 04 (2014-11-13) is deleted from this issue.
04 (2014-11-13)
This is the fourth official release.
The whole document Added hyperlinks for MML commands and counters.
Issue 05 (2014-12-30) Huawei Proprietary and Confidential 1

eRAN
03 (2014-09-04)
This is the third official release.
3.3 User Capacity Usage Changed the number of connected users to the number of RRC
connected users.
3.4 PRACH Performance Modified the monitoring principles, monitoring methods, and
suggested measures for PRACH performance.
RRC Connected User Changed connected user license usage to RRC connected user
License Usage license usage.
02 (2014-05-27)
This is the second official release.
3.7 Paging Resource Usage Changed the maximum number of paging messages that can
be processed per second by a 3900 series base station because
of a product specification change.
01 (2014-04-26)
This is the first official release.
Compared with Draft B (2014-06-30), this issue does not include any new information.
Compared with Draft B (2014-06-30), this issue includes the following changes.
3.8 Main-Control-Board Modified the formula for calculating the percentage of times
CPU Usage that the main-control-board CPU usage reaches or exceeds a
preconfigured threshold (85%).

eRAN
3.9 Baseband-Processing-
Unit CPU Usage
No information in Draft B (2014-06-30) is deleted from this issue.
Draft B (2014-06-30)
This is a draft.
Compared with Draft A (2014-01-20), this draft includes the following new information:
l 3.3 User Capacity Usage
l 3.6 Throughput License Usage
Compared with Draft A (2014-01-20), this draft includes the following changes.
3.1 Overview Modified information in the table "Thresholds and handling

suggestions for the resources to be monitored".
3.2 Downlink User Modified the suggested measures.

Perception
3.5 PDCCH Resource Modified the monitoring principles, monitoring methods, and
Usage suggested measures.
3.7 Paging Resource Usage l Deleted the monitoring item L.Paging.Dis.Num.

l Added suggested measures for the core network.
3.8 Main-Control-Board Modified the suggested measures.

CPU Usage
3.10 Transport Resource Cancelled the monitoring of packet loss rate.

Group Bandwidth Usage
No information in Draft A (2014-01-20) is deleted from this issue.
Draft A (2014-01-20)
This is a draft.

eRAN
Capacity Monitoring Guide 2 Overview
2 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
2.2 Capacity Monitoring Methods

eRAN
2.1 Network Resources

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
Resource Type Meaning Impact of Resource Resource

Insufficiency on the Monitoring Item
System
Cell Physical Bandwidth Users may fail to be 3.2 Downlink User

resou resource consumed on the admitted, and Perception
rces blocks air interface experience of admitted
(PRBs) users is affected.
Synchroniz Maximum User experience is 3.3 User Capacity

ed user number of affected. Usage
capacity synchronized
users in a cell

eRAN
Resource Type Meaning Impact of Resource Resource

Insufficiency on the Monitoring Item
System
Physical Random access Access delays are 3.4 PRACH

random preambles carried prolonged, or even Performance
access on the PRACH access attempts fail.
channel
(PRACH)
resources
Physical Downlink control Uplink and downlink 3.5 PDCCH Resource

downlink channel resources scheduling delays are Usage
control prolonged, and user
channel experience is affected.
(PDCCH)
resources
eNod Licensed Maximum User perception and 3.6 Throughput

eB throughput throughput in an customer income are License Usage
resou eNodeB affected.
rces
Paging eNodeB paging Paging messages may 3.7 Paging Resource
resources capacity be lost, affecting user Usage
experience.
Main- Processing KPIs deteriorate. 3.8 Main-Control-

control- capability of the Board CPU Usage
board CPU main control
board of the
eNodeB
Baseband- Processing KPIs deteriorate. 3.9 Baseband-

processing- capability of the Processing-Unit CPU
unit CPU baseband Usage
processing unit
(BBP)
Transport eNodeB logical Packets may be lost, 3.10 Transport

resource transport affecting user Resource Group
groups resources experience. Bandwidth Usage
Ethernet eNodeB physical Packets may be lost, 3.11 Ethernet Port

ports transport affecting user Bandwidth Usage
resources experience.
2.2 Capacity Monitoring Methods

l Daily monitoring for prediction

eRAN
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.
l 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 4 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.

eRAN
Capacity Monitoring Guide 3 Network Resource Monitoring
3 Network Resource Monitoring
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 main-control-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

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 main-control-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
Synchronized User The maximum number of synchronized users processed by a micro

Capacity Usage eNodeB per second is different from that processed by a macro or
LampSite eNodeB per second.
Paging Resource The maximum number of paging messages processed by a micro

Usage eNodeB per second is different from that processed by a macro or
LampSite eNodeB per second.
Main-Control- If the main-control-board CPU usage of a micro or LampSite eNodeB

Board CPU Usage reaches or exceeds a threshold, the problem cannot be solved by
replacing the main control board.
Baseband- If the baseband-processing-unit CPU usage of a micro eNodeB reaches

Processing-Unit or exceeds a threshold, the problem can be solved only by adding
CPU Usage another micro eNodeB.
Ethernet Port The bandwidths allocated for different types of boards in macro, micro,
Traffic and LampSite eNodeBs are different.
Thresholds and Handling Suggestions

Table 3-2 describes the thresholds and handling suggestions for the resources to be monitored.

eRAN
Table 3-2 Thresholds and handling suggestions for the resources to be monitored
Res Resource Conditions Handling Suggestions

ourc Monitoring
e Item
Typ
e
Cell 3.2 User-perceived rate < n Mbit/ Optimize RF performance, expand

reso Downlink s (user-configurable) the cell bandwidth, add carriers, or
urce User add eNodeBs.
s Perception
3.3 User l Synchronized user Optimize parameter settings,

Capacity capacity usage of a cell optimize RF performance, expand
Usage ≥ 60% the cell bandwidth, add carriers, or
l RRC connected user split cells.
capacity usage of a board
≥ 60%
l RRC connected user
license usage of an
eNodeB ≥ 60%
3.4 PRACH Conflict probability for (Optional) Enable the PRACH

Performanc contention-based preambles resource adjustment algorithm.
e ≥ 5%
Assignment success rate for Enable the PRACH resource

dedicated preambles < 99% adjustment algorithm and reuse of
dedicated preambles.
3.5 PDCCH CCE usage PDCCH Add carriers, split cells, or optimize
Resource ≥ 80% Symbol RF performance.
Usage Number
Adjust Switch
is set to OFF
(Off).
PDCCH
Symbol
Number
Adjust Switch
is set to ON
(On), and
uplink or
downlink PRB
usage reaches
or exceeds
70%.

eRAN
Res Resource Conditions Handling Suggestions

ourc Monitoring
e Item
Typ
e
eNo 3.6 Throughput license usage ≥ Increase the licensed throughput.

deB Throughput 80%
reso License
urce Usage
s
3.7 Paging Percentage of paging Take one of the following measures:
Resource messages received on the S1 l Decrease the number of cells in
Usage interface ≥ 60% 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 Main- Average main-control-board Balance the loads, replace old boards
Control- CPU usage ≥ 60% or with those of higher specifications,
Board CPU percentage of time the CPU or add eNodeBs.
Usage usage reaches or exceeds
85% ≥ 5%
3.9 Average baseband Add boards, replace old boards with

Baseband- processing unit (BBP) CPU those of higher specifications, or
Processing- usage ≥ 60% or percentage balance inter-BBP loads.
Unit CPU of time the CPU usage
Usage reaches or exceeds 85% ≥
5%
3.10 Proportion of average Expand the bandwidth of the

Transport transmission rate to transport resource group.
Resource configured bandwidth ≥
Group 80% or Proportion of
Bandwidth maximum transmission rate
Usage to configured bandwidth ≥
90%
3.11 Proportion of average Expand the eNodeB transmission

Ethernet transmission rate to allocated capacity.
Port bandwidth ≥ 70% or
Bandwidth Proportion of maximum
Usage transmission rate to allocated
bandwidth ≥ 85%

eRAN
3.2 Downlink User Perception
Monitoring Principles
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%
l 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 L.ChMeas.PRB.DL.Avail indicates the number of available downlink PRBs.
l L.Thrp.bits.DL indicates the total downlink traffic volume for PDCP SDUs in a cell.
l L.Thrp.bits.DL.LastTTI indicates the downlink traffic volume sent in the last TTI for PDCP
SDUs before the buffer is empty.
l 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.
l 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)

eRAN
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
User capacity usage can be evaluated by the following three items:
l Synchronized user capacity usage of a cell
l RRC connected user capacity usage of a board
l 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 Synchronized user capacity usage of a cell
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 eNodeB Baseband
Specifications (Maximum Number of UEs in RRC_Connected Mode) in 3900 Series
Base Station Technical Description. The maximum number of synchronized users is
200 for BTS3202E and BTS3203E LTE.
l 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.

eRAN
– To learn the maximum number of RRC connected users of a BBP or main control board,
see eNodeB Baseband Specifications (Maximum Number of UEs in RRC_Connected
Mode) in 3900 Series Base Station Technical Description.
l RRC connected user license usage of an eNodeB
The calculation formula is as follows:
RRC connected user license usage of an eNodeB = ∑L.Traffic.User.Avg / 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 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.
l 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.
l 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.
l 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-control-board 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

eRAN
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. Non-contention
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 Conflict probability for contention-based preambles: The more frequently the contention-
based access is performed, the higher probability that the preambles are 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%
l Assignment success rate for dedicated preambles = L.RA.Dedicate.PreambleAssign.Num /
L.RA.Dedicate.PreambleReq.Num x100%
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 L.RA.UeRaInfoRsp.Num indicates the number of times the UEInformationResponse
message containing RACH information is received.
l L.RA.Dedicate.PreambleAssign.Num indicates the number of times the non-connection-
based preambles are assigned.
l L.RA.Dedicate.PreambleReq.Num indicates the number of times the non-contention-based
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.
l 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;.

eRAN
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 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 L.ChMeas.CCE.ULUsed indicates the number of PDCCH CCEs used for uplink
scheduling.
l 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 Ng Maximum Number of PDCCH CCEs

Bandwidth
(Configurable Number of Number of Number of
) PDCCH PDCCH PDCCH
Symbols = 1 Symbols = 2 Symbols = 3
5 MHz 1/6 4 13 21
1/2 4 12 21
1 3 12 20
2 2 11 19
10 MHz 1/6 10 26 43
1/2 9 26 42
1 8 25 41
2 6 23 39

eRAN
System Ng Maximum Number of PDCCH CCEs

Bandwidth
(Configurable Number of Number of Number of
) PDCCH PDCCH PDCCH
Symbols = 1 Symbols = 2 Symbols = 3
15 MHz 1/6 15 40 65
1/2 14 39 64
1 12 37 62
2 9 34 59
20 MHz 1/6 20 54 87
1/2 19 52 86
1 17 50 84
2 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.
l 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;.
l 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

eRAN
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
l 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.
l 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 and BTS3203E LTE can send a maximum of 500 paging messages
per second.

eRAN
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.
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.
l 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.
l 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 CPU usage of
the main control board and the percentage of times that the main-control-board CPU usage
reaches or exceeds a preconfigured threshold (85%).
The CPU usage of the main control board reflects the busy level of the eNodeB. If the main-
control-board CPUs are busy processing control plane or user plane data, signaling-related KPIs
may deteriorate, and users may experience a low access success rate, low E-RAB setup success
rate, or high service drop rate.
Monitoring Methods
l VS.BBUBoard.CPULoad.Mean
l 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
l VS.BBUBoard.CPULoad.Mean indicates the average CPU usage of the board.

eRAN
l 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%.

l 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:
Figure 3-1
1. Transfer UEs from the 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 is not applicable for LampSite eNodeB, BTS3202E and
BTS3203E.
3. Add eNodeBs
3.9 Baseband-Processing-Unit CPU Usage

eRAN
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 CPU usage of the
BBP 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.
Monitoring Methods
The BBP CPU usage is evaluated by the percentage of times that the BBP CPU usage reaches
or exceeds a preconfigured threshold (85%) and the counter VS.BBUBoard.CPULoad.Mean.
The formula of calculating the percentage of times that the BBP CPU usage reaches or exceeds
a preconfigured threshold (85%) is as follows:
Percentage of times that the BBP CPU usage reaches or exceeds a preconfigured threshold (85%)
= VS.BBUBoard.CPULoad.CumulativeHighloadCount / Measurement period (in the unit of
second) / 5 x 100%
where
l VS.BBUBoard.CPULoad.Mean indicates the average CPU usage of the board.

l VS.BBUBoard.CPULoad.CumulativeHighloadCount indicates the number of times that
the 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%.

l 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:

eRAN
Figure 3-2
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 an eNodeB. Add an eNodeB if the eNodeB already has the maximum number of BBPs
while additional BBPs are still required. You can expand the capacity of the BTS3202E
and BTS3203E LTE only by adding eNodeBs.
3.10 Transport Resource Group Bandwidth Usage

eRAN
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),
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%
l 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.
l 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.

eRAN
In the command output, the value of Tx Bandwidth is the bandwidth configured for the transport
resource group.
Suggested Measures
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% for five days in a week.
l 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%
l (Item 2) Proportion of the maximum uplink transmission rate to the allocated bandwidth =
VS.FEGE.TxMaxSpeed / Allocated bandwidth x 100%
l (Item 3) Proportion of the average downlink reception rate to the allocated bandwidth =
VS.FEGE.RxMeanSpeed / Allocated bandwidth x 100%
l (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.
l VS.FEGE.TxMaxSpeed indicates the maximum transmission rate of an Ethernet port.
l VS.FEGE.RxMeanSpeed indicates the average reception rate of an Ethernet port.
l VS.FEGE.RxMaxSpeed indicates the maximum reception rate of an Ethernet port.
The allocated bandwidth can be queried by referring to Table 3-4.

eRAN
Table 3-4 Allocated bandwidth
LR Switch Value Main Allocated Bandwidth

Control
Board
DISABLE UMPT Min(1.5 Gbit/s, the transmission bandwidth of the

Ethernet port)
LMPT l For items 1 and 2: 300 Mbit/s

l For items 3 and 4: 450 Mbit/s
Boards in l For items 1 and 2: 50 Mbit/s

BTS3202E l For items 3 and 4: 150 Mbit/s
and
BTS3203E
LTE
ENABLE UMPT l For items 1 and 2: value of UL Committed

Information Rate(kbit/s)
LMPT
l For items 3 and 4: value of DL Committed
Boards in Information Rate(kbit/s)
BTS3202E
and
BTS3203E
LTE
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).
l 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.
l 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.

eRAN
Capacity Monitoring Guide 4 Resource Congestion Problem Identification
4 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.
4.1 Resource Congestion Indicators
4.2 Resource Allocation Problem Identification Process

eRAN
4.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 4-1 lists the
counters related to KPIs.
Table 4-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
4.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.
4.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%

eRAN
where
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.
4.2 Resource Allocation Problem Identification Process

Figure 4-1 shows the process of identifying resource allocation problems.

eRAN
Figure 4-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).

eRAN
Capacity Monitoring Guide 5 Related Counters
5 Related Counters
Table 5-1 lists the counters involved in capacity monitoring.
Table 5-1 Counters involved in capacity monitoring
Resource Counter Description

Type
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 downlink traffic volume for

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

PDCP SDUs in a cell
PRACH L.RA.UeRaInfoRspWithCon.N Number of times the UEInformation-

resources um Response messages in which the
contentionDetected IE value is TRUE
is received
L.RA.UeRaInfoRsp.Num Number of times the UEInformation-

Response message containing RACH
information is received
L.RA.Dedicate.PreambleAssign Number of times the non-contention-

.Num based preambles are assigned
L.RA.Dedicate.PreambleReq.N Number of times the contention-based

um preambles are requested
PDCCH L.ChMeas.CCE.CommUsed Number of PDCCH CCEs used for

resources common DCI
L.ChMeas.CCE.ULUsed Number of PDCCH CCEs used for

uplink DCI

eRAN
Capacity Monitoring Guide 5 Related Counters
Resource Counter Description

Type
L.ChMeas.CCE.DLUsed Number of PDCCH CCEs used for

downlink DCI
L.Traffic.User.Avg Number of available CCEs
RRC connected L.Traffic.User.Avg Average number of UEs in a cell

users
Throughput L.Thrp.bits.UL.PDCP.SDU Total uplink traffic volume of PDCP

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

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

resources over the S1 interface in a cell
Board CPU VS.BBUBoard.CPULoad.Mean Average board CPU usage

resources
VS.BBUBoard.CPULoad.Cu- Number of times that the CPU usage
mulativeHighloadCount of boards exceeds the preconfigured
threshold
Transport VS.RscGroup.TxMeanSpeed Maximum transmit rate of the resource

resource groups group
VS.RscGroup.TxMaxSpeed Average transmit rate of the resource

group
Ethernet ports 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


ERAN7.0 Capacity Monitoring Guide (05) (PDF) - en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ERAN7.0 Capacity Monitoring Guide (05) (PDF) - en

Uploaded by

Copyright:

Available Formats

eRAN

Capacity Monitoring Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 05 (2014-12-30) Huawei Proprietary and Confidential i

About This Document

eNodeB Types eNodeB Models

Macro 3900 series base stations, that is, BTS3900,

Micro BTS3202E and BTS3203E

Issue 05 (2014-12-30) Huawei Proprietary and Confidential ii

Product Solution Version Product Version

BTS3900AL l SRAN9.0 V100R09C00

4 Resource Congestion Problem Identification

Issue 05 (2014-12-30) Huawei Proprietary and Confidential iii

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices and

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

Issue 05 (2014-12-30) Huawei Proprietary and Confidential iv

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

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

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

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

Issue 05 (2014-12-30) Huawei Proprietary and Confidential v

Double-click Press the primary mouse button twice continuously and

Issue 05 (2014-12-30) Huawei Proprietary and Confidential vi

About This Document.....................................................................................................................ii

3 Network Resource Monitoring...................................................................................................8

4 Resource Congestion Problem Identification........................................................................26

Issue 05 (2014-12-30) Huawei Proprietary and Confidential vii

1 Changes in eRAN Capacity Monitoring

This section describes changes in each issue of this document.

Topic Change Description

No information in issue 04 (2014-11-13) is deleted from this issue.

Topic Change Description

No information in issue 03 (2014-09-04) is deleted from this issue.

Issue 05 (2014-12-30) Huawei Proprietary and Confidential 1

Topic Change Description

No information in issue 02 (2014-05-27) is deleted from this issue.

Topic Change Description

No information in issue 01 (2014-04-26) is deleted from this issue.

Topic Change Description

Issue 05 (2014-12-30) Huawei Proprietary and Confidential 2

Topic Change Description

No information in Draft B (2014-06-30) is deleted from this issue.

Topic Change Description

3.1 Overview Modified information in the table "Thresholds and handling

3.2 Downlink User Modified the suggested measures.

3.7 Paging Resource Usage l Deleted the monitoring item L.Paging.Dis.Num.

3.8 Main-Control-Board Modified the suggested measures.

3.10 Transport Resource Cancelled the monitoring of packet loss rate.

No information in Draft A (2014-01-20) is deleted from this issue.