3900 Series Capacity Monitoring Guide V100R012C10_10 20171121105220

Capacity Monitoring Guide Contents 8.4.5 Capacity Monitoring Guide 8.4.5.1 GBSS Capacity Monitoring Guidelines 8.4.5.2 RAN Capacity Monitoring Guidelines 8.4.5.3 eRAN Capacity Monitoring Guide 8.4.5.3.1 Changes in eRAN Capacity Monitoring Guide 8.4.5.3.2 Overview 8.4.5.3.2.1 Introduction to Resources 8.4.5.3.2.2 Capacity Monitoring Methods 8.4.5.3.3 Network Resource Monitoring 8.4.5.3.3.1 Overview 8.4.5.3.3.2 Radio Resource Congestion Rate 8.4.5.3.3.3 User Capacity Usage 8.4.5.3.3.4 PDCCH Resource Usage 8.4.5.3.3.5 Throughput License Usage 8.4.5.3.3.6 Paging Resource Usage 8.4.5.3.3.7 Main-Control-Board CPU Usage 8.4.5.3.3.8 Baseband-Processing-Unit CPU Usage 8.4.5.3.3.9 NB-IoT Paging Resource Usage 8.4.5.3.3.10 NB-IoT User Capacity Usage 8.4.5.3.3.11 NB-IoT Subcarrier Usage 8.4.5.3.4 Resource Congestion Problem Identification 8.4.5.3.4.1 Resource Congestion Indicators 8.4.5.3.4.1.1 RRC Resource Congestion Rate 8.4.5.3.4.1.2 E-RAB Resource Congestion Rate 8.4.5.3.4.2 NB-IoT Resource Congestion Indicators 8.4.5.3.4.2.1 NB-IoT RRC Connection Congestion Indicators 8.4.5.3.4.3 Resource Allocation Problem Identification Process

8.4.5 Capacity Monitoring Guide

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

8.4.5.1 GBSS Capacity Monitoring Guidelines Related Document

Description

Download

GBSS Capacity Monitoring Guidelines (BSC6900-Based)

This document provides guidelines on GSM capacity monitoring including details on how to identify resource allocation problem and on how to monitor network resource usage.

You can obtain the BSC6900 GSM product documentation of corresponding version from HUAWEI Technical Support (support.huawei.com) in the following path: Support > Product Support > Wireless Network > GSM-BSS > GBSC > BSC6900 GSM. To go to GBSS Capacity Monitoring Guidelines (BSC6900-Based), choose Operation and Maintenance > Performance Management > GBSS Capacity Monitoring Guidelines (BSC6900-Based).

GBSS Capacity Monitoring Guidelines (BSC6910-Based)

This document provides guidelines on GSM capacity monitoring including details on how to identify resource allocation problem and on how to monitor network resource usage.

You can obtain the BSC6910 GSM product documentation of corresponding version from HUAWEI Technical Support (support.huawei.com),

Related Document

Description

Download

Support > Product Support > Wireless Network > GSMBSS > GBSC > BSC6910 GSM. To go to GBSS Capacity Monitoring Guidelines (BSC6910-Based), choose Operation and Maintenance > Performance Management > GBSS Capacity Monitoring Guidelines (BSC6910-Based).

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

8.4.5.2 RAN Capacity Monitoring Guidelines Related Document

Description

Download

RAN Capacity Monitoring Guidelines(BSC6900-Based)

This document provides guidelines on UMTS capacity monitoring including details on how to identify resource allocation problem and on how to monitor network resource usage.

You can obtain the BSC6900 UMTS product documentation of corresponding version from HUAWEI Technical Support (support.huawei.com) in the following path: Support > Product Support > Wireless Network > WCDMA-RAN > RNC > BSC6900 WCDMA. To go to RAN Capacity Monitoring Guidelines(BSC6900Based), choose

Related Document

Description

Download

Operation and Maintenance > Performance Management > RAN Capacity Monitoring Guidelines(BSC6900Based). RAN Capacity Monitoring Guidelines(BSC6910-Based)

This document provides guidelines on UMTS capacity monitoring including details on how to identify resource allocation problem and on how to monitor network resource usage.

You can obtain the BSC6910 UMTS product documentation of corresponding version from HUAWEI Technical Support (support.huawei.com), Support > Product Support > Wireless Network > WCDMA-RAN > RNC > BSC6910 WCDMA. To go to RAN Capacity Monitoring Guidelines(BSC6910Based), choose Operation and Maintenance > Performance Management > RAN Capacity Monitoring Guidelines(BSC6910Based).

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

8.4.5.3 eRAN Capacity Monitoring Guide Purpose Growing traffic in mobile networks requires more and more resources. Lack of resources will affect user experience. This document provides guidelines on LTE 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: The main control, transmission, and baseband processing units are deployed on the same board and share the CPU for BTS3202E, BTS3203E, BTS3911E and BTS3912E. The main control board and baseband board in this document are boards in BTS3202E, BTS3203E, BTS3911E and BTS3912E. The CPU usage of the main control board is the CPU usage of boards in BTS3202E, BTS3203E, BTS3911E and BTS3912E. This document does not apply to scenarios where a large amount of traffic volume is involved. For guidance in these scenarios, contact Huawei technical support.

The following table lists the eNodeB types and the corresponding eNodeB models. eNodeB Types

eNodeB Models

Macro

3900 series base stations, that is, BTS3900, BTS3900A, BTS3900L, BTS3900AL, and DBS3900

Micro

BTS3202E, BTS3203E, BTS3911E and BTS3912E

