LTE

eNodeB
V100R005C00
Performance Monitoring
Reference
Issue Draft B
Date 2012-07-24
HUAWEI TECHNOLOGIES CO., LTD.

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
Issue Draft B (2012-07-24) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
eNodeB
Performance Monitoring Reference Contents
Contents
1 About this Document ................................................................................................................... 1

2 Introduction.................................................................................................................................... 3
2.1 Overview .......................................................................................................................................................... 3
2.2 Performance Monitoring Types ........................................................................................................................ 3
2.3 Background Information .................................................................................................................................. 5
2.3.1 Precautions for Monitoring on 3900 Series Base Station ........................................................................ 5
2.3.2 Precautions for Monitoring on BTS3202Es ............................................................................................ 5
3 CPU Usage Monitoring ................................................................................................................ 6

3.1 CPU Usage Monitoring .................................................................................................................................... 6
3.1.1 Usage Scenario........................................................................................................................................ 6
3.1.2 Service Impact ........................................................................................................................................ 6
3.1.3 Parameters ............................................................................................................................................... 6
3.1.4 Monitoring Results .................................................................................................................................. 6
4 CPRI BER Monitoring .................................................................................................................. 8

4.1 CPRI BER Monitoring ..................................................................................................................................... 8
4.1.1 Usage Scenario........................................................................................................................................ 8
4.1.2 Service Impact ........................................................................................................................................ 8
4.1.3 Parameters ............................................................................................................................................... 8
4.1.4 Monitoring Results .................................................................................................................................. 9
5 RRU Performance Monitoring.................................................................................................. 10

5.1 RRU/RFU Output Power Monitoring ............................................................................................................ 10
5.1.1 Usage Scenario...................................................................................................................................... 10
5.1.2 Service Impact ...................................................................................................................................... 10
5.1.3 Parameters ............................................................................................................................................. 10
5.1.4 Monitoring Results ................................................................................................................................ 10
5.2 RRU/RFU Temperature Monitoring............................................................................................................... 11
5.2.1 Usage Scenario...................................................................................................................................... 11
5.2.2 Service Impact ...................................................................................................................................... 11
5.2.3 Parameters ............................................................................................................................................. 11
5.3 Sector Performance Monitoring ..................................................................................................................... 12
Issue Draft B (2012-07-24) Huawei Proprietary and Confidential ii

eNodeB
5.3.1 Usage Scenario...................................................................................................................................... 12

5.3.2 Service Impact ...................................................................................................................................... 12
5.3.3 Parameters ............................................................................................................................................. 12
5.4 Spectrum Detection ........................................................................................................................................ 13
5.4.1 Usage Scenario...................................................................................................................................... 13
5.4.2 Service Impact ...................................................................................................................................... 13
5.4.3 Parameters ............................................................................................................................................. 13
6 Transmission Performance Monitoring.................................................................................. 15

6.1 IP Link Monitoring ......................................................................................................................................... 15
6.1.1 Usage Scenario...................................................................................................................................... 15
6.1.2 Service Impact ...................................................................................................................................... 15
6.1.3 Parameters ............................................................................................................................................. 15
6.2 IP Path Performance Monitoring .................................................................................................................... 17
6.2.1 Usage Scenario...................................................................................................................................... 17
6.2.2 Service Impact ...................................................................................................................................... 17
6.2.3 Parameters ............................................................................................................................................. 18
6.3 IP Performance Monitoring ............................................................................................................................ 19
6.3.1 Usage Scenario...................................................................................................................................... 19
6.3.2 Service Impact ...................................................................................................................................... 19
6.3.3 Parameters ............................................................................................................................................. 19
6.4 SCTP Performance Monitoring ...................................................................................................................... 20
6.4.1 Usage Scenario...................................................................................................................................... 20
6.4.2 Service Impact ...................................................................................................................................... 20
6.4.3 Parameters ............................................................................................................................................. 20
6.5 Transmission Performance Monitoring .......................................................................................................... 22
6.5.1 Usage Scenario...................................................................................................................................... 22
6.5.2 Service Impact ...................................................................................................................................... 22
6.5.3 Parameters ............................................................................................................................................. 22
6.6 UDP Injection Test Monitoring ...................................................................................................................... 26
6.6.1 Usage Scenario...................................................................................................................................... 26
6.6.2 Service Impact ...................................................................................................................................... 26
6.6.3 Parameters ............................................................................................................................................. 26
6.7 Local Pass-By Traffic Monitoring .................................................................................................................. 27
Issue Draft B (2012-07-24) Huawei Proprietary and Confidential iii

eNodeB
6.7.1 Usage Scenario...................................................................................................................................... 27

6.7.2 Service Impact ...................................................................................................................................... 27
6.7.3 Parameters ............................................................................................................................................. 28
6.8 Resource Group Monitoring ........................................................................................................................... 28
6.8.1 Usage Scenario...................................................................................................................................... 28
6.8.2 Service Impact ...................................................................................................................................... 28
6.8.3 Parameters ............................................................................................................................................. 29
6.9 PPPoE Performance Monitoring .................................................................................................................... 33
6.9.1 Usage Scenario...................................................................................................................................... 33
6.9.2 Service Impact ...................................................................................................................................... 33
6.9.3 Parameters ............................................................................................................................................. 33
7 Cell Performance Monitoring ................................................................................................... 35

7.1 Service Satisfaction Monitoring ..................................................................................................................... 35
7.1.1 Usage Scenario...................................................................................................................................... 35
7.1.2 Service Impact ...................................................................................................................................... 35
7.1.3 Parameters ............................................................................................................................................. 35
7.2 General Throughput Monitoring .................................................................................................................... 37
7.2.1 Usage Scenario...................................................................................................................................... 37
7.2.2 Service Impact ...................................................................................................................................... 37
7.2.3 Parameters ............................................................................................................................................. 38
7.3 Service Statistics Monitoring ......................................................................................................................... 41
7.3.1 Usage Scenario...................................................................................................................................... 41
7.3.2 Service Impact ...................................................................................................................................... 41
7.3.3 Parameters ............................................................................................................................................. 41
7.4 User Statistics Monitoring .............................................................................................................................. 42
7.4.1 Usage Scenario...................................................................................................................................... 42
7.4.2 Service Impact ...................................................................................................................................... 42
7.4.3 Parameters ............................................................................................................................................. 42
7.5 RB Usage Monitoring .................................................................................................................................... 45
7.5.1 Usage Scenario...................................................................................................................................... 45
7.5.2 Service Impact ...................................................................................................................................... 45
7.5.3 Parameters ............................................................................................................................................. 45
7.6 ICIC Monitoring............................................................................................................................................. 47
Issue Draft B (2012-07-24) Huawei Proprietary and Confidential iv

eNodeB
7.6.1 Usage Scenario...................................................................................................................................... 47

