ERAN Capacity Monitoring Guide (V100R016C10 - 01) (PDF) - en

eRAN
V100R016C10
Capacity Monitoring Guide
Issue 01
Date 2020-04-07
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. 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: https://www.huawei.com
Email: [email protected]
Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Capacity Monitoring Guide Contents
Contents
1 eRAN Capacity Monitoring Guide........................................................................................1

1.1 Changes in eRAN Capacity Monitoring Guide.............................................................................................................. 2
1.2 Capacity Monitoring Overview........................................................................................................................................... 3
1.2.1 Introduction to Resources................................................................................................................................................. 3
1.2.2 Capacity Monitoring Methods......................................................................................................................................... 4
1.3 Network Resource Monitoring............................................................................................................................................5
1.3.1 Overview................................................................................................................................................................................. 5
1.3.2 Resource Usage During MTT........................................................................................................................................... 8
1.3.3 User Experience Satisfaction Rate............................................................................................................................... 10
1.3.4 FDD/TDD User Capacity Usage.................................................................................................................................... 11
1.3.5 PDCCH Resource Usage.................................................................................................................................................. 13
1.3.6 Throughput License Usage............................................................................................................................................. 16
1.3.7 FDD/TDD Paging Resource Usage............................................................................................................................... 17
1.3.8 MPT CPU Usage................................................................................................................................................................. 18
1.3.9 BBP CPU Usage.................................................................................................................................................................. 20
1.3.10 NB-IoT Paging Resource Usage................................................................................................................................. 23
1.3.11 NB-IoT User Capacity Usage....................................................................................................................................... 24
1.3.12 NB-IoT Subcarrier Usage.............................................................................................................................................. 25
1.4 Resource Congestion Diagnosis....................................................................................................................................... 26
1.4.1 FDD/TDD Resource Congestion Indicators............................................................................................................... 26
1.4.1.1 RRC Connection Congestion Rate............................................................................................................................ 26
1.4.1.2 E-RAB Congestion Rate................................................................................................................................................ 26
1.4.2 NB-IoT RRC Connection Congestion Indicators...................................................................................................... 26
1.4.3 Overall Procedure for Resource Analysis................................................................................................................... 27
Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
Capacity Monitoring Guide 1 eRAN Capacity Monitoring Guide
1 eRAN Capacity Monitoring Guide
Purpose
Growing traffic in mobile networks requires more and more resources. Lack of any
resources will affect user experience. This document provides guidelines on LTE
capacity monitoring and methods of identifying network resource bottlenecks. It
explains in detail how to monitor network resource usage. Capacity monitoring
provides data reference for network resource adjustment and capacity expansion
and enables maintenance personnel to take measures before network quality and
user experience deteriorate due to resource insufficiency.
This document does not apply to scenarios that involve a large capacity and a large amount of
traffic volume. For guidance in these scenarios, contact Huawei technical support.
Product Versions
The following table lists the product versions to which this document applies.
Product Solution Version Product Version

Name
BTS3900AL ● SRAN16.1 V100R016C10

● eRAN16.1
BTS3900
● eRAN TDD 16.1
BTS5900
BTS3900A
BTS3900L
BTS5900L
DBS3900
DBS5900
Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Product Solution Version Product Version

Name
DBS3900
LampSite
DBS5900
LampSite
Intended Audience
This document is intended for:
● Field engineers
● Network planning engineers
Organization
1.1 Changes in eRAN Capacity Monitoring Guide

This section describes changes in each issue of this document.
1.2 Capacity Monitoring Overview
This section describes the types of network resources to be monitored and the
methods of monitoring capacity.
1.3 Network Resource Monitoring
This section describes the principles, methods, and suggested measures for
network resource monitoring.
1.4 Resource Congestion Diagnosis
This section describes how to identify resource congestion problems. Network
exceptions can be found by KPI monitoring. There are a number of reasons of
network exceptions. If a KPI deteriorates, you can analyze access-related counters
to determine whether the deterioration is caused by limited capacity.
1.1 Changes in eRAN Capacity Monitoring Guide

This section describes changes in each issue of this document.
01 (2020-04-07)
This is the first commercial release.
Compared with Draft A (2020-01-20), this issue does not include any new topics
or changes, or exclude any topics.
Draft A (2020-01-20)
This is a draft.
Compared with Issue 01 (2019-06-06) of V100R015C10, this issue does not include
any new topics or changes, or exclude any topics.

eRAN
1.2 Capacity Monitoring Overview

This section describes the types of network resources to be monitored and the
methods of monitoring capacity.
1.2.1 Introduction to Resources

The following figure illustrates the resources that can be monitored.
Figure 1-1 Resources to be monitored
The following table explains the resources and their impacts.
Table 1-1 Summary of resources

Resource Type Meaning Impact of Resource Resource
Shortage Monitoring
Indicator
FDD or Physical Bandwidth of Affects admission of 1.3.2

TDD resource physical channels UEs and service Resource
cell blocks on the air interface experience of users Usage
(PRBs) that have been During MTT
admitted
Synchroni Number of Leads to 1.3.4

zed users synchronized UEs deterioration of FDD/TDD
KPIs and user User
experience Capacity
Usage

eRAN
Resource Type Meaning Impact of Resource Resource

Shortage Monitoring
Indicator
Physical Resources Prolongs uplink or 1.3.5 PDCCH

downlink allocated to the downlink Resource
control PDCCH scheduling delay Usage
channel and affects user
(PDCCH) experience
resources
eNode Throughp Maximum Affects user 1.3.6

B ut license permissible experience and Throughput
throughput of an customer revenue License
eNodeB Usage
Paging Paging capability Leads to paging 1.3.7

resources of an eNodeB message loss and FDD/TDD
affects user Paging
experience Resource
Usage
MPT CPU Processing Leads to KPI 1.3.8 MPT

capability of the deterioration CPU Usage
main control board
of an eNodeB
BBP CPU Processing Leads to KPI 1.3.9 BBP

capability of a deterioration CPU Usage
baseband
processing unit of
an eNodeB
NB-IoT NB-IoT paging Leads to paging 1.3.10 NB-

paging capability of an message loss and IoT Paging
resources eNodeB affects user Resource
experience Usage
NB-IoT RRC Number of UEs in Leads to 1.3.11 NB-

