Documente Academic
Documente Profesional
Documente Cultură
Issue 05
Date 2014-12-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Purpose
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.
LampSite DBS3900
Product Version
The following table lists the product version related to this document.
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
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
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.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
5 Related Counters.........................................................................................................................30
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.
3.7 Paging Resource Usage Modified the monitoring principles in the Paging Resource
Usage.
04 (2014-11-13)
This is the fourth official release.
Compared with issue 03 (2014-09-04), this issue does not include any new information.
Compared with issue 03 (2014-09-04), this issue includes the following changes.
The whole document Added hyperlinks for MML commands and counters.
03 (2014-09-04)
This is the third official release.
Compared with issue 02 (2014-05-27), this issue does not include any new information.
Compared with issue 02 (2014-05-27), this issue includes the following changes.
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.
Compared with issue 01 (2014-04-26), this issue does not include any new information.
Compared with issue 01 (2014-04-26), this issue includes the following changes.
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%).
3.9 Baseband-Processing-
Unit CPU Usage
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.5 PDCCH Resource Modified the monitoring principles, monitoring methods, and
Usage suggested measures.
Draft A (2014-01-20)
This is a draft.
2 Overview
This section describes the types of network resources to be monitored and the method of
performing capacity monitoring.
Table 2-1 describes the types of network resources to be monitored and impacts of resource
insufficiency on the system.
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.
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.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.
Ethernet Port The bandwidths allocated for different types of boards in macro, micro,
Traffic and LampSite eNodeBs are different.
Table 3-2 Thresholds and handling suggestions for the resources to be monitored
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%.
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%
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)
In the preceding formula, L.ChMeas.CQI.DL.Y indicates the number of wideband CQI reports
with the value of Y.
Monitoring Principles
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.
– 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.
Monitoring Principles
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;.
Monitoring Principles
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:
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.
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
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
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.
Monitoring Principles
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:
where
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.
Monitoring Principles
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.
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:
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.
Monitoring Principles
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
The following items are used in monitoring this case:
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
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:
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
Monitoring Principles
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
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:
When the BBP CPU usage is high, you are advised to perform capacity expansion as follows:
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.
Monitoring Principles
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.
Monitoring Methods
The following items are used in monitoring this case:
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.
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.
Monitoring Principles
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
The following items are used in monitoring this case:
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.
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.
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.
Counter Description
where
L.RRC.SetupFail.ResFail indicates the number of RRC connection setup failures due to resource
allocation failures.
If the RRC resource congestion rate is higher than 0.2%, KPI deterioration is caused by resource
congestion.
where
If the E-RAB resource congestion rate is higher than 0.2%, KPI deterioration is caused by
resource congestion.
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).
5 Related Counters