7.6.2 Service Impact ...................................................................................................................................... 47
7.6.3 Parameters ............................................................................................................................................. 47
7.7 MU-MIMO Monitoring.................................................................................................................................. 49
7.7.1 Usage Scenario...................................................................................................................................... 49
7.7.2 Service Impact ...................................................................................................................................... 49
7.7.3 Parameters ............................................................................................................................................. 49
7.8 Interference RSSI Statistic Detect Monitoring ............................................................................................... 50
7.8.1 Usage Scenario...................................................................................................................................... 50
7.8.2 Service Impact ...................................................................................................................................... 50
7.8.3 Parameters ............................................................................................................................................. 50
7.9 Interference Detection Monitoring ................................................................................................................. 51
7.9.1 Usage Scenario...................................................................................................................................... 51
7.9.2 Service Impact ...................................................................................................................................... 51
7.9.3 Parameters ............................................................................................................................................. 51
7.10 Scheduled Cell-Level UE Information Monitoring ...................................................................................... 52
7.10.1 Usage Scenario .................................................................................................................................... 52
7.10.2 Service Impact .................................................................................................................................... 52
7.10.3 Parameters ........................................................................................................................................... 52
7.10.4 Monitoring Results .............................................................................................................................. 53
7.11 HARQ Status Monitoring ............................................................................................................................. 53
7.11.1 Usage Scenario .................................................................................................................................... 53
7.11.2 Service Impact ..................................................................................................................................... 53
7.11.3 Parameters ........................................................................................................................................... 54
7.12 Air-Interface DCI Status Monitoring ............................................................................................................ 57
7.12.1 Usage Scenario .................................................................................................................................... 57
7.12.2 Service Impact .................................................................................................................................... 57
7.12.3 Parameters ........................................................................................................................................... 57
7.13 Air-Interface DRB Statistics Monitoring ...................................................................................................... 59
7.13.1 Usage Scenario .................................................................................................................................... 59
7.13.2 Service Impact .................................................................................................................................... 59
7.13.3 Parameters ........................................................................................................................................... 59
8 User Performance Monitoring .................................................................................................. 62

8.1 DL RSRP/RSRQ Monitoring ......................................................................................................................... 62
Issue Draft B (2012-07-24) Huawei Proprietary and Confidential v

eNodeB
8.1.1 Usage Scenario...................................................................................................................................... 62

8.1.2 Service Impact ...................................................................................................................................... 62
8.1.3 Parameters ............................................................................................................................................. 62
8.2 BLER Monitoring .......................................................................................................................................... 63
8.2.1 Usage Scenario...................................................................................................................................... 63
8.2.2 Service Impact ...................................................................................................................................... 63
8.2.3 Parameters ............................................................................................................................................. 63
8.3 Power Headroom Monitoring ......................................................................................................................... 65
8.3.1 Usage Scenario...................................................................................................................................... 65
8.3.2 Service Impact ...................................................................................................................................... 65
8.3.3 Parameters ............................................................................................................................................. 65
8.4 Channel Quality Monitoring .......................................................................................................................... 66
8.4.1 Usage Scenario...................................................................................................................................... 66
8.4.2 Service Impact ...................................................................................................................................... 66
8.4.3 Parameters ............................................................................................................................................. 66
8.5 Scheduling Monitoring ................................................................................................................................... 68
8.5.1 Usage Scenario...................................................................................................................................... 68
8.5.2 Service Impact ...................................................................................................................................... 68
8.5.3 Parameters ............................................................................................................................................. 68
8.6 RLC Data Stream Monitoring ........................................................................................................................ 70
8.6.1 Usage Scenario...................................................................................................................................... 70
8.6.2 Service Impact ...................................................................................................................................... 70
8.6.3 Parameters ............................................................................................................................................. 70
8.7 Throughput Monitoring .................................................................................................................................. 71
8.7.1 Usage Scenario...................................................................................................................................... 71
8.7.2 Service Impact ...................................................................................................................................... 71
8.7.3 Parameters ............................................................................................................................................. 71
8.8 AQM Monitoring ........................................................................................................................................... 73
8.8.1 Usage Scenario...................................................................................................................................... 73
8.8.2 Service Impact ...................................................................................................................................... 73
8.8.3 Parameters ............................................................................................................................................. 73
8.9 Uplink Power Control Monitoring ................................................................................................................. 74
8.9.1 Usage Scenario...................................................................................................................................... 74
8.9.2 Service Impact ...................................................................................................................................... 74
Issue Draft B (2012-07-24) Huawei Proprietary and Confidential vi

eNodeB
8.9.3 Parameters ............................................................................................................................................. 74

8.10 Downlink Power Control Monitoring .......................................................................................................... 76
8.10.1 Usage Scenario .................................................................................................................................... 76
8.10.2 Service Impact .................................................................................................................................... 76
8.10.3 Parameters ........................................................................................................................................... 76
8.11 Uplink ICIC Monitoring ............................................................................................................................... 79
8.11.1 Usage Scenario .................................................................................................................................... 79
8.11.2 Service Impact ..................................................................................................................................... 79
8.11.3 Parameters ........................................................................................................................................... 79
8.12 MCS Statistics Monitoring ........................................................................................................................... 80
8.12.1 Usage Scenario .................................................................................................................................... 80
8.12.2 Service Impact .................................................................................................................................... 80
8.12.3 Parameters ........................................................................................................................................... 80
9 Clock Performance Monitoring ................................................................................................ 82

9.1 Clock Quality Test .......................................................................................................................................... 82
9.1.1 Usage Scenario...................................................................................................................................... 82
9.1.2 Service Impact ...................................................................................................................................... 82
9.1.3 Parameters ............................................................................................................................................. 82
9.2 IP Clock Data Collection ................................................................................................................................ 83
9.2.1 Usage Scenario...................................................................................................................................... 83
9.2.2 Service Impact ...................................................................................................................................... 83
9.2.3 Parameters ............................................................................................................................................. 83
Issue Draft B (2012-07-24) Huawei Proprietary and Confidential vii

eNodeB
Performance Monitoring Reference 1 About this Document
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
Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 1

eNodeB
Performance Monitoring Reference 1 About this Document
Change History
The following describes the changes in eNodeB Performance Monitoring Reference.
The document issues are as follows:
Draft B(2012-07-24)
Draft A (2012-06-29)
Draft B (2012-07-24)
This is draft B.
Compared with issue draft A (2012-06-29) of V100R005C00, this issue includes the following
new information.
Topic Change Description

4 CPRI BER Monitoring Added the description on CPRI BER Monitoring.
Compared with draft A (2012-06-29) of V100R005C00, this issue does not include any
changes.
No information in issue draft A (2012-06-29) of V100R005C00 is deleted from this issue.
Draft A (2012-06-29)
This is draft A.

eNodeB
Performance Monitoring Reference 2 Introduction
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 M2000
CPRI BER Monitoring M2000
RRU Performance RRU/RFU Output Power Monitoring M2000
Monitoring
RRU/RFU Temperature Monitoring M2000
Sector Performance Monitoring Web LMT
Spectrum Detection Web LMT
Transmission IP Link Monitoring M2000
Performance
Monitoring IP Path Performance Monitoring M2000
IP Performance Monitoring M2000
SCTP Performance Monitoring M2000
Transmission Performance Monitoring Web LMT
UDP Test Monitoring M2000
Local Pass-By Traffic Monitoring M2000

eNodeB
Type Task Platform

Resource Group Monitoring M2000
PPPoE Performance Monitoring Web LMT
Cell Performance Service Satisfaction Monitoring M2000
Monitoring
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 M2000
Monitoring
HARQ Statistic Monitoring M2000
Air-Interface DCI Status Monitoring M2000
Air-Interface DRB Statistics Monitoring M2000
User Performance DL RSRP/RSRQ Monitoring M2000
Monitoring
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 Clock Quality Test Monitoring M2000
Monitoring
IP Clock Data Collection M2000

eNodeB
2.3 Background Information

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
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 Interval of reporting monitoring results. It is set to the fixed value 5.
(Seconds)
3.1.4 Monitoring Results

Table 3-2 Results of CPU usage monitoring
Parameter Unit Value Description Formula

Range
Number of Number 1 Number of the boards. N/A
the Boards
Board No. N/A N/A The board number is N/A
displayed as follows:

eNodeB
Performance Monitoring Reference 3 CPU Usage Monitoring

Range
Cabinet No.: Subrack No.:
Slot No.
Number of Number 1 to 15 Number of CPUs varies N/A
the CPUs according to board types.
CPU No. N/A N/A The value range is 0 to the N/A
total number of CPUs.
Type N/A 1 to 3 The CPU type is as follows: N/A
1 indicates active CPU.
2 indicates DSP.
3 indicates slave CPU.
CPU Usage % 0 to 100 CPU usage when the N/A
monitoring results are
reported.

eNodeB
Performance Monitoring Reference 4 CPRI BER Monitoring
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
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
Uplink BER e^(-9) 0 to Uplink BER in the previous N/A
1000000000 test second.
Because LBBPc does not support

CPRI BER monitoring, the uplink
BER of LBBPc is displayed as
N/A.
Downlink BER e^(-9) 0 to Downlink BER in the N/A

1000000000 previous test second.
BER Threshold e^(-9) 0 to BER threshold. N/A
1000000000
If the actual measured
downlink and uplink BER is
greater than the threshold, the
link quality may be poor.

eNodeB
Performance Monitoring Reference 5 RRU Performance Monitoring
5 RRU 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 Interval of reporting monitoring results. It can be set to 1000,2000, or
(ms) 3000.

Table 5-2 Results of RRU/RFU Output Power monitoring

Range
Index of TX N/A 0 to 8 Index of TX channel. N/A

eNodeB

Range
Index of Carrier N/A 0 to 1 If only 0 is displayed, the N/A

RRU supports one carrier.
If both 0 and 1 are
displayed, the RRU/RFU
supports two carriers.
TX Freq of TX MHz 2750 to Downlink frequency of a N/A
Carrier[n] 3449 carrier.
Output power of 0.1 dBm 200 to 1 Output power of a carrier. N/A
TX Carrier[n]
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 Interval of reporting monitoring results. It can be set to 1000,2000, or
(ms) 3000.

eNodeB

Table 5-4 Results of RRU/RFU Temperature monitoring

Range
Board Temperature C 100 to Board temperature. N/A
+200
PA Temperature C 100 to Power amplifier (PA) N/A
+200 temperature.
Branch Index N/A 0 to 7 Index of PA. N/A
LPA Temperature C 100 to Low Power amplifier (LPA) N/A
+200 temperature.
5.3 Sector Performance Monitoring

Radio networks work in open environments and therefore are inevitably affected by external
interference. During network deployment and long-term network operation, external
interference must be detected and located. The base station is a receiver system and
supports wide bands. Therefore, it can be used to simply collect uplink interference
information, reducing manual workloads (for example, carrying instruments) during network
deployment and interference detection. Uplink frequency scanning helps to check the
electromagnetic environment around eNodeBs and detects internal interference in the
eNodeBs. 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 Interval of reporting monitoring results. It can be set to 50, 100, 200,
(ms) 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.

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

Table 5-6 Results of UL Widefreq Scan monitoring

Range
Signal Strength dBm 140 to 50 RSSI in each RB from the N/A
physical layer when the
monitoring result is reported.
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

eNodeB
located.
Slot No. Number of the slot where the board for spectrum detection is located.
RBW(Resolutio Time frequency of Fast Fourier Transport (FFT) frequency detection, in
n Bandwidth) 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
is 100 to 5000. The default value is 200.
Monitor Period Interval of reporting monitoring results. It can be set to 1000, 2000, or
(ms) 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
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
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
Rx Traffic bps 0 to Number of bits N/A
100000000 received every
second within a
monitoring period.
Tx Traffic bps 0 to Number of bits N/A
100000000 transmitted every
second within a
monitoring period.
Rx Packets Packet 0 to Number of received N/A
2000000 packets within a
monitoring period.
Tx Packets Packet 0 to Number of transmitted N/A
2000000 packets within a
monitoring period.
Rx Loss Packet 0 to Number of discarded N/A
Packets 2000000 incoming
packets within a
monitoring period.
Tx Inner Loss Packet 0 to Number of discarded N/A
Packets 2000000 outgoing packets within
a monitoring period.
Rx Loss Ratio 0 to 1000 Packet loss rate of Number of discarded
incoming incoming packets x
packets within a 1000/Total number of
monitoring period. incoming packets
Tx Inner Loss 0 to 1000 Internal packet loss rate Number of discarded
Ratio of outgoing outgoing packets x
packets within a 1000/Total number of
monitoring period. outgoing packets
Internal discarded
packets are the packets
discarded due to
internal congestion

eNodeB

Range
rather than the packets
discarded on
transmission links.
Rx bps 0 to Number of bits with the N/A
Traffic with 100000000 preamble and cyclic
Prefix/CRC redundancy check
(CRC) code received
every second within a
monitoring period.
Tx Traffic with bps 0 to Number of bits with the N/A
Prefix/CRC 100000000 preambles and CRC
code transmitted every
second within a
monitoring period.
Rx bps 0 to Number of bits with the N/A
Traffic with 100000000 minimum frame
Frame/Prefix/ interval, preamble, and
CRC cyclic redundancy
check (CRC) code
received every
second within a
monitoring period.
Tx Traffic with bps 0 to Number of bits with the N/A
Frame/Prefix/ 100000000 minimum frame
CRC interval, preamble, and
cyclic redundancy
check (CRC) code
transmitted every
second within a
monitoring period.
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
6.2.3 Parameters
Table 6-3 Parameters for IP path performance monitoring
IP PATH No. Number of the IP path.
Monitor Period Interval of reporting monitoring results. It is set to 1 by default.
(Seconds)

Table 6-4 Results of IP Path Performance monitoring