cell connected RRC_CONNECTED deterioration of IoT User
users mode KPIs and user Capacity
experience Usage
Subcarrier Subcarrier Affects user 1.3.12 NB-

s resources experience IoT
Subcarrier
Usage
1.2.2 Capacity Monitoring Methods

● Daily monitoring for prediction
The eNodeB defines diverse counters for measuring the usages of resources in
the E-UTRAN; it also defines thresholds for resource usages. If capacity

eRAN
monitoring detects that the consumption of a type of resource continually

exceeds the relevant threshold, preventive measures such as reconfiguration
or capacity expansion can be taken to prevent network congestion. For details
about this capacity monitoring method, see 1.3 Network Resource
Monitoring.
● Problem-driven analysis
This method uses in-depth analysis to identify whether a problem indicated
by counters is caused by network congestion. With this method, problems can
be precisely located so that users can work out a proper network optimization
and expansion solution. For details about this capacity monitoring method,
see 1.4 Resource Congestion Diagnosis.
1. Thresholds defined in this document for resource monitoring are generally lower than those
triggering alarms so that risks of resource insufficiency can be detected as early as possible.
2. The capacity expansion 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 determined
based on the CPU flow control threshold 80%. The RRC connected user license usage
threshold 60% is determined based on the peak-to-average ratio (about 1.5:1). When the
average usage reaches 60%, the peak usage approaches 100%. Both average and peak
values are considered when the threshold is determined. Operators can define their
thresholds based on their network operation conditions.
3. If the network load increases abruptly or even exceeds product specifications, operators can
either use the methods described in this document, which apply to networks experiencing a
steady growth, or define their own criteria based on their network quality requirements
during capacity expansion evaluation and handling. For example, they may perform capacity
expansion once network congestion occurs.
4. 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 evaluation and optimization (such as prediction, evaluation,
optimization, reconfiguration, and capacity expansion), contact Huawei technical support.
1.3 Network Resource Monitoring

This section describes the principles, methods, and suggested measures for
network resource monitoring.
1.3.1 Overview
This section describes monitoring principles, monitoring methods, and related
indicators for all types of resources. It also describes how to identify and handle
resource bottlenecks. Resource insufficiency may be indicated by more than one
monitoring item. For example, a resource bottleneck can be claimed only when
both RRC connected user license usage and MPT CPU usage exceed their
respective thresholds.
For accurate monitoring, this document assumes that all resources are monitored during busy
hours. It is recommended that busy hours be defined as a period when the base station or a cell
is undergoing the maximum resource consumption of a day.

eRAN
Differences Between Base Station Types

Base stations may differ in network resource monitoring. Table 1-2 lists the
differences.
Table 1-2 Differences between base station types

Monitoring Difference
Item
MPT CPU usage If the MPT CPU usage of a micro or LampSite base station
reaches or exceeds a threshold, the problem cannot be
solved by replacing its main control board.
Thresholds and Handling Suggestions

Table 1-3 describes the thresholds and handling suggestions for eRAN capacity
monitoring.
Table 1-3 Thresholds and handling suggestions

Categor Monitoring Conditions to Handling Suggestion
y Item Monitor
FDD or 1.3.2 PRB usage of Optimize radio frequency

TDD cell Resource downlink MTT ≥ 70% (RF) performance, expand
Usage and proportion of cell bandwidth, add carriers,
During MTT downlink MTT ≥ 30%; or add eNodeBs.
alternatively, PRB
usage of uplink MTT ≥
70% and proportion
of uplink MTT ≥ 30%
1.3.3 User Downlink 5 Mbit/s Optimize RF performance,

Experience user experience expand cell bandwidth, add
Satisfaction satisfaction rate ≤ carriers, or add eNodeBs.
Rate 90%
1.3.4 ● Synchronized user Optimize parameter

FDD/TDD capacity usage of a settings, optimize RF
User cell ≥ 60% performance, expand cell
Capacity ● RRC connected bandwidth, add carriers, or
Usage user capacity usage split cells.
of a board ≥ 60%
● RRC connected
user license usage
of an eNodeB ≥
60%

eRAN

y Item Monitor
1.3.5 PDCCH Control PDCCH Add carriers, split cells, or

Resource channel Symbol optimize RF performance.
Usage element Number
(CCE) Adjust
usage ≥ Switch is
50% on.
NB-IoT 1.3.11 NB- RRC connected user ● Reduce the NB-IoT UE

cell IoT User capacity usage of an inactivity timer length so
Capacity NB-IoT cell ≥ 60% that UEs can switch from
Usage RRC_CONNECTED mode
to RRC_IDLE mode as
early as possible when
there is no data
transmission for the UEs.
● Transfer UEs from the
local cell to its
neighboring cells.
● Add NB-IoT eNodeBs or
cells.
1.3.12 NB- Uplink NB-IoT Add NB-IoT eNodeBs or

IoT subcarrier usage ≥ cells.
Subcarrier 50% or downlink NB- Optimize RF performance to
Usage IoT subcarrier usage ≥ improve radio signal quality.
70%
eNodeB 1.3.6 Throughput license Increase the licensed

Throughput usage ≥ 80% throughput.
License
Usage
1.3.7 Percentage of paging Take one of the following

FDD/TDD messages received on measures:
Paging the S1 interface ≥ ● Decrease the number of
Resource 60% cells in the tracking area
Usage list (TAL) that the
congested cell belongs
to, based on live network
conditions.
● Adjust the paging policy
of the core network to
reduce signaling
overheads.
● If the core network is
composed of Huawei
products, enable the
precise paging function.

eRAN

y Item Monitor
1.3.10 NB- Percentage of NB-IoT Take one of the following

IoT Paging paging messages measures:
Resource received on the S1 ● Decrease the number of
Usage interface ≥ 60% cells in the tracking area
list (TAL) that the
congested cell belongs
to, based on live network
conditions.
● Adjust the paging
policies of the core
network.
1.3.8 MPT Average MPT CPU Balance loads, replace

CPU Usage usage ≥ 60% or boards with those of higher
percentage of times specifications, or add
the CPU usage eNodeBs.
reaches or exceeds
85% ≥ 5%
1.3.9 BBP Average BBP CPU Add boards, replace boards