LampSite

DBS3900 LampSite

Product Version The following table lists the product version related to this document. Product Name

BTS3900AL BTS3900 BTS3900A BTS3900L DBS3900 DBS3900 LampSite BTS3202E BTS3203E

Solution Version  

SRAN12.1 eRAN12.1

Product Version

V100R012C10

Product Name

Solution Version

Product Version

BTS3912E BTS3911E

Intended Audience This document is intended for: 

Field engineers



Network planning engineers

Organization Changes in eRAN Capacity Monitoring Guide

This section describes changes in each issue of this document. Overview

This section describes the types of network resources to be monitored and the method of performing capacity monitoring. Network Resource Monitoring Resource Congestion Problem Identification

This section describes how to identify resource congestion problems. Network exceptions can be found through KPI monitoring. If a KPI deteriorates, you can analyze accessrelated counters to decide whether the deterioration is caused by limited capacity. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

8.4.5.3.1 Changes in eRAN Capacity Monitoring Guide This section describes changes in each issue of this document.

01 (2016-03-07) This is the first official release. Compared with issue Draft B (2017-02-10), this issue does not include any change.

Draft B (2017-02-10) This is a draft.

Compared with Draft A (2016-12-31), this issue does not include any new information or modify any issues. Compared with Draft A (2016-12-31), this issue deleted the following information: 

Performance Counters

Draft A (2016-12-31) This is a draft. Compared with Issue 02 (2016-08-01) of V100R011C10, this draft includes the following information new topics: 

Radio Resource Congestion Rate



NB-IoT Paging Resource Usage



NB-IoT User Capacity Usage



NB-IoT Subcarrier Usage



NB-IoT Resource Congestion Indicators

and its sub topics.

Compared with Issue 02 (2016-08-01) of V100R011C10, this draft includes the following changes. Topic

Change Description

Overview

Added the content of NB-IoT.

Performance Counters PDCCH Resource Usage

Added descriptions of the number of ports and uplink-downlink subframe configurations.

Compared with Issue 02 (2016-08-01) of V100R011C10, this issue excludes the following information: 

Downlink User Perception

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Next topic >

8.4.5.3.2 Overview This section describes the types of network resources to be monitored and the method of performing capacity monitoring. Introduction to Resources

Capacity Monitoring Methods

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.2.1 Introduction to Resources The following figure illustrates the resources to be monitored. Figure 1 Resources to be monitored

The following table describes the meaning and impact of the resources. Table 1 Meaning and impact of the resources Resource Type

Resource Meaning

Cell

Bandwidth of Affects the admission of physical channels on new users and the the air interface experience of users who have been admitted

PRBs

Impact of Resource Shortage

Resource Monitoring Indicator Radio Resource Congestion Rate

User Capacity Usage

Synchronized Number of user capacity synchronized users

Leads to deterioration of KPIs and user experience

PDCCH resources

Physical downlink control channel (PDCCH) resources

PDCCH Resource Usage Prolongs uplink or downlink scheduling delay and affects user experience

Maximum permissible throughput of an eNodeB

Affects user experience and customer income

eNodeB Throughput license

Throughput License Usage

Table 1 Meaning and impact of the resources Resource Type

Resource Meaning

Impact of Resource Shortage

Resource Monitoring Indicator

Paging resources

Paging capability of an eNodeB

Leads to paging message losses and affects user experience

Paging Resource Usage

MPT CPU

Processing capability of the main control board of an eNodeB

Leads to KPI deterioration

Main-Control-Board CPU Usage

BBP CPU

Processing capability of a BBP of an eNodeB

Leads to KPI deterioration

Baseband-Processing-Unit CPU Usage

NB-IoT paging resources

NB-IoT paging capability of an eNodeB

Leads to paging message losses and affects user experience

NB-IoT Paging Resource Usage

Number of users in RRC connected mode

Leads to deterioration of KPIs and user experience

NB-IoT User Capacity Usage

Subcarriers

Affects user experience

NB-IoT Subcarrier Usage

NB-IoT RRC cell connected user capacity Subcarriers

Parent Topic: Overview Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Next topic >

8.4.5.3.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. During basic capacity monitoring, preventive measures such as reconfiguration and capacity expansion can be taken to prevent network congestion when the consumption of a type of resource continually exceeds the threshold. For details about this capacity monitoring method, see Network Resource Monitoring.



Problem-driven analysis This method helps identify whether a problem indicated by counters is caused by network congestion through in-depth analysis. With this method, problems can be precisely located so

that users can work out a proper network optimization and expansion solution. For details about this capacity monitoring method, see Resource Congestion Problem Identification. NOTE: 1. 2.

3.

4.

Thresholds defined for resource monitoring are generally lower than those triggering alarms so that risks of resource insufficiency can be detected as early as possible. Thresholds given in this document apply to networks experiencing a steady growth. Thresholds are determined based on product specifications and experiences in working with existing networks. For example, the CPU usage threshold 60% is specified based on the CPU flow control threshold 80%. The eNodeB's RRC connected user license usage threshold 60% is specified based on the peak-to-average ratio (about 1.5:1). When the average usage reaches 60%, the peak usage approaches 100%. Threshold determining considers both average and peak values. Network operators can define the expansion criteria based on the actual situation. If the network load increases abruptly or even exceeds product specifications, whether to perform capacity expansion and how to perform can be determined based on methods applying to networks experiencing a steady growth; alternatively, network operators are allowed to perform capacity expansion based on requirements on network quality, for example, perform capacity expansion once network congestion occurs. Network 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.

