Beruflich Dokumente
Kultur Dokumente
0
Capacity Monitoring Guide
Issue DraftA
Date 2014-1-20
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
For definitions of the man-machine language (MML) commands, parameters, alarms, and
performance counters mentioned in this document, see the "Operation and Maintenance" part in
3900 Series LTE eNodeB Product Documentation for eNodeB base station, BTS3202E Product
Documentation for BTS3202E base station, and BTS3203E LTE Product Documentation for
BTS3203E base station.
For the BTS3202E and the BTS3203E LTE, the main control unit, transmission unit, and baseband
unit share the CPU because they are integrated into the same board, called BTS3202E board or
BTS3203E LTE board. The main control board and the baseband board mentioned in this document
correspond to the BTS3202E board or BTS3203E LTE board, and the CPU usage of the main
control board corresponds to that of the BTS3202E board or BTS3203E LTE board.
This document is not applicable to scenarios with large capacity and heavy traffic. For guidelines in
such scenarios, contact Huawei technical support.
Product Versions
The following table lists the product version related to this document.
Intended Audience
This document is intended for:
Field engineers
Network planning engineers
Change History
This section describes changes in each issue of this document.
Draft A (2014-1-20)
Draft A (2014-1-20)
This is the first draft.
Contents
2 Capacity Monitoring..................................................................................................................... 4
2.1 Introduction ...................................................................................................................................................... 4
2.2 Downlink User Perception ............................................................................................................................... 5
2.2.1 Monitoring Principles ............................................................................................................................. 5
2.2.2 Monitoring Methods ............................................................................................................................... 6
2.2.3 Suggested Measures ................................................................................................................................ 6
2.3 PRACH Resource Usage .................................................................................................................................. 6
2.3.1 Monitoring Principles ............................................................................................................................. 6
2.3.2 Monitoring Methods ............................................................................................................................... 6
2.3.3 Suggested Measures ................................................................................................................................ 7
2.4 PDCCH Resource Usage .................................................................................................................................. 7
2.4.1 Monitoring Principles ............................................................................................................................. 7
2.4.2 Monitoring Methods ............................................................................................................................... 8
2.4.3 Suggested Measures ................................................................................................................................ 8
2.5 Connected User License Usage ........................................................................................................................ 8
2.5.1 Monitoring Principles ............................................................................................................................. 8
2.5.2 Monitoring Methods ............................................................................................................................... 8
2.5.3 Suggested Measures ................................................................................................................................ 9
2.6 Paging Resource Usage .................................................................................................................................... 9
2.6.1 Monitoring Principles ............................................................................................................................. 9
2.6.2 Monitoring Methods ............................................................................................................................... 9
2.6.3 Suggested Measures ................................................................................................................................ 9
2.7 Main-Control-Board CPU Usage ................................................................................................................... 10
2.7.1 Monitoring Principles ........................................................................................................................... 10
2.7.2 Monitoring Methods ............................................................................................................................. 10
2.7.3 Suggested Measures .............................................................................................................................. 10
2.8 LBBP CPU Usage .......................................................................................................................................... 11
2.8.1 Monitoring Principles ........................................................................................................................... 11
1 Overview
This chapter describes the types of network resources to be monitored and the method of
performing capacity monitoring.
Table 1-1 describes the types of network resources to be monitored and impacts of resource
insufficiency on the system.
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.
Thresholds given in this document apply to networks experiencing a steady growth. Thresholds are
determined based on experiences. For example, the 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.
Telecom operators can define thresholds based on the actual situation.
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.
2 Capacity Monitoring
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 connected user
license usage and main-control-board CPU usage exceed the predefined thresholds.
2.1 Introduction
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 2-1 describes types of resources to be monitored, thresholds, and handling suggestions.
PDCCH Resource Usage CCE usage Uplink or downlink Set PDCCH Symbol
80% PRB usage < 90% Number Adjust Switch
to On.
Uplink or downlink
No handling is required.
PRB usage 90%
Connected User License Connected Main-control-board
Add licenses.
Usage user license CPU usage < 60%
usage 60%
Main-control-board
Add eNodeBs.
CPU usage 60%
Paging Resource Usage Decrease the number of
Percentage of paging messages cells in the tracking area
received on the S1 interface 60% or list (TAL) that the
number of paging messages 1500 congested cell belongs
to.
Main-Control-Board Average main-control-board CPU
CPU Usage usage 60% or percentage of times Expand the control-plane
that the CPU usage reaches or capacity of the eNodeB.
eNodeB
exceeds 85% 5%
resources
LBBP CPU Usage Average LBBP CPU usage 60% or
Expand the user-plane
percentage of times that the CPU
capacity of the eNodeB.
usage reaches or exceeds 85% 5%
Transport Resource Packet loss rate 0.05%, proportion
Group Usage of average transmission rate to Expand the bandwidth of
configured bandwidth 80%, or the transport resource
proportion of maximum transmission group.
rate to configured bandwidth 90%
Ethernet Port Traffic Proportion of average transmission
rate to allocated bandwidth 70% or Expand the eNodeB
Proportion of maximum transmission transmission capacity.
rate to allocated bandwidth 85%
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;
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.
If the value of PDCCH Symbol Number Adjust Switch is On, you do not need to monitor PDCCH
resource usage. The reason is that the eNodeB automatically adjusts the number of PDCCH symbols
based on the CCE load to meet the CCE requirement while preventing excessive PDSCH resource
consumption. You can run the LST CELLPDCCHALGO command to query the setting of PDCCH
Symbol Number Adjust Switch.
The percentage of paging messages received by the eNodeB over the S1 interface
reaches or exceeds 60%.
1500 or more paging messages from the mobility management entity (MME) to UEs are
discarded in a day.
If the problem persists after the bandwidth adjustment, you are advised to expand the eNodeB
bandwidth.
LMPT
For items 1 and 2: 360 Mbit/s
For items 3 and 4: 540 Mbit/s
BTS3202E board or
For items 1 and 2: 60 Mbit/s
BTS3203E LTE board For items 3 and 4: 178 Mbit/s
Enable UMPT
For items 1 and 2: value of UL
Committed Information Rate (Kbit/s)
LMPT
For items 3 and 4: value of DL
Committed Information Rate (Kbit/s)
You can run the LST LR command to query the values of LR Switch, UL Committed
Information Rate (Kbit/s), and DL Committed Information Rate (Kbit/s).
The types of main control boards can be queried by running the 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.
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.
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).
4 Related Counters