CPU Usage usage ≥ 60% or with those of higher
percentage of times specifications, or balance
the CPU usage loads between BBPs.
reaches or exceeds
85% ≥ 5%
1.3.2 Resource Usage During MTT

This section describes how to determine whether a network resource bottleneck
has occurred based on the resource usage during MTT, and provides handling
suggestions.
Monitoring Principles
As the number of users increases, the resource usage during main traffic time
(MTT) is also increasing and user demands for resources cannot be satisfied,
causing user data rates and user experience satisfaction levels to decrease. In
experience-based load evaluation, a target is set for user experience satisfaction.
For example, the target is that 90% of users have an experienced data rate not
less than 5 Mbit/s. Analysis is required to identify a threshold of key resources that
hinders achievement of the target. This threshold is used as a reference for cell
capacity expansion.
Monitoring Methods
The resource usage during MTT is calculated as follows:
● Proportion of downlink MTT = L.Thrp.Time.Cell.MTT.DL/Measurement period
(s)

eRAN
● Proportion of uplink MTT = L.Thrp.Time.Cell.MTT.UL/Measurement period (s)

● PRB usage during downlink MTT = L.ChMeas.PRB.MTTDL.Used.Avg/
L.ChMeas.PRB.DL.Avail
● PRB usage during uplink MTT = L.ChMeas.PRB.MTTUL.Used.Avg/
L.ChMeas.PRB.UL.Avail
The counters involved are explained as follows:

● L.Thrp.Time.Cell.MTT.DL: This counter measures the downlink MTT of a cell. In
a measurement period, the downlink traffic volumes reported every second
are sorted in descending order and accrue. When the sum of n downlink
traffic volumes reaches the result of the total downlink traffic volume in the
measurement period multiplied by the MTT calculation threshold, n is taken
as the downlink MTT. (The MTT calculation threshold is specified by the
MttTrafficRatioThld parameter in the CellCounterParaGroup MO. Its default
value is 80%).
● L.Thrp.Time.Cell.MTT.UL: This counter measures the uplink MTT of a cell. In a
measurement period, the uplink traffic volumes reported every second are
sorted in descending order and accrue. When the sum of n uplink traffic
volumes reaches the result of the total uplink traffic volume in the
measurement period multiplied by the MTT calculation threshold, n is taken
as the uplink MTT. (The MTT calculation threshold is specified by the
MttTrafficRatioThld parameter in the CellCounterParaGroup MO. Its default
value is 80%).
● L.ChMeas.PRB.MTTDL.Used.Avg: This counter measures the average number
of downlink PRBs used during the downlink MTT of a cell.
● L.ChMeas.PRB.MTTUL.Used.Avg: This counter measures the average number
of uplink PRBs used during the uplink MTT of a cell.
● L.ChMeas.PRB.DL.Avail: This counter measures the number of available
downlink PRBs in a cell.
● L.ChMeas.PRB.UL.Avail: This counter measures the number of available uplink
PRBs in a cell.
LMPT boards are not compatible with the counters related to the resource usage
during MTT. For these boards, the radio resource congestion rate can be used to
evaluate whether to expand capacity. The radio resource congestion rate is
calculated as follows:
Radio resource congestion rate = MAX(L.ChMeas.PRB.PDSCH.Util.Samp.Index9/∑

(L.ChMeas.PRB.PDSCH.Util.Samp.Indexk), L.ChMeas.PRB.PUSCH.Util.Samp.Index9/∑
(L.ChMeas.PRB.PUSCH.Util.Samp.Indexk)), where k ranges from 0 to 9.
Suggested Measures
If the PRB usage during downlink (or uplink) MTT is greater than or equal to 70%
and the proportion of downlink (or uplink) MTT is greater than or equal to 30%
for a number of days (depending on site conditions; 3 days by default) within a
week and:
● If the proportion of small CQI values in the cell is greater than or equal to a
threshold (depending on site conditions; 10% by default), you are advised to
optimize RF performance to increase throughput.

eRAN
● If the proportion of small CQI values in the cell is less than the threshold, you
are advised to:
– Add carriers or increase the bandwidths of existing carriers.
– Add eNodeBs.
The proportion of small CQI values is calculated as follows:
Proportion of small CQI values = ∑(L.ChMeas.CQI.DL.X)/∑(L.ChMeas.CQI.DL.Y)
In this formula, x ranges from 0 to 3 and y ranges from 0 to 15.
L.ChMeas.CQI.DL.X and L.ChMeas.CQI.DL.Y measure the number of wideband CQI
reports with the value of x and y, respectively.
If an LMPT is used as the main control board, take the preceding measures when the radio
resource congestion rate is 10% or higher for a number of days (depending on site
conditions; 3 days by default) within a week.
1.3.3 User Experience Satisfaction Rate

has occurred based on the user experience satisfaction rate, and provides handling
suggestions.
The user data rate distribution in a cell can be derived from user-level rate
samples. The percentage of rate samples that reach the rate required by services is
considered as the user experience satisfaction rate. This satisfaction rate indicates
the probability that user data rates in a cell reaches the required rate.
Monitoring Methods
The user experience satisfaction rate is calculated as follows:
Downlink 2 Mbit/s user experience satisfaction rate =
The counters involved are explained as follows:

eRAN
L.Thrp.DL.BitRate.Samp.Index0 to L.Thrp.DL.BitRate.Samp.Index9: These counters

measure the numbers of samples with the throughput (per second) of downlink
PDCP SDUs in different ranges.
L.Thrp.bits.DL.PerUser.Out.Index0 to L.Thrp.bits.DL.PerUser.Out.Index5: These

counters measure the distribution of downlink PS throughput of UEs in a cell. The
downlink PS traffic volume is sampled per second. The traffic volume involves only
initial transmission and does not take RLC headers into account. The
corresponding counter is incremented by 1 each time a throughput value falls into
a specific range.
Suggested Measures
If the downlink 5 Mbit/s user experience satisfaction rate is less than or equal to
90% for a number of days (depending on site conditions; 1 day by default) within
a week and:
● If the proportion of small CQI values in the cell is greater than or equal to a
threshold (depending on site conditions; 10% by default), you are advised to
optimize RF performance to increase throughput.
● If the proportion of small CQI values in the cell is less than the threshold, you
are advised to:
– Add carriers or increase the bandwidths of existing carriers.
– Add eNodeBs.
The proportion of small CQI values is calculated as follows:
Proportion of small CQI values = ∑(L.ChMeas.CQI.DL.X)/∑(L.ChMeas.CQI.DL.Y)
In this formula, x ranges from 0 to 3 and y ranges from 0 to 15.