Parent Topic: Overview Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic

8.4.5.3.3 Network Resource Monitoring Overview

This section describes monitoring principles, monitoring methods, and related counters of all types of resources. It also describes how to locate 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 main-control-board CPU usage exceed thresholds. Radio Resource Congestion Rate User Capacity Usage PDCCH Resource Usage Throughput License Usage Paging Resource Usage Main-Control-Board CPU Usage Baseband-Processing-Unit CPU Usage NB-IoT Paging Resource Usage NB-IoT User Capacity Usage NB-IoT Subcarrier Usage

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

< Previous topic Next topic >

8.4.5.3.3.1 Overview This section describes monitoring principles, monitoring methods, and related counters of all types of resources. It also describes how to locate 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 main-controlboard CPU usage exceed thresholds. NOTE: For accurate monitoring, all resources must be monitored during busy hours. It is recommended that busy hours be defined as a period when the system or a cell is undergoing the maximum resource consumption of a day. 

Differences in Monitoring Between eNodeB Types



Thresholds and Handling Suggestions

Differences in Monitoring Between eNodeB Types Table 1

lists the differences in monitoring between eNodeB types.

Table 1 Differences in monitoring between eNodeB types Monitoring Item

Difference

Main-control-board CPU usage

If the main-control-board CPU usage of a micro or LampSite eNodeB reaches or exceeds a threshold, the problem cannot be solved by replacing the main control board.

Thresholds and Handling Suggestions Table 2

describes the thresholds and handling suggestions for eRAN capacity monitoring.

Table 2 Monitoring thresholds and handling suggestions Type

Resource Monitoring Indicator

Monitoring Threshold

Handling Suggestion

Cell

Radio Resource Congestion Rate

Radio resource congestion rate > Optimize RF performance, expand cell 10% bandwidth, add carriers, or add eNodeBs.

Table 2 Monitoring thresholds and handling suggestions Type

Resource Monitoring Indicator User Capacity Usage

Monitoring Threshold

  

NB-IoT cell

Handling Suggestion

Synchronized user capacity Optimize parameter settings, optimize usage of a cell ≥ 60% RF performance, expand cell bandwidth, RRC connected user capacity add carriers, or split cells. usage of a board ≥ 60% RRC connected user capacity usage of an eNodeB ≥ 60%

PDCCH Resource Usage

CCE usage ≥ 50%

NB-IoT User Capacity Usage

RRC connected user capacity usage of an NB-IoT cell ≥ 60%

PDCCH Symbol Number Adjust Switch is set to ON(On).

Add carriers, split cells, or optimize RF performance.



  NB-IoT Subcarrier Usage

eNodeB Throughput

License Usage

Uplink NB-IoT subcarrier usage ≥ 50% or downlink NB-IoT subcarrier usage ≥ 70%

Reduce the NB-IoT UE inactivity timer length to switch users from RRC connected mode to RRC idle mode as early as possible when there is no data transmission. Transfer users from a local cell to its neighboring cells. Add NB-IoT eNodeBs or cells.

Add NB-IoT eNodeBs or cells. Optimize RF performance to improve signal quality.

Throughput license usage ≥ 80% Increase the licensed throughput.

Paging Resource Usage

Percentage of paging messages received on the S1 interface ≥ 60%

NB-IoT Paging Resource Usage

Percentage of NB-IoT paging messages received on the S1 interface ≥ 60%

Take one of the following measures:  Reduce the size of the TAL that contains the congested cell.  Adjust the paging policy of the core network to reduce signaling overhead.  If the core network is deployed by Huawei, enable the precise paging function. Take either of the following measures: Reduce the size of the tracking area list (TAL) that contains the congested cell.



Table 2 Monitoring thresholds and handling suggestions Type

Resource Monitoring Indicator

Monitoring Threshold

Handling Suggestion



Adjust the paging policies of the core network.

Main-ControlBoard CPU Usage

Average main-control-board Balance loads, replace old boards with CPU usage ≥ 60% or percentage those of higher specifications, or add of time the CPU usage reaches eNodeBs. or exceeds 85% ≥ 5%

BasebandProcessing-Unit CPU Usage

Average BBP CPU usage ≥ 60% Add boards, replace old boards with or percentage of time the CPU those of higher specifications, or balance usage reaches or exceeds 85% ≥ inter-BBP loads. 5%

Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Next topic >

8.4.5.3.3.2 Radio Resource Congestion Rate 

Monitoring Principles



Monitoring Methods



Suggested Measures

Monitoring Principles The radio resource congestion rate increases with the number of users. If the resource requirements of users are not fulfilled, user rates will decrease and user satisfaction will also decrease. Therefore, user satisfaction with perceived service quality is considered during experience-based load evaluation. For example, when the data rates of 90% of users reach 5 Mbit/s, the services are regarded as satisfactory and the corresponding key resource congestion threshold is taken as the cell capacity expansion threshold.

Monitoring Methods

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. The counters involved are described as follows: 

L.ChMeas.PRB.PDSCH.Util.Samp.Index0:

number of samples with the PDSCH PRB usage in the

