Escolar Documentos
Profissional Documentos
Cultura Documentos
Issue 10
Date 2014-08-27
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
This document describes the networking and protection of SDH, PDH, Ethernet, ATM, SAN
and video services. In addition, network management information, orderwire and clock planning
is described briefly.
This document provides guides to get the information about how to construct a network.
NOTE
l 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
station, "BTS3202E Product Documentation" for BTS3202E base station, and "BTS3203E LTE Product
Documentation" for BTS3203E base station.
l 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 corresponding units in BTS3202E and BTS3203E LTE. The CPU usage of the main control board is the
CPU usage of boards in BTS3202E and BTS3203E LTE.
l 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.
Product Versions
The following table lists the product version related to this document.
BTS3900L
BTS3900AL
DBS3900
BTS3202E
Intended Audience
This document is intended for:
l Field engineers
l Network planning engineers
Organization
1 Changes in eRAN Capacity Monitoring Guide
2 Overview
This chapter describes the types of network resources to be monitored and the method of
performing capacity monitoring.
3 Capacity Monitoring
This chapter describes how to identify resource allocation problems. Network abnormalities can
be found through KPI monitoring. If a KPI is deteriorated, users can analyze the access counters
(RRC resource congestion rate and E-RAB resource congestion rate) to check 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.
Symbol Description
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
3 Capacity Monitoring...................................................................................................................11
3.1 Introduction..................................................................................................................................................................12
3.2 Downlink User Perception............................................................................................................................................14
3.3 Synchronized User Capacity Usage.............................................................................................................................15
3.4 PRACH Resource Usage..............................................................................................................................................16
3.5 PDCCH Resource Usage..............................................................................................................................................17
3.6 Connected User License Usage....................................................................................................................................19
3.7 Traffic Volume License Usage.....................................................................................................................................20
3.8 Paging Resource Usage................................................................................................................................................20
3.9 Main-Control-Board CPU Usage.................................................................................................................................21
3.10 Baseband Processing Unit CPU Usage......................................................................................................................22
3.11 Transport Resource Group Usage...............................................................................................................................24
3.12 Ethernet Port Traffic...................................................................................................................................................25
5 Related Counters.........................................................................................................................32
10 (2014-08-27)
This is the tenth commercial release.
Compared with issue 09 (2014-04-15), this issue does not include any new information.
Compared with issue 09 (2014-04-15), this issue includes the following changes.
09 (2014-04-15)
This is the ninth commercial release.
Compared with issue 08 (2014-03-14), this issue does not include any new information.
Compared with issue 08 (2014-03-14), this issue includes the following changes.
3.9 Main-Control-Board Modified the formula of "Percentage of times that the main-
CPU Usage control-board CPU usage reaches or exceeds a preconfigured
threshold (85%)."
3.10 Baseband Processing
Unit CPU Usage
08 (2014-03-14)
This is the eighth commercial release.
Compared with issue 07 (2013-12-23), this issue includes the following new information.
l 3.3 Synchronized User Capacity Usage
l 3.7 Traffic Volume License Usage
Compared with issue 07 (2013-12-23), this issue includes the following changes.
3.2 Downlink User Changed the monitoring item to downlink user perception,
Perception and modified the monitoring principles and the suggested
measures.
3.5 PDCCH Resource Modified the monitoring principles, monitoring methods, and
Usage suggested measures.
07 (2013-12-23)
This is the seventh commercial release.
Compared with issue 06 (2013-10-30), this issue does not include any new information.
Compared with issue 06 (2013-10-30), this issue includes the following changes.
3.2 Downlink User Changed the monitoring item to downlink user perception,
Perception and modified the monitoring principles.
Compared with issue 06 (2013-10-30), this issue includes the following changes.
l SRS Resource Usage: The SRS subframe reconfiguration switch is turned on by default.
SRS resources will not become the network bottleneck and therefore will not be monitored.
l PUCCH Resource Usage: The PUCCH algorithm switch is turned on by default. PUCCH
resources will not become the network bottleneck and therefore will not be monitored.
06 (2013-10-30)
This is the sixth commercial release.
Compared with issue 05 (2013-08-26), this issue includes the following new information.
l 5 Related Counters
Compared with issue 05 (2013-08-26), this issue includes the following changes.
3.2 Downlink User l Modified formulas for measuring the monitoring items.
Perception l Added the suggested measures and the conditions for
taking measures.
SRS Resource Usage l Modified the maximum number of UEs supported by SRS
resources when the system bandwidth is 10 MHz.
l Modified suggested measures when the SRS resource
usage exceeds 60%.
3.4 PRACH Resource l Modified the value of N in the formula for calculating
Usage random preamble usage when the system bandwidth is 5
MHz or 10 MHz.
l Added a suggested measure: enabling PRACH resource
adjustment algorithm if required.
PUCCH Resource Usage Modified suggested measures when the PUCCH resource
usage exceeds 60%.
3.5 PDCCH Resource Modified formulas for measuring the monitoring items.
Usage
3.12 Ethernet Port Traffic Added the bandwidth that operators configure for the
BTS3202E and the BTS3023E LTE board, and modified the
unit of bandwidth.
4 Resource Allocation Added the congestion rate threshold. Optimized the resource
Problem Identification allocation problem identification process.
Compared with issue 05 (2013-08-26), this issue includes the following changes.
l "eNodeB Resources" and "Cell Resources": Deleted these two sections. The contents in
these sections are described in Table 2-1, which contains four columns: Resource Type,
Meaning, Impact of Resource Insufficiency on the System, and Monitoring Item.
l "General Process": Deleted this section. The thresholds for the resources to be monitored
and the related handling suggestions are described in Table 3-1. The counters involved in
capacity monitoring formulas are provided in 5 Related Counters.
05 (2013-08-26)
This is the fifth commercial release.
Compared with issue 04 (2013-07-22), this issue does not include any new information.
Compared with issue 04 (2013-07-22), this issue includes the following changes.
3.8 Paging Resource Usage Modified paging specifications of the BTS3202E and
BTS3203E.
04 (2013-07-22)
This is the fourth commercial release.
Compared with issue 03 (2013-06-26), this issue includes the following new information.
l 3.11 Transport Resource Group Usage
Compared with issue 03 (2013-06-26), this issue includes the following changes.
3.11 Transport Resource Added the figure to illustrate the position of Transport
Group Usage Resource Group in TCP/IP model.
03 (2013-06-26)
This is the third commercial release.
Compared with issue 02 (2013-05-27), this issue does not include any new information.
Compared with issue 02 (2013-05-27), this issue includes the following changes.
3.5 PDCCH Resource Added the suggested measures when the uplink or downlink
Usage PRB usage reaches or exceeds 90%.
02 (2013-05-27)
This is the second commercial release.
Compared with issue 01 (2013-04-28), this issue does not include any new information.
Compared with issue 01 (2013-04-28), this issue includes the following changes.
3 Capacity Monitoring Added the descriptions about how to query parameter values.
Compared with issue 01 (2013-04-28), this issue includes the following changes.
l Appendix
01 (2013-04-28)
This is the first commercial release.
Compared with Draft A (2012-12-30), this issue does not include any new information.
Compared with Draft A (2012-12-30), this issue includes the following changes.
Draft A (2012-12-30)
This is the first draft.
2 Overview
This chapter 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.
l Thresholds defined for capacity monitoring in this document are generally lower than those for alarm
triggering so that risks of resource insufficiency can be detected as early as possible.
l 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:
l The CPU usage threshold 60% is specified based on the CPU flow control threshold 80%.
l 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.
l 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 Capacity Monitoring
3.1 Introduction
This chapter 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.
3.1 Introduction
This chapter 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
You need to determine busy hours of the system for accurate monitoring of counters. You are advised to define
busy hours as a period when the system or a cell is undergoing the maximum resource consumption of a day.
Table 3-1 describes types of resources to be monitored, thresholds, and handling suggestions.
3.4 Usage of preambles for Enable the backoff algorithm for the
PRACH contention-based access PRACH.
Resourc 75%
e Usage
Usage of preambles for Enable the PRACH resource
non-contention-based adjustment algorithm and reuse of
access 75% dedicated preambles.
Monitoring Principles
Growing traffic leads to a continuous increase in PRB usage. When the PRB usage approaches
to 100%, user-perceived rates will decrease. As downlink is a major concern in an LTE network,
this document describes only how to monitor downlink user perception.
NOTE
The uplink user perception can be monitored using the same way.
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.Time.DL/1000
where:
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 throughput of downlink data transmitted at the PDCP
layer in a cell.
l L.Thrp.Time.DL indicates the duration for transmitting downlink data at the PDCP layer
in a cell.
Suggested Measures
If both of the following conditions are met:
l Downlink PRB usage 70%
l Downlink user-perceived rate < a user-defined threshold (default value: 2 Mbit/s)
Then:
l If the cell spectral efficiency is low, you are advised to increase the cell throughput by
optimizing RF performance.
l If the cell spectral efficiency is high, you are advised to:
Add carriers or expand the bandwidth of the existing carrier.
Add eNodeBs.
Monitoring Principles
When the number of RRC connected users in a cell exceeds the maximum number defined in
the product specifications, cell KPIs deteriorate. RRC connected users include synchronized
users and users in the out-of-synchronization state. Synchronized users consume air interface
resources and the number of synchronized users is approximately equal to the number of RRC
connected users by default. Therefore, the number of RRC connected users (instead of
synchronized users) is monitored.
NOTE
When the number of RRC connected users in a cell reaches or exceeds the preconfigured threshold, the user-
perceived rate has already decreased to an unacceptable level. Therefore, the user-perceived rate should be
considered first. The number of RRC connected users in a cell can be considered first when the user capacity
of a cell takes priority over user experience.
Monitoring Methods
The following item is used in monitoring this case:
where
l L.Traffic.User.Avg indicates the average number of RRC connected users in a cell.
l The maximum number of synchronized users in a cell is 400 for the LBBPc or 1200 for
the LBBPd.
Suggested Measures
When the synchronized user capacity usage of a local cell reaches or exceeds 60%, you are
advised to:
l 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.
l 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.
l Add cells or expand the local cell bandwidth.
l Split the local cell into multiple cells
Monitoring Principles
The PRACH transmits preambles during random access procedures.
If more than 100 non-contention-based random access attempts are initiated per second,
dedicated preambles will become insufficient and the eNodeB will instruct the UE to initiate
contention-based random access instead, increasing the access delay for the UE. In handover
scenarios, the handover procedure is prolonged.
Monitoring Methods
The following items are used in monitoring this case:
l Random preamble usage = (L.RA.GrpA.Att + L.RA.GrpB.Att)/3600/N x 100%
l Dedicated preamble usage = L.RA.Dedicate.Att/3600/100 x 100%
where
l L.RA.GrpA.Att indicates the number of times that random preambles in group A are
received.
l L.RA.GrpB.Att indicates the number of times that random preambles in group B are
received.
l L.RA.Dedicate.Att indicates the number of times that dedicated preambles are received.
l The value of N varies as follows:
If the system bandwidth is 15 MHz or 20 MHz, N is 100.
If the system bandwidth is 5 MHz or 10 MHz and the PRACH resource adjustment
algorithm is disabled, N is 50.
If the system bandwidth is 5 MHz or 10 MHz and the PRACH resource adjustment
algorithm is enabled, N is 100.
To check whether the PRACH resource adjustment algorithm is enabled, run the LST
CELLALGOSWITCH command to query the value of the RachAlgoSwitch.
Suggested Measures
You are advised to take the following measures:
l f the random preamble usage reaches or exceeds 75% for X days (three days by default) in
a week, enable the adaptive backoff function by running the following command to help
reduce the peak RACH load and average access delay:
MOD CELLALGOSWITCH: LocalCellId=x, RachAlgoSwitch=BackOffSwitch-1;
If the system bandwidth is 5 MHz or 10 MHz, it is good practice to enable the PRACH
resource adjustment algorithm by running the following command:
MOD CELLALGOSWITCH: LocalCellId=x,RachAlgoSwitch=RachAdjSwitch-1;
l If the dedicated preamble usage reaches or exceeds 75% for X days (three days by default)
in a week, enable the PRACH resource adjustment algorithm and reuse of dedicated
preambles between UEs by running the following command:
MOD CELLALGOSWITCH: LocalCellId=x,RachAlgoSwitch=
RachAdjSwitch-1,RachAlgoSwitch=MaksIdxSwitch-1;
This helps reduce the probability of UEs initiating contention-based random access in the
case of dedicated preamble insufficiency and therefore helps reduce the access delay.
Monitoring Principles
This capacity indicator measures the number of control channel elements (CCEs) that can be
used by the PDCCH.
l If PDCCH symbols are insufficient or the cell is heavily loaded, CCEs may fail to be
allocated to UEs to be scheduled, which will result in a long service delay and unsatisfactory
user experience.
l If PDCCH symbols are excessive and the cell is lightly loaded, the resources that can be
used by the PDSCH increases. This will also result in low spectral efficiency.
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.
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
The value of Ng is equal to the PHICH resource parameter value, which can be
queried by running the LST PHICHCFG command.
Suggested Measures
l If the PDCCH Symbol Number Adjust Switch parameter value is Off, you are advised
to set this parameter to On by running the following command:
MOD CELLPDCCHALGO: LocalCellId=x, PdcchSymNumSwitch=ON;
l If the PDCCH Symbol Number Adjust Switch parameter value is set to On and the uplink
or downlink PRB usage reaches or exceeds 70%, you are advised to take one of the
following measures:
Add cells or split existing cells.
Optimize RF performance to reduce the interference to PDCCH from neighboring cells.
Monitoring Principles
The RRC connected user license specifies the maximum permissible number of users in
RRC_CONNECTED mode. If the RRC connected user license usage exceeds a preconfigured
threshold, users may fail to access the network.
Monitoring Methods
The following item is used in monitoring this case:
RRC connected user license usage = L.Traffic.User.Avg/Licensed number of RRC connected
users x 100%
where
l L.Traffic.User.Avg indicates the average number of RRC connected users in a cell.
L.Traffic.User.Avg indicates the sum of the average number of RRC connected users in all
cells under an eNodeB.
l The licensed number of RRC connected users can be queried by running the following
command:
DSP LICENSE: FUNCTIONTYPE=eNodeB;
In the command output, the value of LLT1ACTU01 in the Allocated column is the licensed
number of RRC connected users.
Suggested Measures
Measures to be taken also depend on the main-control-board CPU usage.
If the RRC connected user license usage reaches or exceeds 60% for X days (three days by
default) in a week, you are advised to take the following measures:
l If the main-control-board CPU usage is less than 60%, increase the licensed limit.
l If the main-control-board CPU usage reaches or exceeds 60%, add an eNodeB.
For details about main-control-board CPU usage, see section 3.9 Main-Control-Board CPU
Usage.
Monitoring Principles
When the traffic volume of an eNodeB reaches or exceeds the licensed volume, the eNodeB
performs flow control, which affects user experience and customer income.
Monitoring Methods
The following item is used in monitoring this case:
where
l L.Thrp.bits.UL and L.Thrp.bits.DL indicate the uplink traffic volume and downlink traffic
volume of a cell, respectively. (L.Thrp.bits.UL+L.Thrp.bits.DL) indicates the sum of
uplink and downlink traffic volume of all cells under an eNodeB.
l The licensed eNodeB traffic volume can be queried by running the following command:
DSP LICENSE: FUNCTIONTYPE=eNodeB;
The licensed eNodeB traffic volume is equal to the Allocated parameter value in the record
whose License Identifier is LLT1THRUL01.
Suggested Measures
If the traffic volume license usage of an eNodeB reaches or exceeds 80% for X days (three days
by default) in a week, you are advised to increase the licensed traffic volume.
Monitoring Principles
The eNodeB and BTS3202E and BTS3203E LTE can process a maximum of 750 and 500 paging
messages per second, respectively. If the number of paging messages exceeds that capacity,
paging messages sent from the eNodeB to UEs may be discarded, which leads to a decrease in
the call completion rate.
Monitoring Methods
The following item is used in monitoring this case:
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 by the eNodeB over the S1 interface reaches or
exceeds 60% for X days (three days by default) in a week, you are advised to:
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 provided by Huawei.
Monitoring Principles
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.
l If the CQI related performance counters indicate that the channel quality is poor, KPI
deterioration may not be caused by main-control-board CPU overload but by deterioration
in channel quality.
l If the KPIs deteriorate and the main-control-board CPU usage exceeds a preconfigured
threshold, you are advised to perform capacity expansion according to "Suggested
Measures."
Monitoring Methods
The following items are used in monitoring this case:
l VS.Board.CPUload.Mean
l Percentage of times that the main-control-board CPU usage reaches or exceeds a
preconfigured threshold (85%) = VS.Board.CPULoad.CumulativeHighloadCount/
(3600/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:
l 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.
l Replace the main control board with a UMPT: If the main control board is an LMPT, replace
it with a UMPT.
l Add eNodeBs.
Monitoring Principles
If the eNodeB receives too much traffic, which is expressed either in bit/s or packet/s, the
baseband processing unit CPU responsible for user plane processing is heavily loaded. As a
result, the eNodeB has a low RRC connection setup success rate, low E-RAB setup success rate,
low handover success rate, and high service drop rate.
Monitoring Methods
The following item is used in monitoring this case:
l Percentage of times that the baseband processing unit CPU usage reaches or exceeds a
preconfigured threshold (85%) = VS.Board.CPULoad.CumulativeHighloadCount/
(3600/5) x 100%
where
Suggested Measures
The baseband processing unit CPU becomes overloaded if either of the following conditions is
met for X days (three days by default) in a week:
l The average baseband processing unit CPU usage reaches or exceeds 60%.
l The percentage of times that the baseband processing unit CPU usage reaches or exceeds
85% is greater than or equal to 5%.
When the CPU usage of baseband processing unit is high, you are advised to perform capacity
expansion as follows:
l Migrate cells in the eNodeB. If the eNodeB has multiple baseband processing units and
one of them is overloaded, move cells from the overloaded baseband processing unit to a
baseband processing unit with a lighter load.
Baseband processing unit load can be indicated by the following:
Average CPU usage
Percentage of times that the CPU usage reaches or exceeds a preconfigured threshold
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. If a transport resource
group is congested, it cannot transmit or forward data, which affects service provision.
Figure 3-1 shows the position of transport resource group in the TCP/IP model.
Monitoring Methods
The following items are used in monitoring this case:
where
Suggested Measures
A transport resource group is congested if one 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. The following is an example command:
If the problem persists after the bandwidth adjustment, you are advised to expand the eNodeB
bandwidth.
Monitoring Principles
The Ethernet port traffic is the channel traffic at the physical layer, including uplink and downlink
traffic. The eNodeB Ethernet port traffic reflects the throughput and communication quality of
the Ethernet ports on the main control board of the eNodeB. Based on the monitoring results,
you can determine whether the transmission capacity allocated by an operator for the S1 and X2
interfaces on the eNodeB meet the requirements for uplink and downlink transmissions.
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 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 following command:
DSP BRD: CN=x, SRN=x, SN=x;
In the command output, the value of Config Type is the type of the main control board.
Suggested Measures
You are advised to perform transmission capacity expansion if either of the following conditions
is met:
l The proportion of the average uplink transmission rate (or 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 downlink reception rate) to
the allocated bandwidth reaches or exceeds 85% for at least two days in a week.
This chapter describes how to identify resource allocation problems. Network abnormalities can
be found through KPI monitoring. If a KPI is deteriorated, users can analyze the access counters
(RRC resource congestion rate and E-RAB resource congestion rate) to check whether the
deterioration is caused by resource congestion.
where
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 procedure begins with the identification of abnormal KPIs, followed up by
selecting and performing a KPI analysis on the top N cells.
Cell congestion mainly results from insufficient system resources. Bottlenecks can be detected
by analyzing the access counters (RRC resource congestion rate and E-RAB resource congestion
rate).
5 Related Counters