L.ChMeas.CQI.DL.X and L.ChMeas.CQI.DL.Y measure the number of wideband CQI
reports with the value of x and y, respectively.
1.3.4 FDD/TDD User Capacity Usage

has occurred based on the FDD/TDD user capacity usage, and provides handling
suggestions.
User capacity usage can be evaluated from three aspects:
● RRC connected user capacity usage of a cell
● RRC connected user capacity usage of a board
● RRC connected user license usage of an eNodeB
An RRC connected user is an LTE UE in RRC_CONNECTED mode. If the number of
users served by a cell or board exceeds the maximum number defined in the
product specifications, network KPIs deteriorate. If the number of users processed
by an eNodeB exceeds the licensed number, UE admission may fail.

eRAN
When the number of users reaches the capacity expansion threshold, the user-perceived rate has
already decreased to an unacceptable level. Therefore, the user-perceived rate must be
considered first. The number of users should be considered when operators are more concerned
with user capacity than user experience.
Monitoring Methods
● The RRC connected user capacity usage of a cell is calculated as follows:
RRC connected user capacity usage of a cell = L.Traffic.User.Max/Maximum
allowed number of RRC connected users in the cell x 100%
where
– L.Traffic.User.Max indicates the maximum number of users in the cell.
– For the RRC connected user capacity of a cell served by a 3900 or 5900
series base station, see 3900 & 5900 Series Base Station Technical
Description.
– For the RRC connected user capacity of a cell served by a BTS3202E, see
technical specifications in BTS3202E Technical Description.
– For the RRC connected user capacity of a cell served by a BTS3203E, see
technical specifications in BTS3203E Technical Description.
– For the RRC connected user capacity of a cell served by a BTS3911E or
BTS3912E, see technical specifications in Micro BTS3900 Series Technical
Description.
● RRC connected user capacity usage of a board
The RRC connected user capacity usage of a board is classified into the usage
of a BBP and the usage of a main control board. The calculation formula is as
follows:
RRC connected user capacity usage of boards in an eNodeB =
(L.Traffic.eNodeB.FDD.User.Max + L.Traffic.eNodeB.TDD.User.Max)/Total
maximum allowed number of RRC connected users on the boards x 100%
where
– L.Traffic.eNodeB.FDD.User.Max indicates the maximum number of LTE
FDD users served by the eNodeB.
– L.Traffic.eNodeB.TDD.User.Max indicates the maximum number of LTE
TDD users served by the eNodeB.
– For the maximum allowed number of RRC connected users on a BBP or
on the main control board of a 3900 or 5900 series base station, see 3900
& 5900 Series Base Station Technical Description.
● RRC connected user license usage of an eNodeB
The calculation formula is as follows:
RRC connected user license usage of an eNodeB =
(L.Traffic.eNodeB.FDD.User.Max + L.Traffic.eNodeB.TDD.User.Max)/Licensed
number of RRC connected users of the eNodeB x 100%
where
– L.Traffic.eNodeB.FDD.User.Max indicates the maximum number of LTE
FDD users served by the eNodeB.

eRAN
– L.Traffic.eNodeB.TDD.User.Max indicates the maximum number of LTE

TDD users served by the eNodeB.
– The method of querying the licensed number of RRC connected users of
an eNodeB is as follows:
For an LTE FDD eNodeB, run the command DSP LICINFO:
FUNCTIONTYPE=eNodeB;. In the command output, view the row in
which Model is LT1S0ACTUS00. The value in the Allocated column is the
licensed number of RRC connected users of the eNodeB.
For an LTE TDD eNodeB, run the command DSP LICINFO:
FUNCTIONTYPE=eNodeB;. In the command output, view the row in
which Model is LT1STACTUS00. The value in the Allocated column is the
licensed number of RRC connected users of the eNodeB.
Suggested Measures
● If the synchronized user capacity usage of a cell reaches or exceeds 60% for a
number of days (depending on site conditions; 3 days by default) within a
week, you are advised to take one of the following measures:
– Release UEs in connected mode as early as possible: Reduce the UE
inactivity timer length by running the MOD RRCCONNSTATETIMER
command with the UeInactiveTimer parameter specified. This measure
increases signaling overheads and 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.
● If the RRC connected user capacity usage of a main control board reaches or
exceeds 60% for a number of days (depending on site conditions; 3 days by
default) within a week, you are advised to take measures described in
"Suggested Measures" in 1.3.8 MPT CPU Usage.
● If the RRC connected user capacity usage of a BBP reaches or exceeds 60% for
a number of days (depending on site conditions; 3 days by default) within a
week, you are advised to take measures described in "Suggested Measures" in
1.3.9 BBP CPU Usage.
● If the RRC connected user license usage of an eNodeB reaches or exceeds
60% for a number of days (depending on site conditions; 3 days by default)
within a week, you are advised to determine the MPT CPU usage as described
in 1.3.8 MPT CPU Usage. Then:
– If the MPT CPU usage is less than 60%, you are advised to expand the
licensed capacity.
– If the MPT CPU usage reaches or exceeds 60%, you are advised to add
eNodeBs.
1.3.5 PDCCH Resource Usage

has occurred based on the PDCCH resource usage, and provides handling
suggestions.

eRAN
The PDCCH is composed of control channel elements (CCEs). The PDCCH resource
usage is expressed as the CCE usage on the PDCCH. If the CCE usage is excessively
high, CCEs may fail to be allocated to the new UEs to be scheduled. This failure
will result in a long scheduling delay and unsatisfactory user experience.
Monitoring Methods
The PDCCH resource usage is calculated as follows:
CCE usage (FDD) = (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed +

L.ChMeas.CCE.DLUsed)/Measurement period (in seconds)/1000/Maximum number
of PDCCH CCEs x 100%
CCE usage (TDD) = (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed +

L.ChMeas.CCE.DLUsed)/Measurement period (in seconds)/100/Maximum number
of PDCCH CCEs x 100%
where
● L.ChMeas.CCE.CommUsed indicates the number of PDCCH CCEs used for
common signaling.
● L.ChMeas.CCE.ULUsed indicates the number of PDCCH CCEs used for uplink
scheduling.
● L.ChMeas.CCE.DLUsed indicates the number of PDCCH CCEs used for
downlink scheduling.
Table 1-4 and Table 1-5 list the maximum number of PDCCH CCEs under
different configurations.
Table 1-4 Maximum number of PDCCH CCEs (FDD)
System Bandwidth Ng Maximum Number of PDCCH CCEs