range of [0,10%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index1:

number of samples with the PDSCH PRB usage in the

range of [10%, 20%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index2:

number of samples with the PDSCH PRB usage in the

range of [20%, 30%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index3:

number of samples with the PDSCH PRB usage in the

range of [30%, 40%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index4:

number of samples with the PDSCH PRB usage in the

range of [40%, 50%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index5:

number of samples with the PDSCH PRB usage in the

range of [50%, 60%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index6:

number of samples with the PDSCH PRB usage in the

range of [60%, 70%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index7:

number of samples with the PDSCH PRB usage in the

range of [70%, 80%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index8:

number of samples with the PDSCH PRB usage in the

range of [80%, 90%) in a cell 

L.ChMeas.PRB.PDSCH.Util.Samp.Index9:

number of samples with the PDSCH PRB usage in the

range of [90%, 100%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index0:

number of samples with the PUSCH PRB usage in the

range of [0, 10%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index1:

number of samples with the PUSCH PRB usage in the

range of [10%, 20%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index2:

number of samples with the PUSCH PRB usage in the

range of [20%, 30%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index3:

number of samples with the PUSCH PRB usage in the

range of [30%, 40%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index4:

range of [40%, 50%) in a cell

number of samples with the PUSCH PRB usage in the



L.ChMeas.PRB.PUSCH.Util.Samp.Index5:

number of samples with the PUSCH PRB usage in the

range of [50%, 60%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index6:

number of samples with the PUSCH PRB usage in the

range of [60%, 70%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index7:

number of samples with the PUSCH PRB usage in the

range of [70%, 80%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index8:

number of samples with the PUSCH PRB usage in the

range of [80%, 90%) in a cell 

L.ChMeas.PRB.PUSCH.Util.Samp.Index9:

number of samples with the PUSCH PRB usage in the

range of [90%, 100%) in a cell

Suggested Measures If the radio resource congestion rate is 10% or higher in several days (configurable, 3 days by default) in a week, then: 

If the CQI proportion in a cell is greater than or equal to a threshold (configurable, 10% by default), you are advised to optimize RF performance to increase throughput.



If the CQI proportion in a cell is less than the threshold, you are advised to: 

Add carriers or expand the bandwidths of existing carriers.



Add eNodeBs.

The CQI proportion is calculated as follows: CQI proportion = ∑(L.ChMeas.CQI.DL.x) / ∑(L.ChMeas.CQI.DL.y) In the formula, x ranges from 0 to 3 and y ranges from 0 to 15. L.ChMeas.CQI.DL.x measures the number of times wideband CQI x is reported and L.ChMeas.CQI.DL.y measures the number of times wideband CQI y is reported. Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.3 User Capacity Usage 

Monitoring Principles



Monitoring Methods



Suggested Measures

Monitoring Principles User capacity usage can be evaluated by the following three items: 

Synchronized 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 in the LTE is one who is in the RRC_Connected state, and a synchronized user is an RRC connected user in the synchronization state. When the number of users processed within a cell or by a board exceeds the maximum number defined in the product specifications, network KPIs deteriorate. When the number of users processed by an eNodeB exceeds the maximum number defined in the license, user admission fails. NOTE: When the number of users reaches or exceeds the preconfigured threshold, the user-perceived rate has already decreased to an unacceptable level. Therefore, the user-perceived rate should be considered first. The number of users should be considered first when capacity takes priority over user experience.

Monitoring Methods 

Synchronized user capacity usage of a cell The calculation formula is as follows: Synchronized user capacity usage of a cell = L.Traffic.User.Max / Maximum number of RRC connected users in a cell x 100% where





L.Traffic.User.Max



For details about the maximum number of synchronized users that a single cell served by a BTS3202E supports, see Technical Specifications in BTS3202E Technical Description.



For details about the maximum number of synchronized users that a single cell served by a BTS3203E supports, see Technical Specifications in BTS3203E LTE Technical Description.



For details about the maximum number of synchronized users that a single cell served by a BTS3911E or BTS3912E supports, see "Technical Specifications" in Micro BTS3900 Series Technical Description.

indicates the maximum number of RRC connected users in a cell.

RRC connected user capacity usage of a board The RRC connected user capacity usage of a board involves the baseband processing unit (BBP) and the main control board. The calculation formula is as follows:

RRC connected user capacity usage of a board = L.Traffic.eNodeB.User.Max / Maximum number of RRC connected users of a board x 100% where 

L.Traffic.eNodeB.User.Max

indicates the maximum number of RRC connected users of an

eNodeB. 



For details about the maximum number of RRC connected users of a BBP or main control board, see Technical Specifications of the eNodeB FDD and Technical Specifications of the eNodeB TDD in 3900 Series Base Station Technical Description, respectively.

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.User.Max / Number of licensed RRC connected users of an eNodeB x 100% where 

L.Traffic.eNodeB.User.Max

indicates the maximum number of RRC connected users of an

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 displayed command output, view the line in which Model is LT1S0ACTUS00. The value in the Allocated column is the licensed RRC connected users of the eNodeB. For an LTE TDD eNodeB, run the command DSP LICINFO: FUNCTIONTYPE=eNodeB;. In the displayed command output, view the line in which Model is LT1STACTUS00. The value in the Allocated column is the licensed RRC connected users of the eNodeB.

Suggested Measures 

If the synchronized user capacity usage of a cell reaches or exceeds 60% for X days (three days by default) in a week, you are advised to take one of the following measures: 

Release UEs in idle mode as early as possible: Reduce the UE inactivity timer length by running the MOD RRCCONNSTATETIMER command with the UeInactiveTimer parameter specified. This measure increases signaling overhead 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 X days (three days by default) in a week, you are advised to take measures given in "Suggested Measures" in Main-Control-Board CPU Usage.



If the RRC connected user capacity usage of a BBP reaches or exceeds 60% for X days (three days by default) in a week, you are advised to take measures given in "Suggested Measures" in Baseband-Processing-Unit CPU Usage.



If the RRC connected user license usage of an eNodeB reaches or exceeds 60% for X days (three days by default) in a week, you are advised to determine the main-control-board CPU usage first by referring to Main-Control-Board CPU Usage: 

If the main-control-board CPU usage is less than 60%, you are advised to expand the capacity defined in the license.



If the main-control-board CPU usage reaches or exceeds 60%, you are advised to add eNodeBs.

Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.4 PDCCH Resource Usage 

Monitoring Principles



Monitoring Methods



Suggested Measures

Monitoring Principles This capacity indicator measures the number of control channel elements (CCEs) that can be used by the PDCCH. If the CCE usage is excessively high, CCEs may fail to be allocated to the new UEs to be scheduled, which will result in a long service delay and unsatisfactory user experience.

Monitoring Methods The following item is used in monitoring this case: CCE usage in LTE FDD = (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed) / measurement period (in the unit of second) / 1000 / Maximum number of PDCCH CCEs x 100%

CCE usage in LTE TDD = (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed) / measurement period (in the unit of second) / 100 / Maximum number of PDCCH CCEs x 100% where 

L.ChMeas.CCE.CommUsed



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

indicates the number of PDCCH CCEs used for common signaling.

and Table 2 list the maximum number of PDCCH CCEs in different configurations.

Table 1 Maximum number of PDCCH CCEs in LTE FDD System Bandwidth (Configurable)

Ng

3 MHz

5 MHz

10 MHz

15 MHz

Maximum Number of PDCCH CCEs Number of PDCCH Symbols =1

Number of PDCCH Symbols =2

Number of PDCCH Symbols = 3

1/6

2

7

12

1/2

2

7

12

1

2

7

12

2

1

6

11

1/6

4

13

21

1/2

4

12

21

1

3

12

20

2

2

11

19

1/6

10

26

43

1/2

9

26

42

1

8

25

41

2

6

23

39

1/6

15

40

65

1/2

14

39

64

Table 1 Maximum number of PDCCH CCEs in LTE FDD System Bandwidth (Configurable)

Ng

20 MHz

Maximum Number of PDCCH CCEs Number of PDCCH Symbols =1

Number of PDCCH Symbols =2

Number of PDCCH Symbols = 3

1

12

37

62

2

9

34

59

1/6

20

54

87

1/2

19

52

86

1

17

50

84

2

13

46

80

In preceding tables: 



The number of PDCCH symbols depends on the PDCCH Symbol Number Adjust Switch parameter value, which can be queried by running the LST CELLPDCCHALGO command. 

If the parameter value is On, the number of PDCCH symbols is 3.



If the parameter value is ECFIADAPTIONON, the number of PDCCH symbols is 3.



If the parameter value is Off, the number of PDCCH symbols is equal to the PDCCH Initial Symbol Number parameter value.

The value of Ng is equal to the PHICH resource parameter value, which can be queried by running the LST PHICHCFG command.

Table 2 Maximum number of PDCCH CCEs within 10 ms in LTE TDD System Port Bandwidth (Configurable)

Uplink-Downlink Subframe Configuration SA0

SA1

SA2

SA3

SA4

SA5

SA6

5 MHz

2

62

106

150

136

179

180

84

4

50

90

130

118

158

160

69

2

128

220

312

282

373

376

173

4

104

186

266

243

321

323

146

10 MHz

Table 2 Maximum number of PDCCH CCEs within 10 ms in LTE TDD System Port Bandwidth (Configurable)

Uplink-Downlink Subframe Configuration SA0

SA1

SA2

SA3

SA4

SA5

SA6

15 MHz

2

192

330

470

425

561

565

260

4

160

280

400

365

482

485

220

2

258

444

630

571

751

755

352

4

214

378

542

494

652

656

297

20 MHz

The number of ports listed in the preceding table is specified by the CRS Port Number parameter. To query the CRS Port Number and Subframe assignment values, run the LST CELL command.

Suggested Measures If the CCE usage during busy hours reaches or exceeds 50% for X days (three days by default) in a week, perform the following operations: 

If the PDCCH Symbol Number Adjust Switch parameter value is On, you are advised to: 

Add cells or split existing cells.



Optimize RF performance to reduce the interference to PDCCH from neighboring cells.

Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.5 Throughput License Usage 

Monitoring Principles



Monitoring Methods



Suggested Measures

Monitoring Principles

When the traffic volume in an eNodeB exceeds the license capacity, the eNodeB will control the traffic volume, which affects the data rate perceived by UEs and customers' gains.

Monitoring Methods The following item is used in monitoring this case: Throughput license usage of an eNodeB = ∑(L.Thrp.bits.UL + L.Thrp.bits.DL) / (Licensed eNodeB throughput x measurement period (in the unit of second)) x 100% where 

L.Thrp.bits.UL



The method of querying the licensed eNodeB throughput is as follows:

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 under an eNodeB.

For an LTE FDD eNodeB, run the command DSP LICINFO: FUNCTIONTYPE=eNodeB;. In the displayed command output, view the line in which Model is LT1S0THROU00. The value in the Allocated column is the licensed throughput of the eNodeB. For an LTE TDD eNodeB, run the command DSP LICINFO: FUNCTIONTYPE=eNodeB;. In the displayed command output, view the line in which Model is LT1STTHROU00. The value in the Allocated column is the licensed throughput of the eNodeB.

Suggested Measures If the eNodeB throughput license usage reaches or exceeds 80% for X days (three days by default) in a week, you are advised to increase the licensed throughput. Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.6 Paging Resource Usage Monitoring Principles Paging messages are sent over the S1 interface. Therefore, paging resource usage can be evaluated by the percentage of paging messages received on the S1 interface. If the number of paging times exceeds the maximum, the paging messages sent from the eNodeB to UEs may be discarded, resulting in a decreased call success rate.

On the eNodeB side, paging messages received by the main control board over the S1 interface will be finally sent over the air interface through the baseband processing unit (BBP). If all the cells served by an BBU belong to the same tracking area identified by the tracking area code (TAC), all the paging messages received by the main control board need to be sent out through each BBP. Whether the paging messages can be sent out through the BBP depends on the overall paging capability of the BBP. The overall paging capability of the BBU is determined by the smaller specification between the main control board and BBP. The specifications of the main control board and BBP are as follows: 

UMPT/LBBPd3/UBBPd: 2400 messages/second.



LMPT/LBBPc/LBBPd1/LBBPd2: 1800 messages/second.

The eNodeBs BTS3205E can send a maximum of 400 paging messages per second. The eNodeBs BTS3202E and BTS3203E LTE can send a maximum of 500 paging messages per second. The eNodeBs BTS3911E and BTS3912E can send a maximum of 900 paging messages per second.

Monitoring Methods The paging resource usage is evaluated by the percentage of paging messages received on the S1 interface. The calculation formula is as follows: Percentage of paging messages received on the S1 interface = L.Paging.S1.Rx / measurement period (in the unit of second) / Maximum number of paging messages that can be processed per second x 100% In the preceding formula, L.Paging.S1.Rx indicates the number of paging messages received over the S1 interface.

Suggested Measures If the percentage of paging messages received on the S1 interface reaches or exceeds 60% for X days (three days by default) in a week, you are advised to take either of the following measures: 

Decrease the number of cells in the tracking area list (TAL) that the congested cell belongs to.



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.



Enable the precise paging function if the core network is deployed by Huawei.

Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.7 Main-Control-Board CPU Usage 

Monitoring Principles



Monitoring Methods



Suggested Measures

Monitoring Principles The CPU usage of the main control board becomes high occasionally due to some reasons. However, the occasional high CPU usage is not necessarily the basis for capacity expansion. Therefore, the main-control-board CPU usage is jointly evaluated by the average main-controlboard CPU usage and the percentage of times that the main-control-board CPU usage reaches or exceeds a preconfigured threshold (85%). The main-control-board CPU usage reflects the busy level of the eNodeB. If the main-controlboard CPUs are busy processing control plane or user plane data, signaling-related KPIs may deteriorate, and UEs may experience a low access success rate, low E-RAB setup success rate, or high service drop rate.

Monitoring Methods The main-control-board CPU usage is evaluated by the average CPU usage and the percent of times that the main-control-board CPU usage reaches or exceeds a preconfigured threshold (85%). 

Average CPU usage: VS.BBUBoard.CPULoad.Mean



Percentage of times that the main-control-board CPU usage reaches or exceeds a preconfigured threshold (85%) = VS.BBUBoard.CPULoad.CumulativeHighloadCount / Measurement period (in the unit of second) x 100%

where, VS.BBUBoard.CPULoad.CumulativeHighloadCount indicates the number of times that the CPU usage of the board exceeds a preconfigured threshold.

Suggested Measures The main-control-board CPU of a local eNodeB becomes overloaded if either of the following conditions is met for X days (three days by default) in a week: 

VS.BBUBoard.CPULoad.Mean



The percentage of times that the main-control-board CPU usage reaches or exceeds 85% is greater than or equal to 5%.

reaches or exceeds 60%.

Take one of the following measures:

Figure 1 Suggested Measures

1. Transfer UEs from the local eNodeB: If a neighboring eNodeB is lightly loaded, adjust the antenna downtilt angles or decrease the transmit power of the local eNodeB to shrink the coverage area and reduce the CPU load of the local eNodeB. In addition, expand the coverage area of the neighboring eNodeB for load balancing. 2. Replace the main control board with a UMPT: If the main control board is an LMPT, replace it with a UMPT. This measure can not be used in BTS3202E, BTS3203E, BTS3911E and BTS3912E. 3. Add eNodeBs. Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.8 Baseband-Processing-Unit CPU Usage 

Monitoring Principles



Monitoring Methods



Suggested Measures

Monitoring Principles The CPU usage of the baseband processing unit (BBP) becomes high occasionally due to some reasons. However, the occasional high CPU usage is not necessarily the basis for capacity expansion. Therefore, the BBP CPU usage is jointly evaluated by the average BBP CPU usage and the percentage of times that the BBP CPU usage reaches or exceeds a preconfigured threshold (85%). This capacity indicator measures the BBP CPU usage. If the eNodeB receives too much traffic, the BBP CPU responsible for user plane processing will be heavily loaded. As a result, the eNodeB will experience a low RRC setup success rate, low E-RAB setup success rate, low handover success rate, and high service drop rate.

Monitoring Methods Based on the type of data processed by the BBP, the BBP CPU usage is classified into controlplane CPU usage and user-plane CPU usage. The BBP CPU usage is jointly evaluated by the average BBP CPU usage and the percentage of times that the BBP CPU usage reaches or exceeds a preconfigured threshold (85%). The involved indicators are described as follows: Control-plane CPU usage 

Average control-plane CPU usage: VS.BBUBoard.CPULoad.Mean



Percentage of times that the control-plane CPU usage reaches or exceeds a preconfigured threshold (85%) = VS.BBUBoard.CPULoad.CumulativeHighloadCount / Measurement period (in the unit of second) x 100%

where, VS.BBUBoard.CPULoad.CumulativeHighloadCount indicates the number of times that the controlplane CPU usage of the board exceeds a preconfigured threshold. User-plane CPU usage 

Average user-plane CPU usage: L.Traffic.Board.UPlane.CPULoad.AVG



Percentage of times that the user-plane CPU usage reaches or exceeds a preconfigured threshold (85%) = L.Traffic.Board.UPlane.CPULoad.CumulativeHighloadCount / Measurement period (in the unit of second) x 100%

where, L.Traffic.Board.UPlane.CPULoad.CumulativeHighloadCount indicates the number of times that the user-plane CPU usage of the board exceeds a preconfigured threshold.

Suggested Measures

The BBP CPU of a local eNodeB becomes overloaded if either of the following conditions is met for X days (three days by default) in a week: 

VS.BBUBoard.CPULoad.Mean



The percentage of times that the control-plane CPU usage reaches or exceeds 85% or percentage of times that the user-plane CPU usage reaches or exceeds 85% is greater than or equal to 5%.

or L.Traffic.Board.UPlane.CPULoad.AVG reaches or exceeds 60%.

When the BBP CPU usage is high, you are advised to perform capacity expansion as follows: Figure 1 Capacity Expansion

1. Migrate cells in the eNodeB. If the eNodeB has multiple BBPs and one of them is overloaded, move cells from the overloaded BBP to a BBP with a lighter load. The BBP load can be indicated by the average CPU usage, the percentage of times that the CPU usage reaches or exceeds a preconfigured threshold, or the number of cells established on a BBP.

2. Replace a BBP with low specifications with one with high specifications. For example, if the BBP is an LBBPc, replace the LBBPc with an LBBPd or a UBBP. If the BBP is an LBBPd, replace the LBBPd with a UBBP. 3. Add a BBP. If the eNodeB has vacant slots, add a BBP and migrate existing cells to the new BBP for load sharing. 4. Add eNodeBs. Add an eNodeB for capacity expansion if the number of BBP boards has reached the maximum value that can be added.To expand the capacity of a BTS3202E, BTS3203E, BTS3911E and BTS3912E, you can only add another BTS3202E, BTS3203E, BTS3911E or BTS3912E. Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.9 NB-IoT Paging Resource Usage Monitoring Principles NB-IoT paging messages are transmitted over the S1 interface. The NB-IoT paging resource usage can be estimated using the proportion of NB-IoT paging messages received over the S1 interface. If the paging resource usage exceeds a threshold, paging messages may be lost and user experience may be affected. Paging messages that arrive at the main control board through the S1 interface will sent out from BBPs through the air interface. If all cells of a BBU belong to the same tracking area, all paging messages that arrive at the main control board need to be sent out from each BBP. The paging capability of the BBU determines whether paging messages can be sent out. The overall paging capability of the BBU is determined by the smaller specification between the main control board and BBP. The specifications of the main control board and BBP are as follows: 

UMPT, LBBPd3, and UBBPd: 2400 paging messages per second



LMPT, LBBPc, LBBPd1, and LBBPd2: 1800 paging messages per second

Monitoring Methods The NB-IoT paging resource usage can be estimated using the proportion of NB-IoT paging messages received over the S1 interface. Proportion of NB-IoT paging messages received over the S1 interface = L.NB.Paging.S1.Rx / Measurement period (unit: s) / Maximum number of paging messages sent per second x 100%

L.NB.Paging.S1.Rx

indicates the number of paging messages received over the S1 interface in an

NB-IoT cell.

Suggested Measures If the proportion of NB-IoT paging messages received over the S1 interface each day reaches or exceeds 60% in x days (configurable, three days by default) a week, you are advised to take one of the following measures: 

Reduce the size of the TAL that contains the congested cell.



Adjust the paging policies of the core network.

Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.10 NB-IoT User Capacity Usage Monitoring Principles The NB-IoT user capacity usage is estimated using the NB-IoT RRC connected user capacity usage. If the number of RRC connected users reaches or exceeds a threshold, network KPIs will deteriorate.

Monitoring Methods The NB-IoT RRC connected user capacity usage is calculated as follows: NB-IoT RRC connected user capacity usage = L.NB.Traffic.User.Max / NB-IoT RRC connected user capacity x 100% L.NB.Traffic.User.Max

indicates the maximum number of users in an NB-IoT cell.

Suggested Measures If the NB-IoT RRC connected user capacity usage each day reaches or exceeds 60% in x days (configurable, three days by default) a week, you are advised to take one of the following measures: 

Reduce the NB-IoT UE inactivity timer length to switch users from RRC connected mode to RRC idle mode as early as possible when there is no data transmission. Specifically, run the MOD RRCCONNSTATETIMER command to set the NbUeInactiveTimer parameter to a smaller value. However, this measure will increase signaling overhead and CPU usage.



Transfer users from a local cell to its neighboring cells. If the neighboring cells are lightly loaded, adjust the downtilt angles of antennas or reduce transmit power to shrink the coverage

area of the local cell while using the similar methods to enlarge the coverage areas of the neighboring cells for load balancing. 

Add NB-IoT eNodeBs or cells.

Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.3.11 NB-IoT Subcarrier Usage Monitoring Principles The following types of NB-IoT subcarrier usage need to be monitored: 

3.75 kHz uplink NB-IoT subcarrier usage and 15 kHz uplink NB-IoT subcarrier usage



Downlink NB-IoT subcarrier usage

If the subcarrier usage exceeds a threshold, 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 x 100% Downlink NB-IoT subcarrier usage = L.NB.ChMeas.Subcarrier.DL.Used.Avg / Maximum number of downlink subcarriers x 100% where 

L.NB.ChMeas.Subcarrier.3750Hz.UL.Used.Avg

indicates the average number of 3.75 kHz uplink

subcarriers used in an NB-IoT cell. 

L.NB.ChMeas.Subcarrier.15000Hz.UL.Used.Avg

indicates the average number of 15 kHz uplink

subcarriers used in an NB-IoT cell. 

L.NB.ChMeas.Subcarrier.DL.Used.Avg



The maximum number of uplink subcarriers and that of downlink subcarriers are both 12.

indicates the average number of 15 kHz downlink subcarriers used in an NB-IoT cell.

Suggested Measures If the uplink NB-IoT subcarrier usage during busy hours each day reaches or exceeds 50% or the downlink NB-IoT subcarrier usage during busy hours each day reaches or exceeds 70% in

x days (configurable, three days by default) a week, you are advised to take one of the following measures: 

Add NB-IoT eNodeBs or cells.



Optimize RF performance to improve signal quality.

Parent Topic: Network Resource Monitoring Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic

8.4.5.3.4 Resource Congestion Problem Identification This section describes how to identify resource congestion problems. Network exceptions can be found through KPI monitoring. If a KPI deteriorates, you can analyze access-related counters to decide whether the deterioration is caused by limited capacity. Resource Congestion Indicators NB-IoT Resource Congestion Indicators Resource Allocation Problem Identification Process

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic

8.4.5.3.4.1 Resource Congestion Indicators You can use counters to decide whether there is resource congestion (RRC connection congestion or E-RAB congestion). Table 1 describes the related counters. Table 1 Related counters Counter ID

Counter Description

L.RRC.ConnReq.Att

Number of RRC Connection Request messages (excluding retransmitted messages) received from UEs in a cell

L.RRC.ConnReq.Succ

Number of RRC Connection Setup Complete messages received from UEs in a cell

L.E-RAB.AttEst

Number of times UEs attempt to initiate E-RAB setup procedures

L.E-RAB.SuccEst

Number of successful E-RAB setup procedures initiated by UEs

Table 1 Related counters Counter ID

Counter Description

L.E-RAB.AbnormRel

Number of E-RABs that have data to transmit but are abnormally released by the eNodeB

L.E-RAB.NormRel

Number of E-RABs that are normally released by the eNodeB

RRC Resource Congestion Rate E-RAB Resource Congestion Rate

Parent Topic: Resource Congestion Problem Identification Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Next topic >

8.4.5.3.4.1.1 RRC Resource Congestion Rate The RRC resource congestion rate is a cell-level indicator. It is calculated using the following formula: RRC resource congestion rate = L.RRC.SetupFail.ResFail / L.RRC.ConnReq.Att x 100% where L.RRC.SetupFail.ResFail

indicates the number of RRC connection setup failures due to resource

allocation failures. L.RRC.ConnReq.Att

indicates the number of RRC connection setup requests.

If the RRC resource congestion rate is higher than 0.2%, KPI deterioration is caused by resource congestion. Parent Topic: Resource Congestion Indicators Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Next topic >

8.4.5.3.4.1.2 E-RAB Resource Congestion Rate The E-RAB resource congestion rate is a cell-level indicator. It is calculated using the following formula: E-RAB resource congestion rate = L.E-RAB.FailEst.NoRadioRes / L.E-RAB.AttEst x 100%

where L.E-RAB.FailEst.NoRadioRes

indicates the number of E-RAB setup failures due to radio resource

insufficiency. L.E-RAB.AttEst

indicates the number of E-RAB setup attempts.

If the E-RAB resource congestion rate is higher than 0.2%, KPI deterioration is caused by resource congestion. Parent Topic: Resource Congestion Indicators Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic

8.4.5.3.4.2 NB-IoT Resource Congestion Indicators NB-IoT resource congestion is indicated by RRC connection congestion. You can use the following counters to decide whether there is congestion. Table 1 NB-IoT counters Counter ID

Counter Description

L.NB.RRC.ConnReq.Att

Number of RRC connection setup requests (excluding retransmitted requests) in an NB-IoT cell

L.NB.RRC.SetupFail.ResFail

Number of RRC connection setup failures due to resource allocation failures in an NB-IoT cell

NB-IoT RRC Connection Congestion Indicators

Parent Topic: Resource Congestion Problem Identification Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic Next topic >

8.4.5.3.4.2.1 NB-IoT RRC Connection Congestion Indicators 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 indicates the number of RRC connection setup failures due to resource allocation failures in an NB-IoT cell. L.NB.RRC.SetupFail.ResFail

indicates the number of RRC connection setup requests (excluding retransmitted requests) in an NB-IoT cell. L.NB.RRC.ConnReq.Att

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. Parent Topic: NB-IoT Resource Congestion Indicators Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

8.4.5.3.4.3 Resource Allocation Problem Identification Process Figure 1

shows the process of identifying resource allocation problems.

Figure 1 Process of identifying resource allocation problems

The fault location process begins with the identification of abnormal KPIs, followed up by selecting and performing a KPI analysis on the top N cells. Cell congestion mainly results from insufficient system resources. Bottlenecks can be detected by analyzing the access counters (RRC resource congestion rate and E-RAB resource congestion rate). Parent Topic: Resource Congestion Problem Identification Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. < Previous topic