EnodeB Performance Monitoring

eNodeB
V100R005C00
Performance Monitoring
Reference

Issue 06
Date 2012-09-20

HUAWEI TECHNOLOGIES CO., LTD.

Issue 06 (2012-09-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i

Copyright Huawei Technologies Co., Ltd. 2012. 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: http://www.huawei.com
Email: support@huawei.com

eNodeB
Performance Monitoring Reference Contents

ii

Contents
1 About This Document .................................................................................................................. 1
2 Introduction.................................................................................................................................... 8
2.1 Overview .......................................................................................................................................................... 8
2.2 Performance Monitoring Types ........................................................................................................................ 8
2.3 Precautions ..................................................................................................................................................... 10
2.3.1 Precautions for Monitoring on 3900 Series Base Station ...................................................................... 10
2.3.2 Precautions for Monitoring on BTS3202Es .......................................................................................... 10
3 CPU Usage Monitoring .............................................................................................................. 11
3.1 CPU Usage Monitoring .................................................................................................................................. 11
3.1.1 Usage Scenario ...................................................................................................................................... 11
3.1.2 Service Impact ...................................................................................................................................... 11
3.1.3 Parameters ............................................................................................................................................. 11
3.1.4 Monitoring Results ................................................................................................................................ 11
4 CPRI BER Monitoring ................................................................................................................ 13
4.1 CPRI BER Monitoring ................................................................................................................................... 13
4.1.1 Usage Scenario ...................................................................................................................................... 13
4.1.2 Service Impact ...................................................................................................................................... 13
4.1.3 Parameters ............................................................................................................................................. 13
5 RRU/RFU Performance Monitoring ........................................................................................ 15
5.1 RRU/RFU Output Power Monitoring ............................................................................................................ 15
5.1.1 Usage Scenario ...................................................................................................................................... 15
5.1.2 Service Impact ...................................................................................................................................... 15
5.1.3 Parameters ............................................................................................................................................. 15
5.2 RRU/RFU Temperature Monitoring ............................................................................................................... 16
5.2.1 Usage Scenario ...................................................................................................................................... 16
5.2.2 Service Impact ...................................................................................................................................... 16
5.2.3 Parameters ............................................................................................................................................. 16
5.3 Sector Performance Monitoring ..................................................................................................................... 17
eNodeB

iii

5.3.1 Usage Scenario ...................................................................................................................................... 17
5.3.2 Service Impact ...................................................................................................................................... 17
5.3.3 Parameters ............................................................................................................................................. 17
5.4 Spectrum Detection ........................................................................................................................................ 18
5.4.1 Usage Scenario ...................................................................................................................................... 18
5.4.2 Service Impact ...................................................................................................................................... 18
5.4.3 Parameters ............................................................................................................................................. 18
6 Transmission Performance Monitoring.................................................................................. 20
6.1 IP Link Monitoring ......................................................................................................................................... 20
6.1.1 Usage Scenario ...................................................................................................................................... 20
6.1.2 Service Impact ...................................................................................................................................... 20
6.1.3 Parameters ............................................................................................................................................. 20
6.2 IP Path Performance Monitoring .................................................................................................................... 22
6.2.1 Usage Scenario ...................................................................................................................................... 22
6.2.2 Service Impact ...................................................................................................................................... 22
6.2.3 Parameters ............................................................................................................................................. 23
6.3 IP Performance Monitoring ............................................................................................................................ 24
6.3.1 Usage Scenario ...................................................................................................................................... 24
6.3.2 Service Impact ...................................................................................................................................... 24
6.3.3 Parameters ............................................................................................................................................. 24
6.4 SCTP Performance Monitoring ...................................................................................................................... 25
6.4.1 Usage Scenario ...................................................................................................................................... 25
6.4.2 Service Impact ...................................................................................................................................... 25
6.4.3 Parameters ............................................................................................................................................. 26
6.5 Transmission Performance Monitoring .......................................................................................................... 27
6.5.1 Usage Scenario ...................................................................................................................................... 27
6.5.2 Service Impact ...................................................................................................................................... 27
6.5.3 Parameters ............................................................................................................................................. 27
6.6 UDP Injection Test Monitoring ...................................................................................................................... 31
6.6.1 Usage Scenario ...................................................................................................................................... 31
6.6.2 Service Impact ...................................................................................................................................... 31
6.6.3 Parameters ............................................................................................................................................. 31
6.7 Local Pass-By Traffic Monitoring .................................................................................................................. 32
eNodeB

iv

6.7.1 Usage Scenario ...................................................................................................................................... 32
6.7.2 Service Impact ...................................................................................................................................... 32
6.7.3 Parameters ............................................................................................................................................. 33
6.8 Resource Group Monitoring ........................................................................................................................... 33
6.8.1 Usage Scenario ...................................................................................................................................... 33
6.8.2 Service Impact ...................................................................................................................................... 33
6.8.3 Parameters ............................................................................................................................................. 34
6.9 PPPoE Performance Monitoring .................................................................................................................... 38
6.9.1 Usage Scenario ...................................................................................................................................... 38
6.9.2 Service Impact ...................................................................................................................................... 38
6.9.3 Parameters ............................................................................................................................................. 38
7 Cell Performance Monitoring ................................................................................................... 40
7.1 Service Satisfaction Monitoring ..................................................................................................................... 40
7.1.1 Usage Scenario ...................................................................................................................................... 40
7.1.2 Service Impact ...................................................................................................................................... 40
7.1.3 Parameters ............................................................................................................................................. 40
7.2 General Throughput Monitoring .................................................................................................................... 42
7.2.1 Usage Scenario ...................................................................................................................................... 42
7.2.2 Service Impact ...................................................................................................................................... 42
7.2.3 Parameters ............................................................................................................................................. 43
7.3 Service Statistics Monitoring ......................................................................................................................... 46
7.3.1 Usage Scenario ...................................................................................................................................... 46
7.3.2 Service Impact ...................................................................................................................................... 46
7.3.3 Parameters ............................................................................................................................................. 46
7.4 User Statistics Monitoring .............................................................................................................................. 47
7.4.1 Usage Scenario ...................................................................................................................................... 47
7.4.2 Service Impact ...................................................................................................................................... 47
7.4.3 Parameters ............................................................................................................................................. 47
7.5 RB Usage Monitoring .................................................................................................................................... 50
7.5.1 Usage Scenario ...................................................................................................................................... 50
7.5.2 Service Impact ...................................................................................................................................... 50
7.5.3 Parameters ............................................................................................................................................. 50
7.6 ICIC Monitoring ............................................................................................................................................. 52
eNodeB

v

7.6.1 Usage Scenario ...................................................................................................................................... 52
7.6.2 Service Impact ...................................................................................................................................... 52
7.6.3 Parameters ............................................................................................................................................. 52
7.7 MU-MIMO Monitoring.................................................................................................................................. 54
7.7.1 Usage Scenario ...................................................................................................................................... 54
7.7.2 Service Impact ...................................................................................................................................... 54
7.7.3 Parameters ............................................................................................................................................. 54
7.8 Interference RSSI Statistic Detect Monitoring ............................................................................................... 55
7.8.1 Usage Scenario ...................................................................................................................................... 55
7.8.2 Service Impact ...................................................................................................................................... 55
7.8.3 Parameters ............................................................................................................................................. 55
7.9 Interference Detection Monitoring ................................................................................................................. 56
7.9.1 Usage Scenario ...................................................................................................................................... 56
7.9.2 Service Impact ...................................................................................................................................... 56
7.9.3 Parameters ............................................................................................................................................. 56
7.10 Scheduled Cell-Level UE Information Monitoring ...................................................................................... 57
7.10.1 Usage Scenario .................................................................................................................................... 57
7.10.2 Service Impact .................................................................................................................................... 57
7.10.3 Parameters ........................................................................................................................................... 57
7.10.4 Monitoring Results .............................................................................................................................. 58
7.11 HARQ Status Monitoring ............................................................................................................................. 58
7.11.1 Usage Scenario .................................................................................................................................... 58
7.11.2 Service Impact ..................................................................................................................................... 58
7.11.3 Parameters ........................................................................................................................................... 58
7.12 Air-Interface DCI Status Monitoring ............................................................................................................ 61
7.12.1 Usage Scenario .................................................................................................................................... 61
7.12.2 Service Impact .................................................................................................................................... 62
7.12.3 Parameters ........................................................................................................................................... 62
7.13 Air-Interface DRB Statistics Monitoring ...................................................................................................... 63
7.13.1 Usage Scenario .................................................................................................................................... 63
7.13.2 Service Impact .................................................................................................................................... 63
7.13.3 Parameters ........................................................................................................................................... 64
8 User Performance Monitoring .................................................................................................. 67
8.1 DL RSRP/RSRQ Monitoring ......................................................................................................................... 67
eNodeB

vi

8.1.1 Usage Scenario ...................................................................................................................................... 67
8.1.2 Service Impact ...................................................................................................................................... 67
8.1.3 Parameters ............................................................................................................................................. 67
8.2 BLER Monitoring .......................................................................................................................................... 68
8.2.1 Usage Scenario ...................................................................................................................................... 68
8.2.2 Service Impact ...................................................................................................................................... 68
8.2.3 Parameters ............................................................................................................................................. 68
8.3 Power Headroom Monitoring ......................................................................................................................... 70
8.3.1 Usage Scenario ...................................................................................................................................... 70
8.3.2 Service Impact ...................................................................................................................................... 71
8.3.3 Parameters ............................................................................................................................................. 71
8.4 Channel Quality Monitoring .......................................................................................................................... 71
8.4.1 Usage Scenario ...................................................................................................................................... 71
8.4.2 Service Impact ...................................................................................................................................... 71
8.4.3 Parameters ............................................................................................................................................. 72
8.5 Scheduling Monitoring ................................................................................................................................... 73
8.5.1 Usage Scenario ...................................................................................................................................... 73
8.5.2 Service Impact ...................................................................................................................................... 73
8.5.3 Parameters ............................................................................................................................................. 73
8.6 RLC Data Stream Monitoring ........................................................................................................................ 75
8.6.1 Usage Scenario ...................................................................................................................................... 75
8.6.2 Service Impact ...................................................................................................................................... 75
8.6.3 Parameters ............................................................................................................................................. 76
8.7 Throughput Monitoring .................................................................................................................................. 76
8.7.1 Usage Scenario ...................................................................................................................................... 76
8.7.2 Service Impact ...................................................................................................................................... 76
8.7.3 Parameters ............................................................................................................................................. 77
8.8 AQM Monitoring ........................................................................................................................................... 78
8.8.1 Usage Scenario ...................................................................................................................................... 78
8.8.2 Service Impact ...................................................................................................................................... 78
8.8.3 Parameters ............................................................................................................................................. 78
8.9 Uplink Power Control Monitoring ................................................................................................................. 79
8.9.1 Usage Scenario ...................................................................................................................................... 79
8.9.2 Service Impact ...................................................................................................................................... 79
eNodeB

vii

8.9.3 Parameters ............................................................................................................................................. 79
8.10 Downlink Power Control Monitoring .......................................................................................................... 81
8.10.1 Usage Scenario .................................................................................................................................... 81
8.10.2 Service Impact .................................................................................................................................... 81
8.10.3 Parameters ........................................................................................................................................... 81
8.11 Uplink ICIC Monitoring ............................................................................................................................... 84
8.11.1 Usage Scenario .................................................................................................................................... 84
8.11.2 Service Impact ..................................................................................................................................... 84
8.11.3 Parameters ........................................................................................................................................... 84
8.12 MCS Statistics Monitoring ........................................................................................................................... 85
8.12.1 Usage Scenario .................................................................................................................................... 85
8.12.2 Service Impact .................................................................................................................................... 85
8.12.3 Parameters ........................................................................................................................................... 85
9 Clock Performance Monitoring ................................................................................................ 88
9.1 Clock Quality Test .......................................................................................................................................... 88
9.1.1 Usage Scenario ...................................................................................................................................... 88
9.1.2 Service Impact ...................................................................................................................................... 88
9.1.3 Parameters ............................................................................................................................................. 88
9.2 IP Clock Data Collection ................................................................................................................................ 89
9.2.1 Usage Scenario ...................................................................................................................................... 89
9.2.2 Service Impact ...................................................................................................................................... 89
9.2.3 Parameters ............................................................................................................................................. 89

eNodeB
Performance Monitoring Reference 1 About This Document

1

1 About This Document
Purpose
This document describes the information about eNodeB-related performance monitoring tasks,
including:
The descriptions of parameters for performance monitoring
The descriptions of monitor items
The value range of each monitor item
The formula used to calculate the value of each monitor item
Product Versions
The following table lists the product version related to this document.
Product Name Product Version
DBS3900 LTE V100R005C00
DBS3900 LTE TDD V100R005C00
BTS3900 LTE V100R005C00
BTS3900A LTE V100R005C00
BTS3900L LTE V100R005C00
BTS3900AL LTE V100R005C00
BTS3202E V100R005C00

Intended Audience
This document is intended for:
System engineers
Site maintenance engineers
eNodeB

2

Change History
The following describes the changes in eNodeB Performance Monitoring Reference.
The document issues are as follows:
06(2012-09-20)
05(2012-07-30)
04 (2012-06-29)
03 (2012-05-11)
02 (2012-04-28)
01 (2012-03-30)
Draft B (2012-02-15)
Draft A (2012-01-10)
06 (2012-09-20)
This is the sixth official release.
Compared with issue 05 (2012-07-30) of V100R005C00, this issue does not include any new
information.
Compared with issue 05 (2012-07-30) of V100R005C00, this issue includes the following
changes.
Topic Change Description
7.7 MU-MIMO Monitoring Modified the description of MU-MIMO Monitoring.
7.1 Service Satisfaction Monitoring Modified the description of Service Satisfaction
Monitoring.
7.2 General Throughput Monitoring Modified the description of General Throughput
Monitoring.
7.3 Service Statistics Monitoring Modified the description of Service Statistics
Monitoring.
7.4 User Statistics Monitoring Modified the description of User Statistics
Monitoring.
7.5 RB Usage Monitoring Modified the description of RB Usage Monitoring.

No information in issue 05 (2012-07-30) of V100R005C00 is deleted from this issue.
05 (2012-07-30)
This is the fifth official release.
Compared with issue 04 (2012-06-29) of V100R005C00, this issue does not include any new
information.
changes.
eNodeB

3

4 CPRI BER Monitoring Modified the description of CPRI BER Monitoring.
7.7 MU-MIMO Monitoring Modified the description of the usage scenario of
MU-MIMO Monitoring.

04 (2012-06-29)
This is the fourth official release.
new information.
4 CPRI BER Monitoring Added the description of CPRI BER Monitoring.

changes.
7.5 RB Usage Monitoring Modified the descriptions of the results of RB
Usage Monitoring.
9.1 Clock Quality Test Modified the description of the usage scenario of
Clock Quality Test.

03 (2012-05-11)
This is the third official release.
new information.
2.3 Precautions Added precautions for monitoring on BTS3202Es.

changes.
eNodeB

4

7.4 User Statistics Monitoring Modified the description of the results of User
Statistics Monitoring.
8.6 RLC Data Stream Monitoring Modified the description of the results of RLC
Data Stream Monitoring.
8.7 Throughput Monitoring Modified the description of the results of
Throughput Monitoring.
8.8 AQM Monitoring Modified the description of the results of AQM
Monitoring.

02 (2012-04-28)
This is the second official release.
new information.
8.1 DL RSRP/RSRQ Monitoring Added the description of DL RSRP/RSRQ
Monitoring.

changes.
5.1 RRU/RFU Output Power
Monitoring
Modified the description of the results of
RRU/RFU Output Power Monitoring.
5.2 RRU/RFU Temperature
Monitoring
Modified the description of the
results of
RRU/RFU Temperature Monitoring.

The following information in issue 01 (2012-03-30) of V100R005C00 is deleted from this
issue.
Distance To Fault Test Deleted the description of Distance To Fault Test.

eNodeB

5

01 (2012-03-30)
This is the first official release.
Compared with draft B (2012-02-15) of V100R005C00, this issue includes the following new
information.
6.1 IP Link Monitoring Added the description of IP link monitoring.
9 Clock Performance Monitoring Added the description of clock performance
monitoring.

Compared with draft B (2012-02-15) of V100R005C00, this issue includes the following
changes.
6.2 IP Path Performance Monitoring Modified the description of the results of IP path
performance monitoring.
6.6 UDP Injection Test Monitoring Modified the description of the results of UDP
injection test monitoring.
6.8 Resource Group Monitoring Modified the Monitor Period (ms) parameter for
resource group monitoring.
7.1 Service Satisfaction Monitoring Modified the description of the results of the CN
Operator GBR Degrade Flag parameter.
7.5 RB Usage Monitoring Modified the description of the results of resource
block (RB) usage monitoring.
7.8 Interference RSSI Statistic Detect
Monitoring
interference RSSI statistic detect monitoring.
7.12 Air-Interface DCI Status
Monitoring
air-interface DCI status monitoring.
8.2 BLER Monitoring Modified the description of the results of block
error rate (BLER) monitoring.
8.9 Uplink Power Control
Monitoring
Modified the description of the results of the
PUSCH IBLER target parameter.
8.10 Downlink Power Control
Monitoring
Modified the description of the results of downlink
power control monitoring.
8.11 Uplink ICIC Monitoring Modified the description of the results of uplink
inter-cell interference coordination (ICIC)
monitoring.
8.12 MCS Statistics Monitoring Modified the description of the usage scenario of
MCS statistics monitoring.

eNodeB

6

The following information in draft B (2012-02-15) of V100R005C00 is deleted from this
issue.
6.5 Transmission Performance Monitoring Deleted the description of TRM statistic
monitoring.
8.9 Uplink Power Control Monitoring Deleted the descriptions of the results of the
PUSCH SINR target and PUSCH SINR
Adjust Step parameters.

Draft B (2012-02-15)
This is draft B.
Compared with draft A (2012-01-10) of V100R005C00, this issue includes the following new
information.
3.1 CPU Usage Monitoring

Added the parameters for central processing
unit (CPU) usage monitoring.

Added the description of the results of CPU
usage monitoring.
7.8 Interference RSSI Statistic Detect
Monitoring

Added the parameters for interference received
signal strength indicator (RSSI) statistic detect
monitoring.

Added the description of the results of
interference RSSI statistic detect monitoring.

Compared with draft A (2012-01-10) of V100R005C00, this issue does not include any
changes.
No information in draft A (2012-01-10) of V100R005C00 is deleted from this issue.
Draft A (2012-01-10)
This is draft A.
new information.
6.9 PPPoE Performance Monitoring

Added the parameters for PointtoPoint
Protocol over Ethernet (PPPoE) performance
test.

Added the description of the results of PPPoE
performance test.
eNodeB

7

change:
7.11.4 Monitoring Results Modified the description of the results of HARQ
statistic monitoring.

eNodeB
Performance Monitoring Reference 2 Introduction

8

2 Introduction
2.1 Overview
Performance monitoring is used to monitor the equipment running status and service status of
eNodeBs by using iManager M2000 Mobile Element Management System (referred to as
M2000) or the local maintenance terminal (LMT). Monitoring results are displayed in tables
or charts. In this way, equipment can be maintained and faults can be rectified by analyzing
the exceptions shown in monitoring results.
2.2 Performance Monitoring Types
Table 2-1 Performance Monitoring Types
Type Task Platform
CPU Usage Monitoring CPU Usage Monitoring M2000
CPRI BER Monitoring CPRI BER Monitoring M2000
RRU/RFU Performance
Monitoring
RRU/RFU Output Power Monitoring M2000
RRU/RFU Temperature Monitoring M2000
Sector Performance Monitoring LMT
Spectrum Detection LMT
Transmission
Performance Monitoring
IP Link Monitoring M2000
IP Path Performance Monitoring M2000
IP Performance Monitoring M2000
SCTP Performance Monitoring M2000
Transmission Performance Monitoring LMT
UDP Test Monitoring M2000
Local Pass-By Traffic Monitoring M2000
eNodeB

9

Type Task Platform
Resource Group Monitoring M2000
PPPoE Performance Monitoring LMT
Cell Performance
Monitoring
Service Satisfaction Monitoring M2000
General Throughput Monitoring M2000
Service Statistics Monitoring M2000
User Statistics Monitoring M2000
RB Usage Monitoring M2000
ICIC Monitoring M2000
MU-MIMO Monitoring M2000
Interference RSSI Statistic Detect Monitoring M2000
Interference Detection Monitoring M2000
Scheduled Cell-Level UE Information
Monitoring
M2000
HARQ Statistic Monitoring M2000
Air-Interface DCI Status Monitoring M2000
Air-Interface DRB Statistics Monitoring M2000
User Performance
Monitoring
DL RSRP/RSRQ Monitoring M2000
BLER Monitoring M2000
Power Headroom Monitoring M2000
Channel Quality Monitoring M2000
Scheduling Monitoring M2000
RLC Data Stream Monitoring M2000
Throughput Monitoring M2000
AQM Monitoring M2000
UL Power Control Monitoring M2000
DL Power Control Monitoring M2000
UL ICIC Monitoring M2000
MCS Statistics Monitoring M2000
Clock Performance
Monitoring
Clock Quality Test Monitoring M2000
IP Clock Data Collection M2000

eNodeB

10

2.3 Precautions
This section describes the precautions for monitoring on 3900 series base stations and
BTS3202Es.
2.3.1 Precautions for Monitoring on 3900 Series Base Station
3900 series base stations do not support the PPPoE Performance Monitoring task. The PPPoE
Performance Monitoring task is available only on BTS3202Es.
2.3.2 Precautions for Monitoring on BTS3202Es
Take the following precautions for monitoring on BTS3202Es:
The values of Cabinet No., Subrack No., and Slot No. must be 0.
The value of Local Cell ID must be 0.
The value of Cn Operator ID must be 0.
BTS3202Es do not support CPRI BER monitoring.
BTS3202Es do not support PPP Performance monitoring and MP Performance
monitoring in the Transmission Performance Monitoring task.
In IP Link Monitoring and Transmission Performance Monitoring tasks, Subboard Type
must be BASE_BOARD.

eNodeB
Performance Monitoring Reference 3 CPU Usage Monitoring

11

3 CPU Usage Monitoring
3.1 CPU Usage Monitoring
3.1.1 Usage Scenario
This task is used to monitor the CPU usage of each board of an eNodeB.
3.1.2 Service Impact
None
3.1.3 Parameters
Table 3-1 Parameters for CPU usage monitoring
Parameter Description
Cabinet No. Number of the cabinet where the board is located.
Subrack No. Number of the subrack where the board is located.
Slot No. Number of the slot where the board is located.
Monitor Period
(Seconds)
Interval of reporting monitoring results. It is set to the fixed value 5.

3.1.4 Monitoring Results
Table 3-2 Results of CPU usage monitoring
Parameter Unit Value
Range
Description Formula
Number of
the Boards
Number 1 Number of the boards. N/A
Board No. N/A N/A The board number is
displayed as follows:
N/A
eNodeB
Performance Monitoring Reference 3 CPU Usage Monitoring

12

Range
Description Formula
Cabinet No.: Subrack No.:
Slot No.
Type N/A N/A The CPU type is as follows:

CPU.

DSP.

Sub CPU.
N/A
CPU No. N/A N/A The default CPU number is 0. N/A
CPU Usage % 0 to 100 CPU usage when the
monitoring results are
reported.
N/A

eNodeB
Performance Monitoring Reference 4 CPRI BER Monitoring

13

4 CPRI BER Monitoring
4.1 CPRI BER Monitoring
This task is used to monitor the bit error rate (BER) on the common public radio interface
(CPRI) link to determine whether the fault on the eNodeB is caused by the optical fiber or the
BBU or RRU.
None
4.1.3 Parameters
Table 4-1 Parameters for CPRI BER monitoring
Upper Cabinet NO. The cabinet number of the upper-level node at the other end of the
monitored link.

The upper-level node mentioned in this table is the node connected to the
link towards the BBU.
Upper Subrack NO. The subrack number of the upper-level node at the other end of the
monitored link.
Upper Slot No. The slot number of the upper-level node at the other end of the
monitored link.
Upper Port No. The port number of the upper-level node at the other end of the
monitored link. This parameter is mandatory if the upper-level node
is a BBU. CPRI BER monitoring supports cascaded RRUs. This
parameter is optional if the upper-level node and lower-level node
at the other end of the monitored link are RRUs.
Lower Cabinet No. The cabinet number of the lower-level node at the other end of the
monitored link.

eNodeB
Performance Monitoring Reference 4 CPRI BER Monitoring

14

The lower-level node mentioned in this table is the node connected to the
link towards the lowest-level RRU.
Lower Subrack No. The subrack number of the lower-level node at the other end of the
monitored link.
Lower Slot No. The slot number of the lower-level node at the other end of the
monitored link.

Table 4-2 Results of CPRI BER monitoring
Range
Description Formula
Uplink BER e^(-9) 0 to
1000000000
Uplink BER in the test
second.

Because LBBPc does not
support CPRI BER monitoring,
the uplink BER of LBBPc is
displayed as N/A.
N/A
Downlink
BER
e^(-9) 0 to
1000000000
Downlink BER in the test
second.
N/A
BER
Threshold
e^(-9) 0 to
1000000000
BER threshold.

If the actual measured
downlink and uplink BER is
greater than the threshold, the
link quality may be poor.
N/A

eNodeB
Performance Monitoring Reference 5 RRU/RFU Performance Monitoring

15

5 RRU/RFU Performance Monitoring
5.1 RRU/RFU Output Power Monitoring
This task is used to monitor the remote radio unit (RRU/RFU) output power.
None
5.1.3 Parameters
Table 5-1 Parameters for RRU/RFU Output Power monitoring
Cabinet No. Number of the cabinet where the board for RRU/RFU Output Power
monitoring is located.
Subrack No. Number of the subrack where the board for RRU/RFU Output Power
Slot No. Number of the slot where the board for RRU/RFU Output Power
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000,2000, or
3000.

Table 5-2 Results of RRU/RFU Output Power monitoring
Range
Description Formula
Index of TX N/A BTS3202E:
0 to 1, 3900
Index of TX channel. N/A
eNodeB

16

Range
Description Formula
Series Base
Station :0
to 8
Index of Carrier N/A 0 to 1

If only 0 is displayed, the
RRU supports one carrier.

If both 0 and 1 are
displayed, the RRU/RFU
supports two carriers.
N/A
TX Freq of TX
Carrier[n]
MHz 2750 to
3449
Downlink frequency of a
carrier.
N/A
Output power of
TX Carrier[n]
0.1 dBm 200 to 1 Output power of a carrier. N/A
Output Power 0.1dBm 200 to 1 Output power of a TX channel. N/A

5.2 RRU/RFU Temperature Monitoring
This task is used to monitor the remote radio unit (RRU/RFU) temperature.
None
5.2.3 Parameters
Table 5-3 Parameters for RRU/RFU Temperature monitoring
Cabinet No. Number of the cabinet where the board for RRU/RFU temperature
Subrack No. Number of the subrack where the board for RRU/RFU temperature
Slot No. Number of the slot where the board for RRU/RFU temperature
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000,2000, or
3000.

eNodeB

17

Table 5-4 Results of RRU/RFU Temperature monitoring
Parameter Unit Value Range Description Formu
la
Board Temperature C 100 to +200 Board temperature of
RRU or RFU.
N/A
PA Temperature C 100 to +200 Power amplifier (PA)
temperature.
N/A
Branch Index N/A BTS3202E : 0 to 1,
3900 Series Base
Station : 0 to 7
Index of PA. N/A
LPA Temperature C 100 to +200 Low Power amplifier
(LPA) temperature.
N/A
5.3 Sector Performance Monitoring
The RRU or RFU scans frequencies continuously, calculates the received signal strength, and
reports the strength to the LMT. The received signal strength is used as reference for
interference location and analysis.
None
5.3.3 Parameters
Table 5-5 Parameters for sector performance monitoring
Test Items It can be set only to UL Widefreq Scan.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 50, 100, 200,
500, 1000, or 2000.
Local Sector ID ID of the sector for performance monitoring.
Frequency Band Frequency band supported by the sector. It is set to a value in the range
of 1 to 40.
UL EARFCN Uplink EARFCN of a cell. It is set to a value in the ranges of 18000 to
45589 and 64436 to 65535.
UL Bandwidth Uplink bandwidth of the cell. It can be set to 1.4M, 3M, 5M, 10M,
15M, or 20M.
eNodeB

18

Table 5-6 Results of UL Widefreq Scan monitoring
Range
Description Formula
Signal Strength dBm 140 to 50 RSSI in each RB from the
physical layer when the
monitoring result is reported.
N/A

5.4 Spectrum Detection
This task is used to detect the spectrum status and monitor the interference in frequency and
time domains in radio environments by analyzing spectrum and power distribution of sampled
data.
None
5.4.3 Parameters
Table 5-7 Parameters for spectrum detection
Scan Mode Detects the output power of each TX channel and carrier. It can be set
to Carrier Mode, Channel Current Band Mode, or Channel Full
Band Mode.

TX channel is provided by the RF port of the RRU. A carrier is similar to a cell.
Cabinet No. Number of the cabinet where the board for spectrum detection is
located.
Subrack No. Number of the subrack where the board for spectrum detection is
located.
Slot No. Number of the slot where the board for spectrum detection is located.
RBW(Resolutio
n Bandwidth)
Time frequency of Fast Fourier Transport (FFT) frequency detection, in
units of kHz.

The value range for online high-precision frequency detection is 15
to 200. The default value is 100.

The value range for online or offline wideband frequency detection
eNodeB

19

is 100 to 5000. The default value is 200.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000, 2000, or
3000.
Scan Mode The Autosave to File check box is selected by default, and monitoring
results are automatically saved in the default path. You can also
customize the file name, file format, and another save path.

Spectrum detection results are used for fault identification, which are not displayed on the
LMT. If the results need to be reviewed, send the result file to Huawei technical support for
analysis.
eNodeB
Performance Monitoring Reference 6 Transmission Performance Monitoring

20

6 Transmission Performance Monitoring
6.1 IP Link Monitoring
This task is used to monitor the transmission and reception at the data link layer of eNodeB
Ethernet ports and at the IP layer of IPSec tunnels in real time.
None
6.1.3 Parameters
Table 6-1 Parameters for IP link monitoring
Test Items It can be set to the following values:

FE/GE

TUNNEL
Cabinet No. Number of the cabinet where the board for IP link monitoring is
located.
Subrack No. Number of the subrack where the board for IP link monitoring is
located.
Slot No. Number of the slot where the board for IP link monitoring is located.
Subboard Type It can be set to the following values:

BASE_BOARD

E1_COVERBOARD

BACK_BOARD

ETH_COVERBOARD
Port No. Number of the Ethernet port to which the board for IP link monitoring
is connected. It needs to be set only when the Test Items is set to
eNodeB

21

FE/GE.
Tunnel No. Number of the tunnel for IP link monitoring. It needs to be set only
when the Test Items is set to TUNNEL.

Table 6-2 Results of IP link monitoring
Range
Description Formula
Rx Traffic bps 0 to
100000000
Number of bits
received every second
within a monitoring
period.
N/A
Tx Traffic bps 0 to
100000000
Number of bits
transmitted every
second within a
monitoring period.
N/A
Rx Packets Packet 0 to
2000000
Number of received
packets within a
monitoring period.
N/A
Tx Packets Packet 0 to
2000000
Number of transmitted
packets within a
monitoring period.
N/A
Rx Loss
Packets
Packet 0 to
2000000
Number of discarded
incoming packets
within a monitoring
period.
N/A
Tx Inner Loss
Packets
Packet 0 to
2000000
Number of discarded
outgoing packets within
a monitoring period.
N/A
Rx Loss Ratio 0 to 1000 Packet loss rate of
incoming packets
within a monitoring
period.
Number of discarded
incoming packets x
1000/Total number of
incoming packets
Tx Inner Loss
Ratio
0 to 1000 Internal packet loss rate
of outgoing packets
within a monitoring
period.
Internal discarded
packets are the packets
discarded due to
internal congestion
rather than the packets
Number of discarded
outgoing packets x
1000/Total number of
outgoing packets
eNodeB

22

Range
Description Formula
discarded on
transmission links.
Rx Traffic
with
Prefix/CRC
bps 0 to
100000000
Number of bits with the
preamble and cyclic
redundancy check
(CRC) code received
every second within a
monitoring period.
N/A
Tx Traffic with
Prefix/CRC
bps 0 to
100000000
preambles and CRC
code transmitted every
second within a
monitoring period.
N/A
Rx Traffic
with
Frame/Prefix/
CRC
bps 0 to
100000000
minimum frame
interval, preamble, and
cyclic redundancy
check (CRC) code
received every second
within a monitoring
period.
N/A
Tx Traffic with
Frame/Prefix/
CRC
bps 0 to
100000000
minimum frame
interval, preamble, and
cyclic redundancy
check (CRC) code
transmitted every
second within a
monitoring period.
N/A

6.2 IP Path Performance Monitoring
This task is used to monitor the transmission and reception of service data flows in real time.
This facilitates the verification of the stability of traffic flow.
None
eNodeB

23

6.2.3 Parameters
Table 6-3 Parameters for IP path performance monitoring
IP PATH No. Number of the IP path.
Monitor Period
(Seconds)
Interval of reporting monitoring results. It is set to 1 by default.

Table 6-4 Results of IP Path Performance monitoring
Range
Description Formula
Lost Packets
Ratio
0.001% 0 to 100000 Packet loss rate
within a monitoring
period.
(Number of packets
transmitted by the
eNodeB Number of
packets received by the
peer end) x
100000/Number of
packets transmitted by
the eNodeB
Transmit Rate kbps 0 to 100000 Number of kbits on
the IP path
transmitted by the
eNodeB per second
within a monitoring
period.
N/A
Average Delay ms 0 to 100 Average delay on
the IP path within a
monitoring period.
(Sum of delays for
transmitting the IP PM
data bound to the IP
path from the eNodeB
to the EPC + Sum of
delays for transmitting
data the IP PM data
bound to the IP path
from the eNodeB to the
EPC)/Number of all
quadruplet-based and
triplet-based IP PM
packets bound to the IP
path
One IP path can only be
bound to one triplet IP
PM, but can be bound to
multiple quadruplet IP
eNodeB

24

Range
Description Formula
PMs.
Average Jitter ms 0 to 100 Average jitter on the
IP path within a
monitoring period
Sum of jitters of all the
IP PMs bound to the IP
path/Number of IP PMs
bound to the IP path
The formula for the
jitter of each IP PM is
as follows:
Delay of data
transmission from the
IP PM to the EPC
Average of delay of
data transmission from
the IP PM to the EPC
Transmit
Packets
Number
Packets 0 to
2000000
Total number of
packets transmitted
on the IP path
within a monitoring
period.
N/A
Lost Packets
Number
Packets 0 to
2000000
Total number of
packets discarded
on the IP path
within a monitoring
period.
N/A

6.3 IP Performance Monitoring
This task is used to monitor packet transmission and reception of the eNodeB at the IP layer
in real time.
None
6.3.3 Parameters
Table 6-5 Parameters for IP performance monitoring
Cabinet No. Number of the cabinet where the board for IP performance monitoring
is located.
eNodeB

25

Subrack No. Number of the subrack where the board for IP performance monitoring
is located.
Slot No. Number of the slot where the board for IP performance monitoring is
located.
Monitor Period
(Seconds)

Table 6-6 Results of IP Performance monitoring
Parameter Unit Value Range Description Form
ula
Number
increment of
RX packets
Packets 0 to 2000000 Total number of packets at the IP
layer received by the board within
N/A
Number
increment of
TX packets
Packets 0 to 2000000 Total number of packets at the IP
layer transmitted by the board
within a measurement period.
N/A
Number
increment of
discarded
packets
Packets 0 to 2000000 Total number of discarded
packets at the IP layer within a
measurement period.
N/A

6.4 SCTP Performance Monitoring
This task is used to monitor the transmission and reception of data on the Stream Control
Transmission Protocol (SCTP) link in real time. This facilitates the verification of the stability
of the signaling data flow.
None
eNodeB

26

6.4.3 Parameters
Table 6-7 Parameters for SCTP performance monitoring
Cabinet No. Number of the cabinet where the board for SCTP performance
Subrack No. Number of the subrack where the board for SCTP performance
Slot No. Number of the slot where the board for SCTP performance monitoring
is located.
Monitor Period
(Seconds)

Table 6-8 Results of SCTP Performance monitoring
Range
Description Formula
Receive Total
Packets
Packets 0 to
2000000
Number of packets
received on the SCTP
link within a
monitoring period.
N/A
Send Total
Packets
Packets 0 to
2000000
Number of packets
transmitted on the
SCTP link within a
monitoring period.
N/A
Receive Total
Drop Packets
Packets 0 to
2000000
Number of packets
discarded on the
SCTP link within a
monitoring period.
N/A
Retrans Ratio % 0 to 100 Retransmission ratio
on the SCTP link
within a monitoring
period.
Number of data blocks
retransmitted on the
SCTP link within a
monitoring period x
100/Number of data
blocks transmitted on
the SCTP link

eNodeB

27

6.5 Transmission Performance Monitoring
This task is used to monitor data transmission performance on the following layers/links:
MAC performance: used to monitor data transmission performance at the MAC layer,
such as Send Drop Packets, Receive Packets, and Receive CRC Error Packets.
PPP performance: used to monitor data transmission performance on the PPP link, such
as Send Drop Packets, Receive Drop Packets, and Send Drop Packets Ratio, and Receive
Drop Packets Ratio, which can indicate the quality of the link and whether the quality of
service is affected.
MP performance: used to monitor data transmission performance on the MP link, such as
Send Drop Packets, Receive Drop Packets, and Send Drop Packets Ratio, and Receive
Drop Packets Ratio, which can indicate the quality of the link and whether the quality of
service is affected.
None
6.5.3 Parameters
Table 6-9 Parameters for transmission performance monitoring
Test Items It can be set to MAC Performance, PPP Performance, or MP
Performance.
Monitor Period
(Seconds)
Cabinet No. Number of the cabinet where the board for transmission performance
Subrack No. Number of the subrack where the board for transmission performance
Slot No. Number of the slot where the board for transmission performance
SubBoard Type Types of subboards. It can be set to the following:

Base Board.

Ethernet Cover Board. This can be selected when Test Items is set
to MAC Performance.

E1 COVER BOARD. This can be selected when Test Items is set
to PPP Performance, or MP Performance.
Port No. Number of the port where the board for transmission performance
monitoring is located. This can be selected when Test Items is set to
MAC Performance.
PPPLink No. Number of the PPP link where the board for transmission performance
eNodeB

28

monitoring is located. This can be selected when Test Items is set to
PPP Performance.
MPGroup No. Number of the MP group where the board for transmission
performance monitoring is located. This can be selected when Test
Items is set to MP Performance.

MAC Performance
Table 6-10 Results of MAC Performance monitoring
Parameter Unit Value Range Description Formula
Receive Packets Packet 0 to 2000000 Number of packets the
Ethernet port receives
within a monitoring period.
N/A
Send Packets Packet 0 to 2000000 Number of packets the
Ethernet port transmits
N/A
Receive Bytes bps 0 to 100000000 Number of bits the Ethernet
port receives every second
N/A
Send Bytes bps 0 to 100000000 Number of bits the Ethernet
port transmits every second
N/A
Receive Drop
Packets
Packet 0 to 2000000 Number of discarded
packets the Ethernet port
receives within a
monitoring period.
N/A
Receive CRC
Error Packets
Packet 0 to 2000000 Number of packets with
CRC errors the Ethernet
port receives every second
N/A
Send Drop
Packets
packets the Ethernet port
transmits within a
monitoring period.
N/A

PPP Performance
eNodeB

29

Table 6-11 Results of PPP Performance monitoring
Receive Packets Packet 0 to 2000000 Number of packets
the PPP link receives
within a monitoring
period.
N/A
Send Packets Packet 0 to 2000000 Number of packets
the PPP link
transmits within a
monitoring period.
N/A
Receive Bytes bps 0 to 10000000 Number of bits the
PPP link receives
monitoring period.
N/A
Send Bytes bps 0 to 100000000 Number of bits the
PPP link transmits
monitoring period.
N/A
Receive Drop
Packets
packets the PPP link
receives within a
monitoring period.
N/A
Send Drop
Packets
packets the PPP link
transmits within a
monitoring period.
N/A
Receive Drop
Packets Ratio
0 to 1000 Loss rate of the
packets that the PPP
link receives after the
test is started.
Total number
of discarded
packets the PPP
link receives x
1000/Total
number of
packets the PPP
link receives
Send Drop
Packets Ratio
packets that the PPP
link transmits after
the test is started.
Total number
of discarded
packets the PPP
link transmits x
1000/Total
number of
packets the PPP
link transmits

MP Performance
eNodeB

30

Table 6-12 Results of MP Performance monitoring
Receive Packets Packet 0 to 2000000 Number of packets
the MP group
receives within a
monitoring period.
N/A
Send Packets Packet 0 to 2000000 Number of packets
the MP group
transmits within a
monitoring period.
N/A
Receive Bytes bps 0 to 100000000 Number of bits the
MP group receives
monitoring period.
N/A
Send Bytes bps 0 to 100000000 Number of bits the
MP group transmits
monitoring period.
N/A
Receive Drop
Packets
packets the MP group
receives within a
monitoring period.
N/A
Send Drop
Packets
packets the MP group
transmits within a
monitoring period.
N/A
Receive Drop
Packets Ratio
packets that the MP
group receives after
Total number
of discarded
packets the MP
group receives
x 1000/Total
number of
packets the MP
group receives
Send Drop
Packets Ratio
packets that the MP
group transmits after
Total number
of discarded
packets the MP
group transmits
x 1000/Total
number of
packets the MP
group transmits

eNodeB

31

6.6 UDP Injection Test Monitoring
This task is used to measure the link quality, including the round-trip delays, jitter, and packet
loss rate by injecting User Datagram Protocol (UDP) packets from the eNodeB to other NEs
and then transmitting the packets back to the eNodeB when the eNodeB is not serving any
UEs.
None
6.6.3 Parameters
Table 6-13 Parameters for UDP injection test monitoring
Cabinet No. Number of the cabinet where the board for the UDP test is
located.
Subrack No. Number of the subrack where the board for the UDP test is
located.
Slot No. Number of the slot where the board for the UDP test is located.
Monitor Period
(Seconds)
Source IP Address IP address of the eNodeB.
Source Port No. Number of UDP port on the eNodeB. The value ranges from
1024 to 65,535.
Destination IP Address IP address of the peer end.
Destination Port No Number of UDP port on the peer end. The value ranges from
1024 to 65,535.
DSCP Differentiated services code point (DSCP) of the UDP packet.
The value ranges from 0 to 63. The default value is 63.
Speed (Kbps) Data rate of the data transmission. The value ranges from 28 to
150,000. The default value is 150000.
UDP PACKETS
LENGTH (BYTES)
Length of the UDP packet. The value ranges from 72 to 1500.
The default value is 1500.
Time (Minutes) Duration of UDP test monitoring. The test stops automatically
when the duration expires. The value ranges from 1 to 60. The
default value is 15.

eNodeB

32

Table 6-14 Result of UDP injection test monitoring
Range
Description Formula
Drop Packet
Ratio
0.001% 0 to 100000 Ratio of lost packets to
total packets on the
transmission link within a
monitoring period.
Number of
discarded packets
per minute x
100000/Expected
number of
packets received
on the
transmission link
per minute
Average Drop
Packet Ratio
0.001% 0 to 100000 Average ratio of lost
packets to total packets on
the transmission link
within a monitoring
period.
Total number of
discarded packets
x 100000/Total
number of
packets
Delay us 0 to 100 Delay on the transmission
link when the monitoring
result is reported. This
monitoring item indicates
the time difference
between sending a packet
by the sender and
receiving the packet by the
receiver.
N/A
Jitter N/A 0 to 100 Jitter on the transmission
link within a monitoring
period.
|Delay - Average
Delay|/Average
Delay
Average Delay us 0 to 100 Average delay on the
transmission link within a
monitoring period.
N/A

6.7 Local Pass-By Traffic Monitoring
This task is used to monitor the local traffic and forwarded traffic in real time. Forwarded
traffic is common when eNodeBs are cascaded.
None
eNodeB

33

6.7.3 Parameters
Table 6-15 Parameters for local and forwarded traffic monitoring
Monitor Period (Seconds) Interval of reporting monitoring results. It is set to 1 by
default.

Table 6-16 Results of local and forwarded traffic monitoring
Local Receive
Traffic
Byte/s 0 to 100000000 Number of bytes received by
the eNodeB per second
within a monitoring period
and that are destined for the
local eNodeB.
N/A
Local Send
Traffic
Byte/s 0 to 100000000 Number of bytes transmitted
by the eNodeB within a
monitoring period, excluding
the forwarded traffic.
N/A
eNodeB Bypass
Traffic
Byte/s 0 to 100000000 Number of bytes forwarded
by the eNodeB per second
N/A

6.8 Resource Group Monitoring
This task is used to monitor the real-time information about logical ports in an eNodeB in
single-rate and double-rate modes. The information includes admission bandwidths, transport
loads for services, and bandwidth load ratios.
None
eNodeB

34

6.8.3 Parameters
Table 6-17 Parameters for resource group monitoring
Cabinet No. Number of the cabinet where the board for resource group
Subrack No. Number of the subrack where the board for resource group
Slot No. Number of the slot where the board for resource group
SubBoard Type Type of the subboard for resource group monitoring.
Physical Port Type Type of the physical port for resource group monitoring.
Physical Port No. Number of the physical port for resource group monitoring.
Transmission Resource
Group No.
Number of the transport resource group for resource group
monitoring.
Rate Config Type Rate mode for resource group monitoring. It can be single-rate
mode or double-rate mode.
Monitor Period (ms) Interval of reporting monitoring results. It can be set to 50, 100,
200, 500, 1000, or 2000.

Single Rate
Table 6-18 Results of Single Rate monitoring
Range
Description Formula
Admission
Bandwidth (Tx)
Kbps 0 to
1000000
Admission
bandwidth for data
transmission on the
current logical port
in single-rate
mode.
N/A
Admission
Bandwidth (Rx)
Kbps 0 to
1000000
Admission
bandwidth for data
reception on the
in single-rate
mode.
N/A
GBR Load (Tx) Kbps 0 to
1000000
Transport load for
GBR service data
N/A
eNodeB

35

Range
Description Formula
transmission on the
in single-rate
mode.
GBR Load (Rx) Kbps 0 to
1000000
Transport load for
GBR service data
reception on the
in single-rate
mode.
N/A
GBR Load Ratio
(Tx)
% 0 to 100 Transport load
ratio of GBR
service data
transmission on the
in single-rate
mode.
GBR Load (Tx kbit/s)
x 100/Admission
Bandwidth (Tx kbit/s)
GBR Load Ratio
(Rx)
ratio of GBR
service data
reception on the
in single-rate
mode.
GBR Load (Rx kbit/s)
x 100 /Admission
Bandwidth (Rx kbit/s)
Resource Group
Load (Tx)
Kbps 0 to
1000000
Transport load for
data transmission
on the current
logical port in
single-rate mode.
N/A
Resource Group
Load (Rx)
Kbps 0 to
1000000
Transport load for
data reception on
the current logical
port in single-rate
mode.
N/A
Resource Group
Load Ratio (Tx)
ratio of data
transmission on the
in single-rate
mode.
Resource Group Load
(Tx kbit/s) x100
/Admission Bandwidth
(Tx kbit/s)
Resource Group
Load Ratio (Rx)
ratio of data
reception on the
in single-rate
mode.
Resource Group Load
(Rx kbit/s) x100
/Admission Bandwidth
(Rx kbit/s)
eNodeB

36

Dual Rate
Table 6-19 Results of Dual Rate monitoring
Range
Description Formula
CIR Admission
Bandwidth (Tx)
Kbps 0 to
1000000
Committed
information rate (CIR)
admission bandwidth
for data transmission
on the current logical
port in double-rate
mode.
N/A
CIR Admission
Bandwidth (Rx)
Kbps 0 to
1000000
CIR admission
bandwidth for data
reception on the
current logical port in
double-rate mode.
N/A
PIR Admission
Bandwidth (Tx)
Kbps 0 to
1000000
Peak information rate
(PIR) admission
bandwidth for data
transmission on the
double-rate mode.
N/A
PIR Admission
Bandwidth (Rx)
Kbps 0 to
1000000
PIR admission
bandwidth for data
reception on the
double-rate mode.
N/A
GBR Load (Tx) Kbps 0 to
1000000
Transport load for
GBR service data
transmission on the
double-rate mode.
N/A
GBR Load (Rx) Kbps 0 to
1000000
Transport load for
GBR service data
reception on the
double-rate mode.
N/A
Real Time Traffic
Load (Tx)
Kbps 0 to
1000000
Transport load for
non-flow-controllable
service data
transmission on the
double-rate mode.
N/A
Real Time Traffic
Load (Rx)
Kbps 0 to
1000000
Transport load for
non-flow-controllable
N/A
eNodeB

37

Range
Description Formula
service data reception
port in double-rate
mode.
GBR Load Ratio (Tx) % 0 to 100 Transport load ratio of
GBR service data
transmission on the
double-rate mode.
GBR Load (Tx
kbit/s) x100
/Admission
Bandwidth (Tx
kbit/s)
GBR Load Ratio (Rx) % 0 to 100 Transport load ratio of
GBR service data
reception on the
double-rate mode.
GBR Load (Rx
kbit/s) x100
/Admission
Bandwidth (Rx
kbit/s)
CIR Load Ratio (Tx) % 0 to 100
CIR bandwidth load
ratio of data
transmission on the
double-rate mode.
Transport load
for
non-flow-control
lable services on
the port(Tx
kbit/s) x100
/Available CIR
bandwidth(Tx
kbit/s)
CIR Load Ratio (Rx) % 0 to 100
CIR bandwidth load
ratio of data reception
port in double-rate
mode.
Transport load
for
non-flow-control
lable services on
the port(Rx
kbit/s) x100
/Available CIR
bandwidth(Rx
kbit/s)
Resource Group Load
(Tx)
Kbps 0 to
1000000
Transport load for data
transmission on the
double-rate mode.
Resource Group
Load (Tx
kbit/s)/Admissio
n Bandwidth (Tx
kbit/s)
Resource Group Load
(Rx)
Kbps 0 to
1000000
Transport load for data
reception on the
double-rate mode.
Resource Group
Load (Rx
kbit/s)/Admissio
n Bandwidth (Rx
kbit/s)
PIR Load Ratio (Tx) % 0 to 100 PIR bandwidth load
ratio of data
transmission on the
double-rate mode.
Transport load
on the port(Tx
kbit/s) x100
/Available PIR
bandwidth(Tx
eNodeB

38

Range
Description Formula
kbit/s)
PIR Load Ratio (Rx) % 0 to 100
PIR bandwidth load
ratio of data reception
port in double-rate
mode.
Transport load
on the port(Rx
kbit/s) x100
/Available PIR
bandwidth(Rx
kbit/s)

6.9 PPPoE Performance Monitoring
This task is used to monitor PPPoE online performance. PPPoE online performance
monitoring helps monitor the link quality, which involves number of received packets,
number of transmitted packets, receive rate, transmit rate, number of discarded packets during
reception, number of discarded packets during transmission, packet loss rate during reception,
and packet loss rate during transmission. Packet drip ratio is a key indicator of the efficiency
of packet transmission.
None
6.9.3 Parameters
Table 6-20 Parameters for PPPoE performance monitoring
Cabinet No. Number of the cabinet where the board for the PPPoE performance
tests is located.
Subrack No. Number of the subrack where the board for the PPPoE performance
tests is located.
Slot No. Number of the slot where the board for the PPPoE performance tests is
located.
PPPoELink No. Number of the PPPoE link to be tested.

eNodeB

39

Table 6-21 Results of PPPoE performance monitoring
Receive
Packets
Packet 0 to 2000000 Number of packets
received by the receiving
end of a PPPoE link within
N/A
Send
Packets
transmitted by the
transmitting end of a
PPPoE link within a
monitoring period.
N/A
Receive
Bytes
bps 0 to
300000000
Number of bits received
per second by the receiving
N/A
Send Bytes bps 0 to
300000000
Number of bits transmitted
per second by the
PPPoE link within a
monitoring period.
N/A
Receive
Drop
Packets
discarded by the receiving
N/A
Send Drop
Packets
discarded by the
PPPoE link within a
monitoring period.
N/A
Receive
Drop
Packets
Ratio
% 0 to 100 Statistics on the packet loss
rate of the receiving end of
a PPPoE link within a
monitoring period.
Receive Drop
Packets x 100
/(Receive Drop
Packets +
Receive Packets)
Send Drop
Packets
Ratio
% 0 to 100 Statistics on the packet loss
rate of the transmitting end
of a PPPoE link within a
monitoring period.
Send Drop
Packets x 100
/(Send Packets +
Send Drop
Packets)

eNodeB
Performance Monitoring Reference 7 Cell Performance Monitoring

40

7 Cell Performance Monitoring
7.1 Service Satisfaction Monitoring
This task is used to monitor the QoS satisfaction rate of VoIP services with QoS class
identifier (QCI) 1. The satisfaction rate is the proportion of satisfied VoIP services in a cell to
all VoIP services in the cell. This task is also used to monitor the QoS satisfaction rates of
GBR services with QCIs 2 to 4 in a cell based on the throughput. The QoS satisfaction rates
of GBR services indicate whether the QoS requirements of admitted GBR services are met
and can be used to determine the cell load status.
None
7.1.3 Parameters
Table 7-1 Parameters for service satisfaction monitoring
Test Items It can be set to DL QCI1 Satisfaction rate of Service, DL QCI2
Satisfaction rate of Service, DL QCI3 Satisfaction rate of Service,
DL QCI4 Satisfaction rate of Service, UL QCI1 Satisfaction rate of
Service, UL QCI2 Satisfaction rate of Service, UL QCI3
Satisfaction rate of Service, UL QCI4 Satisfaction rate of Service,
GBR Degrade Flag, or a combination of some items.
Local Cell ID ID of the cell on which satisfaction of service monitoring is performed.
CN Operator ID In a RAN sharing scenario, a cell can be shared by a maximum of 6
operators. In a non-RAN sharing scenario, a cell can be used by only
one operator. This parameter is set to 0 by default.
Monitor Period
(ms)
500, 1000, or 2000.

eNodeB

41

Table 7-2 Results of service satisfaction monitoring
Range
Description Formula
CN Operator ID N/A 0 to 5 ID of the operator for which
satisfaction of service
monitoring is performed.
N/A
CN Operator GBR
Degrade Flag
% 0 to 100 GBR service degradation flag.
Value 0 indicates that GBR
services are not degraded.
Value 100 indicates that GBR
services are degraded.

The function of GBR service
degradation for operators is
removed. Therefore, the
monitoring result of this
parameter is invalid and is
displayed as N/A.
N/A
CN Operator UL
QCI[n] Satisfaction
rate of Service
% 0 to 100 Average QoS satisfaction
rates of different uplink
services in a cell when the
n ranges from 1 to 4.
On the uplink, the QoS
satisfaction rate of QCI 1 is
represented by the ratio of
satisfied VoIP services in a
VoIP logical channel group to
all VoIP services in the
logical channel group. The
QoS satisfaction rate of a
VoIP service is represented
by the proportion of
successfully received voice
packets to all voice packets.
The higher the proportion, the
higher the satisfaction rate.
The uplink QoS satisfaction
rates of GBR services with
QCIs 2 to 4 are evaluated for
each logical channel group.
The QoS satisfaction rate of a
logical channel group is
evaluated based on the
transmitted data and the total
amount of data to be
transmitted. The higher the
transmitted data volume, the
higher the QoS satisfaction
N/A
eNodeB

42

Range
Description Formula
rate.
CN Operator DL
QCI[n] Satisfaction
rate of Service
% 0 to 100 Average QoS satisfaction
rates of different downlink
services in a cell when the
The value range of n is 1 to 4.
On the downlink, the QoS
satisfaction rate of QCI 1 is
represented by the ratio of
satisfied VoIP services in a
cell to all VoIP services in the
cell. The QoS satisfaction rate
of a VoIP service is
represented by the proportion
of voice packets that meet the
delay requirements to all
voice packets. The higher the
proportion, the higher the
satisfaction rate.
The downlink QoS
satisfaction rates of GBR
services with QCIs 2 to 4 are
evaluated based on the ratio
of the scheduled data volume
of these services to the total
data volume to be transmitted
for these services. If the
scheduled data volume is high
or the data volume in the
buffer is low, the QoS
satisfaction rate is high.
N/A

7.2 General Throughput Monitoring
This task is used to monitor uplink and downlink throughput information about all UEs in a
cell in real time. Based on this information, the data transmission status of the eNodeB or UEs
can be determined.
None
eNodeB

43

7.2.3 Parameters
Table 7-3 Parameters for general throughput monitoring
Local Cell ID ID of the cell on which general throughput monitoring is
performed.
Test Items It can be set to RLC Throughput, RLC Throughput of GBR
service, RLC Throughput of NON-GBR service, or a
combination of some items.
operators. In a non-RAN sharing scenario, a cell can be used by
only one operator. This parameter is set to 0 by default.
200, 500, 1000, or 2000.

RLC Throughput
Table 7-4 Results of RLC Throughput monitoring
Range
Description Formula
CN Operator ID N/A 0 to 5 ID of the operator for
which general
throughput monitoring
is performed.
N/A
Cell Uplink RLC
Throughput
bps 0 to
300000000
Uplink throughput of a
cell. Only RLC
payloads are included.
The RLC headers,
retransmitted data, and
state reports are
excluded.
(General uplink
RLC throughput
(Byte) x 8) x
1000/Monitor
Period (ms)
Cell Downlink
RLC Throughput
bps 0 to
300000000
Downlink throughput
of a cell. Only the RLC
The RLC headers,
state reports are
excluded.
(General downlink
RLC throughput
(Byte) x 8) x
1000/Monitor
Period (ms)
CN Operator Cell
Uplink RLC
Throughput
bps 0 to
300000000
Uplink RLC throughput
of an operator of a cell.
Only RLC payloads are
included. The RLC
(Uplink RLC
throughput of an
operator of a cell
(Byte) x 8) x
eNodeB

44

Range
Description Formula
headers, retransmitted
data, and state reports
are excluded.
1000/Monitor
Period (ms)
CN Operator Cell
Downlink RLC
Throughput
bps 0 to
300000000
Downlink RLC
throughput of an
operator of a cell. Only
RLC payloads are
included. The RLC
are excluded.
(Downlink RLC
throughput of an
operator of a cell
(Byte) x 8) x
1000/Monitor
Period (ms)

RLC Throughput of GBR service
Table 7-5 Results of RLC Throughput of GBR service monitoring
Range
Description Formula
which general
is performed.
N/A
Cell GBR Traffic
Uplink RLC
Throughput
bps 0 to
300000000
Uplink throughput of
GBR services in a cell.
included. The RLC
are excluded.
(General RLC
throughput of
uplink GBR
services (Byte) x 8)
x 1000/Monitor
Period (ms)
Cell GBR Traffic
Downlink RLC
Throughput
bps 0 to
300000000
Downlink throughput of
GBR services in a cell.
included. The RLC
are excluded.
(General RLC
throughput of
downlink GBR
x 1000/Monitor
Period (ms)
CN Operator Cell
GBR Traffic
Uplink RLC
Throughput
bps 0 to
300000000
Uplink GBR service
throughput of an
operator of a cell. Only
RLC payloads are
included. The RLC
are excluded.
(Uplink GBR
service throughput
of an operator of a
cell (byte) x 8) x
1000/Monitor
Period (ms)
Operator Cell
GBR Traffic
bps 0 to
300000000
Downlink GBR service
throughput of an
(Downlink GBR
service throughput
eNodeB

45

Range
Description Formula
Downlink RLC
Throughput
operator cell. Only RLC
The RLC headers,
state reports are
excluded.
of an operator of a
cell (Byte) x 8) x
1000/Monitor
Period (ms)

RLC Throughput of NON-GBR service
Table 7-6 Results of RLC Throughput of NON-GBR service monitoring
Range
Description Formula
which general
is performed.
N/A
Cell Non-GBR
Traffic Uplink
RLC Throughput
bps 0 to
300000000
non-GBR services in a
cell. Only RLC
The RLC headers,
state reports are
excluded.
(General RLC
throughput of
uplink non-GBR
x 1000/Monitor
Period (ms)
Cell Non-GBR
Traffic Downlink
RLC Throughput
bps 0 to
300000000
cell. Only RLC
The RLC headers,
state reports are
excluded.
(General RLC
throughput of
downlink non-GBR
x 1000/Monitor
Period (ms)
CN Operator Cell
Non-GBR Traffic
Uplink RLC
Throughput
bps 0 to
300000000
CN operator cell. Only
RLC payloads are
included. The RLC
are excluded.
General uplink
RLC throughput of
non-GBR services
in a CN operator
cell (Byte) x 8) x
1000/Monitor
Period (ms)
CN Operator Cell
Non-GBR Traffic
Downlink RLC
Throughput
bps 0 to
300000000
CN operator cell. Only
RLC payloads are
included. The RLC
General downlink
RLC throughput of
non-GBR services
in a CN operator
cell (Byte) x 8) x
1000/Monitor
eNodeB

46

Range
Description Formula
are excluded.
Period (ms)

7.3 Service Statistics Monitoring
This task is used to count the number of services with different QCIs in a cell to view the
distribution of these services.
None
7.3.3 Parameters
Table 7-7 Parameters for service statistics monitoring
Test Items It can be set to Service Number of QCI1, Service Number of
QCI2, Service Number of QCI3, Service Number of QCI4,
Service Number of QCI5, Service Number of QCI6, Service
Number of QCI7, Service Number of QCI8, or Service Number of
QCI9.
Local Cell ID ID of the cell on which service statistics monitoring is performed.
operators. In a non-RAN sharing scenario, a cell can be used by only
one operator. This parameter is set to 0 by default.
Monitor Period
(ms)
500, 1000, or 2000.

Table 7-8 Results of service statistics monitoring
Range
Description Formula
Service Number
of QCI[n]
Number 0 to 4000 Total number of services
with different QCIs when the
N/A
eNodeB

47

Range
Description Formula
CN Operator ID N/A 0 to 5 ID of the operator for which
service statistics monitoring
is performed.
N/A
CN Operator
Service Number
of QCI[n]
Number 0 to 4000 Total number of services
with different QCIs for an
operator when the
N/A

7.4 User Statistics Monitoring
This task is used to count the number of users in different scenarios to view the distribution of
users in a cell.
None
7.4.3 Parameters
Table 7-9 Parameters for user statistics monitoring
Test Items It can be set to Keep UL Synch Users Number, General Users
Number, NO-Activated Users Number, or a combination of some
items.
Local Cell ID ID of the cell on which user statistics monitoring is performed.
200, 500, 1000, or 2000.

Keep UL Synch Users Number
eNodeB

48

Table 7-10 Results of Keep UL Synch Users Number monitoring
Range
Description Formula
Keep UL Synch
Users Number
Number 0 to 2000 Number of users with
uplink
synchronization in a
cell when the
monitoring result is
reported. Users with
uplink
synchronization are
also known as active
users.
N/A
which user statistics
monitoring is
performed.
N/A
CN Operator
Keep UL Synch
Users Number
Number 0 to 2000 Number of an
operator's users with
uplink
synchronization when
the monitoring result
is reported. Users
with uplink
synchronization are
also known as active
users.
N/A

General Users Number
Table 7-11 Results of General Users Number monitoring
Range
Description Formula
General Users
Number
Number 0 to 2000 Number of
connected users and
users that are
requesting access to
the E-UTRAN in a
cell when the
reported.
Connected users are
active users and
non-active users.
Users that are
the E-UTRAN
consist of the users
Number of connected
users + Number of
users that are requesting
access to the E-UTRAN
eNodeB

49

Range
Description Formula
initiating radio
resource control
(RRC) connection
request or the users
from another
network during
handovers.
CN Operator
ID
N/A 0 to 5 ID of the operator
for which user
statistics monitoring
is performed.
N/A
CN Operator
General Users
Number
Number 0 to 2000 Number of an
operator's connected
users and users that
are requesting
access to the
E-UTRAN when the
reported.
Connected users are
active users and
non-active users.
Users that are
the E-UTRAN
consist of the users
initiating an RRC
connection request
and the users from
another network
during handovers.
Number of connected
users + Number of
users that are requesting
access to the E-UTRAN

NO-Activated Users Number
Table 7-12 Results of NO-Activated Users Number monitoring
Range
Description Formula
which user statistics
monitoring is
performed.
N/A
NO-Activated
Users Number
Number 0 to 2000 Number of non-active
users in a cell when
the monitoring result
is reported.
Non-active users are
N/A
eNodeB

50

Range
Description Formula
also known as users
with uplink
asynchronization.
CN Operator
NO-Activated
Users Number
Number 0 to 2000 Number of non-active
users of an operator
when the monitoring
result is reported.
Non-active users are
also known as users
with uplink
asynchronization.
N/A

7.5 RB Usage Monitoring
This task is used to monitor the usage of cell-level RBs in different scheduling modes. RB is
the minimum unit for time-frequency resource allocation.
During high-volume traffic, the monitoring data may be lost but services are not affected.
7.5.3 Parameters
Table 7-13 Parameters for RB usage monitoring
Local Cell ID ID of the cell on which RB usage monitoring is performed.
200, 500, 1000, or 2000.

eNodeB

51

Table 7-14 Results of RB usage monitoring
Range
Description Formula
Downlink
Equivalent
Used RB
Num
Number 0 to
200000
Number of downlink RBs used
within a monitoring period,
which is the total number of RBs
used by paging messages and
system information blocks
(SIBs) within all transmission
time intervals (TTIs) in the
monitoring period.
N/A
Uplink
Equivalent
Used RB
Num
Number 0 to
200000
Number of uplink RBs used
within a monitoring period,
which is the total number of RBs
occupied by the PUSCH,
PUCCH, and PRACH within all
TTIs in the monitoring period.
N/A
Downlink
Freq
Diversity
Used RB
Num
Number 0 to
200000
Number of RBs allocated for
downlink diversity scheduling
within all TTIs in a measurement
period.
N/A
Downlink
Freq Select
Used RB
Num
Number 0 to
200000
downlink frequency selective
scheduling within all TTIs in a
monitoring period.
N/A
Downlink
HARQ RB
Used RB
Num
Number 0 to
200,000
downlink HARQ retransmission
within all TTIs in a monitoring
period.
N/A
Uplink
PUCCH RB
Num
Number 0 to
200000
Number of RBs used by the
PUCCH within all TTIs in a
monitoring period.
N/A
CN Operator
ID
N/A 0 to 5 ID of the operator for which RB
usage monitoring is performed.
N/A
CN Operator
Downlink
Equivalent
Used RB
Num
Number 0 to
200000
Number of downlink RBs used
by the PDSCH of the operator
within all TTIs in a monitoring
period.

The value of this parameter equals
the actual number of downlink RBs
used by the operator.
N/A
CN Operator
Uplink
Number 0 to Number of uplink RBs used by
the PUSCH of the operator
N/A
eNodeB

52

Range
Description Formula
Equivalent
Used RB
Num
200000 within all TTIs in a monitoring
period.

The value of this parameter equals
the actual number of uplink RBs
used by the operator.

7.6 ICIC Monitoring
This task is used to check the status of ICIC by monitoring the data associated to ICIC.
None
7.6.3 Parameters
Table 7-15 Parameters for ICIC monitoring
Test Items It can be set to HII information, OI information, Proportion of
High Interference RB in System Bandwidth, Edge User RB
Information, Neighbor Cell List Information, or a combination of
some items.
Local Cell ID ID of the cell on which ICIC monitoring is performed.
Monitor Period
(ms)
500, 1000, or 2000.

HII information
Table 7-16 Results of HII information monitoring
Valid RB
Num in One
Hii sent
Number 0 to 110 Number of available RBs
in one HII when the
reported, which is the same
as the number of RBs
N/A
eNodeB

53

occupied by the current cell
bandwidth.

OI information
Table 7-17 Results of OI information monitoring
Valid RB Num
in One Oi sent
Number 0 to 110 Number of valid RBs in one
OI when the monitoring
result is reported, which is
the same as the number of
RBs occupied by the current
cell bandwidth.
N/A

Proportion of High Interference RB in System Bandwidth
Table 7-18 Results of Proportion of High Interference RB in System Bandwidth monitoring
Range
Description Formula
Proportion of High
Interference RB in
System Bandwidth
% 0 to 100 Proportion of high-interference
RBs in the serving cell to RBs
occupied by the current cell
bandwidth when the monitoring
result is reported.
N/A

Edge User RB Information
Table 7-19 Results of Edge User RB Information monitoring
Range
Description Formula
Edge User Valid RB
Num
Number 0 to 110 Number of valid RBs in
the available frequency
band for cell edge users
(CEUs) when the
reported.
N/A

Neighbor Cell List Information
eNodeB

54

Table 7-20 Results of Neighbor Cell List Information monitoring
Range
Description Formula
Valid Neighbor
Cell Num
Number 0 to 32 Number of valid neighboring
cells used for ICIC when the
N/A

7.7 MU-MIMO Monitoring
This task is used to monitor the number of UEs paired with multi-user multiple-input
multiple-output (MU-MIMO) during a transmission time interval (TTI). Two UEs
successfully paired with MU-MIMO are called one pair. On the M2000, the total number of
UEs paired with MU-MIMO within a configured period is displayed, based on which the
number of paired UEs in the current cell can be viewed.
None
7.7.3 Parameters
Table 7-21 Parameters for MU-MIMO monitoring
Local Cell ID ID of the cell on which MU-MIMO monitoring is performed.
Monitor Period
(ms)
500, 1000, or 2000.

Table 7-22 Results of MU-MIMO monitoring
MIMO UE
Pair Num
Pair 0 to 16000 Total number of UEs paired with
uplink MU-MIMO during all
TTIs in the monitoring period.
Two UEs paired with
MU-MIMO are called one pair.
N/A

eNodeB

55

7.8 Interference RSSI Statistic Detect Monitoring
This task is used to monitor the RX power of each RB used by the demodulation reference
signals (DMRS) within the current bandwidth and average RX power of each antenna.
None
7.8.3 Parameters
Table 7-23 Parameters for interference RSSI statistic detect monitoring
Local Cell ID ID of the cell on which interference RSSI statistic detect monitoring
is performed.
200, 500, 1000, or 2000.

Table 7-24 Results of interference RSSI statistic detect monitoring
Range
Description Formula
RB Spectrum
Information
dBm 2
16
to
+2
16

RSSI of an RB.
The power of 12
subcarriers in the
RB is summed
and then averaged
for multiple
antennas. RSSIs
of the RBs falling
beyond the
bandwidth are
reported as 0 by
layer 1.
AntNum
AntNum {P(AntIdx, k, n)}
RSSI_RB(k) =
AntNum - 1
AntIdx = 0 n = 0
11
where,
AntNum indicates the number
of antennas for the current cell.
P( ) indicates the
receive power of subcarrier n
in RBk received by antenna
AntIdx.
RSSI
(Received
Signal
Strength
Indicator)
dBm 140 to
50
RSSI within the
current system
bandwidth.

where,
SysRB indicates the number of
RBs in the current system
bandwidth.
System
Bandwidth
Number 6, 15,
25, 50,
Current system
bandwidth.
N/A
eNodeB

56

Range
Description Formula
(Number of
RB)
75, 100
antenna[y]
RSSI
dBm 140 to
50
RSSI for antenna
y within the
current system
bandwidth. y
ranges from 0 to
7.
RSSI_Ant(AntIdx) = {P(AntIdx, k, n)}
SysRB
k = 0 n = 0
11
where,
P( ) indicates the
in RBk of antenna AntIdx. The
value of AntIdx is y.

7.9 Interference Detection Monitoring
This task is used to record the current interference power of each RB for checking the uplink
interference.
None
7.9.3 Parameters
Table 7-25 Parameters for interference detection monitoring
Local Cell ID ID of the cell on which interference detection monitoring is
performed.
200, 500, 1000, or 2000.

Table 7-26 Results of interference detection monitoring
Range
Description Formula
PUSCH Cell dBm 2
15
to 2
15
1 Average
interference
eNodeB

57

Range
Description Formula
noise power of
the PUSCH in
the whole system
bandwidth.
where,
PUSCH_RB indicates the
number of RBs on the current
PUSCH.
Max RB
Number of
PUCCH
configured in
system
Num
ber
0 to 26 Current PUCCH
bandwidth
(indicated by the
number of RBs).
N/A
System
Bandwidth
(Number of
RB)
Num
ber
6, 15, 25,
50, 75, 100
Current system
bandwidth.
N/A
PUSCH
interference
Noise Power
per RB
dBm 2
15
to 2
15
1 PUSCH
interference
noise power on
the kth RB.
Interference of
the RBs falling
beyond the
PUSCH
bandwidth is
reported as 0.

where,
IN(AntIdx, k, n) indicates the
in RB k received by antenna
AntIdx.

7.10 Scheduled Cell-Level UE Information Monitoring
This task is used to monitor the distribution of UEs in various scheduling modes in a cell.
None
7.10.3 Parameters
Table 7-27 Parameters for scheduled cell-level UE information monitoring
Local Cell ID ID of the cell on which scheduled users statistic monitoring is
performed.
Monitor Period
(ms)
500, 1000, or 2000.
eNodeB

58

Table 7-28 Results of scheduled cell-level UE information monitoring
Range
Description Formula
Total DLSCH
Users Within
Monitor Period
Number 0 to 65535 Total number of UEs in
downlink scheduling mode
N/A
Total DLSCH
Frequency
Selected Users
Within Monitor
Period
downlink frequency selective
scheduling mode within a
monitoring period.
N/A
Total DLSCH
Diversity Users
Within Monitor
Period
downlink diversity scheduling
mode within a monitoring
period.
N/A
Total ULSCH
Users Within
Monitor Period
Number 0 to 65535 Total number of UEs in uplink
scheduling mode within a
monitoring period.
N/A

7.11 HARQ Status Monitoring
This task is used to monitor uplink and downlink HARQ information of all UEs in a cell in
real time. Based on this information, the data transmission status of the eNodeB or UEs can
be determined.
None
7.11.3 Parameters
Table 7-29 Parameters for HARQ status monitoring
Test Items It can be set to DL HARQ State, UL HARQ State, or a combination
of the items.
Local Cell ID ID of the cell on which HARQ statistic monitoring is performed.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000 or 2000.
eNodeB

59

DL HARQ State
Table 7-30 Results of DL HARQ State monitoring
Range
Description Formula
DL PDSCH Code[m]
ACK Num
Number 0 to
64000
Number of ACKs for
codeword m (m = {0, 1})
The greater the proportion of
the number of ACKs to the
total number of ACKs,
NACKs, and DTXs, the more
successfully received
messages from the eNodeB,
indicating effective cell
coverage.
For details about ACK and
NACK, see 3GPP TS 36.321.
N/A
DL PDSCH Code[m]
NACK Num
Number 0 to
64000
Number of NACKs for
The greater the proportion of
the number of NACKs to the
total number of ACKs,
NACKs, and DTXs, the less
successfully received
messages from the eNodeB.
For details about ACK and
NACK, see 3GPP TS 36.321.
N/A
DL PDSCH Code[m]
NoRsp Num
Number 0 to
64000
Number of NoRsps for
NoRsp indicates that no
HARQ feedback is decoded
due to an exception in the
eNodeB, or the eNodeB
decodes the HARQ feedback
but the decoding duration
exceeds the HARQ RTT.
For details about the HARQ
RTT, see DL PDSCH Rsp
for [m] TTI Num.
N/A
DL PDSCH Code[m]
DTX Num
Number 0 to
64000
Number of DTXs for
DTX indicates that the
eNodeB fails to detect the
N/A
eNodeB

60

Range
Description Formula
HARQ feedback.
For details, see 3GPP TS
36.331.
DL PDSCH
Version[m] Num
Number 0 to
64000
Number of times the HARQ
redundancy version in
transport blocks (TBs) sent
from the eNodeB is m (m =
{0, 1, 2, 3}) within a
monitoring period.
N/A
DL PDSCH Rsp for
[m] TTI Num
Number 0 to
64000
Number of times the eNodeB
receives the HARQ feedback
within a downlink scheduling
interval m TTIs (One TTI
equals to one millisecond)
m = {8, 9, 10, 11}. Any value
greater than 11 is treated as
11.
This item monitors the
duration that the eNodeB
internally processes the
HARQ feedback. According
to the protocol, the HARQ
RTT equals to 8 TTIs for
FDD mode. For TDD mode,
the HARQ RTT varies
depending on the subframe
distribution rate. If the
duration exceeds the HARQ
RTT, the eNodeB
experiences internal
processing exceptions.
N/A

UL HARQ State
Table 7-31 Results of UL HARQ State monitoring
Range
Description Formula
UL PUSCH ACK
Num
Num
ber
0 to
64000
Number of times the CRC for
data blocks on the PUSCH is
correct within a monitoring
period. The greater the
proportion of the number of
ACKs to the total number of
ACKs, NACKs, and DTXs, the
more the times that the CRC
N/A
eNodeB

61

Range
Description Formula
for the PUSCH data sent by the
UE to the eNodeB is correct,
indicating higher uplink
transmitting quality of the UE.
UL PUSCH NACK
Num
Num
ber
0 to
64000
Number of times the CRC for
data blocks on the PUSCH is
incorrect within a monitoring
NACKs to the total number of
more the times that the CRC
for the PUSCH data sent by the
UE to the eNodeB is incorrect.
N/A
UL PUSCH DTX
Num
Num
ber
0 to
64000
Number of times the UE does
not transmit data on the
PUSCH within a monitoring
DTXs to the total number of
more the times that the UE
incorrectely demodulates the
downlink PDCCH data.
N/A
UL PUSCH
Version[n] Num
Num
ber
0 to
64000
Number of times the HARQ
redundancy version for the
eNodeB uplink scheduling is m
(m = {0, 1, 2, 3}) within a
monitoring period.
36.321.
N/A

7.12 Air-Interface DCI Status Monitoring
This task is used to monitor the usage of a cell-level PDCCH, including the downlink control
information (DCI) format, aggregation level, and PDCCH symbol number, which are
described as follows:
The DCI format indicates resource allocation information. A specific DCI format is used
in a different MIMO mode.
The aggregation level indicates the size of time-frequency resources occupied by a
PDCCH.
eNodeB

62

The PDCCH symbol number indicates the number of OFDM symbols occupied by a
PDCCH.
None
7.12.3 Parameters
Table 7-32 Parameters for air-interface DCI status monitoring
Test Items It can be set to DCI STATISTIC.
Local Cell ID ID of the cell on which DCI statistic monitoring is performed.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000 or
2000.

Table 7-33 Results of air-interface DCI status monitoring
Range
Description Formula
PDCCH Type
DCI[n] Num
Num
ber
0 to 64000 Total number of times
the PDCCH type is
DCI format n (n = {0,
1, 1A, 1B, 1C, 1D, 2,
2A, 2B, 3, 3A})
within a monitoring
period.

N/A
PDCCH Use [n]
CCE Num
Num
ber
the aggregation level
is n (n = {1, 2, 4, 8})
within a monitoring
period.
N/A
CFI Engross [n]
Symbol State
Num
Num
ber
the control format
indicator (CFI) is n (n
= {1, 2, 3, 4}) OFDM
symbols within a
monitoring period.
N/A
UL DCI
Utilization
Within a
Monitoring
% 0 to 100 Uplink DCI utilization
within a monitoring
period.
Uplink DCI is DCI
Total number of CCEs
in uplink DCI/Total
number of CCEs within
the monitoring period
eNodeB

63

Range
Description Formula
Period format 0.
DL DCI
Utilization
Within a
Monitoring
Period
% 0 to 100 Downlink DCI
utilization within a
monitoring period.
Downlink DCI is DCI
format n, where n is 1,
1A, 1B, 1C, 1D, 2,
2A, and 2B.
in downlink DCI/Total
the monitoring period.
Comm DCI
Utilization
Within a
Monitoring
Period
% 0 to 100 Common DCI
utilization within a
monitoring period.
Common DCI is DCI
format 3 and DCI
format 3A.
in common DC/Total
the monitoring period.
Total CCE Num
Within a
Monitoring
Period
Num
ber
0 to
100000
within a monitoring
period. If the CFI
adaption switch is
disenabled, the total
number of CCEs does
not change. When the
symbol dynamic
adjustment switch is
enabled, the number
of CCEs varies based
on the adjustment of
the CFI. The status of
the switch can be
queried by running the
DSP
CELLPDCCHALG
O command.
N/A

7.13 Air-Interface DRB Statistics Monitoring
This task is used to monitor data transmission information at the cell-level PDCP, RLC, or
MAC layer, including the throughput, number of received packets, and number of transmitted
packets.
None
eNodeB

64

7.13.3 Parameters
Table 7-34 Parameters for air-interface DRB statistics monitoring
Test Items It can be set to DL DRB STATISTIC, UL DRB STATISTIC, or a
combination of the items.
Local Cell ID ID of the cell on which DRB statistics monitoring is performed.
Monitor Period
(ms)

DL DRB STATISTIC
Table 7-35 Results of downlink DRB statistics monitoring
Range
Description Formula
Number of Packets
Received at the DL
PDCP
Packet 0 to
30000000
0
Total number of data
downlink PDCP layer within
N/A
Number of Bits
Received at the DL
PDCP
Bit 0 to
30000000
0
Total throughput for data
downlink PDCP layer within
N/A
Number of TBs for DL
MAC scheduling
Number 0 to
30000000
0
Total number of TBs for
downlink MAC scheduling
N/A
Number of Bits for DL
MAC scheduling
Bit 0 to
30000000
0
Total number of bits
contained in the TBs for
downlink MAC scheduling
N/A
Number of Times DL
RLC Sends Data in
AM mode
Number 0 to
30000000
0
Total number of times the
downlink RLC layer
transmits data in
acknowledgment (AM)
period.

The RLC layer transmits data in
AM or UM modes. In AM mode,
a transmission report is fed back.
In UM, no report is fed back.
N/A
NOTE
eNodeB

65

Range
Description Formula
Number of Times DL
RLC Sends Data in
UM mode
Number 0 to
30000000
0
downlink RLC layer
transmits data in
unacknowledgment (UM)
period.
N/A

UL DRB STATISTIC
Table 7-36 Results of uplink DRB statistics monitoring
Range
Description Formula
Number of TBs for UL
MAC Scheduling
Number 0 to
30000000
0
Total number of TBs for
uplink MAC scheduling
within a monitoring
period.
N/A
Number of Bits for UL
MAC Scheduled
Bit 0 to
30000000
0
Total number of bits
contained in the TBs for
uplink MAC scheduling
within a monitoring
period.
N/A
Number of UL TBs
With CRC Correct
Number 0 to
30000000
0
uplink MAC layer receives
correct CRCs from a UE
within a monitoring
period.
N/A
Number of UL TBs
With CRC Incorrect
Number 0 to
30000000
0
uplink MAC layer receives
incorrect CRCs from a UE
within a monitoring
period.
N/A
Number of Times UL
RLC Receives Data in
AM mode
Number 0 to
30000000
0
uplink RLC layer transmits
data in AM mode within a
monitoring period.
N/A
Number of Times UL
RLC Receives Data in
UM mode
Number 0 to
30000000
0
uplink RLC layer transmits
data in UM mode within a
monitoring period.
N/A
Number of Packets
Transmitted at the UL
PDCP
Packet 0 to
30000000
0
Total number of data
packets transmitted by the
uplink PDCP layer within
N/A
eNodeB

66

Range
Description Formula
Number of Bits
Transmitted at the UL
PDCP
Bit 0 to
30000000
0
Total throughput for data
packets transmitted by the
uplink PDCP layer within
N/A

eNodeB
Performance Monitoring Reference 8 User Performance Monitoring

67

8 User Performance Monitoring
8.1 DL RSRP/RSRQ Monitoring
Reference signal received power (RSRP) and reference signal received quality (RSRQ)
indicate the received signal power and quality of UEs respectively. DL RSRP/RSRQ
Monitoring can be used to:
Calculate loss on the downlink to facilitate the analysis of drive test (DT) data.
Preliminarily detect and isolate network coverage problems.
None
8.1.3 Parameters
Table 8-1 Parameters for DL RSRP/RSRQ monitoring
UEID-MME MME that serves a UE.
UEID-TMSI/Trace
Reference No.
TMSI or trace reference number to be monitored.
480, 640, 1024, or 2048.

eNodeB

68

Table 8-2 Results of DL RSRP/RSRQ monitoring
Range
Description Formula
ServCell PCI N/A N/A Physical cell ID of a serving
cell.
N/A
ServCell RSRP dBm 140 to 44 RSRP of a serving cell. N/A
ServCell RSRQ dB 19.5 to3 RSRQ of a serving cell. N/A
NeighborCell
PCI[n]
N/A N/A Physical cell ID of the nth
neighboring cell. n is an integer
from 1 to 8.

This field specifies the sequence
for reporting the measurement
reports of neighboring cells. A
maximum of eight neighboring
cells are dynamically displayed.
N/A
NeighborCell
RSRP[n]
dBm 140 to 44 RSRP of the nth neighboring
cell. n is an integer from 1 to 8.
N/A
NeighborCell
RSRQ[n]
dB 19.5 to 3 RSRQ of the nth neighboring
cell. n is an integer from 1 to 8.
N/A

8.2 BLER Monitoring
This task is used to monitor the BLERs on each channel of the UE.
None
8.2.3 Parameters
Table 8-3 Parameters for BLER monitoring
Test Items It can be set to Init BLER, Resident BLER, PDCCH BLER, or a
combination of these items.
UEID-TMSI/Trace TMSI or trace reference number to be monitored.
eNodeB

69

Reference No.
200, 500, 1000, or 2000.

Init BLER
Table 8-4 Results of Init BLER monitoring
Range
Description Formula
Physical Cell
Identifier
N/A N/A Physical cell identifier
of the serving cell.
N/A
Downlink
IBLER
0 to
1000
BLER of initial TB
transmission on a
PDSCH within a
monitoring period.
Total number of TBs that
fail to be initially
transmitted on the PDSCH
x 1000/Total number of
initially transmitted TBs on
the PDSCH within the
monitoring period
Uplink
IBLER
0 to
1000
BLER of initial TB
transmission on a
PUSCH within a
monitoring period.
Total number of TBs that
fail to be initially
transmitted on the PUSCH
x 1000/Total number of
initially transmitted TBs on
the PUSCH within the
monitoring period

Resident BLER
Table 8-5 Results of Resident BLER monitoring
Range
Description Formula
Physical Cell
Identifier
N/A
Downlink
RBLER
0 to 1000 BLER of the last TB
retransmission on a
PDSCH within a
monitoring period.
Number of times TBs
that last fail to be
PDSCH x 1000/Total
number of initially
transmitted TBs on
the PDSCH within the
eNodeB

70

Range
Description Formula
monitoring period
Uplink RBLER 0 to 1000 BLER of the last TB
retransmission on a
PUSCH within a
monitoring period.
Number of times TBs
that last fail to be
PUSCH x 1000/Total
number of initially
transmitted TBs on
the PUSCH within the
monitoring period

PDCCH BLER
Table 8-6 Results of PDCCH BLER monitoring
Range
Description Formula
Physical Cell
Identifier
N/A N/A Physical cell
identifier of the
serving cell.
N/A
PDCCH BLER 0 to 1000 BLER of
DLGRANT
decoding on a
PDCCH within a
monitoring period.
Number of times
DLGRANTs decoded
incorrectly x 1000/Total
number of DLGRANTs
sent on a PDCCH
The number of
DLGRANTs decoded
incorrectly is the number
of DTXs that were the
feedback given to the
DLGRANTs sent on a
PDCCH.

8.3 Power Headroom Monitoring
Power headroom (PHR) is the value that the maximum transmit power minus the current
power. This task is used to monitor the power headroom reported by the UE. Based on this
information, the remaining processing capacity of the UE can be estimated as a reference for
the eNodeB to assign uplink RB resources for the UE.
eNodeB

71

None
8.3.3 Parameters
Table 8-7 Parameters for power headroom monitoring
UEID-MME MME that serves the UE.
UEID-TMSI/Tra
ce Reference No.
Monitor Period
(ms)
500, 1000, or 2000.

Table 8-8 Result of power headroom monitoring
Range
Description Formula
Physical Cell
Identifier
N/A 0 to 503 Physical cell identifier of the
serving cell.
N/A
Power Headroom dB 23 to +40 Power headroom last reported by
the UE.
For details about formula of
Power Headroom, see 3GPP TS
36.213, 36.321, and 36.133.
N/A

8.4 Channel Quality Monitoring
This task is used to monitor the uplink and downlink channel status of the UE in real time.
Based on the channel status, the uplink and downlink channel quality of the UE can be
determined.
None
eNodeB

72

8.4.3 Parameters
Table 8-9 Parameters for channel quality monitoring
Test Items It can be set to SINR, CQI, or a combination of the items.

Signal to interference and noise ratio (SINR) indicates the uplink
channel quality of the UE.

CQI indicates the downlink channel quality of the UE.
UEID-TMSI/Trac
e Reference No.
Monitor Period
(ms)
500, 1000, or 2000.

SINR
Table 8-10 Results of SINR monitoring
Physical Cell
Identifier
N/A N/A Physical cell identifier of the
serving cell.
N/A
SINR 0.01 dB 12700 to
+12700
Average SINR for the full
bandwidth of the eNodeB
monitored.
N/A
SINR Flag N/A N/A Flag specifying whether the
average SINR for the full
bandwidth of the UE is
effective. The value 0 indicates
the average SINR is not
effective. The value 1 indicates
the average SINR is effective.
N/A

CQI
Table 8-11 Results of CQI monitoring
Range
Description Formula
Physical Cell
Identifier
N/A
eNodeB

73

Range
Description Formula
UE Code
Count
Numb
er
1 to 2 Number of transmitted
code words in the
downlink when the
reported.
N/A
Effective
Len
ms 41 to 44 Valid length of the
aperiodic CQI for the
full bandwidth. This
parameter takes effect
only when the aperiodic
CQI frequency selection
is configured.
N/A
CQI N/A 0 to 31 Five-bit value mapped
to the originally
reported CQI for the full
bandwidth.

8.5 Scheduling Monitoring
This task is used to monitor the scheduling information sent from the UE, including the
number of scheduling requests (SRs), the status of each data buffer area, and the number of
GAPs, DRXs, and TTIs within a monitoring period.
The status of each data buffer area is not the BSR indexes reported by the UE, but the status
of the buffer area corresponding to different logical channels maintained for the UE and
mapped to the eNodeB based on the BSRs reported by the UE. The eNodeB maintains four
data buffer areas for each UE. The four data buffer areas are BSR[0], BSR[1], BSR[2], and
BSR[3].
None
8.5.3 Parameters
Table 8-12 Parameters for scheduling monitoring
Test Items It can be set to UL SR of Service, UL BSR of Service, Percentage of
DRX activity timer in DRX timer, or a combination of these items.
eNodeB

74

UEID-TMSI/Tra
ce Reference No.
Monitor Period
(ms)
500, 1000, or 2000.

UL SR of Service
Table 8-13 Results of UL SR of Service monitoring
Physical Cell
Identifier
serving cell.
N/A
Number of SRs Number 0 to 64000 Number of SRs reported by
the UE to the eNodeB within
a monitoring period. When
the UE needs to perform a
UL data transfer but there is
no UL resources available,
the UE must send an SR to
require the eNodeB to grant
UL data transfer permission.
36.321.
N/A

UL BSR of Service
Table 8-14 Results of UL BSR of Service monitoring
Range
Description Formula
Physical Cell
Identifier
serving cell.
N/A
Byte Length of
LCG BS[n]
Bit 0 to 150000 Buffered data volume of the
LCG, which is represented
with BSR[n] (n = {0 to 3}),
indicating the volume of
control signaling data to be
scheduled in a butter area.
After reported by the UE,
LongBsr, TruncateBsr, and
ShortBsr are mapped by the
eNodeB into BSR[0] to
BSR[3]. After received the
N/A
eNodeB

75

Range
Description Formula
data from the UE, the eNodeB
subtracts corresponding data in
BSR[n].
36.321.

Percentage of DRX activity timer in DRX timer
Table 8-15 Results of Percentage of DRX activity timer in DRX timer monitoring
Range
Description Formula
Physical Cell
Identifier
serving cell.
N/A
TTIs in GAP
State
Number 0 to
4294967295
Number of accumulated TTIs in
the call gapping (GAP) state
during the monitoring period.
For details, see 3GPP TS 36.213.
N/A
TTIs in DRX
State
Number 0 to
4294967295
Number of accumulated TTIs in
the DRX state during the
monitoring period.
For details, see 3GPP TS 36.321.
N/A
Number of TTI Number 0 to
4294967295
Number of accumulated TTIs
between the establishment and the
release of an L2 case.
N/A

8.6 RLC Data Stream Monitoring
This task is used to monitor the data volume to be sent in the downlink buffer area at the RLC
layer in real time. Based on the monitoring results, whether the data transmission of the
eNodeB or UE is proper can be determined.
None
eNodeB

76

8.6.3 Parameters
Table 8-16 Parameters for RLC data stream monitoring
UEID-TMSI/Tra
ce Reference No.
Monitor Period
(ms)
500, 1000, or 2000.

Table 8-17 Result of RLC data stream monitoring
Physical Cell
Identifier
serving cell.
N/A
RLC Number N/A 0 to 8 Number of DRB set up by
users. The value 0 indicates
that no default bearer has
been set up.
N/A
DRB No. N/A 1 to 8 Number of the DRB. N/A
DRB RLC
Buffer Length
Byte 0 to 10000000 Data stream of the RLC SDUs
to be sent on the data radio
bearer (DRB) from the
downlink buffer area at the
RLC layer when the
N/A

8.7 Throughput Monitoring
This task is used to view the UL and DL throughputs of the UE and the UL and DL
throughputs on each bearer in real time. Based on the monitoring results, whether the data
transmission of the eNodeB or UE is proper can be determined.
None
eNodeB

77

8.7.3 Parameters
Table 8-18 Parameters for throughput monitoring
Test Items It can be set to Throughput of RLC, Throughput of MAC, or a
combination of the items.
UEID-TMSI/Trac
e Reference No.
Monitor Period
(ms)
500, 1000, or 2000.

Throughput of RLC
Table 8-19 Results of RLC throughput monitoring
Range
Description Formula
Physical Cell
Identifier
N/A
RLC Number N/A 0 to 8 Number of DRB set
up by users. The value
0 indicates that no
default bearer has
been set up.
N/A
DRB No. N/A 1to 8 Number of the DRB. N/A
Downlink RLC
Throughput
bps 0 to
300000000
Total throughputs of
the downlink RLC
SDUs sent on the
DRB at the RLC layer
within a monitoring
period.
(Downlink RLC
throughputs on the
RLC logical channels
(Byte) x 8)
x1000/Monitoring
period (ms)
Uplink RLC
Throughput
bps 0 to
300000000
Total throughputs of
the uplink RLC SDUs
received on the DRB
at the RLC layer
within a monitoring
period.
(Uplink RLC
throughputs on the
RLC logical channels
(Byte) x 8) x
1000/Monitoring
period (ms)

Throughput of MAC
eNodeB

78

Table 8-20 Results of MAC throughput monitoring
Physical Cell
Identifier
N/A
Downlink MAC
Throughput
bps 0 to
300000000
User-level downlink
MAC throughputs
within a monitoring
period.
User-level
downlink MAC
throughputs within
a monitoring
period
Uplink MAC
Throughput
bps 0 to
300000000
User-level uplink
MAC throughputs
within a monitoring
period
(Uplink MAC
throughputs(Byte)
x 8) x
1000/Monitoring
period (ms)

8.8 AQM Monitoring
This task is used to monitor the number of discarded packets related to the active queue
management (AQM) algorithm and the number of RLC SDUs to be sent on the DRB from the
downlink RLC buffer area. Based on the monitoring results, whether the data transmission of
the eNodeB or UE is proper can be determined.
None
8.8.3 Parameters
Table 8-21 Parameters for AQM monitoring
Test Items It can be set to Percentage of AQM discard package, DL RLC
buffer length of eNodeB, or a combination of the items.
UEID-TMSI/Trac
e Reference No.
Monitor Period
(ms)
500, 1000, or 2000.

eNodeB

79

Table 8-22 Results of AQM monitoring
Range
Description Formula
Physical Cell
Identifier
serving cell.
N/A
RLC Number N/A 0 to 8 Number of DRB set up by users.
The value 0 indicates that no
default bearer has been set up.
N/A
DRB No. N/A 1 to 8 Number of the DRB. N/A
Number of Packets
in RLC Buffer
Packet 0 to 20000 Number of RLC SDUs to be sent
on the DRB from the downlink
RLC buffer area at the end of a
monitoring period.
N/A
Number of
Discarded Packets
Packet 0 to 20000 Number of SDUs discarded by
AQM.
N/A

8.9 Uplink Power Control Monitoring
This task is used to monitor the necessary information about uplink power control when the
switch for uplink power control is turned on or off. This enables users to obtain the
information about the power adjustment when the switch for uplink power control is turned
on or off.
None
8.9.3 Parameters
Table 8-23 Parameters for uplink power control monitoring
Test Items It can be set to Close-loop Power of UE, PUSCH N max updated of
UE, PUCCH ACK/NACK/DTX Statistic, or a combination of these
items.
UEID-TMSI/Tra
ce Reference No.
eNodeB

80

Monitor Period
(ms)
500, 1000, or 2000.

Close-loop Power of UE
Table 8-24 Results of Close-loop Power of UE monitoring
Range
Description Form
ula
Physical Cell Identifier N/A N/A Physical cell identifier of
the serving cell.
N/A
PUSCH IBLER target 0 to 1000 Target IBLER of PUSCH
closed-loop power control.
The value is set by running
MML commands.
N/A
PUCCH SINR target 0.01 dB 1500 to
+2000
Target SINR of PUCCH
closed-loop power control.
The value is set by running
MML commands.
N/A
PUCCH SINR Adjust
Step
0.01 dB 1500 to
+2000
The difference between the
actual SINR and the target
SINR of PUCCH
closed-loop power control
when the monitoring result
is reported.
N/A

PUSCH N max updated of UE
Table 8-25 Results of PUSCH N max updated of UE monitoring
Range
Description Formula
Physical Cell Identifier N/A N/A Physical cell identifier of
the serving cell.
N/A
Maximum Number of
Transmissions
Number 0 to 10 The maximum number of
transmissions on the uplink
PUSCH. It is set by
running MML commands.
N/A

PUCCH ACK/NACK/DTX Statistic
eNodeB

81

Table 8-26 Results of PUCCH ACK/NACK/DTX Statistic monitoring
Range
Description Formula
Physical Cell
Identifier
N/A N/A Physical cell identifier of
the serving cell.
N/A
Number of
PUCCH ACK
Number 0 to 2000 Number of ACKs detected
on the PUCCH by the
eNodeB within a
monitoring period.
N/A
Number of
PUCCH NACK
Number 0 to 2000 Number of NACKs on the
PUCCH detected by the
eNodeB within a
monitoring period.
N/A
Number of
PUCCH DTX
Number 0 to 2000 Number of DTXs on the
PUCCH detected by the
eNodeB within a
monitoring period.
N/A
PUCCH SINR 0.01 dB 1500 to
+4000
SINR value on the PUCCH
detected by the eNodeB
N/A

8.10 Downlink Power Control Monitoring
This task is used to monitor the necessary information about downlink power control when
the switch for downlink power control is turned on or off. This enables users to obtain the
power adjustment when the switch for downlink power control is turned on or off.
None
8.10.3 Parameters
Table 8-27 Parameters for downlink power control monitoring
Test Items It can be set to PDSCH of UE, PHICH of UE, PDCCH of UE, or
a combination of these items.
UEID-TMSI/Trace
Reference No.
eNodeB

82

200, 500, 1000, or 2000.

PDSCH UE
Table 8-28 Results of PDSCH UE monitoring
Range
Description Formula
Physical Cell
Identifier
serving cell.
N/A
PDSCH PA 0.01 dB 600 to
+300
Power offset between each
resource element (RE) on the
PDSCH and the pilot when
the monitoring result is
reported.
N/A
PDSCH Maximum
Number of
Transmissions
Number 0 to 28 Maximum number of
transmissions on the
PDSCH, excluding the initial
transmission. It is set by
running MML commands.
N/A
PDSCH IBLER
Target
0 to 1000 Target BLER in the initial
transmission during the
semi-static PDSCH power
control. It is set by running
MML commands.
N/A

PHICH UE
Table 8-29 Results of PHICH UE monitoring
Range
Description Formula
Physical Cell
Identifier
N/A N/A Physical cell
identifier of the
serving cell.
N/A
PHICH SINR
Target
0.001
dB
1500 to
+2000
Target SINR of
PHICH
outer-loop
power control.
The value is set
by running
N/A
eNodeB

83

Range
Description Formula
MML
commands.
PHICH SINR
Adjust Step
0.001
dB
1500 to
+2000
SINR
adjustment step
calculated in the
PHICH
outer-loop
power control
Adjustment step x
Number of NACKs
transmitted on the PHICH
within the period of
outer-loop power control
x (Actually measured
BLER Target BLER) x
1000/(1 Target BLER)
PHICH BER 1500 to
+2000
Probability for
decoding
NACKs into
ACKs within the
adjustment
period of the
PHICH
outer-loop
power control
Number of NACKs that
are decoded into ACKs x
1000/Number of NACKs
transmitted on the PHICH
Power Offset
of PHICH
0.01 dB 1500 to
+2000
Power offset
between each
RE on the
PHICH and the
pilot when the
monitoring
result is
reported.
N/A

PDCCH UE
Table 8-30 Results of PDCCH UE monitoring
Range
Description Formula
Physical Cell
Identifier
N/A N/A Physical cell identifier of
the serving cell.
N/A
Power Offset of
PDCCH
0.01 dB 1500 to
+2000
Offset between the
power for transmitting
each RE on the PDCCH
and the pilot power when
the monitoring result is
reported.
N/A
TTI ms 0 to
0xffffffff
TTI for the PDCCH
power transmitted at the
MAC layer.
N/A
eNodeB

84

8.11 Uplink ICIC Monitoring
This task is used to monitor the user properties and neighboring cell information in the uplink
ICIC to obtain the operating status of the uplink ICIC.
None
8.11.3 Parameters
Table 8-31 Parameters for uplink ICIC monitoring
Test Items It can be set to USER PROPERTY or USER NEIGHBOR LIST.
You can also select both test items for simultaneous monitoring.
UEID-TMSI/Trac
e Reference No.
Monitor Period
(ms)
500, 1000, or 2000.

USER PROPERTY
Table 8-32 Results of USER PROPERTY monitoring
Range
Description Formula
Physical Cell
Identifier
N/A N/A Physical cell identifier of the serving
cell.
N/A
User Type N/A N/A User property. It includes the CEUs
and cell center users.
N/A

USER NEIGHBOR LIST
eNodeB

85

Table 8-33 Results of USER NEIGHBOR LIST monitoring
Physical Cell
Identifier
serving cell.
N/A
Strongest
Neighbor Cell
N/A N/A Physical ID of the detected
neighbor cell with the best signal
quality among the cells in the
user neighbor list.
N/A
Sub-Strongest
Neighbor Cell
N/A N/A Physical ID of the detected
neighbor cell with the second
best signal quality among the
cells in the user neighbor list.
N/A

8.12 MCS Statistics Monitoring
This task is used to monitor the number of scheduling attempts and number of RBs in
scenarios of different MCSs. The eNodeB uses different MCSs to schedule UEs in different
channel situations. The step of the MCS ranges from steps 0 through 31. The number of
scheduling attempts indicates the number of scheduling attempts with a specific MCS step,
and the number of RBs indicates the total number of RBs scheduled using a specific MCS
step.
None
8.12.3 Parameters
Table 8-34 Parameters for MCS statistics monitoring
Test Items It can be set to DL MCS or UL MCS. You can also select both test
items for simultaneous monitoring.
UEID-TMSI/Trace
Reference No.
Monitor Period
(ms)

eNodeB

86

DL MCS
Table 8-35 Results of DL MCS monitoring
Range
Description Formula
Physical Cell
Identifier
serving cell.
N/A
DLSCH Code 0
Num[n]
Number 0 to 2000 Total number (n) of scheduling
on codeword 0 in the downlink
scheduling within a monitoring
period.
n = {0,31}
N/A
DLSCH Code 0
RBs[n]
Number 0 to
200,000
Total number (n) of RBs on
codeword 0 in the downlink
period.
mn = {0,31}
N/A
DLSCH Code 1
Num[n]
Number 0 to 2000 Total number (n) of scheduling
on codeword 1 in the downlink
period.
n = {0,31}
N/A
DLSCH Code 1
RBs[n]
Number 0 to
200,000
Total number (n) of RBs on
codeword 1 in the downlink
period.
mn = {0,31}
N/A

UL MCS
Table 8-36 Results of UL MCS monitoring
Range
Description Formula
Physical Cell
Identifier
serving cell.
N/A
ULSCH
Num[n]
Number 0 to 2000 Total number (n) of uplink
period.
n = {0,31}
N/A
ULSCH
RBs[n]
Number 0 to
200,000
Total number (n) of RBs in the
uplink scheduling within a
N/A
eNodeB

87

Range
Description Formula
monitoring period.
n = {0,31}

eNodeB
Performance Monitoring Reference 9 Clock Performance Monitoring

88

9 Clock Performance Monitoring
9.1 Clock Quality Test
This task is used to collect the phase offset data of non-packet-based clocks to facilitate fault
diagnosis. Note that clocks complying with IEEE 1588 V2 or clock over IP are packet-based.
None
9.1.3 Parameters
Table 9-1 Parameters for clock quality test monitoring
Cabinet No. Number of the cabinet where the board for clock quality test
Subrack No. Number of the subrack where the board for clock quality test
Slot No. Number of the slot where the board for clock quality test monitoring is
located.

Table 9-2 Results of clock quality test monitoring
Range
Description Formula
Test Type N/A 1 Type of test result. 1 indicates
phase offset.
N/A
eNodeB

89

Range
Description Formula
Count Value s 128 to
+127
Current phase offset.
The actual value of phase offset
ranges from 128 to +127 and
varies in two scenarios as
follows:

In normal scenarios, the
status of clock modules is
normal, and the value of
phase offset falls within the
range from 10 to +10.

In abnormal scenarios, if
excessive frequency
deviation occurs, the value
of phase offset falls within
the range from 128 to
+127.
N/A

9.2 IP Clock Data Collection
This task is used to collect network jitter data of IP clocks. This helps locate faults and find
out the alarm reporting cause. Causes for reporting reference clockrelated alarms include
jitter, excessive frequency deviation, and excessive phase offset.
None
9.2.3 Parameters
Table 9-3 Parameters for IP clock data collection
Cabinet No. Number of the cabinet where the board for IP clock data collection is
located.
Subrack No. Number of the subrack where the board for IP clock data collection is
located.
Slot No. Number of the slot where the board for IP clock data collection is
located.

eNodeB

90

Table 9-4 Results of IP clock data collection
Range
Description Formula
Report SN N/A N/A Reserved. N/A
Tp1 Max QoS Value ns 2
63
to
2
63
1
Maximum delay per second for
transmitting packets from the
clock server to the eNodeB
N/A
Tp1 Min QoS Value ns 2
63
to
2
63
1
Minimum delay per second for
clock server to the eNodeB
N/A
Tp2 Max QoS Value ns 2
63
to
2
63
1
Maximum delay per second for
eNodeB to the clock server
N/A
Tp2 Min QoS Value ns 2
63
to
2
63
1
Minimum delay per second for
eNodeB to the clock server
N/A

EnodeB Performance Monitoring

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

EnodeB Performance Monitoring

Caricato da

Copyright:

Formati disponibili

eNodeB

Potrebbero piacerti anche