(Configurable)
Number of Number of Number of
PDCCH PDCCH PDCCH
Symbols = 1 Symbols = 2 Symbols = 3
3 MHz 1/6 2 7 12
1/2 2 7 12
1 2 7 12
2 1 6 11
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

eRAN
System Bandwidth Ng Maximum Number of PDCCH CCEs

(Configurable)
Number of Number of Number of
PDCCH PDCCH PDCCH
Symbols = 1 Symbols = 2 Symbols = 3
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
In this table:
● The number of PDCCH symbols depends on the setting of the PDCCH Symbol
Number Adjust Switch parameter. The value of this parameter is displayed in
the LST CELLPDCCHALGO command output.
– If the value is On, the number of PDCCH symbols is 3.
– If the value is Enhanced CFI Adaption On, the number of PDCCH
symbols is 3.
– If the value is Off, the number of PDCCH symbols is equal to the PDCCH
Initial Symbol Number parameter value.
● The value of Ng is equal to the PHICH resource parameter value. The value is
displayed in the LST PHICHCFG command output.
Table 1-5 Maximum number of PDCCH CCEs per 10 ms (TDD)
System Port Uplink-Downlink Subframe Configuration

Bandwidth
(Configurable) 0 1 2 3 4 5 6
5 MHz 2 62 106 150 136 179 180 84
4 50 90 130 118 158 160 69
10 MHz 2 128 220 312 282 373 376 173
4 104 186 266 243 321 323 146

eRAN
System Port Uplink-Downlink Subframe Configuration

Bandwidth
(Configurable) 0 1 2 3 4 5 6
15 MHz 2 192 330 470 425 561 565 260
4 160 280 400 365 482 485 220
20 MHz 2 258 444 630 571 751 755 352
4 214 378 542 494 652 656 297
The number of ports listed in the preceding table is specified by the CRS Port
Number parameter. The uplink-downlink subframe configuration is specified by
the Subframe assignment parameter. The values of these parameters are
displayed in the LST CELL command output.
Suggested Measures
If the daily busy-hour CCE usage reaches or exceeds 50% for a number of days
(depending on site conditions; 3 days by default) within a week, perform the
operations described in this section.
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 of neighboring cells to
the PDCCH.
1.3.6 Throughput License Usage

has occurred based on the throughput license usage, and provides handling
suggestions.
When the eNodeB throughput exceeds its licensed capacity, the eNodeB will
control the traffic volume, which affects the user-perceived data rates of UEs and
the gains of customers.
Monitoring Methods
The throughput license usage is calculated as follows:
Downlink throughput license usage of an eNodeB = ∑(L.Thrp.bits.DL)/(Licensed
eNodeB throughput x 106 x Measurement period in seconds) x (1 –
LICRATIO.UpLicRatio/100) x 100%
Uplink throughput license usage of an eNodeB = ∑(L.Thrp.bits.UL)/(Licensed
eNodeB throughput x 106 x Measurement period in seconds) x
LICRATIO.UpLicRatio/100 x 100%

eRAN
Throughput license usage of an eNodeB = ∑(L.Thrp.bits.UL + L.Thrp.bits.DL)/

(Licensed eNodeB throughput x 106 x Measurement period in seconds) x 100%
where
● L.Thrp.bits.UL and L.Thrp.bits.DL indicate the uplink and downlink cell traffic
volume, respectively. ∑(L.Thrp.bits.UL + L.Thrp.bits.DL) indicates the sum of
uplink and downlink traffic volume of all cells served by the eNodeB.
● The LICRATIO.UpLicRatio parameter specifies the percentage of the licensed
uplink traffic to the total licensed traffic of the eNodeB. The total licensed
traffic is the sum of uplink and downlink licensed traffic. The default value of
this parameter is 25 (in the unit of %).
● The method of querying the licensed eNodeB throughput is as follows:
For an LTE FDD eNodeB, run the command DSP LICINFO:
FUNCTIONTYPE=eNodeB;. In the command output, view the row in which
Model is LT1S0THROU00. The value in the Allocated column is the licensed
eNodeB throughput.
For an LTE TDD eNodeB, run the command DSP LICINFO:
FUNCTIONTYPE=eNodeB;. In the command output, view the row in which
Model is LT1STTHROU00. The value in the Allocated column is the licensed
eNodeB throughput.
Suggested Measures
If the daily busy-hour downlink throughput license usage of an eNodeB is greater
than or equal to 80% for a number of days (depending on site conditions; 3 days
by default) within a week and the result of Downlink throughput license usage of
the eNodeB/Uplink throughput license usage of the eNodeB is greater than 2, you
are advised to decrease the value of the LICRATIO.UpLicRatio parameter. If the
daily busy-hour uplink throughput license usage of the eNodeB is greater than or
equal to 80% for a number of days (depending on site conditions; 3 days by
default) within a week and the result of Uplink throughput license usage of the
eNodeB/Downlink throughput license usage of the eNodeB is greater than 2, you
are advised to increase the value of the LICRATIO.UpLicRatio parameter.
If both the uplink throughput license usage and downlink throughput license
usage of the eNodeB meet requirements and the throughput license usage of the
eNodeB is greater than or equal to 80% for a number of days (depending on site
conditions; 3 days by default) within a week, you are advised to increase the
licensed throughput.
1.3.7 FDD/TDD Paging Resource Usage

has occurred based on the FDD/TDD paging resource usage, and provides
handling suggestions.
Paging messages are transferred over the S1 interface. Paging resource usage is
expressed as a percentage of paging messages received over the S1 interface. If
the number of paging times exceeds the eNodeB capacity, the paging messages