Range
Lost Packets 0.001 0 to 100000 Packet loss (Number of packets
Ratio % rate within a transmitted by the
monitoring period. 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 N/A
the IP path
transmitted by the
eNodeB per
second within a
monitoring period.
Average Delay ms 0 to 100 Average delay on (Sum of delays for
the IP path within a transmitting the IP PM
monitoring period. 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

Range
PMs.
Average Jitter ms 0 to 100 Average jitter on the Sum of jitters of all the
IP path within a IP PMs bound to the IP
monitoring period 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 Packe 0 to Total number of N/A
Number t 2000000 packets transmitted
on the IP
path within a
monitoring period.
Lost Packets Packe 0 to Total number of N/A
Number t 2000000 packets discarded
on the IP
path within a
monitoring period.
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
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.
(Seconds)

Table 6-6 Results of IP Performance monitoring
Parameter Unit Value Range Description Formula

Number Packet 0 to 2000000 Total number of packets at the IP N/A
increment of layer received by the board within
RX packets a monitoring period.
Number Packet 0 to 2000000 Total number of packets at the IP N/A
increment of layer transmitted by the
TX packets board within a measurement
period.
Number Packet 0 to 2000000 Total number of discarded N/A
increment of packets at the IP layer within a
discarded measurement period.
packets
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
6.4.3 Parameters
Table 6-7 Parameters for SCTP performance monitoring
Cabinet No. Number of the cabinet where the board for SCTP performance

eNodeB
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.
(Seconds)

Table 6-8 Results of SCTP Performance monitoring

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

eNodeB
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.
(Seconds)
Cabinet No. Number of the cabinet where the board for transmission
performance monitoring is located.
Subrack No. Number of the subrack where the board for transmission
performance monitoring is located.
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

eNodeB
performance 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
Receive Packets Packet 0 to 2000000 Number of packets the N/A

Ethernet port
receives within a
monitoring period.
Send Packets Packet 0 to 2000000 Number of packets the N/A
Ethernet port
transmits within a
monitoring period.
Receive Bytes bps 0 to 100000000 Number of bits the Ethernet N/A
port receives every
second within a monitoring
period.
Send Bytes bps 0 to 100000000 Number of bits the Ethernet N/A
port transmits every
period.
Receive Drop Packet 0 to 2000000 Number of discarded N/A
Packets packets the Ethernet port
receives within a
monitoring period.
Receive CRC Packet 0 to 2000000 Number of packets with N/A
Error Packets CRC errors the Ethernet
port receives every
period.
Send Drop Packet 0 to 2000000 Number of discarded N/A
Packets packets the Ethernet port
transmits within a
monitoring period.
PPP Performance

eNodeB
Table 6-11 Results of PPP Performance monitoring

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

eNodeB
Table 6-12 Results of MP Performance monitoring

Receive Packets Packet 0 to 2000000 Number of packets N/A
the MP group
receives within a
monitoring period.
Send Packets Packet 0 to 2000000 Number of packets N/A
the MP group
transmits within a
monitoring period.
Receive Bytes bps 0 to 100000000 Number of bits the N/A
MP group receives
monitoring period.
Send Bytes bps 0 to 100000000 Number of bits the N/A
MP group transmits
monitoring period.
Packets packets the MP group
receives within a
monitoring period.
Packets packets the MP group
transmits within a
monitoring period.
Receive Drop 0 to 1000 Loss rate of the Total number
Packets Ratio packets that the MP of discarded
group receives after packets the MP
the test is started. group receives
x 1000/Total
number of
packets the MP
group receives
Send Drop 0 to 1000 Loss rate of the Total number
Packets Ratio packets that the MP of discarded
group transmits after packets the MP
the test is started. group transmits
x 1000/Total
number of
packets the MP
group transmits

eNodeB
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.
(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 of the UDP packet. The value ranges from 72 to 1500.
LENGTH (BYTES) 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

Table 6-14 Result of UDP injection test monitoring

Range
Drop Packet 0 to 1000 Ratio of lost packets to total Number of
Ratio packets on the transmission discarded packets
link within a monitoring per minute x
period. 1000/Expected
number of packets
received on the
transmission link
per minute
Average Drop 0 to 1000 Average ratio of lost Total number of
Packet Ratio packets to total packets on discarded packets
the transmission link within x 1000/Total
a monitoring period. number of packets
Delay us 0 to 100 Delay on the transmission N/A
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.
Jitter N/A 0 to 100 Jitter on the transmission |Delay -
link within a monitoring Average Delay|/A
period. verage Delay
Average Delay us 0 to 100 Average delay on the N/A
transmission link within a
monitoring period.
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
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 Byte/s 0 to 100000000 Number of bytes received N/A
Traffic by the eNodeB per
period and that are destined
for the local eNodeB.
Local Send Byte/s 0 to 100000000 Number of bytes transmitted N/A
Traffic by the eNodeB within a
monitoring period,
excluding the forwarded
traffic.
eNodeB Bypass Byte/s 0 to 100000000 Number of bytes forwarded N/A
Traffic by the eNodeB per
period.
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
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 Number of the transport resource group for resource group
Group No. 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
Admission Kbps 0 to Admission N/A
Bandwidth (Tx) 1000000 bandwidth for data
transmission on the
current logical port
in single-rate
mode.
Admission Kbps 0 to Admission N/A
Bandwidth (Rx) 1000000 bandwidth for data
reception on the
in single-rate
mode.
GBR Load (Tx) Kbps 0 to Transport load for N/A
1000000 GBR service data

eNodeB

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

eNodeB
Dual Rate
Table 6-19 Results of Dual Rate monitoring

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

eNodeB

Range
in double-rate mode.
GBR Load Ratio (Tx) % 0 to 100 Transport load ratio of GBR Load (Tx
GBR service data kbit/s) x100
transmission on the /Admission
current logical port in Bandwidth (Tx
double-rate mode. kbit/s)
GBR Load Ratio (Rx) % 0 to 100 Transport load ratio of GBR Load (Rx
GBR service data kbit/s) x100
reception on the current /Admission
logical port in Bandwidth (Rx
double-rate mode. kbit/s)
CIR Load Ratio (Tx) % 0 to 100 Transport load
for
CIR bandwidth load non-flow-contr
ratio of data ollable services
transmission on the on the port(Tx
current logical port in kbit/s) x100
double-rate mode. /Available CIR
bandwidth(Tx
kbit/s)
CIR Load Ratio (Rx) % 0 to 100 Transport load
for
CIR bandwidth load non-flow-contr
ratio of data reception ollable services
on the current logical on the port(Rx
port in double-rate kbit/s) x100
mode. /Available CIR
bandwidth(Rx
kbit/s)
Resource Group Load Kbps 0 to Resource
(Tx) 1000000 Transport load for data Group Load
transmission on the (Tx
current logical port in kbit/s)/Admissi
double-rate mode. on Bandwidth
(Tx kbit/s)
Resource Group Load Kbps 0 to Resource
(Rx) 1000000 Transport load for data Group Load
reception on the current (Rx
logical port in kbit/s)/Admissi
double-rate mode. on Bandwidth
(Rx kbit/s)
PIR Load Ratio (Tx) % 0 to 100 Transport load
PIR bandwidth load
on the port(Tx
ratio of data
kbit/s) x100
transmission on the
/Available PIR
bandwidth(Tx
double-rate mode.
kbit/s)

eNodeB

Range
PIR Load Ratio (Rx) % 0 to 100 Transport load

PIR bandwidth load
on the port(Rx
ratio of data reception
kbit/s) x100
on the current logical
/Available PIR
port in double-rate
bandwidth(Rx
mode.
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

Table 6-21 Results of PPPoE performance monitoring

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

eNodeB
Performance Monitoring Reference 7 Cell Performance Monitoring
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
four operators. You can choose one or more operators.
In a non-RAN sharing scenario, this parameter is set to 0 by default.
(ms) 500, 1000, or 2000.

eNodeB

Table 7-2 Results of service satisfaction monitoring

Range
CN Operator ID N/A 0 to 3 ID of the operator for which N/A
satisfaction of service
monitoring is performed.
CN Operator % 0 to 100 GBR service degradation flag. N/A
GBR Degrade 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.
CN Operator UL % 0 to 100 Average QoS satisfaction N/A

QCI[n] Satisfaction rates of different uplink
rate of Service 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

eNodeB

Range
rate.
CN Operator DL % 0 to 100 Average QoS satisfaction N/A
QCI[n] Satisfaction rates of different downlink
rate of Service 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.
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
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.
In a non-RAN sharing scenario, this parameter is set to 0 by
default.
200, 500, 1000, or 2000.

RLC Throughput
Table 7-4 Results of RLC Throughput monitoring

Range
CN Operator ID N/A 0 to 3 ID of the operator N/A

for which general
throughput monitoring
is performed.
Cell Uplink RLC bps 0 to Uplink throughput of a (General uplink
Throughput 300000000 cell. Only RLC RLC throughput
payloads are included. (Byte) x 8) x
The RLC headers, 1000/Monitor
retransmitted data, and Period (ms)
state reports are
excluded.
Cell Downlink bps 0 to Downlink throughput (General downlink
RLC Throughput 300000000 of a cell. Only the RLC RLC throughput
payloads are included. (Byte) x 8) x
state reports are
excluded.
CN Operator Cell bps 0 to Uplink RLC throughput (Uplink RLC
Uplink RLC 300000000 of an operator of a cell. throughput of an
Throughput Only RLC payloads are operator of a cell

eNodeB

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

Range
for which general
is performed.
Cell GBR Traffic bps 0 to Uplink throughput of (General RLC
Uplink RLC 300000000 GBR services in a cell. throughput of
Throughput Only RLC payloads are uplink GBR
included. The RLC services (Byte) x 8)
headers, retransmitted x 1000/Monitor
are excluded.
Cell GBR bps 0 to Downlink throughput of (General RLC
Traffic Downlink 300000000 GBR services in a cell. throughput of
RLC Throughput Only RLC payloads are downlink GBR
included. The RLC services (Byte) x 8)
headers, retransmitted x 1000/Monitor
are excluded.
CN Operator Cell bps 0 to Uplink GBR service (Uplink GBR
GBR Traffic 300000000 throughput of an service throughput
Uplink RLC operator of a cell. Only of an operator of a
Throughput RLC payloads are cell (byte) x 8) x
included. The RLC 1000/Monitor
headers, retransmitted Period (ms)
data, and state reports
are excluded.
Operator Cell GBR bps 0 to Downlink GBR service (Downlink GBR

eNodeB

Range
Traffic Downlink 300000000 throughput of an service throughput
RLC Throughput operator cell. Only RLC of an operator of a
payloads are included. cell (Byte) x 8) x
state reports are
excluded.
RLC Throughput of NON-GBR service
Table 7-6 Results of RLC Throughput of NON-GBR service monitoring

Range
for which general
is performed.
Cell Non-GBR bps 0 to Uplink throughput of (General RLC
Traffic Uplink 300000000 non-GBR services in a throughput of
RLC Throughput cell. Only RLC uplink non-GBR
payloads are included. services (Byte) x 8)
The RLC headers, x 1000/Monitor
state reports are
excluded.
Cell Non-GBR bps 0 to Downlink throughput of (General RLC
Traffic Downlink 300000000 non-GBR services in a throughput of
RLC Throughput cell. Only RLC downlink non-GBR
payloads are included. services (Byte) x 8)
The RLC headers, x 1000/Monitor
state reports are
excluded.
CN Operator Cell bps 0 to Uplink throughput of General uplink
Non-GBR Traffic 300000000 non-GBR services in a RLC throughput of
Uplink RLC CN operator cell. Only non-GBR services
Throughput RLC payloads are in a CN operator
included. The RLC cell (Byte) x 8) x
are excluded.
CN Operator Cell bps 0 to Downlink throughput of General downlink
Non-GBR 300000000 non-GBR services in a RLC throughput of
Traffic Downlink CN operator cell. Only non-GBR services
RLC Throughput RLC payloads are in a CN operator
included. The RLC cell (Byte) x 8) x

eNodeB

Range
are excluded.
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.
In a non-RAN sharing scenario, this parameter is set to 0 by default.
(ms) 500, 1000, or 2000.

Table 7-8 Results of service statistics monitoring

Range
Service Number Number 0 to 4000 Total number of N/A
of QCI[n] services with different
QCIs when the monitoring

eNodeB

Range
result is reported. n ranges
from 1 to 9.
CN Operator ID N/A 0 to 3 ID of the operator for which N/A
service statistics monitoring
is performed.
CN Operator Number 0 to 4000 Total number of N/A
Service Number services with different QCIs
of QCI[n] for an operator when the
n ranges from 1 to 9.
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.
four operators. You can choose one or more operators. In a non-RAN
sharing scenario, this parameter is set to 0 by default.
(ms) 500, 1000, or 2000.

Keep UL Synch Users Number

eNodeB
Table 7-10 Results of Keep UL Synch Users Number monitoring

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

Range
General Users Number 0 to 2000 Number of Number of connected
Number connected users and users + Number of
users that are users that are requesting
requesting access to access to the E-UTRAN
the E-UTRAN in a
cell when the
reported.
Connected users are
active users and
non-active users.
Users that are
requesting access to
the E-UTRAN
consist of the users

eNodeB

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

Range

for which user
is performed.
NO-Activated Number 0 to 2000 Number of non-active N/A
Users Number users in a cell when
the monitoring result
is reported.
Non-active users are

eNodeB

Range
also known as
users with uplink
asynchronization.
CN Operator Number 0 to 2000 Number of non-active N/A
NO-Activated users of an
Users Number operator when the
reported. Non-active
users are also known
as users with uplink
asynchronization.
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.

In a non-RAN sharing scenario, this parameter is set to 0 by
default.
200, 500, 1000, or 2000.

eNodeB

Table 7-14 Results of RB usage monitoring

Range
Downlink Number 0 to Number of downlink RBs N/A
Equivalent 200000 used within a monitoring
Used RB period, which is the total number
Num of RBs used by paging messages
and system information blocks
(SIBs) within all transmission
time intervals (TTIs) in the
monitoring period.
Uplink Number 0 to Number of uplink RBs N/A
Equivalent 200000 used within a monitoring
Used RB period, which is the total number
Num of RBs occupied by the PUSCH,
PUCCH, and PRACH within all
TTIs in the monitoring period.
Downlink Number 0 to Number of RBs allocated for N/A
Freq Diversit 200000 downlink diversity
y Used RB scheduling within all TTIs in a
Num measurement period.
Freq Select 200000 downlink frequency selective
Used RB scheduling within all TTIs in a
Num monitoring period.
HARQ RB 200,000 downlink HARQ
Used RB retransmission within all TTIs in
Num a monitoring period.
Uplink Number 0 to Number of RBs used by the N/A
PUCCH RB 200000 PUCCH within all TTIs in a
Num monitoring period.
CN Operator N/A 0 to 3 ID of the operator for which RB N/A
ID usage monitoring is performed.
CN Number 0 to Number of downlink RBs used N/A
Operator Do 200000 by the PDSCH of the
wnlink operator within all TTIs in a
Equivalent monitoring period.
Used RB
Num
The value of this parameter
equals the actual number of
downlink RBs used by the
operator.
CN Operator Number 0 to Number of uplink RBs used by N/A

eNodeB

Range
Uplink 200000 the PUSCH of the
Equivalent operator within all TTIs in a
Used RB monitoring period.
Num
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.
(ms) 500, 1000, or 2000.

HII information
Table 7-16 Results of HII information monitoring

Valid RB Number 0 to 110 Number of available RBs N/A
Num in One in one HII when the
Hii sent monitoring result is

eNodeB

reported, which is the same
as the number of RBs
occupied by the current cell
bandwidth.
OI information
Table 7-17 Results of OI information monitoring

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

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

Range
Edge User Valid RB Number 0 to 110 Number of valid RBs in N/A
Num the available frequency
band for cell edge users
(CEUs) when the
reported.
Neighbor Cell List Information

eNodeB
Table 7-20 Results of Neighbor Cell List Information monitoring

Range
Valid Neighbor Number 0 to 32 Number of valid neighboring N/A
Cell Num cells used for ICIC when the
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). Two UEs successfully paired with MU-MIMO are called one
pair. Based on the monitoring result, the number of UEs paired with MU-MIMO in 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.
(ms) 500, 1000, or 2000.

Table 7-22 Results of MU-MIMO monitoring

MIMO UE Pair 0 to 64000 Number of UEs paired with N/A
Pair Num MU-MIMO when the
Two UEs paired with
MU-MIMO are called one pair.

eNodeB
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
RB Spectrum dBm 216 to RSSI of an RB. AntNumAntNum
AntIdx = 0 n = 0 {P(AntIdx, k, n)}
- 1 11
Information +216 The power of 12 RSSI_RB(k) =

AntNum
subcarriers in the where,
RB is summed
and then averaged AntNum indicates the number
for multiple of antennas for the current cell.
antennas. RSSIs
of the RBs falling P( ) indicates the
beyond the receive power of subcarrier n in
bandwidth are RBk received by antenna
reported as 0 by AntIdx.
layer 1.
RSSI dBm 140 to RSSI within the
(Received 50 current system
Signal Strength bandwidth. where,
Indicator)
SysRB indicates the number of
RBs in the current system
bandwidth.
System Number 6, 15, Current system N/A
Bandwidth 25, 50, bandwidth.

eNodeB

Range
(Number of 75, or
RB) 100
antenna[y] dBm 140 to RSSI for antenna SysRB 11
RSSI_Ant(AntIdx) = {P(AntIdx, k, n)}
RSSI 50 y within the k=0 n=0
current system where,

bandwidth. y AntNum indicates the number
ranges from 0 to of antennas for the current cell.
7.
P( ) indicates the
receive power of subcarrier n 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
PUSCH Cell dBm 215~215-1 Average interference

noise power of the

eNodeB

Range
PUSCH in the whole where,
system bandwidth. PUSCH_RB indicates the
number of RBs on the
current PUSCH.
Max RB Num 0 to 26 Current PUCCH N/A
Number of ber bandwidth (indicated
PUCCH by the number of
configured in RBs).
system
System Num 6, 15, 25, Current system N/A
Bandwidth ber 50, 75, 100 bandwidth.
(Number of
RB)
PUSCH dBm 215 to PUSCH interference
interference 215-1 noise power on the
Noise Power kth RB. Interference
of the RBs falling where,
per RB
beyond the PUSCH AntNum indicates the
bandwidth is number of antennas for the
reported as 0. current cell. IN(AntIdx, k,
n) indicates the receive
power of subcarrier n 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.

eNodeB
(ms) 500, 1000, or 2000.

Table 7-28 Results of scheduled cell-level UE information monitoring

Range
Total DLSCH Number 0 to 65535 Total number of UEs in N/A
Users Within downlink scheduling
Monitor Period mode within a monitoring
period.
Total DLSCH Number 0 to 65535 Total number of UEs in N/A
Frequency downlink frequency selective
Selected Users scheduling mode within a
Within Monitor monitoring period.
Period
Total DLSCH Di Number 0 to 65535 Total number of UEs in N/A
versity Users downlink diversity scheduling
Within Monitor mode within a monitoring
Period period.
Total ULSCH Number 0 to 65535 Total number of UEs in uplink N/A
Users Within scheduling mode within a
Monitor Period monitoring period.
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

eNodeB
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 Interval of reporting monitoring results. It can be set to 1000 or 2000.
(ms)

DL HARQ State
Table 7-30 Results of DL HARQ State monitoring

Range
DL PDSCH Code[m] Number 0 to Number of ACKs for N/A
ACK Num 64000 codeword m (m = {0,
1}) within a monitoring
period. 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.
DL PDSCH Code[m] Number 0 to Number of NACKs for N/A
NACK Num 64000 codeword m (m = {0,
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.
DL PDSCH Code[m] Number 0 to Number of NoRsps for N/A
NoRsp Num 64000 codeword m (m = {0,

eNodeB

Range
period. 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.
DL PDSCH Number 0 to Number of DTXs for N/A
Code[m] DTX Num 64000 codeword m (m = {0,
period. DTX indicates that
the eNodeB fails to detect the
HARQ feedback.
For details, see 3GPP TS
36.331.
DL PDSCH Number 0 to Number of times the HARQ N/A
Version[m] Num 64000 redundancy version in
transport blocks (TBs) sent
from the eNodeB is m (m =
{0, 1, 2, 3}) within a
monitoring period.
DL PDSCH Rsp for Number 0 to Number of times the eNodeB N/A
[m] TTI Num 64000 receives the HARQ
feedback within a downlink
scheduling interval m TTIs
(One TTI equals to one
millisecond) within a
monitoring period.
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

eNodeB

Range
processing exceptions.
UL HARQ State
Table 7-31 Results of UL HARQ State monitoring

Range
UL PUSCH ACK Num 0 to Number of times the CRC for N/A
Num ber 64000 data blocks on the PUSCH is
correct within a monitoring
ACKs to the total number of
ACKs, NACKs, and DTXs, the
more the times that the CRC
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 0 to Number of times the CRC for N/A
Num ber 64000 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.
UL PUSCH DTX Num 0 to Number of times the UE does N/A
Num ber 64000 not transmit data on the
PUSCH within a monitoring
proportion of the number
of DTXs to the total number of
less the times that the UE
receives data on the PDCCH.
UL PUSCH Num 0 to Number of times the HARQ N/A
Version[n] Num ber 64000 redundancy version for the
eNodeB uplink scheduling is m
(m = {0, 1, 2, 3}) within a
monitoring period.
36.321.

eNodeB
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.
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 Interval of reporting monitoring results. It can be set to 1000 or
(ms) 2000.

Table 7-33 Results of air-interface DCI status monitoring

Range
PDCCH Num 0 to 64000 Total number of N/A
Type DCI[n] ber times the PDCCH
Num type is DCI format n
(n = {0, 1, 1A, 1B,
1C, 1D, 2, 2A, 2B,
3, 3A}) within a
monitoring period.

eNodeB

Range
PDCCH Use [n] Num 0 to 64000 Total number of N/A
CCE Num ber times the
aggregation level is
n (n = {1, 2, 4,
8}) within a
monitoring period.
CFI Engross [n] Num 0 to 64000 Total number of N/A
Symbol State ber times the control
Num format indicator
(CFI) is n (n = {1, 2,
3, 4}) OFDM
symbols within a
monitoring period.
UL DCI % 0 to 100 Uplink DCI Total number of CCEs in
Utilization utilization within a uplink DCI/Total number
Within a monitoring period. of CCEs within the
Monitoring Uplink DCI is DCI monitoring period
Period format 0.
DL DCI % 0 to 100 Downlink DCI Total number of CCEs in
Utilization utilization within a downlink DCI/Total
Within a monitoring period. number of CCEs within
Monitoring Downlink DCI the monitoring period.
Period is DCI format
n, where n is 1, 1A,
1B, 1C, 1D, 2, 2A,
and 2B.
Comm DCI % 0 to 100 Common DCI Total number of CCEs in
Utilization utilization within a common DC/Total
Within a monitoring period. number of CCEs within
Monitoring Common DCI the monitoring period.
Period is DCI format 3
and DCI format 3A.
Total CCE Num Num 0 to Total number of N/A
Within a ber 100000 CCEs within a
Monitoring monitoring period.
Period If the CFI is a fixed
value, 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

eNodeB

Range
queried by running
the DSP
CELLPDCCHAL
GO command.
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
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.
(ms)

DL DRB STATISTIC
Table 7-35 Results of downlink DRB statistics monitoring

Range
Number of Packets Packet 0 to Total number of data N/A
Received at the DL 30000000 packets received by the
PDCP 0 downlink PDCP layer within
Number of Bits Bit 0 to Total throughput for data N/A

eNodeB

Range
Received at the DL 30000000 packets received by the
PDCP 0 downlink PDCP layer within
Number of TBs for DL Number 0 to Total number of TBs for N/A
MAC scheduling 30000000 downlink MAC
0 scheduling within a
monitoring period.
Number of Bits for DL Bit 0 to Total number of bits N/A
MAC scheduling 300,000,0 contained in the TBs for
00 downlink MAC
scheduling within a
monitoring period.
Number of Times DL Number 0 to Total number of times the N/A
RLC Sends Data in 30000000 downlink RLC layer
AM mode 0 transmits data in
acknowledgment (AM)
mode within a monitoring
period.
Number of Times DL Number 0 to Total number of times the N/A
RLC Sends Data in 30000000 downlink RLC layer
UM mode 0 transmits data in
unacknowledgment (UM)
mode within a monitoring
period.
UL DRB STATISTIC
Table 7-36 Results of uplink DRB statistics monitoring

Range
Number of TBs for UL Number 0 to Total number of TBs for N/A
MAC Scheduling 30000000 uplink MAC
0 scheduling within a
monitoring period.
Number of Bits for UL Bit 0 to Total number of bits N/A
MAC Scheduled 30000000 contained in the TBs for
0 uplink MAC
scheduling within a
monitoring period.
Number of UL TBs Number 0 to Total number of times the N/A
With CRC Correct 30000000 uplink MAC layer receives
0 correct CRCs from a
UE within a monitoring
period.

eNodeB

Range
Number of UL TBs Number 0 to Total number of times the N/A
With CRC Incorrect 30000000 uplink MAC layer receives
0 incorrect CRCs from a
UE within a monitoring
period.
Number of Times UL Number 0 to Total number of times the N/A
RLC Receives Data in 30000000 uplink RLC layer transmits
AM mode 0 data in AM mode within a
monitoring period.
Number of Times UL Number 0 to Total number of times the N/A
RLC Receives Data in 30000000 uplink RLC layer transmits
UM mode 0 data in UM mode within a
monitoring period.
Number of Packets Packet 0 to Total number of data N/A
Transmitted at the UL 30000000 packets transmitted by the
PDCP 0 uplink PDCP layer within
Number of Bits Bit 0 to Total throughput for data N/A
Transmitted at the UL 30000000 packets transmitted by the
PDCP 0 uplink PDCP layer within

eNodeB
Performance Monitoring Reference 8 User Performance Monitoring
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 of a user.

UEID-TMSI/Trace TMSI or trace reference number to be monitored.
Reference No.
480, 640, 1024, or 2048.

Table 8-2 Results of DL RSRP/RSRQ monitoring
ServCell PCI N/A N/A Physical cell ID of a serving N/A

cell.

eNodeB

ServCell RSRP dBm -140 to -44 RSRP of a serving cell. N/A
ServCell RSRQ dB -19.5 to -3 RSRQ of a serving cell. N/A
NeighborCell N/A N/A Physical cell ID of the nth N/A
PCI[n] 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.
NeighborCell dBm -140 to -44 RSRP of the nth neighboring N/A

RSRP[n] cell. n is an integer from 1 to 8.
NeighborCell dB -19.5 to -3 RSRQ of the nth neighboring N/A
RSRQ[n] cell. n is an integer from 1 to 8.
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.
Reference No.
200, 500, 1000, or 2000.

Init BLER

eNodeB
Table 8-4 Results of Init BLER monitoring

Range
Physical Cell N/A N/A Physical cell identifier N/A
Identifier of the serving cell.
Downlink 0 to BLER of initial TB Total number of TBs that
IBLER 1000 transmission on a fail to be initially
PDSCH within a transmitted on the PDSCH
monitoring period. x 1000/Total number of
initially transmitted TBs on
the PDSCH within the
monitoring period
Uplink 0 to BLER of initial TB Total number of TBs that
IBLER 1000 transmission on a fail to be initially
PUSCH within a transmitted on the PUSCH
monitoring period. 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
Downlink 0 to 1000 BLER of the last TB Number of times
RBLER retransmission on a TBs that last fail to
PDSCH within a be retransmitted on
monitoring period. the PDSCH x
1000/Total number
of initially
transmitted TBs on
the PDSCH within
the monitoring
period
Uplink RBLER 0 to 1000 BLER of the last TB Number of times
retransmission on a TBs that last fail to
PUSCH within a be retransmitted on
monitoring period. the PUSCH x
1000/Total number
of initially
transmitted TBs on
the PUSCH within
the monitoring
period

eNodeB
PDCCH BLER
Table 8-6 Results of PDCCH BLER monitoring

Range
Physical Cell N/A N/A Physical cell N/A
Identifier identifier of the
serving cell.
PDCCH BLER 0 to 1000 BLER Number of
of DLGRANT times DLGRANTs
decoding on a decoded incorrectly x
PDCCH within a 1000/Total number
monitoring period. 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

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.

None
8.3.3 Parameters
Table 8-7 Parameters for power headroom monitoring
UEID-TMSI/Tra TMSI or trace reference number to be monitored.
ce Reference No.

eNodeB
(ms) 500, 1000, or 2000.

Table 8-8 Result of power headroom monitoring

Range
Physical Cell N/A 0~503 Physical cell identifier of the N/A
Identifier serving cell.
Power Headroom dB 23 to +40 Power headroom last reported by N/A
the UE.
For details, see 3GPP TS 36.213,
36.321, and 36.133.
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
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 TMSI or trace reference number to be monitored.
e Reference No.

eNodeB
(ms) 500, 1000, or 2000.

SINR
Table 8-10 Results of SINR monitoring

Physical Cell N/A N/A Physical cell identifier of the N/A
SINR 0.01 dB 12700 to Average SINR for the full N/A
+12700 bandwidth of the eNodeB
monitored.
SINR Flag N/A N/A Flag specifying whether the N/A
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.
CQI
Table 8-11 Results of CQI monitoring

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

eNodeB

Range
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.
ce Reference No.
(ms) 500, 1000, or 2000.

UL SR of Service

eNodeB
Table 8-13 Results of UL SR of Service monitoring

Number of SRs Num 0 to 64000 Number of SRs reported by N/A
ber 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.
UL BSR of Service
Table 8-14 Results of UL BSR of Service monitoring

Range

Byte Length of LCG Bit 0 to 150000 Buffered data volume of the N/A
BS[n] 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
data from the UE, the eNodeB
subtracts corresponding data in
BSR[n].
36.321.
Percentage of DRX activity timer in DRX timer

eNodeB
Table 8-15 Results of Percentage of DRX activity timer in DRX timer monitoring

Range
TTIs in GAP Number 0 to Number of accumulated TTIs in N/A
State 4294967295 the call gapping (GAP) state
during the monitoring period.
For details, see 3GPP TS 36.213.
TTIs in DRX Number 0 to Number of accumulated TTIs in N/A
State 4294967295 the DRX state during the
monitoring period.
For details, see 3GPP TS 36.321.
Number of TTI Number 0 to Number of accumulated TTIs N/A
4294967295 between the establishment and the
release of an L2 case.
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
8.6.3 Parameters
Table 8-16 Parameters for RLC data stream monitoring
ce Reference No.
(ms) 500, 1000, or 2000.

eNodeB

Table 8-17 Result of RLC data stream monitoring

RLC Number N/A 0 to 8 Number of logical channels N/A
set up by users. The value 0
indicates that no default
bearer has been set up.
DRB No. N/A 1 to 8 ID of the logical channel for N/A
a bearer.
DRB RLC Byte 0 to 10000000 Data stream of the RLC N/A
Buffer Length SDUs to be sent on the data
radio bearer (DRB) from the
downlink buffer area at the
RLC layer when the
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
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.
e Reference No.

eNodeB
(ms) 500, 1000, or 2000.

Throughput of RLC
Table 8-19 Results of RLC throughput monitoring

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

Downlink MAC bps 0 to User-level downlink User-level
Throughput 300000000 MAC downlink MAC
throughputs within a throughputs within

eNodeB

monitoring period. a monitoring
period
Uplink MAC bps 0 to User-level uplink (Uplink MAC
Throughput 300000000 MAC throughputs(Byte)
throughputs within a x 8) x
monitoring period 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.
e Reference No.
(ms) 500, 1000, or 2000.

Table 8-22 Results of AQM monitoring

Range

eNodeB

Range
RLC Number N/A 0 to 8 Number of logical channels set up N/A
by users. The value 0 indicates
that no default bearer has been set
up.
DRB No. N/A 1 to 8 ID of the logical channel for a N/A
bearer.
Number of Packets Packet 0 to Number of RLC SDUs to be sent N/A
in RLC Buffer 20,000 on the DRB from the downlink
RLC buffer area at the end of a
monitoring period.
Number Packet 0 to Number of SDUs discarded by N/A
of Discarded 20,000 AQM.
Packets
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.
ce Reference No.
(ms) 500, 1000, or 2000.

eNodeB

Close-loop Power of UE
Table 8-24 Results of Close-loop Power of UE monitoring
Parameter Unit Value Description Form

Range ula
Physical Cell Identifier N/A N/A Physical cell identifier of N/A

the serving cell.
PUSCH IBLER target 0 to 1000 Target IBLER of PUSCH N/A
closed-loop power control.
The value is set by running
MML commands.
PUCCH SINR target 0.01 dB 1500 to Target SINR of PUCCH N/A
+2000 closed-loop power control.
The value is set by running
MML commands.
PUCCH SINR Adjust 0.01 dB 1500 to The difference between the N/A
Step +2000 actual SINR and the target
SINR of PUCCH
closed-loop power
control when the
reported.
PUSCH N max updated of UE
Table 8-25 Results of PUSCH N max updated of UE monitoring

Range

the serving cell.
Maximum Number of Number 0 to 10 The maximum number of N/A
Transmissions transmissions on the uplink
PUSCH. It is set by
running MML commands.
PUCCH ACK/NACK/DTX Statistic

eNodeB
Table 8-26 Results of PUCCH ACK/NACK/DTX Statistic monitoring

Range
Physical Cell N/A N/A Physical cell identifier of N/A
Identifier the serving cell.
Number of Number 0 to 2000 Number of ACKs detected N/A
PUCCH ACK on the PUCCH by the
eNodeB within a
monitoring period.
Number of Number 0 to 2000 Number of NACKs on the N/A
PUCCH NACK PUCCH detected by the
eNodeB within a
monitoring period.
Number of Number 0 to 2000 Number of DTXs on the N/A
PUCCH DTX PUCCH detected by the
eNodeB within a
monitoring period.
PUCCH SINR 0.01 dB 1500 to SINR value on the PUCCH N/A
+4000 detected by the
eNodeB within a
monitoring period.
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.

eNodeB
e Reference No.
(ms) 500, 1000, or 2000.

PDSCH UE
Table 8-28 Results of PDSCH UE monitoring

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

Range
Physical Cell N/A N/A Physical cell N/A
Identifier identifier of the
serving cell.
PHICH SINR 0.001 dB 1500 to Target SINR of N/A
Target +2000 PHICH
outer-loop power
control. The
value is set by

eNodeB

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

Range

the serving cell.
Power Offset of PDCCH 0.01 1500 to Offset between the N/A
dB +2000 power for transmitting
each RE on the PDCCH
and the pilot power when
the monitoring result is
reported.
TTI ms 0 to TTI for the PDCCH N/A
0xffffffff power transmitted at the
MAC layer.

eNodeB
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.
e Reference No.
(ms) 500, 1000, or 2000.

USER PROPERTY
Table 8-32 Results of USER PROPERTY monitoring

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

Range

eNodeB

Range
Strongest Neighbor N/A N/A Physical ID of the detected N/A
Cell neighbor cell with the best
signal quality among the cells
in the user neighbor list.
Sub-Strongest N/A N/A Physical ID of the detected N/A
Neighbor Cell neighbor cell with the second
best signal quality among the
cells in the user neighbor list.
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.
ce Reference No.
(ms)

DL MCS

eNodeB
Table 8-35 Results of DL MCS monitoring

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

Range
ULSCH Number 0 to 2000 Total number (n) of uplink N/A
Num[n] scheduling within a monitoring
period.
n = {0,31}
ULSCH Number 0 to Total number (n) of RBs in the N/A
RBs[n] 200,000 uplink scheduling within a
monitoring period.
n = {0,31}

eNodeB
Performance Monitoring Reference 9 Clock Performance Monitoring
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
Test Type N/A 1 Type of test result. 1 indicates N/A

phase offset.

eNodeB

Range
Count Value s 128~127 Current phase offset. N/A

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.
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

Table 9-4 Results of IP clock data collection

Range
Report SN N/A N/A Reserved. N/A
Tp1 Max QoS Value ns 263 to Maximum delay per second for N/A
2631 transmitting packets from the
clock server to the eNodeB
Tp1 Min QoS Value ns 263 to Minimum delay per second for N/A
clock server to the eNodeB
Tp2 Max QoS Value ns 263 to Maximum delay per second for N/A
eNodeB to the clock server
Tp2 Min QoS Value ns 263 to Minimum delay per second for N/A
eNodeB to the clock server


LTE

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

LTE

Caricato da

Copyright:

Formati disponibili

eNodeB

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential i

1 About this Document ................................................................................................................... 1

3 CPU Usage Monitoring ................................................................................................................ 6

4 CPRI BER Monitoring .................................................................................................................. 8

5 RRU Performance Monitoring.................................................................................................. 10

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential ii

5.3.1 Usage Scenario...................................................................................................................................... 12

6 Transmission Performance Monitoring.................................................................................. 15

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential iii

6.7.1 Usage Scenario...................................................................................................................................... 27

7 Cell Performance Monitoring ................................................................................................... 35

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential iv

7.6.1 Usage Scenario...................................................................................................................................... 47

8 User Performance Monitoring .................................................................................................. 62

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential v

8.1.1 Usage Scenario...................................................................................................................................... 62

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential vi

8.9.3 Parameters ............................................................................................................................................. 74

9 Clock Performance Monitoring ................................................................................................ 82

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential vii

1 About this Document

Product Name Product Version

DBS3900 LTE V100R005C00

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 1

Topic Change Description

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 2

2.2 Performance Monitoring Types

Type Task Platform

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 3

Type Task Platform

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 4

2.3 Background Information

2.3.1 Precautions for Monitoring on 3900 Series Base Station

2.3.2 Precautions for Monitoring on BTS3202Es

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 5

3 CPU Usage Monitoring

3.1 CPU Usage Monitoring

3.1.2 Service Impact

3.1.4 Monitoring Results

Parameter Unit Value Description Formula

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 6

Parameter Unit Value Description Formula

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 7

4 CPRI BER Monitoring

4.1 CPRI BER Monitoring

4.1.2 Service Impact

The upper-level node mentioned in this table is the node connected

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 8

The lower-level node mentioned in this table is the node connected

4.1.4 Monitoring Results

Parameter Unit Value Description Formula

Because LBBPc does not support

Downlink BER e^(-9) 0 to Downlink BER in the N/A

Issue Draft B (2012-07-24) Huawei Proprietary and Confidential 9

5 RRU Performance Monitoring

5.1 RRU/RFU Output Power Monitoring

5.1.2 Service Impact

5.1.4 Monitoring Results

Parameter Unit Value Description Formula

Index of TX N/A 0 to 8 Index of TX channel. N/A