eRAN
sent from the eNodeB to UEs may be discarded, resulting in a decreased call
completion rate.
On the base station side, paging messages received by the main control board
over the S1 interface will be finally sent from the baseband processing unit (BBP)
over the air interface. If all the cells served by a BBU belong to the same tracking
area identified by a 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 BBPs depends on the overall paging
capability of the BBU.
The overall paging capability of the BBU is determined by the smaller capability
between the main control board and BBP capabilities. The capabilities of the main
control board and BBP are as follows:
● UMPT/LBBPd3/UBBPd/UBBPe/UBBPg: 2400 messages per second
● LMPT/LBBPc/LBBPd1/LBBPd2: 1800 messages per second
The paging capability is 400 messages per second for a BTS3205E, 500 messages
per second for a BTS3202E or BTS3203E, and 900 messages per second for a
BTS3911E or BTS3912E.
Monitoring Methods
The paging resource usage, expressed as a percentage of paging messages
received over the S1 interface, is calculated as follows:
Percentage of paging messages received over the S1 interface = L.Paging.S1.Rx/
Measurement period (in seconds)/Number of paging messages that can be
processed per second x 100%
In this formula, L.Paging.S1.Rx indicates the number of paging messages received
over the S1 interface.
Suggested Measures
If the daily percentage of paging messages received over the S1 interface reaches
or exceeds 60% for a number of days (depending on site conditions; 3 days by
default) within a week, you are advised to take one of the following measures:
● Decrease the number of cells in the TAL that the congested cell belongs to,
based on live network conditions.
● 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 overheads.
● Enable the precise paging function if the core network is provided by Huawei.
1.3.8 MPT CPU Usage

has occurred based on the MPT CPU usage, and provides handling suggestions.
The MPT CPU usage may occasionally become high for some reasons. However,
the occasional high CPU usage is not necessarily the basis for capacity expansion.

eRAN
Therefore, the evaluation of MPT CPU usage involves both the average MPT CPU
usage and the percentage of times the MPT CPU usage exceeds a preconfigured
threshold (85%).
The MPT CPU usage reflects how busy an eNodeB is. When the MPT CPUs are
busy processing control plane or user plane data, signaling-related KPIs may
deteriorate. For example, UEs may experience a low access success rate, low E-RAB
setup success rate, or high service drop rate.
Monitoring Methods
The evaluation of MPT CPU usage involves both the average MPT CPU usage and
the percentage of times the MPT CPU usage exceeds a preconfigured threshold
(85%).
● Average CPU usage = VS.BBUBoard.CPULoad.Mean
● Percentage of times the CPU usage exceeds a preconfigured threshold (85%)
= VS.BBUBoard.CPULoad.CumulativeHighloadCount/Measurement period (in
seconds) x 100%
In the formulas, VS.BBUBoard.CPULoad.CumulativeHighloadCount indicates the
number of times the CPU usage of the board exceeds the preconfigured threshold.
Suggested Measures
The MPT CPU of an eNodeB becomes overloaded if either of the following
conditions is met for a number of days (depending on site conditions; 3 days by
default) within a week:
● The average MPT CPU usage (VS.BBUBoard.CPULoad.Mean) reaches or
exceeds 60%.
● The percentage of times the MPT CPU usage exceeds a preconfigured
threshold (85%) is greater than or equal to 5%.
Take a measure as illustrated in Figure 1-2.

eRAN
Figure 1-2 Suggested measures
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 MPT with a higher-capacity one: If the main control board is an
LMPT, replace it with a UMPT.
3. Add eNodeBs.
1.3.9 BBP CPU Usage

has occurred based on the BBP CPU usage, and provides handling suggestions.

eRAN
The BBP CPU usage may occasionally become high for some reasons. However, the
occasional high CPU usage is not necessarily the basis for capacity expansion.
Therefore, the evaluation of BBP CPU usage involves both the average BBP CPU
usage and the percentage of times the BBP CPU usage exceeds a preconfigured
threshold (85%).
This capacity indicator measures the CPU usage of a BBP. If the eNodeB receives
too much traffic, the BBP CPU responsible for user plane processing will be heavily
loaded. Examples of the outcomes include a low RRC setup success rate, low E-
RAB setup success rate, low handover success rate, and high service drop rate.
Monitoring Methods
The evaluation of BBP CPU usage involves both the average BBP CPU usage and
the percentage of times the BBP CPU usage exceeds a preconfigured threshold
(85%).
Control-Plane CPU Usage
● Average control-plane CPU usage = VS.BBUBoard.CPULoad.Mean
● Percentage of times the control-plane CPU usage exceeds a preconfigured
threshold (85%) = VS.BBUBoard.CPULoad.CumulativeHighloadCount/
Measurement period (in seconds) x 100%
In the formulas, VS.BBUBoard.CPULoad.CumulativeHighloadCount indicates the
number of times the control-plane CPU usage of the board exceeds the
preconfigured threshold.
User-Plane CPU Usage
● Average user-plane CPU usage = L.Traffic.Board.UPlane.CPULoad.AVG
● Percentage of times the user-plane CPU usage exceeds a preconfigured
threshold (85%) = L.Traffic.Board.UPlane.CPULoad.CumulativeHighloadCount/
Measurement period (in seconds) x 100%
In the formulas, L.Traffic.Board.UPlane.CPULoad.CumulativeHighloadCount
indicates the number of times the user-plane CPU usage of the board exceeds the
preconfigured threshold.
Suggested Measures
The BBP CPU usage is considered too high if either of the following conditions is
met for a number of days (depending on site conditions; 3 days by default) within
a week:
● The average BBP control-plane CPU usage (VS.BBUBoard.CPULoad.Mean)
reaches or exceeds 60%. Alternatively, the average BBP user-plane CPU usage
(L.Traffic.Board.UPlane.CPULoad.AVG) reaches or exceeds 60%.
● The percentage of times the BBP control-plane CPU usage exceeds a
preconfigured threshold (85%) is greater than or equal to 5%. Alternatively,
the percentage of times the BBP user-plane CPU usage exceeds a
preconfigured threshold (85%) is greater than or equal to 5%.
When the BBP CPU usage is too high, capacity expansion is recommended. Figure
1-3 illustrates how to determine the measure for capacity expansion.

eRAN
Figure 1-3 Capacity expansion measures

eRAN
1. Migrate cells in the eNodeB.

If the eNodeB is equipped with multiple BBPs and one of the BBPs is
overloaded, move cells from this BBP to a BBP with lighter load.
The BBP load can be indicated by the average BBP CPU usage or the
percentage of times that the BBP CPU usage exceeds a preconfigured
threshold. Alternatively, it can be simply indicated by the number of cells on
the BBP. For details, see Cell Data Reconfigurations in eRAN Reconfiguration
Guide.
2. Replace the BBP with a higher-capacity BBP.
For example, if the BBP is an LBBPc, replace it with an LBBPd or UBBP. If the
BBP is an LBBPd, replace it with a UBBP. For detailed operations, see
Replacing BBPs in eRAN Reconfiguration Guide.
3. Add BBPs.
If the eNodeB has any vacant slot, add a BBP and migrate existing cells to the
new BBP for load sharing.
4. Add eNodeBs.
If the number of BBPs installed on the existing eNodeB has reached the
maximum allowed value, you have to add an eNodeB for capacity expansion.
To expand the capacity of a BTS3202E, BTS3203E, BTS3911E, or BTS3912E,
you can only add an eNodeB.
1.3.10 NB-IoT Paging Resource Usage

has occurred based on the NB-IoT paging resource usage, and provides handling
suggestions.
NB-IoT paging messages are transferred over the S1 interface. NB-IoT paging
resource usage is expressed as a percentage of NB-IoT paging messages received
over the S1 interface. If the paging resource usage exceeds the maximum value
defined in product specifications, paging messages may be discarded, affecting
user experience.
On the eNodeB side, paging messages received by the main control board over the
S1 interface will be finally sent from BBPs over the air interface. If all the cells
served by a BBU belong to the same tracking area identified by a 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 BBPs
depends on the overall paging capability of the BBU.
The overall paging capability of the BBU is determined by the smaller capability
between the main control board and BBP capabilities. The capabilities of the main
control board and BBP are as follows:
● UMPT, LBBPd3, and UBBPd: 2400 messages per second
● LMPT, LBBPc, LBBPd1, and LBBPd2: 1800 messages per second

eRAN
Monitoring Methods
The NB-IoT paging resource usage, expressed as a percentage of NB-IoT paging
messages received over the S1 interface, is calculated as follows:
Percentage of NB-IoT paging messages received over the S1 interface =
L.NB.Paging.S1.Rx/Measurement period (in seconds)/Maximum number of paging
messages that can be processed per second x 100%
In this formula, L.NB.Paging.S1.Rx indicates the number of NB-IoT paging
messages received over the S1 interface.
Suggested Measures
If the daily percentage of NB-IoT paging messages received over the S1 interface
reaches or exceeds 60% for a number of days (depending on site conditions; 3
days by default) within a week, you are advised to take one of the following
measures:
● Decrease the number of cells in the TAL that the congested cell belongs to,
based on live network conditions.
● Adjust the paging policies of the core network.
1.3.11 NB-IoT User Capacity Usage

has occurred based on the NB-IoT user capacity usage, and provides handling
suggestions.
The NB-IoT user capacity usage is expressed as the RRC connected user capacity
usage of individual NB-IoT cells. An NB-IoT RRC connected user is an NB-IoT UE in
RRC_CONNECTED mode. If the number of users in a cell exceeds the maximum
value defined in product specifications, network KPIs will deteriorate.
Monitoring Methods
The RRC connected user capacity usage of an NB-IoT cell is calculated as follows:
RRC connected user capacity usage of an NB-IoT cell = L.NB.Traffic.User.Max/
Maximum allowed number of RRC connected users in the NB-IoT cell x 100%
where L.NB.Traffic.User.Max indicates the maximum number of users in the NB-
IoT cell.
For the maximum allowed number of RRC connected users in an NB-IoT cell
served by a 3900 or 5900 series base station, see the technical specifications of an
NB-IoT eNodeB in 3900 & 5900 Series Base Station Technical Description.
Suggested Measures
If the RRC connected user capacity usage of an NB-IoT cell reaches or exceeds
60% in a number of days (depending on site conditions; 3 days by default) within
a week, you are advised to take one of the following measures:

eRAN
● Reduce the NB-IoT UE inactivity timer length so that UEs can switch from
RRC_CONNECTED mode to RRC_IDLE mode as early as possible when there is
no data transmission for the UEs. Specifically, run the MOD
RRCCONNSTATETIMER command with the NbUeInactiveTimer parameter
set to a smaller value. However, this measure will increase signaling
overheads and CPU usage.
● Transfer UEs from the local cell to its neighboring cells. If a neighboring cell is
lightly loaded, adjust the antenna downtilt angle or reduce the transmit
power of the local cell to shrink the coverage area of the local cell, and use
the similar methods to enlarge the coverage area of the neighboring cell for
load balancing.
● Add NB-IoT eNodeBs or cells.
1.3.12 NB-IoT Subcarrier Usage

has occurred based on the NB-IoT subcarrier usage, and provides handling
suggestions.
The NB-IoT subcarrier usage is classified into the following types:
● Uplink NB-IoT subcarrier usage, including 3.75 kHz and 15 kHz NB-IoT
subcarriers
● Downlink NB-IoT subcarrier usage
If the subcarrier usage exceeds the maximum value defined in product
specifications, user experience will deteriorate.
Monitoring Methods
The NB-IoT subcarrier usage is calculated as follows:
Uplink NB-IoT subcarrier usage = (L.NB.ChMeas.Subcarrier.3750Hz.UL.Used.Avg/4
+ L.NB.ChMeas.Subcarrier.15000Hz.UL.Used.Avg)/Maximum number of uplink
subcarriers/1000 x 100%
Downlink NB-IoT subcarrier usage = L.NB.PRB.ChMeas.Subcarrier.DL.Used.Avg/
Maximum number of downlink subcarriers/1000 x 100%
where
● L.NB.ChMeas.Subcarrier.3750Hz.UL.Used.Avg indicates the average number of
uplink 3.75 kHz subcarriers used in an NB-IoT cell.
● L.NB.ChMeas.Subcarrier.15000Hz.UL.Used.Avg indicates the average number
of uplink 15 kHz subcarriers used in an NB-IoT cell.
● L.NB.PRB.ChMeas.Subcarrier.DL.Used.Avg indicates the average number of
downlink 15 kHz subcarriers used in an NB-IoT cell.
● The maximum number of uplink subcarriers and that of downlink subcarriers
are both 12.
Suggested Measures
If the daily busy-hour uplink NB-IoT subcarrier usage reaches or exceeds 50% or
the daily busy-hour downlink NB-IoT subcarrier usage reaches or exceeds 70% in a

eRAN
number of days (depending on site conditions; 3 days by default) within a week,

you are advised to take one of the following measures:
● Add NB-IoT eNodeBs or cells.
● Optimize RF performance to improve radio signal quality.
1.4 Resource Congestion Diagnosis

This section describes how to identify resource congestion problems. Network
exceptions can be found by KPI monitoring. There are a number of reasons of
network exceptions. If a KPI deteriorates, you can analyze access-related counters
to determine whether the deterioration is caused by limited capacity.
1.4.1 FDD/TDD Resource Congestion Indicators

You can use counters to find out whether there is resource congestion, including
RRC connection congestion and E-RAB congestion.
1.4.1.1 RRC Connection Congestion Rate
The RRC connection congestion rate is calculated as follows:

RRC connection 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 a KPI deteriorates, analyze the RRC connection congestion rate. If the congestion
rate is higher than 0.2%, the KPI deterioration is caused by limited capacity.
1.4.1.2 E-RAB Congestion Rate
The E-RAB congestion rate is calculated as follows:

E-RAB congestion rate = L.E-RAB.FailEst.NoRadioRes/L.E-RAB.AttEst x 100%
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 a KPI deteriorates, analyze the E-RAB congestion rate. If the congestion rate is
higher than 0.2%, the KPI deterioration is caused by limited capacity.
1.4.2 NB-IoT RRC Connection Congestion Indicators

You can use the counters related to RRC connection congestion to find out
whether there is NB-IoT resource congestion.

eRAN
The NB-IoT RRC connection congestion rate is calculated as follows:
NB-IoT RRC connection congestion rate = L.NB.RRC.SetupFail.ResFail/

L.NB.RRC.ConnReq.Att x 100%
where
● L.NB.RRC.SetupFail.ResFail indicates the number of RRC connection setup

failures due to resource allocation failures in an NB-IoT cell.
● L.NB.RRC.ConnReq.Att indicates the number of RRC connection setup requests
in an NB-IoT cell (retransmission excluded).
If an NB-IoT KPI deteriorates, analyze the NB-IoT RRC connection congestion rate.
If the congestion rate exceeds 0.2%, the NB-IoT KPI deterioration is caused by
limited capacity.
1.4.3 Overall Procedure for Resource Analysis

Figure 1-4 shows the diagnosis procedure.
Figure 1-4 Diagnosis procedure

eRAN
The diagnosis procedure typically begins with the detection of abnormal KPIs,
followed up by selecting top N cells and performing a KPI analysis on the cells.
Cell congestion mainly results from insufficient system resources. Bottlenecks can
be identified by analyzing access-related KPIs (RRC connection congestion rate
and E-RAB congestion rate).

ERAN Capacity Monitoring Guide (V100R016C10 - 01) (PDF) - en

Uploaded by

Copyright:

Available Formats

ERAN Capacity Monitoring Guide (V100R016C10 - 01) (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

ERAN Capacity Monitoring Guide (V100R016C10 - 01) (PDF) - en

Uploaded by

Copyright:

Available Formats

eRAN

Capacity Monitoring Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. i

1 eRAN Capacity Monitoring Guide........................................................................................1

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. ii

1 eRAN Capacity Monitoring Guide

Product Solution Version Product Version

BTS3900AL ● SRAN16.1 V100R016C10

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 1

Product Solution Version Product Version

1.1 Changes in eRAN Capacity Monitoring Guide

1.1 Changes in eRAN Capacity Monitoring Guide

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 2

1.2 Capacity Monitoring Overview

1.2.1 Introduction to Resources

Figure 1-1 Resources to be monitored

The following table explains the resources and their impacts.

Table 1-1 Summary of resources

FDD or Physical Bandwidth of Affects admission of 1.3.2

Synchroni Number of Leads to 1.3.4

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 3

Resource Type Meaning Impact of Resource Resource

Physical Resources Prolongs uplink or 1.3.5 PDCCH

eNode Throughp Maximum Affects user 1.3.6

Paging Paging capability Leads to paging 1.3.7

MPT CPU Processing Leads to KPI 1.3.8 MPT

BBP CPU Processing Leads to KPI 1.3.9 BBP

NB-IoT NB-IoT paging Leads to paging 1.3.10 NB-

NB-IoT RRC Number of UEs in Leads to 1.3.11 NB-

Subcarrier Subcarrier Affects user 1.3.12 NB-

1.2.2 Capacity Monitoring Methods

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 4

monitoring detects that the consumption of a type of resource continually

1.3 Network Resource Monitoring

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 5

Differences Between Base Station Types

Table 1-2 Differences between base station types

Thresholds and Handling Suggestions

Table 1-3 Thresholds and handling suggestions

FDD or 1.3.2 PRB usage of Optimize radio frequency

1.3.3 User Downlink 5 Mbit/s Optimize RF performance,

1.3.4 ● Synchronized user Optimize parameter

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 6

Categor Monitoring Conditions to Handling Suggestion

1.3.5 PDCCH Control PDCCH Add carriers, split cells, or

NB-IoT 1.3.11 NB- RRC connected user ● Reduce the NB-IoT UE

1.3.12 NB- Uplink NB-IoT Add NB-IoT eNodeBs or

eNodeB 1.3.6 Throughput license Increase the licensed

1.3.7 Percentage of paging Take one of the following

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 7

Categor Monitoring Conditions to Handling Suggestion

1.3.10 NB- Percentage of NB-IoT Take one of the following

1.3.8 MPT Average MPT CPU Balance loads, replace

1.3.9 BBP Average BBP CPU Add boards, replace boards

1.3.2 Resource Usage During MTT

Issue 01 (2020-04-07) Copyright © Huawei Technologies Co., Ltd. 8